Processed: Fixed in giac already

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 972827 1.4.9.69+dfsg1-3
Bug #972827 {Done: Julien Puydt } [libgiac-dev] libgiac-dev: 
should include config.h
There is no source info for the package 'libgiac-dev' at version 
'1.4.9.69+dfsg1-3' with architecture ''
Unable to make a source version for version '1.4.9.69+dfsg1-3'
Marked as fixed in versions 1.4.9.69+dfsg1-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#971788: marked as done (libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1 version is unavailable)

[Atamert Ölçgen]

Now I managed to update and test. Thanks again!

On Wed, Nov 4, 2020 at 1:08 AM Andreas Beckmann  wrote:

> On 11/3/20 9:24 PM, Atamert Ölçgen wrote:
> > As of now I still can't upgrade to 450.80.*.
> > https://packages.debian.org/buster-backports/libnvidia-rtcore also
> > lists 450.66-1~bpo10+1 with the missing dependency. Am I missing
> something?
>
> Please wait some hours until the package has been built and distributed
> to the mirrors ;-)
>
> Andreas
>


-- 
Kind Regards,
Atamert Ölçgen

◻◼◻
◻◻◼
◼◼◼

www.muhuk.com

Bug#973721: marked as done (libssreflect-coq: Depends: coq-8.12.0+4.08.1 but it is not installable)

[Debian Bug Tracking System]

Your message dated Wed, 04 Nov 2020 06:48:18 +
with message-id 
and subject line Bug#973721: fixed in ssreflect 1.11.0-2
has caused the Debian Bug report #973721,
regarding libssreflect-coq: Depends: coq-8.12.0+4.08.1 but it is not installable
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.)


-- 
973721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssreflect-coq
Version: 1.11.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

$ apt install libssreflect-coq
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libssreflect-coq : Depends: coq-8.12.0+4.08.1 but it is not installable
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ssreflect
Source-Version: 1.11.0-2
Done: =?utf-8?q?St=C3=A9phane_Glondu?= 

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ssreflect package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2020 07:25:54 +0100
Source: ssreflect
Architecture: source
Version: 1.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 973721
Changes:
 ssreflect (1.11.0-2) unstable; urgency=medium
 .
   * Recompile with OCaml 4.11.1 (Closes: #973721)
Checksums-Sha1:
 b3b2254ddcbf371c3f92c505d7ef9b4f00202239 1889 ssreflect_1.11.0-2.dsc
 4f363bf1aa3b393d97e51802d51a654375d9bfe0 12768 ssreflect_1.11.0-2.debian.tar.xz
Checksums-Sha256:
 61e59a4d7b070329e65d050c3a2623fa03baaf56a699592714ad5bef36986b24 1889 
ssreflect_1.11.0-2.dsc
 ac1e4318f78a57e415c7cc8af9db27884a743e2f7ca9e9f6e508c2f1146d7af4 12768 
ssreflect_1.11.0-2.debian.tar.xz
Files:
 fc8a8186f2a0abf553c6033770f69cd2 1889 math optional ssreflect_1.11.0-2.dsc
 02c07e120ce74c1114976219ef92aa10 12768 math optional 
ssreflect_1.11.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl+iSrMSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBkNAH/jLXzcvoQTDIuCTF8b360FhjCDZmwDEF
pDid4PpozwzIzl+ycpnzetawJKZ4rEEOwm7qJhQqNwQJHkKFki6mjKij+6tjU7QJ
cfHqFVV4glHW4XdG9OJxADULOJB1OMZRp90M9AfHQ0I3Dy463A9EL1nTYGk4tMyn
XlFzKanT6l3aZVLRdK/oUPPXDTol/D1pKO7jcV1sUXBrav8t4Zbufle1COfkbZGw
AywjCEgP8LkKB9eckrJU5yYJd0GVnf2dF5YT+rtLu2C2BDty794bXbPHRqQaj5m4
upg46e8h2ku4yOFakXkZkvNvGrAwzq1p34MdFw2Ps7NoUrcx/j+pzqs=
=mLTV
-END PGP SIGNATURE End Message ---

Bug#973721: libssreflect-coq: Depends: coq-8.12.0+4.08.1 but it is not installable

[Stéphane Glondu]

Le 03/11/2020 à 22:53, Sebastian Ramacher a écrit :
> The following packages have unmet dependencies:
>  libssreflect-coq : Depends: coq-8.12.0+4.08.1 but it is not installable
> E: Unable to correct problems, you have held broken packages.

Oh. I built the package locally (on Sep 11), but forgot to upload it. Sorry!


Cheers,

-- 
Stéphane

Bug#973721: marked as pending in ssreflect

[Stéphane Glondu]

Control: tag -1 pending

Hello,

Bug #973721 in ssreflect reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/ssreflect/-/commit/586158ab82a226f44a66f99fa110199e8de43dce


Recompile with OCaml 4.11.1 (Closes: #973721)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973721

Processed: Bug#973721 marked as pending in ssreflect

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973721 [libssreflect-coq] libssreflect-coq: Depends: coq-8.12.0+4.08.1 but 
it is not installable
Added tag(s) pending.

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

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

[Boyuan Yang]

Hi,

在 2020-11-03星期二的 22:21 +，Limonciello, Mario写道：
> > -Original Message-
> > From: Boyuan Yang 
> > Sent: Tuesday, November 3, 2020 13:09
> > To: sub...@bugs.debian.org
> > Subject: Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-
> > friendly
> > 
> > Package: fwupd-amd64-signed
> > Severity: grave
> > Version: 1.4.6+2
> > X-Debbugs-CC: 93...@debian.org mario.limoncie...@dell.com
> > 
> > Dear EFI Team,
> > 
> > Package fwupd-amd64-signed currently cannot be installed on Debian
> > Unstable/Sid. It depends on fwupd (= 1.4.6-2) while Sid only has
> > fwupd
> > (= 1.4.6-2+b1).
> 
> I'm sorry can you show me where this +b1 build is?
> 
> I don't see it mentioned in https://tracker.debian.org/pkg/fwupd

It is shown at https://buildd.debian.org/status/package.php?p=fwupd .
If you actually install a Debian Sid system, you can also find the
package with this version string.


> > It seems obvious that such dependency relationship made
> > fwupd/fwupd-
> > amd64-signed not binNMU-friendly. Please consider setting a version
> > range to allow binNMU-ed package to satisfy the dependency
> > relationship.

Please consider reading https://wiki.debian.org/binNMU and see how can
things be improved.

Thanks,
Boyuan Yang

Processed: 972969 fixed in openafs-1.8.6-4

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 972969 openafs/1.8.6-4
Bug #972969 {Done: Benjamin Kaduk } [openafs-modules-dkms] 
openafs-modules-dkms: Does not build on bullseye with kernel 5.9.1
Marked as fixed in versions openafs/1.8.6-4.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

[Limonciello, Mario]

> -Original Message-
> From: Boyuan Yang 
> Sent: Tuesday, November 3, 2020 13:09
> To: sub...@bugs.debian.org
> Subject: Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly
> 
> Package: fwupd-amd64-signed
> Severity: grave
> Version: 1.4.6+2
> X-Debbugs-CC: 93...@debian.org mario.limoncie...@dell.com
> 
> Dear EFI Team,
> 
> Package fwupd-amd64-signed currently cannot be installed on Debian
> Unstable/Sid. It depends on fwupd (= 1.4.6-2) while Sid only has fwupd
> (= 1.4.6-2+b1).

I'm sorry can you show me where this +b1 build is?

I don't see it mentioned in https://tracker.debian.org/pkg/fwupd

> 
> It seems obvious that such dependency relationship made fwupd/fwupd-
> amd64-signed not binNMU-friendly. Please consider setting a version
> range to allow binNMU-ed package to satisfy the dependency
> relationship.
> 
> Thanks,
> Boyuan Yang

Bug#972802: [Pkg-rust-maintainers] Bug#972802: rust-webpki-roots: duplicates ca-certificates, remove from Debian?

[Paul Wise]

On Tue, 2020-11-03 at 20:45 +, kpcyrd wrote:

> It's more complicated than that, there's rustls-native-certs to use the
> local certificate store, but the patch would be so invasive that debian
> would effectively maintain a fork. At the time of writing webpki-roots
> has 85 reverse dependencies on crates.io, while rustls-native-certs has
> 13.

I wonder if a wrapper crate that would present a common API and allow a
build-time choice between the two options would be the way to go? Then
everything that uses either of them could get changed upstream to use
the wrapper, upstream builds could use webpki-roots and Debian could
configure our builds to use rustls-native-certs. Is that plausible?

> > - The quality of the ca-certificates package on debian-based Linux
> > distributions is poor. At the time of writing, this ships many
> > certificates not included in the Mozilla set, either because they
> > failed an audit and were withdrawn[1] or were removed for
> > mississuance[2].
> 
> [1]: https://bugs.mozilla.org/show_bug.cgi?id=1448506
> [2]: https://bugs.mozilla.org/show_bug.cgi?id=1552374

FTR, those URLs are broken, they need "bugs" replaced with "bugzilla".

TÜRKTRUST was removed from the Debian package in 20190110 and Certnomis
was removed from the Debian package in 20200601, those were definitely
quite a bit later than what Mozilla did :(

I'm not sure what the solution there is. It probably doesn't help that
the current maintainer is not yet a Debian member, but is a Debian
Maintainer (DM), but can't upload ca-certificates without a sponsor.
Maybe the package should be co-maintained by the Debian security team? 

https://ftp-master.debian.org/dm.txt

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#957439: libforms: ftbfs with GCC-10

[Paul Wise]

On Tue, 2020-11-03 at 11:18 -0500, Peter S Galbraith wrote:

> Thanks for your upload. Real life took over again. :-(

No worries. Debian should definitely be lower priority than real life :)

> Want to take over the package? :-)

I don't have time to take over another package, sorry. :(

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#957510: marked as done (lxtask: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 4 Nov 2020 01:31:03 +0200
with message-id <20201103233103.ga3...@rep.kiev.ua>
and subject line Re: Bug#957510: lxtask: ftbfs with GCC-10
has caused the Debian Bug report #957510,
regarding lxtask: 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.)


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

[...]
  551 | struct _GTimeVal
  |^
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 utils.h:25,
 from utils.c:27:
/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/glib/gi18n.h:21,
 from utils.c:26:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
gcc -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wl,-z,relro -Wl,-z,now -o lxtask lxtask-main.o 
lxtask-callbacks.o lxtask-functions.o lxtask-interface.o 
lxtask-xfce-taskmanager-linux.o lxtask-utils.o -lgtk-x11-2.0 -lgdk-x11-2.0 
-lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype 
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:45: multiple definition of 
`taskpopup'; lxtask-main.o:./src/interface.h:45: first defined here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:42: multiple definition of 
`selection'; lxtask-main.o:./src/interface.h:42: first defined here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:64: multiple definition of 
`column'; lxtask-main.o:./src/interface.h:64: first defined here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:50: multiple definition of 
`mem_usage_progress_bar_box'; lxtask-main.o:./src/interface.h:50: first defined 
here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:49: multiple definition of 
`cpu_usage_progress_bar_box'; lxtask-main.o:./src/interface.h:49: first defined 
here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:48: multiple definition of 
`mem_usage_progress_bar'; lxtask-main.o:./src/interface.h:48: first defined here
/usr/bin/ld: lxtask-callbacks.o:./src/interface.h:47: multiple definition of 
`cpu_usage_progress_bar'; lxtask-main.o:./src/interface.h:47: first defined here

Bug#973718: blueman: CVE-2020-15238

[Nobuhiro Iwamatsu]

Hi,

I added some comment on https://mentors.debian.net/. Could  you check it?

Best regards,
  Nobuhiro

2020年11月4日(水) 8:09 Nobuhiro Iwamatsu :
>
> Hi,
>
> Sorry,.I will check this,If there is no problem, upload it.
>
> Best regards,
>   Nobuhiro
>
> 2020年11月4日(水) 6:17 Christopher Schramm :
>
> >
> > Hi Salvatore,
> >
> > 2.1.4-1 is waiting at https://mentors.debian.net/package/blueman/. I can
> > add the CVE number and / or this bug to the changelog if you like.
> >
> > Unfortunately my sponsor Nobuhiro seems to be unavailable.
> >
> > Regards
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#957571: mtpaint: diff for NMU version 3.40-3.1

[Sudip Mukherjee]

Control: tags 957571 + patch
Control: tags 957571 + pending
--

Dear maintainer,

I've prepared an NMU for mtpaint (versioned as 3.40-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru mtpaint-3.40/debian/changelog mtpaint-3.40/debian/changelog
--- mtpaint-3.40/debian/changelog   2016-04-07 10:49:10.0 +0100
+++ mtpaint-3.40/debian/changelog   2020-11-03 23:04:37.0 +
@@ -1,3 +1,10 @@
+mtpaint (3.40-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957571)
+
+ -- Sudip Mukherjee   Tue, 03 Nov 2020 23:04:37 
+
+
 mtpaint (3.40-3) unstable; urgency=medium
 
   * Bump Standards-Version to 3.9.7. No changes were needed.
diff -Nru mtpaint-3.40/debian/rules mtpaint-3.40/debian/rules
--- mtpaint-3.40/debian/rules   2016-04-07 10:22:59.0 +0100
+++ mtpaint-3.40/debian/rules   2020-11-03 22:58:01.0 +
@@ -2,6 +2,7 @@
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
+export DEB_CFLAGS_MAINT_APPEND = -fcommon
 %:
dh $@
 

Processed: mtpaint: diff for NMU version 3.40-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957571 + patch
Bug #957571 [src:mtpaint] mtpaint: ftbfs with GCC-10
Added tag(s) patch.
> tags 957571 + pending
Bug #957571 [src:mtpaint] mtpaint: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#973718: blueman: CVE-2020-15238

[Nobuhiro Iwamatsu]

Hi,

Sorry,.I will check this,If there is no problem, upload it.

Best regards,
  Nobuhiro

2020年11月4日(水) 6:17 Christopher Schramm :

>
> Hi Salvatore,
>
> 2.1.4-1 is waiting at https://mentors.debian.net/package/blueman/. I can
> add the CVE number and / or this bug to the changelog if you like.
>
> Unfortunately my sponsor Nobuhiro seems to be unavailable.
>
> Regards



--
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#957762: rgbpaint: diff for NMU version 0.8.7-6.1

[Sudip Mukherjee]

Control: tags 957762 + patch
Control: tags 957762 + pending
--

Dear maintainer,

I've prepared an NMU for rgbpaint (versioned as 0.8.7-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.

--
Regards
Sudip

diff -Nru rgbpaint-0.8.7/debian/changelog rgbpaint-0.8.7/debian/changelog
--- rgbpaint-0.8.7/debian/changelog 2016-04-06 15:04:37.0 +0100
+++ rgbpaint-0.8.7/debian/changelog 2020-11-03 22:46:50.0 +
@@ -1,3 +1,10 @@
+rgbpaint (0.8.7-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957762)
+
+ -- Sudip Mukherjee   Tue, 03 Nov 2020 22:46:50 
+
+
 rgbpaint (0.8.7-6) unstable; urgency=low
 
   * Set Standards-Version to 3.9.7, no changes.
diff -Nru rgbpaint-0.8.7/debian/rules rgbpaint-0.8.7/debian/rules
--- rgbpaint-0.8.7/debian/rules 2016-04-06 11:15:53.0 +0100
+++ rgbpaint-0.8.7/debian/rules 2020-11-03 22:34:54.0 +
@@ -4,6 +4,8 @@
 
 include /usr/share/dpkg/buildflags.mk
 
+export DEB_CFLAGS_MAINT_APPEND = -fcommon
+
 %:
dh $@
 

Processed: rgbpaint: diff for NMU version 0.8.7-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957762 + patch
Bug #957762 [src:rgbpaint] rgbpaint: ftbfs with GCC-10
Added tag(s) patch.
> tags 957762 + pending
Bug #957762 [src:rgbpaint] rgbpaint: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957319: marked as done (gtklp: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 22:48:19 +
with message-id 
and subject line Bug#957319: fixed in gtklp 1.3.1-1
has caused the Debian Bug report #957319,
regarding gtklp: 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.)


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

[...]
 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 text.h:27,
 from text.c:26:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
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 text.h:27,
 from text.c:26:
/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 text.h:27,
 from text.c:26:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -lX11 -o gtklp file.o general.o gtklp.o 
gtklp_functions.o gtklptab.o hpgl2.o image.o output.o ppd.o special.o text.o 
../libgtklp/libgtklp.a -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 
-lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 
-lglib-2.0 -lfontconfig -lfreetype  -lcups  -lX11 
libtool: link: gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -o gtklp file.o 
general.o gtklp.o gtklp_functions.o gtklptab.o hpgl2.o image.o output.o ppd.o 
special.o text.o  ../libgtklp/libgtklp.a -lgtk-x11-2.0 -lgdk-x11-2.0 
-lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lcups -lX11
/usr/bin/ld: general.o:./gtklp/../libgtklp/libgtklp.h:83: multiple definition 
of `progressBar'; file.o:./gtklp/../libgtklp/libgtklp.h:83: first defined here
/usr/bin/ld: 

Processed: Re: Bug#973622 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#973622: fixed in lumpy-sv 0.3.1+dfsg-3)

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.3.1+dfsg-3
Bug #973622 {Done: Andreas Tille } 
[lumpy-sv,lumpy-sv-examples] lumpy-sv,lumpy-sv-examples: both ship 
/usr/share/lumpy-sv/scripts/lumpyexpress.config
Marked as found in versions lumpy-sv/0.3.1+dfsg-3; no longer marked as fixed in 
versions lumpy-sv/0.3.1+dfsg-3 and reopened.

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

Bug#973622: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#973622: fixed in lumpy-sv 0.3.1+dfsg-3)

[Andreas Beckmann]

Control: found -1 0.3.1+dfsg-3

The problem persists.

Andreas

Bug#973723: libcharls-dev ships libcharls.so which is also in libdcmtk-dev

[Adrian Bunk]

Package: libcharls-dev
Version: 2.1.0+dfsg-6
Severity: serious

Unpacking libcharls-dev:amd64 (2.1.0+dfsg-6) over (2.1.0+dfsg-5) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-46o0f4/00-libcharls-dev_2.1.0+dfsg-6_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also in 
package libdcmtk-dev 3.6.4-2.1+b1

Bug#973701: [Pkg-utopia-maintainers] Bug#973701: network-manager: systemctl restart ModemManager.service wipes /etc/resolve.conf (almost) clean

[Cristian Ionescu-Idbohrn]

On Tue, 3 Nov 2020, Michael Biebl wrote:
> 
> This bug report doesn't contain any relevant information to be useful

Bisides the expected comment, what "relevant information" would I need 
to provide to make this bug report useful?  I'd be more than happy to 
provide it.


-- 
Cristian

Bug#973607: marked as done (libqglviewer: Depends upon removed package qt5-default)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 22:05:23 +
with message-id 
and subject line Bug#973607: fixed in libqglviewer 2.6.3+dfsg2-7
has caused the Debian Bug report #973607,
regarding libqglviewer: Depends upon removed package qt5-default
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.)


