Processed: Re: dlint: Dlint fails to find version number of dig

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #991778 [dlint] dlint: Dlint fails to find version number of dig
Severity set to 'important' from 'grave'
> tags -1 + unreproducible
Bug #991778 [dlint] dlint: Dlint fails to find version number of dig
Added tag(s) unreproducible.

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

Bug#991778: dlint: Dlint fails to find version number of dig

[Paul Wise]

Control: severity -1 important
Control: tags -1 + unreproducible

On Sun, 01 Aug 2021 19:00:34 +0200 Patrik Schindler wrote:

> On my Debian Buster system, dig fails to work with
> 
> ;; This program requires DiG version 2.1 or newer, which I cannot find.

I can't reproduce this in a Debian buster chroot.

Could you investigate more closely why it fails on your system?

> Checking on this, I saw that the "ver" call in line 109 doesn't output a
> version number anymore. So I changed that to dig -v.

The command there still works for me in buster:

$ dig localhost any | grep DiG | head -1 | sed -e 's/.*DiG \([0-9.]*\).*/\1/'
9.11.5

> The following replacement for line 109 works for me.
> 
> ver=`dig -v 2>&1 | grep DiG | head -1 | sed -e 's/^DiG \([0-9.]\+\).*$/\1/'`

This seems like a much more correct way to check the version,
so it should be used instead anyway.

> Versions of packages dlint depends on:
> ii  dnsutils  1:9.11.5.P4+dfsg-5.1+deb10u5

I also have 1:9.11.5.P4+dfsg-5.1+deb10u5.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Processed: Re: Bug#993560 closed by Bastian Blank (Re: Bug#993560: FTBFS on arch-any)

[Debian Bug Tracking System]

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

> reopen 993560
Bug #993560 {Done: Bastian Blank } [linux] FTBFS on arch-any
Bug reopened
Ignoring request to alter fixed versions of bug #993560 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#993560: closed by Bastian Blank (Re: Bug#993560: FTBFS on arch-any)

[Daniel Baumann]

reopen 993560
thanks

On 9/3/21 16:24, Debian Bug Tracking System wrote:

Yes, we know.


Great, thanks and looking forward to the upload that will fixes it.

Regards,
Daniel

Bug#978890: quvi: diff for NMU version 0.9.4-1.2

[Boyuan Yang]

Control: tags 978890 + patch
Control: tags 978890 + pending
X-Debbugs-CC: ans...@debian.org

Dear maintainer,

I've prepared an NMU for quvi (versioned as 0.9.4-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
Boyuan Yang

