Processed: severity of 972547 is important

[Debian Bug Tracking System]

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

> severity 972547 important
Bug #972547 [src:linux] linux-image-4.19.0-12-amd64: Freezing when unplugging 
wireless network adapter usb
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#957445: marked as done (libhdf4: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 15 Nov 2020 06:18:20 +
with message-id 
and subject line Bug#957445: fixed in libhdf4 4.2.15-3
has caused the Debian Bug report #957445,
regarding libhdf4: 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.)


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

[...]
libtool: compile:  gfortran -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -O -c ../../../../HDF4.2.14/hdf/src/dfff.f  -fPIC -o 
.libs/dfff.o
libtool: compile:  gfortran -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -O -c ../../../../HDF4.2.14/hdf/src/dfff.f -o dfff.o 
>/dev/null 2>&1
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../../../HDF4.2.14/hdf/src   -Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS 
-DSWAP   -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o dfpf.lo 
../../../../HDF4.2.14/hdf/src/dfpf.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../HDF4.2.14/hdf/src 
-Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS -DSWAP -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c 
../../../../HDF4.2.14/hdf/src/dfpf.c  -fPIC -DPIC -o .libs/dfpf.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../HDF4.2.14/hdf/src 
-Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS -DSWAP -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c 
../../../../HDF4.2.14/hdf/src/dfpf.c -o dfpf.o >/dev/null 2>&1
/bin/bash ../../libtool  --tag=F77   --mode=compile gfortran  -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -O -c -o 
dfpff.lo ../../../../HDF4.2.14/hdf/src/dfpff.f
libtool: compile:  gfortran -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -O -c ../../../../HDF4.2.14/hdf/src/dfpff.f  -fPIC -o 
.libs/dfpff.o
libtool: compile:  gfortran -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -O -c ../../../../HDF4.2.14/hdf/src/dfpff.f -o dfpff.o 
>/dev/null 2>&1
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../../../HDF4.2.14/hdf/src   -Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS 
-DSWAP   -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c -o dfr8f.lo 
../../../../HDF4.2.14/hdf/src/dfr8f.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../HDF4.2.14/hdf/src 
-Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS -DSWAP -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c 
../../../../HDF4.2.14/hdf/src/dfr8f.c  -fPIC -DPIC -o .libs/dfr8f.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../../HDF4.2.14/hdf/src 
-Wdate-time -D_FORTIFY_SOURCE=2 -DBIG_LONGS -DSWAP -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c 
../../../../HDF4.2.14/hdf/src/dfr8f.c -o dfr8f.o >/dev/null 2>&1
/bin/bash ../../libtool  --tag=F77   --mode=compile gfortran  -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -O -c -o 
dfr8ff.lo 

Bug#974751: marked as done (guix: Fails to install with "guix.postinst: 5: systemd-sysusers: not found" if package systemd is not installed)

[Debian Bug Tracking System]

Your message dated Sun, 15 Nov 2020 04:48:19 +
with message-id 
and subject line Bug#974751: fixed in guix 1.2.0~rc1-2
has caused the Debian Bug report #974751,
regarding guix: Fails to install with "guix.postinst: 5: systemd-sysusers: not 
found" if package systemd is not installed
to be marked as done.

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

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


-- 
974751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guix
Version: 1.2.0~rc1-1
Severity: serious

Dear Vagrant,

your recently uploaded guix package fails in the postinst script as
follows on a system without the package systemd being installed:

Setting up guix (1.2.0~rc1-1) ...
/var/lib/dpkg/info/guix.postinst: 5: systemd-sysusers: not found
dpkg: error processing package guix (--configure):
 installed guix package post-installation script subprocess returned error exit 
status 127

Please try to guard that call (and/or provide an alternative code path)
so that it also works with other init systems or even completely without
an init system (like in a chroot).

If that's not possible, you probably need to add a dependency on
"systemd | opensysusers" and check for "sysusers" or "opensysusers"
instead of systemd-sysusers, too. opensysusers is an alternative
implementation of systemd's sysusers that also works with other init
systems or without init system at all.

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages guix depends on:
ii  guile-3.03.0.4-3
ii  guile-3.0-libs   3.0.4-3
ii  guile-gcrypt 0.3.0-2
ii  guile-git0.4.0-1
ii  guile-gnutls 3.6.15-5
ii  guile-json   4.3.2-2
ii  guile-lzlib  0.0.2-2
ii  guile-sqlite30.1.3-1
ii  guile-ssh0.13.1-3
ii  guile-zlib   0.0.1-3
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-4
ii  libgcc-s110.2.0-17
ii  libgcrypt20  1.8.7-2
ii  libgcrypt20-dev [libgcrypt-dev]  1.8.7-2
ii  libgit2-dev  1.0.1+dfsg.1-1
ii  libsqlite3-0 3.33.0-1
ii  libsqlite3-dev   3.33.0-1
ii  libssh-dev   0.9.4-2
ii  libstdc++6   10.2.0-17
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages guix recommends:
pn  nscd  

guix suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: guix
Source-Version: 1.2.0~rc1-2
Done: Vagrant Cascadian 

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

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated guix 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: Sat, 14 Nov 2020 20:06:42 -0800
Source: guix
Architecture: source
Version: 1.2.0~rc1-2
Distribution: experimental
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 974751
Changes:
 guix (1.2.0~rc1-2) experimental; urgency=medium
 .
   * debian/guix.postinst: Only call systemd-sysusers if
 installed. (Closes: #974751). Thanks to Axel Beckert.
   * debian/control:
 - Recommend systemd for systemd-sysusers command.
 - Build-Depends/Depends: Allow slightly older versions of
   guile-gnutls.
   * debian/rules: Adjust guix architecture for armhf.
Checksums-Sha1:
 dab281ea469acc0636e38fa86687a50ca73c60ba 1843 

Bug#958497: geoclue-2.0 violates GDPR

[Michel Le Bihan]

Hello,

I disagree with your opinion on this. I think that users should be
aware that their SSIDs are visible and by deliberately broadcasting it,
they agree that anybody can hear it and record it including any bad
actors. They can always use the hide SSID feature. I think that in this
case it's more like going outside and shouting something and then
complaining that somebody heard that and even recorded that.

Michel Le Bihan

Bug#974073: gcc-10: arm64 internal compiler error: canonical types differ for identical types

[Wookey]

Package: gcc-10
Followup-For: Bug #974073

I tried to build SparseMatrix-2.ii using the sample command on an Ampere emag 
(64GB RAM). It built successfully in an unstable chroot, taking about 5 
minutes, consuming about 3.5GB resident memory to do so, confirming what you 
found.

However building polymake under sbuild still fails, just as in #974058.
So does building polymake in the above (unclean) chroot, or compiling
SparseMatrix.cc alone. Max RAM usage in the polymake build got to
about 20G using 16 cores, but fell back to about 4.7G and only 4 cores
when the sparseMatrix compile dies. 

Building the one file alone:
g++ -c -o 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o 
-MMD -MT 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o 
-MF 
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o.d
 -fPIC -pipe -g -O2 -fdebug-prefix-map=/home/wookey/debian/polymake-4.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++14 -ftemplate-depth-200 -fno-strict-aliasing 
-fopenmp -Wshadow -Wlogical-op -Wconversion -Wzero-as-null-pointer-constant 
-Wno-parentheses -Wno-error=unused-function -Wno-stringop-overflow 
-Wno-array-bounds -DPOLYMAKE_WITH_FLINT  -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 
-DPOLYMAKE_APPNAME=common 
-I/home/wookey/debian/polymake-4.1/include/app-wrappers 
-I/home/wookey/debian/polymake-4.1/include/apps 
-I/home/wookey/debian/polymake-4.1/include/external/permlib 
-I/home/wookey/debian/polymake-4.1/include/external/TOSimplex 
-I/home/wookey/debian/polymake-4.1/include/core-wrappers 
-I/home/wookey/debian/polymake-4.1/include/core 
/home/wookey/debian/polymake-4.1/apps/common/cpperl/generated/SparseMatrix-2.cc 
&& : 'COMPILER_USED=10.2.0'

fails quickly with the same 
/home/wookey/debian/polymake-4.1/include/core/polymake/GenericVector.h:304:11: 
internal compiler error: canonical types differ for identical types error.
This only gets to about 500MB RAM usage before dying.

So, no this doesn't seem to be an OOM-killer issue. Not sure what _is_ going on 
with all that hardcore C++ typing. I'll ask internally if anyone has a clue.

--
Wookey

Bug#943037: Status of this bug?

[Josh Triplett]

I'm aware of the upstream update (and appreciate it); I'm asking about
the status of the Debian package for the new version.

On Sun, Nov 15, 2020 at 12:08:42AM +0100, Leandro Lucarella wrote:
> Hi Josh, Version 2.0.0, released recently, supports python3. The Debian 
> package just needs to be updated. You can download a .deb built from the 
> source from here if you can't wait:
> https://bintray.com/sociomantic-tsunami/tools/git-hub
> 
> On 14 November 2020 22:41:02 GMT+01:00, Josh Triplett  
> wrote:
> >What's the current status of this bug? I'd love to have a version of
> >git-hub that doesn't depend on Python 2; it's the last thing on my
> >system that still wants Python 2.
> 
> -- 
> Leandro Lucarella (luca)
> Sent from my phone. Please excuse my brevity and any typos.

Bug#974751: guix: Fails to install with "guix.postinst: 5: systemd-sysusers: not found" if package systemd is not installed

[Axel Beckert]

Hi Vagrant,

thanks for the prompt fix! I consider to be sufficiently fixed given
that this line wasn't needed before and hence seems to be optional
anyways.

Vagrant Cascadian wrote:
> There are a few other issues related to the lack of proper support for
> init.d scripts as well, and it would be nice to fix issues to support
> other init systems... any help would be appreciated!

Sorry, since I have no idea for what a package manager needs an init
script (or its own user, except maybe for privilege separation during
downloads), I have no idea what actually an init script should do
here.

Looking at /usr/lib/sysusers.d/guix-daemon.conf it seems as if guix
needs some kind of daemon?!? That's unexpected.

I'm also not convinced by guix' concepts (and containing a daemon just
added one more argument against guix) and just installed it to maybe
occasionally understand more if its something useful for me or not.

So I currently neither consider myself a regular user nor a potential
future contributor besides reporting obvious packaging-related bugs
like this one.

[opensysusers]
> I did ask zigo about the status of opensysusers on IRC, and got the
> impression that it might be orphaned or removed from the archive,

I see.

> so did not pursue further, though does not sound like it would be
> difficult to add support.

Ok for me.

> Alternate to having a working sysusers.d implementation, it could be
> documented in README.Debian to create the users and groups manually.

Would be fine for me.

I though wonder if a "Recommends: systemd" or "Suggests: systemd"
would make sense here.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#974751: marked as pending in guix

[Vagrant Cascadian]

Control: tag -1 pending

Hello,

Bug #974751 in guix 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/debian/guix/-/commit/850961a73407cea2319d053c72a80ec103be8ea0


debian/guix.postinst: Only call systemd-sysusers if installed.
(Closes: #974751). Thanks to Axel Beckert.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974751

Processed: Bug#974751 marked as pending in guix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974751 [guix] guix: Fails to install with "guix.postinst: 5: 
systemd-sysusers: not found" if package systemd is not installed
Added tag(s) pending.

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

Bug#943037: Status of this bug?

[Leandro Lucarella]

Hi Josh, Version 2.0.0, released recently, supports python3. The Debian package 
just needs to be updated. You can download a .deb built from the source from 
here if you can't wait:
https://bintray.com/sociomantic-tsunami/tools/git-hub

On 14 November 2020 22:41:02 GMT+01:00, Josh Triplett  
wrote:
>What's the current status of this bug? I'd love to have a version of
>git-hub that doesn't depend on Python 2; it's the last thing on my
>system that still wants Python 2.

-- 
Leandro Lucarella (luca)
Sent from my phone. Please excuse my brevity and any typos.

Processed: tagging 966770, found 966770 in 4.3.0+dfsg-1, tagging 885140, tagging 972339 ..., tagging 970878 ...

[Debian Bug Tracking System]

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

> tags 966770 + experimental
Bug #966770 [src:opencv] opencv: Unversioned Python removal in sid/bullseye
Added tag(s) experimental.
> found 966770 4.3.0+dfsg-1
Bug #966770 [src:opencv] opencv: Unversioned Python removal in sid/bullseye
Marked as found in versions opencv/4.3.0+dfsg-1.
> tags 885140 + experimental
Bug #885140 [src:wicd] wicd: Depends on unmaintained pygtk
Added tag(s) experimental.
> tags 972339 - bullseye
Bug #972339 [printer-driver-hpcups] armhf: hpcups crashes with free() invalid 
pointer for some printers
Removed tag(s) bullseye.
> found 974207 1.4.1231-1
Bug #974207 [src:psi-plus] psi-plus: FTBFS with Qt 5.15
Marked as found in versions psi-plus/1.4.1231-1.
> tags 970878 + experimental
Bug #970878 [src:ghostscript] ghostscript breaks doc-rfc autopkgtest: 
segmentation fault
Added tag(s) experimental.
> found 967623 0.90.6+bzr508-1
Bug #967623 [src:marionnet] marionnet: depends on deprecated GTK 2
Marked as found in versions marionnet/0.90.6+bzr508-1.
> tags 967623 + sid bullseye
Bug #967623 [src:marionnet] marionnet: depends on deprecated GTK 2
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: severity

[Debian Bug Tracking System]

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

> severity 972334 normal
Bug #972334 [src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest failure on 
i386: integration-test-suite-test FAIL non-zero exit status 2
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#972334: severity

[Sylvestre Ledru]

severity 972334 normal

thanks

Hello

As this isn't a new regression (it didn't work before), I am lowering 
the severity to allow migration.


Cheers,
S

Bug#974773: jverein FTBFS: hibiscus/lib does not exist

[Adrian Bunk]

Source: jverein
Version: 2.8.18+git20200921.6212a59+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=jverein=all=2.8.18%2Bgit20200921.6212a59%2Bdfsg-1=1605379443=0

...
compile:
[mkdir] Created dir: /<>/bin
[javac] Compiling 798 source files to /<>/bin

BUILD FAILED
/<>/build/build.xml:55: /<>/hibiscus/lib does not exist.

Total time: 0 seconds
dh_auto_build: error: cd build && ant -Duser.name debian returned exit code 1
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25

Bug#964688: cherry-pick patch from upstream - fixes #964688

[Adrian Bunk]

On Sat, Nov 14, 2020 at 09:28:53PM +0100, Andreas Tille wrote:
> Control: tags -1 pending
> Control: tags 922571 pending
> 
> Hi,
> 
> I have moved sigviewer to Debian Med team[1], fixed the other bug and
> tried to build the new upstream version 0.6.4 but failed:
> 
> ...
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/sigviewer-0.6.4=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=gnu++11 -D_REENTRANT -Wall -  Wextra -fPIC 
> -DVERSION_MAJOR=0 -DVERSION_MINOR=6 -DVERSION_BUILD=4 -DQT_NO_DEBUG_OUTPUT 
> -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
> -I/build/sigviewer-0.6.4/ external/include -Isrc 
> -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/  QtXml 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp/release -Itmp/release 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
> tmp/release/undo_redo_gui_command.o src/gui_impl/commands/ 
> undo_redo_gui_command.cpp
> src/gui_impl/commands/open_file_gui_command.cpp: In member function 'void 
> sigviewer::OpenFileGuiCommand::importEvents()':
> src/gui_impl/commands/open_file_gui_command.cpp:200:23: error: redeclaration 
> of 'sigviewer::FileSignalReader* file_signal_reader'
>   200 | FileSignalReader* file_signal_reader = 
> FileSignalReaderFactory::getInstance()->getHandler (file_path);
>   |   ^~
> src/gui_impl/commands/open_file_gui_command.cpp:185:23: note: 
> 'sigviewer::FileSignalReader* file_signal_reader' previously declared here
>   185 | FileSignalReader* file_signal_reader = 
> FileSignalReaderFactory::getInstance()->getHandler (file_path);
>   |   ^~
> make[1]: *** [Makefile:2576: tmp/release/open_file_gui_command.o] Error 1
> 
> 
> Any help would be welcome

This is from 0002-add-support-for-reading-GDF-formated-event-file.patch,
which seems to be upstream now - and adding the same code twice is what
failed.

>Andreas.

cu
Adrian

Bug#943037: Status of this bug?

[Josh Triplett]

What's the current status of this bug? I'd love to have a version of
git-hub that doesn't depend on Python 2; it's the last thing on my
system that still wants Python 2.

Bug#957186: marked as done (evolver: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 21:18:38 +
with message-id 
and subject line Bug#957186: fixed in evolver 2.70+ds-5
has caused the Debian Bug report #957186,
regarding evolver: 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.)


