Bug#967655: marked as done (nitrokey-app: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 15:50:03 +
with message-id 
and subject line Bug#967655: fixed in nitrokey-app 1.4.1-1
has caused the Debian Bug report #967655,
regarding nitrokey-app: depends on deprecated GTK 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.)


-- 
967655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitrokey-app
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: nitrokey-app
Source-Version: 1.4.1-1
Done: Jan Luca Naumann 

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

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated nitrokey-app 
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, 06 Aug 2020 12:08:55 +0200
Source: nitrokey-app
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jan Luca Naumann 
Changed-By: Jan Luca Naumann 
Closes: 967655
Changes:
 nitrokey-app (1.4.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/control:
 - Update to Debian policy 4.5.0, no changes needed.
 - Clean up Build-Depends. (Closes: #967655)
   * debian/compat: Update to compat version 13.
Checksums-Sha1:
 6253096e32d658e5d211e8df4d8ad7449a1b6a9c 2091 nitrokey-app_1.4.1-1.dsc
 2cf52015a377f32c632760b1fe4d91cde534a0cd 1316160 nitrokey-app_1.4.1.orig.tar.gz
 b4076b6e969a6884a87dd4d2195bf7762ae1795d 5644 
nitrokey-app_1.4.1-1.debian.tar.xz
 075f727043d1c3af75d2df5fc0a06f5c0a055f88 11461 
nitrokey-app_1.4.1-1_amd64.buildinfo
Checksums-Sha256:
 3e4a2b98460a68b6009701ddb987c979f1d5b1c7b6bea48020daaccd406e8073 2091 
nitrokey-app_1.4.1-1.dsc
 

Bug#932639: marked as done (nss-pem FTCBFS: does not pass cross flags to cmake)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 15:50:15 +
with message-id 
and subject line Bug#932639: fixed in nss-pem 1.0.6-1
has caused the Debian Bug report #932639,
regarding nss-pem FTCBFS: does not pass cross flags to cmake
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.)


-- 
932639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss-pem
Version: 1.0.5-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

nss-pem fails to cross build from source, because it does not pass cross
flags to cmake. The easiest way of doing so - using dh_auto_configure -
makes nss-pem cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru nss-pem-1.0.5/debian/changelog 
nss-pem-1.0.5/debian/changelog
--- nss-pem-1.0.5/debian/changelog  2019-07-08 15:01:00.0 +0200
+++ nss-pem-1.0.5/debian/changelog  2019-07-21 16:11:41.0 +0200
@@ -1,3 +1,10 @@
+nss-pem (1.0.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 21 Jul 2019 16:11:41 +0200
+
 nss-pem (1.0.5-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru nss-pem-1.0.5/debian/rules nss-pem-1.0.5/debian/rules
--- nss-pem-1.0.5/debian/rules  2019-07-08 14:46:29.0 +0200
+++ nss-pem-1.0.5/debian/rules  2019-07-21 16:11:34.0 +0200
@@ -7,12 +7,10 @@
dh $@ --builddirectory=build/
 
 override_dh_auto_configure:
-   mkdir build
-   cd build && cmake \
+   dh_auto_configure --sourcedirectory=src --
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
-   -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)/nss \
-   ../src
+   -DLIB_INSTALL_DIR=/usr/lib/$(DEB_HOST_MULTIARCH)/nss
 
 override_dh_auto_build:
(cd nss; QUILT_PATCHES=debian/patches quilt push -a; debian/rules build)
--- End Message ---
--- Begin Message ---
Source: nss-pem
Source-Version: 1.0.6-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated nss-pem 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, 06 Aug 2020 18:35:59 +0300
Source: nss-pem
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 932639 963291
Changes:
 nss-pem (1.0.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Bump policy to 4.5.0.
   * nss: Refreshed to 3.55-1.
   * migrate-to-nss-names.diff: Migrate from NETSCAPE to NSS attributes.
 (Closes: #963291)
   * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. Thanks,
 Helmut Grohne! (Closes: #932639)
Checksums-Sha1:
 804b06b71f8f7b2678bc5cb21c535d75786827a2 2067 nss-pem_1.0.6-1.dsc
 6a80b48ca42c6bd1cfc76c03233566ce1d201664 62953284 nss-pem_1.0.6.orig.tar.xz
 27b1b88e4fb5614027f641f493821206bc766dd7 5488 nss-pem_1.0.6-1.debian.tar.xz
 11d7e621c4d99dec1a608d0174a53c517b29a19b 6618 nss-pem_1.0.6-1_source.buildinfo
Checksums-Sha256:
 7f6068905721bb1c3e033b8bd761536d4efa8eaf179c16f6be9e342a68fae962 2067 
nss-pem_1.0.6-1.dsc
 a5c7e65c2010f67ff835d605e479b72743bb6908101375e228bbc6e3dc2b364f 62953284 
nss-pem_1.0.6.orig.tar.xz
 55eaaf80e479690f9d46fdaee562b798997632fab4511f4d91e8eae0404eb687 5488 
nss-pem_1.0.6-1.debian.tar.xz
 6e06518d2998132b544947c719117ad1f09a22d06f710e5364c11e3b8f8ed90c 6618 
nss-pem_1.0.6-1_source.buildinfo
Files:
 fb6f7ad1572e7b0342fa0eb683a0d4c1 2067 libs optional nss-pem_1.0.6-1.dsc
 aa37a495e712215d190b701166d461db 62953284 libs optional 
nss-pem_1.0.6.orig.tar.xz
 b856497b38fc863571b879e6b7768c52 5488 libs optional 
nss-pem_1.0.6-1.debian.tar.xz
 d9d97a78c75165812299aa8f2a520cc9 6618 libs optional 
nss-pem_1.0.6-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#964662: marked as done (tomcatjss: FTBFS: [javac] /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25: error: package org.apache.tomcat.util.net.jsse does not exist)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:20:49 +
with message-id 
and subject line Bug#964433: fixed in tomcat9 9.0.37-3
has caused the Debian Bug report #964433,
regarding tomcatjss: FTBFS: [javac] 
/<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25: 
error: package org.apache.tomcat.util.net.jsse does not exist
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.)


-- 
964433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tomcatjss
Version: 7.4.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 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 '/<>'
> ant \
>   -Dant.build.javac.source=1.8 -Dant.build.javac.target=1.8 \
>   -Dsrc.dir=tomcat-8.5 \
>   -Dcatalina.jar=/usr/share/java/tomcat9-catalina.jar \
>   -Dtomcat-api.jar=/usr/share/java/tomcat9-api.jar \
>   -Dtomcat-coyote.jar=/usr/share/java/tomcat9-coyote.jar \
>   -Dtomcat-juli.jar=/usr/share/java/tomcat9-juli.jar \
>   -Dinstall.doc.dir=build/usr/share/doc/tomcatjss \
>   -Dinstall.jar.dir=build/usr/share/java \
>   -Dslf4j-api.jar=/usr/share/java/slf4j-api.jar \
>   install
> Buildfile: /<>/build.xml
> 
> compile:
> [mkdir] Created dir: /<>/build/classes
> [javac] /<>/build.xml:220: warning: 'includeantruntime' was 
> not set, defaulting to build.sysclasspath=last; set to false for repeatable 
> builds
> [javac] Compiling 9 source files to /<>/build/classes
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 8
> [javac] /<>/src/org/dogtagpki/tomcat/JSSKeyManager.java:36: 
> warning: X509CertImpl is internal proprietary API and may be removed in a 
> future release
> [javac] import sun.security.x509.X509CertImpl;
> [javac] ^
> [javac] 
> /<>/src/org/dogtagpki/tomcat/JSSTrustManager.java:37: warning: 
> X509CertImpl is internal proprietary API and may be removed in a future 
> release
> [javac] import sun.security.x509.X509CertImpl;
> [javac] ^
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25:
>  error: package org.apache.tomcat.util.net.jsse does not exist
> [javac] import org.apache.tomcat.util.net.jsse.JSSEImplementation;
> [javac]   ^
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:29:
>  error: cannot find symbol
> [javac] public class JSSImplementation extends JSSEImplementation {
> [javac]^
> [javac]   symbol: class JSSEImplementation
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSUtil.java:26: error: 
> package org.apache.tomcat.util.net.jsse does not exist
> [javac] import org.apache.tomcat.util.net.jsse.JSSEKeyManager;
> [javac]   ^
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSUtil.java:27: error: 
> package org.apache.tomcat.util.net.jsse does not exist
> [javac] import org.apache.tomcat.util.net.jsse.JSSEUtil;
> [javac]   ^
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSUtil.java:31: error: 
> cannot find symbol
> [javac] public class JSSUtil extends JSSEUtil {
> [javac]  ^
> [javac]   symbol: class JSSEUtil
> [javac] /<>/src/org/dogtagpki/tomcat/JSSKeyManager.java:87: 
> warning: X509CertImpl is internal proprietary API and may be removed in a 
> future release
> [javac] list.add(new X509CertImpl(c.getEncoded()));
> [javac]  ^
> [javac] 
> /<>/src/org/dogtagpki/tomcat/JSSTrustManager.java:181: warning: 
> X509CertImpl is internal proprietary API and may be removed in a future 
> release
> [javac] X509CertImpl caCert = new 
> X509CertImpl(cert.getEncoded());
> [javac] ^
> [javac] 
> /<>/src/org/dogtagpki/tomcat/JSSTrustManager.java:181: warning: 
> X509CertImpl is internal proprietary API and may be removed in a future 
> release
> [javac] X509CertImpl caCert = new 
> X509CertImpl(cert.getEncoded());
> [javac]   ^
> [javac] 
> /<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:37:
>  error: method 

Bug#964433: marked as done (libtomcat9-java: tomcatjss fails to build with the latest libtomcat9-java)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:20:49 +
with message-id 
and subject line Bug#964433: fixed in tomcat9 9.0.37-3
has caused the Debian Bug report #964433,
regarding libtomcat9-java: tomcatjss fails to build with the latest 
libtomcat9-java
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.)


-- 
964433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtomcat9-java
Version: 9.0.37-1
Severity: important

Hi,

A recent update has broke tomcatjss build:

[javac] 
/<>/tomcat-8.5/src/org/dogtagpki/tomcat/JSSImplementation.java:25: 
error: package org.apache.tomcat.util.net.jsse does not exist
[javac] import org.apache.tomcat.util.net.jsse.JSSEImplementation;

It built fine with 9.0.35-1 when 7.5.0~a1-1 was uploaded to experimental, now a 
new beta2
and the version in sid both fail.
--- End Message ---
--- Begin Message ---
Source: tomcat9
Source-Version: 9.0.37-3
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated tomcat9 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, 06 Aug 2020 18:59:11 +0300
Source: tomcat9
Architecture: source
Version: 9.0.37-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Timo Aaltonen 
Closes: 964433
Changes:
 tomcat9 (9.0.37-3) unstable; urgency=medium
 .
   * control: Bump build-dep on bnd, drop bnd compat and re-export patches.
 (Closes: #964433)
Checksums-Sha1:
 bca33a258e1e669d0433c49ae50b85f98d73958c 2723 tomcat9_9.0.37-3.dsc
 338d7d196b91492fc1d95aa7b83cbc139aff3d10 33548 tomcat9_9.0.37-3.debian.tar.xz
 04d895f34ef2cf10f6804dd3b562bddcc9ed028c 14284 
tomcat9_9.0.37-3_source.buildinfo
Checksums-Sha256:
 a596b2faa1eeec84a8e08ee28699ff10028a29f020f4b965dc06e0bf1d425d41 2723 
tomcat9_9.0.37-3.dsc
 dd443cdc42e4708c9c150172f094ab82d7de0728a4c3338efa81d0c396839063 33548 
tomcat9_9.0.37-3.debian.tar.xz
 187ab4beee121da78d99c8d7d2d9a43f5df31a88c8cb00a330ee82433b4bac6a 14284 
tomcat9_9.0.37-3_source.buildinfo
Files:
 ab9b5ee21a4c14cfdaf065bd0ed65b4f 2723 java optional tomcat9_9.0.37-3.dsc
 074986a10e68121bbb7672267b83d93b 33548 java optional 
tomcat9_9.0.37-3.debian.tar.xz
 3dbd860caab451cbe16d6b094405b002 14284 java optional 
tomcat9_9.0.37-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl8sKOkACgkQy3AxZaiJ
hNxUew/7BOFye7ArqbJ4rvKyg6n2EJs2uXi73eRO7RSinbCPLEJbtjM94jDpbQyf
BPou+90A/EODgkCFpwfa+BSxiwvzohs++Zua1kZNI67nC2Fv1cjcOgavfnOezWVV
7T1Ubz2mrl0gxeMqw3U7m+eynUODlYx9r3tHd/QMmUwaStpn73/zH0k3wISHIGqa
6NZp3RgCMkEIvRC6PS4RTxwCDJssoPhrAr+5fvvMsHSOzl3fN46nVzov7dsC9bS/
RfL4YfbPoS2eyX/h9IBxPeCjZw6W646tOHFx0r3atAiGPrPOj7JLtsBiytGKmu98
LmyokabYWeT1AkRcuPQ8ytS5bGHKgs+7XkR/BncabvwA0GTabcc9VXTAFMWmt5Hh
wYcbOSsgO2oVDDPq+E2LqnEHB/QhSGKwQedAkx5DnMeNe79vUeUTELw1GBypK96k
8s2wtmgGkZ3IXDOOoM0I6ydjMw4YoKTnh6eLrIp40ICwkERvEhIcrtb5qCMlLb8G
s+Pck4CnCsuaa8dmF4wp34vX+rERYMPfq9le6qH//vSzXV5G4ysACcsYThPDYdTO
9RXDyLPI81bm8yULWH/QJ8fP+rDiOtzh168HDIkziG5jXo9dkBTkl8bnb6/reMOh
zZusLhDD/rhVyGcaupkjTrbJPSJGwsRwPITWiLIUxREt2ydv0hM=
=6E4g
-END PGP SIGNATURE End Message ---

Bug#966495: marked as done (python-pyxs: please make the build reproducible)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:20:19 +
with message-id 
and subject line Bug#966495: fixed in python-pyxs 0.4.2~git20190115.97f14313-3
has caused the Debian Bug report #966495,
regarding python-pyxs: please make the build reproducible
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.)


-- 
966495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyxs
Version: 0.4.2~git20190115.97f14313-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] I noticed that
python-pyxs could not be built reproducibly.

This is because the linkcode Sphinx extension and linkcode_resolve get
confused and try to link to the documentation to the @contextlib.contextmanager
decorator, and then uses relpath... All this results in links differing
depending on the number of directory components in the absolute build path:

  
href="https://github.com/selectel/pyxs/tree/0.4.2-dev/pyxs/../../../../usr/lib/python3.8/contextlib.py#L25-L33

vs.

  
href="https://github.com/selectel/pyxs/tree/0.4.2-dev/pyxs/../../../../../usr/lib/python3.8/contextlib.py#L25-L33;

As these links are broken anyway, I've attached a patch that will simply
hide them if we know they will be wrong. I think the right fix would be
to resolve the location of the exact function "underneath" the decorator.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/docs/conf.py  2020-07-29 11:09:24.036630132 +0100
--- b/docs/conf.py  2020-07-29 11:45:54.186574021 +0100
@@ -119,6 +119,8 @@
 import pyxs
 fn = inspect.getsourcefile(obj)
 fn = os.path.relpath(fn, os.path.dirname(pyxs.__file__))
+if fn.startswith(".."):
+return None
 source, lineno = inspect.getsourcelines(obj)
 return fn, lineno, lineno + len(source) - 1
 
--- End Message ---
--- Begin Message ---
Source: python-pyxs
Source-Version: 0.4.2~git20190115.97f14313-3
Done: =?utf-8?b?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= 

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

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated python-pyxs 
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, 06 Aug 2020 00:32:33 +0200
Source: python-pyxs
Architecture: source
Version: 0.4.2~git20190115.97f14313-3
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Hof 
Changed-By: Marc Dequènes (Duck) 
Closes: 966495
Changes:
 python-pyxs (0.4.2~git20190115.97f14313-3) unstable; urgency=medium
 .
   * Fix typo in Suggests.
   * Make python-pyxs-doc Multi-Arch: foreign.
   * Fix links in documentation. (Closes: #966495)
Checksums-Sha1:
 5b70c310838cff8f3b4fbd453b36162dc4b85e00 2190 
python-pyxs_0.4.2~git20190115.97f14313-3.dsc
 821e77c9c7d3d88b088bd522725f29197b628330 3352 
python-pyxs_0.4.2~git20190115.97f14313-3.debian.tar.xz
 8dd9582a9e04b2a2821bf8cbbf298e13d3e44c0d 7727 
python-pyxs_0.4.2~git20190115.97f14313-3_amd64.buildinfo
Checksums-Sha256:
 c0e5c9921635acb27c22b4000b99156d13a34162541a18145723f6f051df36f0 2190 
python-pyxs_0.4.2~git20190115.97f14313-3.dsc
 cc94cc449418a5a6f58ca85a2c664f6a6c027dc70c70fdeafcf741fdbe06d1d5 3352 
python-pyxs_0.4.2~git20190115.97f14313-3.debian.tar.xz
 e346dc121b1df13f3f226744da36ba8d55afb0fb4def3dbc8571b6ea08cfc3c1 7727 
python-pyxs_0.4.2~git20190115.97f14313-3_amd64.buildinfo
Files:
 5c48b3c5fbaf53aa5cce90b02341d62a 2190 python optional 
python-pyxs_0.4.2~git20190115.97f14313-3.dsc
 510e7ad406a8b09775de0990698f5340 3352 python optional 
python-pyxs_0.4.2~git20190115.97f14313-3.debian.tar.xz
 02720f21b0d81b8c4dfb1a940eb04480 7727 python optional 
python-pyxs_0.4.2~git20190115.97f14313-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#967241: marked as done (RM: twistedchecker/experimental -- ROM; Not in unstable, irrelevant for Debian)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:42:09 +
with message-id 
and subject line Bug#967241: Removed package(s) from experimental
has caused the Debian Bug report #967241,
regarding RM: twistedchecker/experimental -- ROM; Not in unstable, irrelevant 
for Debian
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.)


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

This package does not really belong in Debian and has never been in unstable.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from experimental:

twistedchecker |  0.0~r29-1 | source, all

--- Reason ---
ROM; Not in unstable, irrelevant for Debian
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#964541: marked as done (flatpak: Wrong argument order for clone syscall seccomp filter on s390x)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 22:33:39 +
with message-id 
and subject line Bug#964541: fixed in flatpak 1.8.1-2
has caused the Debian Bug report #964541,
regarding flatpak: Wrong argument order for clone syscall seccomp filter on 
s390x
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.)


-- 
964541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: make-dfsg
Version: 4.3-4
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy ubuntu-patch

In Ubuntu, the attached patch was applied to achieve the following:

The autopkgtests for flatpak-builder/s390x where failing with

  echo Building
  make: echo: Operation not permitted
  make: *** [Makefile:2: all] Error 127


git bisect lead to

commit 749a54d7a458dc6779936138caf40ce600a80052 (refs/bisect/bad)
Author: Aron Barath 
Date:   Mon Jul 9 09:05:31 2018 +0200

* job.c (child_execute_job): Prefer posix_spawn() over fork()/exec()

and I can confirm that disabling posix_spawn makes the autopkgtest
work again.

Earlier research also indicated that this is a heisenbug, if I try
to print to stderr before printing to stdout, no issue occurs.


  * Pass --disable-posix-spawn to configure, as use of posix_spawn()
causes a regression on s390x, with commands getting EPERM when
writing to stdout.


Thanks for considering the patch.

*** /tmp/tmp79xr4v61/make-dfsg_4.3-4ubuntu1.debdiff
diff -u make-dfsg-4.3/debian/rules make-dfsg-4.3/debian/rules
--- make-dfsg-4.3/debian/rules
+++ make-dfsg-4.3/debian/rules
@@ -28,13 +28,13 @@
mkdir -p $(BUILDDIR_GUILE)
ac_cv_lib_util_getloadavg=no dh_auto_configure --parallel \
-B$(BUILDDIR_GUILE) -- --prefix=$(PREFIX) $(confflags) \
-  --with-guile
+  --with-guile --disable-posix-spawn
 endif
 ifneq (,$(filter make, $(shell dh_listpackages)))
mkdir -p $(BUILDDIR_NORMAL)
ac_cv_lib_util_getloadavg=no dh_auto_configure --parallel  \
-B$(BUILDDIR_NORMAL) -- --prefix=$(PREFIX) $(confflags) \
-  --with-guile=no
+  --with-guile=no --disable-posix-spawn
 endif
 
 override_dh_auto_build:


-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy
  APT policy: (991, 'groovy'), (500, 'groovy'), (500, 'focal-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1018-oem (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: flatpak
Source-Version: 1.8.1-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated flatpak 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: Thu, 06 Aug 2020 22:45:21 +0100
Source: flatpak
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 964541
Changes:
 flatpak (1.8.1-2) unstable; urgency=medium
 .
   * Include flatpak-bisect and flatpak-coredumpctl in libflatpak-dev
 - Depends: python3, to be able to run the scripts themselves
 - Recommends: flatpak, for both scripts
 - Suggests: gdb and systemd-coredump, for flatpak-coredumpctl
 - Suggests: python3-gi and ostree, for flatpak-bisect
   * d/p/Fix-argument-order-of-clone-for-s390x-in-seccomp-filter.patch:
 Add proposed patch to fix seccomp filtering on s390x.
 Thanks to Julian Andres Klode. (Closes: #964541, LP: #1886814)
Checksums-Sha1:
 

Bug#967752: marked as done (sopwith: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 22:34:17 +
with message-id 
and subject line Bug#967752: fixed in sopwith 1.8.4-14
has caused the Debian Bug report #967752,
regarding sopwith: depends on deprecated GTK 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.)


-- 
967752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sopwith
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: sopwith
Source-Version: 1.8.4-14
Done: prono...@debian.org (Kenneth J. Pronovici)

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

Debian distribution maintenance software
pp.
Kenneth J. Pronovici  (supplier of updated sopwith 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: Thu, 06 Aug 2020 22:05:11 +
Source: sopwith
Architecture: source
Version: 1.8.4-14
Distribution: unstable
Urgency: medium
Maintainer: Kenneth J. Pronovici 
Changed-By: Kenneth J. Pronovici 
Closes: 967752
Changes:
 sopwith (1.8.4-14) unstable; urgency=medium
 .
   * Remove build dependency on unused, deprecated GTK2 (closes: #967752).
Checksums-Sha1:
 b7b58c70b790792caefae610ce2ec94fbecff873 1890 sopwith_1.8.4-14.dsc
 77727bdc7299cedec1ead7ffa300f02f235c1587 21384 sopwith_1.8.4-14.debian.tar.xz
 59253cc9f101b9e320d4821261072b972fbdc57a 9648 sopwith_1.8.4-14_amd64.buildinfo
Checksums-Sha256:
 afd6d216abaa30764e14aca3b1da52450a2dcf727eecb76f3af59a66201288b8 1890 
sopwith_1.8.4-14.dsc
 90bdba6fa49957bed77e618c7cfc085fc5747e6d12d78d1c46b9c05cfbfdc32c 21384 
sopwith_1.8.4-14.debian.tar.xz
 6538ba871282bb6cbf0d82eb932e5c05944892da8ce658061ef535dbffa08d0b 9648 
sopwith_1.8.4-14_amd64.buildinfo
Files:
 ed0119869919c6c1dcc9de739b1fddc9 1890 

Bug#964380: marked as done (pango1.0: New upstream development branch 1.45.x, required by GTK 4)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 22:34:02 +
with message-id 
and subject line Bug#964380: fixed in pango1.0 1.45.5-1
has caused the Debian Bug report #964380,
regarding pango1.0: New upstream development branch 1.45.x, required by GTK 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.)


-- 
964380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pango1.0
Version: 1.44.7-4
Severity: wishlist

GTK 3.98.5 (GTK 4 prerelease) requires Pango 1.45.0+. This is a development
branch, so should probably go to experimental first.
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.45.5-1
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 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: Thu, 06 Aug 2020 20:50:54 +0100
Source: pango1.0
Architecture: source
Version: 1.45.5-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 964380
Changes:
 pango1.0 (1.45.5-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release (Closes: #964380)
   * d/watch: Look for odd-numbered branches too
   * d/control.in: Update dependencies
   * d/copyright: Update
   * Drop patch, applied upstream
   * d/*.symbols: Update
   * Temporarily remove libpango1.0-0 again to decouple this version
 update from the NEW queue
Checksums-Sha1:
 331051ce764875bc16f12f49ef4faf8b2fafc0bb 3521 pango1.0_1.45.5-1.dsc
 2edbde5a82227c960f9be4beafb649b50336f80c 532524 pango1.0_1.45.5.orig.tar.xz
 cea9228927bd6fc3e1d602002aff3bf409d1859b 32784 pango1.0_1.45.5-1.debian.tar.xz
 94c249a1497262e074f11bf35ad853251c2a1eb5 9119 
pango1.0_1.45.5-1_source.buildinfo
Checksums-Sha256:
 773560e02e7814efd4b29ce4e3487158ff24566b1f256f93bbfbe7a0b8a5da5c 3521 
pango1.0_1.45.5-1.dsc
 f61dd911de2d3318b43bbc56bd271637a46f9118a1ee4378928c06df8a1c1705 532524 
pango1.0_1.45.5.orig.tar.xz
 0b11792c26b3fadf7d161bc6d42a62df087abf290bfd356a7f0586abbd03de20 32784 
pango1.0_1.45.5-1.debian.tar.xz
 d03a4c7c087de744284bbf08c9e4c220165a2841605f91f8eb1bfd148c26de75 9119 
pango1.0_1.45.5-1_source.buildinfo
Files:
 0939527a4c6edb3c8ce6f6698e241447 3521 libs optional pango1.0_1.45.5-1.dsc
 c6ebafc35afdc22f8da28e07a180d75d 532524 libs optional 
pango1.0_1.45.5.orig.tar.xz
 e1ad3e49e577a822bc011b2bbb556af5 32784 libs optional 
pango1.0_1.45.5-1.debian.tar.xz
 602b1f56309ce9235f79bc04322cb80f 9119 libs optional 
pango1.0_1.45.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl8sgskQHHNtY3ZAZGVi
aWFuLm9yZwAKCRDgWuFHj4FMT1KlEACmEgYWm0Omvn5gXFx1kgOiBJg6m8fDuIvx
gSdCH/GBPkeN+prcUrrYfKIluSViCC2lueaBQFCtOxU4N3ld9DLKExRhsdNUgHkO
XWkX8KCQUPGPQn++1CPQQy/DBI7fFwoZexoRUJJTCFeCeLhZ9BIYWW8fkwhCVzFk
VRO2nkPusUcn4LJk9UXDhExGZOMJ4XvE4sr3ZbuHCUsOKDNgJR7QlcTCL/vk2kRc
GxOmwwLVQ7HAXM2wb3zf4fVx/naE/eUsFtIUKNKvfBMVXxCDAg9D1JWS/Zm7B/49
ITgLxduOAP8hlG1+jnFv7WDRD9DPZjiv3mmyGA9qMvY+DFm3y41yqgqrZrwG39Nu
HL9TUdIEGIHP0SdZ85hoyKGAdiPU4ShivAq/EaFZ5MHerNOGo4MD7FSvcvz/BHse
5EMNiaNJ1qgiPpvuwNaSaRbBVBb5R+eP8f99k/9ryZJSlykQ/oebLmWHQ3dbCSd6
HmYUBAabAAHCOhI7utrmMagH3Yz4RY5lOyQ738JbzTP1NarIYvHLVVpj1NUf88Dt
8WLJOucPxBrZFHZiRiVufLBh5FFp1q2NzrF2O3aRiUBLjasxxyNErGpwLM+L34Rp
JV9RdF9+VRZmhonkKHUojS7EBALMQ/mNsudbBX5G9ddqHE6Rd8KqtnQ5lvYZF9BG
Ueyu27ANBQ==
=/yZc
-END PGP SIGNATURE End Message ---

Bug#958477: marked as done (libpango1.0-0: Please return the package to bullseye/sid)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:00:11 +
with message-id 
and subject line Bug#958477: fixed in pango1.0 1.44.7-5
has caused the Debian Bug report #958477,
regarding libpango1.0-0: Please return the package to bullseye/sid
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.)


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

Package: libpango1.0-0
Version: 1.42.4-8
Severity: wishlist

Dear Maintainer,

I have some packages installed that depend on this virtual package (cairo-
compmgr, deadbeef-static, flashplugin-nonfree). Thus I can't upgrade pango-
related packages to 1.44, because there is no 1.44 version for this virtual
package.



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

Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_UA:ru (charmap=UTF-8)

Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpango1.0-0 depends on:
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libpangoft2-1.0-0    1.42.4-8
ii  libpangox-1.0-0  0.0.2-5+b2
ii  libpangoxft-1.0-0    1.42.4-8

libpango1.0-0 recommends no packages.

libpango1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.44.7-5
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 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: Wed, 05 Aug 2020 21:56:44 +0100
Binary: gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-0 libpango-1.0-0-dbgsym 
libpango1.0-dev libpango1.0-doc libpango1.0-udeb libpangocairo-1.0-0 
libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0 libpangoft2-1.0-0-dbgsym 
libpangoxft-1.0-0 libpangoxft-1.0-0-dbgsym pango1.0-tests pango1.0-tests-dbgsym 
pango1.0-tools pango1.0-tools-dbgsym
Source: pango1.0
Architecture: all amd64 i386 source
Version: 1.44.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956520 958035 958477 959978
Description: 
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and rendering of internationalized text
 libpangoxft-1.0-0 - Layout and rendering of internationalized text
 pango1.0-tests - Layout and rendering of internationalized text - installed 
tests
 pango1.0-tools - Development utilities for Pango
Changes:
 pango1.0 (1.44.7-5) unstable; urgency=medium
 .
   * Team upload
   * Revert removal of libpango1.0-0 binary package.
 Apparently 7 years is not long enough to update dependencies in the
 fast-moving world of third-party proprietary software.
 - Relax version constraints from lockstep versioning to (>= 1.42)
   (which is still 5 years newer than the last real libpango1.0-0
   package) so that the obsolete binary package can stay on end-user
   systems after upgrade, even after it has been removed from Debian.
 - Downgrade libpangox-1.0-0 dependency to Suggests.
   This is not strictly correct, because libpango1.0-0 traditionally
   included libpangox. However, libpangox is unmaintained upstream,
   in danger of being 

Bug#959978: marked as done (libpango1.0-0: Newer version needed (depending on newest libpango-1.0-0, etc.))

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:00:11 +
with message-id 
and subject line Bug#959978: fixed in pango1.0 1.44.7-5
has caused the Debian Bug report #959978,
regarding libpango1.0-0: Newer version needed (depending on newest 
libpango-1.0-0, etc.)
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.)


-- 
959978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpango1.0-0
Version: 1.42.4-8
Severity: normal

Dear Maintainer,

In my system, I must hold the dependencies below, since libpango1.0-0
depends on those exact versions. They can be updated do 1.44.7-4, so
should be libpango1.0-0, right?

Thanks in advance,
Alexandre

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 libpango1.0-0 depends on:
hi  libpango-1.0-0   1.42.4-8
hi  libpangocairo-1.0-0  1.42.4-8
hi  libpangoft2-1.0-01.42.4-8
ii  libpangox-1.0-0  0.0.2-5+b2
hi  libpangoxft-1.0-01.42.4-8

libpango1.0-0 recommends no packages.

libpango1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.44.7-5
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 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: Wed, 05 Aug 2020 21:56:44 +0100
Binary: gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-0 libpango-1.0-0-dbgsym 
libpango1.0-dev libpango1.0-doc libpango1.0-udeb libpangocairo-1.0-0 
libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0 libpangoft2-1.0-0-dbgsym 
libpangoxft-1.0-0 libpangoxft-1.0-0-dbgsym pango1.0-tests pango1.0-tests-dbgsym 
pango1.0-tools pango1.0-tools-dbgsym
Source: pango1.0
Architecture: all amd64 i386 source
Version: 1.44.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956520 958035 958477 959978
Description: 
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and rendering of internationalized text
 libpangoxft-1.0-0 - Layout and rendering of internationalized text
 pango1.0-tests - Layout and rendering of internationalized text - installed 
tests
 pango1.0-tools - Development utilities for Pango
Changes:
 pango1.0 (1.44.7-5) unstable; urgency=medium
 .
   * Team upload
   * Revert removal of libpango1.0-0 binary package.
 Apparently 7 years is not long enough to update dependencies in the
 fast-moving world of third-party proprietary software.
 - Relax version constraints from lockstep versioning to (>= 1.42)
   (which is still 5 years newer than the last real libpango1.0-0
   package) so that the obsolete binary package can stay on end-user
   systems after upgrade, even after it has been removed from Debian.
 - Downgrade libpangox-1.0-0 dependency to Suggests.
   This is not strictly correct, because libpango1.0-0 traditionally
   included libpangox. However, libpangox is unmaintained upstream,
   in danger of being removed from Debian, and no longer present in
   Ubuntu i386, and in practice it seems to be rarely-used.
 

Bug#956520: marked as done (libpango-1.0-0: The new package breaks certain packages like dropbox or Minecraft-launcher)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:00:11 +
with message-id 
and subject line Bug#956520: fixed in pango1.0 1.44.7-5
has caused the Debian Bug report #956520,
regarding libpango-1.0-0: The new package breaks certain packages like dropbox 
or Minecraft-launcher
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.)


-- 
956520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpango-1.0-0
Version: 1.44.7-3
Severity: important

Dear Maintainer,

it seems the package libpango1.0-0 has been renamed to libpango-1.0-0. This
made apt removing some manually installed packages (with dpkg) like dropbox and
Minecraft-launcher on upgrading the held back packages like libpango and
nautilus.

For example dropbox can not be configured any more, as libpango1.0-0 is now
unavailable:

# dpkg -i dropbox_xxx.deb
[...]
dpkg: dependency problems prevent configuration of dropbox:
 dropbox depends on libpango1.0-0 (>= 1.36.3); however:
  Package libpango1.0-0 is not installed.

dpkg: error processing package dropbox (--install):
 dependency problems - leaving unconfigured
[...]

There are probably more dpkg packages provided by 3rd party that depend on
libpango1.0-0 so i assume an transitional package would be a good idea.





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

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

Versions of packages libpango-1.0-0 depends on:
ii  fontconfig 2.13.1-2+b1
ii  libc6  2.30-4
ii  libfribidi01.0.8-2
ii  libglib2.0-0   2.64.1-1
ii  libharfbuzz0b  2.6.4-1
ii  libthai0   0.1.28-3

libpango-1.0-0 recommends no packages.

libpango-1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.44.7-5
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 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: Wed, 05 Aug 2020 21:56:44 +0100
Binary: gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-0 libpango-1.0-0-dbgsym 
libpango1.0-dev libpango1.0-doc libpango1.0-udeb libpangocairo-1.0-0 
libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0 libpangoft2-1.0-0-dbgsym 
libpangoxft-1.0-0 libpangoxft-1.0-0-dbgsym pango1.0-tests pango1.0-tests-dbgsym 
pango1.0-tools pango1.0-tools-dbgsym
Source: pango1.0
Architecture: all amd64 i386 source
Version: 1.44.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956520 958035 958477 959978
Description: 
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and rendering of internationalized text
 libpangoxft-1.0-0 - Layout and rendering of internationalized text
 pango1.0-tests - Layout and rendering of internationalized text - installed 
tests
 pango1.0-tools - Development utilities for Pango
Changes:
 pango1.0 (1.44.7-5) unstable; urgency=medium
 .
   * Team upload
   * Revert removal of libpango1.0-0 binary package.
 Apparently 7 years is not long enough to update dependencies in the
 

Bug#958035: marked as done (libpango1.0-0 transitional package must be provided without tight version)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:00:11 +
with message-id 
and subject line Bug#958035: fixed in pango1.0 1.44.7-5
has caused the Debian Bug report #958035,
regarding libpango1.0-0 transitional package must be provided without tight 
version
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.)


-- 
958035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpango1.0-0
Version: 1.42.4-8
Severity: important

The libpango1.0-0 transitional package was recently dropped from
pango1.0, which would be fine except that it leaves systems in a
broken state unable to upgrade libpango-1.0-0.

The problem arises from some 3rd party sources providing deb packages
that users might reasonably want to use,
- google-talkplugin for accessing Google Hangouts on firefox
- flashplugin-nonfree for managing Adobe flash plugin.
(admittedly the latter is in Debian contrib, we can fix it ourselves)
There's also dropbox, not that I'd recommend people to use dropbox but
sometimes they don't have a choice.

The problem is the tight version dependency in libpango1.0-0,
Depends: libpango-1.0-0 (= 1.42.4-8)

So once you dropped libpango1.0-0, it's stuck at 1.42.4-8, no path
forwards for upgrading to libpango-1.0-0 1.44.7-3.

The transitional package libpango1.0-0 needs to be provided to fix
this situation, and needs to be provided without the tight version
dependency,

libpango1.0-0 Depends: libpango-1.0-0 (>= 1.44.7-3)
 libpangocairo-1.0-0  (>= 1.44.7-3)
 libpangoft2-1.0-0(>= 1.44.7-3)
 libpangox-1.0-0  (>= 1.44.7-3)
 libpangoxft-1.0-0(>= 1.44.7-3)
 
Only after that kind of open transitional dependency can the
transitional package be dropped.

Probably this should be fixed also in libpango1.0-0 1.42.4-7~deb10u2
for buster, unless you want to keep the fixed transitional package in
for another release cycle.


-- 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.5.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (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 libpango1.0-0 depends on:
ii  libpango-1.0-0   1.42.4-8
ii  libpangocairo-1.0-0  1.42.4-8
ii  libpangoft2-1.0-01.42.4-8
ii  libpangox-1.0-0  0.0.2-5+b2
ii  libpangoxft-1.0-01.42.4-8

libpango1.0-0 recommends no packages.

libpango1.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.44.7-5
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 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: Wed, 05 Aug 2020 21:56:44 +0100
Binary: gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-0 libpango-1.0-0-dbgsym 
libpango1.0-dev libpango1.0-doc libpango1.0-udeb libpangocairo-1.0-0 
libpangocairo-1.0-0-dbgsym libpangoft2-1.0-0 libpangoft2-1.0-0-dbgsym 
libpangoxft-1.0-0 libpangoxft-1.0-0-dbgsym pango1.0-tests pango1.0-tests-dbgsym 
pango1.0-tools pango1.0-tools-dbgsym
Source: pango1.0
Architecture: all amd64 i386 source
Version: 1.44.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 956520 958035 958477 959978
Description: 
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of 

Bug#957698: marked as done (pommed: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 20:25:57 +
with message-id 
and subject line Bug#957698: fixed in pommed 1.39~dfsg-5.1
has caused the Debian Bug report #957698,
regarding pommed: ftbfs with GCC-10
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.)


-- 
957698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pommed
Version: 1.39~dfsg-5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/pommed_1.39~dfsg-5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  679 | {
  | ^
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o evloop.o 
evloop.c
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbus.o 
dbus.c
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from gpomme.h:8,
 from conffile.c:39:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from gpomme.h:8,
 from conffile.c:39:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc -g -O2 -Wall -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE 
-I/usr/include/x86_64-linux-gnu -Wdate-time -D_FORTIFY_SOURCE=2  -c -o power.o 
power.c
evloop.c: In function ‘evloop_timer_callback’:
evloop.c:141:3: warning: ignoring return value of ‘read’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  141 |   read(fd, , sizeof(ticks));
  |   ^~~
power.c: In function ‘sysfs_check_ac_state’:
power.c:54:3: warning: ignoring return value of ‘fread’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
   54 |   fread(_state, 1, 1, fp);
  |   ^~
In file included from /usr/include/string.h:495,
 from conffile.c:22:
In function ‘strncpy’,
inlined from ‘config_load’ at conffile.c:129:7:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  

Bug#957034: marked as done (bandwidthd: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:27 +
with message-id 
and subject line Bug#957034: fixed in bandwidthd 2.0.1+cvs20090917-12
has caused the Debian Bug report #957034,
regarding bandwidthd: ftbfs with GCC-10
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.)


-- 
957034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bandwidthd
Version: 2.0.1+cvs20090917-11
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/bandwidthd_2.0.1+cvs20090917-11_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
In file included from conf.y:12:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from conf.y:12:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned 
char q3, unsigned char q4);
  | ^~
flex -Pbdconfig_ -s -i -t -I conf.l > conf.l.c
gcc -g -O2  -I/usr/local/include -DHAVE_CONFIG_H -c -o conf.l.o conf.l.c
gcc -Wall -g -O2  -I/usr/local/include -DHAVE_CONFIG_H   -c -o pgsql.o pgsql.c
In file included from pgsql.c:1:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from pgsql.c:1:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned 
char q3, unsigned char q4);
  | ^~
pgsql.c:418:13: warning: ‘pgsqllngjmp’ defined but not used [-Wunused-function]
  418 | static void pgsqllngjmp(int signal)
  | ^~~
gcc -Wall -g -O2  -I/usr/local/include -DHAVE_CONFIG_H   -c -o extensions.o 
extensions.c
In file included from extensions.c:1:
bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never 
defined
  250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize);
  | ^
In file included from extensions.c:1:
bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never 
defined
  237 | inline struct IPData *FindIp(uint32_t ipaddr);
  |   ^~
bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never 
defined
  234 | inline void Credit(struct Statistics *Stats, const struct ip *ip);
  | ^~
bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never 
defined
  231 | 

Bug#961767: marked as done (transmission-remote-gtk: Add Hash information in Torrent Details > General tab)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:19:02 +
with message-id 
and subject line Bug#961767: fixed in transmission-remote-gtk 1.4.1-4
has caused the Debian Bug report #961767,
regarding transmission-remote-gtk: Add Hash information in Torrent Details > 
General tab
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.)


-- 
961767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: transmission-remote-gtk
Version: 1.4.1-1
Severity: normal
Tags: patch
Control: forwarded -1 
https://github.com/bbarenblat/debian-transmission-remote-gtk/pull/2

Hello,
i've just submitted a patch upstream to add the Hash information to the
General tab of the Torrent details section.

Maybe you also want to apply it to the debian package before upstream release
a new version?

Regards,
Sandro

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

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

Versions of packages transmission-remote-gtk depends on:
ii  libc6   2.30-2
ii  libcurl47.64.0-4
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libgeoip1   1.6.12-1
ii  libglib2.0-02.64.2-1
ii  libgtk-3-0  3.24.5-1
ii  libjson-glib-1.0-0  1.4.4-2
ii  libnotify4  0.7.7-4
ii  libpango-1.0-0  1.42.4-6
ii  libproxy1v5 0.4.15-13

transmission-remote-gtk recommends no packages.

transmission-remote-gtk suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: transmission-remote-gtk
Source-Version: 1.4.1-4
Done: Benjamin Barenblat 

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

Debian distribution maintenance software
pp.
Benjamin Barenblat  (supplier of updated 
transmission-remote-gtk 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, 06 Aug 2020 16:57:18 -0400
Source: transmission-remote-gtk
Architecture: source
Version: 1.4.1-4
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Barenblat 
Changed-By: Benjamin Barenblat 
Closes: 961767
Changes:
 transmission-remote-gtk (1.4.1-4) unstable; urgency=medium
 .
   * Add torrent hash information to torrent details pane (closes:
 #961767).
Checksums-Sha1:
 178bf24b1d2e4d68fd09cbf02718bfa459160d16 2300 
transmission-remote-gtk_1.4.1-4.dsc
 8e5b793f303d02de2516e8ab084fde14d487bffc 8128 
transmission-remote-gtk_1.4.1-4.debian.tar.xz
 762b2f4e311865564129fd6534c9e77c80fc7738 14972 
transmission-remote-gtk_1.4.1-4_amd64.buildinfo
Checksums-Sha256:
 5817ab02302861857517dfb97441f5a1153ee1f0320c17c5507e47792db5f659 2300 
transmission-remote-gtk_1.4.1-4.dsc
 a4f631ac5b376b6214663e83734949736e11437d682f762d8c9746e6eabed98c 8128 
transmission-remote-gtk_1.4.1-4.debian.tar.xz
 9f20b05a55660d5be02883a10fbc883623f061e0c192185fa3cd698aa966cf23 14972 
transmission-remote-gtk_1.4.1-4_amd64.buildinfo
Files:
 e57913f9e7ceab70a8b374b0f9839005 2300 net optional 
transmission-remote-gtk_1.4.1-4.dsc
 2d0d3a0b95612da1c191f9d17d078057 8128 net optional 
transmission-remote-gtk_1.4.1-4.debian.tar.xz
 f67c59929ec3cc95fe14018fbabeaf90 14972 net optional 
transmission-remote-gtk_1.4.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQbf+q7LkywHKVTMA5ZUVm53A7cMFAl8scGEACgkQ5ZUVm53A
7cP/3g//en02PC/eXAaJ5h9e5AYeiroyby2eevkAwUdCn+U7DJ/c5R4bnNHElGFu
0WJ1XsU4WqGEgx4pbSf6J0a7gbBN8vjhAgHni5AI1DpyyCYoC0Mv76ZS4+Rr7l9S
HonVPxevgUKkvKR69EL3EJqZW+UG7CRHpYKfuXAK6j3m7xwAkmYAaH+QlR1KoD8S
rM+acf++E4p8LIVz2eQ9x3STkzpqvBguh+iELL99PqXX5vgPEqJGRFtFOxc+IKHU
331gpbrtAQUFL1me4QNaEX2dtxsJ5+T1YTBaqtFKR+2M1xBYlRi3C8//Mvebhivv

Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:33 +
with message-id 
and subject line Bug#936299: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #936299,
regarding chirp: 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.)


-- 
936299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:chirp
Version: 1:20190718-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:chirp

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: chirp
Source-Version: 1:20200227+py3+20200213-1
Done: Christoph Berg 

We believe that the bug you reported is fixed in the latest version of
chirp, 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.
Christoph Berg  (supplier of updated chirp 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: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 885265 936299
Changes:
 chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
 .
   * Switch to upstream py3 branch based on python3-wxgtk4.0.
 (Closes: #885265, #936299)
   * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
 89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
 aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 e81437a37e483eb7970153020f025c34eac18140 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
 18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 
chirp_20200227+py3+20200213-1.dsc
 

Bug#885265: marked as done (chirp: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 21:18:33 +
with message-id 
and subject line Bug#885265: fixed in chirp 1:20200227+py3+20200213-1
has caused the Debian Bug report #885265,
regarding chirp: 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.)


-- 
885265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chirp
Version: 1:20170714-1
Severity: important
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.

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 ---
Source: chirp
Source-Version: 1:20200227+py3+20200213-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated chirp 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: Thu, 06 Aug 2020 22:59:46 +0200
Source: chirp
Architecture: source
Version: 1:20200227+py3+20200213-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 885265 936299
Changes:
 chirp (1:20200227+py3+20200213-1) unstable; urgency=medium
 .
   * Switch to upstream py3 branch based on python3-wxgtk4.0.
 (Closes: #885265, #936299)
   * Lots of python3 porting missing, tested so far: Baofeng UV-5R.
Checksums-Sha1:
 89e008df68c1376761b8a2549a21bc35efd8b7b4 2193 chirp_20200227+py3+20200213-1.dsc
 aeba1b24682bc62765386988fca317a7a7a0a5ee 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 e81437a37e483eb7970153020f025c34eac18140 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Checksums-Sha256:
 18e70711e5489de4ca75aa580a6e95eab811ce10886cd44ee45ede66ba2395d5 2193 
chirp_20200227+py3+20200213-1.dsc
 898bc3359716dad537ef2f74c3e08c07ddf83c4ce325a33dfc1b45abcd991628 1198525 
chirp_20200227+py3+20200213.orig.tar.gz
 be493d1babc0ea6bf72399fedaf331b8692ffa88573686009235b953eefcf6b7 11760 
chirp_20200227+py3+20200213-1.debian.tar.xz
Files:
 a4adfb0ec790927a42e1520c126bbb66 2193 hamradio optional 
chirp_20200227+py3+20200213-1.dsc
 d3b68c04be9b401d629352f77a6835be 1198525 hamradio optional 
chirp_20200227+py3+20200213.orig.tar.gz
 ea204a4426b0d1a5b3dff8aec0286073 11760 hamradio optional 
chirp_20200227+py3+20200213-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl8scRMACgkQTFprqxLS
p64Wvg//a1RMcgo6hV/u+CxYzMu0W/KX7WTogvgWzRdiVyPto+zoFpTY34UOQEfj
+161D8+qwljnu2rGXkWtNk09uC+BP/gXTwm/gauBvLt0Nayc1dLcT/My8eqrpVM2
rVl2m+Sdp4sW91XSKkfToW4/1MlBshAp6earrviI3fUH7bhotIP2KTqA7jJN3McD
84P/E9QUwaHsHKY4sDTCdwHtUa2aZAzEZ2dD3P7zA9QLrBBrjgFzKEraMO5FS5LV
vOakC9rYI5MuxcRXtrRGVqhcWnmrP1bjPn1yM+NFmYL2A/NLFRkjW/4Hn9wuGfgY
g1+T2qHBkjQAbjiJ5QePsNkM847okR8Ida3/zK/SsvYauj/VSAS7PDNyVjliEue3
KSOGDz5N7Bz4zKsOxUuMr/HdZFK9tZfvmYPK46g75zjipcD8irTPE1YBEfu1LRLC
TMntdMZq8dDxDVQ4hgE0k69Mv85pN7Xjm/E9ODIzk9V43ZRiDWLMmuRWm7vKrIbi
z2XYIMDO+DN0BCjSz2/jw1mCY9lWJwAcW/+tBgyJsMzUrDTtaC/4awo4NN3S+6hd
1+DIovoMSC/1cBh0gUhzJ6ySLRLcjI3AF0okPbR6iMNKm9aUY9S4fCM7kjf0vmD+
AmOrL4h61iM1omm3spmHzmnpFP4JNmV5yjfEKbbNcs4ZBQ1tcR4=
=mq0M
-END PGP SIGNATURE End Message ---

Bug#966500: marked as done (python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6))

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 23:19:29 +
with message-id 
and subject line Bug#966500: fixed in notcurses 1.6.11+dfsg.1-1
has caused the Debian Bug report #966500,
regarding python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6)
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.)


-- 
966500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-notcurses
Version: 1.6.9+dfsg.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-notcurses_1.6.9+dfsg.1-2_amd64.deb ...
  Unpacking python3-notcurses (1.6.9+dfsg.1-2) over (1.5.1+dfsg.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-notcurses_1.6.9+dfsg.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/notcurses-pydemo', which is also in package 
notcurses-bin 1.5.1+dfsg.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-notcurses_1.6.9+dfsg.1-2_amd64.deb


cheers,

Andreas


notcurses-bin=1.5.1+dfsg.1-1_python3-notcurses=1.6.9+dfsg.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: notcurses
Source-Version: 1.6.11+dfsg.1-1
Done: Nick Black 

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

Debian distribution maintenance software
pp.
Nick Black  (supplier of updated notcurses 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, 03 Aug 2020 02:56:22 -0400
Source: notcurses
Architecture: source
Version: 1.6.11+dfsg.1-1
Distribution: unstable
Urgency: medium
Maintainer: Nick Black 
Changed-By: Nick Black 
Closes: 966500
Changes:
 notcurses (1.6.11+dfsg.1-1) unstable; urgency=medium
 .
   * Add Breaks+Replaces for notcurses-bin << 1.6 (Closes: #966500)
   * New notcurses-demo phase "zoo" available
   * Add python3-pypandoc dependency
   * Don't install notcurses-pydemo nor notcurses-pydemo.1 as part of
 notcurses-bin; these both belong in python3-notcurses.
Checksums-Sha1:
 c4014b2a1d015926c2140d65c81460e3070921c2 2994 notcurses_1.6.11+dfsg.1-1.dsc
 459eb7c8c845d4e04407edd105177c57f8398d09 5172948 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 76b2d7ae79317580c9786bc30b1c59b835defa25 833 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 47a2e07007b7d563368af9ad51b3a40181a9c758 12084 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 f473033d963eece7fd2333af4e1a071f431c97ea 13544 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo
Checksums-Sha256:
 d86b911912d1bb2373d9bb7961eeb91879cb6a4fe0002f2056e2420d05b4a3e7 2994 
notcurses_1.6.11+dfsg.1-1.dsc
 9c0169afdbb87c2bff15f882aff6316ba179c33cd4144e3aa5d1967de50381f8 5172948 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 da381d2b9553a37421b6ce97e6000c5c9b4aaff3b04dfc2835d82a86d6d5378c 833 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 73c19fb047b60bfd3f45d7a2393c48a8f5e10839c42c45ee445f9de9d35f5a56 12084 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 65ba0c992c5753f64ac57b1f3160cf8c1f584bb15c25977c3f104a3b320140b5 13544 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo
Files:
 e1ee4c1a23e22d91eacc21365e9a87f2 2994 libs optional 
notcurses_1.6.11+dfsg.1-1.dsc
 159e35442dd261aedbf7e81bba13728a 5172948 libs optional 
notcurses_1.6.11+dfsg.1.orig.tar.xz
 ab9a27493eb2300ec8346b89d61873a3 833 libs optional 
notcurses_1.6.11+dfsg.1.orig.tar.xz.asc
 845701818f902193119a4009e51b9f64 12084 libs optional 
notcurses_1.6.11+dfsg.1-1.debian.tar.xz
 8f4a7c87d118815a949d92acc05b9651 13544 libs optional 
notcurses_1.6.11+dfsg.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#963871: marked as done (emacs-websocket: FTBFS without external DNS)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 23:18:30 +
with message-id 
and subject line Bug#963871: fixed in emacs-websocket 1.12+18.g5aaf9d1-1
has caused the Debian Bug report #963871,
regarding emacs-websocket: FTBFS without external DNS
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.)


-- 
963871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs-websocket
Version:  1.12+8.g31e122a-1
Severity: serious
Tags: ftbfs

This package fails to build when DNS lookups are not available.

  Test websocket-client-with-remote-server condition:
  (error "echo.websocket.org/443 Temporary failure in name resolution")

  [...]

  1 unexpected results:
FAILED  websocket-client-with-remote-server

See 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/emacs-websocket.html
for a full build log.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: emacs-websocket
Source-Version: 1.12+18.g5aaf9d1-1
Done: Nicholas D Steeves 

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

Debian distribution maintenance software
pp.
Nicholas D Steeves  (supplier of updated emacs-websocket 
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, 06 Aug 2020 18:50:35 -0400
Source: emacs-websocket
Architecture: source
Version: 1.12+18.g5aaf9d1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Nicholas D Steeves 
Closes: 963871
Changes:
 emacs-websocket (1.12+18.g5aaf9d1-1) unstable; urgency=medium
 .
   * Import new upstream snapshot.
 - this snapshot includes collaborative work that makes it possible to run
   the functional tests using a localhost Tornado program rather than
   echo.websocket.org using the elisp interface introduced between
   commit:74e4b82 and commit:31e122a (Closes: #963871).
   * Add python3-tornado as a build-dep to run these tests.
   * debian/elpa-test: Activate the use of the local server for functional
 tests.
   * Drop 0001-Drop-unused-wstest-server-proc.patch (it has been fixed and is
 now used).
   * Migrate to debhelper-compat 13.
Checksums-Sha1:
 dd332c23d36c589acee318b496eeb0b1519623f4 2129 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 27e76fa385caec34d18881a3aa4a7d7a3c5a6f21 27526 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 063ff2b8ca3a1405e5e1fb3c713a40480764a93a 2304 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 459a45a9138a4e99dd6e7c50e70037494bb50937 8079 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo
Checksums-Sha256:
 adb9667a14c76caae7fad8a82edc836f6a605e6f1f4083e0a65f287e662865e6 2129 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 eb7c4aacc2b18c48fd9a507f2577ad4690bfe8d9ee8d26a4efb6bd89c0135792 27526 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 c66657004712fc3c1748c7edb787334a6897bcc55fab718913f129bcbe80b622 2304 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 04cb4aaf9be810a5a5b58afb879dd91e0771b182e36e7e15220029c92c55dc35 8079 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo
Files:
 5b9af3ae0196d43008a9a4193bb7fe4d 2129 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1.dsc
 78ed754c97cb155d9fe7839dd816a462 27526 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1.orig.tar.gz
 0b25a146d680ee68ff7d02be058d1302 2304 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1.debian.tar.xz
 0f609298c131f611c2fa02dcbee9c119 8079 lisp optional 
emacs-websocket_1.12+18.g5aaf9d1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAl8sizsACgkQWogwR199
EGEhqhAAzQTEqPyZYc+E1tIuaYgNN4gO10Dkkewf+uzo6HLja0e09j/crmJs37Zt
S68tExbkUlA6EyNkTnc+T/SK8ErM20rbj3SofmbY6gmNAZHkIXuLapj82pb4kpnx
S0pn3t3b8vY0MpOqOF7zTQy02jQ/6dYiKHQRouNFhKgAvLJAxV5/ALWbjk858xUc
7M4WE70BU0GYnqwAaUX1EbOHjJ7fMDRvYf2YY5P2BaD6h+MgUj87rmDXaWjtyH6G
cp52nQLqJOCZ9AgHPH3AUhojpsiWchKNOvu8Fp/kzuC0qnUxgXYstktNs9Vpw4PN
Btc01FuwT1XTd2b6meYUJ98o3D+OB07TZaOwebSiIBnU/Dk4mu5cSmAlYTNW5bb9

Bug#963291: marked as done (nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared (first use in this function); did you mean ‘CKO_NSS_TRUST’?)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 15:50:16 +
with message-id 
and subject line Bug#963291: fixed in nss-pem 1.0.6-1
has caused the Debian Bug report #963291,
regarding nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ 
undeclared (first use in this function); did you mean ‘CKO_NSS_TRUST’?
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.)


-- 
963291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss-pem
Version: 1.0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/cc -DHAVE_LOWKEYTI_H -Dnsspem_EXPORTS -I/usr/include/nss 
> -I/usr/include/nspr  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I../nss/dist/private/nss -fPIC   -o CMakeFiles/nsspem.dir/pinst.c.o   -c 
> /<>/src/pinst.c
> /<>/src/pfind.c: In function ‘collect_objects’:
> /<>/src/pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_TRUST’?
>   279 | case CKO_NETSCAPE_TRUST:
>   |  ^~
>   |  CKO_NSS_TRUST
> /<>/src/pfind.c:279:10: note: each undeclared identifier is 
> reported only once for each function it appears in
> /<>/src/pfind.c:283:10: error: ‘CKO_NETSCAPE_CRL’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_CRL’?
>   283 | case CKO_NETSCAPE_CRL:
>   |  ^~~~
>   |  CKO_NSS_CRL
> /<>/src/pfind.c:286:10: error: ‘CKO_NETSCAPE_SMIME’ undeclared 
> (first use in this function); did you mean ‘CKO_NSS_SMIME’?
>   286 | case CKO_NETSCAPE_SMIME:
>   |  ^~
>   |  CKO_NSS_SMIME
> [ 50%] Building C object CMakeFiles/nsspem.dir/pobject.c.o
> /usr/bin/cc -DHAVE_LOWKEYTI_H -Dnsspem_EXPORTS -I/usr/include/nss 
> -I/usr/include/nspr  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -I../nss/dist/private/nss -fPIC   -o CMakeFiles/nsspem.dir/pobject.c.o   -c 
> /<>/src/pobject.c
> /<>/src/pfind.c:289:10: error: ‘CKO_NETSCAPE_BUILTIN_ROOT_LIST’ 
> undeclared (first use in this function); did you mean 
> ‘CKO_NSS_BUILTIN_ROOT_LIST’?
>   289 | case CKO_NETSCAPE_BUILTIN_ROOT_LIST:
>   |  ^~
>   |  CKO_NSS_BUILTIN_ROOT_LIST
> make[4]: *** [CMakeFiles/nsspem.dir/build.make:118: 
> CMakeFiles/nsspem.dir/pfind.c.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/nss-pem_1.0.5-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: nss-pem
Source-Version: 1.0.6-1
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated nss-pem 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, 06 Aug 2020 18:35:59 +0300
Source: nss-pem
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 932639 963291
Changes:
 nss-pem (1.0.6-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Bump policy to 4.5.0.
   * nss: Refreshed to 3.55-1.
   * migrate-to-nss-names.diff: Migrate from NETSCAPE to NSS attributes.
 (Closes: #963291)
   * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. Thanks,
 Helmut Grohne! (Closes: #932639)
Checksums-Sha1:
 

Bug#904064: marked as done (ITP: responder -- LLMNR, NBT-NS and MDNS poisoner)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 19:45:30 +0100
with message-id 

and subject line ITP: responder -- LLMNR, NBT-NS and MDNS poisoner
has caused the Debian Bug report #904064,
regarding ITP: responder -- LLMNR, NBT-NS and MDNS poisoner
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.)


-- 
904064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: "Samuel Henrique" 
Severity: wishlist
User: samuel...@debian.org
Usertags: gsoc2018-portkalipackages

* Package name: responder
* URL : https://github.com/SpiderLabs/Responder

* License : GPL-3+
  Programming Lang: Python
  Description :
Responder an LLMNR, NBT-NS and MDNS poisoner. It will answer to *specific*
NBT-NS (NetBIOS Name Service) queries based on their name suffix. By
default, the tool will only answer to File Server Service request, which is
for SMB.

I intend to maintain this package under the Debian Security Tools Packaging
Team (pkg-security).

-- 
Samuel Henrique 
--- End Message ---
--- Begin Message ---
Given that I don't have plans to work on this package anmore, I'm
closing this ITP.

Regards,

-- 
Samuel Henrique --- End Message ---

Bug#944509: marked as done (libportaudio2: random crashes in pa_linux_alsa.c: Assertion failed - fix available)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 15:38:18 +
with message-id 
and subject line Bug#944509: fixed in portaudio19 19.6.0-1.1
has caused the Debian Bug report #944509,
regarding libportaudio2: random crashes in pa_linux_alsa.c: Assertion failed - 
fix available
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.)


-- 
944509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libportaudio2
Version: 19.6.0-1
Severity: important

Dear PA maintainers,

our RaspberryPi based smart speaker software started crashing with the
update to buster - the reason is not really clear, but pyaudio started
to crash with
python3: src/hostapi/alsa/pa_linux_alsa.c:3641: 
PaAlsaStreamComponent_BeginPolling: Assertion `ret == self->nfds' failed.
I could reproduce this bug 100% with our pyaudio based application on
arm, but I guess it might show up in other areas, too.

Fortunately, there is a patch posted to the portaudio mailing list
already back in July 2019 (but I only found it recently).

https://lists.columbia.edu/pipermail/portaudio/2019-July/001888.html

I rebuild the arm version of libportaudio2 locally and after installing
it on our system, with nothing else changed, the crashed went away.
(patch attached)

I have already contacted upstream mailing list to include the patch, but
the activity level of development there is rather low.

Could you be so nice and include this patch into the Debian sources,
ideally backporting/uploading it also to buster?

Thanks a lot and all the best

Norbert



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

Kernel: Linux 5.3.10 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 libportaudio2 depends on:
ii  libasound21.1.9-1
ii  libc6 2.29-3
ii  libjack0 [libjack-0.125]  1:0.125.0-3+b1

libportaudio2 recommends no packages.

libportaudio2 suggests no packages.

-- no debconf information
diff --git a/src/hostapi/alsa/pa_linux_alsa.c b/src/hostapi/alsa/pa_linux_alsa.c
index 584cde8..643198c 100644
--- a/src/hostapi/alsa/pa_linux_alsa.c
+++ b/src/hostapi/alsa/pa_linux_alsa.c
@@ -3628,12 +3628,18 @@ error:
 
 /** Fill in pollfd objects.
  */
-static PaError PaAlsaStreamComponent_BeginPolling( PaAlsaStreamComponent* 
self, struct pollfd* pfds )
+static PaError PaAlsaStreamComponent_BeginPolling( PaAlsaStreamComponent* 
self, struct pollfd* pfds, int *xrunOccurred )
 {
 PaError result = paNoError;
 int ret = alsa_snd_pcm_poll_descriptors( self->pcm, pfds, self->nfds );
-(void)ret;  /* Prevent unused variable warning if asserts are turned off */
-assert( ret == self->nfds );
+if( -EPIPE == ret )
+{
+  *xrunOccurred = 1;
+}
+else
+{
+  assert( ret == self->nfds );
+}
 
 self->ready = 0;
 
@@ -3794,17 +3800,22 @@ static PaError PaAlsaStream_WaitForFrames( PaAlsaStream 
*self, unsigned long *fr
 if( pollCapture )
 {
 capturePfds = self->pfds;
-PA_ENSURE( PaAlsaStreamComponent_BeginPolling( >capture, 
capturePfds ) );
+PA_ENSURE( PaAlsaStreamComponent_BeginPolling( >capture, 
capturePfds,  ) );
 totalFds += self->capture.nfds;
 }
 if( pollPlayback )
 {
 /* self->pfds is in effect an array of fds; if necessary, index 
past the capture fds */
 playbackPfds = self->pfds + (pollCapture ? self->capture.nfds : 0);
-PA_ENSURE( PaAlsaStreamComponent_BeginPolling( >playback, 
playbackPfds ) );
+PA_ENSURE( PaAlsaStreamComponent_BeginPolling( >playback, 
playbackPfds,  ) );
 totalFds += self->playback.nfds;
 }
 
+if ( xrun )
+{
+  break;
+}
+
 #ifdef PTHREAD_CANCELED
 if( self->callbackMode )
 {--- End Message ---
--- Begin Message ---
Source: portaudio19
Source-Version: 19.6.0-1.1
Done: Thorsten Glaser 

We believe that the bug you reported is fixed in the latest version of
portaudio19, 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 

Bug#610529: marked as done (infon-server: unowned files after purge (policy 6.8))

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:10:21 +
with message-id 
and subject line Bug#966207: Removed package(s) from unstable
has caused the Debian Bug report #610529,
regarding infon-server: unowned files after purge (policy 6.8)
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.)


-- 
610529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: infon-server
Version: 0~r198-3+b1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts piuparts.d.o

Hi, 

during a test with piuparts I noticed your package left unowned files on the 
system after purge, which is a violation of policy 6.8:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release goal 
since lenny.

From the attached log (scroll to the bottom...):

0m16.6s ERROR: FAIL: Package purging left files on system:
  /etc/init.d/infon-server   not owned

This is especially bad as it's an init.d script...


cheers,
Holger
Start: 2010-12-29 16:07:57 UTC

Package: infon-server
Priority: extra
Section: games
Installed-Size: 616
Maintainer: Joachim Breitner 
Architecture: amd64
Source: infon (0~r198-3)
Version: 0~r198-3+b1
Depends: libc6 (>= 2.7), libevent-1.4-2 (>= 1.4.13-stable), zlib1g (>= 1:1.1.4), metainit
Filename: pool/main/i/infon/infon-server_0~r198-3+b1_amd64.deb
Size: 152204
MD5sum: 4194612ec73d7913a0de66375a627f4d
SHA1: 02be1f87da070a4ddb87a23a767be3a1d95cc02d
SHA256: 7377a73da4596fb9a58506bd74305c856786789f76a4b8c163b4c298dd047e92
Description: Program bugs to compete for food and survival - Server
 Infon is a game which simulates the live of simple bugs who eat,
 propagate, eat each other and evolve. The players can not control
 the bugs directly but write their “intelligence” in the simple
 script language lua and upload it to the game using a plain telnet
 connection. The code can then be modified even while the game
 is running.
 .
 This package contains the infon server which hosts the game. To
 upload code to it, you only need a telnet client. To be able to
 view the game, see the infon-viewer package.
Homepage: http://infon.dividuum.de/
Tag: network::server, role::program, use::gameplaying

Executing: sudo /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/  infon-server
Guessed: debian
0m0.0s INFO: --
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile.
0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: --
0m0.0s INFO: piuparts version 0.39~201012291607 starting up.
0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ infon-server
0m0.0s INFO: Running on: Linux piatti 2.6.32.27-dsa-amd64 #1 SMP Mon Dec 13 10:07:36 UTC 2010 x86_64
0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmp59X9Vf
0m0.0s DEBUG: Unpacking sid.tar.gz into /org/piuparts.debian.org/tmp/tmp59X9Vf
0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmp59X9Vf', '-zxf', 'sid.tar.gz']
0m1.9s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmp59X9Vf', '-zxf', 'sid.tar.gz']
0m1.9s DEBUG: Created policy-rc.d and chmodded it.
0m1.9s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmp59X9Vf', 'apt-get', 'update']
0m4.9s DUMP: 
  Get:1 http://piatti.debian.org sid Release.gpg [835 B]
  Ign http://piatti.debian.org/debian/ sid/contrib Translation-en
  Ign http://piatti.debian.org/debian/ sid/main Translation-en
  Ign http://piatti.debian.org/debian/ sid/non-free Translation-en
  Get:2 http://piatti.debian.org sid Release [104 kB]
  Ign http://piatti.debian.org sid/main amd64 Packages/DiffIndex
  Ign http://piatti.debian.org sid/contrib amd64 Packages/DiffIndex
  Ign http://piatti.debian.org sid/non-free amd64 Packages/DiffIndex
  Get:3 http://piatti.debian.org sid/main amd64 Packages [9103 kB]
  Get:4 http://piatti.debian.org sid/contrib amd64 Packages [71.9 kB]
  Get:5 

Bug#468046: marked as done (Wish for User: field)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:34 +
with message-id 
and subject line Bug#966206: Removed package(s) from unstable
has caused the Debian Bug report #468046,
regarding Wish for User: field
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.)


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

I wish for a User: field that will translate to sysvinit scripts
running start-stop-daemon with --chuid $USER.  This is useful for
starting services that do not themselves know how to give up root
priviledges (in this case, supybot).

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Version: 0.0.5+rm

Dear submitter,

as the package metainit 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/966206

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#891594: marked as done (python-omniorb-dbg: broken symlinks: /usr/lib/python2.7/dist-packages/*_d.so -> *._d.so.4)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #891594,
regarding python-omniorb-dbg: broken symlinks: 
/usr/lib/python2.7/dist-packages/*_d.so -> *._d.so.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.)


-- 
891594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-omniorb-dbg
Version: 4.2.2-0.1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

  /usr/lib/python2.7/dist-packages/_omnisslTPmodule_d.so -> 
_omnisslTPmodule._d.so.4
  /usr/lib/python2.7/dist-packages/_omnipymodule_d.so -> _omnipymodule._d.so.4
  /usr/lib/python2.7/dist-packages/_omnicodesetsmodule_d.so -> 
_omnicodesetsmodule._d.so.4
  /usr/lib/python2.7/dist-packages/_omniConnMgmtmodule_d.so -> 
_omniConnMgmtmodule._d.so.4

These targets seem to have weird names and do not exist anywhere
in the archive.


cheers,

Andreas


python-omniorb-dbg_4.2.2-0.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4.2.2-0.2+rm

Dear submitter,

as the package python-omniorb 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/967054

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#937970: marked as done (python-omniorb: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #937970,
regarding python-omniorb: 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.)


-- 
937970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-omniorb
Version: 4.2.2-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:python-omniorb

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: 4.2.2-0.2+rm

Dear submitter,

as the package python-omniorb 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/967054

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966802: marked as done (RM: python-ntlm -- RoM; abandoned upstream and Python 2 only)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:33:18 +
with message-id 
and subject line Bug#966802: Removed package(s) from unstable
has caused the Debian Bug report #966802,
regarding RM: python-ntlm -- RoM; abandoned upstream and Python 2 only
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.)


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

Hi,

Upstream no longer develops python-ntlm which remained Python 2 only.
No reason to keep it in the archive, please remove it.

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

python-ntlm |1.1.0-1 | source, all

--- Reason ---
RoM; abandoned upstream and Python 2 only
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#918707: marked as done ([python-omniorb] add package for python3)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #918707,
regarding [python-omniorb] add package for python3
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.)


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

Package: python-omniorb
Version: 4.2.2-0.2
Severity: wishlist

Would it be possible to add python3 package.
So far only python 2.7 are created.
--- End Message ---
--- Begin Message ---
Version: 4.2.2-0.2+rm

Dear submitter,

as the package python-omniorb 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/967054

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967053: marked as done (RM: pynifti -- RoQA; Replaced by nibabel, Python 2)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 10:34:11 -0700
with message-id <87r1sj3ch8@iris.silentflame.com>
and subject line Re: Bug#967053: RM: pynifti -- RoQA; Replaced by nibabel, 
Python 2
has caused the Debian Bug report #967053,
regarding RM: pynifti -- RoQA; Replaced by nibabel, Python 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.)


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

Please remove pynifti. It depends on Python 2 and has been replaced
by nibabel. Acked by the maintainers in #937490.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Hello,

On Mon 03 Aug 2020 at 07:07PM +02, Moritz Muehlenhoff wrote:

> Package: ftp.debian.org
> Severity: normal
>
> Please remove pynifti. It depends on Python 2 and has been replaced
> by nibabel. Acked by the maintainers in #937490.

Looks like I already removed it last month!

-- 
Sean Whitton


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

Bug#967054: marked as done (RM: python-omniorb -- RoQA; Depends on Python 2, unmaintained, leaf package)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:01 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #967054,
regarding RM: python-omniorb -- RoQA; Depends on Python 2, unmaintained, leaf 
package
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.)


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

Please remove python-omniorb. It depends on Python 2 and the last maintainer 
upload
was in 2011. It's dropped from testing for over two years and there are no 
reverse
deps remaining.

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:

omniidl-python |  4.2.2-0.2 | all
python-omniorb |  4.2.2-0.2 | source
python-omniorb | 4.2.2-0.2+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-omniorb-dbg | 4.2.2-0.2+b1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
python-omniorb-doc |  4.2.2-0.2 | all
python-omniorb-omg |  4.2.2-0.2 | all

--- Reason ---
RoQA; Depends on Python 2, unmaintained, leaf package
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966779: marked as done (python-ntlm: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:33:22 +
with message-id 
and subject line Bug#966802: Removed package(s) from unstable
has caused the Debian Bug report #937959,
regarding python-ntlm: Unversioned Python 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.)


-- 
937959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-ntlm
Version: 1.1.0-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: 1.1.0-1+rm

Dear submitter,

as the package python-ntlm 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/966802

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966441: marked as done (RM: golang-github-adroll-goamz -- RoQA; No update for a long time; official AWS Go sdk exists)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:16:17 +
with message-id 
and subject line Bug#966441: Removed package(s) from unstable
has caused the Debian Bug report #966441,
regarding RM: golang-github-adroll-goamz -- RoQA; No update for a long time; 
official AWS Go sdk 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.)


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

This package is pretty outdated with current AWS API.
There's no rdepends. All packages which previously used this library have
migrated to official AWS SDK, golang-github-aws-aws-sdk-go.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-github-adroll-goamz | 0.0~git20170225.0.c5d7d9b-1 | source
golang-github-adroll-goamz-dev | 0.0~git20170225.0.c5d7d9b-1 | all

--- Reason ---
RoQA; No update for a long time; official AWS Go sdk exists
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966658: marked as done (RM: acfax -- RoM: obsolete and buggy)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:31:09 +
with message-id 
and subject line Bug#966658: Removed package(s) from unstable
has caused the Debian Bug report #966658,
regarding RM: acfax -- RoM: obsolete and buggy
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.)


-- 
966658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:acfax
Version: 981011-17
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/acfax_981011-17_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
FChooser.c: In function ‘ChildrenUpdate’:
FChooser.c:502:34: warning: unused variable ‘child_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~
FChooser.c:502:22: warning: unused variable ‘parent_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~~
FChooser.c: In function ‘DirectoryCallback’:
FChooser.c:596:17: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  596 | int index = (int)client_data;
  | ^
FChooser.c: In function ‘UpdateLists’:
FChooser.c:855:62: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  855 | 
XtAddCallback(menuItem,XtNcallback,DirectoryCallback,(XtPointer)i);
  |  ^
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o Directory.o Directory.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from Directory.h:29,
 from Directory.c:26:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
Directory.c: In function ‘DirEntryDump’:
Directory.c:209:27: warning: format ‘%d’ expects argument of type ‘int’, but 
argument 4 has type ‘long int’ [-Wformat=]
  209 |  fprintf(fp,"%20s, Size %7d, Prot %3o\n",
  | ~~^
  |   |
  |   int
  | %7ld
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o DirMgr.o DirMgr.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdlib.h:25,
 from DirMgr.c:25:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # 

Bug#956975: marked as done (acfax: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:31:13 +
with message-id 
and subject line Bug#966658: Removed package(s) from unstable
has caused the Debian Bug report #956975,
regarding acfax: ftbfs with GCC-10
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.)


-- 
956975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:acfax
Version: 981011-17
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/acfax_981011-17_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
FChooser.c: In function ‘ChildrenUpdate’:
FChooser.c:502:34: warning: unused variable ‘child_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~
FChooser.c:502:22: warning: unused variable ‘parent_idea’ [-Wunused-variable]
  502 | XtWidgetGeometry parent_idea,child_idea;
  |  ^~~
FChooser.c: In function ‘DirectoryCallback’:
FChooser.c:596:17: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  596 | int index = (int)client_data;
  | ^
FChooser.c: In function ‘UpdateLists’:
FChooser.c:855:62: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  855 | 
XtAddCallback(menuItem,XtNcallback,DirectoryCallback,(XtPointer)i);
  |  ^
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o Directory.o Directory.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdio.h:27,
 from Directory.h:29,
 from Directory.c:26:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
Directory.c: In function ‘DirEntryDump’:
Directory.c:209:27: warning: format ‘%d’ expects argument of type ‘int’, but 
argument 4 has type ‘long int’ [-Wformat=]
  209 |  fprintf(fp,"%20s, Size %7d, Prot %3o\n",
  | ~~^
  |   |
  |   int
  | %7ld
gcc -g -O2 -fno-strict-aliasing-I. -Dlinux -D__amd64__ 
-D_POSIX_C_SOURCE=199309L-D_POSIX_SOURCE 
-D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE
 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
  -DFUNCPROTO=15 
-DNARROWPROTO   -DSBL_16 -DDSP_SELECT -O2 -Wall-c -o DirMgr.o DirMgr.c
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/stdlib.h:25,
 from DirMgr.c:25:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning 

Bug#939441: marked as done (firmware-iwlwifi: Microcode SW error detected / Error sending REPLY_ADD_STA: time out after 2000ms)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 17:31:33 +0200
with message-id <20200806153133.ga19...@xanadu.blop.info>
and subject line Re: Bug#939441: firmware-iwlwifi: Microcode SW error detected 
/ Error sending REPLY_ADD_STA: time out after 2000ms
has caused the Debian Bug report #939441,
regarding firmware-iwlwifi: Microcode SW error detected / Error sending 
REPLY_ADD_STA: time out after 2000ms
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.)


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

During heavy Wi-Fi use (rsync), every few seconds (see first kern.log
extract):

Microcode SW error detected.  Restarting 0x200.

And once:

Error sending REPLY_ADD_STA: time out after 2000ms.

followed by an event log dump (see second kern.log
extract).  At that point the Wi-Fi froze, and could only
be restored by restarting NetworkManager.



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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.135
Sep  5 08:23:41 sago kernel: [0.00] microcode: microcode updated early 
to revision 0xa0b, date = 2010-09-28
Sep  5 08:23:41 sago kernel: [0.00] Linux version 5.2.0-2-amd64 
(debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP 
Debian 5.2.9-2 (2019-08-21)
Sep  5 08:23:41 sago kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.2.0-2-amd64 
root=UUID=b5cca383-fde9-4f0b-9735-36077a0c8ede ro quiet
Sep  5 08:23:41 sago kernel: [0.00] x86/fpu: Supporting XSAVE feature 
0x001: 'x87 floating point registers'
Sep  5 08:23:41 sago kernel: [0.00] x86/fpu: Supporting XSAVE feature 
0x002: 'SSE registers'
Sep  5 08:23:41 sago kernel: [0.00] x86/fpu: Enabled xstate features 
0x3, context size is 576 bytes, using 'standard' format.
Sep  5 08:23:41 sago kernel: [0.00] BIOS-provided physical RAM map:
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0x-0x0009b7ff] usable
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0x0009b800-0x0009] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0x0010-0xdf451bff] usable
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xdf451c00-0xdfff] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xf800-0xfbff] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xfec0-0xfec0] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xfed18000-0xfed1bfff] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xfed2-0xfed8] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xfeda-0xfeda5fff] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xfee0-0xfee0] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0xffe0-0x] reserved
Sep  5 08:23:41 sago kernel: [0.00] BIOS-e820: [mem 
0x0001-0x00041fff] usable
Sep  5 08:23:41 sago kernel: [0.00] NX (Execute Disable) protection: 
active
Sep  5 08:23:41 sago kernel: [0.00] SMBIOS 2.4 present.
Sep  5 08:23:41 sago kernel: [0.00] DMI: Dell Inc. Precision M6400  
   /076V94, BIOS A09 11/05/2009
Sep  5 08:23:41 sago kernel: [0.00] tsc: Fast TSC calibration failed
Sep  5 08:23:41 sago kernel: [0.00] e820: update [mem 
0x-0x0fff] usable ==> reserved
Sep  5 08:23:41 sago kernel: [0.00] e820: remove [mem 
0x000a-0x000f] usable
Sep  5 08:23:41 sago kernel: [0.00] last_pfn = 0x42 max_arch_pfn = 
0x4
Sep  5 08:23:41 sago kernel: [0.00] MTRR default type: uncachable
Sep  5 

Bug#939262: marked as done (firmware-iwlwifi: Consider update to newest version (20190815))

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 17:32:43 +0200
with message-id <20200806153243.ga19...@xanadu.blop.info>
and subject line Re: Bug#939262: firmware-iwlwifi: Consider update to newest 
version (20190815)
has caused the Debian Bug report #939262,
regarding firmware-iwlwifi: Consider update to newest version (20190815)
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.)


-- 
939262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-iwlwifi
Version: 20190717-2
Severity: normal

Dear Maintainer,

It looks like a newer version of modules is available as version 20190815:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tag/?h=20190815

I have a newer Lenovo Yoga X1 (Gen 4) and the 20190717 wifi firmware
does not work ("SYNC CMD GEO_TX_POWER_LIMIT" error). Through some
searching I saw that there were other reports of upgrades needed to the
underlying firmware. I manually installed 20190815 and this resolved the
issue (wifi works now)

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.135

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20200619-1

Hi,

Version 20200619-1 is now available. Closing this bug.

- Lucas


On 02/09/19 at 09:57 -0400, Sean Enck wrote:
> Package: firmware-iwlwifi
> Version: 20190717-2
> Severity: normal
> 
> Dear Maintainer,
> 
> It looks like a newer version of modules is available as version 20190815:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tag/?h=20190815
> 
> I have a newer Lenovo Yoga X1 (Gen 4) and the 20190717 wifi firmware
> does not work ("SYNC CMD GEO_TX_POWER_LIMIT" error). Through some
> searching I saw that there were other reports of upgrades needed to the
> underlying firmware. I manually installed 20190815 and this resolved the
> issue (wifi works now)
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
> 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
> 
> firmware-iwlwifi depends on no packages.
> 
> firmware-iwlwifi recommends no packages.
> 
> Versions of packages firmware-iwlwifi suggests:
> ii  initramfs-tools  0.135
> 
> -- no debconf information--- End Message ---

Bug#957043: marked as done (bitz-server: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:45 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #957043,
regarding bitz-server: ftbfs with GCC-10
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.)


-- 
957043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bitz-server
Version: 2.0.3-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/bitz-server_2.0.3-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
   debian/rules override_dh_installdocs-indep
make[1]: Entering directory '/<>'
cp -r /<>/doc/doxygen/html/* 
/<>/debian/bitz-server-doc/usr/share/doc/bitz-server-doc/docs/
dh_installdocs
make[1]: Leaving directory '/<>'
   dh_installdocs -Nbitz-server-doc
   dh_installchangelogs
   dh_installman
   dh_installinit
   debian/rules override_dh_installsystemd
make[1]: Entering directory '/<>'
dh_installsystemd -pbitz-server --no-enable --name=bitz-server 
bitz-server.service
make[1]: Leaving directory '/<>'
   dh_lintian
   dh_perl
   dh_link
   dh_strip_nondeterminism
   dh_compress
   dh_fixperms
   dh_missing
   dh_strip
   debian/rules override_dh_makeshlibs
make[1]: Entering directory '/<>'
dh_makeshlibs
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libicap1/DEBIAN/symbols doesn't match 
completely debian/libicap1.symbols.amd64
--- debian/libicap1.symbols.amd64 (libicap1_2.0.3-1_amd64)
+++ dpkg-gensymbolsWrdG5i   2020-02-26 12:40:21.761012747 +
@@ -1,6 +1,6 @@
 libicap.so.1 libicap1 #MINVER#
  (regex|optional)"^_ZN?K?S" 1.0.0
- (c++)"__gnu_cxx::__normal_iterator, std::allocator > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, 
__gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0
+#MISSING: 2.0.3-1# (c++)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, 
__gnu_cxx::__ops::_Iter_pred > > >(__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred > >, std::random_access_iterator_tag)@Base" 1.0.0
  (c++)"icap::Header::Header()@Base" 1.0.0
  (c++)"icap::Header::attach(std::__cxx11::basic_string, std::allocator >, 
std::__cxx11::basic_string, std::allocator 
>)@Base" 1.0.0
  (c++)"icap::Header::attach_encapsulated(std::__cxx11::basic_string, std::allocator >)@Base" 1.0.0
@@ -64,14 +64,14 @@
  (c++)"icap::util::send_response(icap::Response*, 
psocksxx::iosockstream*)@Base" 1.0.0
  (c++)"icap::util::split(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.0.0
  (c++)"icap::util::trim(std::__cxx11::basic_string, std::allocator >&)@Base" 1.0.0
- (c++)"std::_Rb_tree, std::allocator > 
>, std::_Select1st, std::allocator > 
> >, std::less, 
std::allocator, std::allocator > 
> > >::_M_erase(std::_Rb_tree_node, 
std::allocator > > >*)@Base" 1.0.0
+#MISSING: 2.0.3-1# (c++)"std::_Rb_tree, std::allocator > 
>, std::_Select1st, std::allocator > 
> >, std::less, 
std::allocator, std::allocator > 
> > >::_M_erase(std::_Rb_tree_node, 
std::allocator > > >*)@Base" 1.0.0
  

Bug#936211: marked as done (bitz-server: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:45 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #936211,
regarding bitz-server: 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.)


-- 
936211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bitz-server
Version: 2.0.3-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:bitz-server

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: 2.0.3-1+rm

Dear submitter,

as the package bitz-server 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/966418

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967121: marked as done (bitz-server: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:45 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #967121,
regarding bitz-server: Unversioned Python 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.)


-- 
967121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bitz-server
Version: 2.0.3-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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: 2.0.3-1+rm

Dear submitter,

as the package bitz-server 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/966418

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966418: marked as done (RM: bitz-server -- ROM; RC-buggy; abandoned upstream)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:23:40 +
with message-id 
and subject line Bug#966418: Removed package(s) from unstable
has caused the Debian Bug report #966418,
regarding RM: bitz-server -- ROM; RC-buggy; abandoned upstream
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

bitz-server is RC-buggy with no response from upstream since more then 11
month.

Please remove it from unstable.


CU
Jörg




-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl8gAAkACgkQCfifPIyh
0l2+OxAAlTEX/A+XxfklEN1cHQ2pSWp4ONW8JVjndiJNACBCMqM/eZAIKKkM4suB
EqH0BdYBVtGrwypcE/0J0qSU+u7Vbcrbd1L86LtcvM5f9Oic2V5gKFCtxX79XIEd
Nb5VkNul4zc8jr7cJo4rMVwF+cTmbO1jqdesGEBLTZazdGsHu/5FxCdwjnyC/7bj
sLo3UU584udHnU9cGquYLDCk4KCSHVq3F2o6WxRFiNSU2DEFf7RDVOL/+0rQg1wr
J7JAmtTPhCDvLucWGxnw+KP3/eyY59sUEXFInfSApddNNGpqPhEWhlEItzc2nvjq
sOtM9aj7/sbauCKloHD7m/HFfcUjH4QYoeyL+Xze42R7Y4CgSCtMSzikfu3nN8VV
88YW/YT6MOsAXH4s5TD5WW+WEYh13/8eTBR/LsRmSvt/tUcOEm07X2vvdc3tewNI
u/ZrXv3L+7rHTm0Bvdlx/P6SaKUPv6sneE9xwllXT72uoUqI4tgXCnAoSuKwXMSE
o3vkAjKl3kZYNps/ko/4/P9qYIAgyJLyBu+g07V9svklxuiqaz9dIN69hSFvdFJa
qbx563uRNnYzjmxV1s8vZYvuY02rSA+SIMBwTOhu69HWWqr0zqOHYIjX27Ex+4Wy
ru2haNROjuJlgY/cEEIFbYoULaR4UbkTqvG48aAmWnav1M7gggI=
=vhWb
-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:

bitz-server |2.0.3-1 | source, amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
bitz-server-doc |2.0.3-1 | all
libicap-dev |2.0.3-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
  libicap1 |2.0.3-1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x

--- Reason ---
ROM; RC-buggy; abandoned upstream
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966440: marked as done (RM: golang-github-docker-goamz -- RoQA; Upstream is gone)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:25:36 +
with message-id 
and subject line Bug#966440: Removed package(s) from unstable
has caused the Debian Bug report #966440,
regarding RM: golang-github-docker-goamz -- RoQA; Upstream is gone
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.)


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

The upstream repo https://github.com/docker/goamz was removed.
And there's no rdepends of this package.
It was used by docker-registry previously.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-github-docker-goamz | 0.0~git20160206.0.f0a21f5-3 | source
golang-github-docker-goamz-dev | 0.0~git20160206.0.f0a21f5-3 | all

--- Reason ---
RoQA; Upstream is gone
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967065: marked as done (RM: freehep-graphicsio -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:44:40 +
with message-id 
and subject line Bug#967065: Removed package(s) from unstable
has caused the Debian Bug report #967065,
regarding RM: freehep-graphicsio -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio |2.1.1-5 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967064: marked as done (RM: freehep-graphics2d -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:44:18 +
with message-id 
and subject line Bug#967064: Removed package(s) from unstable
has caused the Debian Bug report #967064,
regarding RM: freehep-graphics2d -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of freehep-
graphics2d, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphics2d |2.1.1-6 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966538: marked as done (firefox-esr: Firefox accuses debian-9.13.0-amd64-netinst.iso of containing malware)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 18:43:15 +0100
with message-id <20200806174315.gq16...@tack.einval.com>
and subject line Re: Debian Strech 9.13 ISO Download - Firefox says its 
containing a virus
has caused the Debian Bug report #966538,
regarding firefox-esr: Firefox accuses debian-9.13.0-amd64-netinst.iso of 
containing malware
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.)


-- 
966538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 68.10.0esr-1~deb10u1
Severity: normal

Dear Maintainer,

examining
  https://lists.debian.org/debian-cd/2020/07/msg00056.html
i downloaded
  
https://cdimage.debian.org/mirror/cdimage/archive/9.13.0/amd64/iso-cd/debian-9.13.0-amd64-netinst.iso
by the Firefox of a 6 day old Debian 10 installation.
Like the OP of the debian-cd mail, i experience on the first download of
that file a warning, that it contains a virus.

The downloaded ISO passes the usual verification by gpg and sha512sum.
See
  https://lists.debian.org/debian-cd/2020/07/msg00057.html
for the details of my verification.

I could not get more info from the warning dialog window. Clicking on
the "open" button brought me to a dialog which offers me to put the
ISO image somewhere esle.
I also failed to find any info about the virus scanner in firefox.

-- Package-specific info:

$ dpkg -s firefox-esr
Package: firefox-esr
Status: install ok installed
...
Architecture: amd64
Version: 68.10.0esr-1~deb10u1
...
Conffiles:
 /etc/firefox-esr/firefox-esr.js cebd145f0dd82696213e50218ff1a1bf

-- Addons package information

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
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 firefox-esr depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libasound21.1.8-1
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-10
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3+deb10u1
ii  libgcc1   1:8.3.0-6
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2+deb10u2
ii  libgtk-3-03.24.5-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.42.4-8~deb10u1
ii  libstartup-notification0  0.12-6
ii  libstdc++68.3.0-6
ii  libvpx5   1.7.0-3+deb10u1
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec58  7:4.1.6-1~deb10u1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-6
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-3
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-4+deb10u1

-- no debconf information
--- End Message ---
--- Begin Message ---
Hey Thomas,

I hope you're keeping ok!

On Thu, Jul 30, 2020 at 04:05:54PM +0200, Thomas Schmitt wrote:
>
>Well, as upstream programmer i could - intentionally or as victim of
>malware myself - be the culprit who sneaks malware into a Debian ISO.
>I try hard to keep my machines clean and my moral reputable, but in the end
>i do not dare to be more affirmative than "Quite surely".
>
>> I've raised a few tickets with Google
>
>Please notify bug 966538 about any progress.

Nothing visibly came from any of those tickets.

It seems Google have a habit of ignoring you, unless you submit to
their rules and set up a webmaster account on their system. Ugh. :-(

Maswan (admin at acc.umu.se, the hoster for 

Bug#931561: marked as done (Failed to load mediatek/mt7610u)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 17:39:00 +0200
with message-id <20200806153900.ga20...@xanadu.blop.info>
and subject line Re: Bug#931561: Failed to load mediatek/mt7610u
has caused the Debian Bug report #931561,
regarding Failed to load mediatek/mt7610u
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.)


-- 
931561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-misc-nonfree 
Version: 20190114-1


USB Wi-Wi adapter "Archer T2U" does not work.


lsusb output:

Bus 004 Device 002: ID 8087:8001 Intel Corp. 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8009 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer T2U" 
2.4G+5G WLAN Adapter



lsmod | grep mt76
mt76x0118784  0
mt76   40960  1 mt76x0
mac80211  815104  5 mt76,mt76x0,rt2x00lib,rt2x00usb,rt2800lib
cfg80211  761856  4 mt76x0,rt2x00lib,mac80211,r8188eu
usbcore   290816  9 
xhci_hcd,rt2800usb,mt76x0,ehci_pci,usbhid,ehci_hcd,xhci_pci,rt2x00usb,r8188eu


dmesg output:

[ 2028.014840] usb 1-14: new high-speed USB device number 6 using xhci_hcd
[ 2028.178216] usb 1-14: New USB device found, idVendor=148f, idProduct=761a, 
bcdDevice= 1.00
[ 2028.178221] usb 1-14: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 2028.178224] usb 1-14: Product: WiFi
[ 2028.178227] usb 1-14: Manufacturer: MediaTek
[ 2028.178229] usb 1-14: SerialNumber: 1.0
[ 2028.307040] usb 1-14: reset high-speed USB device number 6 using xhci_hcd
[ 2028.461948] mt76x0 1-14:1.0: ASIC revision: 7612 MAC revision: 76502000
[ 2028.462534] mt76x0 1-14:1.0: firmware: failed to load mediatek/mt7610u.bin 
(-2)
[ 2028.462542] mt76x0 1-14:1.0: Direct firmware load for mediatek/mt7610u.bin 
failed with error -2
[ 2028.462825] mt76x0: probe of 1-14:1.0 failed with error -2


-- 
С уважением,
Евгений.
--- End Message ---
--- Begin Message ---
Version: 20200619-1

Hi,

> [ 2028.462534] mt76x0 1-14:1.0: firmware: failed to load mediatek/mt7610u.bin 
> (-2)

Added in version 20200619-1. Closing this bug.

Lucas


On 07/07/19 at 20:11 +0300, Евгений wrote:
> Package: firmware-misc-nonfree 
> Version: 20190114-1
> 
> 
> USB Wi-Wi adapter "Archer T2U" does not work.
> 
> 
> lsusb output:
> 
> Bus 004 Device 002: ID 8087:8001 Intel Corp. 
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 002: ID 8087:8009 Intel Corp. 
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 005: ID 148f:761a Ralink Technology, Corp. MT7610U ("Archer 
> T2U" 2.4G+5G WLAN Adapter
> 
> 
> 
> lsmod | grep mt76
> mt76x0118784  0
> mt76   40960  1 mt76x0
> mac80211  815104  5 mt76,mt76x0,rt2x00lib,rt2x00usb,rt2800lib
> cfg80211  761856  4 mt76x0,rt2x00lib,mac80211,r8188eu
> usbcore   290816  9 
> xhci_hcd,rt2800usb,mt76x0,ehci_pci,usbhid,ehci_hcd,xhci_pci,rt2x00usb,r8188eu
> 
> 
> dmesg output:
> 
> [ 2028.014840] usb 1-14: new high-speed USB device number 6 using xhci_hcd
> [ 2028.178216] usb 1-14: New USB device found, idVendor=148f, idProduct=761a, 
> bcdDevice= 1.00
> [ 2028.178221] usb 1-14: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 2028.178224] usb 1-14: Product: WiFi
> [ 2028.178227] usb 1-14: Manufacturer: MediaTek
> [ 2028.178229] usb 1-14: SerialNumber: 1.0
> [ 2028.307040] usb 1-14: reset high-speed USB device number 6 using xhci_hcd
> [ 2028.461948] mt76x0 1-14:1.0: ASIC revision: 7612 MAC revision: 76502000
> [ 2028.462534] mt76x0 1-14:1.0: firmware: failed to load mediatek/mt7610u.bin 
> (-2)
> [ 2028.462542] mt76x0 1-14:1.0: Direct firmware load for mediatek/mt7610u.bin 
> failed with error -2
> [ 2028.462825] mt76x0: probe of 1-14:1.0 failed with error -2
> 
> 
> -- 
> С уважением,
> Евгений.--- End Message ---

Bug#929307: marked as done (firmware-atheros: Qualcomm Atheros QCA9377. No Wi-Fi Adapter Found. Error message at boot about ath10k.)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 17:42:30 +0200
with message-id <20200806154230.ga21...@xanadu.blop.info>
and subject line Re: Bug#929307: firmware-atheros: Qualcomm Atheros QCA9377. No 
Wi-Fi Adapter Found. Error message at boot about ath10k.
has caused the Debian Bug report #929307,
regarding firmware-atheros: Qualcomm Atheros QCA9377. No Wi-Fi Adapter Found. 
Error message at boot about ath10k.
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.)


-- 
929307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-atheros
Version: 20190502-1
Severity: important

Dear Maintainer,

Despite installing the firmware-atheros package through the firmware-linux-
nonfree package, wifi still doesn't work.

When booting, I am presented with the following messages:
ath10k_pci :07:00.0: firmware: failed to load ath10k/pre-cal-
pci-:07:00.0.bin (-2)
firmware_class: See https://wiki.debian.org/Firmware for information about
missing firmware
ath10k_pci :07:00.0: firmware: failed to load ath10k/cal-
pci-:07:00.0.bin (-2)

I don't know whether these mean anything related to the problem I'm getting,
but they are as close as I've got to a clue about what's going on.

I've checked other bug reports, and there are some which are similar to mine.
Typically, they include other error messages which report an inability to
directly load certain firmware files. However, I don't get these.

I'm currently on buster, and have tried installing the version of the package
currently in unstable, but the same problems persisted after I did so, so I
reverted back to the buster version.

The wifi adapter does work on windows 10, but I don't know if it works on other
distros.

I don't know if this is a bug, or if I haven't done something I needed to, but
I would appreciate some assistance.




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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.133

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20200619-1

Hi,

> ath10k_pci :07:00.0: firmware: direct-loading firmware 
> ath10k/QCA9377/hw1.0/board-2.bin

This is included in version 20200619-1, so I think that this bug can be
closed.

- Lucas--- End Message ---

Bug#966870: marked as done (nsis: FTBFS: ld: build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: multiple definition of `version'; build/urelease/halibut/biblio.o:./Docs/src/bin/ha

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:04:25 +
with message-id 
and subject line Bug#966870: fixed in nsis 3.05-4
has caused the Debian Bug report #966870,
regarding nsis: FTBFS: ld: 
build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: 
multiple definition of `version'; 
build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
defined here
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.)


-- 
966870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nsis
Version: 3.05-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> gcc -o build/urelease/halibut/halibut -Wl,-z,relro -Wl,-z,now 
> build/urelease/halibut/biblio.o build/urelease/halibut/bk_xhtml.o 
> build/urelease/halibut/contents.o build/urelease/halibut/error.o 
> build/urelease/halibut/help.o build/urelease/halibut/index.o 
> build/urelease/halibut/input.o build/urelease/halibut/keywords.o 
> build/urelease/halibut/licence.o build/urelease/halibut/main.o 
> build/urelease/halibut/malloc.o build/urelease/halibut/misc.o 
> build/urelease/halibut/style.o build/urelease/halibut/tree234.o 
> build/urelease/halibut/ustring.o build/urelease/halibut/version.o
> /usr/bin/ld: 
> build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/contents.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/error.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/help.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/index.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/input.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/keywords.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/main.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/malloc.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/misc.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/style.o:./Docs/src/bin/halibut/halibut.h:272: multiple 
> definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/ustring.o:./Docs/src/bin/halibut/halibut.h:272: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> /usr/bin/ld: 
> build/urelease/halibut/version.o:./Docs/src/bin/halibut/version.c:19: 
> multiple definition of `version'; 
> build/urelease/halibut/biblio.o:./Docs/src/bin/halibut/halibut.h:272: first 
> defined here
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/nsis_3.05-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 

Bug#773869: marked as done (freehep-vectorgraphics: Newer version of software exists at http://freehep.github.io/freehep-vectorgraphics/)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:49:18 +
with message-id 
and subject line Bug#967068: Removed package(s) from unstable
has caused the Debian Bug report #773869,
regarding freehep-vectorgraphics: Newer version of software exists at 
http://freehep.github.io/freehep-vectorgraphics/
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.)


-- 
773869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freehep-graphicsio-pdf
Version: 2.1.1+dfsg-1
Severity: normal

The software at java.freehep.org was declared "obsolete" in 2007, but
has been taken up at http://freehep.github.io/freehep-vectorgraphics/
where it is undergoing - AFAICT - minor development and bug-fixing
work.  The current release is version 2.4 - it may well make sense to
package this in place of the current version.

This obviously applies to all of the freehep-vectorgraphics packages,
but I'm only writing this single bug report.

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Version: 2.1.1+dfsg-3+rm

Dear submitter,

as the package freehep-graphicsio-pdf 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/967068

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967068: marked as done (RM: freehep-graphicsio-pdf -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:49:15 +
with message-id 
and subject line Bug#967068: Removed package(s) from unstable
has caused the Debian Bug report #967068,
regarding RM: freehep-graphicsio-pdf -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-pdf, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-pdf | 2.1.1+dfsg-3 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967066: marked as done (RM: freehep-graphicsio-emf -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:47:01 +
with message-id 
and subject line Bug#967066: Removed package(s) from unstable
has caused the Debian Bug report #967066,
regarding RM: freehep-graphicsio-emf -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-emf, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-emf | 2.1.1-emfplus+dfsg1-4 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967067: marked as done (RM: freehep-graphicsio-java -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:48:12 +
with message-id 
and subject line Bug#967067: Removed package(s) from unstable
has caused the Debian Bug report #967067,
regarding RM: freehep-graphicsio-java -- ROM; obsoleted by 
freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-java, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-java |2.1.1-3 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#957820: marked as done (snap: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:03:55 +
with message-id 
and subject line Bug#957820: fixed in snap 2013-11-29-10
has caused the Debian Bug report #957820,
regarding snap: ftbfs with GCC-10
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.)


-- 
957820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:snap
Version: 2013-11-29-9
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/snap_2013-11-29-9_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
/usr/bin/ld: zoeDNA.o:./Zoe/zoeTools.h:45: multiple definition of `zoeMethod'; 
zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDNA.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDNA.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDistribution.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeDuration.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFastaFile.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeature.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeatureFactory.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:45: multiple definition of 
`zoeMethod'; zoe-loop.o:./Zoe/zoeTools.h:45: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:44: multiple definition of 
`zoeConstructor'; zoe-loop.o:./Zoe/zoeTools.h:44: first defined here
/usr/bin/ld: zoeFeatureTable.o:./Zoe/zoeTools.h:43: multiple definition of 
`zoeFunction'; zoe-loop.o:./Zoe/zoeTools.h:43: 

Bug#927011: marked as done (snap: Package info contains a 404 url)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:03:55 +
with message-id 
and subject line Bug#927011: fixed in snap 2013-11-29-10
has caused the Debian Bug report #927011,
regarding snap: Package info contains a 404 url
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.)


-- 
927011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: snap
Version: 2013-11-29-6
Severity: minor

Dear Maintainer,

(Minor issue, may be fixed in later version but I don't use testing, disregard 
this if so)

The package info contains a 404 url:

Homepage: https://www.psc.edu/index.php/user-resources/software/snap


root@plague:~/.ipfs# apt show snap
Package: snap
Version: 2013-11-29-6
Priority: extra
Section: science
Maintainer: Debian Med Packaging Team

Installed-Size: 2,718 kB
Depends: libc6 (>= 2.14)
Homepage: https://www.psc.edu/index.php/user-resources/software/snap
Download-Size: 373 kB
APT-Manual-Installed: yes
APT-Sources: http://ftp.uk.debian.org/debian stretch/main amd64 Packages
Description: location of genes from DNA sequence with hidden markov
model
 SNAP is a general purpose gene finding program suitable for both
eukaryotic
 and prokaryotic genomes. SNAP is an acroynm for Semi-HMM-based
Nucleic Acid
 Parser.
 
 

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

Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores)
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: systemd (via /run/systemd/system)

Versions of packages snap depends on:
ii  libc6  2.24-11+deb9u4

snap recommends no packages.

snap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: snap
Source-Version: 2013-11-29-10
Done: Pierre Gruet 

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

Debian distribution maintenance software
pp.
Pierre Gruet  (supplier of updated snap 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: Thu, 06 Aug 2020 15:01:26 +0200
Source: snap
Architecture: source
Version: 2013-11-29-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Pierre Gruet 
Closes: 927011 957820
Changes:
 snap (2013-11-29-10) unstable; urgency=medium
 .
   [ Dylan Aïssi ]
   * d/control: Update homepage (Closes: #927011).
 .
   [ Pierre Gruet ]
   * Avoiding multiple definitions error due to gcc-10 (Closes: #957820)
   * Depending on debhelper-compat
   * Bumping Standards version to 4.5.0 (Rules-Requires-Root field added)
   * Adding salsa-ci.yml file
   * Renaming d/NEWS.Debian to d/NEWS
   * Changing deprecated ADTTMP variable name in debian/tests/run-unit-test
   * Adding Bug- and Repository-related fields in d/upstream/metadata
   * Adding and documenting Lintian overrides
   * Trim trailing whitespace.
   * Remove obsolete field Name from debian/upstream/metadata (already present 
in
 machine-readable debian/copyright).
 .
   [ Andreas Tille ]
   * Override script-with-language-extension
Checksums-Sha1:
 3842224a3385d0de9a9eb006ddbaf7784ad76cb4 2068 snap_2013-11-29-10.dsc
 e5304b5050853e3da51ed54c1e4a65fc55239c46 10340 snap_2013-11-29-10.debian.tar.xz
 255ed47405f40c0c11b8fdb49dd36ca389e71688 5738 
snap_2013-11-29-10_amd64.buildinfo
Checksums-Sha256:
 d80ea221f22f4625da7724d0db6eda53ab6b36daa688327a01e2f1a5d33037de 2068 
snap_2013-11-29-10.dsc
 50a7300f8e18c678bd22870ec2e69a1a612578da8e3c50f1c497a7851bf96eb7 10340 
snap_2013-11-29-10.debian.tar.xz
 2652a402b2685ad23a85cf218c0303ff98ff20e136bbb195580201ed7e6c8268 5738 
snap_2013-11-29-10_amd64.buildinfo
Files:
 cf275953978b0d62869c26daecbe5e34 2068 science optional snap_2013-11-29-10.dsc
 c3630dcdb2de23c5ed39bfee817aa530 10340 science optional 
snap_2013-11-29-10.debian.tar.xz
 de5a7f67aaffdc2f7c42ac332901c965 5738 science optional 
snap_2013-11-29-10_amd64.buildinfo

Bug#956187: marked as done (firejail-profiles: Updated profile for Microsoft Teams for Linux)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:18:36 +
with message-id 
and subject line Bug#956187: fixed in firejail 0.9.62-4
has caused the Debian Bug report #956187,
regarding firejail-profiles: Updated profile for Microsoft Teams for Linux
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.)


-- 
956187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firejail-profiles
Version: 0.9.62-3
Severity: important
Tags: patch

Dear Maintainer,

Microsoft Teams for Linux has been updated with a packagad desktop
version of their program which can be downloaded when visiting
https://teams.microsoft.com. The new Teams Debian package comes with
a renamed application 'teams' and uses a few more standard command
line tools. To support the new version, I created a new
'teams.profile' to match the name of the binary and allows access
to the new helper programs that package is using.

I don't know if the current teams-for-linux will still work, if not
that one could be retired and all of the profile information updated
to a profile using the name of the new binary.

The new teams.profile is:
---
include teams-for-linux.profile

whitelist ${HOME}/.config/teams
whitelist ${HOME}/.config/Microsoft/Microsoft Teams

private-bin teams,readlink,dirname,mkdir,nohup
---

Please test,

Patrik



-- System Information:
Debian Release: bullseye/sid
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'testing'), (500, 'oldstable-updates'), 
(500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.15 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_FI.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 firejail-profiles depends on:
ii  firejail  0.9.62-3

firejail-profiles recommends no packages.

firejail-profiles suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.62-4
Done: Reiner Herrmann 

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail 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, 06 Aug 2020 17:45:00 +0200
Source: firejail
Architecture: source
Version: 0.9.62-4
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 948656 950007 956187
Changes:
 firejail (0.9.62-4) unstable; urgency=high
 .
   * Import security fixes for CVE-2020-17367 and CVE-2020-17368:
 - don't interpret output arguments after end-of-options tag
 - don't pass command line through shell when redirecting output
   * Import profile updates:
 - allow additional characters in paths
 - profile for Element
 - profile for teams (Closes: #956187)
 - whitelist /usr/share/doc for some document viewers (Closes: #950007)
 - whitelist /usr/share/firefox in firefox profile (Closes: #948656)
   * Bump debhelper compat level to 13.
   * Bump Standards-Version to 4.5.0.
   * Fix test-suite container check.
   * Add upstream bugtracker to metadata.
   * Move dh_missing calls to their own override target.
   * Update Vcs-* URLs.
   * Add Forwarded headers to patches.
Checksums-Sha1:
 e33e539223b9b97cabfba311dabfa09101a01726 2456 firejail_0.9.62-4.dsc
 f0b629033ad54dbeacbb72970f00903a1440 18252 firejail_0.9.62-4.debian.tar.xz
 f5a9f7bd9a5e2fc74162dba5e910f5424ca7ef65 5372 
firejail_0.9.62-4_source.buildinfo
Checksums-Sha256:
 6e821df544ca684fd1e57f2f92e8d175aec28510e1a6005d71b7870f711a2e74 2456 
firejail_0.9.62-4.dsc
 cf4ef8e20dc3b9c86b7792ed1b4de54d0d96762900721171f3551d27e4e7a38a 18252 
firejail_0.9.62-4.debian.tar.xz
 f5a774a1948c54f93c58b0ec6cc0056e194dcb71a0c44a3ab2aa708e3e321f38 5372 
firejail_0.9.62-4_source.buildinfo
Files:
 8ba485d021da72ac0868de57cf201f44 2456 utils optional firejail_0.9.62-4.dsc
 

Bug#950007: marked as done (firejail-profiles: firefox cannot read standard Debian docs folder /usr/share/doc)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:18:36 +
with message-id 
and subject line Bug#950007: fixed in firejail 0.9.62-4
has caused the Debian Bug report #950007,
regarding firejail-profiles: firefox cannot read standard Debian docs folder 
/usr/share/doc
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.)


-- 
950007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firejail-profiles
Version: 0.9.62-2~bpo10+1
Severity: normal

Dear Maintainer,

I regularly use offline docs, but a recent change to the firefox profile has 
blocked access to all the docs provided by Debian in /usr/share/doc:

File not found

Firefox can’t find the file at /usr/share/doc/.

Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.

Or for a specific example:
file:///usr/share/doc/python3.7/html/library/collections.html#collections.OrderedDict

File not found

Firefox can’t find the file at 
/usr/share/doc/python3.7/html/library/collections.html#collections.OrderedDict.

Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.


 ~ $ ls -ld /usr/share/doc
drwxr-xr-x 3396 root root 131072 Jän 27 18:09 /usr/share/doc
 ~ $ ls -ld /usr/share/doc/python3.7/html/library/collections.html 
-rw-r--r-- 1 root root 165855 Apr  3  2019 
/usr/share/doc/python3.7/html/library/collections.html



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Kernel taint flags: 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 firejail-profiles depends on:
ii  firejail  0.9.62-2~bpo10+1

firejail-profiles recommends no packages.

firejail-profiles suggests no packages.

-- Configuration Files:
/etc/firejail/firefox.profile changed:
include firefox.local
include globals.local
noblacklist ${HOME}/.cache/mozilla
noblacklist ${HOME}/.mozilla
mkdir ${HOME}/.cache/mozilla/firefox
mkdir ${HOME}/.mozilla
whitelist ${HOME}/.cache/mozilla/firefox
whitelist ${HOME}/.mozilla
whitelist /usr/share/mozilla
whitelist /usr/share/webext
include whitelist-usr-share-common.inc
include firefox-common.profile

/etc/firejail/transmission-daemon.profile changed:
quiet
include transmission-daemon.local
include globals.local
mkdir ${HOME}/.config/transmission-daemon
whitelist ${HOME}/.config/transmission-daemon
whitelist /var/lib/transmission
caps.keep ipc_lock,net_bind_service,setgid,setuid,sys_chroot
private-bin transmission-daemon
private-etc 
alternatives,ca-certificates,crypto-policies,nsswitch.conf,pki,resolv.conf,ssl
read-write /var/lib/transmission
writable-var-log
writable-run-user
include transmission-common.profile


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.62-4
Done: Reiner Herrmann 

We believe that the bug you reported is fixed in the latest version of
firejail, 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.
Reiner Herrmann  (supplier of updated firejail 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, 06 Aug 2020 17:45:00 +0200
Source: firejail
Architecture: source
Version: 0.9.62-4
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 948656 950007 956187
Changes:
 firejail (0.9.62-4) unstable; urgency=high
 .
   * Import security fixes for CVE-2020-17367 and CVE-2020-17368:
 - don't interpret output arguments after end-of-options tag
 - don't pass command line through shell when redirecting output
   * Import profile updates:
 - allow additional characters in paths
 - profile 

Bug#966326: marked as done (RM: mrtrix -- RoQA; Replaced by mrtrix3)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:37 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #966326,
regarding RM: mrtrix -- RoQA; Replaced by mrtrix3
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.)


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

Please remove mrtrix. It depends on Python 2 and has been replaced
by mrtrix3. Acked by the maintainers in #937090.

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:

mrtrix |   0.2.13-2 | source
mrtrix | 0.2.13-2+b1 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, 
ppc64el, s390x
mrtrix-doc |   0.2.13-2 | all

--- Reason ---
RoQA; Replaced by mrtrix3
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967178: marked as done (mrtrix: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:43 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #967178,
regarding mrtrix: Unversioned Python 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.)


-- 
967178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mrtrix
Version: 0.2.13-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

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.2.13-2+rm

Dear submitter,

as the package mrtrix 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/966326

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#937090: marked as done (mrtrix: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:43 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #937090,
regarding mrtrix: 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.)


-- 
937090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mrtrix
Version: 0.2.13-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:mrtrix

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.2.13-2+rm

Dear submitter,

as the package mrtrix 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/966326

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966332: marked as done (RM: cfv -- ROM; python2-only; no external deps; no py3 support yet)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:17:20 +
with message-id 
and subject line Bug#966332: Removed package(s) from unstable
has caused the Debian Bug report #966332,
regarding RM: cfv -- ROM; python2-only; no external deps; no py3 support yet
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.)


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

The cfv package upstream is MIA; refreshed development efforts and porting
to python3 happens at https://github.com/cfv-project/cfv/commits/python3
however it is not yet mature to replace the existing package.

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936288

The intent is to re-ITP cfv again when py3 support is stable.

Cheers,
 Stefan


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

   cfv | 1.18.3-2.1 | source, all

--- Reason ---
ROM; python2-only; no external deps; no py3 support yet
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967645: marked as done (mrtrix: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:43 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #967645,
regarding mrtrix: depends on deprecated GTK 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.)


-- 
967645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrtrix
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Version: 0.2.13-2+rm

Dear submitter,

as the package mrtrix 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/966326

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#948656: marked as done (firejail-profiles: firefox-esr running under firejail does not load correct preferences)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:18:36 +
with message-id 
and subject line Bug#948656: fixed in firejail 0.9.62-4
has caused the Debian Bug report #948656,
regarding firejail-profiles: firefox-esr running under firejail does not load 
correct preferences
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.)


-- 
948656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firejail-profiles
Version: 0.9.62-2
Severity: normal

Dear Maintainer,

With the upgrade to firejail-profiles 0.9.62-2 Firefox ESR running under
firejail now does not load the correct user preferences.

In my case these are the Firefox preferences that are altered when using
firejail:

# General / Startup
  - Always check if Firefox is your default browser --> set to enabled

# General / Language and Appearance / Language
  - language used to display menus, messages, and notifications --> unset

# Search
  - One-Click Search Engines --> Twitter added as Search Engine (??)

# Privacy and Security / Firefox Data Collection and Use
  - send technical and interaction data to Mozilla --> set to enabled
  - install and run studies --> set to enabled
  - make personalized extension recommendations --> set to enabled


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

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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 firejail-profiles depends on:
ii  firejail  0.9.62-2

firejail-profiles recommends no packages.

firejail-profiles suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.62-4
Done: Reiner Herrmann 

We believe that the bug you reported is fixed in the latest version of
firejail, 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.
Reiner Herrmann  (supplier of updated firejail 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, 06 Aug 2020 17:45:00 +0200
Source: firejail
Architecture: source
Version: 0.9.62-4
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 948656 950007 956187
Changes:
 firejail (0.9.62-4) unstable; urgency=high
 .
   * Import security fixes for CVE-2020-17367 and CVE-2020-17368:
 - don't interpret output arguments after end-of-options tag
 - don't pass command line through shell when redirecting output
   * Import profile updates:
 - allow additional characters in paths
 - profile for Element
 - profile for teams (Closes: #956187)
 - whitelist /usr/share/doc for some document viewers (Closes: #950007)
 - whitelist /usr/share/firefox in firefox profile (Closes: #948656)
   * Bump debhelper compat level to 13.
   * Bump Standards-Version to 4.5.0.
   * Fix test-suite container check.
   * Add upstream bugtracker to metadata.
   * Move dh_missing calls to their own override target.
   * Update Vcs-* URLs.
   * Add Forwarded headers to patches.
Checksums-Sha1:
 e33e539223b9b97cabfba311dabfa09101a01726 2456 firejail_0.9.62-4.dsc
 f0b629033ad54dbeacbb72970f00903a1440 18252 firejail_0.9.62-4.debian.tar.xz
 f5a9f7bd9a5e2fc74162dba5e910f5424ca7ef65 5372 
firejail_0.9.62-4_source.buildinfo
Checksums-Sha256:
 6e821df544ca684fd1e57f2f92e8d175aec28510e1a6005d71b7870f711a2e74 2456 
firejail_0.9.62-4.dsc
 cf4ef8e20dc3b9c86b7792ed1b4de54d0d96762900721171f3551d27e4e7a38a 18252 
firejail_0.9.62-4.debian.tar.xz
 f5a774a1948c54f93c58b0ec6cc0056e194dcb71a0c44a3ab2aa708e3e321f38 5372 
firejail_0.9.62-4_source.buildinfo
Files:
 8ba485d021da72ac0868de57cf201f44 2456 utils optional firejail_0.9.62-4.dsc
 

Bug#947654: marked as done (mrtrix: depends on deprecated libpangox-1.0-0)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:16:43 +
with message-id 
and subject line Bug#966326: Removed package(s) from unstable
has caused the Debian Bug report #947654,
regarding mrtrix: depends on deprecated libpangox-1.0-0
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.)


-- 
947654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mrtrix
Version: 0.2.12-1
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pangox
Control: block 947649 by -1

This package has a runtime dependency on libpangox-1.0-0, the Core X
backend for Pango, which has been deprecated since at least 2012, is
unmaintained upstream and is essentially unmaintained in Debian.

Using a general-purpose graphical toolkit such as GTK or Qt, or a
non-deprecated Pango backend with (such as Xft or Cairo), is recommended.

The severity of this bug might be increased in future if there is an
effort to remove libpangox-1.0-0 from Debian, but for the moment it's
normal-severity.

This dependency is likely to be as a result of using libgtkglext1-dev
(see #702010). It might be possible to avoid the direct dependency by
linking with -Wl,--as-needed.

smcv
--- End Message ---
--- Begin Message ---
Version: 0.2.13-2+rm

Dear submitter,

as the package mrtrix 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/966326

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#949478: marked as done (browser-plugin-freshplayer-pepperflash might be useless now)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:14 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #949478,
regarding browser-plugin-freshplayer-pepperflash might be useless now
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.)


-- 
949478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: browser-plugin-freshplayer-pepperflash
Version: 0.3.9-2
Severity: serious

All major browsers (including Firefox) have dropped support for NPAPI.
--- End Message ---
--- Begin Message ---
Version: 0.3.9-2+rm

Dear submitter,

as the package freshplayerplugin 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/966474

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966474: marked as done (RM: freshplayerplugin -- RoQA; FTBFS, Obsolete, Unsupported by browsers, EOL upstream)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:09 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #966474,
regarding RM: freshplayerplugin -- RoQA; FTBFS, Obsolete, Unsupported by 
browsers, EOL upstream
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.)


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

As per Adobe Flash Player EOL [1] flash player is going end of life by
end of this year. Similar statements are linked from that article by
Apple, Facebook, Google, Microsoft and Mozilla.

Currently browsers in Debian have already dropped NPAPI and the
package itself fails to build from source. [2] [3]

The time has come to kill Flash and remove this package from the archive.


[1] 
https://www.adobe.com/uk/products/flashplayer/end-of-life.html?cq_ck=1591175470736

[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947288

[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949478
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

browser-plugin-freshplayer-pepperflash | 0.3.9-2+b1 | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x
freshplayerplugin |0.3.9-2 | source

--- Reason ---
RoQA; FTBFS, Obsolete, Unsupported by browsers, EOL upstream
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967355: marked as done (freshplayerplugin: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:14 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #967355,
regarding freshplayerplugin: depends on deprecated GTK 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.)


-- 
967355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freshplayerplugin
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Version: 0.3.9-2+rm

Dear submitter,

as the package freshplayerplugin 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/966474

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#947288: marked as done (freshplayerplugin: FTBFS: No package 'libdrm' found)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:21:14 +
with message-id 
and subject line Bug#966474: Removed package(s) from unstable
has caused the Debian Bug report #947288,
regarding freshplayerplugin: FTBFS: No package 'libdrm' 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.)


-- 
947288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freshplayerplugin
Version: 0.3.9-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

freshplayerplugin cannot be built in a current sid environment any more:

-- Checking for modules 
'alsa;gio-2.0;x11;xrandr;xrender;xcursor;gl;libdrm;libevent;libevent_pthreads;cairo;pango;pangocairo;pangoft2;freetype2;openssl;icu-uc'
--   No package 'libdrm' found
CMake Error at /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:458 (message):
  A required package was not found
Call Stack (most recent call first):
  /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:637 
(_pkg_check_modules_internal)
  CMakeLists.txt:45 (pkg_check_modules)


-- Configuring incomplete, errors occurred!


Andreas


freshplayerplugin_0.3.9-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.3.9-2+rm

Dear submitter,

as the package freshplayerplugin 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/966474

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#965048: marked as done (elpa-magithub: Dependency on deprecated ‘magit-popup’ causes warning, should migrate to ‘transient’)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:39:28 +
with message-id 
and subject line Bug#968006: Removed package(s) from unstable
has caused the Debian Bug report #965048,
regarding elpa-magithub: Dependency on deprecated ‘magit-popup’ causes warning, 
should migrate to ‘transient’
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.)


-- 
965048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-magithub
Version: 0.1.7-2
Severity: important
Tags: upstream

When using current Magit (release “2.99.0.git0957.ge8c7bd03-1” from
Debian) while Magithub is installed, Magit repeatedly interrupts with
a warning:

Warning (magit): Magit no longer uses Magit-Popup.
It now uses Transient.
See https://emacsair.me/2019/02/14/transient-0.1.

However your configuration and/or some third-party package that
you use still depends on the `magit-popup' package. But because
`magit' no longer depends on that, `package' has removed it from
your system.

If some package that you use still depends on `magit-popup' but
does not declare it as a dependency, then please contact its
maintainer about that and install `magit-popup' explicitly.

[…]

(the full text is from function ‘magit--magit-popup-warning’ in
‘/usr/share/emacs/site-lisp/elpa-src/magit-2.99.0/magit-obsolete.el’.)

The interruption is often enough that the Magit user interface becomes
effectively unusable, hence this bug is “Severity: important”.

This warning occurs on my system is because Magithub has a dependency
on ‘magit-popup’, but does not declare it in a way that the Emacs
package manager can detect. A debugging backtrace shows:

=
Debugger entered--entering a function:
* magit--magit-popup-warning()
  magit-define-popup-action(magit-dispatch-popup 72 "Magithub" 
magithub-dispatch-popup 33)
  (progn (magit-define-popup-action (quote magit-dispatch-popup) 72 "Magithub" 
(function magithub-dispatch-popup) 33) (define-key magit-status-mode-map "H" 
(function magithub-dispatch-popup)))
  (lambda nil (progn (magit-define-popup-action (quote magit-dispatch-popup) 72 
"Magithub" (function magithub-dispatch-popup) 33) (define-key 
magit-status-mode-map "H" (function magithub-dispatch-popup()
  
eval-after-load-helper("/usr/share/emacs/site-lisp/elpa/magit-2.99.0/magit.elc")
  run-hook-with-args(eval-after-load-helper 
"/usr/share/emacs/site-lisp/elpa/magit-2.99.0/magit.elc")
  
do-after-load-evaluation("/usr/share/emacs/site-lisp/elpa/magit-2.99.0/magit.elc")
  require(magit)
  
byte-code("\300\301!\210\302\303\304\305\306\307%\210\310\311\312\313\314DD\315\306\303\316\317\320\321&\011\207"
 [require magit custom-declare-group magit-extras nil "Additional functionality 
for Magit." :group magit-extensions custom-declare-variable 
magit-gitk-executable funcall function #f(compiled-function () #) "The Gitk executable." :set-after (magit-git-executable) :type 
string] 10)
  autoload-do-load((autoload "magit-extras" "Like `next-line' but with 
Magit-specific shift-selection.\n\nMagit's selection mechanism is based on the 
region but selects\nan area that is larger than the region.  This causes 
`next-line'\nwhen invoked while holding the shift key to move down one 
line\nand thereby select two lines.  When invoked inside a hunk body\nthis 
command does not move point on the first invocation and\nthereby it only 
selects a single line.  Which inconsistency you\nprefer is a matter of 
preference.\n\n(fn  ARG TRY-VSCROLL)" t nil) magit-next-line)
  command-execute(magit-next-line)
=

According to the warning message:

=
* If you use `magit-popup' to define your own popups but do not
  modify any of Magit's old popups, then you have to install
  `magit-popup' explicitly.  (You can also migrate to Transient,
  but there is no need to rush that.)
=

So according to that, either of those resolutions would be sufficient
to avoid this breakage.


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

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

Versions of packages elpa-magithub depends on:
ii  elpa-ghub+  0.3-5
ii  elpa-git-commit 2.99.0.git0957.ge8c7bd03-1
ii  

Bug#968006: marked as done (RM: magithub -- ROM; abandoned upstream; superseded by magit-forge)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:39:24 +
with message-id 
and subject line Bug#968006: Removed package(s) from unstable
has caused the Debian Bug report #968006,
regarding RM: magithub -- ROM; abandoned upstream; superseded by magit-forge
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.)


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

As stated on its git repository[1], the code has mostly migrated and
merged in magit-forge[2], which is now in experimental suite for testing
purposes and will probably be uploaded to unstable within this weekend.

Thus, this package has lost its meaning for being part of the Debian
archives and should be removed asap.

Cheers.


[1] https://github.com/vermiculus/magithub
[2] https://github.com/magit/forge

-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: 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:

elpa-magithub |0.1.7-2 | all
  magithub |0.1.7-2 | source

--- Reason ---
ROM; abandoned upstream; superseded by magit-forge
--

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 968...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967947: marked as done (RM: python-snowballstemmer -- NBS; binary python3-snowballstemmer now built by src:snowball)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:40:27 +
with message-id 
and subject line Bug#967947: Removed package(s) from unstable
has caused the Debian Bug report #967947,
regarding RM: python-snowballstemmer -- NBS; binary python3-snowballstemmer now 
built by src:snowball
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.)


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

Dear FTP masters,

Please remove python-snowballstemmer source package from sid. The only
binary package which used to be built from it is now built from snowball
source.

See this merge request for details:

https://salsa.debian.org/debian/snowball/-/merge_requests/4

--
Dmitry Shachnev


signature.asc
Description: 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:

python-snowballstemmer |2.0.0-1 | source

--- Reason ---
NBS; binary python3-snowballstemmer now built by src:snowball
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967899: marked as done (RM: hlint [armel armhf mips64el mipsel s390x] -- ROM; Unbuildable)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:41:55 +
with message-id 
and subject line Bug#967899: Removed package(s) from unstable
has caused the Debian Bug report #967899,
regarding RM: hlint [armel armhf mips64el mipsel s390x] -- ROM; Unbuildable
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.)


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

Hi,

The latest version of hlint build depends on haskell-ghc-lib-parser,
which is unbuildable on armel,armhf,mips64el,mipsel and s390x.

Please remove hlint from these architectures.

Thanks,

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

 hlint |   2.1.17-1 | armel, armhf, mips64el, mipsel, s390x
libghc-hlint-dev |   2.1.17-1 | armel, armhf, mips64el, mipsel, s390x
libghc-hlint-prof |   2.1.17-1 | armel, armhf, mips64el, mipsel, s390x

--- Reason ---
ROM; Unbuildable
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#957645: marked as done (oroborus: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:19:58 +
with message-id 
and subject line Bug#957645: fixed in oroborus 2.0.20+nmu1
has caused the Debian Bug report #957645,
regarding oroborus: ftbfs with GCC-10
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.)


-- 
957645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oroborus
Version: 2.0.20
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/oroborus_2.0.20_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
then mv -f ".deps/frame.Tpo" ".deps/frame.Po"; else rm -f ".deps/frame.Tpo"; 
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT getopt1.o -MD -MP -MF ".deps/getopt1.Tpo" -c -o getopt1.o 
getopt1.c; \
then mv -f ".deps/getopt1.Tpo" ".deps/getopt1.Po"; else rm -f 
".deps/getopt1.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT getopt.o -MD -MP -MF ".deps/getopt.Tpo" -c -o getopt.o 
getopt.c; \
then mv -f ".deps/getopt.Tpo" ".deps/getopt.Po"; else rm -f ".deps/getopt.Tpo"; 
exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT globals.o -MD -MP -MF ".deps/globals.Tpo" -c -o globals.o 
globals.c; \
then mv -f ".deps/globals.Tpo" ".deps/globals.Po"; else rm -f 
".deps/globals.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT hints.o -MD -MP -MF ".deps/hints.Tpo" -c -o hints.o hints.c; \
then mv -f ".deps/hints.Tpo" ".deps/hints.Po"; else rm -f ".deps/hints.Tpo"; 
exit 1; fi
hints.c: In function ‘initGnomeHints’:
hints.c:152:10: warning: variable ‘root’ set but not used 
[-Wunused-but-set-variable]
  152 |   Window root;
  |  ^~~~
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT i18n.o -MD -MP -MF ".deps/i18n.Tpo" -c -o i18n.o i18n.c; \
then mv -f ".deps/i18n.Tpo" ".deps/i18n.Po"; else rm -f ".deps/i18n.Tpo"; exit 
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT keyboard.o -MD -MP -MF ".deps/keyboard.Tpo" -c -o keyboard.o 
keyboard.c; \
then mv -f ".deps/keyboard.Tpo" ".deps/keyboard.Po"; else rm -f 
".deps/keyboard.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT misc.o -MD -MP -MF ".deps/misc.Tpo" -c -o misc.o misc.c; \
then mv -f ".deps/misc.Tpo" ".deps/misc.Po"; else rm -f ".deps/misc.Tpo"; exit 
1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT oroborus.o -MD -MP -MF ".deps/oroborus.Tpo" -c -o oroborus.o 
oroborus.c; \
then mv -f ".deps/oroborus.Tpo" ".deps/oroborus.Po"; else rm -f 
".deps/oroborus.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  -DDATADIR=\"/usr/share/oroborus\" 
 -Wall -g -O2 -MT parserc.o -MD -MP -MF ".deps/parserc.Tpo" -c -o parserc.o 
parserc.c; \
then mv -f ".deps/parserc.Tpo" ".deps/parserc.Po"; else rm -f 
".deps/parserc.Tpo"; exit 1; fi
parserc.c: In function ‘parseRc’:
parserc.c:47:5: warning: ‘strncpy’ specified bound 512 equals destination size 
[-Wstringop-truncation]
   47 | strncpy (filename, file, sizeof (filename));
  | ^~~
if gcc -DHAVE_CONFIG_H -I. -I. -I.-g -O2  

Bug#966702: marked as done (mongo-cxx-driver: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 15:13:22 -0400
with message-id <20200806191322.gf13...@connexer.com>
and subject line Re: Bug#966702: mongo-cxx-driver: maintainer address bounces
has caused the Debian Bug report #966702,
regarding mongo-cxx-driver: maintainer address bounces
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.)


-- 
966702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-cxx-driver
Version: 3.6.0-1
Severity: serious
X-Debbugs-Cc: Roberto C. Sanchez 

The maintainer address bounces, see below.

Ansgar

 Forwarded Message 
From: Mail Delivery Subsystem 
To: envel...@ftp-master.debian.org
Subject: Delivery Status Notification (Failure)
Date: Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
Authentication-Results: tsukuyomi; dkim=pass (Good 2048 bit rsa-sha256 

   signature) header.d=googlemail.com header.a=rsa-sha256
X-Spam-Status: No, score=-101.9 required=5.0 
tests=BAYES_00,RCVD_IN_DNSWL_NONE,
SHORTCIRCUIT shortcircuit=ham 
autolearn=disabled version=3.4.2

Hello ftpmas...@ftp-master.debian.org,

We're writing to let you know that the group you tried to contact 
(mongo-cxx-driver-debian) may not exist, or you may not have permission to post 
messages to the group. A few more details on why you weren't able to post:

 * You might have spelled or formatted the group name incorrectly.
 * The owner of the group may have removed this group.
 * You may need to join the group before receiving permission to post.
 * This group may not be open to posting.

If you have questions related to this or any other Google Group, visit the Help 
Center at https://groups.google.com/support/.

Thanks,

Google Groups



- Original message -

X-Google-Smtp-Source: 
ABdhPJwHRCOrpgXWjZI0cNO0Ut5Nj9NtgTlkcmjDB98t1jmqaLbiHNDnltvm43img0BhMZV+q8Ge
X-Received: by 2002:a1c:9a02:: with SMTP id c2mr6501743wme.16.1596242048316;
Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1596242048; cv=none;
d=google.com; s=arc-20160816;
b=OZWP0X/e1+poO0/njPMgEzl7xxplS38kGNFAuif7twjiehuLOF8jsGy4GuQGY0XU7+
 BEEpeLzkmglqMnRMafEO+Oj6UMwCBkViZX4QbnNtsHSCJcCCGMHvryooPVNf4cxFxEB7
 1bAhCDUYkXDoiy8Hzqg/TgfV4pVCSTNu/TLyF+dxpnuDZi/LLu8WAZYWDn2y/s5j6blu
 8NtbvyrhN14O4LAO+WMfIv/SqOlS96IExeJnguLFOZ+mJZEKi3e8JBLPLnCn740o7GP2
 ylZ4+xI8Vf5pOGUo+uLVZWNYXBJgTWupnkO20YdhIiCWGTBkBvL+2EoVp+qzkdNfGK3e
 TxAA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=date:message-id:subject:content-transfer-encoding:mime-version
 :auto-submitted:precedence:to:from;
bh=pMWByNUUOJCpAwm8HG7BWG7fSKEVM2pWZL7v1quA8lg=;
b=UdeOpVXBU2fecAcbIVR7fOjwF0gaBOc5xlV96I9clq36fj9dTN/vmpdkNKIe0v7/hy
 QfJOBCNi3mE3MVDHx8m81j6W8emDOMn0FZPH5+C5WcpcCR0LX6ARS/EWOFpv7fJp+K0j
 q0F41n7dkaz/m2AFhelLyemYHpxC75+cw/h1Hd94vb+Nrjh931nSE6PfMQqoVyqkuPgk
 CoUjQEOS/ZFYSJFDsZuwLRdP3SB8iMTDBwBgFaqR900nfpeAH3OJuJPhxgkFkbjScjq6
 /0e9SCWJbkWvrjtQ3NzovTG+Uw+Ts3mYUrrXYY5vxLlUKCiGO9B/xNyiDP15OzfOb3O2
 51Uw==
ARC-Authentication-Results: i=1; gmr-mx.google.com;
   spf=pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) smtp.mailfrom=envel...@ftp-master.debian.org
Return-Path: 
Received: from mailly.debian.org (mailly.debian.org. 
[2001:41b8:202:deb:6564:a62:52c3:4b72])
by gmr-mx.google.com with ESMTPS id m3si648598wme.0.2020.07.31.17.34.08
for 
(version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
Fri, 31 Jul 2020 17:34:08 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) client-ip=2001:41b8:202:deb:6564:a62:52c3:4b72;
Authentication-Results: gmr-mx.google.com;
   spf=pass (google.com: best guess record for domain of 
envel...@ftp-master.debian.org designates 2001:41b8:202:deb:6564:a62:52c3:4b72 
as permitted sender) smtp.mailfrom=envel...@ftp-master.debian.org
Received: from fasolo.debian.org ([138.16.160.17]:44886)
from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP 
CA,CN=fasolo.debian.org,EMAIL=hostmas...@fasolo.debian.org (verified)
by mailly.debian.org with esmtps 
(TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.92)
(envelope-from )
id 1k1fTT-0006aS-VU; Sat, 01 Aug 2020 00:34:07 +

Bug#966224: marked as done (RM: ezmlm-idx/experimental -- RoQA; NPOASR; useless without qmail)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:45 +
with message-id 
and subject line Bug#966224: Removed package(s) from experimental
has caused the Debian Bug report #966224,
regarding RM: ezmlm-idx/experimental -- RoQA; NPOASR; useless without qmail
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.)


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

with qmail removed from the archive, there is no point in keeping the
orphaned mailing list manager for it that never found its way out of
experimental.


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

 ezmlm-idx | 7.1.1-1~exp0.1 | source, amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
ezmlm-idx-mysql | 7.1.1-1~exp0.1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
ezmlm-idx-pgsql | 7.1.1-1~exp0.1 | amd64, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x

--- Reason ---
RoQA; NPOASR; useless without qmail
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#543397: marked as done (metainit: Please provide a manpage for MetaInit::Parse)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:34 +
with message-id 
and subject line Bug#966206: Removed package(s) from unstable
has caused the Debian Bug report #543397,
regarding metainit: Please provide a manpage for MetaInit::Parse
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.)


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

MetaInit::Parse includes POD documentation, but there is no manpage generated
for it, unlike other Perl modules in Debian. Please add one and refer to it from
update-metainit(1).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages metainit depends on:
ii  perl  5.10.0-25  Larry Wall's Practical Extraction 

metainit recommends no packages.

metainit suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 0.0.5+rm

Dear submitter,

as the package metainit 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/966206

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#965722: marked as done (metainit: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:34 +
with message-id 
and subject line Bug#966206: Removed package(s) from unstable
has caused the Debian Bug report #965722,
regarding metainit: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metainit
Version: 0.0.5
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package metainit uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 0.0.5+rm

Dear submitter,

as the package metainit 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/966206

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#885838: marked as done (infon-viewer: please migrate kdebase-bin relationship to kdialog)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:10:21 +
with message-id 
and subject line Bug#966207: Removed package(s) from unstable
has caused the Debian Bug report #885838,
regarding infon-viewer: please migrate kdebase-bin relationship to kdialog
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.)


-- 
885838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: infon-viewer
Version: 0~r198-8
Severity: wishlist
Tags: patch

Dear Maintainer,

your package depends or recommends a package which used to provide the
kdialog utility.  Now kdialog is shipped in an own source and binary,
so the package relation can be adjusted to use it directly.

Attached there is a patch for this.

Thanks,
-- 
Pino
--- a/debian/control
+++ b/debian/control
@@ -35,7 +35,7 @@ Package: infon-viewer
 Architecture: any
 Recommends: infon-devel
 Suggests: infon-server
-Depends: ${shlibs:Depends}, ${misc:Depends}, ssft, zenity | kdebase-bin
+Depends: ${shlibs:Depends}, ${misc:Depends}, ssft, zenity | kdialog
 Description: Program bugs to compete for food and survival - GUI
  Infon is a game which simulates the live of simple bugs who eat,
  propagate, eat each other and evolve. The players can not control
--- End Message ---
--- Begin Message ---
Version: 0~r198-8+rm

Dear submitter,

as the package infon 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/966207

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966207: marked as done (RM: infon -- ROM; No longer actively maintained)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:10:17 +
with message-id 
and subject line Bug#966207: Removed package(s) from unstable
has caused the Debian Bug report #966207,
regarding RM: infon -- ROM; No longer actively maintained
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

while requesting removal of `metainit` I noticed that this is still used
by the `infon` package. This, too, has probably little value these days
and I don’t mind if it is removed.

Cheers,
Joachim


-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXxsciBMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsaI0Anii60ChD3xat2tZv/8lG6U/XrzBAAKCz
Tx4yj9JieitEn7wjGfHgAP1HSg==
=DDD+
-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:

 infon |   0~r198-8 | source
infon-server | 0~r198-8+b4 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
infon-server | 0~r198-8+b5 | mips64el
infon-viewer | 0~r198-8+b4 | amd64, arm64, armel, armhf, i386, mipsel, ppc64el, 
s390x
infon-viewer | 0~r198-8+b5 | mips64el

--- Reason ---
ROM; No longer actively maintained
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#651004: marked as done (metainit: Move common shell script code to /lib/init/std-sysvinitscript? )

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:34 +
with message-id 
and subject line Bug#966206: Removed package(s) from unstable
has caused the Debian Bug report #651004,
regarding metainit: Move common shell script code to 
/lib/init/std-sysvinitscript? 
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.)


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

Package: metainit
Version: 0.0.5
Severity: wishlist

Hi.  Thanks to your blog post, I just had a closer look at metainit, and
it occured to me that it would be cleaner if the generated init.d
scripts sourced a common file for the common code.  Here is a draft
patch implementing this, while also fixing a bug in the handling of the
post-stop hook.

The generated script still lack reload and status support.  I guess both
should be added eventually.

diff -Nru metainit-0.0.5/debian/metainit.install 
metainit-0.0.5+nmu1/debian/metainit.install
--- metainit-0.0.5/debian/metainit.install  2007-06-16 17:01:58.0 
+0200
+++ metainit-0.0.5+nmu1/debian/metainit.install 2011-12-05 00:18:26.0 
+0100
@@ -2,4 +2,5 @@
 translators/usr/share/metainit/
 update-metainit/usr/sbin
 lib/*  /usr/share/perl5
+std-sysvinitscript /lib/init
 
diff -Nru metainit-0.0.5/std-sysvinitscript 
metainit-0.0.5+nmu1/std-sysvinitscript
--- metainit-0.0.5/std-sysvinitscript   1970-01-01 01:00:00.0 +0100
+++ metainit-0.0.5+nmu1/std-sysvinitscript  2011-12-05 00:12:23.0 
+0100
@@ -0,0 +1,76 @@
+# Exit if the package is not installed
+[ -x "$DAEMON" ] || exit 5
+
+# Load the VERBOSE setting and other rcS variables
+. /lib/init/vars.sh
+
+# Define LSB log_* functions.
+# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
+. /lib/lsb/init-functions
+
+#
+# Function that starts the daemon/service
+#
+do_start()
+{
+   prestart_hook
+   start-stop-daemon --start --oknodo --background --quiet --make-pidfile 
--pidfile $PIDFILE --exec $DAEMON -- \
+   $DAEMON_ARGS || return 1
+}
+
+#
+# Function that stops the daemon/service
+#
+do_stop()
+{
+   start-stop-daemon --stop --oknodo --quiet --retry=TERM/30/KILL/5 
--pidfile $PIDFILE --name $BASENAME
+   RETVAL="$?"
+
+   rm -f $PIDFILE
+
+   poststop_hook
+   return "$RETVAL"
+}
+
+#
+# Function that sends a SIGHUP to the daemon/service
+#
+do_reload() {
+   start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name 
$NAME
+   return 0
+}
+
+case "$1" in
+  start)
+   [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
+   do_start
+log_end_msg $?
+   ;;
+  stop)
+   [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
+   do_stop
+log_end_msg $?
+   ;;
+  restart|force-reload)
+   #
+   # If the "reload" option is implemented then remove the
+   # 'force-reload' alias
+   #
+   log_daemon_msg "Restarting $DESC" "$NAME"
+   do_stop
+   case "$?" in
+ 0)
+   do_start
+log_end_msg "$?"
+   ;;
+ *)
+   # Failed to stop
+   log_end_msg 1
+   ;;
+   esac
+   ;;
+  *)
+   echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload}" >&2
+   exit 3
+   ;;
+esac
diff -Nru metainit-0.0.5/utils/create-sysvinit-file 
metainit-0.0.5+nmu1/utils/create-sysvinit-file
--- metainit-0.0.5/utils/create-sysvinit-file   2007-06-21 21:20:45.0 
+0200
+++ metainit-0.0.5+nmu1/utils/create-sysvinit-file  2011-12-05 
00:16:14.0 +0100
@@ -72,112 +72,26 @@
 EOF
 ;
 
-# ... and the rest of the initscript, that is identical for all
-# metainit-created scripts.
-print << 'EOF'
-# Exit if the package is not installed
-[ -x "$DAEMON" ] || exit 5
-
-# Load the VERBOSE setting and other rcS variables
-. /lib/init/vars.sh
-
-# Define LSB log_* functions.
-# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
-. /lib/lsb/init-functions
-
-#
-# Function that starts the daemon/service
-#
-do_start()
-{
-EOF
-;
-
 if($initparams{"Prestart-Hook"}) {
+print "prestart_hook() {\n";
 print "\t" . join("\n\t",split("\n",$initparams{"Prestart-Hook"}));
-print "\n";
-}
-
-print << 'EOF'
-   start-stop-daemon --start --oknodo --background --quiet --make-pidfile 
--pidfile $PIDFILE --exec $DAEMON -- \
-   $DAEMON_ARGS || return 1
+print "}\n";
+} else {
+print "prestart_hook() { }\n";
 }
 
-#
-# Function that stops the daemon/service
-#

Bug#966206: marked as done (RM: metainit -- ROM; Obsolete, unused)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 16:12:29 +
with message-id 
and subject line Bug#966206: Removed package(s) from unstable
has caused the Debian Bug report #966206,
regarding RM: metainit -- ROM; Obsolete, unused
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Nudged by #965722 I think it’s probably best to remove metainit. I wrote
that 13 years ago to alleivate the pains during the init system wars,
but it never caught on, and is quite obsolete now.

If someone disagrees feel free to take over the package.

-BEGIN PGP SIGNATURE-

iHEEARECADEWIQQxTjstYFpus1p9gRn2KOuTR0MgbAUCXxsbsxMcbm9tZWF0YUBk
ZWJpYW4ub3JnAAoJEPYo65NHQyBsV80AnRMMeHtJDmyCgmOyTbucLidMekwgAJ9M
CseFz5s5B9crRe3BzOZMwZTgVA==
=TsU9
-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:

dh-metainit |  0.0.5 | all
  metainit |  0.0.5 | source, all

--- Reason ---
ROM; Obsolete, unused
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#828998: marked as done (ITP: gophernicus -- Gopher server)

[Debian Bug Tracking System]

Your message dated Thu, 6 Aug 2020 12:06:59 -0400
with message-id <20200806160659.safjsrhu7yuva...@zeta.rak.ac>
and subject line done
has caused the Debian Bug report #828998,
regarding ITP: gophernicus -- Gopher server
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.)


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

Dear Maintainer,

As of the time of this report, the only Gopher server available in an 
official Debian package is pygopherd.  That one has an annoying problem 
with zombies.  Therefore I would very much appreciate having Gophernicus 
made available.  This one is written in C, is modern, full-featured, and 
hopefully secure.  Its home git repository is at 
http://gophernicus.org/git/gophernicus.git/.  A .deb package may be 
created simply by typing "make deb".

Please advise if the below license is acceptable for a Debian package.  
If not, we can talk about it at gopher-proj...@lists.alioth.debian.org.

Gophernicus - Copyright (c) 2009-2015 Kim Holviala 
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
  notice, this list of conditions and the following disclaimer in the
  documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

-- System Information:
Debian Release: 7.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.5-x86_64-linode69 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gophernicus depends on:
ii  debconf   1.5.49
ii  libc6 2.19-11
ii  netbase   5.0
ii  openbsd-inetd [inet-superserver]  0.20091229-2

Versions of packages gophernicus recommends:
ii  lsb-release  4.1+Debian8+deb7u1

Versions of packages gophernicus suggests:
ii  lynx  2.8.8dev.12-2
ii  php5-cli  5.4.45-0+deb7u3

-- debconf information:
* gophernicus/fqdn: nyx.feedle.net
--- End Message ---
--- Begin Message ---
Control: fixed -1 3.0.1-1

Done. Had wrong ITP/bug number in changelog.


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

Bug#966534: marked as done (RM: autodns-dhcp -- ROM; Old package with better alternatives on the archive.)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 10:25:07 -0700
with message-id <87wo2b3cwc@iris.silentflame.com>
and subject line Re: Bug#966534: RM: autodns-dhcp -- ROM; Old package with 
better alternatives on the archive.
has caused the Debian Bug report #966534,
regarding RM: autodns-dhcp -- ROM; Old package with better alternatives on the 
archive.
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.)


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


The functionality of the package is not exactly covered by any other package
but similar functionality is achieved by other packages and this old one
hasn't been really tested on current software versions, even though it
should work, so if somebody wants to use it he can always get it from old
releases.

Thanks.
--- End Message ---
--- Begin Message ---
Hello,

On Thu 30 Jul 2020 at 12:10PM +02, Santiago Garcia Mantinan wrote:

> Package: ftp.debian.org
> Severity: normal
>
>
> The functionality of the package is not exactly covered by any other package
> but similar functionality is achieved by other packages and this old one
> hasn't been really tested on current software versions, even though it
> should work, so if somebody wants to use it he can always get it from old
> releases.

It sounds like you should orphan the package but I don't see a reason
for removal here -- it isn't RC-buggy and you say yourself that it
should work.

-- 
Sean Whitton


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

Processed: Re: Bug#965282: wpasupplicant: fails to create /var/run/wpa_supplicant control interface in Debian 10

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 965282
Bug #965282 [wpasupplicant] wpasupplicant: fails to create 
/var/run/wpa_supplicant control interface in Debian 10
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
965282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#966700: marked as done (RM: kimagemapeditor [armel mips64el ppc64el s390x] -- ROM; requires QtWebEngine)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:32:36 +
with message-id 
and subject line Bug#966700: Removed package(s) from unstable
has caused the Debian Bug report #966700,
regarding RM: kimagemapeditor [armel mips64el ppc64el s390x] -- ROM; requires 
QtWebEngine
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.)


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

Hi,

the new version of src:kimagemapeditor requires QtWebEngine for the main
interface: as result, it is built only on few architectures.  Hence,
please remove kimagemapeditor on the following architectures:
  armel mips64el ppc64el s390x

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

kimagemapeditor | 4:19.08.1-1 | armel
kimagemapeditor | 4:19.08.1-1+b1 | mips64el, ppc64el, s390x

--- Reason ---
ROM; requires QtWebEngine
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#937959: marked as done (python-ntlm: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:33:22 +
with message-id 
and subject line Bug#966802: Removed package(s) from unstable
has caused the Debian Bug report #937959,
regarding python-ntlm: 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.)


-- 
937959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-ntlm
Version: 1.1.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:python-ntlm

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: 1.1.0-1+rm

Dear submitter,

as the package python-ntlm 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/966802

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#899676: marked as done (python-omniorb: Invalid maintainer address pkg-corba-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:35:07 +
with message-id 
and subject line Bug#967054: Removed package(s) from unstable
has caused the Debian Bug report #899676,
regarding python-omniorb: Invalid maintainer address 
pkg-corba-de...@lists.alioth.debian.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.)


-- 
899676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-omniorb
Version: 3.6-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of python-omniorb,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package python-omniorb since the list address
pkg-corba-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-corba-de...@lists.alioth.debian.org is 3.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 4.2.2-0.2+rm

Dear submitter,

as the package python-omniorb 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/967054

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967072: marked as done (RM: freehep-graphicsio-tests -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:53:15 +
with message-id 
and subject line Bug#967072: Removed package(s) from unstable
has caused the Debian Bug report #967072,
regarding RM: freehep-graphicsio-tests -- ROM; obsoleted by 
freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-tests, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-tests | 2.1.1+dfsg1-5 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967071: marked as done (RM: freehep-graphicsio-swf -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:52:52 +
with message-id 
and subject line Bug#967071: Removed package(s) from unstable
has caused the Debian Bug report #967071,
regarding RM: freehep-graphicsio-swf -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-swf, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-swf | 2.1.1+dfsg-3 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967070: marked as done (RM: freehep-graphicsio-svg -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:52:30 +
with message-id 
and subject line Bug#967070: Removed package(s) from unstable
has caused the Debian Bug report #967070,
regarding RM: freehep-graphicsio-svg -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-svg, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-svg |2.1.1-5 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967069: marked as done (RM: freehep-graphicsio-ps -- ROM; obsoleted by freehep-vectorgraphics)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:52:06 +
with message-id 
and subject line Bug#967069: Removed package(s) from unstable
has caused the Debian Bug report #967069,
regarding RM: freehep-graphicsio-ps -- ROM; obsoleted by freehep-vectorgraphics
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.)


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

Package freehep-vectorgraphics provide a more recent version of
freehep-graphicsio-ps, so the latter can be removed. Thanks!
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

freehep-graphicsio-ps |2.1.1-3 | source

--- Reason ---
ROM; obsoleted by freehep-vectorgraphics
--

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 967...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#957798: marked as done (silversearcher-ag: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 18:18:30 +
with message-id 
and subject line Bug#957798: fixed in silversearcher-ag 2.2.0+git20200805-1
has caused the Debian Bug report #957798,
regarding silversearcher-ag: ftbfs with GCC-10
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.)


-- 
957798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:silversearcher-ag
Version: 2.2.0-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/silversearcher-ag_2.2.0-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
gcc -DHAVE_CONFIG_H -I. -I./src   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE -c -o 
src/main.o src/main.c
gcc -DHAVE_CONFIG_H -I. -I./src   -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE -c -o 
src/zfile.o src/zfile.c
gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pthread  -Wall -Wextra -Wformat=2 
-Wno-format-nonliteral -Wshadow -Wpointer-arith -Wcast-qual 
-Wmissing-prototypes -Wno-missing-braces -std=gnu89 -D_GNU_SOURCE  -Wl,-z,relro 
-o ag src/ignore.o src/log.o src/options.o src/print.o src/print_w32.o 
src/scandir.o src/search.o src/lang.o src/util.o src/decompress.o src/main.o 
src/zfile.o -lpcre -llzma   -lz  
/usr/bin/ld: src/log.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/log.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/log.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/log.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/options.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/options.o:./src/ignore.h:32: multiple definition of 
`root_ignores'; src/ignore.o:./src/ignore.h:32: first defined here
/usr/bin/ld: src/options.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/options.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/options.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/print.o:./src/options.h:94: multiple definition of `opts'; 
src/ignore.o:./src/options.h:94: first defined here
/usr/bin/ld: src/print.o:./src/util.h:15: multiple definition of `out_fd'; 
src/ignore.o:./src/util.h:15: first defined here
/usr/bin/ld: src/print.o:./src/util.h:54: multiple definition of `stats'; 
src/ignore.o:./src/util.h:54: first defined here
/usr/bin/ld: src/print.o:./src/log.h:12: multiple definition of `print_mtx'; 
src/ignore.o:./src/log.h:12: first defined here
/usr/bin/ld: src/print.o:./src/ignore.h:32: multiple 

Bug#957995: marked as done (xscorch: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 19:34:06 +
with message-id 
and subject line Bug#957995: fixed in xscorch 0.2.1-1+nmu4
has caused the Debian Bug report #957995,
regarding xscorch: ftbfs with GCC-10
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.)


-- 
957995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xscorch
Version: 0.2.1-1+nmu2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/xscorch_0.2.1-1+nmu2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
make[4]: Leaving directory '/<>/libj/jreg'
Making all in jstr
make[4]: Entering directory '/<>/libj/jstr'
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_arg.o -MD 
-MP -MF .deps/libjstr_a-str_arg.Tpo -c -o libjstr_a-str_arg.o `test -f 
'str_arg.c' || echo './'`str_arg.c
mv -f .deps/libjstr_a-str_arg.Tpo .deps/libjstr_a-str_arg.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_case.o 
-MD -MP -MF .deps/libjstr_a-str_case.Tpo -c -o libjstr_a-str_case.o `test -f 
'str_case.c' || echo './'`str_case.c
mv -f .deps/libjstr_a-str_case.Tpo .deps/libjstr_a-str_case.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_cgi.o -MD 
-MP -MF .deps/libjstr_a-str_cgi.Tpo -c -o libjstr_a-str_cgi.o `test -f 
'str_cgi.c' || echo './'`str_cgi.c
mv -f .deps/libjstr_a-str_cgi.Tpo .deps/libjstr_a-str_cgi.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_comp.o 
-MD -MP -MF .deps/libjstr_a-str_comp.Tpo -c -o libjstr_a-str_comp.o `test -f 
'str_comp.c' || echo './'`str_comp.c
mv -f .deps/libjstr_a-str_comp.Tpo .deps/libjstr_a-str_comp.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_con.o -MD 
-MP -MF .deps/libjstr_a-str_con.Tpo -c -o libjstr_a-str_con.o `test -f 
'str_con.c' || echo './'`str_con.c
mv -f .deps/libjstr_a-str_con.Tpo .deps/libjstr_a-str_con.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_copy.o 
-MD -MP -MF .deps/libjstr_a-str_copy.Tpo -c -o libjstr_a-str_copy.o `test -f 
'str_copy.c' || echo './'`str_copy.c
mv -f .deps/libjstr_a-str_copy.Tpo .deps/libjstr_a-str_copy.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_creat.o 
-MD -MP -MF .deps/libjstr_a-str_creat.Tpo -c -o libjstr_a-str_creat.o `test -f 
'str_creat.c' || echo './'`str_creat.c
mv -f .deps/libjstr_a-str_creat.Tpo .deps/libjstr_a-str_creat.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_info.o 
-MD -MP -MF .deps/libjstr_a-str_info.Tpo -c -o libjstr_a-str_info.o `test -f 
'str_info.c' || echo './'`str_info.c
mv -f .deps/libjstr_a-str_info.Tpo .deps/libjstr_a-str_info.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_io.o -MD 
-MP -MF .deps/libjstr_a-str_io.Tpo -c -o libjstr_a-str_io.o `test -f 'str_io.c' 
|| echo './'`str_io.c
mv -f .deps/libjstr_a-str_io.Tpo .deps/libjstr_a-str_io.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_num.o -MD 
-MP -MF .deps/libjstr_a-str_num.Tpo -c -o libjstr_a-str_num.o `test -f 
'str_num.c' || echo './'`str_num.c
mv -f .deps/libjstr_a-str_num.Tpo .deps/libjstr_a-str_num.Po
gcc -DHAVE_CONFIG_H -I. -I../.. -I../-g -O2 -MT libjstr_a-str_printf.o 
-MD -MP -MF .deps/libjstr_a-str_printf.Tpo -c -o libjstr_a-str_printf.o `test 
-f 'str_printf.c' || echo './'`str_printf.c
mv -f .deps/libjstr_a-str_printf.Tpo .deps/libjstr_a-str_printf.Po
gcc 

Bug#966453: marked as done (RM: golang-github-unknwon-cae -- RoQA; Orphaned, open security issues, dead upstream, no rdeps)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:28 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #966453,
regarding RM: golang-github-unknwon-cae -- RoQA; Orphaned, open security 
issues, dead upstream, no rdeps
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.)


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

Please golang-github-unknwon-cae. It was once introduced for gitea, is 
security-buggy
and there are no remaining rdeps.

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:

golang-github-unknwon-cae | 0.0~git20160715.0.c6aac99-4 | source
golang-github-unknwon-cae-dev | 0.0~git20160715.0.c6aac99-4 | all

--- Reason ---
RoQA; Orphaned, open security issues, dead upstream, no rdeps
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966442: marked as done (RM: golang-github-cbroglie-mapstructure -- RoQA; fork of golang-github-mitchellh-mapstructure; no rdepends)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:17:52 +
with message-id 
and subject line Bug#966442: Removed package(s) from unstable
has caused the Debian Bug report #966442,
regarding RM: golang-github-cbroglie-mapstructure -- RoQA; fork of 
golang-github-mitchellh-mapstructure; no rdepends
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.)


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

This fork is used to build golang-github-docker-goamz.
After removing #966440 golang-github-docker-goamz, this can be removed as well.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-github-cbroglie-mapstructure | 0.0~git20150405.0.25325b4-2 | source
golang-github-cbroglie-mapstructure-dev | 0.0~git20150405.0.25325b4-2 | all

--- Reason ---
RoQA; fork of golang-github-mitchellh-mapstructure; no rdepends
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967955: marked as done (golang-github-unknwon-cae: CVE-2020-7664)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:32 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #967955,
regarding golang-github-unknwon-cae: CVE-2020-7664
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.)


-- 
967955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7664[0]:
| In all versions of the package github.com/unknwon/cae/zip, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


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-2020-7664
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7664
[1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160715.0.c6aac99-4+rm

Dear submitter,

as the package golang-github-unknwon-cae 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/966453

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#889200: marked as done (O: golang-github-unknwon-cae -- PHP-like Compression and Archive Extensions in Go)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:32 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #889200,
regarding O: golang-github-unknwon-cae -- PHP-like Compression and Archive 
Extensions in Go
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.)


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

This package was added to Debian as a dependency of Gitea. I am no longer
working on Gitea and no longer have a reason to continue maintaining the
dependencies.

-- 
Michael Lustfield
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160715.0.c6aac99-4+rm

Dear submitter,

as the package golang-github-unknwon-cae 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/966453

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#967956: marked as done (golang-github-unknwon-cae: CVE-2020-7668)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:19:32 +
with message-id 
and subject line Bug#966453: Removed package(s) from unstable
has caused the Debian Bug report #967956,
regarding golang-github-unknwon-cae: CVE-2020-7668
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.)


-- 
967956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-unknwon-cae
Version: 0.0~git20160715.0.c6aac99-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-unknwon-cae.

CVE-2020-7668[0]:
| In all versions of the package github.com/unknwon/cae/tz, the
| ExtractTo function doesn't securely escape file paths in zip archives
| which include leading or non-leading "..". This allows an attacker to
| add or replace files system-wide.


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-2020-7668
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7668

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 0.0~git20160715.0.c6aac99-4+rm

Dear submitter,

as the package golang-github-unknwon-cae 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/966453

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#966699: marked as done (RM: parley [armel mips64el ppc64el s390x] -- ROM; requires QtWebEngine)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:31:56 +
with message-id 
and subject line Bug#966699: Removed package(s) from unstable
has caused the Debian Bug report #966699,
regarding RM: parley [armel mips64el ppc64el s390x] -- ROM; requires QtWebEngine
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.)


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

Hi,

the new version of src:parley requires QtWebEngine for the main
interface: as result, it is built only on few architectures.  Hence,
please remove parley on the following architectures:
  armel mips64el ppc64el s390x

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

parley | 4:17.08.3-1.1 | armel
parley | 4:17.08.3-1.1+b1 | mips64el, ppc64el, s390x

--- Reason ---
ROM; requires QtWebEngine
--

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 966...@bugs.debian.org.

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

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#965402: marked as done (acfax: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 06 Aug 2020 17:31:13 +
with message-id 
and subject line Bug#966658: Removed package(s) from unstable
has caused the Debian Bug report #965402,
regarding acfax: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acfax
Version: 981011-17
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package acfax uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 981011-17+rm

Dear submitter,

as the package acfax 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/966658

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.
Sean Whitton (the ftpmaster behind the curtain)--- End Message ---

Bug#957710: marked as done (proxychains: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 07 Aug 2020 04:49:08 +
with message-id 
and subject line Bug#957710: fixed in proxychains 3.1-9
has caused the Debian Bug report #957710,
regarding proxychains: ftbfs with GCC-10
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.)


-- 
957710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:proxychains
Version: 3.1-8.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/proxychains_3.1-8.1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in proxychains
make[3]: Entering directory '/<>/proxychains'
Making all in docs
make[4]: Entering directory '/<>/proxychains/docs'
Making all in en
make[5]: Entering directory '/<>/proxychains/docs/en'
make[5]: Nothing to be done for 'all'.
make[5]: Leaving directory '/<>/proxychains/docs/en'
make[5]: Entering directory '/<>/proxychains/docs'
make[5]: Nothing to be done for 'all-am'.
make[5]: Leaving directory '/<>/proxychains/docs'
make[4]: Leaving directory '/<>/proxychains/docs'
make[4]: Entering directory '/<>/proxychains'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libproxychains.lo libproxychains.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o core.lo core.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c core.c  -fPIC -DPIC -o .libs/core.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c libproxychains.c  -fPIC -DPIC -o 
.libs/libproxychains.o
core.c: In function ‘proxy_gethostbyname’:
core.c:657:4: warning: ignoring return value of ‘read’ declared with attribute 
‘warn_unused_result’ [-Wunused-result]
  657 |read(pipe_fd[0],,sizeof(buff));
  |^~~
In file included from /usr/include/string.h:495,
 from /usr/include/memory.h:29,
 from core.c:24:
In function ‘strncpy’,
inlined from ‘tunnel_to’ at core.c:314:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin___strncpy_chk’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
core.c: In function ‘tunnel_to’:
core.c:312:8: note: length computed here
  312 |  c=strlen(user);
  |^~~~
In file included from /usr/include/string.h:495,
 from /usr/include/memory.h:29,
 from core.c:24:
In function ‘strncpy’,
inlined from ‘tunnel_to’ at core.c:318:6:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: 
‘__builtin_strncpy’ specified bound depends on the length of the source 
argument [-Wstringop-overflow=]
  106 |   return __builtin___strncpy_chk (__dest, __src,