-- 
973607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libqglviewer
Version: 2.6.3+dfsg2-6
Severity: serious
Tags: patch
Justification: autopkgtest depends upon removed package
X-Debbugs-Cc: mity...@debian.org

Hi! Your package's autopkgtests depends upon qt5-default, which has been
removed in the last Qt upload (current transition going on).

It seems that sadly we did not find this fact earlier on when we where
preparing the upload.

The fix is simple: replace qt5-default with qtbase5-dev in your test's control
file.

Thanks, Lisandro.

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

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: libqglviewer
Source-Version: 2.6.3+dfsg2-7
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated libqglviewer 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: Tue, 03 Nov 2020 22:53:35 +0100
Source: libqglviewer
Architecture: source
Version: 2.6.3+dfsg2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 973607
Changes:
 libqglviewer (2.6.3+dfsg2-7) unstable; urgency=medium
 .
   [ Lisandro Damián Nicanor Pérez Meyer ]
   * [4658700] Replace qt5-default with qtbase5-dev for running autopkgtests.
 (Closes: #973607)
 .
   [ Anton Gladky ]
   * [17c550c] Add gitlab-ci.yml
   * [42a5a0d] Disable blhc and reprotest
   * [d518081] Fix for new qt5_5.15
   * [32b8f1b] Set debhelper-compat version in Build-Depends.
   * [06fea77] Update standards version to 4.5.0, no changes needed.
   * [e6a0c91] Use compat level 13
   * [75988ed] Update doc path install
Checksums-Sha1:
 782fbd471ebb7b7f123c35f3d3f9f9d37850a409 2362 libqglviewer_2.6.3+dfsg2-7.dsc
 d8397dda9e963fa3f808f8c9c19eea312d81d529 9220 
libqglviewer_2.6.3+dfsg2-7.debian.tar.xz
 50d6cc3f8f983682788a7a3c1d98247bfcbd1b01 10066 
libqglviewer_2.6.3+dfsg2-7_source.buildinfo
Checksums-Sha256:
 bc0629734e4ad60e628fd96492f61361cd4885d60ce1c2d06f7f365d79ceac47 2362 
libqglviewer_2.6.3+dfsg2-7.dsc
 2f440a9248e261e38ced1818a4de2469d6b7c89cf5e63f46915c0741757c4733 9220 
libqglviewer_2.6.3+dfsg2-7.debian.tar.xz
 7921ecbda302267869b1ba0c79dcaf0730ac78dbe776453b0e202c9b9e6a4353 10066 
libqglviewer_2.6.3+dfsg2-7_source.buildinfo
Files:
 a54a59725f8682b9b4ad56b86949b80d 2362 libs optional 
libqglviewer_2.6.3+dfsg2-7.dsc
 a70770af5435da4acef920941ceafe3b 9220 libs optional 
libqglviewer_2.6.3+dfsg2-7.debian.tar.xz
 2940fcca30145dd23f2194821f77448d 10066 libs optional 
libqglviewer_2.6.3+dfsg2-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+h0aoACgkQ0+Fzg8+n
/wZLAg//S3fmVB392Z7PxeAfXczWJAiqgABIr9qr7pRWBskACL/5xLr1WV4SoxTc
uVcejQaccDQ0D5KN7J3qt0PjeC54dIuf5CAqvVSel+R4Q4jfNqMPw/zA2wUy1fzB
XbaDGp9q0am5aOgvuKE4aFkvq9ZzaFp87D8GyLIzoLhhzPZVWEwZ/Zal+hTEQyoD
bpBsg289NRfLnWNaOCWt9l+/lh6kbEkiQikQRvN1GSJf+hbz1idDTAitd6oGpLSy
a1Uh6ERevzgaBr3sjEeEBvmVcu3yGUSv89JGfubmTdLbgIG72PFmUUNdlbIjjo3O
cLA40FMpXLLeUjRaxXSfWEmOJPsZxkxxZY2MgXwi4wd4le5TLiUay97yQ1V+beUp

Bug#971788: marked as done (libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1 version is unavailable)

[Andreas Beckmann]

On 11/3/20 9:24 PM, Atamert Ölçgen wrote:
> As of now I still can't upgrade to 450.80.*.
> https://packages.debian.org/buster-backports/libnvidia-rtcore also
> lists 450.66-1~bpo10+1 with the missing dependency. Am I missing something?

Please wait some hours until the package has been built and distributed
to the mirrors ;-)

Andreas

Bug#973417: AWS // Fixed by updating instance type

[TechAN]

Hi,

I add the same issue on AWS Xen powered instances. (t2, m4, c4, r4, ...). 
Updating instances to newer family powered by Nitro (t3, m5, c5, r5, ...) fixed 
the issue. 

Envoyé de mon iPhone

Processed: bug 973720 is forwarded to https://github.com/go-resty/resty/issues/386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 973720 https://github.com/go-resty/resty/issues/386
Bug #973720 [src:golang-github-go-resty-resty] FTBFS: 
TestClientRetryWaitCallbackSwitchToDefault fails on 32-bit systems
Set Bug forwarded-to-address to 'https://github.com/go-resty/resty/issues/386'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973721: libssreflect-coq: Depends: coq-8.12.0+4.08.1 but it is not installable

[Sebastian Ramacher]

Package: libssreflect-coq
Version: 1.11.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

$ apt install libssreflect-coq
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libssreflect-coq : Depends: coq-8.12.0+4.08.1 but it is not installable
E: Unable to correct problems, you have held broken packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#973718: blueman: CVE-2020-15238

[Christopher Schramm]

Hi Salvatore,

2.1.4-1 is waiting at https://mentors.debian.net/package/blueman/. I can 
add the CVE number and / or this bug to the changelog if you like.


Unfortunately my sponsor Nobuhiro seems to be unavailable.

Regards

Bug#973720: FTBFS: TestClientRetryWaitCallbackSwitchToDefault fails on 32-bit systems

[Alois Micard]

Source: golang-github-go-resty-resty
Version: 2.3.0-2
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source
X-Debbugs-Cc: al...@micard.lu

The test TestClientRetryWaitCallbackSwitchToDefault pass on 64-bit systems, but 
fail on 32-bit systems, such as i386, armhf.

Error log:

```
=== RUN   TestClientRetryWaitCallbackSwitchToDefault
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
resty_test.go:41: Method: GET
resty_test.go:42: Path: /set-retrywaittime-test
retry_test.go:477: Client has slept 1.329608 seconds before retry 3
--- FAIL: TestClientRetryWaitCallbackSwitchToDefault (9.74s)
```

See:
- 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/golang-github-go-resty-resty.html
- 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/golang-github-go-resty-resty.html


--
Aloïs Micard (creekorful) 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2

Bug#973718: blueman: CVE-2020-15238

[Salvatore Bonaccorso]

Source: blueman
Version: 2.1.3-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.0.8-1
Control: fixed -1 2.0.8-1+deb10u1

Hi,

The following vulnerability was published for blueman.