-- 
957186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:evolver
Version: 2.70+ds-4
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/evolver_2.70+ds-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
/usr/bin/ld: veravg.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: pixgraph.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: tmain.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: tordup.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: wulff.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: help.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: psgraph.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: check.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: utility.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: skeleton.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: storage.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: dump.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: iterate.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: filgraph.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition of `evolver_display_short_description'; 
calcforc.o:./_build/nox-d/src/../../../src/proto.h:32: first defined here
/usr/bin/ld: zoom.o:./_build/nox-d/src/../../../src/proto.h:32: multiple 
definition 

Bug#974574: nbdkit: diff for NMU version 1.22.3-1.1

[Hilko Bengen]

Hi Dominic,

thanks for your NMU. Please push your changes since 1.22.3-1 to git and
reschedule for immediate acceptance into unstable.

Cheers,
-Hilko

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

[Luke Hall]

On Sat, 14 Nov 2020 04:02:40 +0100 Markus Koschany  wrote:

Am Freitag, den 13.11.2020, 23:13 -0300 schrieb Alejandro Taboada:
> Hello Markus,
> 
> It doesn’t work. The output log is quite different. I throws a timeout and

> just at the end the “unprivileged client crmd”.
> See attached log.

I'm sorry but I uploaded an older version that missed a do_reply line. That's
why are you seeing timeouts now. Now I have uploaded the correct version from
my test server to https://people.debian.org/~apo/lts/pacemaker/


This update to buster went out over-night and didn't cause the same issues.

Start-Date: 2020-11-14  06:02:48
Commandline: /usr/bin/unattended-upgrade
Upgrade: pacemaker:amd64 (2.0.1-5, 2.0.1-5+deb10u1)
End-Date: 2020-11-14  06:03:13


OpenPGP_0xE92032F399E1C6EC.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#964688: cherry-pick patch from upstream - fixes #964688

[Andreas Tille]

Control: tags -1 pending
Control: tags 922571 pending

Hi,

I have moved sigviewer to Debian Med team[1], fixed the other bug and
tried to build the new upstream version 0.6.4 but failed:

...
g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/sigviewer-0.6.4=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=gnu++11 -D_REENTRANT -Wall -  Wextra -fPIC 
-DVERSION_MAJOR=0 -DVERSION_MINOR=6 -DVERSION_BUILD=4 -DQT_NO_DEBUG_OUTPUT 
-DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. 
-I/build/sigviewer-0.6.4/ external/include -Isrc 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/  
QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtCore -Itmp/release 
-Itmp/release -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
tmp/release/undo_redo_gui_command.o src/gui_impl/commands/ 
undo_redo_gui_command.cpp
src/gui_impl/commands/open_file_gui_command.cpp: In member function 'void 
sigviewer::OpenFileGuiCommand::importEvents()':
src/gui_impl/commands/open_file_gui_command.cpp:200:23: error: redeclaration of 
'sigviewer::FileSignalReader* file_signal_reader'
  200 | FileSignalReader* file_signal_reader = 
FileSignalReaderFactory::getInstance()->getHandler (file_path);
  |   ^~
src/gui_impl/commands/open_file_gui_command.cpp:185:23: note: 
'sigviewer::FileSignalReader* file_signal_reader' previously declared here
  185 | FileSignalReader* file_signal_reader = 
FileSignalReaderFactory::getInstance()->getHandler (file_path);
  |   ^~
make[1]: *** [Makefile:2576: tmp/release/open_file_gui_command.o] Error 1


Any help would be welcome

   Andreas.


[1] https://salsa.debian.org/med-team/sigviewer

On Sat, Nov 14, 2020 at 11:10:33AM +0200, Adrian Bunk wrote:
> Hi Andreas,
> 
> could you make an upload with one of these two solutions
> (cherry-pick fix or new upstream)?
> 
> Thanks
> Adrian
> 
> 
> On Wed, Aug 19, 2020 at 02:31:42PM +0200, Alois Schlögl wrote:
> > attached is a patch that fixes bug #964688 (FTBFS).
> > 
> > The patch corresponds to commit 93d5cec298ec6c787e45f7b3486cf47ff3461c75
> > in upstream.
> > 
> > Upgrading to sigviewer 0.6.4 would also solve this issue.
> > 
> > 
> > Best,
> >   Alois
> > 
> > 
> > 
> > 
> > 
> > 
> 
> > commit 93d5cec298ec6c787e45f7b3486cf47ff3461c75
> > Author: Alois Schloegl 
> > Date:   Wed Oct 24 00:06:10 2018 +0200
> > 
> > fix compilation on Debian 9 with Qt v5.7.1
> > 
> > diff --git a/src/file_handling/file_signal_reader.h 
> > b/src/file_handling/file_signal_reader.h
> > index eeac188..39d3207 100644
> > --- a/src/file_handling/file_signal_reader.h
> > +++ b/src/file_handling/file_signal_reader.h
> > @@ -10,6 +10,7 @@
> >  #include "base/data_block.h"
> >  #include "application_context_impl.h"
> >  
> > +#include 
> >  #include 
> >  #include 
> >  #include 
> > diff --git a/src/gui/gui_action_factory.h b/src/gui/gui_action_factory.h
> > index 07586e4..dc99c0d 100644
> > --- a/src/gui/gui_action_factory.h
> > +++ b/src/gui/gui_action_factory.h
> > @@ -12,6 +12,7 @@
> >  #include 
> >  #include 
> >  #include 
> > +#include 
> >  
> >  namespace sigviewer
> >  {
> > diff --git a/src/gui_impl/signal_browser/signal_graphics_item.cpp 
> > b/src/gui_impl/signal_browser/signal_graphics_item.cpp
> > index cc60066..0572ed1 100644
> > --- a/src/gui_impl/signal_browser/signal_graphics_item.cpp
> > +++ b/src/gui_impl/signal_browser/signal_graphics_item.cpp
> > @@ -457,8 +457,8 @@ void SignalGraphicsItem::mousePressEvent 
> > (QGraphicsSceneMouseEvent * event )
> >  //check whether a user added stream has already been 
> > existing
> >  XDFdata->userAddedStream = XDFdata->streams.size();
> >  XDFdata->streams.emplace_back();
> > -std::time_t currentTime = std::time(nullptr);
> > -std::string timeString = 
> > std::asctime(std::localtime());
> > +time_t currentTime = time(nullptr);
> > +std::string timeString = 
> > asctime(localtime());
> >  timeString.pop_back(); //we don't need '\n' at the end
> >  XDFdata->streams.back().streamHeader =
> >  ""
> 
> 

-- 
http://fam-tille.de

Processed: Re: Bug#964688: cherry-pick patch from upstream - fixes #964688

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #964688 [src:sigviewer] sigviewer: FTBFS: 
src/file_handling_impl/biosig_reader.cpp:142:10: error: ‘QFile’ has not been 
declared
Added tag(s) pending.
> tags 922571 pending
Bug #922571 [src:sigviewer] sigviewer FTCBFS: does not pass cross flags to qmake
Added tag(s) pending.

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

Bug#974751: guix: Fails to install with "guix.postinst: 5: systemd-sysusers: not found" if package systemd is not installed

[Vagrant Cascadian]

On 2020-11-14, Axel Beckert wrote:
> your recently uploaded guix package fails in the postinst script as
> follows on a system without the package systemd being installed:
>
> Setting up guix (1.2.0~rc1-1) ...
> /var/lib/dpkg/info/guix.postinst: 5: systemd-sysusers: not found
> dpkg: error processing package guix (--configure):
>  installed guix package post-installation script subprocess returned error 
> exit status 127
>
> Please try to guard that call (and/or provide an alternative code path)
> so that it also works with other init systems or even completely without
> an init system (like in a chroot).

Yes, thanks for catching that!

There are a few other issues related to the lack of proper support for
init.d scripts as well, and it would be nice to fix issues to support
other init systems... any help would be appreciated!


> If that's not possible, you probably need to add a dependency on
> "systemd | opensysusers" and check for "sysusers" or "opensysusers"
> instead of systemd-sysusers, too. opensysusers is an alternative
> implementation of systemd's sysusers that also works with other init
> systems or without init system at all.

I did ask zigo about the status of opensysusers on IRC, and got the
impression that it might be orphaned or removed from the archive, so did
not pursue further, though does not sound like it would be difficult to
add support.

Alternate to having a working sysusers.d implementation, it could be
documented in README.Debian to create the users and groups manually.

Thanks!


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#974574: nbdkit: diff for NMU version 1.22.3-1.1

[Dominic Hargreaves]

Control: tags 974574 + patch
Control: tags 974574 + pending

Dear maintainer,

I've prepared an NMU for nbdkit (versioned as 1.22.3-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Changelog:

nbdkit (1.22.3-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Temporarily stop building the torrent plugin since
libtorrent-rasterbar-dev is RC-buggy (see #956285), to allow nbdkit to
migrate to testing. The torrent plugin has never been available in
testing, so this does not represent a regression there (Closes: #974574) 

 -- Dominic Hargreaves   Sat, 14 Nov 2020 19:13:45 +

Regards.

diff -Nru nbdkit-1.22.3/debian/changelog nbdkit-1.22.3/debian/changelog
--- nbdkit-1.22.3/debian/changelog	2020-09-23 10:35:11.0 +0100
+++ nbdkit-1.22.3/debian/changelog	2020-11-14 19:13:45.0 +
@@ -1,3 +1,13 @@
+nbdkit (1.22.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Temporarily stop building the torrent plugin since
+libtorrent-rasterbar-dev is RC-buggy (see #956285), to allow nbdkit to
+migrate to testing. The torrent plugin has never been available in
+testing, so this does not represent a regression there (Closes: #974574) 
+
+ -- Dominic Hargreaves   Sat, 14 Nov 2020 19:13:45 +
+
 nbdkit (1.22.3-1) unstable; urgency=medium
 
   * New upstream version 1.22.3
diff -Nru nbdkit-1.22.3/debian/control nbdkit-1.22.3/debian/control
--- nbdkit-1.22.3/debian/control	2020-09-17 15:12:47.0 +0100
+++ nbdkit-1.22.3/debian/control	2020-11-14 16:54:20.0 +
@@ -20,7 +20,6 @@
  tcl-dev,
  libselinux1-dev,
  libssh-dev,
- libtorrent-rasterbar-dev,
  libvirt-dev,
  zlib1g-dev,
  linux-image-arm64 [arm64] ,
diff -Nru nbdkit-1.22.3/debian/nbdkit.install nbdkit-1.22.3/debian/nbdkit.install
--- nbdkit-1.22.3/debian/nbdkit.install	2020-09-10 00:38:52.0 +0100
+++ nbdkit-1.22.3/debian/nbdkit.install	2020-11-14 17:20:08.0 +
@@ -34,7 +34,6 @@
 /usr/lib/*-*/nbdkit/plugins/nbdkit-streaming-plugin.so
 /usr/lib/*-*/nbdkit/plugins/nbdkit-tar-plugin.so
 /usr/lib/*-*/nbdkit/plugins/nbdkit-tmpdisk-plugin.so
-/usr/lib/*-*/nbdkit/plugins/nbdkit-torrent-plugin.so
 /usr/lib/*-*/nbdkit/plugins/nbdkit-zero-plugin.so
 /usr/lib/*-*/nbdkit/filters
 /usr/share/man/man1/nbdkit-cdi-plugin.1
@@ -60,7 +59,6 @@
 /usr/share/man/man1/nbdkit-streaming-plugin.1
 /usr/share/man/man1/nbdkit-tar-plugin.1
 /usr/share/man/man1/nbdkit-tmpdisk-plugin.1
-/usr/share/man/man1/nbdkit-torrent-plugin.1
 /usr/share/man/man1/nbdkit-zero-plugin.1
 /usr/share/man/man3/nbdkit-cc-plugin.3
 /usr/share/man/man3/nbdkit-sh-plugin.3

Processed: nbdkit: diff for NMU version 1.22.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 974574 + patch
Bug #974574 [nbdkit] nbdkit: build-depends on libtorrent-rasterbar-dev, which 
is not in testing
Added tag(s) patch.
> tags 974574 + pending
Bug #974574 [nbdkit] nbdkit: build-depends on libtorrent-rasterbar-dev, which 
is not in testing
Added tag(s) pending.

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

Bug#974759: insighttoolkit4-python: not installable with python 3.8

[Ralf Treinen]

Package: insighttoolkit4-python
Version: 4.13.2-dfsg1-1
Severity: serious
User: trei...@debian.org
Usertag: edos-unstallable

Hi,

insighttoolkit4-python depends on python3 (< 3.8), the current version
of python3 in sid however is 3.8.6-1. The dependency is generated from
${python3:Depends} so it might be sufficient to recompile the package.

-Ralf.

Bug#954613: rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev

[Wolfgang Silbermayr]

On Sun, 8 Nov 2020 09:55:38 +0100 Sylvestre Ledru  wrote:
> Hello Wofgang,
> 
> Do you have the intention to fix process-viewer?
> 
> We have a RC bug from March on it.

Hi Sylvestre,

I updated the patch in the debcargo-conf repo on Salsa in a way that fixes the
problem.

My previous gpg subkey for signing uploads expired recently, and I uploaded
the newly generated subkey. Seems like I'll be able to perform the upload
early in December, after the new key got imported. If you'd like to see the
fix earlier, feel free to upload the update.

Best regards,
Wolfgang.

Bug#974754: libjbig0: invalid ELF header when loading libjbig.so.0

[Ryan Beethe]

Package: libjbig0
Version: 2.1-3.1+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I use libjbig indirectly through the php-gd package.  When running php
from the command line, I get the following error:

 PHP Warning:  PHP Startup: Unable to load dynamic library 'gd.so'
 (tried: /usr/lib/php/20180731/gd.so
 (/usr/lib/x86_64-linux-gnu/libjbig.so.0: invalid ELF header),
 /usr/lib/php/20180731/gd.so.so (/usr/lib/php/20180731/gd.so.so: cannot
 open shared object file: No such file or directory)) in Unknown on line
 0

I was able to fix my system by recompiling the source (with the patches
from the debian package) and overriding the broken library with the
recompiled one.

I'm not actually sure what could cause this or even how long it has been
broken.


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

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

Versions of packages libjbig0 depends on:
ii  libc6  2.28-10

libjbig0 recommends no packages.

libjbig0 suggests no packages.

-- no debconf information

Processed: severity of 967623 is serious

[Debian Bug Tracking System]

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

> severity 967623 serious
Bug #967623 [src:marionnet] marionnet: depends on deprecated GTK 2
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#974705: fence-agents test hangs

[Valentin Vidic]

One of autopkgtests in fence-agents package seems to be broken
in the same way - just hangs in wait forever and using bash works:

https://salsa.debian.org/ha-team/fence-agents/-/blob/master/debian/tests/delay

-- 
Valentin

Bug#973126: marked as done (responses: 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 Sat, 14 Nov 2020 17:18:45 +
with message-id 
and subject line Bug#973126: fixed in responses 0.12.1-1
has caused the Debian Bug report #973126,
regarding responses: 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.)


-- 
973126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: responses
Version: 0.9.0-2
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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
> 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
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> copying responses.py -> /<>/.pybuild/cpython3_3.9_responses/build
> copying test_responses.py -> 
> /<>/.pybuild/cpython3_3.9_responses/build
> running egg_info
> writing responses.egg-info/PKG-INFO
> writing dependency_links to responses.egg-info/dependency_links.txt
> writing requirements to responses.egg-info/requires.txt
> writing top-level names to responses.egg-info/top_level.txt
> reading manifest file 'responses.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*~' found anywhere in 
> distribution
> writing manifest file 'responses.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying responses.py -> /<>/.pybuild/cpython3_3.8_responses/build
> copying test_responses.py -> 
> /<>/.pybuild/cpython3_3.8_responses/build
> running egg_info
> writing responses.egg-info/PKG-INFO
> writing dependency_links to responses.egg-info/dependency_links.txt
> writing requirements to responses.egg-info/requires.txt
> writing top-level names to responses.egg-info/top_level.txt
> reading manifest file 'responses.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*~' found anywhere in 
> distribution
> writing manifest file 'responses.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_responses/build; python3.9 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> plugins: localserver-0.5.0
> collected 46 items
> 
> test_responses.py ..F... 
> [100%]
> 
> === FAILURES 
> ===
> __ test_arbitrary_status_code 
> __
> test_responses.py:345: in test_arbitrary_status_code
> run()
> :3: in wrapper
> ???
> test_responses.py:343: in run
> assert resp.reason is None
> E   assert "I'm a Teapot" is None
> E+  where "I'm a Teapot" = .reason
> === warnings summary 
> ===
> responses.py:11
> responses.py:11
>   /<>/.pybuild/cpython3_3.9_responses/build/responses.py:11: 
> DeprecationWarning: Using or importing the ABCs from 'collections' instead of 
> from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
> stop working
> from collections import namedtuple, Sequence, Sized
> 
> /usr/lib/python3/dist-packages/cookies.py:312
>   /usr/lib/python3/dist-packages/cookies.py:312: DeprecationWarning: Flags 
> not at the start of the expression '(?ix)  # Case-insens' (truncated)
> ATTR_RE = re.compile(ATTR)
> 
> .pybuild/cpython3_3.9_responses/build/test_responses.py::test_response
> 

Bug#974730: systemd 247~rc2-2 install crashed several system

[Eric Valette]

Le 14/11/2020 à 17:50, Michael Biebl a écrit :


This is very bad for remote managed Linux system with difficult
access
like in data center...


In a data center (without remote access) I would recommend *not* using
unstable, and experimental even more so. I uploaded this version to
experimental for a reason.


Sure but if this is not fixed, then it will happen just later.



While systemd does offers a far superior boot time by dependency and
//ism, this will soon become unmanageable I fear.



While I can understand if you are pissed when a remote machine has
become unreachable, this remark is unnecessary.
Please don't, this really drains my motivation.


As such bug drain my motivation for helping finding bug early enough by 
using/testing experimental so that discovered bug affects the minimum 
people.


BTW the nas is one thing, the unbootable laptop is for me even worse. I 
do not know why you downgraded severity as my system crashed during 
upgrade and was not recoverable by unexperienced people. And 
experimental is not an excuse.


-- eric

Bug#974730: systemd 247~rc2-2 install crashed several system

[Michael Biebl]

Am Samstag, den 14.11.2020, 17:00 +0100 schrieb Eric Valette:
> Le 14/11/2020 à 13:54, Michael Biebl a écrit :
> 
> > Are you configuring your NAS with ifupdown (using allow-hotplug).
> 
> Yes indeed. I use a fixed address outside my DHCP dynamic range so
> no 
> need to something sophisticated and no graphical interface so no
> need 
> for network-manager and I hate transfering all the control to
> systemd...
> 
> allow-hotplug eth0
> iface eth0 inet static
>   

Ok, thanks for confirming.
This means ifup@.service is used which has

BindsTo=sys-subsystem-net-devices-%i.device

and further confirms my theory, that this issue is related to units
with BindsTo= being stopped (and not restarted) during a
daemon-reexec due to the udev tags related changes.

> 
> This is very bad for remote managed Linux system with difficult
> access 
> like in data center...

In a data center (without remote access) I would recommend *not* using
unstable, and experimental even more so. I uploaded this version to
experimental for a reason.

> > Fwiw, that sounds very much like
> > https://github.com/systemd/systemd/issues/17605#issuecomment-727187837
> > 
> 
> While systemd does offers a far superior boot time by dependency and 
> //ism, this will soon become unmanageable I fear.
> 

While I can understand if you are pissed when a remote machine has
become unreachable, this remark is unnecessary.
Please don't, this really drains my motivation.


Regards,
Michael


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

Processed: block 974574 with 956285

[Debian Bug Tracking System]

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

> block 974574 with 956285
Bug #974574 [nbdkit] nbdkit: build-depends on libtorrent-rasterbar-dev, which 
is not in testing
974574 was not blocked by any bugs.
974574 was blocking: 968912
Added blocking bug(s) of 974574: 956285
> thanks
Stopping processing here.

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

Bug#974751: guix: Fails to install with "guix.postinst: 5: systemd-sysusers: not found" if package systemd is not installed

[Axel Beckert]

Package: guix
Version: 1.2.0~rc1-1
Severity: serious

Dear Vagrant,

your recently uploaded guix package fails in the postinst script as
follows on a system without the package systemd being installed:

Setting up guix (1.2.0~rc1-1) ...
/var/lib/dpkg/info/guix.postinst: 5: systemd-sysusers: not found
dpkg: error processing package guix (--configure):
 installed guix package post-installation script subprocess returned error exit 
status 127

Please try to guard that call (and/or provide an alternative code path)
so that it also works with other init systems or even completely without
an init system (like in a chroot).

If that's not possible, you probably need to add a dependency on
"systemd | opensysusers" and check for "sysusers" or "opensysusers"
instead of systemd-sysusers, too. opensysusers is an alternative
implementation of systemd's sysusers that also works with other init
systems or without init system at all.

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages guix depends on:
ii  guile-3.03.0.4-3
ii  guile-3.0-libs   3.0.4-3
ii  guile-gcrypt 0.3.0-2
ii  guile-git0.4.0-1
ii  guile-gnutls 3.6.15-5
ii  guile-json   4.3.2-2
ii  guile-lzlib  0.0.2-2
ii  guile-sqlite30.1.3-1
ii  guile-ssh0.13.1-3
ii  guile-zlib   0.0.1-3
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-4
ii  libgcc-s110.2.0-17
ii  libgcrypt20  1.8.7-2
ii  libgcrypt20-dev [libgcrypt-dev]  1.8.7-2
ii  libgit2-dev  1.0.1+dfsg.1-1
ii  libsqlite3-0 3.33.0-1
ii  libsqlite3-dev   3.33.0-1
ii  libssh-dev   0.9.4-2
ii  libstdc++6   10.2.0-17
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages guix recommends:
pn  nscd  

guix suggests no packages.

-- no debconf information

Processed: pcp: diff for NMU version 5.2.2-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 974704 + patch
Bug #974704 [src:pcp] pcp: FTBFS on some archs: Cannot find (any matches for) 
"usr/lib/pcp/pmdas/infiniband[...]
Added tag(s) patch.
> tags 974704 + pending
Bug #974704 [src:pcp] pcp: FTBFS on some archs: Cannot find (any matches for) 
"usr/lib/pcp/pmdas/infiniband[...]
Added tag(s) pending.

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

Bug#974704: pcp: diff for NMU version 5.2.2-1.1

[Dominic Hargreaves]

Control: tags 974704 + patch
Control: tags 974704 + pending

Dear maintainer,

I've prepared an NMU for pcp (versioned as 5.2.2-1.1) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.

I have tested this fix on i386 and the contents of the
pcp-pmda-infiniband package look plausible.

However, note that I have partially reverted a change in the last
upload to add architecture constraints to the libibumad-dev and
libibmad-dev build-deps. They were causing the build-failure and
I couldn't see why they were needed. But please let me know if this
wasn't the right fix.

Note also that this is one of the last blockers for the perl
5.32 transition which is ongoing, so any early confirmation (so that
I can reschedule the NMU) or a source-only maintainer upload would be
welcome. (In the latter case, please note that I did not touch the
d/control regeneration script in my NMU, and also note that the upload
must be source-only in order to comply with the bullseye release policy[1]

Regards,
Dominic

[1] 
diff -Nru pcp-5.2.2/debian/changelog pcp-5.2.2/debian/changelog
--- pcp-5.2.2/debian/changelog	2020-11-10 21:31:00.0 +
+++ pcp-5.2.2/debian/changelog	2020-11-14 15:02:58.0 +
@@ -1,3 +1,11 @@
+pcp (5.2.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove architecture constraints to libibumad-dev and libibmad-dev
+(closes: #974704)
+
+ -- Dominic Hargreaves   Sat, 14 Nov 2020 15:02:58 +
+
 pcp (5.2.2-1) unstable; urgency=low
 
   * Remove python3-all-dev dependency (closes: #972330)
diff -Nru pcp-5.2.2/debian/control pcp-5.2.2/debian/control
--- pcp-5.2.2/debian/control	2020-11-10 21:31:00.0 +
+++ pcp-5.2.2/debian/control	2020-11-14 15:02:53.0 +
@@ -4,7 +4,7 @@
 Homepage: https://pcp.io
 Maintainer: PCP Development Team 
 Uploaders: Nathan Scott , Ken McDonell 
-Build-Depends: bison, flex, gawk, procps, pkg-config, debhelper (>= 5), perl (>= 5.6), libreadline-dev | libreadline5-dev | libreadline-gplv2-dev, chrpath, libbsd-dev [kfreebsd-any], libkvm-dev [kfreebsd-any], python3-dev, libnspr4-dev, libnss3-dev, libsasl2-dev, libuv1-dev, libssl-dev, libavahi-common-dev, qtbase5-dev, qtbase5-dev-tools, libqt5svg5-dev, qtchooser, autotools-dev, zlib1g-dev, autoconf, libclass-dbi-perl, libdbd-mysql-perl, python3-psycopg2, dh-python, libpfm4-dev, libncurses5-dev, python3-six, python3-json-pointer, python3-requests, libextutils-autoinstall-perl, libxml-tokeparser-perl, librrds-perl, libjson-perl, libwww-perl, libnet-snmp-perl, libnss3-tools, liblzma-dev, libsystemd-dev, bpftrace (>= 0.9.2) [amd64 arm64 ppc64el], libibumad-dev [amd64 arm64 mips64el ppc64el s390x], libibmad-dev [amd64 arm64 mips64el ppc64el s390x], manpages
+Build-Depends: bison, flex, gawk, procps, pkg-config, debhelper (>= 5), perl (>= 5.6), libreadline-dev | libreadline5-dev | libreadline-gplv2-dev, chrpath, libbsd-dev [kfreebsd-any], libkvm-dev [kfreebsd-any], python3-dev, libnspr4-dev, libnss3-dev, libsasl2-dev, libuv1-dev, libssl-dev, libavahi-common-dev, qtbase5-dev, qtbase5-dev-tools, libqt5svg5-dev, qtchooser, autotools-dev, zlib1g-dev, autoconf, libclass-dbi-perl, libdbd-mysql-perl, python3-psycopg2, dh-python, libpfm4-dev, libncurses5-dev, python3-six, python3-json-pointer, python3-requests, libextutils-autoinstall-perl, libxml-tokeparser-perl, librrds-perl, libjson-perl, libwww-perl, libnet-snmp-perl, libnss3-tools, liblzma-dev, libsystemd-dev, bpftrace (>= 0.9.2) [amd64 arm64 ppc64el], libibumad-dev, libibmad-dev, manpages
 Standards-Version: 3.9.3
 X-Python3-Version: >= 3.3
 

Processed: Re: Bug#968366: libproxy#126: buffer overflow when PAC is enabled

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #968366 [src:libproxy] libproxy: CVE-2020-26154: buffer overflow when PAC 
is enabled
Ignoring request to alter tags of bug #968366 to the same tags previously set

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

Bug#968366: libproxy#126: buffer overflow when PAC is enabled

[Salvatore Bonaccorso]

Control: tags -1 + fixed-upstream

Hi,

On Thu, Aug 13, 2020 at 04:36:59PM +0100, Simon McVittie wrote:
> Source: libproxy
> Version: 0.4.14-2
> Severity: grave
> Justification: user security hole
> Tags: security upstream
> Forwarded: https://github.com/libproxy/libproxy/pull/126
> X-Debbugs-Cc: Debian Security Team 
> 
> Li Fei (@lifeibiren on Github) reported that if the server serving a PAC
> file sends more than 102400 bytes without a Content-Length present,
> libproxy can overflow its buffer by PAC_HTTP_BLOCK_SIZE (512) bytes.
> 
> This PR is said to fix it, although I have not reviewed it in detail, and
> it would be better if someone who knows C++ better than me did the review:
> 
> https://github.com/libproxy/libproxy/pull/126

FTWIW, the fix has been merged upstream.

Regards,
Salvatore

Bug#974730: systemd 247~rc2-2 install crashed several system

[Eric Valette]

Le 14/11/2020 à 13:54, Michael Biebl a écrit :


Are you configuring your NAS with ifupdown (using allow-hotplug).


Yes indeed. I use a fixed address outside my DHCP dynamic range so no 
need to something sophisticated and no graphical interface so no need 
for network-manager and I hate transfering all the control to systemd...


allow-hotplug eth0
iface eth0 inet static



This is very bad for remote managed Linux system with difficult access 
like in data center...




Fwiw, that sounds very much like
https://github.com/systemd/systemd/issues/17605#issuecomment-727187837



While systemd does offers a far superior boot time by dependency and 
//ism, this will soon become unmanageable I fear.


Thanks for the pointer...

-- eric

Bug#974745: lava: fails to install: TypeError: Abstract base class containing model fields not permitted for proxy model 'TokenProxy'

[Sebastian Ramacher]

Package: lava-server
Version: 2020.06-2
Severity: grave
X-Debbugs-Cc: sramac...@debian.org
Justification: renders package unusable

lava-server cannot be installed in unstable and hence the package is unusable:
| lava-server manage migrate --noinput --fake-initial
| Traceback (most recent call last):
|   File "/usr/bin/lava-server", line 68, in 
| main()
|   File "/usr/bin/lava-server", line 64, in main
| execute_from_command_line([sys.argv[0]] + options.command)
|   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 381, in execute_from_command_line
| utility.execute()
|   File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", 
line 375, in execute
| self.fetch_command(subcommand).run_from_argv(self.argv)
|   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
323, in run_from_argv
| self.execute(*args, **cmd_options)
|   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
361, in execute
| self.check()
|   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
387, in check
| all_issues = self._run_checks(
|   File 
"/usr/lib/python3/dist-packages/django/core/management/commands/migrate.py", 
line 65, in _run_checks
| issues.extend(super()._run_checks(**kwargs))
|   File "/usr/lib/python3/dist-packages/django/core/management/base.py", line 
377, in _run_checks
| return checks.run_checks(**kwargs)
|   File "/usr/lib/python3/dist-packages/django/core/checks/registry.py", line 
72, in run_checks
| new_errors = check(app_configs=app_configs)
|   File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 13, 
in check_url_config
| return check_resolver(resolver)
|   File "/usr/lib/python3/dist-packages/django/core/checks/urls.py", line 23, 
in check_resolver
| return check_method()
|   File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 399, 
in check
| for pattern in self.url_patterns:
|   File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
| res = instance.__dict__[self.name] = self.func(instance)
|   File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 584, 
in url_patterns
| patterns = getattr(self.urlconf_module, "urlpatterns", 
self.urlconf_module)
|   File "/usr/lib/python3/dist-packages/django/utils/functional.py", line 80, 
in __get__
| res = instance.__dict__[self.name] = self.func(instance)
|   File "/usr/lib/python3/dist-packages/django/urls/resolvers.py", line 577, 
in urlconf_module
| return import_module(self.urlconf_name)
|   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
| return _bootstrap._gcd_import(name[level:], package, level)
|   File "", line 1014, in _gcd_import
|   File "", line 991, in _find_and_load
|   File "", line 975, in _find_and_load_unlocked
|   File "", line 671, in _load_unlocked
|   File "", line 783, in exec_module
|   File "", line 219, in _call_with_frames_removed
|  File "/usr/lib/python3/dist-packages/lava_rest_app/urls.py", line 22, in 

| from lava_rest_app.base.views import LavaObtainAuthToken
|   File "/usr/lib/python3/dist-packages/lava_rest_app/base/views.py", line 51, 
in 
| from rest_framework.authtoken.views import ObtainAuthToken
|   File "/usr/lib/python3/dist-packages/rest_framework/authtoken/views.py", 
line 2, in 
| from rest_framework.authtoken.models import Token
|   File "/usr/lib/python3/dist-packages/rest_framework/authtoken/models.py", 
line 43, in 
| class TokenProxy(Token):
|   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 172, 
in __new__
| raise TypeError(
| TypeError: Abstract base class containing model fields not permitted for 
proxy model 'TokenProxy'.
| migration
| dpkg: error processing package lava-server (--configure):
|  installed lava-server package post-installation script subprocess returned 
error exit status 1

This issue also causes lava's autopkgtests to fail:
https://ci.debian.net/data/autopkgtest/testing/amd64/l/lava/8152337/log.gz

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#931342: closing 931342

[Salvatore Bonaccorso]

close 931342 8:6.9.11.24+dfsg-1
thanks

Bug#974593: marked as done (libavif8-gdk-pixbuf: missing Breaks+Replaces: libavif7-gdk-pixbuf)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 15:04:21 +
with message-id 
and subject line Bug#974593: fixed in libavif 0.8.3-3
has caused the Debian Bug report #974593,
regarding libavif8-gdk-pixbuf: missing Breaks+Replaces: libavif7-gdk-pixbuf
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.)


-- 
974593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libavif8-gdk-pixbuf
Version: 0.8.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libavif8-gdk-pixbuf_0.8.3-1_amd64.deb ...
  Unpacking libavif8-gdk-pixbuf:amd64 (0.8.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libavif8-gdk-pixbuf_0.8.3-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-avif.so',
 which is also in package libavif7-gdk-pixbuf:amd64 0.8.2-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libavif8-gdk-pixbuf_0.8.3-1_amd64.deb

Since libavif7-gdk-pixbuf is gone, the Breaks+Replaces can be unversioned.


cheers,

Andreas


libavif7-gdk-pixbuf=0.8.2-4_libavif8-gdk-pixbuf=0.8.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libavif
Source-Version: 0.8.3-3
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated libavif 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: Sat, 14 Nov 2020 09:22:15 -0500
Source: libavif
Architecture: source
Version: 0.8.3-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Boyuan Yang 
Closes: 974593
Changes:
 libavif (0.8.3-3) unstable; urgency=high
 .
   * Let libavif8-gdk-pixbuf Breaks+Replaces libavif7-gdk-pixbuf.
 (Closes: #974593)
Checksums-Sha1:
 0498084a3673f579d0c7b7091e8a5ddfc0264bc4 2304 libavif_0.8.3-3.dsc
 7a5d467c2477fdbba5655a87d66d631703898500 2948213 libavif_0.8.3.orig.tar.gz
 ba30ddfdda0ba6ef64e851de1b6dae95e9974e66 5160 libavif_0.8.3-3.debian.tar.xz
 8c4778a8f6cdd55e189b8b12c5b435e2a37be273 10537 libavif_0.8.3-3_amd64.buildinfo
Checksums-Sha256:
 36b29e180a44c0b0d98f929e2e2e91676c8d2145a18adcae4defad9d45c0 2304 
libavif_0.8.3-3.dsc
 0527720a493a08cfcd56cae2fe10e8c674112ebf1a6e1c30d38fca5bb2a504b2 2948213 
libavif_0.8.3.orig.tar.gz
 4cb0be834dfc049ec9769eb2620665936e3523e6659eefec2e6cd2cbd84f7598 5160 
libavif_0.8.3-3.debian.tar.xz
 b8c27a5f6a1a1578d2fb1ffc81a86dc080d68fadcdcea658e025d98ebc6977eb 10537 
libavif_0.8.3-3_amd64.buildinfo
Files:
 e2db67a1c4c341ddf222aff0a35ecdb2 2304 libs optional libavif_0.8.3-3.dsc
 c6fee6142fa3359a9a72927d7473cf76 2948213 libs optional 
libavif_0.8.3.orig.tar.gz
 c282264b98b5a1d926c9d58c8a6d098e 5160 libs optional 
libavif_0.8.3-3.debian.tar.xz
 07f0304b207ac2775796d0c5ae13fabf 10537 libs optional 
libavif_0.8.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl+v6IcACgkQwpPntGGC
Ws63zRAApw78HKwk1hpt9iHC3u/Yi+cj4vrCU6FjW6RPktU8cXtIOzB5ui3HshqX
f8NXE2TyqP5t/fMnB//21M4oaMKdaLaXKCV+Ko7ObHrtaVGuxXwdiCca2Rhj0M9v
hJru9wVs3Sq2RC8pZVvFf8XFoQrzSbm/c1k2X+fr0o8l9rCRdo+VlqOgw6Bp0zZq
9Qnam06exsPJ5v+zq1EQQsuz3zvVc8wHAEqOCygq85mq7WomNzj5657laEu8y6VF
F3ugbexPmiEatxM2w2J3WRDwUv0kXo/FAJvqUSJGAb3/VNTlSKm/JhDllBwiNFXy
mtVX7VCc6yX9skzx1Bs78j69z3/vg4oZgwba5zeX76Z1vNTI27fz80E/SUMEvD62
WqH9q9FlZJQuoNA2rSwxrl/zmezb+WjfV0fbE5cWqQhkH+MDhYRZ0NKuj7xDwNsN
RipXt7qBo0ct4q6Ffh5bLk/ZzOgDvVU23bmkRadNepOgx/lgXcP7hiEIrxj597mZ

Processed: closing 931342

[Debian Bug Tracking System]

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

> close 931342 8:6.9.11.24+dfsg-1
Bug #931342 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-13137
Marked as fixed in versions imagemagick/8:6.9.11.24+dfsg-1.
Bug #931342 {Done: =?utf-8?q?Moritz_M=C3=BChlenhoff?= } 
[src:imagemagick] imagemagick: CVE-2019-13137
Bug 931342 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: limit source to tulip, tagging 592120, tagging 973988, tagging 423486, tagging 750961, tagging 354887 ...

[Debian Bug Tracking System]

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

> limit source tulip
Limiting to bugs with field 'source' containing at least one of 'tulip'
Limit currently set to 'source':'tulip'

> tags 592120 + pending
Bug #592120 [tulip] tulip: Segfault when pressing Ctrl-n, or trying to import a 
dot file
Ignoring request to alter tags of bug #592120 to the same tags previously set
> tags 973988 + pending
Bug #973988 [tulip] tulip: Wrong link to the DejaVuSans.ttf font
Ignoring request to alter tags of bug #973988 to the same tags previously set
> tags 423486 + pending
Bug #423486 [tulip] tulip segfault when adding a node
Ignoring request to alter tags of bug #423486 to the same tags previously set
> tags 750961 + pending
Bug #750961 [tulip] tulip: Rendered graph image is corrupted
Ignoring request to alter tags of bug #750961 to the same tags previously set
> tags 354887 + pending
Bug #354887 [tulip] tulip: segfault on import
Ignoring request to alter tags of bug #354887 to the same tags previously set
> tags 972917 + pending
Bug #972917 [src:tulip] tulip ftbfs with python3.9
Ignoring request to alter tags of bug #972917 to the same tags previously set
> tags 973996 + pending
Bug #973996 [tulip] tulip: missing dependency -> python3-sip
Ignoring request to alter tags of bug #973996 to the same tags previously set
> tags 401748 + pending
Bug #401748 [tulip] tulip: segfault on (dot) import
Ignoring request to alter tags of bug #401748 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
354887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354887
401748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401748
423486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423486
592120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592120
750961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750961
972917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972917
973988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973988
973996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to tulip, tagging 972917, tagging 423486, tagging 973996, tagging 750961, tagging 354887 ...

[Debian Bug Tracking System]

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

> limit source tulip
Limiting to bugs with field 'source' containing at least one of 'tulip'
Limit currently set to 'source':'tulip'

> tags 972917 + pending
Bug #972917 [src:tulip] tulip ftbfs with python3.9
Added tag(s) pending.
> tags 423486 + pending
Bug #423486 [tulip] tulip segfault when adding a node
Added tag(s) pending.
> tags 973996 + pending
Bug #973996 [tulip] tulip: missing dependency -> python3-sip
Added tag(s) pending.
> tags 750961 + pending
Bug #750961 [tulip] tulip: Rendered graph image is corrupted
Added tag(s) pending.
> tags 354887 + pending
Bug #354887 [tulip] tulip: segfault on import
Added tag(s) pending.
> tags 973988 + pending
Bug #973988 [tulip] tulip: Wrong link to the DejaVuSans.ttf font
Added tag(s) pending.
> tags 401748 + pending
Bug #401748 [tulip] tulip: segfault on (dot) import
Added tag(s) pending.
> tags 592120 + pending
Bug #592120 [tulip] tulip: Segfault when pressing Ctrl-n, or trying to import a 
dot file
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
354887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354887
401748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401748
423486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423486
592120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592120
750961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750961
972917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972917
973988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973988
973996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to tulip, tagging 973988, tagging 972917, tagging 354887, tagging 423486, tagging 592120 ...

[Debian Bug Tracking System]

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

> limit source tulip
Limiting to bugs with field 'source' containing at least one of 'tulip'
Limit currently set to 'source':'tulip'

> tags 973988 + pending
Bug #973988 [tulip] tulip: Wrong link to the DejaVuSans.ttf font
Ignoring request to alter tags of bug #973988 to the same tags previously set
> tags 972917 + pending
Bug #972917 [src:tulip] tulip ftbfs with python3.9
Ignoring request to alter tags of bug #972917 to the same tags previously set
> tags 354887 + pending
Bug #354887 [tulip] tulip: segfault on import
Ignoring request to alter tags of bug #354887 to the same tags previously set
> tags 423486 + pending
Bug #423486 [tulip] tulip segfault when adding a node
Ignoring request to alter tags of bug #423486 to the same tags previously set
> tags 592120 + pending
Bug #592120 [tulip] tulip: Segfault when pressing Ctrl-n, or trying to import a 
dot file
Ignoring request to alter tags of bug #592120 to the same tags previously set
> tags 401748 + pending
Bug #401748 [tulip] tulip: segfault on (dot) import
Ignoring request to alter tags of bug #401748 to the same tags previously set
> tags 750961 + pending
Bug #750961 [tulip] tulip: Rendered graph image is corrupted
Ignoring request to alter tags of bug #750961 to the same tags previously set
> tags 973996 + pending
Bug #973996 [tulip] tulip: missing dependency -> python3-sip
Ignoring request to alter tags of bug #973996 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
354887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354887
401748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401748
423486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423486
592120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592120
750961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750961
972917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972917
973988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973988
973996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#970471: marked as done (bibletime: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 14:33:41 +
with message-id 
and subject line Bug#970471: fixed in bibletime 3.0-3
has caused the Debian Bug report #970471,
regarding bibletime: FTBFS on mips64el
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.)


-- 
970471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bibletime
Severity: import
Tags: ftbfs

The mips64el build fails with:

/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -flto -fno-fat-lto-objects -Wl,-z,relro -Wl,-z,now ...
/usr/bin/ld: /tmp/bibletime.hEI8hx.ltrans9.ltrans.o: .symtab local
symbol at index 536 (>= sh_info of 65)
/usr/bin/ld: /tmp/bibletime.hEI8hx.ltrans9.ltrans.o: error adding
symbols: bad value
collect2: error: ld returned 1 exit status
--- End Message ---
--- Begin Message ---
Source: bibletime
Source-Version: 3.0-3
Done: robe...@debian.org (=?utf-8?q?Roberto_C=2E_S=C3=A1nchez?=)

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

Debian distribution maintenance software
pp.
Roberto C. Sánchez  (supplier of updated bibletime 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: Sat, 14 Nov 2020 08:36:18 -0500
Source: bibletime
Architecture: source
Version: 3.0-3
Distribution: unstable
Urgency: medium
Maintainer: CrossWire Packaging Team 

Changed-By: Roberto C. Sánchez 
Closes: 970471
Changes:
 bibletime (3.0-3) unstable; urgency=medium
 .
   [ Bastian Germann ]
   * Team upload
   * Revert "Add two upstream patches"
   * Add missing qml-module-qtquick2 dependency
   * Disable lto-partition on mips64el (Closes: #970471)
Checksums-Sha1:
 be7e80d1f0fb51576ef859c9f3569dc80b06125d 2556 bibletime_3.0-3.dsc
 6acc445200b7523e272e29b5cb5451277e2b6350 19588 bibletime_3.0-3.debian.tar.xz
 94a2f9a0c5c058b22e6062b0b32a479d59ad6f42 15695 bibletime_3.0-3_amd64.buildinfo
Checksums-Sha256:
 4aa5dafc12f6f9bc52754c9a1a88477ff0df5117bc018c66f9997deca341d08f 2556 
bibletime_3.0-3.dsc
 8c8ae73f3c1c26a63135b80dc4fb8d088aa1ab2ff75d4e81dd3b97f7c3179790 19588 
bibletime_3.0-3.debian.tar.xz
 713cffe60cdeeda04ea2edfe327bdbc71cfa8450fdfb839e08044324b89e1265 15695 
bibletime_3.0-3_amd64.buildinfo
Files:
 45750d359480780b97dae3ed73f60800 2556 kde optional bibletime_3.0-3.dsc
 2c200b2cf43878ace818e5a9a0f47afe 19588 kde optional 
bibletime_3.0-3.debian.tar.xz
 6a1482d13ef55e120c62005d7388686f 15695 kde optional 
bibletime_3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEz9ERzDttUsU/BH8iLNd4Xt2nsg8FAl+v4asACgkQLNd4Xt2n
sg9Frw//UlXp5i8fOfZYODPltv7fFKJnMqoVlTaS0XMwCuclOVpsd4/01ADhHE45
YVypYw5/74ng5A3ENNelT2HjS5pbDyPbMC11eavKX3/AyGQe6a6/KBpqQ4TBJ9ku
MwPvJ32tSKZtVqp0FS2omfZtlTjRPqZgWyKGVKsIqfLdG5oenja9JE9kpMlvuhAK
mgkopPn1aDpsP8VjskVW/pXkl+0fmcwqansYlyRB7h7wbch9opySOSevPSiDcPmi
ddo8oMJom40/Pfxc1VPRtxq5Jtxjt6ezHwGSRz5ty+PZhEWZHmR4IAUgR2/0PqGG
NeEpVW+ESm6I5Iez1jrvevqDOP9nzeO2KL+63nMgTY5CcYfA5Vx5OVkruGkeUaRE
jhO1pNPVCnGXfp7YRcFVzKTT/U3h2ZzDkGmuyA/avfXNIIHU9qTJkL2I32gD7Amr
Vh21P+lgWL9naUIhERNui1byZyKt0Bw/+/V+Ut025FL6PDkG4I6WNex9JzhGgTZs
XQQEr7Nq73uxH9hQOd3G0cm0H9cIeNWuFmPJ7Vpjh0gPawR+y7uOWPvSH1DCmCip
f0Ebivk8RJOEUloUIkqKbJhZpEgulU64G8cst0Ssil8osj2xgOeeF4Q5MbzSnh7c
2p6sbKdi4HcWj6NDFMMTQyLk78uqG1SKlHV3GFmf0lV5rr0ytzI=
=MrDn
-END PGP SIGNATURE End Message ---

Bug#974073: Help with an arm64 specific gcc internal error with polymake

[Dominic Hargreaves]

On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote:
> During the perl 5.32 transition we observed a build failure on arm64 which
> is reproducible on the porterbox and at lease three different buidds::
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974073
> 
> However Matthias Klose (and I) tried to isolate the problem using the
> expanded source and that doesn't fail:
> 
> g++ -c -std=c++14 -g -O2 -fPIC -fstack-protector-strong -ftemplate-depth=200 
> -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op -Wconversion 
> -Wzero-as-null-pointer-constant -Wno-parentheses -Wno-error=unused-function 
> -Wno-stringop-overflow -Wno-array-bounds SparseMatrix-2.ii
> 
> (source file attached).
> 
> Can anyone help try and pin this down?

Matthias theorized that this could be the OOM killer, which is why
it doesn't happen when built sequentially.

Does anyone have access to a higher RAM machine than the buildds
and amdahl (11GiB) that could help test this theory (and maybe do a
porter upload to unblock the issue for the perl transition?

Cheers
Dominic

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

[Rafael Laboissière]

* Sebastian Ramacher  [2020-11-14 12:40]:

I couldn't push them directly, so I've created a MR: 
https://salsa.debian.org/pkg-octave-team/octave-database/-/merge_requests/1


Great, thanks. It is merged now.

Best,

Rafael Laboissière

Bug#974705: New dash package breaks systemds timedated test (hangs in wait)

[Michael Biebl]

On Sat, 14 Nov 2020 02:37:31 +0100 Michael Biebl 
wrote:

> Afaics, the sh script get's stuck at the "wait" call at
> 
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/tests/timedated#L166
> 
> Downgrading dash to 0.5.10.2-7 makes the test pass again.

Using /bin/bash is also sufficient, to make this test pass.
 
> Thus filing with RC to hopefully prevent testing migration until the
> root cause is found.

It seems I was not quick enough for that.



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

Bug#974099: marked as pending in octave-database

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #974099 in octave-database 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/pkg-octave-team/octave-database/-/commit/4bfc7b345901e849bc931610933658ce16163af3


debian/{control,tests}/: Run tests with default postgresql version (Closes: 
#974099)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974099

Processed: Bug#974099 marked as pending in octave-database

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974099 [src:octave-database] octave-database build depends on 
postgresql-12 that will not be in bullseye
Ignoring request to alter tags of bug #974099 to the same tags previously set

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

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Dominic Hargreaves]

On Sat, Nov 14, 2020 at 03:01:10PM +0100, Marco d'Itri wrote:
> On Nov 14, Dominic Hargreaves  wrote:
> 
> > This seems to be same as #953562 which was reported in March.
> Why do you think that this is the same?

The symptoms seem identical, at least. Maybe there is more than one
root cause that I'm not aware of - feel free to unmerge if you don't
think the new problem is caused by Replaces not working.

Thanks
Dominic

Bug#974738: fwupd: FTBFS on various architectures

[Limonciello, Mario]

Yes, I'm aware. I fixed all but ppc64le in the upstream packaging. That one is 
under discussion. Will wait until that one is also fixed for next upload.

Get Outlook for Android


From: Salvatore Bonaccorso 
Sent: Saturday, November 14, 2020 7:33:16 AM
To: Debian Bug Tracking System 
Subject: Bug#974738: fwupd: FTBFS on various architectures


[EXTERNAL EMAIL]

Source: fwupd
Version: 1.5.1-1
Severity: serious
Tags: ftbfs
Justification: fails to builds from source on various architectures
X-Debbugs-Cc: car...@debian.org

Hi

The last upload of fwupd fails to build on various architectures:

https://buildd.debian.org/status/logs.php?pkg=fwupd=1.5.1-1=sid

Regards,
Salvatore

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Marco d'Itri]

On Nov 14, Dominic Hargreaves  wrote:

> This seems to be same as #953562 which was reported in March.
Why do you think that this is the same?

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#970471: [pkg-crosswire-devel] Bug#970471: RFS: bibletime [RC]

[Roberto C . Sánchez]

On Sat, Nov 14, 2020 at 02:00:05PM +0100, Bastian Germann wrote:
> The fix from Adrian is now applied on salsa. Who wants to upload
> bibletime 3.0-3?
> 
I have just built and uploaded the package.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Processed: affects 974552

[Debian Bug Tracking System]

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

> affects 974552 perl-base
Bug #974552 [libcrypt1] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Bug #953562 [libcrypt1] libcrypt1 should ship file in /usr, Replaces is useless
Added indication that 974552 affects perl-base
Added indication that 953562 affects perl-base
> thanks
Stopping processing here.

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

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Dominic Hargreaves]

Control: reassign -1 libcrypt1
Control: forcemerge -1 953562

On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> 
> > Control: reassign -1 perl-base
> > Control: affects -1 upgrade-reports
> > Control: severity -1 grave
> >
> > Hi Perl team,
> >
> > I have reassigned this bug to perl because perl-base being essential
> > must remain functional during an upgrade and AFAICT perl-base fails in
> > this case here.
> >
> > If it is a direct linkage, then you might be needing a Pre-Depends.  If
> > it is an indirect linkage then I am not sure how to fix it. :-/
> 
> I don't think perl-base is doing anything wrong here, it already uses
> Pre-Depends.  AFAICS the problem is that libcrypt.so.1 can temporarily
> go missing if libc6 2.31-4 is unpacked before libcrypt1, breaking the
> assumption that binaries from essential packages are always usable.
> 
> I don't have a good idea how to fix that, though. :-(

Right - perl-base 5.32.0-5 has the following:

Pre-Depends: libc6 (>= 2.29), libcrypt1 (>= 1:4.1.0)

I don't think we can do anything about this on the perl side, so
reassigning to libcrypt.

This seems to be same as #953562 which was reported in March.

Processed: Re: Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libcrypt1
Bug #974552 [perl-base] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Bug reassigned from package 'perl-base' to 'libcrypt1'.
Ignoring request to alter found versions of bug #974552 to the same values 
previously set
Ignoring request to alter fixed versions of bug #974552 to the same values 
previously set
> forcemerge -1 953562
Bug #974552 [libcrypt1] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Bug #953562 [libcrypt1] libcrypt1 should ship file in /usr, Replaces is useless
Severity set to 'grave' from 'serious'
Added indication that 953562 affects upgrade-reports
Bug #974552 [libcrypt1] upgrade-reports: libc6/libcrypt split breaks perl 
during buster->bullseye upgrade
Marked as found in versions libxcrypt/1:4.4.15-1.
Merged 953562 974552

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

Bug#970471: [pkg-crosswire-devel] Processed: reopen

[Roberto C . Sánchez]

On Sat, Nov 14, 2020 at 02:35:51PM +0200, Adrian Bunk wrote:
> Control: found -1 3.0-1
> Control: severity -1 serious
> Control: tags -1 patch
> 
> On Mon, Sep 21, 2020 at 04:45:45PM -0400, Roberto C. Sánchez wrote:
> >...
> > I spent some time on this today and thanks to a suggestion from someone
> > in IRC, I was able to determine that removing link-time optimization
> > fixed the mips64el build.  Specifically, these lines had to be removed:
> > 
> > -SET_TARGET_PROPERTIES("${target}" PROPERTIES
> > -INTERPROCEDURAL_OPTIMIZATION TRUE)
> >...
> 
> After some further debugging I ended up with the workaround below.
> 

Adrian,

Thanks so much for taking the time to debug this and submit a patch.
Your effort is very much appreciated.

Bastian has already committed the patch to our Salsa repository and an
upload will be on the way shortly.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

[Matteo Settenvini]

The problem suddenly become worse.

Now that fwupd 1.5.1 has landed in sid, and some dependencies
apparently changed, the fwupd-amd64-signed package holding off fwupd
upgrade and forcing it to stay at version 1.4.6-2, is breaking the
system:

nov 14 14:29:52 rosebud kernel: fwupd[11192]: segfault at 8 ip
56035dbcc548 sp 7ffddfa64b00 error 4 in
fwupd[56035dbaf000+2]
nov 14 14:29:52 rosebud kernel: Code: c7 44 24 08 00 00 00 00 66 2e 0f
1f 84 00 00 00 00 00 48 8b 11 8b 44 24 10 be 01 00 00 00 4c 8b 34 c2>
nov 14 14:29:52 rosebud systemd[1]: fwupd.service: Main process exited,
code=killed, status=11/SEGV

This goes away after uninstalling the fwupd-amd64-signed package and
installing fwupd 1.5.1, but of course on a system with SecureBoot
enabled, this is not helping much if you have pending BIOS updates.

Cheers,
Matteo


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

Bug#974738: fwupd: FTBFS on various architectures

[Salvatore Bonaccorso]

Source: fwupd
Version: 1.5.1-1
Severity: serious
Tags: ftbfs
Justification: fails to builds from source on various architectures
X-Debbugs-Cc: car...@debian.org

Hi

The last upload of fwupd fails to build on various architectures:

https://buildd.debian.org/status/logs.php?pkg=fwupd=1.5.1-1=sid

Regards,
Salvatore

Bug#963947: marked as done (gcc-10-cross-mipsen: FTBFS: empty variable name)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 21:25:47 +0800
with message-id <7c4908ed-58bc-4fcc-9fe2-6fa8e161d...@gmail.com>
and subject line Re: gcc-10-cross-mipsen: FTBFS: empty variable name
has caused the Debian Bug report #963947,
regarding gcc-10-cross-mipsen: FTBFS: empty variable name
to be marked as done.

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

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


-- 
963947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963947
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-10-cross-mipsen
Version: 2+c1
Severity: serious
Tags: ftbfs

This package fails to build on current sid.

  Command: dpkg-buildpackage -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package gcc-10-cross-mipsen
  dpkg-buildpackage: info: source version 2+c1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by YunQiang Su 
   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  debian/rules:6: *** empty variable name.  Stop.
  dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2
 

This was presumably broken by the backward incompatible changes in
make_4.3-1.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
On Mon, 29 Jun 2020 06:30:47 +0300 Niko Tyni  wrote:
> Source: gcc-10-cross-mipsen
> Version: 2+c1
> Severity: serious
> Tags: ftbfs
> 
> This package fails to build on current sid.

This bug has been fixed by 3+c1.

> 
>   Command: dpkg-buildpackage -us -uc -b -rfakeroot
>   dpkg-buildpackage: info: source package gcc-10-cross-mipsen
>   dpkg-buildpackage: info: source version 2+c1
>   dpkg-buildpackage: info: source distribution unstable
>   dpkg-buildpackage: info: source changed by YunQiang Su 
>dpkg-source --before-build .
>   dpkg-buildpackage: info: host architecture amd64
>fakeroot debian/rules clean
>   debian/rules:6: *** empty variable name.  Stop.
>   dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
> exit status 2
>  
> 
> This was presumably broken by the backward incompatible changes in
> make_4.3-1.
> -- 
> Niko Tyni   nt...@debian.org
> 
> --- End Message ---

Processed: Re: Bug#960837: opendht: Need -latomic on at least RISC-V architecture

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #960837 [src:opendht] opendht: Need -latomic on at least RISC-V architecture
Added tag(s) patch.

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

Bug#960837: opendht: Need -latomic on at least RISC-V architecture

[Adrian Bunk]

Control: tags -1 patch

On Sun, Nov 08, 2020 at 09:53:53AM +0200, Juhani Numminen wrote:
> Control: reassign -1 src:opendht 2.1.1-1
> Control: severity -1 serious
> Control: tags -1 +ftbfs
> 
> On Sun, 17 May 2020 14:31:40 +0200 Petter Reinholdtsen  
> wrote:
> > 
> > I had a look at the build failure on RISC-V, as reported by the
> > autobuilders[1], and the problem seem to be that -latomic is not used
> > during linking.
> > 
> >  [1] https://buildd.debian.org/status/package.php?p=opendht >
> 
> The build failures with this message, undefined reference to 
> `__atomic_exchange_8',
> are now happening on two release architectures, armel and mipsel.

