Debian Bug report logs - #974107
Segfault when running isenkram-lookup

Toggle useless messages

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

From: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

To: submit@bugs.debian.org

Subject: Segfault when running isenkram-lookup

Date: Mon, 9 Nov 2020 23:49:00 +0100

Package: isenkram-cli
Version: 0.44
Severity: serious

On an updated Debian testing:

$ isenkram-lookup
/usr/lib/python3/dist-packages/isenkram/lookup.py:85: Warning invalid 
uninstantiatable type '(null)' in cast to 'AsProvided'
  provided = cpt.get_provided_for_kind(AppStream.ProvidedKind.MODALIAS)
Segmentation fault

I'm not really an isenkram user, but stumbled upon this issue in 
connection with Ubuntu's testing of package uploads. The isenkram-lookup 
command is included in the debian/tests/test-command-line script, which 
causes various tests to fail.

I filed the Ubuntu bug <https://launchpad.net/bugs/1903574> too, which 
includes some details about the crash. OTOH it seems to very easy to 
reproduce it...

Thanks!

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Matthias Klumpp <mak@debian.org>, Gunnar Hjalmarsson <gunnarhj@ubuntu.com>, 974107@bugs.debian.org, submit@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Tue, 10 Nov 2020 01:07:55 +0100

[Gunnar Hjalmarsson]
> On an updated Debian testing:
>
> $ isenkram-lookup
> /usr/lib/python3/dist-packages/isenkram/lookup.py:85: Warning invalid 
> uninstantiatable type '(null)' in cast to 'AsProvided'
>    provided = cpt.get_provided_for_kind(AppStream.ProvidedKind.MODALIAS)
> Segmentation fault
>
> I'm not really an isenkram user, but stumbled upon this issue in 
> connection with Ubuntu's testing of package uploads. The isenkram-lookup 
> command is included in the debian/tests/test-command-line script, which 
> causes various tests to fail.

Thank you for the heads up.  I'm involving the appstream maintainer,
perhaps he got an idea how to fix this.  Look like that part has changed
since the code was written.

-- 
Happy hacking
Petter Reinholdtsen

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

From: Matthias Klumpp <mak@debian.org>

To: Petter Reinholdtsen <pere@hungry.com>

Cc: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>, 974107@bugs.debian.org, Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Tue, 10 Nov 2020 01:21:50 +0100

Am Di., 10. Nov. 2020 um 01:08 Uhr schrieb Petter Reinholdtsen
<pere@hungry.com>:
>
> [Gunnar Hjalmarsson]
> > On an updated Debian testing:
> >
> > $ isenkram-lookup
> > /usr/lib/python3/dist-packages/isenkram/lookup.py:85: Warning invalid
> > uninstantiatable type '(null)' in cast to 'AsProvided'
> >    provided = cpt.get_provided_for_kind(AppStream.ProvidedKind.MODALIAS)
> > Segmentation fault
> >
> > I'm not really an isenkram user, but stumbled upon this issue in
> > connection with Ubuntu's testing of package uploads. The isenkram-lookup
> > command is included in the debian/tests/test-command-line script, which
> > causes various tests to fail.
>
> Thank you for the heads up.  I'm involving the appstream maintainer,
> perhaps he got an idea how to fix this.  Look like that part has changed
> since the code was written.

Can you give me some context for this code? If this is a warning
coming from libappstream, it means that it somehow got fed a null
pointer instead of a valid AsProvided object into its list, which
shouldn't happen - is your code doing that? Are you feeding it some
special metadata? What is the component name where this is failing?

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Matthias Klumpp <mak@debian.org>

Cc: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Tue, 10 Nov 2020 11:56:47 +0100

[Matthias Klumpp]
> Can you give me some context for this code? If this is a warning
> coming from libappstream, it means that it somehow got fed a null
> pointer instead of a valid AsProvided object into its list, which
> shouldn't happen - is your code doing that? Are you feeding it some
> special metadata? What is the component name where this is failing?

