Bug#954754: marked as done (remaster-iso: Missing isolinux as dependency)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 05:49:51 +
with message-id 
and subject line Bug#954754: fixed in remaster-iso 0.9.3-1
has caused the Debian Bug report #954754,
regarding remaster-iso: Missing isolinux as dependency
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: remaster-iso
Version: 0.9.2-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I recently installed remaster-iso package, but when I issued the
remaster-compose command, I got this:

- -
# remaster-compose
...
Drive current: -outdev
'stdio:/home/morfik/Desktop/debian/202003222304-remaster-iso.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 25.4g free
xorriso : WARNING : -volid text problematic as automatic mount point name
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
xorriso : NOTE : -as mkisofs: Ignored option '-cache-inodes'
Added to ISO image: directory '/'='/home/morfik/Desktop/debian/iso-extract'
xorriso : UPDATE :1083 files added in 1 seconds
xorriso : FAILURE : Given path does not exist on disk: -boot_image
system_area='/usr/lib/ISOLINUX/isohdpfx.bin'
xorriso : UPDATE :1083 files added in 1 seconds
xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE'
I: ... 202003222304-remaster-iso ISO composition attempt is now complete.
I: Creating a MD5SUM of the completed iso file ...
md5sum: /home/morfik/Desktop/debian/202003222304-remaster-iso.iso: No such file
or directory
I: ... iso MD5SUM completed.
- -

This ERROR is because the /usr/lib/ISOLINUX/isohdpfx.bin file doesn't exist in
my system -- I didn't have the **isolinux** package installed. After I
installed
it, everything works well now:

- -
# remaster-compose
...
Drive current: -outdev
'stdio:/home/morfik/Desktop/debian/202003222340-remaster-iso.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 25.4g free
xorriso : WARNING : -volid text problematic as automatic mount point name
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
xorriso : NOTE : -as mkisofs: Ignored option '-cache-inodes'
Added to ISO image: directory '/'='/home/morfik/Desktop/debian/iso-extract'
xorriso : UPDATE :1083 files added in 1 seconds
xorriso : UPDATE :1083 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file
'/usr/lib/ISOLINUX/isohdpfx.bin'
libisofs: NOTE : Automatically adjusted MBR geometry to 1019/152/32
libisofs: NOTE : Aligned image size to cylinder size by 509 blocks
xorriso : UPDATE :  1.18% done
...
xorriso : UPDATE :  99.10% done
ISO image produced: 1239104 sectors
Written to medium : 1239104 sectors at LBA 0
Writing to 'stdio:/home/morfik/Desktop/debian/202003222340-remaster-iso.iso'
completed successfully.

I: ... 202003222340-remaster-iso ISO composition attempt is now complete.
I: Creating a MD5SUM of the completed iso file ...
I: ... iso MD5SUM completed.
- -



- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (130, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.11-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages remaster-iso depends on:
ii  rsync   3.1.3-8
ii  squashfs-tools  1:4.4-1
ii  xorriso 1.5.2-1

remaster-iso recommends no packages.

remaster-iso suggests no packages.




-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQR1ZhNYxftXAnkWpwEy2ctjR5bMoQUCXnfqiQAKCRAy2ctjR5bM
oXHUAP9IUZhM+SyC2UDEMuOEF3O3SKyDCm4csBiTT0X27rFgcgD+O99UWMkl2r7x
deX0T2v2aFYvZX1sSqKN/6CcIx4ODwU=
=K1YU
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: remaster-iso
Source-Version: 0.9.3-1
Done: Richard Nelson 

We believe that the bug you reported is fixed in the latest version of
remaster-iso, which is due to be installed in the Debian FTP archive.

A summary of the changes between this 

Bug#936539: marked as done (font-manager: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 05:05:45 +
with message-id 
and subject line Bug#936539: fixed in font-manager 0.7.7-0.1
has caused the Debian Bug report #936539,
regarding font-manager: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:font-manager
Version: 0.7.3-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:font-manager

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: font-manager
Source-Version: 0.7.7-0.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated font-manager 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Mar 2020 23:46:50 -0400
Source: font-manager
Architecture: source
Version: 0.7.7-0.1
Distribution: unstable
Urgency: medium
Maintainer: Alessio Treglia 
Changed-By: Boyuan Yang 
Closes: 890151 936539 949144
Changes:
 font-manager (0.7.7-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 0.7.7.
 + Fix build error. (Closes: #949144)
   * debian/control:
 + Bump Standards-Version to 4.5.0.
 + Bump debhelper compat to v12.
 + Migrate package to python3. (Closes: #890151, #936539)
 + Update Vcs-* fields and put Debian git packaging repo under
   Salsa fonts-team group.
 + Add Debian Fonts team into the uploaders list for team
   maintenance.
   * debian/rules: Clean up old build instructions.
   * debian/copyright: Update information.
   * debian/compat: Dropped, no longer necessary.
   * debian/source/options, debian/source/local-options: 

Bug#890151: marked as done (font-manager: Please switch to python-gobject-2/python-gi)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 05:05:45 +
with message-id 
and subject line Bug#890151: fixed in font-manager 0.7.7-0.1
has caused the Debian Bug report #890151,
regarding font-manager: Please switch to python-gobject-2/python-gi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
890151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: font-manager
Version: 0.7.3-1.1
Severity: important
Tags: buster sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: pygobject-trans-rm

Dear Maintainer,

Your package font-manager depends against the python-gobject
transitional package.

We would like to drop this transitional package for buster.

Could you please switch to either python-gobject-2 (if your package
is using the old python binding for GObject) or to python-gi (if your
package is using the new gobject-introspection one).

Please don't hesitate to contact me if you have any questions.

Kind Regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: font-manager
Source-Version: 0.7.7-0.1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated font-manager 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Mar 2020 23:46:50 -0400
Source: font-manager
Architecture: source
Version: 0.7.7-0.1
Distribution: unstable
Urgency: medium
Maintainer: Alessio Treglia 
Changed-By: Boyuan Yang 
Closes: 890151 936539 949144
Changes:
 font-manager (0.7.7-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 0.7.7.
 + Fix build error. (Closes: #949144)
   * debian/control:
 + Bump Standards-Version to 4.5.0.
 + Bump debhelper compat to v12.
 + Migrate package to python3. (Closes: #890151, #936539)
 + Update Vcs-* fields and put Debian git packaging repo under
   Salsa fonts-team group.
 + Add Debian Fonts team into the uploaders list for team
   maintenance.
   * debian/rules: Clean up old build instructions.
   * debian/copyright: Update information.
   * debian/compat: Dropped, no longer necessary.
   * debian/source/options, debian/source/local-options: Dropped,
 useless now.
   * debian/patches: Drop all patches, merged upstream.
Checksums-Sha1:
 b31f9e4512777d01ebcdbf958b7d16f55b23559d 2308 font-manager_0.7.7-0.1.dsc
 c8686f5f805e90d4e61df36f322fadd473d21b44 1699104 font-manager_0.7.7.orig.tar.xz
 914468c0bf6a2fe6c76fbd74f26923fe7e5798e1 3848 
font-manager_0.7.7-0.1.debian.tar.xz
 2444d985227ec6717df0aaa38d69522a0290307b 15896 
font-manager_0.7.7-0.1_amd64.buildinfo
Checksums-Sha256:
 c8cd26ddabc87fdd09ea015f0c4da877e174b525cfb6e7142a6fe224dd5a86c4 2308 
font-manager_0.7.7-0.1.dsc
 f8e013f8168184cf62b73a6b0053a94daf8bb22aeecd4203904e5127632d90a2 1699104 
font-manager_0.7.7.orig.tar.xz
 f934c1a7f6dad94aca8774f9625f006e06b4f5ccd6229a6ea16c20012a1fc626 3848 
font-manager_0.7.7-0.1.debian.tar.xz
 c832c299c9281076af1bfbcd4800fd2ad7e2933bd32ad318889fb0a3b86f50f2 15896 
font-manager_0.7.7-0.1_amd64.buildinfo
Files:
 9c349d8568811ff514f6c00cb42dfe94 2308 graphics optional 
font-manager_0.7.7-0.1.dsc
 0273461f7917815c94d1ec1e83308fde 1699104 graphics optional 
font-manager_0.7.7.orig.tar.xz
 a9180765ccac6200c11daaee1f9069dc 3848 graphics optional 
font-manager_0.7.7-0.1.debian.tar.xz
 49acb12dfea3b58b6be3d7923c5b258c 15896 graphics optional 
font-manager_0.7.7-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl5wTJgACgkQwpPntGGC
Ws4zyxAAl+Dkucze79cUQagu3p3w3Pqn0nYZtUYTMuqp6uYjab+wu6OOpiI+eebk
cQ1mWQhGvyZRG1TJzcO8klgsfWes4XPXkrmj1molJCSkWSs2SBHNKd1gnOCKGXAH
njZPvScw2WWSzasHSvTmAyePGejNNzm7Y+SSf9IsSQlpv4xB7OWyN1aIVPvBqsLF
yEoYE0nEwf/F4gS/3wPuk2MAE90lkAC/IQ+wAYm0BtmdE/DrjeqyzTRRlREceg3M
7Y+AyqxfyXq0iKGjTrHSmvlZDtElDisSwlwVnaa3GSjt9vNq++4jspUPoTm7oGl5
2+OUPHQNoP7ovY/FeN63K6h0AZd8mKI/KkYgemOWSmX2Um6y4hEAW9YVGMeklDrt

Bug#954752: marked as done (RM: pycha -- RoQA; Depends on Pygtk2, which is going away)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:53:05 +
with message-id 
and subject line Bug#954752: Removed package(s) from unstable
has caused the Debian Bug report #954752,
regarding RM: pycha -- RoQA; Depends on Pygtk2, which is going away
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Please remove pycha. It depends on pygtk2, which is going away and
there are no reverse deps.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

 pycha |0.7.0-2 | source
python-pycha |0.7.0-2 | all

--- Reason ---
RoQA; Depends on Pygtk2, which is going away
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/954752

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#951850: marked as done (php7.3: disable apparmor support on !linux archs)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #951850,
regarding php7.3: disable apparmor support on !linux archs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.15-2
Severity: minor
Tags: patch

Hi,

AppArmor is a Linux Security Manager, and as such it is specific for
Linux. Hence, enable the AppArmor support only on Linux, as it is
useless on non-Linux architectures.

Thanks,
-- 
Pino
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Build-Depends: apache2-dev (>= 2.4),
firebird-dev [!hurd-any !m68k !hppa !ppc64] | firebird2.5-dev 
[!hurd-any !m68k !hppa !ppc64] | firebird2.1-dev [!hurd-any !m68k !hppa !ppc64],
flex,
freetds-dev,
-   libapparmor-dev,
+   libapparmor-dev [linux-any],
libapr1-dev (>= 1.2.7-8),
libargon2-dev | libargon2-0-dev,
libbz2-dev,
--- a/debian/control.in
+++ b/debian/control.in
@@ -18,7 +18,7 @@ Build-Depends: apache2-dev (>= 2.4),
firebird-dev [!hurd-any !m68k !hppa !ppc64] | firebird2.5-dev 
[!hurd-any !m68k !hppa !ppc64] | firebird2.1-dev [!hurd-any !m68k !hppa !ppc64],
flex,
freetds-dev,
-   libapparmor-dev,
+   libapparmor-dev [linux-any],
libapr1-dev (>= 1.2.7-8),
libargon2-dev | libargon2-0-dev,
libbz2-dev,
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#952895: marked as done (php7.3-fpm: Can't install/upgrade on system with elogind (forced init switch))

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #952895,
regarding php7.3-fpm: Can't install/upgrade on system with elogind (forced init 
switch)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-fpm
Version: 7.3.15-4
Severity: normal
Tags: patch

Dear Maintainer,

with commit ccbb813a4268e79c8bb2ef24f468eec23b53e73a is no longer possible
to install php7.3-fmp package with alternative inits when elogind is installed.
For example for me it forces removal of elogind and switch to systemd (from 
runit-init):

# apt-get install php7.3-fpm
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  daemon libapache2-mod-php7.3 libnss-systemd libpam-systemd libsystemd0 
php7.3-cgi php7.3-cli php7.3-common
  php7.3-curl php7.3-gd php7.3-intl php7.3-json php7.3-mbstring php7.3-mysql 
php7.3-opcache php7.3-readline
  php7.3-soap php7.3-sqlite3 php7.3-xml php7.3-xmlrpc systemd systemd-sysv
Suggested packages:
  php-pear systemd-container
The following packages will be REMOVED:
  elogind elogind-run libelogind-dev libelogind0 libpam-elogind 
libpam-elogind-compat runit-init
The following NEW packages will be installed:
  daemon libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv
The following packages will be upgraded:
  libapache2-mod-php7.3 php7.3-cgi php7.3-cli php7.3-common php7.3-curl 
php7.3-fpm php7.3-gd php7.3-intl
  php7.3-json php7.3-mbstring php7.3-mysql php7.3-opcache php7.3-readline 
php7.3-soap php7.3-sqlite3 php7.3-xml
  php7.3-xmlrpc
17 upgraded, 6 newly installed, 7 to remove and 22 not upgraded.
Need to get 12.6 MB of archives.
After this operation, 13.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

Please consider to add support for alternative inits using opentmpfiles.
Note also that opentmpfiles will work on non-linux ports so this patch 
will probably help with #951803 too.
Patch is attached, I can make a MR on salsa if you prefer

Best Regards,
Lorenzo

-- Package-specific info:
 Additional PHP 7.3 information 

 PHP 7.3 SAPI (php7.3query -S): 

 PHP 7.3 Extensions (php7.3query -M -v): 

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = -1
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[imap]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect 

Bug#951803: marked as done (php7.3: FTBFS on !linux archs)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #951803,
regarding php7.3: FTBFS on !linux archs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.15-1
Severity: important
Tags: patch

Hi,

php7.3 does not compile anymore on non-Linux architectures.
The issue is the systemd integration unconditionally enabled, as
obviously does not work on non-Linux architectures (as systemd is
specific to Linux).

The fix is to enable the systemd integration only on Linux; patch
attached for it.

Thanks,
-- 
Pino
--- a/debian/rules
+++ b/debian/rules
@@ -128,6 +128,10 @@ else
   CONFIGURE_DTRACE_ARGS := --disable-dtrace
 endif
 
+ifeq ($(DEB_HOST_ARCH_OS),linux)
+  CONFIGURE_SYSTEMD := --with-fpm-systemd
+endif
+
 # specify some options to our patch system
 QUILT_DIFF_OPTS := -p
 QUILT_NO_DIFF_TIMESTAMPS := 1
@@ -237,7 +241,7 @@ export fpm_config = \

--with-config-file-scan-dir=/etc/php/$(PHP_NAME_VERSION)/fpm/conf.d \
$(COMMON_CONFIG) \
--with-libevent-dir=/usr \
-   --with-fpm-systemd
+   $(CONFIGURE_SYSTEMD)
 
 export phpdbg_config = \
--prefix=/usr --enable-phpdbg --enable-cli --disable-cgi \
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#711520: marked as done (php7.3: Apache module has non-standard name)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #711520,
regarding php7.3: Apache module has non-standard name
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
711520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.10.4
Severity: normal

Hi,

On libapache2-mod-php5_5.5.0~rc2+dfsg-2_amd64.deb I get:
W: libapache2-mod-php5: non-standard-apache2-module-package-name 
libapache2-mod-php5 != libapache2-libphp5
E: libapache2-mod-php5: apache2-module-does-not-ship-load-file libphp5

However, the suggested 'libapache2-libphp5' is not in the expected module
naming scheme at all.

Perhaps this happens because the shipped module is
./usr/lib/apache2/modules/libphp5.so and Lintian wrongly uses this to
construct an expected package name.

The second test seems to suffer from the same problem: we do ship the module
file, the test makes a wrong assumption about its name.


Cheers,
Thijs

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lintian depends on:
ii  binutils   2.22-8
ii  bzip2  1.0.6-4
ii  diffstat   1.55-3
ii  file   5.11-2
ii  gettext0.18.1.1-9
ii  hardening-includes 2.2
ii  intltool-debian0.35.0+20060710.1
ii  libapt-pkg-perl0.1.26+b1
ii  libarchive-zip-perl1.30-6
ii  libc-bin   2.13-38
ii  libclass-accessor-perl 0.34-1
ii  libclone-perl  0.31-1+b2
ii  libdigest-sha-perl 5.71-2
ii  libdpkg-perl   1.16.10
ii  libemail-valid-perl0.190-1
ii  libipc-run-perl0.92-1
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtimedate-perl   1.2000-1
ii  liburi-perl1.60-1
ii  locales2.13-38
ii  locales-all [locales]  2.13-38
ii  man-db 2.6.2-1
ii  patchutils 0.3.2-1.1
ii  perl [libdigest-sha-perl]  5.14.2-21

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.16.10
ii  libhtml-parser-perl3.69-2
pn  libperlio-gzip-perl
ii  libtext-template-perl  1.45-2
ii  lzma   9.22-2
ii  man-db 2.6.2-1
ii  xz-utils [lzma]5.1.1alpha+20120614-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#954767: marked as done (RM: bali-phy [mipsel] -- ROM; Timeout when building on mipsel is blocking testing migration)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:53:46 +
with message-id 
and subject line Bug#954767: Removed package(s) from unstable
has caused the Debian Bug report #954767,
regarding RM: bali-phy [mipsel] -- ROM; Timeout when building on mipsel is 
blocking testing migration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Hi,

please remove bali-phy for mipsel from testing.  Currently the build
time test suite has a timeout error.  We might consider to exclude
mipsel from the list of architectures but may be this is just a
temporary issue so its possibly better with just removing the outdated
mipsel build for the moment.

Kind regards

  Andreas.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  bali-phy | 3.4.1+dfsg-2 | mipsel

--- Reason ---
ROM; Timeout when building on mipsel is blocking testing migration
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/954767

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#929631: marked as done (Could session.gc_probability being non-default be documented better ?)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #929631,
regarding Could session.gc_probability being non-default be documented better ?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
929631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.4-2
Severity: minor

Hi,
I found the a somewhat lingering bug in Ubuntu which just as much
applies to Debian.
Hence I thought the best would be to forward that to you so that we
can go the same route on handling it.

The behavior is quite old since
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595706
I have found quite some refs, but not one directly asking for that yet
that would be solved.
I mean https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831752 is the
same bug, but closed for 7.0 being removed.

I didn't want to revive old bugs on my own, but obviously feel free to
close this and reassing the old one if you prefer that. Just let me
know so I can follow.

## From here on I'm quoting the original bug that Ubuntu got ##

The Ubuntu distribution of PHP doesn't use the usual PHP mechanism of
session garbage collection. It sets "session.gc_probability" to zero
in the php.ini file, thus making it seem like garbage collection is
disabled. In fact it still occurs but with a cron job.

In my Docker image, the PHP "sessionclean" program is being executed
and it seems that this uses the "session.gc_maxlifetime" setting from
the apache2 version of the php.ini file. However this is non-obvious
and not documented in the php.ini file. Thus when recently rebuilding
my Docker image for my web service, I started getting what seemed to
be premature session timeouts and I couldn't figure out why and I
ended up raising a bug on the PHP team
(https://bugs.php.net/bug.php?id=76368).

If the Ubuntu team is going to modify the PHP package so it differs in
behaviour from the description in the PHP provided documentation, then
they need to provide updated documentation.

I would suggest that the simplest solution is to update the php.ini
file so that where "session.gc_probability" is set to zero there is a
short paragraph saying why (because it is handled by the cron job) and
also make it clear somewhere in that file that the
"session.gc_maxlifetime" setting is still relevant even though
"session.gc_probability" is zero.
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#946211: marked as done (php7.3-fpm: does not depend on used procps)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #946211,
regarding php7.3-fpm: does not depend on used procps
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
946211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-fpm
Severity: minor

php7.3-fpm.service uses /bin/kill but the package doesn't depend on procps.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'oldstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php7.3-fpm depends on:
ii  libapparmor12.13.3-7
ii  libargon2-1 0~20171227-0.2
ii  libc6   2.29-3
ii  libmagic1   1:5.37-6
ii  libpcre2-8-010.34-3+b1
ii  libsodium23 1.0.18-1
ii  libssl1.1   1.1.1d-2
ii  libsystemd0 244-3
ii  libxml2 2.9.4+dfsg1-8
ii  mime-support3.64
pn  php7.3-cli  
pn  php7.3-common   
pn  php7.3-json 
pn  php7.3-opcache  
ii  tzdata  2019c-3
ii  ucf 3.0038+nmu1
ii  zlib1g  1:1.2.11.dfsg-1+b1

php7.3-fpm recommends no packages.

Versions of packages php7.3-fpm suggests:
pn  php-pear  
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#919703: marked as done (php7.3: sodium_crypto_pwhash() Causes Error)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #919703,
regarding php7.3: sodium_crypto_pwhash() Causes Error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
919703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3
Version: 7.3.0-2
Severity: normal

Dear Maintainer,

Attempting to use sodium_crypto_pwhash is triggering a (non-informative) error 
from libsodium. The proximate cause appears to be the final argument. I can 
trigger the error with the following line in an interactive PHP shell:

php > echo base64_encode(sodium_crypto_pwhash(32, 'test', 
random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), 
SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, 
SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_ALG_ARGON2I13));
PHP Warning:  Uncaught SodiumException: internal error in php shell code:1
Stack trace:
#0 php shell code(1): sodium_crypto_pwhash()
#1 {main}
  thrown in php shell code on line 1

What I expect to see is 32 bytes of essentially random data base64-encoded.

I am able to get output without an error by executing either of the follwing 
statements:

echo base64_encode(sodium_crypto_pwhash(32, 'test', 
random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), 
SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, 
SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE));
echo base64_encode(sodium_crypto_pwhash(32, 'test', 
random_bytes(SODIUM_CRYPTO_PWHASH_SALTBYTES), 
SODIUM_CRYPTO_PWHASH_OPSLIMIT_INTERACTIVE, 
SODIUM_CRYPTO_PWHASH_MEMLIMIT_INTERACTIVE, SODIUM_CRYPTO_PWHASH_ALG_DEFAULT));

Curiously, the default algorithm right now is supposed to be 
SODIUM_CRYPTO_PWHASH_ALG_ARGON2I13, so it must be something in how this is 
mapped to the algorithm when passed on to libsodium.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php7.3 depends on:
pn  libapache2-mod-php7.3 | php7.3-fpm | php7.3-cgi  
pn  php7.3-common

php7.3 recommends no packages.

php7.3 suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#932886: marked as done (libapache2-mod-php7.3: fails to switch to locale when calling php setlocale())

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #932886,
regarding libapache2-mod-php7.3: fails to switch to locale when calling php 
setlocale()
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
932886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-php7.3
Version: 7.3.4-2
Severity: important

Dear Maintainer,

Setup:

I have two hosts, one up-to-date Debian Stretch with PHP 7.0, the other 
up-to-date Debian Buster with PHP 7.3. Both have (near to) identical 
configuration of PHP, Apache and locales.

Problem:

When running the following php script on 7.3 within a browser the setlocale() 
line does not seem to take effect:



On PHP 7.3 within the browser the output is not translated. It does however 
work as expected when run on the CLI. On Debian Stretch it works appropriately 
on both the browser and cli.

$ locale -a
C
C.UTF-8
dutch
en_US.utf8
nl_NL
nl_NL.iso88591
nl_NL.utf8
POSIX

$ cat /etc/default/locale 
#  File generated by update-locale
LANG="en_US.UTF-8"
LANGUAGE="en_US:en"

$ cat /etc/apache2/mods-enabled/mpm_*
LoadModule mpm_itk_module /usr/lib/apache2/modules/mpm_itk.so

StartServers 5
MinSpareServers   5
MaxSpareServers  10
MaxRequestWorkers 150
MaxConnectionsPerChild   0

LoadModule mpm_prefork_module /usr/lib/apache2/modules/mod_mpm_prefork.so


-- Package-specific info:
 Additional PHP 7.3 information 

 PHP 7.3 SAPI (php7.3query -S): 

 PHP 7.3 Extensions (php7.3query -M -v): 

 Configuration files: 
[PHP]
engine = On
short_open_tag = On
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = -1
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 360
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
html_errors = On
error_log = php_errors.log
arg_separator.input = ";&"
variables_order = "EGPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 33M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 32M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
date.timezone = "Europe/Amsterdam"
[filter]
[iconv]
[imap]
[intl]
[sqlite3]
sqlite3.defensive = 1
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = On
[ODBC]
odbc.allow_persistent = Off
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = Off
mysqli.max_links = -1
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[mysqlnd]
mysqlnd.collect_statistics = On
mysqlnd.collect_memory_statistics = Off
[OCI8]
[PostgreSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[bcmath]
bcmath.scale = 0
[browscap]
[Session]
session.save_handler = files
session.save_path = "/shared/tmp/php7.3"
session.use_strict_mode = 0
session.use_cookies = 1
session.use_only_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =

Bug#914723: marked as done (logrotate_script: /usr/lib/php/php7.2-fpm-reopenlogs: not found)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #914723,
regarding logrotate_script: /usr/lib/php/php7.2-fpm-reopenlogs: not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
914723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-fpm
Version: 7.3.0~rc4-1
Severity: normal

Dear Maintainer,

After removing php-fpm.. I suspect the issue is present in 7.3 too.
Perhaps it should check whether the binary is still available.

Gr,

Olaf

logrotate_script: 2: logrotate_script: /usr/lib/php/php5.6-fpm-reopenlogs: not 
found
error: error running non-shared postrotate script for /var/log/php5.6-fpm.log 
of '/var/log/php5.6-fpm.log '
logrotate_script: 2: logrotate_script: /usr/lib/php/php7.2-fpm-reopenlogs: not 
found
error: error running non-shared postrotate script for /var/log/php7.2-fpm.log 
of '/var/log/php7.2-fpm.log '

Gr,

Olaf

-- Package-specific info:
 Additional PHP 7.3 information 

 PHP 7.3 SAPI (php7.3query -S): 

 PHP 7.3 Extensions (php7.3query -M -v): 

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = -1
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[mysqlnd]
mysqlnd.collect_statistics = On
mysqlnd.collect_memory_statistics = Off
[OCI8]
[PostgreSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[bcmath]
bcmath.scale = 0
[browscap]
[Session]
session.save_handler = files
session.use_strict_mode = 0
session.use_cookies = 1
session.use_only_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =
session.cookie_httponly =
session.cookie_samesite =
session.serialize_handler = php
session.gc_probability = 0
session.gc_divisor = 1000
session.gc_maxlifetime = 1440
session.referer_check =
session.cache_limiter = nocache
session.cache_expire = 180
session.use_trans_sid = 0
session.sid_length = 26
session.trans_sid_tags = "a=href,area=href,frame=src,form="
session.sid_bits_per_character = 5
[Assertion]
zend.assertions = -1
[COM]
[mbstring]
[gd]
[exif]
[Tidy]
tidy.clean_output = Off
[soap]
soap.wsdl_cache_enabled=1
soap.wsdl_cache_dir="/tmp"
soap.wsdl_cache_ttl=86400
soap.wsdl_cache_limit = 5
[sysvshm]
[ldap]
ldap.max_links = -1
[dba]
[opcache]
[curl]
[openssl]

 

Bug#954779: marked as done (RM: php7.3 -- ROM; Superseded by PHP 7.4)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:15 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #954779,
regarding RM: php7.3 -- ROM; Superseded by PHP 7.4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

please remove PHP 7.3 from archive as it has been superseded by PHP 7.4.

Thank you,
Ondrej

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl54n5ZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJ6jQ//VyQYP8/R3vcWHnyT5ExH5VUtJv9uppuX17Os/0WtNwQIAogKOhdOkNSc
IGq60CG9QHsAinlDzhA/ylelv1TxoGz3L37KR178zg8/XDB/IKkSCGIi3xljAutH
Qg8PG0u926gXHsRvYpmURVSupLdH4cvqjxx47Z8c9iRxvXicdECZ1j3QnWV8aye0
URAIBVPkDrkEcC3C4mofR1GjC+71A/+Sv07Bv2Q8U/f0RdlUT69TpRCOaJUJ8I0g
PXLpOwzAmihZ5QuLKl6hDUin8vSBXgy/OFaWRmQth8LtkLkHzEakg14HeTLszNZR
ORbOY5qDSQdHLrdyTLCqc2EjFFW5+Cfo0NHOjcvUFgAzzHhzt6m8W0dblbMFCJFB
8g9DT8DOk6c61JvpAZG5XL1MMIS441n7Tp2a2C9stBdgHUufhKJMeECz6lmN2eqI
LLA8vJGQZxAK40gMJfTh8vBDQHmvBlWafPUNjujRB5NivoOHSOGpjsNgAkXccfii
FNSzx4G6KBThS0K5LidxYNOwjUCYERLNyGYkHMA++ksIdIfyfSSx9o24DFBcXzdA
85Qz5H4e4PLqvzvT4WLxMuwskaXpIjb9i+Ng2FAWIAqYLoBcchE/EbPo0p9gDl1J
9jrtl1/JB8oRIE+Y47wpBxs1qanKwtEpY5nNekc6M3mrntJXjLc=
=K1ov
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libapache2-mod-php7.3 |   7.3.15-3 | amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
libphp7.3-embed |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3 |   7.3.15-3 | source, all
php7.3-bcmath |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-bz2 |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-cgi |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-cli |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-common |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-curl |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-dba |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-dev |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-enchant |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-fpm |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
 php7.3-gd |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-gmp |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-imap |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-interbase |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-intl |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-json |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-ldap |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-mbstring |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-mysql |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-odbc |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-opcache |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-pgsql |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-phpdbg |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-pspell |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-readline |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-recode |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
php7.3-snmp |   7.3.15-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
php7.3-soap |   7.3.15-3 | amd64, arm64, armel, 

Bug#937404: marked as done (pycha: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:53:13 +
with message-id 
and subject line Bug#954752: Removed package(s) from unstable
has caused the Debian Bug report #937404,
regarding pycha: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
937404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycha
Version: 0.7.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pycha

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.7.0-2+rm

Dear submitter,

as the package pycha has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954752

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#948923: marked as done (php7.3 FTCBFS: autoconf issues)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #948923,
regarding php7.3 FTCBFS: autoconf issues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.12-1
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

php7.3 fails to cross build from source. The immediate failure stems
from using the build architecture pkg-config. Once doing so, it fails
finding required dependencies that are only installed for the host
architecture. This is a very common problem and the fix is very simple:
Use AC_PATH_TOOL instead of AC_PATH_PROG for finding pkg-config. Then
there is a non-failure, but one that struck my eyes anyway: In addition
to using AC_CHECK_SIZEOF, php also has its own PHP_CHECK_SIZEOF.
Unfortunately, it got cross compilation completely wrong. I'm attaching
a patch that fixes the pkg-config issue and changes PHP_CHECK_SIZEOF to
use AC_CHECK_SIZEOF underneath while retaining the additional headers.
The patch should be suitable for upstream inclusion in my view. It does
not make php7.3 cross buildable though. At some point, it fails running
the cross built php for generating "phar.php". This problem doesn't seem
to be new[1], but I don't particularly like the suggested workarounds.
So I'm only reporting the well-understood aspects here. Please close
this bug anyhow when fixing the pkg-config and sizeof aspects.

Helmut

[1] https://stackoverflow.com/questions/6559480/cross-compiling-php
--- php7.3-7.3.12.orig/acinclude.m4
+++ php7.3-7.3.12/acinclude.m4
@@ -1059,7 +1059,7 @@
 LIBS=
 old_LDFLAGS=$LDFLAGS
 LDFLAGS=
-AC_RUN_IFELSE([AC_LANG_SOURCE([[#include 
+AC_CHECK_SIZEOF([$1],[$2],[
 #if STDC_HEADERS
 #include 
 #include 
@@ -1071,21 +1071,8 @@
 #include 
 #endif
 $3
-
-int main()
-{
-	FILE *fp = fopen("conftestval", "w");
-	if (!fp) return(1);
-	fprintf(fp, "%d\n", sizeof($1));
-	return(0);
-}
-  ]])], [
-eval $php_cache_value=`cat conftestval`
-  ], [
-eval $php_cache_value=0
-  ], [
-ifelse([$2],,[eval $php_cache_value=0], [eval $php_cache_value=$2])
 ])
+eval $php_cache_value=\$AS_TR_SH([ac_cv_sizeof_$1])
   LDFLAGS=$old_LDFLAGS
   LIBS=$old_LIBS
 ])
@@ -2178,7 +2165,7 @@
 
   dnl First try to find pkg-config
   if test -z "$PKG_CONFIG"; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   dnl If pkg-config is found try using it
@@ -2337,7 +2324,7 @@
 
   dnl First try to find pkg-config
   if test -z "$PKG_CONFIG"; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   dnl If pkg-config is found try using it
@@ -2570,7 +2557,7 @@
   dnl If xml2-config fails, try pkg-config
   if test "$found_libxml" = "no"; then
 if test -z "$PKG_CONFIG"; then
-  AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+  AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
 fi
 
 dnl If pkg-config is found try using it
--- php7.3-7.3.12.orig/aclocal.m4
+++ php7.3-7.3.12/aclocal.m4
@@ -2176,7 +2176,7 @@
 
   dnl First try to find pkg-config
   if test -z "$PKG_CONFIG"; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   dnl If pkg-config is found try using it
@@ -2335,7 +2335,7 @@
 
   dnl First try to find pkg-config
   if test -z "$PKG_CONFIG"; then
-AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
   fi
 
   dnl If pkg-config is found try using it
@@ -2570,7 +2570,7 @@
   dnl If xml2-config fails, try pkg-config
   if test "$found_libxml" = "no"; then
 if test -z "$PKG_CONFIG"; then
-  AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+  AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
 fi
 
 dnl If pkg-config is found try using it
--- php7.3-7.3.12.orig/ext/odbc/config.m4
+++ php7.3-7.3.12/ext/odbc/config.m4
@@ -319,7 +319,7 @@
   AC_MSG_CHECKING(for iODBC support)
   if test "$PHP_IODBC" != "no"; then
 if test -z "$PKG_CONFIG"; then
-  AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
+  AC_PATH_TOOL(PKG_CONFIG, pkg-config, no)
 fi
 if test -x "$PKG_CONFIG" && $PKG_CONFIG --exists libiodbc ; then
   PHP_ADD_LIBRARY_WITH_PATH(iodbc, $PHP_IODBC/$PHP_LIBDIR)
--- php7.3-7.3.12.orig/sapi/fpm/config.m4
+++ php7.3-7.3.12/sapi/fpm/config.m4
@@ -582,7 +582,7 @@
 
   if test 

Bug#885468: marked as done (pycha: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:53:13 +
with message-id 
and subject line Bug#954752: Removed package(s) from unstable
has caused the Debian Bug report #885468,
regarding pycha: Depends on unmaintained pygtk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
885468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycha
Version: 0.7.0-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.7.0-2+rm

Dear submitter,

as the package pycha has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954752

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#922309: marked as done (php7.3: please set timezone in php.ini files to the system's timezone)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #922309,
regarding php7.3: please set timezone in php.ini files to the system's timezone
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
922309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.3
Version: 7.3.2-3
Severity: normal
Control: affects -1 cacti

Hi,

As maintainer of the Cacti package I have been asked by my upstream
developers to make sure that the timezone is set. I explained to them
that I can't do that in my package as the PHP configuration is off
limits. If I understand the situation correctly (I am not very
knowledgeable on PHP) there are multiple functions in PHP nowadays that
also complain if the timezone isn't set.

Instead of requiring every admin to set the timezone, couldn't the
Debian package set the timezone during initial installation to the same
timezone as the system has, as a default?

See for more background the upstream issue where this appeared:
https://github.com/Cacti/cacti/issues/2331

Paul



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#945526: marked as done (php7.3-mbstring uses an embedded copy of libonig)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #945526,
regarding php7.3-mbstring uses an embedded copy of libonig
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
945526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-mbstring
Version: 7.3.11-1~deb10u1
Severity: important
Tags: security

Hi,

While working on recent libonig vulnerabilities, I noticed that PHP does not 
link it anymore, despite using it as a build-dependency:
$ ldd /usr/lib/php/20180731/mbstring.so 
linux-vdso.so.1 (0x7ffe463ed000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a84ef1000)
/lib64/ld-linux-x86-64.so.2 (0x7f5a8527)

AFAICS the package uses the embedded copy from ext/mbstring/oniguruma/ ; using 
Debian's version would involve passing --with-onig=DIR to the configure script.

It seems this was introduced during a refactoring for 7.0.0-rc1-1
https://lists.debian.org/debian-security/2019/11/msg00020.html

See https://wiki.debian.org/EmbeddedCodeCopies for further information.

Cheers!
Sylvain

--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#930039: marked as done (cannot allocate memory in static TLS block)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #930039,
regarding cannot allocate memory in static TLS block
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgomp1
Version: 8.3.0-6
Severity: important

Hi!

I don't really know if libgcomp1 is the one to blame here, but when using
PHP based software lige nextcloud on top of Buster I'm seing this error:

PHP Startup: Unable to load dynamic library 'imagick.so' (tried: 
/usr/lib/php/20180731/imagick.so (/lib/aarch64-linux-gnu/libgomp.so.1: cannot 
allocate memory in static TLS block), /usr/lib/php/20180731/imagick.so.so 
(/usr/lib/php/20180731/imagick.so.so: cannot open shared object file: No such 
file or directory)) at Unknown#0

Which seems to point to libgomp1, I have tried the versions on unstable (-7)
without changes.

I don't know what else to add here but if you want me to do any tests,
please don't hesitate to ask.

Regards.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 4.19.0-5-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=gl_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgomp1 depends on:
ii  gcc-8-base  8.3.0-6
ii  libc6   2.28-10

libgomp1 recommends no packages.

libgomp1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#914699: marked as done (php7.3-fpm.conf)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #914699,
regarding php7.3-fpm.conf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
914699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-fpm
Version: 7.3.0~rc5-2
Severity: normal

Dear Maintainer,

Some questions about this file.

> # Deny access to raw php sources by default

Shouldn't this cover phar and phtml as well?
What does this cover? A failure of the handler?

Cause if proxy_fcgi_module or this conf file aren't present, like after just 
installing apache2, .php files are server raw as-is.

> 

Is this different from ".\.phps$"?

And why the special case for files without basename?

Gr,

Olaf


# Redirect to local php-fpm if mod_php is not available


# Enable http authorization headers

SetEnvIfNoCase ^Authorization$ "(.+)" HTTP_AUTHORIZATION=$1



SetHandler "proxy:unix:/run/php/php7.3-fpm.sock|fcgi://localhost"


# Deny access to raw php sources by default
# To re-enable it's recommended to enable access to the files
# only in specific virtual host or directory
Require all denied

# Deny access to files without filename (e.g. '.php')

Require all denied




-- Package-specific info:
 Additional PHP 7.3 information 

 PHP 7.3 SAPI (php7.3query -S): 

 PHP 7.3 Extensions (php7.3query -M -v): 

 Configuration files: 
[PHP]
engine = On
short_open_tag = Off
precision = 14
output_buffering = 4096
zlib.output_compression = Off
implicit_flush = Off
unserialize_callback_func =
serialize_precision = -1
disable_functions = 
pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
disable_classes =
zend.enable_gc = On
expose_php = Off
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = Off
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
html_errors = On
variables_order = "GPCS"
request_order = "GP"
register_argc_argv = Off
auto_globals_jit = On
post_max_size = 8M
auto_prepend_file =
auto_append_file =
default_mimetype = "text/html"
default_charset = "UTF-8"
doc_root =
user_dir =
enable_dl = Off
file_uploads = On
upload_max_filesize = 2M
max_file_uploads = 20
allow_url_fopen = On
allow_url_include = Off
default_socket_timeout = 60
[CLI Server]
cli_server.color = On
[Date]
[filter]
[iconv]
[intl]
[sqlite3]
[Pcre]
[Pdo]
[Pdo_mysql]
pdo_mysql.default_socket=
[Phar]
[mail function]
SMTP = localhost
smtp_port = 25
mail.add_x_header = Off
[ODBC]
odbc.allow_persistent = On
odbc.check_persistent = On
odbc.max_persistent = -1
odbc.max_links = -1
odbc.defaultlrl = 4096
odbc.defaultbinmode = 1
[Interbase]
ibase.allow_persistent = 1
ibase.max_persistent = -1
ibase.max_links = -1
ibase.timestampformat = "%Y-%m-%d %H:%M:%S"
ibase.dateformat = "%Y-%m-%d"
ibase.timeformat = "%H:%M:%S"
[MySQLi]
mysqli.max_persistent = -1
mysqli.allow_persistent = On
mysqli.max_links = -1
mysqli.default_port = 3306
mysqli.default_socket =
mysqli.default_host =
mysqli.default_user =
mysqli.default_pw =
mysqli.reconnect = Off
[mysqlnd]
mysqlnd.collect_statistics = On
mysqlnd.collect_memory_statistics = Off
[OCI8]
[PostgreSQL]
pgsql.allow_persistent = On
pgsql.auto_reset_persistent = Off
pgsql.max_persistent = -1
pgsql.max_links = -1
pgsql.ignore_notice = 0
pgsql.log_notice = 0
[bcmath]
bcmath.scale = 0
[browscap]
[Session]
session.save_handler = files
session.use_strict_mode = 0
session.use_cookies = 1
session.use_only_cookies = 1
session.name = PHPSESSID
session.auto_start = 0
session.cookie_lifetime = 0
session.cookie_path = /
session.cookie_domain =
session.cookie_httponly =
session.cookie_samesite =
session.serialize_handler = php
session.gc_probability = 0
session.gc_divisor = 1000
session.gc_maxlifetime = 1440
session.referer_check =
session.cache_limiter = nocache
session.cache_expire = 180
session.use_trans_sid = 0
session.sid_length = 26

Bug#927284: marked as done (argon2 build dependency not quite correct)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #927284,
regarding argon2 build dependency not quite correct
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
927284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php7.3
Version: 7.3.3-1
Severity: minor


While trying to backport php7.3 to stretch, I noticed that php won't build with 
the stretch version of libargon2

Current build dependency is:
libargon2-dev | libargon2-0-dev

This needs changing to
libargon2-dev



libargon2-dev - buster. Works.  Not in stretch.
libargon2-0-dev - stretch (doesn't build) Virtual in buster.



 
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#918743: marked as done (php-fpm.conf: Shouldn't pass URLs for missing files to PHP-FPM)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #918743,
regarding php-fpm.conf: Shouldn't pass URLs for missing files to PHP-FPM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
918743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-fpm
Version: 7.3.0-2
Severity: minor
Tags: patch

Dear Maintainer,

The current behavior of php-fpm.conf is to pass URLs for files which
match ".+\.ph(ar|p|tml)$" to PHP-FPM regardless of whether the file
exists.  This causes a few issues:

- It prevents Apache error handling (e.g. ErrorDocument).
- It adds unnecessary load to PHP-FPM.
- It adds unnecessary request overhead for the request.
- It causes "AH01071: Got error 'Primary script unknown'" to be logged
  to the Apache error log for each request.

This can be avoided by using an  directive around SetHandler, as
done on the PHP-FPM page on the Apache Wiki.[1]  I have attached a patch
which does this.

Thanks for considering,
Kevin

1.  https://wiki.apache.org/httpd/PHP-FPM


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.20.0 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php7.3-fpm depends on:
ii  libapparmor12.13.2-3
ii  libargon2-1 0~20171227-0.1
ii  libc6   2.28-2
ii  libmagic1   1:5.34-2
ii  libpcre2-8-010.32-3
ii  libsodium23 1.0.16-2
ii  libssl1.1   1.1.1a-1
ii  libsystemd0 240-2
ii  libxml2 2.9.4+dfsg1-7+b3
ii  mime-support3.61
ii  php7.3-cli  7.3.0-2
ii  php7.3-common   7.3.0-2
ii  php7.3-json 7.3.0-2
ii  php7.3-opcache  7.3.0-2
ii  tzdata  2018i-1
ii  ucf 3.0038+nmu1
ii  zlib1g  1:1.2.11.dfsg-1

php7.3-fpm recommends no packages.

Versions of packages php7.3-fpm suggests:
ii  php-pear  1:1.10.6+submodules+notgz-1

Versions of packages php7.3-common depends on:
ii  libc6   2.28-2
ii  libssl1.1   1.1.1a-1
ii  php-common  2:69
ii  ucf 3.0038+nmu1

-- Configuration Files:
/etc/apache2/conf-available/php7.3-fpm.conf changed [not included]

-- no debconf information
>From 2d80e7bd564cce570b8725614e3b73ccd8b74a11 Mon Sep 17 00:00:00 2001
Message-Id: 
<2d80e7bd564cce570b8725614e3b73ccd8b74a11.1546987306.git.ke...@kevinlocke.name>
From: Kevin Locke 
Date: Tue, 8 Jan 2019 15:32:19 -0700
Subject: [PATCH] Don't pass URLs for missing files to PHP-FPM

When there is no file matching a request URL ending in a matched PHP
extension, passing it to PHP-FPM doesn't make sense.  It adds
unnecessary PHP-FPM load and request overhead, prevents Apache error
handling (e.g.  ErrorDocument), and causes `AH01071: Got error 'Primary
script unknown'` to be logged.

Avoid this by using an  directive to only configure SetHandler if
the requested file exists, as documented on [PHP-FPM] on the Apache
Wiki.

[PHP-FPM]: https://wiki.apache.org/httpd/PHP-FPM

Signed-off-by: Kevin Locke 
---
 debian/php-fpm.conf | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/php-fpm.conf b/debian/php-fpm.conf
index 3fc2f80c0..1d78fbb48 100644
--- a/debian/php-fpm.conf
+++ b/debian/php-fpm.conf
@@ -7,7 +7,9 @@
 
 
 
-SetHandler 
"proxy:unix:/run/php/php@php_vers...@-fpm.sock|fcgi://localhost"
+
+SetHandler 
"proxy:unix:/run/php/php@php_vers...@-fpm.sock|fcgi://localhost"
+
 
 
 # Deny access to raw php sources by default
-- 
2.20.1

--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the 

Bug#910400: marked as done (mysqli stopped connecting to MySQL servers using caching_sha2_password)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #910400,
regarding mysqli stopped connecting to MySQL servers using caching_sha2_password
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
910400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: php7.3-mysql
Version: 7.3.0~rc2-2
Severity: grave

After update to 7.3.0~rc2-2 (sid), mysqli extension stopped working. It 
can't connect to MySQL server, giving the following error message:


PHP message: PHP Warning:  mysqli::__construct(): The server requested 
authentication method unknown to the client [caching_sha2_password]


It worked before the update (version 7.3.0~alpha3-1, I think).

caching_sha2_password is the default authentication method in MySQL 8.0.
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#949856: marked as done (Warnings upon purge about problems that are cleaned up anyway at the end)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 03:54:36 +
with message-id 
and subject line Bug#954779: Removed package(s) from unstable
has caused the Debian Bug report #949856,
regarding Warnings upon purge about problems that are cleaned up anyway at the 
end
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
949856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.3-common
Severity: minor
Version: 7.3.12-1

Here the user gets warnings,
but when he checks, the stuff warned about is already gone.

So maybe something should be done so the "spurious warnings" are never
shown to the user.

# aptitude purge php~i
The following packages will be REMOVED:
  php-cli{p}  php-common{p}  php-json{p}  php7.3-cli{p}  php7.3-common{p}  
php7.3-json{p}  php7.3-opcache{p}  php7.3-readline{p}
0 packages upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 12.7 MB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 167262 files and directories currently installed.)
Removing php-cli (2:7.3+69) ...
Removing php7.3-cli (7.3.12-1) ...
Removing php7.3-readline (7.3.12-1) ...
Removing php7.3-opcache (7.3.12-1) ...
Removing php-json (2:7.3+69) ...
Removing php7.3-json (7.3.12-1) ...
Removing php7.3-common (7.3.12-1) ...
Removing php-common (2:69) ...
Processing triggers for man-db (2.9.0-2) ...
(Reading database ... 167143 files and directories currently installed.)
Purging configuration files for php-common (2:69) ...
Purging configuration files for php7.3-json (7.3.12-1) ...
Purging configuration files for php7.3-readline (7.3.12-1) ...
Purging configuration files for php7.3-common (7.3.12-1) ...
dpkg: warning: while removing php7.3-common, directory 
'/etc/php/7.3/mods-available' not empty so not removed
Purging configuration files for php7.3-cli (7.3.12-1) ...
dpkg: warning: while removing php7.3-cli, directory '/etc/php/7.3' not empty so 
not removed
Purging configuration files for php7.3-opcache (7.3.12-1) ...
Current status: 0 (+0) broken, 0 (+0) upgradable, 18366 (+0) new.
# find /etc/php
find: ‘/etc/php’: No such file or directory
--- End Message ---
--- Begin Message ---
Version: 7.3.15-3+rm

Dear submitter,

as the package php7.3 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/954779

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#946441: marked as done (mirror submission for mirror.biznetgio.com)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 04:02:47 +0100
with message-id <20200324030247.gc750...@bongo.bofh.it>
and subject line Re: Bug#945529: mirror submission for mirror.biznetgio.com
has caused the Debian Bug report #946441,
regarding mirror submission for mirror.biznetgio.com
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
946441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirror.biznetgio.com
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Agik Agustono 
Country: ID Indonesia
Location: Jakarta
Sponsor: Biznet Gio Nusantara https://www.biznetgio.com
Comment: Hi Debian Support
 Please add my mirror in your list
 
 Thanks
 
 Agik




Trace Url: http://mirror.biznetgio.com/debian/project/trace/
Trace Url: 
http://mirror.biznetgio.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.biznetgio.com/debian/project/trace/mirror.biznetgio.com
--- End Message ---
--- Begin Message ---
Duplicate of #949928.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#945529: marked as done (mirror submission for mirror.biznetgio.com)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 04:02:47 +0100
with message-id <20200324030247.gc750...@bongo.bofh.it>
and subject line Re: Bug#945529: mirror submission for mirror.biznetgio.com
has caused the Debian Bug report #945529,
regarding mirror submission for mirror.biznetgio.com
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
945529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirror.biznetgio.com
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Agik Agustono 
Country: ID Indonesia
Location: Jakarta
Sponsor: PT. Biznet Gio Nusantara https://www.biznetgio.com




Trace Url: http://mirror.biznetgio.com/debian/project/trace/
Trace Url: 
http://mirror.biznetgio.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.biznetgio.com/debian/project/trace/mirror.biznetgio.com
--- End Message ---
--- Begin Message ---
Duplicate of #949928.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#807990: marked as done (allow users absent from users.oath to login)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 02:58:12 +
with message-id 
and subject line Bug#807990: fixed in oath-toolkit 2.6.1-1.4
has caused the Debian Bug report #807990,
regarding allow users absent from users.oath to login
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
807990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-oath
Version: 2.4.1-1
Severity: wishlist

Since only root can (and should) update /etc/users.oath, it's pretty
inconvenient to deploy pam-oath in any environment, as it
automatically kicks out any user using password authentication.

It would be good if there was an option in the pam module that would
allow authentication to succeed if the user is *not* present in the
users file.

Thanks!

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-oath depends on:
ii  libc6   2.19-18+deb8u1
ii  liboath02.4.1-1
ii  libpam-runtime  1.1.8-3.1
ii  libpam0g1.1.8-3.1

libpam-oath recommends no packages.

libpam-oath suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: oath-toolkit
Source-Version: 2.6.1-1.4
Done: =?utf-8?q?Antoine_Beaupr=C3=A9?= 

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated oath-toolkit 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 13 Mar 2020 20:30:26 -0400
Source: oath-toolkit
Architecture: source
Version: 2.6.1-1.4
Distribution: unstable
Urgency: medium
Maintainer: OATH Toolkit Team 
Changed-By: Antoine Beaupré 
Closes: 807990
Changes:
 oath-toolkit (2.6.1-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * patch: fail gracefully for missing users (Closes: #807990)
   * push to salsa
Checksums-Sha1:
 1882f71449d75aafc472fb4a52295a7d72b82bde 1893 oath-toolkit_2.6.1-1.4.dsc
 07c2e676de609666a0bb324c7f279965ec66c12c 21796 
oath-toolkit_2.6.1-1.4.debian.tar.xz
 d70b6514f4dbcd021fca19d7be726869cf25b135 10664 
oath-toolkit_2.6.1-1.4_amd64.buildinfo
Checksums-Sha256:
 163f17747428d4169d8657ef81b526bc0802d3555e2d110ab91569f017e02479 1893 
oath-toolkit_2.6.1-1.4.dsc
 212d1f10fb2ca849295c1a2c0f449ead9da9169f74ad2fc52979c4bf4b7eb0b7 21796 
oath-toolkit_2.6.1-1.4.debian.tar.xz
 5ddd1b0097ddccb8714ae544add772ef8652ab77a0735b35f6469fece25cc14a 10664 
oath-toolkit_2.6.1-1.4_amd64.buildinfo
Files:
 a9a1aa53b16472c0fd74001da6ed966e 1893 devel optional oath-toolkit_2.6.1-1.4.dsc
 939bd854393fb40ab2c97a3a71b01de4 21796 devel optional 
oath-toolkit_2.6.1-1.4.debian.tar.xz
 a7dde57fb1f1b2de0017abedb26597b4 10664 devel optional 
oath-toolkit_2.6.1-1.4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl5sNuMACgkQPqHd3bJh
2XtnZwf+PlwQTAmawVy8aLzApqunp0Z3Zkg0q0/zLs4XgHEiHS8cv/4XFHWywlmg
0cMZBHbzVUfBn8nN9V9P0KG+0JHYt5x8EeMtift/oSfpcDFCRqUBFFwAT8/Emcb8
3mWygpSPCuEphOgw3UPzW8WO65X6/kEbfnxweCJpMuLU6riEhKRhYQ6fd303N2Lm
yrLLgoKF4rIBmW6WFrNRIBigRSxo0lUFCFrutyH48Ddu5lDLjqXCWVWxaU3YxMBd
hBUKIjKJyE5iMVDBXB6ihGg0cSLMXGeGvA7tUzYqt5WfnH0V+u3N8QUxI7VF78ej
fjRJudPZM5xqj9l+F30Behd8zDuugQ==
=GamI
-END PGP SIGNATURE End Message ---

Bug#943097: marked as done (ghc: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 02:57:26 +
with message-id 
and subject line Bug#943097: fixed in ghc 8.8.1+dfsg1+is+8.6.5+dfsg1-3
has caused the Debian Bug report #943097,
regarding ghc: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
943097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghc
Version: 8.8.1+dfsg1+is+8.6.5+dfsg1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ghc
Source-Version: 8.8.1+dfsg1+is+8.6.5+dfsg1-3
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated ghc 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:50:31 -0400
Source: ghc
Architecture: source
Version: 8.8.1+dfsg1+is+8.6.5+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Sandro Tosi 
Closes: 943097
Changes:
 ghc (8.8.1+dfsg1+is+8.6.5+dfsg1-3) unstable; urgency=medium
 .
   * Switch to python3-sphinx; Closes: #943097
Checksums-Sha1:
 40563a14d2492fe1b142f8f317c668b08886e320 2477 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3.dsc
 435907f6fda477c07a122d35ea9c8b0fa7473b0a 54032 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3.debian.tar.xz
 1d0fe27a3d047fbd96690e0f80671da268bc80ca 13520 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3_amd64.buildinfo
Checksums-Sha256:
 b1ceebc7e15396f2ef8ef632e766516570d5782ef90c72eabbd47170a4a5263f 2477 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3.dsc
 44f7998ed9b2b8cca03f502f5d4132a40efcb1f2cfe9787d0aec6ac0d3b8cf05 54032 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3.debian.tar.xz
 8b2c988e2ba0456dd03deee1eb0e1a2b1e5da6ffe3b90411fa2a4b193a7268a5 13520 
ghc_8.8.1+dfsg1+is+8.6.5+dfsg1-3_amd64.buildinfo
Files:
 317f41c032af32bed9ba22fec4e38add 2477 haskell optional 

Bug#942565: marked as done (cross-toolchain-base-mipsen_8_all.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 01:49:27 +
with message-id 
and subject line Bug#942565: fixed in cross-toolchain-base-mipsen 10
has caused the Debian Bug report #942565,
regarding cross-toolchain-base-mipsen_8_all.changes REJECTED
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cross-toolchain-base-mipsen
Version: 8
Severity: serious

On 2019-10-18 01:35, Debian FTP Masters wrote:
> 
> libc6-dev-mips-cross_2.29-2cross1_all.deb: Built-Using refers to non-existing 
> source package linux (= 5.2.17-1+b1)
> 
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 

The Built-Using is wrongly using the binary version, the source version
(in that case 5.2.17-1) should be used instead.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- End Message ---
--- Begin Message ---
Source: cross-toolchain-base-mipsen
Source-Version: 10
Done: YunQiang Su 

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

Debian distribution maintenance software
pp.
YunQiang Su  (supplier of updated cross-toolchain-base-mipsen 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 19:44:30 +0800
Source: cross-toolchain-base-mipsen
Architecture: source
Version: 10
Distribution: unstable
Urgency: medium
Maintainer: Cross Toolchain Base Team 

Changed-By: YunQiang Su 
Closes: 942565
Changes:
 cross-toolchain-base-mipsen (10) unstable; urgency=medium
 .
   * Don't generate Build-Using linux with binNMU version tail. (Closes: 
#942565)
   * Build with glibc 2.30+ and binutils 2.34+.
Checksums-Sha1:
 a2ef75ae9ec4d10d522254d6ea5f31a024f08947 10646 
cross-toolchain-base-mipsen_10.dsc
 14f70ac9fff44d1a51f6c7a8af0eb47c599f3e80 42872 
cross-toolchain-base-mipsen_10.tar.xz
 ddb5cc8aa827c01cb263b7c30f8e4613f8c76e5a 11008 
cross-toolchain-base-mipsen_10_source.buildinfo
Checksums-Sha256:
 156d429041074214b0d5a33ab4077b04a942362f5e871565a5a28a6180cb07a5 10646 
cross-toolchain-base-mipsen_10.dsc
 4b4df45f5f8f36d119aaef6a36f260794d6e234540983f6a1e112cb73cc3de24 42872 
cross-toolchain-base-mipsen_10.tar.xz
 10d96e578e218d02770447db9d5f42f44f2d0edcfd8a4fd01fd5eb39f2235d6b 11008 
cross-toolchain-base-mipsen_10_source.buildinfo
Files:
 ce2ff6bf351b06a5757cd3a2da295e8f 10646 devel optional 
cross-toolchain-base-mipsen_10.dsc
 a59b0d099664c913b511b9850b209f8d 42872 devel optional 
cross-toolchain-base-mipsen_10.tar.xz
 933d9537169791a767dfe0b0c8673185 11008 devel optional 
cross-toolchain-base-mipsen_10_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCgAtFiEET3MbhxKET+7/a6zdW0gHVdEZ6o4FAl55Y88PHHN5cUBkZWJp
YW4ub3JnAAoJEFtIB1XRGeqOl7AIAIzf4X79+c/9BXC0lCWIag6FH868jG2bD4Jv
bN5ww9I42xi0x25uLiLdSmUQ1KzGU535Mv5lCwhp+7fpqVxMin2if8uGdBpuvKiE
B6HD87n73naXQo0y/LHPjoNg0ktAh9LIlnU6PMeLpFRHvFBpxl9foM69gPHdjrqu
MbOsV11IevKv8EOD3crf3hUkJ32UympTfkI1mECBh0Ututolq7YZNCAI0jjEIC1a
jiZ0vuRcLtLVgRBri2e4I1lxBnnVc2byeJDEoVxyuTWGN+2ad5gsWIZSdpuAA2Mq
Il7k5uTobLqpbiNDrxfADnGRgAwuUUTOP9KQP+nqRETVehbviiE=
=Yuyr
-END PGP SIGNATURE End Message ---

Bug#942981: marked as done (cwiid: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 00:49:22 +
with message-id 
and subject line Bug#936358: fixed in cwiid 0.6.00+svn201-5
has caused the Debian Bug report #936358,
regarding cwiid: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cwiid
Version: 0.6.00+svn201-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: cwiid
Source-Version: 0.6.00+svn201-5
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated cwiid 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:04:15 -0400
Source: cwiid
Architecture: source
Version: 0.6.00+svn201-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Scott Kitterman 
Closes: 936358
Changes:
 cwiid (0.6.00+svn201-5) unstable; urgency=medium
 .
   * QA upload.
   * Rip out python bindings (Closes: #936358)
 - Obsolete libs, python2 only which is being removed
 - Delete wmgui, wminput, and python-cwiid binaries
Checksums-Sha1:
 673c9d63f8c67884ccd7674b61c5e94a4202aee8 2028 cwiid_0.6.00+svn201-5.dsc
 770e4556bdbdb5a5cb6c195e4c56e123157b19b3 15992 
cwiid_0.6.00+svn201-5.debian.tar.xz
 cdd8f27edf5ae8e3c26a3995a6da305d6af2af40 10773 
cwiid_0.6.00+svn201-5_source.buildinfo
Checksums-Sha256:
 1fe1fe658c0c46f5855ee1975f5c9e43d1778a52bfc965e0a66a0b04b23bd9fc 2028 
cwiid_0.6.00+svn201-5.dsc
 8221b8a5ce294b3dd677d8a4d259ac30d6dab95fadb854e1d9559950691a 15992 
cwiid_0.6.00+svn201-5.debian.tar.xz
 eb66b142d97144daf03b8a8a5c499f6ef3938f3f09c9966b352adf0edfafa5de 10773 
cwiid_0.6.00+svn201-5_source.buildinfo
Files:
 0a8b14bbcce3dfc622717e7752eca8e6 2028 utils extra 

Bug#936358: marked as done (cwiid: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 00:49:22 +
with message-id 
and subject line Bug#936358: fixed in cwiid 0.6.00+svn201-5
has caused the Debian Bug report #936358,
regarding cwiid: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cwiid
Version: 0.6.00+svn201-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:cwiid

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.


--- End Message ---
--- Begin Message ---
Source: cwiid
Source-Version: 0.6.00+svn201-5
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated cwiid 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:04:15 -0400
Source: cwiid
Architecture: source
Version: 0.6.00+svn201-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Scott Kitterman 
Closes: 936358
Changes:
 cwiid (0.6.00+svn201-5) unstable; urgency=medium
 .
   * QA upload.
   * Rip out python bindings (Closes: #936358)
 - Obsolete libs, python2 only which is being removed
 - Delete wmgui, wminput, and python-cwiid binaries
Checksums-Sha1:
 673c9d63f8c67884ccd7674b61c5e94a4202aee8 2028 cwiid_0.6.00+svn201-5.dsc
 770e4556bdbdb5a5cb6c195e4c56e123157b19b3 15992 
cwiid_0.6.00+svn201-5.debian.tar.xz
 cdd8f27edf5ae8e3c26a3995a6da305d6af2af40 10773 
cwiid_0.6.00+svn201-5_source.buildinfo
Checksums-Sha256:
 1fe1fe658c0c46f5855ee1975f5c9e43d1778a52bfc965e0a66a0b04b23bd9fc 2028 
cwiid_0.6.00+svn201-5.dsc
 8221b8a5ce294b3dd677d8a4d259ac30d6dab95fadb854e1d9559950691a 15992 
cwiid_0.6.00+svn201-5.debian.tar.xz
 

Bug#951830: marked as done (mirror submission for mirrors.nipa.cloud)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 01:45:13 +0100
with message-id <20200324004513.gb750...@bongo.bofh.it>
and subject line Re: Bug#951695: mirror submission for mirrors.nipa.cloud
has caused the Debian Bug report #951830,
regarding mirror submission for mirrors.nipa.cloud
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirrors.nipa.cloud
Type: leaf
Archive-architecture: amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Natthaphon Phoonsookserm 
Country: TH Thailand
Location: Thailand
Sponsor: NIPA.CLOUD 1st Cloud Thailand https://www.nipa.cloud
Comment: NIPA.CLOUD 1st Cloud Thailand
 Internet link 20 Gbps
 http://mirrors.nipa.cloud/debian




Trace Url: http://mirrors.nipa.cloud/debian/project/trace/
Trace Url: http://mirrors.nipa.cloud/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirrors.nipa.cloud/debian/project/trace/mirrors.nipa.cloud
--- End Message ---
--- Begin Message ---
Duplicate of #953160.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#951695: marked as done (mirror submission for mirrors.nipa.cloud)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 01:45:13 +0100
with message-id <20200324004513.gb750...@bongo.bofh.it>
and subject line Re: Bug#951695: mirror submission for mirrors.nipa.cloud
has caused the Debian Bug report #951695,
regarding mirror submission for mirrors.nipa.cloud
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirrors.nipa.cloud
Type: leaf
Archive-architecture: amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Natthaphon Phoonsookserm 
Country: TH Thailand
Location: Thailand
Sponsor: NIPA.CLOUD 1st Cloud Thailand https://www.nipa.cloud
Comment: NIPA.CLOUD 1st Cloud Thailand
 Internet link 20 Gbps
 http://mirrors.nipa.cloud/debian




Trace Url: http://mirrors.nipa.cloud/debian/project/trace/
Trace Url: http://mirrors.nipa.cloud/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirrors.nipa.cloud/debian/project/trace/mirrors.nipa.cloud
--- End Message ---
--- Begin Message ---
Duplicate of #953160.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#954818: marked as done (mirror submission for mirror.cloroformo.org)

[Debian Bug Tracking System]

Your message dated Tue, 24 Mar 2020 01:42:21 +0100
with message-id <20200324004221.ga750...@bongo.bofh.it>
and subject line Re: Bug#954818: mirror submission for mirror.cloroformo.org
has caused the Debian Bug report #954818,
regarding mirror submission for mirror.cloroformo.org
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954818
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: mirror.cloroformo.org
Type: leaf
Archive-architecture: amd64
Archive-http: /debian/
Maintainer: Francisco 
Country: ES Spain
Location: Merida
Comment: Homeserver 200Mbits




Trace Url: http://mirror.cloroformo.org/debian/project/trace/
Trace Url: 
http://mirror.cloroformo.org/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://mirror.cloroformo.org/debian/project/trace/mirror.cloroformo.org
--- End Message ---
--- Begin Message ---
On Mar 24, Francisco  wrote:

> Comment: Homeserver 200Mbits
Dynamic IP, low bandwidth: does not qualify.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

Bug#913682: marked as done (quilt: fails to document QUILT_PC environment variable)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 23:21:31 +
with message-id 
and subject line Bug#913682: fixed in quilt 0.66-1
has caused the Debian Bug report #913682,
regarding quilt: fails to document QUILT_PC environment variable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
913682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quilt
Version: 0.65-2
Severity: minor

Dear Maintainer,

Sometimes quilt users must be able to switch between completely
different patch series.  For example, I ran into this issue when
dealing with applying an extra patch in debian/patches (to configure
both RCU_EXPERT and RCU_NOCB_CPU to default to "yes" to deal with
random Ryzen lockups) which turned out to conflict with a patch in
debian/patches-rt that "also" patched RCU_EXPERT default from "no" to
something else where apt-src applies the former set of patches when installing
and applies the latter set of patches on top of the former set when
building just (I think) the rt set of binary packages for the linux kernel.

I guess it could be claimed that the Debian Linux kernel should be
reorganized to use just one patch series, but currently that is not
the case (probably because that reorganization would be difficult),
and that is likely true of some other packages as well.  In sum,
multiple patch series are an unfortunate fact of life.

The only way to manage multiple patch series with quilt that I am
aware of (and it took a difficult google search to find this
information) is to specify both the QUILT_PATCHES and QUILT_PC
environment variables where the former points to the directory where
the series file is located (either debian/patches or
debian/patches-rt) and the latter is necessary to change between the
normal .pc location to somewhere else (I used .pc-rt for the above
specific case), I guess it could be argued that it is a rare case when
you attempt to manage with quilt two distinct patch series so QUILT_PC
is normally unnecessary.  But when you need it (as in the above case)
it is a lifesaver so I think it is worth documenting this environment
variable in the man page in the same section where QUILT_PATCHES and
several other environment variables are already documented.

You may also want to change the documentation of QUILT_SERIES there
that claims the search order for series can be prempted by an absolute
pathname for the series file, but that didn't work, and QUILT_PC did
the trick instead with QUILT_SERIES=series (which is the same as the
default value).

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages quilt depends on:
ii  bsdmainutils  11.1.2+b1
ii  bzip2 1.0.6-9
ii  diffstat  1.61-1+b1
ii  gettext   0.19.8.1-8
ii  patch 2.7.6-3
ii  perl  5.28.0-3

Versions of packages quilt recommends:
ii  less  487-0.1+b1

Versions of packages quilt suggests:
ii  graphviz2.40.1-5+b1
ii  postfix [mail-transport-agent]  3.3.0-1+b1
ii  procmail3.22-26

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: quilt
Source-Version: 0.66-1
Done: Martin Quinson 

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated quilt 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 23:54:33 +0100
Source: quilt
Binary: quilt quilt-el
Architecture: source all
Version: 0.66-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 quilt  - Tool to work with series 

Bug#923706: marked as done (quilt annotate requires ed)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 23:21:31 +
with message-id 
and subject line Bug#923706: fixed in quilt 0.66-1
has caused the Debian Bug report #923706,
regarding quilt annotate requires ed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
923706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923706
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quilt
Version: 0.65-3
Severity: important

Executing `quilt annotate`, at somepoint, apparently requires ed to be
installed.

Steps to reproduce:

  # Create a test directory
  $ mkdir /tmp/quiltbug && cd /tmp/quiltbug

  # Create a short test file
  $ for file in /etc/cron.*; do echo $file >> short.txt; done

  # Create the first patch
  $ quilt new short.patch && quilt add short.txt
  $ sed -i '5d' short.txt && quilt refresh

  # Bug
  $ quilt annotate
  sh: 1: ed: not found
  patch:  ed FAILED
  [...]


Regards,
Christian
--- End Message ---
--- Begin Message ---
Source: quilt
Source-Version: 0.66-1
Done: Martin Quinson 

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated quilt 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 23:54:33 +0100
Source: quilt
Binary: quilt quilt-el
Architecture: source all
Version: 0.66-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 quilt  - Tool to work with series of patches
 quilt-el   - simple Emacs interface of quilt
Closes: 793151 913682 923706
Changes:
 quilt (0.66-1) unstable; urgency=medium
 .
   [ Martin Quinson ]
   * New upstream release.
 - Document QUILT_PC in the manpage (Closes: #913682)
   * Update patches. Drop the following ones:
 - d/p/fixbuildrun (applied upstream)
 - d/p/fix-mail-threading (was cherry-picked from upstream)
   * Install NEWS file, that is the upstream's changelog.
   * Bump standard-version to 4.5.0 (install NEWS even if it's not mandated)
   * Use debhelper v12.
   * d/control: Depends on ed, as annotate sometimes needs it
 (Closes: #923706).
   * Install dpatch2quilt as /usr/bin/dpatch2quilt instead of as example
 (Closes: #793151).
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Submit (from ./configure), Name
 (from ./configure), Repository.
   * Wrap long lines in changelog entries: 0.25-3, 0.11-1.
Checksums-Sha1:
 dbde4e7fb23e024f66ed8ba2ea9e00e848e8927f 2014 quilt_0.66-1.dsc
 e848f46d1e2b0dd07eee1a04f04fb2a4c37bf1d0 413069 quilt_0.66.orig.tar.gz
 bb5cb1f593e7203706503a0063bb8e3a50a9c856 37700 quilt_0.66-1.debian.tar.xz
 a82fd4fc5aa531628777deab0f3b8628231ae824 7492 quilt-el_0.66-1_all.deb
 4b8bbfd992d9cfd05316bf58e51b2c6a41b2a2bc 318260 quilt_0.66-1_all.deb
 c4e02154271e6acc4168fc2e5ebfde421ce0e14b 8075 quilt_0.66-1_amd64.buildinfo
Checksums-Sha256:
 40f7e9015bb0c1036c57353be800b28cbc4578c8b0f2811c61c6c545cbb10d00 2014 
quilt_0.66-1.dsc
 314b319a6feb13bf9d0f9ffa7ce6683b06919e734a41275087ea457cc9dc6e07 413069 
quilt_0.66.orig.tar.gz
 f129bfd3e1cc140df5438368e214b361e1ef1402bca3ede49c45da88beb0d13f 37700 
quilt_0.66-1.debian.tar.xz
 3a25155df0c18659de8f71ed4e49ff5d017f6e66cf2915bfb2a31b143365006c 7492 
quilt-el_0.66-1_all.deb
 6a7d6bc2e87cc8174231d6fe7fed7d7acd3b090b8dc4148ea883ead5ccec4d75 318260 
quilt_0.66-1_all.deb
 abc3110a2f8c134971f1fa7f7a533c2bb5f481bb888f26ec107208d8d0e653e4 8075 
quilt_0.66-1_amd64.buildinfo
Files:
 1ebf85391a3c24914df7c923e7635e1b 2014 vcs optional quilt_0.66-1.dsc
 6800c2404a2c0598ab2eff92a636ba70 413069 vcs optional quilt_0.66.orig.tar.gz
 bbf95cfb951000a397c6722c224ab183 37700 vcs optional quilt_0.66-1.debian.tar.xz
 6eee646a7b357644c3b81e152034572e 7492 vcs optional quilt-el_0.66-1_all.deb
 270f07669b9bd16dcc6fa7d3a92ca2c1 318260 vcs optional quilt_0.66-1_all.deb
 2c63f7f85e151dd8eb4668192b159e82 8075 vcs optional quilt_0.66-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#793151: marked as done (quilt: Please ship dpatch2quilt.sh as /usr/bin/dpatch2quilt instead of as example)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 23:21:31 +
with message-id 
and subject line Bug#793151: fixed in quilt 0.66-1
has caused the Debian Bug report #793151,
regarding quilt: Please ship dpatch2quilt.sh as /usr/bin/dpatch2quilt instead 
of as example
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
793151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: quilt
Version: 0.63-3
Severity: wishlist

Hi,

it would be helpful if /usr/share/doc/quilt/examples/dpatch2quilt.sh
would be shipped in /usr/bin/ (and then without the .sh suffix)
instead.

TIA!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (111, 'buildd-unstable'), 
(111, 'buildd-experimental'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages quilt depends on:
ii  bsdmainutils  9.0.6
ii  bzip2 1.0.6-8
ii  diffstat  1.59-1
ii  gettext   0.19.4-1
ii  patch 2.7.5-1
ii  perl  5.20.2-6

Versions of packages quilt recommends:
ii  less  458-3

Versions of packages quilt suggests:
ii  graphviz2.38.0-10
ii  postfix [mail-transport-agent]  2.11.3-1
ii  procmail3.22-25

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: quilt
Source-Version: 0.66-1
Done: Martin Quinson 

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

Debian distribution maintenance software
pp.
Martin Quinson  (supplier of updated quilt 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 23:54:33 +0100
Source: quilt
Binary: quilt quilt-el
Architecture: source all
Version: 0.66-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Quinson 
Changed-By: Martin Quinson 
Description:
 quilt  - Tool to work with series of patches
 quilt-el   - simple Emacs interface of quilt
Closes: 793151 913682 923706
Changes:
 quilt (0.66-1) unstable; urgency=medium
 .
   [ Martin Quinson ]
   * New upstream release.
 - Document QUILT_PC in the manpage (Closes: #913682)
   * Update patches. Drop the following ones:
 - d/p/fixbuildrun (applied upstream)
 - d/p/fix-mail-threading (was cherry-picked from upstream)
   * Install NEWS file, that is the upstream's changelog.
   * Bump standard-version to 4.5.0 (install NEWS even if it's not mandated)
   * Use debhelper v12.
   * d/control: Depends on ed, as annotate sometimes needs it
 (Closes: #923706).
   * Install dpatch2quilt as /usr/bin/dpatch2quilt instead of as example
 (Closes: #793151).
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Submit (from ./configure), Name
 (from ./configure), Repository.
   * Wrap long lines in changelog entries: 0.25-3, 0.11-1.
Checksums-Sha1:
 dbde4e7fb23e024f66ed8ba2ea9e00e848e8927f 2014 quilt_0.66-1.dsc
 e848f46d1e2b0dd07eee1a04f04fb2a4c37bf1d0 413069 quilt_0.66.orig.tar.gz
 bb5cb1f593e7203706503a0063bb8e3a50a9c856 37700 quilt_0.66-1.debian.tar.xz
 a82fd4fc5aa531628777deab0f3b8628231ae824 7492 quilt-el_0.66-1_all.deb
 4b8bbfd992d9cfd05316bf58e51b2c6a41b2a2bc 318260 quilt_0.66-1_all.deb
 c4e02154271e6acc4168fc2e5ebfde421ce0e14b 8075 quilt_0.66-1_amd64.buildinfo
Checksums-Sha256:
 40f7e9015bb0c1036c57353be800b28cbc4578c8b0f2811c61c6c545cbb10d00 2014 
quilt_0.66-1.dsc
 314b319a6feb13bf9d0f9ffa7ce6683b06919e734a41275087ea457cc9dc6e07 413069 
quilt_0.66.orig.tar.gz
 f129bfd3e1cc140df5438368e214b361e1ef1402bca3ede49c45da88beb0d13f 37700 
quilt_0.66-1.debian.tar.xz
 3a25155df0c18659de8f71ed4e49ff5d017f6e66cf2915bfb2a31b143365006c 7492 
quilt-el_0.66-1_all.deb
 6a7d6bc2e87cc8174231d6fe7fed7d7acd3b090b8dc4148ea883ead5ccec4d75 318260 
quilt_0.66-1_all.deb
 

Bug#954786: marked as done (ITP: python-bcbio-gff -- Python3 library to read and write Generic Feature Format)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 23:00:10 +
with message-id 
and subject line Bug#954786: fixed in python-bcbio-gff 0.6.6-1
has caused the Debian Bug report #954786,
regarding ITP: python-bcbio-gff -- Python3 library to read and write Generic 
Feature Format
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist

Subject: ITP: python-bcbio-gff -- Python3 library to read and write Generic 
Feature Format
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: python-bcbio-gff
  Version : 0.6.6
  Upstream Author : Brad Chapman 
* URL : https://github.com/chapmanb/bcbb/tree/master/gff
* License : BioPython
  Programming Lang: Python
  Description : Python3 library to read and write Generic Feature Format
 A Python library to read and write Generic Feature Format (GFF).
 .
 Generic Feature Format (GFF) is a biological sequence file format for
 representing features and annotations on sequences. It is a tab
 delimited format, making it accessible to biologists and editable in
 text editors and spreadsheet programs. It is also well defined and can
 be parsed via automated programs. GFF files are available from many of
 the large sequencing and annotation centers.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/python-bcbio-gff
--- End Message ---
--- Begin Message ---
Source: python-bcbio-gff
Source-Version: 0.6.6-1
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-bcbio-gff 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 15:00:21 +0100
Source: python-bcbio-gff
Binary: python3-bcbio-gff
Architecture: source all
Version: 0.6.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python3-bcbio-gff - Python3 library to read and write Generic Feature Format
Closes: 954786
Changes:
 python-bcbio-gff (0.6.6-1) unstable; urgency=medium
 .
   * Initial release (Closes: #954786)
Checksums-Sha1:
 e73372dd36aea764fd0788a7a0757f6bd73d1062 2112 python-bcbio-gff_0.6.6-1.dsc
 cacd2ce6d071c58bc7f0e2f19149becc525d5577 19099 
python-bcbio-gff_0.6.6.orig.tar.gz
 5ca46a6bd0a1cb090d5746bd5f7e84e8c134adfd 2024 
python-bcbio-gff_0.6.6-1.debian.tar.xz
 0ad0436b17375aafcabafe93325b975bb963d0d5 6814 
python-bcbio-gff_0.6.6-1_amd64.buildinfo
 2bc1f09a629ffeb92f9ebe12e6c2b6d1b4eee507 14988 
python3-bcbio-gff_0.6.6-1_all.deb
Checksums-Sha256:
 a160507ec9ba90e08d36c1dc6e5319d189ee58be6cf6bfc2184fa5f83e6c9d48 2112 
python-bcbio-gff_0.6.6-1.dsc
 74c6920c91ca18ed9cb872e9471c0be442dad143d8176345917eb1fefc86bc37 19099 
python-bcbio-gff_0.6.6.orig.tar.gz
 442ef178213b1feea729278d5dacdd14cd44082760bcc24320e1c2a367f3b47b 2024 
python-bcbio-gff_0.6.6-1.debian.tar.xz
 22e0b9c2a980833b4a40e775ebef9418ab7840c06cf36f2210a5cb5691149de9 6814 
python-bcbio-gff_0.6.6-1_amd64.buildinfo
 0e4caa6dd309ee7d5b19faad24754b241781a8bc1c732e4694c62db54264760c 14988 
python3-bcbio-gff_0.6.6-1_all.deb
Files:
 543ba7b4235f321b2b67cbe59ebb6722 2112 science optional 
python-bcbio-gff_0.6.6-1.dsc
 bcaf710c5fa11fe66f3782a8c38bc02e 19099 science optional 
python-bcbio-gff_0.6.6.orig.tar.gz
 dba5950ff933c94dae8c9ae086b83a7e 2024 science optional 
python-bcbio-gff_0.6.6-1.debian.tar.xz
 906f5539321258c5c1f9930e3336b727 6814 science optional 
python-bcbio-gff_0.6.6-1_amd64.buildinfo
 c37381b332f2cb7081cdaa47a59381e9 14988 python optional 
python3-bcbio-gff_0.6.6-1_all.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl54wZcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHq4w/9Fi/zheDCAkWUH0r3AuY/fhPnoUZt6CbZ
t7SuLvDnnizcAyzGIo2fSXd3gTmR0NJyt9n0X7iSZhVjkUv7DbbZXTO3FhlBLnBz

Bug#942227: marked as done (fish: "unreachable" state reached when redirecting to/from an unopenable file with `exec')

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:09:04 -0400
with message-id <87pnd2wwov@posteo.net>
and subject line Re: Bug#942227: fish: "unreachable" state reached when 
redirecting to/from an unopenable file with `exec'
has caused the Debian Bug report #942227,
regarding fish: "unreachable" state reached when redirecting to/from an 
unopenable file with `exec'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fish
Version: 3.0.2-2
Severity: normal
Tags: upstream

Dear Maintainer,

I was running a program under GDB, and I needed to have it read from a
file which it is not permitted to read. So I typed

  (gdb) run < /dev/mem

GDB ran fish (since that is my $SHELL) to execute my program. But fish
was terminated by SIGABRT with the following stacktrace:

An error occurred while redirecting file '/dev/mem'
open: Permission denied
 fish: src/exec.cpp:1032: failed assertion: this should be unreachable
 fish: Backtrace:
 fish: 0   /usr/bin/fish(+0xb16e7) [0x556056e7]
 fish: 1   parse_execution_context_t::run_1_job(tnode_t, 
block_t const*) + 2101
 fish: 2   
parse_execution_context_t::run_job_conjunction(tnode_t,
 block_t const*) + 196
 fish: 3   parse_execution_result_t 
parse_execution_context_t::run_job_list(tnode_t,
 block_t const*) + 281
 fish: 4   parse_execution_context_t::eval_node(tnode_t, 
block_t const*, io_chain_t const&) + 1380
 fish: 5   int 
parser_t::eval_node(std::shared_ptr, 
tnode_t, io_chain_t const&, block_type_t, 
std::shared_ptr) + 777
 fish: 6   parser_t::eval(std::shared_ptr, io_chain_t 
const&, block_type_t) + 176
 fish: 7   parser_t::eval(std::__cxx11::basic_string, std::allocator >, io_chain_t const&, 
block_type_t) + 225
 fish: 8   run_command_list(std::vector, std::allocator >, 
std::allocator, 
std::allocator > > >*, io_chain_t const&) + 147
 fish: 9   main + 2200
 fish: 10  __libc_start_main + 235
 fish: 11  _start + 42

The first two lines are expected, but it then aborts because it reached
an "unreachable" state (how embarrassing!)

At first I thought that the problem was being run by GDB, but it is
actually `exec' that is the problem. For example:

  $ fish -c 'exec cat < /dev/mem'
  An error occurred while redirecting file '/dev/mem'
  open: Permission denied
   fish: src/exec.cpp:1032: failed assertion: this should be unreachable
   fish: Backtrace:
  [...]

Note the `exec' and the `<'. Without the `<', `cat' tries to open
/dev/mem, not `fish', so the bug does not appear.

This is not only specific to /dev/mem or special files. It can be any
unreadable file, for example /etc/shadow. It can even be a file that
does not exist. (Just remember to look for a file that does not exist
outside of your home directory, since you are sure to have created every
possible filename in your home directory if you are anything like me
(actually, I usually just shove it under ~/misc these days).)

Each time, it aborts in src/exec.cpp:1032. Fish should of course exit
with an error, but it should not reach an "unreachable" state.

This also happens if you redirect *to* an unwritable file even if it is
readable (such as /etc/passwd).

Also note that without the `exec', the bug does not appear:

  $ fish -c 'cat < /dev/mem'
  An error occurred while redirecting file '/dev/mem'
  open: Permission denied

This looks like an upstream bug (hence the "upstream" tag), but I'm not
sure because I haven't tried it with upstream fish yet. I'll send
another message with my findings if I do get around to trying it with
upstream.

Thanks,
Asher

-- 
A witty saying proves nothing, but saying something pointless gets
people's attention.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fish depends on:
ii  bc  1.07.1-2+b2
ii  dpkg1.19.7
ii  elinks [www-browser]0.13~20190125-4
ii  epiphany-browser [www-browser]  3.32.1.2-3
ii  firefox-esr [www-browser]   60.8.0esr-1
ii  fish-common 3.0.2-2
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  

Bug#954748: marked as done (RFA: python-weberror -- Python web error handling and exception catching module)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 22:46:51 +0100
with message-id <20200323214651.bxm6jrbkj23aq...@p1otr.com>
and subject line closing as package is removed from unstable/testing
has caused the Debian Bug report #954748,
regarding RFA: python-weberror -- Python web error handling and exception 
catching module
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal

I request an adopter for the python-weberror package.

The package description is:
 This Python module provides error handling and exception catching
 functionality for WSGI web applications. It is primarily used by Pylons
 (python-pylons).
--- End Message ---
--- Begin Message ---
sorry for confusion


signature.asc
Description: PGP signature
--- End Message ---

Bug#954181: marked as done (Please stop disabling Bluetooth monitor support in libpcap)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 21:20:38 +
with message-id 
and subject line Bug#954181: fixed in libpcap 1.9.1-3
has caused the Debian Bug report #954181,
regarding Please stop disabling Bluetooth monitor support in libpcap
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpcap0.8
Version: 1.8.1-6

That version of the package has a patch, patches/bluez-build.diff, that 
"[Includes] bluetooth/mgmt.h in bt-monitor compile test to make it fail with 
BlueZ 5.x."

This has already caused at least one complaint with Wireshark running on a 
Debian derivative, Linux Mint (well, a derivative of a derivative...):


https://ask.wireshark.org/question/15232/how-to-modify-link-layer-header-for-bluetooth-captures/

Please remove this, so that people can use the bluetooth-monitor device on 
Debian - and on its derivatives, once it trickles down to all the derivatives.  
I built the current master-branch versions of libpcap and tcpdump on Ubuntu 
18.04, and they work Just Fine, at least on my VMware Fusion VM with my Mac's 
Bluetooth adapter turned on (they may have found some problems in the Wireshark 
*dissector* for Bluetooth monitor messages, but that's another matter).--- End Message ---
--- Begin Message ---
Source: libpcap
Source-Version: 1.9.1-3
Done: Romain Francoise 

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

Debian distribution maintenance software
pp.
Romain Francoise  (supplier of updated libpcap 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 20:17:44 +0100
Source: libpcap
Architecture: source
Version: 1.9.1-3
Distribution: unstable
Urgency: medium
Maintainer: Romain Francoise 
Changed-By: Romain Francoise 
Closes: 954181
Changes:
 libpcap (1.9.1-3) unstable; urgency=medium
 .
   * Drop debian/patches/bluez-build.diff (closes: #954181).
Checksums-Sha1:
 e14c6d36d3308ca6629022996f75b40c280c8c7f 2352 libpcap_1.9.1-3.dsc
 854337c5c51ad2eef8b24f628feb3398293551b7 19280 libpcap_1.9.1-3.debian.tar.xz
 523c3b7c38bcd3aec9a013e75d2081c55a49c120 5609 libpcap_1.9.1-3_source.buildinfo
Checksums-Sha256:
 646152cd08636ddb5f1c508b2c2c0aa61e1139cab6ab78075178619d7aeb0b12 2352 
libpcap_1.9.1-3.dsc
 84df1e5b4159ab83c136c174f0bb0eb8de06d7bf8a9237033ce933127afec17e 19280 
libpcap_1.9.1-3.debian.tar.xz
 df5bdd1d55a656a57a653246b6edbd6a2bb6849171ae78965ed31ae4342d1a05 5609 
libpcap_1.9.1-3_source.buildinfo
Files:
 758d9200d0ff174599f54d0cdbbc300d 2352 devel optional libpcap_1.9.1-3.dsc
 d5bb23316d30316d47d1efc16644f458 19280 devel optional 
libpcap_1.9.1-3.debian.tar.xz
 2dadb89b06eff9138435efa6526ad866 5609 devel optional 
libpcap_1.9.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvjSXQsqYfs1+d+QtrRX0NfBfli0FAl55Is8ACgkQrRX0NfBf
li3iKxAAq8r8IxWLONKntBah0Dfi8PyBSpIbcxyDEdSvhQYveA2YHgiqrLwHyI9S
67Lza6IIMlAgTh6c+/ddj91lDv7XiB3O9Kc1owJTgwYV2LUTmIWsCNcdgkLHA663
jvj8oMVmJhnE2/reLgECLt2WLlI0NbJ2UI8tI9i82Bk3cb3d6qi1pEkiBScPeDdG
EvSLNvTtuB0rTvmYjdP1pnxbenPR4RYrYgxij1ehOs559zZnq4U2wa/yMk05PiAa
1ovPjmQa49qdAyl0+XGCpuRCQZqiQhO5rMwIw8YjwHQUKZnQL+nBvH50/hjTBHuk
IjQcDYDmptqxwarzqXC8hPrzndhEnXsE13VifQVrVmQkNZ1Z8vDLU089cxakBRDq
gHMGmt4PA9wpk5xK4qHObp808OaXswfsiaZ2TDKiE0Jw87Jjot9Mb/jR6D2Zp1B2
mqkYfnz7Cc/AvM+E+OFUJ8HPzyiru7MthiTerMWIRRu5wFj/mGmLQluby07psimk
WhKpkHdV6VH50BoFTPbxv6uhQ4g3eXoaB1m7bAD9DBrZmacOvrUwKYILuU4+5DlE
c8lHyzOtp1WW53o0dlcUKJPojHzGSpECBcV7jXD6Ycg1pGRuvFjmjWywrAlbvjCF
0u++U/+bH+MMOcbp0eBk3e/Nl3k8BikxnHxCk4/kSBsBJtmNH1Q=
=omqU
-END PGP SIGNATURE End Message ---

Bug#953074: marked as done (python3-twisted: conch/client/knownhosts.py:492: SyntaxWarning: "is" with a literal. Did you mean "=="?)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:24 +
with message-id 
and subject line Bug#948560: fixed in twisted 18.9.0-7
has caused the Debian Bug report #948560,
regarding python3-twisted: conch/client/knownhosts.py:492: SyntaxWarning: "is" 
with a literal. Did you mean "=="?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twisted
Version: 18.9.0-6
Severity: normal
File: /usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py
Usertag: warnings

I got a warning from Python when upgrading python3-twisted recently:

Setting up python3-twisted (18.9.0-6) ...
/usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py:492: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if keytype is "EC":

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-twisted depends on:
ii  python3   3.7.5-3
ii  python3-attr  19.3.0-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hamcrest  1.9.0-2
ii  python3-hyperlink 19.0.0-1
ii  python3-idna  2.6-2
ii  python3-incremental   16.10.1-3.1
ii  python3-openssl   19.0.0-1
ii  python3-service-identity  18.1.0-5
ii  python3-twisted-bin   18.9.0-6
ii  python3-zope.interface4.7.1-1

python3-twisted recommends no packages.

Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-pampy 
pn  python3-qt4   
pn  python3-serial
ii  python3-tk3.8.0-1
pn  python3-wxgtk2.8  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-7
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:49:21 +0100
Source: twisted
Architecture: source
Version: 18.9.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - 

Bug#930626: marked as done (twisted: CVE-2019-12855)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:24 +
with message-id 
and subject line Bug#930626: fixed in twisted 18.9.0-7
has caused the Debian Bug report #930626,
regarding twisted: CVE-2019-12855
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-3
Severity: important
Tags: security upstream
Forwarded: https://twistedmatrix.com/trac/ticket/9561

Hi,

The following vulnerability was published for twisted.

CVE-2019-12855[0]:
| In words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP
| support did not verify certificates when used with TLS, allowing an
| attacker to MITM connections.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12855
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12855
[1] https://twistedmatrix.com/trac/ticket/9561
[2] https://github.com/twisted/twisted/pull/1147

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-7
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:49:21 +0100
Source: twisted
Architecture: source
Version: 18.9.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
Checksums-Sha1:
 3c43921a889a3b58ff635de0d4380641452a2d18 3363 twisted_18.9.0-7.dsc
 7e45bebe2aa6dccd1fcdcc3b5d93a21a1395adee 41712 twisted_18.9.0-7.debian.tar.xz
Checksums-Sha256:
 b97af62d2b050c3702f88e603ae488d45618bc3a389ffb0bc8099fb52752d90b 3363 
twisted_18.9.0-7.dsc
 fb428c0256ff81fc2e03815e511151a4c6f1fac7c4330b12388e7a466acdb13d 41712 
twisted_18.9.0-7.debian.tar.xz
Files:
 09212cffe8e7d2f6acabc567fe2fac02 3363 python optional twisted_18.9.0-7.dsc
 1284d646560c4ca87c8979f893d02859 41712 python optional 
twisted_18.9.0-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl55EvkACgkQXkCM2RzY

Bug#930626: marked as done (twisted: CVE-2019-12855)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:36 +
with message-id 
and subject line Bug#930626: fixed in twisted 18.9.0-8
has caused the Debian Bug report #930626,
regarding twisted: CVE-2019-12855
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-3
Severity: important
Tags: security upstream
Forwarded: https://twistedmatrix.com/trac/ticket/9561

Hi,

The following vulnerability was published for twisted.

CVE-2019-12855[0]:
| In words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP
| support did not verify certificates when used with TLS, allowing an
| attacker to MITM connections.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12855
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12855
[1] https://twistedmatrix.com/trac/ticket/9561
[2] https://github.com/twisted/twisted/pull/1147

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-8
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:14:09 +0100
Source: twisted
Architecture: source
Version: 18.9.0-8
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-8) unstable; urgency=high
 .
   * A no-change upload to set urgency to high since the upload
 fixes security issues.
 .
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
 .
   [ Moritz Muehlenhoff  ]
   * Remove Suggests on python-gtk2/python-glade2, which is being removed.
Checksums-Sha1:
 240d4f043a58ca6a557561a43364f61ff57324cd 3363 twisted_18.9.0-8.dsc
 1919f66c3d525e6b0e94b07bf8a419c208d5270c 41776 twisted_18.9.0-8.debian.tar.xz
Checksums-Sha256:
 53083bd6a882bc1dc919b9fed4647c4d9d9356aea18cbdc5ec0de280dea09d3d 3363 
twisted_18.9.0-8.dsc
 820329295f00727ed2aed992adc841c13adf8d54425bfbb04a37941d344fc9ba 41776 
twisted_18.9.0-8.debian.tar.xz
Files:
 03a3587d903c592ad422874ee88eb66d 3363 python 

Bug#948560: marked as done (Use of 'is' token for comparing string in knownhosts.py)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:24 +
with message-id 
and subject line Bug#948560: fixed in twisted 18.9.0-7
has caused the Debian Bug report #948560,
regarding Use of 'is' token for comparing string in knownhosts.py
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twisted
Version: 18.9.0-6
Severity: normal


During update to new python3-twisted:

Setting up python3-twisted (18.9.0-6) ...
/usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py:492: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if keytype is "EC":


It appears to be fixed in twisted 19.2.0+ tho:
https://github.com/twisted/twisted/commit/de05fee07a39d3415e4a3e9738d141b43b54f95c
which was released almost a year ago.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-twisted depends on:
ii  python3   3.7.5-3
ii  python3-attr  18.2.0-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hamcrest  1.9.0-2
ii  python3-hyperlink 19.0.0-1
ii  python3-idna  2.6-2
ii  python3-incremental   16.10.1-3.1
ii  python3-openssl   19.0.0-1
ii  python3-service-identity  18.1.0-5
ii  python3-twisted-bin   18.9.0-6
ii  python3-zope.interface4.6.0-4

python3-twisted recommends no packages.

Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-pampy 
pn  python3-qt4   
ii  python3-serial3.4-5
pn  python3-tk
pn  python3-wxgtk2.8  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-7
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:49:21 +0100
Source: twisted
Architecture: source
Version: 18.9.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - 

Bug#929915: marked as done (vala: debian/rules: simplify parallel build)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:58:04 +
with message-id 
and subject line Bug#929915: fixed in vala 0.48.2-1
has caused the Debian Bug report #929915,
regarding vala: debian/rules: simplify parallel build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
929915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vala
Version: 0.42.5-1
Severity: wishlist
Tags: patch

While looking into the vala package, I noticed that it bears unnecessary
complexity for running the bootstrap build. Using dh_auto_* works there
and removes the need for computing DEB_MAKE_PARALLEL. I've attached a
patch to demonstrate that. If you don't like the patch, please close
this bug anyway.

Helmut
diff --minimal -Nru vala-0.42.5/debian/changelog vala-0.42.5/debian/changelog
--- vala-0.42.5/debian/changelog2019-01-22 18:07:20.0 +0100
+++ vala-0.42.5/debian/changelog2019-06-02 20:48:44.0 +0200
@@ -1,3 +1,10 @@
+vala (0.42.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Simplify parallelity using more dh_auto_*. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 02 Jun 2019 20:48:44 +0200
+
 vala (0.42.5-1) unstable; urgency=medium
 
   * New upstream release
diff --minimal -Nru vala-0.42.5/debian/rules vala-0.42.5/debian/rules
--- vala-0.42.5/debian/rules2019-01-22 18:07:20.0 +0100
+++ vala-0.42.5/debian/rules2019-06-02 20:48:44.0 +0200
@@ -4,13 +4,6 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-O1 -Wl,-z,defs -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND = -Wall
 
-DEB_PARALLEL_JOBS = $(patsubst parallel=%,%,$(filter 
parallel=%,$(DEB_BUILD_OPTIONS)))
-ifneq (,$(DEB_PARALLEL_JOBS))
-DEB_MAKE_PARALLEL = -j$(DEB_PARALLEL_JOBS)
-else
-DEB_MAKE_PARALLEL =
-endif
-
 %:
dh $@ --with gnome
 
@@ -27,8 +20,8 @@
dh_auto_configure --builddirectory=bootstrap/build
 
 bootstrap: configure-bootstrap
-   make $(DEB_MAKE_PARALLEL) -C bootstrap/build
-   make $(DEB_MAKE_PARALLEL) -C bootstrap/build 
DESTDIR=$(CURDIR)/bootstrap/install install
+   dh_auto_build --builddirectory=bootstrap/build
+   dh_auto_install --builddirectory=bootstrap/build -- 
DESTDIR=$(CURDIR)/bootstrap/install
 
 override_dh_auto_configure: bootstrap
find -name '*.vala.stamp' -delete
--- End Message ---
--- Begin Message ---
Source: vala
Source-Version: 0.48.2-1
Done: Rico Tzschichholz 

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

Debian distribution maintenance software
pp.
Rico Tzschichholz  (supplier of updated vala 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:45:06 +0100
Source: vala
Binary: libvalacodegen-0.48-0 valac-bin valac valac-0.48-vapi vala-0.48-doc 
libvala-0.48-0 libvala-0.48-dev valadoc libvaladoc-0.48-0 libvaladoc-0.48-data 
libvaladoc-0.48-dev
Architecture: source
Version: 0.48.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Rico Tzschichholz 
Description:
 libvala-0.48-0 - C# like language for the GObject system - library
 libvala-0.48-dev - C# like language for the GObject system - development 
headers
 libvalacodegen-0.48-0 - internal package for C# like language for the GObject 
system
 libvaladoc-0.48-0 - API documentation generator for vala (library)
 libvaladoc-0.48-data - API documentation generator for vala (data)
 libvaladoc-0.48-dev - API documentation generator for vala (devel files)
 vala-0.48-doc - C# like language for the GObject system - documentation
 valac  - C# like language for the GObject system
 valac-0.48-vapi - C# like language for the GObject system - vapi files
 valac-bin  - internal package for C# like language for the GObject system
 valadoc- API documentation generator for vala
Closes: 916312 929915 942869
Changes:
 vala (0.48.2-1) unstable; urgency=medium
 .
   [ Rico Tzschichholz ]
   * New upstream release
   * Add README.md to docs (Closes: #942869)
   * Make valadoc 

Bug#953074: marked as done (python3-twisted: conch/client/knownhosts.py:492: SyntaxWarning: "is" with a literal. Did you mean "=="?)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:36 +
with message-id 
and subject line Bug#948560: fixed in twisted 18.9.0-8
has caused the Debian Bug report #948560,
regarding python3-twisted: conch/client/knownhosts.py:492: SyntaxWarning: "is" 
with a literal. Did you mean "=="?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twisted
Version: 18.9.0-6
Severity: normal
File: /usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py
Usertag: warnings

I got a warning from Python when upgrading python3-twisted recently:

Setting up python3-twisted (18.9.0-6) ...
/usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py:492: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if keytype is "EC":

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-twisted depends on:
ii  python3   3.7.5-3
ii  python3-attr  19.3.0-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hamcrest  1.9.0-2
ii  python3-hyperlink 19.0.0-1
ii  python3-idna  2.6-2
ii  python3-incremental   16.10.1-3.1
ii  python3-openssl   19.0.0-1
ii  python3-service-identity  18.1.0-5
ii  python3-twisted-bin   18.9.0-6
ii  python3-zope.interface4.7.1-1

python3-twisted recommends no packages.

Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-pampy 
pn  python3-qt4   
pn  python3-serial
ii  python3-tk3.8.0-1
pn  python3-wxgtk2.8  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-8
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:14:09 +0100
Source: twisted
Architecture: source
Version: 18.9.0-8
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-8) unstable; urgency=high
 .
   * A no-change upload to set urgency to high since the upload
 fixes security issues.
 .
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   

Bug#953950: marked as done (twisted: CVE-2020-10108 CVE-2020-10109)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:36 +
with message-id 
and subject line Bug#953950: fixed in twisted 18.9.0-8
has caused the Debian Bug report #953950,
regarding twisted: CVE-2020-10108 CVE-2020-10109
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
953950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-6
Severity: important
Tags: security upstream
Control: found -1 19.10.0~rc1-1
Control: found -1 18.9.0-3
Control: found -1 16.6.0-2

Hi,

The following vulnerabilities were published for twisted.

CVE-2020-10108[0]:
| In Twisted Web through 19.10.0, there was an HTTP request splitting
| vulnerability. When presented with two content-length headers, it
| ignored the first header. When the second content-length value was set
| to zero, the request body was interpreted as a pipelined request.


CVE-2020-10109[1]:
| In Twisted Web through 19.10.0, there was an HTTP request splitting
| vulnerability. When presented with a content-length and a chunked
| encoding header, the content-length took precedence and the remainder
| of the request body was interpreted as a pipelined request.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-10108
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10108
[1] https://security-tracker.debian.org/tracker/CVE-2020-10109
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10109
[2] https://know.bishopfox.com/advisories/twisted-version-19.10.0#INOR

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-8
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:14:09 +0100
Source: twisted
Architecture: source
Version: 18.9.0-8
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-8) unstable; urgency=high
 .
   * A no-change upload to set urgency to high since the upload
 fixes security issues.
 .
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
 .
   [ Moritz Muehlenhoff  ]
   * Remove 

Bug#930389: marked as done (twisted: CVE-2019-12387)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:24 +
with message-id 
and subject line Bug#930389: fixed in twisted 18.9.0-7
has caused the Debian Bug report #930389,
regarding twisted: CVE-2019-12387
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-3
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for twisted.

CVE-2019-12387[0]:
| In Twisted before 19.2.1, twisted.web did not validate or sanitize
| URIs or HTTP methods, allowing an attacker to inject invalid
| characters such as CRLF.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12387
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12387
[1] 
https://github.com/twisted/twisted/commit/6c61fc4503ae39ab8ecee52d10f10ee2c371d7e2
[2] 

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-7
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:49:21 +0100
Source: twisted
Architecture: source
Version: 18.9.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
Checksums-Sha1:
 3c43921a889a3b58ff635de0d4380641452a2d18 3363 twisted_18.9.0-7.dsc
 7e45bebe2aa6dccd1fcdcc3b5d93a21a1395adee 41712 twisted_18.9.0-7.debian.tar.xz
Checksums-Sha256:
 b97af62d2b050c3702f88e603ae488d45618bc3a389ffb0bc8099fb52752d90b 3363 
twisted_18.9.0-7.dsc
 fb428c0256ff81fc2e03815e511151a4c6f1fac7c4330b12388e7a466acdb13d 41712 
twisted_18.9.0-7.debian.tar.xz
Files:
 09212cffe8e7d2f6acabc567fe2fac02 3363 python optional twisted_18.9.0-7.dsc
 1284d646560c4ca87c8979f893d02859 41712 python optional 
twisted_18.9.0-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl55EvkACgkQXkCM2RzY
OdKz7Af/Rrni523VhMNJP7r2XieyoYcBDG7wflZQZxvn7xa8N2ZBKmjCsiJRCOEf

Bug#953950: marked as done (twisted: CVE-2020-10108 CVE-2020-10109)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:24 +
with message-id 
and subject line Bug#953950: fixed in twisted 18.9.0-7
has caused the Debian Bug report #953950,
regarding twisted: CVE-2020-10108 CVE-2020-10109
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
953950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-6
Severity: important
Tags: security upstream
Control: found -1 19.10.0~rc1-1
Control: found -1 18.9.0-3
Control: found -1 16.6.0-2

Hi,

The following vulnerabilities were published for twisted.

CVE-2020-10108[0]:
| In Twisted Web through 19.10.0, there was an HTTP request splitting
| vulnerability. When presented with two content-length headers, it
| ignored the first header. When the second content-length value was set
| to zero, the request body was interpreted as a pipelined request.


CVE-2020-10109[1]:
| In Twisted Web through 19.10.0, there was an HTTP request splitting
| vulnerability. When presented with a content-length and a chunked
| encoding header, the content-length took precedence and the remainder
| of the request body was interpreted as a pipelined request.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-10108
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10108
[1] https://security-tracker.debian.org/tracker/CVE-2020-10109
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10109
[2] https://know.bishopfox.com/advisories/twisted-version-19.10.0#INOR

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-7
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:49:21 +0100
Source: twisted
Architecture: source
Version: 18.9.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
Checksums-Sha1:
 3c43921a889a3b58ff635de0d4380641452a2d18 3363 twisted_18.9.0-7.dsc
 7e45bebe2aa6dccd1fcdcc3b5d93a21a1395adee 41712 twisted_18.9.0-7.debian.tar.xz
Checksums-Sha256:
 

Bug#954585: marked as done (should.js: FTBFS: dh_auto_test: error: cd ./should-equal && sh -e ../debian/nodejs/should-equal/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:56:56 +
with message-id 
and subject line Bug#954585: fixed in should.js 13.2.3~dfsg-3
has caused the Debian Bug report #954585,
regarding should.js: FTBFS: dh_auto_test: error: cd ./should-equal && sh -e 
../debian/nodejs/should-equal/test returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: should.js
Version: 13.2.3~dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>   mkdir node_modules
>   ln -s /usr/share/nodejs/rollup-plugin-node-resolve ./node_modules/
>   ln -s ../should-equal node_modules/should-equal
>   ln -s ../should-format node_modules/should-format
>   ln -s ../should-type node_modules/should-type
>   ln -s ../should-type-adaptors node_modules/should-type-adaptors
>   ln -s ../should-util node_modules/should-util
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/should-equal/build
>   cd ./should-equal && sh -e ../debian/nodejs/should-equal/build
> (!) You have passed an unrecognized option
> Unknown CLI flag: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 
> 17, 18. Allowed options: acorn, acornInjectPlugins, amd, assetFileNames, 
> banner, c, cache, chunkFileNames, chunkGroupingSize, compact, config, 
> context, d, dir, dynamicImportFunction, e, entryFileNames, environment, 
> esModule, experimentalCacheExpiry, experimentalOptimizeChunks, 
> experimentalTopLevelAwait, exports, extend, external, f, file, footer, 
> format, freeze, g, globals, h, i, indent, inlineDynamicImports, input, 
> interop, intro, m, manualChunks, moduleContext, n, name, 
> namespaceToStringTag, noConflict, o, onwarn, outro, paths, perf, plugins, 
> preferConst, preserveModules, preserveSymlinks, shimMissingExports, silent, 
> sourcemap, sourcemapExcludeSources, sourcemapFile, strict, treeshake, v, w, 
> watch
> 
> index.js → stdout...
> 'use strict';
> 
> function _interopDefault (ex) { return (ex && (typeof ex === 'object') && 
> 'default' in ex) ? ex['default'] : ex; }
> 
> var t = _interopDefault(require('should-type'));
> 
> function format(msg) {
>   var args = arguments;
>   for (var i = 1, l = args.length; i < l; i++) {
> msg = msg.replace(/%s/, args[i]);
>   }
>   return msg;
> }
> 
> var hasOwnProperty = Object.prototype.hasOwnProperty;
> 
> function EqualityFail(a, b, reason, path) {
>   this.a = a;
>   this.b = b;
>   this.reason = reason;
>   this.path = path;
> }
> 
> function typeToString(tp) {
>   return tp.type + (tp.cls ? "(" + tp.cls + (tp.sub ? " " + tp.sub : "") + 
> ")" : "");
> }
> 
> var PLUS_0_AND_MINUS_0 = "+0 is not equal to -0";
> var DIFFERENT_TYPES = "A has type %s and B has type %s";
> var EQUALITY = "A is not equal to B";
> var EQUALITY_PROTOTYPE = "A and B have different prototypes";
> var WRAPPED_VALUE = "A wrapped value is not equal to B wrapped value";
> var FUNCTION_SOURCES = "function A is not equal to B by source code value 
> (via .toString call)";
> var MISSING_KEY = "%s has no key %s";
> var SET_MAP_MISSING_KEY = "Set/Map missing key %s";
> 
> var DEFAULT_OPTIONS = {
>   checkProtoEql: true,
>   checkSubType: true,
>   plusZeroAndMinusZeroEqual: true,
>   collectAllFails: false
> };
> 
> function setBooleanDefault(property, obj, opts, defaults) {
>   obj[property] = typeof opts[property] !== "boolean" ? defaults[property] : 
> opts[property];
> }
> 
> var METHOD_PREFIX = "_check_";
> 
> function EQ(opts, a, b, path) {
>   opts = opts || {};
> 
>   setBooleanDefault("checkProtoEql", this, opts, DEFAULT_OPTIONS);
>   setBooleanDefault("plusZeroAndMinusZeroEqual", this, opts, DEFAULT_OPTIONS);
>   setBooleanDefault("checkSubType", this, opts, DEFAULT_OPTIONS);
>   setBooleanDefault("collectAllFails", this, opts, DEFAULT_OPTIONS);
> 
>   this.a = a;
>   this.b = b;
> 
>   this._meet = opts._meet || [];
> 
>   this.fails = opts.fails || [];
> 
>   this.path = path || [];
> }
> 
> function ShortcutError(fail) {
>   this.name = "ShortcutError";
>   this.message = "fail fast";
>   this.fail = fail;
> }
> 
> ShortcutError.prototype = Object.create(Error.prototype);
> 
> EQ.checkStrictEquality = function(a, b) 

Bug#948560: marked as done (Use of 'is' token for comparing string in knownhosts.py)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:36 +
with message-id 
and subject line Bug#948560: fixed in twisted 18.9.0-8
has caused the Debian Bug report #948560,
regarding Use of 'is' token for comparing string in knownhosts.py
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
948560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-twisted
Version: 18.9.0-6
Severity: normal


During update to new python3-twisted:

Setting up python3-twisted (18.9.0-6) ...
/usr/lib/python3/dist-packages/twisted/conch/client/knownhosts.py:492: 
SyntaxWarning: "is" with a literal. Did you mean "=="?
  if keytype is "EC":


It appears to be fixed in twisted 19.2.0+ tho:
https://github.com/twisted/twisted/commit/de05fee07a39d3415e4a3e9738d141b43b54f95c
which was released almost a year ago.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-twisted depends on:
ii  python3   3.7.5-3
ii  python3-attr  18.2.0-1
ii  python3-automat   0.6.0-1
ii  python3-constantly15.1.0-1
ii  python3-hamcrest  1.9.0-2
ii  python3-hyperlink 19.0.0-1
ii  python3-idna  2.6-2
ii  python3-incremental   16.10.1-3.1
ii  python3-openssl   19.0.0-1
ii  python3-service-identity  18.1.0-5
ii  python3-twisted-bin   18.9.0-6
ii  python3-zope.interface4.6.0-4

python3-twisted recommends no packages.

Versions of packages python3-twisted suggests:
pn  python3-glade2
pn  python3-gtk2  
pn  python3-pampy 
pn  python3-qt4   
ii  python3-serial3.4-5
pn  python3-tk
pn  python3-wxgtk2.8  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-8
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:14:09 +0100
Source: twisted
Architecture: source
Version: 18.9.0-8
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-8) unstable; urgency=high
 .
   * A no-change upload to set urgency to high since the upload
 fixes security issues.
 .
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - 

Bug#954808: marked as done (memcached: buffer overflow vulnerability)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:56:41 +
with message-id 
and subject line Bug#954808: fixed in memcached 1.6.2-1
has caused the Debian Bug report #954808,
regarding memcached: buffer overflow vulnerability
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: memcached
Version: 1.6.1-1
Severity: important
Tags: security upstream fixed-upstream
Forwarded: https://github.com/memcached/memcached/issues/629

Hi

Please see https://github.com/memcached/memcached/issues/629 for the
report. it is fixed in 1.6.2 upstream.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: memcached
Source-Version: 1.6.2-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated memcached 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:56:59 +
Source: memcached
Built-For-Profiles: nocheck
Architecture: source
Version: 1.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Closes: 954808
Changes:
 memcached (1.6.2-1) unstable; urgency=medium
 .
   * New upstream security releas. (Closes: #954808)
 
Checksums-Sha1:
 b44332ed7e05188367e9bfc6640f8af88576b293 1913 memcached_1.6.2-1.dsc
 a6a07f0433adaa13a3cafdf8c26acb640cdd001f 536527 memcached_1.6.2.orig.tar.gz
 1b75022c72fbabf07fca06ca5f2c393c023b8c5d 15272 memcached_1.6.2-1.debian.tar.xz
 93bf9ebe5f339619b2861a2e53ce7f4bb2bd86e9 6254 memcached_1.6.2-1_amd64.buildinfo
Checksums-Sha256:
 85b6a386fa09b33ff30709fb7c83ebb129790b62610b579f4610f4b0854d85a0 1913 
memcached_1.6.2-1.dsc
 06720118c40689be0b85249b3dcb23c6e6d5e3ce53893aca9faced264145168b 536527 
memcached_1.6.2.orig.tar.gz
 e59f14bdac720830ef7b585fae6b892055b7644e5be0ad54a98720a23a4e9dbd 15272 
memcached_1.6.2-1.debian.tar.xz
 79319c18679d0e37fa962d3a9a06a58d75c924afccdc59e80b69074603b1bdfa 6254 
memcached_1.6.2-1_amd64.buildinfo
Files:
 476f282a951b1cb7099f7a32470ccce1 1913 web optional memcached_1.6.2-1.dsc
 f4405eaff0448523406e868b32186a7d 536527 web optional 
memcached_1.6.2.orig.tar.gz
 ce2fa5b58f8c81c8604c3d5b56f2a02d 15272 web optional 
memcached_1.6.2-1.debian.tar.xz
 9593517547e6f5178eeaeb715edf2010 6254 web optional 
memcached_1.6.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl55FPwACgkQHpU+J9Qx
HlhYmw//eR7bdIKeXucwMG+OPBmhLckfxJeyfQZlasZJuokXalW4aRj3MuUs7Nm8
Lu2Zdfwzpp3UA73ucJVssp67ezRfHsf7lL3K+/1Xa6uUBXawtwmoQ0kQ3gnp1h3S
1dWnMJHkflH+2yw0vWxy4Ggbb1dEeHtu8ao/XPxHAI+V6s4Z4idHAOzNvQYMfh1h
u044KASZCJVt9TYzENa3Nzp48vS/AHBzyKqJlWyDYOGZloRsoPQVT4NuXqC5b0RX
xlf8hV5ZD5+0KsgKivR8F5R6DHQQmP6kq2lp6t4zyf4UfYE8GY4cf6UDde0c/FcM
7ezc0vwUoK+K+uInklBKvK/zh0+XIPiAFfPlt/GwDRR4hUpvK0SsZjk4aVcJFJnx
S/0FQszXSG4bHtoui/bOQTveDFNByUX10gIleIFItoku3N0BQUhwBD2exGm0rqgX
kO52R7vLdlT/Qdlo4HNyvWYzV/3Sh7HowBSfqKQ87Ny2ftv8iUtMGxFdP4SYTrlB
PkhmJ054Pr9jBBqWrjmR2RErys5iiEg+a4ZTvhh6az7HfV7Gk88JyvjZYLqOjE2o
uZBn893srZMaxeZgOSw+yjcegf4vBcMVLdAsML42x8eoCCaheZjDnnqMdt9TCFEh
O7VElixChiwHFN9QQC5G03XFRyD8eg9yJ3mJtDv4kGM4apBwB00=
=erB1
-END PGP SIGNATURE End Message ---

Bug#942389: marked as done (rollup 1.10 transition: should.js build fails with You have passed an unrecognized option)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:56:56 +
with message-id 
and subject line Bug#942389: fixed in should.js 13.2.3~dfsg-3
has caused the Debian Bug report #942389,
regarding rollup 1.10 transition: should.js build fails with You have passed an 
unrecognized option
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

package: should.js
version: 13.2.3~dfsg-1
severity: important

I think git repo is not having the latest commits, so not sure if -2 is 
different,


(!) You have passed an unrecognized option
Unknown CLI flag: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 
16, 17, 18. Allowed options: acorn, acornInjectPlugins, amd, 
assetFileNames, banner, c, cache, chunkFileNames, chunkGroupingSize, 
compact, config, context, d, dir, dynamicImportFunction, e, 
entryFileNames, environment, esModule, experimentalCacheExpiry, 
experimentalOptimizeChunks, experimentalTopLevelAwait, exports, extend, 
external, f, file, footer, format, freeze, g, globals, h, i, indent, 
inlineDynamicImports, input, interop, intro, m, manualChunks, 
moduleContext, n, name, namespaceToStringTag, noConflict, o, onwarn, 
outro, paths, perf, plugins, preferConst, preserveModules, 
preserveSymlinks, shimMissingExports, silent, sourcemap, 
sourcemapExcludeSources, sourcemapFile, strict, treeshake, v, w, watch


index.js → stdout...
'use strict';


--- End Message ---
--- Begin Message ---
Source: should.js
Source-Version: 13.2.3~dfsg-3
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated should.js 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 16:31:02 +0100
Source: should.js
Architecture: source
Version: 13.2.3~dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 942389 954585
Changes:
 should.js (13.2.3~dfsg-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Debian Janitor ]
   * Set fields Upstream-Contact in debian/copyright.
   * Remove obsolete fields Name, Contact from debian/upstream/metadata.
 .
   [ Xavier Guimard ]
   * Fix build for rollup ≥ 1 (Closes: #954585, #942389)
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
Checksums-Sha1: 
 44418bdd2c603d1af59a094114661f1bc184cea6 3776 should.js_13.2.3~dfsg-3.dsc
 047a0a2574c25a9871443c53b39f73eb32746e58 4880 
should.js_13.2.3~dfsg-3.debian.tar.xz
Checksums-Sha256: 
 2879482047849cf0a61d9f3d8f35e1d8aca9f20d648880b3abb9d09afc6ad816 3776 
should.js_13.2.3~dfsg-3.dsc
 2a39173d57796b53890c4a043db5e03fe74eb0a946785134599904069253ad2b 4880 
should.js_13.2.3~dfsg-3.debian.tar.xz
Files: 
 9590221e85c50ece253b0652fb3b03b1 3776 javascript optional 
should.js_13.2.3~dfsg-3.dsc
 98111776560fe4bbadd6c605b7790e43 4880 javascript optional 
should.js_13.2.3~dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl55AuMACgkQ9tdMp8mZ
7unzfg//WnK9ma00JXmMYJpHgyeq4SjwykehdpGf7y/Ts3ANtSATwj0vPCAjSsUl
yiXNZOLANJLRRwWHtiw2FzyMXb/KLBLvJLjPZFsy8TeOc0HwR0KHPXldRUalQHYi
Q9Vt2wsM8JbgS+ITVyUr7Bt0yEYGW4xvaUq9UeifAofQZnrwif27AZ3R3gmXR4ru
KtLMwYc6c+AZBJUYX5PAkOEYOq+aSIh12Mq+ZZK75DccdbblSRraM/myZtF329UP
YkoLcw3OScF+Zm2TUOIgJe8p8CszHYP8uJecrRaErs3ezoTaEMnzkrIA2bCKLIkm
ah9eaTGGKpmC0pNSokS0ZWPmy3YdjnLbOGTRBww9BXeN7FQJA8faN0Z5M+/B8mAA
OxgeL8sEQ4uafLpJNqnn1o0l9nkU1P9X0MowmiF7CIYaeZvoBF2p/fIUld4Ntd5x
QbG3OxwqcLggDlzBmW1C737iITEOJujgvh9uKEcN/VB67/lSMxfQAYstnv0mTDw3
CYOzkimgO+8v3TQXqRGbsV5OHMeoZr2NBMH2b8MT/tB95+0ByFxsMhZ6X+FetmCB
KUoNHX/Uy0xCqhJCHKvyETW2RLEIPoxgsITCRXXu7drvn2pRqlsoqCWBNzOk0KSw
lELoV4TopPlaIDltCnmr9GGZwJAo2/ucFCHafsgOgnxPDJRKG/g=
=Zhof
-END PGP SIGNATURE End Message ---

Bug#942869: marked as done (valadoc: README's content is "See README.md" but README.md is absent)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:58:04 +
with message-id 
and subject line Bug#942869: fixed in vala 0.48.2-1
has caused the Debian Bug report #942869,
regarding valadoc: README's content is "See README.md" but README.md is absent
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valadoc
Version: 0.42.5-1
Severity: normal

$ cat /usr/share/doc/valadoc/README 
See README.md
$ ls /usr/share/doc/valadoc/
changelog.Debian.gz  changelog.gz  copyright  NEWS.gz  README  THANKS


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (991, 'stable'), (500, 'stable-updates'), (500, 'stable-debug'), 
(500, 'oldstable-updates'), (500, 'oldstable-debug'), (500, 'oldstable'), (70, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-linux-latest-25 (SMP w/16 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages valadoc depends on:
ii  libc6  2.28-10
ii  libglib2.0-0   2.58.3-2
ii  libvala-0.42-0 0.42.5-1
ii  libvaladoc-0.42-0  0.42.5-1
ii  valac  0.42.5-1

valadoc recommends no packages.

valadoc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vala
Source-Version: 0.48.2-1
Done: Rico Tzschichholz 

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

Debian distribution maintenance software
pp.
Rico Tzschichholz  (supplier of updated vala 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:45:06 +0100
Source: vala
Binary: libvalacodegen-0.48-0 valac-bin valac valac-0.48-vapi vala-0.48-doc 
libvala-0.48-0 libvala-0.48-dev valadoc libvaladoc-0.48-0 libvaladoc-0.48-data 
libvaladoc-0.48-dev
Architecture: source
Version: 0.48.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Rico Tzschichholz 
Description:
 libvala-0.48-0 - C# like language for the GObject system - library
 libvala-0.48-dev - C# like language for the GObject system - development 
headers
 libvalacodegen-0.48-0 - internal package for C# like language for the GObject 
system
 libvaladoc-0.48-0 - API documentation generator for vala (library)
 libvaladoc-0.48-data - API documentation generator for vala (data)
 libvaladoc-0.48-dev - API documentation generator for vala (devel files)
 vala-0.48-doc - C# like language for the GObject system - documentation
 valac  - C# like language for the GObject system
 valac-0.48-vapi - C# like language for the GObject system - vapi files
 valac-bin  - internal package for C# like language for the GObject system
 valadoc- API documentation generator for vala
Closes: 916312 929915 942869
Changes:
 vala (0.48.2-1) unstable; urgency=medium
 .
   [ Rico Tzschichholz ]
   * New upstream release
   * Add README.md to docs (Closes: #942869)
   * Make valadoc recommend gtk-doc-tools (Closes: #916312)
 .
   [ Helmut Grohne ]
   * Simplify parallelity using more dh_auto_* (Closes: #929915)
Checksums-Sha1:
 2a4a14520ed351345530c459801fc4fe2417d907 2748 vala_0.48.2-1.dsc
 f95959d872dfd606749318c42f566ebb60e82a56 3433912 vala_0.48.2.orig.tar.xz
 215e2b9bd293ccf9fb9dda3de71b1d0a87662244 33436 vala_0.48.2-1.debian.tar.xz
Checksums-Sha256:
 a725ff66b9181cb8e2d9ab37cbadf48c440d6c93f8f65f5525d8b2e4116bf554 2748 
vala_0.48.2-1.dsc
 f095b0e624b8f4e5a426028ac255e477fad8c3b4c8cbbdebda8d6cd95bf79477 3433912 
vala_0.48.2.orig.tar.xz
 11b4bff12cd4c38785e70473fa85cfdd127ebcbd73643880cfee21914e1878f8 33436 
vala_0.48.2-1.debian.tar.xz
Files:
 b6d503a070ff14132637d863ab596af9 2748 devel optional vala_0.48.2-1.dsc
 81bac61d3b77591704b0714f12b69f3f 3433912 devel optional vala_0.48.2.orig.tar.xz
 04e41f2b25ad2a06b1c42fa780f8dbb5 33436 devel optional 

Bug#930389: marked as done (twisted: CVE-2019-12387)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:57:36 +
with message-id 
and subject line Bug#930389: fixed in twisted 18.9.0-8
has caused the Debian Bug report #930389,
regarding twisted: CVE-2019-12387
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twisted
Version: 18.9.0-3
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for twisted.

CVE-2019-12387[0]:
| In Twisted before 19.2.1, twisted.web did not validate or sanitize
| URIs or HTTP methods, allowing an attacker to inject invalid
| characters such as CRLF.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-12387
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12387
[1] 
https://github.com/twisted/twisted/commit/6c61fc4503ae39ab8ecee52d10f10ee2c371d7e2
[2] 

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: twisted
Source-Version: 18.9.0-8
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated twisted 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:14:09 +0100
Source: twisted
Architecture: source
Version: 18.9.0-8
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 930389 930626 948560 953950
Changes:
 twisted (18.9.0-8) unstable; urgency=high
 .
   * A no-change upload to set urgency to high since the upload
 fixes security issues.
 .
 twisted (18.9.0-7) unstable; urgency=medium
 .
   [ Marc Deslauriers ]
   * SECURITY UPDATE: incorrect URI and HTTP method validation
 - debian/patches/CVE-2019-12387.patch: prevent CRLF injections in
   src/twisted/web/_newclient.py, src/twisted/web/client.py,
   src/twisted/web/test/injectionhelpers.py,
   src/twisted/web/test/test_agent.py,
   src/twisted/web/test/test_webclient.py.
 - CVE-2019-12387
 - Closes: #930389
   * SECURITY UPDATE: incorrect cert validation in XMPP support
 - debian/patches/CVE-2019-12855-*.patch: upstream patches to implement
   certificate checking.
 - CVE-2019-12855
 - Closes: #930626
   * SECURITY UPDATE: HTTP/2 denial of service issues
 - debian/patches/CVE-2019-951x.patch: buffer outbound control frames
   and timeout invalid clients in src/twisted/web/_http2.py,
   src/twisted/web/error.py, src/twisted/web/http.py,
   src/twisted/web/test/test_http.py,
   src/twisted/web/test/test_http2.py.
 - CVE-2019-9511
 - CVE-2019-9514
 - CVE-2019-9515
   * SECURITY UPDATE: request smuggling attacks
 - debian/patches/CVE-2020-1010x-pre1.patch: refactor to reduce
   duplication in src/twisted/web/test/test_http.py.
 - debian/patches/CVE-2020-1010x.patch: fix several request smuggling
   attacks in src/twisted/web/http.py,
   src/twisted/web/test/test_http.py.
 - CVE-2020-10108
 - CVE-2020-10109
 - Closes: #953950
 .
   [ Emmanuel Arias ]
   * Add patch to fix SyntaxWarning (Closes: #948560).
 .
   [ Moritz Muehlenhoff  ]
   * Remove Suggests on python-gtk2/python-glade2, which is being removed.
Checksums-Sha1:
 240d4f043a58ca6a557561a43364f61ff57324cd 3363 twisted_18.9.0-8.dsc
 1919f66c3d525e6b0e94b07bf8a419c208d5270c 41776 twisted_18.9.0-8.debian.tar.xz
Checksums-Sha256:
 53083bd6a882bc1dc919b9fed4647c4d9d9356aea18cbdc5ec0de280dea09d3d 3363 
twisted_18.9.0-8.dsc
 820329295f00727ed2aed992adc841c13adf8d54425bfbb04a37941d344fc9ba 41776 
twisted_18.9.0-8.debian.tar.xz
Files:
 03a3587d903c592ad422874ee88eb66d 3363 python optional twisted_18.9.0-8.dsc
 1ada38febf5d794ac88ab24972d0fbf8 41776 

Bug#916312: marked as done (valadoc: Should depend on gtk-doc-tools for the gtkdoc doclet)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:58:04 +
with message-id 
and subject line Bug#916312: fixed in vala 0.48.2-1
has caused the Debian Bug report #916312,
regarding valadoc: Should depend on gtk-doc-tools for the gtkdoc doclet
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
916312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valadoc
Version: 0.30.0~git20160518-2
Severity: normal

Dear Maintainer,

I think valadoc should depend on gtk-doc-tools or at least recommend it.
Without it, using the gtkdoc doclet (--doclet gtkdoc) leads to a fatal
error:

gtkdoc-scan:  error: Failed to execute child process "gtkdoc-scan" (No such 
file or directory)

Installing the gtk-doc-tools package fixes the issue.

I would expect the various doclets to work out of the box after
installing the valadoc package, but in any case I believe recommending
the required packages which make the options work would make a lot of
sense.

Regards,

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages valadoc depends on:
ii  libc6   2.24-11+deb9u3
ii  libcdt5 2.38.0-17
ii  libcgraph6  2.38.0-17
ii  libgee-0.8-20.18.1-1
ii  libglib2.0-02.50.3-2
ii  libgvc6 2.38.0-17
ii  libvala-0.34-0  0.34.7-1
ii  libvaladoc3 0.30.0~git20160518-2

valadoc recommends no packages.

Versions of packages valadoc suggests:
ii  valac  0.34.7-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: vala
Source-Version: 0.48.2-1
Done: Rico Tzschichholz 

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

Debian distribution maintenance software
pp.
Rico Tzschichholz  (supplier of updated vala 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 20:45:06 +0100
Source: vala
Binary: libvalacodegen-0.48-0 valac-bin valac valac-0.48-vapi vala-0.48-doc 
libvala-0.48-0 libvala-0.48-dev valadoc libvaladoc-0.48-0 libvaladoc-0.48-data 
libvaladoc-0.48-dev
Architecture: source
Version: 0.48.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Rico Tzschichholz 
Description:
 libvala-0.48-0 - C# like language for the GObject system - library
 libvala-0.48-dev - C# like language for the GObject system - development 
headers
 libvalacodegen-0.48-0 - internal package for C# like language for the GObject 
system
 libvaladoc-0.48-0 - API documentation generator for vala (library)
 libvaladoc-0.48-data - API documentation generator for vala (data)
 libvaladoc-0.48-dev - API documentation generator for vala (devel files)
 vala-0.48-doc - C# like language for the GObject system - documentation
 valac  - C# like language for the GObject system
 valac-0.48-vapi - C# like language for the GObject system - vapi files
 valac-bin  - internal package for C# like language for the GObject system
 valadoc- API documentation generator for vala
Closes: 916312 929915 942869
Changes:
 vala (0.48.2-1) unstable; urgency=medium
 .
   [ Rico Tzschichholz ]
   * New upstream release
   * Add README.md to docs (Closes: #942869)
   * Make valadoc recommend gtk-doc-tools (Closes: #916312)
 .
   [ Helmut Grohne ]
   * Simplify parallelity using more dh_auto_* (Closes: #929915)
Checksums-Sha1:
 2a4a14520ed351345530c459801fc4fe2417d907 2748 vala_0.48.2-1.dsc
 f95959d872dfd606749318c42f566ebb60e82a56 3433912 vala_0.48.2.orig.tar.xz
 215e2b9bd293ccf9fb9dda3de71b1d0a87662244 33436 vala_0.48.2-1.debian.tar.xz
Checksums-Sha256:
 a725ff66b9181cb8e2d9ab37cbadf48c440d6c93f8f65f5525d8b2e4116bf554 2748 
vala_0.48.2-1.dsc
 

Processed: closing 916873

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 916873
Bug #916873 [python-twisted-core] python-twisted-core: Incorrect versioned 
dependency on python-attr
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
916873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#951496: marked as done (libffi: libffi 3.3 breaks OpenJDK Zero on powerpc)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:54:54 +
with message-id 
and subject line Bug#951496: fixed in libffi 3.3-4
has caused the Debian Bug report #951496,
regarding libffi: libffi 3.3 breaks OpenJDK Zero on powerpc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
951496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libffi
Version: 3.3-3
Severity: important
Tags: upstream
User: debian-powe...@lists.debian.org
Usertags: powerpc

Hi!

Since libffi 3.3 breaks OpenJDK Zero on powerpc [1], I have reverted the 
breaking
changes in a manual upload (3.3-3+powerpc) in Debian Ports and have set the 
package
to "not-for-us" until the issue has been fixed upstream.

Once the issue has been fixed and this bug is closed, I will mark the package 
for
building again on powerpc.

Thanks,
Adrian

> [1] https://github.com/libffi/libffi/issues/536

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: libffi
Source-Version: 3.3-4
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libffi 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 21:28:54 +0100
Source: libffi
Architecture: source
Version: 3.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 951496
Changes:
 libffi (3.3-4) unstable; urgency=medium
 .
   * Update powerpc sysv assembly for ffi_powerpc.h changes (#541).
 Closes: #951496.
Checksums-Sha1:
 0efbe23e79d8239fa9e5603c76854aca1025f526 1932 libffi_3.3-4.dsc
 8f26c02e8de73c5791f48b3e42a5f9ea96b4b8e3 9016 libffi_3.3-4.debian.tar.xz
 3ed8c0ae9ae3fd3ab74deac5c959781a38fabd7b 6378 libffi_3.3-4_source.buildinfo
Checksums-Sha256:
 4190ad8e7ae9167a0c67c5926bc3705acb191745cca93ef845dbc06fc097f380 1932 
libffi_3.3-4.dsc
 0e8a6d9d87202d04d7646178479c3d365a845f9723da26625d533a169b378100 9016 
libffi_3.3-4.debian.tar.xz
 2b479effaa39d8510300080644e5e3c6c8c3bd2e61914fe97b4712f71d27743e 6378 
libffi_3.3-4_source.buildinfo
Files:
 5385839e71ed62c59feccd19bd727f7f 1932 libs optional libffi_3.3-4.dsc
 7c71abd2c1f277241f88938f584e074b 9016 libs optional libffi_3.3-4.debian.tar.xz
 98d4757c339c9c5431b0dadbcc0c3d8b 6378 libs optional 
libffi_3.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl55HVUQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9d92EAC2et6r1j1xyrnIh91iHYklfKiVk6c6Vo8c
NQ7Tp3DGNX3XPwQQNkcPPuj5JbvORIyUMcwd+0tUpHuL7TG78nSsIIcYJvWcsekf
jdePdiDDPDaTdQMaRVRLnaz2ZCcNIv/3TfQL8PvaQpDw+e+Ltk7fKc7TWEavpcdm
MwvNmK2+LJOtr/e2dYT1+tzm4vieQWFdj2XGZW5N/o4JlCjaY4KJ+U+aMQJrcZpA
pOplNB4ts23Fpj9nRfLKGSYY79EXGBJZMcE4Rj3/+bK6ZN/H69hgtliT1/N4m0ov
ZoCLgKEHthCuY/Mvo24o6YLk0sOaFEiGTgedW/6w0to8d1dYzuNwiW04lLjDuAS0
BS5IVnp9MqOOm6X7+N/zL54jRTvS+NWyrq5csp8bwDE+owzRua8fCCEreLtJVBPK
scTQXUTsZgScdjDQvssrIV4e+E93uelfim8xaTL2Ms1B0VzZt0husob86HPefH7f
B30sslvBFgXySigs1/g8DPj6xHnZOCemNbfc9b9a+T6KBsE7LPWltOtfpp156NHo
c2+rpKHRpndOLNk7eg2ShkUZEs2Y+gYRawiECgngij1G2Rd04KmTfY49+bfiJnDc
hHskEzBwJHdbKMNkduqTjk8X0AMA5tAoqDUKo7VqBsUwIv54ZyopOjpkYWfLStU2
q/Z0o7U/6Q==
=5cd7
-END PGP SIGNATURE End Message ---

Processed: closing 504754

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 504754
Bug #504754 [audacious-plugins] audacious: Please include a Debian skin like 
xmms did
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
504754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954807: marked as done (apt upgrade sometimes marks packages as manually installed)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 20:51:40 +0100
with message-id <20200323204831.ga669...@debian.org>
and subject line Re: Bug#954807: apt upgrade sometimes marks packages as 
manually installed
has caused the Debian Bug report #954807,
regarding apt upgrade sometimes marks packages as manually installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 2.0.0
Severity: normal


When a package listed as an argument to apt upgrade is already at the
requested version, it is marked as manually installed:

# apt-mark showmanual libc6
# apt upgrade libc6
Reading package lists... Done
Building dependency tree
Reading state information... Done
libc6 is already the newest version (2.30-2).
libc6 set to manually installed.
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# apt-mark showmanual libc6
libc6
#

Please do not mark packages listed as arguments to apt upgrade as
manually installed.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'unstable'), (600, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8),
LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages apt depends on:
ii  adduser 3.118
ii  debian-archive-keyring  2019.1
ii  gpgv2.2.19-3
ii  libapt-pkg6.0   2.0.0
ii  libc6   2.30-2
ii  libgcc-s1   10-20200312-2
ii  libgnutls30 3.6.12-2
ii  libseccomp2 2.4.3-1
ii  libstdc++6  10-20200312-2

Versions of packages apt recommends:
ii  ca-certificates  20190110

Versions of packages apt suggests:
ii  apt-doc  2.0.0
pn  aptitude | synaptic | wajig  
ii  dpkg-dev 1.19.7
ii  gnupg2.2.19-3
pn  powermgmt-base   

-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Mar 23, 2020 at 08:26:06PM +0100, Piotr Engelking wrote:
> Package: apt
> Version: 2.0.0
> Severity: normal
> 
> 
> When a package listed as an argument to apt upgrade is already at the
> requested version, it is marked as manually installed:
> 
> # apt-mark showmanual libc6
> # apt upgrade libc6
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> libc6 is already the newest version (2.30-2).
> libc6 set to manually installed.
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> # apt-mark showmanual libc6
> libc6
> #
> 
> Please do not mark packages listed as arguments to apt upgrade as
> manually installed.

This is not a bug, but a feature. You ran the equivalent of 
apt install libc6 && apt upgrade, and that causes libc6 to be
manually installed, because you manually requested it to be
installed.

It's not a feature I agree with, even in the "install" case, but I
can understand the argument for having it. But then, I do have to
use that a bit more often than the average user probably, because
I do need to tweak the solver choices or help it along by giving it
more hints.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en--- End Message ---

Bug#954751: marked as done (libgcc-10-dev: Missing include/sanitizer/)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 19:34:32 +
with message-id 
and subject line Bug#954751: fixed in gcc-10 10-20200323-1
has caused the Debian Bug report #954751,
regarding libgcc-10-dev: Missing include/sanitizer/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgcc-10-dev
Version: 10-20200321-1

Hi,

Since last upgrade of my sid chroot, the include directory
"include/sanitizer/" is missing from libgcc-10-dev:amd64.

Before, there was:
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/asan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/common_interface_defs.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/lsan_interface.h
/usr/lib/gcc/x86_64-linux-gnu/10/include/sanitizer/tsan_interface.h

Regards,
Arnaud Giersch
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200323-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:01:05 +0100
Source: gcc-10
Architecture: source
Version: 10-20200323-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954438 954751
Changes:
 gcc-10 (10-20200323-1) unstable; urgency=medium
 .
   * GCC snapshot, taken from the trunk (20200323, 497498c878d).
   * libgcc-N-dev: Include sanitizer headers again. Closes: #954751.
   * gm2: Define lang_register_spec_functions for jit. Closes: #954438.
Checksums-Sha1:
 65fb895e7ec903c5c2ed846919f716ded9a9a09e 27934 gcc-10_10-20200323-1.dsc
 bb8dbbcfdd78be675945a216724df7a5ec9b0098 89032771 
gcc-10_10-20200323.orig.tar.gz
 3cc0f1efd3d6d34f32ecc82048e21456047faaa4 556704 
gcc-10_10-20200323-1.debian.tar.xz
 f1b5ffc91302ab5bfc4b5770a4a50b47a1d82acc 10999 
gcc-10_10-20200323-1_source.buildinfo
Checksums-Sha256:
 a4533b73ae1fb8db3a01efe96595e763062ae5be1648f67cc840e83c7cc94c4b 27934 
gcc-10_10-20200323-1.dsc
 f363a4d542bae2e12397eda80e5b8c416713c06ca2cb053a6d38c1b08086b11b 89032771 
gcc-10_10-20200323.orig.tar.gz
 a340266d6522964cfe33f4b252d379a600360c7a676adb31d37f8e419b8e9fdc 556704 
gcc-10_10-20200323-1.debian.tar.xz
 d7bdd31a2aefeed0b81866a3141fa5a1ffd7de313f9389137d84595c5ea55082 10999 
gcc-10_10-20200323-1_source.buildinfo
Files:
 a8e23fa4d91ce4abb5d6e31d4bf13808 27934 devel optional gcc-10_10-20200323-1.dsc
 a633781b4d6cf5b57a023e8dad69608e 89032771 devel optional 
gcc-10_10-20200323.orig.tar.gz
 1d13a088737968c6eac6e3f420232feb 556704 devel optional 
gcc-10_10-20200323-1.debian.tar.xz
 8a2a7e99722cca626c6ad73f4f7f18cb 10999 devel optional 
gcc-10_10-20200323-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl54+gMQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9QSDD/9SZC2fMHDAm7MGf6z4jnie5ED7dJtNnlev
WSR4wqRxFKerKWkRMuGF6zRAsVZoU1UPqWKWhXrZ7Pz4uOCnZsDcE5EnQmdtxlcq
uFYNbbOApR4HSC8atn/UTwXcrLa3rD9a713drYBTQmULn34ryiGsJJ+vsfBqFe/5
GyN0WNkBKrwb/775dCW/0ebJaZKR5NGpvdzYZ2Znk+igUVtcOcpKHMCO4lWkExEs
qRGTjUgz4/fT2LJyOwnt5jxmUKGRvsuPCQVceYfqAS8mHJ9bfDfPgqMnzRp9wCCx
mfSyTf00+PtefY3unhjxaOFcemU1kSmFs3zp729ruNel/MpyeiCF1w3km6zCgRo4
zCxtC+NgATWYEbji7GUfs6HkUEl8T9ZwnJj7wU1Qj0JXmLx8dQuFqJsdoZ94EJRW
UzDUh2s35DV88mXapuwweYRrCGMCw7zC5TTXXAdxuzX/zKxn1JN9Qd8aepyhrZqn
dPEkxHGvXQjiPSrc8OBUdCD/UZ/EUng8NZLqzSygugL7zvUpSdysDORv7phdXtUb
1SmaxfPu7cjyOF8YKCuzldVkrl9xYHuLu3CW7EBIKqrZt5SFSe7tYrxfF/V2UIjG
13utiDUOgZxdEkvfZSfj/Iu9ZK4zJbylRwPvCX2Slqsi6EQtwTQNfoyCrg6gJLwE
/0FYR+o2uA==
=dFEl
-END PGP SIGNATURE End Message ---

Bug#954438: marked as done (libgccjit0: GCCJIT leads to linking error)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 19:34:32 +
with message-id 
and subject line Bug#954438: fixed in gcc-10 10-20200323-1
has caused the Debian Bug report #954438,
regarding libgccjit0: GCCJIT leads to linking error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgccjit0
Version: 10-20200312-2
Severity: important

Dear Maintainer,

libgccjit0 leads to linking error, I have the following C source code: 

#include 
#include 
#include 

int main(int argc, char **argv) {
gcc_jit_context *ctxt;
ctxt = gcc_jit_context_acquire();
gcc_jit_rvalue *args[2]; 
printf("%5.8lf\n", sin(30)); 
return 0;
}


and I compiled it using the following command line:

gcc-10 test.c -o test -lgccjit

or 

gcc-10 test.c -lgccjit -o test 

leads to the same error message:

/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/libgccjit.so: undefined reference 
to `lang_register_spec_functions()'
collect2: error: ld returned 1 exit status

However, exactly the same gcc and gccjit version on Fedora Rawhide work as 
intened. 

It seems a gccjit issue rather than a ld issue. 

Thanks, 
Gong-Yi. 



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgccjit0 depends on:
ii  binutils   2.34-5
ii  gcc-10-base10-20200312-2
ii  libc6  2.30-2
ii  libgcc-10-dev  10-20200312-2
ii  libgmp10   2:6.2.0+dfsg-4
ii  libisl22   0.22.1-1
ii  libmpc31.1.0-1
ii  libmpfr6   4.0.2-1
ii  libzstd1   1.4.4+dfsg-3
ii  zlib1g 1:1.2.11.dfsg-2

libgccjit0 recommends no packages.

libgccjit0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10-20200323-1
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:01:05 +0100
Source: gcc-10
Architecture: source
Version: 10-20200323-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 954438 954751
Changes:
 gcc-10 (10-20200323-1) unstable; urgency=medium
 .
   * GCC snapshot, taken from the trunk (20200323, 497498c878d).
   * libgcc-N-dev: Include sanitizer headers again. Closes: #954751.
   * gm2: Define lang_register_spec_functions for jit. Closes: #954438.
Checksums-Sha1:
 65fb895e7ec903c5c2ed846919f716ded9a9a09e 27934 gcc-10_10-20200323-1.dsc
 bb8dbbcfdd78be675945a216724df7a5ec9b0098 89032771 
gcc-10_10-20200323.orig.tar.gz
 3cc0f1efd3d6d34f32ecc82048e21456047faaa4 556704 
gcc-10_10-20200323-1.debian.tar.xz
 f1b5ffc91302ab5bfc4b5770a4a50b47a1d82acc 10999 
gcc-10_10-20200323-1_source.buildinfo
Checksums-Sha256:
 a4533b73ae1fb8db3a01efe96595e763062ae5be1648f67cc840e83c7cc94c4b 27934 
gcc-10_10-20200323-1.dsc
 f363a4d542bae2e12397eda80e5b8c416713c06ca2cb053a6d38c1b08086b11b 89032771 
gcc-10_10-20200323.orig.tar.gz
 a340266d6522964cfe33f4b252d379a600360c7a676adb31d37f8e419b8e9fdc 556704 
gcc-10_10-20200323-1.debian.tar.xz
 d7bdd31a2aefeed0b81866a3141fa5a1ffd7de313f9389137d84595c5ea55082 10999 
gcc-10_10-20200323-1_source.buildinfo
Files:
 a8e23fa4d91ce4abb5d6e31d4bf13808 27934 devel optional gcc-10_10-20200323-1.dsc
 a633781b4d6cf5b57a023e8dad69608e 89032771 devel optional 
gcc-10_10-20200323.o

Bug#944066: marked as done (golang-github-nrdcg-goinwx: Please update/expand "Andrew" copyright holder)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 19:04:16 +
with message-id 
and subject line Bug#944066: fixed in golang-github-nrdcg-goinwx 0.6.1-3
has caused the Debian Bug report #944066,
regarding golang-github-nrdcg-goinwx: Please update/expand "Andrew" copyright 
holder
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
944066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-nrdcg-goinwx
Version: 0.6.1-1
Severity: wishlist
X-Debbugs-CC: Thorsten Alteholz , 
ftpmas...@debian.org

Hi,

I just ACCEPTed golang-github-nrdcg-goinwx from NEW but was wondering 
if you could find a nicer copyright holder name than just "Andrew."

Whatever the legality of this (the discussion I will leave to others
to dissect ad nauseum…) it just doesn't feel Pquite right to me.


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: golang-github-nrdcg-goinwx
Source-Version: 0.6.1-3
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-nrdcg-goinwx 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 18:43:01 +0100
Source: golang-github-nrdcg-goinwx
Architecture: source
Version: 0.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 944066
Changes:
 golang-github-nrdcg-goinwx (0.6.1-3) unstable; urgency=medium
 .
   * debian/copyright: add full name of Andrew (Closes: #944066)
   * debian/control: use dh12
   * debian/control: bump standard to 4.5.0 (no changes)
Checksums-Sha1:
 0ea3a4ef053932a3ef1a9cdbb2dd853bea052ed7 2471 
golang-github-nrdcg-goinwx_0.6.1-3.dsc
 5d6527219ab7df99a773166d725301e92b51661b 2152 
golang-github-nrdcg-goinwx_0.6.1-3.debian.tar.xz
 a80f0f66857c4530fc9eb1d88244e2ea6a953daa 6308 
golang-github-nrdcg-goinwx_0.6.1-3_amd64.buildinfo
Checksums-Sha256:
 b0355870484e6b11d36d19c261505d8ef98283a785e1eda588bded2b21550298 2471 
golang-github-nrdcg-goinwx_0.6.1-3.dsc
 d8d36a614d5fdf40bdf1fe553313a9c1aa17b224d2919da5eac3217a09932963 2152 
golang-github-nrdcg-goinwx_0.6.1-3.debian.tar.xz
 92af3aa5293739b7fe70bfc29381437f0cdb0284e02c0c9ca74b0b7f434a5abb 6308 
golang-github-nrdcg-goinwx_0.6.1-3_amd64.buildinfo
Files:
 d0074f7c77ce019c3d7f317fe7ea74b1 2471 devel optional 
golang-github-nrdcg-goinwx_0.6.1-3.dsc
 d51b86f998ba488bc0220933078d963c 2152 devel optional 
golang-github-nrdcg-goinwx_0.6.1-3.debian.tar.xz
 67b66b0f6bce0043b859adeb79e7eb43 6308 devel optional 
golang-github-nrdcg-goinwx_0.6.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl55Au1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR0/VEAC5ugMGeADQmjItMl80t0CP1UMi/BSl
gUPSuBF2IDD0Q0sa2EvopbubxFv7W1UpHEBQlqfiLL7Zialu8jHfyfHhWhj1ZZ65
Cv7zbs7O2xc9Bq9fo9kimYransc0zKfznF3TZnbARtQsO4Hdg3bHhZf/wiRnUDTz
x2KeRGaTlhilnqzA2HuwSmydZcg6/PzfHGvzkf4c6ysW7q4/a507vuUUiw7lju9r
oI0+kLYCM71X22vrACYLQdfoXnAHlpkBap7sgMZOD+IYOcCEskMri9aN9+1OCQ9p
/p4BgpEvfX716BaYsazeCGnPMbQr0fuWonUV/b7lXiOie0Hx7V8RZoYooxvKxB+4
4SZaLta1oijDg/dBRoCuaGh0LdNkUCvE3laHvA/XVjpwbUUKghfNIghUlwmyrlD/
qEpBnQ/T2oHScbrdPt3QeK7yTMLTKHG6+TopYoO22spRycKoyTcc1cSLt6FlajL2
LbAimnODAZdGHnyXt2g7fnbA7j0Oivm/6cuKbAJAo0teOGZN34CWfqwrGsueK3/+
lhMe7EcMlyYReBj/Ngp8Uet9kNrd8WS+gZ4C0macbWrMKTzYA/dBa6S5CgzhC34m
ldhsIeL9rd2F5/TYbAS8S4GFQIEGAG+C71Qq87lxmr3EPc0oFkqcN99fc+YhPKQN
rl2txkWS4KYHig==
=ciXL
-END PGP SIGNATURE End Message ---

Bug#954242: marked as done (qgis-providers: postinst failure: free(): invalid pointer)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 19:58:02 +0100
with message-id 
and subject line Re: Bug#954242: qgis-providers: postinst failure: free(): 
invalid pointer
has caused the Debian Bug report #954242,
regarding qgis-providers: postinst failure: free(): invalid pointer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qgis-providers
Version: 3.10.3+dfsg-1+b1
Severity: serious


Dear Maintainer,

here is the problem:

Setting up qgis-providers (3.10.3+dfsg-1+b1) ...
free(): invalid pointer
Aborted (core dumped)
dpkg: error processing package qgis-providers (--configure):
 installed qgis-providers package post-installation script subprocess returned 
error exit status 134


Note that my system has glibc 2.31 from experimental and the following 
environment variables are set:

MALLOC_PERTURB_=117
MALLOC_CHECK_=3


Running "valgrind /usr/lib/qgis/crssync" finds many memory errors, and the 
first one is:

==34194== Invalid free() / delete / delete[] / realloc()
==34194==at 0x4838EAB: operator delete(void*) (vg_replace_malloc.c:586)
==34194==by 0x76643D5: __cxa_finalize (cxa_finalize.c:83)
==34194==by 0xEC8FF62: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.15.3.1)
==34194==by 0x400FF92: _dl_fini (dl-fini.c:138)
==34194==by 0x7663DD6: __run_exit_handlers (exit.c:108)
==34194==by 0x7663F89: exit (exit.c:139)
==34194==by 0x764CCF1: (below main) (libc-start.c:342)
==34194==  Address 0x1796f740 is 0 bytes inside a block of size 17 free'd
==34194==at 0x4838EAB: operator delete(void*) (vg_replace_malloc.c:586)
==34194==by 0x76643D5: __cxa_finalize (cxa_finalize.c:83)
==34194==by 0x7B12702: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0)
==34194==by 0x400FF92: _dl_fini (dl-fini.c:138)
==34194==by 0x7663DD6: __run_exit_handlers (exit.c:108)
==34194==by 0x7663F89: exit (exit.c:139)
==34194==by 0x764CCF1: (below main) (libc-start.c:342)
==34194==  Block was alloc'd at
==34194==at 0x4837DEF: operator new(unsigned long) (vg_replace_malloc.c:344)
==34194==by 0x7B0E91F: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0)
==34194==by 0x7B11A2C: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0)
==34194==by 0x400FC09: call_init.part.0 (dl-init.c:72)
==34194==by 0x400FD08: call_init (dl-init.c:30)
==34194==by 0x400FD08: _dl_init (dl-init.c:119)
==34194==by 0x40010C9: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qgis-providers depends on:
ii  dpkg  1.20.0
ii  libc6 2.31-0experimental0
ii  libexpat1 2.2.9-1
ii  libgcc-s1 10-20200312-2
ii  libgdal26 3.0.4+dfsg-1+b1
ii  libhdf5-103   1.10.4+repack-11
ii  libnetcdf15   1:4.7.3-1
ii  libpq512.2-1+b1
ii  libqca-qt5-2  2.2.1-2
ii  libqca-qt5-2-plugins  2.2.1-2
ii  libqgis-core3.10.33.10.3+dfsg-1+b1
ii  libqgis-gui3.10.3 3.10.3+dfsg-1+b1
ii  libqscintilla2-qt5-15 2.11.2+dfsg-6
ii  libqt5core5a [qtbase-abi-5-12-5]  5.12.5+dfsg-9
ii  libqt5gui55.12.5+dfsg-9
ii  libqt5network55.12.5+dfsg-9
ii  libqt5sql55.12.5+dfsg-9
ii  libqt5sql5-sqlite 5.12.5+dfsg-9
ii  libqt5webkit5 5.212.0~alpha4-1
ii  libqt5widgets55.12.5+dfsg-9
ii  libqt5xml55.12.5+dfsg-9
ii  libspatialite75.0.0~beta0-1~exp4
ii  libsqlite3-0  3.31.1-4
ii  libstdc++610-20200312-2
ii  libxml2   2.9.10+dfsg-4
ii  qgis-providers-common 3.10.3+dfsg-1

qgis-providers recommends no packages.

qgis-providers suggests no packages.

-- no debconf information

-- 
Laurent.
--- End Message ---
--- Begin Message 

Bug#952024: marked as done (ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:51:26 +
with message-id 
and subject line Bug#952024: fixed in ruby-rspec-puppet 2.7.8-2
has caused the Debian Bug report #952024,
regarding ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec-puppet
Version: 2.7.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> LoadError:
>   libfacter was not found. Please make sure it was installed to the expected 
> location.
>   cannot load such file -- libfacter.so
> # ./lib/rspec-puppet.rb:1:in `'
> # ./spec/spec_helper.rb:11:in `'
> # ./spec/unit/monkey_patches_spec.rb:1:in `'
> # --
> # --- Caused by: ---
> # LoadError:
> #   cannot load such file -- libfacter.so
> #   ./lib/rspec-puppet.rb:1:in `'
> 
> Finished in 0.4 seconds (files took 2.18 seconds to load)
> 0 examples, 0 failures, 87 errors occurred outside of examples
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-rspec-puppet_2.7.8-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-rspec-puppet
Source-Version: 2.7.8-2
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-rspec-puppet 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 00:40:31 +0100
Source: ruby-rspec-puppet
Architecture: source
Version: 2.7.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Daniel Leidert 
Closes: 952024
Changes:
 ruby-rspec-puppet (2.7.8-2) unstable; urgency=medium
 .
   * Team upload.
   * d/copyright (Source): Use github address.
   * d/upstream/metadata: Set Archive: GitHub.
   * d/patches/002_Fix-Ruby2.7-FrozenError.patch: Add new patch.
 - Fix FrozenError running tests with Ruby 2.7 (closes: #952024).
   * d/patches/series: Enable new patch.
   * d/upstream/metadata: Add some missing fields.
Checksums-Sha1:
 e86c9392461dfccb96d96a78ee35cf4440b771dd 2106 ruby-rspec-puppet_2.7.8-2.dsc
 239a5ddfef2d4968db63005db9c92bbe2d7beb35 4404 
ruby-rspec-puppet_2.7.8-2.debian.tar.xz
 b6669bfe51cbf381dec64cd60815e496117750b7 9959 
ruby-rspec-puppet_2.7.8-2_amd64.buildinfo
Checksums-Sha256:
 6a0525e9bed305902778628dca7af45e9e1568943c4102bc213de015abdae638 2106 
ruby-rspec-puppet_2.7.8-2.dsc
 21ca5089503be0f80bdaed43ae30dc8d8164bf41518f3f3a6734590248a34f5e 4404 
ruby-rspec-puppet_2.7.8-2.debian.tar.xz
 cd598314a29e8938cbb7691231d980781f177944a6d03097ad5230009764e1f3 9959 
ruby-rspec-puppet_2.7.8-2_amd64.buildinfo
Files:
 51a64950511c2fc564cf586bbedcf7a5 2106 ruby optional 
ruby-rspec-puppet_2.7.8-2.dsc
 3b2b31286633d33221a2b0f433ac4623 4404 ruby optional 
ruby-rspec-puppet_2.7.8-2.debian.tar.xz
 9747766d22b41dd8ffba3a784682b537 9959 ruby optional 
ruby-rspec-puppet_2.7.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl54/w8ACgkQS80FZ8KW

Bug#937197: marked as done (openconnect: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:19:27 +
with message-id 
and subject line Bug#937197: fixed in openconnect 8.05-1
has caused the Debian Bug report #937197,
regarding openconnect: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
937197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openconnect
Version: 8.02-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:openconnect

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 8.05-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated openconnect 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Mar 2020 19:13:13 +
Source: openconnect
Architecture: source
Version: 8.05-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 935198 937197
Changes:
 openconnect (8.05-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/8.05' (Closes: #935198)
   * Drop patches, merged upstream in v8.05
   * Build-depend on Python3, v8.05 can build documentation with it now
 (Closes: #937197)
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.0, no changes
   * Add myself to Uploaders
   * Addn Lintian override for hipreport-android.sh
   * Drop rules for dbgsym migration
   * Add libopenconnect.la to d/not-installed
Checksums-Sha1:
 6dc01402beac6363b96fb1cb47e3f046fc369561 2574 

Bug#943354: marked as done (New upstream release)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:19:27 +
with message-id 
and subject line Bug#935198: fixed in openconnect 8.05-1
has caused the Debian Bug report #935198,
regarding New upstream release
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openconnect
Version: 8.02-1
Severity: wishlist

8.0.4 was released a few months ago, and has support for Pulse Connect Secure, 
which is something my company's VPN now requires. It'd be great for the package 
to be updated to at least that version.

Thanks,
-- 
Jonny Lamb
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 8.05-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated openconnect 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Mar 2020 19:13:13 +
Source: openconnect
Architecture: source
Version: 8.05-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 935198 937197
Changes:
 openconnect (8.05-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/8.05' (Closes: #935198)
   * Drop patches, merged upstream in v8.05
   * Build-depend on Python3, v8.05 can build documentation with it now
 (Closes: #937197)
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.0, no changes
   * Add myself to Uploaders
   * Addn Lintian override for hipreport-android.sh
   * Drop rules for dbgsym migration
   * Add libopenconnect.la to d/not-installed
Checksums-Sha1:
 6dc01402beac6363b96fb1cb47e3f046fc369561 2574 openconnect_8.05-1.dsc
 7fc0ed9cb34b401740100f36695036d256c0 1922100 openconnect_8.05.orig.tar.gz
 0dce024e00efe199fad25d7e741c37fb760aee98 833 openconnect_8.05.orig.tar.gz.asc
 97ffe2f6b8a48aab7deb631746e5fbe2a1148c45 14600 openconnect_8.05-1.debian.tar.xz
 8ce885c579f20d0da002c35db45fa4705d6cea05 8266 
openconnect_8.05-1_source.buildinfo
Checksums-Sha256:
 28db090c2fefa0ba70ff3b9cd2b78281713e0244acb0bde4f583ffefe23b1b3e 2574 
openconnect_8.05-1.dsc
 335c2952d0cb36822acb112eaaf5e3b4acffc6874985fb614fec0b76c4c12992 1922100 
openconnect_8.05.orig.tar.gz
 93a1aea81827e9c5a0cbcda745a2634e022163778dd7bf3a31cbd3126fa34bee 833 
openconnect_8.05.orig.tar.gz.asc
 d63f5d995306e11dec69c26aa10ed3aae62659f6bb22001a7ca8391fb3154af7 14600 
openconnect_8.05-1.debian.tar.xz
 c2e3b288e6bd1e665552be784aa6ec748714a68e1c8a7a10d52a1261d15c7cf2 8266 
openconnect_8.05-1_source.buildinfo
Files:
 79b4c675e231ad7fd9e1ff1c8a082ae6 2574 net optional openconnect_8.05-1.dsc
 6f649c04114435961b87036deb484f47 1922100 net optional 
openconnect_8.05.orig.tar.gz
 61e8d007765f1894f8649ac6dc00dfae 833 net optional 
openconnect_8.05.orig.tar.gz.asc
 a222abc651ffe50a8215aff02443a019 14600 net optional 
openconnect_8.05-1.debian.tar.xz
 e9440da5a430d45546ce0bc8ea18ba91 8266 net optional 
openconnect_8.05-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAl54+tERHGJsdWNhQGRl
Ymlhbi5vcmcACgkQSylmgFB4UWLIawf8C7+8Lll2xFXtxpBJsA/Nd9iGxznApRll
tNWR8eOsV25zDIvUK8YmZ/ozpNVTyrws1fz5quRH6irnxw6kYeJkGMPi2aBG4EvE
Ax3G9DpiayIoSY2S0YfmgXg4OzzG6vZIDspc2d32BqDOv8LAtOJSI+Zb68C3G7ar
/rXeCsuB9KQ0k68DcXvKUd/BGQHUgtlW06a5iN+g5MLUMkJu/79dUxLknTnxWTUc
xJnHe69WJgF4PUlH6cXZQ98IVBjkoNby4Dodlwsdw8Fp5L65aSdWAi3ONTG9JmYw
bb5Y54jUam2dyCHPOIGuoBXR/CvcrZwCWbkwy10mTPH9D4VBJESzTA==
=CRMx
-END PGP SIGNATURE End Message ---

Bug#935198: marked as done (openconnect: New upstream release 8.04 supporting Juniper Pulse Secure protocol)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:19:27 +
with message-id 
and subject line Bug#935198: fixed in openconnect 8.05-1
has caused the Debian Bug report #935198,
regarding openconnect: New upstream release 8.04 supporting Juniper Pulse 
Secure protocol
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openconnect
Version: 8.04-0~bpo10+0
Severity: wishlist
Tags: upstream

Hello,

Openconnect 8.04 has been released and support the new protocol used by up-to-
date Juniper products.

I built it by myself and it works just fine with no packaging modification.

Thanks,

Adam.



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openconnect depends on:
ii  libc62.28-10
ii  libgnutls30  3.6.7-4
ii  libopenconnect5  8.04-0~bpo10+0
ii  libproxy1v5  0.4.15-5
ii  libxml2  2.9.4+dfsg1-7+b3
ii  vpnc-scripts 0.1~git20190117-1

openconnect recommends no packages.

openconnect suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 8.05-1
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated openconnect 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Mar 2020 19:13:13 +
Source: openconnect
Architecture: source
Version: 8.05-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 935198 937197
Changes:
 openconnect (8.05-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Luca Boccassi ]
   * Update upstream source from tag 'upstream/8.05' (Closes: #935198)
   * Drop patches, merged upstream in v8.05
   * Build-depend on Python3, v8.05 can build documentation with it now
 (Closes: #937197)
   * Set Rules-Requires-Root: no
   * Bump Standards-Version to 4.5.0, no changes
   * Add myself to Uploaders
   * Addn Lintian override for hipreport-android.sh
   * Drop rules for dbgsym migration
   * Add libopenconnect.la to d/not-installed
Checksums-Sha1:
 6dc01402beac6363b96fb1cb47e3f046fc369561 2574 openconnect_8.05-1.dsc
 7fc0ed9cb34b401740100f36695036d256c0 1922100 openconnect_8.05.orig.tar.gz
 0dce024e00efe199fad25d7e741c37fb760aee98 833 openconnect_8.05.orig.tar.gz.asc
 97ffe2f6b8a48aab7deb631746e5fbe2a1148c45 14600 openconnect_8.05-1.debian.tar.xz
 8ce885c579f20d0da002c35db45fa4705d6cea05 8266 
openconnect_8.05-1_source.buildinfo
Checksums-Sha256:
 28db090c2fefa0ba70ff3b9cd2b78281713e0244acb0bde4f583ffefe23b1b3e 2574 
openconnect_8.05-1.dsc
 335c2952d0cb36822acb112eaaf5e3b4acffc6874985fb614fec0b76c4c12992 1922100 
openconnect_8.05.orig.tar.gz
 93a1aea81827e9c5a0cbcda745a2634e022163778dd7bf3a31cbd3126fa34bee 833 
openconnect_8.05.orig.tar.gz.asc
 d63f5d995306e11dec69c26aa10ed3aae62659f6bb22001a7ca8391fb3154af7 14600 
openconnect_8.05-1.debian.tar.xz
 c2e3b288e6bd1e665552be784aa6ec748714a68e1c8a7a10d52a1261d15c7cf2 8266 
openconnect_8.05-1_source.buildinfo
Files:
 79b4c675e231ad7fd9e1ff1c8a082ae6 2574 net optional openconnect_8.05-1.dsc
 6f649c04114435961b87036deb484f47 1922100 net optional 
openconnect_8.05.orig.tar.gz
 61e8d007765f1894f8649ac6dc00dfae 833 net optional 
openconnect_8.05.orig.tar.gz.asc
 a222abc651ffe50a8215aff02443a019 14600 net optional 
openconnect_8.05-1.debian.tar.xz
 e9440da5a430d45546ce0bc8ea18ba91 8266 net optional 

Bug#954276: marked as done (cloud-init - RuntimeError: dictionary keys changed during iteration)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:04:13 +
with message-id 
and subject line Bug#954276: fixed in cloud-init 20.1-2
has caused the Debian Bug report #954276,
regarding cloud-init - RuntimeError: dictionary keys changed during iteration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cloud-init
Version: 20.1-1
Severity: serious

cloud-init 20.1-1 fails to provision Azure:

| 2020-03-19 14:31:48,840 - util.py[DEBUG]: Running module disk_setup () failed
| Traceback (most recent call last):
|   File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 848, in 
_run_modules
| ran, _r = cc.run(run_name, mod.handle, func_args,
|   File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
| return self._runners.run(name, functor, args, freq, clear_on_fail)
|   File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 185, in run
| results = functor(*args)
|   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_disk_setup.py", 
line 129, in handle
| update_disk_setup_devices(disk_setup, cloud.device_name_to_device)
|   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_disk_setup.py", 
line 166, in update_disk_setup_devices
| for origname in disk_setup.keys():
| RuntimeError: dictionary keys changed during iteration

Bastian

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cloud-init depends on:
pn  cloud-guest-utils   
ii  fdisk   2.34-0.1
ii  gdisk   1.0.5-1
pn  ifupdown
ii  locales 2.29-10
ii  lsb-base11.1.0
ii  lsb-release 11.1.0
ii  net-tools   1.60+git20180626.aebd88e-1
ii  procps  2:3.3.15-2+b1
ii  python3 3.7.5-3
pn  python3-configobj   
ii  python3-jinja2  2.10.1-2
pn  python3-jsonpatch   
pn  python3-jsonschema  
pn  python3-oauthlib
ii  python3-requests2.22.0-2
ii  python3-six 1.14.0-2
ii  python3-yaml5.3-2
ii  util-linux  2.34-0.1

Versions of packages cloud-init recommends:
pn  eatmydata  
ii  sudo   1.8.31-1

Versions of packages cloud-init suggests:
pn  btrfs-progs  
ii  e2fsprogs1.45.5-2
pn  xfsprogs 
--- End Message ---
--- Begin Message ---
Source: cloud-init
Source-Version: 20.1-2
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated cloud-init 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 09:02:27 -0700
Source: cloud-init
Architecture: source
Version: 20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team 
Changed-By: Noah Meyerhans 
Closes: 954276 954363
Changes:
 cloud-init (20.1-2) unstable; urgency=medium
 .
   * Fix python 3.8 incompatibility (Closes: #954276)
   * Cherry-pick fa1abfec2705 (ec2: only redact token request headers in
 logs, avoid altering request) from upstream. (Closes: #954363)
   * Cherry-pick 1f860e5ac7eb (ec2: Do not fallback to IMDSv1 on EC2) from
 upstream.
Checksums-Sha1:
 c6c23bbeae0c491fca68804807a05bf651a8c46e 2397 cloud-init_20.1-2.dsc
 bf1ea9c04a451a9cab9e770b5971f019287032f2 29744 cloud-init_20.1-2.debian.tar.xz
 ad818f6f6a37182ae188d5bbb49fe76960f5ff2b 6275 
cloud-init_20.1-2_source.buildinfo
Checksums-Sha256:
 3256701cb987dcdc7cfb8a5aaa477575c6075c1720f73e7f4dd951cb87a7a2df 2397 
cloud-init_20.1-2.dsc
 a5aff4677f2ca976c2eef9f7d1d14cab1b1d690a7a758d517e1e94f060206b09 29744 

Bug#954363: marked as done (cloud-init fails to obtain an IMDS API token on Amazon EC2)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 18:04:14 +
with message-id 
and subject line Bug#954363: fixed in cloud-init 20.1-2
has caused the Debian Bug report #954363,
regarding cloud-init fails to obtain an IMDS API token on Amazon EC2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cloud-init
Version: 20.1-1
Severity: important

Cloud-init 20.1 attempts to obtain an API token for use with Amazon EC2
instance metadata service (IMDS).  On EC2, this operation should always
succeed, whether using IMDSv1 or v2, and cloud-init will always access
IMDS in v2 mode.  However, this fails on EC2:

2020-03-20 18:25:10,331 - DataSourceEc2.py[DEBUG]: Fetching Ec2 IMDSv2 API Token
2020-03-20 18:25:10,332 - url_helper.py[DEBUG]: [0/1] open 
'http://169.254.169.254/latest/api/token' with {'url': 
'http://169.254.169.254/latest/api/token', 'allow_redirects': True, 'method': 
'PUT', 'timeout': 1.0, 'headers': {'User-Agent': 'Cloud-Init/20.1', 
'X-aws-ec2-metadata-token-ttl-seconds': 'REDACTED'}} configuration
2020-03-20 18:25:10,336 - url_helper.py[DEBUG]: Read from 
http://169.254.169.254/latest/api/token (400, 0b) after 1 attempts
2020-03-20 18:25:10,336 - DataSourceEc2.py[WARNING]: Calling 
'http://169.254.169.254/latest/api/token' failed [0/1s]: empty response [400]
2020-03-20 18:25:10,344 - url_helper.py[DEBUG]: Please wait 1 seconds while we 
wait to try again

With 20.1, cloud-init will fall back to using IMDSv1 in this case, but
this behavior will change in future versions, which will always use v2
mode (it is backwards-compatible with v1), and only use v1 mode for
compatibility with non-AWS services providing IMDS-compatible metadata
endpoints.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-cloud-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cloud-init depends on:
ii  fdisk   2.34-0.1
ii  gdisk   1.0.5-1
ii  ifupdown0.8.35+b1
ii  locales 2.30-2
ii  lsb-base11.1.0
ii  lsb-release 11.1.0
ii  net-tools   1.60+git20180626.aebd88e-1
ii  procps  2:3.3.16-4
ii  python3 3.8.2-1
ii  python3-configobj   5.0.6-3
ii  python3-jinja2  2.10.1-2
ii  python3-jsonpatch   1.23-3
ii  python3-jsonschema  3.0.2-4
ii  python3-oauthlib3.1.0-1
ii  python3-requests2.22.0-2
ii  python3-six 1.14.0-2
ii  python3-yaml5.3.1-1
ii  util-linux  2.34-0.1

Versions of packages cloud-init recommends:
ii  cloud-guest-utils  0.31-1
pn  eatmydata  
ii  sudo   1.8.31-1

Versions of packages cloud-init suggests:
pn  btrfs-progs  
ii  e2fsprogs1.45.5-2
pn  xfsprogs 

-- debconf information:
* cloud-init/datasources:Ec2
--- End Message ---
--- Begin Message ---
Source: cloud-init
Source-Version: 20.1-2
Done: Noah Meyerhans 

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

Debian distribution maintenance software
pp.
Noah Meyerhans  (supplier of updated cloud-init 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 09:02:27 -0700
Source: cloud-init
Architecture: source
Version: 20.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team 
Changed-By: Noah Meyerhans 
Closes: 954276 954363
Changes:
 cloud-init (20.1-2) unstable; urgency=medium
 .
   * Fix python 3.8 incompatibility (Closes: #954276)
   * Cherry-pick fa1abfec2705 (ec2: only redact token request headers in
 logs, avoid altering request) from upstream. (Closes: #954363)
   * Cherry-pick 1f860e5ac7eb (ec2: Do not fallback to IMDSv1 on EC2) from
 upstream.

Bug#950870: marked as done (ITP: ruby-dry-container -- Simple, configurable object container implemented in Ruby)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 17:00:10 +
with message-id 
and subject line Bug#950870: fixed in ruby-dry-container 0.7.2-1
has caused the Debian Bug report #950870,
regarding ITP: ruby-dry-container -- Simple, configurable object container 
implemented in Ruby
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
950870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Utkarsh Gupta 

* Package name : ruby-dry-container
  Version : 0.7.2
  Upstream Author : dry team
* URL :  https://github.com/dry-rb/dry-container
* License : Expat
  Programming Lang : Ruby
  Description: Simple, configurable object container implemented in Ruby
 dry-container is a simple, thread-safe container, intended to be one half
 of a dependency injection system, possibly in combination with
dry-auto_inject.
 .
 At its most basic, dependency injection is a simple technique that makes it
 possible to implement patterns or principles of code design that rely on
object
 composition, such as the SOLID principles.
--- End Message ---
--- Begin Message ---
Source: ruby-dry-container
Source-Version: 0.7.2-1
Done: Utkarsh Gupta 

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated ruby-dry-container 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 07 Feb 2020 10:17:08 -0500
Source: ruby-dry-container
Binary: ruby-dry-container
Architecture: source all
Version: 0.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Utkarsh Gupta 
Description:
 ruby-dry-container - Simple, configurable object container implemented in Ruby
Closes: 950870
Changes:
 ruby-dry-container (0.7.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #950870)
Checksums-Sha1:
 ba463b3bd40f2039c43ed3c73e64e597ff299cb0 2210 ruby-dry-container_0.7.2-1.dsc
 edd89098c0d19c0ace0a0a8c2bf7e0f17f9ade50 14878 
ruby-dry-container_0.7.2.orig.tar.gz
 47d1a34d5260997dc60859b723c5d1ab0003f10b 2412 
ruby-dry-container_0.7.2-1.debian.tar.xz
 ff68a4442e59819c13077a4c1ce8603a6f0317a6 9504 
ruby-dry-container_0.7.2-1_all.deb
 0e39d359279f9f5a91bacc094b3a86a9ab884b1c 9156 
ruby-dry-container_0.7.2-1_amd64.buildinfo
Checksums-Sha256:
 71ecd5816ece11e9690c6bc0636e0376e3f4dddeca93fcc141cc7096f7ac65fc 2210 
ruby-dry-container_0.7.2-1.dsc
 48e22b77c19500c62f933f6633a676d0f3f7502dd4dc762225109e6749a5d3e3 14878 
ruby-dry-container_0.7.2.orig.tar.gz
 ce9731ee1e04dbdfe5fa02535cb4d2e1d9d14d57a6938623b3d5cec4866784fb 2412 
ruby-dry-container_0.7.2-1.debian.tar.xz
 eb57d9e359668ef069e5efddb1104fae198f599f30d3db5a0a9d702c7a55ed1a 9504 
ruby-dry-container_0.7.2-1_all.deb
 a8b51dfc1d40a83ca5ef36d62e20a2206aabb1c9b812436817416c8559350ff6 9156 
ruby-dry-container_0.7.2-1_amd64.buildinfo
Files:
 638f412a45f7f57e91a1648d48e74ad9 2210 ruby optional 
ruby-dry-container_0.7.2-1.dsc
 81b246ec3e30b243528852954659bbd5 14878 ruby optional 
ruby-dry-container_0.7.2.orig.tar.gz
 1ad74e6552fba9784d0133327fe6b9c6 2412 ruby optional 
ruby-dry-container_0.7.2-1.debian.tar.xz
 24f78b22c61a4896dcf03d84076c0c03 9504 ruby optional 
ruby-dry-container_0.7.2-1_all.deb
 b2b6402f9de663b620711a78beab420a 9156 ruby optional 
ruby-dry-container_0.7.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl5kjFkTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlmC4D/0caI5bB3tR0u/wlxiHFfkXZuh5vjkB
NL3H6DDUVZv5rMgKoPDhZs7y/3+SxOC1RQ4Ye8o7mxfSoa+e8idjCmAi8MwTdgC7
LsWUI3tHtj6DKYGxD813S4gB/BEGgI7+eXciwksYs3YSu6RbB9yVD7BZG/k0VpZ1
Y1sguln+rLucgqYz5mNeummGROss5tpHmYjWsX2Mqy4lt05/vrpEJV3bEeOxpDV6
CUwQDkIwtZGyVEMTp4qUF1P2zrMxduBmdDyw2mJgkPYUuzgQrXxH3/Q3InsERz+r
Atp63vkmJytOOiEYvlUrj9HelxOYQlEL8tIktw1Ex+xNSQ2wB22zo9h/VVMgjROy
rAHyH8J58uivHiPYPH5AeOS5InO0xCnCPRcUDoxa8SGT44C6fZVDbZHuEcpAzB4U
JYlJLR9AWJ7JfLlpzJrSAK0UygUHUn4CqMEjIM+CLmhGvfezyStXI5GS9uNVB5xo

Bug#954723: marked as done (golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 15:50:00 +
with message-id 
and subject line Bug#954723: fixed in golang-github-mendersoftware-scopestack 
0.0~git20180403.c2f5599-4
has caused the Debian Bug report #954723,
regarding golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: 
cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/mendersoftware/scopestack returned exit code 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-mendersoftware-scopestack
Version: 0.0~git20180403.c2f5599-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/mendersoftware/scopestack
> runtime/internal/sys
> container/list
> internal/cpu
> runtime/internal/atomic
> runtime/internal/math
> math/bits
> unicode/utf8
> internal/race
> sync/atomic
> internal/bytealg
> unicode
> math
> internal/testlog
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> strings
> reflect
> time
> internal/syscall/unix
> internal/poll
> internal/fmtsort
> os
> fmt
> github.com/mendersoftware/scopestack
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack
> # github.com/mendersoftware/scopestack 
> [github.com/mendersoftware/scopestack.test]
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:23:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:29:2: undefined: 
> mendertesting.AssertTrue
> src/github.com/mendersoftware/scopestack/scope_stack_test.go:35:2: undefined: 
> mendertesting.AssertTrue
> FAIL  github.com/mendersoftware/scopestack [build failed]
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/mendersoftware/scopestack returned exit code 2

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/golang-github-mendersoftware-scopestack_0.0~git20180403.c2f5599-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-mendersoftware-scopestack
Source-Version: 0.0~git20180403.c2f5599-4
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-mendersoftware-scopestack 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 17:48:02 +0530
Source: golang-github-mendersoftware-scopestack
Binary: golang-github-mendersoftware-scopestack-dev
Architecture: source all
Version: 0.0~git20180403.c2f5599-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Description:
 golang-github-mendersoftware-scopestack-dev - Scopestack package for Golang 
Build Status
Closes: 954723
Changes:
 golang-github-mendersoftware-scopestack (0.0~git20180403.c2f5599-4) unstable; 
urgency=medium
 .
   * Team Upload.
   * Switch to use golang-testify for assert (Closes: #954723)
   * Update 

Bug#939483: marked as done (krb5: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 15:22:39 +
with message-id 
and subject line Bug#939483: fixed in krb5 1.17-7
has caused the Debian Bug report #939483,
regarding krb5: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
939483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:krb5
Version: 1.17-6
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:cheetah

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.


pgptYTySvoTcU.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: krb5
Source-Version: 1.17-7
Done: Sam Hartman 

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

Debian distribution maintenance software
pp.
Sam Hartman  (supplier of updated krb5 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 10:46:41 -0400
Source: krb5
Architecture: source
Version: 1.17-7
Distribution: unstable
Urgency: medium
Maintainer: Sam Hartman 
Changed-By: Sam Hartman 
Closes: 939483
Changes:
 krb5 (1.17-7) unstable; urgency=medium
 .
   * Use python3 for building docs; pull patch from upstream, Closes: #939483
Checksums-Sha1:
 33cbad0d87e9a3a3faa1783b1a414b31f5d28d08 3177 krb5_1.17-7.dsc
 20ca90bbc96f95ff5e23669e7a79254241de44bc 144276 krb5_1.17-7.debian.tar.xz
 1104bded638a47d403fa9d1ac956c7afbe07af63 5451 krb5_1.17-7_source.buildinfo
Checksums-Sha256:
 e87976ef609ade00c83f7d58628bb705f7c1a4647c3bbf2bc80b806e08622086 3177 
krb5_1.17-7.dsc
 b8f39a918fc2872b5befe4e77fc8ed40f193ab2ebfbb9d5b670a461b618542f4 144276 
krb5_1.17-7.debian.tar.xz
 c0b0711d4eeb12da6c6b0a0516610a1565ea0a2b06d56c68e52ac57472d768cb 5451 
krb5_1.17-7_source.buildinfo
Files:
 d4f0ea1132e532584d3560e00a99ac18 3177 net optional krb5_1.17-7.dsc
 

Bug#954529: marked as done (libgit2: FTBFS: ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 14:57:30 +
with message-id 
and subject line Bug#954529: fixed in libgit2 0.28.4+dfsg.1-4
has caused the Debian Bug report #954529,
regarding libgit2: FTBFS: 
./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:11:
 undefined reference to `pthread_create'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit2
Version: 0.28.4+dfsg.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_fa306.dir/src.c.o: in function `main':
> ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:11:
>  undefined reference to `pthread_create'
> /usr/bin/ld: 
> ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:12:
>  undefined reference to `pthread_detach'
> /usr/bin/ld: 
> ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:13:
>  undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/libgit2_0.28.4+dfsg.1-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 0.28.4+dfsg.1-4
Done: Utkarsh Gupta 

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated libgit2 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 19:52:32 +0530
Source: libgit2
Architecture: source
Version: 0.28.4+dfsg.1-4
Distribution: unstable
Urgency: medium
Maintainer: Utkarsh Gupta 
Changed-By: Utkarsh Gupta 
Closes: 954529
Changes:
 libgit2 (0.28.4+dfsg.1-4) unstable; urgency=medium
 .
   * Add BD on ca-certificates to fix FTBFS (Closes: #954529)
 (Thanks to Sudip Mukherjee for his help :))
Checksums-Sha1:
 023ceaa4172b1b19a9c18242f0b8df7cc451ded4 2234 libgit2_0.28.4+dfsg.1-4.dsc
 02340e7c0318844d09f685b9b40f55e98b8cb402 14404 
libgit2_0.28.4+dfsg.1-4.debian.tar.xz
 e7ad9a5a8df23c29d7ce07f9ef2710036d20f526 7774 
libgit2_0.28.4+dfsg.1-4_amd64.buildinfo
Checksums-Sha256:
 34e9cea9b9226230578cac7cc0782477555e5304f2380642c41551072b1c8061 2234 
libgit2_0.28.4+dfsg.1-4.dsc
 e69efd766ba438ef41df0c253d94e0f225148146f0dc0cb9c4a412d0856a63c6 14404 
libgit2_0.28.4+dfsg.1-4.debian.tar.xz
 93f7bcb380a5b80b22b5e9a2d4dd97d853a8b4b1a336baa320f415b02d5ce2f2 7774 
libgit2_0.28.4+dfsg.1-4_amd64.buildinfo
Files:
 25059ec5a4f49b79ac0c66af0da794c6 2234 libs optional libgit2_0.28.4+dfsg.1-4.dsc
 fb12473ca720d675f91919de8e28a4fa 14404 libs optional 
libgit2_0.28.4+dfsg.1-4.debian.tar.xz
 bb33c703bc2a45199675abc29ced4697 7774 libs optional 
libgit2_0.28.4+dfsg.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEbJ0QSEqa5Mw4X3xxgj6WdgbDS5YFAl54x/gTHHV0a2Fyc2hA
ZGViaWFuLm9yZwAKCRCCPpZ2BsNLlgeAD/92rC8PpSA2nkVak2L2IyZkKkxlOFe7
hoIrA7CWTvcdDiXhGhpmtb77h5cVSDeJxP1zFUf90aqh77MCGJ0QTR/CNZ8VjULP
7QGbd9KsyOI1I9Lapc3kKWfxT5ELn7jshLasEVHwPytF957io2MgPaxq88G+z1z9
wsRR+1uucwLj8WN3p0vwnBmGp8rmRbTLdLo9KikDc1bV4209t9fmODz4GysZOruw
o2gwWLYOmsuywniJBtrb1lTgGHr1SlVy92IVszUMJ0wzvFa4jA/FtnLlHKkBfPIY
VM8gQOWRb7wVF5sEq3zp/QxxD9GJMna5xKqL3NiI1Go2iJtw1aKS8xAy1j5xj9LJ
s8NN0S9zKrSEvM/ARIKb2I8zDQy1hiv1Pf0VpaGRGlfoVERzGw8zuG3Ur/HudD+9

Bug#954355: marked as done (libjavascriptcoregtk-4.0-18: WebKitWebProcess crashes on ppc64el, mprotect fails)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 14:30:21 +0100
with message-id <20200323133021.GA28610@perseus.local>
and subject line Re: Bug#954355: libjavascriptcoregtk-4.0-18: WebKitWebProcess 
crashes on ppc64el, mprotect fails
has caused the Debian Bug report #954355,
regarding libjavascriptcoregtk-4.0-18: WebKitWebProcess crashes on ppc64el, 
mprotect fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjavascriptcoregtk-4.0-18
Version: 2.28.0-2
Severity: important

Dear Maintainer,

The attached very simple C program makes WebKitWebProcess crash on ppc64el.

I managed to get a stacktrace using the following steps:

(gdb) b g_subprocess_launcher_new
(gdb) r
Thread 1 "test" hit Breakpoint 1 ...
(gdb) set follow-fork-mode child
(gdb) c
Thread 2.1 "WebKitWebProces" received signal SIGABRT, Aborted.

The crash happens in:

#0  0x73f16f58 in __libc_signal_restore_set (set=0x7fffd838) at 
../sysdeps/unix/sysv/linux/internal-signals.h:84
#1  __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:48
#2  0x73ef7e8c in __GI_abort () at abort.c:79
#3  0x72066f74 in CRASH_WITH_INFO(...) () at 
DerivedSources/ForwardingHeaders/wtf/Assertions.h:660
#4  JSC::Config::permanentlyFreeze() () at 
../Source/JavaScriptCore/runtime/JSCConfig.cpp:78
#5  0x72284510 in JSC::VM::VM(JSC::VM::VMType, JSC::HeapType) () at 
../Source/JavaScriptCore/runtime/VM.cpp:586
#6  0x72285764 in JSC::VM::create(JSC::HeapType) () at 
../Source/JavaScriptCore/runtime/VM.cpp:703
#7  0x75beced8 in WebCore::commonVMSlow() () at 
../Source/WebCore/bindings/js/CommonVM.cpp:55
#8  0x7635b504 in WebCore::commonVM() () at 
../Source/WebCore/bindings/js/CommonVM.h:52

Line 78 of JSCConfig.cpp and the preceding code is:

#elif OS(LINUX)
result = mprotect(_jscConfig, ConfigSizeToProtect, PROT_READ);
#elif OS(WINDOWS)
// FIXME: Implement equivalent, maybe with VirtualProtect.
// Also need to fix WebKitTestRunner.
#endif
RELEASE_ASSERT(!result);

The complete stack trace is also attached.

--
Dmitry Shachnev
#include 
#include 
#include 
#include 

void web_process_terminated(G_GNUC_UNUSED WebKitWebView *view,
WebKitWebProcessTerminationReason reason,
G_GNUC_UNUSED gpointer user_data) {
if (reason == WEBKIT_WEB_PROCESS_CRASHED) {
g_printf("The process crashed.\n");
}
gtk_main_quit();
}

int main(int argc, char **argv) {
gtk_init(, );

WebKitWebView *view = WEBKIT_WEB_VIEW(webkit_web_view_new());
g_object_ref(view);
g_signal_connect(view, "web-process-terminated", G_CALLBACK(web_process_terminated), NULL);

webkit_web_view_load_html(view, "", NULL);

gtk_main();

return 0;
}
#0  0x73f16f58 in __libc_signal_restore_set (set=0x7fffd838) at 
../sysdeps/unix/sysv/linux/internal-signals.h:84
#1  __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:48
#2  0x73ef7e8c in __GI_abort () at abort.c:79
#3  0x72066f74 in CRASH_WITH_INFO(...) () at 
DerivedSources/ForwardingHeaders/wtf/Assertions.h:660
#4  JSC::Config::permanentlyFreeze() () at 
../Source/JavaScriptCore/runtime/JSCConfig.cpp:78
#5  0x72284510 in JSC::VM::VM(JSC::VM::VMType, JSC::HeapType) () at 
../Source/JavaScriptCore/runtime/VM.cpp:586
#6  0x72285764 in JSC::VM::create(JSC::HeapType) () at 
../Source/JavaScriptCore/runtime/VM.cpp:703
#7  0x75beced8 in WebCore::commonVMSlow() () at 
../Source/WebCore/bindings/js/CommonVM.cpp:55
#8  0x7635b504 in WebCore::commonVM() () at 
../Source/WebCore/bindings/js/CommonVM.h:52
#9  WebCore::PageScriptDebugServer::PageScriptDebugServer(WebCore::Page&) () at 
../Source/WebCore/inspector/PageScriptDebugServer.cpp:58
#10 0x76343c28 in 
WebCore::InspectorController::InspectorController(WebCore::Page&, 
WebCore::InspectorClient*) () at 
../Source/WebCore/inspector/InspectorController.cpp:105
#11 0x7661b9f8 in std::make_unique(WebCore::Page&, 
WebCore::InspectorClient*&) ()
at /usr/include/c++/9/bits/unique_ptr.h:857
#12 WTF::makeUnique(WebCore::Page&, WebCore::InspectorClient*&) ()
at DerivedSources/ForwardingHeaders/wtf/StdLibExtras.h:483
#13 WebCore::Page::Page(WebCore::PageConfiguration&&) () at 
../Source/WebCore/page/Page.cpp:279
#14 0x7513eff4 in std::make_unique(WebCore::PageConfiguration&&) () at 
/usr/include/c++/9/bits/unique_ptr.h:857
#15 

Bug#954100: marked as done (Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 14:28:19 +0100
with message-id <0f0575b7188fe6ac64115ec322c6e182290a7f1b.ca...@gmail.com>
and subject line Error: A deprecated csdestruct_derived typemap was found for 
vtkGDCMTesting
has caused the Debian Bug report #954100,
regarding Error: A deprecated csdestruct_derived typemap was found for 
vtkGDCMTesting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdcm
Version: 3.0.4
Severity: serious
Tags: upstream ftbfs

Using SWIG 4.0, gdcm ftbfs

> cd /gdcm/obj-x86_64-linux-gnu/Utilities/VTK && /usr/bin/cmake -E 
> make_directory /gdcm/obj-x86_64-linux-gnu/Utilities/VTK 
> /gdcm/obj-x86_64-linux-gnu/Utilities/VTK/CMakeFiles/vtkgdcmsharpglue.dir && 
> /usr/bin/cmake -E env SWIG_LIB=/usr/share/swig4.0 /usr/bin/swig4.0 -csharp 
> -namespace vtkgdcm -dllimport vtkgdcmsharpglue -outdir 
> /gdcm/obj-x86_64-linux-gnu/Utilities/VTK -c++ -I/usr/include 
> -I/usr/include/vtk-7.1 -I/usr/include/freetype2 
> -I/usr/include/x86_64-linux-gnu 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python3.8 
> -I/usr/include/hdf5/openmpi -I/usr/include/jsoncpp -I/usr/include/libxml2 
> -I/usr/include/tcl -I/gdcm/obj-x86_64-linux-gnu/Source/Common 
> -I/gdcm/Source/Common -I/gdcm/Source/DataStructureAndEncodingDefinition 
> -I/gdcm/Source/MediaStorageAndFileFormat -I/gdcm/Source/DataDictionary 
> -I/gdcm/Utilities/VTK -o 
> /gdcm/obj-x86_64-linux-gnu/Utilities/VTK/CMakeFiles/vtkgdcmsharpglue.dir/vtkgdcmCSHARP_wrap.cxx
> /gdcm/Utilities/VTK/vtkgdcm.i
> /usr/include/vtk-7.1/vtkStringArray.h:36: Warning 402: Base class 
> 'vtkAbstractArray' is incomplete.
> /usr/include/vtk-7.1/vtkAlgorithm.h:38: Warning 402: Only forward declaration 
> 'vtkAbstractArray' was found.
> /gdcm/Utilities/VTK/vtkgdcm.i:354: Error: A deprecated csdestruct_derived 
> typemap was found for vtkGDCMTesting, please remove it and replace all 
> csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, 
> csdispose_derived, csdisposing and csdisposing_derived typemaps.
> /gdcm/Utilities/VTK/vtkgdcm.i:365: Error: A deprecated csdestruct_derived 
> typemap was found for vtkGDCMImageReader, please remove it and replace all 
> csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, 
> csdispose_derived, csdisposing and csdisposing_derived typemaps.
> /gdcm/Utilities/VTK/vtkgdcm.i:376: Error: A deprecated csdestruct_derived 
> typemap was found for vtkGDCMImageWriter, please remove it and replace all 
> csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, 
> csdispose_derived, csdisposing and csdisposing_derived typemaps.
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v 
> returned exit code 1
> make[1]: *** [debian/rules:110: override_dh_auto_build-arch] Error 25
> make[1]: Leaving directory '/gdcm'
> make: *** [debian/rules:54: build] Error 2
--- End Message ---
--- Begin Message ---
Version: 3.0.5-1

Forgot to tag it in the changelog, so closing this manually. --- End Message ---

Bug#954204: marked as done (node-eslint-scope autopkgtest failure is blocking node-espree, acorn, rollup and webpack)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 13:20:00 +
with message-id 
and subject line Bug#954204: fixed in node-eslint-scope 4.0.3-6
has caused the Debian Bug report #954204,
regarding node-eslint-scope autopkgtest failure is blocking node-espree, acorn, 
rollup and webpack
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-eslint-scope
Version: 4.0.3-5
Severity: important

Strangely the tests during build seems to be passing with node-espree 6.0.0+ds-2

And the only change in node-espree is updating node-acorn-jsx version. So 
probably node-eslint-scope needs to be adapted for the new version of 
node-acorn-jsx that is part of the acorn 6 bundle.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---
--- Begin Message ---
Source: node-eslint-scope
Source-Version: 4.0.3-6
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated node-eslint-scope 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 13:57:21 +0100
Source: node-eslint-scope
Architecture: source
Version: 4.0.3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 954204
Changes:
 node-eslint-scope (4.0.3-6) unstable; urgency=medium
 .
   * add patch cherry-picked upstream to use espree 6;
 re-enable tests related to espree;
 closes: bug#954204, thanks to Pirate Praveen and Xavier Guimard
Checksums-Sha1:
 6d4a1e910ac5726686163e018d81cb0240754632 2265 node-eslint-scope_4.0.3-6.dsc
 9f67971fb4eda0792ba04923813a3f1e281adcd5 6236 
node-eslint-scope_4.0.3-6.debian.tar.xz
 6658b3b6f1c77b2aa62ebcda4bb3ffe3c6125d0b 9861 
node-eslint-scope_4.0.3-6_amd64.buildinfo
Checksums-Sha256:
 acef6f79d7af83866a33fdc42f213fe405b08bcd102a5254a3c0ca645175c873 2265 
node-eslint-scope_4.0.3-6.dsc
 c73d0ceba1eaafdcc89208275ecd600d972202d2a611e46c4cc86284f5cf9437 6236 
node-eslint-scope_4.0.3-6.debian.tar.xz
 8e46472d4ad4027d62598cb427fa423c0d6932582b129bdd71609c147193122e 9861 
node-eslint-scope_4.0.3-6_amd64.buildinfo
Files:
 770dd4192b8050225f5b53d57f6befd9 2265 javascript optional 
node-eslint-scope_4.0.3-6.dsc
 253da427b62a8109363ce5ee42194c02 6236 javascript optional 
node-eslint-scope_4.0.3-6.debian.tar.xz
 cd9d0d7c820165d84081781bce7d4ded 9861 javascript optional 
node-eslint-scope_4.0.3-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl54spsACgkQLHwxRsGg
ASFtYQ//RvdTVeaUSuSMiVfP64VggPedjlt2BnvzTW8wqQUUXz/djpjSUIVAlJRQ
R1lkXeVVJq7gZKMLeFMuBRKUfTm921zAp4NdbSP8G0Vcmgs+3sRrsTtuK1oBVBe/
oBvdYEWJbUKMXyt4jP7V6b/qt61YucGHIVKtbimP0TUySbCfnmkBY089jARZRKaM
qeeEcjBNgtewgYPc4+CkkbyRVmLNr2ajY9dbMxczAn6XGx8tSGXS31/RtyDON8zB
+QQtem1ZSRZt6TFK1fEDDlsOCkqQ8WfaTIzSIRXxb0+XG6Yk3R8Fyvcc5hFA8vDk
IFrgZ61e4M1tHRDKEkmc0+mcgrZ4BCxxu39gIea2FwW4xDb+c+w6f8zL9GwnFoIP
LOj1e4vPTDpL2TgLhQruFQFwWG6pEGYTtcCbEcHY0TzUShs5l7Tc46CZg5rMWCRI
Co7axaS43iOT2Ovl8u3hpq1J8hpxt/fpjkdGiDHlBQHeDrMjlrPrH0x+U3VUfLqa
oI4lsD+D2ILZntNo/Jnlu0F8j93eTALHTXGDjZ5bWvQVi+Knh7EZOEWHo65CED58
vgmbWRlFSaYzg7d95Xb8JRmb6A0jS/nUa7OuhhKbDHjTJUBGVxTJ/NG73jn/ef3D
7k86rLG+eF8gPliYBQ2gcqRxFMQEEQhabqu1BX2NFkpAKDPiZMk=
=SFLZ
-END PGP SIGNATURE End Message ---

Bug#954646: marked as done (node-fbjs: FTBFS: ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 13:20:08 +
with message-id 
and subject line Bug#954646: fixed in node-fbjs 1.0.0-3
has caused the Debian Bug report #954646,
regarding node-fbjs: FTBFS: ln: failed to create symbolic link 
'packages/fbjs/node_modules/4': File exists
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-fbjs
Version: 1.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p packages/fbjs/node_modules
> for f in `ls -s debian/build_modules`; do \
>   ln -s ../../../debian/build_modules/$f packages/fbjs/node_modules/$f; \
> done
> ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists
> cd packages/fbjs && gulp build
> [03:11:46] Local gulp not found in /<>/packages/fbjs
> [03:11:46] Try running: npm install gulp
> [03:11:46] Using globally installed gulp
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot find module 'merge-stream'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object. (/<>/packages/fbjs/gulpfile.js:14:21)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/node-fbjs_1.0.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-fbjs
Source-Version: 1.0.0-3
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-fbjs 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 10:43:15 +0100
Source: node-fbjs
Architecture: source
Version: 1.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 954646
Changes:
 node-fbjs (1.0.0-3) unstable; urgency=medium
 .
   * Team upload
   * Add build dependency to node-merge-stream (Closes: #954646)
   * Fix gulpfile for node-gulp 4
   * Add skippable autopkgtest file to avoid auto detection
   * Declare installed modules using ${nodejs:Provides}
   * Declare compliance with policy 4.5.0
Checksums-Sha1: 
 a2c547915c2da6b4120f9e243bce650f1808bf26 3655 node-fbjs_1.0.0-3.dsc
 9bbce235177f0ad0cf457a1adbf64f4022e38020 12780 node-fbjs_1.0.0-3.debian.tar.xz
Checksums-Sha256: 
 047d0a5dc24d7364c071c6b10a7b837a08b123c65f5b29a8cc0545d2308a1202 3655 
node-fbjs_1.0.0-3.dsc
 f54b05f06e0656f3a35f79592380b6e45c646409219b7fe3b8bef505a25c2aa8 12780 
node-fbjs_1.0.0-3.debian.tar.xz
Files: 
 285f23863519696ff0b2d01a3d167bfc 3655 javascript optional node-fbjs_1.0.0-3.dsc
 3a24582eadbd88701876c29e443a325f 12780 javascript optional 
node-fbjs_1.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl54sYwACgkQ9tdMp8mZ

Bug#954682: marked as done (rainbow.js: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 13:21:03 +
with message-id 
and subject line Bug#954682: fixed in rainbow.js 2.1.4+ds-3
has caused the Debian Bug report #954682,
regarding rainbow.js: FTBFS: AssertionError [ERR_ASSERTION]: Task function must 
be specified
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rainbow.js
Version: 2.1.4+ds-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> NODE_PATH=debian/node_modules gulp pack
> [08:53:01] Local modules not found in /<>
> [08:53:01] Try running: npm install
> [08:53:01] Using globally installed gulp
> assert.js:339
> throw err;
> ^
> 
> AssertionError [ERR_ASSERTION]: Task function must be specified
> at Gulp.set [as _setTask] 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/set-task.js:10:3)
> at Gulp.task 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/task.js:13:8)
> at Object. (/<>/gulpfile.js:251:6)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/rainbow.js_2.1.4+ds-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rainbow.js
Source-Version: 2.1.4+ds-3
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated rainbow.js 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 13:43:55 +0100
Source: rainbow.js
Architecture: source
Version: 2.1.4+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 954682
Changes:
 rainbow.js (2.1.4+ds-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Pirate Praveen ]
   * Build with rollup 1.10 and add node-yargs as build dep
 .
   [ Xavier Guimard ]
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Update lintian overrides
   * Add fix for gulp 4 (Closes: #954682)
Checksums-Sha1: 
 d40265f78560bb69e6ca28f245bd1231f8a0aa5c 2133 rainbow.js_2.1.4+ds-3.dsc
 4d18314078e96acaec185ae6264d21fc2b8c6ca9 8300 
rainbow.js_2.1.4+ds-3.debian.tar.xz
Checksums-Sha256: 
 237c28a5919186a2327a87130bf23b00c816d24350ca9559c9f18811b15deeef 2133 
rainbow.js_2.1.4+ds-3.dsc
 fcf6afb2805f8cf4122baa66d283d2ebe3bbf67b013281997f259e0981b61c31 8300 
rainbow.js_2.1.4+ds-3.debian.tar.xz
Files: 
 68bbcb349e51b2dfd0b6ac9d594698ed 2133 javascript optional 
rainbow.js_2.1.4+ds-3.dsc
 c772497257314260d60ca7045b374b98 8300 javascript optional 
rainbow.js_2.1.4+ds-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl54r9oACgkQ9tdMp8mZ
7unIqQ//SPXcOEWDQuOoxShmVT2hIGSt6y6hP+oojn/lX5qi0gIRATzvrDcMqCFf
fEselIlK9TDP+09MwtQU0jnzTltVyfMUux2sR3PFBld/+yHF1qyHdMVEfcKDKC2l
6QHxQzuGP7GSkGMIPm44lmj+UaSs9Mi/tq4fprnFoNnL9S4ngUI+f6LvZKuvX3NE

Bug#954596: marked as done (node-bluebird: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 12:55:56 +
with message-id 
and subject line Bug#954596: fixed in node-bluebird 3.5.3+dfsg1-2
has caused the Debian Bug report #954596,
regarding node-bluebird: FTBFS: dh_auto_test: error: /bin/sh -e 
debian/tests/pkg-js/test returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-bluebird
Version: 3.5.3+dfsg1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Bluebird depends on itself to build. Therefore we need to copy a
> # prebuilt version of Bluebird into place to bootstrap things in
> # Debian.
> cp -r /<>/debian/node-modules/ /<>/node_modules/
> node tools/build.js --release --no-minify
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot find module 'acorn/dist/walk'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object. (/<>/tools/ast_passes.js:3:12)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at require (/<>/tools/job-runner/job-runner.js:426:16)
> at eval (eval at  
> (/<>/tools/job-runner/job-runner.js:429:9), :5:21)
> at Object. 
> (/<>/tools/job-runner/job-runner.js:429:9)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot find module 'acorn/dist/walk'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object. (/<>/tools/ast_passes.js:3:12)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at require (/<>/tools/job-runner/job-runner.js:426:16)
> at eval (eval at  
> (/<>/tools/job-runner/job-runner.js:429:9), :5:21)
> at Object. 
> (/<>/tools/job-runner/job-runner.js:429:9)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot find module 'acorn/dist/walk'
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:636:15)
> at Function.Module._load (internal/modules/cjs/loader.js:562:25)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at Object. (/<>/tools/ast_passes.js:3:12)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> at require (/<>/tools/job-runner/job-runner.js:426:16)
> at eval (eval at  
> (/<>/tools/job-runner/job-runner.js:429:9), :5:21)
> at Object. 
> (/<>/tools/job-runner/job-runner.js:429:9)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> internal/modules/cjs/loader.js:638
> throw err;
> ^
> 
> Error: Cannot 

Bug#954703: marked as done (libvirt-python: FTBFS: Missing type converters: virTypedParameterPtr *:1 virTypedParameterPtr:1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 12:19:23 +
with message-id 
and subject line Bug#954703: fixed in libvirt-python 6.1.0-1
has caused the Debian Bug report #954703,
regarding libvirt-python: FTBFS: Missing type converters: virTypedParameterPtr 
*:1 virTypedParameterPtr:1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvirt-python
Version: 5.6.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3,python2 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py config 
> running config
> I: pybuild base:217: python3.7 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python2 setup.py build 
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python2 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 478 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 387 wrapper functions
> Missing type converters: 
> virTypedParameterPtr *:1 
> virTypedParameterPtr:1 
> ERROR: failed virConnectSetIdentity
> ERROR: failed virDomainGetGuestInfo
> error: command '/usr/bin/python2' failed with exit status 1
> E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python2 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 2.7 returned exit 
> code 13
> make: *** [debian/rules:12: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/03/22/libvirt-python_5.6.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libvirt-python
Source-Version: 6.1.0-1
Done: =?utf-8?q?Guido_G=C3=BCnther?= 

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt-python 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 12:24:30 +0100
Source: libvirt-python
Architecture: source
Version: 6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 936934 954703
Changes:
 libvirt-python (6.1.0-1) unstable; urgency=medium
 .
   * [318c6a9] New upstream version 6.1.0
 (Closes: #954703)
   * [b2883ff] Drop python2 support
 (Closes: #936934)
Checksums-Sha1:
 15736551d023bbab3f3ed126773df32c2633ad27 2269 libvirt-python_6.1.0-1.dsc
 4963e3b84a903e19d831c468152c6b0306e6b4d7 196848 
libvirt-python_6.1.0.orig.tar.gz
 0fa18ed7385479d7619dc8a5bdded1860ff8730e 488 
libvirt-python_6.1.0.orig.tar.gz.asc
 d599cf412f6d5f9e9c6759bfa6c54023b741cd70 9576 
libvirt-python_6.1.0-1.debian.tar.xz
 e92f9104a2dcc833727d1dd82ca9d30a80a71672 8049 
libvirt-python_6.1.0-1_source.buildinfo
Checksums-Sha256:
 7e680f721e5e96070f1f3ff68d622ffbc797774b785177c369343048b669f77d 2269 
libvirt-python_6.1.0-1.dsc
 be644f4809c0e1d368e3ac065df3c66a26dcfe61ecb607ee9706e1799f22c35a 196848 
libvirt-python_6.1.0.orig.tar.gz
 2e03af03995ec80c25c5d7216733afaae0e683d0ad4e635f0c5e19d186f2aa3b 488 
libvirt-python_6.1.0.orig.tar.gz.asc
 

Bug#936934: marked as done (libvirt-python: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 12:19:23 +
with message-id 
and subject line Bug#936934: fixed in libvirt-python 6.1.0-1
has caused the Debian Bug report #936934,
regarding libvirt-python: Python2 removal in sid/bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
936934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvirt-python
Version: 5.0.0-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:libvirt-python

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: libvirt-python
Source-Version: 6.1.0-1
Done: =?utf-8?q?Guido_G=C3=BCnther?= 

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated libvirt-python 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 12:24:30 +0100
Source: libvirt-python
Architecture: source
Version: 6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 936934 954703
Changes:
 libvirt-python (6.1.0-1) unstable; urgency=medium
 .
   * [318c6a9] New upstream version 6.1.0
 (Closes: #954703)
   * [b2883ff] Drop python2 support
 (Closes: #936934)
Checksums-Sha1:
 15736551d023bbab3f3ed126773df32c2633ad27 2269 libvirt-python_6.1.0-1.dsc
 4963e3b84a903e19d831c468152c6b0306e6b4d7 196848 
libvirt-python_6.1.0.orig.tar.gz
 0fa18ed7385479d7619dc8a5bdded1860ff8730e 488 
libvirt-python_6.1.0.orig.tar.gz.asc
 d599cf412f6d5f9e9c6759bfa6c54023b741cd70 9576 
libvirt-python_6.1.0-1.debian.tar.xz
 e92f9104a2dcc833727d1dd82ca9d30a80a71672 8049 
libvirt-python_6.1.0-1_source.buildinfo
Checksums-Sha256:
 

Processed: closing 953719

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 953719
Bug #953719 [src:libhandy] src:libhandy: fails to migrate to testing for too 
long
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
953719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954705: marked as done (libjs-jsencrypt: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 12:04:16 +
with message-id 
and subject line Bug#954705: fixed in libjs-jsencrypt 2.3.0+dfsg2-2
has caused the Debian Bug report #954705,
regarding libjs-jsencrypt: FTBFS: AssertionError [ERR_ASSERTION]: Task function 
must be specified
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjs-jsencrypt
Version: 2.3.0+dfsg2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh /usr/share/openstack-pkg-tools/pkgos.make
> dh: error: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose 
> from: binary binary-arch binary-indep build build-arch build-indep clean 
> install install-arch install-indep)
> mkdir -p bin
> gulp
> [08:50:32] Local modules not found in /<>
> [08:50:32] Try running: npm install
> [08:50:32] Using globally installed gulp
> assert.js:339
> throw err;
> ^
> 
> AssertionError [ERR_ASSERTION]: Task function must be specified
> at Gulp.set [as _setTask] 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/set-task.js:10:3)
> at Gulp.task 
> (/usr/share/nodejs/gulp/node_modules/undertaker/lib/task.js:13:8)
> at Object. (/<>/gulpfile.js:39:6)
> at Module._compile (internal/modules/cjs/loader.js:778:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require (internal/modules/cjs/helpers.js:25:18)
> make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/libjs-jsencrypt_2.3.0+dfsg2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libjs-jsencrypt
Source-Version: 2.3.0+dfsg2-2
Done: Xavier Guimard 

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated libjs-jsencrypt 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 12:35:14 +0100
Source: libjs-jsencrypt
Architecture: source
Version: 2.3.0+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 954705
Changes:
 libjs-jsencrypt (2.3.0+dfsg2-2) unstable; urgency=medium
 .
   * Team upload
   * Bump debhelper compatibility level to 12
   * Declare compliance with policy 4.5.0
   * Add "Rules-Requires-Root: no"
   * Change priority to optional
   * Add upstream/metadata
   * Update lintian overrides
   * Add fix for gulp ≥ 4 (Closes: #954705)
   * Fix debian/rules
   * Fix copyright
   * Update VCS fields to salsa
Checksums-Sha1: 
 993d8ca9c2f1e5e08d8e713fb992dc5d85c8019c 2081 libjs-jsencrypt_2.3.0+dfsg2-2.dsc
 c256268be61fd691c3877e1ee0dfeb36e3cac961 3816 
libjs-jsencrypt_2.3.0+dfsg2-2.debian.tar.xz
Checksums-Sha256: 
 0143f47ae94d39b742fd234346d2da4ec22946d20c4bbc13235af6363fbb9ad7 2081 
libjs-jsencrypt_2.3.0+dfsg2-2.dsc
 1c2f77c9331b8a38a1d9916a85826e5a1356e1154dec26a0b8dfe7a964697aa5 3816 
libjs-jsencrypt_2.3.0+dfsg2-2.debian.tar.xz
Files: 
 73a68c78a74a3d01a47b294951f831c6 2081 javascript optional 

Bug#952192: marked as done (golang-github-go-xorm-core: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/go-xorm/core returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 12:04:10 +
with message-id 
and subject line Bug#952192: fixed in golang-github-go-xorm-core 0.6.2-3
has caused the Debian Bug report #952192,
regarding golang-github-go-xorm-core: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/go-xorm/core 
returned exit code 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
952192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-go-xorm-core
Version: 0.6.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/go-xorm/core
> runtime/internal/atomic
> internal/cpu
> runtime/internal/sys
> internal/race
> sync/atomic
> runtime/internal/math
> unicode
> unicode/utf8
> internal/bytealg
> math/bits
> internal/testlog
> math
> encoding
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> bytes
> strings
> reflect
> bufio
> regexp/syntax
> internal/syscall/unix
> time
> regexp
> internal/poll
> context
> encoding/binary
> internal/fmtsort
> os
> fmt
> database/sql/driver
> encoding/gob
> database/sql
> github.com/go-xorm/core
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/go-xorm/core
> flag provided but not defined: -test.testlogfile
> Usage of /tmp/go-build490368215/b001/core.test:
>   -dbtype string
>   database type (default "mysql")
> FAIL  github.com/go-xorm/core 0.003s
> FAIL
> dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/go-xorm/core returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/golang-github-go-xorm-core_0.6.2-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: golang-github-go-xorm-core
Source-Version: 0.6.2-3
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-go-xorm-core 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Mar 2020 20:00:36 +0100
Source: golang-github-go-xorm-core
Architecture: source
Version: 0.6.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 952192
Changes:
 golang-github-go-xorm-core (0.6.2-3) unstable; urgency=medium
 .
   * fix test (Closes: #952192)
   * debian/control: use dh12
   * debian/control: set standard to 4.5.0 (no changes)
Checksums-Sha1:
 203d8a00b2956404ff7cb6d4e94e9c2111798627 2443 
golang-github-go-xorm-core_0.6.2-3.dsc
 2783eed43f6a01547754581238b52a64366b1fb7 2996 
golang-github-go-xorm-core_0.6.2-3.debian.tar.xz
 f8cf369f5413dee9c2927360b75ac5497b3b1603 6400 
golang-github-go-xorm-core_0.6.2-3_amd64.buildinfo
Checksums-Sha256:
 b4256a55499fc0fec586809bd4d36fb0eb62daec9f452fdea042ec7162912cb1 2443 
golang-github-go-xorm-core_0.6.2-3.dsc
 3ba758620a78e527ac4e6fc1cd87f29665b0a1572b77e5b07e3bd22364bf4b88 2996 
golang-github-go-xorm-core_0.6.2-3.debian.tar.xz
 

Bug#953698: marked as done (src:python-setoptconf: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 13:03:45 +0100
with message-id <66393f95-ee42-f13b-1728-ab83ac901...@yahoo.no>
and subject line close bug
has caused the Debian Bug report #953698,
regarding src:python-setoptconf: fails to migrate to testing for too long
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
953698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-setoptconf
Version: 0.2.0-3
Severity: serious
Control: fixed -1 0.2.0-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-setoptconf in its current version in unstable has been trying
to migrate for 156 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-setoptconf




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.2.0-5--- End Message ---

Processed: closing 952132

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 952132 0.68.2+ds-1
Bug #952132 [rollup] vue-router.js: FTBFS: build-dependency not installable: 
rollup
Marked as fixed in versions node-rollup/0.68.2+ds-1.
Bug #952132 [rollup] vue-router.js: FTBFS: build-dependency not installable: 
rollup
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Move to the correct packages and merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 952129 node-boom
Bug #952129 [src:node-cryptiles] node-cryptiles: FTBFS: unsatisfiable 
build-dependency: node-hapi-boom (>= 7.0.0) (versioned dep on a virtual pkg?)
Bug reassigned from package 'src:node-cryptiles' to 'node-boom'.
No longer marked as found in versions node-cryptiles/4.2.0-3.
Ignoring request to alter fixed versions of bug #952129 to the same values 
previously set
> affects 952129 src:node-cryptiles
Bug #952129 [node-boom] node-cryptiles: FTBFS: unsatisfiable build-dependency: 
node-hapi-boom (>= 7.0.0) (versioned dep on a virtual pkg?)
Added indication that 952129 affects src:node-cryptiles
> close 952129 7.4.3-1
Bug #952129 [node-boom] node-cryptiles: FTBFS: unsatisfiable build-dependency: 
node-hapi-boom (>= 7.0.0) (versioned dep on a virtual pkg?)
Marked as fixed in versions node-boom/7.4.3-1.
Bug #952129 [node-boom] node-cryptiles: FTBFS: unsatisfiable build-dependency: 
node-hapi-boom (>= 7.0.0) (versioned dep on a virtual pkg?)
Marked Bug as done
> reassign 952132 rollup
Bug #952132 [src:vue-router.js] vue-router.js: FTBFS: build-dependency not 
installable: rollup
Bug reassigned from package 'src:vue-router.js' to 'rollup'.
No longer marked as found in versions vue-router.js/3.0.7+ds-2.
Ignoring request to alter fixed versions of bug #952132 to the same values 
previously set
> affects 952129 src:vue-router.js
Bug #952129 {Done: Adrian Bunk } [node-boom] node-cryptiles: 
FTBFS: unsatisfiable build-dependency: node-hapi-boom (>= 7.0.0) (versioned dep 
on a virtual pkg?)
Added indication that 952129 affects src:vue-router.js
> close 952129 0.68.2+ds-1
Bug #952129 {Done: Adrian Bunk } [node-boom] node-cryptiles: 
FTBFS: unsatisfiable build-dependency: node-hapi-boom (>= 7.0.0) (versioned dep 
on a virtual pkg?)
There is no source info for the package 'node-boom' at version '0.68.2+ds-1' 
with architecture ''
Unable to make a source version for version '0.68.2+ds-1'
Marked as fixed in versions 0.68.2+ds-1.
Bug #952129 {Done: Adrian Bunk } [node-boom] node-cryptiles: 
FTBFS: unsatisfiable build-dependency: node-hapi-boom (>= 7.0.0) (versioned dep 
on a virtual pkg?)
Bug 952129 is already marked as done; not doing anything.
> reassign 952143 node-hoek 9.0.3+~5.0.0+~4.0.0-2
Bug #952143 [src:node-sntp] node-sntp: FTBFS: unsatisfiable build-dependencies: 
node-hapi-teamwork (>= 3.0.0)
Bug reassigned from package 'src:node-sntp' to 'node-hoek'.
No longer marked as found in versions node-sntp/3.1.2-2.
Ignoring request to alter fixed versions of bug #952143 to the same values 
previously set
Bug #952143 [node-hoek] node-sntp: FTBFS: unsatisfiable build-dependencies: 
node-hapi-teamwork (>= 3.0.0)
Marked as found in versions node-hoek/9.0.3+~5.0.0+~4.0.0-2.
> reassign 952148 node-hoek 9.0.3+~5.0.0+~4.0.0-2
Bug #952148 [src:node-hawk] node-hawk: FTBFS: unsatisfiable build-dependencies 
(purely virtual?): node-hapi-sntp (>= 3.0.0), node-hapi-hoek (>= 8.0.0), 
node-hapi-boom (>= 7.0.0), node-hapi-cryptiles (>= 4.0.0)
Bug reassigned from package 'src:node-hawk' to 'node-hoek'.
No longer marked as found in versions node-hawk/7.1.2+dfsg-1.
Ignoring request to alter fixed versions of bug #952148 to the same values 
previously set
Bug #952148 [node-hoek] node-hawk: FTBFS: unsatisfiable build-dependencies 
(purely virtual?): node-hapi-sntp (>= 3.0.0), node-hapi-hoek (>= 8.0.0), 
node-hapi-boom (>= 7.0.0), node-hapi-cryptiles (>= 4.0.0)
Marked as found in versions node-hoek/9.0.3+~5.0.0+~4.0.0-2.
> forcemerge 952143 952148
Bug #952143 [node-hoek] node-sntp: FTBFS: unsatisfiable build-dependencies: 
node-hapi-teamwork (>= 3.0.0)
Bug #952148 [node-hoek] node-hawk: FTBFS: unsatisfiable build-dependencies 
(purely virtual?): node-hapi-sntp (>= 3.0.0), node-hapi-hoek (>= 8.0.0), 
node-hapi-boom (>= 7.0.0), node-hapi-cryptiles (>= 4.0.0)
Merged 952143 952148
> affects 952143 src:node-sntp src:node-hawk
Bug #952143 [node-hoek] node-sntp: FTBFS: unsatisfiable build-dependencies: 
node-hapi-teamwork (>= 3.0.0)
Bug #952148 [node-hoek] node-hawk: FTBFS: unsatisfiable build-dependencies 
(purely virtual?): node-hapi-sntp (>= 3.0.0), node-hapi-hoek (>= 8.0.0), 
node-hapi-boom (>= 7.0.0), node-hapi-cryptiles (>= 4.0.0)
Added indication that 952143 affects src:node-sntp and src:node-hawk
Added indication that 952148 affects src:node-sntp and src:node-hawk
> retitle 952143 node-hoek: node-hapi-hoek provides lost version
Bug #952143 [node-hoek] node-sntp: FTBFS: unsatisfiable build-dependencies: 
node-hapi-teamwork (>= 3.0.0)
Bug #952148 [node-hoek] node-hawk: FTBFS: unsatisfiable build-dependencies 
(purely virtual?): node-hapi-sntp (>= 3.0.0), node-hapi-hoek (>= 8.0.0), 
node-hapi-boom (>= 7.0.0), node-hapi-cryptiles (>= 4.0.0)
Changed Bug title to 'node-hoek: node-hapi-hoek provides lost version' from 
'node-sntp: FTBFS: unsatisfiable build-dependencies: node-hapi-teamwork (>= 
3.0.0)'.
Changed Bug title to 'node-hoek: node-hapi-hoek provides lost version' 

Bug#954688: marked as done (with-simulated-input-el: FTBFS: Spies can only be created in ‘before-each’)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 11:36:27 +
with message-id 
and subject line Bug#954688: fixed in with-simulated-input-el 
2.4+git20200216.29173588-1
has caused the Debian Bug report #954688,
regarding with-simulated-input-el: FTBFS: Spies can only be created in 
‘before-each’
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: with-simulated-input-el
Version: 2.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200322 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> skipping upstream build
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L .
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Spies can only be created in ‘before-each’
> dh_elpa_test: error: buttercup -L . returned exit code 255
> make: *** [debian/rules:4: binary] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/22/with-simulated-input-el_2.4-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: with-simulated-input-el
Source-Version: 2.4+git20200216.29173588-1
Done: Lev Lamberov 

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

Debian distribution maintenance software
pp.
Lev Lamberov  (supplier of updated with-simulated-input-el 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 16:04:17 +0500
Source: with-simulated-input-el
Architecture: source
Version: 2.4+git20200216.29173588-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Lev Lamberov 
Closes: 954688
Changes:
 with-simulated-input-el (2.4+git20200216.29173588-1) unstable; urgency=medium
 .
   * New upstream version 2.4+git20200216.29173588 (Closes: #954688)
   * Declare Standards-Version 4.5.0 (no changes needed)
Checksums-Sha1:
 49d9ef5150f15a92fd997297546576f8e0d93e5b 2312 
with-simulated-input-el_2.4+git20200216.29173588-1.dsc
 fb13f7439eea6e7ae494173d51540fc3b15f1600 20802 
with-simulated-input-el_2.4+git20200216.29173588.orig.tar.gz
 0f65ea91ff52383a2d3c363bbcfd5b6656b18766 2492 
with-simulated-input-el_2.4+git20200216.29173588-1.debian.tar.xz
 94229c55fbceebb769b940e2f5de000f369bddf1 7766 
with-simulated-input-el_2.4+git20200216.29173588-1_amd64.buildinfo
Checksums-Sha256:
 f5f316cda3cb21d877a14c52d51223a0cbd9645aa730d5224cea149f1114def8 2312 
with-simulated-input-el_2.4+git20200216.29173588-1.dsc
 5d093c3512534ddbab4b3e37e433b55680e924faa1f8c347d903b0cab845a1fe 20802 
with-simulated-input-el_2.4+git20200216.29173588.orig.tar.gz
 3a30051eea809c740f44fe77b57e5a44b4edbe06be2116305466cc85b6d070f5 2492 
with-simulated-input-el_2.4+git20200216.29173588-1.debian.tar.xz
 96a95652661aac87fb7181997debbe00c03ac25d8b0fcd73cd2b7d8e0f41d16b 7766 
with-simulated-input-el_2.4+git20200216.29173588-1_amd64.buildinfo
Files:
 11468325761f43da3380e0692b105c9a 2312 lisp optional 
with-simulated-input-el_2.4+git20200216.29173588-1.dsc
 acc932194200912587335387c4122f12 20802 lisp optional 
with-simulated-input-el_2.4+git20200216.29173588.orig.tar.gz
 95c80b3ac6273173a66a333f73aa9238 2492 lisp optional 
with-simulated-input-el_2.4+git20200216.29173588-1.debian.tar.xz
 fd56d73f1eea26bed70c03ea29d3df8c 7766 lisp optional 
with-simulated-input-el_2.4+git20200216.29173588-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: RFS: ukui-control-center/2.0.0-1 -- utilities to configure the UKUI desktop

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 941848
Bug #941848 [sponsorship-requests] RFS: ukui-control-center/2.0.0-1 -- 
utilities to configure the UKUI desktop
Marked Bug as done
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
941848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#953777: marked as done (php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' not found)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 10:53:07 +
with message-id 
and subject line Bug#953777: fixed in php-doctrine-cache 1.10.0-4
has caused the Debian Bug report #953777,
regarding php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' 
not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
953777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-apcu, php-doctrine-cache
Control: found -1 php-apcu/5.1.18+4.0.11-1
Control: found -1 php-doctrine-cache/1.10.0-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of php-apcu the autopkgtest of php-doctrine-cache
fails in testing when that autopkgtest is run with the binary packages
of php-apcu from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
php-apcu   from testing5.1.18+4.0.11-1
php-doctrine-cache from testing1.10.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. As php-apcu is
part of the php7.4 transition, I wouldn't be surprised if this failure
is due to a missing (versioned) (test) dependency somewhere, and the
test is mixing and matching php7 versions (both php7.3 and php7.4 are
installed in the test).

Currently this regression is blocking the migration of php-apcu to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? There is a bug (#953727) with the
same symptoms filed against php-codecoverage and xdebug. The underlying
issue may be the same.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=php-apcu

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-doctrine-cache/4542910/log.gz

autopkgtest [17:47:34]: test command1: mkdir -p vendor debian/tmp &&
phpab -o vendor/autoload.php -t debian/autoload.tests.php.tpl tests &&
memcached -d -u memcache && redis-server --daemonize yes && phpunit
--bootstrap vendor/autoload.php
autopkgtest [17:47:34]: test command1: [---
phpab %development% - Copyright (C) 2009 - 2020 by Arne Blankerts and
Contributors

Scanning directory tests

Autoload file vendor/autoload.php generated.

12043:C 12 Mar 2020 17:47:34.337 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
12043:C 12 Mar 2020 17:47:34.337 # Redis version=5.0.7, bits=64,
commit=, modified=0, pid=12043, just started
12043:C 12 Mar 2020 17:47:34.337 # Configuration loaded
Class 'DOMDocument' not found
autopkgtest [17:47:34]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: php-doctrine-cache
Source-Version: 1.10.0-4
Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= 

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-doctrine-cache 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 11:24:53 +0100
Source: php-doctrine-cache
Architecture: source
Version: 1.10.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Ondřej Surý 
Closes: 953777
Changes:
 php-doctrine-cache (1.10.0-4) unstable; urgency=medium
 .
   * Team upload.
   * The autopkgtest dependencies were underspecified (Closes: #953777)
Checksums-Sha1:
 676e918bfd3ad4adc4aee25b20f11a282be7e55b 2533 php-doctrine-cache_1.10.0-4.dsc
 ce17b5af65674642483b9913877da170df68f523 9256 
php-doctrine-cache_1.10.0-4.debian.tar.xz
 7caf185fd50a1d45743124efc550d0e4597efddf 8813 

Bug#953555: marked as done (/usr/bin/glslangValidator: glslangValidator broken with some spirv-tools versions)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 10:51:33 +
with message-id 
and subject line Bug#953555: fixed in glslang 8.13.3559-3
has caused the Debian Bug report #953555,
regarding /usr/bin/glslangValidator: glslangValidator broken with some 
spirv-tools versions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
953555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glslang-tools
Version: 8.13.3559-2
Severity: important
File: /usr/bin/glslangValidator

$ glslangValidator 
glslangValidator: error while loading shared libraries: libSPIRV-Tools.so: 
cannot open shared object file: No such file or directory
$

$ ldd `which glslangValidator `
linux-vdso.so.1 (0x7ffcba1f)
libSPIRV-Tools.so => not found
libSPIRV-Tools-opt.so => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fe4b6584000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fe4b63b8000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fe4b6273000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fe4b60b3000)
/lib64/ld-linux-x86-64.so.2 (0x7fe4b6f93000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fe4b6097000)
$

$ dpkg -L spirv-tools | grep lib
/usr/include/spirv-tools/libspirv.h
/usr/include/spirv-tools/libspirv.hpp
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libSPIRV-Tools-link.a
/usr/lib/x86_64-linux-gnu/libSPIRV-Tools-opt.a
/usr/lib/x86_64-linux-gnu/libSPIRV-Tools-reduce.a
/usr/lib/x86_64-linux-gnu/libSPIRV-Tools-shared.so
/usr/lib/x86_64-linux-gnu/libSPIRV-Tools.a
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/SPIRV-Tools-shared.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/SPIRV-Tools.pc
$


$ dpkg -l spirv-tools | egrep ^ii
ii  spirv-tools2019.4-1 amd64API and commands for processing 
SPIR-V modules
$

Updating to spirv-tools 2019.5-1 does fix it tho, so maybe some version
constrain in dependencies of glslang-tools would be useful to have?

Cheers,
Witold


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages glslang-tools depends on:
ii  libc62.29-10
ii  libstdc++6   10-20200222-1
ii  spirv-tools  2019.4-1

glslang-tools recommends no packages.

glslang-tools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glslang
Source-Version: 8.13.3559-3
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated glslang 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 12:31:08 +0200
Source: glslang
Architecture: source
Version: 8.13.3559-3
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 953555
Changes:
 glslang (8.13.3559-3) unstable; urgency=medium
 .
   * control: Bump dependency on spirv-tools to match where shared libs
 were introduced. (Closes: #953555)
   * control: Build on all archs again.
Checksums-Sha1:
 730cb583be421e7f2e8c861a149af03417765ac0 2121 glslang_8.13.3559-3.dsc
 dfe08fd8c5592a96ceb593a7bc779a4e569eb473 13130 glslang_8.13.3559-3.diff.gz
 4eeea9e94c8186e86c7378946df9c5fdfc86a0ba 6975 
glslang_8.13.3559-3_source.buildinfo
Checksums-Sha256:
 a5c6397ba4c1896eccc074ac9500a4aadca7950cd7f79a514d91fb9f8fe5c1e6 2121 
glslang_8.13.3559-3.dsc
 

Bug#954717: marked as done (gnome-session-flashback: conffiles not removed)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 10:36:12 +
with message-id 
and subject line Bug#954717: fixed in gnome-flashback 3.36.0-3
has caused the Debian Bug report #954717,
regarding gnome-session-flashback: conffiles not removed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
954717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-session-flashback
Version: 3.36.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate

The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.

https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb

This bug report brought to you by adequate:

https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/

$ p=gnome-session-flashback ; adequate $p ; dpkg-query -W -f='${Conffiles}\n' 
$p | grep obsolete
gnome-session-flashback: obsolete-conffile 
/etc/xdg/autostart/gnome-flashback-screensaver.desktop
 /etc/xdg/autostart/gnome-flashback-screensaver.desktop 
4b4a9ed842f6534d0af6359a1d15309b obsolete

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (860, 
'testing-proposed-updates'), (800, 'unstable-debug'), (800, 'unstable'), (790, 
'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 
'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-session-flashback depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gnome-flashback  3.36.0-2
ii  gnome-panel  3.36.0-1
ii  gnome-session-bin3.36.0-1
ii  gnome-session-common 3.36.0-1
ii  gnome-settings-daemon3.36.0-1
ii  metacity 1:3.36.0-1

Versions of packages gnome-session-flashback recommends:
ii  gnome-power-manager  3.32.0-2

Versions of packages gnome-session-flashback suggests:
ii  desktop-base 10.0.3
ii  gnome-keyring3.34.0-1
ii  gnome-user-docs  3.36.0-1

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: gnome-flashback
Source-Version: 3.36.0-3
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated gnome-flashback 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 23 Mar 2020 13:11:39 +0300
Source: gnome-flashback
Architecture: source
Version: 3.36.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Dmitry Shachnev 
Closes: 954717
Changes:
 gnome-flashback (3.36.0-3) unstable; urgency=medium
 .
   * Remove gnome-screensaver autostart file on upgrade. (Closes: #954717)
   * Backport upstream patch to disable unimplemented placement modes.
   * Backport upstream patch to fix locking screen from end session dialog.
Checksums-Sha1:
 a5ba3a235d2c0437c8aa4f232e697a9e6dafe482 2898 gnome-flashback_3.36.0-3.dsc
 190b16988476bba30bae1db21b67496aeb168b6c 10236 
gnome-flashback_3.36.0-3.debian.tar.xz
 454887fc66d3cfbfa8daf6f9fbde36c21379ef8a 16459 
gnome-flashback_3.36.0-3_source.buildinfo
Checksums-Sha256:
 01a64be559c39e7946a95d598d9c8eb5004ec1d5920f43bfad008b9591f5b1fe 2898 

Processed: closing 952608

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 952608
Bug #952608 [src:php-defaults] src:php-defaults: Block transition until PECL 
extensions are rebuilt
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
952608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#504754: marked as done (audacious: Please include a Debian skin like xmms did)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 09:49:35 +
with message-id 
and subject line Bug#504754: fixed in audacious-plugins 4.0-2
has caused the Debian Bug report #504754,
regarding audacious: Please include a Debian skin like xmms did
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
504754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: audacious
Version: 1.5.1-4
Severity: wishlist

The old xmms package contained a nice Debian skin, which I liked very
much. The file in the old package was
/usr/share/xmms/Skins/debfskin.tar.gz

I've tested this skin with audacious and it works. Would it be possible to
include this skin in the package?


--- End Message ---
--- Begin Message ---
Source: audacious-plugins
Source-Version: 4.0-2
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated audacious-plugins 
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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 23 Mar 2020 10:34:17 +0100
Source: audacious-plugins
Architecture: source
Version: 4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Andrej Shadura 
Closes: 504754
Changes:
 audacious-plugins (4.0-2) unstable; urgency=medium
 .
   * Add the Debian XMMS skin (Closes: #504754).
   * Update copyrights.
Checksums-Sha1:
 774516201b17bc70be82245d95320c41031adfdd 2851 audacious-plugins_4.0-2.dsc
 534292f72a9ca429cfd3e134016d2d97e0741a67 50504 
audacious-plugins_4.0-2.debian.tar.xz
Checksums-Sha256:
 dcb89ce0d16f7f7e8eeb0867ee673ffe6148ae5d58372fd908d381fd786fc49b 2851 
audacious-plugins_4.0-2.dsc
 867f0e19484f7c8e2311a4f35a44e84b4ccc796b90ab2fce397a0176a2cc34fc 50504 
audacious-plugins_4.0-2.debian.tar.xz
Files:
 7213efac39a62629503fec866c8511b9 2851 sound optional 
audacious-plugins_4.0-2.dsc
 030f5a8354ee0965448ed9f3253141ab 50504 sound optional 
audacious-plugins_4.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl54g7cACgkQXkCM2RzY
OdLzCgf/UZWu0X+t6Sgs9vFi4pspLyWQ8fU9tM80/CGJAUQzpc3LUhye4XqckRmX
cnedL7vrFL3Vqy/8iuBz127HjYsiOZDDu0385CRx35d9yPhI6FoN49nfXytdkzph
+cbU5/2uYrLqbBBjWJQMeSyxCm/3deGQq+Y5ENqt/cTQ/CHvey/MyM0xwF1XAxWz
K24uyrlodctIbtJabsZ8+1Rx2z2Xdk7JZmzcYaAOQqTjVtwIpZVmiHqcHg7yv3ZK
r95MiqSIME11BSwo1umwOiTdD9h6aG8CX0RoILFmjByOy7LLcUXpydxPVkKH0gSj
/2SXT/dCg38klWKLq1bRG4en5BN+9w==
=FpYX
-END PGP SIGNATURE End Message ---

Bug#909505: marked as done (bidentd: calls update-inetd with wrong arguments)

[Debian Bug Tracking System]

Your message dated Mon, 23 Mar 2020 09:49:41 +
with message-id 
and subject line Bug#909505: fixed in bidentd 1.1.4-1.2
has caused the Debian Bug report #909505,
regarding bidentd: calls update-inetd with wrong arguments
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bidentd
Version: 1.1.4-1.1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package bidentd.
  (Reading database ... 
(Reading database ... 8336 files and directories currently installed.)
  Preparing to unpack .../bidentd_1.1.4-1.1+b2_i386.deb ...
  Unpacking bidentd (1.1.4-1.1+b2) ...
  Setting up bidentd (1.1.4-1.1+b2) ...
  update-inetd: error: --pattern is not relevant with --add
  dpkg: error processing package bidentd (--configure):
   installed bidentd package post-installation script subprocess returned error 
exit status 255
  Errors were encountered while processing:
   bidentd


update-inetd got more strict recently and rejects superfluous
usage of --group


cheers,

Andreas


bidentd_1.1.4-1.1+b2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bidentd
Source-Version: 1.1.4-1.2
Done: Paride Legovini 

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

Debian distribution maintenance software
pp.
Paride Legovini  (supplier of updated bidentd 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 ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Mar 2020 13:12:52 +
Source: bidentd
Architecture: source
Version: 1.1.4-1.2
Distribution: unstable
Urgency: medium
Maintainer: Wesley W. Terpstra (Debian) 
Changed-By: Paride Legovini 
Closes: 909505
Changes:
 bidentd (1.1.4-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * postinst: do not call update-inetd with the --pattern option when --add
 is used (closes: #909505).
Checksums-Sha1:
 3a50eb06639e470c97cd3ab800993d7cb96cbbb2 1701 bidentd_1.1.4-1.2.dsc
 5ee93e853c8bf1c745f2d9c89dd7d6cd032e5ce7 15988 bidentd_1.1.4-1.2.debian.tar.xz
 86660a9393bacdf67ec454e47ec62e385112ef50 6002 bidentd_1.1.4-1.2_amd64.buildinfo
Checksums-Sha256:
 8a4db60a728510782480a8c8f6b5adf08dc1e7b339eb171571eebe50d299eef0 1701 
bidentd_1.1.4-1.2.dsc
 72312ec7f55b23d1cd3e6f73093782e8aa544959a4dcd9b8dbc004328657fab5 15988 
bidentd_1.1.4-1.2.debian.tar.xz
 c4ec4679884822d0a79610e3381624ba8b382c796edad04bc70daf6339819bf4 6002 
bidentd_1.1.4-1.2_amd64.buildinfo
Files:
 dfd93dc0cac29d6993b2961b24b36030 1701 net extra bidentd_1.1.4-1.2.dsc
 b4da39c597cbac848f486876a2929cef 15988 net extra 
bidentd_1.1.4-1.2.debian.tar.xz
 2deb4eb3a4dfdb273e4b687df31fcc5b 6002 net extra 
bidentd_1.1.4-1.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEESYqTBWsFJgT6y8ijKb+g0HkpCsoFAl54g5sACgkQKb+g0Hkp
Csp2PxAAgsBz0d/UCCyL07QyGK4nVKqDAgXRiHc/czv1tSqAmMfjwMOJ0Pfe2oLN
+XqB8NuNPO7xPnE93hg6NUPeBE+Kl7Q0RBQEobelXrM2RnxXtABiGyzTKqxbcTMh
f2a4foc/vx6NEwaRvuVr5ArKD6Or0dfjt1nuyUGOkWmdY80gegPr5+Kh/mt48Rko
jqg4vcqakdt8tl2ID8y+kLIqTk8XL7geaXaFFRvCP+OIY9IwpgejV2yw469xqUZa
9NAMlqIOkcceunocR7mgeO65SjuuXsVJGfDYcPDnfqg1pkkU3EnxXZkMssp81kW8
FwPIF8H4L3YzIdNoc9xf1Ht6B6om3K3pfo5iR5uxJyZCb/0704KCmVT6OEBEuE7T
/O964ZH/yWLBoASpnhS/8m6EOxyRpASZQGqX/MvLHb/sctgdticfP9EXnyStxj3A
rxYWL8OkBewOoVUGDblQz1MMd1nc4L500RBTtJrF7iCGxhL5eqt6e97leCQsN1we
EJdErkmUKkE068V3V2Qyky3qs1eeKvWEaHFgmcy1xtl1EUbdAj4hcJMKAuMW/nr/
odySZ1lykboe32gfmCLB867qkJM7Qb9ayF5VGm/UBPvwJiNOOuqHb5PnQbS6kLV7
mmIH7Bvfi3ks+kYgnLvFH/E0t/tMqxbfQkNpVnKWDBsj2/8f/Mc=
=n2JR
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 920245 1.17.4-1
Bug #920245 {Done: Janos LENART } [src:kubernetes] 
kubernetes: build-depends on non-existing 
golang-github-opencontainers-docker-runc-dev
Marked as fixed in versions kubernetes/1.17.4-1.
Bug #920245 {Done: Janos LENART } [src:kubernetes] 
kubernetes: build-depends on non-existing 
golang-github-opencontainers-docker-runc-dev
Bug 920245 is already marked as done; not doing anything.
> close 860502 1.17.4-1
Bug #860502 {Done: Janos LENART } [src:kubernetes] 
kubernetes: FTBFS w/etcd 2.x (on armel and armhf)
Marked as fixed in versions kubernetes/1.17.4-1.
Bug #860502 {Done: Janos LENART } [src:kubernetes] 
kubernetes: FTBFS w/etcd 2.x (on armel and armhf)
Bug 860502 is already marked as done; not doing anything.
> close 860504 1.17.4-1
Bug #860504 {Done: Janos LENART } [src:kubernetes] 
kubernetes: FTBFS on ppc64el: relocations too big
Marked as fixed in versions kubernetes/1.17.4-1.
Bug #860504 {Done: Janos LENART } [src:kubernetes] 
kubernetes: FTBFS on ppc64el: relocations too big
Bug 860504 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
860502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860502
860504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860504
920245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems