Debian Bug report logs - #821533
mlmmj-php-web-admin: PHP 7.0 Transition

Toggle useless messages

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

From: Ondřej Surý <ondrej@debian.org>

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

Subject: mlmmj-php-web-admin: PHP 7.0 Transition

Date: Mon, 18 Apr 2016 22:58:43 +0200

Package: mlmmj-php-web-admin
Version: 1.2.18.1-1
Severity: important
User: pkg-php-maint@lists.alioth.debian.org
Usertags: php7.0-transition

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

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The mlmmj-php-web-admin package currently depends on php5 .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
     phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
     MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
     specify a dependency, please use the generic name, unless you
     absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
     /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
     php-apcu-bc) can be used as a template how to change the PHP
     extension packaging.  It's mostly cut&paste since the d/rules tries
     to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
     package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
     need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
     7.0, that means that all packages needs to be made compatible with
     PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
     maintained software.  However some extensions has been deprecated
     (f.e. mysql) and thus old unmaintained software will stop working
     and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

    RM: mlmmj-php-web-admin -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-pear@lists.alioth.debian.org -- for PEAR related packages
pkg-php-pecl@lists.alioth.debian.org -- for PHP extensions
pkg-php-maint@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

- -- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUqDXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHsZoP/1YrAC/4GL64QwjhvnW/F+rU
vF+cp9gOOO/Gy34+mXULaS8h1fJ8fxUU2rfpvt+fxUJdKZov4ZQusAJMafcJHMMt
p3g+6Yq85dhkpwPTgL7NngL/cGEmqkRF6HlsE6m390FgnI56pSUboGJaA6hvpkdG
jkt9eVXDCKOECkfxzwnHSDJxm3FOWyuh2c1ZAAM+MzA+wpuVa7MISHzkhBwvaXi/
mfmjJmZZuKGkuDWw/p3BqWLU6Zd1fk0mvG6tttYR0YrQePlGekDnfBSbo5KGjthp
Jruv31NYhTjVln+k+0kGcWpmKT6Ax/Ji955qcNhoM4oSqPGT2Oy8MO8GXubdvevJ
kWitSYceVu7jhsKaMbAXRYQxW0bA+0jJbgEOQxnAqQ19saHNLRmv+MrhnMV3ULLH
Xrdard35DC4BYGXv6HjQF69vy6W0z+ClgMRLrSHY6chFkb4BzCyPCCelPw15UQD+
nNngY2Kotxqso2wh4F1F4sbdKeQlws1YtxRypm+qq4+UZvqLl7Yp6615kres6ozO
qB9qv9eR0OCS5FL+q8HA/A9+lfs+b0aAXri8zlTJYXdN7BBWAqZ0Z9HDMzWMhiwz
C2IQt5dxpHI+VSOa7tv0y9WFDU0MYLCCyqp/6smL1VZVsLK/erB0OIRJlQKb7mY0
gGoVpVdrkwEYikmBWVON
=Iqhp
-----END PGP SIGNATURE-----

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

From: Ondřej Surý <ondrej@sury.org>

To: 821533@bugs.debian.org

Subject: Bumping severity of PHP 7.0 transition bugs to serious

Date: Thu, 5 May 2016 10:20:56 +0200

Dear maintainer(s),

I am bumping the severity of this bug to serious, as we are going to
remove src:php5 from Debian and your package is blocking the first
step which is removal of php5 from testing.  Please either update your
package to support PHP 7.0 or remove the package from Debian unstable
alltogether.

Cheers,
Ondrej

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

From: Chris Knadle <Chris.Knadle@coredump.us>

To: Ondřej Surý <ondrej@sury.org>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Thu, 19 May 2016 02:47:54 +0000

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

I have a patch to switch mlmmj to use PHP 7.0 instead of PHP 5 (that change
is trivial -- literally php5 -> php), but I'm running into a snag testing
the resulting binary packages: trying to load Apache2 with PHP 7.0 fails to
start with the error message:

  "Apache is running as threaded MPM, but your PHP module is not compiled
   to be threadsafe.  You need to recompile PHP."