Not quite sure what you are looking for.  Just running isenkram-lookup
from isenkram-cli seem to trigger the error.  The code in question is in
/usr/lib/python3/dist-packages/isenkram/lookup.py, method
pkgs_handling_appstream_modaliases().

-- 
Happy hacking
Petter Reinholdtsen

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

From: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

To: Petter Reinholdtsen <pere@hungry.com>, Matthias Klumpp <mak@debian.org>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Tue, 10 Nov 2020 14:32:39 +0100

Additional observations:

* The testing failure in Ubuntu started around October 31.

* The test-command-line script fails on amd64 and i386 but succeeds on
  other architectures.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

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

From: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

To: Petter Reinholdtsen <pere@hungry.com>, Matthias Klumpp <mak@debian.org>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 07:03:35 +0100

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

Attached please find the stdout from Ubuntu's autopkgtest when running 
the test-command-line script in amd64.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

[test-command-line-stdout.gz (application/gzip, attachment)]

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>, Matthias Klumpp <mak@debian.org>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 21:28:26 +0100

[Gunnar Hjalmarsson]
> Additional observations:
>
> * The testing failure in Ubuntu started around October 31.
>
> * The test-command-line script fails on amd64 and i386 but succeeds on
>    other architectures.

Is it possible to 'diff' the logs from a successful and a failing test,
to see what changed?  Perhaps a new version of some package or
something?

I get the following when running in my Sid chroot:

  isenkram-lookup 

  (process:10498): GLib-GObject-CRITICAL (recursed) **:
  g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failedAborted

No idea what it mean. :)

-- 
Happy hacking
Petter Reinholdtsen

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

From: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

To: Petter Reinholdtsen <pere@hungry.com>, Matthias Klumpp <mak@debian.org>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 22:21:30 +0100

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

On 2020-11-12 21:28, Petter Reinholdtsen wrote:
> [Gunnar Hjalmarsson]
>> Additional observations:
>>
>> * The testing failure in Ubuntu started around October 31.
>>
>> * The test-command-line script fails on amd64 and i386 but succeeds on
>>     other architectures.
> 
> Is it possible to 'diff' the logs from a successful and a failing test,
> to see what changed?  Perhaps a new version of some package or
> something?
> 
> I get the following when running in my Sid chroot:
> 
>    isenkram-lookup
> 
>    (process:10498): GLib-GObject-CRITICAL (recursed) **:
>    g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failedAborted
> 
> No idea what it mean. :)

Unfortunately I don't have the knowledge to help with the analysis. But 
yes, since isenkram hasn't changed recently, the explanation ought to be 
changes in some other package(s).

Anyway, I attached two logs from test runs in Ubuntu's autopkgtest which 
passed. One is on amd64 from October 29 and one is on arm64 from 
yesterday. They both show a bunch of warning messages, but lack the 
"KeyError" from a recent amd64 test run (attached in my last message).

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

[test-command-line-stdout_success_amd64_20201029.gz (application/gzip, attachment)]

[test-command-line-stdout_success_arm64_20201111.gz (application/gzip, attachment)]

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

From: Matthias Klumpp <mak@debian.org>

To: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

Cc: Petter Reinholdtsen <pere@hungry.com>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 23:20:03 +0100

Am Do., 12. Nov. 2020 um 22:21 Uhr schrieb Gunnar Hjalmarsson
<gunnarhj@ubuntu.com>:
>
> On 2020-11-12 21:28, Petter Reinholdtsen wrote:
> > [Gunnar Hjalmarsson]
> >> Additional observations:
> >>
> >> * The testing failure in Ubuntu started around October 31.
> >>
> >> * The test-command-line script fails on amd64 and i386 but succeeds on
> >>     other architectures.
> >
> > Is it possible to 'diff' the logs from a successful and a failing test,
> > to see what changed?  Perhaps a new version of some package or
> > something?
> >
> > I get the following when running in my Sid chroot:
> >
> >    isenkram-lookup
> >
> >    (process:10498): GLib-GObject-CRITICAL (recursed) **:
> >    g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failedAborted
> >
> > No idea what it mean. :)
>
> Unfortunately I don't have the knowledge to help with the analysis. But
> yes, since isenkram hasn't changed recently, the explanation ought to be
> changes in some other package(s).
>
> Anyway, I attached two logs from test runs in Ubuntu's autopkgtest which
> passed. One is on amd64 from October 29 and one is on arm64 from
> yesterday. They both show a bunch of warning messages, but lack the
> "KeyError" from a recent amd64 test run (attached in my last message).