diff -Nru quvi-0.9.4/debian/changelog quvi-0.9.4/debian/changelog
--- quvi-0.9.4/debian/changelog 2016-02-18 10:51:44.0 -0500
+++ quvi-0.9.4/debian/changelog 2021-09-03 23:17:49.0 -0400
@@ -1,3 +1,11 @@
+quvi (0.9.4-1.2) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/control: Update Vcs-* fields.
+  * debian/patches/0001: Fix FTBFS with autoconf 2.70 (Closes: #978890).
+
+ -- Boyuan Yang   Fri, 03 Sep 2021 23:17:49 -0400
+
 quvi (0.9.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload with maintainer permission.
diff -Nru quvi-0.9.4/debian/control quvi-0.9.4/debian/control
--- quvi-0.9.4/debian/control   2016-02-18 10:49:00.0 -0500
+++ quvi-0.9.4/debian/control   2021-09-03 23:14:49.0 -0400
@@ -2,8 +2,8 @@
 Section: utils
 Priority: optional
 Maintainer: Ansgar Burchardt 
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/quvi.git
-Vcs-Git: git://anonscm.debian.org/collab-maint/quvi.git
+Vcs-Git: https://salsa.debian.org/debian/quvi.git
+Vcs-Browser: https://salsa.debian.org/debian/quvi
 Homepage: http://quvi.sourceforge.net
 Standards-Version: 3.9.4
 Build-Depends: debhelper (>= 9), dh-autoreconf, pkg-config, asciidoc,
diff -Nru quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch
quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch
--- quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch   1969-
12-31 19:00:00.0 -0500
+++ quvi-0.9.4/debian/patches/0001-Fix-FTBFS-with-autoconf-2.70.patch   2021-
09-03 23:16:58.0 -0400
@@ -0,0 +1,24 @@
+From: Boyuan Yang 
+Date: Fri, 3 Sep 2021 23:16:08 -0400
+Subject: Fix FTBFS with autoconf 2.70
+
+See also https://bugs.gentoo.org/68
+
+Bug-Debian: https://bugs.debian.org/978890
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index c45d4d8..d64f00d 100644
+--- a/configure.ac
 b/configure.ac
+@@ -6,7 +6,7 @@ AC_PREREQ([2.69])
+ AC_INIT([quvi], m4_esyscmd([./gen-ver.sh -c | tr -d '\n']),
+ [http://quvi.sf.net/bugs/],[],[http://quvi.sf.net/])
+ 
+-AC_DEFINE_UNQUOTED([BUILD_OPTS], "$@",
++AC_DEFINE_UNQUOTED([BUILD_OPTS], "$*",
+   [Define to configure invocation command line options])
+ 
+ AC_CONFIG_SRCDIR([src/main.c])
diff -Nru quvi-0.9.4/debian/patches/series quvi-0.9.4/debian/patches/series
--- quvi-0.9.4/debian/patches/series1969-12-31 19:00:00.0 -0500
+++ quvi-0.9.4/debian/patches/series2021-09-03 23:16:58.0 -0400
@@ -0,0 +1 @@
+0001-Fix-FTBFS-with-autoconf-2.70.patch


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

Processed: quvi: diff for NMU version 0.9.4-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 978890 + patch
Bug #978890 [src:quvi] quvi: ftbfs with autoconf 2.70
Added tag(s) patch.
> tags 978890 + pending
Bug #978890 [src:quvi] quvi: ftbfs with autoconf 2.70
Added tag(s) pending.

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

Bug#978789: marked as done (coinor-cgl: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Sat, 04 Sep 2021 03:03:28 +
with message-id 
and subject line Bug#978789: fixed in coinor-cgl 0.60.3+repack1-3
has caused the Debian Bug report #978789,
regarding coinor-cgl: ftbfs with autoconf 2.70
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.)


-- 
978789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:coinor-cgl
Version: 0.60.3+repack1-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/coinor-cgl_0.60.3+repack1-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
am__tar=''
am__untar=''
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
coin_doxy_excludes=''
coin_doxy_logname=''
coin_doxy_tagfiles=''
coin_doxy_tagname=''
coin_doxy_usedot=''
coin_have_doxygen=''
coin_have_latex=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dos2unix=''
dvidir='${docdir}'
exec_prefix='NONE'
have_autoconf=''
have_automake=''
have_svn=''
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sol_cc_compiler=''
subdirs=''
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "Cgl"
#define PACKAGE_TARNAME "cgl"
#define PACKAGE_VERSION "0.60.3"
#define PACKAGE_STRING "Cgl 0.60.3"
#define PACKAGE_BUGREPORT "c...@lists.coin-or.org"
#define PACKAGE_URL ""

configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-static --enable-dot 
--enable-dependency-linking returned exit code 1
make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: coinor-cgl
Source-Version: 0.60.3+repack1-3
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
coinor-cgl, 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.
Boyuan Yang  (supplier of updated coinor-cgl 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: Fri, 03 Sep 2021 22:38:42 -0400
Source: coinor-cgl
Architecture: source
Version: 0.60.3+repack1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 971559 978789
Changes:
 coinor-cgl (0.60.3+repack1-3) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + coinor-libcgl1: Add Multi-Arch: same.
 

Bug#993638: libxml2: XHTML 1.0 validation is broken

[Vincent Lefevre]

Package: libxml2
Version: 2.9.12+dfsg-3
Severity: grave
Justification: renders package unusable

After the upgrade to 2.9.12+dfsg-3, XHTML 1.0 validation is broken.
There was no such issue with 2.9.10+dfsg-6.7.

Testcase:


http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
title
text


$ xmllint --noout --loaddtd --valid test.html
error : xmlAddEntity: invalid redeclaration of predefined entity
error : xmlAddEntity: invalid redeclaration of predefined entity

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

Kernel: Linux 5.10.0-8-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 libxml2 depends on:
ii  libc6 2.31-17
ii  libicu67  67.1-7
ii  liblzma5  5.2.5-2
ii  zlib1g1:1.2.11.dfsg-2

libxml2 recommends no packages.

libxml2 suggests no packages.

-- no debconf information

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

Processed: forcibly merging 993621 993636

[Debian Bug Tracking System]

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

> forcemerge 993621 993636
Bug #993621 [printer-driver-pnm2ppa] printer-driver-pnm2ppa: postinst failed: 
tempfile: not found
Bug #993621 [printer-driver-pnm2ppa] printer-driver-pnm2ppa: postinst failed: 
tempfile: not found
Marked as found in versions pnm2ppa/1.13-11.
Bug #993636 [printer-driver-pnm2ppa] printer-driver-pnm2ppa: Problem 
installation this version.
Severity set to 'grave' from 'important'
Marked as found in versions pnm2ppa/1.13-10.
Added tag(s) bookworm and sid.
Merged 993621 993636
> thanks
Stopping processing here.

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

Bug#993044: marked as done (libxcrypt breaks existing password hashes)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 23:50:28 +
with message-id 
and subject line Bug#993044: fixed in libxcrypt 1:4.4.25-2
has caused the Debian Bug report #993044,
regarding libxcrypt breaks existing password hashes
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.)


-- 
993044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libxcrypt
version: 1:4.4.22-1
severity: serious
justification: breaks login

See bug #992848.
Because of the way libpam0g calls libxcrypt any existing sha256 hash
will be rejected at login as expired.
I'm going to fix this in pam using the linux-pam upstream fix, but
libxcrypt should not migrate to testing before the fixed pam is in
testing.

This bug is intended to block that migration.
Feel free to do something else that blocks the migration.
If this bug is still open when libpam migrates, I'll close it.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libxcrypt
Source-Version: 1:4.4.25-2
Done: Marco d'Itri 

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

Debian distribution maintenance software
pp.
Marco d'Itri  (supplier of updated libxcrypt 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: Sat, 04 Sep 2021 01:15:24 +0200
Source: libxcrypt
Architecture: source
Version: 1:4.4.25-2
Distribution: unstable
Urgency: medium
Maintainer: Marco d'Itri 
Changed-By: Marco d'Itri 
Closes: 993044 993466
Changes:
 libxcrypt (1:4.4.25-2) unstable; urgency=medium
 .
   * Add a symbols file for arc, contributed by Alexey Brodkin.
 (Closes: #993466)
   * Conflict with older versions of libpam0g which broke support for
 sha-256 hashes with libxcrypt >= 4.4.22. (Closes: #993044)
Checksums-Sha1:
 72937099c028697d345b00d13747766f257ecabf 1525 libxcrypt_4.4.25-2.dsc
 f71046bb5b1b38aa52aa4c94ba6f4d46fb7d0fc6 7728 libxcrypt_4.4.25-2.debian.tar.xz
 44b214c7fcd485b317d6bf3d977f78412bf13fec 6382 
libxcrypt_4.4.25-2_amd64.buildinfo
Checksums-Sha256:
 8160446ad08ca293986c62d8c06bc1515787ef3fb25d7a4344d2c3cf224110b9 1525 
libxcrypt_4.4.25-2.dsc
 8c9306712fc7d4f368487685c8cba3e3fd9fab89d5515e0e006d480abc72c740 7728 
libxcrypt_4.4.25-2.debian.tar.xz
 313f8ba5c88e85dfc5f98055d4b788dafa89819e4c714d8beba64ae67d9ec54f 6382 
libxcrypt_4.4.25-2_amd64.buildinfo
Files:
 ce81b5e046f3a041fff9f01dad006c76 1525 admin optional libxcrypt_4.4.25-2.dsc
 7884b1631fba1ae1c6423000e5dc342d 7728 admin optional 
libxcrypt_4.4.25-2.debian.tar.xz
 a167cc821056d15924451701753fe05c 6382 admin optional 
libxcrypt_4.4.25-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCYTKtlAAKCRDLPsM64d7X
geXWAQD1C46GBgWwoykG7PjnpdFTyOyUs3FJCr3dnPqZfjiuxwEA4q1gp8S27Bz8
tD4nH7liFEO9MNPkYxHUnVY9mY0jzgs=
=meUf
-END PGP SIGNATURE End Message ---

Bug#980134: marked as done (shaarli: Missing minified js and css for frontend)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 23:52:28 +
with message-id 
and subject line Bug#980134: fixed in shaarli 0.12.0+dfsg-3
has caused the Debian Bug report #980134,
regarding shaarli: Missing minified js and css for frontend
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.)


-- 
980134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shaarli
Version: 0.12.0+dfsg-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: jvalle...@mailbox.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Shaarli package is currently missing minified js and css files which
are expected by the frontend. They should be built by webpack, but
several dependencies are missing:

- - awesomeplete
- - blazy
- - sass-loader

While the packaged shaarli is technically usable, it is missing both
functionality and styling that would be expected by users. Therefore
it should be kept out of stable releases until this issue is fixed.

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 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 shaarli depends on:
ii  gettext 0.21-3
ii  javascript-common   11+nmu1
ii  libapache2-mod-php7.4 [libapache2-mod-php]  7.4.11-1
ii  libapache2-mod-php8.0 [libapache2-mod-php]  8.0.1-1
ii  libjs-jquery3.5.1+dfsg+~3.5.5-5
ii  libjs-jquery-lazyload   1.7.2-1.1
ii  libjs-jquery-ui 1.12.1+dfsg-7
ii  php-arthurhoaro-web-thumbnailer 2.0.3+dfsg-1
ii  php-common  2:76
ii  php-curl2:7.4+76
ii  php-gd  2:7.4+76
ii  php-intl2:7.4+76
ii  php-ldap2:7.4+76
ii  php-mbstring2:7.4+76
ii  php-netscape-bookmark-parser2.1.0-3
ii  php-oscarotero-gettext  4.8.2-4
ii  php-parsedown   1.7.3-2
ii  php-pubsubhubbub-publisher  0~~20181009-2
ii  php-slim3.12.3-4
ii  php7.4-curl [php-curl]  7.4.11-1
ii  php7.4-gd [php-gd]  7.4.11-1
ii  php7.4-intl [php-intl]  7.4.11-1
ii  php7.4-json [php-json]  7.4.11-1
ii  php7.4-ldap [php-ldap]  7.4.11-1
ii  php7.4-mbstring [php-mbstring]  7.4.11-1
ii  php8.0 [php]8.0.1-1
ii  php8.0-mbstring [php-mbstring]  8.0.1-1

Versions of packages shaarli recommends:
ii  nginx-core [httpd]  1.18.0-6+b1

shaarli suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmAA3EEWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICAEFD/94NdyTYq9ovONlDL6aKnrjdsu9
BVZp/cB4N2nGfEiEpjc4nQ0EqCZCvAwBJWNGa3FoG44jNniLZnO9Kk4+oZfCcMwE
wxR+9wuaT9EQwEj5OLseHIcX0I48B4BfRRlJbVhLerMLxJ098V5xo3jRYvUD+Ak7
ZCGvfRCuZ2LnoRbhHT4bg9w1OReU15B5nDz3mWIzSW7Q6tDQJX/Xnltfy5ahNS4k
mzCjeyUIIn2JGt+u+9Iw7DP/kdl5pYfw2W7ui7flus3oSpO5/Q1o0nBWOH5oZ/r9
fNpaoTROu+68P2Qx+/1wDneP2WnNbg07R0rV0htdy3nMMUIkcOXMygz1YaB7dO0d
hK5k2GF/EjH1t7CP4wQa4UZE2byRnVD4JeEzy3A5f7pMGxkzuxJ1HU0qUXJrUQ26
/Eh6uBTecl+k8d3WDsYKeaysfYi5AzT4MYvVx+VsK5864j/IAHokvz5NxeEhOQAM
BHVdu51yWNlKR0cqe5jwk4BVWBtzNr+1tN4TfmrZ3IwgORGWPpSmdAWA48w8IxuF
0Gv7VSIMYCt3dtm7dNhGUOApkqh73bk9RywY7b9/Qw2qabnezcu2TTrB9GArSUTa
DwDkt80aB2gb3gCJ8qpNEiPNQ3q81p6XaroC1KEvsxL0yQv+y6fufQJ+67ElyRIL
uN/19lslqG3JkbHofw==
=+EB3
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: shaarli
Source-Version: 0.12.0+dfsg-3
Done: James Valleroy 

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

Debian distribution maintenance software
pp.
James 

Bug#988386: marked as done (ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 CVE-2021-39252 CVE-2021-3925

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 23:00:09 +
with message-id 
and subject line Bug#988386: fixed in ntfs-3g 1:2021.8.22-1
has caused the Debian Bug report #988386,
regarding ntfs-3g: CVE-2021-33285 CVE-2021-35269 CVE-2021-35268 CVE-2021-33289 
CVE-2021-33286 CVE-2021-35266 CVE-2021-33287 CVE-2021-35267 CVE-2021-39251 
CVE-2021-39252 CVE-2021-39253 CVE-2021-39254 CVE-2021-39255 CVE-2021-39256 
CVE-2021-39257 CVE-2021-39258 CVE-2021-39259 CVE-2021-39260 CVE-2021-39261 
CVE-2021-39262 CVE-2021-39263
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.)


-- 
988386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntfs-3g
Version: 2017.3.23AR.3

For CVE's pending from upstream, is everything already mirrored so upstream
fixes are applied in the next release? I'm asking because the upstream
maintainers are trying to identify how soon their fixes will be applied to
your packages.

Thanks,




-- 

*Jeremy Galindo* Associate Mgr., Offensive Security
Datto, Inc. Direct Line www.datto.com


Join the conversation! [image: Facebook] 
[image: Twitter]  [image: LinkedIn]
  [image: Blog RSS]
 [image: Slideshare]
  [image: Spiceworks]

--- End Message ---
--- Begin Message ---
Source: ntfs-3g
Source-Version: 1:2021.8.22-1
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated ntfs-3g 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, 02 Sep 2021 18:10:12 +0200
Source: ntfs-3g
Binary: libntfs-3g89 libntfs-3g89-dbgsym ntfs-3g ntfs-3g-dbgsym ntfs-3g-dev 
ntfs-3g-dev-dbgsym ntfs-3g-udeb
Architecture: source amd64
Version: 1:2021.8.22-1
Distribution: experimental
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libntfs-3g89 - read/write NTFS driver for FUSE (runtime library)
 ntfs-3g- read/write NTFS driver for FUSE
 ntfs-3g-dev - read/write NTFS driver for FUSE (development)
 ntfs-3g-udeb - read/write NTFS driver for FUSE (udeb)
Closes: 988386
Changes:
 ntfs-3g (1:2021.8.22-1) experimental; urgency=high
 .
   * New upstream release (closes: #988386) fixing CVE-2021-33285,
 CVE-2021-35269, CVE-2021-35268, CVE-2021-33289, CVE-2021-33286,
 CVE-2021-35266, CVE-2021-33287, CVE-2021-35267, CVE-2021-39251,
 CVE-2021-39252, CVE-2021-39253, CVE-2021-39254, CVE-2021-39255,
 CVE-2021-39256, CVE-2021-39257, CVE-2021-39258, CVE-2021-39259,
 CVE-2021-39260, CVE-2021-39261, CVE-2021-39262, CVE-2021-39263: multiple
 buffer overflows.
   * Library transition from libntfs-3g886 to libntfs-3g89 .
Checksums-Sha1:
 8c2fa9724907b8f15b49c1aa0599674e7bfca454 2135 ntfs-3g_2021.8.22-1.dsc
 20304c0f5621deff5ed898b56c7848ea2d945621 899447 ntfs-3g_2021.8.22.orig.tar.gz
 2997885b5ddd295af322ee7e74cf6338566f6517 22460 
ntfs-3g_2021.8.22-1.debian.tar.xz
 e56a0ca8e7e828f321cb684305ebb6b60550bcfe 416780 
libntfs-3g89-dbgsym_2021.8.22-1_amd64.deb
 403fcbd497b8561e372751aa055eff4fc79f1f7e 171028 
libntfs-3g89_2021.8.22-1_amd64.deb
 d50dfa4b680d687e0b4a9771188277985939d8b8 1157236 
ntfs-3g-dbgsym_2021.8.22-1_amd64.deb
 d114d18ff685d7061436afd4ea9d338f6c8b85ee 56688 
ntfs-3g-dev-dbgsym_2021.8.22-1_amd64.deb
 2d8b61f7057a8cb1152735e2b1a68b4cd3384be8 242556 
ntfs-3g-dev_2021.8.22-1_amd64.deb
 303cc04ad7e5feb57a2412480bae2c2121288d8a 230452 
ntfs-3g-udeb_2021.8.22-1_amd64.udeb
 d77ee39509a74917e6a903bedfcc02a2c20bb275 8739 
ntfs-3g_2021.8.22-1_amd64.buildinfo
 14e96e91d111793eaa5975fdf64987b6b68657db 410956 ntfs-3g_2021.8.22-1_amd64.deb
Checksums-Sha256:
 b3a841e5f0f20959f149544f701aa4c51f22809b985acedc2d3c585a4fc6735c 2135 
ntfs-3g_2021.8.22-1.dsc
 

Processed: Re: Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-signed-arm64
Bug #993612 [bugs.debian.org] bugs.debian.org: Socionext SynQuacer fails to 
mount rootfs after upgrade to Bullseye
Bug reassigned from package 'bugs.debian.org' to 'linux-signed-arm64'.
Ignoring request to alter found versions of bug #993612 to the same values 
previously set
Ignoring request to alter fixed versions of bug #993612 to the same values 
previously set
> found -1 5.10.46+4, 5.10.46+4~bpo10+1
Bug #993612 [linux-signed-arm64] bugs.debian.org: Socionext SynQuacer fails to 
mount rootfs after upgrade to Bullseye
There is no source info for the package 'linux-signed-arm64' at version 
'5.10.46+4' with architecture ''
Unable to make a source version for version '5.10.46+4'
There is no source info for the package 'linux-signed-arm64' at version 
'5.10.46+4~bpo10+1' with architecture ''
Unable to make a source version for version '5.10.46+4~bpo10+1'
Marked as found in versions 5.10.46+4~bpo10+1 and 5.10.46+4.
> tag -1 moreinfo
Bug #993612 [linux-signed-arm64] bugs.debian.org: Socionext SynQuacer fails to 
mount rootfs after upgrade to Bullseye
Added tag(s) moreinfo.
> severity -1 important
Bug #993612 [linux-signed-arm64] bugs.debian.org: Socionext SynQuacer fails to 
mount rootfs after upgrade to Bullseye
Severity set to 'important' from 'critical'

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

Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

[Don Armstrong]

Control: reassign -1 linux-signed-arm64
Control: found -1 5.10.46+4, 5.10.46+4~bpo10+1
Control: tag -1 moreinfo
Control: severity -1 important


On Fri, 03 Sep 2021, Luca Di Stefano wrote:
> A few days ago I tried to upgrade one of the six Socionext SynQuacers
> that we have to the latest Debian release.
> 
> It was running fine on Buster using the 4.19 kernel and had no previous 
> issues.

[...]

> The next boot sequence would start and get to the point where it would
> look for the rootfs without finding it and going into initramfs
> 
> I've then proceeded to reinstall buster on that machine and it just
> worked fine, then also tried installing the kernel from backports
> linux- image-5.10.0-0.bpo.8-arm64 and after reboot it caused the same
> problem not finding the rootfs and going into initramfs.

I'm not familiar with the hardware of this particular device, but I
suspect that some necessary driver was (likely inadvertently) excluded
from the configuration of the 5.10 kernel, but included in 4.19.

Looking at the output from the boot of both kernels should give you an
idea of what module/device is broken, and providing that to this bug
will give one of the maintainers of the arm64 kernel a chance of helping
fix the issue.

-- 
Don Armstrong  https://www.donarmstrong.com

If a nation values anything more than freedom, it will lose its
freedom; and the irony of it is that if it is comfort or money it
values more, it will lose that, too.
 -- W. Somerset Maugham

Bug#993631: cfgrib FTBFS: test failures

[Alastair McKinstry]

This is a bug in python3-eccodes which now depends on ecmwflibs.
Ecmwflibs in now in the NEW queue

On 03/09/2021, 21:51, "Adrian Bunk"  wrote:

Source: cfgrib
Version: 0.9.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1

Bug#982914: closing 982914

[Yadd]

close 982914 
thanks

Processed: closing 982914

[Debian Bug Tracking System]

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

> close 982914
Bug #982914 [chai] chai: broken-symlink /usr/share/doc/chai -> libjs-chai, 
missing-copyright-file
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#993631: cfgrib FTBFS: test failures

[Adrian Bunk]

Source: cfgrib
Version: 0.9.9.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=cfgrib=0.9.9.0-1

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
for p in python3.9; do \
PY3VERNUM=`echo $p | sed -e 's/python//' `; \
pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
done
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_cfgrib/build; 
python3.9 -m pytest tests
= test session starts ==
platform linux -- Python 3.9.7, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>, configfile: pyproject.toml
collected 6 items / 9 errors / 2 skipped

 ERRORS 
__ ERROR collecting .pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.9_cfgrib/build/tests/test_20_main.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3/dist-packages/gribapi/bindings.py:28: in 
import ecmwflibs as findlibs
E   ModuleNotFoundError: No module named 'ecmwflibs'

During handling of the above exception, another exception occurred:
/usr/lib/python3.9/importlib/__init__.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_20_main.py:3: in 
from cfgrib import __main__
cfgrib/__init__.py:19: in 
from .cfmessage import CfMessage
cfgrib/cfmessage.py:29: in 
from . import messages
cfgrib/messages.py:28: in 
import eccodes  # type: ignore
/usr/lib/python3/dist-packages/eccodes/__init__.py:13: in 
from .eccodes import *  # noqa
/usr/lib/python3/dist-packages/eccodes/eccodes.py:12: in 
from gribapi import (
/usr/lib/python3/dist-packages/gribapi/__init__.py:13: in 
from .gribapi import *  # noqa
/usr/lib/python3/dist-packages/gribapi/gribapi.py:34: in 
from . import errors
/usr/lib/python3/dist-packages/gribapi/errors.py:16: in 
from .bindings import ENC, ffi, lib
/usr/lib/python3/dist-packages/gribapi/bindings.py:30: in 
import findlibs
E   ModuleNotFoundError: No module named 'findlibs'
...
=== short test summary info 
ERROR tests/test_20_main.py
ERROR tests/test_20_messages.py
ERROR tests/test_25_cfmessage.py
ERROR tests/test_30_dataset.py
ERROR tests/test_40_xarray_store.py
ERROR tests/test_40_xarray_to_grib_regular_ll.py
ERROR tests/test_50_datamodels.py
ERROR tests/test_50_sample_data.py
ERROR tests/test_50_xarray_getitem.py
!!! Interrupted: 9 errors during collection 
= 2 skipped, 9 errors in 1.97s =
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.9_cfgrib/build; python3.9 -m pytest tests
make[1]: *** [debian/rules:19: override_dh_auto_test] Error 13



(m68k builds with nocheck)

Bug#993630: isso depends on deprecated node-jade which is going to be removed

[Yadd]

Package: isso
Severity: serious

Hi,

isso depends on node-jade which is no more maintained.

Cheers,
Yadd

Processed: fixed 982914 in 4.3.0+ds+~4.2.14-2

[Debian Bug Tracking System]

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

> fixed 982914 4.3.0+ds+~4.2.14-2
Bug #982914 [chai] chai: broken-symlink /usr/share/doc/chai -> libjs-chai, 
missing-copyright-file
Marked as fixed in versions node-chai/4.3.0+ds+~4.2.14-2.
> thanks
Stopping processing here.

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

Bug#993628: openvdb FTBFS: Could NOT find GTest

[Adrian Bunk]

Source: openvdb
Version: 8.1.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=openvdb=8.1.0-1

...
-- 
-- --- Configuring OpenVDBUnitTests ---
-- 
CMake Error at 
/usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR
  GTEST_MAIN_LIBRARY) (Required is at least version "1.8")
Call Stack (most recent call first):
  /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.18/Modules/FindGTest.cmake:205 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  openvdb/openvdb/unittest/CMakeLists.txt:40 (find_package)


-- Configuring incomplete, errors occurred!

Bug#993627: ndpi: Bus error on armhf when built on 64bit hardware

[Adrian Bunk]

Source: ndpi
Version: 4.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ndpi=armhf

...
Bus error
openvpn.pcapERROR
...
make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1


This is likely an alignment problem, similar to the fixed #917238.

Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

[Paul Gevers]

Hi Hilko,

On 02-09-2021 23:39, Hilko Bengen wrote:
> * Paul Gevers:
> 
>> On Thu, 2 Sep 2021 10:17:22 +0200 Sascha Steinbiss  wrote:
>>> I think this is done now. With YARA 4.1.2 and 
>>> golang-github-hillu-go-yara 4.1.0 now in unstable, the build works again 
>>> as the build-time tests complete fine.
>>>
>>> @Hilko any other comments?
>>
>> If there are incompatible API changes, the soname needs to be bumped.
> 
> The soname was bumped, from 4 to 8.

Sorry, I somehow missed that. So if I understand it, you just forgot to
close the bug?

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: severity of 993559 is serious

[Debian Bug Tracking System]

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

> severity 993559 serious
Bug #993559 [ganeti-3.0] ganeti-3.0 unable to remove a dpkg-divert during 
postrm when 2.16 is still there
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#993547: marked as done (saods9: Error in startup script)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 19:19:08 +
with message-id 
and subject line Bug#993547: fixed in saods9 8.2+repack-3
has caused the Debian Bug report #993547,
regarding saods9: Error in startup script
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.)


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


Package: saods9
Version: 8.3~b1+repack-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Launching ds9 from the command line, result in an output error :

Error in startup script: cannot find symbol "Signal_Init": 
/usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so: 
undefined symbol: _Signal_Init

while executing
"load /usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so 
Signal"

("package ifneeded Signal 1.4.4.1" script)
invoked from within
"package require Signal"
(file "/usr/share/saods9/library/ds9.tcl" line 229)

instead of launching the program

a.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

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

Versions of packages saods9 depends on:
ii  libtk-img  1:1.4.13+dfsg-1
ii  tcl-awthemes   10.4.0-1
ii  tcl-signal 1.4.4.1-1
ii  tcl-tls1.7.22-2
ii  tcl-ttkthemes  3.2.2-1
ii  tcl-xpa2.1.20-1
ii  tclfitsy   8.2+repack-2
ii  tcliis 8.2+repack-2
ii  tcllib 1.20+dfsg-1
ii  tclxml 1:3.2.7-5
ii  tk 8.6.11+1
ii  tk-html1   1.04-2
ii  tk-mpeg1.0.9-1
ii  tk-table   2.10.7-1
ii  tkblt  3.2.23-1
ii  tkcon  2:2.7.10-2
ii  tksao  8.2+repack-2

Versions of packages saods9 recommends:
ii  saods9-doc  8.2+repack-2

Versions of packages saods9 suggests:
pn  python3-pyds9  
pn  xpa-tools  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: saods9
Source-Version: 8.2+repack-3
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated saods9 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: Fri, 03 Sep 2021 20:51:26 +0200
Source: saods9
Architecture: source
Version: 8.2+repack-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 993547
Changes:
 saods9 (8.2+repack-3) unstable; urgency=medium
 .
   * Re-order and rename patches according to subsystem
   * Fix d/watch base URL
   * Adjust package name of tclsignal to new version (Closes: #993547)
   * Push Standards-Version to 4.6.0. No changes needed
Checksums-Sha1:
 82dcb91415531630f7a844172b11a899aa14878d 2511 saods9_8.2+repack-3.dsc
 b8aa928b05b8e83258546f1a32a518461ca67952 21764 
saods9_8.2+repack-3.debian.tar.xz
Checksums-Sha256:
 7003d63f3ebd314886324ee5e2e08e496094836ef9a479699a9015b93a2ddf65 2511 
saods9_8.2+repack-3.dsc
 f3425525f79bc480a5aab2e3dd67edf227140156ae0d85c83ca5f9068347d3c0 21764 
saods9_8.2+repack-3.debian.tar.xz
Files:
 95bda4fce96eb525b0d3b397b2378520 2511 science optional saods9_8.2+repack-3.dsc
 e1e64ba365d1b6d09cbd5a18dbda0cd5 21764 science optional 
saods9_8.2+repack-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmEyb7wACgkQcRWv0HcQ
3PdANhAAvcCSa/JsYCppoGrkb630N10A5d9SYE30SFPInPXaCRhHsbc+zpYCsw9d
+OqWma5tnrNoYdxqBhXXBFbWFJPhXX77o4X8upZed+AjD4sFiIcmA5hxlLg334ml
wNI+XC9Rxam4WvYTBpYTd71NfWUCLqugWbw9u9qLSB2N/J8ZwKtnewY3JKriY3B8
rJMRY4P2kib4neVgM3C8m+ffqW/ntPu6gn3+Rd5BiekTNMO4nwYXSSYqgneoai7w
1oR7QFSaz5U6v+sSGsmL7ILKyTQTYx/4C3pz58waZd23EDtDqyOWEjjl7HnmjTbB

Bug#993547: marked as done (saods9: Error in startup script)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 19:06:21 +
with message-id 
and subject line Bug#993547: fixed in saods9 8.3~b1+repack-2
has caused the Debian Bug report #993547,
regarding saods9: Error in startup script
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.)


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


Package: saods9
Version: 8.3~b1+repack-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Launching ds9 from the command line, result in an output error :

Error in startup script: cannot find symbol "Signal_Init": 
/usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so: 
undefined symbol: _Signal_Init

while executing
"load /usr/lib/tcltk/x86_64-linux-gnu/Signal1.4.4.1/libSignal1.4.4.1.so 
Signal"

("package ifneeded Signal 1.4.4.1" script)
invoked from within
"package require Signal"
(file "/usr/share/saods9/library/ds9.tcl" line 229)

instead of launching the program

a.

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

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

Versions of packages saods9 depends on:
ii  libtk-img  1:1.4.13+dfsg-1
ii  tcl-awthemes   10.4.0-1
ii  tcl-signal 1.4.4.1-1
ii  tcl-tls1.7.22-2
ii  tcl-ttkthemes  3.2.2-1
ii  tcl-xpa2.1.20-1
ii  tclfitsy   8.2+repack-2
ii  tcliis 8.2+repack-2
ii  tcllib 1.20+dfsg-1
ii  tclxml 1:3.2.7-5
ii  tk 8.6.11+1
ii  tk-html1   1.04-2
ii  tk-mpeg1.0.9-1
ii  tk-table   2.10.7-1
ii  tkblt  3.2.23-1
ii  tkcon  2:2.7.10-2
ii  tksao  8.2+repack-2

Versions of packages saods9 recommends:
ii  saods9-doc  8.2+repack-2

Versions of packages saods9 suggests:
pn  python3-pyds9  
pn  xpa-tools  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: saods9
Source-Version: 8.3~b1+repack-2
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated saods9 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: Fri, 03 Sep 2021 20:43:03 +0200
Source: saods9
Architecture: source
Version: 8.3~b1+repack-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 993547
Changes:
 saods9 (8.3~b1+repack-2) experimental; urgency=medium
 .
   * Adjust package name of tclsignal to new version (Closes: #993547)
Checksums-Sha1:
 7e21b353fe711a321d7d690fcac0f5cf0fb65a69 2532 saods9_8.3~b1+repack-2.dsc
 e15a668ad45308559ddd45df458473d4e4b41db7 21744 
saods9_8.3~b1+repack-2.debian.tar.xz
Checksums-Sha256:
 e19d0caf2a77ef9c3b0abc70f8a500c9de002a01d7e5a94d4c1687e58d7fe9a0 2532 
saods9_8.3~b1+repack-2.dsc
 f15145a6fa71c514a24b6b92a81527629927f57a056066202aa515e6a11d0d66 21744 
saods9_8.3~b1+repack-2.debian.tar.xz
Files:
 3bddb360eb83a512cee7087c3ffe0fe1 2532 science optional 
saods9_8.3~b1+repack-2.dsc
 78002ca5ad37bfc3f0c1906992872dd8 21744 science optional 
saods9_8.3~b1+repack-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmEybhkACgkQcRWv0HcQ
3PeUyQ/9FC+75359iT2ELIOI6jr6ybzUBPEumtL4AKQUWzZValxbPBPjIPNdhs42
Q7u8YRJUkjdgc8PnOesA0m2efopMpTuH/NKK6TmIFi0p1wKWl4Hl2dyYXC9qnffZ
xBG0pWD3lfPFi1jiAeQhuGpzCltBkw3Vw4Wxd2L8PtEAIYmnu2ExEtzmy5d38auD
n4Or7PP3pqZFKEr69/HHSxAqA1QMCkj0P4jFbeAjsX+qYuqKDJ0B+jOSGo0FVJno
XTkZVdaKFDx/kfOqfvH/ukvDkVnYUN3cE+qTa4NiH8O/Shxh/3IIIsRsLdJEp6aE
APkmWR1685GsBXHPBc3uqLML605CHLtmY6nayj8oUp8NcHzohegl/xfTnJ35bb34

Bug#991353: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2021-1093, CVE-2021-1094, CVE-2021-1095)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 19:02:20 +
with message-id 
and subject line Bug#991353: fixed in nvidia-graphics-drivers-legacy-390xx 
390.144-1~deb10u1
has caused the Debian Bug report #991353,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2021-1093, CVE-2021-1094, 
CVE-2021-1095
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.)


-- 
991353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: reassign -5 src:nvidia-graphics-drivers-tesla-440 440.64.00-1
Control: retitle -5 nvidia-graphics-drivers-tesla-440: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: tag -5 + wontfix
Control: reassign -6 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -6 nvidia-graphics-drivers-tesla-450: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: reassign -7 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -7 nvidia-graphics-drivers-tesla-460: CVE-2021-1093, 
CVE-2021-1094, CVE-2021-1095
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 450.51-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5211

CVE‑2021‑1093   NVIDIA GPU Display Driver for Windows and Linux
contains a vulnerability in firmware where the driver contains an
assert() or similar statement that can be triggered by an attacker,
which leads to an application exit or other behavior that is more
severe than necessary, and may lead to denial of service or system
crash.

CVE‑2021‑1094   NVIDIA GPU Display Driver for Windows and Linux
contains a vulnerability in the kernel mode layer (nvlddmkm.sys)
handler for DxgkDdiEscape where an out of bounds array access may
lead to denial of service or information disclosure.

CVE‑2021‑1095   NVIDIA GPU Display Driver for Windows and Linux
contains a vulnerability in the kernel mode layer (nvlddmkm.sys)
handlers for all control calls with embedded parameters where
dereferencing an untrusted pointer may lead to denial of service.

Driver Branch   CVE IDs Addressed
R470, R460, R450, R418, R390CVE‑2021‑1093, CVE‑2021‑1094, CVE‑2021‑1095

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.144-1~deb10u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, 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 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-390xx 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, 26 Jul 2021 10:50:49 +0200
Source: nvidia-graphics-drivers-legacy-390xx
Architecture: source
Version: 390.144-1~deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 989885 991353
Changes:
 nvidia-graphics-drivers-legacy-390xx (390.144-1~deb10u1) buster; urgency=medium
 .
   * Rebuild for buster.
 .
 nvidia-graphics-drivers-legacy-390xx (390.144-1) unstable; urgency=medium
 .
   * New upstream legacy branch release 390.144 (2021-07-20).
 * Fixed CVE-2021-1093, CVE-2021-1094, CVE-2021-1095.  (Closes: #991353)
   https://nvidia.custhelp.com/app/answers/detail/a_id/5211
 - Worked around a bug in Meson 

Processed: Bug#993547 marked as pending in saods9

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993547 [saods9] saods9: Error in startup script
Ignoring request to alter tags of bug #993547 to the same tags previously set

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

Bug#993547: marked as pending in saods9

[Ole Streicher]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-astro-team/saods9/-/commit/d35ed90531514fd30bb556504f2d328f02cdafd2


Adjust package name of tclsignal to new version

Closes: #993547


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993547

Bug#993547: marked as pending in saods9

[Ole Streicher]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-astro-team/saods9/-/commit/018e6e5079a1966165557e82edbab0146e34f190


Adjust package name of tclsignal to new version

Closes: #993547


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/993547

Processed: Bug#993547 marked as pending in saods9

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #993547 [saods9] saods9: Error in startup script
Added tag(s) pending.

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

Bug#993621: printer-driver-pnm2ppa: postinst failed: tempfile: not found

[Boyuan Yang]

Package: printer-driver-pnm2ppa
Severity: grave
Version: 1.13-10
X-Debbugs-CC: o...@debian.org
Tags: sid bookworm

Dear Debian Printer Team members,

Package printer-driver-pnm2ppa failed to install due to errors in postinst:

/var/lib/dpkg/info/printer-driver-pnm2ppa.postinst: 1: tempfile: not found

The tempfile command is no longer available after Debian 11 release. Please
consider using "mktemp" from coreutils instead. This bug does not affect
packages in released Debian 11 stable.

-- 
Thanks,
Boyuan Yang


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

Bug#971328: marked as done (nageru: uses deprecated libavresample)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 17:04:29 +
with message-id 
and subject line Bug#971328: fixed in nageru 2.0.2-1
has caused the Debian Bug report #971328,
regarding nageru: uses deprecated libavresample
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.)


-- 
971328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nageru
Version: 2.0.1-1
Severity: important
Tags: sid bullseye
Usertags: libavresample-removal
Control: block 971318 by -1

Dear maintainer,

nageru currently Build-Depends or Depends on libavresample-dev. The
ffmpeg developers consider libavresample as obsolete and replaced the
library with libswresample. Please switch nageru to use
libswresample.

Note that this switch will require changes if nageru doesn't already
have support for libsvresample.

Cheers 
--- End Message ---
--- Begin Message ---
Source: nageru
Source-Version: 2.0.2-1
Done: Steinar H. Gunderson 

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

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

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

Debian distribution maintenance software
pp.
Steinar H. Gunderson  (supplier of updated nageru package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Sep 2021 18:45:12 +0200
Source: nageru
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Steinar H. Gunderson 
Changed-By: Steinar H. Gunderson 
Closes: 971328
Changes:
 nageru (2.0.2-1) unstable; urgency=medium
 .
   * New upstream release.
 * Obsoletes fix-ffmpeg-height-calculation.diff.
   * Remove unused build-dependency libavresample-dev. (Closes: #971328)
Checksums-Sha1:
 615420085b9a0a05c988dccb73c0235dea828a5f 2381 nageru_2.0.2-1.dsc
 985f93e40a2dd723670ee504b27884e0df3dc17e 684897 nageru_2.0.2.orig.tar.gz
 fe5d0f0182a62ccdb05a953c55a050b0d433fcf1 5800 nageru_2.0.2-1.debian.tar.xz
 95ba6982f8c565d05af75d7d1cb4d99dea10513b 14814 nageru_2.0.2-1_amd64.buildinfo
Checksums-Sha256:
 9c108972f5327658582147482560dd47b0e7dadef16179771b95580d281fd6c3 2381 
nageru_2.0.2-1.dsc
 7cf63ad9ca5a2cfc87e92c9e4f7f9d95e3cd2988da6e14341bbca6a8a0c2d7b6 684897 
nageru_2.0.2.orig.tar.gz
 d5ef1a25773e79b79b9a615610585c5cfac89bc9c07c6458c1dace6fca4afc10 5800 
nageru_2.0.2-1.debian.tar.xz
 7332736edb6c4a7dc586a3eb7659894ec9d9c4e6c7bc90d1a72449f14d4dcb02 14814 
nageru_2.0.2-1_amd64.buildinfo
Files:
 bda2f4931dcd208f75803c36f2554ca1 2381 video optional nageru_2.0.2-1.dsc
 8ab5e730bb883ce1d08823fba7957355 684897 video optional nageru_2.0.2.orig.tar.gz
 6fed8d0f7f8b2effefc0c59e63663cd1 5800 video optional 
nageru_2.0.2-1.debian.tar.xz
 97dfca63589ec7c61bff6fe0fd173a58 14814 video optional 
nageru_2.0.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwukAT/AowY5OrduDf2F1YXeXj3YFAmEyUloACgkQf2F1YXeX
j3aZkhAAvixgPkFhHov4QrC7wdz0XI7TlD6FI2To9kSZa+nK34OBKCUDXedBipNW
8U+4OpS8YHOXVmv97lqtbsBNh7yMiwbzLklCqN5L/84Vry/9oicJx3XKSprXohha
3nbuhTW1NtwD4FhhMeXR429XwQ/xWhgTPkn0GBmT71GMDQXvpiPmInOft3o3I6SC
JCgQoeEjslVQuerL81VBXhUkVvMFyGkZLJ9hrgwlm0XqYxz6uCEDw8EvTnkdquYn
6mrXfUbX9pzoE7o1eSNV222UzPJdIP0qauxZhisH/G6K7/3CaGCr/fHGZ2Xvzbkv
4mxLjqn9mqWJfri8SsN27VS1TCHL3uiJtVjl3886Hb3aaGlptqAZ1qJotS7IdNFu
pcBN4TNnsbp4TQBSDoBquJbgxgN6dtj6vNgTk0ot3bKVHNITWywLzy7WiaSn3BH+
n1hg63rOVvEB/7unKjysUwvXfXwT4Y/q7CdiDRInhAIyZojyG7VvGTpxU1dYjuZm
CRqb4c6Suxd0AOO1MBG257N6uEva5keiAF8FdwdnfzLJddCcV6+SQG0GG0vmg7jn
+3YZT+NiowPYVTnjQJ9oLOFJTTEn6kULHgasoOcHdXP83YG7zX3glbYWxDSqXc7o
jo4cHYbYIJt7PH8mNYZ2N/jTmCYFcTOe9LbXJBbkC9lHk5tarcg=
=0fG/
-END PGP SIGNATURE End Message ---

Bug#978860: marked as done (libquvi: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 17:04:22 +
with message-id 
and subject line Bug#978860: fixed in libquvi 0.9.3-2
has caused the Debian Bug report #978860,
regarding libquvi: ftbfs with autoconf 2.70
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.)


-- 
978860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libquvi
Version: 0.9.3-1.3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/libquvi_0.9.3-1.3_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
exec_prefix='NONE'
glib_CFLAGS=''
glib_LIBS=''
host='x86_64-pc-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libcurl_CFLAGS=''
libcurl_LIBS=''
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
liblua_CFLAGS=''
liblua_LIBS=''
libproxy_CFLAGS=''
libproxy_LIBS=''
libquvi_scripts_CFLAGS=''
libquvi_scripts_LIBS=''
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='${localstatedir}/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target='x86_64-pc-linux-gnu'
target_alias=''
target_cpu='x86_64'
target_os='linux-gnu'
target_vendor='pc'

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "libquvi"
#define PACKAGE_TARNAME "libquvi"
#define PACKAGE_VERSION "0.9.3"
#define PACKAGE_STRING "libquvi 0.9.3"
#define PACKAGE_BUGREPORT "http://quvi.sf.net/bugs/;
#define PACKAGE_URL "http://quvi.sf.net/;
#define BUILD_OPTS "--build=x86_64-linux-gnu
--prefix=/usr
--includedir=${prefix}/include
--mandir=${prefix}/share/man
--infodir=${prefix}/share/info
--sysconfdir=/etc
--localstatedir=/var
--disable-option-checking
--disable-silent-rules
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu
--disable-maintainer-mode
--disable-dependency-tracking"

configure: exit 77
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking returned exit code 77
make: *** [debian/rules:4: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: libquvi
Source-Version: 0.9.3-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
libquvi, 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.
Boyuan Yang  (supplier of updated libquvi 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: Fri, 03 Sep 2021 10:52:08 -0400
Source: libquvi
Architecture: source
Version: 0.9.3-2
Distribution: unstable
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 978860
Changes:
 libquvi (0.9.3-2) unstable; urgency=high
 .
   * QA upload.
   * Orphan package.
   * debian/control: Set Vcs-* fields to git packaging repo on Salsa
 GitLab platform.
   * debian/control: Drop outdated 

Bug#993614: libbloom: Please restrict the valgrind build dependency

[Adrian Bunk]

Source: libbloom
Version: 1.6-4
Severity: serious
Tags: ftbfs

Please add an architecture restriction
[amd64 arm64 armhf i386 mipsel mips64el powerpc ppc64 ppc64el s390x]
to the valgrind build dependency.

This allows building libbloom on architectures without valgrind.

Severity set to RC since the build dependencies no longer being
fulfillable on armel blocks testing migration.

Bug#993612: bugs.debian.org: Socionext SynQuacer fails to mount rootfs after upgrade to Bullseye

[Luca Di Stefano]

Package: bugs.debian.org
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

A few days ago I tried to upgrade one of the six Socionext SynQuacers that we
have to the latest Debian release.

It was running fine on Buster using the 4.19 kernel and had no previous issues.

I followed the normal procedure for updating Debian to the next release:

- apt update; apt upgrade for the current OS and reboot
- changing the release's codename of all apt sources to bullseye
- apt update again
- apt upgrade; apt dist-upgrade
- reboot

The next boot sequence would start and get to the point where it would look for
the rootfs without finding it
and going into initramfs

I've then proceeded to reinstall buster on that machine and it just worked
fine, then also tried installing the kernel from backports linux-
image-5.10.0-0.bpo.8-arm64
 and after reboot it caused the same problem not finding the rootfs and going
into initramfs.

Searching about SynQuacer related issues i found Bug#891787
https://lists.debian.org/debian-kernel/2018/02/msg00348.html
and verified that those options mentioned in the bug report were enabled
correctly in both kernel config file for bullseye and for teh backported
kernel.

Thank you very much.

Luca







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

Kernel: Linux 5.10.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#993514: marked as done (perl/experimental FTBFS with gdbm 1.20)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 16:33:55 +
with message-id 
and subject line Bug#993514: fixed in perl 5.34.0-2
has caused the Debian Bug report #993514,
regarding perl/experimental FTBFS with gdbm 1.20
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.)


-- 
993514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perl
Version: 5.34.0-1
Severity: serious
Tags: ftbfs fixed-upstream
Forwarded: https://github.com/Perl/perl5/issues/18915

https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/perl.html
https://buildd.debian.org/status/package.php?p=perl=experimental

...
Failed 1 test out of 2544, 99.96% okay.
../ext/GDBM_File/t/gdbm.t
...
make[2]: *** [makefile:808: test] Error 1
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.34.0-2
Done: Niko Tyni 

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Aug 2021 22:02:26 +0300
Source: perl
Architecture: source
Version: 5.34.0-2
Distribution: experimental
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Closes: 993514
Changes:
 perl (5.34.0-2) experimental; urgency=medium
 .
   * Apply upstream patch fixing issues with gdbm 1.20. (Closes: #993514)
Checksums-Sha1:
 fddaf7486ba3db1611a32134e2c1b0dfd0b38a70 2886 perl_5.34.0-2.dsc
 2b8a5a7b1f34d12a0e8b405481b7654b5ff4617e 166616 perl_5.34.0-2.debian.tar.xz
 a2a13656565dfd53757228fba3d0b1268d1d2ebe 6291 perl_5.34.0-2_source.buildinfo
Checksums-Sha256:
 037d37b26a472c75610d1d4147737cd790d582ee6b0ebae90e80c94261494988 2886 
perl_5.34.0-2.dsc
 091f04dd26cca1cd82e280ecba407098f3cd2be500fd8367e038cb6498074838 166616 
perl_5.34.0-2.debian.tar.xz
 0e0508eab2ec457c3bf807e2375f68a4895b1f2926a711274e76e4a634abfb6e 6291 
perl_5.34.0-2_source.buildinfo
Files:
 80823ccf8db0fb89b31d434fb779dafc 2886 perl standard perl_5.34.0-2.dsc
 bb3600938adc5033da67b8a636e39fe1 166616 perl standard 
perl_5.34.0-2.debian.tar.xz
 e3cb0407cb8875a5931c59f1be05833c 6291 perl standard 
perl_5.34.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAmEyRV8RHG50eW5pQGRl
Ymlhbi5vcmcACgkQLsD/s7cwGx/I6g/9ENUxt7XQkKnIzN1WH+ahQP290OzumliW
YYOYmhVkFfh4BSYID7OMjQaGbroThARjIleHw/wTRuiYRC0IUf2DkKTSB/6Ojl8f
9yW5jKU+vrtC4zDCMZ3MkiAGdVkb8E+hIPqp+jGHhirVt7Hpwx9VzvgMt/eS2Ah9
lb2nevhAVXdXAys/9x6gVxr904OX+TVL8xOQnX+Dic2afLAsIi2WG13OQDvYf1d0
N4OrcHVvrmMJnPgIjEggJGswRNKTFM3pouyzu+fLJQWHVY4aFR+EZ/hmIoZE9eSQ
gGVn09N4I98PmLM8YHYsH9ZGCcEmJXqJ/9dww9pBM2ktd0ZTr3M6gIcMezn3+sZ3
pZoBGneSpb+QR3Q2eux8BBFjKLE/yisQykpsMWeWvIBBLB8gHbmXw+5sX5OyvPUn
CAdJS3cT7OREf0NWK72S4NPYhWEf05xHVdoUEaLIuAUYo/15jprMrJqX4Fam4j/g
y7OBzoMudvoR6vVPmldcY7Jb8fL3E7b1tb/FmIArUID6OzRq+ymrHzPGdrHv62X7
KvXCrjwdxh84SStnnhGr/ojKg9bA7d6AKapdy+D/cAugM2S92Bmi3bcNvXsAymLs
7tUkS8gFZlfwkgBz546jO2iEZlG4624id6ETksH7qHyF1zZJrXmkDJzuGBlJgJs2
ar3tclIvpW4=
=IbvD
-END PGP SIGNATURE End Message ---

Bug#993611: xrootd FTBFS on 32bit: error: no matching function for call to ‘max(off64_t, uint64_t&)’

[Adrian Bunk]

Source: xrootd
Version: 5.3.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xrootd=5.3.1-1

...
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc: In function ‘ssize_t 
ceph_posix_pwrite(int, const void*, size_t, off64_t)’:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: error: no 
matching function for call to ‘max(off64_t, uint64_t&)’
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
In file included from /usr/include/c++/10/memory:63,
 from 
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:254:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&)’
  254 | max(const _Tp& __a, const _Tp& __b)
  | ^~~
/usr/include/c++/10/bits/stl_algobase.h:254:5: note:   template argument 
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:   
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and 
‘uint64_t’ {aka ‘long long unsigned int’})
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
In file included from /usr/include/c++/10/memory:63,
 from 
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:36:
/usr/include/c++/10/bits/stl_algobase.h:300:5: note: candidate: ‘template constexpr const _Tp& std::max(const _Tp&, const _Tp&, 
_Compare)’
  300 | max(const _Tp& __a, const _Tp& __b, _Compare __comp)
  | ^~~
/usr/include/c++/10/bits/stl_algobase.h:300:5: note:   template argument 
deduction/substitution failed:
/<>/src/XrdCeph/src/XrdCeph/XrdCephPosix.cc:803:97: note:   
deduced conflicting types for parameter ‘const _Tp’ (‘long long int’ and 
‘uint64_t’ {aka ‘long long unsigned int’})
  803 | if (offset + count) fr->maxOffsetWritten = std::max(offset + count 
- 1, fr->maxOffsetWritten);
  | 
^
...

Processed: tagging 993480

[Debian Bug Tracking System]

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

> tags 993480 + sid bookworm
Bug #993480 [gcl] gcl: Fails to install in unstable
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Processed: tagging 993541

[Debian Bug Tracking System]

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

> tags 993541 + sid bookworm
Bug #993541 [src:libbpp-core] libbpp-core FTBFS: symbol differences
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#993560: marked as done (FTBFS on arch-any)

[Debian Bug Tracking System]

Your message dated Fri, 3 Sep 2021 16:14:39 +0200
with message-id <20210903141437.ga3...@shell.thinkmo.de>
and subject line Re: Bug#993560: FTBFS on arch-any
has caused the Debian Bug report #993560,
regarding FTBFS on arch-any
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.)


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

Package: linux
Version: 5.14-1~exp1
Severity: serious

Hi,

unfortunately the 5.14-1~exp1 upload failed to build on all 
architectures (except for 'all').


Regards,
Daniel

---snip---
make[5]: Leaving directory '/<>/tools/perf'
make[4]: Leaving directory '/<>/tools/perf'
rm -f /<>/debian/linux-perf-5.14/usr/bin/trace_5.14
mkdir -p /<>/debian/linux-perf-5.14/usr/share/bash-completion/
mv /<>/debian/linux-perf-5.14/etc/bash_completion.d \

/<>/debian/linux-perf-5.14/usr/share/bash-completion/completions
rmdir --ignore-fail-on-non-empty /<>/debian/linux-perf-5.14/etc
cd /<>/debian/linux-perf-5.14 && ! find \! -type d \! -path 
'*[_-]5.14*' | grep .

./usr/include/perf/perf_dlfilter.h
make[3]: *** [/<>/debian/rules.d/tools/perf/Makefile:57: 
install] Error 1
make[3]: Leaving directory 
'/<>/debian/build/build-tools/tools/perf'

make[2]: *** [debian/rules.real:730: install-perf] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules.gen:34: binary-arch_amd64_real] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:43: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned 
exit status 2

---snap---
--- End Message ---
--- Begin Message ---
> unfortunately the 5.14-1~exp1 upload failed to build on all architectures
> (except for 'all').

Yes, we know.

Bastian

-- 
You're dead, Jim.
-- McCoy, "Amok Time", stardate 3372.7--- End Message ---

Bug#952950: nss: Replace PKCS11 headers provided by OASIS

[Bastian Germann]

Control: severity -1 normal

On Thu, 1 Apr 2021 23:48:51 +0200 Timo Röhling  wrote:

On Tue, 23 Mar 2021 00:44:07 +0100 Bastian Germann  
wrote:
> As far as I can see, the license for NSS's PKCS#11 headers is MPL 2.0
> (DFSG-free) and not the OASIS IPR.
Well, I can see from the discussion you linked that the OASIS IPR
license is intended to apply to their work products, and not the shared
code. And they do have separate rules for their open repositories, which
default to BSD-3-Clause license unless stated otherwise [1].

However, the PKCS#11 repository [2] is not in the linked "oasis-open"
namespace on Github, there is an explicit reference to the IPR
license in that repository.

As for the MPL 2.0 license, the Mozilla upstream added that to their
version of the headers after stating that bug 1618918 had clarified the
situation, but I can't seem to access that bug [3].

Cheers
Timo

[1] https://www.oasis-open.org/open-repositories/#licensingRules
[2] https://github.com/oasis-tcs/pkcs11
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1618918


The nss PKCS#11 files have a different provenance from the OASIS ones. If Mozilla decides to license 
them as MPL 2.0, that is their choice. They have a legal department who was involved and decided 
they go this way. The point is, the license of the files is not the OASIS one as suggested by the 
bug submitter, so the bug is invalid. I do not think the license was OASIS in any of the public NSS 
releases, even though it might have been in some patch submission.

Processed: Re: nss: Replace PKCS11 headers provided by OASIS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #952950 [src:nss] nss: Replace PKCS11 headers provided by OASIS
Severity set to 'normal' from 'serious'

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

Bug#993164: marked as done (proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails)

[Debian Bug Tracking System]

Your message dated Fri, 3 Sep 2021 14:39:27 +0200
with message-id <328cf4fa-39df-dd62-4cee-80ee19130...@web.de>
and subject line Re: Bug#993164: proftpd-core: When upgrading from Buster to 
Bullseyes, the installation of ProFTPd fails
has caused the Debian Bug report #993164,
regarding proftpd-core: When upgrading from Buster to Bullseyes, the 
installation of ProFTPd fails
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.)


-- 
993164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-core
Version: 1.3.7a+dfsg-12
Severity: serious
Justification: 1

Dear Maintainer,

   This error occurred for the first time when upgrading the system from Buster 
to Bullseye:
   dpkg: Fehler beim Bearbeiten des Paketes proftpd-mod-crypto (--configure):
   Abhängigkeitsprobleme - verbleibt unkonfiguriert
   dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proftpd-mod-wrap:
   proftpd-mod-wrap hängt ab von proftpd-core (= 1.3.7a+dfsg-12); aber:
   Paket proftpd-core ist noch nicht konfiguriert.
   .
   .
   Fehler traten auf beim Bearbeiten von:
proftpd-core
proftpd-mod-crypto
proftpd-mod-wrap
proftpd-basic

   Then I deleted all the packages involved and tried to reinstall them with 
the same result:
dpkg --remove proftpd-basic proftpd-core proftpd-mod-crypto proftpd-mod-wrap
apt install proftpd-core proftpd-basic proftpd-mod-crypto proftpd-mod-wrap
   
   After deleting all packages again, I only installed proftpd-core:
apt install proftpd-core

   See "systemctl status proftpd.service" and "journalctl -xe" for details.
   dpkg: Fehler beim Bearbeiten des Paketes proftpd-core (--configure):
 »installiertes proftpd-core-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
   Fehler traten auf beim Bearbeiten von:
   proftpd-core
   
   The package obviously cannot be installed due to the proftpd-core script.
   
   My expectation of you would be to make ProFTPd installable.

   Best regards
   Andreas Günther


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 proftpd-core depends on:
ii  adduser  3.118
ii  debianutils  4.11.2
ii  init-system-helpers  1.60
ii  libacl1  2.2.53-10
ii  libc62.31-13
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-4
ii  libhiredis0.14   0.14.1-1
ii  libmemcached11   1.0.18-4.2
ii  libmemcachedutil21.0.18-4.2
ii  libncursesw6 6.2+20201114-2
ii  libpam-runtime   1.4.0-9
ii  libpam0g 1.4.0-9
ii  libpcre3 2:8.39-13
ii  libssl1.11.1.1k-1
ii  libtinfo66.2+20201114-2
ii  lsb-base 11.1.0
ii  netbase  6.3
ii  sed  4.7-1
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages proftpd-core recommends:
ii  proftpd-doc  1.3.7a+dfsg-12

Versions of packages proftpd-core suggests:
pn  openbsd-inetd | inet-superserver  
ii  openssl   1.1.1k-1
pn  proftpd-mod-crypto
pn  proftpd-mod-geoip 
pn  proftpd-mod-ldap  
pn  proftpd-mod-mysql 
pn  proftpd-mod-odbc  
pn  proftpd-mod-pgsql 
pn  proftpd-mod-snmp  
pn  proftpd-mod-sqlite
pn  proftpd-mod-wrap  

-- Configuration Files:
/etc/logrotate.d/proftpd-core changed:
/var/log/proftpd/proftpd.log 
/var/log/proftpd/controls.log 
/var/log/proftpd/tls.log
/var/log/proftpd/sftp.log
{
weekly
missingok
rotate 7
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
postrotate
# reload could be not sufficient for all logs, a restart is 
safer
invoke-rc.d proftpd restart 2>/dev/null >/dev/null || true
endscript
}
/var/log/proftpd/xferlog
/var/log/proftpd/xferreport
{
monthly
missingok
rotate 7
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
prerotate
endscript
postrotate
# reload 

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Hilmar Preuße]

Am 31.08.2021 um 12:53 teilte Andreas Günther mit:

Hi Andreas,


but I realized that now. The whole time the installer was bothered by a line
in "/etc/proftpd/proftpd.conf", namely "IdentLookups off". I commented on this
line and thus everything could be reinstalled and started successfully.


Hmmm. In proftpd-dfsg (1.3.7a-2) I did:

  * Enclose "IdentLookups off" in  in 
sample

configuration.

According to https://github.com/proftpd/proftpd/issues/677 .


Best regards and thank you very much


Can we close the case now?

Hilmar
--
sigfault




OpenPGP_signature
Description: OpenPGP digital signature

Bug#993164: proftpd-core: When upgrading from Buster to Bullseyes, the installation of ProFTPd fails

[Andreas Günther]

Am Freitag, 3. September 2021, 14:36:27 CEST schrieb Hilmar Preuße:
> 
> Can we close the case now?
> 
> Hilmar

Yes, we can!

Andreas

Bug#990528: marked as done (ndpi: CVE-2021-36082)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 11:00:10 +
with message-id 
and subject line Bug#990528: fixed in ndpi 4.0-1
has caused the Debian Bug report #990528,
regarding ndpi: CVE-2021-36082
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.)


-- 
990528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndpi
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ndpi.

CVE-2021-36082[0]:
| ntop nDPI 3.4 has a stack-based buffer overflow in
| processClientServerHello.

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=30393
https://github.com/google/oss-fuzz-vulns/blob/main/vulns/ndpi/OSV-2021-304.yaml
https://github.com/ntop/nDPI/commit/1ec621c85b9411cc611652fd57a892cfef478af3


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-36082
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36082

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: ndpi
Source-Version: 4.0-1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated ndpi 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 27 Aug 2021 14:04:41 +0200
Source: ndpi
Binary: libndpi-bin libndpi-bin-dbgsym libndpi-dev libndpi-wireshark libndpi4.0 
libndpi4.0-dbgsym
Architecture: source amd64
Version: 4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Gianfranco Costamagna 
Description:
 libndpi-bin - extensible deep packet inspection library - ndpiReader
 libndpi-dev - extensible deep packet inspection library - development files
 libndpi-wireshark - extensible deep packet inspection library - wireshark 
dissector
 libndpi4.0 - extensible deep packet inspection library - shared library
Closes: 990528
Changes:
 ndpi (4.0-1) unstable; urgency=medium
 .
   * New upstream version 4.0
 - CVE-2021-36082 Closes: #990528
   * Refresh patches
   * bump somane from 3.4 to 4.0 and refresh symbols
   * update copyright file
   * add patch to force usage of system uthash
Checksums-Sha1:
 9368ab2cc4cc68b53cece39dbcf70990ef20972c 2105 ndpi_4.0-1.dsc
 ed8837de7b061ed6c03862f77e1901c3596c9d5e 120053617 ndpi_4.0.orig.tar.gz
 d000afa180d0c13e80163d21007a19ea03a3ea71 14760 ndpi_4.0-1.debian.tar.xz
 38f366c70d5c2c898565553c718a2fb4cb5b9a8c 163604 
libndpi-bin-dbgsym_4.0-1_amd64.deb
 856f1ca4c0d5d23ef3bdcacf3573888e9a4a7da6 70972 libndpi-bin_4.0-1_amd64.deb
 0f70ffad100b2be318260e01db500161726910c3 401512 libndpi-dev_4.0-1_amd64.deb
 6d9862debe65f3235870aaa8a8a37710d552f7ec 26824 
libndpi-wireshark_4.0-1_amd64.deb
 cba321fcb178c4db0c464e76af0f5c2ecd3a6dc5 557392 
libndpi4.0-dbgsym_4.0-1_amd64.deb
 6c801a02b712686a7b0a4441def96c963ebaaa1c 313076 libndpi4.0_4.0-1_amd64.deb
 3c0ae89639545895b23836c856460ecb1e01b6d1 8281 ndpi_4.0-1_amd64.buildinfo
Checksums-Sha256:
 3ee0cda773aa1d65661af91b1c318444c855c60218f4a71f556ebde675d714e9 2105 
ndpi_4.0-1.dsc
 99e0aba6396fd633c3840f30e4942f6591a08066d037f560b65ba64e7310f4d6 120053617 
ndpi_4.0.orig.tar.gz
 b0e318a5c86ccd7deba1ad1e0f4711ea31e5f20f3558b3ede675dca4320021b1 14760 
ndpi_4.0-1.debian.tar.xz
 1f4c2b16d6b4965c8209db5b0c7d0cc5130cd6ba517dfc6df26761078fa24992 163604 
libndpi-bin-dbgsym_4.0-1_amd64.deb
 180f336463d8cabc77c1b4b24a422368fcd94fbc766371d44a137f1dfec236cd 70972 
libndpi-bin_4.0-1_amd64.deb
 8b721104512175cc597b1ebd4b5c6d7df589ab995f07e182c91276ddb1245a3e 401512 
libndpi-dev_4.0-1_amd64.deb
 ef614cd42bb8bc7540412554d9bc82a4fd3277c3f5ec46195ff3a34f5c06b00c 26824 
libndpi-wireshark_4.0-1_amd64.deb
 f1f0eb4d3d3db5fd8099d2fa0d0b89c1d36897bbab6dbd2c266f77fa372bcc50 557392 
libndpi4.0-dbgsym_4.0-1_amd64.deb
 

Bug#978766: marked as done (aprx: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 10:18:43 +
with message-id 
and subject line Bug#978766: fixed in aprx 2.9.0+dfsg-5
has caused the Debian Bug report #978766,
regarding aprx: ftbfs with autoconf 2.70
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.)


