Debian Bug report logs - #833695
popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz contains invalid data

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: submit@bugs.debian.org

Subject: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz contains

Date: Mon, 08 Aug 2016 01:07:18 +0200

Package: popularity-contest
Version: 1.64
Severity: serious
X-Debbugs-CC: reproducible-builds@lists.alioth.debian.org

Hi,

Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file
contains an invalid line:

    Package: libfyba0-dbg                       0     2     0     0
--> Package: libf erdp-ommon                    0     0     0     1
    Package: libg++2.8.1.3-dbg                  0     0     0     1

That's (currently) line 54869. The "space" on the second line is actually
a 0xa0 character. This results in a few issues in dependent packages,
hence the RC severity.

$ python3
Python 3.5.2+ (default, Aug  5 2016, 08:07:14) 
[GCC 6.1.1 20160724] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import popcon
>>> popcon.package("foo")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/popcon.py", line 145, in package
    raw = package_raw(*packages)
  File "/usr/lib/python3/dist-packages/popcon.py", line 189, in package_raw
    data = _fetch()
  File "/usr/lib/python3/dist-packages/popcon.py", line 108, in _fetch
    txt = _decompress(txt)
  File "/usr/lib/python3/dist-packages/popcon.py", line 134, in _decompress
    data = data.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 3574857: invalid start byte

You can see this happening here:

  https://jenkins.debian.net/view/reproducible/view/problems/job/reproducible_html_notes/

It also may also affect other packages:

  https://codesearch.debian.net/search?q=all-popcon-results.txt.gz&perpkg=1


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #14 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Chris Lamb <lamby@debian.org>, 833695@bugs.debian.org

Subject: Re: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

Date: Mon, 8 Aug 2016 11:18:45 +0200

On Mon, Aug 08, 2016 at 01:07:18AM +0200, Chris Lamb wrote:
> Package: popularity-contest
> Version: 1.64
> Severity: serious
> X-Debbugs-CC: reproducible-builds@lists.alioth.debian.org
> 
> Hi,
> 
> Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file
> contains an invalid line:
> 
>     Package: libfyba0-dbg                       0     2     0     0
> --> Package: libf erdp-ommon                    0     0     0     1
>     Package: libg++2.8.1.3-dbg                  0     0     0     1
> 
> That's (currently) line 54869. The "space" on the second line is actually
> a 0xa0 character. This results in a few issues in dependent packages,
> hence the RC severity.

Hello Chris,

Please do not inflate bug severity.

This is not a bug in the Debian package since it only provide the client side.
It would be pointless to remove it from testing due to this.

The popcon server neer promised that all-popcon-results.txt.gz was a
valid UTF8 file. Software must not assume that.

Please reassign to python-popcon.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #19 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Bill Allombert <ballombe@debian.org>, 833695@bugs.debian.org

Cc: reproducible-builds@lists.alioth.debian.org

Subject: Re: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

Date: Mon, 08 Aug 2016 11:34:43 +0200

> Please reassign to python-popcon.

Well, there are perhaps two bugs here, so simply reassigning won't be
sufficient:

Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
the client should not be removed from testing but I could not find a
suitable pseudo-package for the popcon "web" service.

(The code that generates this file appears to be in the popularity-contest
source package, hence why I filed it here)

Where should this issue be raised? I don't care about the severity, more
that it gets fixed. How can I help? :)


Secondly, src:python-popcon assumes valid data. Perhaps. But it would
still have to raise an error if it could not parse the file so there's
not much it could reasonably do. It *could* print a nicer exception so
its easier to track down the problem, but that's purely aesthetic..


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #24 received at 833695-done@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Chris Lamb <lamby@debian.org>

Cc: 833695-done@bugs.debian.org

