[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#930446: marked as done (popularity-contest: unable to submit report, impossible to debug)

Your message dated Mon, 30 Mar 2020 21:03:29 +0000
with message-id <E1jJ1ZB-00070l-Ge@fasolo.debian.org>
and subject line Bug#930446: fixed in popularity-contest 1.70
has caused the Debian Bug report #930446,
regarding popularity-contest: unable to submit report, impossible to debug
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
930446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930446
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: popularity-contest
Version: 1.67
Severity: normal

Dear Maintainer,

on several of my hosts, popularity-contest logs

  unable to submit report to http://popcon.debian.org/cgi-bin/popcon.cgi.
  unable to submit report.

But it does not log why and there is no way that I could find to trigger
the sending from the command line with debug output enabled.

http://popcon.debian.org/cgi-bin/pop is reachable from the host via curl. Also,
according to the documentation it should fall back to email, which it does not
do. It does not log why it does not do that.

Cheers,
Stefan

Relevant parts of /etc/popularity-contest.conf (without MY_HOSTID):

PARTICIPATE="yes"
USEHTTP="yes"
DAY="2"



-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages popularity-contest depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  dpkg                   1.19.7

Versions of packages popularity-contest recommends:
ii  cron [cron-daemon]                         3.0pl1-133
ii  exim4-daemon-light [mail-transport-agent]  4.92-7
ii  gnupg                                      2.2.12-1

Versions of packages popularity-contest suggests:
pn  anacron   <none>
pn  tor       <none>
pn  torsocks  <none>

-- debconf information:
* popularity-contest/participate: true
  popularity-contest/submiturls:

--- End Message ---
--- Begin Message --- 
Source: popularity-contest
Source-Version: 1.70
Done: Bill Allombert <ballombe@debian.org>

We believe that the bug you reported is fixed in the latest version of
popularity-contest, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 930446@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bill Allombert <ballombe@debian.org> (supplier of updated popularity-contest package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 30 Mar 2020 19:47:56 +0200
Source: popularity-contest
Architecture: source
Version: 1.70
Distribution: unstable
Urgency: low
Maintainer: Popularity Contest Developers <debian-popcon@lists.debian.org>
Changed-By: Bill Allombert <ballombe@debian.org>
Closes: 865730 930446
Changes:
 popularity-contest (1.70) unstable; urgency=low
 .
   * debian-popcon.gpg: use new submission key
   * debian/cron.daily:
     - fix reporting logic to avoid double submissions.  Closes: #930446
     - store last successful http submission timestamp in
       /var/lib/popularity-contest/lastsub.
     - run 'popularity-contest --su-nobody' as root. This allows
       popcon to read the configuration file and /proc/*/maps files.
       Closes: #865730. Thanks Robert Luberda.
     - rename /var/log/popularity-contest.new.gpg to
              /var/log/popularity-contest.gpg
   * debian/control:
     - Updated Standards-Version from 4.4.0 to 4.5.0.  No change needed.
     - Build-Depends on debhelper-compat (=12)
   * debian/compat: removed
   * Update example server-side scripts to popcon.d.o version:
     - popanal.py: bump stable version to 1.67
     - popcon.pl: update URL from Alioth to Salsa
   * popularity-contest:
     - add private option --su-nobody to drop privileges after reading
       the configuration file and /proc.
   * examples/bin/popanal3.py:
     - Python 3 version of popanal.py (experimental), will replace popanal.py
Checksums-Sha1:
 f3fa5c385cea4b24a26938dfd9ac08bab5b28825 1731 popularity-contest_1.70.dsc
 c484771485b29f1d64d59c01ba0101347bd155b4 77748 popularity-contest_1.70.tar.xz
 07a1de63175a9bf11a486994b8aef0c10b38d51b 5800 popularity-contest_1.70_source.buildinfo
Checksums-Sha256:
 9cc11b3169350f767129e08bf9abf8b3a6e3290cdf9ab2a4230846c74c665aa0 1731 popularity-contest_1.70.dsc
 b1b399e1c89d2fbc79ad7a699cce59721494b8020d77a904fa5ba332d905fae4 77748 popularity-contest_1.70.tar.xz
 5883cf1fa15e0ed39354f8b571cd25babed978f365f5fd6531a72891c00a2e22 5800 popularity-contest_1.70_source.buildinfo
Files:
 a15bebcb72a334aa568a70839f035b32 1731 misc optional popularity-contest_1.70.dsc
 c1dff74f6f91b293ddf7f66e6d666295 77748 misc optional popularity-contest_1.70.tar.xz
 a628bdd5e00d85f6138eb013607b1241 5800 misc optional popularity-contest_1.70_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAl6CVaYACgkQjw58K0Ui
44eUpBAAi615dw0FIqCL5VIdQuB5CFxTtXGIvBlAxrAmvIqp0NAnLnkpe1InR07I
wGHMpUW97i15/AQ8XANrQOKqDmGmP3yT4inMvdJyYOPVFHQyBsrd0zByK8NK5o5W
B+LsKeihftsVlJBMZuBA1DN9iplT93yrzsXUAN0EBkOdc9RgnBnU2uHhImAflFbn
W9MW3MQbgD6X+WUDrrSAxv7DbpDTmFjk52jW5JasFRC5tELcxRdOR4NyoC4lJiBB
2q5HmZqnAtg/9vChBGpu1raAMtvMPrqvg71Bd+DZHXPkP7dNQm402y51JLIFUJFp
SCOrABXJuxDUJIz8IPO60P0xoFNZfaV4ZZ630VxWlj3cuTUGrjh9A2vYVnr4I+WZ
JN1pk0HtWzqjLKS6OnjaDrLzlv4Fyfp9yPyJzZOaz3fQWCUfXvVDBsLRB1NCzme5
LS08aBWMfWPoirNFLHHb7OVYiObkvMGif7g0sKwQeKmWY0Ti+tHxpKytqTncYS1Y
I5/pa13H3KkWEXZUTCOc8ZozlZZMKwYSBCMb38nzLBaR+TJ12T+BXTxmuyecekJR
MN9rHJjMpJPep/F0MnMqm7UW5c412rw5KFNc5kJwhfLAgGgAaBwKOL7UTDwfteRh
4awTM+TjKRHkT3tl4BdWYceCLsyqVL66pZs745L1cVkXoS5czUY=
=vJLM
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: