Debian Bug report logs - #597105
add support to build python3-* packages

Toggle useless messages

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

From: Matthias Klose <doko@debian.org>

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

Subject: add support to build python3-* packages

Date: Thu, 16 Sep 2010 18:53:07 +0200

Package: debhelper
Severity: wishlist

Please add support to build python3-* packages; in #597099 you'll see what is 
currently necessary to add building a python3-* package.  It would be nice if 
the overrides don't explicitly need to be added.  The various python3-* packages 
are currently in experimental.

Debhelper currently uses `pversions' to iterate over the requested python 
versions. Maybe it is just enough to iterate over the output of py3versions too, 
if dh is called --with python3?



diff -Nru pyxdg-0.19/debian/rules pyxdg-0.19/debian/rules
--- pyxdg-0.19/debian/rules     2009-12-09 21:11:54.000000000 +0100
+++ pyxdg-0.19/debian/rules     2010-09-16 16:57:45.000000000 +0200
@@ -1,4 +1,20 @@
 #!/usr/bin/make -f

 %:
-       dh $@
+       dh $@ --with python3
+
+override_dh_auto_clean:
+       dh_auto_clean
+       rm -rf build
+
+override_dh_auto_build:
+       dh_auto_build
+       set -ex; for python in $(shell py3versions -r); do \
+               $$python setup.py build; \
+       done
+
+override_dh_auto_install:
+       dh_auto_install
+       set -ex; for python in $(shell py3versions -r); do \
+               $$python setup.py install --root=$(CURDIR)/debian/tmp 
--install-layout=deb; \
+       done

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

From: Joey Hess <joeyh@debian.org>

To: Matthias Klose <doko@debian.org>, 597105@bugs.debian.org

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Wed, 29 Sep 2010 16:43:21 -0400

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

Matthias Klose wrote:
> Please add support to build python3-* packages; in #597099 you'll
> see what is currently necessary to add building a python3-* package.
> It would be nice if the overrides don't explicitly need to be added.
> The various python3-* packages are currently in experimental.
> 
> Debhelper currently uses `pversions' to iterate over the requested
> python versions. Maybe it is just enough to iterate over the output
> of py3versions too, if dh is called --with python3?

Is there not something in debian/control that can be examined to see if
the package is intended to be built for python3?

-- 
see shy jo

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

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

From: Matthias Klose <doko@debian.org>

To: Joey Hess <joeyh@debian.org>

Cc: 597105@bugs.debian.org, Piotr Ożarowski <piotr@debian.org>

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Wed, 29 Sep 2010 23:53:52 +0200