Subject: Re: [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

Date: Mon, 8 Aug 2016 12:58:48 +0200

On Mon, Aug 08, 2016 at 11:34:43AM +0200, Chris Lamb wrote:
> > Please reassign to python-popcon.
> 
> Well, there are perhaps two bugs here, so simply reassigning won't be
> sufficient:
> 
> Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
> the client should not be removed from testing but I could not find a
> suitable pseudo-package for the popcon "web" service.

You could report the issue on the popcon-developers list.

It is not invalid data, the server reports what was submitted.

> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 3574857: invalid start byte

The issue is that python-popcon assumes that the file is in UTF-8 while
it is actually in raw 8-bit.
There are normally no valid multibyte UTF8 sequence in this file, so it
is pointless to handle it as UTF-8 anyway.

I close this bug. Feel free to discuss this on the popcon-developers list.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #29 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Holger Levsen <holger@layer-acht.org>

To: Reproducible Builds discussion list <reproducible-builds@lists.alioth.debian.org>

Cc: Bill Allombert <ballombe@debian.org>, 833695@bugs.debian.org, control@bugs.debian.org

Subject: Re: [Reproducible-builds] [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

Date: Mon, 8 Aug 2016 11:17:46 +0000

[Message part 1 (text/plain, inline)]

reopen 833695
severity 833695 important
clone 833695 -1
reassign -1 python-popcon
severity -1 normal
retitle -1 python-popcon must not crash on invalid data
thanks

On Mon, Aug 08, 2016 at 11:34:43AM +0200, Chris Lamb wrote:
> > Please reassign to python-popcon.
> 
> Well, there are perhaps two bugs here, so simply reassigning won't be
> sufficient:
> 
> Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
> the client should not be removed from testing but I could not find a
> suitable pseudo-package for the popcon "web" service.
>
> (The code that generates this file appears to be in the popularity-contest
> source package, hence why I filed it here)

Bill, following this I have reopened the bug and downgraded the
severity. 
 
> Where should this issue be raised? I don't care about the severity, more
> that it gets fixed. How can I help? :)

I also disagree with merely tracking an issue which breaks Debian
infrastrcuture on a mailinglist instead of a proper bug tracker.

Bill, if you really insist #833695 should not be assigned at
popularity-contest then please reassign it to qa.debian.org
pseudo-package.

> Secondly, src:python-popcon assumes valid data. Perhaps. But it would
> still have to raise an error if it could not parse the file so there's
> not much it could reasonably do. It *could* print a nicer exception so
> its easier to track down the problem, but that's purely aesthetic..

agreed, but that still would be nice, thus the cloned bug.


-- 
cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message #40 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Holger Levsen <holger@layer-acht.org>

Cc: Reproducible Builds discussion list <reproducible-builds@lists.alioth.debian.org>, Bill Allombert <ballombe@debian.org>, 833695@bugs.debian.org

Subject: Re: [Reproducible-builds] [Popcon-developers] Bug#833695: popularity-contest: http://popcon.debian.org/all-popcon-results.txt.gz containso

Date: Sat, 17 Jun 2017 14:44:18 +0200

On Mon, Aug 08, 2016 at 11:17:46AM +0000, Holger Levsen wrote:
> On Mon, Aug 08, 2016 at 11:34:43AM +0200, Chris Lamb wrote:
> > > Please reassign to python-popcon.
> > 
> > Well, there are perhaps two bugs here, so simply reassigning won't be
> > sufficient:
> > 
> > Firstly, all-popcon-results.txt.gz contains invalid data. I agree that
> > the client should not be removed from testing but I could not find a
> > suitable pseudo-package for the popcon "web" service.
> >
> > (The code that generates this file appears to be in the popularity-contest
> > source package, hence why I filed it here)
> 
> Bill, following this I have reopened the bug and downgraded the
> severity. 
>  
> > Where should this issue be raised? I don't care about the severity, more
> > that it gets fixed. How can I help? :)
> 
> I also disagree with merely tracking an issue which breaks Debian
> infrastrcuture on a mailinglist instead of a proper bug tracker.
> 
> Bill, if you really insist #833695 should not be assigned at
> popularity-contest then please reassign it to qa.debian.org
> pseudo-package.

Were you saying that the qa.debian.org website is using python-popcon
and so was broken because of this ? In that case, yes, it would
have been appropriate to report the bug there.

In any case, could you deal with this bug, either by closing it or by
reassigning it ? Thanks.

There is nothing I can do from my side.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #45 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <aoki.osamu@gmail.com>

To: 833695@bugs.debian.org

Cc: popcon-developers@lists.alioth.debian.org, Chris Lamb <lamby@debian.org>

Subject: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 14:29:53 +0900

Hi,