Fix/workaround below.

> Regards,
> Juhani

cu
Adrian

--- debian/rules.old2020-11-14 12:04:18.032821426 +
+++ debian/rules2020-11-14 12:07:45.514909271 +
@@ -3,6 +3,10 @@
 
 # Hardening
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc riscv64 sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 

Processed: severity of 974730 is grave

[Debian Bug Tracking System]

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

> severity 974730 grave
Bug #974730 [systemd] systemd 247~rc2-2 install crashed several system
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.

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

Bug#970471: RFS: bibletime [RC]

[Bastian Germann]

The fix from Adrian is now applied on salsa. Who wants to upload
bibletime 3.0-3?

Bug#974730: systemd 247~rc2-2 install crashed several system

[Michael Biebl]

On Sat, 14 Nov 2020 11:56:25 +0100 Eric Valette 
wrote:
> Package: systemd
> Version: 247~rc2-2
> Severity: critical
> Justification: breaks the whole system
> 
> I have updated several machine with experimental version and they did
break for
> various reasosn during install:
> 
>   1) One is a NAS that I was updating via ssh. during update, the
ssh session closed,
>   it was impossible to open a new one, and as the machine is
headless, very difficult to
>   know what happened. The power button did an acpi shutdwon and
the machine
>   did restart, but trying to do apt-get -f install, I have been
prompted to do a
>   dpkg --configure -a because update was interrupted.  After that
the machine was
>   operationnal again
>   2) One was a laptop, running a very recent kernel 5.9.8, This
time i did update
>   logged on a X11 kde konsole. During update, the entire X
session crashed, virtual
>   terminal were unreachable, remote login was impossible. Doing a
CTRL-ALT-DEL,
>   somehow did shutdown the machine but rebooting was impossible.
I had to select
>   an old kernel with its own initramfs, and to downgrade systemd
to the one from
>   unstable to get things back on order.