and looking at the README.Debian.gz for libapache2-mod-php7.0, the document
only discusses PHP 5.  :-/  I'm having a look at the php7.0 source
package... libapache2-mod-php.postinst.extra seems to test for mpm but I'm
suspecting that this needs tweaking for how Apache2 is currently packaged in
Sid.  ('a2query -M' returns 'event' which is not a case that's being looked
for, and Apache2 isn't split into mpm/prefork packages anymore.)

   -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us

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

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

From: Ondřej Surý <ondrej@sury.org>

To: Chris Knadle <Chris.Knadle@coredump.us>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: Re: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Thu, 19 May 2016 10:23:11 +0200

The code is postinst is correct. This should switch to prefork when
a2query -M returns anything else then prefork or itk:

        mpm=$(a2query -M)
        case "$(a2query -M)" in
            prefork|itk) return 0;;
            *) if apache2_switch_mpm prefork; then return 0; fi;;
        esac

Could you check your apt.log for:

ERROR: $PHP_MODULE module already enabled, not enabling PHP
@PHP_VERSION@

or

ERROR: Could not switch to prefork MPM, not enabling PHP @PHP_VERSION@

?

Cheers,
-- 
Ondřej Surý <ondrej@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Thu, May 19, 2016, at 04:47, Chris Knadle wrote:
> I have a patch to switch mlmmj to use PHP 7.0 instead of PHP 5 (that
> change
> is trivial -- literally php5 -> php), but I'm running into a snag testing
> the resulting binary packages: trying to load Apache2 with PHP 7.0 fails
> to
> start with the error message:
> 
>   "Apache is running as threaded MPM, but your PHP module is not compiled
>    to be threadsafe.  You need to recompile PHP."
> 
> and looking at the README.Debian.gz for libapache2-mod-php7.0, the
> document
> only discusses PHP 5.  :-/  I'm having a look at the php7.0 source
> package... libapache2-mod-php.postinst.extra seems to test for mpm but
> I'm
> suspecting that this needs tweaking for how Apache2 is currently packaged
> in
> Sid.  ('a2query -M' returns 'event' which is not a case that's being
> looked
> for, and Apache2 isn't split into mpm/prefork packages anymore.)
> 
>    -- Chris
> 
> -- 
> Chris Knadle
> Chris.Knadle@coredump.us
> 
> 
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

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

From: Chris Knadle <Chris.Knadle@coredump.us>

To: Ondřej Surý <ondrej@sury.org>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: Re: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Thu, 19 May 2016 15:24:14 +0000

Ondřej Surý:
> The code is postinst is correct. This should switch to prefork when
> a2query -M returns anything else then prefork or itk:
> 
>         mpm=$(a2query -M)
>         case "$(a2query -M)" in
>             prefork|itk) return 0;;
>             *) if apache2_switch_mpm prefork; then return 0; fi;;
>         esac
> Could you check your apt.log for:
> 
> ERROR: $PHP_MODULE module already enabled, not enabling PHP
> @PHP_VERSION@
> 
> or
> 
> ERROR: Could not switch to prefork MPM, not enabling PHP @PHP_VERSION@

Hmm.  Well I don't have an apt.log, but I found this in /var/log/apt/term:

   Creating config file /etc/php/7.0/apache2/php.ini with new version
   Setting up libapache2-mod-php7.0 (7.0.6-10) ...
   Warning: Could not load Apache 2.4 maintainer script helper

Something to note: /usr/share/apache2/apache2-maintscript-helper is part of
the 'apache2' package, which libapache2-mod-php7.0 doesn't depend on.  (It
currently depends on apache2-api and apache2-bin.)  After installing this I
found Apache2 wasn't running and then loaded the apache2 package, then tried
making links in /etc/apache2/mods-enabled to
/etc/apache2/mods-available/php7.0.conf and php7.0.load, leading to the
Apache2 error concerning the PHP module not being threadsafe.

