Bug#978452: marked as done (python3-opencv: missing dependency on libcharls2)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 07:03:35 +
with message-id 
and subject line Bug#978452: fixed in opencv 4.5.1+dfsg-2
has caused the Debian Bug report #978452,
regarding python3-opencv: missing dependency on libcharls2
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.)


-- 
978452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-opencv
Version: 4.5.1+dfsg-1
Severity: grave

Hello,
i've just upgraded to opencv 4.5.1 and when importing the python module, i got
this error:

Traceback (most recent call last):
  File "tool", line 10, in 
import cv2
ImportError: libcharls.so.2: cannot open shared object file: No such file or 
directory

which is provided by libcharls2, and after installing it, i can import cv2 fine.

set to RC level because if i cant even import the module, that's a broken enough
package that's unusable.

Regards,
Sandro

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

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

Versions of packages python3-opencv depends on:
ii  libc6   2.30-2
ii  libgcc-s1   10.2.1-3
ii  libopencv-calib3d4.54.5.1+dfsg-1
ii  libopencv-contrib4.54.5.1+dfsg-1
ii  libopencv-core4.5   4.5.1+dfsg-1
ii  libopencv-dnn4.54.5.1+dfsg-1
ii  libopencv-features2d4.5 4.5.1+dfsg-1
ii  libopencv-flann4.5  4.5.1+dfsg-1
ii  libopencv-highgui4.54.5.1+dfsg-1
ii  libopencv-imgcodecs4.5  4.5.1+dfsg-1
ii  libopencv-imgproc4.54.5.1+dfsg-1
ii  libopencv-ml4.5 4.5.1+dfsg-1
ii  libopencv-objdetect4.5  4.5.1+dfsg-1
ii  libopencv-photo4.5  4.5.1+dfsg-1
ii  libopencv-shape4.5  4.5.1+dfsg-1
ii  libopencv-stitching4.5  4.5.1+dfsg-1
ii  libopencv-superres4.5   4.5.1+dfsg-1
ii  libopencv-video4.5  4.5.1+dfsg-1
ii  libopencv-videoio4.54.5.1+dfsg-1
ii  libopencv-videostab4.5  4.5.1+dfsg-1
ii  libopencv-viz4.54.5.1+dfsg-1
ii  libstdc++6  10.2.1-3
ii  python3 3.9.1-1
ii  python3-numpy [python3-numpy-abi9]  1:1.19.4-1+b1

python3-opencv recommends no packages.

python3-opencv suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opencv
Source-Version: 4.5.1+dfsg-2
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated opencv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Dec 2020 14:45:26 +0800
Source: opencv
Architecture: source
Version: 4.5.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Mo Zhou 
Closes: 978028 978452
Changes:
 opencv (4.5.1+dfsg-2) unstable; urgency=medium
 .
   [ Mo Zhou ]
   * Bump B-D from VTK-7 to VTK-9.
   * Add runtime Deps libcharls2 for python3-opencv. (Closes: #978452)
 .
   [ Pino Toscano ]
   * Fix FTBFS on architectures without java. (Closes: #978028)
Checksums-Sha1:
 35eeaa91f61bcd2fc1c26814f7c88bc862811374 6845 opencv_4.5.1+dfsg-2.dsc
 0e109925c780cf6427af7c7b0895b4ba86b37dc4 33600 
opencv_4.5.1+dfsg-2.debian.tar.xz
 e75a8b677c8c57c7994b453b85a05c36e2bc504f 11807 
opencv_4.5.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 56bdddbbe3179a0d9c6395b88ac9ca4d0a46e95f76188c2742e34a87f1c9e886 6845 
opencv_4.5.1+dfsg-2.dsc
 3fa4953f4423aed2b5226e29f7542c3f60b2c2240dd69ec8dad9757f39a25af0 33600 
opencv_4.5.1+dfsg-2.debian.tar.xz
 

Processed: Re: Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #978555 {Done: Steve Langasek } [libpam-modules] 
libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): 
/lib/security/pam_unix.so: cannot open shared object file
Severity set to 'serious' from 'normal'

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

Bug#977473: Re-activate test for gdcm

[Andreas Tille]

Control: retitle -1 Reactivate test for gdcm which was excluded due to failure
Control: severity -1 important

This single test prevented testing migration of this package and all
its dependencies.  Thus the test was deactivated for the moment to
enable building the package.  But the issue should be clarified.

The exclusion of the test is done in debian/patches/ignore_failing_test.patch.

Kind regards

Andreas.

-- 
http://fam-tille.de

Processed: Re-activate test for gdcm

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Reactivate test for gdcm which was excluded due to failure
Bug #977473 [src:insighttoolkit4] insighttoolkit4: FTBFS: TypeError: in method 
'itkGDCMImageIO_GetValueFromTag', argument 3 of type 'std::string &'
Changed Bug title to 'Reactivate test for gdcm which was excluded due to 
failure' from 'insighttoolkit4: FTBFS: TypeError: in method 
'itkGDCMImageIO_GetValueFromTag', argument 3 of type 'std::string &''.
> severity -1 important
Bug #977473 [src:insighttoolkit4] Reactivate test for gdcm which was excluded 
due to failure
Severity set to 'important' from 'serious'

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

Bug#962203: NMU

[Paul Wise]

On Mon, 2020-12-28 at 21:50 -0500, Calum McConnell wrote:

> Yeah, when I tried to build it locally, it failed due to files that
> are present in the source package but missing from Git.

There are more changes than just the documentation build things though.

> I eventually gave up and just included the PDF I built locally in the
> source package.

I don't think it is ever appropriate to include generated files in
version control repositories and almost never in source tarballs.

> If you'd like, I can revert back and generate a more minimal NMU.
> ...
> As long as it gets fixed!

Maybe lets wait for A Mennucc1 to do a maintainer upload, and if it
gets close to the next autoremoval date, do a more minimal NMU.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#962203: NMU

[Calum McConnell]

On Tue, 2020-12-29 at 10:36 +0800, Paul Wise wrote:
> On Mon, 14 Dec 2020 17:23:08 -0500 Calum McConnell wrote:
> 
> > I have prepared an NMU for this package.  It is currently at
> > https://mentors.debian.net/package/debdelta/ .  While I need a sponsor
> > to
> > get it into Debian, I am now reaching out to
> > ment...@lists.debian.org to
> > see if I can expedite the process.
> 
> I was looking at sponsoring this, but based on the debdiff it appears
> to have some changes that are not in the patch you posted to the bug.

Yeah, when I tried to build it locally, it failed due to files that are
present in the source package but missing from Git.  I had to manually
generate the PDF docs, and the additional changes were me trying to
automate that process.  However, while the modified commands ran fine on
my testing box and in a testing schroot, they broke spectacularally in the
unstable schroot.  After several hours of adding more build dependencies
to try and make it work, I eventually gave up and just included the PDF I
built locally in the source package.  

If you'd like, I can revert back and generate a more minimal NMU.

> It looks like A Mennucc1 will be working on this issue soon though.

As long as it gets fixed!

Thanks,
Calum


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

Bug#978188: marked as done (workrave: FTBFS: main.c:403:45: error: expected expression before ‘WorkraveApplet’)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 02:42:43 +
with message-id 
and subject line Bug#978188: fixed in workrave 1.10.44-6
has caused the Debian Bug report #978188,
regarding workrave: FTBFS: main.c:403:45: error: expected expression before 
‘WorkraveApplet’
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.)


-- 
978188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: workrave
Version: 1.10.44-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /bin/bash ../../../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H 
> -I. -I../../../..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-cast-function-type 
> -Wall -std=c99 -I../../../../common/include -I../../../../libs/dbus/include 
> -I../../../../backend/include -I../../../../frontend/common/include 
> -I./../include -I./../../common/include   -pthread 
> -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DWORKRAVE_PKGDATADIR="\"/usr/share/workrave\"" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o libworkrave_plugin_la-main.lo `test -f 'main.c' 
> || echo './'`main.c
> sed -e "s,\@libexecdir\@,/usr/lib/x86_64-linux-gnu,g" < 
> workrave-xfce-applet-2.0.desktop.in.in > workrave-xfce-applet.desktop.in
> LC_ALL=C /usr/bin/intltool-merge  -d -u -c 
> ../../../../po/.intltool-merge-cache ../../../../po 
> workrave-xfce-applet.desktop.in workrave-xfce-applet.desktop
> Found cached translation database
> Merging translations into workrave-xfce-applet.desktop.
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wno-cast-function-type -Wall -std=c99 
> -I../../../../common/include -I../../../../libs/dbus/include 
> -I../../../../backend/include -I../../../../frontend/common/include 
> -I./../include -I./../../common/include -pthread 
> -I/usr/include/xfce4/libxfce4panel-2.0 -I/usr/include/gtk-3.0 
> -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
> -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
> -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
> -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/xfce4 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -DWORKRAVE_PKGDATADIR=\"/usr/share/workrave\" -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c main.c  -fPIC -DPIC -o 
> .libs/libworkrave_plugin_la-main.o
> main.c: In function ‘workrave_applet_construct’:
> main.c:403:28: warning: implicit declaration of function ‘panel_slice_new0’; 
> did you mean ‘g_slice_new0’? [-Wimplicit-function-declaration]
>   403 |   WorkraveApplet *applet = panel_slice_new0(WorkraveApplet);
>   |^~~~
>   |g_slice_new0
> main.c:403:45: error: expected expression before ‘WorkraveApplet’
>   403 |   WorkraveApplet *applet = panel_slice_new0(WorkraveApplet);
>   | ^~
> main.c: At top level:
> main.c:421:1: warning: data definition has no type or storage class
>   421 | XFCE_PANEL_PLUGIN_REGISTER(workrave_applet_construct);
>   | ^~
> main.c:421:1: warning: type defaults to ‘int’ in declaration of 
> ‘XFCE_PANEL_PLUGIN_REGISTER’ [-Wimplicit-int]
> main.c:421:1: warning: parameter names (without types) in function declaration
> main.c:401:13: warning: ‘workrave_applet_construct’ defined but not used 

Bug#962203: NMU

[Paul Wise]

On Mon, 14 Dec 2020 17:23:08 -0500 Calum McConnell wrote:

> I have prepared an NMU for this package.  It is currently at
> https://mentors.debian.net/package/debdelta/ .  While I need a sponsor to
> get it into Debian, I am now reaching out to ment...@lists.debian.org to
> see if I can expedite the process.

I was looking at sponsoring this, but based on the debdiff it appears
to have some changes that are not in the patch you posted to the bug.

It looks like A Mennucc1 will be working on this issue soon though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#978265: marked as done (sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 00:35:44 +
with message-id 
and subject line Bug#978265: fixed in sshuttle 1.0.5-1
has caused the Debian Bug report #978265,
regarding sshuttle: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
978265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sshuttle
Version: 1.0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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_clean
> rm -rf tmp
> rm -rf docs/.build docs/_build
> make[1]: Leaving directory '/<>'
>  dpkg-source -b .
> dpkg-source: warning: upstream signing key but no upstream tarball signature
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building sshuttle using existing 
> ./sshuttle_1.0.4.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  sshuttle-1.0.4/sshuttle/version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/sshuttle_1.0.4-1.diff.TyP0YN
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:42:24Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/sshuttle_1.0.4-1_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: sshuttle
Source-Version: 1.0.5-1
Done: Brian May 

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

Debian distribution maintenance software
pp.
Brian May  (supplier of updated sshuttle package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Dec 2020 11:00:34 +1100
Source: sshuttle
Architecture: source
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Brian May 
Changed-By: Brian May 
Closes: 978265
Changes:
 sshuttle (1.0.5-1) unstable; urgency=medium
 .
   * New upstream version.
   * Fixes FTBS error. Closes: #978265.
Checksums-Sha1:
 a2df44a07128d1e7f1cd8ad8f5147d39c1552ef6 1991 sshuttle_1.0.5-1.dsc
 7bda540d85b4b8b15ff81f496e8eec6f1d4623dd 88823 sshuttle_1.0.5.orig.tar.gz
 2de0f5c4d3b461104b449d9e1d7600e1c8b5f891 15540 sshuttle_1.0.5-1.debian.tar.xz
 62d8799ff296bbc4752c0d54a60aa16ef80f223c 7664 sshuttle_1.0.5-1_source.buildinfo
Checksums-Sha256:
 1d90fa3fe3d56c29c032b98625a148e1260b250aed619be7f1768a27354319f1 1991 
sshuttle_1.0.5-1.dsc
 fd8c691aac2cb80933aae7f94d9d9e271a820efc5c48e73408f1a90da426a1bd 88823 
sshuttle_1.0.5.orig.tar.gz
 d499067a955c3b5e2904b2166abc2d40cbc9bb08977aa07f35ca173071c46c1e 15540 
sshuttle_1.0.5-1.debian.tar.xz
 93d6d0204e3c4f8db8b04deec140dbfa78658bad5a0f61e90ba863fc5ff85be4 7664 
sshuttle_1.0.5-1_source.buildinfo
Files:
 a0042419c1b3cc3f8b5ea577e15b3c40 1991 net optional sshuttle_1.0.5-1.dsc
 10c9765f2cc2a3e3e080a4a218428cc4 88823 net optional sshuttle_1.0.5.orig.tar.gz
 a89b42168b42ca9034c14f6a280af45f 15540 net optional 
sshuttle_1.0.5-1.debian.tar.xz
 240b5c9146f264df56febb1bb6b60317 7664 net optional 

Bug#911587: infnoise: busy-waits, using too much CPU

[Axel Beckert]

Hi Stephen,

Stephen Kitt wrote:
> I have figured out what was wrong (cue brown paper bag for me), I’ll upload a
> fix shortly.

Yay, thanks! Much appreciated!

> > Not sure if any of these fix this issue.
> 
> 0.3.1 was already in unstable,

Oops, ok, sorry, my fault for not looking closer.

> but the error came from incomplete build
> flags...

Yeah, just read the changelog of the package.

> > That's nice, but any chance to get infnoise back into testing?
> 
> Yup!

Thanks again!

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

Bug#977357: marked as done (libgdf ftbfs on s390x (test failures))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 23:48:27 +
with message-id 
and subject line Bug#977357: fixed in libgdf 0.1.3-7
has caused the Debian Bug report #977357,
regarding libgdf ftbfs on s390x (test failures)
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.)


-- 
977357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgdf
Version: 0.1.3-6
Severity: serious
Tags: sid bullseye

see
https://buildd.debian.org/status/fetch.php?pkg=libgdf=s390x=0.1.3-6=1606417737=0

stalls migration to testing.


[...]
43% tests passed, 4 tests failed out of 7

Total Test time (real) =   0.04 sec

The following tests FAILED:
  4 - testRWConsistency (Child aborted)
  5 - testSparseSampling (Child aborted)
  6 - testHeader3 (Child aborted)
  7 - testDataTypes (Child aborted)
Errors while running CTest
make[1]: *** [Makefile:152: test] Error 8
make[1]: Leaving directory '/<>/obj-s390x-linux-gnu'
dh_auto_test: error: cd obj-s390x-linux-gnu && make -j1 test ARGS\+=-j1 returned
exit code 2
make: *** [debian/rules:33: binary-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: libgdf
Source-Version: 0.1.3-7
Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= 

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

Debian distribution maintenance software
pp.
Rafael Laboissière  (supplier of updated libgdf 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, 28 Dec 2020 19:58:39 -0300
Source: libgdf
Architecture: source
Version: 0.1.3-7
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Rafael Laboissière 
Closes: 977357
Changes:
 libgdf (0.1.3-7) unstable; urgency=medium
 .
   * d/p/check-system-endianness.patch: Update patch.
 This fixes the problem of detection of endianness on the s390x
 architecture, what was causing the FTBFS on that architecture.
 (Closes: #977357)
Checksums-Sha1:
 f345aff7e1d0c98d17b98042bf5f2f1e5b6c08fb 2490 libgdf_0.1.3-7.dsc
 7ed4f72fc5ed437da86d0e9b02e7822869c888ee 7932 libgdf_0.1.3-7.debian.tar.xz
 ddfe99c64eef0c1d51f87d8d5fca302917a5c876 22310 libgdf_0.1.3-7_amd64.buildinfo
Checksums-Sha256:
 25a1383675c37c27b9882b0336098008c8b0a2df431a3aa8a77cd9afd67d61fa 2490 
libgdf_0.1.3-7.dsc
 bff5bf33d5f8ba29a3f534bafc6ee2faa6b27c57da19c9b0942828f51987a633 7932 
libgdf_0.1.3-7.debian.tar.xz
 f707a75160e8ba345aaa13a73791efa1d2176a7daf4fdd21e3881856152fe020 22310 
libgdf_0.1.3-7_amd64.buildinfo
Files:
 4c4dabe2a64c90ccfb670df7e9575a8c 2490 libs optional libgdf_0.1.3-7.dsc
 a88efff2a9050d47412f1f4381a09bd4 7932 libs optional 
libgdf_0.1.3-7.debian.tar.xz
 52327bcb0f2e58a321f52c6278dd5bb6 22310 libs optional 
libgdf_0.1.3-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl/qajsACgkQISSqGYN4
XJC/ZQ/+Lcgsy8KfJHKnpqOBabZyjs/5FRuObvY0hQpYAW/0Lje40sKPpVpCKdHf
ZVs3eYYsItrL+WCX4MUrnl7qn8PjWkNK7rTnxFCdueF1lm74A7uOBoawWhmqKe10
m7nOyJ52QUXx9/PIcC2VMLxrrOYMNff4t7IKHdOSW1wRzpuqf2wsRQ4ex/9NloU7
gz8FlS3mzvKDTI2yPoW9p8s9ovw1JQboZvQDwDOZNW/i8xGq16qEGsy7PykGfIeR
PWBeCD3CJY5DanHNw95ZVaBoDIZOfhfn38IiJKixZjZjiR4Mqw2ekWN68Sf7wPaz
KFNPiJ9fuQo3fOvcWJWS+LOExK9KC4+bzEqnLD0biJqOg+KR2cjUsmfBXExPd6O6
rX3oFZu/Uq6GoYum1nmYmFg7vFxHVKpRmzUeKfNcf7M1jsOqlQ28jNONkfMCuKJF
A0KWHoX6YrBiXarPqc0KpjOIQX+phRi6pQDx7nmVNecoRV8cCygq/DFAfWzsbOCr
Mw+sIqaM7VOFudIety+n3wJzfQ6Q2g+lPlkfVlJpdedDokAr9dTxlF8fN/1KgZjk
vWTKo7jju3i4KQ5OAcDKf+QJcs0oRdrCS0By2OTn+gD7DAXlBkTIvnkFGt2PjP0M
lDcwF1WAEH5ui/cVxdDIz51UcEjTGYXgymQ0X8l0t1/HfFkhfqo=
=DkKY
-END PGP SIGNATURE End Message ---

Processed: Bug#977357 marked as pending in libgdf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977357 [src:libgdf] libgdf ftbfs on s390x (test failures)
Added tag(s) pending.

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

Bug#977357: marked as pending in libgdf

[Rafael Laboissiere]

Control: tag -1 pending

Hello,

Bug #977357 in libgdf 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/neurodebian-team/libgdf/-/commit/e1ecf1858c67cdf55bc1520493ed1954063ace20


d/p/check-system-endianness.patch: Update patch

This fixes the problem of detection of endianness on the s390x architecture, 
what was causing the FTBFS on that architecture.

Gbp-Dch: Full

Closes: #977357


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977357

Processed: Re: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #978555 [libpam-modules] libpam-modules: breaks cron: PAM unable to 
dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file
Severity set to 'normal' from 'grave'

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

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Vincent Lefevre]

Control: severity -1 normal

After a reboot too, the problem no longer occurs.

Perhaps there should be a warning saying that some services may need
to be restarted.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#978583: marked as done (libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't follow the proper hierarchy)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 23:03:52 +
with message-id 
and subject line Bug#978583: fixed in trapperkeeper-filesystem-watcher-clojure 
1.2.2-2
has caused the Debian Bug report #978583,
regarding libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't 
follow the proper hierarchy
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.)


-- 
978583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtrapperkeeper-filesystem-watcher-clojure
Version: 1.2.2-1
Severity: grave
Owner: po...@debian.org

The .jar in this package contains the following .clj files:

clj/
clj/puppetlabs/
clj/puppetlabs/trapperkeeper/
clj/puppetlabs/trapperkeeper/services/
clj/puppetlabs/trapperkeeper/services/protocols/
clj/puppetlabs/trapperkeeper/services/protocols/filesystem_watch_service.clj
clj/puppetlabs/trapperkeeper/services/watcher/
clj/puppetlabs/trapperkeeper/services/watcher/filesystem_watch_core.clj
clj/puppetlabs/trapperkeeper/services/watcher/filesystem_watch_service.clj

They should be following this hierarchy instead:

puppetlabs/trapperkeeper/
puppetlabs/trapperkeeper/services/
puppetlabs/trapperkeeper/services/protocols/
puppetlabs/trapperkeeper/services/protocols/filesystem_watch_service.clj
puppetlabs/trapperkeeper/services/watcher/
puppetlabs/trapperkeeper/services/watcher/filesystem_watch_core.clj
puppetlabs/trapperkeeper/services/watcher/filesystem_watch_service.clj

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄
--- End Message ---
--- Begin Message ---
Source: trapperkeeper-filesystem-watcher-clojure
Source-Version: 1.2.2-2
Done: =?utf-8?q?Louis-Philippe_V=C3=A9ronneau?= 

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

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau  (supplier of updated 
trapperkeeper-filesystem-watcher-clojure 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, 28 Dec 2020 17:31:10 -0500
Source: trapperkeeper-filesystem-watcher-clojure
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Clojure Maintainers 

Changed-By: Louis-Philippe Véronneau 
Closes: 978583
Changes:
 trapperkeeper-filesystem-watcher-clojure (1.2.2-2) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild using lein. (Closes: #978583)
   * d/control: use dh13.
   * d/control: Standards-Version update to 4.5.1. Add Rules-Requires-Root.
   * d/*.lintian-overrides: override false positive jar-contains-source tag.
   * d/watch: create.
   * d/tests: add autopkgtests.
Checksums-Sha1:
 08874e01f9ce3c2f85f0a163a434aa44368bdfd1 2673 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.dsc
 18e76b5bca0dc1519e98491e74f2b6ce5d6a01b9 3348 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.debian.tar.xz
 5e8a25f145dd5314d882d759c634ef2c2564dd0f 13082 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2_amd64.buildinfo
Checksums-Sha256:
 bdadb2d4fa21eb9cedebddbf3db08041657c44bd4d7d83f98d1ad256a373d9f1 2673 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.dsc
 da6cde5dfaf389dfd993c02eb94fa6ec5fb23c73647aeddb93e0ee5fcc90bac8 3348 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.debian.tar.xz
 3f30183d48e2c8a323d62781d83b1796f2870618b60141d0b0ad055a5ee27751 13082 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2_amd64.buildinfo
Files:
 714f7fd85dd28d06a4662487d4c6e789 2673 java optional 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.dsc
 ae721c22910940d03234e02fbb93d330 3348 java optional 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2.debian.tar.xz
 7be9b8594b0d1ee803f662717ba12882 13082 java optional 
trapperkeeper-filesystem-watcher-clojure_1.2.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZ39U8fqGga2OwLzmeurE7GqqCpcFAl/qXsAACgkQeurE7Gqq
CpcNhRAAg7o6k8KGQ1OjsBvfQM5F1XwUsR1AhKwwX/HsSm+3pTOw3w4ELn3kxxZu
wuhwQMSAjqkKFrZ9jKPrLz8sC2Attx4ag8QRp3XYDz6NntNEIAuSHMfEOwsuguy8

Bug#978515: marked as done (grub2: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 22:48:43 +
with message-id 
and subject line Bug#978515: fixed in grub2 2.04-12
has caused the Debian Bug report #978515,
regarding grub2: non-standard gcc/g++ used for build (gcc-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.)


-- 
978515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub2
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.04-12
Done: Colin Watson 

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated grub2 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, 28 Dec 2020 22:33:23 +
Source: grub2
Architecture: source
Version: 2.04-12
Distribution: unstable
Urgency: medium
Maintainer: GRUB Maintainers 
Changed-By: Colin Watson 
Closes: 978515
Changes:
 grub2 (2.04-12) unstable; urgency=medium
 .
   * Cherry-pick from upstream:
 - mdraid1x_linux: Fix gcc10 error -Werror=array-bounds
 - zfs: Fix gcc10 error -Werror=zero-length-bounds
   * Build with GCC 10 (closes: #978515).
Checksums-Sha1:
 a9ebd9115681ea02f06c39d70c29c9699541403a 7120 grub2_2.04-12.dsc
 52d4dea1bda70074378657f05193de4ba0202aab 1097944 grub2_2.04-12.debian.tar.xz
Checksums-Sha256:
 ecd5750b126d4cf2a8ef387dd17085f46f8334283278669b4ab98059e1ea5c21 7120 
grub2_2.04-12.dsc
 9d1e490cc6c6e94e0f71b6b139c3f7be8b0cc3de3c1e5626bd77f8f816b9b701 1097944 
grub2_2.04-12.debian.tar.xz
Files:
 32c659f066db1b4773f4e52dc568c3a7 7120 admin optional grub2_2.04-12.dsc
 70ced8331adc76d4963536251e656970 1097944 admin optional 
grub2_2.04-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAl/qXWUACgkQOTWH2X2G
UAtFjRAAmEZedBhsGfQxZEMjgo+w8FiBn3Tec063dadlwvruX1M3+tn7Swv8nhL5
ssCpsNwESaiYPM6B0liTNSjmbvJ1NL0xe39XeENaR8ATQurPWBcCAuETcGYfH8ND
0cg9sSKNRb1XIFNBSUHtPBT1mi2WZ7Sj5NZOQtS+kvg3B3iTKPAWl31wxazqkwPw
yPZcpAfhPAXAzboDztUtPr3tGgh9xex0Hhvfa4EN0c4h1SsqoQGkK4nwJs42Md/r
hHhq2TUVYpaofhWJIpq4UYyq2NWxRLLV3as+rFMZC5LS9g/FkpCrF3ms6d+Ow9zm
ZH00y0yNqM7dPa7rFMnKkHWwg+GgoKAtt1ZK1j6jx8uPNvVVjOc9goMzTzzCH6Jt
jpX8ufuxwnfffpBr7CTlAxwVfjxt8fDP3hMv0GZXkSOMYPD6icFL8tCcTW+3QNKY
1vMZlERdWRjxyeasze7UYT+UuPStK0ZD9qfLfFD3BmmcPRIEVYMdhBbWc3sSTQ9T
H4GnAkFpFFDMnvxCtYcaclwoCFKwD7/qWx5kiotdAcdoRK9yyQc256jfo+MBvrwl
3t4CaP5et+MMtT9m6oHVSj+1GRUseRL1WHiICQEYUZqEljxTRgPnSvhggok8GEDp
xaCMxCCiVdyC0EgggFqAAY2ylHIue53mmFFwwABPbVaF0RInkoI=
=hrYE
-END PGP SIGNATURE End Message ---

Processed: Bug#978515 marked as pending in grub2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978515 [grub2] grub2: non-standard gcc/g++ used for build (gcc-9)
Added tag(s) pending.

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

Bug#978515: marked as pending in grub2

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #978515 in grub2 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/grub-team/grub/-/commit/fdff3397ab772d328e179bc34900f045df84cc78


Build with GCC 10

Closes: #978515


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978515

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

[Justin Erenkrantz]

On Mon, Dec 28, 2020 at 5:00 PM Justin Erenkrantz 
wrote:

> It's not clear to me if OpenSSL authors intended to make this breaking
> change.  On the serf side, we would need to think through what it would
> mean to have our app callback return false upon failure in order to
> short-circuit the check.
>
> I probably won't get a chance to open an upstream OpenSSL issue today (or
> even tomorrow)...
>

I found the original issue where they changed the behavior and added a
comment there:

https://github.com/openssl/openssl/issues/11297

Cheers.  -- justin

Bug#974011: xmille: Incorrect license/copyright for xmille

[Keith Packard]

Adrian Bunk  writes:

> I am just a normal user enjoying the game, and looking at the number of 
> uploads in the past decade two maintainers might be sufficient to handle
> the load.  ;-)

I've uploaded 'kgames' to the new queue :-)

Thanks for playing.

-- 
-keith


signature.asc
Description: PGP signature

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

[Justin Erenkrantz]

As an update, I've been able to triage this a bit further.

It's definitely that last noted change (erroring out on expired self-signed
root) that broke it.  OpenSSL 1.1.1{g,h} are fine, but {i,-stable} are
not.  Reverting just x509_vfy.c to what is in 1.1.1h causes the test to
pass.

In this test case, Serf receives 2 verify callbacks in test_ssl_handshake.
The first failing test case is to not have a known CA - so, we are
intentionally trying to trigger a verify failure.  One of the app
callback received has the expected failure, the other doesn't.  Serf
basically flags the second (success) as an unexpected pass.

2020-12-28T16:51:34.045142-05 test/test_ssl.c: Cert failure received: 4 ;
expected failure mask: 4

2020-12-28T16:51:34.045159-05 test/test_ssl.c: Cert failure received: 0 ;
expected failure mask: 4

The upstream issues/commits appear to be:

https://github.com/openssl/openssl/issues/13427
https://github.com/openssl/openssl/commit/3bed88a3970605a2ff817065f93b08e965d89e5f#diff-2a76d0a7ddc5ae2646a6c183270a7b4d5302d8491acb0af0dfbd70643efdf431

The key difference is almost certainly this change:

https://github.com/openssl/openssl/blob/OpenSSL_1_1_1h/crypto/x509/x509_vfy.c#L1754

---
return verify_cb_cert(ctx, xi, 0,

X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE);
---

https://github.com/openssl/openssl/blob/OpenSSL_1_1_1-stable/crypto/x509/x509_vfy.c#L1755

---
if (!verify_cb_cert(ctx, xi, 0,
X509_V_ERR_UNABLE_TO_VERIFY_LEAF_SIGNATURE))
return 0;

xs = xi;
goto check_cert_time;
---

Up to 1.1.1h, OpenSSL would stop processing the certificate after sending
along the leaf error to the app callback.  In -stable (1.1.1i+ and master),
if the app's callback doesn't return a failure, it will then proceed to the
date check portion (check_cert_time) - which then receives a successful
verification callback.

It's not clear to me if OpenSSL authors intended to make this breaking
change.  On the serf side, we would need to think through what it would
mean to have our app callback return false upon failure in order to
short-circuit the check.

I probably won't get a chance to open an upstream OpenSSL issue today (or
even tomorrow)...

Cheers.  -- justin

Index: test/test_ssl.c

===

--- test/test_ssl.c (revision 1884847)

+++ test/test_ssl.c (working copy)

@@ -465,6 +465,7 @@



 tb->result_flags |= TEST_RESULT_SERVERCERTCB_CALLED;



+test__log(TEST_VERBOSE, __FILE__, "Cert failure received: %d ;
expected failure mask: %d\n", failures, expected_failures);

 /* We expect an error from the certificate validation function. */

 if (failures & expected_failures)

 return APR_SUCCESS;



On Sun, Dec 27, 2020 at 11:22 AM James McCoy  wrote:

> On Sun, Dec 27, 2020 at 10:46:24AM -0500, Justin Erenkrantz wrote:
> > Thanks.  I expect that this might be due to the last change - erroring
> out on
> > an expired self-signed root cert.  Though I thought we didn’t check in a
> root
> > cert for our test chain...could Debian’s packaging be including a cert
> for
> > testing?
>
> I use create_certs.py from trunk to re-generate the test certificates
> every build, otherwise I was running into time bombs with the certs
> expiring.  Other than that, I don't do anything different than the
> normal test process.
>
> The Debian packaging does have some local patches[0] applied to address
> issues that have been fixed upstream but not yet released.
>
> [0]: https://sources.debian.org/patches/serf/1.3.9-8/
>
> > I will try to take a look this week with Debian sid...I assume it has
> 1.1.1i
> > already?  — justin
>
> Yes, it does.
>
> Cheers,
> --
> James
> GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
>

Bug#975193: marked as done (libkgapi: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 22:42:09 +0100
with message-id <8751877.rMLUfLXkoz@tuxin>
and subject line Re: Bug#975193: libkgapi: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
has caused the Debian Bug report #975193,
regarding libkgapi: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make 
-j4 test ARGS\+=-j4 returned exit code 2
to be marked as done.

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

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


-- 
975193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975193
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkgapi
Version: 20.08.2-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):
> make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j4
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: fake-fakenamtest
>   Start  2: core-accountinfofetchjobtest
>   Start  3: core-accountmanagertest
>   Start  4: core-createjobtest
>  1/48 Test  #1: fake-fakenamtest ..   Passed0.11 sec
>   Start  5: core-fetchjobtest
>  2/48 Test  #2: core-accountinfofetchjobtest ..   Passed0.12 sec
>   Start  6: contacts-contactcreatejobtest
>  3/48 Test  #4: core-createjobtest    Passed0.11 sec
>   Start  7: contacts-contactdeletejobtest
>  4/48 Test  #5: core-fetchjobtest .   Passed0.12 sec
>   Start  8: contacts-contactfetchjobtest
>  5/48 Test  #7: contacts-contactdeletejobtest .   Passed0.12 sec
>   Start  9: contacts-contactfetchphotojobtest
>  6/48 Test  #6: contacts-contactcreatejobtest .   Passed0.16 sec
>   Start 10: contacts-contactmodifyjobtest
>  7/48 Test  #8: contacts-contactfetchjobtest ..***Failed0.12 sec
> * Start testing of ContactFetchJobTest *
> Config: Using QtTest library 5.15.1, Qt 5.15.1 (x86_64-little_endian-lp64 
> shared (dynamic) release build; by GCC 10.2.0)
> PASS   : ContactFetchJobTest::initTestCase()
> PASS   : ContactFetchJobTest::testFetchAll()
> FAIL!  : ContactFetchJobTest::testFetchSingle() Compared values are not the 
> same
>Loc: [/<>/autotests/contacts/contactfetchjobtest.cpp(77)]
> PASS   : ContactFetchJobTest::cleanupTestCase()
> Totals: 3 passed, 1 failed, 0 skipped, 0 blacklisted, 6ms
> * Finished testing of ContactFetchJobTest *
> 
>   Start 11: contacts-contactsgroupcreatejobtest
>  8/48 Test  #3: core-accountmanagertest ...   Passed0.37 sec
>   Start 12: contacts-contactsgroupdeletejobtest
>  9/48 Test  #9: contacts-contactfetchphotojobtest .   Passed0.14 sec
>   Start 13: contacts-contactsgroupfetchjobtest
> 10/48 Test #10: contacts-contactmodifyjobtest .   Passed0.18 sec
>   Start 14: contacts-contactsgroupmodifyjobtest
> 11/48 Test #12: contacts-contactsgroupdeletejobtest ...   Passed0.12 sec
>   Start 15: calendar-calendarcreatejobtest
> 12/48 Test #13: contacts-contactsgroupfetchjobtest    Passed0.12 sec
>   Start 16: calendar-calendardeletejobtest
> 13/48 Test #11: contacts-contactsgroupcreatejobtest ...   Passed0.15 sec
>   Start 17: calendar-calendarfetchjobtest
> 14/48 Test #14: contacts-contactsgroupmodifyjobtest ...   Passed0.15 sec
>   Start 18: calendar-calendarmodifyjobtest
> 15/48 Test #16: calendar-calendardeletejobtest    Passed0.12 sec
>   Start 19: calendar-eventcreatejobtest
> 16/48 Test #15: calendar-calendarcreatejobtest    Passed0.12 sec
>   Start 20: calendar-eventdeletejobtest
> 17/48 Test #17: calendar-calendarfetchjobtest .   Passed0.12 sec
>   Start 21: calendar-eventfetchjobtest
> 18/48 Test #18: calendar-calendarmodifyjobtest    Passed0.13 sec
>   Start 22: calendar-eventmodifyjobtest
> 19/48 Test #19: calendar-eventcreatejobtest ...   Passed0.12 sec
>   Start 23: calendar-freebusyqueryjobtest
> 20/48 Test #20: calendar-eventdeletejobtest ...   Passed0.12 sec
>   Start 24: tasks-taskcreatejobtest
> 21/48 Test #21: calendar-eventfetchjobtest    Passed0.12 sec
>   Start 25: tasks-taskdeletejobtest
> 22/48 Test #22: calendar-eventmodifyjobtest ...   Passed0.12 sec
>   Start 26: tasks-taskfetchjobtest
> 23/48 Test #23: 

Bug#951588: kontact: akonadi is not operational

[Sandro Knauß]

control: tags -1 + moreinfo
control: severity -1 important

Hey,

please retry with the current version in testing/unstable and give us more 
information what you have tried to do before kontact returns with a segfault. 
Maybe this issue is more for the Akonadi package?

At least from what I can tell is that is works for a lot of people, so I lower 
the severity.

hefee


On Dienstag, 18. Februar 2020 14:34:53 CET Alberto Fuentes wrote:
> Package: kontact
> Version: 4:19.08.3-1
> Severity: grave
> Justification: renders package unusable
> 
> Application: Akonadi Control (akonadi_control), signal: Aborted
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [Current thread is 1 (Thread 0x7ff192558800 (LWP 1433258))]
> 
> Thread 5 (Thread 0x7ff189e1f700 (LWP 1433262)):
> #0  0x7ff195d5abef in __GI___poll (fds=0x7ff1800021e0, nfds=1,
> timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x7ff19510710e in ?? () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2  0x7ff19510722f in
> g_main_context_iteration () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3  0x7ff1962e381b in
> QEventDispatcherGlib::processEvents(QFlags)
> () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #4  0x7ff19628c71b in
> QEventLoop::exec(QFlags) () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #5  0x7ff1960cd731 in QThread::exec() () from /usr/lib/x86_64-linux-
> gnu/libQt5Core.so.5
> #6  0x7ff196bf14e6 in ?? () from
> /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7  0x7ff1960ce8b2 in ?? ()
> from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8  0x7ff195c52fb7 in
> start_thread (arg=) at
> pthread_create.c:486
> #9  0x7ff195d651af in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 4 (Thread 0x7ff18a703700 (LWP 1433261)):
> #0  0x7ff195d5abef in __GI___poll (fds=0x55fdcd713ff0, nfds=2,
> timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x7ff19510710e in ?? () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2  0x7ff195107473 in
> g_main_loop_run () from /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0
> #3  0x7ff18b9c89e6 in ?? () from
> /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4  0x7ff19512fd7d in ?? ()
> from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5  0x7ff195c52fb7 in
> start_thread (arg=) at
> pthread_create.c:486
> #6  0x7ff195d651af in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 3 (Thread 0x7ff18af04700 (LWP 1433260)):
> #0  0x7ff195d5abef in __GI___poll (fds=0x55fdcd6ffb90, nfds=1,
> timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x7ff19510710e in ?? () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2  0x7ff19510722f in
> g_main_context_iteration () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
> #3  0x7ff195107281 in ?? () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4  0x7ff19512fd7d in ?? ()
> from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5  0x7ff195c52fb7 in
> start_thread (arg=) at
> pthread_create.c:486
> #6  0x7ff195d651af in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 2 (Thread 0x7ff1912c6700 (LWP 1433259)):
> #0  0x7ff195d5abef in __GI___poll (fds=0x7ff1912c5ca8, nfds=1,
> timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
> #1  0x7ff194ff1cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
> #2  0x7ff194ff391a in xcb_wait_for_event () from /usr/lib/x86_64-linux-
> gnu/libxcb.so.1
> #3  0x7ff191eabca0 in ?? () from /usr/lib/x86_64-linux-
> gnu/libQt5XcbQpa.so.5
> #4  0x7ff1960ce8b2 in ?? () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5  0x7ff195c52fb7 in
> start_thread (arg=) at
> pthread_create.c:486
> #6  0x7ff195d651af in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
> 
> Thread 1 (Thread 0x7ff192558800 (LWP 1433258)):
> [KCrash Handler]
> #6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
> #7  0x7ff195c90535 in __GI_abort () at abort.c:79
> #8  0x55fdcbc662e2 in akMessageHandler (type=QtFatalMsg, msg=...,
> context=...) at ./src/shared/akdebug.cpp:205
> #9  akMessageHandler (type=, context=..., msg=...) at
> ./src/shared/akdebug.cpp:194
> #10 0x55fdcbc6834e in (anonymous namespace)::RemoteLogger::dbusLogger
> (type=QtFatalMsg, ctx=..., msg=...) at ./src/shared/akremotelog.cpp:178
> #11 0x7ff1960c64b1 in ?? () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff1960c65c9 in ?? ()
> from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff196096a44 in
> QMessageLogger::fatal(char const*, ...) const () from
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
> #14 0x55fdcbc3c4e1 in AgentManager::AgentManager (this=0x7ffd636395f0,
> verbose=, parent=) at
> /usr/include/x86_64-linux- gnu/qt5/QtCore/qlogging.h:91
> #15 0x55fdcbc3e374 in main (argc=, argv=)
> at ./src/akonadicontrol/main.cpp:76
> [Inferior 1 (process 1433258) detached]
> 
> 
> 
> -- System Information:
> 

Processed: Re: Bug#951588: kontact: akonadi is not operational

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #951588 [kontact] kontact: akonadi is not operational
Added tag(s) moreinfo.
> severity -1 important
Bug #951588 [kontact] kontact: akonadi is not operational
Severity set to 'important' from 'grave'

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

Bug#957574: marked as done (nas: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 21:48:40 +
with message-id 
and subject line Bug#957574: fixed in nas 1.9.4-7
has caused the Debian Bug report #957574,
regarding nas: 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.)


-- 
957574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nas
Version: 1.9.4-6
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/nas_1.9.4-6_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

[...]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
config.c: In function ‘ddaSetConfig’:
config.c:30:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   30 | num = (int) value;
  |   ^
config.c:40:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   40 | num = (int) value;
  |   ^
config.c:45:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   45 | num = (int) value;
  |   ^
config.c:53:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   53 | num = (int) value;
  |   ^
config.c:64:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   64 | num = (int) value;
  |   ^
config.c:69:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   69 | num = (int) value;
  |   ^
config.c:87:14: warning: implicit declaration of function ‘strcmp’ 
[-Wimplicit-function-declaration]
   87 | if (!strcmp(str, "/dev/pcaudio") || !strcmp(str, "/dev/pcdsp"))
  |  ^~
config.c:92:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   92 | num = (int) value;
  |   ^
config.c:103:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  103 | num = (int) value;
  |   ^
config.c:128:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  128 | num = (int) value;
  |   ^
config.c:141:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  141 | num = (int) value;
  |   ^
config.c:154:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  154 | num = (int) value;
  |   ^
config.c:164:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  164 | num = (int) value;
  |   ^
config.c:170:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  170 | num = (int) value;
  |   ^
config.c:176:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  176 | num = (int) value;
  |   ^
config.c:182:15: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  182 | num = (int) value;
  |   ^
config.c: In function ‘ddaUseMsg’:
config.c:217:5: warning: implicit declaration of function ‘ErrorF’ 
[-Wimplicit-function-declaration]
  217 | ErrorF("\nNo Server specific options supported.\n");
  | ^~
rm -f 

Bug#978584: anyremote-doc: missing Breaks+Replaces: anyremote (<< 6.7.3-2)

[Andreas Beckmann]

Package: anyremote-doc
Version: 6.7.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../anyremote-doc_6.7.3-2_all.deb ...
  Unpacking anyremote-doc (6.7.3-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/anyremote-doc_6.7.3-2_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/anyremote/NEWS.gz', which is also in 
package anyremote 6.7.3-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/anyremote-doc_6.7.3-2_all.deb

This is probably caused by a behavioral change of dh_installdocs
that was activated by the recent debhelper-compat bump.


cheers,

Andreas


anyremote=6.7.3-1_anyremote-doc=6.7.3-2.log.gz
Description: application/gzip

Bug#978583: libtrapperkeeper-filesystem-watcher-clojure: files in .jar don't follow the proper hierarchy

[Louis-Philippe Véronneau]

Package: libtrapperkeeper-filesystem-watcher-clojure
Version: 1.2.2-1
Severity: grave
Owner: po...@debian.org

The .jar in this package contains the following .clj files:

clj/
clj/puppetlabs/
clj/puppetlabs/trapperkeeper/
clj/puppetlabs/trapperkeeper/services/
clj/puppetlabs/trapperkeeper/services/protocols/
clj/puppetlabs/trapperkeeper/services/protocols/filesystem_watch_service.clj
clj/puppetlabs/trapperkeeper/services/watcher/
clj/puppetlabs/trapperkeeper/services/watcher/filesystem_watch_core.clj
clj/puppetlabs/trapperkeeper/services/watcher/filesystem_watch_service.clj

They should be following this hierarchy instead:

puppetlabs/trapperkeeper/
puppetlabs/trapperkeeper/services/
puppetlabs/trapperkeeper/services/protocols/
puppetlabs/trapperkeeper/services/protocols/filesystem_watch_service.clj
puppetlabs/trapperkeeper/services/watcher/
puppetlabs/trapperkeeper/services/watcher/filesystem_watch_core.clj
puppetlabs/trapperkeeper/services/watcher/filesystem_watch_service.clj

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#976037: marked as done (ms-gsl's autopkg tests are broken by design)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 21:18:27 +
with message-id 
and subject line Bug#976037: fixed in ms-gsl 3.1.0-4
has caused the Debian Bug report #976037,
regarding ms-gsl's autopkg tests are broken by design
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.)


-- 
976037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: src:ms-gsl
Version: 3.1.0-3
Severity: serious

$ cat debian/tests/control
Tests: with-gcc8-std14 with-gcc8-std17
Depends: cmake, g++-8, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-gcc9-std14 with-gcc9-std17
Depends: cmake, g++-9, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-gcc10-std17 with-gcc10-std20
Depends: cmake, g++-10, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-clang8-std14 with-clang8-std17
Depends: cmake, clang-8, libc++-8-dev, libc++abi-8-dev, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-clang9-std14 with-clang9-std17
Depends: cmake, clang-9, libc++-9-dev, libc++abi-9-dev, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-clang10-std14 with-clang10-std17
Depends: cmake, clang-10, libc++-10-dev, libc++abi-10-dev, libgtest-dev, 
pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-clang11-std17 with-clang11-std20
Depends: cmake, clang-11, libc++-11-dev, libc++abi-11-dev, libgtest-dev, 
pkg-config
Restrictions: allow-stderr, skip-not-installable

Tests: with-clang12-std17 with-clang12-std20
Depends: cmake, clang-12, libc++-12-dev, libc++abi-12-dev, libgtest-dev, 
pkg-config
Restrictions: allow-stderr, skip-not-installable

Now, there's at least one test (the clang-12 one), which never will succeed. So
what's the value of these tests when you always have failures due to
non-existing versions?  Please just test for the default gcc and clang.
--- End Message ---
--- Begin Message ---
Source: ms-gsl
Source-Version: 3.1.0-4
Done: Nicholas Guriev 

We believe that the bug you reported is fixed in the latest version of
ms-gsl, 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.
Nicholas Guriev  (supplier of updated ms-gsl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Dec 2020 17:13:40 +0300
Source: ms-gsl
Architecture: source
Version: 3.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Nicholas Guriev 
Changed-By: Nicholas Guriev 
Closes: 976037
Changes:
 ms-gsl (3.1.0-4) unstable; urgency=medium
 .
   * Run autopkgtests only against default GCC and Clang (closes: #976037).
   * Bump Standards-Versions to 4.5.1, no related changes for this.
Checksums-Sha1:
 30f8e7d7732749b1d14bab539795846b53461079 2015 ms-gsl_3.1.0-4.dsc
 f46059fefa2188e603863109862696796af7d112 6480 ms-gsl_3.1.0-4.debian.tar.xz
 08e411ffe6919f187ab516014c60fe64546b8bd5 5240 ms-gsl_3.1.0-4_source.buildinfo
Checksums-Sha256:
 a4349ab6b8d36642defa1567dcb384a202a31c7c41983736766e28fc04e18d04 2015 
ms-gsl_3.1.0-4.dsc
 4eddccb6ae03a907435da926f9e1af9c09ee323caa06e41b126b8ca1d971c30f 6480 
ms-gsl_3.1.0-4.debian.tar.xz
 5ad0d9046cf405ac27b84005473ea471154fe48c3b656d7c60978520cfabf8c4 5240 
ms-gsl_3.1.0-4_source.buildinfo
Files:
 048bdf52334820951e3052c5b6d3b170 2015 libdevel optional ms-gsl_3.1.0-4.dsc
 ce0ba0c0ebfca42b093a9a4f99db4077 6480 libdevel optional 
ms-gsl_3.1.0-4.debian.tar.xz
 51f328c544c66cb0ca6eab3ca996682d 5240 libdevel optional 
ms-gsl_3.1.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoDLeOit93I/iGLK2bXpN3piwCsFAl/qRvsACgkQ2bXpN3pi
wCuubQ//WNwNjoOAxohgp82M6FJP03UyCsZ4JYyfHWq5K6k1D7VjQLoR+Nkfooyt
UyIRZxcXx3+26yWy+zJRfiDZOxXmqsgbAuhQS38QmaGURlqk4dHYobWKUkSAIwIG
2LJH8/C9rIlDRv96q5JgqLUUZm/S40E9EUSVDZejz5NDDcUKXF5YPIewtpEmVbMH
l07pudmDcQb6+ed9a0DikK/7HWhK/CbQ3pUhIbf3mJ9iNLBp578lSpd2KYeMDpTr
VUvWnWAtM7/wWAefaCMj4E0P4vqThjwHt+hdxIiXuE7dQ+z4+fWJvDb49TtBh7J7
H62GdH21oWE+/fsqiV6wUdt8xMY7dAsHxZPXUysJ4DTxPeQAlmCz1GCEra/FINFI

Bug#978343: marked as done (lincity: FTBFS: configure:14792: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 21:03:43 +
with message-id 
and subject line Bug#978343: fixed in lincity 1.13.1-15
has caused the Debian Bug report #978343,
regarding lincity: FTBFS: configure:14792: error: possibly undefined macro: 
AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?)
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.)


-- 
978343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lincity
Version: 1.13.1-14
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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 '/<>'
> cp /usr/share/gettext/config.rpath /<>
> cp /usr/share/gettext/po/Makefile.in.in /<>/po
> dh_autoreconf
> acinclude.m4:9: warning: underquoted definition of FC_EXPAND_DIR
> acinclude.m4:9:   run info Automake 'Extending aclocal'
> acinclude.m4:9:   or see 
> https://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:108: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.ac:108: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:108: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.ac:108: the top level
> autoreconf: configure.ac: AM_GNU_GETTEXT is used, but not 
> AM_GNU_GETTEXT_VERSION
> libtoolize: putting auxiliary files in '.'.
> libtoolize: copying file './ltmain.sh'
> libtoolize: putting macros in 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
> libtoolize: and rerunning libtoolize and aclocal.
> libtoolize: 'AC_PROG_RANLIB' is rendered obsolete by 'LT_INIT'
> acinclude.m4:9: warning: underquoted definition of FC_EXPAND_DIR
> acinclude.m4:9:   run info Automake 'Extending aclocal'
> acinclude.m4:9:   or see 
> https://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:108: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> /usr/share/aclocal/gettext.m4:55: AM_GNU_GETTEXT is expanded from...
> configure.ac:108: the top level
> ERROR: Use of AM_GNU_GETTEXT without [external] argument is no longer 
> supported.
> configure.ac:108: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd
> aclocal.m4:77: AM_GNU_GETTEXT is expanded from...
> configure.ac:108: the top level
> configure:14792: error: possibly undefined macro: AM_INTL_SUBDIR
>   If this token and others are legitimate, please use m4_pattern_allow.
>   See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make[1]: *** [debian/rules:9: override_dh_autoreconf] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/lincity_1.13.1-14_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: lincity
Source-Version: 1.13.1-15
Done: Kari Pahula 

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

Bug#978331: marked as done (libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 21:03:38 +
with message-id 
and subject line Bug#978331: fixed in libpdf-builder-perl 3.021-1
has caused the Debian Bug report #978331,
regarding libpdf-builder-perl: FTBFS: dh_auto_test: error: make -j4 test 
TEST_VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
978331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdf-builder-perl
Version: 3.020-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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 '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00-all-usable.t ... 
> 1..108
> ok 1 - use PDF::Builder;
> ok 2 - use PDF::Builder::Outlines;
> ok 3 - use PDF::Builder::Annotation;
> ok 4 - use PDF::Builder::Resource;
> ok 5 - use PDF::Builder::Util;
> ok 6 - use PDF::Builder::Lite;
> ok 7 - use PDF::Builder::NamedDestination;
> ok 8 - use PDF::Builder::UniWrap;
> ok 9 - use PDF::Builder::Matrix;
> ok 10 - use PDF::Builder::Docs;
> ok 11 - use PDF::Builder::Page;
> ok 12 - use PDF::Builder::Content;
> ok 13 - use PDF::Builder::Outline;
> ok 14 - use PDF::Builder::Resource::PaperSizes;
> ok 15 - use PDF::Builder::Resource::Colors;
> ok 16 - use PDF::Builder::Resource::Pattern;
> ok 17 - use PDF::Builder::Resource::BaseFont;
> ok 18 - use PDF::Builder::Resource::Shading;
> ok 19 - use PDF::Builder::Resource::Glyphs;
> ok 20 - use PDF::Builder::Resource::UniFont;
> ok 21 - use PDF::Builder::Resource::ColorSpace;
> ok 22 - use PDF::Builder::Resource::Font;
> ok 23 - use PDF::Builder::Resource::XObject;
> ok 24 - use PDF::Builder::Resource::ExtGState;
> ok 25 - use PDF::Builder::Resource::CIDFont;
> ok 26 - use PDF::Builder::Resource::ColorSpace::Separation;
> ok 27 - use PDF::Builder::Resource::ColorSpace::Indexed;
> ok 28 - use PDF::Builder::Resource::ColorSpace::DeviceN;
> ok 29 - use PDF::Builder::Resource::ColorSpace::Indexed::WebColor;
> ok 30 - use PDF::Builder::Resource::ColorSpace::Indexed::Hue;
> ok 31 - use PDF::Builder::Resource::ColorSpace::Indexed::ACTFile;
> ok 32 - use PDF::Builder::Resource::CIDFont::CJKFont;
> ok 33 - use PDF::Builder::Resource::CIDFont::TrueType;
> ok 34 - use PDF::Builder::Resource::CIDFont::TrueType::FontFile;
> ok 35 - use PDF::Builder::Resource::XObject::Image;
> ok 36 - use PDF::Builder::Resource::XObject::Form;
> ok 37 - use PDF::Builder::Resource::XObject::Image::GIF;
> ok 38 - use PDF::Builder::Resource::XObject::Image::JPEG;
> ok 39 - use PDF::Builder::Resource::XObject::Image::PNG;
> ok 40 - use PDF::Builder::Resource::XObject::Image::PNG_IPL;
> ok 41 - use PDF::Builder::Resource::XObject::Image::PNM;
> ok 42 - use PDF::Builder::Resource::XObject::Image::TIFF;
> ok 43 - use PDF::Builder::Resource::XObject::Image::TIFF_GT;
> ok 44 - use PDF::Builder::Resource::XObject::Image::GD;
> ok 45 - use PDF::Builder::Resource::XObject::Image::TIFF::File_GT;
> ok 46 - use PDF::Builder::Resource::XObject::Image::TIFF::File;
> ok 47 - use PDF::Builder::Resource::XObject::Form::Hybrid;
> ok 48 - use PDF::Builder::Resource::XObject::Form::BarCode;
> ok 49 - use PDF::Builder::Resource::XObject::Form::BarCode::ean13;
> ok 50 - use PDF::Builder::Resource::XObject::Form::BarCode::code128;
> ok 51 - use PDF::Builder::Resource::XObject::Form::BarCode::int2of5;
> ok 52 - use PDF::Builder::Resource::XObject::Form::BarCode::code3of9;
> ok 53 - use PDF::Builder::Resource::XObject::Form::BarCode::codabar;
> ok 54 - use PDF::Builder::Resource::Font::CoreFont;
> ok 55 - use PDF::Builder::Resource::Font::SynFont;
> ok 56 - use PDF::Builder::Resource::Font::Postscript;
> ok 57 - use PDF::Builder::Resource::Font::BdFont;
> ok 58 - use PDF::Builder::Resource::Font::CoreFont::webdings;
> ok 59 - use PDF::Builder::Resource::Font::CoreFont::timesbolditalic;
> ok 60 - use PDF::Builder::Resource::Font::CoreFont::zapfdingbats;
> ok 61 - use PDF::Builder::Resource::Font::CoreFont::symbol;
> ok 62 - use PDF::Builder::Resource::Font::CoreFont::georgiabolditalic;
> ok 63 - use PDF::Builder::Resource::Font::CoreFont::courierbold;
> ok 64 - use PDF::Builder::Resource::Font::CoreFont::trebuchetbolditalic;
> ok 65 - use PDF::Builder::Resource::Font::CoreFont::verdanaitalic;
> ok 66 - use 

Bug#978516: marked as done (openjdk-11-jre-dcevm: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 20:48:51 +
with message-id 
and subject line Bug#978516: fixed in openjdk-11-jre-dcevm 11.0.9+1-2
has caused the Debian Bug report #978516,
regarding openjdk-11-jre-dcevm: non-standard gcc/g++ used for build (gcc-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.)


-- 
978516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-11-jre-dcevm
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: openjdk-11-jre-dcevm
Source-Version: 11.0.9+1-2
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated openjdk-11-jre-dcevm 
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, 28 Dec 2020 11:16:59 -0800
Source: openjdk-11-jre-dcevm
Architecture: source
Version: 11.0.9+1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 978516
Changes:
 openjdk-11-jre-dcevm (11.0.9+1-2) unstable; urgency=medium
 .
   * Team upload.
   * Build with default g++ (Closes: #978516)
   * Bump Standards-Version to 4.5.1
Checksums-Sha1:
 a979432e48fe1db4be21df9e3a7d315a215a892a 2291 
openjdk-11-jre-dcevm_11.0.9+1-2.dsc
 738a940ecd539d1c5c9a26224d0836c9ffdf08b9 5756 
openjdk-11-jre-dcevm_11.0.9+1-2.debian.tar.xz
 844c542532f5e1d2fed08dc3019b324de1cb6d54 9884 
openjdk-11-jre-dcevm_11.0.9+1-2_amd64.buildinfo
Checksums-Sha256:
 b46100a76969dd3b8c0342ade55e9721bd58b994bcdc9b155256a4cd7d394b8b 2291 
openjdk-11-jre-dcevm_11.0.9+1-2.dsc
 7d3c51f3d85b61e0532e8e0452a6c0f553b3a4af62e0957e9a22f1432c467cbc 5756 
openjdk-11-jre-dcevm_11.0.9+1-2.debian.tar.xz
 0629a022868a11f0597b55d4d744e016b01c6a6cdf6f0c5274096e7622dccb37 9884 
openjdk-11-jre-dcevm_11.0.9+1-2_amd64.buildinfo
Files:
 76d8d27e6e5c48854d19158507cb04ca 2291 java optional 
openjdk-11-jre-dcevm_11.0.9+1-2.dsc
 9fa53e1f785b296dd5624c19cf84c6b1 5756 java optional 
openjdk-11-jre-dcevm_11.0.9+1-2.debian.tar.xz
 3d68460591f65dd740f784bdcee87210 9884 java optional 
openjdk-11-jre-dcevm_11.0.9+1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl/qQG4UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbXSRAAu8nX8bo3V8RfRU5Z3XvtrHTrZ10E
gNVnP4KNDgL9ZQF3jbdbx5gw8ghnDr/VvGe3+xZzPTxw4SOFXPaLY6erNnBhCf0N
89uL9VNh8/ZFCFF5xuWgqMoXgteE4EOQhR1RW2zyQ6OYINvQYpumOXWngnYtY88V
ZVeAX4RXtQoZTX4Pz1drS+ev62NXY/wSVdNOarjFjZ4WEg5XUXp5CRL9bChItVM1
oSkur1kGsltrclC8Mt8uiGACngJHXR6vgGSgoWOY+8wji3aV/zpBvyndAIg8yZBH
t2r+aYIfeuZ+zDJFHRYy65sMMViBaY5x10RgsfLxfrdCsDmeMyAGqegAPzK8bob0
xqLp3eYr9HoUy/j+DYGJSXIsZ6uH2FxNBB47v0gCuLcv4K2O+gX1EFZXn0YQ/jRR
aoLfJgRuKy6lswN6rBGX2qUzPMzSTt9QyZyzDJc/UMMMV1tnQglwAYE68NFmMq7D
NjYQIOB+Eqt5dJixCDMaFaC5wfiSMvZ/lxmXAYKBAhNBTeKJAmbRcUIWyxDL/GW/
asPiott2rKFo/N98KyCM/11woATPPc2ziBMM6+zf3YHSv25Qst2WbkoNRR9gKh7T
UFtx86uaHl8wsi8Nt3QW0b4KMr/6DZYBEWOIQVYPxWbZOGsWSdZ1DGKgFN11QDG0
2l1xrduwg/2tSdE=
=WbwZ
-END PGP SIGNATURE End Message ---

Processed: found 974797 in 1.6-1, block 974797 with 975931

[Debian Bug Tracking System]

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

> found 974797 1.6-1
Bug #974797 {Done: Andreas Beckmann } [pocl] pocl: Please 
upgrade to llvm-toolchain-11
Bug #974823 {Done: Andreas Beckmann } [pocl] pocl: Please 
upgrade to llvm-toolchain-11
There is no source info for the package 'pocl' at version '1.6-1' with 
architecture ''
Unable to make a source version for version '1.6-1'
Marked as found in versions 1.6-1 and reopened.
Marked as found in versions 1.6-1 and reopened.
> block 974797 with 975931
Bug #974797 [pocl] pocl: Please upgrade to llvm-toolchain-11
Bug #974823 [pocl] pocl: Please upgrade to llvm-toolchain-11
974797 was not blocked by any bugs.
974797 was not blocking any bugs.
Added blocking bug(s) of 974797: 975931
974823 was not blocked by any bugs.
974823 was not blocking any bugs.
Added blocking bug(s) of 974823: 975931
> thanks
Stopping processing here.

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

Bug#978560: marked as done (mediastreamer2: dropped pkgconfig file breaks kopete)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 20:19:47 +
with message-id 
and subject line Bug#978560: fixed in mediastreamer2 1:4.4.21-2
has caused the Debian Bug report #978560,
regarding mediastreamer2: dropped pkgconfig file breaks kopete
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.)