On 29.09.2010 22:43, Joey Hess wrote:
> Matthias Klose wrote:
>> Please add support to build python3-* packages; in #597099 you'll
>> see what is currently necessary to add building a python3-* package.
>> It would be nice if the overrides don't explicitly need to be added.
>> The various python3-* packages are currently in experimental.
>>
>> Debhelper currently uses `pversions' to iterate over the requested
>> python versions. Maybe it is just enough to iterate over the output
>> of py3versions too, if dh is called --with python3?
>
> Is there not something in debian/control that can be examined to see if
> the package is intended to be built for python3?

yes, three new substitution variables for the binary packages and the 
Python3-Version attribute (however the latter is not required, afaiu), e.g.

Package: python3-tk
Architecture: any
Depends: ${python3:Depends}, ${shlibs:Depends}, ${misc:Depends}
Provides: ${python3:Provides}
Suggests: tix, python3-tk-dbg
XB-Python3-Version: ${python3:Versions}
Description: Tkinter - Writing Tk applications with Python 3.x
 A module for writing portable GUI applications with Python 3.x using Tk.
 Also known as Tkinter.

It will not be uncommon that a source package builds both python-foo and 
python3-foo.

  Matthias

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

From: Piotr Ożarowski <piotr@debian.org>

To: 597105@bugs.debian.org

Cc: Matthias Klose <doko@debian.org>

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Thu, 30 Sep 2010 00:20:44 +0200

[Matthias Klose, 2010-09-29]
> On 29.09.2010 22:43, Joey Hess wrote:
>> Is there not something in debian/control that can be examined to see if
>> the package is intended to be built for python3?

I'd say existence of "python3-*" binary package and python3-all or
python3-all-dev in build dependencies is enough to start iterating over
`py3versions -rv` output (with pythonX.Y setup.py build/install ...)

Same for python3-all-dbg build dependency and python3-*-dbg binary
packages.

Note that setup3.py should be used instead of setup.py if available

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

From: Éric Araujo <merwok@netwok.org>

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

Subject: Re: using setup3.py

Date: Tue, 23 Aug 2011 08:16:10 +0200

Package: debhelper
Version: 8.9.4
Followup-For: Bug #597105

Hi,

> Maybe it is just enough to iterate over the output
> of py3versions too, if dh is called --with python3?

> I'd say existence of "python3-*" binary package and python3-all or
> python3-all-dev in build dependencies is enough to start iterating over
> `py3versions -rv` output (with pythonX.Y setup.py build/install ...)

Either of these solutions would match my naïve user’s expectations.

> Note that setup3.py should be used instead of setup.py if available
I’m not aware that people use that convention.  The 3.x distutils docs
certainly don’t suggest that at all; what I’ve seen are version checks in
setup.py or Makefile.

Regards



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

Kernel: Linux 3.0.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debhelper depends on:
ii  binutils              2.21.52.20110606-2 The GNU assembler, linker and bina
ii  dpkg-dev              1.16.0.3           Debian package development tools
ii  file                  5.04-5+b1          Determines file type using "magic"
ii  html2text             1.3.2a-15          advanced HTML to text converter
ii  man-db                2.6.0.2-2          on-line manual pager
ii  perl                  5.12.4-4           Larry Wall's Practical Extraction 
ii  perl-base             5.12.4-4           minimal Perl system
ii  po-debconf            1.0.16+nmu1        tool for managing templates file t

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make                       0.59       tool that converts source archives

-- no debconf information

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

From: Julian Gilbey <jdg@debian.org>

To: Joey Hess <joeyh@debian.org>, 597105@bugs.debian.org

Cc: Matthias Klose <doko@debian.org>

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Sun, 11 Sep 2011 21:42:28 +0100

On Wed, Sep 29, 2010 at 04:43:21PM -0400, Joey Hess wrote:
> Matthias Klose wrote:
> > Please add support to build python3-* packages; in #597099 you'll
> > see what is currently necessary to add building a python3-* package.
> > It would be nice if the overrides don't explicitly need to be added.
> > The various python3-* packages are currently in experimental.
> > 
> > Debhelper currently uses `pversions' to iterate over the requested
> > python versions. Maybe it is just enough to iterate over the output
> > of py3versions too, if dh is called --with python3?
> 
> Is there not something in debian/control that can be examined to see if
> the package is intended to be built for python3?

Also, the python_distutils script (called with -Spython_distutils)
barfs as well; perhaps a parallel python3_distutils could be created?

   Julian

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

From: Julian Gilbey <jdg@debian.org>

To: Joey Hess <joeyh@debian.org>, 597105@bugs.debian.org

Cc: Matthias Klose <doko@debian.org>

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Sun, 11 Sep 2011 22:03:42 +0100

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

On Sun, Sep 11, 2011 at 09:42:28PM +0100, Julian Gilbey wrote:
> Also, the python_distutils script (called with -Spython_distutils)
> barfs as well; perhaps a parallel python3_distutils could be created?

Attached is a patch for python3_distutils from python_distutils.

   Julian

[python3.diff (text/x-diff, attachment)]

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

From: Joey Hess <joeyh@debian.org>

To: 597105@bugs.debian.org

Cc: Matthias Klose <doko@debian.org>, Julian Gilbey <jdg@debian.org>

Subject: Re: Bug#597105: add support to build python3-* packages

Date: Thu, 8 Dec 2011 18:17:40 -0400

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

Julian's patch adding a --buildsystem=python3 seems problimatic, since
I understand that many packages will want to build for both python2 and
python3, and debhelper only supports using one buildsystem at a time.

Since pyversions/py3versions already look at debian/control,
couldn't one of them get a switch that reads the tea-leaves and
says which python versions a package is intended to build for?
debhelper's python buildsystem could them use that.

-- 
see shy jo

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

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

From: Piotr Ożarowski <piotr@debian.org>

To: debian-python@lists.debian.org

Subject: pybuild - one to rule^W build them all

Date: Sat, 19 Jan 2013 18:14:22 +0100

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