Are you configuring your NAS with ifupdown (using allow-hotplug).

Fwiw, that sounds very much like 
https://github.com/systemd/systemd/issues/17605#issuecomment-727187837


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

Bug#974704: pcp: FTBFS on some archs: Cannot find (any matches for) "usr/lib/pcp/pmdas/infiniband[...]

[Dominic Hargreaves]

On Sat, Nov 14, 2020 at 12:35:04AM +, Dominic Hargreaves wrote:
> This package FTBFS on the architectures which don't have bpftrace as a
> dependency since:

...

Also, if you do do another upload, please can you do a source-only
upload or make sure that you build on an up-to-date sid (the upload
on Wednesday was built against perl 5.30 on amd64).

Thanks
Dominic

Processed: Re: Bug#970471: [pkg-crosswire-devel] Processed: reopen

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.0-1
Bug #970471 [bibletime] bibletime: FTBFS on mips64el
Marked as found in versions bibletime/3.0-1.
> severity -1 serious
Bug #970471 [bibletime] bibletime: FTBFS on mips64el
Severity set to 'serious' from 'normal'
> tags -1 patch
Bug #970471 [bibletime] bibletime: FTBFS on mips64el
Added tag(s) patch.

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

Bug#966965: marked as done (dune-grid-glue: FTBFS: terminate called after throwing an instance of 'Dune::Exception')

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 11:48:22 +
with message-id 
and subject line Bug#966965: fixed in dune-grid-glue 2.7.0-3
has caused the Debian Bug report #966965,
regarding dune-grid-glue: FTBFS: terminate called after throwing an instance of 
'Dune::Exception'
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.)