I just noticed popcon data is full of strange package names with illegal
characters:

 ^@    (Ox00)
 ^A    (Ox01)
 /
 <
 -     (starting)
 _
 .

Situation may be getting worse than what Chris reported as I see the
data.

For example:
Package: /mCTge2x                           0     0     0     1
Package: /miv5p4ngaN05^Atkg-30/iLe/usro0400     0     0     0     1
Package: /ml/ccSe3d1emdyn03bCe5.-mt6        0     0     0     1
Package: /onninpxs3modeits                  0     0     0     1
Package: /r3n4qLD9341s0OsMsl2l0160m00       0     0     0     1
Package: /r3n4qLD93Osk.jarrac5502e/gsa00     0     0     0     1
Package: /sa                                0     0     0     1
Package: /sbin/setcap                       0     0     0     1
Package: /shinrmsgmaddrr0aatngs1xir/-0H0o9urWxm/d0a6     0     0     0     1
Package: /su<Olibqmi-proxy                  0     0     0     1
Package: /tc6                               0     0     0     1
Package: /tcEMT_neeeearly2Oonur             0     0     0     1
Package: /toovcbietdiauliai6_nib3_rsnpranoe/ia/i6_nib3mcpdds-dn     0     0     0     1
Package: /toovctpa.erNv8ATIwdcw.cagx0eemb/nbualry/yc._-r0eemb/nbualry/yc._-r0eemb/nbualry/yc._-no6i1mkbubr5iriumglscbubr5iriumsceiumgrsR0np/0/r.-sR0np/0.h3oipsR0np/0/gg_C2dxmhlwpe.aPi1/ez6ve-HI1ss_r/ezkaa/p.ouaoec._n.gg_Cnib3_-r0eem.4t4/W2ht-/es0/gdaspp.oss-r0eem.4t4/W2ht-/es0/gdaspp.oss-r0eem.4t4t4gyefziimimweltthjo.eb.g6miis0ai6isPsTU4ygy6Mhpaterap8i-     0     0     0     1
Package: /u                                 0     0     0     1
Package: /u-CT0                             0     0     0     1
Package: /u-CTbin                           0     0     0     1
Package: /u0240akla                         0     0     0     1
Package: /u0k-52Lples2T-gb_it0600           0     0     0     1
Package: /u2Bit.duntsse-mby-sr/nk94400      0     0     0     1
Package: /u3Tuby-crhashemk3bsetuTuby-crhashemk3bsetuTuby-crhashemk3bsetuTuby-ashemk3bsetu.bsetuTuby-ashemk3bsetu.bsetuTubyr.m.Dte-CTI     0     0     0     1
Package: /u4yWa1bpython3-pyc-n_ty           0     0     0     1

Then I saw this bug report.

I think popcon data gathering tool should filter out the entire report
from the client sending bogus data.

This maybe just broken user hacked client but this may be some kind of
intrusion efforts.  Chris's comment seems toindicate these are caused by
a bug.  That's better than what I was afraid.

These useless data may choke other parsers (I parse this to make a set
of data for debian-reference).

For now, I will filter these data out here ...

Chris, who should we ask to get this fixed?

Regards,

Osamu

Message #50 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Chris Lamb <lamby@debian.org>

To: Osamu Aoki <aoki.osamu@gmail.com>, 833695@bugs.debian.org

Cc: popcon-developers@lists.alioth.debian.org

Subject: Re: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 08:40:37 +0100

Hi Osamu,

> Chris, who should we ask to get this fixed?

I'm not sure I'm the best person to ask; I maintain neither the source
of the data nor the library :)


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

Message #55 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Osamu Aoki <aoki.osamu@gmail.com>, 833695@bugs.debian.org

Subject: Re: [Popcon-developers] Bug#833695: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 12:44:24 +0200