-- 
978766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aprx
Version: 2.9.0+dfsg-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/aprx_2.9.0+dfsg-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
LD='gcc'
LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,--as-needed'
LIBCRYPTO=''
LIBGETADDRINFO=''
LIBM=''
LIBOBJS=''
LIBPTHREAD=''
LIBRESOLV=''
LIBRT=''
LIBS=''
LIBSOCKET=''
LIBSSL=''
LTLIBOBJS=''
OBJEXT='o'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_URL=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
SET_MAKE=''
SHELL='/bin/bash'
VERSION_STRING=''
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build_alias='x86_64-linux-gnu'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE}'
dvidir='${docdir}'
exec_prefix='NONE'
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='/usr/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='/usr/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""

configure: exit 2
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --with-pthread 
--sbindir=/usr/sbin --sysconfdir=/etc --localstatedir=/var 
--mandir=/usr/share/man returned exit code 2
make[1]: *** [debian/rules:25: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: aprx
Source-Version: 2.9.0+dfsg-5
Done: Christoph Berg 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Sep 2021 12:04:27 +0200
Source: aprx
Architecture: source
Version: 2.9.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Christoph Berg 
Closes: 978766 990609
Changes:
 aprx (2.9.0+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Dave Hibberd ]
   * Bump dh to 13
   * Remove colint from uploaders, thanks for all your work
 - Closes: #990609
   * Bump standards to 4.6.0.0
   * Added hardening flags to d/rules
 - 

Processed: Bug#978766 marked as pending in aprx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978766 [src:aprx] aprx: ftbfs with autoconf 2.70
Added tag(s) pending.

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

Bug#978766: marked as pending in aprx

[Christoph Berg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/aprx/-/commit/d6f17dc27826210839f9e23a3c6bdc36d1b29321


Fix FTBFS with autoconf 2.70. (Closes: #978766)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978766

Bug#993503: marked as done (gcc-11-base: coinstallation error for mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 3 Sep 2021 10:35:25 +0200
with message-id <0caa770a-4c17-88d4-63ad-8e7cfffab...@debian.org>
and subject line fixed in 11.2.0-4
has caused the Debian Bug report #993503,
regarding gcc-11-base: coinstallation error for mipsel
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.)


-- 
993503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-11-base
Version: 11.2.0-3
Severity: serious
Justification: dpkg unpack error

gcc-11-base's changelog.Debian.gz is different on mipsel than everywhere
else. Indeed, the version is duplicate in the changelog. As such,
gcc-11-base:mipsel fails to coinstall with everything else despite being
marked Multi-Arch: same.

| Unpacking gcc-11-base:mipsel (11.2.0-3) ...
| dpkg: error processing archive 
/tmp/apt-dpkg-install-kpSb1U/012-gcc-11-base_11.2.0-3_mipsel.deb (--unpack):
|  trying to overwrite shared '/usr/share/doc/gcc-11-base/changelog.Debian.gz', 
which is different from other instances of package gcc-11-base:mipsel

The cause seems to be a binary upload. Any normal upload should fix this
issue without further changes.

Helmut
--- End Message ---
--- Begin Message ---
Version: 11.2.0-4--- End Message ---

Bug#991111: marked as done (python3.10: Please exclude test_concurrent_futures also on armhf and alpha)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 07:50:15 +
with message-id 
and subject line Bug#99: fixed in python3.10 3.10.0~rc1-2
has caused the Debian Bug report #99,
regarding python3.10: Please exclude test_concurrent_futures also on armhf and 
alpha
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.)


-- 
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.9
Severity: important
Tags: patch ftbfs
Control: clone -1 -2
Control: reassign -2 python3.10
Control: retitle -2 python3.10: Please exclude test_concurrent_futures also on 
alpha

test_concurrent_futures frequently hangs during the build on alpha:

https://buildd.debian.org/status/package.php?p=python3.9=experimental
https://buildd.debian.org/status/logs.php?pkg=python3.9=alpha

...
23:57:55 load avg: 0.00 running: test_concurrent_futures (23 hour 51 min)
...


Workaround:

--- python3.9-3.9.6/debian/rules.old2021-07-14 14:46:00.200490919 +
+++ python3.9-3.9.6/debian/rules2021-07-14 14:46:18.848548468 +
@@ -542,7 +542,7 @@
   TEST_EXCLUDES += test_gdb
 endif
 
-ifneq (,$(filter $(DEB_HOST_ARCH), riscv64))
+ifneq (,$(filter $(DEB_HOST_ARCH), alpha riscv64))
   TEST_EXCLUDES += test_concurrent_futures
 endif
 
--- End Message ---
--- Begin Message ---
Source: python3.10
Source-Version: 3.10.0~rc1-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.10 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Sep 2021 09:33:09 +0200
Source: python3.10
Architecture: source
Version: 3.10.0~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 99
Changes:
 python3.10 (3.10.0~rc1-2) unstable; urgency=medium
 .
   * Fix path to mkdir on a unified-/usr system. Addresses: #992775.
   * Use command -v instead of which in shell scripts.
   * Also don't run the test_concurrent_futures test on armhf and sparc64.
 Closes: #99.
Checksums-Sha1:
 490bb56b6c6f441ba2801ab8af8e8bea35732824 3537 python3.10_3.10.0~rc1-2.dsc
 44ca541ddd77535218358d7f4c7f05f5f01e1946 213564 
python3.10_3.10.0~rc1-2.debian.tar.xz
 6252ae44c466c7523382391fdfbbbf62906ebb75 10175 
python3.10_3.10.0~rc1-2_source.buildinfo
Checksums-Sha256:
 41433e98b604887d6cbf20d6a90f5f119d754cd87246b7be538fb0f9df7c3da9 3537 
python3.10_3.10.0~rc1-2.dsc
 47d0388b3d7b42b41c8faf688c4f83ba8dd95429491a704f200e6d23438f998c 213564 
python3.10_3.10.0~rc1-2.debian.tar.xz
 cc68cfa44cf272e7f2574a7ac21d0d8a3b398958cc5e31ec9d472a1ef0e6c391 10175 
python3.10_3.10.0~rc1-2_source.buildinfo
Files:
 7a05e293aa6368ad2d4f6f22c3130342 3537 python optional 
python3.10_3.10.0~rc1-2.dsc
 900d6155ac5642728b8da0937c98aa11 213564 python optional 
python3.10_3.10.0~rc1-2.debian.tar.xz
 857a227a750d3a391d8a0ffb6bdd6e6a 10175 python optional 
python3.10_3.10.0~rc1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmEx0OEQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9c6sEACrV1s7TvVHqyjZvMW+Y3J/WN14ajEPUlA7
8hSp34jT/y5/a7QG88Qe94HcqVkzF+QcvkLqAz3g1LNofA7Q8wzEYI1sbSbhq3kY
APQYOn/t5AtLKQJGjynXSUUyzLQ8UJPGuFcAwzgXfk0eNItfnbnkdDvBDHteNzyo
LX4QR6SfZok6wYwPrNohkZHVfRDH9XutIi8ZSj2eNf3EGWl4Ps3KSOr8BsbZYLio
q68QDzNX+0bzPHn000fA6rcwq7Lq0kW9/OZnBMBfn1iqaZKVk0JiAqjhgx+1CVTm
5QPMi8Ymb0VSkpl9oHOfK9EN1bzIGUaRyOTcUDkFvzVdSqHnDVt6oA2pqozcNZVw
ENJpyo9spKrd4Dbbw+GIUGUp7MzagNPaVhcef3ue6/H1qxCQYjb+uMk9ixQ/hNlF
+4lQxQb5XI7HS/eqkJOF6l7DtLejmjD4MSaLdQXrnZu1H3cVqYl2JCDHC+En0zNG
aiGxkWdwCUAguwvwl2J0+MTfy4ehw2cMYRIeQEavr/J11Xm5zQdv4adqi2MXZgOZ
QZijJYNFggqEIu0vxy5WgWTy5N+NkNoufduEwQkiJj+SYBYVAltKoCIGN6npPdrc
6jNbqnI5Gq0fPu4lbCOg3UmK7IFsp5l3HIX9opfRT6nM/qqth73AVFAvQq6X1jlf
dUEWXToWng==
=c6Ms
-END PGP SIGNATURE End Message ---

Bug#991110: marked as done (python3.9: Please exclude test_concurrent_futures also on armhf and alpha)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 06:49:04 +
with message-id 
and subject line Bug#991110: fixed in python3.9 3.9.7-2
has caused the Debian Bug report #991110,
regarding python3.9: Please exclude test_concurrent_futures also on armhf and 
alpha
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.)


-- 
991110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3.9
Severity: important
Tags: patch ftbfs
Control: clone -1 -2
Control: reassign -2 python3.10
Control: retitle -2 python3.10: Please exclude test_concurrent_futures also on 
alpha

test_concurrent_futures frequently hangs during the build on alpha:

https://buildd.debian.org/status/package.php?p=python3.9=experimental
https://buildd.debian.org/status/logs.php?pkg=python3.9=alpha

...
23:57:55 load avg: 0.00 running: test_concurrent_futures (23 hour 51 min)
...


Workaround:

--- python3.9-3.9.6/debian/rules.old2021-07-14 14:46:00.200490919 +
+++ python3.9-3.9.6/debian/rules2021-07-14 14:46:18.848548468 +
@@ -542,7 +542,7 @@
   TEST_EXCLUDES += test_gdb
 endif
 
-ifneq (,$(filter $(DEB_HOST_ARCH), riscv64))
+ifneq (,$(filter $(DEB_HOST_ARCH), alpha riscv64))
   TEST_EXCLUDES += test_concurrent_futures
 endif
 
--- End Message ---
--- Begin Message ---
Source: python3.9
Source-Version: 3.9.7-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3.9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Sep 2021 08:18:44 +0200
Source: python3.9
Architecture: source
Version: 3.9.7-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 989000 991110 992091 992669 992775 993413
Changes:
 python3.9 (3.9.7-2) unstable; urgency=medium
 .
   * Fix CFLAGS in the python3.x-config scripts. Closes: #992669, #989000.
   * Support arc-linux-gnu in the multiarch header. Closes: #992091.
   * Don't run the test_concurrent_futures test on alpha and sparc64.
 Closes: #991110.
   * Fix path to mkdir on a unified-/usr system. Closes: #992775.
   * Use command -v instead of which in shell scripts. Closes: #993413.