Later on in /var/log/apt/term when upgrading libapache2-mod-php7.0:

    Setting up libapache2-mod-php7.0 (7.0.6-12) ...
    ERROR: php7.7 module already enabled, not enabling PHP 7.0

?  php7.7?  That sounds odd.

   -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us

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

From: Ondřej Surý <ondrej@sury.org>

To: Chris Knadle <Chris.Knadle@coredump.us>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: Re: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Thu, 19 May 2016 17:32:08 +0200

php7.7 sounds odd, but it's result of this command:

a2query -m | sed -n 's/^\(php[\.0-9]*\) (enabled.*)/\1/p'

Hmm, I'll speak with apache2 maintainers how to solve this. It looks
like you need to install apache2 first and then install
libapache2-mod-php7.0.

Unfortunatelly you should not depend on apache2 package:

https://lintian.debian.org/tags/apache2-module-depends-on-real-apache2-package.html

Cheers,
-- 
Ondřej Surý <ondrej@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Thu, May 19, 2016, at 17:24, Chris Knadle wrote:
> Ondřej Surý:
> > The code is postinst is correct. This should switch to prefork when
> > a2query -M returns anything else then prefork or itk:
> > 
> >         mpm=$(a2query -M)
> >         case "$(a2query -M)" in
> >             prefork|itk) return 0;;
> >             *) if apache2_switch_mpm prefork; then return 0; fi;;
> >         esac
> > Could you check your apt.log for:
> > 
> > ERROR: $PHP_MODULE module already enabled, not enabling PHP
> > @PHP_VERSION@
> > 
> > or
> > 
> > ERROR: Could not switch to prefork MPM, not enabling PHP @PHP_VERSION@
> 
> Hmm.  Well I don't have an apt.log, but I found this in
> /var/log/apt/term:
> 
>    Creating config file /etc/php/7.0/apache2/php.ini with new version
>    Setting up libapache2-mod-php7.0 (7.0.6-10) ...
>    Warning: Could not load Apache 2.4 maintainer script helper
> 
> Something to note: /usr/share/apache2/apache2-maintscript-helper is part
> of
> the 'apache2' package, which libapache2-mod-php7.0 doesn't depend on. 
> (It
> currently depends on apache2-api and apache2-bin.)  After installing this
> I
> found Apache2 wasn't running and then loaded the apache2 package, then
> tried
> making links in /etc/apache2/mods-enabled to
> /etc/apache2/mods-available/php7.0.conf and php7.0.load, leading to the
> Apache2 error concerning the PHP module not being threadsafe.
> 
> Later on in /var/log/apt/term when upgrading libapache2-mod-php7.0:
> 
>     Setting up libapache2-mod-php7.0 (7.0.6-12) ...
>     ERROR: php7.7 module already enabled, not enabling PHP 7.0
> 
> ?  php7.7?  That sounds odd.
> 
>    -- Chris
> 
> -- 
> Chris Knadle
> Chris.Knadle@coredump.us

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

From: Chris Knadle <Chris.Knadle@coredump.us>

To: Ondřej Surý <ondrej@sury.org>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: Re: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Thu, 19 May 2016 18:48:57 +0000

Ondřej Surý:
> php7.7 sounds odd, but it's result of this command:
> 
> a2query -m | sed -n 's/^\(php[\.0-9]*\) (enabled.*)/\1/p'
> 
> Hmm, I'll speak with apache2 maintainers how to solve this. It looks
> like you need to install apache2 first and then install
> libapache2-mod-php7.0.

Yeah that was it.  I really appreciate the help, I'm not sure I would have
figured that out.  Removing libapache2-mod-php7.0 required removing php as
well as mlmmj-php-web, etc temporarily, reinstalling libapache2-mod-php7.0
after apache2 works fine.

> Unfortunatelly you should not depend on apache2 package:
> 
> https://lintian.debian.org/tags/apache2-module-depends-on-real-apache2-package.html