On Mon, Sep 18, 2017 at 02:29:53PM +0900, Osamu Aoki wrote:
> Hi,
> 
> I just noticed popcon data is full of strange package names with illegal
> characters:
> 
>  ^@    (Ox00)
>  ^A    (Ox01)
>  /
>  <
>  -     (starting)
>  _
>  .
> 
> Situation may be getting worse than what Chris reported as I see the
> data.
> 
> For example:
> Package: /mCTge2x                           0     0     0     1
> Package: /miv5p4ngaN05^Atkg-30/iLe/usro0400     0     0     0     1
> Package: /ml/ccSe3d1emdyn03bCe5.-mt6        0     0     0     1
> Package: /onninpxs3modeits                  0     0     0     1
> Package: /r3n4qLD9341s0OsMsl2l0160m00       0     0     0     1
> Package: /r3n4qLD93Osk.jarrac5502e/gsa00     0     0     0     1
> Package: /sa                                0     0     0     1
> Package: /sbin/setcap                       0     0     0     1
> Package: /shinrmsgmaddrr0aatngs1xir/-0H0o9urWxm/d0a6     0     0     0     1
> Package: /su<Olibqmi-proxy                  0     0     0     1
> Package: /tc6                               0     0     0     1
> Package: /tcEMT_neeeearly2Oonur             0     0     0     1
> Package: /toovcbietdiauliai6_nib3_rsnpranoe/ia/i6_nib3mcpdds-dn     0     0     0     1
> Package: /toovctpa.erNv8ATIwdcw.cagx0eemb/nbualry/yc._-r0eemb/nbualry/yc._-r0eemb/nbualry/yc._-no6i1mkbubr5iriumglscbubr5iriumsceiumgrsR0np/0/r.-sR0np/0.h3oipsR0np/0/gg_C2dxmhlwpe.aPi1/ez6ve-HI1ss_r/ezkaa/p.ouaoec._n.gg_Cnib3_-r0eem.4t4/W2ht-/es0/gdaspp.oss-r0eem.4t4/W2ht-/es0/gdaspp.oss-r0eem.4t4t4gyefziimimweltthjo.eb.g6miis0ai6isPsTU4ygy6Mhpaterap8i-     0     0     0     1
> Package: /u                                 0     0     0     1
> Package: /u-CT0                             0     0     0     1
> Package: /u-CTbin                           0     0     0     1
> Package: /u0240akla                         0     0     0     1
> Package: /u0k-52Lples2T-gb_it0600           0     0     0     1
> Package: /u2Bit.duntsse-mby-sr/nk94400      0     0     0     1
> Package: /u3Tuby-crhashemk3bsetuTuby-crhashemk3bsetuTuby-crhashemk3bsetuTuby-ashemk3bsetu.bsetuTuby-ashemk3bsetu.bsetuTubyr.m.Dte-CTI     0     0     0     1
> Package: /u4yWa1bpython3-pyc-n_ty           0     0     0     1
> 
> Then I saw this bug report.
> 
> I think popcon data gathering tool should filter out the entire report
> from the client sending bogus data.
> 
> This maybe just broken user hacked client but this may be some kind of
> intrusion efforts.  Chris's comment seems toindicate these are caused by
> a bug.  That's better than what I was afraid.
> 
> These useless data may choke other parsers (I parse this to make a set
> of data for debian-reference).
> 
> For now, I will filter these data out here ...

I will have a look, but this bug report is unrelated.
I do not want to be in the business of deciding what it is valid and what
is not.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #60 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Osamu Aoki <aoki.osamu@gmail.com>

To: Bill Allombert <ballombe@debian.org>

Cc: 833695@bugs.debian.org

Subject: Re: [Popcon-developers] Bug#833695: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 20:51:14 +0900

Hi,

On Mon, Sep 18, 2017 at 12:44:24PM +0200, Bill Allombert wrote:
> I will have a look, but this bug report is unrelated.
> I do not want to be in the business of deciding what it is valid and what
> is not.

Ok, no one seem to know who to get this fixed.

Just FYI:

> >  ^@    (Ox00)
This causes grep to choke.

I worked around the problem by changing "grep" to
  grep --binary-files=text

Osamu

Message #65 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Osamu Aoki <aoki.osamu@gmail.com>

Cc: Bill Allombert <ballombe@debian.org>, 833695@bugs.debian.org

Subject: Re: [Popcon-developers] Bug#833695: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 14:01:33 +0200

On Mon, Sep 18, 2017 at 08:51:14PM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Mon, Sep 18, 2017 at 12:44:24PM +0200, Bill Allombert wrote:
> > I will have a look, but this bug report is unrelated.
> > I do not want to be in the business of deciding what it is valid and what
> > is not.
> 
> Ok, no one seem to know who to get this fixed.
> 
> Just FYI:
> 
> > >  ^@    (Ox00)
> This causes grep to choke.