Checksums-Sha1:
 17ef1d15102029c66744acb83eac93c1bfdb4165 3493 python3.9_3.9.7-2.dsc
 f011a4231b2d6d51af4f70f5e838491a9c6ce38c 212164 python3.9_3.9.7-2.debian.tar.xz
 bb3310ec52ac37947e13658074daa864dda59b15 10182 
python3.9_3.9.7-2_source.buildinfo
Checksums-Sha256:
 7b14f5d79bd3a33ff2ffac479655416b139222a18e7e93b6afe6b69b4821ec4b 3493 
python3.9_3.9.7-2.dsc
 80e2be75e2b1e7553a828a8c45d27852e4b054375875b7408e99669e75e3c937 212164 
python3.9_3.9.7-2.debian.tar.xz
 7e9345550c51e9a6a7bac60ef49831fafa0422e7bcbaf74915f10375aca5c741 10182 
python3.9_3.9.7-2_source.buildinfo
Files:
 15f1c468a2eb2d25e6157efaf69eb8b0 3493 python optional python3.9_3.9.7-2.dsc
 751091f441daa0a73fbaddff5a9a2875 212164 python optional 
python3.9_3.9.7-2.debian.tar.xz
 8a40b4a4126fd3e8fff876403d3d2803 10182 python optional 