[debhelper's #538978 and #597105 bugs BCCed]

Hi,

FYI: python3 package in experimental (3.3.0-2) contains pybuild tool
with dh command sequencer integration.

You can build modules/extensions for Python 2.X *and* Python 3.X with
this debian/rules file:

 #!/usr/bin/make -f
 %:
 	dh $@ --with python2,python3 --buildsystem=pybuild

pybuild.pm will check Build-Depends* and build Python (python,
python-dev, python-dbg, python-all, python-all-dev, python-all-dbg),
Python 3 (python3, python3-dev, python3-dbg, python3-all,
python3-all-dev, python3-all-dbg) and PyPy (pypy) modules/extensions.

It can be configured via command line or CDBS-like - by exporting
PYBUILD_OPTION / PYBUILD_OPTION_interpreter / 
PYBUILD_OPTION_interpreterversion env. variables in debian/rules, f.e.

* if you don't want to use debian/*.install files,
  you can set DESTDIR for each interpreter (note that you can use "python2" for
  all python2.X interpreters and "python3" for all python3.X ones):

 export PYBUILD_DESTDIR_python2=debian/python-foo/
 export PYBUILD_DESTDIR_python2-dbg=debian/python-foo-dbg/
 export PYBUILD_DESTDIR_python3=debian/python3-foo/
 export PYBUILD_DESTDIR_python3-dbg=debian/python3-foo-dbg/
 export PYBUILD_DESTDIR_python3.1-dbg=debian/spam-pkg-with-python3.1-only/
 export PYBUILD_DESTDIR_pypy=debian/pypy-foo/

* if you want to add some custom arguments to Python 3's install command:

 export PYBUILD_INSTALL_ARGS_python3=--install-scripts=/usr/share/foo/

* you can disable (almost) any action via --disable / DISABLE env. var:

 export PYBUILD_DISABLE=configure
 export PYBUILD_DISABLE_python3.1=test

* if you want to disable Build-Depends detection:

 export PYBUILD_INTERPRETERS=python{version} python{version}-dbg
 export PYBUILD_VERSIONS=2.7 3.3

* if auto detection didn't detect the right build system:

 export PYBUILD_SYSTEM=distutils

* if you want to add a custom command before or after each iteration:

 export PYBUILD_BEFORE_BUILD=echo {version} >> '{dir}/enabled'
 export PYBUILD_AFTER_INSTALL=rm -rf '{destdir}/{install_dir}/foo/tests'


Right now it supports distutils (i.e. setup.py) and custom build systems only
(I tried to add cmake one that uses dh_auto_* tools, but failed to teach cmake
which interpreter should be used).

Anyone wants to contribute more plugins? Let me know if you want some guidance
or if I can make writing plugins easier.

If your build system is not yet supported, you can use custom build system:

 export PYBUILD_SYSTEM=custom
 export PYBUILD_CLEAN_ARGS=rm -rf {build_dir}/python{version}/
 export PYBUILD_CONFIGURE_ARGS=./configure --python={version}
 export PYBUILD_BUILD_ARGS=make build --dir={build_dir} --python={version}
 export PYBUILD_INSTALL_ARGS=make --destdir={destdir} --python={version} --install-dir={install_dir}
 export PYBUILD_TEST_ARGS_python2=cd {build_dir}; nosetests
 export PYBUILD_TEST_ARGS_python3=cd {build_dir}; python{version} -m discover


PS pybuild manpage is available also here: http://deb.li/pybuild
-- 
Piotr Ożarowski                         Debian GNU/Linux Developer
www.ozarowski.pl          www.griffith.cc           www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

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

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

From: Osamu Aoki <osamu@debian.org>

To: 597105@bugs.debian.org

Subject: RE: Message #5 for add support to build python3-* packages

Date: Sat, 18 May 2013 07:58:08 +0900

Hi,

As I see this bug report, 2 distinct approaches are discussed.

 * Message #5  : just build python3 only
 * Message #45 : fancy build for both python and python3

This comment on Message #5.  http://bugs.debian.org/597105#5

I used this patch to build a package and got hit by an intriguing
Bug#708138.  Jakub Wilk  helped me to understand the problem.

Script in Message #5 containing "$$python setup.py install" should have
"--force".

Here is why.  Let's think if we have 3.2 and 3.3.  This script execute
3.3 first and install script with #! line set to 3.3.  If there is no
--force, second run with python3 will not overwrite this installed
file.  This is not optimal since non-default version is written into
installed script #! line.

Regards,

Osamu

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

From: Niels Thykier <niels@thykier.net>

To: 597105-close@bugs.debian.org

Subject: Bug#597105: fixed in debhelper 11.3

Date: Sun, 20 May 2018 20:49:16 +0000

Source: debhelper
Source-Version: 11.3

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

Debian distribution maintenance software
pp.
Niels Thykier <niels@thykier.net> (supplier of updated debhelper 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: Sun, 20 May 2018 20:35:00 +0000
Source: debhelper
Binary: debhelper dh-systemd
Architecture: source
Version: 11.3
Distribution: unstable
Urgency: medium
Maintainer: Debhelper Maintainers <debhelper@packages.debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Description:
 debhelper  - helper programs for debian/rules
 dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
Closes: 491027 513521 568033 597105 597342 769840 776853 813686 816332 894510 895196 895286 896464 897026 897083 897569 897937 897949 898161 898347 899125
Changes:
 debhelper (11.3) unstable; urgency=medium
 .
   [ Niels Thykier ]
   * Buildsystem.pm: Fix use of undefined variable in certain
     error conditions.
   * dh_makeshlibs: Support -VUpstream-Version and -VNone as
     alternative to passing -V or omitting -V respectively.
   * dh_makeshlibs: Make -VUpstream-Version the default in
     compat 12 when -V is omitted.  (Closes: #896464)
   * dh_makeshlibs: Correct handling of an explicit -V when
     a source builds multiple library packages and provides
     explicit shlibs files for a subset of them.  Previously,
     the -V option could have been ignored for some of the
     packages containing libraries.
   * Dh_Lib.pm: Fall back to a regular mv(1) when rename fails
     with EXDEV (cross mount point moves).  This restores
     debhelper's ability to move files between mount points,
     which can happen in dh_builddeb has to correct the
     extension of a binary package built by dpkg-deb.
     Thanks to Evan Krall for the report.  (Closes: #897569)
   * dh_missing.1: Consistently mention that dh_missing
     defaults to --list-missing in compat 12.  Thanks to
     Robie Basak for spotting the contradicting documentation.
     (Closes: #898161)
   * dh_compress:  Avoid adding a duplicate ".gz" extension on
     a symlink if it already has it.   This can happen e.g. with
     dh_installman recompresses a manpage that was compressed and
     had a valid symlink to it.  Thanks to Andreas Hasenack for
     reporting the bug.  (Closes: LP: #1765851)
   * debian/control: Depend on dwz for dh_dwz.
   * dh_dwz: Generate a per-package multifile by default.  This
     feature can be disabled by --no-dwz-multifile.
   * dh: Run dh_dwz by default in compat 12.
   * dh_dwz: Remove warning about the dwz feature being experimental.
   * dwz.pm: Ditto.
   * dh_installsystemd: Use the basename of the "tmpfiles" config
     files.  This makes "systemd-tmpfiles --create" search for it
     in both /usr/lib/tmpfiles.d and in /etc/tmpfiles.d.  With
     this change the system administrator can now override the
     "tmpfiles" config shipped by the package in
     /usr/libtmpfiles.d.  Thanks to Nick Groenen and Seyeong Kim
     for filing the bug.  (Closes: #894510)
   * dh_installinit: Ditto.
   * dh_installchangelogs: Look for changelog files installed by the
     upstream build system in the package build dir (i.e. d/<pkg>/
     and *not* debian/tmp!) and use them in preference to the one in the
     source package where available.  This avoids some cases of duplicated
     upstream changelogs.  Thanks to Evgeni Golov for the suggestion.
     (Closes: #513521)
   * dh_md5sums: Stop deleting empty md5sums files as dpkg (now) creates
     the empty file on install if absent.  Thanks to Rhonda D'Vine for
     suggesting the improvement.  (Closes: #776853)
   * Dh_Lib.pm: Re-organise exports.
   * Dh_Lib.pm: Retract "print_and_complex_doit"; the only potential
     consumer went with a different code snippet.
   * dh_installinitramfs: New tool to install initramfs hook scripts and
     handle related maintscripts.  Thanks to Evgeni Golov for the
     suggestion.  (Closes: #491027)
   * installinitramfs.pm: New sequence to enable dh_installinitramfs in
     compat 11 and earlier.
   * dh_installdirs: Add --(no-)create-in-sourcedir option to make
     dh_installdirs create directories in the source directory in addition
     in the package build directory.  Furthermore, dh_installdirs now
     accepts --sourcedir to overrule the default source directory (just
     like e.g. dh_install).  Thanks to Robert Luberda for the suggestion.
     (Closes: #816332)
   * Buildsystem.pm: Move code from Dh_Buildsystems.pm to Buildsystem.pm
     to make the latter independent of the former.  This makes it possible
     to load Buildsystem.pm without debian/control being present.  Thanks
     to Andreas Tille for the bug report.  (Closes: #897026)
   * dh_installinit.1: Fix some incorrect markup in the documentation of
     --no-enable.
   * makefile.pm: Revert the use of -O/-Oline for make, which helps
     debugging what commands time out on the buildds.  Thanks to
     Adrian Bunk for the report.  (Closes: #895196)
   * dh_testroot.1: Update R³ documentation to reflect the current
     implementation and not the initial draft.  Thanks to Jens Reyer
     for reporting the inconsistency.  (Closes: #899125)
   * d/changelog: Retroactively add Closes for LP bug #1766102 in 11.2
     release.
   * Dh_Lib.pm: Correct control parser to permit zero or more leading
     space after the "Section" field (instead of "exactly one" space).
   * python_distutils.pm: Deprecate the python-distutils build system
     and mark it as removed in compat 12.  Users are recommended to
     migrate to the third-party build system called "pybuild".  This
     deprecation implies that python3 (among other) will not be
     supported in the python-distutils build system.
     (Closes: #568033, #597105, #597342, #769840, #813686, #898347)
   * Dh_Lib.pm: Remove warning for using "debhelper-compat"
     build-dependency.
 .
   [ Dmitry Shachnev ]
   * qmake.pm: Use ${DEB_HOST_GNU_TYPE}-qmake wrapper for
     cross-compilation.  (Closes: #895286)
 .
   [ Helmut Grohne ]
   * cmake: Pass CC/CXX environment variables down during native
     compilation as well. (Closes: #897083)
 .
   [ Chris Lamb ]
   * dh_listpackages.1: Document that packages are listed in the
     order that they appear in debian/control.
     (Closes: #897949)
 .
   [ Peter Pentchev ]
   * Dh_Lib: Permit leading and trailing whitespace around the
     debhelper-compat dependency when it is the first or the last
     relation listed.  (Closes: #897937)
 .
   [ Jakub Wilk ]
   * dh_usrlocal: Fix invalid POD markup.
Checksums-Sha1:
 c5d56030dfc68a314ff93b1442590be85a92eb1f 1681 debhelper_11.3.dsc
 462d3cf30ecfb50a97c75c4e4abdf10892ae920c 463656 debhelper_11.3.tar.xz
 00d25bd7c1f9cfd489a36616075411f8b1d99103 4587 debhelper_11.3_source.buildinfo
Checksums-Sha256:
 f8317e2e58e1be4aa00a74d5f6f7cb6ebf2f415e4c998be0b8657ca2262ecfea 1681 debhelper_11.3.dsc
 5bb3cb08aae1f3d926537b53592dda734135b08f8a6288bcff423a6dc2fa5250 463656 debhelper_11.3.tar.xz
 1bd86408a10064dee24085a88615f1355285380bebb72d6c0e8c54b1a5701af0 4587 debhelper_11.3_source.buildinfo
Files:
 0e6979b42194acada5bccb02f1a52f45 1681 devel optional debhelper_11.3.dsc
 978402ce4fa2e27cfb70cb5fb30b4b24 463656 devel optional debhelper_11.3.tar.xz
 ff9fb971ceac48052c3ebd260876311b 4587 devel optional debhelper_11.3_source.buildinfo

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

iQIzBAEBCAAdFiEEsxMaRR2/33ygW0GXBUu7n32AZEIFAlsB3M4ACgkQBUu7n32A
ZEKskA/8C3J5ubadevzgiv0hdx30BQpfvzHc/gbARbNLILa3RoAxYt5htgmqQDH8
/CtMtXGCrYaKWALRyBIhTYowhoKpq2IMsznJsdP66pezpX0JdkiTeVwoFdXvRy/A
m2z2uCnQFDRoGRRLXfy793MTgOei6JqraO+RWNCju1YkNkor/LGi22v1vsdb1dR2
Rub2laqQ+EVIpQ6ORjZKBDBlnI5tmDmuEacDLyQHDeBqEVl3BGDxSSxIVHHnc8mS
+zh0GLLzMSc/h9N18ElQiWJK5JPYax/sLh9tmua53mxRLzpmP5wuq+DJX9+UMoYO
tW2m8FfVjmfVo1NwRqt/CFge6QDeMUFkLuW6tc6CRo88IzC1JxGFzL7C4eGg2C0/
hKZX5r3GHsT+CArgVMJRNhGnQXqQaQRTnxUgUqouaefuZxETKidZjAMZqNBREv4E
IxD7U5WhxRckKTocXwVx5AGV3nP4jCL+5UGc3Ezn41yvSXD9ew7gbmEwXJzyB6MT
/3tQh694lcY3wMIvwvW/HqoFzNzDef7t26xWy0Vb77KnGlf5hSQL/L4DPFJEv4BH
p94SQ1YhPoaStrlcPVACMHj7rRflZEaoQzKKv5Eg2P+R0UvYTl+tbhS6tlaPHErG
fs4+VguK8D6sSh01dXeBUULpqyBbJSsegAg1hjcTHMKGPqg9nD0=
=1svF
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.