CVE-2020-15238[0]:
| Blueman is a GTK+ Bluetooth Manager. In Blueman before 2.1.4, the
| DhcpClient method of the D-Bus interface to blueman-mechanism is prone
| to an argument injection vulnerability. The impact highly depends on
| the system configuration. If Polkit-1 is disabled and for versions
| lower than 2.0.6, any local user can possibly exploit this. If
| Polkit-1 is enabled for version 2.0.6 and later, a possible attacker
| needs to be allowed to use the `org.blueman.dhcp.client` action. That
| is limited to users in the wheel group in the shipped rules file that
| do have the privileges anyway. On systems with ISC DHCP client
| (dhclient), attackers can pass arguments to `ip link` with the
| interface name that can e.g. be used to bring down an interface or add
| an arbitrary XDP/BPF program. On systems with dhcpcd and without ISC
| DHCP client, attackers can even run arbitrary scripts by passing
| `-c/path/to/script` as an interface name. Patches are included in
| 2.1.4 and master that change the DhcpClient D-Bus method(s) to accept
| BlueZ network object paths instead of network interface names. A
| backport to 2.0(.8) is also available. As a workaround, make sure that
| Polkit-1-support is enabled and limit privileges for the
| `org.blueman.dhcp.client` action to users that are able to run
| arbitrary commands as root anyway in
| /usr/share/polkit-1/rules.d/blueman.rules.


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-15238
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15238
[1] 
https://github.com/blueman-project/blueman/security/advisories/GHSA-jpc9-mgw6-2xwx
[2] https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1897287
[3] 
https://github.com/blueman-project/blueman/commit/02161d60e8e311b08fb18254615259085fcd668

Regards,
Salvatore

Processed: blueman: CVE-2020-15238

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0.8-1
Bug #973718 [src:blueman] blueman: CVE-2020-15238
Marked as found in versions blueman/2.0.8-1.
> fixed -1 2.0.8-1+deb10u1
Bug #973718 [src:blueman] blueman: CVE-2020-15238
Marked as fixed in versions blueman/2.0.8-1+deb10u1.

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

Bug#973539: marked as done (qcustomplot autopkgtest fails: stderr: CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message))

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 21:03:47 +
with message-id 
and subject line Bug#973539: fixed in qcustomplot 2.0.1+dfsg1-3
has caused the Debian Bug report #973539,
regarding qcustomplot autopkgtest fails: stderr: CMake Warning (dev) at 
/usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message)
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.)


-- 
973539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qcustomplot
Version: 2.0.1+dfsg1-2
Severity: serious
User: debian-qt-...@lists.debian.org
Usertags: qt5.15
Control: block 972278 by -1

Dear Maintainer,

qcustomplot autopkgtest failed when run against Qt 5.15 from unstable:

https://ci.debian.net/data/autopkgtest/testing/amd64/q/qcustomplot/7873285/log.gz

All 5 tests are failing because the following message is printed to stderr:

  CMake Warning (dev) at 
/usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:44 (message):
qt5_use_modules is not part of the official API, and might be removed in Qt 
6.
  Call Stack (most recent call first):
/usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreMacros.cmake:431 
(_qt5_warn_deprecated)
CMakeLists.txt:17 (QT5_USE_MODULES)
  This warning is for project developers.  Use -Wno-dev to suppress it.

The CMakeLists.txt files are generated inside the autopkgtests.
But debian/patches/01_Add_CMakeLists.patch should be probably also updated.

The official Qt CMake API is documented here:

https://doc.qt.io/qt-5/cmake-get-started.html

In addition, stderr of buildtest-plot test also contains some compiler
warnings:

  /tmp/tmp.1E2C1tcj0m/src/mainwindow.cpp: In member function ‘void 
MainWindow::setupStyledDemo(QCustomPlot*)’:
  /tmp/tmp.1E2C1tcj0m/src/mainwindow.cpp:1058:80: warning: ‘int qrand()’ is 
deprecated: use QRandomGenerator instead [-Wdeprecated-declarations]
   1058 | y3[i] = 
0.05+3*(0.5+qCos(x3[i]*x3[i]*0.2+2)*0.5)/(double)(x3[i]+0.7)+qrand()/(double)RAND_MAX*0.01;
|   
 ^
  ...

See the log for the complete stderr contents.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qcustomplot
Source-Version: 2.0.1+dfsg1-3
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated qcustomplot 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: Tue, 03 Nov 2020 21:41:27 +0100
Source: qcustomplot
Architecture: source
Version: 2.0.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 973539
Changes:
 qcustomplot (2.0.1+dfsg1-3) unstable; urgency=medium
 .
   [ Anton Gladky ]
   * [0eda999] Update autopkgtests. (Closes: #973539)
   * [8dfed02] Convert patches to gbp pq
   * [e14754c] Wrap long lines in changelog entries: 2.0.1+dfsg1-2.
   * [2070ece] Apply cme fix dpkg
   * [16bc3e6] Refresh cmakelist-patch
 .
   [ Dmitry Shachnev ]
   * [15f9a6a] Fix Qt 5.15 deprecation warnings
   * [148cdec] Update debian/libqcustomplot-doc.doc-base to fix broken 
references.
Checksums-Sha1:
 c5ccc77a796241b8dd98cdf164af096a119d1b91 2232 qcustomplot_2.0.1+dfsg1-3.dsc
 15245cb1639c37dc66e34a62a2ff297037f3d0de 6656 
qcustomplot_2.0.1+dfsg1-3.debian.tar.xz
 b09d985388bd73360745a5135dc007ce23a9a28e 10512 
qcustomplot_2.0.1+dfsg1-3_source.buildinfo
Checksums-Sha256:
 9fea9c2f2c4d471cacaff9f1fff33d02dca021667388a8c4a60c5bcbf706a1d0 2232 
qcustomplot_2.0.1+dfsg1-3.dsc
 ebc46039f1b19cd35531e93ce792ed6436b8b3addec9e9b61160a95c0270dbc1 6656 
qcustomplot_2.0.1+dfsg1-3.debian.tar.xz
 6606ef4a150fe093188807c12a8575f381f8f20d4d7da9372a656a6e6d772cad 10512 
qcustomplot_2.0.1+dfsg1-3_source.buildinfo
Files:
 24e0f833613ca1d12235ec4a518611b4 2232 libs optional 
qcustomplot_2.0.1+dfsg1-3.dsc
 28016d9ac4ebe744b5234ea89285ce6c 6656 libs optional 

Processed: genshi: incompatible with Python 3.9

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 972531 973014
Bug #972531 [src:genshi] genshi: incompatible with Python 3.9
Bug #972531 [src:genshi] genshi: incompatible with Python 3.9
Added tag(s) bullseye and sid.
Bug #973014 [src:genshi] genshi's autopkg tests are failing with python3.9
Severity set to 'normal' from 'serious'
Added tag(s) upstream.
Merged 972531 973014
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972531
973014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:python-livereload: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.6.3-1
Bug #973716 [src:python-livereload] src:python-livereload: fails to migrate to 
testing for too long: autopkgtest regression
Marked as fixed in versions python-livereload/2.6.3-1.
Bug #973716 [src:python-livereload] src:python-livereload: fails to migrate to 
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 970495
Bug #973716 {Done: Paul Gevers } [src:python-livereload] 
src:python-livereload: fails to migrate to testing for too long: autopkgtest 
regression
973716 was not blocked by any bugs.
973716 was not blocking any bugs.
Added blocking bug(s) of 973716: 970495

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

Bug#973716: src:python-livereload: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: python-livereload
Version: 2.6.1-3
Severity: serious
Control: close -1 2.6.3-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 970495

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-livereload in its current version in unstable has been trying
to migrate for 60 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-livereload




signature.asc
Description: OpenPGP digital signature

Bug#972802: [Pkg-rust-maintainers] Bug#972802: rust-webpki-roots: duplicates ca-certificates, remove from Debian?

[kpcyrd]

On Sat, Oct 24, 2020 at 11:50:14AM +0800, Paul Wise wrote:
> > This is a very non-trivial downstream patch though, the project I'm
> > trying to package runs in a sandbox and loading certificates from disk
> > at runtime is not possible without redesigning some things.
> 
> One option to solve this would be to have src:rust-webpki-roots provide
> webpki-roots-build containing build.py and then have ca-certificates
> build-dep on webpki-roots, run build.py and build a binary package
> containing the generated rust code. That seems a bit ick though.
> 
> Is there any chance of webpki/rustls upstream switching from embedding
> to runtime loading of certs like other TLS stacks do?

It's more complicated than that, there's rustls-native-certs to use the
local certificate store, but the patch would be so invasive that debian
would effectively maintain a fork. At the time of writing webpki-roots
has 85 reverse dependencies on crates.io, while rustls-native-certs has
13.

rustls-native-certs compares itself to webpki-roots in the readme, I
think this bit is interesting:

> Cons:
> [...]
> - The quality of the ca-certificates package on debian-based Linux
> distributions is poor. At the time of writing, this ships many
> certificates not included in the Mozilla set, either because they
> failed an audit and were withdrawn[1] or were removed for
> mississuance[2].

[1]: https://bugs.mozilla.org/show_bug.cgi?id=1448506
[2]: https://bugs.mozilla.org/show_bug.cgi?id=1552374

Bug#971788: marked as done (libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1 version is unavailable)

[Atamert Ölçgen]

Hi Andreas,
Thanks a lot for looking into this.

As of now I still can't upgrade to 450.80.*.
https://packages.debian.org/buster-backports/libnvidia-rtcore also
lists 450.66-1~bpo10+1 with the missing dependency. Am I missing something?

On Tue, Nov 3, 2020 at 11:51 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Your message dated Tue, 3 Nov 2020 09:46:59 +0100
> with message-id 
> and subject line Re: Bug#971788: libnvidia-rtcore: Broken dependnecies:
> dependant libgcc-s1 version is unavailable
> has caused the Debian Bug report #971788,
> regarding libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1
> version is unavailable
> 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.)
>
>
> --
> 971788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971788
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Aidan Gauland 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Wed, 7 Oct 2020 22:00:34 +1300
> Subject: libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1
> version is unavailable
> Package: libnvidia-rtcore
> Version: 450.66-1~bpo10+1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The current buster-backports version of libnvidia-rtcore depends upon
> libgcc-s1 >= 4.2 which is unavailable in buster or buster-backports,
> making this package impossible to install.
>
> It looks like either gcc-10 needs to be backported to buster, or
> libnvidia-rtcore needs to be ported to a version of gcc available in
> buster.
>
> Regards,
> Aidan Gauland
>
>
>
> -- System Information:
> Debian Release: 10.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/32 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_NZ.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 libnvidia-rtcore depends on:
> ii  libc6  2.28-10
> pn  libgcc-s1  
> ii  libgcc11:8.3.0-6
>
> libnvidia-rtcore recommends no packages.
>
> libnvidia-rtcore suggests no packages.
>
>
>
> -- Forwarded message --
> From: Andreas Beckmann 
> To: Aidan Gauland , 971788-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 3 Nov 2020 09:46:59 +0100
> Subject: Re: Bug#971788: libnvidia-rtcore: Broken dependnecies: dependant
> libgcc-s1 version is unavailable
> On 10/7/20 11:00 AM, Aidan Gauland wrote:
> > The current buster-backports version of libnvidia-rtcore depends upon
> > libgcc-s1 >= 4.2 which is unavailable in buster or buster-backports,
> > making this package impossible to install.
>
> The package was built in sid instead of buster by accident and picked up
> that wrong dependency.
> This is fixed with new version just uploaded to buster-backports.
>
> Andreas



-- 
Kind Regards,
Atamert Ölçgen

◻◼◻
◻◻◼
◼◼◼

www.muhuk.com