python3.9_3.9.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmExwG8QHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9QGnEACjGY7FIq519X9/41eagYOofuSWhuvEW5hn
5MaS+TE09oKuUoJEXZ8xqwxI+cyUOW3jtNNC0kfqWuoTPrvMWNbhZpeLZIIYCn8Q
+dHOsc8zmjl0U2uyFjF2EIWk9JoE/RJswjRueeP1lAusZ2lY6fpLXkihKldizOmj
1gNlEDSxjDPeKFvD625ijN92yZBi3qM4yqxZH1MdUPRLYEkVRxHv8FOjvUhebxhp
EvIOVCQEJD4pi5KzrAsDYaGpaw6dfuqDmOyDw2l7WR1oev6DfjGSJh18O5kswBkb
aVCLt2Zpm24HTyw0KAkX7gh8WO2JKN1nNMqWDSsN8w5XM7U988yLPFL6XhpARN3V
bgL5QmiBNtjQwA1NiszzDrw+CHkwMdnnB1LZG+hFZpsyOrNPHGGBuqKE+ZoUfcz4
w+tVzoZgvh5eC2CVVCTikvQQjeOAi8Hqs/WM8T4n6gBY2GO21Pxhm9C8OlbcIk7Y
TCc7uCqa8ClRoFq/S+P5F6bDEQo9RYwppWTJVtixS0xOTPfaab7pPa4HIQ4+7VLq
T4g4SIPUIex5BgH7nNlF8M/I7xaXGRepzyM+yFgcUAU2InvRvefbqG7+pPOlDG8v
p9mzVV7sU1NFf0Ocxhf8N7DjZ5G9CdFW+kkUo9AVvMYO0VAESKSOSYHkNC/Ryq5B
NWKnv2vH1Q==
=QBOs
-END PGP SIGNATURE End Message ---