Hmm.  If that's the case then I'm guessing the way to fix this dependency
issue would involve splitting off certain things from the apache2 package
into yet another binary package.  :-/  Ugh.

Thanks much.

   -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us

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

From: Chris Knadle <Chris.Knadle@coredump.us>

To: Ondřej Surý <ondrej@sury.org>

Cc: 821532@bugs.debian.org, 821533@bugs.debian.org

Subject: Re: mlmmj-php-web, mlmmj-php-web-admin: PHP 7.0 Transition

Date: Wed, 25 May 2016 21:51:40 +0000

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

The PHP 5 -> 7 transition: there was one eregi() call and one ereg() call
which are functions deprecated in PHP 5.3.-0 removed from PHP 7.0.0.  With
those fixed the mlmmj-php-web and mlmmj-php-web-admin packages work fine.

debdiff attached.

   -- Chris

-- 
Chris Knadle
Chris.Knadle@coredump.us

[mlmmj_1.2.18.1-2.debdiff (text/plain, attachment)]

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

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

From: Christopher Knadle <Chris.Knadle@coredump.us>

To: 821533-close@bugs.debian.org

Subject: Bug#821533: fixed in mlmmj 1.2.18.1-2

Date: Thu, 26 May 2016 07:49:14 +0000

Source: mlmmj
Source-Version: 1.2.18.1-2

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