Processed: closing 964652

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 964660
Bug #964660 [wnpp] ITP: google-auth-java: FTBFS: build-dependency not 
installable: libgrpc-java
Marked Bug as done
> close 964625
Bug #964625 [src:google-api-client-java] google-api-client-java: FTBFS: Failed 
to execute goal on project google-api-client: Could not resolve dependencies 
for project com.google.api-client:google-api-client:jar:1.27.1: Cannot access 
central (https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.grpc:grpc-context:jar:debian has not been downloaded from it before. -> 
[Help 1]
Marked Bug as done
> close 964601
Bug #964601 [src:google-oauth-client-java] google-oauth-client-java: FTBFS: 
[ERROR] Failed to execute goal on project google-oauth-client: Could not 
resolve dependencies for project 
com.google.oauth-client:google-oauth-client:jar:1.27.0: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.grpc:grpc-context:jar:debian has not been downloaded from it before. -> 
[Help 1]
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
964601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964601
964625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964625
964660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

[tobias]

i upgraded myself today to 4.19.0-12 (or 4.19.152-1 according to 
upstream version numbers)

no issue yet.

this blog contains some interesting info: http://blog.pi3.com.pl/?p=720
both CVE's mentioned are fixed now in debian
https://security-tracker.debian.org/tracker/CVE-2020-25220
https://security-tracker.debian.org/tracker/CVE-2020-14356

so i think it looks good.

Tobias.

Bug#973701: [Pkg-utopia-maintainers] Bug#973701: network-manager: 'systemctl restart ModemManager.service' wipes /etc/resolve.conf (almost) clean

[Michael Biebl]

Control: tags -1 + moreinfo

Am 03.11.20 um 16:45 schrieb Cristian Ionescu-Idbohrn:

Package: network-manager
Version: 1.27.91-1
Severity: grave

/etc/resolve.conf includes the expected configuration (WRT
nameservers) on bootup.

After upgrading network-manager and restarting it, /etc/resolve.conf
(which is a symlink to /run/NetworkManager/resolv.conf) is basically
wiped out.  Includes only this:

# Generated by NetworkManager

Rebooting brings things to normal.  Still, this isn't wintendo.  I'd
expect better.

There are some workarounds (suggested in some other bug reports) that
bring the system back to an usable state, but far away from perfect
(dhclient wlan0).  Duplicated home router nameserver addresses in
/etc/resolv.conf:

nameserver 192.168.0.1
nameserver 192.168.0.1

which is not what my configuration is.


This bug report doesn't contain any relevant information to be useful

Processed: Re: [Pkg-utopia-maintainers] Bug#973701: network-manager: 'systemctl restart ModemManager.service' wipes /etc/resolve.conf (almost) clean

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #973701 [network-manager] network-manager: 'systemctl restart 
ModemManager.service' wipes /etc/resolve.conf (almost) clean
Added tag(s) moreinfo.

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

Bug#957439: libforms: ftbfs with GCC-10

[Peter S Galbraith]

Thanks for your upload. Real life took over again. :-(

Want to take over the package? :-)

Peter

> On Tue, 2020-08-25 at 17:30 -0400, Peter S Galbraith wrote:
> 
> > I am on vacation so *should* have time to look into this soonish.
> 
> Did you get a chance to look at the libforms FTBFS with GCC-10?
> 
> -- 
> bye,
> pabs
> 
> https://wiki.debian.org/PaulWise

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

[Boyuan Yang]

Package: fwupd-amd64-signed
Severity: grave
Version: 1.4.6+2
X-Debbugs-CC: 93...@debian.org mario.limoncie...@dell.com

Dear EFI Team,

Package fwupd-amd64-signed currently cannot be installed on Debian
Unstable/Sid. It depends on fwupd (= 1.4.6-2) while Sid only has fwupd
(= 1.4.6-2+b1).

It seems obvious that such dependency relationship made fwupd/fwupd-
amd64-signed not binNMU-friendly. Please consider setting a version
range to allow binNMU-ed package to satisfy the dependency
relationship.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#973178: marked as done (python-streamz: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 19:03:47 +
with message-id 
and subject line Bug#973178: fixed in python-streamz 0.6.1-1
has caused the Debian Bug report #973178,
regarding python-streamz: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
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.)


-- 
973178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-streamz
Version: 0.6.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-streamz
> dpkg-buildpackage: info: source version 0.6.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nilesh Patra 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_streamz/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_streamz/build' (and 
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-streamz using existing 
> ./python-streamz_0.6.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building python-streamz in 
> python-streamz_0.6.0-1.debian.tar.xz
> dpkg-source: info: building python-streamz in python-streamz_0.6.0-1.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/core.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/dask.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/compatibility.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/sources.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/orderedweakset.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/graph.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/utils_test.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/batch.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/collection.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> copying streamz/utils.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz
> creating 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/dataframe
> copying streamz/dataframe/core.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/dataframe
> copying streamz/dataframe/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/dataframe
> copying streamz/dataframe/aggregations.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/dataframe
> copying streamz/dataframe/utils.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/dataframe
> creating /<>/.pybuild/cpython3_3.9_streamz/build/streamz/tests
> copying streamz/tests/test_kafka.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/tests
> copying streamz/tests/test_graph.py -> 
> /<>/.pybuild/cpython3_3.9_streamz/build/streamz/tests
> copying streamz/tests/__init__.py -> 
> 

Bug#973625: marked as done (python3-nanostat: ships /usr/lib/python3/dist-packages/scripts/test.sh)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 19:03:40 +
with message-id 
and subject line Bug#973625: fixed in python-nanoget 1.12.2-4
has caused the Debian Bug report #973625,
regarding python3-nanostat: ships /usr/lib/python3/dist-packages/scripts/test.sh
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.)


-- 
973625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-nanostat
Version: 1.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

your package ships a file with a very generic name which has now caused a
file conflict with other packages doing the same mistake.

cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: python-nanoget
Source-Version: 1.12.2-4
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-nanoget 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: Tue, 03 Nov 2020 19:37:33 +0100
Source: python-nanoget
Architecture: source
Version: 1.12.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973625
Changes:
 python-nanoget (1.12.2-4) unstable; urgency=medium
 .
   * Move test scripts to examples
 Closes: #973625
Checksums-Sha1:
 d19095280d616877ce9c2512a6d3f8e410f221b5 2217 python-nanoget_1.12.2-4.dsc
 8e55fd68f4eef25c69ba86e4ea11ea1ffc21eb1d 26143548 
python-nanoget_1.12.2-4.debian.tar.xz
 d4a12feb079e5379c79b147fbfef24d98c3fa618 8207 
python-nanoget_1.12.2-4_amd64.buildinfo
Checksums-Sha256:
 ec840196109cfdbd4a5f53c3f991faf517a018d808f49071614b574fee2d8447 2217 
python-nanoget_1.12.2-4.dsc
 98ee1e134531855e34383e700f5463c0f4ec2daeaea843b43d42d7fb1b3688d2 26143548 
python-nanoget_1.12.2-4.debian.tar.xz
 21564fb35fb0b15274eedf0e049444ecc96146758be0ff7a765d77fcb99bd629 8207 
python-nanoget_1.12.2-4_amd64.buildinfo
Files:
 869e823f9effd1935c2bfdb475337f13 2217 science optional 
python-nanoget_1.12.2-4.dsc
 174debc6a5ca59cb0f8025aa42b59062 26143548 science optional 
python-nanoget_1.12.2-4.debian.tar.xz
 8c0414d90128322d7d474163dd12e573 8207 science optional 
python-nanoget_1.12.2-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+hpeARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE5Bg/9EXLiNgYHReD9mB9B8h8qu4O3tWhVXB/5
2OJWwE/MkwGiDdIbujZkdJUU8nqZhX6JU+k0/czQKQlve4Nq1vhZXN2TPOBnIjw8
qQ6B9SLY/epIzOxDjlbTEx/gKxklSztjbeoW1bGaKUJT8RBopkf9Q06pIdiFaLGw
W7tIAMZFWl5vkpeiv/iu3y3TTEul96i4hQC4vJkCN4GOh6ntMB/Zaaw9STH9OFfw
zeMwgORT++O5SwSTXYZ9klZQD6+0yIoNW3cOpFIitPADJy/ygoKsYmecv0C2mWyR
eOSwvxKtSRcUCle01yEaTM3av1tilywkFXIMxjiU9SzNHUZyrACWuQd6/wS8mvJx
MOHEAxJGQzEXAccunEXd5nVbO7CSCQyQ7/ncD+WWoTp3ejbsyO7ECQr5gw5ttNmx
v8KRZJzmVBDV5rim4l2GC14mS+da+zDDL69BC59aYqjyrQnPX81jqAz6KzxLk0H5
72+1yCLB3ZngaWNEwDsW1vzWK1nCtt1MxjgD0QOwkmbbuc5xdbCX1r2j23xRpElK
bGQrX5JdROlgFrjBPqlywgCChMMVtTuNRQ3WZbEUug7ItH2TISIlTKyVHPQFLdnn
J3Nk+FWIUjlBNlDXyf80lNAGE6yQZBHvGBnMz6lYn/5Ze7EdEXGHVrAzFDEbJ0vP
JGE5cIm/DL8=
=2sh9
-END PGP SIGNATURE End Message ---

Bug#973543: nvidia-cuda-toolkit: CVE-2020-5991

[Andreas Beckmann]

Control: found -1 10.0.130-1

On 11/1/20 3:51 PM, Salvatore Bonaccorso wrote:
> The following vulnerability was published for nvidia-cuda-toolkit.
> 
> I have no further details apart what is in [1], which seem to indicate
> Operating System Windows only. Do you find more information on that?

That's also all I could find so far. But I can't really imagine that the
NVJPEG library has windows specific code ... (unlike some driver
components). So working towards 11.1...


Andreas

Processed: Re: Bug#973543: nvidia-cuda-toolkit: CVE-2020-5991

[Debian Bug Tracking System]

Processing control commands:

> found -1 10.0.130-1
Bug #973543 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2020-5991
Marked as found in versions nvidia-cuda-toolkit/10.0.130-1.

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

Bug#936241: broctl: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Mon, Oct 14, 2019 at 07:23:54PM -0400, Scott Kitterman wrote:
> It looks like broctl is replaced by zeekctl upstream:
> 
> https://github.com/zeek/zeekctl
> 
> It does support python3, so it'd be great to see this updated to the newer 
> version.

zeekctl is in experimental for a few months, can broctl be removed now?

Cheers,
Moritz

Bug#973714: Depends on argyll which is going away

[Moritz Muehlenhoff]

Package: displaycal
Severity: serious

argyll is filed for removal from the archive (#966416), but displaycal
depends on it.

Cheers,
Moritz

Bug#973712: Depends on argyll which is going away

[Moritz Muehlenhoff]

Package: colord-sensor-argyll
Severity: serious

argyll is filed for removal from the archive (#966416), but colord-sensor-argyll
depends on it.

Cheers,
Moritz

Bug#973001: marked as done (seqan3: autopackage tests need updating for new googletest)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 18:03:36 +
with message-id 
and subject line Bug#973001: fixed in seqan3 3.0.2+ds-4
has caused the Debian Bug report #973001,
regarding seqan3: autopackage tests need updating for new googletest
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.)


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

Dear Maintainer,

The autopkg tests need to be updated for the new googletest.  There are 
failures such as

/tmp/autopkgtest-lxc.u2mymoo7/downtmp/autopkgtest_tmp/unit/alphabet/cigar/../alphabet_test_template.hpp:86:
 Failure
Type parameterized test suite alphabet is defined via 
REGISTER_TYPED_TEST_SUITE_P, but never instantiated via 
INSTANTIATE_TYPED_TEST_SUITE_P. None of the test cases will run.

Ideally, TYPED_TEST_P definitions should only ever be included as part of 
binaries that intend to use them. (As opposed to, for example, being placed in 
a library that may be linked in to get other utilities.)



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

Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: seqan3
Source-Version: 3.0.2+ds-4
Done: cru...@debian.org (Michael R. Crusoe)

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated seqan3 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: Tue, 03 Nov 2020 17:38:50 +0100
Source: seqan3
Architecture: source
Version: 3.0.2+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 973001
Changes:
 seqan3 (3.0.2+ds-4) unstable; urgency=medium
 .
   * Add patches to cope with googletest 1.10.0.20201025-1. Closes: #973001
   * Drop down to g++-9 for testing due to an ICE with g++-10 10.2.0-16:
 https://bugs.debian.org/973698
   * Fix for missing changelog
Checksums-Sha1:
 c4fe4045c1541bc5f52f9f9ccdab4f2a970a7831 2505 seqan3_3.0.2+ds-4.dsc
 43077f6b8521a0fb400f3307aead223d491d20c0 10584 seqan3_3.0.2+ds-4.debian.tar.xz
 beae265d70af0a1df7f6b305a88a5600f63e287b 13426 
seqan3_3.0.2+ds-4_source.buildinfo
Checksums-Sha256:
 ddeb83bcbcb7ffec8ffd5d675664785d0320124b6ade6a33bcd65d13f588c996 2505 
seqan3_3.0.2+ds-4.dsc
 e6610895edadb7de2e00e4e3141c24abeac208835d8df970217797e2bb8b694b 10584 
seqan3_3.0.2+ds-4.debian.tar.xz
 29babe3e952e309628e111af46efc2b4d083517c0217145ab2e28570985bac14 13426 
seqan3_3.0.2+ds-4_source.buildinfo
Files:
 3654b183d6e5c0552ad3abacabfa6280 2505 science optional seqan3_3.0.2+ds-4.dsc
 d73c035b798a0a672d007b69ce38a717 10584 science optional 
seqan3_3.0.2+ds-4.debian.tar.xz
 05e17937c2b34d812b94a8ea027d59cd 13426 science optional 
seqan3_3.0.2+ds-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl+hl9gACgkQPCZ2P2xn
5uJ56BAAxTDsfUpg1nQ6p18coAQrh4w3ydWoFDg7/ePAF4SdLu45cDW237pcUGPU
0F35g+nc+AfJtueYlhBurZxYs+JIkVq9izRZmuU7LXlK9iGWIULpAMIWvYNXeYqr
ZggOa7Y3LW7iAhK7M1c9+kizYZXv54c0RRuEWgiWs3kpGtlYRoABybgvkWHB7yeT
a8/jeGsYjgFRYViKwQMkRf2o34zjqxWTX2poX/wl74qwV1orLtvRXNwaT2XB6Tz0
kyCtTISRclYnwRJZEGEddSx98pxG3uu8k5UOGN+Xn0l5JEE2DLGF1BXpC8D3azFd
vUlVXCu9rIPHq+pGsuzW113910IcwF40VJUNrAJItQ7GjIesEAtVhenoFT888Sar
wdtdjKk+7MibRvU3rsDQNhhjY80kJqbdultHuTKAfRinhzZAaBSg8AyzR0tGkwo3
HmvEw/rO6THUFfRV7MnknF+sv5+uLUsyDMEuTZ7P/q5kEqeM0uKND0gsb7k/CFJG
SP4x5de4QAt2C4qld9BZvVvadjEi7OPwjYI59JcpvOS97So2JKuhsNv5x2I/4j7k
iKw43EDi30+4Ojb3GkNPCnUZ7LewzcGiiBjjlQKMAmoRKBHmRb4ZjIRWFX1PAdXU

Processed: remove package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 972802 RM: rust-webpki-roots -- ROM; duplicates ca-certificates
Bug #972802 [src:rust-webpki-roots] rust-webpki-roots: duplicates 
ca-certificates, remove from Debian?
Changed Bug title to 'RM: rust-webpki-roots -- ROM; duplicates ca-certificates' 
from 'rust-webpki-roots: duplicates ca-certificates, remove from Debian?'.
> reassign 972802 ftp.debian.org
Bug #972802 [src:rust-webpki-roots] RM: rust-webpki-roots -- ROM; duplicates 
ca-certificates
Bug reassigned from package 'src:rust-webpki-roots' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #972802 to the same values 
previously set
Ignoring request to alter fixed versions of bug #972802 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
972802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973118: marked as done (kgb-bot: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 17:48:41 +
with message-id 
and subject line Bug#973118: fixed in kgb-bot 1.58-1
has caused the Debian Bug report #973118,
regarding kgb-bot: FTBFS: dh_auto_test: error: perl Build test --verbose 1 
returned exit code 255
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.)


-- 
973118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kgb-bot
Version: 1.57-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>'
> LANG=bg_BG.utf8 LC_ALL=bg_BG.utf8 dh_auto_test
>   perl Build test --verbose 1
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB.pm
> # blib/lib/App/KGB.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/WWW/Shorten/Debli.pm
> # blib/lib/WWW/Shorten/Debli.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/API.pm
> # blib/lib/App/KGB/API.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/Change.pm
> # blib/lib/App/KGB/Change.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/Client.pm
> # blib/lib/App/KGB/Client.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/Commit.pm
> # blib/lib/App/KGB/Commit.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/Painter.pm
> # blib/lib/App/KGB/Painter.pm syntax OK
> # Executing: "/usr/bin/perl" "-Iblib/lib" "-I/<>/blib/lib" 
> "-I/<>/blib/arch" "-Iprivinc" "-I/etc/perl" 
> "-I/usr/local/lib/x86_64-linux-gnu/perl/5.30.3" 
> "-I/usr/local/share/perl/5.30.3" "-I/usr/lib/x86_64-linux-gnu/perl5/5.30" 
> "-I/usr/share/perl5" "-I/usr/lib/x86_64-linux-gnu/perl-base" 
> "-I/usr/lib/x86_64-linux-gnu/perl/5.30" "-I/usr/share/perl/5.30" 
> "-I/usr/local/lib/site_perl" "-I." -c blib/lib/App/KGB/Client/CVS.pm

Bug#973208: marked as done (pytest-mpi: FTBFS: ModuleNotFoundError: No module named 'pytest_mpi')

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 17:33:45 +
with message-id 
and subject line Bug#973208: fixed in pytest-mpi 0.4-2
has caused the Debian Bug report #973208,
regarding pytest-mpi: FTBFS: ModuleNotFoundError: No module named 'pytest_mpi'
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.)