Bug#978823: marked as done (gnome-icon-theme: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Fri, 03 Sep 2021 06:48:46 +
with message-id 
and subject line Bug#978823: fixed in gnome-icon-theme 3.12.0-4
has caused the Debian Bug report #978823,
regarding gnome-icon-theme: ftbfs with autoconf 2.70
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.)


-- 
978823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnome-icon-theme
Version: 3.12.0-3
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/gnome-icon-theme_3.12.0-3_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
Setting up icon mapping for: actions
Setting up icon mapping for: emotes
Setting up icon mapping for: apps
Setting up icon mapping for: categories
Setting up icon mapping for: devices
Setting up icon mapping for: status
Setting up icon mapping for: mimetypes
Setting up icon mapping for: places
Setting up icon mapping for: emblems
Going to set up icon mapping for 48x48
Setting up icon mapping for: animations
Setting up icon mapping for: actions
Setting up icon mapping for: emotes
Setting up icon mapping for: apps
Setting up icon mapping for: categories
Setting up icon mapping for: devices
Setting up icon mapping for: status
Setting up icon mapping for: mimetypes
Setting up icon mapping for: places
Setting up icon mapping for: emblems
Going to set up icon mapping for 256x256
Setting up icon mapping for: actions
Setting up icon mapping for: emotes
Setting up icon mapping for: apps
Setting up icon mapping for: categories
Setting up icon mapping for: devices
Setting up icon mapping for: status
Setting up icon mapping for: mimetypes
Setting up icon mapping for: places
Setting up icon mapping for: emblems
make[3]: Leaving directory '/<>/src'
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
make[3]: Nothing to be done for 'install-exec-am'.
make -C po uninstall
 /bin/mkdir -p '/<>/debian/gnome-icon-theme/usr/share/pkgconfig'