You want this patch for AppStream:
https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
Basically, Python thought it could free more objects than it should
actually have freed - not sure why this has worked before, this
behavior was apparently broken for quite a while. Maybe it just worked
by accident, or another bug was fixed in Python which triggered this
issue.

In any case, it'll be fixed in Debian soon-ish with the new AppStream
release, but Ubuntu will need a backported fix.

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

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

From: Matthias Klumpp <mak@debian.org>

To: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

Cc: Petter Reinholdtsen <pere@hungry.com>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 23:22:05 +0100

Am Do., 12. Nov. 2020 um 23:20 Uhr schrieb Matthias Klumpp <mak@debian.org>:
> [...]
> You want this patch for AppStream:
> https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
> Basically, Python thought it could free more objects than it should
> actually have freed - not sure why this has worked before, this
> behavior was apparently broken for quite a while. Maybe it just worked
> by accident, or another bug was fixed in Python which triggered this
> issue.
>
> In any case, it'll be fixed in Debian soon-ish with the new AppStream
> release, but Ubuntu will need a backported fix.
> [...]

Oh, btw: Thank you all for the last messages, knowing which commands
to run to reproduce this easily helped quite a bit with finding the
culprit quite quickly (and I also looked in the code for other
instances of this, but found only the ones in AsPool).

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

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

From: Petter Reinholdtsen <pere@hungry.com>

To: Matthias Klumpp <mak@debian.org>, Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

Cc: 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 12 Nov 2020 23:54:53 +0100

[Matthias Klumpp]
> Oh, btw: Thank you all for the last messages, knowing which commands
> to run to reproduce this easily helped quite a bit with finding the
> culprit quite quickly (and I also looked in the code for other
> instances of this, but found only the ones in AsPool).

Well, thank you for looking into this.  Should this BTS report be
reassigned somewhere, given that the code issue is not in isenkram?

-- 
Happy hacking
Petter Reinholdtsen

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

From: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

To: Matthias Klumpp <mak@debian.org>, Petter Reinholdtsen <pere@hungry.com>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Fri, 13 Nov 2020 01:28:13 +0100

On 2020-11-12 23:20, Matthias Klumpp wrote:
> You want this patch for AppStream:
> https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248

But only comments are changed there!?

Still... I built AppStream with that commit applied:

https://launchpad.net/~gunnarhj/+archive/ubuntu/appstream

and that miraculously fixes it. Thanks!