-- 
966965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dune-grid-glue
Version: 2.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> make[5]: Nothing to be done for 'CMakeFiles/build_tests.dir/build'.
> make[5]: Leaving directory '/<>/build'
> [100%] Built target build_tests
> make[4]: Leaving directory '/<>/build'
> /usr/bin/cmake -E cmake_progress_start /<>/build/CMakeFiles 0
> make[3]: Leaving directory '/<>/build'
> make[2]: Leaving directory '/<>/build'
> cd build; PATH=/<>/debian/tmp-test:$PATH /usr/bin/dune-ctest 
>Site: ip-172-31-4-50
>Build name: Linux-c++
> Create new tag: 20200802-1723 - Experimental
> Test project /<>/build
>   Start  1: callmergertwicetest
>  1/12 Test  #1: callmergertwicetest    Passed0.00 sec
>   Start  2: ringcommtest
>  2/12 Test  #2: ringcommtest ...   Passed0.32 sec
>   Start  3: ringcommtest-mpi-2
>  3/12 Test  #3: ringcommtest-mpi-2 .***Failed2.27 sec
> SIZE: 2
> 0: COMM 0x558be8fd81c0
> 0 Start Communication, size 2
> SIZE: 2
> 1: COMM 0x55f1640f31c0
> 1 Start Communication, size 2
> 0 maxSize done... 
> 1 maxSize done... 
> 0: size = 2
> 0: left = 1 right = 1
> 0: next = 1
> 1: size = 2
> 1: left = 0 right = 0
> 1: next = 0
> terminate called after throwing an instance of 'Dune::Exception'
> terminate called after throwing an instance of 'Dune::Exception'
>   what():  Dune::Exception 
> [eh:/<>/dune/grid-glue/test/ringcommtest.cc:24]: MPI ERROR -- 
> MPI_ERR_TAG: invalid tag
>   what():  Dune::Exception 
> [eh:/<>/dune/grid-glue/test/ringcommtest.cc:24]: MPI ERROR -- 
> MPI_ERR_TAG: invalid tag
> [ip-172-31-4-50:19859] *** Process received signal ***
> [ip-172-31-4-50:19860] *** Process received signal ***
> [ip-172-31-4-50:19859] Signal: Aborted (6)
> [ip-172-31-4-50:19859] Signal code:  (-6)
> [ip-172-31-4-50:19860] Signal: Aborted (6)
> [ip-172-31-4-50:19860] Signal code:  (-6)
> [ip-172-31-4-50:19859] [ 0] [ip-172-31-4-50:19860] [ 0] 
> /lib/x86_64-linux-gnu/libc.so.6(+0x3bd30)[0x7fafcbac6d30]
> [ip-172-31-4-50:19859] [ 1] 
> /lib/x86_64-linux-gnu/libc.so.6(+0x3bd30)[0x7fd42a3f2d30]
> [ip-172-31-4-50:19860] [ 1] 
> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fd42a3f2cb1]
> [ip-172-31-4-50:19860] [ 2] 
> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fafcbac6cb1]
> [ip-172-31-4-50:19859] [ 2] 
> /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7fd42a3dc537]
> [ip-172-31-4-50:19860] [ 3] 
> /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7fafcbab0537]
> [ip-172-31-4-50:19859] [ 3] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x9a80c)[0x7fd42a63080c]
> [ip-172-31-4-50:19860] [ 4] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x9a80c)[0x7fafcbd0480c]
> [ip-172-31-4-50:19859] [ 4] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa58f6)[0x7fd42a63b8f6]
> [ip-172-31-4-50:19860] [ 5] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa58f6)[0x7fafcbd0f8f6]
> [ip-172-31-4-50:19859] [ 5] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa5961)[0x7fafcbd0f961]
> [ip-172-31-4-50:19859] [ 6] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa5961)[0x7fd42a63b961]
> [ip-172-31-4-50:19860] [ 6] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa5bf5)[0x7fd42a63bbf5]
> [ip-172-31-4-50:19860] [ 7] 
> /<>/build/dune/grid-glue/test/ringcommtest(+0x3386)[0x55f1640ee386]
> [ip-172-31-4-50:19860] 
> /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa5bf5)[0x7fafcbd0fbf5]
> [ip-172-31-4-50:19859] [ 7] 
> /<>/build/dune/grid-glue/test/ringcommtest(+0x3386)[0x558be8fd3386]
> [ip-172-31-4-50:19859] [ 8] [ 8] 
> /usr/lib/x86_64-linux-gnu/libmpi.so.40(ompi_errhandler_invoke+0xd7)[0x7fafcbe91337]
> [ip-172-31-4-50:19859] [ 9] 
> /usr/lib/x86_64-linux-gnu/libmpi.so.40(ompi_errhandler_invoke+0xd7)[0x7fd42a7bd337]
> [ip-172-31-4-50:19860] [ 9] 
> /usr/lib/x86_64-linux-gnu/libmpi.so.40(MPI_Isend+0x265)[0x7fafcbed17c5]
> [ip-172-31-4-50:19859] [10] 
> 

Processed: glom: diff for NMU version 1.30.4-6.1

[Debian Bug Tracking System]

Processing control commands:

> tags 972597 + patch
Bug #972597 [glom] PostgreSQL 13 transition
Added tag(s) patch.
> tags 972597 + pending
Bug #972597 [glom] PostgreSQL 13 transition
Added tag(s) pending.

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

Bug#972597: glom: diff for NMU version 1.30.4-6.1

[Sebastian Ramacher]

Control: tags 972597 + patch
Control: tags 972597 + pending

Dear maintainer,

I've prepared an NMU for glom (versioned as 1.30.4-6.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru glom-1.30.4/debian/changelog glom-1.30.4/debian/changelog
--- glom-1.30.4/debian/changelog	2020-03-09 22:12:58.0 +0100
+++ glom-1.30.4/debian/changelog	2020-11-14 12:44:41.0 +0100
@@ -1,3 +1,13 @@
+glom (1.30.4-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/: Switch to default postgresql version and generate concrete
+dependencies during the build. (Closes: #972597)
+- Add libpq-dev to Build-Depends for a useable pg_config
+- Use pg_config to look up postgresql's bindir and generate dependencies
+
+ -- Sebastian Ramacher   Sat, 14 Nov 2020 12:44:41 +0100
+
 glom (1.30.4-6) unstable; urgency=medium
 
   * debian/rules: Fix FTBFS with python3.8 (Closes: #952416)
diff -Nru glom-1.30.4/debian/control glom-1.30.4/debian/control
--- glom-1.30.4/debian/control	2020-03-09 22:12:58.0 +0100
+++ glom-1.30.4/debian/control	2020-11-14 09:36:09.0 +0100
@@ -30,13 +30,14 @@
libgoocanvasmm-2.0-dev (>= 1.90.11),
libgtkmm-3.0-dev (>= 3.18.0),
libgtksourceviewmm-3.0-dev (>= 3.18.0),
+   libpq-dev,
libtool,
libtool-bin,
libxml++2.6-dev (>= 2.24.0),
libxml-parser-perl,
libxslt1-dev (>= 1.1.10),
mm-common,
-   postgresql-12,
+   postgresql,
python-gi-dev,
python3-dev (>= 3.8),
python3-sphinx,
@@ -101,7 +102,7 @@
  iso-codes,
  libgda-5.0-postgres,
  libglom-1.30-0 (= ${binary:Version}),
- postgresql-12
+ ${postgresql:Depends}
 Recommends: glom-doc (= ${binary:Version})
 Description: database designer and user interface
  With Glom you can design table definitions and the relationships between
@@ -145,7 +146,7 @@
  gir1.2-gda-5.0,
  libgda-5.0-postgres,
  libglom-1.30-0 (= ${binary:Version}),
- postgresql-12
+ ${postgresql:Depends}
 Description: Command-line utilities for Glom
  With Glom you can design table definitions and the relationships between
  them, plus arrange the fields on the screen. You can edit and search the
diff -Nru glom-1.30.4/debian/control.in glom-1.30.4/debian/control.in
--- glom-1.30.4/debian/control.in	2020-03-09 22:12:58.0 +0100
+++ glom-1.30.4/debian/control.in	2020-11-14 09:59:47.0 +0100
@@ -26,13 +26,14 @@
libgoocanvasmm-2.0-dev (>= 1.90.11),
libgtkmm-3.0-dev (>= 3.18.0),
libgtksourceviewmm-3.0-dev (>= 3.18.0),
+   libpq-dev,
libtool,
libtool-bin,
libxml++2.6-dev (>= 2.24.0),
libxml-parser-perl,
libxslt1-dev (>= 1.1.10),
mm-common,
-   postgresql-12,
+   postgresql,
python-gi-dev,
python3-dev (>= 3.8),
python3-sphinx,
@@ -97,7 +98,7 @@
  iso-codes,
  libgda-5.0-postgres,
  libglom-1.30-0 (= ${binary:Version}),
- postgresql-12
+ ${postgresql:Depends}
 Recommends: glom-doc (= ${binary:Version})
 Description: database designer and user interface
  With Glom you can design table definitions and the relationships between
@@ -141,7 +142,7 @@
  gir1.2-gda-5.0,
  libgda-5.0-postgres,
  libglom-1.30-0 (= ${binary:Version}),
- postgresql-12
+ ${postgresql:Depends}
 Description: Command-line utilities for Glom
  With Glom you can design table definitions and the relationships between
  them, plus arrange the fields on the screen. You can edit and search the
diff -Nru glom-1.30.4/debian/rules glom-1.30.4/debian/rules
--- glom-1.30.4/debian/rules	2020-03-09 22:12:58.0 +0100
+++ glom-1.30.4/debian/rules	2020-11-14 12:38:02.0 +0100
@@ -16,7 +16,7 @@
 override_dh_auto_configure:
 	dh_auto_configure -- \
 		--disable-update-mime-database \
-		--with-postgres-utils=/usr/lib/postgresql/12/bin \
+		--with-postgres-utils=$(shell pg_config --bindir) \
 		PYTHON_CPPFLAGS="$(PYTHON_CPPFLAGS_PKGCONFIG)" \
 		PYTHON_LIBS="-L/usr/lib/$(DEB_HOST_MULTIARCH) $(PYTHON_LIB_PKGCONFIG)" \
 		PYTHON=python3 PYTHON_VERSION=3
@@ -52,3 +52,6 @@
 
 override_dh_missing:
 	dh_missing --list-missing
+
+override_dh_gencontrol:
+	dh_gencontrol -- -Vpostgresql:Depends=postgresql-$(shell pg_config --bindir | grep -o "[[:digit:]]*")


signature.asc
Description: PGP signature

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

[Sebastian Ramacher]

On 2020-11-14 10:46:23 +0100, Rafael Laboissière wrote:
> * Sebastian Ramacher  [2020-11-14 09:22]:
> 
> > Control: tags 974099 + patch
> > Control: tags 974099 + pending
> > 
> > Dear maintainer,
> > 
> > octave-database currently blocks the removal of postgresql-12 from
> > testing which blocks the perl 5.32 transition. To unblock the situation,
> > I've prepared an NMU for octave-database (versioned as 2.4.4-3.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I should delay
> > it longer.
> 
> Thank you for the upload.
> 
> Could you please push your changes to the Git depository for the package ?
> https://salsa.debian.org/pkg-octave-team/octave-database

I couldn't push them directly, so I've created a MR:
https://salsa.debian.org/pkg-octave-team/octave-database/-/merge_requests/1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#957074: cdrkit: ftbfs with GCC-10

[John Paul Adrian Glaubitz]

Hello!

> Fedora has a patch for gcc-10
> 
> https://src.fedoraproject.org/rpms/cdrkit/blob/master/f/cdrkit-1.1.11-gcc10.patch

Is anyone taking care of this package at the moment?

I'm happy to adopt cdrkit for the time being until libisofs from libburnia
has gained support for creating legacy HFS filesystems which is required
for older Macintosh systems.

For this reason, I'm currently using genisoimage when creating Debian CD
images for m68k.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#974733: q2-quality-filter: unsatisfiable build-dependencies

[Ralf Treinen]

Source: q2-quality-filter
Version: 2019.10.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

q2-quality-filter build-depends both on python3-pandas (indirectly, via
a dependency of qiime), and on q2-types.

python3-pandas version 1.1.4+dfsg-1 Breaks q2-types (<< 2019.10.0-1.1~).
However, the only version of q2-types in the archive is 2019.10.0-1.

-Ralf.

Bug#974730: systemd 247~rc2-2 install crashed several system

[Eric Valette]

Package: systemd
Version: 247~rc2-2
Severity: critical
Justification: breaks the whole system

I have updated several machine with experimental version and they did break for
various reasosn during install:

1) One is a NAS that I was updating via ssh. during update, the ssh 
session closed,
it was impossible to open a new one, and as the machine is headless, 
very difficult to
know what happened. The power button did an acpi shutdwon and the 
machine
did restart, but trying to do apt-get -f install, I have been prompted 
to do a
dpkg --configure -a because update was interrupted.  After that the 
machine was
operationnal again
2) One was a laptop, running a very recent kernel 5.9.8, This time i 
did update
logged on a X11 kde konsole. During update, the entire X session 
crashed, virtual
terminal were unreachable, remote login was impossible. Doing a 
CTRL-ALT-DEL,
somehow did shutdown the machine but rebooting was impossible. I had to 
select
an old kernel with its own initramfs, and to downgrade systemd to the 
one from
unstable to get things back on order.

Sorry to providfe little traces but I think it is usefull to warn that updating 
may cause
problem that may need a boot rescue medium to repair.

-- Package-specific info:

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

Kernel: Linux 5.4.77 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser3.118
ii  libacl12.2.53-8
ii  libapparmor1   3.0.0-1
ii  libaudit1  1:3.0~alpha9-1
ii  libblkid1  2.36-3+b2
ii  libc6  2.31-4
ii  libcap21:2.44-1
ii  libcrypt1  1:4.4.17-1
ii  libcryptsetup122:2.3.4-1+exp1
ii  libgcrypt201.8.7-2
ii  libgnutls303.6.15-5
ii  libgpg-error0  1.38-2
ii  libidn2-0  2.3.0-3
ii  libip4tc2  1.8.6-1
ii  libkmod2   27+20200310-2
ii  liblz4-1   1.9.2-2
ii  liblzma5   5.2.4-1+b1
ii  libmount1  2.36-3+b2
ii  libpam0g   1.3.1-5
ii  libpcre2-8-0   10.34-7
ii  libseccomp22.5.0-3
ii  libselinux13.1-2+b1
ii  libsystemd0246.6-2
ii  libzstd1   1.4.5+dfsg-4
ii  mount  2.36-3+b2
ii  ntp [time-daemon]  1:4.2.8p15+dfsg-1
ii  util-linux 2.36-3+b2

Versions of packages systemd recommends:
ii  dbus  1.13.18-1

Versions of packages systemd suggests:
ii  policykit-10.105-29
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.139
ii  libnss-systemd   246.6-2
ii  libpam-systemd   246.6-2
ii  udev 246.6-2

-- Configuration Files:
/etc/systemd/journald.conf changed [not included]

-- no debconf information

Bug#974726: q2-metadata: unsatisfiable build-dependencies

[Ralf Treinen]

Source: q2-metadata
Version: 2019.10.0+dfsg-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

q2-metadata build-depends both on python3-pandas and on q2-types.

python3-pandas version 1.1.4+dfsg-1 Breaks q2-types (<< 2019.10.0-1.1~).
However, the only version of q2-types in the archive is 2019.10.0-1.

-Ralf.

Bug#971178: closing 971178

[Timo Aaltonen]

close 971178 
thanks

Processed: closing 974702

[Debian Bug Tracking System]

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

> close 974702
Bug #974702 [intel-opencl-icd] intel-opencl-icd causes all OpenCL programs to 
abort
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: fixed 974702 in 20.44.18297-1

[Debian Bug Tracking System]

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

> fixed 974702 20.44.18297-1
Bug #974702 {Done: Timo Aaltonen } [intel-opencl-icd] 
intel-opencl-icd causes all OpenCL programs to abort
Marked as fixed in versions intel-compute-runtime/20.44.18297-1.
> thanks
Stopping processing here.

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

Processed: closing 971178

[Debian Bug Tracking System]

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

> close 971178
Bug #971178 [src:intel-compute-runtime] intel-compute-runtime: FTBFS: make[3]: 
*** 
[igdrcl_lib_release/scheduler/CMakeFiles/scheduler_Gen9core.dir/build.make:84: 
bin/scheduler/x64/gen9/scheduler_Gen9core.bin] Error 245
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#974702: closing 974702

[Timo Aaltonen]

close 974702 
thanks

fixed by 20.44.18297-1

Processed: severity of 973848 is grave, forcibly merging 973858 973848

[Debian Bug Tracking System]

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

> severity 973848 grave
Bug #973848 [chromium] chromium: Unsupported version, many security bugs unfixed
Severity set to 'grave' from 'important'
> forcemerge 973858 973848
Bug #973858 [chromium] chromium: Outdated version, more than 100 open security 
issues
Bug #973858 [chromium] chromium: Outdated version, more than 100 open security 
issues
Marked as found in versions chromium/83.0.4103.116-3.1.
Bug #973848 [chromium] chromium: Unsupported version, many security bugs unfixed
Marked as found in versions chromium/84.0.4147.105-1.
Added tag(s) security.
Merged 973848 973858
> thanks
Stopping processing here.

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

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

[Rafael Laboissière]

* Sebastian Ramacher  [2020-11-14 09:22]:


Control: tags 974099 + patch
Control: tags 974099 + pending

Dear maintainer,

octave-database currently blocks the removal of postgresql-12 from 
testing which blocks the perl 5.32 transition. To unblock the situation, 
I've prepared an NMU for octave-database (versioned as 2.4.4-3.1) and 
uploaded it to DELAYED/2. Please feel free to tell me if I should delay 
it longer.


Thank you for the upload.

Could you please push your changes to the Git depository for the package ? 
https://salsa.debian.org/pkg-octave-team/octave-database


Best,

Rafael Laboissière

Bug#974722: slurm-llnl: CVE-2020-27746: X11 forwarding - fix potential leak of the magic cookie when sent as an argument to the xauth command

[Salvatore Bonaccorso]

Source: slurm-llnl
Version: 19.05.5-2.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2020-27746[0]:
| X11 forwarding - avoid unsafe use of magic cookie as arg to xauth
| command

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-27746
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27746
[1] 
https://github.com/SchedMD/slurm/commit/07309deb45c33e735e191faf9dd31cca1054a15c
[2] https://lists.schedmd.com/pipermail/slurm-announce/2020/45.html
[3] https://www.schedmd.com/news.php?id=240

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#974721: slurm-llnl: CVE-2020-27745: PMIx - fix potential buffer overflows from use of unpackmem()

[Salvatore Bonaccorso]

Source: slurm-llnl
Version: 19.05.5-2.1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for slurm-llnl.

CVE-2020-27745[0]:
| PMIx - fix potential buffer overflows from use of unpackmem()

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-27745
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27745
[1] 
https://github.com/SchedMD/slurm/commit/c3142dd87e06621ff148791c3d2f298b5c0b3a81
[2] https://lists.schedmd.com/pipermail/slurm-announce/2020/45.html
[3] https://www.schedmd.com/news.php?id=240

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#974702: intel-opencl-icd causes all OpenCL programs to abort

[Giuseppe Bilotta]

On Sat, Nov 14, 2020 at 9:46 AM Timo Aaltonen  wrote:

> Hi, please try with the current version, I think this was due to the old
> driver being built with llvm10. 20.44 was uploaded yesterday.

> And 972620 should be fixed as well.

Hello, I just tested intel-opencl-icd 20.44.18297-1 with libigc1 and
libigdfcl1 at version 1.0.5353.1-2 and indeed both bugs seem to be
fixed.

(I'd be wary of the code still calling abort in case of issues,
though, since an ICD should just fail “properly” when things go wrong
during init.)

Thanks a lot,

Giuseppe Bilotta

-- 
Giuseppe "Oblomov" Bilotta

Bug#968027: marked as done (dino-im: FTBFS: error: [...]/xmpp-vala/src/glib_fixes.vapi not found)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 10:03:14 +0100
with message-id <20201114090314.GA432796@fama>
and subject line dino-im: FTBFS: error: [...]/xmpp-vala/src/glib_fixes.vapi not 
found
has caused the Debian Bug report #968027,
regarding dino-im: FTBFS: error: [...]/xmpp-vala/src/glib_fixes.vapi not found
to be marked as done.

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

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


-- 
968027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dino-im
Version: 0.1.0+20200623.717d0b7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

dino-im/experimental FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=dino-im=experimental

   dh_auto_build -a -O--buildsystem=cmake\+ninja
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
[1/642] cd /<>/obj-x86_64-linux-gnu/xmpp-vala && echo -e 
"gdk-pixbuf-2.0\ngee-0.8\ngio-2.0\nglib-2.0\ngobject-2.0\nicu-uc\n" > 
/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.deps
[2/642] cd /<>/obj-x86_64-linux-gnu/qlite && echo -e 
"gee-0.8\nglib-2.0\ngobject-2.0\nsqlite3\n" > 
/<>/obj-x86_64-linux-gnu/exports/qlite.deps
[3/642] cd /<>/obj-x86_64-linux-gnu/libdino && echo -e 
"gdk-pixbuf-2.0\ngee-0.8\nglib-2.0\ngmodule-2.0\ngobject-2.0\nxmpp-vala\nqlite" 
> /<>/obj-x86_64-linux-gnu/exports/dino.deps
[4/642] cd /<>/obj-x86_64-linux-gnu/libdino && cp 
/<>/libdino/src/dino_i18n.h 
/<>/obj-x86_64-linux-gnu/exports/dino_i18n.h
[5/642] cd /<>/obj-x86_64-linux-gnu/xmpp-vala && /usr/bin/valac 
--color=always -C 
--header=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.h 
--internal-header=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala_internal.h
 --vapi=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala.vapi 
--internal-vapi=/<>/obj-x86_64-linux-gnu/exports/xmpp-vala_internal.vapi
 -b /<>/xmpp-vala -d 
/<>/obj-x86_64-linux-gnu/xmpp-vala --pkg=gdk-pixbuf-2.0 
--pkg=gee-0.8 --pkg=gio-2.0 --pkg=glib-2.0 --pkg=gobject-2.0 --pkg=icu-uc 
--define=ALPN_SUPPORT --vapidir=/<>/xmpp-vala/vapi -g 
--target-glib=2.38 /<>/xmpp-vala/src/core/namespace_state.vala 
/<>/xmpp-vala/src/core/stanza_attribute.vala 
/<>/xmpp-vala/src/core/stanza_node.vala 
/<>/xmpp-vala/src/core/stanza_reader.vala 
/<>/xmpp-vala/src/core/stanza_writer.vala 
/<>/xmpp-vala/src/core/xmpp_log.vala 
/<>/xmpp-vala/src/core/xmpp_stream.vala 
/<>/xmpp-vala/src/module/bind.vala 
/<>/xmpp-vala/src/module/bookmarks_provider.vala 
/<>/xmpp-vala/src/module/conference.vala 
/<>/xmpp-vala/src/module/iq/module.vala 
/<>/xmpp-vala/src/module/iq/stanza.vala 
/<>/xmpp-vala/src/module/jid.vala 
/<>/xmpp-vala/src/module/message/module.vala 
/<>/xmpp-vala/src/module/message/stanza.vala 
/<>/xmpp-vala/src/module/presence/flag.vala 
/<>/xmpp-vala/src/module/presence/module.vala 
/<>/xmpp-vala/src/module/presence/stanza.vala 
/<>/xmpp-vala/src/module/roster/flag.vala 
/<>/xmpp-vala/src/module/roster/item.vala 
/<>/xmpp-vala/src/module/roster/module.vala 
/<>/xmpp-vala/src/module/roster/versioning_module.vala 
/<>/xmpp-vala/src/module/sasl.vala 
/<>/xmpp-vala/src/module/session.vala 
/<>/xmpp-vala/src/module/stanza.vala 
/<>/xmpp-vala/src/module/stanza_error.vala 
/<>/xmpp-vala/src/module/stream_error.vala 
/<>/xmpp-vala/src/module/tls.vala 
/<>/xmpp-vala/src/module/util.vala 
/<>/xmpp-vala/src/module/xep/0048_bookmarks.vala 
/<>/xmpp-vala/src/module/xep/0048_conference.vala 
/<>/xmpp-vala/src/module/xep/0402_bookmarks2.vala 
/<>/xmpp-vala/src/module/xep/0004_data_forms.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/flag.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/identity.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/info_result.vala
 /<>/xmpp-vala/src/module/xep/0030_service_discovery/item.vala 
/<>/xmpp-vala/src/module/xep/0030_service_discovery/items_result.vala
 /<>/xmpp-vala/src/module/xep/0030_service_discovery/module.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/flag.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/module.vala 
/<>/xmpp-vala/src/module/xep/0045_muc/status_code.vala 
/<>/xmpp-vala/src/module/xep/0047_in_band_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0049_private_xml_storage.vala 
/<>/xmpp-vala/src/module/xep/0054_vcard/module.vala 
/<>/xmpp-vala/src/module/xep/0060_pubsub.vala 
/<>/xmpp-vala/src/module/xep/0065_socks5_bytestreams.vala 
/<>/xmpp-vala/src/module/xep/0066_out_of_band_data.vala 
/<>/xmpp-vala/src/module/xep/0077_in_band_registration.vala 
/<>/xmpp-vala/src/module/xep/0082_date_time_profiles.vala 
/<>/xmpp-vala/src/module/xep/0084_user_avatars.vala 

Bug#973134: marked as done (python-webob: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Sat, 14 Nov 2020 09:04:26 +
with message-id 
and subject line Bug#973134: fixed in python-webob 1:1.8.6-1.1
has caused the Debian Bug report #973134,
regarding python-webob: FTBFS: tests failed
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.)