Debian distribution maintenance software
pp.
Christopher Knadle <Chris.Knadle@coredump.us> (supplier of updated mlmmj 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: Wed, 11 May 2016 22:46:20 -0400
Source: mlmmj
Binary: mlmmj mlmmj-php-web mlmmj-php-web-admin
Architecture: source amd64 all
Version: 1.2.18.1-2
Distribution: unstable
Urgency: medium
Maintainer: MLMMJ packaging team <pkg-mlmmj-devel@lists.alioth.debian.org>
Changed-By: Christopher Knadle <Chris.Knadle@coredump.us>
Description:
 mlmmj      - mail server independent mailing list manager
 mlmmj-php-web - web interface for mlmmj, written in php
 mlmmj-php-web-admin - administrative web interface for mlmmj, written in php
Closes: 804436 821532 821533
Changes:
 mlmmj (1.2.18.1-2) unstable; urgency=medium
 .
   * debian/control
     - Add myself to Uploaders
     - Depend on PHP 7 rather than PHP 5 (Closes: #821532, #821533)
     - Update Standards-Version to 3.9.8 (no changes needed)
     - Update Vcs-Browser and Vcs-Git links with https version
   * debian/copyright
     - Update from DEP5 to copyright 1.0 format
     - Update BSD keyword to BSD-4-clause
   * debian/docs:
     - Remove debian/README.source (file removed)
   * debian/patches:
     - Update 05_fix_displayed_full_paths.diff for line offset fuzz
     - Reorder series file to apply patches in numeric order
     - Add 06_fix-php-web-for-php7.diff to fix mlmmj web packages for PHP 7.0
     - Add 07_fix-crontab-suggestions.diff to fix the crontab instructions to
       include the user (root) to run the crontab entry, and inform the user
       that the Debian package already includes a crontab entry
       (Closes: #804436)
   * debian/rules:
     - Update to split up package building for arch and indep so that
       binary-arch doesn't produce "arch: all" packages which is supposed
       to happen only in the binary-indep target
   * debian/README.source:
     - Remove file as it is no longer necessary; stated that the package is
       using dpatch which isn't the case as of 1.2.17-4
Checksums-Sha1:
 da238e55575139190bc0572bc6df5ad332e0b74f 2077 mlmmj_1.2.18.1-2.dsc
 851d1596f97b594b65f73951efde8150a9df8724 23200 mlmmj_1.2.18.1-2.debian.tar.xz
 8f31914d8a2af67bc2874c18e3eaf1cd84078d8d 390592 mlmmj-dbgsym_1.2.18.1-2_amd64.deb
 ad7b179598910117dc3cebd84f806631d28e4cc4 37472 mlmmj-php-web-admin_1.2.18.1-2_all.deb
 9653baf09c32d95bb2144cacc5d63d3cea0d8af7 22450 mlmmj-php-web_1.2.18.1-2_all.deb
 22338a9d80e8c118a8666ffcdecb5466597ec0ff 185804 mlmmj_1.2.18.1-2_amd64.deb
Checksums-Sha256:
 a354d0cfa5d9a7a73e78cb822d864523987db0820595d7b4d18d20dfbe60be35 2077 mlmmj_1.2.18.1-2.dsc
 619b197760a68c211f02a5ddf8ce36945adfa269e43927c425268adf84733629 23200 mlmmj_1.2.18.1-2.debian.tar.xz
 8071679686381efabeac64da818275bef166fc5bb95f8677d8a2ccdc49e7c8a4 390592 mlmmj-dbgsym_1.2.18.1-2_amd64.deb
 4680a577ae90bd8ac52bf9b7bdd62a8b12b7d32022fdc420c703cf16746759b4 37472 mlmmj-php-web-admin_1.2.18.1-2_all.deb
 c4604705e373dd17b31b07561c8985f3db3f8d64ced92527d499a108e21736c0 22450 mlmmj-php-web_1.2.18.1-2_all.deb
 dd37a4fa2f2f3bdc467f36efa26b758f7155d1569eb746019d1a027a18f62725 185804 mlmmj_1.2.18.1-2_amd64.deb
Files:
 d9d976f1530ee0a491c7199dc46bd6d6 2077 mail optional mlmmj_1.2.18.1-2.dsc
 558c450e514ae09aa0e9b4cb07db3aae 23200 mail optional mlmmj_1.2.18.1-2.debian.tar.xz
 0c03076e877c35b65ba62a6c693cc222 390592 debug extra mlmmj-dbgsym_1.2.18.1-2_amd64.deb
 0da03dcd9f14690c79250fb3dbecea91 37472 mail optional mlmmj-php-web-admin_1.2.18.1-2_all.deb
 08ec2971248f6961cbd0299395f0aeee 22450 mail optional mlmmj-php-web_1.2.18.1-2_all.deb
 78eae3fff6351be2fd19207b03f19924 185804 mail optional mlmmj_1.2.18.1-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXRqgEAAoJENQWrRWsa0P+LC4P+wWMxRcdJQEWj52i9BgDuW9F
o72BNBnkHMHeAiCWB+R1IIxrvfJWwQ+jt4AZHM8Vz+HEPN0xvay4/bsIox9eSWGz
agWhbwoEVzSeSROjVx09JQfH2v2yBqfwySaVxeTZkLrYaOax9K5hOnDPbTxXPQx1
JbSwYGoXVGnbwAxB3s8upXhSVFAlsVyuJDDKGPLdrS20bQpZ6HvcAc0sLQKq/6VH
qR7gq188wjzwk7vlZIUdCsGogEDo5+4WMRR5x8u8f8KQ+BrMKqykC/0EYaJV6IF7
bKMCLw0KQglS1uXtrvRp2bqhi2W3T6AeSntdSZQroUhg7c3pzgyd4B9t2nj5Tlj4
g/0T8/4Pgc3TNB9UXDTz3/c2uuyptORAd/JaMZMaeSCk7OcA5wqCrm+zLdJ5iuzr
O1LJ2KQbVG/4uvYj7li+WAu2Sc5x0kRdLqy/g8LPaZvvUOosPYuH0Pmj1GqJ/O9S
XO75inpISNlQ3iqBIVD9EOkcWLbinL1wcx9CKKQg2W4OQXdJ04Bm3rNvonSmFt2z
vEuSp4Lqc7RnORCywKGIAvJyFOVtM/5cbM7sA66o6Z3xvEW2z5PcCeqNVXIy8zWr
tRXx5CDrY+u2+S1QRL5i3+jv/cJeJQCvRPqZegy5QusnKE2V7R57jXweyvcVX1lv
JwG+Lhnzti0AQ7UPcTKM
=7fVM
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.