make[4]: Entering directory '/<>/po'
 /bin/mkdir -p '/<>/debian/gnome-icon-theme/usr/share/icons/gnome'
 /usr/bin/install -c -m 644 gnome-icon-theme.pc 
'/<>/debian/gnome-icon-theme/usr/share/pkgconfig'
 /usr/bin/install -c -m 644 index.theme 
'/<>/debian/gnome-icon-theme/usr/share/icons/gnome'
linguas="af am an ar as ast az be be@latin bg bn bn_IN br bs ca ca@valencia crh 
cs csb cy da de dz el en_CA en_GB en@shaw eo es et eu fa fi fr fur fy ga gd gl 
gu he hi hr hu id is it ja ka kk km kn ko ku li lt lv mai mg mk ml mn mr ms nb 
nds ne nhn nl nn oc or pa pl ps pt pt_BR ro ru rw si sk sl sq sr sr@latin sv ta 
te tg th tk tr ug uk uz uz@cyrillic vi wa xh zh_CN zh_HK zh_TW "; \
for lang in $linguas; do \
  rm -f 
/<>/debian/gnome-icon-theme/usr//locale/$lang/LC_MESSAGES/gnome-icon-theme.mo;
 \
  rm -f 
/<>/debian/gnome-icon-theme/usr//locale/$lang/LC_MESSAGES/gnome-icon-theme.mo.m;
 \
done
make[4]: Leaving directory '/<>/po'
if [ -h /<>/debian/gnome-icon-theme/usr/share/icons/gnome ]; then \
rm -f /<>/debian/gnome-icon-theme/usr/share/icons/gnome; \
fi
if [ -d /<>/debian/gnome-icon-theme/usr/share/icons/gnome ]; then \
touch /<>/debian/gnome-icon-theme/usr/share/icons/gnome; \
fi
make  install-data-hook
make[4]: Entering directory '/<>'
if test -z "/<>/debian/gnome-icon-theme" ; then \
/usr/bin/gtk-update-icon-cache -q 
/<>/debian/gnome-icon-theme/usr/share/icons/gnome; \
fi
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
rm -r debian/gnome-icon-theme/usr/share/locale
rm: cannot remove 'debian/gnome-icon-theme/usr/share/locale': No such file or 
directory
make[1]: *** [debian/rules:15: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
--- End Message ---
--- Begin 

Processed: Re: dlt-viewer: missing .h files in dev package

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 2.21.2+dfsg-2
Bug #993562 {Done: Gianfranco Costamagna } 
[src:dlt-viewer] dlt-viewer: missing .h files in dev package
No longer marked as fixed in versions dlt-viewer/2.21.2+dfsg-2.
> fixed -1 2.21.2+dfsg-3
Bug #993562 {Done: Gianfranco Costamagna } 
[src:dlt-viewer] dlt-viewer: missing .h files in dev package
Marked as fixed in versions dlt-viewer/2.21.2+dfsg-3.
> close -1
Bug #993562 {Done: Gianfranco Costamagna } 
[src:dlt-viewer] dlt-viewer: missing .h files in dev package
Bug 993562 is already marked as done; not doing anything.

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

Bug#993562: dlt-viewer: missing .h files in dev package

[Gianfranco Costamagna]

control: notfixed -1 2.21.2+dfsg-2
control: fixed -1 2.21.2+dfsg-3
control: close -1

On Fri, 3 Sep 2021 08:38:16 +0200 Gianfranco Costamagna 
 wrote:
> On Fri, 3 Sep 2021 08:33:27 +0200 Gianfranco Costamagna 
>  wrote:
> > Source: dlt-viewer
> > version: 2.21.2+dfsg-2
> > severity: serious
> > tags: patch
> > 
> > Hello, looks like the version -2 of the package was missing lots of .h 
> > header files leading to an
> > impossibility to compile any plugin with it.
> > I fixed this in the -3 version in sid, and I would like to propose a 
> > stable-update
> > 
> > Gianfranco
> > 
> > 
> 
> 

Processed: Re: dlt-viewer: missing .h files in dev package

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.21.2+dfsg-2
Bug #993562 [src:dlt-viewer] dlt-viewer: missing .h files in dev package
Marked as fixed in versions dlt-viewer/2.21.2+dfsg-2.
> close -1
Bug #993562 [src:dlt-viewer] dlt-viewer: missing .h files in dev package
Marked Bug as done

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

Bug#993562: dlt-viewer: missing .h files in dev package

[Gianfranco Costamagna]

control: fixed -1 2.21.2+dfsg-2
control: close -1
On Fri, 3 Sep 2021 08:33:27 +0200 Gianfranco Costamagna 
 wrote:
> Source: dlt-viewer
> version: 2.21.2+dfsg-2
> severity: serious
> tags: patch
> 
> Hello, looks like the version -2 of the package was missing lots of .h header 
> files leading to an
> impossibility to compile any plugin with it.
> I fixed this in the -3 version in sid, and I would like to propose a 
> stable-update
> 
> Gianfranco
> 
> 

Bug#993562: dlt-viewer: missing .h files in dev package

[Gianfranco Costamagna]

Source: dlt-viewer
version: 2.21.2+dfsg-2
severity: serious
tags: patch

Hello, looks like the version -2 of the package was missing lots of .h header 
files leading to an
impossibility to compile any plugin with it.
I fixed this in the -3 version in sid, and I would like to propose a 
stable-update

Gianfranco

Processed: saods9 <-- tcl-signal

[Debian Bug Tracking System]

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

> reassign 993547 saods9 8.3~b1+repack-1
Bug #993547 [tcl-signal] saods9: Error in startup script
Bug reassigned from package 'tcl-signal' to 'saods9'.
No longer marked as found in versions tcl-signal/1.4.4.1-1.
Ignoring request to alter fixed versions of bug #993547 to the same values 
previously set
Bug #993547 [saods9] saods9: Error in startup script
Marked as found in versions saods9/8.3~b1+repack-1.
> thanks
Stopping processing here.

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