-- 
973208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pytest-mpi
Version: 0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pytest-mpi/build/pytest_mpi
> copying src/pytest_mpi/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pytest-mpi/build/pytest_mpi
> copying src/pytest_mpi/_version.py -> 
> /<>/.pybuild/cpython3_3.9_pytest-mpi/build/pytest_mpi
> UPDATING 
> /<>/.pybuild/cpython3_3.9_pytest-mpi/build/pytest_mpi/_version.py
> set 
> /<>/.pybuild/cpython3_3.9_pytest-mpi/build/pytest_mpi/_version.py
>  to '0+unknown'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_pytest-mpi/build/pytest_mpi
> copying src/pytest_mpi/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_pytest-mpi/build/pytest_mpi
> copying src/pytest_mpi/_version.py -> 
> /<>/.pybuild/cpython3_3.8_pytest-mpi/build/pytest_mpi
> UPDATING 
> /<>/.pybuild/cpython3_3.8_pytest-mpi/build/pytest_mpi/_version.py
> set 
> /<>/.pybuild/cpython3_3.8_pytest-mpi/build/pytest_mpi/_version.py
>  to '0+unknown'
> PYTHONPATH=`pybuild --print {build_dir}` http_proxy='127.0.0.1:9' 
> sphinx-build -N -bhtmldocs/ build/html # HTML generator
> Running Sphinx v3.2.1
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 319, in 
> eval_config_file
> execfile_(filename, namespace)
>   File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 89, in 
> execfile_
> exec(code, _globals)
>   File "/<>/docs/conf.py", line 29, in 
> import pytest_mpi
> ModuleNotFoundError: No module named 'pytest_mpi'
> 
> make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/pytest-mpi_0.4-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: pytest-mpi
Source-Version: 0.4-2
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pytest-mpi 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, 04 Nov 2020 01:04:33 +0800
Source: pytest-mpi
Architecture: source
Version: 0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Drew Parsons 
Closes: 973208
Changes:
 pytest-mpi (0.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Drew Parsons ]
   * build docs against default python version. Closes: #973208.
Checksums-Sha1:
 9538a04a50f66599deb41f2d370e3f0ce59c696e 2277 pytest-mpi_0.4-2.dsc
 0237b1cb1671d8658b1ba028d240b882723b4be2 3252 pytest-mpi_0.4-2.debian.tar.xz
Checksums-Sha256:
 

Processed: tagging 915837, tagging 966251, tagging 969823, tagging 969797, tagging 969815, tagging 969938 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 915837 + buster bullseye sid
Bug #915837 [camping] camping: FTBFS with rails 5.2
Added tag(s) buster, bullseye, and sid.
> tags 966251 + sid bullseye
Bug #966251 {Done: Xavier Guimard } [src:node-streamtest] 
node-streamtest: autopkgtest failure with nodejs 12
Added tag(s) sid and bullseye.
> tags 969823 + sid bullseye
Bug #969823 {Done: Fabio Augusto De Muzio Tobich } 
[src:etktab] etktab: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969797 + sid bullseye
Bug #969797 {Done: Sudip Mukherjee } 
[src:altermime] altermime: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969815 + sid bullseye
Bug #969815 {Done: Giovani Augusto Ferreira } [src:comprez] 
comprez: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969938 + sid bullseye
Bug #969938 [debirf] debirf: bullseye: switch from /updates to -security
Added tag(s) bullseye and sid.
> tags 969803 + sid bullseye
Bug #969803 {Done: Noah Meyerhans } [src:awscli] awscli: 
autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969845 + sid bullseye
Bug #969845 {Done: Giovani Augusto Ferreira } 
[src:missidentify] missidentify: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969848 + sid bullseye
Bug #969848 {Done: Giovani Augusto Ferreira } 
[src:myrescue] myrescue: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969852 + sid bullseye
Bug #969852 {Done: Giovani Augusto Ferreira } [src:pompem] 
pompem: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969812 + sid bullseye
Bug #969812 {Done: Sudip Mukherjee } [src:cldump] 
cldump: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969863 + sid bullseye
Bug #969863 {Done: Giovani Augusto Ferreira } 
[src:rifiuti2] rifiuti2: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969842 + sid bullseye
Bug #969842 {Done: Sudip Mukherjee } 
[src:mailcheck] mailcheck: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969849 + sid bullseye
Bug #969849 {Done: Sudip Mukherjee } [src:ncap] 
ncap: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969819 + sid bullseye
Bug #969819 {Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= } 
[src:dmidecode] dmidecode: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969834 + sid bullseye
Bug #969834 {Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= } 
[src:ipmitool] ipmitool: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969795 + sid bullseye
Bug #969795 {Done: Fabio Augusto De Muzio Tobich } 
[src:2vcard] 2vcard: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969830 + sid bullseye
Bug #969830 {Done: Thomas Goirand } [src:git-review] 
git-review: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969843 + sid bullseye
Bug #969843 {Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= 
} [src:makebootfat] makebootfat: autopkgtest should be 
marked superficial
Added tag(s) sid and bullseye.
> tags 969867 + sid bullseye
Bug #969867 {Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= } 
[src:sane-frontends] sane-frontends: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969808 + sid bullseye
Bug #969808 {Done: Adam Borowski } [src:cfourcc] cfourcc: 
autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 877740 + sid bullseye
Bug #877740 [gedit-latex-plugin] gedit-latex-plugin: Depends: gvfs-bin, which 
contains only deprecated tools
Added tag(s) bullseye and sid.
> tags 969826 + sid bullseye
Bug #969826 {Done: Joao Eriberto Mota Filho } [src:flpsed] 
flpsed: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969811 + sid bullseye
Bug #969811 {Done: Joao Eriberto Mota Filho } 
[src:changetrack] changetrack: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969832 + sid bullseye
Bug #969832 {Done: Joao Eriberto Mota Filho } [src:gox] 
gox: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969840 + sid bullseye
Bug #969840 {Done: Joao Eriberto Mota Filho } [src:lxmms2] 
lxmms2: autopkgtest should be marked superficial
Added tag(s) bullseye and sid.
> tags 969817 + sid bullseye
Bug #969817 {Done: Joao Eriberto Mota Filho } 
[src:diffmon] diffmon: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969881 + sid bullseye
Bug #969881 {Done: Doug Torrance } [src:wmforecast] 
wmforecast: autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969882 + sid bullseye
Bug #969882 {Done: Doug Torrance } [src:wmxres] wmxres: 
autopkgtest should be marked superficial
Added tag(s) sid and bullseye.
> tags 969837 + sid bullseye
Bug #969837 {Done: 

Processed: found 960688 in 1.4.6-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 960688 1.4.6-2
Bug #960688 [fwupd] fwupd: missing Breaks: fwupdate (<< 12-7)
Marked as found in versions fwupd/1.4.6-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
960688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: libjogl2-java, build-depends no longer satisfiable on 32-bit architectures.

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 972478 serious
Bug #972478 [libjogl2-java] libjogl2-java, build-depends no longer satisfiable 
on 32-bit architectures.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973703: cantor-backend-scilab: dependency no longer available on i386 and armhf

[peter green]

Package: cantor-backend-scilab
Version: 4:20.04.3-1
Severity: serious

As a result of swt dropping support for 32-bit targets, libjogl2-java can no 
longer be built on i386 and armhf and the
existing binaries have been removed in unstable. This in turn has lead to the 
removal of scilab on those architectures.

Please adjust the architecture list for cantor-backend-scilab accordingly.

Bug#973701: network-manager: 'systemctl restart ModemManager.service' wipes /etc/resolve.conf (almost) clean

[Cristian Ionescu-Idbohrn]

Package: network-manager
Version: 1.27.91-1
Severity: grave

/etc/resolve.conf includes the expected configuration (WRT
nameservers) on bootup.

After upgrading network-manager and restarting it, /etc/resolve.conf
(which is a symlink to /run/NetworkManager/resolv.conf) is basically
wiped out.  Includes only this:

# Generated by NetworkManager

Rebooting brings things to normal.  Still, this isn't wintendo.  I'd
expect better.

There are some workarounds (suggested in some other bug reports) that
bring the system back to an usable state, but far away from perfect 
(dhclient wlan0).  Duplicated home router nameserver addresses in 
/etc/resolv.conf:

nameserver 192.168.0.1
nameserver 192.168.0.1

which is not what my configuration is.


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

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

Versions of packages network-manager depends on:
ii  adduser  3.118
ii  dbus 1.12.20-1
ii  libaudit11:2.8.5-3.1
ii  libbluetooth35.55-1
ii  libc62.31-4
ii  libcurl3-gnutls  7.72.0-1
ii  libglib2.0-0 2.66.1-2
ii  libgnutls30  3.6.15-4
ii  libjansson4  2.13.1-1
ii  libmm-glib0  1.14.6-0.1
ii  libndp0  1.6-1+b1
ii  libnewt0.52  0.52.21-4+b2
ii  libnm0   1.27.91-1
ii  libpam-systemd   246.6-2
ii  libpsl5  0.21.0-1.1
ii  libreadline8 8.0-4
ii  libselinux1  3.1-2+b1
ii  libsystemd0  246.6-2
ii  libteamdctl0 1.31-1
ii  libudev1 246.6-2
ii  libuuid1 2.36-3+b2
ii  policykit-1  0.105-29
ii  udev 246.6-2
ii  wpasupplicant2:2.9.0-15

Versions of packages network-manager recommends:
ii  crda 4.14+git20191112.9856751-1
ii  dnsmasq-base [dnsmasq-base]  2.82-1
ii  iptables 1.8.5-3
ii  modemmanager 1.14.6-0.1
pn  ppp  

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1+b2
pn  libteam-utils

-- no debconf information