(I'm getting old.)

> In any case, it'll be fixed in Debian soon-ish with the new AppStream
> release, but Ubuntu will need a backported fix.

Right, we'll need to backport to Ubuntu 20.10. For some reason isenkram 
is not present in the archive for Ubuntu 20.04. Is there any other 
reason for such an appstream backport to 20.04?

On 2020-11-12 23:54, Petter Reinholdtsen wrote:
> Should this BTS report be reassigned somewhere, given that the
> code issue is not in isenkram?

Yeah, looks like it should be reassigned to the appstream package.

-- 
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj

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

From: Matthias Klumpp <mak@debian.org>

To: Gunnar Hjalmarsson <gunnarhj@ubuntu.com>

Cc: Petter Reinholdtsen <pere@hungry.com>, 974107@bugs.debian.org

Subject: Re: Bug#974107: Segfault when running isenkram-lookup

Date: Thu, 19 Nov 2020 12:37:46 +0100

Am Fr., 13. Nov. 2020 um 01:28 Uhr schrieb Gunnar Hjalmarsson
<gunnarhj@ubuntu.com>:
>
> On 2020-11-12 23:20, Matthias Klumpp wrote:
> > You want this patch for AppStream:
> > https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
>
> But only comments are changed there!?
>
> Still... I built AppStream with that commit applied:
>
> https://launchpad.net/~gunnarhj/+archive/ubuntu/appstream
>
> and that miraculously fixes it. Thanks!
>
> (I'm getting old.)
>
> > In any case, it'll be fixed in Debian soon-ish with the new AppStream
> > release, but Ubuntu will need a backported fix.
>
> Right, we'll need to backport to Ubuntu 20.10. For some reason isenkram
> is not present in the archive for Ubuntu 20.04. Is there any other
> reason for such an appstream backport to 20.04?
>
> On 2020-11-12 23:54, Petter Reinholdtsen wrote:
> > Should this BTS report be reassigned somewhere, given that the
> > code issue is not in isenkram?
>
> Yeah, looks like it should be reassigned to the appstream package.

Looks like I was speaking too soon and this isn't actually an issue in
AppStream - my fix resolves the issue with Python, but breaks the Vala
bindings instead: https://github.com/ximion/appstream/issues/289
So, this has to be fixed in some other tool...
Also, please don't backport that patch.

Cheers,
    Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

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

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 974107-close@bugs.debian.org

Subject: Bug#974107: fixed in appstream 0.13.1-1

Date: Fri, 04 Dec 2020 14:10:15 +0000

Source: appstream
Source-Version: 0.13.1-1
Done: Matthias Klumpp <mak@debian.org>

We believe that the bug you reported is fixed in the latest version of
appstream, 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 974107@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp <mak@debian.org> (supplier of updated appstream 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: SHA256

Format: 1.8
Date: Tue, 01 Dec 2020 10:10:16 +0100
Source: appstream
Binary: appstream appstream-dbgsym appstream-doc apt-config-icons apt-config-icons-hidpi apt-config-icons-large apt-config-icons-large-hidpi gir1.2-appstream-1.0 gir1.2-appstreamcompose-1.0 libappstream-compose-dev libappstream-compose0 libappstream-compose0-dbgsym libappstream-dev libappstream4 libappstream4-dbgsym libappstreamqt-dev libappstreamqt2 libappstreamqt2-dbgsym
Architecture: source amd64 all
Version: 0.13.1-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp <mak@debian.org>
Changed-By: Matthias Klumpp <mak@debian.org>
Description:
 appstream  - Software component metadata management
 appstream-doc - Developer documentation for AppStream
 apt-config-icons - APT configuration snippet to enable icon downloads
 apt-config-icons-hidpi - APT configuration snippet to enable HiDPI icon downloads
 apt-config-icons-large - APT configuration snippet to enable large icon downloads
 apt-config-icons-large-hidpi - APT configuration snippet to enable large HiDPI icon downloads
 gir1.2-appstream-1.0 - Library to access AppStream services (introspection data)
 gir1.2-appstreamcompose-1.0 - Building blocks to compose AppStream metadata (introspection data
 libappstream-compose-dev - Building blocks to compose AppStream metadata (development files)
 libappstream-compose0 - Building blocks to compose AppStream metadata
 libappstream-dev - Library to access AppStream services (development files)
 libappstream4 - Library to access AppStream services
 libappstreamqt-dev - Qt5 library to access AppStream services (development files)
 libappstreamqt2 - Qt5 library to access AppStream services
Closes: 974107
Changes:
 appstream (0.13.1-1) unstable; urgency=medium
 .
   * New upstream version: 0.13.1
     - Includes workaround for a gobject-introspection ambiguity that
       prevents declaring certain ownership relations. The workaround,
       at least for now, makes both Python and Vala work again when
       using GIR data (Closes: #974107)
   * Drop extra highlight.js copy
   * Add packages for the experimental appstream-compose library
   * Update description texts slightly
   * Update symbols file
Checksums-Sha1:
 062df7a4271be54278b745f9093bd8d04826e2db 3281 appstream_0.13.1-1.dsc
 e15dec444aaa5294503b1b3fd86d5944d2507440 2221448 appstream_0.13.1.orig.tar.xz
 868d8ddfcc29c20a84c94754ee8c8150f5ed3fca 14984 appstream_0.13.1-1.debian.tar.xz
 c9cfd2278b0f1f64d98d0be6d1c53ae0c152184e 70680 appstream-dbgsym_0.13.1-1_amd64.deb
 f302f4842a8f650117137f6cd09ed21891f771c0 1486704 appstream-doc_0.13.1-1_all.deb
 1e7a9e8b586ab6f4376fb6ffe8fc464e0a817dac 19793 appstream_0.13.1-1_amd64.buildinfo
 b9951ef096a019c4331b78d706e2d72fa780f811 279164 appstream_0.13.1-1_amd64.deb
 82f869df82e4fbf923f928b02e706186e87b262e 10068 apt-config-icons-hidpi_0.13.1-1_all.deb
 6a88267bb9992e8b29ca6ba078454a021adfc093 10152 apt-config-icons-large-hidpi_0.13.1-1_all.deb
 49c7ead18090eafe49a45489356b04faf24db2d4 10152 apt-config-icons-large_0.13.1-1_all.deb
 fe61152c225afc1fb5154ea1c1d0d7009e8b20f9 10152 apt-config-icons_0.13.1-1_all.deb
 d98e00b6192e524c2ba7c6e714bb33d6366138e2 25848 gir1.2-appstream-1.0_0.13.1-1_amd64.deb
 9be84dc02cb645b957378ce0456ecca1e7d6dd32 12744 gir1.2-appstreamcompose-1.0_0.13.1-1_amd64.deb
 4496a38dada6ad63b6ce8d23d81f4f60522ad945 19596 libappstream-compose-dev_0.13.1-1_amd64.deb
 60f6fe76ac0a3ec196b6af298dc06e786860ce7b 67800 libappstream-compose0-dbgsym_0.13.1-1_amd64.deb
 6efa7dea51c3b75d4b4c7285a0dad6f7efeb9297 34520 libappstream-compose0_0.13.1-1_amd64.deb
 ab256a889b5bd5f20416e3f45bd731e265949167 78304 libappstream-dev_0.13.1-1_amd64.deb
 ed23b49c1ff5cd8f780c3fae8a5467f10249b213 476672 libappstream4-dbgsym_0.13.1-1_amd64.deb
 24612989d0034ade6e6f76b2db31f1f87810b2e3 151420 libappstream4_0.13.1-1_amd64.deb
 4721daf6acc022867a656ebeba475a14bcd91322 18160 libappstreamqt-dev_0.13.1-1_amd64.deb
 5e618705fbc2d804e08fe396039246b1fe77938d 901836 libappstreamqt2-dbgsym_0.13.1-1_amd64.deb
 9b78b6d70194b98dc79c5386df16e5bc27ee7e01 67228 libappstreamqt2_0.13.1-1_amd64.deb
Checksums-Sha256:
 7f27d99f00ace768f0db598376b7a12138d4695ae090d907be943cec1b30e2f4 3281 appstream_0.13.1-1.dsc
 ba7de61223aaa76d8c47d8857bf185c28d4c2a099f3ab02c8837091e7e8f8626 2221448 appstream_0.13.1.orig.tar.xz
 db278a3e0ffe376b9ca2f63aed61a54147bb42f90d9824285fbb31a64350ca8c 14984 appstream_0.13.1-1.debian.tar.xz
 fc237fb5172eae0eff891cb0fd4edd001a1e4f6c5810129682b58269dad11084 70680 appstream-dbgsym_0.13.1-1_amd64.deb
 89a2c0ac39f60e02335ac48581dfd5f8db7ab1c69b794abe871d5e3047695b7b 1486704 appstream-doc_0.13.1-1_all.deb
 896870db956670c1711411c94af0368afc5d690e9404359e74bdf7b3b451acf4 19793 appstream_0.13.1-1_amd64.buildinfo
 050db9d2276f0fda85e113e1f2e24d67ea38744725b6a98a8f3ebf55cb83469c 279164 appstream_0.13.1-1_amd64.deb
 3e825f3f5c3be2a8eb9d8f4b538acf64c43de203ac9121f233a380784fc74839 10068 apt-config-icons-hidpi_0.13.1-1_all.deb
 7a092fd9cfdfb48af19e333f13702edf518d945fb5e1f1340d15c13b97230028 10152 apt-config-icons-large-hidpi_0.13.1-1_all.deb
 bfb2591efcfe033b6c60fb44eb133c84e1cda0f208bb9a835fe34fc0f1d718c1 10152 apt-config-icons-large_0.13.1-1_all.deb
 b640bf066f7d861d0e40f30de888827fcef59c950aec605fd917eccf53f95cab 10152 apt-config-icons_0.13.1-1_all.deb
 7f8ae68c5fb9ffae7f0ad2cab748055048d403cdd879b98fe70ae425ad7773fc 25848 gir1.2-appstream-1.0_0.13.1-1_amd64.deb
 edf248f328ce867db90378072df79f5ef1bf30e9db5264a039580a0f01e82b23 12744 gir1.2-appstreamcompose-1.0_0.13.1-1_amd64.deb
 44443c049bf67021481728394c978dbab2e8b0b0830067a0bc402f01eacf0af4 19596 libappstream-compose-dev_0.13.1-1_amd64.deb
 dd7fe50d5d05aa6a4ee78907ef5028461c58feac409721c2dae44407591f3858 67800 libappstream-compose0-dbgsym_0.13.1-1_amd64.deb
 5b7adeb7bc7439eb1993c41fb0c270f13cec0bd6cb60fb5ed564b5d4e290b196 34520 libappstream-compose0_0.13.1-1_amd64.deb
 c5e1cebd7a38edfc232cdd86ee53bf1aa55ddbcdaada6a9988d2ae1c5762666f 78304 libappstream-dev_0.13.1-1_amd64.deb
 a4219e031ed5aa515ec048249fa30ec7f3c8bfb735dd68748efc41c48f538741 476672 libappstream4-dbgsym_0.13.1-1_amd64.deb
 89734080c7ab3cadf78897b79e96ba5bed55c1e55dcc3067af480b93d431cd4f 151420 libappstream4_0.13.1-1_amd64.deb
 d13ec6e330a00355961cfd8399c2014897520c40111041a1a6b058f264291c4c 18160 libappstreamqt-dev_0.13.1-1_amd64.deb
 f088969b69ce137eea4a71d4ecd072f280a8b406fa40f8ef2952563b3556bd1a 901836 libappstreamqt2-dbgsym_0.13.1-1_amd64.deb
 57d0fe81224d385821f2afae0c6f0ec989b62195fc5ddfbe0ccf0e2d6b7ddf57 67228 libappstreamqt2_0.13.1-1_amd64.deb
Files:
 0393f2dad0fec77bf1d1dd03169ebf2a 3281 admin optional appstream_0.13.1-1.dsc
 6b865cd6f8865ef186e9bf3b3b60affb 2221448 admin optional appstream_0.13.1.orig.tar.xz
 dc15b7b23df41693af658329bcc2149e 14984 admin optional appstream_0.13.1-1.debian.tar.xz
 bdc09efb251e4065ef2912d9a3d72eb6 70680 debug optional appstream-dbgsym_0.13.1-1_amd64.deb
 3fd7b18504cbd86452d48574ed13856b 1486704 doc optional appstream-doc_0.13.1-1_all.deb
 b507eb3445160c9a7a98f2df42817346 19793 admin optional appstream_0.13.1-1_amd64.buildinfo
 403cef80bbe0c1a8f165a9657757eb93 279164 admin optional appstream_0.13.1-1_amd64.deb
 8754f3715b74c5fa9de389dee088630f 10068 misc optional apt-config-icons-hidpi_0.13.1-1_all.deb
 e5a5662f35720813306f15fe6487ab7f 10152 misc optional apt-config-icons-large-hidpi_0.13.1-1_all.deb
 183d49d8fad2d3e9921d1215ff206ae7 10152 misc optional apt-config-icons-large_0.13.1-1_all.deb
 5ca26f41031b5118a6cb08e4792d98b3 10152 misc optional apt-config-icons_0.13.1-1_all.deb
 5955c1bcd4175ec0732f88157e2e17b7 25848 introspection optional gir1.2-appstream-1.0_0.13.1-1_amd64.deb
 5a55417370286dbb698fff496e20daa2 12744 introspection optional gir1.2-appstreamcompose-1.0_0.13.1-1_amd64.deb
 a42f6ee14e20c50dc3cc3e18e4335bfa 19596 libdevel optional libappstream-compose-dev_0.13.1-1_amd64.deb
 8916b9c3f8d7dc245047034a3e40e650 67800 debug optional libappstream-compose0-dbgsym_0.13.1-1_amd64.deb
 7add60aca76c280dc1dd42fa2ba9c3b0 34520 libs optional libappstream-compose0_0.13.1-1_amd64.deb
 c7d7c75861acd7aed4bdd40fc24ef379 78304 libdevel optional libappstream-dev_0.13.1-1_amd64.deb
 1c4bbfe63fbc7a1fb0e71cda47a20e11 476672 debug optional libappstream4-dbgsym_0.13.1-1_amd64.deb
 d5f6ea445766ce4c3e1a0729b548b491 151420 libs optional libappstream4_0.13.1-1_amd64.deb
 f1278f25e80156c199b72b25703900a4 18160 libdevel optional libappstreamqt-dev_0.13.1-1_amd64.deb
 48d78a875bedd200da3eb871b6dbb6e3 901836 debug optional libappstreamqt2-dbgsym_0.13.1-1_amd64.deb
 bd703230b4d93eee3a51c47ba222f097 67228 libs optional libappstreamqt2_0.13.1-1_amd64.deb

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

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl/FjDEPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrD8sP/iakZBRrAAjlwTtz7S4r8izgVuHeQe5WIB/F
MVFSDoFAsEEHdpysi+JcEg2fDFycNn8fKTMdumhZa8LiW0tu2t0SXqHccL07WZSD
/q7iVNUIFXAgSHiomE+eSCBXJCMZhWI62Idi1iUjriFbOZm5rGtbpcMqYWQEnInm
NE6n9qsNBHYd9wle42Up9fUncGau/9Vv26/CTAvR0C0MNWgnAFWB+GnzsQ+pNSCU
PjfU5JzBkgUTkhpLvXYmSoMW0Nlzqp465nqRrbtZEdZV7C8aXfTVQNVrb+jMNb+Z
PyeS2F1JFYen0cc3X4Sly00KIRW1lnTO44Y6/MGr33wTY6f3R1TcaI5gAgQ5+mij
ZpN7aVJwlpTFGC115UUmiAiFrjyFQ6bSUydWhhYtRB0NiPzBkmk6Yd+VsReEdwak
H2nHSwZC2gF917pu3io5hWpDFxirZ/o5D9HVNN3zEs95KRBqf8c9i7kcw29hpo3C
fPfUxijYNRPGNlb9mY0+OKvzhEdfajPsjwzwRESjJwUMx3CpTuMST8aAe/B6E/J9
AuXnjzWV/JWSzsWBc1O7nC8AR4xidVjirYv0A14aHJbanjax9IhT63dpOxqt6qgS
kueYXGutqThqZ7p7SFqpLwBOrEtHX8e+pZIa8sclc6kvhMz8b0j++N6+ir+TOlom
ggQC6CKr
=/BC/
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.