-- 
978560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mediastreamer2
Version: 1:4.4.21-1
Severity: serious
tags: patch

Hello, kopete does use pkgconfig to find the mediastreamer2, and the new 
version with the cmake switch dropped the pkgconfig
installation.

I did craft a patch to install the pkgconfig file in cmake builds too (as it is 
done with autoconf).

It might be not the best patch to fix the issue, but it should work (the 
variables are called differently in cmake/autotools, so I had to set includedir 
manually in cmake before configuring the .pc.in file).

Please have a look and apply / forward upstream if you like it.

G.

Description: Add pkgconfig file to help kopete find the library
Author: Gianfranco Costamagna 
Forwarded: no
Last-Update: 2020-12-28

Index: mediastreamer2-4.4.21/CMakeLists.txt
===
--- mediastreamer2-4.4.21.orig/CMakeLists.txt
+++ mediastreamer2-4.4.21/CMakeLists.txt
@@ -666,8 +666,12 @@
set(PACKAGE_DATA_DIR "${CMAKE_INSTALL_DATADIR}")
 endif()
 
+set(libdir ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR})
+set(includedir ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_INCLUDEDIR})
 configure_file(${CMAKE_CURRENT_SOURCE_DIR}/mediastreamer-config.h.cmake 
${CMAKE_CURRENT_BINARY_DIR}/mediastreamer-config.h)
 set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/mediastreamer-config.h 
PROPERTIES GENERATED ON)
+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/mediastreamer.pc.in 
${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc)
+set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc 
PROPERTIES GENERATED ON)
 add_definitions("-DHAVE_CONFIG_H")
 
 if(ENABLE_DOC)
@@ -699,6 +703,11 @@
NO_SET_AND_CHECK_MACRO
 )
 
+install(FILES
+   "${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc"
+   DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig
+)
+
 install(EXPORT ${EXPORT_TARGETS_NAME}Targets
FILE Mediastreamer2Targets.cmake
DESTINATION ${CONFIG_PACKAGE_LOCATION}
--- End Message ---
--- Begin Message ---
Source: mediastreamer2
Source-Version: 1:4.4.21-2
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated mediastreamer2 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, 28 Dec 2020 20:51:15 +0100
Source: mediastreamer2
Architecture: source
Version: 1:4.4.21-2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Closes: 978560
Changes:
 mediastreamer2 (1:4.4.21-2) unstable; urgency=medium
 .
   * Drop cmake version constraint satisfied in oldstable
   * Drop Multi-Arch: same on libmediastreamer-dev, contains
 arch-specific data
   * d/patch/install-pkgconfig: Install mediastreamer.pc.
 Thanks to Gianfranco Costamagna (Closes: #978560)
Checksums-Sha1:
 701fc954d36fc32d3bc41addfd628a26a9cdfe80 2927 mediastreamer2_4.4.21-2.dsc
 30ed11f8725291435f236f5cc661b1d92a9a 6072 
mediastreamer2_4.4.21-2.debian.tar.xz
 775c40519ee46a9affaea226dc7e2da4eea75782 15690 
mediastreamer2_4.4.21-2_amd64.buildinfo
Checksums-Sha256:
 eb1b2d67165473b610b72382a8b313d28673cddfee8bde5a18321ead0ea6cc52 2927 
mediastreamer2_4.4.21-2.dsc
 074ab81bf83b05203c8d7037d637231eeaf6c9cc6a0a3f5e7e477c4f2eb61255 6072 
mediastreamer2_4.4.21-2.debian.tar.xz
 6f3fede0406252e1e3a977220d4215d35887477799d4a8fdf649da888c591a24 15690 
mediastreamer2_4.4.21-2_amd64.buildinfo
Files:
 bbcead2c279320f3bafb60097cb61ae8 2927 libs optional mediastreamer2_4.4.21-2.dsc
 957e7cc9481b0259346dbdcdf03c8471 6072 libs optional 

Processed: Re: kalgebra: Output is always blank

[Debian Bug Tracking System]

Processing control commands:

> tags -1 buster
Bug #955567 [kalgebra] kalgebra: Output is always blank
Added tag(s) buster.

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

Bug#955567: kalgebra: Output is always blank

[Paul Gevers]

Control: tags -1 buster

Hi Charles,

On 28-12-2020 20:51, Charles Samuels wrote:
> On Monday, December 28, 2020 11:30:18 AM PST Paul Gevers wrote:
>> I tried to reproduce this in current testing and for me it works. Is
>> this issue still a problem for you?
> 
> Yes it is still an issue (stable).

I can then only assume it got fixed in the mean time (in
unstable/testing). Tagging this bug as appropriate, but leaving it open
for now just in case somebody wants to jump in.

> Curiously, when I right click on the output area, the popup menu with "Clear" 
> is positioned in relation to the desktop and not the place I clicked at (so 
> if 
> you click at coordinate 100x100 in the area, the popup appears at 100x100 
> global coordinates).
> 
> I use KDE's desktop scaling (1.5x). I tried disabling that and then 
> restarting 
> kalgebra (without logging out) with no change.
> 
> I see nothing interesting in .xsession-errors or kalgebra's output

I can't offer much help, as I'm not familiar with the KDE stack. I was
mostly interested from the release process point of view.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#957732: marked as done (qtermwidget: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 21:07:15 +0100
with message-id <20e07c08-030f-d6cc-739c-13d75a456...@debian.org>
and subject line Re: qtermwidget: ftbfs with GCC-10
has caused the Debian Bug report #957732,
regarding qtermwidget: 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.)


-- 
957732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qtermwidget
Version: 0.14.1-3
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/qtermwidget_0.14.1-3_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 /<>/lib/ColorScheme.h:34,
 from /<>/lib/ColorScheme.cpp:23:
/<>/lib/CharacterColor.h:84:8: note: because ‘Konsole::ColorEntry’ 
has user-provided ‘void Konsole::ColorEntry::operator=(const 
Konsole::ColorEntry&)’
   84 |   void operator=(const ColorEntry& rhs)
  |^~~~
[ 54%] Building CXX object CMakeFiles/qtermwidget5.dir/lib/History.cpp.o
/usr/bin/c++  -DCOLORSCHEMES_DIR=\"/usr/share/qtermwidget5/color-schemes\" 
-DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DHAVE_UPDWTMPX -DHAVE_UTF8PROC 
-DKB_LAYOUT_DIR=\"/usr/share/qtermwidget5/kb-layouts\" -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH 
-DQT_NO_URL_CAST_FROM_STRING -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB 
-DTRANSLATIONS_DIR=\"/usr/share/qtermwidget5/translations\" 
-Dqtermwidget5_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -I/<>/lib 
-I/<>/obj-x86_64-linux-gnu/lib -isystem 
/usr/include/x86_64-linux-gnu/qt5 -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/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
 -fno-exceptions -Wall -Wextra -Wchar-subscripts -Wno-long-long -Wpointer-arith 
-Wundef -Wformat-security -Wnon-virtual-dtor -Woverloaded-virtual -Wpedantic 
-O2 -g -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden   -fPIC 
-std=gnu++14 -o CMakeFiles/qtermwidget5.dir/lib/History.cpp.o -c 
/<>/lib/History.cpp
[ 55%] Building CXX object CMakeFiles/qtermwidget5.dir/lib/HistorySearch.cpp.o
/usr/bin/c++  -DCOLORSCHEMES_DIR=\"/usr/share/qtermwidget5/color-schemes\" 
-DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DHAVE_UPDWTMPX -DHAVE_UTF8PROC 
-DKB_LAYOUT_DIR=\"/usr/share/qtermwidget5/kb-layouts\" -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH 
-DQT_NO_URL_CAST_FROM_STRING -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB 
-DTRANSLATIONS_DIR=\"/usr/share/qtermwidget5/translations\" 
-Dqtermwidget5_EXPORTS -I/<>/obj-x86_64-linux-gnu 
-I/<> -I/<>/lib 
-I/<>/obj-x86_64-linux-gnu/lib -isystem 
/usr/include/x86_64-linux-gnu/qt5 -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/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
 -fno-exceptions -Wall -Wextra -Wchar-subscripts -Wno-long-long -Wpointer-arith 
-Wundef -Wformat-security -Wnon-virtual-dtor -Woverloaded-virtual -Wpedantic 

Bug#957732: qtermwidget: ftbfs with GCC-10

[Paul Gevers]

Version: 0.16.1-1

Hi,

On Fri, 17 Apr 2020 11:09:35 + Matthias Klose  wrote:
> 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.

A successful upload happened since.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: owner 978516

[Debian Bug Tracking System]

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

> owner 978516 tmanc...@debian.org
Bug #978516 [openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: non-standard gcc/g++ 
used for build (gcc-9)
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.

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

Bug#955567: kalgebra: Output is always blank

[Charles Samuels]

On Monday, December 28, 2020 11:30:18 AM PST Paul Gevers wrote:
>  wrote:
> > KAlgebra shows nothing in its output screen. This only applies
> > to the algebraic displays, the graphs and dictionary tabs seem
> > to work fine.
> > 
> > Reproduce: Enter any equation into the input text box and press enter.
> > 
> > Expected: The result of the equation and the equation inputted should be
> > visible.
> > 
> > Actual: Nothing appears. Even the border of the frame appears missing.
> > 
> > Also: Right clicking on the empty area causes a context menu to appear
> > in the wrong place. I'm not sure if that's related.
> 
> I tried to reproduce this in current testing and for me it works. Is
> this issue still a problem for you?

Yes it is still an issue (stable).

Curiously, when I right click on the output area, the popup menu with "Clear" 
is positioned in relation to the desktop and not the place I clicked at (so if 
you click at coordinate 100x100 in the area, the popup appears at 100x100 
global coordinates).

I use KDE's desktop scaling (1.5x). I tried disabling that and then restarting 
kalgebra (without logging out) with no change.

I see nothing interesting in .xsession-errors or kalgebra's output

Charles

Bug#978315: marked as done (dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:48:29 +
with message-id 
and subject line Bug#978315: fixed in dasher 5.0.0~beta~repack2-2
has caused the Debian Bug report #978315,
regarding dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned 
exit code 2
to be marked as done.

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

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


-- 
978315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dasher
Version: 5.0.0~beta~repack2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/po'
> INTLTOOL_EXTRACT="/usr/bin/intltool-extract" XGETTEXT="/usr/bin/xgettext" 
> srcdir=. /usr/bin/intltool-update --gettext-package dasher --pot
> xgettext: x-c.c:1666: phase5_get: Assertion `UNICODE_VALUE (c) >= 0 && 
> UNICODE_VALUE (c) < 0x11' failed.
> ERROR: xgettext failed to generate PO template file. Please consult
>error message above if there is any.
> make[2]: *** [Makefile:153: dasher.pot] Error 1
> make[2]: Leaving directory '/<>/po'
> make[1]: *** [Makefile:535: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/dasher_5.0.0~beta~repack2-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: dasher
Source-Version: 5.0.0~beta~repack2-2
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated dasher 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, 28 Dec 2020 20:29:37 +0100
Source: dasher
Binary: dasher dasher-data dasher-dbgsym
Architecture: source
Version: 5.0.0~beta~repack2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 dasher - graphical predictive text input system
 dasher-data - Data files for dasher
Closes: 978315
Changes:
 dasher (5.0.0~beta~repack2-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Fill in Homepage field.
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Name.
   * Fix day-of-week for changelog entries 3.2.10-4, 3.2.10-3.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Samuel Thibault ]
   * control: Update alioth list domain.
   * rules: Drop now-default -Wl,--as-needed option
   * patches/intltool-update: Avoid issue with intltool-update
 (Closes: #978315).
Checksums-Sha1:
 f00cff8c6710cad8abc007b2639a3e286e70d909 2284 dasher_5.0.0~beta~repack2-2.dsc
 fb50e5f45939e5d7626e26a68b0ee3e0e3173e0d 2089964 
dasher_5.0.0~beta~repack2-2.debian.tar.xz
Checksums-Sha256:
 88f0c6e1c3faa7bbd09af8a639dcf7c3ec6c44d7fb94bab9c279f04aa1473ab7 2284 
dasher_5.0.0~beta~repack2-2.dsc
 aa9b2ba8ebb16d4e91644bc7c2b23f63dfbe87b9a1407eb425800f733ceabc8e 2089964 
dasher_5.0.0~beta~repack2-2.debian.tar.xz
Files:
 f6a1550c660e2761e858f3fce10d1b76 2284 x11 optional 
dasher_5.0.0~beta~repack2-2.dsc
 

Bug#957435: marked as done (libfabric: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 20:40:01 +0100
with message-id <5c9fb60e-8f45-b0ed-fddb-f4318d006...@debian.org>
and subject line Re: libfabric: ftbfs with GCC-10
has caused the Debian Bug report #957435,
regarding libfabric: 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.)


-- 
957435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libfabric
Version: 1.6.2-3
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/libfabric_1.6.2-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_ep_rdm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:684:
 multiple definition of `fi_ibv_msg_ep_cm_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:684:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_ep_rdm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:683:
 multiple definition of `fi_ibv_msg_ep_atomic_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:683:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:687:
 multiple definition of `fi_ibv_msg_srq_ep_msg_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:687:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:686:
 multiple definition of `fi_ibv_msg_ep_rma_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:686:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:685:
 multiple definition of `fi_ibv_msg_ep_msg_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:685:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:684:
 multiple definition of `fi_ibv_msg_ep_cm_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:684:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cm.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:683:
 multiple definition of `fi_ibv_msg_ep_atomic_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:683:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cntr.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:687:
 multiple definition of `fi_ibv_msg_srq_ep_msg_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:687:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cntr.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:686:
 multiple definition of `fi_ibv_msg_ep_rma_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:686:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cntr.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:685:
 multiple definition of `fi_ibv_msg_ep_msg_ops'; 
prov/verbs/src/.libs/src_libfabric_la-fi_verbs.o:./prov/verbs/src/fi_verbs.h:685:
 first defined here
/usr/bin/ld: 
prov/verbs/src/ep_rdm/.libs/src_libfabric_la-verbs_rdm_cntr.o:./prov/verbs/src/ep_rdm/../fi_verbs.h:684:
 multiple definition of 

Processed: Re: kalgebra: Output is always blank

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 4:20.08.0-1
Bug #955567 [kalgebra] kalgebra: Output is always blank
Ignoring request to alter found versions of bug #955567 to the same values 
previously set

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

Bug#955567: kalgebra: Output is always blank

[Paul Gevers]

Control: notfound -1 4:20.08.0-1

Hi Charles,

On Thu, 02 Apr 2020 16:57:16 + (UTC) Charles Samuels
 wrote:
> KAlgebra shows nothing in its output screen. This only applies
> to the algebraic displays, the graphs and dictionary tabs seem
> to work fine.
> 
> Reproduce: Enter any equation into the input text box and press enter.
> 
> Expected: The result of the equation and the equation inputted should be 
> visible.
> 
> Actual: Nothing appears. Even the border of the frame appears missing.
> 
> Also: Right clicking on the empty area causes a context menu to appear
> in the wrong place. I'm not sure if that's related.

I tried to reproduce this in current testing and for me it works. Is
this issue still a problem for you?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: cloning 978315, reassign -1 to gettext ..., severity of -1 is important, affects -1

[Debian Bug Tracking System]

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

> clone 978315 -1
Bug #978315 [src:dasher] dasher: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Bug 978315 cloned as bug 978580
> reassign -1 gettext
Bug #978580 [src:dasher] dasher: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Bug reassigned from package 'src:dasher' to 'gettext'.
No longer marked as found in versions dasher/5.0.0~beta~repack2-1.
Ignoring request to alter fixed versions of bug #978580 to the same values 
previously set
> retitle -1 xgettext: should provide an option to ignore some directories
Bug #978580 [gettext] dasher: FTBFS: dh_auto_test: error: make -j4 check 
VERBOSE=1 returned exit code 2
Changed Bug title to 'xgettext: should provide an option to ignore some 
directories' from 'dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2'.
> severity -1 important
Bug #978580 [gettext] xgettext: should provide an option to ignore some 
directories
Severity set to 'important' from 'serious'
> affects -1 + dasher
Bug #978580 [gettext] xgettext: should provide an option to ignore some 
directories
Added indication that 978580 affects dasher
> thanks
Stopping processing here.

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

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978387,
regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=mkcmake
>dh_auto_clean -O--buildsystem=mkcmake
>dh_autoreconf_clean -O--buildsystem=mkcmake
>dh_clean -O--buildsystem=mkcmake
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building inputplug using existing 
> ./inputplug_0.3.orig.tar.gz
> dpkg-source: warning: newly created empty file '_mkc_cc_type.err' will not be 
> represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  inputplug-0.3/_mkc_cc_type.res
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/inputplug_0.3-1.diff.s55vjd
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:44:18Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/inputplug_0.3-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978271,
regarding runawk: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=mkcmake
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=mkcmake
>dh_auto_configure -O--buildsystem=mkcmake
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=mkcmake
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
> SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
> LIBEXECDIR=/usr/lib/x86_64-linux-gnu
> ==
> all ===> runawk
> checking C compiler type... gcc 10.2.1
> bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
> 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" 
> utility'
> *** Error code 1
> dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
> INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
> LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu 
> returned exit code 1
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/runawk_1.6.0-2_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978387,
regarding runawk: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=mkcmake
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=mkcmake
>dh_auto_configure -O--buildsystem=mkcmake
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=mkcmake
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
> SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
> LIBEXECDIR=/usr/lib/x86_64-linux-gnu
> ==
> all ===> runawk
> checking C compiler type... gcc 10.2.1
> bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
> 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" 
> utility'
> *** Error code 1
> dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
> INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
> LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu 
> returned exit code 1
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/runawk_1.6.0-2_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978387: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978387,
regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'
to be marked as done.

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

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


-- 
978387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mk-configure
Version: 0.35.0-1
Severity: serious
Justification: causes FTBFS of libmaa


It looks like mk-configure fails to recognize gcc-10.2.1 (which migrated
to testing almost a week ago), what causes my libmaa package to FTBFS, see:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libmaa.html

   dh "binary" --buildsystem=mkcmake
   dh_update_autotools_config -O--buildsystem=mkcmake
   dh_autoreconf -O--buildsystem=mkcmake
   dh_auto_configure -O--buildsystem=mkcmake
   dh_auto_build -O--buildsystem=mkcmake
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu
==
all ===> doc
==
all ===> maa
checking C compiler type... gcc 10.2.1
bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
*** Error code 1
dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu returned 
exit code 1
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Regards,
Robert

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


Versions of packages mk-configure depends on:
ii  bmake  20200710-5

Versions of packages mk-configure recommends:
ii  pkg-config  0.29.2-1

mk-configure suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 a492934bf07cd69d560d6ee6a16e280c 5700 devel optional 

Bug#978387: marked as done (runawk: FTBFS: bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #977908,
regarding runawk: FTBFS: bmake[2]: 
"/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 'Settings for 
gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=mkcmake
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=mkcmake
>dh_auto_configure -O--buildsystem=mkcmake
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> (level 9 in use)
>dh_auto_build -O--buildsystem=mkcmake
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
>   mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
> SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
> LIBEXECDIR=/usr/lib/x86_64-linux-gnu
> ==
> all ===> runawk
> checking C compiler type... gcc 10.2.1
> bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
> 'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" 
> utility'
> *** Error code 1
> dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
> INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
> LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu 
> returned exit code 1
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/runawk_1.6.0-2_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978271,
regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=mkcmake
>dh_auto_clean -O--buildsystem=mkcmake
>dh_autoreconf_clean -O--buildsystem=mkcmake
>dh_clean -O--buildsystem=mkcmake
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building inputplug using existing 
> ./inputplug_0.3.orig.tar.gz
> dpkg-source: warning: newly created empty file '_mkc_cc_type.err' will not be 
> represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  inputplug-0.3/_mkc_cc_type.res
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/inputplug_0.3-1.diff.s55vjd
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:44:18Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/inputplug_0.3-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 

Bug#978271: marked as done (inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #977908,
regarding inputplug: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --buildsystem=mkcmake
>dh_auto_clean -O--buildsystem=mkcmake
>dh_autoreconf_clean -O--buildsystem=mkcmake
>dh_clean -O--buildsystem=mkcmake
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building inputplug using existing 
> ./inputplug_0.3.orig.tar.gz
> dpkg-source: warning: newly created empty file '_mkc_cc_type.err' will not be 
> represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  inputplug-0.3/_mkc_cc_type.res
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/inputplug_0.3-1.diff.s55vjd
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:44:18Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/inputplug_0.3-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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

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: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#978271: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #978271,
regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'
to be marked as done.

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

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


-- 
978271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mk-configure
Version: 0.35.0-1
Severity: serious
Justification: causes FTBFS of libmaa


It looks like mk-configure fails to recognize gcc-10.2.1 (which migrated
to testing almost a week ago), what causes my libmaa package to FTBFS, see:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libmaa.html

   dh "binary" --buildsystem=mkcmake
   dh_update_autotools_config -O--buildsystem=mkcmake
   dh_autoreconf -O--buildsystem=mkcmake
   dh_auto_configure -O--buildsystem=mkcmake
   dh_auto_build -O--buildsystem=mkcmake
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu
==
all ===> doc
==
all ===> maa
checking C compiler type... gcc 10.2.1
bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
*** Error code 1
dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu returned 
exit code 1
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Regards,
Robert

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


Versions of packages mk-configure depends on:
ii  bmake  20200710-5

Versions of packages mk-configure recommends:
ii  pkg-config  0.29.2-1

mk-configure suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 a492934bf07cd69d560d6ee6a16e280c 5700 devel optional 

Bug#977908: marked as done (mk-configure: Fails with 'Settings for gcc-10.2.1 is not available')

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 19:19:57 +
with message-id 
and subject line Bug#977908: fixed in mk-configure 0.35.really.0.33.0-1
has caused the Debian Bug report #977908,
regarding mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'
to be marked as done.

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

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


-- 
977908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mk-configure
Version: 0.35.0-1
Severity: serious
Justification: causes FTBFS of libmaa


It looks like mk-configure fails to recognize gcc-10.2.1 (which migrated
to testing almost a week ago), what causes my libmaa package to FTBFS, see:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libmaa.html

   dh "binary" --buildsystem=mkcmake
   dh_update_autotools_config -O--buildsystem=mkcmake
   dh_autoreconf -O--buildsystem=mkcmake
   dh_auto_configure -O--buildsystem=mkcmake
   dh_auto_build -O--buildsystem=mkcmake
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu
==
all ===> doc
==
all ===> maa
checking C compiler type... gcc 10.2.1
bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
*** Error code 1
dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu returned 
exit code 1
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Regards,
Robert

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


Versions of packages mk-configure depends on:
ii  bmake  20200710-5

Versions of packages mk-configure recommends:
ii  pkg-config  0.29.2-1

mk-configure suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mk-configure
Source-Version: 0.35.really.0.33.0-1
Done: Andrej Shadura 

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

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated mk-configure 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, 28 Dec 2020 20:05:56 +0100
Source: mk-configure
Architecture: source
Version: 0.35.really.0.33.0-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 977908 978271 978387
Changes:
 mk-configure (0.35.really.0.33.0-1) unstable; urgency=medium
 .
   * Revert to mk-configure 0.33.0 (Closes: #977908, #978271, #978387).
Checksums-Sha1:
 07edfdae539a40d37a5b020fd665db403b383f30 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 558286f7f92944aec79b68d70f6abd3d7fa29fde 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 5dc9ca8b56b8d86ff61f21c9065de852e5d5c33b 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Checksums-Sha256:
 fa3764111d1ddc1f43cc5d63092b71e4a5b819706fdcfc7e341249ecceddaa24 1936 
mk-configure_0.35.really.0.33.0-1.dsc
 d99264c9ea2b18ff000594d7d181d6613bf65804c009be19e3b326c63677f2d4 136380 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 eff06d50266154049ff5b8476e93931b9abcb03b545b81125e2b3321ad3efccc 5700 
mk-configure_0.35.really.0.33.0-1.debian.tar.xz
Files:
 fb905a2959747aed4c7fe550f7e311ba 1936 devel optional 
mk-configure_0.35.really.0.33.0-1.dsc
 f1484fe97bd93bd372d058940c67c6da 136380 devel optional 
mk-configure_0.35.really.0.33.0.orig.tar.xz
 a492934bf07cd69d560d6ee6a16e280c 5700 devel optional 

Bug#978097: marked as done (libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 2.4.1-2 ???))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 18:33:27 +
with message-id 
and subject line Bug#978097: fixed in cpu-features 0.6.0-3
has caused the Debian Bug report #978097,
regarding libcpu-features-dev: missing Breaks+Replaces: libvolk2-dev (<< 
2.4.1-2 ???)
to be marked as done.

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

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


-- 
978097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcpu-features-dev
Version: 0.6.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block -1 with 978096

Hi,

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

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

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

  Preparing to unpack .../libcpu-features-dev_0.6.0-1+b1_amd64.deb ...
  Unpacking libcpu-features-dev (0.6.0-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/cpu_features/cpu_features_cache_info.h', 
which is also in package libvolk2-dev:amd64 2.4.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libcpu-features-dev_0.6.0-1+b1_amd64.deb
 
src:volk seems to use an embedded copy of libcpu-features-dev and ships it
in libvolk2-dev. I've requested that to be dropped in #978096, but as long
as this has not happened the version libcpu-features-dev should use in the
to-be-added Breaks+Replaces is only a guess.


cheers,

Andreas


libvolk2-dev=2.4.1-1_libcpu-features-dev=0.6.0-1+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cpu-features
Source-Version: 0.6.0-3
Done: Shengjing Zhu 

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated cpu-features package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Dec 2020 02:11:14 +0800
Source: cpu-features
Architecture: source
Version: 0.6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Shengjing Zhu 
Changed-By: Shengjing Zhu 
Closes: 978097
Changes:
 cpu-features (0.6.0-3) unstable; urgency=medium
 .
   * Add Multi-Arch hint
   * Add Breaks and Replaces to libvolk2-dev (Closes: #978097)
   * Add powerpc to Architecture
   * Add x32 to Architecture
   * Expose internal headers.
 One internal header is used in ppc public header
Checksums-Sha1:
 af01daca990ce6a7217d8a6c500fc0c0f412d55d 1450 cpu-features_0.6.0-3.dsc
 6940c5202ab4c331c3ccf3427ee543f0f97a2f5c 3596 
cpu-features_0.6.0-3.debian.tar.xz
 ffdcdc33de10f73bb42b37063e25715ae591d8d5 5869 
cpu-features_0.6.0-3_amd64.buildinfo
Checksums-Sha256:
 514f5486fa4f8ca0eeaefdd510d2df0270788b15c801439d768f0886cf1d2aaf 1450 
cpu-features_0.6.0-3.dsc
 7e53ddf752558d24274296db65b2fc2aa1ae5012320b40a0ed14aa280aef26b5 3596 
cpu-features_0.6.0-3.debian.tar.xz
 099fe0bbc407d5fc22c5167d7a8505d1301f5be6de1588ebe419e45faf7915a0 5869 
cpu-features_0.6.0-3_amd64.buildinfo
Files:
 997710eadf4161c88333bfaee3ada662 1450 libdevel optional 
cpu-features_0.6.0-3.dsc
 78db0dc17d387550cf9738822e2c8f5f 3596 libdevel optional 
cpu-features_0.6.0-3.debian.tar.xz
 6e4fc7442b12deef42e0676c042724ac 5869 libdevel optional 
cpu-features_0.6.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX+ogSRAcemhzakBkZWJp
YW4ub3JnAAoJEMSFSjgY4LAWTqgA/1hQ31HVJjEMF6cmUsXuTzzmhziqjp/HzpV4
Ncr0MN6RAP4okE+bzTOs7oH/5w8DHzD/daDUxc6HYl+7aQqGy64HCA==
=+2Hu
-END PGP SIGNATURE End Message ---

Processed: forcibly merging 978356 977844

[Debian Bug Tracking System]

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

> forcemerge 978356 977844
Bug #978356 [src:libcxx-serial] libcxx-serial: FTBFS: dh_missing: error: 
missing files, aborting
Bug #977844 [src:libcxx-serial] src:libcxx-serial: libcxx-serial FTBFS with new 
catkin (patch attached)
Severity set to 'serious' from 'normal'
Added tag(s) bullseye and sid.
Merged 977844 978356
> thanks
Stopping processing here.

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

Bug#975832: marked as done (python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy scheme None)

[Debian Bug Tracking System]

Your message dated Tue, 29 Dec 2020 03:20:42 +0900
with message-id <9414a464016e60d09ec015e716bd0...@duckcorp.org>
and subject line Re: python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: 
plugin flit failed with: Not supported proxy scheme None
has caused the Debian Bug report #975832,
regarding python-aiosqlite: FTBFS: E: pybuild pybuild:353: build: plugin flit 
failed with: Not supported proxy scheme None
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.)


-- 
975832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aiosqlite
Version: 0.15.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_auto_build
> E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy 
> scheme None
> E: pybuild pybuild:353: build: plugin flit failed with: Not supported proxy 
> scheme None
> dh_auto_build: error: pybuild --build -i python{version} -p "3.8 3.9" 
> returned exit code 13
> make[1]: *** [debian/rules:18: override_dh_auto_build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/python-aiosqlite_0.15.0-2_unstable.log

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

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

Quack,

This is no longer failing.

Recently #975825 caused problems too but this is fixed.

I re-ran the build on Salsa to check and all is fine:
  https://salsa.debian.org/debian/aiosqlite/-/pipelines/204076

Regards.
\_o<

--
Marc Dequènes--- End Message ---

Processed: src:rust-num-traits: fails to migrate to testing for too long: Depends on non-migrating rust-libm

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.2.14-1
Bug #978572 [src:rust-num-traits] src:rust-num-traits: fails to migrate to 
testing for too long: Depends on non-migrating rust-libm
Marked as fixed in versions rust-num-traits/0.2.14-1.
Bug #978572 [src:rust-num-traits] src:rust-num-traits: fails to migrate to 
testing for too long: Depends on non-migrating rust-libm
Marked Bug as done

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

Bug#978572: src:rust-num-traits: fails to migrate to testing for too long: Depends on non-migrating rust-libm

[Paul Gevers]

Source: rust-num-traits
Version: 0.2.11-1+doctestfix
Severity: serious
Control: close -1 0.2.14-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:rust-num-traits in its current version in unstable has been trying
to migrate for 40 days [2], but earlier versions also didn't migrate.
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-num-traits




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:scummvm: fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.2.0+dfsg1-2
Bug #978570 [src:scummvm] src:scummvm: fails to migrate to testing for too 
long: FTBFS on armhf, mips64el and s390x
Marked as fixed in versions scummvm/2.2.0+dfsg1-2.
Bug #978570 [src:scummvm] src:scummvm: fails to migrate to testing for too 
long: FTBFS on armhf, mips64el and s390x
Marked Bug as done
> block -1 by 975492
Bug #978570 {Done: Paul Gevers } [src:scummvm] src:scummvm: 
fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x
978570 was not blocked by any bugs.
978570 was not blocking any bugs.
Added blocking bug(s) of 978570: 975492

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

Bug#978571: xserver-xorg-video-amdgpu: FTBFS on mips64el, mipsel

[Ivo De Decker]

package: src:xserver-xorg-video-amdgpu
version: 19.1.0-2
severity: serious
tags: ftbfs

Hi,

The latest upload of xserver-xorg-video-amdgpu to unstable fails on mips64el, 
mipsel:

https://buildd.debian.org/status/package.php?p=xserver-xorg-video-amdgpu

Cheers,

Ivo

Bug#978570: src:scummvm: fails to migrate to testing for too long: FTBFS on armhf, mips64el and s390x

[Paul Gevers]

Source: scummvm
Version: 2.1.2+dfsg1-1
Severity: serious
Control: close -1 2.2.0+dfsg1-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 975492

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:scummvm in
its current version in unstable has been trying to migrate for 35 days
[2], but the upload before also didn't migrate. 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=scummvm




OpenPGP_signature
Description: OpenPGP digital signature

Bug#978567: src:godot: fails to migrate to testing for too long: FTBFS on mips64el

[Paul Gevers]

Source: godot
Version: 3.2-stable-2
Severity: serious
Tags: sid bullseye ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:godot 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 tagged this bug to only affect sid and bullseye, so it doesn't
affect (old-)stable.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Bug#911587: marked as done (infnoise: busy-waits, using too much CPU)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 17:48:34 +
with message-id 
and subject line Bug#911587: fixed in infnoise 0.3.1+git20190812+dfsg-1
has caused the Debian Bug report #911587,
regarding infnoise: busy-waits, using too much CPU
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.)


-- 
911587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: infnoise
Version: 0.3.0+dfsg-1
Severity: serious

Dear Maintainer,

Version 0.3 of infnoise busy-waits; 0.2.6 didn’t, so this is a
regression.

I’m designating this as serious to prevent 0.3 from migrating to
testing.

Regards,

Stephen


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

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

Versions of packages infnoise depends on:
ii  libc6 2.24-11+deb9u3
ii  libftdi1  0.20-4
ii  libusb-0.1-4  2:0.1.12-30

infnoise recommends no packages.

infnoise suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: infnoise
Source-Version: 0.3.1+git20190812+dfsg-1
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated infnoise 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, 28 Dec 2020 18:30:58 +0100
Source: infnoise
Architecture: source
Version: 0.3.1+git20190812+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 911587 930876
Changes:
 infnoise (0.3.1+git20190812+dfsg-1) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Let dh_auto_build pass cross tools to make.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Stephen Kitt ]
   * New upstream snapshot. Closes: #930876.
   * Set LINUX when building to ensure the daemon waits for the entropy
 pool instead of busy-waiting. Closes: #911587.
   * Update lintian overrides.
   * Add missing Pre-Depends.
   * Switch to debhelper compatibility level 13.
   * Standards-Version 4.5.1, no further change required.
Checksums-Sha1:
 32f9b8a4506ad638849fee5906ce926945c0a3ea 1961 
infnoise_0.3.1+git20190812+dfsg-1.dsc
 6af9a742cb0908a27c1610ff369c60e2b6caaa2f 25218346 
infnoise_0.3.1+git20190812+dfsg.orig.tar.gz
 99a8df66d62addf5ea7b7d0996216dca20f03d93 6460 
infnoise_0.3.1+git20190812+dfsg-1.debian.tar.xz
 e27de41656321718663dfe18429ae4a23eb20c29 6088 
infnoise_0.3.1+git20190812+dfsg-1_source.buildinfo
Checksums-Sha256:
 58fd3275cd1fb5b44f92b5f6e2ea63aade961faef4e19ca995a9d1020ffd3714 1961 
infnoise_0.3.1+git20190812+dfsg-1.dsc
 04634f5cc389922c16f562b3b32f6b5050697063b0e78f19d7a65c350299f923 25218346 
infnoise_0.3.1+git20190812+dfsg.orig.tar.gz
 b8b34e1d0992468db9e3dbb5c70a4aa87395aa55c4743de34414a18be42f6578 6460 
infnoise_0.3.1+git20190812+dfsg-1.debian.tar.xz
 26f78aaf4554988fa10b70b6393006fa4454c2093283c20224fe01ee31188e3b 6088 
infnoise_0.3.1+git20190812+dfsg-1_source.buildinfo
Files:
 5a560cb60ad9f21c70fde2e588598c22 1961 utils optional 
infnoise_0.3.1+git20190812+dfsg-1.dsc
 8f4036bf57f61d09fd148bdb7eb45762 25218346 utils optional 
infnoise_0.3.1+git20190812+dfsg.orig.tar.gz
 06daac5d7497d44874051a9aed484e0c 6460 utils optional 
infnoise_0.3.1+git20190812+dfsg-1.debian.tar.xz
 833fe105f0c945197d538ad91c8f9bbd 6088 utils 

Processed: src:xmobar: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#978565: src:xmobar: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: xmobar
Version: 0.33-1
Severity: serious
Control: close -1 0.36-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 975472

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:xmobar 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=xmobar




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.18.2-1
Bug #978564 [src:gst-plugins-bad1.0] src:gst-plugins-bad1.0: fails to migrate 
to testing for too long: dependency is not migrating
Marked as fixed in versions gst-plugins-bad1.0/1.18.2-1.
Bug #978564 [src:gst-plugins-bad1.0] src:gst-plugins-bad1.0: fails to migrate 
to testing for too long: dependency is not migrating
Marked Bug as done
> block -1 by 976288
Bug #978564 {Done: Paul Gevers } [src:gst-plugins-bad1.0] 
src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is 
not migrating
978564 was not blocked by any bugs.
978564 was not blocking any bugs.
Added blocking bug(s) of 978564: 976288

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

Bug#978564: src:gst-plugins-bad1.0: fails to migrate to testing for too long: dependency is not migrating

[Paul Gevers]

Source: gst-plugins-bad1.0
Version: 1.18.0-2
Severity: serious
Control: close -1 1.18.2-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 976288

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:gst-plugins-bad1.0 in unstable has been trying to migrate for 61
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.

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.
In this case, I think it may be wise to upload to
testing-proposed-updates and ask for an unblock. Otherwise your two bug
fix releases may not make it to bullseye.

Paul

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




OpenPGP_signature
Description: OpenPGP digital signature

Processed: [bts-link] source package src:golang-github-xenolf-lego

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:golang-github-xenolf-lego
> # 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 #975789 (http://bugs.debian.org/975789)
> # Bug title: golang-github-xenolf-lego: FTBFS: 
> src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment 
> mismatch: 1 variable but d.client.Account.Login returns 2 values
> #  * https://github.com/go-acme/lego/pull/1176
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 975789 + fixed-upstream
Bug #975789 [src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS: 
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment 
mismatch: 1 variable but d.client.Account.Login returns 2 values
Added tag(s) fixed-upstream.
> usertags 975789 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:bambootracker
> # 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 #974580 (http://bugs.debian.org/974580)
> # Bug title: bambootracker FTBFS on 32bit
> #  * https://github.com/rerrahkr/BambooTracker/issues/263
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 974580 + fixed-upstream
Bug #974580 [src:bambootracker] bambootracker FTBFS on 32bit
Added tag(s) fixed-upstream.
> usertags 974580 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 974580 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#911587: infnoise: busy-waits, using too much CPU

[Stephen Kitt]

Hi Axel,

On Mon, 28 Dec 2020 09:29:04 +0100, Axel Beckert  wrote:
> Stephen Kitt wrote:
> > Dear Maintainer,  
> 
> You're writing to yourself as "Dear Maintainer"? :-)

I didn’t bother changing the reportbug template, and who knows the maintainer
might not always be me ;-).

> > Version 0.3 of infnoise busy-waits; 0.2.6 didn’t, so this is a
> > regression.  
> 
> Any news on this? I just dist-upgraded a box which has a Infinite
> Noise TRNG connected from Buster to Bullseye and noticed that infnoise
> is gone. That way I stumbled upon this bug report.

I have figured out what was wrong (cue brown paper bag for me), I’ll upload a
fix shortly.

> There seems a new upstream release (0.3.1) at
> https://github.com/13-37-org/infnoise/releases/tag/0.3.1 (but no
> changelog entry for it so far) and 57 more commits to master since
> then:
> 
> https://github.com/13-37-org/infnoise/compare/0.3.1...master
> 
> Not sure if any of these fix this issue.

0.3.1 was already in unstable, but the error came from incomplete build
flags...

> > I’m designating this as serious to prevent 0.3 from migrating to
> > testing.  
> 
> That's nice, but any chance to get infnoise back into testing?

Yup!

Regards,

Stephen


pgpqnVJI1cYEP.pgp
Description: OpenPGP digital signature

Bug#978411: marked as done (src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 17:04:20 +
with message-id 
and subject line Bug#978411: fixed in golang-gopkg-lxc-go-lxc.v2 
0.0+git20201012.d1943fb-2
has caused the Debian Bug report #978411,
regarding src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too 
long: maintainer built arch:all binary
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.)


-- 
978411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-lxc-go-lxc.v2
Version: 0.0+git20190625.f4822c6-1
Severity: serious
Control: close -1 0.0+git20201012.d1943fb-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:golang-gopkg-lxc-go-lxc.v2 in its current version in unstable has
been trying to migrate for 62 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.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=golang-gopkg-lxc-go-lxc.v2




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-gopkg-lxc-go-lxc.v2
Source-Version: 0.0+git20201012.d1943fb-2
Done: =?utf-8?q?Cl=C3=A9ment_Hermann?= 

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

Debian distribution maintenance software
pp.
Clément Hermann  (supplier of updated 
golang-gopkg-lxc-go-lxc.v2 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, 28 Dec 2020 16:36:20 CET
Source: golang-gopkg-lxc-go-lxc.v2
Binary: 
Architecture: source
Version: 0.0+git20201012.d1943fb-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Clément Hermann 
Description: 
Closes: 978411
Changes:
 golang-gopkg-lxc-go-lxc.v2 (0.0+git20201012.d1943fb-2) unstable; urgency=medium
 .
   * d/control:
 - Change section to golang
 - Declare compliance with Debian Policy 4.5.1 (no change)
 - Switch to @debian.org address in Uploaders
 - Rules-Requires-Root: no
   * d/gbp.conf: Specify compression type for consistency
   * source-only upload to allow migration to testing (Closes: #978411)
Checksums-Sha256: 
 a68b7f86fa5516780d5578131b00a10132462ece0fa78d060919ae013d812d4b 2452 
golang-gopkg-lxc-go-lxc.v2_0.0+git20201012.d1943fb-2.dsc
 8c76c90aefb50fd53f7986ea8f8be683a176406d60fc199ee79e4d7489d0764d 3948 
golang-gopkg-lxc-go-lxc.v2_0.0+git20201012.d1943fb-2.debian.tar.xz
 ef553b56ebb5e91300c572172db662b92f49b06e9a4b109b1149fcb22a664947 6731 

Bug#963371: marked as done (isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 17:04:32 +
with message-id 
and subject line Bug#963371: fixed in isoquery 3.2.4-1
has caused the Debian Bug report #963371,
regarding isoquery: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p /<>/debian/tmpdir/locale
> localedef -i de_DE -f UTF-8 /<>/debian/tmpdir/locale/de_DE.UTF-8
> LOCPATH=/<>/debian/tmpdir/locale LANG=de LC_ALL=de_DE.UTF-8 
> dh_auto_test
>   make -j4 check VERBOSE=1
> make[2]: Verzeichnis „/<>“ wird betreten
> Making check in po
> make[3]: Verzeichnis „/<>/po“ wird betreten
> make[3]: Für das Ziel „check“ ist nichts zu tun.
> make[3]: Verzeichnis „/<>/po“ wird verlassen
> Making check in src
> make[3]: Verzeichnis „/<>/src“ wird betreten
> make[3]: Für das Ziel „check“ ist nichts zu tun.
> make[3]: Verzeichnis „/<>/src“ wird verlassen
> Making check in tests
> make[3]: Verzeichnis „/<>/tests“ wird betreten
> make  check-am
> make[4]: Verzeichnis „/<>/tests“ wird betreten
> make  options integration\
>
> make[5]: Verzeichnis „/<>/tests“ wird betreten
> gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" 
> -DPACKAGE_VERSION=\"3.2.3\" -DPACKAGE_STRING=\"isoquery\ 3.2.3\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" 
> -DVERSION=\"3.2.3\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 
> -DGETTEXT_PACKAGE=\"isoquery\" -I.  -I../src -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o options.o 
> options.c
> gcc -DPACKAGE_NAME=\"isoquery\" -DPACKAGE_TARNAME=\"isoquery\" 
> -DPACKAGE_VERSION=\"3.2.3\" -DPACKAGE_STRING=\"isoquery\ 3.2.3\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"isoquery\" 
> -DVERSION=\"3.2.3\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 
> -DGETTEXT_PACKAGE=\"isoquery\" -I.  -DTESTDIR=\".\" -I../src 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/json-glib-1.0 -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> integration-integration.o `test -f 'integration.c' || echo './'`integration.c
> gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
> integration integration-integration.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 
> -lgobject-2.0 -lglib-2.0 ../src/options.o 
> gcc  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o 
> options options.o -lglib-2.0 -ljson-glib-1.0 -lgio-2.0 -lgobject-2.0 
> -lglib-2.0 ../src/options.o 
> make[5]: Verzeichnis „/<>/tests“ wird verlassen
> make  check-TESTS
> make[5]: Verzeichnis „/<>/tests“ wird betreten
> make[6]: Verzeichnis „/<>/tests“ wird betreten
> PASS: options 1 /options/standard_default
> PASS: options 2 /options/standard_provided
> PASS: options 3 /options/standard_deprecated_639
> PASS: options 4 /options/standard_deprecated_3166
> PASS: options 5 /options/standard_invalid
> PASS: options 6 /options/pathname_default
> PASS: options 7 /options/pathname_provided
> PASS: options 8 /options/pathname_provided_with_dir_separator
> PASS: options 9 /options/pathname_from_standard
> PASS: options 10 /options/name_default
> PASS: options 11 /options/name_name
> PASS: options 12 /options/name_official_name
> PASS: options 13 /options/name_common_name
> PASS: options 14 /options/null_separator
> PASS: options 15 /options/invalid_option
> PASS: integration 1 /integration/iso_639-2/all_localized
> PASS: integration 2 /integration/iso_639-2/all_null_separator
> PASS: 

Bug#978226: marked as done (perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6 sbuild-build-depends-main-dummy)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 17:04:46 +
with message-id 
and subject line Bug#978226: fixed in prove6 0.0.12-3
has caused the Debian Bug report #978226,
regarding perl6-zef: FTBFS: Errors while processing:  rakudo  raku-getopt-long 
raku-tap-harness  prove6  sbuild-build-depends-main-dummy
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.)


-- 
978226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perl6-zef
Version: 0.9.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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-compat (= 13), dh-perl6, build-essential, 
> fakeroot, prove6, raku-tap-harness
> Filtered Build-Depends: debhelper-compat (= 13), dh-perl6, build-essential, 
> fakeroot, prove6, raku-tap-harness
> 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 [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [400 B]
> Get:5 copy:/<>/apt_archive ./ Packages [475 B]
> Fetched 1832 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...
> The following additional packages will be installed:
>   autoconf automake autopoint autotools-dev bsdextrautils ca-certificates
>   debhelper dh-autoreconf dh-perl6 dh-strip-nondeterminism dwz file
>   fonts-glyphicons-halflings gettext gettext-base groff-base intltool-debian
>   libapt-pkg-perl libarchive-zip-perl libarray-unique-perl libcgi-pm-perl
>   libclass-accessor-perl libdebhelper-perl libdebian-source-perl libelf1
>   libencode-locale-perl liberror-perl libexporter-lite-perl
>   libexporter-tiny-perl libfile-listing-perl libfile-stripnondeterminism-perl
>   libgraph-perl libheap-perl libhtml-form-perl libhtml-parser-perl
>   libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-date-perl
>   libhttp-message-perl libhttp-negotiate-perl libhttp-server-simple-perl
>   libicu67 libio-html-perl libio-socket-ssl-perl libio-stringy-perl
>   libipc-system-simple-perl libjs-angularjs libjs-bootstrap
>   liblist-moreutils-perl liblist-moreutils-xs-perl liblwp-mediatypes-perl
>   liblwp-protocol-https-perl libmagic-mgc libmagic1 libnet-http-perl
>   libnet-ssleay-perl libparse-debcontrol-perl libpath-tiny-perl libpipeline1
>   libsigsegv2 libsub-install-perl libsub-name-perl libsub-override-perl
>   libtie-ixhash-perl libtimedate-perl libtommath1 libtool libtry-tiny-perl
>   libuchardet0 liburi-perl libuv1 libwww-mechanize-perl libwww-perl
>   libwww-robotrules-perl libxml2 m4 man-db moarvm netbase nqp nqp-data openssl
>   perl-openssl-defaults po-debconf prove6 raku-getopt-long raku-tap-harness
>   rakudo sensible-utils
> Suggested packages:
>   autoconf-archive gnu-standards autoconf-doc dh-make gettext-doc
>   libasprintf-dev libgettextpo-dev groff libdata-dump-perl
>   libcrypt-ssleay-perl libtool-doc gfortran | fortran95-compiler gcj-jdk
>   libauthen-ntlm-perl m4-doc apparmor less www-browser libmail-box-perl
>   valgrind
> Recommended packages:
>   curl | wget | lynx libcgi-fast-perl libarchive-cpio-perl libhtml-format-perl
>   libclone-perl libunicode-utf8-perl libltdl-dev libdata-dump-perl
>   libhttp-daemon-perl libmailtools-perl libmail-sendmail-perl
> The following NEW packages will be installed:
>   autoconf automake autopoint autotools-dev bsdextrautils ca-certificates
>   debhelper dh-autoreconf dh-perl6 dh-strip-nondeterminism dwz file
>   fonts-glyphicons-halflings gettext gettext-base groff-base intltool-debian
>   libapt-pkg-perl libarchive-zip-perl libarray-unique-perl libcgi-pm-perl
>   libclass-accessor-perl libdebhelper-perl libdebian-source-perl libelf1
>   libencode-locale-perl liberror-perl libexporter-lite-perl
>   libexporter-tiny-perl 

Bug#978365: [Pkg-fonts-devel] Bug#978365: fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace' -> 'master_ufo/instance_ufo/Inter-Thin.ufo': Compiling UFO failed

[James Godfrey-Kittle]

Here's a bunch more context on this failure:

https://github.com/rsms/inter/issues/184
https://github.com/googlefonts/fontmake/issues/581
https://github.com/rsms/inter/issues/200
https://github.com/rsms/inter/issues/210

I'm surprised the fonts-inter package is still using fontmake directly
instead of the Inter project's build tools, especially since per
https://github.com/rsms/inter/issues/200 it sounds like this could
yield incorrect output.

Bug#958105: marked as done (ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 16:48:36 +
with message-id 
and subject line Bug#958105: fixed in ferm 2.5.1-1
has caused the Debian Bug report #958105,
regarding ferm: v2.5 broke @ipfilter(), resulting in 
deferred=ARRAY(0x55b7a9219368) errors
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.)


-- 
958105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ferm
Version: 2.5-1.1
Severity: serious
Tags: upstream

Dear Maintainer,

Ferm got updated from v2.4 to v2.5, which brought a regression of @ipfilter()
function, when used, resulting in an error.

I believe the serious severity is warranted. The error makes it so that ferm
doesn't apply any rules, so if you rely on ferm to setup firewall rules, your
system would be unprotected. It might also break other software on the system
which rely on the rules to be present.

My particular issue is detailed in the upstream bug tracker
https://github.com/MaxKellermann/ferm/issues/71. It looks like it was already
fixed in master
https://github.com/MaxKellermann/ferm/commit/cea364a246f6988c6dc7f1603586f58c11b7dc28,
but the fix hasn't made it into any release yet.
--- End Message ---
--- Begin Message ---
Source: ferm
Source-Version: 2.5.1-1
Done: Alexander Wirt 

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

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

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated ferm 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, 28 Dec 2020 17:08:19 +0100
Source: ferm
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Closes: 955613 958105
Changes:
 ferm (2.5.1-1) unstable; urgency=medium
 .
   * New upstream version 2.5.1
   * Backport from master to resolve @resolve (Closes: #955613, #958105)
Checksums-Sha1:
 c6eb41c9effbfae5c22775b07721bd3131aa9566 2070 ferm_2.5.1-1.dsc
 763c2e4ff8fbc8136f58a8763db53ff2cedf4832 74860 ferm_2.5.1.orig.tar.xz
 e3e7c71b7ff106319f9d016ef7153508d6785582 833 ferm_2.5.1.orig.tar.xz.asc
 812efd4eaa68f1d28e8642a37f6c3927efa6755e 21188 ferm_2.5.1-1.debian.tar.xz
 ba10dc5152912cd09b082419f13d67266575c069 5702 ferm_2.5.1-1_amd64.buildinfo
Checksums-Sha256:
 f7b4e3c33fe9d5ecd0ed387847067ca8a5328143317741670f907ebfc55b5916 2070 
ferm_2.5.1-1.dsc
 4b2ebf0f7e0d8d839d4e6d21ffd2aa1936df919eae3227b257afeb41844e942b 74860 
ferm_2.5.1.orig.tar.xz
 ff12c56563d2959aec96f0f99b8864b2dca27ba29cdf368d033e1182e5c1857f 833 
ferm_2.5.1.orig.tar.xz.asc
 7401f5862e3ac330204c797b902edae2b9a0fe89ab7e4ed831b260df5b59555c 21188 
ferm_2.5.1-1.debian.tar.xz
 a9d7a538bd328cdf0731e0213afe4bee395fc7efd42a2e54dc34273b573f2115 5702 
ferm_2.5.1-1_amd64.buildinfo
Files:
 26c7f55c645dcff8795fa5e0d2c0e6a4 2070 net optional ferm_2.5.1-1.dsc
 6d14d9e5e672885bc6f2fceafbf2942f 74860 net optional ferm_2.5.1.orig.tar.xz
 39d942720c5692f45fe75e36e45817e0 833 net optional ferm_2.5.1.orig.tar.xz.asc
 8d432e528321e69b92a07c518c8227d6 21188 net optional ferm_2.5.1-1.debian.tar.xz
 dd617e10eb026d26416fa35476103efa 5702 net optional ferm_2.5.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbjlmweHRXblz0FtJHkX4yp3iOxYFAl/qCFQACgkQHkX4yp3i
Oxbtsg//YL3TLExiOwP7Vp2/wcKlEjSJQ4p/ee7ko0kw1ZK2yy+KzviverAFDbuS
h+0TxiJ0Ex1XOhW6moJP1UEs8SuLAqWN6rnqP02DSolVIcXZN5HP4xJliztjOdTC
+N0h1Nz7XUsl4XIV/pYWCBLnk5MAMu0/v0gCK2KPSTCGsJ0zywNrPXiABf8h5j8U
gsOv6jcwdQJGineI7x1Q2ikmmZd68UbBGuBMhOVRS/vJHTFWfnE+z2z6w7m1KjTx
6vGQfmXF/hKNIoXVkl5bCj/1hViMX3xBUywk2gJ75eiy6/nbIpfpceddO8uHIG3+
X3HmggMb0wdJTHLdQqQqwPaK01tbGPeHnvybD2s8s2rl2LKHJecwTAPcdT64WNag
Qc2bnHhS5eaJo81wKhDOuVEUdN16FRCS7/FAzGR/zqU0FCzNOCB5wYbpfIIv2eoT
ajZDXjmQjaLpqqD6N8ENEUx+B8Lbu7XbvWTpu63SZ4LgzY+kKcuA3MqfC0Hdy3e/
CZFOVbfYVJ79RfgQkXZ38YQLxywA4SDKxIeB+vpAAjvwi9xg0IMeHW71134EWJWU
xYgB64OelXnyNpRmzKtdCwD0JU+M/BvFHNmwYj1dBctySyagkkR+w/NumQ0jB3Ys
T1zddeMrwmo9+1ZrFq3pbb+3OhOiNB+acQ9jDGWtBnQL45130Rk=
=S5u2
-END PGP SIGNATURE End Message ---

Processed: Reopening as the bug is still not fixed

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #975943 {Done: =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= 
} [raspi-firmware] raspi-firmware: arm_64bit is missing 
and linux-image-arm64 unbootable
'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 raspi-firmware/1.20201022-2.

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

Bug#975943: Reopening as the bug is still not fixed

[Diederik de Haas]

Control: reopen -1 

Turns out that DPKG_MAINTSCRIPT_ARCH can also have the value 'all' and then it 
still does the wrong thing.
# aptitude reinstall udev
...
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-trunk-arm64
latest_kernel: '/boot/vmlinuz-5.10.0-trunk-arm64'
latest_initrd: '/boot/initrd.img-5.10.0-trunk-arm64'
DPKG_MAINTSCRIPT_ARCH: 'all'
arch: 'all'
...
# head -n5 /boot/firmware/config.txt 
enable_uart=1
upstream_kernel=1

kernel=vmlinuz-5.10.0-trunk-arm64
# For details on the initramfs directive, see


Just submitted a merge request to only use the direct approach:
https://salsa.debian.org/debian/raspi-firmware/-/merge_requests/20

Cheers,
  Diederik

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

Processed: reassign 978226 to prove6, affects 978226

[Debian Bug Tracking System]

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

> reassign 978226 prove6
Bug #978226 [src:perl6-zef] perl6-zef: FTBFS: Errors while processing:  rakudo  
raku-getopt-long raku-tap-harness  prove6  sbuild-build-depends-main-dummy
Bug reassigned from package 'src:perl6-zef' to 'prove6'.
No longer marked as found in versions perl6-zef/0.9.1-3.
Ignoring request to alter fixed versions of bug #978226 to the same values 
previously set
> affects 978226 perl6-zef
Bug #978226 [prove6] perl6-zef: FTBFS: Errors while processing:  rakudo  
raku-getopt-long raku-tap-harness  prove6  sbuild-build-depends-main-dummy
Added indication that 978226 affects perl6-zef
> thanks
Stopping processing here.

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

Bug#978226: perl6-zef: FTBFS: Errors while processing: rakudo raku-getopt-long raku-tap-harness prove6 sbuild-build-depends-main-dummy

[Dominique Dumont]

On Saturday, 26 December 2020 22:40:58 CET Lucas Nussbaum wrote:
> > rakudo-helper.pl: Reinstalling all perl6 modules ...
> > (1/3) reinstall: raku-tap-harness
> > (2/3) reinstall: prove6
> > ===SORRY!=== Error while compiling
> > //vendor#sources/B4401FC2C8E71132AE0D3CE2C47A7D2FBB0D50F1 (App::Prove6)
> > Could not find Getopt::Long in:
> > CompUnit::Repository::Staging#name(vendor)#/tmp/qcmENjAngJ/build

prove6's /usr/share/perl6/debian-sources/prove6/prove6.p6deps file is empty. So 
rakudo does not build raku-getopt-long before prove6.

This is due to a bug in dh_perl6 which was fixed in version 0.4. I'll re-upload 
prove6 with a versioned dependency on dh_perl6 to fix this bug.

All the best

Bug#978348: marked as done (ipp-usb: FTBFS: src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 16:20:50 +
with message-id 
and subject line Bug#978348: fixed in ipp-usb 0.9.15-1
has caused the Debian Bug report #978348,
regarding ipp-usb: FTBFS: 
src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use 
int32(err) (type int32) as type _Ctype_int in argument to _Cfunc_libusb_strerror
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.)


-- 
978348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipp-usb
Version: 0.9.14-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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 '/<>'
> rm -f *.8 ipp-usb
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building ipp-usb using existing 
> ./ipp-usb_0.9.14.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: ignoring deletion of file ipp-usb.8, use 
> --include-removal to override
> dpkg-source: info: building ipp-usb in ipp-usb_0.9.14-2.debian.tar.xz
> dpkg-source: info: building ipp-usb in ipp-usb_0.9.14-2.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 
> github.com/OpenPrinting/ipp-usb
> internal/unsafeheader
> runtime/internal/sys
> runtime/internal/atomic
> internal/cpu
> internal/race
> runtime/internal/math
> sync/atomic
> unicode
> unicode/utf8
> internal/bytealg
> math/bits
> internal/testlog
> encoding
> math
> internal/nettrace
> container/list
> runtime/cgo
> runtime
> crypto/internal/subtle
> crypto/subtle
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> internal/reflectlite
> sync
> internal/singleflight
> math/rand
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> vendor/golang.org/x/net/dns/dnsmessage
> bytes
> strings
> reflect
> hash
> bufio
> hash/crc32
> internal/syscall/unix
> time
> internal/syscall/execenv
> crypto
> crypto/internal/randutil
> crypto/hmac
> crypto/rc4
> vendor/golang.org/x/crypto/hkdf
> vendor/golang.org/x/text/transform
> path
> context
> internal/poll
> os
> encoding/binary
> internal/fmtsort
> crypto/sha1
> crypto/sha512
> crypto/cipher
> fmt
> path/filepath
> net
> crypto/aes
> crypto/des
> io/ioutil
> crypto/ed25519/internal/edwards25519
> compress/flate
> encoding/xml
> github.com/OpenPrinting/goipp
> compress/gzip
> log
> math/big
> crypto/md5
> crypto/sha256
> encoding/hex
> encoding/base64
> net/url
> encoding/pem
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/poly1305
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/crypto/chacha20poly1305
> vendor/golang.org/x/text/unicode/bidi
> crypto/rand
> crypto/elliptic
> encoding/asn1
> crypto/ed25519
> crypto/rsa
> crypto/dsa
> vendor/golang.org/x/crypto/cryptobyte
> crypto/x509/pkix
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/text/unicode/norm
> vendor/golang.org/x/net/http2/hpack
> crypto/ecdsa
> mime
> mime/quotedprintable
> net/http/internal
> os/signal
> runtime/debug
> vendor/golang.org/x/net/idna
> net/textproto
> crypto/x509
> vendor/golang.org/x/net/http/httpproxy
> vendor/golang.org/x/net/http/httpguts
> mime/multipart
> crypto/tls
> net/http/httptrace
> net/http
> github.com/OpenPrinting/ipp-usb
> # github.com/OpenPrinting/ipp-usb
> src/github.com/OpenPrinting/ipp-usb/usbio_libusb.go:64:43: cannot use 
> int32(err) (type int32) as type _Ctype_int in argument to 
> _Cfunc_libusb_strerror
> dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
> github.com/OpenPrinting/ipp-usb returned exit code 2
> make: *** [debian/rules:6: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/ipp-usb_0.9.14-2_unstable.log

A list of current common problems and possible solutions is available at

Bug#978351: requests: FTBFS: AttributeError: 'LookupDict' object has no attribute '__name__'

[Daniele Tricoli]

Hello Lucas,
many thanks for the report!

On Sat, 26 Dec 2020 23:08:21 +0100 Lucas Nussbaum  wrote:
> Source: requests
> Version: 2.25.0+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201226 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 '/<>'
> > PYTHONPATH=. python3 -m sphinx -D html_last_updated_fmt="December 08, 2020" 
> > -N -bhtml docs/ \
> > debian/python-requests-doc/usr/share/doc/python-requests-doc/html/
> > Running Sphinx v3.4.1
> > making output directory... done
> > loading intersphinx inventory from https://docs.python.org/3/objects.inv...
> > loading intersphinx inventory from 
> > https://urllib3.readthedocs.io/en/latest/objects.inv...
> > building [mo]: targets for 0 po files that are out of date
> > building [html]: targets for 15 source files that are out of date
> > updating environment: [new config] 15 added, 0 changed, 0 removed
> > reading sources... [  6%] api
> > 
> > Exception occurred:
> >   File "/usr/lib/python3/dist-packages/sphinx/util/typing.py", line 160, in 
> > _restify_py37
> > return ':obj:`%s.%s`' % (cls.__module__, cls.__name__)
> > AttributeError: 'LookupDict' object has no attribute '__name__'
> > The full traceback has been saved in /tmp/sphinx-err-itgtnj9a.log, if you 
> > want to report the issue to the developers.
> > Please also report this if it was a user error, so that a better error 
> > message can be provided next time.
> > A bug report can be filed in the tracker at 
> > . Thanks!
> > make[1]: *** [debian/rules:21: override_dh_sphinxdoc] Error 2

I can reproduce it using python3-sphinx 3.4.1, I'm still investigating since
from sphinx's CHANGELOG the only incompatible change[¹] upgrading from sphinx
3.3.1 (using it building the documentation is fine) seems to not be related to
this.

Cheers,

[¹] https://github.com/sphinx-doc/sphinx/issues/8105

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature

Bug#978560: mediastreamer2: dropped pkgconfig file breaks kopete

[Gianfranco Costamagna]

Source: mediastreamer2
Version: 1:4.4.21-1
Severity: serious
tags: patch

Hello, kopete does use pkgconfig to find the mediastreamer2, and the new 
version with the cmake switch dropped the pkgconfig
installation.

I did craft a patch to install the pkgconfig file in cmake builds too (as it is 
done with autoconf).

It might be not the best patch to fix the issue, but it should work (the 
variables are called differently in cmake/autotools, so I had to set includedir 
manually in cmake before configuring the .pc.in file).

Please have a look and apply / forward upstream if you like it.

G.

Description: Add pkgconfig file to help kopete find the library
Author: Gianfranco Costamagna 
Forwarded: no
Last-Update: 2020-12-28

Index: mediastreamer2-4.4.21/CMakeLists.txt
===
--- mediastreamer2-4.4.21.orig/CMakeLists.txt
+++ mediastreamer2-4.4.21/CMakeLists.txt
@@ -666,8 +666,12 @@
set(PACKAGE_DATA_DIR "${CMAKE_INSTALL_DATADIR}")
 endif()
 
+set(libdir ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_LIBDIR})
+set(includedir ${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_INCLUDEDIR})
 configure_file(${CMAKE_CURRENT_SOURCE_DIR}/mediastreamer-config.h.cmake 
${CMAKE_CURRENT_BINARY_DIR}/mediastreamer-config.h)
 set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/mediastreamer-config.h 
PROPERTIES GENERATED ON)
+configure_file(${CMAKE_CURRENT_SOURCE_DIR}/mediastreamer.pc.in 
${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc)
+set_source_files_properties(${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc 
PROPERTIES GENERATED ON)
 add_definitions("-DHAVE_CONFIG_H")
 
 if(ENABLE_DOC)
@@ -699,6 +703,11 @@
NO_SET_AND_CHECK_MACRO
 )
 
+install(FILES
+   "${CMAKE_CURRENT_BINARY_DIR}/mediastreamer.pc"
+   DESTINATION ${CMAKE_INSTALL_LIBDIR}/pkgconfig
+)
+
 install(EXPORT ${EXPORT_TARGETS_NAME}Targets
FILE Mediastreamer2Targets.cmake
DESTINATION ${CONFIG_PACKAGE_LOCATION}

Bug#895037: Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

[Ivo De Decker]

Hi,

On Thu, Dec 10, 2020 at 03:08:00PM +, Simon McVittie wrote:
> On Thu, 10 Dec 2020 at 14:37:21 +, Mike Gabriel wrote:
> > On  Do 10 Dez 2020 15:35:19 CET, Paul Gevers wrote:
> > > We're running into the freeze of bullseye soon. The first bug I checked
> > > is still only severity important, so is it realistic to get this done
> > > before bullseye release? [...]
> > > If yes, action is needed, this isn't going to happen
> > > magically. At the least raising the blocking bugs to severity serious.
> > 
> > I'd suggest to raise severity of the still open bugs and get libappindicator
> > kicked out before the bullseye release.
> > 
> > The fixes are easy to be done. Maintainers can ping me if they have 
> > problems.
> 
> Raising the blocking bugs to RC as requested.

I added some hints to finish this, and now libindicator and libappindicator
are no longer in testing.

Thanks!

Ivo

Bug#970808: python3-venv is gone

[Aivar Annamaa]

Dear Matthias,

Can you please explain the problem you reported on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970808 ?

python3-venv seems to be present in buster, bullseye and sid.

Best regards,
Aivar

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Vincent Lefevre]

On 2020-12-28 16:09:13 +0100, Vincent Lefevre wrote:
> After the upgrade, I now get in my logs:
> 
> Dec 28 16:00:01 zira CRON[2661963]: PAM unable to dlopen(pam_unix.so): 
> /lib/security/pam_unix.so: cannot open shared object file: No such file or 
> directory
> Dec 28 16:00:01 zira CRON[2661963]: PAM adding faulty module: pam_unix.so
> Dec 28 16:00:01 zira cron[2661963]: Authentication failure
> Dec 28 16:00:01 zira CRON[2661963]: Authentication failure

It seems that a "service cron restart" solved the issue.
Perhaps a bug in cron, which cached the old location?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#973848: hardware acceleration

[Felix C. Stegerman]

Hi!

I can confirm that adding

  --use-gl=desktop

to

  /etc/chromium.d/default-flags

makes hardware acceleration work (again) with chromium
87.0.4280.88-0.3 on unstable (on two systems with integrated intel
graphics), according to chrome://gpu.

NB: to get accelerated video decoding I had to also add

  --enable-accelerated-video-decode

(but this is not a regression AFAIK, since it was not available at all
-- at least not by default or using that option -- before).

- Felix

Bug#978555: libpam-modules: breaks cron: PAM unable to dlopen(pam_unix.so): /lib/security/pam_unix.so: cannot open shared object file

[Vincent Lefevre]

Package: libpam-modules
Version: 1.4.0-1
Severity: grave
Justification: renders package unusable

After the upgrade, I now get in my logs:

Dec 28 16:00:01 zira CRON[2661963]: PAM unable to dlopen(pam_unix.so): 
/lib/security/pam_unix.so: cannot open shared object file: No such file or 
directory
Dec 28 16:00:01 zira CRON[2661963]: PAM adding faulty module: pam_unix.so
Dec 28 16:00:01 zira cron[2661963]: Authentication failure
Dec 28 16:00:01 zira CRON[2661963]: Authentication failure

Indeed, the new file location is

  /lib/x86_64-linux-gnu/security/pam_unix.so

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

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

Versions of packages libpam-modules depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libaudit1  1:3.0-1
ii  libc6  2.31-5
ii  libcrypt1  1:4.4.17-1
ii  libdb5.3   5.3.28+dfsg1-0.6
ii  libnsl21.3.0-2
ii  libpam-modules-bin 1.4.0-1
ii  libpam0g   1.4.0-1
ii  libselinux13.1-2+b2
ii  libtirpc3  1.2.6-3

libpam-modules recommends no packages.

libpam-modules suggests no packages.

-- debconf information:
  libpam-modules/disable-screensaver:

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#977824: marked as done (CI fails with PHPUnit 9)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 14:39:20 +
with message-id 
and subject line Bug#977824: fixed in php-imagick 3.4.4-4.2
has caused the Debian Bug report #977824,
regarding CI fails with PHPUnit 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.)


-- 
977824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-imagick
Version: 3.4.4-4.1
Severity: serious
Tags: upstream patch
X-Debbugs-Cc: pkg-php-p...@lists.alioth.debian.org

Hi,

With recent phpunit (>= 9) as now available in unstable, the autopkgtest
of php-imagick fails because of a void --EXPECTF-- stanza. The attached
naive patch workarounds this issue.

Regards

David
From: =?utf-8?q?David_Pr=C3=A9vot?= 
Date: Mon, 21 Dec 2020 09:37:41 -0400
Subject: Void expectation is not allowed with PHPUnit 9

---
 imagick-3.4.4/tests/bug_72226.phpt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/imagick-3.4.4/tests/bug_72226.phpt b/imagick-3.4.4/tests/bug_72226.phpt
index 6ad5631..6724b87 100644
--- a/imagick-3.4.4/tests/bug_72226.phpt
+++ b/imagick-3.4.4/tests/bug_72226.phpt
@@ -19,4 +19,5 @@ if (class_exists('ImagickKernelException', false) == true) {
 }
 
 ?>
---EXPECTF--
+--EXPECTREGEX--
+^$


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-imagick
Source-Version: 3.4.4-4.2
Done: =?utf-8?q?David_Pr=C3=A9vot?= 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-imagick 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, 28 Dec 2020 09:09:48 -0400
Source: php-imagick
Architecture: source
Version: 3.4.4-4.2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: David Prévot 
Closes: 977824
Changes:
 php-imagick (3.4.4-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adapt to recent version of PHPUnit (9) (Closes: #977824)
Checksums-Sha1:
 e05b7cf0be7180b23a408283017156579ac85353 1826 php-imagick_3.4.4-4.2.dsc
 72a460bc664f63ae6756758fde305b55ca41489a 13736 
php-imagick_3.4.4-4.2.debian.tar.xz
 dcc8b6174f13a422ace79fdb09195c3b6236da86 11423 
php-imagick_3.4.4-4.2_amd64.buildinfo
Checksums-Sha256:
 c78aabe5c6d5499bdd6b3ef0a513f44b448f187be4b6a26522d32cfb21882204 1826 
php-imagick_3.4.4-4.2.dsc
 57a69749d722516ac1c23c3722e66ac9454a54f1204b673e10cbafa503bf0f53 13736 
php-imagick_3.4.4-4.2.debian.tar.xz
 a258f025276e1966e543d9e761878246012357a5a5ca4c246bc02bad20bc056c 11423 
php-imagick_3.4.4-4.2_amd64.buildinfo
Files:
 37b3d63c056e320e56e4c8bd153326bc 1826 php optional php-imagick_3.4.4-4.2.dsc
 efd78519cd76fb3526caad9a08f8bbf9 13736 php optional 
php-imagick_3.4.4-4.2.debian.tar.xz
 8a25adce49086df8c54b40ea079ab5b9 11423 php optional 
php-imagick_3.4.4-4.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAl/p3JwSHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08v9MH/0S4y6V9nBOQABU6F12jF1/pPJmnEZaS
IeN35wxKf3XZL/e1OpxEEz5LAJKq8mdbkbHJga9SyxWsVUHHwAvoAzLFnyen3Sq/
ikivDKjdOt7DI2q+Kze46Yq/ltNxi7qfZ6SeQ8ahUTxgpZGRdv9rMzOO8aWrfXaF
5rU+QnqwchwA947lee0uH7gwHG6j6hdBnHxl6N8df95sDgC8hL0MlWhkFIjO8dRG
cA6Krz5C8drGgWYTw3A8mauA7vdTMub6i5Sufq5lyz5cL4CNaJqZNwHPS48AfQOZ
fZc1d8qtBxHCjeLuAdSRBor50Xqj98Nvu6uiQeyrSExZdDW9PAdcKyk=
=iX8O
-END PGP SIGNATURE End Message ---

Bug#933948: marked as done (courier-mta randomly stops, cannot restart or start services, it just appears started, but it exists)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 14:34:01 +
with message-id 
and subject line Bug#933948: fixed in courier 1.0.14-1
has caused the Debian Bug report #933948,
regarding courier-mta randomly stops, cannot restart or start services, it just 
appears started, but it exists
to be marked as done.

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

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


-- 
933948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-mta
Version: 1.0.6-1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

   * What led up to the situation?

   I have made dist-upgrade from 9 to Debian 10
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   Just upgraded the system. Courier MTA apparently randomly stops and cannot 
be restarted.
   
This includes courier-imap-ssl

If I use web administrationa and click SAVE on IMAP or incoming ESMTP, and 
install new configuration, services start working.

If I just use service courier-imap-ssl start this does not work, even if 
service is enabled.

Example for courier-imap-ssl

I have restarted from web administration, so this works:

Executing /usr/sbin/imapd-ssl stop ; . /etc/courier/imapd-ssl ; test 
"$IMAPDSSLSTART" != YES || /usr/sbin/imapd-ssl start...
Executing /usr/sbin/imapd stop ; . /etc/courier/imapd ; test "$IMAPDSTART" != 
YES || /usr/sbin/imapd start...


root@stw1:/tmp# service courier-imap-ssl status
● courier-imap-ssl.service - LSB: Courier IMAP server (TLS)
   Loaded: loaded (/etc/init.d/courier-imap-ssl; generated)
   Active: active (exited) since Sun 2019-08-04 11:28:14 MST; 17h ago
 Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 2379)
   Memory: 0B
   CGroup: /system.slice/courier-imap-ssl.service

Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.
root@stw1:/tmp# lsof -i :993
COMMAND PIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
couriertc 31390root3u  IPv6 332900  0t0  TCP *:imaps (LISTEN)


Now if I do following:


root@stw1:/tmp# service courier-imap-ssl stop
root@stw1:/tmp# service courier-imap-ssl start
root@stw1:/tmp# lsof -i :993
root@stw1:/tmp#

This does not work.

root@stw1:/tmp# service courier-imap-ssl status
● courier-imap-ssl.service - LSB: Courier IMAP server (TLS)
   Loaded: loaded (/etc/init.d/courier-imap-ssl; generated)
   Active: active (exited) since Mon 2019-08-05 05:28:47 MST; 16s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 31976 ExecStart=/etc/init.d/courier-imap-ssl start (code=exited, 
status=0/SUCCESS)

Aug 05 05:28:47 stw1.rcdrun.com systemd[1]: Starting LSB: Courier IMAP serve…...
Aug 05 05:28:47 stw1.rcdrun.com systemd[1]: Started LSB: Courier IMAP server…S).
Hint: Some lines were ellipsized, use -l to show in full.


So if I do simple:

/usr/sbin/imapd-ssl start

This works.

It broke my email system and I need to install third party supervision to make 
sure that services are running.


-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (90, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages courier-mta depends on:
ii  courier-authlib0.69.0-2
ii  courier-base   1.0.6-1
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-10
ii  libcourier-unicode42.1-3
ii  libgcc11:8.3.0-6
ii  libgdbm6   1.18.1-4
ii  libidn11   1.33-2.2
ii  libnet-cidr-perl   0.19-1
ii  libperl5.285.28.1-6
ii  libstdc++6 8.3.0-6
ii  sysvinit-utils 2.93-8

courier-mta recommends no packages.

Versions of packages courier-mta suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20180807cvs-1
pn  courier-doc  
pn  courier-filter-perl  
pn  couriergrey  
ii  emacs-nox [mail-reader]  1:26.1+1-3.2
ii  mailutils [mail-reader]  1:3.5-3
ii  mutt [mail-reader]   1.10.1-2.1

-- Configuration Files:
/etc/courier/aliases/system changed:
root: postmaster
mailer-daemon: postmaster
MAILER-DAEMON: postmaster
uucp: postmaster
www-data: postmaster
postmaster: admin

/etc/courier/courierd changed:
prefix="/usr"
exec_prefix="/usr"
. /etc/environment
PATH=/usr/bin:/bin:/usr/bin:/usr/local/bin
SHELL=/bin/sh
DSNTOAUTHADDR=0
DYNAMICDELIVERIES=1
DEFAULTDELIVERY="|| 

Bug#978411: src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary

[Clément Hermann]

Hi Paul,

On 27/12/2020 07:12, Paul Gevers wrote:
> Source: golang-gopkg-lxc-go-lxc.v2
> Version: 0.0+git20190625.f4822c6-1
> Severity: serious
> Control: close -1 0.0+git20201012.d1943fb-1
> Tags: sid bullseye pending
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
> 
> Dear maintainer(s),
> 
> As recently announced [1], the Release Team now considers packages that
> are out-of-sync between testing and unstable for more than 60 days as
> having a Release Critical bug in testing. Your package
> src:golang-gopkg-lxc-go-lxc.v2 in its current version in unstable has
> been trying to migrate for 62 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.
> 
> Your package is only blocked because the arch:all binary package(s)
> aren't built on a buildd. Unfortunately the Debian infrastructure
> doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
> shortly do a no-changes source-only upload to DELAYED/15, closing this
> bug. Please let me know if I should delay or cancel that upload.


Thanks!

I'll make an upload later today with some small fixes, so you can cancel it.

Cheers,

-- 
nodens

Bug#971040: Fix available

[Bruno Kleinert]

Hi,

on https://extensions.gnome.org/extension/690/easyscreencast/ I stumled
over user's 'johncorso' comment pointing to a fix:

> Working on Debian bullseye/sid with GNOME 3.38.2.
> Thanks to Ian2020 for all the work.
> Pull: https://github.com/EasyScreenCast/EasyScreenCast/pull/276
> Fork: https://github.com/Ian2020/EasyScreenCast

Cheers,
Bruno



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

Bug#977824: php-imagick: diff for NMU version 3.4.4-4.2

[David Prévot]

Hi Ondřej,

Le Mon, Dec 28, 2020 at 02:55:26PM +0100, Ondřej Surý a écrit :
> David, feel free to upload directly.

Thanks for the explicit and quick acknowledgment, rescheduled to 0-day.

Regards

David


signature.asc
Description: PGP signature

Bug#973848: security update of chromium in Debian stable?

[Tomas Pospisek]

On Mon, 28 Dec 2020, Jan Luca Naumann wrote:


I have got a successful buster build half an hour ago :)


Yay!

As soon as [1] is fixed or at least worked around (so we do not release 
a version with a regression), I think we could do the update.


Do you have your build available anywhere? Because maybe I or passers by 
could then install your build and help testing whatever workaround comes 
out of [1]?



I will contact the security team now to discuss the update.


+1 !!!

Thanks a lot!
*t


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

Am 28.12.20 um 12:37 schrieb Tomas Pospisek:

Hi Jan Luca,

are you working on or respectively are you planing to do the stable build?

(I am not sure if I would be able to get access to a powerful enough
 machine to do the build and get up to speed within reasonable time on how
 to build chromium and on how to do it efficiently so that I do not have
 to wait 24 hours for the build to proceed and fail again before I
 apply the next fix...?)

Greetings!
*t

Bug#977000: marked as done (python3-apt: dak crashes after security update)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 13:53:34 +
with message-id 
and subject line Bug#977000: fixed in python-apt 1.8.4.3
has caused the Debian Bug report #977000,
regarding python3-apt: dak crashes after security update
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.)


-- 
977000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-apt
Version: 1.8.4.2
Severity: grave
Tags: security
Justification: renders package unusable

dak crashes with a segmentation fault in python3-apt when processing
uploads or processing the NEW queue on ftp-master; and also on my
playground server (used to generate the backtrace).

$ gdb --batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' \
-args /usr/bin/python3 ~dak/dak/dak/dak.py examine-package \
python3-apt_1.8.4.2_amd64.deb &> dak-segfault.txt

produced the attached backtrace.

The problematic line seems to be:

+---
| return apt_inst.DebFile(fh).control.extractdata("control")
+---[ 
https://salsa.debian.org/ftp-team/dak/-/blob/891420d6c0c46472f25585ac05760dabc84e74ad/daklib/utils.py#L939
 ]

and indeed

$ gdb --args python3 -c 'import apt_inst; 
apt_inst.DebFile(open("python3-apt_1.8.4.2_amd64.deb")).control.extractdata("control")'

also reproduces the segmentation fault.

Ansgar

-- System Information:
Debian Release: 10.7
Architecture: amd64 (x86_64)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages python3-apt depends on:
ii  libapt-inst2.0 1.8.2.2
ii  libapt-pkg5.0  1.8.2.2
ii  libc6  2.28-10
ii  libgcc11:8.3.0-6
ii  libstdc++6 8.3.0-6
ii  python-apt-common  1.8.4.2
ii  python33.7.3-1

Versions of packages python3-apt recommends:
pn  iso-codes
pn  lsb-release  

Versions of packages python3-apt suggests:
ii  apt  1.8.2.2
pn  python-apt-doc   
ii  python3-apt-dbg  1.8.4.2

-- no debconf information
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 1948]

Program received signal SIGSEGV, Segmentation fault.
0x768b90e6 in ararchive_new (type=0x768c00a0 , 
args=, kwds=) at /usr/include/c++/8/new:169
169 { return __p; }
#0  0x768b90e6 in ararchive_new (type=0x768c00a0 , 
args=, kwds=) at /usr/include/c++/8/new:169
#1  0x768b973d in debfile_new (type=type@entry=0x768c00a0 
, args=args@entry=(<_io.TextIOWrapper at remote 
0x75a461f8>,), kwds=kwds@entry=0x0) at python/arfile.cc:613
#2  0x005ce067 in type_call (kwds=0x0, args=(<_io.TextIOWrapper at 
remote 0x75a461f8>,), type=0x768c00a0 ) at 
../Objects/typeobject.c:929
#3  _PyObject_FastCallKeywords (callable=, 
stack=0x75a89a10, nargs=, kwnames=) at 
../Objects/call.c:199
#4  0x0053ed81 in call_function (pp_stack=0x7fffd7b0, 
oparg=, kwnames=) at ../Python/ceval.c:4619
#5  0x0054653a in _PyEval_EvalFrameDefault (f=, 
throwflag=) at ../Python/ceval.c:3093
#6  0x005cd68c in PyEval_EvalFrameEx (throwflag=0, f=Frame 
0x75a89890, for file /mnt/data/srv/dak/dak/daklib/utils.py, line 939, in 
deb_extract_control (fh=<_io.TextIOWrapper at remote 0x75a461f8>)) at 
../Python/ceval.c:547
#7  function_code_fastcall (globals=, nargs=, 
args=, co=) at ../Objects/call.c:283
#8  _PyFunction_FastCallKeywords (func=, stack=, 
nargs=, kwnames=) at ../Objects/call.c:408
#9  0x0053ebb0 in call_function (pp_stack=0x7fffd990, 
oparg=, kwnames=) at ../Python/ceval.c:4616
#10 0x0054653a in _PyEval_EvalFrameDefault (f=, 
throwflag=) at ../Python/ceval.c:3093
#11 0x005cd68c in PyEval_EvalFrameEx (throwflag=0, f=Frame 0xedcd38, 
for file /mnt/data/srv/dak/dak/dak/examine_package.py, line 261, in 
read_control (filename='python3-apt_1.8.4.2_amd64.deb', recommends=[], 
predepends=[], depends=[], section='', maintainer='', arch='', 
deb_file=<_io.TextIOWrapper at remote 0x75a461f8>)) at ../Python/ceval.c:547
#12 function_code_fastcall (globals=, nargs=, 
args=, co=) at ../Objects/call.c:283
#13 _PyFunction_FastCallKeywords (func=, stack=, 
nargs=, kwnames=) at ../Objects/call.c:408
#14 0x0054207c in call_function (kwnames=0x0, oparg=, 
pp_stack=) at ../Python/ceval.c:4616
#15 _PyEval_EvalFrameDefault (f=, throwflag=) at 
../Python/ceval.c:3124
#16 0x0053f732 in 

Bug#961491: marked as done (CVE-2020-10936: Security flaws in setuid wrappers)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 13:53:39 +
with message-id 
and subject line Bug#961491: fixed in sympa 6.2.40~dfsg-1+deb10u1
has caused the Debian Bug report #961491,
regarding CVE-2020-10936: Security flaws in setuid wrappers
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.)


-- 
961491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: sympa
severity: critical
tags: upstream security patch

Security advisory: https://sympa-community.github.io/security/2020-002.html

Excerpt:

--snip--
A vulnerability has been discovered in Sympa web interface by which attacker 
can execute arbitrary code with root
privileges.

Sympa uses two sorts of setuid wrappers:

FastCGI wrappers
newaliases wrapper

The FastCGI wrappers (wwsympa-wrapper.fcgi and sympa_soap_server-wrapper.fcgi) 
were used to make the web interface
running under privileges of a dedicated user.

The newaliases wrapper (sympa_newaliases-wrapper) allows Sympa to update the 
alias database with root privileges.

Since these setuid wrappers did not clear environment variables, if environment 
variables like PERL5LIB were injected,
forged code might be loaded and executed under privileges of setuid-ed users.
--snap--

Affects all versions of Sympa. Patch is attached.

The following change should also be considered to switch off installation as 
setuid, which is not needed in most cases:
https://github.com/sympa-community/sympa/pull/944/commits/bc9579c7abddc77c92ad51897bd16aba12383d5f

See also 
https://github.com/sympa-community/sympa/issues/943#issuecomment-633278517 
which claims that the patch
is incomplete.

CVE is not yet published.

Regards
Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
commit 3f8449c647e5ab32cf6f8837cb600c1756b6189c
Author: IKEDA Soji 
Date:   Fri Mar 27 21:28:18 2020 +0900

Sympa SA 2020-002 (candidate): Setuid wrappers should clear environment variables to avoid exploits.

diff --git a/src/cgi/sympa_soap_server-wrapper.fcgi.c b/src/cgi/sympa_soap_server-wrapper.fcgi.c
index f4c6a66..435d40c 100644
--- a/src/cgi/sympa_soap_server-wrapper.fcgi.c
+++ b/src/cgi/sympa_soap_server-wrapper.fcgi.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
   2006, 2007, 2008, 2009, 2010, 2011 Comite Reseau des Universites
   Copyright (c) 2011, 2012, 2013, 2014, 2015, 2016, 2017 GIP RENATER
+  Copyright 2020 The Sympa Community. See the AUTHORS.md
+  file at the top-level directory of this distribution and at
+  .
  
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
@@ -24,8 +27,10 @@
 #include 
 
 int main(int argn, char **argv, char **envp) {
+char *myenvp[] = { "IFS= \t\n", "PATH=/bin:/usr/bin", NULL };
+
 setreuid(geteuid(),geteuid());
 setregid(getegid(),getegid());
 argv[0] = SYMPASOAP;
-return execve(SYMPASOAP,argv,envp);
+return execve(SYMPASOAP, argv, myenvp);
 }
diff --git a/src/cgi/wwsympa-wrapper.fcgi.c b/src/cgi/wwsympa-wrapper.fcgi.c
index c66c7f8..34198ec 100644
--- a/src/cgi/wwsympa-wrapper.fcgi.c
+++ b/src/cgi/wwsympa-wrapper.fcgi.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
   2006, 2007, 2008, 2009, 2010, 2011 Comite Reseau des Universites
   Copyright (c) 2011, 2012, 2013, 2014, 2015, 2016, 2017 GIP RENATER
+  Copyright 2020 The Sympa Community. See the AUTHORS.md
+  file at the top-level directory of this distribution and at
+  .
  
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
@@ -24,8 +27,10 @@
 #include 
 
 int main(int argn, char **argv, char **envp) {
+char *myenvp[] = { "IFS= \t\n", "PATH=/bin:/usr/bin", NULL };
+
 setreuid(geteuid(),geteuid()); // Added to fix the segfault
 setregid(getegid(),getegid()); // Added to fix the segfault
 argv[0] = WWSYMPA;
-return execve(WWSYMPA,argv,envp);
+return execve(WWSYMPA, argv, myenvp);
 }
diff --git a/src/libexec/sympa_newaliases-wrapper.c b/src/libexec/sympa_newaliases-wrapper.c
index a399218..a1e5935 100644
--- a/src/libexec/sympa_newaliases-wrapper.c
+++ b/src/libexec/sympa_newaliases-wrapper.c
@@ -6,6 +6,9 @@
   Copyright (c) 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 

Bug#952428: marked as done (sympa: CVE-2020-9369: Security flaws in CSRF prevention)

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 13:53:39 +
with message-id 
and subject line Bug#952428: fixed in sympa 6.2.40~dfsg-1+deb10u1
has caused the Debian Bug report #952428,
regarding sympa: CVE-2020-9369: Security flaws in CSRF prevention
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.)


-- 
952428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: sympa
severity: critical
version: 6.2.40~dfsg-3
tags: patch

A vulnerability has been discovered in Sympa web interface that can
cause denial of service (DoS) attack.

By submitting requests with malformed parameters, this flaw allows to
create junk files in Sympa's directory for temporary files.  And
particularly by tampering token to prevent CSRF, it allows to originate
excessive notification messages to listmasters.

Full advisory:

https://sympa-community.github.io/security/2020-001.html

Regards
   Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.
From 9b86fb3f0337d70221d63392db7d1a52b439dc8f Mon Sep 17 00:00:00 2001
From: IKEDA Soji 
Date: Tue, 11 Feb 2020 17:52:22 +0900
Subject: [PATCH] Sympa SA 2020-001 (candidate).  Denial of service caused by
 malformed CSRF token.

---
 src/cgi/wwsympa.fcgi.in | 25 +++--
 1 file changed, 3 insertions(+), 22 deletions(-)

diff --git a/src/cgi/wwsympa.fcgi.in b/src/cgi/wwsympa.fcgi.in
index 2eb8aec..c7b5195 100644
--- a/src/cgi/wwsympa.fcgi.in
+++ b/src/cgi/wwsympa.fcgi.in
@@ -992,9 +992,6 @@ our %in_regexp = (
 
 # Role
 'role' => 'member|editor|owner',
-
-## CSRF token is a lower case MD5 hash
-'csrftoken' => '^[0-9a-f]{32}$',
 );
 
 ## Regexp applied on incoming parameters (%in)
@@ -1262,8 +1259,6 @@ while ($query = CGI::Fast->new) {
 # affected to another anonymous session.
 undef $ENV{'HTTP_COOKIE'};
 unless (defined $session) {
-Sympa::send_notify_to_listmaster($robot,
-'failed_to_create_web_session', {});
 wwslog('info', 'Failed to create session');
 $session = Sympa::WWW::Session->new($robot, {});
 }
@@ -2149,32 +2144,18 @@ sub get_parameters {
 if ($one_p !~ /^$regexp$/s
 || (defined $negative_regexp && $one_p =~ /$negative_regexp/s)
 ) {
-## Dump parameters in a tmp file for later analysis
-my $dump_file =
-  Conf::get_robot_conf($robot, 'tmpdir')
-. '/sympa_dump.'
-. time . '.'
-. $PID;
-unless (open DUMP, ">$dump_file") {
-wwslog('err', 'Failed to create %s: %s',
-$dump_file, $ERRNO);
-}
-Sympa::Tools::Data::dump_var(\%in, 0, \*DUMP);
-close DUMP;
-
 Sympa::WWW::Report::reject_report_web('user', 'syntax_errors',
 {p_name => $p},
 '', '');
 wwslog(
 'err',
-'Syntax error for parameter %s value "%s" not conform to regexp:%s; dumped vars in %s',
+'Syntax error for parameter %s value "%s" not conform to regexp:%s',
 $pname,
 $one_p,
-$regexp,
-$dump_file
+$regexp
 );
 $in{$p} = '';
-next;
+last;
 }
 }
 }
-- 
1.8.3.1



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sympa
Source-Version: 6.2.40~dfsg-1+deb10u1
Done: Sylvain Beucler 

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

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

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

Debian distribution maintenance software
pp.
Sylvain Beucler  (supplier of updated sympa package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Dec 2020 14:39:54 

Bug#977824: php-imagick: diff for NMU version 3.4.4-4.2

[Ondřej Surý]

David, feel free to upload directly.

Ondřej
--
Ondřej Surý  (He/Him)

> On 28. 12. 2020, at 14:48, David Prévot  wrote:
> 
> Control: tags 977824 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for php-imagick (versioned as 3.4.4-4.2) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
> 
> The patch is also available as a pull request on salsa:
> 
> https://salsa.debian.org/php-team/pecl/php-imagick/-/merge_requests/2
> 
> Regards.
> 
> David
> 

Bug#978514: marked as done (gringo: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Mon, 28 Dec 2020 13:50:04 +
with message-id 
and subject line Bug#978514: fixed in gringo 5.4.1-3
has caused the Debian Bug report #978514,
regarding gringo: non-standard gcc/g++ used for build (gcc-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.)


-- 
978514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gringo
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: gringo
Source-Version: 5.4.1-3
Done: Thomas Krennwallner 

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

Debian distribution maintenance software
pp.
Thomas Krennwallner  (supplier of updated gringo 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, 28 Dec 2020 12:50:01 +
Source: gringo
Architecture: source
Version: 5.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Thomas Krennwallner 
Closes: 978514
Changes:
 gringo (5.4.1-3) unstable; urgency=medium
 .
   * debian/symbols: fix symbols for g++-10 >= 10.2.1
   * Bug fix: "non-standard gcc/g++ used for build (gcc-9)", thanks to
 Matthias Klose (Closes: #978514).
Checksums-Sha1:
 504749c55d83981159d02526adc0793579bd2859 2128 gringo_5.4.1-3.dsc
 b3cb1d5e88da599583df6f453a2ea94708cd231c 23188 gringo_5.4.1-3.debian.tar.xz
 8c0f8c37dbd77c11de2ab49321fa920e8c75bd29 8224 gringo_5.4.1-3_amd64.buildinfo
Checksums-Sha256:
 7b5b4eea19e17441ebe9683fa03dc65d50f8a4dbb4c883d54cd4e153fdce87af 2128 
gringo_5.4.1-3.dsc
 ac6de74b51b4275a7b9b0ddb4d1b9c510d5bb1da609f887fdf6187007e948e62 23188 
gringo_5.4.1-3.debian.tar.xz
 52d01ee562ae9cfdb23362b04c9ab3700532aeb01ded84089ca054299e8e0d11 8224 
gringo_5.4.1-3_amd64.buildinfo
Files:
 96da9a924ce14ae2e3ece5be5ca52f99 2128 interpreters optional gringo_5.4.1-3.dsc
 40ec74909fcc1d3045989d95de3899e0 23188 interpreters optional 
gringo_5.4.1-3.debian.tar.xz
 162cf2633c0e7c491348fe00cab460d7 8224 interpreters optional 
gringo_5.4.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEzH7vLECGZFUde0TKJ5ffdKZmmqkFAl/p3kQACgkQJ5ffdKZm
mqlD9RAAlnGcEyT2R/zfm6t837N7me/cd1PTr4R//g4XyoSBj155wZOnLMkM91jn
nYoab4LKrHcxQxw5ojFmzlGGx064LEj/WEhcPFtyauctj+QXajwKOCe/Ro0te8J+
GLDXFh6sL4GaNyPtfJcCEdJZgMoiw2wlc0OqdLvWf3Oyx3g2KpguZYxtXgIbIl7V
i2jKzvu0rSCx+HSG8RrMjWTUpC0GluVw8Tdt1yaPbkmnNikNmlhbTguh6yDJJ6NW
mJlunBmMbrwQJxB+hYtSNhYu+4NrB25MNgQboDcchjeHG/NxfZbG/DvYZjMlSvOc
IS9stdtO9Ma3lyqfKVantYWWY46bjDAUSYd+DuD+fBANIvUIH7RLDauAib8IHIIO
vpoehRF/1j3iCB/jEHoOaMUmQSyiFmvO9EZ1JDX0pxASukg9MGSyLSVonAWndnp3
QAgXnZ6s/UsrdOmiHljQCR5u093AqaaAFeV8kvis45FS3ab9h390AcrKexbGJuvJ
nhfN63zsnvIFawh/1UIMwLhZVgvVsiQQtqnNzij2m/M00+OwNsgVJ6BPGJUZevwL
HPccmVqgpXhyqyPzaWnwcGe8mJKMlRCImQrX/whIA/MgLeFcybMT0WfZQUARJIf1
eN7/eN26fQqgkOh50IiaUqAh9/wIdIsalLQuY103QQh2qqKEGm4=
=ca2i
-END PGP SIGNATURE End Message ---

Bug#974011: xmille: Incorrect license/copyright for xmille

[Adrian Bunk]

On Sat, Dec 26, 2020 at 12:25:37PM -0800, Keith Packard wrote:
> Steven Robbins  writes:
>...
> > If you are NOT interested in maintaining the package, then I can continue.  
> > Unless Adrian wants to do it?  ;-)
> 
> I'm easy; three is even better than two?
>...

I am just a normal user enjoying the game, and looking at the number of 
uploads in the past decade two maintainers might be sufficient to handle
the load.  ;-)

> -keith

cu
Adrian