Cheers,

-- 
Cristian

Bug#973677: Confirmed even in 5.19.5-2

[Oliver Sander]

I (apparently) solved the problem by updating a few plasma packages to 5.19,
in particular

plasma-workspace
plasma-desktop

(and possibly one or two more).  They are still at 5.17 in unstable.



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#973677: Confirmed even in 5.19.5-2

[Oliver Sander]

I'm seeing the same thin even with libkscreenlocker5 5.19.5-2 from experimental.
The locked screen is completely black, and wiggling the mouse shows the cursor
but nothing else.

My workaround to unlocking the session is to switch to a TTY shell by 
ctrl-shift-2,
and using 'loginctl unlock-session'.



smime.p7s
Description: S/MIME Cryptographic Signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 973291 + src:ros-ros
Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Added indication that 973291 affects src:ros-ros
Added indication that 973095 affects src:ros-ros
> forcemerge 973291 973290
Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Removed indication that 973095 affects src:ros-ros, src:ros-rospack, and 
src:ros-angles
Added indication that 973095 affects src:ros-angles,src:ros-ros,src:ros-rospack
Removed indication that 973291 affects src:ros-rospack, src:ros-ros, and 
src:ros-angles
Added indication that 973291 affects src:ros-angles,src:ros-ros,src:ros-rospack
Bug #973290 [cmake-extras] ros-ros ftbfs in unstable with python3.9
Added indication that 973290 affects src:ros-angles,src:ros-ros,src:ros-rospack
Merged 973095 973290 973291
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095
973290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973290
973291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973290: ros-ros ftbfs in unstable with python3.9

[Timo Röhling]

Control: reassign -1 cmake-extras
Control: merge 973291 -1
Control: affects 973291 + src:ros-ros

Hi Matthias,

On Wed, 28 Oct 2020 09:45:53 +0100 Matthias Klose  wrote:
> to reproduce, you can use the repositories found at:
>
> deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
> deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

> the cmake output looks like it's using just python3, but apparently
that gets
> translated to the wrong python3 version.

The Python 3.9 rebuild of ros-rospack is missing in the ~ginggs
repository, probably due to bug #973291.
Linking against the old Python 3.8 version from sid causes the build
failure.
I verified that the build succeeds with an updated librospack-dev, so
I'm merging this bug.

Cheers
Timo

Processed (with 2 errors): Re: ros-ros ftbfs in unstable with python3.9

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cmake-extras
Bug #973290 [src:ros-ros] ros-ros ftbfs in unstable with python3.9
Bug reassigned from package 'src:ros-ros' to 'cmake-extras'.
No longer marked as found in versions ros-ros/1.15.7-1.
Ignoring request to alter fixed versions of bug #973290 to the same values 
previously set
> merge 973291 -1
Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Unable to merge bugs because:
affects of #973290 is '' not 'src:ros-rospack,src:ros-angles'
Failed to merge 973291: Did not alter merged bugs.

> affects 973291 + src:ros-ros
Failed to mark 973291 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/merge -- Unable to lock 
/srv/bugs.debian.org/spool/lock/merge Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


-- 
973095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973095
973290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973290
973291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973538: marked as done (poppler autopkgtest fails: error: ‘template class QLinkedList’ is deprecated: Use std::list instead)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 13:03:31 +
with message-id 
and subject line Bug#973538: fixed in poppler 20.09.0-3
has caused the Debian Bug report #973538,
regarding poppler autopkgtest fails: error: ‘template class 
QLinkedList’ is deprecated: Use std::list instead
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.)


-- 
973538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 20.09.0-2
Severity: serious
User: debian-qt-...@lists.debian.org
Usertags: qt5.15
Control: block 972278 by -1

Dear Maintainer,

poppler autopkgtest failed when run against Qt 5.15 from unstable:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/poppler/7873281/log.gz

