Debian Bug report logs - #852343
wicd-daemon: needs to look for dhcpcd5 instead of dhcpcd after the release of Stretch

Display info messages

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

From: Jörg-Volker Peetz <jvpeetz@t-online.de>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: wicd-daemon packages dependencies

Date: Fri, 17 Aug 2012 13:31:44 +0200

Package: wicd-daemon
Version: 1.7.2.4-2
Severity: normal

Dear Maintainers,

the dependency on an dhcp client in the packages should be formulated with the
help of the virtual packet "dhcp-client" as something like

  dhcpcd | pump | udhcpc | dhcp-client

(Compare bug #680976.)

Furthermore, I would like to suggest to change the dependency on
"wireless-tools" to a recommendation, since with newer kernels this package
isn't mandatory any more.

-- 
Best regards,
Jörg-Volker.

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

From: Axel Beckert <abe@debian.org>

To: Jörg-Volker Peetz <jvpeetz@t-online.de>, 685146@bugs.debian.org

Subject: Re: Bug#685146: wicd-daemon packages dependencies

Date: Sun, 22 Jan 2017 04:36:14 +0100

Hi,

Jörg-Volker Peetz wrote:
> the dependency on an dhcp client in the packages should be formulated with the
> help of the virtual packet "dhcp-client" as something like
> 
>   dhcpcd | pump | udhcpc | dhcp-client
> 
> (Compare bug #680976.)

I disagree here. Wicd has a list of supported DHCP clients and handles
each one differently depending on its features. AFAIK wicd is not
capable of talking to arbitrary DHCP clients. Hence the way #680976
has been fixed was correct.

> Furthermore, I would like to suggest to change the dependency on
> "wireless-tools" to a recommendation,

Indeed, wicd theoretically could be used to handle wired
configurations only. I'm though not sure if wicd works properly
without iwconfig, iwlist and friends installed, so I'm reluctant here.
Additionally, I consider such cases being very rare.

Less rare, but a similar case is the question if wpa-supplicant needs
to be a hard dependency. E.g. there might be users just connecting to
open or WEP-"secured" wifi networks. (But at least the latter case
should be very rare nowadays, too.)

I'd avoid these kind of changes before the Stretch release as they
need quite some testing. But I might reconsider them after the Stretch
release.

> since with newer kernels this package isn't mandatory any more.

I don't see why this would be relevant here. The sole reason for
downgrading these dependencies is because there might be use cases
where wireless at all is not needed. (AFAIK wicd can't yet use "iw"
instead of iwconfig and friends.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

From: Jörg-Volker Peetz <jvpeetz@web.de>

To: Axel Beckert <abe@debian.org>, 685146@bugs.debian.org

Subject: Re: Bug#685146: wicd-daemon packages dependencies

Date: Mon, 23 Jan 2017 16:36:24 +0100

Hi,

Axel Beckert wrote on 01/22/17 04:36:
> Hi,
> 
> Jörg-Volker Peetz wrote:
>> the dependency on an dhcp client in the packages should be formulated with the
>> help of the virtual packet "dhcp-client" as something like
>>
>>   dhcpcd | pump | udhcpc | dhcp-client
>>
>> (Compare bug #680976.)

This means wicd does not cooperate with dhcpcd5?

> 
> I disagree here. Wicd has a list of supported DHCP clients and handles
> each one differently depending on its features. AFAIK wicd is not
> capable of talking to arbitrary DHCP clients. Hence the way #680976
> has been fixed was correct.
> 
>> Furthermore, I would like to suggest to change the dependency on
>> "wireless-tools" to a recommendation,
> 
> Indeed, wicd theoretically could be used to handle wired
> configurations only. I'm though not sure if wicd works properly
> without iwconfig, iwlist and friends installed, so I'm reluctant here.
> Additionally, I consider such cases being very rare.

The intention was not to dispense with wired networking, but that the package iw
"will become the canonical command line tool for wireless configuration" as it
says in its description.

> 
> Less rare, but a similar case is the question if wpa-supplicant needs
> to be a hard dependency. E.g. there might be users just connecting to
> open or WEP-"secured" wifi networks. (But at least the latter case
> should be very rare nowadays, too.)
> 
> I'd avoid these kind of changes before the Stretch release as they
> need quite some testing. But I might reconsider them after the Stretch
> release.
> 
>> since with newer kernels this package isn't mandatory any more.
> 
> I don't see why this would be relevant here. The sole reason for
> downgrading these dependencies is because there might be use cases
> where wireless at all is not needed. (AFAIK wicd can't yet use "iw"
> instead of iwconfig and friends.)
> 
I didn't know that.

> 		Regards, Axel
> 
By the way, I recommended this because I intended to use wicd. I'm not a heavy
user of wireless networking. Maybe, the priority of this bug should then be set
to wishlist?

Regards,
Jörg-Volker.

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

From: Axel Beckert <abe@debian.org>

To: Jörg-Volker Peetz <jvpeetz@web.de>

Cc: 685146@bugs.debian.org

Subject: Re: Bug#685146: wicd-daemon packages dependencies

Date: Mon, 23 Jan 2017 17:49:58 +0100

Control: severity -1 wishlist
Control: clone -1 -2
Control: retitle -1 wicd-daemon: should only recommend wireless-tools and wpa-supplicant
Control: retitle -2 wicd-daemon: Should switch from iwconfig/ifconfig to iw/ip
Control: tag -2 + upstream
Control: forwarded -2 https://blueprints.launchpad.net/wicd/+spec/support-ip-iw

Hi,

Jörg-Volker Peetz wrote:
> Axel Beckert wrote on 01/22/17 04:36:
> > Jörg-Volker Peetz wrote:
> >> the dependency on an dhcp client in the packages should be formulated with the
> >> help of the virtual packet "dhcp-client" as something like
> >>
> >>   dhcpcd | pump | udhcpc | dhcp-client
> >>
> >> (Compare bug #680976.)
> 
> This means wicd does not cooperate with dhcpcd5?

My immediate repsonse would have been: It does work with dhcpcd5
because after https://bugs.debian.org/783272 we updated that
dependency to dhcpcd5.

But your question made me think and after some checking I noticed that
I probably assumed too much for that change: dhcpcd5 does only provide
/sbin/dhcpcd5 while wicd searches for "dhcpcd" without "5". So it
likely never find "dhcpcd5".

So the next thing is to check if changing the paths inside wicd from
dhcpcd to dhcpcd5 suffices to fix that or if that renaming was because
of interface incompatibilities -- which could mean that wicd can't use
dhcpcd[5] at all anymore in Debian.

Will have closer look at that. Thanks for making me aware of that
(even if unintended :-).

> >> Furthermore, I would like to suggest to change the dependency on
> >> "wireless-tools" to a recommendation,
> > 
> > Indeed, wicd theoretically could be used to handle wired
> > configurations only. I'm though not sure if wicd works properly
> > without iwconfig, iwlist and friends installed, so I'm reluctant here.
> > Additionally, I consider such cases being very rare.
> 
> The intention was not to dispense with wired networking, but that the package iw
> "will become the canonical command line tool for wireless configuration" as it
> says in its description.
[...]
> >> since with newer kernels this package isn't mandatory any more.
> > 
> > I don't see why this would be relevant here. The sole reason for
> > downgrading these dependencies is because there might be use cases
> > where wireless at all is not needed. (AFAIK wicd can't yet use "iw"
> > instead of iwconfig and friends.)
>
> I didn't know that.

Ah, ok. 

See https://blueprints.launchpad.net/wicd/+spec/support-ip-iw for the
upstream thoughts on that. (Not much there yet, though.)

> By the way, I recommended this because I intended to use wicd. I'm not a heavy
> user of wireless networking. Maybe, the priority of this bug should then be set
> to wishlist?

Indeed. And split up into two separate issues.

Thanks!

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

From: Axel Beckert <abe@debian.org>

To: Jörg-Volker Peetz <jvpeetz@web.de>, 685146@bugs.debian.org

Subject: Re: [pkg-wicd-maint] Bug#685146: wicd-daemon packages dependencies

Date: Mon, 23 Jan 2017 18:59:57 +0100

Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 wicd-daemon: needs to look for dhcpcd5 instead of dhcpcd after the release of Stretch
Control: tag -2 sid buster

Hi again,

TL;DR: wicd works fine with dhcpcd5.

Axel Beckert wrote:
> Jörg-Volker Peetz wrote:
> > This means wicd does not cooperate with dhcpcd5?
> 
> My immediate repsonse would have been: It does work with dhcpcd5
> because after https://bugs.debian.org/783272 we updated that
> dependency to dhcpcd5.
> 
> But your question made me think and after some checking I noticed that
> I probably assumed too much for that change: dhcpcd5 does only provide
> /sbin/dhcpcd5 while wicd searches for "dhcpcd" without "5". So it
> likely never find "dhcpcd5".

I luckily was wrong here: While the package only contains
/sbin/dhcpcd5 (which is what I checked) its postinst script creates a
symlink at /sbin/dhcpcd via update-alternatives and hence wicd finds
the right dhcpcd binary. It also works fine with dhcpcd5. I'm
currently writing this mail over a wireless connection established
with wicd and with dhcpcd5 as used DHCP client.

Bit since -- to my knowledge -- there is no other package offering an
alternative for dhcpcd anymore, and Iexpect that the alternatives
system will get removed from the dhcpcd5 package in the future, wicd
should be patched to look for dhcpcd5 instead, at least in Debian.
Cloning this bug report accordingly.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

From: Axel Beckert <abe@debian.org>

To: Niels Thykier <niels@thykier.net>

Cc: 928428@bugs.debian.org, Salvo Tomaselli <tiposchi@tiscali.it>, 852343@bugs.debian.org, 901592@bugs.debian.org

Subject: Re: Bug#928428: unblock: [pre-approval] wicd/1.7.4+tb2-7

Date: Sun, 12 May 2019 22:21:12 +0200

Hi Niels,

Niels Thykier wrote:
> Axel Beckert:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: unblock
> > 
> > In the light of dhcpcd5 automremoval (#928056, #928104, #928105), I'd
> > like to upload a wicd package which relies less on dhcpcd5.  [...]
[...]
> AFAICT, the dhcpcd5 issues have been fixed and wicd is at the moment not
> at risk of being removed from testing on that account.

Ack. Actually I didn't expected those CVEs to be fixed that quickly
given how RC bugs in that package were handled in the past. I guess
these memories are from the times where the Debian packages of dhcpcd*
was (not really) maintained by the upstream maintainer.

> If so, then I would prefer deferring these changes to bullseye in
> general to reduce the risks of regressions in testing at the moment.

I actually thought that way, too, and nearly would have closed the
request myself.

But then again it seems that if only the default DHCP client
dependency is installed, it won't find the according binary. (See
https://bugs.debian.org/852343 — probably has the wrong severity,
should be at least important from my point of view.)

Then again, in most cases, when wicd is being installed, that
alternative dependency where dhcpcd5 comes first (#901592) is usually
already fulfilled by isc-dhcp-client which is installed by default and
hence present on most installations.

So while the impact of #852343 (at least together with #901592) is
probably RC on the paper, there are actually only very few people who
actually will run into it (and nobody who complained by having run
into it so far), e.g. those who have no DHCP client installed at all
when wicd is being installed or which uninstall all other DHCP clients
afterwards.

The only real impact I can imagine is on derivatives which install
wicd by default and follow Debian release cycles — of which I can't
remember any at the moment — at least Raspbian uses pure dhcpcd5 +
dhcpcd-gtk (and not Debian's packages of dhcpcd* as I just noticed).

So I'm generally fine with postponing this until bullseye. If you
agree with my reasoning above, please close this unblock request.

Will drop the created git branch "buster" only after the release of
buster, though, just to be on the safe side.

Salvo Tomaselli wrote:
> Well I use isc-dhcp-client and it works fine

I'm sorry, but IMHO this fact is not really relevant for this
discussion.

> so I guess it is an ok change.

... and since it ignores the core issues of th proposed change, this
reasoning is IMHO bogus.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

From: Axel Beckert <abe@debian.org>

To: 852343-close@bugs.debian.org

Subject: Bug#852343: fixed in wicd 1.7.4+tb2+2019.09.18git2e0ba579-1

Date: Fri, 06 Dec 2019 13:01:07 +0000

Source: wicd
Source-Version: 1.7.4+tb2+2019.09.18git2e0ba579-1

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

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated wicd 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, 02 Dec 2019 04:47:07 +0100
Source: wicd
Binary: python3-wicd wicd wicd-cli wicd-curses wicd-daemon wicd-gtk
Architecture: source all
Version: 1.7.4+tb2+2019.09.18git2e0ba579-1
Distribution: experimental
Urgency: low
Maintainer: Debian WICD Packaging Team <pkg-wicd-maint@lists.alioth.debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
 python3-wicd - wired and wireless network manager - Python module
 wicd       - wired and wireless network manager - metapackage
 wicd-cli   - wired and wireless network manager - scriptable console client
 wicd-curses - wired and wireless network manager - Curses client
 wicd-daemon - wired and wireless network manager - daemon
 wicd-gtk   - wired and wireless network manager - GTK+ client
Closes: 833929 852343 901592 938823
Changes:
 wicd (1.7.4+tb2+2019.09.18git2e0ba579-1) experimental; urgency=low
 .
   Upload to experimental to get a broader testing base of the python3 port
   and the dhcpcd5 changes. Not yet fully functional again.
 .
   [ Axel Beckert ]
   * Don't list dhcpcd5 as preferred DHCP client in the alternative
     dependencies list. (Closes: #901592)
   * Replace versioned python build-dependency with an unversioned
     build-dependency on python2.
   * Look for "dhcpcd5" instead of "dhcpcd". (Closes: #852343)
   * Demote alternative list of DHCP clients from a hard dependency to a
     recommendation since in theory wicd can also be used just to switch
     between multiple static configurations. (Also closes: #901592)
   * Package git snapshot to test the port to Python 3. (Closes: #938823)
     + Refresh remaining patches as necessary.
     + Change (build-)dependencies to python3 variants.
     + Switch from python-gobject-2 to python3-gi.
     + Rename python-wicd to python3-wicd.
     + Use pybuild build system.
     + Add patches with all remaining needed changes, especially
       bytes vs string conversions and path issues.
     + Copy the generated wpath.py into the build directory before running
       dh_auto_test, i.e. the test suite.
     + Add some more files (mostly under "other") to debian/clean.
     + Add iw as dependency. iwconfig seems not yet fully replaced though.
     + Vcs-Git: Set branch to python3 until merged into master.
   * Bump debhelper compatibility level to 12.
     + Build-depend on "debhelper-compat (= 12)" to replace debian/compat.
   * Declare compliance with Debian Policy 4.4.1. (No changes needed.)
   * Add "Pre-Depends: ${misc:Pre-Depends}" to wicd-daemon as recommended
     by Lintian.
   * Disable test suite while Python 3 port is still incomplete.
 .
   [ Ondřej Nový ]
   * d/copyright: Change Format URL to correct one
 .
   [ Giap Tran ]
   * Apply patch by Vincent Lefevre to fix auto(re)connect while GUI is
     open. (Closes: #833929)
Checksums-Sha1:
 f185c951ff0e1448dc42a07ce24d8e9c7a17fb61 2446 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.dsc
 e1442c4aab6760e5a9a8bfdd286524adac65d22e 553934 wicd_1.7.4+tb2+2019.09.18git2e0ba579.orig.tar.gz
 aae10bc36fd0bdb9c65f1bb8f5b7db658f719cc5 33420 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.debian.tar.xz
 b0028ecf0255c09ec9a65a79d39de34eef0940c4 56856 python3-wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 f11b7aa540d15335f6a111b318613aee184e1a16 29148 wicd-cli_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 a904c6a29207f641b33ec0a89909ef728552d29a 53620 wicd-curses_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 b7a83e96a7167d04a70f25c5d89ffe24797cf5b2 168712 wicd-daemon_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 3f19ce45ce90aa652b0aa91db46db95cd7e16247 156432 wicd-gtk_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 26b2e79127e51ce0b10e3165a38e09aaf4c96388 25720 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 9876f6cd573f8147f0a6bc989d5cf3d1a864134d 7930 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_amd64.buildinfo
Checksums-Sha256:
 7f496324da8276dd7c5be0a64eb5de1f7e438610078e57023fd07610cbd7eed2 2446 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.dsc
 25adc321fe99d0916bdf0ac2ecb7409c238cc0298ea08a93ae1ccb7ef83b0c08 553934 wicd_1.7.4+tb2+2019.09.18git2e0ba579.orig.tar.gz
 1fe9503769f56c32c4151e7f560dc8e750399d8919b9b5d2e8cda55d0452753f 33420 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.debian.tar.xz
 87d695d0ca7be7e6bb0a16eb37df157b05cd99cd72b3e701e253e1e93df927c7 56856 python3-wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 29efc2bae08d4054a0667c6126a253b7e2d23232d26a523520525bbb557e49e8 29148 wicd-cli_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 344fd32246a95f0db863a63d2d424b7d54b80e78f8fe8e8de42911e71f920851 53620 wicd-curses_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 1f590d911519dc7bc169925120d7c9735b022b0ad4356742ffe2fdb0764ea589 168712 wicd-daemon_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 8af97ce05fa5007a6c19afd37918baef8e63cc13bef49bc03e03632d732d50a6 156432 wicd-gtk_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 5e1c834ac8cb203eb317baa7d6f2187dfcf9072db44f6166f966573fffda2518 25720 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 00766aaad8df3282dd8b0b21c9543fc5bfddb5fc20ec9eabe40be487984366f8 7930 wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_amd64.buildinfo
Files:
 0a4378a6b37314339003661f247ca002 2446 net optional wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.dsc
 7855d741d7b14e6fb44129236e9bba7f 553934 net optional wicd_1.7.4+tb2+2019.09.18git2e0ba579.orig.tar.gz
 382978110e6a8e4adc3cf5beab476c7a 33420 net optional wicd_1.7.4+tb2+2019.09.18git2e0ba579-1.debian.tar.xz
 a94ec13e4077a5190a11fc83007b0360 56856 python optional python3-wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 31fed310c645a398273841b6c88756e9 29148 net optional wicd-cli_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 9f9cfd118d01d9e954dfdd2c2f9dee74 53620 net optional wicd-curses_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 ca1dfc363a71d200f5d3f7363374ae28 168712 net optional wicd-daemon_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 b14c5d0ff4a3001001b4c9908e78b357 156432 net optional wicd-gtk_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 534e5652f3783947cf63ecd5423ddf01 25720 net optional wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_all.deb
 b277cb8d9f1d5ee8d651a98d955e0b35 7930 net optional wicd_1.7.4+tb2+2019.09.18git2e0ba579-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAl3kiaUACgkQa+Zjx1o1
yXU9AA/9ENiD+FST4UpbgiMS0hViu2BQ40ftf3uOB/0YUFo0/yLBf+mHryJBPhEL
+5HsiidFZf3CKR0GSr/vKtsE/mfNYmL1BKjRfOoyhtuezXzAtKuq3XLXuIW+ogSq
MLUEdL48Rr1l3gkvelrRQGKcM/vsubL5xlLt/9UdT/sc0JSsgzevyWaiYq+mY4Qi
g1U7X9NiNTYpbNXZjJ0NrdmbNcQtCl4i+P6I0DrzXSdCFGikB/Sgmzfm9QXEOQQ1
EG18xWjosE4PQztAo2RDGAahPnHs5MT2NFNwz8Fy8Ib0mY0DK+rV/EcHD3TZVJN0
V6XFRELV1Y+XPurw3uOHoPl/lcUGRtpafOEnU3V8RjsxchoOCH909Kj59J3FYTw4
dj1Dn96GJnNdCboNXyvdYkxIajaNGJ1KWCU74DWHD/wKrVPQlCKUxymWz4NrAkpy
fPmVb2APRxqU1k4/f3/dKQbB/a0OQcbb731DZis9tA7ELBlR0EhfJTLkh/HoSDug
lQB4VHLPNTHh4ih07eHKhkyyf1ZfRs15N5m7f55ATL137pIGexBN3M2I1jpjeQVR
lmWabXiXHlIRpK8+6uxTTzLOSPQeJbaHlhR5EKPSWdxtp7eu79QmZsvjN9O72hY1
4SmCWxcNqId8KtWKyn8ai3givGvwi617KP67Mf0zUPS7y8rPy/Y=
=S3n+
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.