Could you clarify which files exactly have this ?

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #70 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Osamu Aoki <aoki.osamu@gmail.com>, 833695@bugs.debian.org

Cc: Chris Lamb <lamby@debian.org>, popcon-developers@lists.alioth.debian.org

Subject: Re: [Popcon-developers] Bug#833695: strange popcon data on web (getting worse)

Date: Mon, 18 Sep 2017 16:41:00 +0200

On Mon, Sep 18, 2017 at 02:29:53PM +0900, Osamu Aoki wrote:
> For example:
> Package: /mCTge2x                           0     0     0     1
> Package: /miv5p4ngaN05^Atkg-30/iLe/usro0400     0     0     0     1
> Package: /ml/ccSe3d1emdyn03bCe5.-mt6        0     0     0     1
> Package: /onninpxs3modeits                  0     0     0     1
> Package: /r3n4qLD9341s0OsMsl2l0160m00       0     0     0     1
> Package: /r3n4qLD93Osk.jarrac5502e/gsa00     0     0     0     1
> Package: /sa                                0     0     0     1
> Package: /sbin/setcap                       0     0     0     1
> Package: /shinrmsgmaddrr0aatngs1xir/-0H0o9urWxm/d0a6     0     0     0     1

I have found and removed the file with this line.
It looks like a valid submission that was corrupted in transit.
I will try to improve the server code to discard that. 

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #75 received at 833695@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: Bill Allombert <ballombe@debian.org>, 833695@bugs.debian.org

Cc: Osamu Aoki <aoki.osamu@gmail.com>, Chris Lamb <lamby@debian.org>, popcon-developers@lists.alioth.debian.org

Subject: Re: [Popcon-developers] Bug#833695: Bug#833695: strange popcon data on web (getting worse)

Date: Tue, 19 Sep 2017 00:58:07 +0200

On Mon, Sep 18, 2017 at 04:41:00PM +0200, Bill Allombert wrote:
> On Mon, Sep 18, 2017 at 02:29:53PM +0900, Osamu Aoki wrote:
> > For example:
> > Package: /mCTge2x                           0     0     0     1
> > Package: /miv5p4ngaN05^Atkg-30/iLe/usro0400     0     0     0     1
> > Package: /ml/ccSe3d1emdyn03bCe5.-mt6        0     0     0     1
> > Package: /onninpxs3modeits                  0     0     0     1
> > Package: /r3n4qLD9341s0OsMsl2l0160m00       0     0     0     1
> > Package: /r3n4qLD93Osk.jarrac5502e/gsa00     0     0     0     1
> > Package: /sa                                0     0     0     1
> > Package: /sbin/setcap                       0     0     0     1
> > Package: /shinrmsgmaddrr0aatngs1xir/-0H0o9urWxm/d0a6     0     0     0     1
> 
> I have found and removed the file with this line.
> It looks like a valid submission that was corrupted in transit.
> I will try to improve the server code to discard that. 

I have found 48 others corrupted files. I removed them.
I have tweaked the server code as well.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 

Message #82 received at 833695-close@bugs.debian.org (full text, mbox, reply):

From: Bill Allombert <ballombe@debian.org>

To: 833695-close@bugs.debian.org

Subject: Bug#833695: fixed in popularity-contest 1.66

Date: Tue, 20 Feb 2018 22:41:58 +0000

Source: popularity-contest
Source-Version: 1.66

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 833695@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: Tue, 20 Feb 2018 14:56:14 +0100
Source: popularity-contest
Binary: popularity-contest
Architecture: source all
Version: 1.66
Distribution: unstable
Urgency: medium
Maintainer: Popularity Contest Developers <debian-popcon@lists.debian.org>
Changed-By: Bill Allombert <ballombe@debian.org>
Description:
 popularity-contest - Vote for your favourite packages automatically