The error is:

  autopkgtest [06:16:09]: test qt5: [---
  In file included from /usr/include/poppler/qt5/poppler-qt5.h:44,
   from 
/tmp/autopkgtest-lxc.ps5f1bjb/downtmp/build.gvJ/src/debian/tests/test-qt5.cpp:1:
  /usr/include/poppler/qt5/poppler-annotation.h:594:5: error: ‘template class QLinkedList’ is deprecated: Use std::list instead 
[-Werror=deprecated-declarations]
594 | QLinkedList linePoints() const;
| ^~~

And a few similar errors below.

This is an error (not a warning) because debian/tests/qt5 is using -Werror
flag.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 20.09.0-3
Done: Emilio Pozuelo Monfort 

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated poppler 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: Tue, 03 Nov 2020 13:27:06 +0100
Source: poppler
Architecture: source
Version: 20.09.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Closes: 973538
Changes:
 poppler (20.09.0-3) unstable; urgency=medium
 .
   * debian/tests: build with -Wno-deprecated-declarations, so that we don't
 fail if an rdep deprecates some symbols. Closes: #973538.
Checksums-Sha1:
 7f6604d92ac872f51c4669443fd57b0d47678d51 3302 poppler_20.09.0-3.dsc
 6ddce8fabce47d8c35ad602cb3ca2cfcef423dd9 1642932 poppler_20.09.0.orig.tar.xz
 f22e24473f4526689ce00eaeec8ea85caffe8a48 33828 poppler_20.09.0-3.debian.tar.xz
 6a516f75b3f9f3da0e696855bf90808a7bcc1ed8 6447 
poppler_20.09.0-3_source.buildinfo
Checksums-Sha256:
 7bd7903fed9030ec57e937733fe0f68bd6c506cfe8a8c1a25f09ec50bb8c4d1b 3302 
poppler_20.09.0-3.dsc
 4ed6eb5ddc4c37f2435c9d78ff9c7c4036455aea3507d1ce8400070aab745363 1642932 
poppler_20.09.0.orig.tar.xz
 8ab7f9d1edab08ac68c4c74d139aa833ddbe3f4dbc913b84d1300d9a2534 33828 
poppler_20.09.0-3.debian.tar.xz
 52e9ba8ac2a53097a1bab3c4b93e9d57f1252cb31ac8662f1d39ad076d5c02d2 6447 
poppler_20.09.0-3_source.buildinfo
Files:
 c13721e8cd90e2bf5d5b04425885d334 3302 devel optional poppler_20.09.0-3.dsc
 969328317ed60213f78b3502b074b72e 1642932 devel optional 
poppler_20.09.0.orig.tar.xz
 87a831ab5cbf17e555ff43bdde4d53f4 33828 devel optional 
poppler_20.09.0-3.debian.tar.xz
 6eff82c3f6321052f1437b3a86aed884 6447 devel optional 
poppler_20.09.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAl+hT0sACgkQnUbEiOQ2
gwKhXg/8C7qCxruFg5AyCdqqTYorfeTXhQd3MI/gp1/Ar2Q6N6uNefo7usIiIRMi
x1oBaq8UxvHiHS/8fGcTpFV3V7iZ6szFzTZVwenTxD2sWJV1KoPGVuLbQmF6MtpI
YEFbFhHmg6+AJUentX7WQKidplk+yr83BLdPFJlTIVFbcedhNKHZIGAmtS8Vvu0i
D3YcX1PRGQ1P9u+dR5+2DNdGOkJZHjLmuMhYXmNTrsv1+/KIaQuDpdcxCD6T11F2
SES692tR2M7UZE9yUlnUUqrw/kqD89iyKzVD3YceH+VoqcFhkvni9qsXk5RgakQV
R5TboD/8bDeIRxVd1zJ5hWeVr5/9wA/LU8gwSfks+qnKIeeQJ8uDQ9o3H7OoCugu
npVHRGbnwEf2yihyYV4S2niijIgRgX7wzBy7EajcVyKOuTv99wYbCNAHR39hCaxL
nwzo9xD2gtglm48LkMQ2ma2pw6xjDu6m9BnUqGA+4Wd6aTEt/uRtOfp4jESYx3KB
QdDCfcJNVTAc0/FyTodNFS7xm3Uk7CspCeR1fEBWFRjav/HVzZzDGQZfampwH0pU

Bug#973607: Opened a MR

[Lisandro Damián Nicanor Pérez Meyer]

Hi! I have created a MR in order to fix this bug in
https://salsa.debian.org/science-team/libqglviewer/-/merge_requests/2

Cheers, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#973071: marked as done (pybtex: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 12:34:17 +
with message-id 
and subject line Bug#973071: fixed in pybtex 0.23.0-1
has caused the Debian Bug report #973071,
regarding pybtex: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.9 3.8" returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d build/doctrees   source build/html
> Running Sphinx v3.2.1
> loading translations [en]... done
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 9 source files that are out of date
> updating environment: [new config] 9 added, 0 changed, 0 removed
> reading sources... [ 11%] api/formatting
> reading sources... [ 22%] api/index
> reading sources... [ 33%] api/parsing
> reading sources... [ 44%] api/plugins
> reading sources... [ 55%] api/styles
> reading sources... [ 66%] cmdline
> reading sources... [ 77%] formats
> reading sources... [ 88%] history
> reading sources... [100%] index
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 11%] api/formatting
> writing output... [ 22%] api/index
> writing output... [ 33%] api/parsing
> writing output... [ 44%] api/plugins
> writing output... [ 55%] api/styles
> writing output... [ 66%] cmdline
> writing output... [ 77%] formats
> writing output... [ 88%] history
> writing output... [100%] index
> 
> /<>/docs/source/api/formatting.rst:126: WARNING: unknown option: 
> -l python
> /<>/docs/source/cmdline.rst:61: WARNING: unknown option: --format
> /<>/docs/source/cmdline.rst:87: WARNING: unknown option: 
> --style-language
> /<>/docs/source/cmdline.rst:94: WARNING: unknown option: 
> --output-backend
> /<>/docs/source/cmdline.rst:109: WARNING: unknown option: 
> --name-style
> /<>/docs/source/cmdline.rst:109: WARNING: unknown option: 
> --abbreviate-names
> /<>/docs/source/cmdline.rst:149: WARNING: unknown option: --style
> generating indices...  genindexdone
> writing additional pages...  searchdone
> copying static files... ... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 7 warnings.
> 
> The HTML pages are in build/html.
> 
> build finished. the html pages are in build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:284: cp -r /<>/*.egg-info 
> /<>/.pybuild/cpython3_3.9_pybtex/build
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_pybtex/build; 
> python3.9 -m nose -v tests
> test_parser (tests.bibtex_parser_test.AtCharacterInUnwantedEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.AtCharacterTest) ... ok
> test_parser (tests.bibtex_parser_test.AtTest) ... ok
> test_parser (tests.bibtex_parser_test.BracesAndQuotesTest) ... ok
> test_parser (tests.bibtex_parser_test.BracesTest) ... ok
> test_parser (tests.bibtex_parser_test.CaseSensitivityTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossFileMacrosTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossrefTest) ... ok
> test_parser (tests.bibtex_parser_test.CrossrefWantedTest) ... ok
> test_parser (tests.bibtex_parser_test.DuplicateFieldTest) ... ok
> test_parser (tests.bibtex_parser_test.EmptyDataTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryInCommentTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryInStringTest) ... ok
> test_parser (tests.bibtex_parser_test.EntryTypesTest) ... ok
> test_parser (tests.bibtex_parser_test.FieldNamesTest) ... ok
> test_parser (tests.bibtex_parser_test.InlineCommentTest) ... ok
> test_parser (tests.bibtex_parser_test.KeyParsingTest) ... ok
> test_parser (tests.bibtex_parser_test.KeylessEntriesTest) ... ok
> test_parser (tests.bibtex_parser_test.MacrosTest) ... ok
> test_parser (tests.bibtex_parser_test.SimpleEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.UnusedEntryTest) ... ok
> test_parser (tests.bibtex_parser_test.WantedEntriesTest) ... ok
> test_parser 

Bug#973095: ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.

[Timo Röhling]

Control: reassign -1 cmake-extras
Control: reassign 973291 cmake-extras
Control: merge -1 973291
Control: affects -1 + src:ros-angles src:ros-rospack

Dear cmake-extras maintainers,

I believe bugs #973095 and #973291 can be traced back to your package:

> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > make[5]: Entering directory '/<>/build'
> > [ 90%] Building CXX object test/CMakeFiles/utest.dir/utest.cpp.o
> > cd /<>/build/test && /usr/bin/c++
-DGTEST_VERSION_MAJOR=1 -DGTEST_VERSION_MINOR=8 -DGTEST_VERSION_PATCH=0
-DGTEST_VERSION_UNKNOWN -DROS_BUILD_SHARED_LIBS=1
-I/<>/angles/include
-I/usr/src/googletest/googlemock/include
-I/usr/src/googletest/googletest/include -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o
CMakeFiles/utest.dir/utest.cpp.o -c /<>/angles/test/utest.cpp
> > make[5]: *** No rule to make target 'gmock/libgmock.a', needed by
'devel/lib/angles/utest'. Stop.
> > make[5]: Leaving directory '/<>/build'
> > make[4]: *** [CMakeFiles/Makefile2:324:
test/CMakeFiles/utest.dir/all] Error 2

Starting with version 1.9.0.20190831, the Googletest CMake scripts put
the library build artifacts into a "lib" subfolder of the current binary
output folder. The ExternalProject_Add() part of GMockConfig.cmake still
assumes they are in the binary folder itself, and subsequently creates
invalid interface libraries.

Cheers
Timo

Processed: Re: ros-angles: FTBFS: make[5]: *** No rule to make target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'. Stop.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cmake-extras
Bug #973095 [src:ros-angles] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Bug reassigned from package 'src:ros-angles' to 'cmake-extras'.
No longer marked as found in versions ros-angles/1.9.13-1.
Ignoring request to alter fixed versions of bug #973095 to the same values 
previously set
> reassign 973291 cmake-extras
Bug #973291 [src:ros-rospack] ros-rospack ftbfs with new googletest
Bug reassigned from package 'src:ros-rospack' to 'cmake-extras'.
No longer marked as found in versions ros-rospack/2.6.2-2.
Ignoring request to alter fixed versions of bug #973291 to the same values 
previously set
> merge -1 973291
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest
Merged 973095 973291
> affects -1 + src:ros-angles src:ros-rospack
Bug #973095 [cmake-extras] ros-angles: FTBFS: make[5]: *** No rule to make 
target 'gmock/libgmock.a', needed by 'devel/lib/angles/utest'.  Stop.
Bug #973291 [cmake-extras] ros-rospack ftbfs with new googletest
Added indication that 973095 affects src:ros-angles and src:ros-rospack
Added indication that 973291 affects src:ros-angles and src:ros-rospack

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

Processed: forward issue

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/silx-kit/fabio/issues/410
Bug #973028 [src:python-fabio] python-fabio's autopkg tests are failing with 
python3.9
Set Bug forwarded-to-address to 'https://github.com/silx-kit/fabio/issues/410'.

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

Bug#973028: forward issue

[Matthias Klose]

Control: forwarded -1 https://github.com/silx-kit/fabio/issues/410

Processed: Re: python-molotov's autopkg tests are failing with python3.9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #973033 [src:python-molotov] python-molotov's autopkg tests are failing 
with python3.9
Added tag(s) patch.

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

Bug#973033: python-molotov's autopkg tests are failing with python3.9

[Matthias Klose]

Control: tags -1 + patch

this needs a new upstream first:

2.0 - 2020-10-23


- added the --disable-dns-resolve option (#119)
- fix multiprocessing pickling issues by using dill
- display the max worker in the sizing result (#123)
- add aiodogstatsd (#122)
- added the --single-run option (#124)
- added support for 3.8 & 3.9 in tox/travis-ci
- speed up tests
- dropped support for 3.5

Bug#972867: marked as done (gdcm: FTBFS in testing and unstable)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 10:18:55 +
with message-id 
and subject line Bug#972867: fixed in charls 2.1.0+dfsg-6
has caused the Debian Bug report #972867,
regarding gdcm: FTBFS in testing and unstable
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.)


-- 
972867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdcm
Version: 3.0.7-3
Severity: serious
Tags: ftbfs bullseye sid


Hi Maintainer

As per reproducible builds [1], gdcm recently started failing to build
in testing and unstable.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gdcm.html


/usr/bin/c++ -DgdcmMSFF_EXPORTS -I../Source/Common -ISource/Common
-I../Source/DataStructureAndEncodingDefinition
-I../Source/DataDictionary -I../Source/InformationObjectDefinition
-I../Source/MediaStorageAndFileFormat -I../Utilities -IUtilities
-I/usr/include/openjpeg-2.3 -I/usr/include/json-c -I/usr/include/json
-g -O2 -ffile-prefix-map=/build/1st/gdcm-3.0.7=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -DCHARLS_DLL -MD -MT
Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o
-MF 
Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o.d
-o 
Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o
-c ../Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx
In file included from
../Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx:24:
../Utilities/gdcm_charls.h:21:11: fatal error: CharLS/charls.h: No
such file or directory
   21 | # include 
  |   ^
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: charls
Source-Version: 2.1.0+dfsg-6
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated charls 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: Tue, 03 Nov 2020 10:55:49 +0100
Source: charls
Architecture: source
Version: 2.1.0+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Mathieu Malaterre 
Closes: 972867
Changes:
 charls (2.1.0+dfsg-6) unstable; urgency=medium
 .
   [ Mathieu Malaterre ]
   * Team upload.
   * d/patches: Remove change_library_name patch
   * d/rules: Provide symlinks to mimic CharLS 2.0.x behavior. Closes: #972867
 .
   [ Sebastiaan Couwenberg ]
   * d/*.maintscript: Switching a directory to symlink
Checksums-Sha1:
 c807870aa211b752daadbb54c1ab7aceeb78b823 2065 charls_2.1.0+dfsg-6.dsc
 3afbb88708eadcc6e1892ccf946a12b7f8039f28 5556 charls_2.1.0+dfsg-6.debian.tar.xz
 d1b6269109feb5258f2ab49fe73013b97acfbd0b 6660 
charls_2.1.0+dfsg-6_source.buildinfo
Checksums-Sha256:
 a43d6f841c14273cea6e1568d486b6a024b6ac534cce643da8a892b38d7ef04e 2065 
charls_2.1.0+dfsg-6.dsc
 49b5409da46e7647a4b2c688e96c0bb035edcc7b26e43e536bddffbb2f4321e5 5556 
charls_2.1.0+dfsg-6.debian.tar.xz
 e794a140771397e7b5062f1864be8c81be8f14e6044747f253521e5b9c510974 6660 
charls_2.1.0+dfsg-6_source.buildinfo
Files:
 b2d3e8881e7d19e0f210b7a17e2a81a7 2065 science optional charls_2.1.0+dfsg-6.dsc
 2a341eb3afd180ed36dcc5882875c4fe 5556 science optional 
charls_2.1.0+dfsg-6.debian.tar.xz
 bb7513bdf3761a606f0140c1ae43e8bf 6660 science optional 
charls_2.1.0+dfsg-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAl+hKoIRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0WK2w//Xzx6HqPt8FvlMp+Ho3q04x01glTU1NTM
1W/g7/iFtP1ycfDR6C00zDjJepYoRS0z4RtQWPrVVBILtM9FBfIDGp5iOEXY3vJh
a0bMqBlvioxsA8QZRpKdZV+lkmaVcQ8PJ0Hh1hXxFG+l93TPocBTjukG908Qcs9D
sJ5vCWnTOACJoMfgfJbX/FMa6fW2AfbV33D7WmRbsdR5Udb0MJgyOhX5EQnFVXGN
Sx8pk0UR92ACivx8h68Y0TW7KkugdyPshLzVURzLrhR00uIdDhPcaDJTVUKEN+0u
eehGplCqe9tOVEmUBe1BFOcPm6EBbdYFVqprKQuRsbGS6ZZVq9fzAHDnp93ygp2r

Processed: Re: Bug#973652: xfce4-helpers: missing Breaks+Replaces: libexo-common (<< 4.15)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973652 [xfce4-helpers] xfce4-helpers: missing Breaks+Replaces: 
libexo-common (<< 4.15)
Added tag(s) pending.

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

Bug#973652: xfce4-helpers: missing Breaks+Replaces: libexo-common (<< 4.15)

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: tag -1 pending

On Mon, 2020-11-02 at 21:07 +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Hi, thanks for the report, I've updated the package in our repository and will
do an upload soon.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl+hEOkACgkQ3rYcyPpX
RFttfggAkBS8fer1daX2jzDWJGJDdEQlOBkaA+WL3YGxnQOS/9amcdE5EaUxeMSd
mv2Xmurk0+j2hPoCkg46Ax9WKh6htD8S1S43UqIM9jLkA/mLhPunbwEXiTzcozHx
QZsfOQnfp8yvwoY+xFklOkMMZdc7jZPvQU1LjUSUJ/vXJamhiJLV/FEomTgloGJX
DI0OCVy9ExamYZCKWk+MCi/arlJW7YaaDzWNNvWd7hA7qwPa6xbnlGKZZ/RHWFTO
YvK5hZcTLeMikPhpDFjnWWmxmmHTMtSrDy/I8bjGaVTZqRTA7uLLxf5KVpMhHG7H
873vFYgB3JJPWTJbdUs3HDbt0Sqcgw==
=S2FG
-END PGP SIGNATURE-

Bug#973631: marked as done (python3-mdtraj: /usr/bin/mdconvert is already owned by unrelated isync package)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 09:49:06 +
with message-id 
and subject line Bug#973631: fixed in mdtraj 1.9.4+git20201015.068f29a-5
has caused the Debian Bug report #973631,
regarding python3-mdtraj: /usr/bin/mdconvert is already owned by unrelated 
isync 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.)


-- 
973631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mdtraj
Version: 1.9.4+git20201015.068f29a-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Selecting previously unselected package python3-mdtraj.
  Preparing to unpack 
.../36-python3-mdtraj_1.9.4+git20201015.068f29a-4_amd64.deb ...
  Unpacking python3-mdtraj (1.9.4+git20201015.068f29a-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-qEpbdG/36-python3-mdtraj_1.9.4+git20201015.068f29a-4_amd64.deb
 (--unpack):
   trying to overwrite '/usr/bin/mdconvert', which is also in package isync 
1.3.0-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-qEpbdG/36-python3-mdtraj_1.9.4+git20201015.068f29a-4_amd64.deb


The isync package already ships these files since 2009:

usr/bin/mdconvert
usr/share/man/man1/mdconvert.1.gz


cheers,

Andreas


isync=1.3.0-2_python3-mdtraj=1.9.4+git20201015.068f29a-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mdtraj
Source-Version: 1.9.4+git20201015.068f29a-5
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mdtraj 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: Tue, 03 Nov 2020 16:07:00 +0800
Source: mdtraj
Architecture: source
Version: 1.9.4+git20201015.068f29a-5
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 973631
Changes:
 mdtraj (1.9.4+git20201015.068f29a-5) unstable; urgency=medium
 .
   * debian patch rename-mdconvert-mdtraj.patch renames mdconvert to
 mdconvert-mdtraj to avoid filename conflict with mdconvert from
 the isync package. Closes: #973631.
Checksums-Sha1:
 9b2ed847315565a63c70e68aa1def820ff888dc3 2732 
mdtraj_1.9.4+git20201015.068f29a-5.dsc
 7198efbd3556bd1c1cdd476245fecfed1870a97c 298496 
mdtraj_1.9.4+git20201015.068f29a-5.debian.tar.xz
Checksums-Sha256:
 d5be4724dfe00efa01aa72fd83d1d66d4fcf78f32326cc2ff4eafbff5c77bedd 2732 
mdtraj_1.9.4+git20201015.068f29a-5.dsc
 2a95f551d0ef042b463d09991b42677bbffbbfed8ffe6474e41442344690bdd1 298496 
mdtraj_1.9.4+git20201015.068f29a-5.debian.tar.xz
Files:
 ee619a972959954779de5e9c82f5d8c2 2732 python optional 
mdtraj_1.9.4+git20201015.068f29a-5.dsc
 63ac2d02033a35b0b1940d87a680a344 298496 python optional 
mdtraj_1.9.4+git20201015.068f29a-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl+hIisACgkQVz7x5L1a
AfpP5BAAls90MPB7nndmg+RGS85qLogjFu/BslfpVPwI3V2KJN44JQUVqu0ZXqjJ
Ph9WzGzqtFve6aExkOc6xPi5FoYTZPAskzcbEgtTepryYXHWTsKPxAIHkTYIvw6b
chhU6sHOhp1b9Q4BIx/Oi31iCg1QvM7hyOMT5zCcrPFc6KslfZpBR+0Fb2hjlTUi
d4+46lww64+/QCh15by75fkCkfhAxh1UtvygjfK29hgEJ0HY4cacs+lt0M6i/G7m
extRf3aOUtqvSBPvCWDnXbJjgPymBjF8qBQ/YDt7j6tR+b74dB42o36PqzTqR3A7
HX5ZKeod4DeleyK8eTeZmCyMelhz4CvukzPsClfyd3/db1gPRXlhEA52utuw54iX
zXN9sJxI3gva2RFzy2Z/oabtFLwyIPA4LHUsNGutv/5RrkvpOb+9CfztrxRVeV7q
8a8rY4C2iImY+NwCkOI1nSnljJEN4BhiQFrNRcihtj6YjHESh/SDnuiR7F95xAOd
vv7EYUMoE1a4nSmNH4h3mqslLdBMhSkw3+POGOU3j8I9EVkkVOGVPmNIyxl4B8vV
M1Ql0Cr9YboCZx9G1r5UFyjL3dFLEXOgfzVD3d2jS0l9hUkIOIMmQsirlTRO4bPx
KxOywtABZXnhIQcVGbufBvnJzFtCw+CtSmv0uoYBpQiJH1b16yM=
=NsqQ
-END PGP SIGNATURE End Message ---

Bug#925793: marked as pending in ola

[Wouter Verhelst]

Control: tag -1 pending

Hello,

Bug #925793 in ola reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/wouter/ola/-/commit/a5fe685026c18dab8260704fe828560b322b8a9c


Changelog entry for upstream merge. Closes: #944927, #925793


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/925793

Processed: Bug#925793 marked as pending in ola

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #925793 [src:ola] ola: ftbfs with GCC-9
Added tag(s) pending.

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

Bug#973623: stack overflows with ghc on ppc64el

[Michael Hudson-Doyle]

In that case, someone should upload something like this:

(master *)mwhudson@anduril:~/src/pkg/DHG_packages/p/ghc$ git diff
diff --git a/p/ghc/debian/rules b/p/ghc/debian/rules
index a5fd42860b..af3f8851d3 100755
--- a/p/ghc/debian/rules
+++ b/p/ghc/debian/rules
@@ -50,7 +50,7 @@ endif
 # once #901947 has been fixed.
 # Do the same for powerpcspe, due to https://bugs.debian.org/904915
 # Do the same for sparc64, due to https://bugs.debian.org/908998
-ifneq (,$(filter mips mipsel powerpc powerpcspe sparc64, $(DEB_HOST_ARCH)))
+ifneq (,$(filter mips mipsel powerpc powerpcspe ppc64el sparc64,
$(DEB_HOST_ARCH)))
   EXTRA_CONFIGURE_FLAGS += --disable-ld-override
 endif

but not me right now as I'm going to bed :)

On Tue, 3 Nov 2020 at 20:33, Matthias Klose  wrote:

> the patch mentioned above is already part of bintuils 2.35.1-2.
>
> --
> To unsubscribe, send mail to 973623-unsubscr...@bugs.debian.org.
>

Bug#973635: marked as done (python-is-python3: missing Breaks+Replaces: python-minimal)

[Debian Bug Tracking System]

Your message dated Tue, 03 Nov 2020 08:52:03 +
with message-id 
and subject line Bug#973635: fixed in what-is-python 8
has caused the Debian Bug report #973635,
regarding python-is-python3: missing Breaks+Replaces: python-minimal
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.)


-- 
973635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-is-python3
Version: 3.8.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
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 .../python-is-python3_3.8.6-1_all.deb ...
  Unpacking python-is-python3 (3.8.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-is-python3_3.8.6-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/python', which is also in package 
python-minimal 2.7.16-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-is-python3_3.8.6-1_all.deb

(Same as #973273, but for python-is-python3)


cheers,

Andreas


python-minimal=2.7.16-1_python-is-python3=3.8.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: what-is-python
Source-Version: 8
Done: Matthias Klose 

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

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated what-is-python package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Nov 2020 09:20:30 +0100
Source: what-is-python
Architecture: source
Version: 8
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose  
Changed-By: Matthias Klose 
Closes: 973635
Changes:
 what-is-python (8) unstable; urgency=medium
 .
   * python-is-python3: Add breaks/replaces for python-minimal.
 Closes: #973635.
Checksums-Sha1:
 858b2d8130aa17116a2c3b62370edc27a92aadaf 1716 what-is-python_8.dsc
 ae2407272b727234e635f65ced6a0ff879badc51 2516 what-is-python_8.tar.xz
 67ef59128f37a0c89cc2ee781e39aad1762c942a 6318 what-is-python_8_source.buildinfo
Checksums-Sha256:
 1388641adc2fb2cf78967ac88cccf65e81124e8aba643593060c53abe23479d4 1716 
what-is-python_8.dsc
 fcde2743948b7adea39d8b3ca52bdc2c70fa9fec37000239a34c57f5f4eb508e 2516 
what-is-python_8.tar.xz
 3aa1173c6050218b5dc93111b0a8418898cae997ec51c162dde63e2bbe985e06 6318 
what-is-python_8_source.buildinfo
Files:
 bfb1432d867fb6a552c59767bab58e25 1716 python optional what-is-python_8.dsc
 57696a340b440f3795979c151f072055 2516 python optional what-is-python_8.tar.xz
 9eea2d537ac34c6e586e9c4ba7c860dd 6318 python optional 
what-is-python_8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl+hFxMQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9cbqD/9HcTXKHXbXw0DghRH89UTIleLAWovAXGf3
enpDCwaFalnSIYpi9Mf37m7BoBEpNglsQqxzKeUwAXVnd2im63ma5/5Do8EES8Jx
rVi6YCbaE8pE5QTRO0q3uC5BEIqYnoxuIlszGCtWjncZncI2YtX4pq25Hqn5rpsM
yu30NwApQ8mo/xljLy+AycNvaH1jW/YYaOpuzYAmKb5AlDjg3+s9oOcG4GOvJfeH
oSKTk26j6agnO/Q0bP/vSJ8/4tpURsXCID3/mXzcAHUlqSEoV9vr/iJ7x4cfPKq1
r2SXTOyEOY+wV7J2wprhYIsejXPx8pmDdWhJTmyHxZMYNhnMQw8yVim+1pzfH+9V
Nfrpw3W/kcSaXmkBGPA49LJsvCxsOiZUfKCvsGWPUnIPjvGLRrFglXxpThBiYOsW
pVPnK3C/1Qp8J4fF8IluwrpafBo9okwcqYXWDNurXbKgU2NaZBZYVQCpn6Y46KGL
cbHwnpXeWYssdtPB4BVjlRmmuFJAc6ptf9LfC69DJMpZ3zd722aHiFMeGbchevOt
zhqHrd0VLJzbcbeyKrZk4Iw6TzKAabfnCu1O4kxzvU+b4WvKoAbqW/JHLxEQHxdE
z3wclpZlrBe//IzE8kRN7Ce2/iNBTO6Mq6d9qM4/m9QfRBTYvMjWa4jHFiJR+1lN
ubKEzXl6+A==
=/8mZ
-END PGP SIGNATURE End Message ---

Processed: closing 896620

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 896620 0.14.0-1
Bug #896620 [src:dipy] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked as fixed in versions dipy/0.14.0-1.
Bug #896620 [src:dipy] FTBFS with sphinx 1.7.2: exception: cannot import name 
'Directive'
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
896620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#971788: marked as done (libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1 version is unavailable)

[Debian Bug Tracking System]

Your message dated Tue, 3 Nov 2020 09:46:59 +0100
with message-id 
and subject line Re: Bug#971788: libnvidia-rtcore: Broken dependnecies: 
dependant libgcc-s1 version is unavailable
has caused the Debian Bug report #971788,
regarding libnvidia-rtcore: Broken dependnecies: dependant libgcc-s1 version is 
unavailable
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.)


-- 
971788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnvidia-rtcore
Version: 450.66-1~bpo10+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The current buster-backports version of libnvidia-rtcore depends upon
libgcc-s1 >= 4.2 which is unavailable in buster or buster-backports,
making this package impossible to install.

It looks like either gcc-10 needs to be backported to buster, or
libnvidia-rtcore needs to be ported to a version of gcc available in buster.

Regards,
Aidan Gauland



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

Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ.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 libnvidia-rtcore depends on:
ii  libc6  2.28-10
pn  libgcc-s1  
ii  libgcc1    1:8.3.0-6

libnvidia-rtcore recommends no packages.

libnvidia-rtcore suggests no packages.
--- End Message ---
--- Begin Message ---
On 10/7/20 11:00 AM, Aidan Gauland wrote:
> The current buster-backports version of libnvidia-rtcore depends upon
> libgcc-s1 >= 4.2 which is unavailable in buster or buster-backports,
> making this package impossible to install.

The package was built in sid instead of buster by accident and picked up
that wrong dependency.
This is fixed with new version just uploaded to buster-backports.

Andreas--- End Message ---

Processed: found 973660 in 1:78.3.1-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 973660 1:78.3.1-2
Bug #973660 [src:thunderbird] thunderbird: FTBFS on s390x in buster
Marked as found in versions thunderbird/1:78.3.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#904652: pulseaudio: looses device and replace it with dummy package so no sound possible

[alain]

Package: pulseaudio
Version: 13.0-5
Followup-For: Bug #904652
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr

it seems that the problem keeps going on with the 5.9.0-1 kernel .

so , same problem , same solution :

for me :

lsmod | grep hdmi

alain@testing:~$ lsmod | grep hdmi

snd_hda_codec_hdmi 73728  1
snd_hda_codec 163840  4
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core  106496  5
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pcm   135168  6
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
snd   110592  35
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi

sudo nano /etc/modprobe.d/hdmi-blacklist.conf

blacklist snd_hda_codec_hdmi

and test .






-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 5.9.0-1-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.58
ii  libasound2   1.2.3.2-1
ii  libasound2-plugins   1.2.2-2
ii  libc62.31-4
ii  libcap2  1:2.44-1
ii  libdbus-1-3  1.12.20-1
ii  libgcc-s110.2.0-15
ii  libice6  2:1.0.10-1
ii  libltdl7 2.4.6-14
ii  liborc-0.4-0 1:0.4.32-1
ii  libpulse013.0-5
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-8
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   10.2.0-15
ii  libsystemd0  246.6-2
ii  libtdb1  1.4.3-1
ii  libudev1 246.6-2
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.6.12-1
ii  libx11-xcb1  2:1.6.12-1
ii  libxcb1  1.14-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 13.0-5

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.12.20-1
ii  libpam-systemd [logind]  246.6-2
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  4.0-2
pn  pavumeter
ii  udev 246.6-2

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See 

Processed: tagging 973660

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 973660 + buster
Bug #973660 [src:thunderbird] thunderbird: FTBFS on s390x in buster
Added tag(s) buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#973639: libgromacs6: missing Breaks+Replaces: libgromacs5

[Mark Abraham]

Hi Andreas,

Thanks for the report, and sorry for the omission. This was already fixed
upstream by bumping to soversion 0.2.0 and will be in 2021~beta2

Mark

On Mon, 2 Nov 2020 at 19:00, Andreas Beckmann  wrote:

> Package: libgromacs6
> Version: 2021~beta1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libgromacs6_2021~beta1-1_amd64.deb ...
>   Unpacking libgromacs6:amd64 (2021~beta1-1) ...
>   dpkg: error processing archive
> /var/cache/apt/archives/libgromacs6_2021~beta1-1_amd64.deb (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/libgmxapi.so.0.1.0',
> which is also in package libgromacs5:amd64 2020.4-2
>   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/var/cache/apt/archives/libgromacs6_2021~beta1-1_amd64.deb
>
> Shared libraries with independent soversions shouldn't be bundled in the
> same
> binary package.
>
>
> cheers,
>
> Andreas
>

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

[Debian Bug Tracking System]

Your message dated Tue, 3 Nov 2020 09:42:11 +0100
with message-id 
and subject line fixed in 0.4.2-13.4
has caused the Debian Bug report #937996,
regarding python-pam: 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.)


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

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.4.2-13.4--- End Message ---

Processed: found 973660 in 78.3.1-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 973660 78.3.1-2
Bug #973660 [src:thunderbird] thunderbird: FTBFS on s390x in buster
The source 'thunderbird' and version '78.3.1-2' do not appear to match any 
binary packages
Marked as found in versions thunderbird/78.3.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: raise severity for Python2 issue

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 943149 serious
Bug #943149 [src:pam-mysql] pam-mysql: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
943149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 972417 to light-locker, forcibly merging 870641 972417

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 972417 light-locker
Bug #972417 [xfce4-power-manager] xfce4-power-manager: System left idle => 
'display power management' auto-locks session => no X session or lightdm greeter
Bug reassigned from package 'xfce4-power-manager' to 'light-locker'.
No longer marked as found in versions xfce4-power-manager/1.6.1-1, 
xfce4-power-manager/1.7.0-1, and xfce4-power-manager/1.6.6-1.
Ignoring request to alter fixed versions of bug #972417 to the same values 
previously set
> forcemerge 870641 972417
Bug #870641 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #805711 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #846278 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #868087 [light-locker] light-locker: Locking screen with light-locker 
crashes system to blinking cursor
Bug #908329 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #922095 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #929461 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #929834 [light-locker] lightdm-gtk-greeter: After locking screen, display 
is turned off and unlock prompt is not visible.
Bug #931555 [light-locker] light-locker does not show lightdm greeting screen 
when the X server recovers its DPMS state from standby to normal
Bug #972417 [light-locker] xfce4-power-manager: System left idle => 'display 
power management' auto-locks session => no X session or lightdm greeter
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=110863'.
Severity set to 'important' from 'grave'
Added indication that 972417 affects lightdm-gtk-greeter
Marked as found in versions light-locker/1.8.0-2, light-locker/1.7.0-3, 
light-locker/1.4.0-2, light-locker/1.8.0-1, and light-locker/1.8.0-3.
Added tag(s) fixed-upstream.
Bug #805711 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #846278 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #868087 [light-locker] light-locker: Locking screen with light-locker 
crashes system to blinking cursor
Bug #908329 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #922095 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #929461 [light-locker] light-locker, lightdm: screen stays off after resume
Bug #929834 [light-locker] lightdm-gtk-greeter: After locking screen, display 
is turned off and unlock prompt is not visible.
Bug #931555 [light-locker] light-locker does not show lightdm greeting screen 
when the X server recovers its DPMS state from standby to normal
Merged 805711 846278 868087 870641 908329 922095 929461 929834 931555 972417
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
805711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805711
846278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846278
868087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868087
870641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870641
908329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908329
922095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922095
929461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929461
929834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929834
931555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931555
972417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems