Processed: Re: python3-gevent: gevent 1.4 not compatible with python 3.8

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #958476 [python3-gevent] python3-gevent: gevent 1.4 not compatible with 
python 3.8
Added tag(s) patch.

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

Bug#958476: python3-gevent: gevent 1.4 not compatible with python 3.8

[Matthias Klose]

Control: tags -1 + patch

I packaged the recent version, cause the current isn't compatible with 3.9
either. All triggered autopkg tests passed.

Packaging proposal at
https://launchpad.net/ubuntu/+source/python-gevent/20.9.0-0ubuntu1

Processed: Re: aria2: autopkgtest needs update for new version of python3-defaults: output to stderr

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #975900 [src:aria2] aria2: autopkgtest needs update for new version of 
python3-defaults: output to stderr
Added tag(s) patch.

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

Bug#975900: aria2: autopkgtest needs update for new version of python3-defaults: output to stderr

[Matthias Klose]

Control: tags -1 + patch

patch at
https://patches.ubuntu.com/a/aria2/aria2_1.35.0-2ubuntu1.patch

Processed: bug 973605 is forwarded to https://github.com/odoo/odoo/pull/61199

[Debian Bug Tracking System]

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

> forwarded 973605 https://github.com/odoo/odoo/pull/61199
Bug #973605 [src:odoo] odoo: Multiple privacy-breach-generic (fetching data 
from an external website at runtime)
Set Bug forwarded-to-address to 'https://github.com/odoo/odoo/pull/61199'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#976171: fmutils failed, breaking tex-common

[Debian Bug Tracking System]

Processing control commands:

> reassign -1  texlive-latex-base
Bug #976171 [texlive-base] fmutils failed,  breaking tex-common
Bug reassigned from package 'texlive-base' to 'texlive-latex-base'.
No longer marked as found in versions texlive-base/2020.20201129-1.
Ignoring request to alter fixed versions of bug #976171 to the same values 
previously set
> severity 976170 serious
Bug #976170 {Done: Hilmar Preusse } [texlive-latex-base] lamed 
format gone, needs to break against old texlive-formats-extra
Severity set to 'serious' from 'normal'
> forcemerge -1 976170
Bug #976171 [texlive-latex-base] fmutils failed,  breaking tex-common
Bug #976171 [texlive-latex-base] fmutils failed,  breaking tex-common
Marked as fixed in versions texlive-base/2020.20201129-2.
Bug #976170 {Done: Hilmar Preusse } [texlive-latex-base] lamed 
format gone, needs to break against old texlive-formats-extra
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions texlive-base/2020.20201129-2.
Added indication that 976170 affects tex-common
Bug #976170 [texlive-latex-base] lamed format gone, needs to break against old 
texlive-formats-extra
Marked as fixed in versions texlive-base/2020.20201129-2.
Merged 976170 976171

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

Bug#976171: fmutils failed, breaking tex-common

[Hilmar Preuße]

Control: reassign -1  texlive-latex-base
Control: severity 976170 serious
Control: forcemerge -1 976170

Am 01.12.2020 um 02:07 teilte Vincent Lefevre mit:


Dup of bug 976170?


Probably. Forcemerge.

Hilmar
--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature

Bug#974705: Changes to job handling cause hangs in wait

[Herbert Xu]

On Tue, Dec 01, 2020 at 05:06:18PM +1100, Herbert Xu wrote:
>
> For some reason this is causing the final two tee's to be created
> as children of debian/tests/timedated rather than the bash shell.

An alternative to changing the parent is of course to do

wait $MONPID

instead of

wait

I think this makes more sense anyway as otherwise someone could
easily introduce a hang if they unwittingly add a backgrounded
job to this script.

Cheers,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#957206: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

[Shah, Amul]

Hi Andreas,
The latest GT.M version, V6.3-014, has a number of GCC-10 fixes in it. 
debian/rules needed some changes to handle executables that are no longer in 
the build. I made the necessary changes and tested the build (GCC-10) on my 
Debian unstable machine. I pushed the changes. Please let me know if there is 
more work to do. I have free time.

Thanks,
Amul

-Original Message-
From: Andreas Tille 
Sent: Monday, November 30, 2020 3:40 PM
To: 957206-mainto...@bugs.debian.org; Shah, Amul 
Subject: EXTERNAL: Re: Bug#957206: New upstream version available (Was: 
Bug#957206: fis-gtm: ftbfs with GCC-10)

CAUTION: This email originated from outside of the company. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.



Hi again Amul,

I updated Git to the next upstream version.  It also does not build
successfully.  We *really* should fix this *right* now.  Otherwise
fis-gtm will be not released with the next stable release.

Kind regards

  Andreas.

On Thu, Oct 01, 2020 at 03:52:01PM +0200, Andreas Tille wrote:
> Hi again
>
> On Fri, 7 Aug 2020 14:55:21 +, Shah, Amul wrote:
> > Thanks for the ping. We have a fix, just not enough time in a day. :(
>
> I think we should upload that fix in the near future.
>
> Kind regards
>
>  Andreas.

The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.

Bug#974705: Changes to job handling cause hangs in wait

[Herbert Xu]

On Tue, Dec 01, 2020 at 04:38:37PM +1100, Herbert Xu wrote:
> 
> FWIW I'm unable to reproduce it with autopkgtest.  This is what
> I get:
> 
> root@test0:~# autopkgtest --test-name=timedated systemd-246.6/ -B -- lxc -s 
> autopkgtest-sid
> autopkgtest [16:32:45]: starting date: 2020-12-01
> autopkgtest [16:32:45]: version 5.15
> autopkgtest [16:32:45]: host test0; command line: /usr/bin/autopkgtest 
> --test-name=timedated systemd-246.6/ -B -- lxc -s autopkgtest-sid
> autopkgtest [16:33:13]: testbed dpkg architecture: amd64
> autopkgtest [16:33:13]: testbed running kernel: Linux 5.9.0-rc1+ #18 SMP 
> PREEMPT Sat Aug 29 23:45:30 AEST 2020
> autopkgtest [16:33:13]:  unbuilt-tree systemd-246.6/
> autopkgtest [16:33:18]: testing package systemd version 246.6-5

Nevermind, I see that the script has been modified to use bash.

I can reproduce the problem now so it's all good.

Thanks,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#974705: Changes to job handling cause hangs in wait

[Herbert Xu]

On Mon, Nov 16, 2020 at 10:29:16AM +, Andrej Shadura wrote:
> 
> I’d like to forward a bug report I received. Michael, who reported it,
> was able to bisect it to 6c691b3, which was the first of the series of
> commits changing job handling.
> 
> I must note that I had troubles debugging it: I was only able to
> reproduce the issue in an autopkgtest virtual machine, but not on my
> normal system nor in a fresh Debian unstable Docker container.

FWIW I'm unable to reproduce it with autopkgtest.  This is what
I get:

root@test0:~# autopkgtest --test-name=timedated systemd-246.6/ -B -- lxc -s 
autopkgtest-sid
autopkgtest [16:32:45]: starting date: 2020-12-01
autopkgtest [16:32:45]: version 5.15
autopkgtest [16:32:45]: host test0; command line: /usr/bin/autopkgtest 
--test-name=timedated systemd-246.6/ -B -- lxc -s autopkgtest-sid
autopkgtest [16:33:13]: testbed dpkg architecture: amd64
autopkgtest [16:33:13]: testbed running kernel: Linux 5.9.0-rc1+ #18 SMP 
PREEMPT Sat Aug 29 23:45:30 AEST 2020
autopkgtest [16:33:13]:  unbuilt-tree systemd-246.6/
autopkgtest [16:33:18]: testing package systemd version 246.6-5
autopkgtest [16:33:18]: build not needed
autopkgtest [16:33:18]: test timedated: preparing testbed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies...Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
 Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
The following additional packages will be installed:
  acl libnss-systemd
The following NEW packages will be installed:
  acl libnss-systemd
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 255 kB of archives.
After this operation, 577 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 libnss-systemd amd64 246.6-5 
[194 kB]
Get:2 http://deb.debian.org/debian sid/main amd64 acl amd64 2.2.53-8 [60.8 kB]
Fetched 255 kB in 1s (489 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libnss-systemd:amd64.
(Reading database ... 12641 files and directories currently installed.)
Preparing to unpack .../libnss-systemd_246.6-5_amd64.deb ...
Unpacking libnss-systemd:amd64 (246.6-5) ...
Selecting previously unselected package acl.
Preparing to unpack .../acl_2.2.53-8_amd64.deb ...
Unpacking acl (2.2.53-8) ...
Setting up libnss-systemd:amd64 (246.6-5) ...
First installation detected...
Checking NSS setup...
Setting up acl (2.2.53-8) ...
Setting up autopkgtest-satdep (0) ...
Processing triggers for libc-bin (2.31-4) ...
(Reading database ... 12667 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [16:33:29]: test timedated: [---
original tz: Etc/UTC
timedatectl works
change timezone
reset timezone to original
no adjtime file
UTC set in adjtime file
non-zero values in adjtime file
fourth line adjtime file
no final newline in adjtime file
only one line in adjtime file
only one line in adjtime file, no final newline
only two lines in adjtime file
only two lines in adjtime file, no final newline
unknown value in 3rd line of adjtime file
disable NTP
enable NTP
re-disable NTP
autopkgtest [16:33:32]: test timedated: ---]
autopkgtest [16:33:32]: test timedated:  - - - - - - - - - - results - - - - - 
- - - - -
timedatedPASS
autopkgtest [16:33:32]:  summary
timedatedPASS
root@test0:~# 

Cheers,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#957206: EXTERNAL: Re: Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

[Andreas Tille]

Hi Amul,

thanks for the quick response.  Unfortunately the package does not build
successfully yet:

make[2]: Leaving directory '/build/fis-gtm-6.3-014/obj-x86_64-linux-gnu'
cd 
debian/fis-gtm-6.3-007-stage1/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64 
&& \
gtm_destdir=/build/fis-gtm-6.3-014/debian/fis-gtm-6.3-007 \
gtmcompile="-embed_source" \
./gtminstall --utf8 default --user root --group root --verbose \
--noprompt-for-sys-cfg --distrib . \
--installdir 
/build/fis-gtm-6.3-014/debian/fis-gtm-6.3-007/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64
Processed command line
gtm_buildtype  :  pro
gtm_distrib  :  .
gtm_dryrun  :  N
gtm_group  :  root
gtm_group_already  :  N
gtm_group_restriction  :  N
gtm_icu_version  :  default
gtm_installdir  :  
/build/fis-gtm-6.3-014/debian/fis-gtm-6.3-007/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64
gtm_keep_obj  :  N
gtm_lcase_utils  :  Y
gtm_overwrite_existing  :  N
gtm_prompt_for_group  :  N
gtm_prompt_for_sys_reconfig  :  N
gtm_user  :  root
gtm_verbose  :  Y
timestamp  :  20201201060722
Determined architecture, OS and GT.M version
gtm_arch  :  x8664
gtm_buildtype  :  pro
gtm_dist  :  .
gtm_distrib  :  .
gtm_dryrun  :  N
gtm_flavor  :  x8664
gtm_ftp_dirname  :  linux_x8664
gtm_group  :  root
gtm_group_already  :  N
gtm_group_restriction  :  N
gtm_hostos  :  linux
gtm_icu_version  :  default
gtm_install_flavor  :  x86_64
gtm_installdir  :  
/build/fis-gtm-6.3-014/debian/fis-gtm-6.3-007/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64
gtm_keep_obj  :  N
gtm_lcase_utils  :  Y
gtm_overwrite_existing  :  N
gtm_prompt_for_group  :  N
gtm_prompt_for_sys_reconfig  :  N
gtm_sf_dirname  :  GT.M-amd64-Linux
gtm_user  :  root
gtm_verbose  :  Y
gtm_version  :  V6.3-014
gtmroutines  :  /tmp/gtminstall_20201201060722(.)
timestamp  :  20201201060722
Downloaded and unpacked GT.M distribution
gtm_arch  :  x8664
gtm_buildtype  :  pro
gtm_dist  :  .
gtm_distrib  :  .
gtm_dryrun  :  N
gtm_flavor  :  x8664
gtm_ftp_dirname  :  linux_x8664
gtm_group  :  root
gtm_group_already  :  N
gtm_group_restriction  :  N
gtm_hostos  :  linux
gtm_icu_version  :  default
gtm_install_flavor  :  x86_64
gtm_installdir  :  
/build/fis-gtm-6.3-014/debian/fis-gtm-6.3-007/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-014_x86_64
gtm_keep_obj  :  N
gtm_lcase_utils  :  Y
gtm_overwrite_existing  :  N
gtm_prompt_for_group  :  N
gtm_prompt_for_sys_reconfig  :  N
gtm_sf_dirname  :  GT.M-amd64-Linux
gtm_tmp  :  .
gtm_user  :  root
gtm_verbose  :  Y
gtm_version  :  V6.3-014
gtmroutines  :  /tmp/gtminstall_20201201060722(.)
timestamp  :  20201201060722
Non-root installations not currently supported
gtminstall [option] ... [version]
Options are:
--build-type buildtype - * type of GT.M build, default is pro
--copyenv dirname - copy gtmprofile and gtmcshrc files to dirname; incompatible 
with linkenv
--copyexec dirname - copy gtm script to dirname; incompatible with linkexec
--debug - * turn on debugging with set -x
--distrib dirname or URL - source directory for GT.M distribution tarball, 
local or remote
--filename filename - name of GT.M distribution tarball
--dry-run - do everything short of installing GT.M, including downloading the 
distribution
--group group - group that should own the GT.M installation
--group-restriction - limit execution to a group; defaults to unlimited if not 
specified
--help - print this usage information
--installdir dirname - directory where GT.M is to be installed; defaults to 
/usr/lib/fis-gtm/version_platform
--keep-obj - keep .o files of M routines (normally deleted on platforms with 
GT.M support for routines in shared libraries)
--linkenv dirname - create link in dirname to gtmprofile and gtmcshrc files; 
incompatible with copyenv
--linkexec dirname - create link in dirname to gtm script; incompatible with 
copyexec
--noprompt-for-sys-cfg - do not prompt to adjust OS configuration files
--overwrite-existing - install into an existing directory, overwriting 
contents; defaults to requiring new directory
--prompt-for-group - * GT.M installation script will prompt for group; default 
is yes for production releases V5.4-002 or later, no for all others
--ucaseonly-utils -- install only upper case utility program names; defaults to 
both if not specified
--user username - user who should own GT.M installation; default is root
--utf8 ICU_version - install UTF-8 support using specified  major.minor ICU 
version; specify default to use default version
--verbose - * output diagnostic information as the script executes; default is 
to run quietly
options that take a value (e.g, --group) can be specified as either 
--option=value or --option value
options marked with * are likely to be of interest primarily to GT.M developers
version is defaulted from mumps file if one exists in the same directory as the 
installer
This version must run as root.
make[1]: *** [debian/rules:30: override_dh_auto_install] Error 1
make[1]: Leaving directory 

Bug#952003: marked as done (relion: FTBFS: src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0. Use MPI_Comm_set_errhandler

[Debian Bug Tracking System]

Your message dated Tue, 1 Dec 2020 07:05:14 +0100
with message-id <20201201060514.gd31...@an3as.eu>
and subject line Bug was closed with new upstream version
has caused the Debian Bug report #952003,
regarding relion: FTBFS: src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ 
declared with attribute error: MPI_Errhandler_set was removed in MPI-3.0.  Use 
MPI_Comm_set_errhandler instead.
to be marked as done.

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

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


-- 
952003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: relion
Version: 1.4+dfsg-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CXX   --mode=compile mpicxx.openmpi 
> -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -fpic  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o src/autopicker_mpi.lo src/autopicker_mpi.cpp
> libtool: compile:  mpicxx.openmpi -DHAVE_CONFIG_H -I. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fpic -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> src/autopicker_mpi.cpp  -fPIC -DPIC -o src/.libs/autopicker_mpi.o
> src/mpi.cpp: In constructor ‘MpiNode::MpiNode(int&, char**)’:
> src/mpi.cpp:56:23: error: call to ‘MPI_Errhandler_set’ declared with 
> attribute error: MPI_Errhandler_set was removed in MPI-3.0.  Use 
> MPI_Comm_set_errhandler instead.
>56 | MPI_Errhandler_set(MPI_COMM_WORLD, MPI_ERRORS_RETURN);
>   | ~~^~~
> make[3]: *** [Makefile:1305: src/mpi.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/relion_1.4+dfsg-4_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
This bug should have been closed with relion 3.x

-- 
http://fam-tille.de--- End Message ---

Bug#974705: Changes to job handling cause hangs in wait

[Herbert Xu]

On Tue, Dec 01, 2020 at 04:42:03PM +1100, Herbert Xu wrote:
>
> Nevermind, I see that the script has been modified to use bash.
> 
> I can reproduce the problem now so it's all good.

OK the problem is this:

sh -c 'sleep 1d& exec $MYSHELL -c "sleep 1& wait"'

You can replace MYSHELL with whatever shell you want to use.

Essentially dash will now wait for all children, even ones that
were created prior to its existence, however, bash only waits for
children that it created directly.

FWIW ksh exhibits the same behaviour as dash and I think there
is nothing wrong with this.

So the problem is really in the parent of this shell, which appears
to be bash:

bash -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  
. ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.is4n6xxr/downtmp/build.f2G/real-tree"; mkdir -p 
-m 1777 -- "/tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.is4n6xxr/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.is4n6xxr/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f 
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set 
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd 
"$buildtree"; export AUTOPKGTEST_NORMAL_USER=; export ADT_NORMAL_USER=; chmod 
+x 
/tmp/autopkgtest-lxc.is4n6xxr/downtmp/build.f2G/real-tree/debian/tests/timedated;
 touch /tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-stdout 
/tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-stderr; 
/tmp/autopkgtest-lxc.is4n6xxr/downtmp/build.f2G/real-tree/debian/tests/timedated
 2> >(tee -a /tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-stderr >&2) > 
>(tee -a /tmp/autopkgtest-lxc.is4n6xxr/downtmp/timedated-stdout);

For some reason this is causing the final two tee's to be created
as children of debian/tests/timedated rather than the bash shell.

Cheers,
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Bug#975849: marked as done (cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Tue, 01 Dec 2020 05:52:53 +
with message-id 
and subject line Bug#975849: fixed in cjs 4.8.0-1
has caused the Debian Bug report #975849,
regarding cjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
975849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cjs
Version: 4.6.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_strip --dbgsym-migration='libcjs-dbg (<< 3.0.1-1~)' || dh_strip
> make[1]: Leaving directory '/<>'
>dh_makeshlibs
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libcjs0/DEBIAN/symbols doesn't match 
> completely debian/libcjs0.symbols
> --- debian/libcjs0.symbols (libcjs0_4.6.0-2_amd64)
> +++ dpkg-gensymbolsk6tI83 2020-11-25 11:25:10.029214030 +
> @@ -22,7 +22,7 @@
>   _Z27gjs_cairo_pattern_get_protoP9JSContext@Base 3.4.4
>   
> _Z27gjs_cairo_surface_constructP9JSContextN2JS6HandleIP8JSObjectEEP14_cairo_surface@Base
>  3.4.4
>   _Z27gjs_cairo_surface_get_protoP9JSContext@Base 3.4.4
> - 
> (optional=gccO3ppc64el)_Z27gjs_object_require_propertyIPN2JS6RootedIP8JSObjectEEEbP9JSContextNS0_6HandleIS3_EEPKc14GjsConstStringT_@Base
>  3.4.4
> +#MISSING: 4.6.0-2# 
> (optional=gccO3ppc64el)_Z27gjs_object_require_propertyIPN2JS6RootedIP8JSObjectEEEbP9JSContextNS0_6HandleIS3_EEPKc14GjsConstStringT_@Base
>  3.4.4
>   
> _Z27gjs_object_require_propertyP9JSContextN2JS6HandleIP8JSObjectEEPKcNS2_I4jsidEENS1_13MutableHandleINS1_5ValueEEE@Base
>  3.4.4
>   
> _Z27gjs_object_require_propertyP9JSContextN2JS6HandleIP8JSObjectEEPKcNS2_I4jsidEENS1_13MutableHandleIS4_EE@Base
>  3.4.4
>   
> _Z27gjs_object_require_propertyP9JSContextN2JS6HandleIP8JSObjectEEPKcNS2_I4jsidEEP13GjsAutoJSChar@Base
>  3.8.0
> @@ -79,7 +79,10 @@
>   _ZN11ToggleQueue9is_queuedEP8_GObject@Base 3.4.4
>   _ZN11ToggleQueueD1Ev@Base 3.4.4
>   _ZN11ToggleQueueD2Ev@Base 3.4.4
> + 
> _ZN13GjsMaybeOwnedIP8JSObjectE16switch_to_rootedEP9JSContextPFvN2JS6HandleIS1_EEPvES8_@Base
>  4.6.0-2
>   _ZN13GjsMaybeOwnedIP8JSObjectE18on_context_destroyEPvP8_GObject@Base 3.4.4
> + 
> _ZN13GjsMaybeOwnedIP8JSObjectE4rootEP9JSContextRKS1_PFvN2JS6HandleIS1_EEPvESA_@Base
>  4.6.0-2
> + _ZN16GjsHeapOperationIP8JSObjectE12expose_to_jsERN2JS4HeapIS1_EE@Base 
> 4.6.0-2
>   _ZN19AutoReportExceptionD1Ev@Base 3.8.0
>   _ZN19AutoReportExceptionD2Ev@Base 3.8.0
>   
> (optional=templinst)_ZN2JS14StructGCPolicyINS_18PropertyDescriptorEE5traceEP8JSTracerPS1_PKc@Base
>  3.8.0
> @@ -87,24 +90,36 @@
>   
> (optional=templinst|subst)_ZN2JS14StructGCPolicyINS_8GCVectorINS_5ValueEL{size_t}8EN2js15TempAllocPolicy5traceEP8JSTracerPS5_PKc@Base
>  3.8.0
>   
> (optional=templinst|subst)_ZN2JS14StructGCPolicyINS_8GCVectorIP8JSObjectL{size_t}0EN2js17SystemAllocPolicy5traceEP8JSTracerPS6_PKc@Base
>  3.8.0
>   
> (optional=templinst|subst)_ZN2JS14StructGCPolicyINS_8GCVectorIP8JSObjectL{size_t}8EN2js15TempAllocPolicy5traceEP8JSTracerPS6_PKc@Base
>  3.8.0
> + _ZN2JS8GCVectorINS_5ValueELm8EN2js15TempAllocPolicyEEC1EOS4_@Base 4.6.0-2
> + _ZN2JS8GCVectorINS_5ValueELm8EN2js15TempAllocPolicyEEC2EOS4_@Base 4.6.0-2
>   
> (optional=templinst|subst)_ZN2JS8GCVectorINS_5ValueEL{size_t}8EN2js15TempAllocPolicyEED1Ev@Base
>  3.8.0
>   
> (optional=templinst|subst)_ZN2JS8GCVectorINS_5ValueEL{size_t}8EN2js15TempAllocPolicyEED2Ev@Base
>  3.8.0
> + _ZN2JS8GCVectorIP8JSObjectLm0EN2js17SystemAllocPolicyEEC1EOS5_@Base 4.6.0-2
> + _ZN2JS8GCVectorIP8JSObjectLm0EN2js17SystemAllocPolicyEEC2EOS5_@Base 4.6.0-2
> + _ZN2JS8GCVectorIP8JSObjectLm8EN2js15TempAllocPolicyEEC1EOS5_@Base 4.6.0-2
> + _ZN2JS8GCVectorIP8JSObjectLm8EN2js15TempAllocPolicyEEC2EOS5_@Base 4.6.0-2
> + _ZN2js14BarrierMethodsI4jsidE10exposeToJSES1_@Base 4.6.0-2
> + _ZN2js14BarrierMethodsIP8JSObjectE10exposeToJSES2_@Base 4.6.0-2
> + _ZN7GjsInitC1Ev@Base 4.6.0-2
> + _ZN7GjsInitC2Ev@Base 4.6.0-2
>   _ZN7GjsInitD1Ev@Base 3.4.4
>   _ZN7GjsInitD2Ev@Base 3.4.4
> - (optional=mozjs|arch=!amd64 !arm64 !armel !armhf !hppa !i386 !ia64 
> !mips64el !mipsel !powerpc !ppc64 !ppc64el !riscv64 !s390x 
> 

Bug#975411: meson: autopkgtest arm64

[Michel Le Bihan]

Hello,

I implemented this test in 
https://github.com/mesonbuild/meson/commit/631a7b5a2a8ffa31d0d126608e79841be02ecfea
 . Please enable it in the next version.

Michel Le Bihan

Bug#976171: fmutils failed, breaking tex-common

[Vincent Lefevre]

Dup of bug 976170?

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976170

976170:

fmtutil [ERROR]: running `aleph -ini   -jobname=lamed -progname=lamed 
*lambda.ini  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#974754: marked as done (libjbig0: invalid ELF header when loading libjbig.so.0)

[Debian Bug Tracking System]

Your message dated Tue, 1 Dec 2020 01:11:04 +0100
with message-id <08fd4679-3f07-0ad5-a0c9-928bdffdf...@debian.org>
and subject line Re: libjbig0: invalid ELF header when loading libjbig.so.0
has caused the Debian Bug report #974754,
regarding libjbig0: invalid ELF header when loading libjbig.so.0
to be marked as done.

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

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


-- 
974754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Fri, 27 Nov 2020 09:01:41 -0700 Ryan Beethe
 wrote:
> I am fine closing this issue, sorry for the noise.

Don't worry.

Andreas

PS: have you tried reinstalling the borked package?--- End Message ---

Processed: tagging 975818, tagging 975797, tagging 975849, tagging 975854, tagging 975851, tagging 975848 ...

[Debian Bug Tracking System]

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

> tags 975818 + experimental
Bug #975818 [src:libgtkada] libgtkada: FTBFS: AttributeError: 
'xml.etree.ElementTree.Element' object has no attribute 'getchildren'
Added tag(s) experimental.
> tags 975797 + experimental
Bug #975797 [src:qtwebkit-opensource-src] qtwebkit-opensource-src: FTBFS: 
NameError: name 'bytecodeSections' is not defined
Added tag(s) experimental.
> tags 975849 + experimental
Bug #975849 [src:cjs] cjs: FTBFS: dpkg-gensymbols: error: some symbols or 
patterns disappeared in the symbols file: see diff output below
Added tag(s) experimental.
> tags 975854 + experimental
Bug #975854 [src:mediastreamer2] mediastreamer2: FTBFS: 
string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound 8 equals 
destination size [-Werror=stringop-truncation]
Added tag(s) experimental.
> tags 975851 + experimental
Bug #975851 [src:sensible-utils] sensible-utils: FTBFS: po4a::po: Invalid value 
for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 
'file' or 'never')
Added tag(s) experimental.
> tags 975848 + experimental
Bug #975848 [src:rocksdb] rocksdb: FTBFS: ./db/version_edit.h:178:33: error: 
implicitly-declared ‘constexpr rocksdb::FileDescriptor::FileDescriptor(const 
rocksdb::FileDescriptor&)’ is deprecated [-Werror=deprecated-copy]
Added tag(s) experimental.
> tags 976156 + sid bullseye
Bug #976156 [libapache-mod-auth-kerb] libapache-mod-auth-kerb probably 
shouldn't be released in its current form
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975797
975818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975818
975848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975848
975849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975849
975851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975851
975854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975854
976156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#975143: marked as done (rosegarden: FTBFS: Panner.cpp:138:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 23:48:40 +
with message-id 
and subject line Bug#975143: fixed in rosegarden 1:20.06-2
has caused the Debian Bug report #975143,
regarding rosegarden: FTBFS: Panner.cpp:138:18: error: aggregate ‘QPainterPath 
path’ has incomplete type and cannot be defined
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.)


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

Hi,

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

Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBUILD_DEBUG 
> -DDEBUG -DHAVE_ALSA -DHAVE_LIBJACK -DHAVE_LIBSNDFILE -DHAVE_LIRC 
> -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS 
> -DQT_NO_URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -DROSEGARDENPRIVATE_LIB_MAKEDLL -DSTABLE -DWANT_TIMING 
> -I/<>/obj-x86_64-linux-gnu/src -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src/rosegardenprivate_autogen/include 
> -I/usr/include/raptor2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
> -Woverloaded-virtual -Wextra -Wformat-nonliteral -Wformat-security 
> -Winit-self -Wswitch-enum -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef 
> -Wcast-align -Wchar-subscripts -W -Wpointer-arith -fno-check-new -fno-common 
> -Werror=return-type -fvisibility=hidden -Wsuggest-override -fPIC -std=gnu++11 
> -o CMakeFiles/rosegardenprivate.dir/gui/widgets/LineEdit.cpp.o -c 
> /<>/src/gui/widgets/LineEdit.cpp
> /<>/src/gui/widgets/Panner.cpp: In member function ‘virtual void 
> Rosegarden::Panner::paintEvent(QPaintEvent*)’:
> /<>/src/gui/widgets/Panner.cpp:138:18: error: aggregate 
> ‘QPainterPath path’ has incomplete type and cannot be defined
>   138 | QPainterPath path;
>   |  ^~~~
> make[3]: *** [src/CMakeFiles/rosegardenprivate.dir/build.make:2419: 
> src/CMakeFiles/rosegardenprivate.dir/gui/widgets/Panner.cpp.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/rosegarden_20.06-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Dennis Braun  (supplier of updated rosegarden package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Nov 2020 13:52:05 +0100
Source: rosegarden
Architecture: source
Version: 1:20.06-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 975143
Changes:
 rosegarden (1:20.06-2) unstable; urgency=medium
 .
   * Fix QPainterPath compilation error (Closes: #975143)
   * Bump S-V to 4.5.1
Checksums-Sha1:
 8cb62edac0bf5f37b5cb274420a4b31546de06e0 2315 rosegarden_20.06-2.dsc
 581eaa73a00f3464a35601e596a899c0d322ab06 12180 rosegarden_20.06-2.debian.tar.xz
 e2a0bf0f19ca8e86215409ce06d3846797c71536 

Processed: Re: Bug#954403: joblib: configuration error installing python3-joblib

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-minimal 3.8.6-1
Bug #954403 [src:joblib] joblib: configuration error installing python3-joblib
Bug #975517 [src:joblib] joblib fails to install with Python 3.9
Bug reassigned from package 'src:joblib' to 'python3-minimal'.
Bug reassigned from package 'src:joblib' to 'python3-minimal'.
No longer marked as found in versions joblib/0.14.0-3 and joblib/0.17.0-0.1.
No longer marked as found in versions joblib/0.17.0-0.1 and joblib/0.14.0-3.
Ignoring request to alter fixed versions of bug #954403 to the same values 
previously set
Ignoring request to alter fixed versions of bug #975517 to the same values 
previously set
Bug #954403 [python3-minimal] joblib: configuration error installing 
python3-joblib
Bug #975517 [python3-minimal] joblib fails to install with Python 3.9
Marked as found in versions python3-defaults/3.8.6-1.
Marked as found in versions python3-defaults/3.8.6-1.
> affects -1 src:joblib
Bug #954403 [python3-minimal] joblib: configuration error installing 
python3-joblib
Bug #975517 [python3-minimal] joblib fails to install with Python 3.9
Added indication that 954403 affects src:joblib
Added indication that 975517 affects src:joblib

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

Bug#954403: joblib: configuration error installing python3-joblib

[Sebastian Ramacher]

Control: reassign -1 python3-minimal 3.8.6-1
Control: affects -1 src:joblib

On 2020-03-21 11:25:31 +0200, Graham Inggs wrote:
> Source: joblib
> Version: 0.14.0-3
> Severity: serious
> Control: affects -1 src:spades src:circlator
> 
> Hi Maintainer
> 
> While attempting to run the autopkgtests triggered by python3-defaults
> for spades [1] and circlator [2], python3-joblib fails to install with
> the following error:
> 
> Setting up python3-joblib (0.14.0-3) ...
> ...
>   File 
> "/usr/lib/python3/dist-packages/joblib/test/test_func_inspect_special_encoding.py",
> line 0
> SyntaxError: unknown encoding: big5
> 
> dpkg: error processing package python3-joblib (--configure):
>  installed python3-joblib package post-installation script subprocess
> returned error exit status 1

That's not an issue in joblib, but in py3compile. If python3.X is
installed, everything works as expected as one can see in the
statsmodels and scikit-learn tests. Compilation fails if
python3.X-minimal is installed, but python3.X is not. Then some module
handling encoding is not installed and py3compile fails.

One can easily reproduce this issue in current unstable with
python3.8-minimal installed and python3.8 removed. In the autopkgtests
of circlator and spades we also see

The following packages were automatically installed and are no longer required:
  libpython3.8-minimal python3.8-minimal
Use 'apt autoremove' to remove them.

Reassigning to python3-minimal which contains py3compile. Not sure what
the best option here is to fix in py3compile, but ignoring that
particular error would be a start. A file without bytecode would be
better than installation failure in this case.

Cheers

> 
> I've set the severity serious as this blocks the migration of
> python3-defaults with Python 3.8 as default.
> 
> Regards
> Graham
> 
> 
> [1] 
> https://ci.debian.net/user/britney/jobs?package=spades[]=testing[]=amd64
> [2] 
> https://ci.debian.net/user/britney/jobs?package=circlator[]=testing[]=amd64

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 21:48:38 +
with message-id 
and subject line Bug#973174: fixed in python-envisage 4.9.0-2.1
has caused the Debian Bug report #973174,
regarding python-envisage: FTBFS: dh_auto_test: error: pybuild --test -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.)


-- 
973174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-envisage
Version: 4.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):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
>   pybuild --test -i python{version} -p "3.9 3.8"
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_envisage/build; python3.9 -m unittest 
> discover -v 
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42'
> test_init_ipkernel_with_explicit_gui_backend 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_initial_namespace 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_initialize_twice 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_io_pub_thread_stopped 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_ipykernel_live_objects 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_ipython_util_io_globals_restored 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_ipython_util_io_globals_restored_if_they_dont_exist 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_lifecycle 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_no_new_atexit_handlers 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_no_threads_leaked 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_shutdown_closes_console_pipes 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_shutdown_restores_displayhook_and_excepthook 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_shutdown_restores_output_streams 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_shutdown_restores_sys_modules_main 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_shutdown_restores_sys_path 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_zmq_sockets_closed 
> (envisage.plugins.ipython_kernel.tests.test_internal_ipkernel.TestInternalIPKernel)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_get_service_twice 
> (envisage.plugins.ipython_kernel.tests.test_ipython_kernel_plugin.TestIPythonKernelPlugin)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_import_from_api 
> (envisage.plugins.ipython_kernel.tests.test_ipython_kernel_plugin.TestIPythonKernelPlugin)
>  ... skipped 'skipping tests that require the ipykernel package'
> test_kernel_namespace_extension_point 
> (envisage.plugins.ipython_kernel.tests.test_ipython_kernel_plugin.TestIPythonKernelPlugin)
>  ... 

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

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 21:35:55 +
with message-id 
and subject line Bug#973074: fixed in python-apptools 4.5.0-1.1
has caused the Debian Bug report #973074,
regarding python-apptools: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> xvfb-run -a dh_auto_test
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_apptools/build; python3.9 -m nose -v 
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user42'
> apptools.io.h5.tests.test_dict_node.test_create ... ok
> apptools.io.h5.tests.test_dict_node.test_is_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_is_not_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_create_with_data ... ok
> apptools.io.h5.tests.test_dict_node.test_create_with_array_data ... ok
> apptools.io.h5.tests.test_dict_node.test_load_saved_dict_node ... ok
> apptools.io.h5.tests.test_dict_node.test_load_saved_dict_node_with_array ... 
> ok
> apptools.io.h5.tests.test_dict_node.test_keys ... ok
> apptools.io.h5.tests.test_dict_node.test_delete_item ... ok
> apptools.io.h5.tests.test_dict_node.test_delete_array ... ok
> apptools.io.h5.tests.test_dict_node.test_auto_flush ... ok
> apptools.io.h5.tests.test_dict_node.test_auto_flush_off ... ok
> apptools.io.h5.tests.test_dict_node.test_undefined_key ... ok
> apptools.io.h5.tests.test_dict_node.test_basic_dtypes ... ok
> apptools.io.h5.tests.test_dict_node.test_mixed_type_list ... ok
> apptools.io.h5.tests.test_dict_node.test_dict ... ok
> apptools.io.h5.tests.test_dict_node.test_wrap_self_raises_error ... ok
> apptools.io.h5.tests.test_file.test_reopen ... ok
> apptools.io.h5.tests.test_file.test_open_from_pytables_object ... ok
> apptools.io.h5.tests.test_file.test_open_from_closed_pytables_object ... ok
> apptools.io.h5.tests.test_file.test_create_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_getitem_failure ... ok
> apptools.io.h5.tests.test_file.test_iteritems ... ok
> apptools.io.h5.tests.test_file.test_create_plain_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_plain_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_create_chunked_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_chunked_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_create_extendable_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_extendable_array_with_H5Group ... 
> ok
> apptools.io.h5.tests.test_file.test_str_and_repr ... ok
> apptools.io.h5.tests.test_file.test_shape_and_dtype ... ok
> apptools.io.h5.tests.test_file.test_shape_only_raises ... ok
> apptools.io.h5.tests.test_file.test_create_duplicate_array_raises ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_array_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_array_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_dict_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_dict_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_table_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_table_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_delete_existing_group_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_remove_group_with_remove_node ... ok
> apptools.io.h5.tests.test_file.test_remove_node_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_remove_node_with_H5Group ... ok
> apptools.io.h5.tests.test_file.test_read_mode_raises_on_nonexistent_file ... 
> ok
> apptools.io.h5.tests.test_file.test_cleanup ... ok
> apptools.io.h5.tests.test_file.test_create_group_with_H5File ... ok
> apptools.io.h5.tests.test_file.test_create_group_with_H5Group ... ok
> 

Bug#957276: marked as done (gluegen2: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 21:33:48 +
with message-id 
and subject line Bug#957276: fixed in gluegen2 2.3.2-8
has caused the Debian Bug report #957276,
regarding gluegen2: 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.)


-- 
957276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gluegen2
Version: 2.3.2-7
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/gluegen2_2.3.2-7_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

[...]
   [cc]   | ~^
   [cc] In file included from 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.c:7:
   [cc] /usr/include/string.h:125:40: note: expected ‘char * restrict’ but 
argument is of type ‘const char *’
   [cc]   125 | extern char *strncpy (char *__restrict __dest,
   [cc]   |   ~^~
   [cc] 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.c: In 
function ‘destroyModelMutable’:
   [cc] 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.c:737:11:
 warning: passing argument 1 of ‘free’ discards ‘const’ qualifier from pointer 
target type [-Wdiscarded-qualifiers]
   [cc]   737 | free(s->modelNamePointerCString);
   [cc]   |  ~^
   [cc] In file included from 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.c:5:
   [cc] /usr/include/stdlib.h:563:25: note: expected ‘void *’ but argument 
is of type ‘const char *’
   [cc]   563 | extern void free (void *__ptr) __THROW;
   [cc]   |   ~~^
   [cc] Starting link

junit.test1p1.c.build:
 [echo] Compiling Bindingtest1p1
 [echo]c.compiler.src.files junit.test1p1.c.src.files
 [echo]compiler.cfg.id compiler.cfg.linux.amd64
 [echo]linker.cfg.id linker.test1.fixed.cfg.id
 [echo]output.lib.name Bindingtest1p1
   [cc] 5 total files to be compiled.
   [cc] cc1: warning: command-line option ‘-fno-rtti’ is valid for 
C++/D/ObjC++ but not for C
   [cc] In file included from 
/<>/build/test/build/gensrc/native/TK_Surface_JNI.c:12:
   [cc] 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.h:319:6:
 warning: #warning "Hello Native Compiler" [-Wcpp]
   [cc]   319 | #warning "Hello Native Compiler"
   [cc]   |  ^~~
   [cc] cc1: warning: command-line option ‘-fno-rtti’ is valid for 
C++/D/ObjC++ but not for C
   [cc] In file included from 
/<>/build/test/build/gensrc/native/TK_Engine_JNI.c:12:
   [cc] 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.h:319:6:
 warning: #warning "Hello Native Compiler" [-Wcpp]
   [cc]   319 | #warning "Hello Native Compiler"
   [cc]   |  ^~~
   [cc] cc1: warning: command-line option ‘-fno-rtti’ is valid for 
C++/D/ObjC++ but not for C
   [cc] In file included from 
/<>/build/test/build/gensrc/native/TK_ModelConst_JNI.c:12:
   [cc] 
/<>/src/junit/com/jogamp/gluegen/test/junit/generation/test1.h:319:6:
 warning: #warning "Hello Native Compiler" [-Wcpp]
   [cc]   319 | #warning "Hello Native Compiler"
   [cc]   |  ^~~
   [cc] cc1: warning: command-line option ‘-fno-rtti’ is valid for 
C++/D/ObjC++ but not for C
   [cc] In file included from 

Processed: affects 976171

[Debian Bug Tracking System]

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

> affects 976171 tex-common
Bug #976171 [texlive-base] fmutils failed,  breaking tex-common
Added indication that 976171 affects tex-common
> thanks
Stopping processing here.

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

Bug#957184: eurephia: diff for NMU version 1.1.0-6.1

[Alberto Gonzalez Iniesta]

Hi, Sudip.

Thanks for the upload. No need to cancel it :-)

On Mon, Nov 30, 2020 at 08:52:30PM +, Sudip Mukherjee wrote:
> Control: tags 957184 + patch
> Control: tags 957184 + pending
> --
> 
> Dear maintainer,
> 
> I've prepared an NMU for eurephia (versioned as 1.1.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should cancel it.
> 
> --
> Regards
> Sudip
> 
> diff -Nru eurephia-1.1.0/debian/changelog eurephia-1.1.0/debian/changelog
> --- eurephia-1.1.0/debian/changelog   2016-09-16 08:38:26.0 +0100
> +++ eurephia-1.1.0/debian/changelog   2020-11-30 20:44:45.0 +
> @@ -1,3 +1,11 @@
> +eurephia (1.1.0-6.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix ftbfs with GCC-10. (Closes: #957184)
> +- Use fcommon with CFLAGS.
> +
> + -- Sudip Mukherjee   Mon, 30 Nov 2020 20:44:45 
> +
> +
>  eurephia (1.1.0-6) unstable; urgency=medium
>  
>* Make build reproducible. Thanks Chris Lamb for the patch!
> diff -Nru eurephia-1.1.0/debian/rules eurephia-1.1.0/debian/rules
> --- eurephia-1.1.0/debian/rules   2015-07-07 16:04:12.0 +0100
> +++ eurephia-1.1.0/debian/rules   2020-11-29 22:27:12.0 +
> @@ -3,7 +3,7 @@
>   dh $@
>  
>  override_dh_auto_configure:
> - $(shell DEB_CFLAGS_MAINT_APPEND="-fPIC -std=gnu89" dpkg-buildflags 
> --export=configure) ./configure --prefix /usr --plug-in --fw-iptables 
> --db-sqlite3 --sqlite3-path /var/lib/eurephia --eurephiadm --openvpn-src 
> /usr/include/openvpn
> + $(shell DEB_CFLAGS_MAINT_APPEND="-fPIC -std=gnu89 -fcommon" 
> dpkg-buildflags --export=configure) ./configure --prefix /usr --plug-in 
> --fw-iptables --db-sqlite3 --sqlite3-path /var/lib/eurephia --eurephiadm 
> --openvpn-src /usr/include/openvpn
>  override_dh_auto_clean:
>   rm -rf configure.log
>   dh_auto_clean

-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Processed: freebirth: diff for NMU version 0.3.2-9.3

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957228: freebirth: diff for NMU version 0.3.2-9.3

[Sudip Mukherjee]

Control: tags 957228 + patch
Control: tags 957228 + pending
--

Dear maintainer,

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

--
Regards
Sudip

diff -u freebirth-0.3.2/debian/changelog freebirth-0.3.2/debian/changelog
--- freebirth-0.3.2/debian/changelog
+++ freebirth-0.3.2/debian/changelog
@@ -1,3 +1,11 @@
+freebirth (0.3.2-9.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957228)
+- Use fcommon with CFLAGS.
+
+ -- Sudip Mukherjee   Mon, 30 Nov 2020 20:56:31 
+
+
 freebirth (0.3.2-9.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u freebirth-0.3.2/debian/rules freebirth-0.3.2/debian/rules
--- freebirth-0.3.2/debian/rules
+++ freebirth-0.3.2/debian/rules
@@ -5,7 +5,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-CFLAGS=-g -Wall $(shell pkg-config --cflags gtk+-2.0) $(shell dpkg-buildflags 
--get CFLAGS)
+CFLAGS=-g -Wall $(shell pkg-config --cflags gtk+-2.0) $(shell dpkg-buildflags 
--get CFLAGS) -fcommon
 LDFLAGS=$(shell pkg-config --libs gtk+-2.0) $(shell dpkg-buildflags --get 
LDFLAGS)
 
 # Handle DEB_BUILD_OPTIONS

Bug#975133: marked as done (tupi: FTBFS: tslider.cpp:292:29: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 20:53:08 +
with message-id 
and subject line Bug#975133: fixed in tupi 0.2+git08-4
has caused the Debian Bug report #975133,
regarding tupi: FTBFS: tslider.cpp:292:29: error: aggregate ‘QPainterPath path’ 
has incomplete type and cannot be defined
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.)


-- 
975133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tupi
Version: 0.2+git08-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> g++ -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O2 
> -Wall -Wextra -D_REENTRANT -fPIC -DHAVE_THEORA -DHAVE_LIBAV -DHAVE_QUAZIP 
> -DHAVE_MULTIMEDIA -DHAVE_ZLIB -DK_NODEBUG -DVERSION=\"0.2\" 
> -DCODE_NAME=\"Beraba\" -DREVISION=\"git08\" -DCONFIG_VERSION=\"2\" 
> -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -I../tcore -I.. 
> -I../../libbase -I../tcore -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
> -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
> -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/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o tslider.o tslider.cpp
> In file included from tapplication.h:41,
>  from txyspinbox.h:41,
>  from txyspinbox.cpp:36:
> thememanager.h:64:56: warning: ‘QXmlParseException’ is deprecated 
> [-Wdeprecated-declarations]
>64 | bool error(const QXmlParseException & exception);
>   |^
> thememanager.h:65:61: warning: ‘QXmlParseException’ is deprecated 
> [-Wdeprecated-declarations]
>65 | bool fatalError(const QXmlParseException & exception);
>   | ^
> In file included from tapplication.h:42,
>  from txyspinbox.h:41,
>  from txyspinbox.cpp:36:
> tvhbox.h:67:66: warning: ‘constexpr QFlags::QFlags(QFlags::Zero) [with 
> Enum = Qt::AlignmentFlag; QFlags::Zero = int 
> QFlags::Private::*]’ is deprecated: Use default 
> constructor instead [-Wdeprecated-declarations]
>67 | void addWidget(QWidget *child, Qt::Alignment alignment = 0);
>   |  ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1304,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qchar.h:43,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:49,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QString:1,
>  from ../tcore/tapplicationproperties.h:41,
>  from txyspinbox.h:40,
>  from txyspinbox.cpp:36:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
>   123 | QT_DEPRECATED_X("Use default constructor instead") 
> Q_DECL_CONSTEXPR inline QFlags(Zero) noexcept : i(0) {}
>   |   
>  ^~
> /usr/lib/qt5/bin/rcc -name tgui_images tgui_images.qrc -o qrc_tgui_images.cpp
> /usr/lib/qt5/bin/moc -DHAVE_THEORA -DHAVE_LIBAV -DHAVE_QUAZIP 
> -DHAVE_MULTIMEDIA -DHAVE_ZLIB -DK_NODEBUG -DVERSION=\"0.2\" 
> -DCODE_NAME=\"Beraba\" -DREVISION=\"git08\" -DCONFIG_VERSION=\"2\" 
> -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
> -DQT_XML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB --include 
> /<>/src/framework/tgui/moc_predefs.h 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
> -I/<>/src/framework/tgui -I/<>/src/framework/tcore 
> -I/<>/src/framework -I/<>/src/libbase 
> -I/<>/src/framework/tcore -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
> -I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
> -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/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/10 
> 

Processed: eurephia: diff for NMU version 1.1.0-6.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957184: eurephia: diff for NMU version 1.1.0-6.1

[Sudip Mukherjee]

Control: tags 957184 + patch
Control: tags 957184 + pending
--

Dear maintainer,

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

--
Regards
Sudip

diff -Nru eurephia-1.1.0/debian/changelog eurephia-1.1.0/debian/changelog
--- eurephia-1.1.0/debian/changelog 2016-09-16 08:38:26.0 +0100
+++ eurephia-1.1.0/debian/changelog 2020-11-30 20:44:45.0 +
@@ -1,3 +1,11 @@
+eurephia (1.1.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957184)
+- Use fcommon with CFLAGS.
+
+ -- Sudip Mukherjee   Mon, 30 Nov 2020 20:44:45 
+
+
 eurephia (1.1.0-6) unstable; urgency=medium
 
   * Make build reproducible. Thanks Chris Lamb for the patch!
diff -Nru eurephia-1.1.0/debian/rules eurephia-1.1.0/debian/rules
--- eurephia-1.1.0/debian/rules 2015-07-07 16:04:12.0 +0100
+++ eurephia-1.1.0/debian/rules 2020-11-29 22:27:12.0 +
@@ -3,7 +3,7 @@
dh $@
 
 override_dh_auto_configure:
-   $(shell DEB_CFLAGS_MAINT_APPEND="-fPIC -std=gnu89" dpkg-buildflags 
--export=configure) ./configure --prefix /usr --plug-in --fw-iptables 
--db-sqlite3 --sqlite3-path /var/lib/eurephia --eurephiadm --openvpn-src 
/usr/include/openvpn
+   $(shell DEB_CFLAGS_MAINT_APPEND="-fPIC -std=gnu89 -fcommon" 
dpkg-buildflags --export=configure) ./configure --prefix /usr --plug-in 
--fw-iptables --db-sqlite3 --sqlite3-path /var/lib/eurephia --eurephiadm 
--openvpn-src /usr/include/openvpn
 override_dh_auto_clean:
rm -rf configure.log
dh_auto_clean

Bug#973210: marked as done (python-django-celery-results: FTBFS: ModuleNotFoundError: No module named 'celery.five')

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 20:48:30 +
with message-id 
and subject line Bug#973210: fixed in python-django-celery-results 2.0.0-1
has caused the Debian Bug report #973210,
regarding python-django-celery-results: FTBFS: ModuleNotFoundError: No module 
named 'celery.five'
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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/apps.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/models.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/managers.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/admin.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/utils.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0003_auto_20181106_1101.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0001_initial.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> creating 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/cache.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/database.py -> 
> /<>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/apps.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/models.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/managers.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/admin.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/utils.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> creating 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0003_auto_20181106_1101.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0001_initial.py -> 
> 

Bug#954613: marked as done (rust-process-viewer: FTBFS: unsatisfiable build-dependency: librust-sysinfo-0.9+default-dev (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 20:49:20 +
with message-id 
and subject line Bug#954613: fixed in rust-process-viewer 0.2.6-2
has caused the Debian Bug report #954613,
regarding rust-process-viewer: FTBFS: unsatisfiable build-dependency: 
librust-sysinfo-0.9+default-dev (versioned dep on a virtual pkg?)
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.)


-- 
954613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-process-viewer
Version: 0.2.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-cairo-rs-0.7+default-dev, 
> librust-gdk-0.11+default-dev, librust-gdk-pixbuf-0.7+default-dev, 
> librust-gio-0.7+default-dev, librust-glib-0.8+default-dev, 
> librust-gtk-0.7+default-dev, librust-libc-0.2+default-dev, 
> librust-pango-0.7+default-dev, librust-serde-1+default-dev, 
> librust-serde-derive-1+default-dev, librust-sysinfo-0.9+default-dev, 
> librust-toml-0.5+default-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 11), dh-cargo (>= 18), cargo, rustc, 
> libstd-rust-dev, librust-cairo-rs-0.7+default-dev, 
> librust-gdk-0.11+default-dev, librust-gdk-pixbuf-0.7+default-dev, 
> librust-gio-0.7+default-dev, librust-glib-0.8+default-dev, 
> librust-gtk-0.7+default-dev, librust-libc-0.2+default-dev, 
> librust-pango-0.7+default-dev, librust-serde-1+default-dev, 
> librust-serde-derive-1+default-dev, librust-sysinfo-0.9+default-dev, 
> librust-toml-0.5+default-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [483 B]
> Get:5 copy:/<>/apt_archive ./ Packages [567 B]
> Fetched 2013 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-sysinfo-0.9+default-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/rust-process-viewer_0.2.6-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: rust-process-viewer
Source-Version: 0.2.6-2
Done: Debian Rust Maintainers 

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

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

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

Debian distribution maintenance software
pp.
Debian Rust Maintainers  
(supplier of updated rust-process-viewer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#976169: psi4: autopkgtest regression in testing: ImportError: cannot import name 'core' from partially initialized module 'psi4'

[Paul Gevers]

Source: psi4
Version: 1:1.3.2-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing (I believe the added support of
Python3.9) the autopkgtest of psi4 started to fail. I copied some of the
output at the bottom of this report. Can you please investigate the
situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/psi4/8534048/log.gz

autopkgtest [19:22:54]: test testsuite.sh: [---
Running test simint/scf5... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test gcp/hf3c
Running test python/energy... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test v2rdm_casscf/v2rdm3
Skipping test cfour/sp-rhf-ccsd_t_
Running test sapt1... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test libefp/qchem-qmefp-sp
Skipping test dftd3/energy
Running test erd/scf5... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Running test scf-property... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/psi4", line 177, in 
import psi4
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 60, in 
raise ImportError("{0}".format(err))
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely due to a circular import)
(/usr/lib/x86_64-linux-gnu/psi4/__init__.py)
FAILED
LOG:


2020-11-30 19:22
Skipping test mrcc/ccsdt
Running test dfmp2-1... Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/psi4/__init__.py", line 55, in 
from . import core
ImportError: cannot import name 'core' from partially initialized module
'psi4' (most likely 

Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

[Andreas Tille]

Hi again Amul,

I updated Git to the next upstream version.  It also does not build
successfully.  We *really* should fix this *right* now.  Otherwise
fis-gtm will be not released with the next stable release.

Kind regards

  Andreas.

On Thu, Oct 01, 2020 at 03:52:01PM +0200, Andreas Tille wrote:
> Hi again
> 
> On Fri, 7 Aug 2020 14:55:21 +, Shah, Amul wrote:
> > Thanks for the ping. We have a fix, just not enough time in a day. :(
> 
> I think we should upload that fix in the near future.
> 
> Kind regards
> 
>  Andreas.
> 
> -- 
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#969074: [PATCH] d/p/lp-1894129-*: fix FTBFS (LP: #1894129 Closes: #969074)

[Paul Gevers]

Hi all, Christian,

On Tue,  8 Sep 2020 15:40:11 +0200 Christian Ehrhardt
 wrote:
> Signed-off-by: Christian Ehrhardt 
> ---
>  ...raseReserved-override-driver-queue_p.patch |  74 
>  ...BlockEraseReserved-skip-unless-iSCSI.patch |  39 
>  ...e-Write-override-driver-queue_pdu-ca.patch |  71 
>  ...e-Write-skip-InvalidDataOutSize-unle.patch |  39 
>  ...EraseReserved-override-driver-queue_.patch |  74 
>  ...ryptoEraseReserved-skip-unless-iSCSI.patch |  39 
>  ...iteReserved-override-driver-queue_pd.patch |  68 +++
>  ...-test-tool-Use-extern-int-in-headers.patch |  58 ++
>  ...mdSnTooHigh-override-driver-queue_pd.patch |  68 +++
>  ...mdSnTooLow-override-driver-queue_pdu.patch |  69 
>  ...ataSnInvalid-override-driver-queue_p.patch | 166 ++
>  ...-unused-iscsi_queue_pdu-symbol-overl.patch | 104 +++
>  debian/patches/series |  12 ++
>  13 files changed, 881 insertions(+)
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-BlockEraseReserved-override-driver-queue_p.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-BlockEraseReserved-skip-unless-iSCSI.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-Compare-Write-override-driver-queue_pdu-ca.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-Compare-Write-skip-InvalidDataOutSize-unle.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-CryptoEraseReserved-override-driver-queue_.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-CryptoEraseReserved-skip-unless-iSCSI.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-OverwriteReserved-override-driver-queue_pd.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-Use-extern-int-in-headers.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-iSCSICmdSnTooHigh-override-driver-queue_pd.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-iSCSICmdSnTooLow-override-driver-queue_pdu.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-iSCSIDataSnInvalid-override-driver-queue_p.patch
>  create mode 100644 
> debian/patches/lp-1894129-test-tool-remove-unused-iscsi_queue_pdu-symbol-overl.patch

If your comfortable, can this please be uploaded? libiscsi is a key
package (so won't be autoremoved) and the freeze is getting near. Let's
not wait with fixing this until the latest moment.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: src:imlib2: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #973353 {Done: Paul Gevers } [src:imlib2] src:imlib2: 
fails to migrate to testing for too long: FTBFS on s390x
Added tag(s) ftbfs.
> reopen -1
Bug #973353 {Done: Paul Gevers } [src:imlib2] src:imlib2: 
fails to migrate to testing for too long: FTBFS on s390x
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions imlib2/1.7.0-1.

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

Bug#973353: src:imlib2: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Control: tags -1 ftbfs
Control: reopen -1

Hi,

On Thu, 29 Oct 2020 11:49:42 +0100 Paul Gevers  wrote:
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-removed.

This package is a key package, and as such will not be autoremoved.

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

As this bug seem to require a reupload to fix the FTBFS, I have reopened
it (I should not have closed it), and tagged it ftbfs.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS everywhere

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.1.57-1
Bug #976167 [src:rust-redox-syscall] src:rust-redox-syscall: fails to migrate 
to testing for too long: FTBFS everywhere
The source 'rust-redox-syscall' and version '0.1.57-1' do not appear to match 
any binary packages
Marked as fixed in versions rust-redox-syscall/0.1.57-1.
Bug #976167 [src:rust-redox-syscall] src:rust-redox-syscall: fails to migrate 
to testing for too long: FTBFS everywhere
Marked Bug as done
> block -1 by 971209
Bug #976167 {Done: Paul Gevers } [src:rust-redox-syscall] 
src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS 
everywhere
976167 was not blocked by any bugs.
976167 was not blocking any bugs.
Added blocking bug(s) of 976167: 971209

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

Bug#976167: src:rust-redox-syscall: fails to migrate to testing for too long: FTBFS everywhere

[Paul Gevers]

Source: rust-redox-syscall
Version: 0.1.40-2
Severity: serious
Control: close -1 0.1.57-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 971209

Dear maintainer(s),

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

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

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

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

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

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#973210 marked as pending in python-django-celery-results

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973210 [src:python-django-celery-results] python-django-celery-results: 
FTBFS: ModuleNotFoundError: No module named 'celery.five'
Added tag(s) pending.

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

Bug#973210: marked as pending in python-django-celery-results

[Michael Fladischer]

Control: tag -1 pending

Hello,

Bug #973210 in python-django-celery-results 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/python-team/packages/python-django-celery-results/-/commit/a90fa3fad75f3e060f8dcd03b09f21cd9cb3a72b


New upstream release (Closes: #973210).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973210

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

[Paul Gevers]

Hi David,

On 30-11-2020 17:05, David Steele wrote:
> All works well, until you test the new version of one package along with
> the old version of the other. In one scenario there is a recursion, where
> topydo ends up calling itself via the alternatives hook.

Ack. That's probably what we're seeing then.

> I didn't worry too much about this when I submitted the new packages,
> because the issue was transient, and the common popcon is like 5. I
> failed to consider that ci would evaluate the packages independently,
> and would choke.

Happens. Glad you're able to point us at the problem so quickly. I have
blocklisted todo.txt-base already yesterday, so the infrastructure is
somewhat protected now. I'll lift the block once you close this bug.

> I'm reworking the packages so that they can manage this upgrade
> without complaint. That process will take at least days. I'd be willing to
> consider more drastic means to resolve this, either by overriding the
> failures this one time, or by deleting the packages from the distribution
> and starting fresh. 

Take the time you need. Better do it well now than rush.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#974090 closed by Debian FTP Masters (reply to Hideki Yamane ) (Bug#974090: fixed in lcdf-typetools 2.108-2)

[Debian Bug Tracking System]

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

> # BTS doesn't handle these double assigned bugs extremely well
> reassign 974090 src:lcdf-typetools 2.108-1
Bug #974090 {Done: Hideki Yamane } 
[src:fonts-gfs-artemisia, src:lcdf-typetools] fonts-gfs-artemisia breaks 
lcdf-typetools autopkgtest: lots of failures
Bug reassigned from package 'src:fonts-gfs-artemisia, src:lcdf-typetools' to 
'src:lcdf-typetools'.
No longer marked as found in versions fonts-gfs-artemisia/1.1-6 and 
lcdf-typetools/2.108-1.
No longer marked as fixed in versions lcdf-typetools/2.108-2.
Bug #974090 {Done: Hideki Yamane } [src:lcdf-typetools] 
fonts-gfs-artemisia breaks lcdf-typetools autopkgtest: lots of failures
Marked as found in versions lcdf-typetools/2.108-1.
> affects 974090 src:fonts-gfs-artemisia
Bug #974090 {Done: Hideki Yamane } [src:lcdf-typetools] 
fonts-gfs-artemisia breaks lcdf-typetools autopkgtest: lots of failures
Added indication that 974090 affects src:fonts-gfs-artemisia
> fixed 974090 2.108-2
Bug #974090 {Done: Hideki Yamane } [src:lcdf-typetools] 
fonts-gfs-artemisia breaks lcdf-typetools autopkgtest: lots of failures
Marked as fixed in versions lcdf-typetools/2.108-2.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> usertags 974090 - breaks
Usertags were: needs-update breaks.
Usertags are now: needs-update.
> thanks
Stopping processing here.

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

Processed: RM: xnnpack [armhf] -- RoQA; package no longer builds on armhf

[Debian Bug Tracking System]

Processing control commands:

> block 973560 by -1
Bug #973560 {Done: Paul Gevers } [src:xnnpack] src:xnnpack: 
fails to migrate to testing for too long: FTBFS on armhf
973560 was not blocked by any bugs.
973560 was not blocking any bugs.
Added blocking bug(s) of 973560: 976164

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

Bug#975994: zimlib breaks python-libzim autopkgtest: segfaults

[Paul Gevers]

Hi Kunal

On 30-11-2020 02:34, Kunal Mehta wrote:
> So I plan to close this bug with an upload of python-libzim 0.0.3-2 that
> depends on libzim-dev >= 6.3.0. Will that be enough for the CI system or
> do I also need to have zimlib Break the older python-libzim versions?

That versioned Depends relation should be enough for CI. But what about
users that do a partial upgrade? (Yes, I know, officially not supported
in Debian, but in practice it works pretty well).

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976081: [Pkg-javascript-devel] Bug#976081: Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

[Pirate Praveen]

On Tue, Dec 1, 2020 at 00:28, Pirate Praveen  
wrote:



On Mon, Nov 30, 2020 at 19:46, Paolo Greppi  
wrote:
The resulting package was not installable due to node-babel-runtime 
missing from testing


May be we can add babel-runtime as a component? (it is going to 
contrib anyway)


Or see if we can replace babel-runtime to @babel/runtime with patch and 
node-babel7 as runtime dependency.

Bug#976081: [Pkg-javascript-devel] Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

[Pirate Praveen]

On Mon, Nov 30, 2020 at 19:46, Paolo Greppi  
wrote:
On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen 
 wrote:

Control: clone -1 -2
Control: retitle -2 "Provide prebuilt yarnpkg in contrib"

On Sat, Nov 28, 2020 at 22:07, Paolo Greppi  
wrote:
>> 3. Build it using 'deb >> 
https://snapshot.debian.org/archive/debian/20200502T085134Z sid >> 
main' (the last version that builds in sid) and embed the built >> 
files in the package (as two steps, like we bootstrap babel, rollup 
>> etc). This will mean, we will have to move it to contrib. I 
prefer >> shipping yarn in contrib to missing it in bullseye.

> > +1

I have a created a new branch master-contrib in salsa and pushed my 
changes.
Please review the changes and if it looks good, we can upload it. 
Also we can move this discussion to the cloned bug.


I have made a couple of commits to master-contrib branch.

The resulting package was not installable due to node-babel-runtime 
missing from testing


May be we can add babel-runtime as a component? (it is going to contrib 
anyway)



Also it does not install the man manpage.


Pushed a change, so it should get installed now.

Bug#976081: [Pkg-javascript-devel] Bug#976081: yarnpkg: Provide prebuilt yarnpkg in contrib

[Paolo Greppi]

On Sun, 29 Nov 2020 18:02:16 +0530 Pirate Praveen  
wrote:

Control: clone -1 -2
Control: retitle -2 "Provide prebuilt yarnpkg in contrib"

On Sat, Nov 28, 2020 at 22:07, Paolo Greppi  
wrote:
>> 3. Build it using 'deb 
>> https://snapshot.debian.org/archive/debian/20200502T085134Z sid 
>> main' (the last version that builds in sid) and embed the built 
>> files in the package (as two steps, like we bootstrap babel, rollup 
>> etc). This will mean, we will have to move it to contrib. I prefer 
>> shipping yarn in contrib to missing it in bullseye.
> 
> +1


I have a created a new branch master-contrib in salsa and pushed my 
changes.
Please review the changes and if it looks good, we can upload it. Also 
we can move this discussion to the cloned bug.


I have made a couple of commits to master-contrib branch.

The resulting package was not installable due to node-babel-runtime missing 
from testing.

I naïvely removed that from the run time deps, but now yarnpkg fails with:

  internal/modules/cjs/loader.js:905
throw err;
^

  Error: Cannot find module 'babel-runtime/helpers/asyncToGenerator'
  Require stack:
  - /usr/share/nodejs/yarn/lib/cli/index.js
  - /usr/share/nodejs/yarn/bin/yarn.js
  at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:902:15)
  at Function.Module._load (internal/modules/cjs/loader.js:747:27)
  at Module.require (internal/modules/cjs/loader.js:974:19)
  at require (internal/modules/cjs/helpers.js:88:18)
  at _load_asyncToGenerator (/usr/share/nodejs/yarn/lib/cli/index.js:17:54)
  at /usr/share/nodejs/yarn/lib/cli/index.js:21:41
  at Object. (/usr/share/nodejs/yarn/lib/cli/index.js:605:3)
  at Module._compile (internal/modules/cjs/loader.js:1085:30)
  at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
  at Module.load (internal/modules/cjs/loader.js:950:32) {
code: 'MODULE_NOT_FOUND',
requireStack: [
  '/usr/share/nodejs/yarn/lib/cli/index.js',
  '/usr/share/nodejs/yarn/bin/yarn.js'
]
  }

Also it does not install the man manpage.

Paolo

Bug#975457: marked as done (mandos: password-agent autopkgtest does not seem to be reliable)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 18:48:24 +
with message-id 
and subject line Bug#975457: fixed in mandos 1.8.13-1
has caused the Debian Bug report #975457,
regarding mandos: password-agent autopkgtest does not seem to be reliable
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.)


-- 
975457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mandos
Version: 1.8.12-1
Severity: serious
Justification: https://release.debian.org/bullseye/rc_policy.txt 6a
X-Debbugs-Cc: debian...@lists.debian.org

The password-agent autopkgtest doesn't seem to be stable: it sometimes
fails and sometimes succeeds. In
 we can see that
around half the migration-reference tests in the last month have succeeded
and half have failed.

The end of the log from an example test failure is quoted below.

This can be a problem for the packages that it depends on, such as
glib2.0 and systemd: if the most recent migration-reference test happens
to have succeeded, but then the test with a proposed version of glib2.0
or systemd fails, then the testing migration infrastructure will assume
that it's a regression caused by glib2.0 or systemd.

If this test cannot be made reliable, please mark it with
"Restrictions: flaky" so that it will not be used as a migration gate.

Thanks,
smcv

# Start of connect_question_socket tests
ok 117 /task/connect_question_socket/name-too-long
ok 118 /task/connect_question_socket/connect-fail
ok 119 /task/connect_question_socket/bad-epoll
ok 120 /task/connect_question_socket/usable
# End of connect_question_socket tests
# Start of send_password_to_socket tests
ok 121 /task/send_password_to_socket/client-not-exited
ok 122 /task/send_password_to_socket/password-not-read
Bail out! 
ERROR:dracut-module/password-agent.c:6020:test_send_password_to_socket_EMSGSIZE:
 'string_set_contains(cancelled_filenames, question_filename)' should be TRUE
**
ERROR:dracut-module/password-agent.c:6020:test_send_password_to_socket_EMSGSIZE:
 'string_set_contains(cancelled_filenames, question_filename)' should be TRUE
bash: line 1:  1815 Aborted bash -ec 
'/usr/lib/dracut/modules.d/90mandos/password-agent --test --verbose' 2> >(tee 
-a /tmp/autopkgtest-lxc.q6elt0p6/downtmp/password-agent-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.q6elt0p6/downtmp/password-agent-stdout)
--- End Message ---
--- Begin Message ---
Source: mandos
Source-Version: 1.8.13-1
Done: Teddy Hogeborn 

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

Debian distribution maintenance software
pp.
Teddy Hogeborn  (supplier of updated mandos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Nov 2020 19:15:43 +0100
Source: mandos
Architecture: source
Version: 1.8.13-1
Distribution: unstable
Urgency: medium
Maintainer: Mandos Maintainers 
Changed-By: Teddy Hogeborn 
Closes: 975457
Changes:
 mandos (1.8.13-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix "password-agent autopkgtest does not seem to be reliable"
 by making the test more reliable (Closes: #975457)
   * debian/mandos-client.templates: Rename "_description" header to
 "_Description".
   * debian/control (Standards-Version): Change to "4.5.1".
Checksums-Sha1:
 172b35468be94c81f4f57eb07dc6611db95d1068 2318 mandos_1.8.13-1.dsc
 a3bdc4f7a766f9386dd41d160c48eca6d27de7c6 242455 mandos_1.8.13.orig.tar.gz
 93aca6637461f265d511aa9d7941e65cc4098798 25772 mandos_1.8.13-1.debian.tar.xz
 be19d33205c06574bccf3fb52097cc89626c5899 10516 mandos_1.8.13-1_amd64.buildinfo
Checksums-Sha256:
 82658b443ea41099755f55c151ec8c3df451c21f134e56a75a2d7bed93fec614 2318 
mandos_1.8.13-1.dsc
 7e6d9cfdccadf636afd68a1af4fa937c8314ca49afc625712ab6e94446f1d508 242455 
mandos_1.8.13.orig.tar.gz
 3fcc6ad8fd2680b6ce0d35dadf808b6429f07313e65b3f4e209f9bd1ec993db8 25772 
mandos_1.8.13-1.debian.tar.xz
 5c8d605f3569ef9cd6a35bcb874c82cb1184e86dadc152575fefa77ba6cb9ed1 10516 

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

[Pirate Praveen]

On Mon, Nov 30, 2020 at 19:35, Jonas Smedegaard  wrote:

Btw, it seems you need to push latest changes to git for yarnpkg


The recent changes are in master-1 branch as we could not fix the 
master branch (attempted to build with babel 7 without success).

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2020-11-30 19:31:26)
> Quoting Pirate Praveen (2020-11-30 18:43:27)
> > On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard  wrote:
> > > yarnpkg depends on node-node-uuid.
> > > 
> > > node-node-uuid was deprecated 2 yars ago, replaced by node-uuid.
> > > 
> > > Please change to instead depend on node-uuid.
> > > 
> > > Raised severity as this is the last package relying on the old name, 
> > > and we want to drop it before freeze.
> > 
> > Since node-yarnpkg is not in bullseye and ftbfs already (it needs a 
> > snapshot.debian.org chroot with babel 6 from the time 1.22.4-3 was 
> > built by buildd), I think you can request node-node-uuid to be removed 
> > from bullseye or add an rc bug for auto removal. We can fix 
> > node-yarnpkg if we need to fix another breakage like node-mkdirp 1.0. 
> > Or if someone wants to fix it earlier, feel free.
> 
> Thanks for the heads-up.
> 
> node-node-uuid is just a virtual package so no ftpmaster requests are 
> involved, though.

I am talking nonsense above: not a virtual package but not a separate 
_source_ package is the reason there's no need to involve ftpmasters 
here.

Btw, it seems you need to push latest changes to git for yarnpkg.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

[Jonas Smedegaard]

Quoting Pirate Praveen (2020-11-30 18:43:27)
> On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard  wrote:
> > yarnpkg depends on node-node-uuid.
> > 
> > node-node-uuid was deprecated 2 yars ago, replaced by node-uuid.
> > 
> > Please change to instead depend on node-uuid.
> > 
> > Raised severity as this is the last package relying on the old name, 
> > and we want to drop it before freeze.
> 
> Since node-yarnpkg is not in bullseye and ftbfs already (it needs a 
> snapshot.debian.org chroot with babel 6 from the time 1.22.4-3 was 
> built by buildd), I think you can request node-node-uuid to be removed 
> from bullseye or add an rc bug for auto removal. We can fix 
> node-yarnpkg if we need to fix another breakage like node-mkdirp 1.0. 
> Or if someone wants to fix it earlier, feel free.

Thanks for the heads-up.

node-node-uuid is just a virtual package so no ftpmaster requests are 
involved, though.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#976035: marked as done (Doesn't work with Python 3.9)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 18:18:34 +
with message-id 
and subject line Bug#976035: fixed in mitmproxy 5.3.0-1
has caused the Debian Bug report #976035,
regarding Doesn't work with Python 3.9
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.)


-- 
976035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mitmproxy
Version: 5.1.1-2
Severity: grave
Tags: upstream fixed-upstream 
Control: forwarded -1 https://github.com/mitmproxy/mitmproxy/issues/4021

[...]
  File "/usr/lib/python3/dist-packages/mitmproxy/utils/typecheck.py", line 73,
in check_option_type
elif not isinstance(value, typeinfo):
  File "/usr/lib/python3.9/typing.py", line 697, in __instancecheck__
return self.__subclasscheck__(type(obj))
  File "/usr/lib/python3.9/typing.py", line 700, in __subclasscheck__
raise TypeError("Subscripted generics cannot be used with"
TypeError: Subscripted generics cannot be used with class and instance checks



This is fixed at https://github.com/mitmproxy/mitmproxy/pull/4179 but there is
no release since it was merged.



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

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

Versions of packages mitmproxy depends on:
ii  dpkg  1.20.5
ii  fonts-font-awesome5.0.10+really4.7.0~dfsg-2
ii  python3   3.9.0-3
ii  python3-blinker   1.4+dfsg1-0.3
ii  python3-brotli1.0.9-2+b1
ii  python3-certifi   2020.6.20-1
ii  python3-click 7.1.2-1
ii  python3-cryptography  3.2.1-1
ii  python3-flask 1.1.2-2
ii  python3-h11   0.11.0-1
ii  python3-h23.2.0-2
ii  python3-hyperframe5.2.0-4
ii  python3-kaitaistruct  0.8-3
ii  python3-ldap3 2.7-2
ii  python3-openssl   19.1.0-2
ii  python3-passlib   1.7.2-2
ii  python3-pkg-resources 50.3.0-1
ii  python3-protobuf  3.12.3-2+b1
ii  python3-publicsuffix2 2.20191221-2
ii  python3-pyasn10.4.8-1
ii  python3-pyparsing 2.4.7-1
ii  python3-pyperclip 1.8.0-1
ii  python3-ruamel.yaml   0.16.12-2
ii  python3-sortedcontainers  2.1.0-2
ii  python3-tornado   6.1.0-1
ii  python3-urwid 2.1.1-1+b1
ii  python3-wsproto   0.15.0-3

mitmproxy recommends no packages.

mitmproxy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.3.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mitmproxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Nov 2020 12:10:21 +0100
Source: mitmproxy
Architecture: source
Version: 5.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andrej Shadura 
Closes: 975178 976035
Changes:
 mitmproxy (5.3.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #976035, #975178).
 - Refresh patches
 - Bump build dependencies.
Checksums-Sha1:
 22b5a0c1bb971734ddea818b5bddd772ba978498 2732 mitmproxy_5.3.0-1.dsc
 383f56f0acd8d5cd92a2c442363d7ac29aaf865b 27272534 mitmproxy_5.3.0.orig.tar.gz
 18cdab66483a67946a6404fa8a252e8a36bb97fb 11804 mitmproxy_5.3.0-1.debian.tar.xz
Checksums-Sha256:
 744cb3f01ffcb8b83b40dee8ed83cc2e6436842d0d1d62f5e17313463d774bcd 2732 
mitmproxy_5.3.0-1.dsc
 

Bug#975178: marked as done (mitmproxy: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 18:18:34 +
with message-id 
and subject line Bug#975178: fixed in mitmproxy 5.3.0-1
has caused the Debian Bug report #975178,
regarding mitmproxy: FTBFS: E: Build killed with signal TERM after 150 minutes 
of inactivity
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.)


-- 
975178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mitmproxy
Version: 5.1.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> original = getattr(target, name, DEFAULT)
> else:
> local = True
> 
> if name in _builtins and isinstance(target, ModuleType):
> self.create = True
> 
> if not self.create and original is DEFAULT:
> >   raise AttributeError(
> "%s does not have the attribute %r" % (target, name)
> )
> E   AttributeError:  '/<>/.pybuild/cpython3_3.9_mitmproxy/build/mitmproxy/ctx.py'> 
> does not have the attribute 'log'
> 
> /usr/lib/python3.9/unittest/mock.py:1378: AttributeError
> == 131 failed, 548 passed, 668 deselected, 94 error in 32.25 
> seconds ===
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/mitmproxy_5.1.1-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: mitmproxy
Source-Version: 5.3.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mitmproxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Nov 2020 12:10:21 +0100
Source: mitmproxy
Architecture: source
Version: 5.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Andrej Shadura 
Closes: 975178 976035
Changes:
 mitmproxy (5.3.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #976035, #975178).
 - Refresh patches
 - Bump build dependencies.
Checksums-Sha1:
 22b5a0c1bb971734ddea818b5bddd772ba978498 2732 mitmproxy_5.3.0-1.dsc
 383f56f0acd8d5cd92a2c442363d7ac29aaf865b 27272534 mitmproxy_5.3.0.orig.tar.gz
 18cdab66483a67946a6404fa8a252e8a36bb97fb 11804 mitmproxy_5.3.0-1.debian.tar.xz
Checksums-Sha256:
 744cb3f01ffcb8b83b40dee8ed83cc2e6436842d0d1d62f5e17313463d774bcd 2732 
mitmproxy_5.3.0-1.dsc
 e4a3de2fdc2c169f0e9c3a04c39de14d2650edf46b3157645339e4920b3a8e26 27272534 
mitmproxy_5.3.0.orig.tar.gz
 4427cdf3b95608e3ab3a2e07a4a3a8c78b91a0cbd7a50647a034d9d87255a0ba 11804 
mitmproxy_5.3.0-1.debian.tar.xz
Files:
 36b81a60d3930e1b40ba0cb30b9742ab 2732 net optional mitmproxy_5.3.0-1.dsc
 a47eea59f1ce860a88355f71bab97251 27272534 net optional 
mitmproxy_5.3.0.orig.tar.gz
 da1217fb8cc3518ea923a5d9a4b680a0 11804 net optional 
mitmproxy_5.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl/FNDAACgkQXkCM2RzY
OdJ2ZQf/dsHdIzlJJrv74zyvnGltjupxSO+EviVO1f7yN8uMJXZ6j6cTYU+4m03Y
+0oknzkPxLtwn+QRONiXcG0oHUYH8lHcXqimB2m16XyROAjWSl7lWeAZOMnjUsrr
H+Ozd+QaxhPjGVYwekwrhFGEKsyVuVGpiLQRY52VU9lSA1ZIeqyWRDcKXuGY636P
DvvckXrV3NoTdzmhz9T/gswuvk1Yh2B8t2KOw0Yj5QOIfYY87ynGGG+xyfTikOCt
zojgj07u+uogfe3yMgNH+bNXKcJvp84I+Qjjawc1dLxQZGCPblrvfiShw+f+e7fP
xAkCGcs1YXSis5WOs0DaaMArTBRYRA==
=8gxD
-END PGP 

Bug#975157: (no subject)

[Ryan Pavlik]

This has been fixed upstream, so an upcoming update will resolve it.



signature.asc
Description: OpenPGP digital signature

Processed: [bts-link] source package src:consul

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:consul
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #975584 (http://bugs.debian.org/975584)
> # Bug title: consul: CVE-2020-28053
> #  * https://github.com/hashicorp/consul/issues/9240
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 975584 + fixed-upstream
Bug #975584 [src:consul] consul: CVE-2020-28053
Added tag(s) fixed-upstream.
> usertags 975584 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:compyle

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:compyle
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #972006 (http://bugs.debian.org/972006)
> # Bug title: pycompyle ftbfs with python3.9 (test failures)
> #  * https://github.com/pypr/compyle/issues/64
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 972006 + fixed-upstream
Bug #972006 [src:compyle] pycompyle ftbfs with python3.9 (test failures)
Added tag(s) fixed-upstream.
> usertags 972006 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 972006 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#976155: [Pkg-javascript-devel] Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

[Pirate Praveen]

On Mon, Nov 30, 2020 at 18:32, Jonas Smedegaard  wrote:

Package: yarnpkg
Version: 1.22.4-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

yarnpkg depends on node-node-uuid.

node-node-uuid was deprecated 2 yars ago, replaced by node-uuid.

Please change to instead depend on node-uuid.

Raised severity as this is the last package relying on the old name,
and we want to drop it before freeze.


Since node-yarnpkg is not in bullseye and ftbfs already (it needs a 
snapshot.debian.org chroot with babel 6 from the time 1.22.4-3 was 
built by buildd), I think you can request node-node-uuid to be removed 
from bullseye or add an rc bug for auto removal. We can fix 
node-yarnpkg if we need to fix another breakage like node-mkdirp 1.0. 
Or if someone wants to fix it earlier, feel free.

Bug#976156: libapache-mod-auth-kerb probably shouldn't be released in its current form

[Sam Hartman]

package: libapache-mod-auth-kerb
severity: serious
version: 5.4-2.4
tags: security
justification: unmaintained with security weaknesses

Hi.  As part of a recent krb5 transition, I took a look at
libapache-mod-auth-kerb.
As part of that transition, libapache-mod-auth-kerb was removed from
testing.
I think that in its current state, that's a good idea.
So I'm opening a serious bug as Kerberos maintainer, questioning whether
libapache-mod-auth-kerb uses Kerberos securely.
If someone is going to step up and agree to spend real time maintaining
libapache-mod-auth-kerb, and they choose to downgrade this bug, I have
no objection.
What I don't want to see happen is the package continue to be vaguely
unmaintained and be released in its current form.

There are better replacements for  this package already in Debian.
My recommendation would be that for spnego authentication use
libapache2-mod-auth-gssapi.
For basic authentication use PAM and libpam-krb5 or libpam-sss.

The two biggest security issues I see are:

1) Vulnerable to dictionary attacks because  of old Kerberos API usage.
Kerberos as designed is vulnerable to dictionary attacks.  There is a
mechanism called timestamp (or encrypted challenge) preauthentication in
which  the client rather than the KDC produces the attackable quantity.
That way, you need to observe an exchange with a legitimate user in
order to attack a password.
libapache-mod-auth-kerb supports that.
However if you can observe exchanges between the webserver and KDC, you
can attack the passwords.

Modern Kerberos has a facility called FAST  that prevents this type of
dictionary attack by encrypting the entire Kerberos exchange.
Libapache-mod-auth-kerb does not support FAST because it does not use
the right APIs to provide an armour ticket to the Kerberos library.

2) Rather than using the verify_init_creds API within the Kerberos
library, libapache-mod-auth-kerb open-codes its own initial credentials
verification API based on old code extracted from the Kerberos library.
I am concerned that this code may have been improved and enhanced in
security relevant ways in the many years since it was extracted.
I'd recommend this be audited.

3) Replay cache usage.  The code currently doesn't provide a replay
cache for SPNEGO tokens.
I am not sure this is a good idea, and comments in the code indicate it
is a security problem.
It's a bit tricky.  It's quite possibly the case that replay caches are
not needed provided that TLS is used for the HTTP connection, and that
the cost of replay caches is too high.

I think this should be audited, and either the comments in the code
explaining that not using replay caches are a security problem replaced
with an explanation of why they are not (or turn on the replay cache).
The bugs in MIT Kerberos 1.3 that made replay caches problematic are not
an issue in 2020.

Again, I'm happy if someone steps up to spend significant effort
modernizing and maintaining the package and wants to downgrade this bug.
Be aware that you probably end up becoming upstream as well.


signature.asc
Description: PGP signature

Bug#976155: yarnpkg: depends on obsolete virtual node-node-uuid

[Jonas Smedegaard]

Package: yarnpkg
Version: 1.22.4-4
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

yarnpkg depends on node-node-uuid.

node-node-uuid was deprecated 2 yars ago, replaced by node-uuid.

Please change to instead depend on node-uuid.

Raised severity as this is the last package relying on the old name,
and we want to drop it before freeze.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/FLKwACgkQLHwxRsGg
ASH50g/+M4XGPGcy9FRzeKx/9mh5jiyo3G6uJkr6gi8+aVDCKwWf/WnnEdAsPiL0
3SZdhih+EffgzkDLv/On6h5cMcSRr54I2QtKdwpRWS2Dr/RbhjWp9+FgQdCr7qPC
FJxXJdzANYqxhLVRhmZOj5VDHVJNfFc9VlhJXdQ8a9nPK11cO5ksZ4a49MOZYvkL
a19BsiMMqFjSDqzGUb7rOiouTUS9HQixt4Kn0en2qhOZ+1Ff1T/EmCe9ZPSdJ0Ou
ic3MQGf2mhJkKGf3Ebd591y1pfIeH/rWpqIJrzMQchvikwGn48FxHXVj3bigOHHy
Mt4GbNfXq3CxwN2OwSajPYM5YuLaMYPTUrwfGqunheZG+YHc4hVbKbdJD3SghW7w
LNTQOZeBM+Lxw8o4TYJCpJaMWh6upgldRUzhytGvQHDLY+OJ7brB+tVthocDGgXD
04529fWiBzgPV02OXNlWofdFCYRZjj0+Jy0BuPODEPDpN4mR7RbIRS72P64BeNZf
PAvW2J5As60O1aw6jKvt/022tNKuXkSbqqs6RinlB++9YMh7C/O4CSQGRV6wimgv
kBJDysPD9NCV6uA4lVHwgfOFoL7BQSlCyAjYcCX2txDA3yuHV58eNPYBoqa3cvdS
5g9Ilq2GIebzFQv747KJaubDteoxIf0nSAMrrsmjbX45V/PKSJA=
=hRxU
-END PGP SIGNATURE-

Bug#976047: marked as done (shoogle: flaky autopkgtest on ci.debian.net and missing needs-internet restriction)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 17:23:22 +
with message-id 
and subject line Bug#976047: fixed in shoogle 0.1.4-10
has caused the Debian Bug report #976047,
regarding shoogle: flaky autopkgtest on ci.debian.net and missing 
needs-internet restriction
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.)


-- 
976047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shoogle
Version: 0.1.4-9
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Control: affects -1 python3-defaults

Dear maintainer(s),

shoogle has an autopkgtest, great. However, it fails more often than it
passes [1].

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

I copied the output at the bottom of this report. Can you please look
into it and make the test more robust (against network issues). If you
keep the test that requires internet, you should add the needs-internet
restriction too.

Paul

[1] https://ci.debian.net/packages/s/shoogle/testing/amd64/
[2] https://ci.debian.net/packages/s/shoogle/testing/arm64/

https://ci.debian.net/data/autopkgtest/testing/amd64/s/shoogle/8333563/log.gz

==
FAIL: test_main_execute_with_missing_parameter
(tests.test_shoogle.TestShoogle)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.es_gm45h/downtmp/build.BYz/src/tests/test_shoogle.py",
line 158, in test_main_execute_with_missing_parameter
self.assertIn('Missing required parameter "task"', e.err)
AssertionError: 'Missing required parameter "task"' not found in
'/tmp/autopkgtest-lxc.es_gm45h/downtmp/build.BYz/src/shoogle/common.py:34:
ResourceWarning: unclosed \n
apis =
download("https://www.googleapis.com/discovery/v1/apis;)\nResourceWarning:
Enable tracemalloc to get the object allocation
traceback\n/tmp/autopkgtest-lxc.es_gm45h/downtmp/build.BYz/src/shoogle/common.py:64:
ResourceWarning: unclosed \n
service_json = download(service["discoveryRestUrl"])\nResourceWarning:
Enable tracemalloc to get the object allocation traceback\n[ERROR]
googleapiclient.discovery: Missing required parameter "tasklist"\n'

--
Ran 12 tests in 5.137s

FAILED (failures=1)
Test failed: 
error: Test failed: 
autopkgtest [12:10:55]: test test-unittest: ---]
--- End Message ---
--- Begin Message ---
Source: shoogle
Source-Version: 0.1.4-10
Done: David Steele 

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

Debian distribution maintenance software
pp.
David Steele  (supplier of updated shoogle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 30 Nov 2020 11:52:18 -0500
Source: shoogle
Architecture: source
Version: 0.1.4-10
Distribution: unstable
Urgency: medium
Maintainer: David Steele 
Changed-By: David Steele 
Closes: 976047
Changes:
 shoogle (0.1.4-10) unstable; urgency=medium
 .
   * Resolve autopkgtest instability (Closes: #976047).
Checksums-Sha1:
 5cd35f0063668b1148c8d6fb3385bf5d5f2c959b 1958 shoogle_0.1.4-10.dsc
 e6f82f8e71d7376efdf8c0d7d2778e37c3586be6 6700 shoogle_0.1.4-10.debian.tar.xz
 5d7d27885b383385c9a59f3a91c4f920142a124d 6720 shoogle_0.1.4-10_source.buildinfo
Checksums-Sha256:
 bf4a2019971b0e18b1bb29fcbebf2a51e96ad9adeed6577a3374e85a3c2b4f98 1958 
shoogle_0.1.4-10.dsc
 bd5b59fad00c575c97795cadd67efb8c71ce0a47fdb8ec15d742e9716a5ae844 6700 
shoogle_0.1.4-10.debian.tar.xz
 03842f53adbf8ffef5f3ecb5cb7783c6b8b56e7276d9cec4576b95d937e38f40 6720 
shoogle_0.1.4-10_source.buildinfo
Files:
 3a2d5ed2e75351c9ea1c7c5954fb13d8 1958 devel optional shoogle_0.1.4-10.dsc
 

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com

As it seems, arch builds its kernel with the same parameter disabled, as seen
on line 6528 here
https://github.com/archlinux/svntogit-packages/blob/packages/linux/trunk/config

And yet, nvidia 340 from aur still works, possibly because of this patch
https://aur.archlinux.org/cgit/aur.git/tree/0003-kernel-5.9.patch?h=nvidia-340xx

As I have said in previous bug reports, I really do not know how to patch
stuff. But if someone guides me, I am willing to try it with debian's 5.9.11.



-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

/proc/version:
Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-16) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.152444] Console: colour VGA+ 80x25
[0.589867] pci :01:00.0: vgaarb: setting as boot VGA device
[0.589867] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.589867] pci :01:00.0: vgaarb: bridge control possible
[0.589867] vgaarb: loaded
[0.773909] Linux agpgart interface v0.103
[3.150010] nvidia: loading out-of-tree module taints kernel.
[3.150022] nvidia: module license 'NVIDIA' taints kernel.
[3.212616] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.246017] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.253080] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.253092] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.620844] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.750995] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.780945] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.787570] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[3.788308] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
[9.684983] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Nov 30 15:29 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Nov 30 15:30 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Nov 30 15:30 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Nov 30 15:29 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jun  8 11:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   25 Jun  8 11:36 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jun  8 11:36 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jun  8 11:36 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jun  8 11:36 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jun  8 11:36 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jun  8 11:36 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jun  8 11:36 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Jan  5  2020 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root 

Bug#973096: python-bleach: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

[Lee Garrett]

Hi,

I've prepared a fix for this package at

https://salsa.debian.org/python-team/packages/python-bleach/-/merge_requests/1

I lack permissions to merge to master and upload this package. The patch
itself is based on a pending upstream MR, details are in the quilt patch
annotation.

Regards,
Lee

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com

That is tough! It may also be the end for me on debian, after ~13 years,
because my financial status does not allow a hw upgrade right now. Why is that
kernel parameter so important?
Can't you just make a patch that works?
Also, will the same happen on future versions of the kernel, e.g in the
forthcoming 5.10 which is an lts?

As for building the kernel on my own, I think I am not able to. I tried it once
for an old atom pc and I failed completely. For now, I have uninstalled linux-
image-amd64 so as to stay in 5.9.9 for as long as I can. I may check other
kernels for debian later this week, e.g. liquorix, just in case they are built
differently.



-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

/proc/version:
Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-16) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.152444] Console: colour VGA+ 80x25
[0.589867] pci :01:00.0: vgaarb: setting as boot VGA device
[0.589867] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.589867] pci :01:00.0: vgaarb: bridge control possible
[0.589867] vgaarb: loaded
[0.773909] Linux agpgart interface v0.103
[3.150010] nvidia: loading out-of-tree module taints kernel.
[3.150022] nvidia: module license 'NVIDIA' taints kernel.
[3.212616] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.246017] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.253080] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.253092] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.620844] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.750995] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.780945] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.787570] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[3.788308] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
[9.684983] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Nov 30 15:29 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Nov 30 15:30 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Nov 30 15:30 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Nov 30 15:29 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jun  8 11:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   25 Jun  8 11:36 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jun  8 11:36 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jun  8 11:36 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jun  8 11:36 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jun  8 11:36 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jun  8 11:36 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jun  8 11:36 

Bug#976111: topydo 0.13-3 upload seems to hang ci.debian.net workers while testing todo.txt-base

[David Steele]

On Sun, Nov 29, 2020 at 3:51 PM Paul Gevers  wrote:

> Source: topydo
> Version: 0.13-3
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: issue
>
> Dear David,
>
> I have no idea what's happening, but currently we have multiple workers
> (on different architectures) off-line on the ci.debian.net
> infrastructure. In the current (short) list of pending tests,
> todo.txt-base sticks out as being triggered (by topydo) some time ago
> and waiting on all architectures. armhf finished (tmpfail) while I was
> writing this message so I noticed it already ran multiple times but the
> test on armhf times out after 2:55 hours (previous tests were under 1
> minute) with an error in autopkgtest so is treated as tmpfail (and
> retried).
>
> Can you help us investigate what's going on? What is topydo doing?


Topydo is a package implementing a todo.txt client.

Todo.txt-base is a helper program adding features to todo.txt clients.

Both are new, and I am new to the alternatives environment. I started by
having todo.txt-base serve as the application installed as the todo/todo.txt
application. Packages using this model were accepted, but turned out
to be unworkable as I attempted to expand the ecosystem.

So there are new versions of topydo and todo.txt-base in sid which use
the todo.txt provider (topydo) as the home for the "todo" and "todo.txt"
applications. It calls todo.txt-base features as necessary for the added
features. Autopkgtests pass in sid.

All works well, until you test the new version of one package along with
the old version of the other. In one scenario there is a recursion, where
topydo ends up calling itself via the alternatives hook.

I didn't worry too much about this when I submitted the new packages,
because the issue was transient, and the common popcon is like 5. I
failed to consider that ci would evaluate the packages independently,
and would choke.

I'm reworking the packages so that they can manage this upgrade
without complaint. That process will take at least days. I'd be willing to
consider more drastic means to resolve this, either by overriding the
failures this one time, or by deleting the packages from the distribution
and starting fresh.

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[Andreas Beckmann]

On 11/30/20 4:59 PM, Andreas Beckmann wrote:
> I'm afraid that is the end for 340xx, at least if you want to use a
> recent kernel (i.e. newer than stable).

Or you build your own kernel - rebuilding the Debian kernel with some
configure option toggled should not be that difficult.


Andreas

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[Andreas Beckmann]

On 11/30/20 4:34 PM, jim_p wrote:
> So, this change is/was really needed? What will happen to nvidia 340 now?
> One of the reasons I am still on debian is that it still packages it. I can 
> not
> find a patch for it so as to help more.
> Also, will this change be made in future kernel builds as well?

I'm afraid that is the end for 340xx, at least if you want to use a
recent kernel (i.e. newer than stable).

Andreas

Processed: Re: Bug#975344: libapache-mod-auth-kerb: Uses Internal Krb5 APIs [test this patch please]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of 
internal
Added tag(s) pending.

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

Bug#975344: libapache-mod-auth-kerb: Uses Internal Krb5 APIs [test this patch please]

[Sam Hartman]

control: tags -1 pending

I've uploaded to delayed/3, using your minimal patch.

Thanks.


--Sam

Bug#957572: marked as done (munipack: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 15:33:51 +
with message-id 
and subject line Bug#957572: fixed in munipack 0.5.12-1
has caused the Debian Bug report #957572,
regarding munipack: 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.)


-- 
957572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:munipack
Version: 0.5.11-2.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/munipack_0.5.11-2.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

[...]
checking for library containing gethostbyname... none required
checking for library containing connect... none required
checking fitsio.h usability... yes
checking fitsio.h presence... yes
checking for fitsio.h... yes
checking for ffclos in -lcfitsio... yes
checking for lmder_ in -lminpack... yes
checking for __oakleaf_MOD_rmean_real64 in -loakleaf... yes
checking for wx-config... /usr/bin/wx-config
checking for wxWidgets version >= 3.0.0... yes (version 3.0.4)
checking for wxWidgets static library... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating lib/Makefile
config.status: creating preprocess/Makefile
config.status: creating kombine/Makefile
config.status: creating photometry/Makefile
config.status: creating artificial/Makefile
config.status: creating fits/Makefile
config.status: creating list/Makefile
config.status: creating astrometry/Makefile
config.status: creating colouring/Makefile
config.status: creating vo/Makefile
config.status: creating munipack/Makefile
config.status: creating wxMathPlot/Makefile
config.status: creating xmunipack/Makefile
config.status: creating doc/Makefile
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --disable-maintainer-mode

 Configured Munipack:

  Virtual Observatory support enabled: yes
   Command line interface enabled: yes
 Graphical User Interface enabled: yes
  Bundle installation: no

   dh_auto_build -O--no-parallel
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in lib
make[3]: Entering directory '/<>/lib'
gfortran -I../include -J../include -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -ffpe-summary=invalid,zero,overflow -c -o minpack.o 
minpack.f90
gfortran -I../include -J../include -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -ffpe-summary=invalid,zero,overflow -c -o minpacks.o 
minpacks.f95
rm -f libminpacks.a
ar cru libminpacks.a minpack.o minpacks.o 
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib libminpacks.a
gfortran -I../include -J../include -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -ffpe-summary=invalid,zero,overflow -c -o fitsio.o 
fitsio.f95
fitsio.f95:1411:45:

 1411 | call ftpclj(unit,colnum,frow,felem,nrows,values,status)
  | 1
..
 1427 | call ftpclj(unit,colnum,frow,felem,nrows,values,status)
  | 2
Error: Type mismatch between actual argument at (1) and actual argument at (2) 
(LOGICAL(4)/INTEGER(4)).
make[3]: *** [Makefile:577: fitsio.o] Error 1
make[3]: Leaving directory '/<>/lib'

Bug#976056: nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from Linux 5.9.11 onwards

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-8
Followup-For: Bug #976056
X-Debbugs-Cc: pitsior...@gmail.com

So, this change is/was really needed? What will happen to nvidia 340 now?
One of the reasons I am still on debian is that it still packages it. I can not
find a patch for it so as to help more.
Also, will this change be made in future kernel builds as well?



-- Package-specific info:
uname -a:
Linux mitsos 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

/proc/version:
Linux version 5.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 10.2.0 (Debian 10.2.0-16) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:8490]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.152444] Console: colour VGA+ 80x25
[0.589867] pci :01:00.0: vgaarb: setting as boot VGA device
[0.589867] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.589867] pci :01:00.0: vgaarb: bridge control possible
[0.589867] vgaarb: loaded
[0.773909] Linux agpgart interface v0.103
[3.150010] nvidia: loading out-of-tree module taints kernel.
[3.150022] nvidia: module license 'NVIDIA' taints kernel.
[3.212616] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[3.246017] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.253080] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[3.253092] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 
11 11:06:58 PST 2019
[3.620844] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[3.750995] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[3.780945] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[3.787570] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[3.788308] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
[9.684983] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs

Device node permissions:
crw-rw+ 1 root video 226,   0 Nov 30 15:29 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Nov 30 15:30 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Nov 30 15:30 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Nov 30 15:29 pci-:01:00.0-card -> ../card0
video:*:44:jim

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jun  8 11:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jun  8 11:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jun  8 11:36 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   25 Jun  8 11:36 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jun  8 11:36 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jun  8 11:36 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jun  8 11:36 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jun  8 11:36 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Jun  8 11:36 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Jun  8 11:36 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Jan  5  2020 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-340xx
lrwxrwxrwx 1 root root   57 Jan  5  2020 
/etc/alternatives/nvidia--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libEGL.so.1
lrwxrwxrwx 1 root root   56 Jan  5  2020 

Bug#976147: [debian-mysql] Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails

[Faustin Lammler]

Hi Jörg!
I am not sure that I understand what are the steps that I could follow
to verify this.

Are you trying to dist-upgrade from buster to sid?

In that case, I was not able to reproduce the error in a container with
the following steps:
| # podman run -it debian:10 bash
| # apt update
| # apt upgrade
| # apt install mariadb-server -y
| # dpkg -l | grep mariadb-server
| ii  mariadb-server   1:10.3.25-0+deb10u1 all   MariaDB database 
server (metapackage depending on the latest version)
| ii  mariadb-server-10.3  1:10.3.25-0+deb10u1 amd64 MariaDB database 
server binaries
| ii  mariadb-server-core-10.3 1:10.3.25-0+deb10u1 amd64 MariaDB database core 
server files
| # printf 'deb http://deb.debian.org/debian/ sid main' >/etc/apt/sources.list
| # apt update
| # apt upgrade
| # apt dist-upgrade
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| Calculating upgrade... Done
| The following packages were automatically installed and are no longer 
required:
|   fdisk libapt-pkg5.0 libfdisk1 libffi6 libhogweed4 libnettle6 libperl5.28 
libreadline5 libreadline7 perl-modules-5.28
| Use 'apt autoremove' to remove them.
| The following packages will be REMOVED:
|   galera-3 mariadb-client-10.3 mariadb-client-core-10.3 mariadb-server-10.3 
mariadb-server-core-10.3
| The following NEW packages will be installed:
|   galera-4 libedit2 libprocps8 mariadb-client-10.5 mariadb-client-core-10.5 
mariadb-server-10.5 mariadb-server-core-10.5 procps
| The following packages have been kept back:
|   gcc-8-base
| The following packages will be upgraded:
|   mariadb-server
| 1 upgraded, 8 newly installed, 5 to remove and 1 not upgraded.
| Need to get 14.5 MB of archives.
| After this operation, 11.1 MB disk space will be freed.
| Do you want to continue? [Y/n]
| ...
| # dpkg -l | grep mariadb-server
| ii  mariadb-server   1:10.5.8-3  all   MariaDB database 
server (metapackage depending on the latest version)
| rc  mariadb-server-10.3  1:10.3.25-0+deb10u1 amd64 MariaDB database 
server binaries
| ii  mariadb-server-10.5  1:10.5.8-3  amd64 MariaDB database 
server binaries
| ii  mariadb-server-core-10.5 1:10.5.8-3  amd64 MariaDB database core 
server files

Can you please give us more details about the steps?

Regards,
Faustin


signature.asc
Description: PGP signature

Bug#975275: marked as done (ceph: CVE-2020-25660: CEPHX_V2 replay attack protection lost)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 14:33:56 +
with message-id 
and subject line Bug#975275: fixed in ceph 14.2.15-1
has caused the Debian Bug report #975275,
regarding ceph: CVE-2020-25660: CEPHX_V2 replay attack protection lost
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.)


-- 
975275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 14.2.9-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for ceph.

CVE-2020-25660[0]:
| cephx authentication protocol does not verify ceph clients correctly

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-25660
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25660
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1890354

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.15-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Nov 2020 23:58:00 +0100
Source: ceph
Architecture: source
Version: 14.2.15-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 956750 957079 963760 975275
Changes:
 ceph (14.2.15-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #956750):
 - Fix FTBFS with GCC-10 (Closes: #957079).
 - Fix CVE-2020-10753 (Closes: #963760).
 - Fix CVE-2020-25660 (Closes: #975275).
   * Refreshed patches:
 - 32bit-avoid-size_t.patch
 - add-option-to-disable-ceph-dencoder.patch
 - bluefs-use-uint64_t-for-len.patch
 - disable-crypto.patch
 - mds-purgequeue-use_uint64_t.patch
   * Raw wrap-and-sort -bastk.
   * Added myself as uploader.
   * Added librdkafka-dev as build-depends.
   * Fixed debian/libcephfs-dev.install.
   * debian/calc-max-parallel.sh: allow for more values of --max-parallel so
 that ceph builds faster on more powerful machines.
   * Add a patch to make Ceph aware of Python 3.9:
 - make-ceph-python-3.9-aware.patch
   * Add a debian/source/options to ignore CRLF to CR changes.
   * Use --home in ceph-common.postinst when creating the Ceph system user.
   * Updated debian/libcephfs2.symbols (added 3 new symbols).
   * Package: ceph-resource-agents, switch Priority: to optional.
   * Add debian/source.lintian-overrides to allow .js which shipped by upstream
 in both compiled and source version.
   * Removed now useless dpkg-maintscript-helper rm_conffile: they have been
 around for more than one release.
   * debian/ceph-osd.postinst: remove as it's doing nothing.
   * Fix debian/lib{rbd1,rados2}.symbols (3 missing symbols).
Checksums-Sha1:
 787a030f50e004093e3fe259316f1d196b2b1a6e 5915 ceph_14.2.15-1.dsc
 81c88c8705ad45e6b83ffa8013f007d84b5cb89f 129254705 ceph_14.2.15.orig.tar.gz
 49deecdad40d7527a4bdcf886ff0525d6ea8e9a0 110008 ceph_14.2.15-1.debian.tar.xz
 1f5c1fbd52c022aa7bf1c4ead85f6733e7d95266 34467 ceph_14.2.15-1_amd64.buildinfo
Checksums-Sha256:
 0d51b04606e2c1a671707c8272e75748cfe99005d4206861dba458089ebd4e8a 5915 
ceph_14.2.15-1.dsc
 ccc616a17f0a18a9b1de7417e870847740f329d52cb5ab35230e7424cfbd04e7 129254705 
ceph_14.2.15.orig.tar.gz
 b9e009bb78c35363eaedc0ef31122314febae0859d6bdafed4d0273a39f00b96 110008 
ceph_14.2.15-1.debian.tar.xz
 c8e9c840c5ecba26a33c074774133e5b6550fe6f1b729434260c4b38b08c3f4c 34467 
ceph_14.2.15-1_amd64.buildinfo
Files:
 10b5dcb170278b53c77ac12dc1a4e5a5 5915 admin optional ceph_14.2.15-1.dsc
 4b7f92e537bb4c5e1cd3d3972728a2f5 129254705 admin optional 
ceph_14.2.15.orig.tar.gz
 ab150c24bf9eb0a03afc7b1b65edfebe 110008 admin optional 

Bug#963760: marked as done (new upstream release (1.4.11))

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 14:33:56 +
with message-id 
and subject line Bug#963760: fixed in ceph 14.2.15-1
has caused the Debian Bug report #963760,
regarding new upstream release (1.4.11)
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.)


-- 
963760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph
Severity: important
Tags: security

Hi,

Ceph 1.4.10 has been released, fixing CVE-2020-10753. It would be nice
if you could upgrade the package in unstable.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.15-1
Done: Thomas Goirand 

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Nov 2020 23:58:00 +0100
Source: ceph
Architecture: source
Version: 14.2.15-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 956750 957079 963760 975275
Changes:
 ceph (14.2.15-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #956750):
 - Fix FTBFS with GCC-10 (Closes: #957079).
 - Fix CVE-2020-10753 (Closes: #963760).
 - Fix CVE-2020-25660 (Closes: #975275).
   * Refreshed patches:
 - 32bit-avoid-size_t.patch
 - add-option-to-disable-ceph-dencoder.patch
 - bluefs-use-uint64_t-for-len.patch
 - disable-crypto.patch
 - mds-purgequeue-use_uint64_t.patch
   * Raw wrap-and-sort -bastk.
   * Added myself as uploader.
   * Added librdkafka-dev as build-depends.
   * Fixed debian/libcephfs-dev.install.
   * debian/calc-max-parallel.sh: allow for more values of --max-parallel so
 that ceph builds faster on more powerful machines.
   * Add a patch to make Ceph aware of Python 3.9:
 - make-ceph-python-3.9-aware.patch
   * Add a debian/source/options to ignore CRLF to CR changes.
   * Use --home in ceph-common.postinst when creating the Ceph system user.
   * Updated debian/libcephfs2.symbols (added 3 new symbols).
   * Package: ceph-resource-agents, switch Priority: to optional.
   * Add debian/source.lintian-overrides to allow .js which shipped by upstream
 in both compiled and source version.
   * Removed now useless dpkg-maintscript-helper rm_conffile: they have been
 around for more than one release.
   * debian/ceph-osd.postinst: remove as it's doing nothing.
   * Fix debian/lib{rbd1,rados2}.symbols (3 missing symbols).
Checksums-Sha1:
 787a030f50e004093e3fe259316f1d196b2b1a6e 5915 ceph_14.2.15-1.dsc
 81c88c8705ad45e6b83ffa8013f007d84b5cb89f 129254705 ceph_14.2.15.orig.tar.gz
 49deecdad40d7527a4bdcf886ff0525d6ea8e9a0 110008 ceph_14.2.15-1.debian.tar.xz
 1f5c1fbd52c022aa7bf1c4ead85f6733e7d95266 34467 ceph_14.2.15-1_amd64.buildinfo
Checksums-Sha256:
 0d51b04606e2c1a671707c8272e75748cfe99005d4206861dba458089ebd4e8a 5915 
ceph_14.2.15-1.dsc
 ccc616a17f0a18a9b1de7417e870847740f329d52cb5ab35230e7424cfbd04e7 129254705 
ceph_14.2.15.orig.tar.gz
 b9e009bb78c35363eaedc0ef31122314febae0859d6bdafed4d0273a39f00b96 110008 
ceph_14.2.15-1.debian.tar.xz
 c8e9c840c5ecba26a33c074774133e5b6550fe6f1b729434260c4b38b08c3f4c 34467 
ceph_14.2.15-1_amd64.buildinfo
Files:
 10b5dcb170278b53c77ac12dc1a4e5a5 5915 admin optional ceph_14.2.15-1.dsc
 4b7f92e537bb4c5e1cd3d3972728a2f5 129254705 admin optional 
ceph_14.2.15.orig.tar.gz
 ab150c24bf9eb0a03afc7b1b65edfebe 110008 admin optional 
ceph_14.2.15-1.debian.tar.xz
 0512a5c8bb6f0c253313c6bc990fd517 34467 admin optional 
ceph_14.2.15-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/E9u8ACgkQ1BatFaxr
Q/7jmQ//fcbse7DmhMTre2XGdbqsLymgDP/r9cmiPo4dLALUWLwnNtiqS9deJPaO
jCvTKwkYLUrAF0QJPxarlFHU6SSw92denY0LYO++cPyNjVq7duipGFEh/EMrUdbv
9/NnOdcODg9lc9T49pYDpDW325JXGs4QXMi/g+VTJvJ6MSQTyh/iHvxE2WKsK5X7
8Zebs972nmcD5SMOKZjCv1Ew42XGK+smO/YgwcW7Pxf5+E9JXRzQUE7zOWRFb5qg

Bug#957079: marked as done (ceph: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 14:33:56 +
with message-id 
and subject line Bug#957079: fixed in ceph 14.2.15-1
has caused the Debian Bug report #957079,
regarding ceph: 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.)


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

[...]
In file included from /<>/src/msg/msg_types.h:24,
 from /<>/src/common/entity_name.h:20,
 from /<>/src/auth/Auth.h:19,
 from /<>/src/auth/AuthSessionHandler.h:20,
 from /<>/src/msg/async/AsyncConnection.h:29,
 from /<>/src/msg/async/Protocol.h:10,
 from /<>/src/msg/async/ProtocolV1.h:7,
 from /<>/src/msg/async/ProtocolV1.cc:4:
/<>/src/include/blobhash.h: In member function 
‘std::_Hashtable<_Key, _Value, _Alloc, _ExtractKey, _Equal, _H1, _H2, _Hash, 
_RehashPolicy, _Traits>::iterator std::_Hashtable<_Key, _Value, _Alloc, 
_ExtractKey, _Equal, _H1, _H2, _Hash, _RehashPolicy, _Traits>::find(const 
key_type&) [with _Key = entity_addrvec_t; _Value = std::pair >; _Alloc = 
std::allocator > >; _ExtractKey = 
std::__detail::_Select1st; _Equal = std::equal_to; _H1 = 
std::hash; _H2 = std::__detail::_Mod_range_hashing; _Hash = 
std::__detail::_Default_ranged_hash; _RehashPolicy = 
std::__detail::_Prime_rehash_policy; _Traits = 
std::__detail::_Hashtable_traits]’:
/<>/src/include/blobhash.h:38:10: warning: iteration 4 invokes 
undefined behavior [-Waggressive-loop-optimizations]
   38 |   sh += 8;
  |   ~~~^~~~
/<>/src/include/blobhash.h:36:12: note: within this loop
   36 | while (len) {
  |^~~
In file included from /<>/src/msg/msg_types.h:24,
 from /<>/src/common/entity_name.h:20,
 from /<>/src/auth/Auth.h:19,
 from /<>/src/auth/AuthSessionHandler.h:20,
 from /<>/src/msg/async/AsyncConnection.h:29,
 from /<>/src/msg/async/Protocol.h:10,
 from /<>/src/msg/async/ProtocolV2.h:9,
 from /<>/src/msg/async/ProtocolV2.cc:6:
/<>/src/include/blobhash.h: In member function 
‘std::_Hashtable<_Key, _Value, _Alloc, _ExtractKey, _Equal, _H1, _H2, _Hash, 
_RehashPolicy, _Traits>::iterator std::_Hashtable<_Key, _Value, _Alloc, 
_ExtractKey, _Equal, _H1, _H2, _Hash, _RehashPolicy, _Traits>::find(const 
key_type&) [with _Key = entity_addrvec_t; _Value = std::pair >; _Alloc = 
std::allocator > >; _ExtractKey = 
std::__detail::_Select1st; _Equal = std::equal_to; _H1 = 
std::hash; _H2 = std::__detail::_Mod_range_hashing; _Hash = 
std::__detail::_Default_ranged_hash; _RehashPolicy = 
std::__detail::_Prime_rehash_policy; _Traits = 
std::__detail::_Hashtable_traits]’:
/<>/src/include/blobhash.h:38:10: warning: iteration 4 invokes 
undefined behavior [-Waggressive-loop-optimizations]
   38 |   sh += 8;
  |   ~~~^~~~
/<>/src/include/blobhash.h:36:12: note: within this loop
   36 | while (len) {
  |^~~
[  7%] Building CXX object 
src/msg/CMakeFiles/common-msg-objs.dir/async/EventSelect.cc.o
cd /<>/obj-x86_64-linux-gnu/src/msg && /usr/bin/c++  
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D__linux__ 

Bug#972908: marked as done (ceph fbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 14:33:56 +
with message-id 
and subject line Bug#957079: fixed in ceph 14.2.15-1
has caused the Debian Bug report #957079,
regarding ceph fbfs with python3.9
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.)


-- 
957079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ceph
Version: 14.2.9-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ceph ftbfs with python3.9; to reproduce, you can use the repositories found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ceph_14.2.9-1build1_amd64-2020-10-24T18:28:45Z.build

[...]
In file included from /<>/src/common/bit_str.cc:14:
/<>/src/common/bit_str.h:23:13: error: variable or field
‘print_bit_str’ declared void
   23 | extern void print_bit_str(
  | ^
/<>/src/common/bit_str.h:24:5: error: ‘uint64_t’ was not
declared in this scope; did you mean ‘u_int64_t’?
   24 | uint64_t bits,
  | ^~~~
  | u_int64_t
/<>/src/common/bit_str.h:25:10: error: ‘ostream’ is not a
member of ‘std’
   25 | std::ostream ,
  |  ^~~
/<>/src/common/bit_str.h:18:1: note: ‘std::ostream’ is defined
in header ‘’; did you forget to ‘#include ’?
   17 | #include 
  +++ |+#include 
   18 |
/<>/src/common/bit_str.h:25:19: error: ‘out’ was not declared
in this scope
   25 | std::ostream ,
  |   ^~~
/<>/src/common/bit_str.h:26:5: error: expected primary-expression
before ‘const’
   26 | const std::function ,
  | ^
/<>/src/common/bit_str.h:27:5: error: expected primary-expression
before ‘bool’
   27 | bool dump_bit_val = false);
  | ^~~~
/<>/src/common/bit_str.h:29:13: error: variable or field
‘dump_bit_str’ declared void
   29 | extern void dump_bit_str(
  | ^~~~
/<>/src/common/bit_str.h:30:5: error: ‘uint64_t’ was not
declared in this scope; did you mean ‘u_int64_t’?
   30 | uint64_t bits,
  | ^~~~
  | u_int64_t
/<>/src/common/bit_str.h:31:21: error: expected primary-expression
before ‘*’ token
   31 | ceph::Formatter *f,
  | ^
/<>/src/common/bit_str.h:31:22: error: ‘f’ was not declared in
this scope
   31 | ceph::Formatter *f,
  |  ^
/<>/src/common/bit_str.h:32:5: error: expected primary-expression
before ‘const’
   32 | const std::function ,
  | ^
/<>/src/common/bit_str.h:33:5: error: expected primary-expression
before ‘bool’
   33 | bool dump_bit_val = false);
  | ^~~~
make[3]: *** [src/common/CMakeFiles/common-common-objs.dir/build.make:449:
src/common/CMakeFiles/common-common-objs.dir/bit_str.cc.o] Error 1
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.15-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Nov 2020 23:58:00 +0100
Source: ceph
Architecture: source
Version: 14.2.15-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 956750 957079 963760 975275
Changes:
 ceph (14.2.15-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #956750):
 - Fix FTBFS with GCC-10 (Closes: #957079).
 - Fix CVE-2020-10753 (Closes: #963760).
 - Fix CVE-2020-25660 (Closes: #975275).
   * Refreshed patches:
 - 32bit-avoid-size_t.patch
 - add-option-to-disable-ceph-dencoder.patch
 - bluefs-use-uint64_t-for-len.patch
 - disable-crypto.patch
 - 

Processed: Re: Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to 
build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
Ignoring request to change severity of Bug 976056 to the same value.
> retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled from 
> Linux 5.9.11 onwards
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: Fails to 
build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)
Changed Bug title to 'nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled 
from Linux 5.9.11 onwards' from 'nvidia-legacy-340xx-driver: Fails to build 
with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)'.
> tag -1 upstream wontfix
Bug #976056 [nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires 
DRM_LEGACY, disabled from Linux 5.9.11 onwards
Added tag(s) upstream and wontfix.

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

Bug#976056: nvidia-legacy-340xx-driver: Fails to build with kernel 5.9.11 (package linux-image-5.9.0-4-amd64)

[Andreas Beckmann]

Control: severity -1 serious
Control: retitle -1 nvidia-legacy-340xx-driver: requires DRM_LEGACY, disabled 
from Linux 5.9.11 onwards
Control: tag -1 upstream wontfix

On 11/29/20 1:37 PM, Salvatore Bonaccorso wrote:
> Some background: In the 5.9.11-1 upload for src:linux we disabled
> NOUVEAU_LEGACY_CTX_SUPPORT which was keeping DRM_LEGACY enabled (cf.
> #975038). The intention of disabling DRM_LEGACY was actually already
> much earlier in 5.5.17-1, but due to the above it was kept enabled
> until noticed now.

Thanks for that information.

Andreas

Processed: Confirm bug

[Debian Bug Tracking System]

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

> tags 933798 confirmed
Bug #933798 [libnetfilter-conntrack-dev] libnetfilter-conntrack-dev: unhandled 
symlink to directory conversion: /usr/share/doc/PACKAGE
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#973098: marked as done (twms: FTBFS: error: Error: setup script specifies an absolute path:)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 13:33:21 +
with message-id 
and subject line Bug#973098: fixed in twms 0.07z+git20201130+6edd37d-1
has caused the Debian Bug report #973098,
regarding twms: FTBFS: error: Error: setup script specifies an absolute path:
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.)


-- 
973098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twms
Version: 0.07z+git20200829+cb7d39a-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):
>  debian/rules build
> dh build --with=python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/dist.py:466: UserWarning: The 
> version specified ('0.06y') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/daemon.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/fetchers.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/correctify.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/overview.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/__init__.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/bbox.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/gpxparse.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/twms.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/projections.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/drawing.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/canvas.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/capabilities.py -> 
> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/reproject.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/sketch.py -> /<>/.pybuild/cpython3_3.9/build/twms
> copying twms/filter.py -> /<>/.pybuild/cpython3_3.9/build/twms
> running egg_info
> creating twms.egg-info
> writing twms.egg-info/PKG-INFO
> writing dependency_links to twms.egg-info/dependency_links.txt
> writing entry points to twms.egg-info/entry_points.txt
> writing requirements to twms.egg-info/requires.txt
> writing top-level names to twms.egg-info/top_level.txt
> writing manifest file 'twms.egg-info/SOURCES.txt'
> reading manifest file 'twms.egg-info/SOURCES.txt'
> writing manifest file 'twms.egg-info/SOURCES.txt'
> error: Error: setup script specifies an absolute path:
> 
> /<>/README.md
> 
> setup() arguments must *always* be /-separated paths relative to the
> setup.py directory, *never* absolute paths.
> 
> E: pybuild pybuild:352: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.9 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p "3.9 3.8" 
> returned exit code 13
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/twms_0.07z+git20200829+cb7d39a-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: twms
Source-Version: 0.07z+git20201130+6edd37d-1
Done: Andrej 

Processed: Falcon builds but autopkgtest fails (and some build time test failures are ignored

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #936503 [src:falcon] falcon: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#936503: Falcon builds but autopkgtest fails (and some build time test failures are ignored

[Andreas Tille]

Control: tags -1 pending

Hi,

since some time falcon[1] in Git builds with some cheating - some test
errors are simply ignored.  Also the autopktest is failing.  It would be
great if someone would spent time on these two RC bugs in an advent
calendar attempt.

Kind regards

Andreas.

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

-- 
http://fam-tille.de

Processed: Falcon builds but autopkgtest fails (and some build time test failures are ignored

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #902132 [src:falcon] falcon: FTBFS since python-networkx version 2.1-1; 
fails in test suite
Added tag(s) pending.

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

Bug#976147: Upgrade from mariadb-server-10.3 to mariadb-server-10.5 fails

[Jörg Frings-Fürst]

Package: mariadb-server-10.5
Version: 1:10.5.8-3
Severity: critical

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

on apt dist-upgrade on my sid system mariadb-server-10.3 are uninstalled and
mariadb-server-10.5 are not installed.

[quote]
Start-Date: 2020-11-30  12:52:01
Commandline: apt dist-upgrade
Requested-By: jff (1000)
Install: linux-headers-5.9.0-3-amd64:amd64 (5.9.9-1, automatic),
[...]
 libvirt-daemon:amd64 (6.9.0-1, 6.9.0-1+b1)
Remove: mariadb-server-core-10.3:amd64 (1:10.3.24-2), mariadb-server-10.3:amd64
(1:10.3.24-2), mariadb-server:amd64 (1:10.3.24-2)
End-Date: 2020-11-30  13:02:56
[/quote]

[quote]
$ sudo systemctl status mysql
[sudo] Passwort für jff:
Unit mysql.service could not be found.
[/quote]

[quote]
$ sudo apt install mariadb-server-10.5
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Die folgenden zusätzlichen Pakete werden installiert:
  galera-4 libhtml-template-perl mariadb-client-10.5 mariadb-client-core-10.5
mariadb-server-core-10.5 socat
Vorgeschlagene Pakete:
  libipc-sharedcache-perl mariadb-test
Die folgenden Pakete werden ENTFERNT:
  default-mysql-client mariadb-client-10.3 mariadb-client-core-10.3
Die folgenden NEUEN Pakete werden installiert:
  galera-4 libhtml-template-perl mariadb-client-10.5 mariadb-client-core-10.5
mariadb-server-10.5 mariadb-server-core-10.5 socat
0 aktualisiert, 7 neu installiert, 3 zu entfernen und 2 nicht aktualisiert.
Es müssen noch 14,0 MB von 14,4 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 96,9 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]
Holen:1 http://mirror.1und1.de/debian bullseye/main amd64 mariadb-client-10.5
amd64 1:10.5.8-3 [1.490 kB]
Holen:2 http://mirror.1und1.de/debian bullseye/main amd64 mariadb-client-
core-10.5 amd64 1:10.5.8-3 [778 kB]
Holen:3 http://mirror.1und1.de/debian bullseye/main amd64 galera-4 amd64
26.4.6-1 [928 kB]
Holen:4 http://mirror.1und1.de/debian bullseye/main amd64 mariadb-server-
core-10.5 amd64 1:10.5.8-3 [6.615 kB]
Holen:5 http://mirror.1und1.de/debian bullseye/main amd64 mariadb-server-10.5
amd64 1:10.5.8-3 [4.201 kB]
Es wurden 14,0 MB in 10 s geholt (1.356 kB/s).
Vorkonfiguration der Pakete ...
dpkg: mariadb-client-core-10.3: Abhängigkeitsprobleme, wird aber wie gefordert
dennoch entfernt:
 mariadb-client-10.3 hängt ab von mariadb-client-core-10.3 (>= 1:10.3.24-2).

(Lese Datenbank ... 527347 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von mariadb-client-core-10.3 (1:10.3.24-2) ...
dpkg: mariadb-client-10.3: Abhängigkeitsprobleme, wird aber wie gefordert
dennoch entfernt:
 default-mysql-client hängt ab von mariadb-client-10.3.

Entfernen von mariadb-client-10.3 (1:10.3.24-2) ...
Vormals nicht ausgewähltes Paket mariadb-client-10.5 wird gewählt.
(Lese Datenbank ... 527297 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../mariadb-client-10.5_1%3a10.5.8-3_amd64.deb
...
Entpacken von mariadb-client-10.5 (1:10.5.8-3) ...
dpkg: default-mysql-client: Abhängigkeitsprobleme, wird aber wie gefordert
dennoch entfernt:
 dbconfig-mysql hängt ab von default-mysql-client | virtual-mysql-client; aber:
  Paket default-mysql-client soll entfernt werden.
  Paket virtual-mysql-client ist nicht installiert.
  Paket mariadb-client-10.5, das virtual-mysql-client bereitstellt, ist noch
nicht konfiguriert.
  Paket mariadb-client-10.3, das virtual-mysql-client bereitstellt, ist nicht
installiert.
  Paket mariadb-client-10.1, das virtual-mysql-client bereitstellt, ist nicht
installiert.

(Lese Datenbank ... 527371 Dateien und Verzeichnisse sind derzeit installiert.)
Entfernen von default-mysql-client (1.0.5) ...
Vormals nicht ausgewähltes Paket mariadb-client-core-10.5 wird gewählt.
(Lese Datenbank ... 527368 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../0-mariadb-client-
core-10.5_1%3a10.5.8-3_amd64.deb ...
Entpacken von mariadb-client-core-10.5 (1:10.5.8-3) ...
Vormals nicht ausgewähltes Paket galera-4 wird gewählt.
Vorbereitung zum Entpacken von .../1-galera-4_26.4.6-1_amd64.deb ...
Entpacken von galera-4 (26.4.6-1) ...
Vormals nicht ausgewähltes Paket mariadb-server-core-10.5 wird gewählt.
Vorbereitung zum Entpacken von .../2-mariadb-server-
core-10.5_1%3a10.5.8-3_amd64.deb ...
Entpacken von mariadb-server-core-10.5 (1:10.5.8-3) ...
Vormals nicht ausgewähltes Paket socat wird gewählt.
Vorbereitung zum Entpacken von .../3-socat_1.7.3.4-1_amd64.deb ...
Entpacken von socat (1.7.3.4-1) ...
Vormals nicht ausgewähltes Paket mariadb-server-10.5 wird gewählt.
Vorbereitung zum Entpacken von .../4-mariadb-server-10.5_1%3a10.5.8-3_amd64.deb
...
/var/lib/mysql: found previous version 10.3
Entpacken von mariadb-server-10.5 (1:10.5.8-3) ...
Vormals nicht ausgewähltes Paket libhtml-template-perl wird gewählt.
Vorbereitung zum Entpacken von .../5-libhtml-template-perl_2.97-1_all.deb ...
Entpacken von 

Bug#971703: marked as done (golang-github-knadh-koanf: not buildable from source in Debian)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 12:33:25 +
with message-id 
and subject line Bug#971703: fixed in golang-github-knadh-koanf 0.10.0-2
has caused the Debian Bug report #971703,
regarding golang-github-knadh-koanf: not buildable from source in Debian
to be marked as done.

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

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


-- 
971703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-knadh-koanf
Version: 0.10.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy

Dear maintainers,

The golang-github-knadh-koanf package cannot be built in Debian due to
missing build-dependency, golang-github-rhnvrm-simples3-dev:

$ sudo apt build-dep golang-github-knadh-koanf
[sudo] password for vorlon: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:golang-github-knadh-koanf : Depends: 
golang-github-rhnvrm-simples3-dev but it is not installable
E: Unable to correct problems, you have held broken packages.
$

This package is not in the Debian NEW queue, and does not have an open ITP
bug.

Please take care of the missing build-dependency.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: golang-github-knadh-koanf
Source-Version: 0.10.0-2
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-knadh-koanf 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, 28 Nov 2020 15:15:13 +
Source: golang-github-knadh-koanf
Architecture: source
Version: 0.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 971703
Changes:
 golang-github-knadh-koanf (0.10.0-2) unstable; urgency=medium
 .
   * upload source package (Closes: #971703)
Checksums-Sha1:
 7f8e8ab8ee168b4d818855e41ec24aacec4812fb 2666 
golang-github-knadh-koanf_0.10.0-2.dsc
 cb5a4489d5f8cfde0103a08e3d4da93e87efce9e 2296 
golang-github-knadh-koanf_0.10.0-2.debian.tar.xz
 d963cbfc43fc96ed053096fd685851f5adb57464 7318 
golang-github-knadh-koanf_0.10.0-2_amd64.buildinfo
Checksums-Sha256:
 af9b42d690bd03d50a22b53cf16ed22e973ae0a3c205388cf1520b0b40638978 2666 
golang-github-knadh-koanf_0.10.0-2.dsc
 d491b1f8b02db829c818b3716795f4b100ce653d39fc06e786ac6523bee41657 2296 
golang-github-knadh-koanf_0.10.0-2.debian.tar.xz
 2a15f4500199198d24d968549e6116c440a52dd8ffc71ac050ba7a71411d741f 7318 
golang-github-knadh-koanf_0.10.0-2_amd64.buildinfo
Files:
 905fa79f78d9936192f6a4942d4e86f7 2666 devel optional 
golang-github-knadh-koanf_0.10.0-2.dsc
 6535c50dfd611d530cff8f79b2b5b628 2296 devel optional 
golang-github-knadh-koanf_0.10.0-2.debian.tar.xz
 31e45a5351501650cadb24d4fe99aac0 7318 devel optional 
golang-github-knadh-koanf_0.10.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAl/CfsNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR/t4EAC89mWAqVJr0nfSJTcZq/OdKYyhhLzH
KFbM+31JLBpXya9yggXVWJnW0O8CdbDvZdJSVHKaWbJ7WL6Yvm+PC/Tq7Apy9eLP

Bug#972907: marked as done (astra-toolbox ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 12:33:20 +
with message-id 
and subject line Bug#972907: fixed in astra-toolbox 1.8.3-3
has caused the Debian Bug report #972907,
regarding astra-toolbox ftbfs with python3.9
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.)


-- 
972907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:astra-toolbox
Version: 3.7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

astra-toolbox ftbfs with python3.9; to reproduce, you can use the repositories
found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/astra-toolbox_1.8.3-2build1_amd64-2020-10-25T06:33:59Z.build

[...]
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/log.py to
log.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/pythonutils.py
to pythonutils.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/matrix.py
to matrix.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/sirt.py
to sirt.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/__init__.py
to __init__.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugins/cgls.py
to cgls.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/data3d.py
to data3d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/functions.py
to functions.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/data2d.py
to data2d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/__init__.py
to __init__.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/tests.py
to tests.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/creators.py
to creators.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/algorithm.py
to algorithm.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/matlab.py
to matlab.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/projector3d.py
to projector3d.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/optomo.py
to optomo.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/projector.py
to projector.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/plugin.py
to plugin.cpython-39.pyc
byte-compiling
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra/astra.py
to astra.cpython-39.pyc
running install_egg_info
Writing
../debian/python3-astra-toolbox/usr/lib/python3.9/site-packages/astra_toolbox-1.8.3-py3.9.egg-info
make[2]: Leaving directory '/<>/build-python'
find debian/python3-astra-toolbox -name __pycache__ -depth -exec rm -fr {} \;
mkdir -p debian/python3-astra-toolbox/usr/lib/python3
mv debian/python3-astra-toolbox/usr/lib/python3.8/site-packages
debian/python3-astra-toolbox/usr/lib/python3/dist-packages
mv: cannot stat 'debian/python3-astra-toolbox/usr/lib/python3.8/site-packages':
No such file or directory
make[1]: *** [debian/rules:41: override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: astra-toolbox
Source-Version: 1.8.3-3
Done: Sebastien Delafond 

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated astra-toolbox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please 

Processed: tagging 975178, tagging 976035

[Debian Bug Tracking System]

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

> tags 975178 + pending
Bug #975178 [src:mitmproxy] mitmproxy: FTBFS: E: Build killed with signal TERM 
after 150 minutes of inactivity
Added tag(s) pending.
> tags 976035 + pending
Bug #976035 [mitmproxy] Doesn't work with Python 3.9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#976109: [Pkg-xen-devel] Bug#976109: xen: CVE-2020-29040

[Hans van Kranenburg]

Hi,

On 11/29/20 8:50 PM, Salvatore Bonaccorso wrote:
> Source: xen
> Version: 4.14.0+80-gd101b417b7-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 xen.
> 
> CVE-2020-29040[0]:
> | An issue was discovered in Xen through 4.14.x allowing x86 HVM guest
> | OS users to cause a denial of service (stack corruption), cause a data
> | leak, or possibly gain privileges because of an off-by-one error.
> | NOTE: this issue is caused by an incorrect fix for CVE-2020-27671.

Yes, there's also a limited number of cases in which this is possible,
and you just left that text out, which makes it sound a lot more
horrible: "Only x86 HVM guests which have physical devices passed
through to them can leverage the vulnerability.".

I suspect that if anyone today is using Debian testing to run Xen and
also is passing through devices is doing that to test performance use
cases and not to untrusted guests.

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

Yes, it will off course be included in next upload.

Hans

Bug#972504: marked as done (python-cogent ftbfs with python3.9 as supported python3 version)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 12:29:16 +0100
with message-id 

and subject line Re: python-cogent ftbfs with python3.9 as supported python3 
version
has caused the Debian Bug report #972504,
regarding python-cogent ftbfs with python3.9 as supported python3 version
to be marked as done.

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

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


-- 
972504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-cogent
Version: 2020.2.7a+dfsg-2
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

python-cogent ftbfs with python3.9 as supported python3 version:

[...]
==
ERROR: test_dendro_shape (tests.test_draw.test_dendrogram.TestDendro)
exercising using different values of shape parameter
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_dendrogram.py",
line 125, in test_dendro_shape
fig = dnd.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_annotated_dotplot_remove_tracks
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
removing annotation tracks from dotplot should work
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 209, in test_annotated_dotplot_remove_tracks
orig_fig = dp.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 564, in figure
result = func()
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 355, in _build_2x2_fig
_ = self._build_fig(xaxis="x2", yaxis="y2")
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 326, in _build_fig
f = self.core.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_count_gaps_per_seq
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
creation of drawables works
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 241, in test_count_gaps_per_seq
self._check_drawable_styles(aln.count_gaps_per_seq, styles)
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 140, in _check_drawable_styles
self._check_drawable_attrs(obj.drawable.figure, style)
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 222, in figure
self.layout.yaxis.title = ytitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_dotplot_annotated
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
alignment with / without annotated seqs
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 174, in test_dotplot_annotated
self._check_drawable_attrs(dp.figure, "scatter")
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 'dict' object has no attribute 'title'

==
ERROR: test_dotplot_regression
(tests.test_draw.test_draw_integration.AlignmentDrawablesTests)
Tests whether dotplot produces traces and in correct ordering. Also tests if
pop_trace() works
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/tests/test_draw/test_draw_integration.py",
line 148, in test_dotplot_regression
_ = dp.figure
  File
"/<>/.pybuild/cpython3_3.9_cogent3/build/cogent3/draw/drawable.py",
line 221, in figure
self.layout.xaxis.title = xtitle
AttributeError: 

Bug#976068: marked as done (python-fakeredis' autopkg tests fail)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 11:03:24 +
with message-id 
and subject line Bug#976068: fixed in python-fakeredis 1.4.5-1
has caused the Debian Bug report #976068,
regarding python-fakeredis' autopkg tests fail
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.)


-- 
976068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-fakeredis
Version: 1.4.4-1
Severity: serious
Tags: sid bullseye

python-fakeredis' autopkg tests fail:

[...]
=== FAILURES ===
 TestFuzz.test _

self = 

@pytest.mark.slow
def test(self):
class Machine(CommonMachine):
create_command_strategy = self.create_command_strategy
command_strategy = self.command_strategy

>   hypothesis.stateful.run_state_machine_as_test(Machine)

test/test_hypothesis.py:468:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/hypothesis/stateful.py:75: in
run_state_machine_as_test
def run_state_machine_as_test(state_machine_factory, *, settings=None):
/usr/lib/python3/dist-packages/hypothesis/internal/reflection.py:654: in accept
return func(*bound.args, **bound.kwargs)
/usr/lib/python3/dist-packages/hypothesis/stateful.py:200: in
run_state_machine_as_test
run_state_machine(state_machine_factory)
/usr/lib/python3/dist-packages/hypothesis/stateful.py:92: in run_state_machine
@given(st.data())
test/test_hypothesis.py:454: in one_command
self._compare(command)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = Machine({}), command = Command('exec', b'')

def _compare(self, command):
fake_result, fake_exc = self._evaluate(self.fake, command)
real_result, real_exc = self._evaluate(self.real, command)

if fake_exc is not None and real_exc is None:
raise fake_exc
elif real_exc is not None and fake_exc is None:
assert real_exc == fake_exc, "Expected exception {} not
raised".format(real_exc)
elif (real_exc is None and isinstance(real_result, list)
  and command.args and command.args[0].lower() == 'exec'):
assert fake_result is not None
# Transactions need to use the normalize functions of the
# component commands.
assert len(self.transaction_normalize) == len(real_result)
assert len(self.transaction_normalize) == len(fake_result)
for n, r, f in zip(self.transaction_normalize, real_result,
fake_result):
assert n(f) == n(r)
self.transaction_normalize = []
else:
>   assert fake_result == real_result
E   assert WrappedExcept...ec' command")) == WrappedExcepti...ec' 
command"))
E -WrappedException(ResponseError("wrong number of arguments for
'exec' command"))
E +WrappedException(ExecAbortError("Transaction discarded because
of: wrong number of arguments for 'exec' command"))

test/test_hypothesis.py:424: AssertionError
- Captured stdout call -
Falsifying example:
state = Machine()
state.init_attrs(attrs={'fields': [b'', b'\x00'],
 'keys': [b'', b'\x00'],
 'scores': [0.0, 1.0],
 'values': [b'', b'\x00']})
state.init_data(commands=[])
state.one_command(command=Command('exec', b''))
state.teardown()
= 1 failed, 1086 passed, 88 skipped in 264.91 seconds ==
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:9:
DeprecationWarning: the imp module is deprecated in favour of importlib; see the
module's documentation for alternative uses
  import imp
autopkgtest [18:34:51]: test command1: ---]
autopkgtest [18:34:51]: test command1:  - - - - - - - - - - results - - - - - -
- - - -
command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: python-fakeredis
Source-Version: 1.4.5-1
Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= 

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

Bug#964496: libjson-validator-perl: URL is gone, this is now RC

[Andrius Merkys]

Hello,

On 2020-11-29 18:59, Wouter Verhelst wrote:
> This bug is still present. Additionally, the URL for the OpenAPI JSON
> scheme now returns a 404 error, which means that any software using
> OpenAPI on Debian with this bug present will fail to function correctly.>
> Please fix this bug before the release of bullseye.

While I agree that this is an important issue, I do not think severity
"serious" is appropriate here. It is true that the upstream provides
caching mechanism, but any URL may become offline, and a general
approach to prevent failures in such cases is to use Debian-packaged
files. With OpenAPI schemas provided in openapi-specification binary
package, this is as simple as replacing OpenAPI URLs with
/usr/share/openapi-specification/schemas/$VERSION/schema.json in the
using code.

The upstream caching mechanism could indeed be employed, but as said
before [1], preferable way to use it needs transparency of cache hashes.

By the way, could you please provide OpenAPI URL that returns 404 now?

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964496#24

Best,
Andrius

Processed: bug 968318 is forwarded to https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3

[Debian Bug Tracking System]

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

> forwarded 968318 https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3
Bug #968318 [src:pyhst2] pyhst2: FTBFS with CUDA 11: Unsupported gpu 
architecture 'compute_30'
Set Bug forwarded-to-address to 
'https://gitlab.esrf.fr/mirone/pyhst2/-/issues/3'.
> thanks
Stopping processing here.

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

Processed: reassign 972095 to src:python-fakeredis, forcibly merging 972153 972095

[Debian Bug Tracking System]

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

> reassign 972095 src:python-fakeredis
Bug #972095 [python-fakeredis] missing test-dependency
Bug reassigned from package 'python-fakeredis' to 'src:python-fakeredis'.
No longer marked as found in versions 1.4.3-1.
Ignoring request to alter fixed versions of bug #972095 to the same values 
previously set
> forcemerge 972153 972095
Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= } 
[src:python-fakeredis] python-fakeredis autopkg test fails
Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= } 
[src:python-fakeredis] python-fakeredis autopkg test fails
Added tag(s) patch.
Bug #972095 [src:python-fakeredis] missing test-dependency
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked as fixed in versions python-fakeredis/1.4.4-1.
Marked as found in versions python-fakeredis/1.4.3-1.
Added tag(s) sid and bullseye.
Merged 972095 972153
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 972153, forcibly merging 972153 972095

[Debian Bug Tracking System]

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

> unarchive 972153
Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= } 
[src:python-fakeredis] python-fakeredis autopkg test fails
Unarchived Bug 972153
> forcemerge 972153 972095
Bug #972153 {Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= } 
[src:python-fakeredis] python-fakeredis autopkg test fails
Unable to merge bugs because:
package of #972095 is 'python-fakeredis' not 'src:python-fakeredis'
Failed to forcibly merge 972153: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Bug#976068 marked as pending in python-fakeredis

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976068 [src:python-fakeredis] python-fakeredis' autopkg tests fail
Added tag(s) pending.

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

Bug#976068: marked as pending in python-fakeredis

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #976068 in python-fakeredis 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/python-team/packages/python-fakeredis/-/commit/d847240e3e423a0ce1ec6b815c89a9f1e28f204f


Skip flaky test (Closes: #976068).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976068

Bug#976105: marked as done (golang-github-tidwall-buntdb FTBFS: FAIL: TestOnExpiredSync)

[Debian Bug Tracking System]

Your message dated Mon, 30 Nov 2020 10:18:22 +
with message-id 
and subject line Bug#976105: fixed in golang-github-tidwall-buntdb 1.1.2-3
has caused the Debian Bug report #976105,
regarding golang-github-tidwall-buntdb FTBFS: FAIL: TestOnExpiredSync
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.)


-- 
976105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-tidwall-buntdb
Version: 1.1.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=golang-github-tidwall-buntdb=all=1.1.2-2=1606145966=0

...
=== RUN   TestOnExpiredSync
--- FAIL: TestOnExpiredSync (2.00s)
=== RUN   Example_descKeys
--- PASS: Example_descKeys (0.00s)
=== RUN   ExampleDesc
--- PASS: ExampleDesc (0.00s)
=== RUN   ExampleDB_CreateIndex_jSON
--- PASS: ExampleDB_CreateIndex_jSON (0.00s)
=== RUN   ExampleDB_CreateIndex_strings
--- PASS: ExampleDB_CreateIndex_strings (0.00s)
=== RUN   ExampleDB_CreateIndex_ints
--- PASS: ExampleDB_CreateIndex_ints (0.00s)
=== RUN   ExampleDB_CreateIndex_multipleFields
--- PASS: ExampleDB_CreateIndex_multipleFields (0.00s)
FAIL
FAILgithub.com/tidwall/buntdb   12.634s
FAIL
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/tidwall/buntdb returned exit code 1
make: *** [debian/rules:4: binary-indep] Error 25
--- End Message ---
--- Begin Message ---
Source: golang-github-tidwall-buntdb
Source-Version: 1.1.2-3
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-tidwall-buntdb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Nov 2020 09:51:55 +
Source: golang-github-tidwall-buntdb
Architecture: source
Version: 1.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 976105
Changes:
 golang-github-tidwall-buntdb (1.1.2-3) unstable; urgency=medium
 .
   * Team Upload.
   * Disable flaky test (Closes: #976105)
Checksums-Sha1:
 c22c71198087243b442f89c20631e89225353a25 2431 
golang-github-tidwall-buntdb_1.1.2-3.dsc
 f8186e3c085d5e24a5c0c0ddf8c897371199cb75 3392 
golang-github-tidwall-buntdb_1.1.2-3.debian.tar.xz
 48db3dfcb4434e1e9d951751edae20bfecea3d57 7027 
golang-github-tidwall-buntdb_1.1.2-3_amd64.buildinfo
Checksums-Sha256:
 af6f890e99240510f9ced62584f77780ccc411d2325e0297609b6fa2ae590a16 2431 
golang-github-tidwall-buntdb_1.1.2-3.dsc
 204d0501ff0bbdd166d5696188e38e947f678deafb11f8b587f164a129f37f76 3392 
golang-github-tidwall-buntdb_1.1.2-3.debian.tar.xz
 be17c82842fb79793eb908a82a71c49c169d09dcd7f7e41f70e370900e66eba8 7027 
golang-github-tidwall-buntdb_1.1.2-3_amd64.buildinfo
Files:
 32f5c66d8a51658b68edb05e4f5698d5 2431 devel optional 
golang-github-tidwall-buntdb_1.1.2-3.dsc
 813bb4a271cd96d831af994b0cdd4880 3392 devel optional 
golang-github-tidwall-buntdb_1.1.2-3.debian.tar.xz
 6f2875670eb5c69f5c334da154cede42 7027 devel optional 
golang-github-tidwall-buntdb_1.1.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl/EwdoUHG5wYXRyYTk3
NEBnbWFpbC5jb20ACgkQALrnSzQzafFF5A/9Hz29mt9llvPgIX+qQRcYX+ddpPTS
tkUqrWenqQKHSxxN/ys/xc3QapoMEWafhrlC7MZz3Fk9HxiO/cv34mkPt6u+9WMb
mGMfS3IILYaUc0xtsEJwQnvn21XyWC7mn0VODx10opJEtfd8/iBAWIjEcvS6sSTq
n2KPFXNvQ/71cgR7lt2LShefH79fgiIKTdYzUsamv3bKAO/qfW9oDoh/kLE49eW1
YGuxUV9LpaR7xtRVvsaEsZDlBOMCqT3sklXwNNn5hhh599tI/XLU/DUTaC6ZvEK+
YBOhEtF6vf7MzeaW6FxiPgF45aD/ijmLFpRwxZQN6X4c1c/FG0PMGzPZzbWCXhA9
beQ3/kzkiXsdnfSM/eeAbbLKKTDcnFG3YG8Vatkc/juok0Wjpp/FoW92q0DeIkHg
4PhwZJjI0/hgnM57W/Rf1/La+VS54KlhLoemxMGTXX3bui8eAGRA5LzzF1FB6TLD
aN+rpqLAfovTm3fEnV6vwVkLTon/MAEEAtVbhYSWBrQjwa2kJg5CV4bo6Xa8xtgX
mCSQ/PbrrIGjCqk2ZfLQf4TiYlSNNQDlSlgjfQj/65tz6ZHHi0ObGSYRsVfnIA5d
ebNCA/5cLKyvwZLAI9Uz6Vr91sO1pUJEFemC98MTfGQHcrCcEopJuhIXMx3dfCW/
j1az8oIpMk2+Uq0=
=LJER
-END PGP SIGNATURE End Message ---

Processed: Bug#976105 marked as pending in golang-github-tidwall-buntdb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976105 [src:golang-github-tidwall-buntdb] golang-github-tidwall-buntdb 
FTBFS: FAIL: TestOnExpiredSync
Added tag(s) pending.

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