-- 
973134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-webob
Version: 1:1.8.6-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 '/<>'
> # enable network, tests.test_in_wsgiref.test_request_reading needs it
> set -e ; for vers in `py3versions -vr` ; do \
>   http_proxy='' PYTHONPATH=.:/<>/src python$vers -m pytest 
> tests ; \
> done
> py3versions: no X-Python3-Version in control file, using supported versions
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> collected 2388 items
> 
> tests/test_acceptparse.py .. [  
> 1%]
>  [  
> 4%]
>  [  
> 7%]
>  [ 
> 10%]
>  [ 
> 13%]
>  [ 
> 17%]
>  [ 
> 20%]
>  [ 
> 23%]
>  [ 
> 26%]
>  [ 
> 29%]
>  [ 
> 32%]
>  [ 
> 35%]
>  [ 
> 38%]
>  [ 
> 41%]
>  [ 
> 44%]
>  [ 
> 47%]
>  [ 
> 50%]
>  [ 
> 52%]
> tests/test_byterange.py ...  [ 
> 53%]
> tests/test_cachecontrol.py ...   [ 
> 54%]
> tests/test_client.py .   [ 
> 54%]
> tests/test_client_functional.py  [ 
> 55%]
> tests/test_compat.py ... [ 
> 55%]
> tests/test_cookies.py .s.s.s [ 
> 57%]
>  [ 
> 59%]
> tests/test_cookies_bw.py .   [ 
> 59%]
> tests/test_datetime_utils.py ..  [ 
> 60%]
> tests/test_dec.py .  [ 
> 61%]
> tests/test_descriptors.py .. [ 
> 62%]
>  [ 
> 65%]
> .[ 
> 66%]
> tests/test_etag.py ..[ 
> 67%]
> tests/test_etag_nose.py ...  [ 
> 67%]
> tests/test_exc.py    [ 
> 69%]
> tests/test_headers.py .  [ 
> 70%]
> tests/test_in_wsgiref.py FF  [ 
> 70%]
> tests/test_misc.py ...s.s.   [ 
> 70%]
> tests/test_multidict.py  [ 
> 72%]
>  [ 
> 75%]
> 