Closes: 833695 865718 865728 865748
Changes:
 popularity-contest (1.66) unstable; urgency=medium
 .
   * popularity-contest: Ignore files under /usr/lib/mime/packages/
     for voting.  Closes: #865728. Thanks Robert Luberda.
   * Migrate popcon.debian.org to https. Thanks Julien Cristau.
   * debian/control:
     - Set Maintainer to debian-popcon@lists.debian.org.
     - Set Vcs-Git/Vcs-Browser to salsa.debian.org
     - Updated Standards-Version from 3.9.8 to 4.1.3.  No change needed.
   * README: update for salsa migration
   * debian/source/format: added: move to (3.0) native format.
   * debian-popcon.gpg: use new submission key
   * examples/bin/popanal.py:
     - reject lines with malformed timestamp. Closes: #833695.
   * examples/bin/popcon-process.sh:
     - add support for gpg2
   * Update example server-side scripts to popcon.d.o version.
   [Robert Luberda]
   * popularity-contest: handle dpkg diversions. Closes: #865748
   [Paul Wise]
   * Change the Linux Counter URL to the new domain.
   * Use https instead of http in URLs where possible.
     Closes: #865718
Checksums-Sha1:
 4320ebdd1914971be64156cc35db5df13c0a2f86 1724 popularity-contest_1.66.dsc
 adce58f244d1df46e3cbb4e2da30e22e41bfc8f6 78420 popularity-contest_1.66.tar.xz
 173863939d5f6076fa8971c2a33ae3047e1a33de 68852 popularity-contest_1.66_all.deb
 d09c62af3af01a43a05a82062b012e243c08a0ea 5669 popularity-contest_1.66_amd64.buildinfo
Checksums-Sha256:
 838835b3a2e3f42eedb07d999e0d62e7c53eaf68bcc817a811b92650105cf408 1724 popularity-contest_1.66.dsc
 1dccffb296a09111b5d568789a486f63490b5156db6956cfbef8818a380269c5 78420 popularity-contest_1.66.tar.xz
 8e243ad93d13faefe7703a20ad11f01db0e0a10180c498bcf1e7edeeb4363541 68852 popularity-contest_1.66_all.deb
 791a9caa6ee6df6de81ee38e5a7d74d4fddb331a17f2bbd87e22c85be4aba884 5669 popularity-contest_1.66_amd64.buildinfo
Files:
 00f627518dfd855e117be14b8030e345 1724 misc optional popularity-contest_1.66.dsc
 8f67fa8be6d9db275916087b996d09e6 78420 misc optional popularity-contest_1.66.tar.xz
 29b565ab198f70c88d14782f17f1300b 68852 misc optional popularity-contest_1.66_all.deb
 2660c63ee9a03300b835b58b8904a285 5669 misc optional popularity-contest_1.66_amd64.buildinfo

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

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAlqMnboACgkQjw58K0Ui
44dtohAAnAsDHSI3pRzoKRvUU4VCvuAoAOK6TNTN34/Ioru7hUOv8yAt/rVzy6oQ
4E8L+bioA2D962PnabY8nF26VsG8v2E4kDvUYcmUUl/9XNZGrOJbFa0s9Wjyk+NK
0zQLwqVn6knl3+dIa5Y+3WocpJDzjdE3cfc3ufYMwIEsfATyxBYUKWacB1D/0Dtt
ihUR0uRHlfiqIwG+F1g3PGVdjPvV3Mlpi3ONbEtIvPecXd+9U0yeG4VabVQoNOEA
hzYDEICNI6nWmTFFp/kpPpE/kkiz/noj7eEy3p5cV7Si833wDFdkHkbz9II4U0nY
FdvuDrJbXX2c59p1yOPbzvNoOsaBbzMVPPcqb8Uee9dDRZ3b/30GwHgrbH8gGCHD
ageWMsgGscCmdNaCXeFKr0aoZBoNDoIc09Yl0Hup7vRxtiepOycJRVW5D/UxjnZu
2r/dOWiWltl3TlI8sHqF2Z7WGiTfeqpxWVuONfhUxJ6lFYXjBe2/HYLg+LNIjIaV
MCinEs1qYMPTVmHxRah+h8H8go7q0KJO1yQxfruSzbw8gB/IfBvMzUzcAIaIONk6
NSWhjUN17CSqHK9OakU7uxm7gKOE0viaSPxmop21ZJ07JRma36uClIB+tNWOpuNB
TMCZ//T7FvweSeIN83ynZIeZRUS14Yk5VzEBM1xVnp9VXU8xEoc=
=FaNz
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.