Processed: tagging 974704

[Debian Bug Tracking System]

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

> tags 974704 + ftbfs
Bug #974704 [src:pcp] pcp: FTBFS on some archs: Cannot find (any matches for) 
"usr/lib/pcp/pmdas/infiniband[...]
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#974702: intel-opencl-icd causes all OpenCL programs to abort

[Timo Aaltonen]

On Sat, 14 Nov 2020 01:05:56 +0100 Giuseppe Bilotta 
 wrote:

Package: intel-opencl-icd
Version: 20.37.17906-1
Severity: critical

When this package is installed, any OpenCL program will abort with the
message


Hi, please try with the current version, I think this was due to the old 
driver being built with llvm10. 20.44 was uploaded yesterday.



And 972620 should be fixed as well.


--
t

Bug#974716: q2-cutadapt: unsatisfiable build-dependency

[Ralf Treinen]

Source: q2-cutadapt
Version: 2019.10.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

q2-cutadapt build-depends both on python3-pandas and on q2-types.

python3-pandas version 1.1.4+dfsg-1 Breaks q2-types (<< 2019.10.0-1.1~).
However, the only version of q2-types in the archive is 2019.10.0-1.

Bug#974717: q2-demux: unsatisfiable build-dependency

[Ralf Treinen]

Source: q2-demux
Version: 2019.10.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

q2-demux build-depends both on python3-pandas and on q2-types.

python3-pandas version 1.1.4+dfsg-1 Breaks q2-types (<< 2019.10.0-1.1~).
However, the only version of q2-types in the archive is 2019.10.0-1.

Processed: octave-database: diff for NMU version 2.4.4-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 974099 + patch
Bug #974099 [src:octave-database] octave-database build depends on 
postgresql-12 that will not be in bullseye
Added tag(s) patch.
> tags 974099 + pending
Bug #974099 [src:octave-database] octave-database build depends on 
postgresql-12 that will not be in bullseye
Added tag(s) pending.

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

Bug#974099: octave-database: diff for NMU version 2.4.4-3.1

[Sebastian Ramacher]

Control: tags 974099 + patch
Control: tags 974099 + pending

Dear maintainer,

octave-database currently blocks the removal of postgresql-12 from
testing which blocks the perl 5.32 transition. To unblock the situation,
I've prepared an NMU for octave-database (versioned as 2.4.4-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should delay
it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru octave-database-2.4.4/debian/changelog octave-database-2.4.4/debian/changelog
--- octave-database-2.4.4/debian/changelog	2020-07-28 10:38:50.0 +0200
+++ octave-database-2.4.4/debian/changelog	2020-11-14 09:18:48.0 +0100
@@ -1,3 +1,11 @@
+octave-database (2.4.4-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/{control,tests}/: Run tests with default postgresql version
+(Closes: #974099)
+
+ -- Sebastian Ramacher   Sat, 14 Nov 2020 09:18:48 +0100
+
 octave-database (2.4.4-3) unstable; urgency=medium
 
   * d/control:
diff -Nru octave-database-2.4.4/debian/control octave-database-2.4.4/debian/control
--- octave-database-2.4.4/debian/control	2020-05-04 21:00:42.0 +0200
+++ octave-database-2.4.4/debian/control	2020-11-14 09:08:29.0 +0100
@@ -6,7 +6,7 @@
 Build-Depends: debhelper-compat (= 13),
dh-octave (>= 0.7.1),
libpq-dev,
-   postgresql-12
+   postgresql
 Standards-Version: 4.5.0
 Homepage: https://octave.sourceforge.io/database/
 Vcs-Git: https://salsa.debian.org/pkg-octave-team/octave-database.git
diff -Nru octave-database-2.4.4/debian/tests/control octave-database-2.4.4/debian/tests/control
--- octave-database-2.4.4/debian/tests/control	2019-11-12 16:57:36.0 +0100
+++ octave-database-2.4.4/debian/tests/control	2020-11-14 09:09:46.0 +0100
@@ -1,2 +1,2 @@
 Tests: test-pq-connect
-Depends: @, postgresql-12
+Depends: @, postgresql
diff -Nru octave-database-2.4.4/debian/tests/test-pq-connect octave-database-2.4.4/debian/tests/test-pq-connect
--- octave-database-2.4.4/debian/tests/test-pq-connect	2019-11-12 16:54:48.0 +0100
+++ octave-database-2.4.4/debian/tests/test-pq-connect	2020-11-14 09:12:34.0 +0100
@@ -15,7 +15,7 @@
 done
 
 ### Extend PATH for the PostrgeSQL commands
-PATH=$PATH:/usr/lib/postgresql/12/bin/
+PATH=$PATH:$(pg_config --bindir)
 
 ### Create temporary directory for DB data and temporary file for the
 ### OCtave script


signature.asc
Description: PGP signature