Processed: found 979672 in 390.138-6
Processing commands for cont...@bugs.debian.org:
> found 979672 390.138-6
Bug #979672 {Done: Andreas Beckmann }
[src:nvidia-graphics-drivers-legacy-390xx]
nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056
Marked as found in versions nvidia-graphics-drivers-legacy-390xx/390.138-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#962203: marked as done (DeprecationWarning: isAlive() is deprecated, use is_alive() instead)
Your message dated Sun, 10 Jan 2021 06:19:37 +
with message-id
and subject line Bug#962203: fixed in debdelta 0.65+nmu1
has caused the Debian Bug report #962203,
regarding DeprecationWarning: isAlive() is deprecated, use is_alive() instead
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
962203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdelta
Version: 0.65
Severity: normal
Hi!
It seems that something needs to be update in debdelta:
=
# debdelta-upgrade
Created,time 0.15sec, speed 151kB/sec, libmtdev1_1.1.6-1_amd64.deb
Downloaded, time 0.47sec, speed 83kB/sec,
libcryptsetup12_2%3a2.3.2-1_2%3a2.3.3-1_amd64.debdelta
Created,time 0.33sec, speed 709kB/sec,
libcryptsetup12_2%3a2.3.3-1_amd64.deb
Downloaded, time 0.41sec, speed 104kB/sec,
calibre-bin_4.99.4+dfsg+really4.17.0-1_4.99.4+dfsg+really4.17.0-1+b1_amd64.debdelta
Created,time 2.09sec, speed 375kB/sec,
calibre-bin_4.99.4+dfsg+really4.17.0-1+b1_amd64.deb
Downloaded, time 2.38sec, speed 206kB/sec,
libqt5gui5_5.12.5+dfsg-10_5.12.5+dfsg-10+b1_amd64.debdelta
/usr/bin/debdelta-upgrade:5384: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
if patching_thread.isAlive() and no_delta and VERBOSE > 1 :
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
Created,time 6.01sec, speed 484kB/sec,
libqt5gui5_5.12.5+dfsg-10+b1_amd64.deb
/usr/bin/debdelta-upgrade:5405: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive():
/usr/bin/debdelta-upgrade:5410: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while progress_thread != None and progress_thread.isAlive():
Delta-upgrade statistics:
total resulting debs, size 3956kB time 11sec virtual speed 340kB/sec
=
Thank you!
Best regards,
Nelson
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debdelta depends on:
ii binutils 2.34-8
ii bzip2 1.0.8-3
ii libbz2-1.01.0.8-3
ii libc6 2.30-8
ii python3 3.8.2-3
ii python3-requests 2.23.0+dfsg-2
ii zlib1g1:1.2.11.dfsg-2
Versions of packages debdelta recommends:
ii bsdiff 4.3-21+b1
ii gnupg-agent 2.2.20-1
ii gnupg2 2.2.20-1
ii gpg-agent [gnupg-agent] 2.2.20-1
ii python3-apt 2.1.3
ii python3-debian 0.1.37
pn xdelta
ii xdelta3 3.0.11-dfsg-1+b1
ii xz-utils [lzma] 5.2.4-1+b1
Versions of packages debdelta suggests:
pn debdelta-doc
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debdelta
Source-Version: 0.65+nmu1
Done: Calum McConnell
We believe that the bug you reported is fixed in the latest version of
debdelta, 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 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Calum McConnell (supplier of updated debdelta
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, 01 Jan 2021 17:15:42 -0500
Source: debdelta
Architecture: source
Version: 0.65+nmu1
Distribution: unstable
Urgency: high
Maintainer: A Mennucc1
Changed-By: Calum McConnell
Closes: 954420 962203
Changes:
debdelta (0.65+nmu1) unstable; urgency=high
.
* Non-maintainer upload.
* Fix
Bug#954420: marked as done (Python deprecation warning)
Your message dated Sun, 10 Jan 2021 06:19:37 +
with message-id
and subject line Bug#962203: fixed in debdelta 0.65+nmu1
has caused the Debian Bug report #962203,
regarding Python deprecation warning
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.)
--
962203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdelta
Version: 0.65
Severity: minor
There's a new deprecation warning that popped up recently:
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debdelta depends on:
ii binutils 2.34-5
ii bzip2 1.0.8-2
ii libbz2-1.01.0.8-2
ii libc6 2.30-2
ii python3 3.8.2-1
ii python3-requests 2.22.0-2
ii zlib1g1:1.2.11.dfsg-2
Versions of packages debdelta recommends:
ii bsdiff 4.3-21+b1
pn gnupg2
ii gpg-agent [gnupg-agent] 2.2.19-3
ii python3-apt 1.9.10
ii python3-debian 0.1.36
ii xdelta 1.1.3-9.3
ii xdelta3 3.0.11-dfsg-1+b1
ii xz-utils [lzma] 5.2.4-1+b1
Versions of packages debdelta suggests:
pn debdelta-doc
-- Configuration Files:
/etc/debdelta/sources.conf changed [not included]
--- End Message ---
--- Begin Message ---
Source: debdelta
Source-Version: 0.65+nmu1
Done: Calum McConnell
We believe that the bug you reported is fixed in the latest version of
debdelta, 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 962...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Calum McConnell (supplier of updated debdelta
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, 01 Jan 2021 17:15:42 -0500
Source: debdelta
Architecture: source
Version: 0.65+nmu1
Distribution: unstable
Urgency: high
Maintainer: A Mennucc1
Changed-By: Calum McConnell
Closes: 954420 962203
Changes:
debdelta (0.65+nmu1) unstable; urgency=high
.
* Non-maintainer upload.
* Fix "DeprecationWarning: isAlive() is deprecated, use is_alive()
instead" (Closes: #962203, #954420)
Checksums-Sha1:
62a539a59c23bc8e4bafe75ef0b8a69026193214 1568 debdelta_0.65+nmu1.dsc
dc92bc6387f66b78b06fb1217d50081d29c9 266712 debdelta_0.65+nmu1.tar.xz
Checksums-Sha256:
480bf8511a569969da95f97a4d4fb351992a55e0a251aceabad8bad17ce7 1568
debdelta_0.65+nmu1.dsc
fb44170f322b9d072014c35c6061c1986ee9570c5425fa3576a0f8edbee29313 266712
debdelta_0.65+nmu1.tar.xz
Files:
0f8d9e1a4ac353f12b673963e5b12c61 1568 devel optional debdelta_0.65+nmu1.dsc
f3b04c5931c20d0af9bb457c20ae87f6 266712 devel optional
debdelta_0.65+nmu1.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl/6mNMACgkQMRa6Xp/6
aaPR9Q//emmpEw4aFCBCi0f2hlVHHEU8bRgryVhlARiaJ8wJeL+kSw3Nzi/Pmju7
ZsQHdP6krqeg7SuapoNs6lUDOgZkbCW7SsaFcpe6e1vHCOt2xM9P4RhyhEvvpsmG
vMb4ChhFgoZVkidjhbinV/Zvmxbw5nVfdIlYCLkPgsDJWJF1v5VUOlyoZDYTj7il
ybt+IZOFHw5+xfUqhChQF1MmS/qdS+ZJXpNQH/z30xmtHUrhTXT0IIceCwyFKEL5
1thb2k9qyfpiIP8OEVt5PB7rSsF59Nvd8MTayDxuLuNbgG5rfGTrdO4FSM4y8zoc
2OJJA1o0KRq6gFp/LJ57Hs8Ke6QDL8MtLBmK6p6//g+wllIfFcwscMRhBkh6lDyw
2IGnv0Q6ESdtf5gtnaTJzVtjnOdbDx8lqnbNgkpORMDlhB+ZLQc0KWuQvk3T8bV7
8z1/l5yndqnkBgiciuTiQLLvoY9aGsAVDJ2kaZvTAWFKk9a4wKnGHQZ6oTDj+kIL
bl7dBA1OlCx9vkMXGEb2OgHZ2Ox+kc8NWu6Mjl2gOHiaM5N4BQHGWzh4pSEKP2Nj
BJ2WeT7ZQAWxzuopCyRR3k49JPzYxh8sIOcncVw8XbtJBnSjAFWSLFWHSSjFSzeg
gn23LcRAfksGBaJDKSTTz0HqalxS3bKakn3JzpOQkz0uu6pBv5U=
=kBNc
-END PGP SIGNATURE End
Bug#954420: marked as done (Python deprecation warning)
Your message dated Sun, 10 Jan 2021 06:19:37 +
with message-id
and subject line Bug#954420: fixed in debdelta 0.65+nmu1
has caused the Debian Bug report #954420,
regarding Python deprecation warning
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.)
--
954420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdelta
Version: 0.65
Severity: minor
There's a new deprecation warning that popped up recently:
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debdelta depends on:
ii binutils 2.34-5
ii bzip2 1.0.8-2
ii libbz2-1.01.0.8-2
ii libc6 2.30-2
ii python3 3.8.2-1
ii python3-requests 2.22.0-2
ii zlib1g1:1.2.11.dfsg-2
Versions of packages debdelta recommends:
ii bsdiff 4.3-21+b1
pn gnupg2
ii gpg-agent [gnupg-agent] 2.2.19-3
ii python3-apt 1.9.10
ii python3-debian 0.1.36
ii xdelta 1.1.3-9.3
ii xdelta3 3.0.11-dfsg-1+b1
ii xz-utils [lzma] 5.2.4-1+b1
Versions of packages debdelta suggests:
pn debdelta-doc
-- Configuration Files:
/etc/debdelta/sources.conf changed [not included]
--- End Message ---
--- Begin Message ---
Source: debdelta
Source-Version: 0.65+nmu1
Done: Calum McConnell
We believe that the bug you reported is fixed in the latest version of
debdelta, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Calum McConnell (supplier of updated debdelta
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, 01 Jan 2021 17:15:42 -0500
Source: debdelta
Architecture: source
Version: 0.65+nmu1
Distribution: unstable
Urgency: high
Maintainer: A Mennucc1
Changed-By: Calum McConnell
Closes: 954420 962203
Changes:
debdelta (0.65+nmu1) unstable; urgency=high
.
* Non-maintainer upload.
* Fix "DeprecationWarning: isAlive() is deprecated, use is_alive()
instead" (Closes: #962203, #954420)
Checksums-Sha1:
62a539a59c23bc8e4bafe75ef0b8a69026193214 1568 debdelta_0.65+nmu1.dsc
dc92bc6387f66b78b06fb1217d50081d29c9 266712 debdelta_0.65+nmu1.tar.xz
Checksums-Sha256:
480bf8511a569969da95f97a4d4fb351992a55e0a251aceabad8bad17ce7 1568
debdelta_0.65+nmu1.dsc
fb44170f322b9d072014c35c6061c1986ee9570c5425fa3576a0f8edbee29313 266712
debdelta_0.65+nmu1.tar.xz
Files:
0f8d9e1a4ac353f12b673963e5b12c61 1568 devel optional debdelta_0.65+nmu1.dsc
f3b04c5931c20d0af9bb457c20ae87f6 266712 devel optional
debdelta_0.65+nmu1.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl/6mNMACgkQMRa6Xp/6
aaPR9Q//emmpEw4aFCBCi0f2hlVHHEU8bRgryVhlARiaJ8wJeL+kSw3Nzi/Pmju7
ZsQHdP6krqeg7SuapoNs6lUDOgZkbCW7SsaFcpe6e1vHCOt2xM9P4RhyhEvvpsmG
vMb4ChhFgoZVkidjhbinV/Zvmxbw5nVfdIlYCLkPgsDJWJF1v5VUOlyoZDYTj7il
ybt+IZOFHw5+xfUqhChQF1MmS/qdS+ZJXpNQH/z30xmtHUrhTXT0IIceCwyFKEL5
1thb2k9qyfpiIP8OEVt5PB7rSsF59Nvd8MTayDxuLuNbgG5rfGTrdO4FSM4y8zoc
2OJJA1o0KRq6gFp/LJ57Hs8Ke6QDL8MtLBmK6p6//g+wllIfFcwscMRhBkh6lDyw
2IGnv0Q6ESdtf5gtnaTJzVtjnOdbDx8lqnbNgkpORMDlhB+ZLQc0KWuQvk3T8bV7
8z1/l5yndqnkBgiciuTiQLLvoY9aGsAVDJ2kaZvTAWFKk9a4wKnGHQZ6oTDj+kIL
bl7dBA1OlCx9vkMXGEb2OgHZ2Ox+kc8NWu6Mjl2gOHiaM5N4BQHGWzh4pSEKP2Nj
BJ2WeT7ZQAWxzuopCyRR3k49JPzYxh8sIOcncVw8XbtJBnSjAFWSLFWHSSjFSzeg
gn23LcRAfksGBaJDKSTTz0HqalxS3bKakn3JzpOQkz0uu6pBv5U=
=kBNc
-END PGP SIGNATURE End
Bug#962203: marked as done (DeprecationWarning: isAlive() is deprecated, use is_alive() instead)
Your message dated Sun, 10 Jan 2021 06:19:37 +
with message-id
and subject line Bug#954420: fixed in debdelta 0.65+nmu1
has caused the Debian Bug report #954420,
regarding DeprecationWarning: isAlive() is deprecated, use is_alive() instead
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
954420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdelta
Version: 0.65
Severity: normal
Hi!
It seems that something needs to be update in debdelta:
=
# debdelta-upgrade
Created,time 0.15sec, speed 151kB/sec, libmtdev1_1.1.6-1_amd64.deb
Downloaded, time 0.47sec, speed 83kB/sec,
libcryptsetup12_2%3a2.3.2-1_2%3a2.3.3-1_amd64.debdelta
Created,time 0.33sec, speed 709kB/sec,
libcryptsetup12_2%3a2.3.3-1_amd64.deb
Downloaded, time 0.41sec, speed 104kB/sec,
calibre-bin_4.99.4+dfsg+really4.17.0-1_4.99.4+dfsg+really4.17.0-1+b1_amd64.debdelta
Created,time 2.09sec, speed 375kB/sec,
calibre-bin_4.99.4+dfsg+really4.17.0-1+b1_amd64.deb
Downloaded, time 2.38sec, speed 206kB/sec,
libqt5gui5_5.12.5+dfsg-10_5.12.5+dfsg-10+b1_amd64.debdelta
/usr/bin/debdelta-upgrade:5384: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
if patching_thread.isAlive() and no_delta and VERBOSE > 1 :
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
Created,time 6.01sec, speed 484kB/sec,
libqt5gui5_5.12.5+dfsg-10+b1_amd64.deb
/usr/bin/debdelta-upgrade:5405: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive():
/usr/bin/debdelta-upgrade:5410: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while progress_thread != None and progress_thread.isAlive():
Delta-upgrade statistics:
total resulting debs, size 3956kB time 11sec virtual speed 340kB/sec
=
Thank you!
Best regards,
Nelson
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debdelta depends on:
ii binutils 2.34-8
ii bzip2 1.0.8-3
ii libbz2-1.01.0.8-3
ii libc6 2.30-8
ii python3 3.8.2-3
ii python3-requests 2.23.0+dfsg-2
ii zlib1g1:1.2.11.dfsg-2
Versions of packages debdelta recommends:
ii bsdiff 4.3-21+b1
ii gnupg-agent 2.2.20-1
ii gnupg2 2.2.20-1
ii gpg-agent [gnupg-agent] 2.2.20-1
ii python3-apt 2.1.3
ii python3-debian 0.1.37
pn xdelta
ii xdelta3 3.0.11-dfsg-1+b1
ii xz-utils [lzma] 5.2.4-1+b1
Versions of packages debdelta suggests:
pn debdelta-doc
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debdelta
Source-Version: 0.65+nmu1
Done: Calum McConnell
We believe that the bug you reported is fixed in the latest version of
debdelta, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Calum McConnell (supplier of updated debdelta
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, 01 Jan 2021 17:15:42 -0500
Source: debdelta
Architecture: source
Version: 0.65+nmu1
Distribution: unstable
Urgency: high
Maintainer: A Mennucc1
Changed-By: Calum McConnell
Closes: 954420 962203
Changes:
debdelta (0.65+nmu1) unstable; urgency=high
.
* Non-maintainer upload.
* Fix
Bug#975672: Bug#979245: RFS: xylib/1.6-0.1 [RC] [NMU] -- Library for reading x-y data from several file formats
Hi Fabian I see you've imported the package into the Debian Science Team area on salsa. Since xylib is orphaned, do you intend to adopt it and maintain it within the Debian Science team? That would be a great outcome. If you update the Maintainer and Uploaders fields in debian/control, close #979256 in the changelog and update the version to 1.6-1, then I can sponsor the maintainer upload to adopt the package :) regards Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#979689: pepperflashplugin-nonfree: Installation script fails to download flash from adobe's servers
Package: pepperflashplugin-nonfree Version: 1.8.7 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: pitsior...@gmail.com Dear Maintainer, Please consider this a followup of #978954, which talks about flash's deprecation from adobe. As mentioned in the title, the installation script fails to download the relevant file. Wget tries 3 times, but the download url redirects here https://www.adobe.com/products/flashplayer/end-of-life.html where there is nothing to download, rendering the package not installable. Here is the full output of apt Unpacking pepperflashplugin-nonfree (1.8.7) ... Setting up pepperflashplugin-nonfree (1.8.7) ... --2021-01-10 07:26:28-- https://get.adobe.com/flashplayer/webservices/json/?platform_type=Linux_arch=x86_64_dist=Chrome Resolving get.adobe.com (get.adobe.com)... 193.104.215.66 Connecting to get.adobe.com (get.adobe.com)|193.104.215.66|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome [following] --2021-01-10 07:26:29-- https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Resolving www.adobe.com (www.adobe.com)... 212.205.43.11, 212.205.43.26, 2a02:587:8ff:25::d4cd:4da2, ... Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2021-01-10 07:26:45-- (try: 2) https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Retrying. --2021-01-10 07:27:02-- (try: 3) https://www.adobe.com/products/flashplayer/end-of- life.html?platform_type=Linux_arch=x86_64_dist=Chrome Connecting to www.adobe.com (www.adobe.com)|212.205.43.11|:443... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Giving up. ERROR: failed to determine upstream version More information might be available at: http://wiki.debian.org/PepperFlashPlayer -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE 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) Versions of packages pepperflashplugin-nonfree depends on: ii binutils 2.35.1-7 ii ca-certificates 20200601 ii libgcc-s110.2.1-3 ii libstdc++6 10.2.1-3 ii wget 1.21-1+b1 pepperflashplugin-nonfree recommends no packages. Versions of packages pepperflashplugin-nonfree suggests: pn chromium pn ttf-dejavu ii ttf-mscorefonts-installer 3.8 pn ttf-xfree86-nonfree -- no debconf information
Bug#977094: marked as done (sasmodels FTBFS with pytest 6)
Your message dated Sun, 10 Jan 2021 04:19:03 +
with message-id
and subject line Bug#977094: fixed in sasmodels 1.0.4-3
has caused the Debian Bug report #977094,
regarding sasmodels FTBFS with pytest 6
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.)
--
977094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sasmodels
Version: 1.0.4-1
Severity: important
User: pyt...@packages.debian.org
Usertags: pytest-v6
Hi,
sasmodels FTBFS with pytest 6 in experimental. See the relevant
part of the changelog as to why:
https://docs.pytest.org/en/stable/changelog.html#id170
The error log below has more details.
> I: pybuild base:232: cd
> /<>/.pybuild/cpython3_3.9_sasmodels/build; python3.9 -m pytest -v
> = test session starts
> ==
> platform linux -- Python 3.9.1, pytest-6.0.2, py-1.9.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> collecting ... collected 32 items / 1 error / 31 selected
>
> ERRORS
>
> _ ERROR collecting
> .pybuild/cpython3_3.9_sasmodels/build/sasmodels/model_test.py _
> /usr/lib/python3/dist-packages/pluggy/hooks.py:286: in __call__
> return self._hookexec(self, self.get_hookimpls(), kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:92: in _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
> /usr/lib/python3/dist-packages/pluggy/manager.py:83: in
> self._inner_hookexec = lambda hook, methods, kwargs: hook.multicall(
> ../../../conftest.py:54: in pytest_pycollect_makeitem
> test = pytest.Function(name+index, collector, args=args, callobj=call)
> /usr/lib/python3/dist-packages/_pytest/nodes.py:95: in __call__
> warnings.warn(NODE_USE_FROM_PARENT.format(name=self.__name__),
> stacklevel=2)
> E pytest.PytestDeprecationWarning: Direct construction of Function has been
> deprecated, please use Function.from_parent.
> E See
> https://docs.pytest.org/en/stable/deprecations.html#node-construction-changed-to-node-from-parent
> for more details.
> === short test summary info
>
> ERROR sasmodels/model_test.py - pytest.PytestDeprecationWarning: Direct
> const...
> Interrupted: 1 error during collection
>
> === 1 error in 2.09s
> ===
> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.9_sasmodels/build; python3.9 -m pytest -v
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make: *** [debian/rules:31: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
> 2
--- End Message ---
--- Begin Message ---
Source: sasmodels
Source-Version: 1.0.4-3
Done: Stuart Prescott
We believe that the bug you reported is fixed in the latest version of
sasmodels, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stuart Prescott (supplier of updated sasmodels 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: Sun, 10 Jan 2021 12:40:14 +1100
Source: sasmodels
Architecture: source
Version: 1.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Stuart Prescott
Closes: 977094
Changes:
sasmodels (1.0.4-3) unstable; urgency=medium
.
* Patch test collection to be compatible with pytest 6 (Closes: #977094).
Checksums-Sha1:
7196353063129644839a6957a0ae6b76f0b79c29 2428 sasmodels_1.0.4-3.dsc
1dc8923ed6b6c0afdb993819ca42b5c9d7a0665c 8560 sasmodels_1.0.4-3.debian.tar.xz
d7a80ab0bafb041b88685b5808d1c8957a6d238d 10173
sasmodels_1.0.4-3_amd64.buildinfo
Checksums-Sha256:
87e846440ddae077a4f1281f8dbe0537e7c9224c70d344814f2789349b5ae9d2 2428
sasmodels_1.0.4-3.dsc
Bug#978328: marked as done (python-jpype: FTBFS: mv: cannot stat '/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar': No such file or directory)
Your message dated Sun, 10 Jan 2021 12:18:03 +0900 with message-id <87a6thzdhw.wl-tak...@asis.media-as.org> and subject line Re: python-jpype: FTBFS: mv: cannot stat '/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar': No such file or directory has caused the Debian Bug report #978328, regarding python-jpype: FTBFS: mv: cannot stat '/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar': No such file or directory 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.) -- 978328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-jpype Version: 1.1.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_python3 > mv > /<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar > /<>/debian/python3-jpype/usr/share/java > mv: cannot stat > '/<>/debian/python3-jpype/usr/lib/python3.9/dist-packages/org.jpype.jar': > No such file or directory > make[1]: *** [debian/rules:13: override_dh_python3] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/12/26/python-jpype_1.1.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- This was alread closed at 1.2.0-1. ref #976782 -- 谷口 貴紀 (TANIGUCHI Takaki) tak...@asis.media-as.org http://takaki-web.media-as.org/ tak...@debian.org pgpMAu5JwqI_l.pgp Description: OpenPGP Digital Signature --- End Message ---
Processed: notfound 870396 in 1.2.3.2-1, notfixed 966037 in 0.6.0-2, notfixed 972200 in 1:78.3.1-2~deb10u2 ...
Processing commands for cont...@bugs.debian.org:
> # unconfuse the bts - found and fixed in the same version
> notfound 870396 1.2.3.2-1
Bug #870396 {Done: Thorsten Glaser } [src:alsa-lib]
alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)
No longer marked as found in versions alsa-lib/1.2.3.2-1.
> notfixed 966037 0.6.0-2
Bug #966037 {Done: Alex Mestiashvili } [src:krop]
krop: Uses old name of sip module
No longer marked as fixed in versions 0.6.0-2.
> notfixed 972200 1:78.3.1-2~deb10u2
Bug #972200 {Done: Carsten Schoenert } [thunderbird]
Thunderbird Collects Data
No longer marked as fixed in versions 1:78.3.1-2~deb10u2.
> notfixed 973505 4:20.08.2-3
Bug #973505 {Done: Sandro Knauß } [akregator] akregator:
Feeds no longer update
No longer marked as fixed in versions 4:20.08.2-3.
> notfound 973603 14.0.0+dfsg.2-1
Bug #973603 {Done: Sébastien Delafond } [src:odoo] odoo:
source-is-missing for minified JS files
No longer marked as found in versions odoo/14.0.0+dfsg.2-1.
> notfixed 977351 3.14.12-1
Bug #977351 {Done: Anton Gladky } [facter] boost 1.74
incompatible with boost 1.71, breaks puppet
No longer marked as fixed in versions facter/3.14.12-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
870396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870396
966037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966037
972200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972200
973505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973505
973603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973603
977351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979672: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056)
Your message dated Sun, 10 Jan 2021 02:53:54 + with message-id and subject line Bug#979672: fixed in nvidia-graphics-drivers-legacy-390xx 390.141-1 has caused the Debian Bug report #979672, regarding nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056 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.) -- 979672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979672 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 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE‑2021‑1056 Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE‑2021‑1056 Control: reassign -5 src:nvidia-graphics-drivers-tesla-440 Control: retitle -5 nvidia-graphics-drivers-tesla-440: CVE‑2021‑1056 Control: reassign -6 src:nvidia-graphics-drivers-tesla-450 Control: retitle -6 nvidia-graphics-drivers-tesla-450: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 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 https://nvidia.custhelp.com/app/answers/detail/a_id/5142 CVE‑2021‑1052 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape or IOCTL in which user-mode clients can access legacy privileged APIs, which may lead to denial of service, escalation of privileges, and information disclosure. CVE‑2021‑1053 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape or IOCTL in which improper validation of a user pointer may lead to denial of service. CVE‑2021‑1056 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer (nvidia.ko) in which it does not completely honor operating system file system permissions to provide GPU device-level isolation, which may lead to denial of service or information disclosure. CVE‑2021‑1052 and CVE‑2021‑1053 affect R460 and R450 driver branches only. Andreas --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-legacy-390xx Source-Version: 390.141-1 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 979...@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: Sun, 10 Jan 2021 03:31:58 +0100 Source: nvidia-graphics-drivers-legacy-390xx Architecture: source Version: 390.141-1 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 979672 Changes: nvidia-graphics-drivers-legacy-390xx (390.141-1) unstable; urgency=medium . * New upstream legacy branch release 390.141 (2021-01-07). * Fixed CVE‑2021‑1056. (Closes: #979672) https://nvidia.custhelp.com/app/answers/detail/a_id/5142 - Fixed a driver installation failure on Linux kernel 5.8 release candidates, where the NVIDIA kernel module failed to build with error "'struct mm_struct' has no member named 'mmap_sem'". - Fixed a driver installation failure on Linux kernel 5.8 release candidates, where the NVIDIA kernel module failed to build with error "too many arguments to function '__vmalloc'". . [ Andreas Beckmann ] * Re-enable building the nvidia-uvm module. * Refresh patches. * Update symbols files. * Update lintian overrides. Checksums-Sha1: 10c89d8b602167f94380adb2fa5dbcdaafbb16a2 7598 nvidia-graphics-drivers-legacy-390xx_390.141-1.dsc
Processed: Re: scantool: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957781 [src:scantool] scantool: ftbfs with GCC-10 Added tag(s) patch. -- 957781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957781: scantool: ftbfs with GCC-10
Package: scantool
Version: 2.1-2
Followup-For: Bug #957781
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix compilation with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru scantool-2.1/debian/patches/gcc-10.patch
scantool-2.1/debian/patches/gcc-10.patch
--- scantool-2.1/debian/patches/gcc-10.patch1969-12-31 19:00:00.0
-0500
+++ scantool-2.1/debian/patches/gcc-10.patch2021-01-09 21:44:33.0
-0500
@@ -0,0 +1,121 @@
+--- a/globals.h
b/globals.h
+@@ -37,19 +37,19 @@
+ #define C_LIGHT_GRAY55
+
+ //
+-int is_not_genuine_scan_tool;
++extern int is_not_genuine_scan_tool;
+
+ // Options
+-int system_of_measurements;
+-int display_mode;
++extern int system_of_measurements;
++extern int display_mode;
+
+ // File names
+-char *options_file_name;
+-char *data_file_name;
+-char *code_defs_file_name;
+-char log_file_name[20];
++extern char *options_file_name;
++extern char *data_file_name;
++extern char *code_defs_file_name;
++extern char log_file_name[20];
+ #ifdef LOG_COMMS
+-char comm_log_file_name[20];
++extern char comm_log_file_name[20];
+ #endif
+
+ void write_log(const char *log_string);
+@@ -58,6 +58,6 @@
+ void write_comm_log(const char *marker, const char *data);
+ #endif
+
+-DATAFILE *datafile;
++extern DATAFILE *datafile;
+
+ #endif
+--- a/main.c
b/main.c
+@@ -16,6 +16,23 @@
+
+ #define WINDOW_TITLE "ScanTool.net " SCANTOOL_VERSION_EX_STR
+
++int is_not_genuine_scan_tool;
++
++// Options
++int system_of_measurements;
++int display_mode;
++
++// File names
++char *options_file_name;
++char *data_file_name;
++char *code_defs_file_name;
++char log_file_name[20];
++#ifdef LOG_COMMS
++char comm_log_file_name[20];
++#endif
++
++DATAFILE *datafile;
++
+
+ void write_log(const char *log_string)
+ {
+--- a/serial.h
b/serial.h
+@@ -77,13 +77,15 @@
+ int display_error_message(int error, int retry);
+
+ // variables
+-volatile int serial_time_out;
+-volatile int serial_timer_running;
++extern volatile int serial_time_out;
++extern volatile int serial_timer_running;
+
+ struct COMPORT {
+int number;
+int baud_rate;
+int status;// READY, NOT_OPEN, USER_IGNORED
+-} comport;
++};
++
++extern struct COMPORT comport;
+
+ #endif
+--- a/serial.c
b/serial.c
+@@ -24,6 +24,11 @@
+ #define TX_TIMEOUT_MULTIPLIER0
+ #define TX_TIMEOUT_CONSTANT 1000
+
++volatile int serial_time_out;
++volatile int serial_timer_running;
++
++struct COMPORT comport;
++
+
+
+ //timer interrupt handler for sensor data
+--- a/error_handlers.h
b/error_handlers.h
+@@ -1,7 +1,7 @@
+ #ifndef ERROR_HANDLERS_H
+ #define ERROR_HANDLERS_H
+
+-char temp_error_buf[256];
++extern char temp_error_buf[256];
+
+ void fatal_error(char *msg);
+
+--- a/error_handlers.c
b/error_handlers.c
+@@ -3,6 +3,8 @@
+ #include "error_handlers.h"
+
+
++char temp_error_buf[256];
++
+ void fatal_error(char *msg)
+ {
+if (datafile != NULL)
diff -Nru scantool-2.1/debian/patches/series scantool-2.1/debian/patches/series
--- scantool-2.1/debian/patches/series 1969-12-31 19:00:00.0 -0500
+++ scantool-2.1/debian/patches/series 2021-01-09 21:33:51.0 -0500
@@ -0,0 +1 @@
+gcc-10.patch
Processed: Re: sdlbasic: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957786 [src:sdlbasic] sdlbasic: ftbfs with GCC-10 Added tag(s) patch. -- 957786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957786: sdlbasic: ftbfs with GCC-10
Package: sdlbasic Version: 0.0.20070714-6 Followup-For: Bug #957786 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix compilation with GCC 10. Thanks for considering the patch. Logan diff -Nru sdlbasic-0.0.20070714/debian/patches/gcc-10.patch sdlbasic-0.0.20070714/debian/patches/gcc-10.patch --- sdlbasic-0.0.20070714/debian/patches/gcc-10.patch 1969-12-31 19:00:00.0 -0500 +++ sdlbasic-0.0.20070714/debian/patches/gcc-10.patch 2021-01-09 21:27:45.0 -0500 @@ -0,0 +1,41 @@ +--- a/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h b/src/sdlBasic/src/sdlBrt/SDLengine/SDLengine.h +@@ -315,14 +315,14 @@ + void crossfadehandler(int s); + int hit_pixelperfect(SDL_Surface *imga,int xa1,int ya1,int xa2,int ya2,SDL_Surface *imgb,int xb1,int yb1,int xb2,int yb2); + +-Uint32(*getpixel)(SDL_Surface *surface, int x, int y); ++extern Uint32(*getpixel)(SDL_Surface *surface, int x, int y); + Uint32 getpixel8(SDL_Surface *surface, int x, int y); + Uint32 getpixel16(SDL_Surface *surface, int x, int y); + Uint32 getpixel24BE(SDL_Surface *surface, int x, int y); + Uint32 getpixel24(SDL_Surface *surface, int x, int y); + Uint32 getpixel32(SDL_Surface *surface, int x, int y); + +-void (*putpixel)(SDL_Surface *surface, int x, int y, Uint32 col ); ++extern void (*putpixel)(SDL_Surface *surface, int x, int y, Uint32 col ); + void putpixel8(SDL_Surface *surface, int x, int y, Uint32 col ); + void putpixel16(SDL_Surface *surface, int x, int y, Uint32 col ); + void putpixel24BE(SDL_Surface *surface, int x, int y, Uint32 col ); +@@ -337,7 +337,7 @@ + void draw_ellipse(SDL_Surface *surface,int vx,int vy,int Xradius,int Yradius,Uint32 color); + void draw_fillellipse(SDL_Surface *surface,int vx,int vy,int Xradius,int Yradius,Uint32 color); + +-Uint32 (*rrgb)(int col); ++extern Uint32 (*rrgb)(int col); + Uint32 rrgb8(int col); + Uint32 rrgb16(int col); + Uint32 rrgb24(int col); +--- a/src/sdlBasic/src/sdlBrt/SDLengine/screen.c b/src/sdlBasic/src/sdlBrt/SDLengine/screen.c +@@ -28,6 +28,10 @@ + + #include "SDLengine.h" + ++Uint32(*getpixel)(SDL_Surface *surface, int x, int y); ++void (*putpixel)(SDL_Surface *surface, int x, int y, Uint32 col ); ++Uint32 (*rrgb)(int col); ++ + //_ + + //SCREEN diff -Nru sdlbasic-0.0.20070714/debian/patches/series sdlbasic-0.0.20070714/debian/patches/series --- sdlbasic-0.0.20070714/debian/patches/series 2017-11-29 18:15:20.0 -0500 +++ sdlbasic-0.0.20070714/debian/patches/series 2021-01-09 21:25:21.0 -0500 @@ -9,3 +9,4 @@ quickhelp.patch link_gmodule_libs.patch useless_links.patch +gcc-10.patch
Bug#962203: NMU
On Tue, 29 Dec 2020 10:55:39 +0800 Paul Wise wrote: > Maybe lets wait for A Mennucc1 to do a maintainer upload, and if it > gets close to the next autoremoval date, do a more minimal NMU. The next autoremoval date is getting closer, so it looks like A Mennucc1 does not have time to fix this issue, please upload a more minimal NMU and I will sponsor that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#974024: marked as done (inn2 FTBFS on IPV6-only buildds)
Your message dated Sun, 10 Jan 2021 00:48:39 + with message-id and subject line Bug#974024: fixed in inn2 2.6.3+20210104-1 has caused the Debian Bug report #974024, regarding inn2 FTBFS on IPV6-only buildds 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.) -- 974024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: inn2 Version: 2.6.3+20200601-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=inn2=armhf=2.6.3%2B20200601-1=1591433398=0 https://buildd.debian.org/status/fetch.php?pkg=inn2=armel=2.6.3%2B20200601-1%2Bb1=1604879007=0 ... lib/network/server..MISSED 34-42 (killed by signal 14) ... Failed Set Fail/Total (%) Skip Stat Failing Tests -- -- lib/network/server9/3426%8 -- 34-42 Failed 9/3631 tests, 99.75% okay, 55 tests skipped. Files=60, Tests=3631, 12.90 seconds (2.43 usr + 1.92 sys = 4.35 CPU) make[2]: *** [Makefile:38: test] Error 1 --- End Message --- --- Begin Message --- Source: inn2 Source-Version: 2.6.3+20210104-1 Done: Marco d'Itri We believe that the bug you reported is fixed in the latest version of inn2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri (supplier of updated inn2 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: Sun, 10 Jan 2021 01:22:23 +0100 Source: inn2 Architecture: source Version: 2.6.3+20210104-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri Changed-By: Marco d'Itri Closes: 974024 Changes: inn2 (2.6.3+20210104-1) unstable; urgency=medium . * New upstream snapshot. Fixes: + Reproducibility on IPv6-only systems. (Closes: #974024) Checksums-Sha1: 088e3d32047089125ae031900bffa8d3697dee72 1490 inn2_2.6.3+20210104-1.dsc 9bb62f6256859369e94a387bab9bc6775efcdc38 1697576 inn2_2.6.3+20210104.orig.tar.xz 4a19d989aafa88934605c756433f6b41c632d2d6 34948 inn2_2.6.3+20210104-1.debian.tar.xz 0b2c038e683519b1d1c6398bcbdc202cdf52c666 7717 inn2_2.6.3+20210104-1_amd64.buildinfo Checksums-Sha256: 232fd1b5d013dbd53b82dda9a27a27247f8dbcf93dd5414f42c7c088c383b896 1490 inn2_2.6.3+20210104-1.dsc 6497b26fbe47cee735a2a77b20b6cc769f3cd136ec50c3eacfaaeac413530447 1697576 inn2_2.6.3+20210104.orig.tar.xz 9f22e6c3be5ed20b2d491b8178a3be7fd50ba99ded3bb0af8bdfa602747f2eec 34948 inn2_2.6.3+20210104-1.debian.tar.xz a621f691d02d099125365fcb703d9df4220950d9ffd697c0941ea9e46278df9c 7717 inn2_2.6.3+20210104-1_amd64.buildinfo Files: 202bd7e3cf84427b0ea1bbe65a9c1e13 1490 news optional inn2_2.6.3+20210104-1.dsc fee9f89a4b3bb92c399a62287862a6a3 1697576 news optional inn2_2.6.3+20210104.orig.tar.xz 8df8f02b21777ce8c3d3e5f99d88cdb9 34948 news optional inn2_2.6.3+20210104-1.debian.tar.xz 45a70646d0bb7e0979d3ef37b6f52398 7717 news optional inn2_2.6.3+20210104-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQQnKUXNg20437dCfobLPsM64d7XgQUCX/pJHAAKCRDLPsM64d7X gTmzAP4rh077fyIc5sP3FR6+06WcNSGYAZ/tSK970uH7GqlORAEAxxf3bjPaOBGz Mkgz6fS6XLZI3UjIvOGNLbvqw5HnDQ4= =5IXm -END PGP SIGNATURE End Message ---
Bug#957801: siproxd: ftbfs with GCC-10
Package: siproxd Version: 1:0.8.1-4.1 Followup-For: Bug #957801 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu hirsute ubuntu-patch X-Debbugs-Cc: lo...@ubuntu.com Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc-10.patch: Fix compilation with GCC 10. Thanks for considering the patch. Logan diff -Nru siproxd-0.8.1/debian/control siproxd-0.8.1/debian/control --- siproxd-0.8.1/debian/control2018-04-03 08:43:31.0 -0400 +++ siproxd-0.8.1/debian/control2021-01-09 19:35:35.0 -0500 @@ -1,8 +1,7 @@ Source: siproxd Section: net Priority: optional -Maintainer: Ubuntu Developers -XSBC-Original-Maintainer: Debian VoIP Team +Maintainer: Debian VoIP Team Uploaders: Mark Purcell , Kilian Krause , Mikael Magnusson , Faidon Liambotis Build-Depends: debhelper (>= 9), libosip2-dev (>= 3.1.0), automake, dh-autoreconf, autoconf, docbook-utils, libltdl3-dev Standards-Version: 3.8.4 diff -Nru siproxd-0.8.1/debian/patches/gcc-10.patch siproxd-0.8.1/debian/patches/gcc-10.patch --- siproxd-0.8.1/debian/patches/gcc-10.patch 1969-12-31 19:00:00.0 -0500 +++ siproxd-0.8.1/debian/patches/gcc-10.patch 2021-01-09 19:35:34.0 -0500 @@ -0,0 +1,11 @@ +--- a/src/accessctl.c b/src/accessctl.c +@@ -34,7 +34,7 @@ + static char const ident[]="$Id: accessctl.c 424 2009-03-28 09:37:47Z hb9xar $"; + + /* configuration storage */ +-struct siproxd_config configuration; ++extern struct siproxd_config configuration; + + + /* diff -Nru siproxd-0.8.1/debian/patches/series siproxd-0.8.1/debian/patches/series --- siproxd-0.8.1/debian/patches/series 2013-05-26 01:05:43.0 -0400 +++ siproxd-0.8.1/debian/patches/series 2021-01-09 19:35:21.0 -0500 @@ -2,3 +2,4 @@ non-empty-dependency_libs-in-la-file.diff siproxd-libtool-2.4.patch debian-user-1.diff +gcc-10.patch
Processed: Re: siproxd: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957801 [src:siproxd] siproxd: ftbfs with GCC-10 Added tag(s) patch. -- 957801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979364: marked as done (nodejs: CVE-2020-8265 CVE-2020-8287)
Your message dated Sun, 10 Jan 2021 00:20:03 + with message-id and subject line Bug#979364: fixed in nodejs 12.20.1~dfsg-1 has caused the Debian Bug report #979364, regarding nodejs: CVE-2020-8265 CVE-2020-8287 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.) -- 979364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 12.19.0~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 10.21.0~dfsg-1~deb10u1 Control: found -1 14.13.0~dfsg-1 Hi, The following vulnerabilities were published for nodejs. CVE-2020-8265[0]: | nodejs: use-after-free in TLSWrap CVE-2020-8287[1]: | nodejs: HTTP Request Smuggling If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-8265 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8265 [1] https://security-tracker.debian.org/tracker/CVE-2020-8287 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8287 Regards, Salvatore --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 12.20.1~dfsg-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Jan 2021 00:02:53 +0100 Source: nodejs Binary: libnode-dev libnode72 libnode72-dbgsym nodejs nodejs-dbgsym nodejs-doc Architecture: source ppc64el all Version: 12.20.1~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode72 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Closes: 979364 Changes: nodejs (12.20.1~dfsg-1) unstable; urgency=medium . * New upstream version 12.20.1~dfsg. Closes: #979364. Fixed vulnerabilities: + CVE-2020-8265: use-after-free in TLSWrap (High) + CVE-2020-8287: HTTP Request Smuggling (Low) * Patch to always use pure javascript cjs lexer instead of wasm files that can't be generated with currently available packages. * copyright: cjs-module-lexer is expat * copyright: exclude cjs-module-lexer unbuildable files * copyright: fix some copyright years * lintian-overrides: false positive for a unicode regexp * copyright: shjs is no longer used Checksums-Sha1: d6d4f4ec976f40f840d76462aaaf06dfe57578a6 3450 nodejs_12.20.1~dfsg-1.dsc 3d9244fa2ed24aafa75924c7998c0f00ce478f7a 85444 nodejs_12.20.1~dfsg.orig-types-node.tar.xz 593071b6c5765dc98b7dc7cb76026feb21ede4a0 18558244 nodejs_12.20.1~dfsg.orig.tar.xz 4b298bc0d70b35d96ce3cfb4f974ff36ec4d07c6 134176 nodejs_12.20.1~dfsg-1.debian.tar.xz f57e0711a7211e7278516bbf5fcacb3f5897441a 409400 libnode-dev_12.20.1~dfsg-1_ppc64el.deb c798baafd5393bce742e7a5b97fbd3b5a6929b1d 367647752 libnode72-dbgsym_12.20.1~dfsg-1_ppc64el.deb 472509639d0bf876e5c99707a83105d068c0668b 8743944 libnode72_12.20.1~dfsg-1_ppc64el.deb 25ceaa5f95d3fd5cda8fa91aee6ff1cbf71be927 122752 nodejs-dbgsym_12.20.1~dfsg-1_ppc64el.deb b2bffc8b5e5f87e08264895ea33242419f58d38d 2537628 nodejs-doc_12.20.1~dfsg-1_all.deb c7dab3f5773413ebb1c4e3e64d567aada301583b 10214 nodejs_12.20.1~dfsg-1_ppc64el.buildinfo 77eb08282a07b5ddec182f1f22419d9e152615e7 144908 nodejs_12.20.1~dfsg-1_ppc64el.deb Checksums-Sha256: 21caa233c2b1b6075ff70c487053f6c5a7ad536c5844ff3dfa62467db8b6435b 3450 nodejs_12.20.1~dfsg-1.dsc ad7f1131cb433ff0c472c4c4aef5b60690430d7e230b857666ba08d7537e6f70 85444 nodejs_12.20.1~dfsg.orig-types-node.tar.xz
Bug#979681: soapaligner: FTBFS with GCC 10
Source: soapaligner
Version: 2.20-4
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Hi,
soapaligner currently FTBFS with GCC 10 (which is now the default in
unstable). [1]
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix compilation with GCC 10.
Thanks for considering the patch.
Logan
[1]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/soapaligner.html
diff -Nru soapaligner-2.20/debian/patches/gcc-10.patch
soapaligner-2.20/debian/patches/gcc-10.patch
--- soapaligner-2.20/debian/patches/gcc-10.patch1969-12-31
19:00:00.0 -0500
+++ soapaligner-2.20/debian/patches/gcc-10.patch2021-01-09
18:46:50.0 -0500
@@ -0,0 +1,36 @@
+--- a/extratools.h
b/extratools.h
+@@ -59,12 +59,12 @@
+ HITITEM *itemList;
+ }HITTABLE;
+
+-BWT * occBwt;
+-HASHTABLE * occHashtable;
+-unsigned int * occCollector;
+-unsigned int occCollected;
++extern BWT * occBwt;
++extern HASHTABLE * occHashtable;
++extern unsigned int * occCollector;
++extern unsigned int occCollected;
+
+-FILE * textPositionFile;
++extern FILE * textPositionFile;
+ void registerTPFile(FILE * filePtr,unsigned int searchMode);
+
+ void registerQIndex(unsigned int queryIndex);
+--- a/extratools.c
b/extratools.c
+@@ -5,6 +5,13 @@
+ // Hash Table
+ // All things like those
+
++BWT * occBwt;
++HASHTABLE * occHashtable;
++unsigned int * occCollector;
++unsigned int occCollected;
++
++FILE * textPositionFile;
++
+ void LoadLookupTable(LOOKUPTABLE * lookupTable, const char * fileName, const
int tableSize) {
+ (*lookupTable).tableSize = tableSize;
+ unsigned long long NR_TOP = 1 << (tableSize * 2);
diff -Nru soapaligner-2.20/debian/patches/series
soapaligner-2.20/debian/patches/series
--- soapaligner-2.20/debian/patches/series 2020-04-17 05:45:00.0
-0400
+++ soapaligner-2.20/debian/patches/series 2021-01-09 18:43:23.0
-0500
@@ -2,3 +2,4 @@
linkerror.patch
UsageDoublette.patch
spelling.patch
+gcc-10.patch
Processed: Re: sptk: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957839 [src:sptk] sptk: ftbfs with GCC-10 Added tag(s) patch. -- 957839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957839: sptk: ftbfs with GCC-10
Package: sptk
Version: 3.9-2
Followup-For: Bug #957839
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix compilation with GCC 10.
Thanks for considering the patch.
Logan
diff -Nru sptk-3.9/debian/patches/gcc-10.patch
sptk-3.9/debian/patches/gcc-10.patch
--- sptk-3.9/debian/patches/gcc-10.patch1969-12-31 19:00:00.0
-0500
+++ sptk-3.9/debian/patches/gcc-10.patch2021-01-09 17:36:40.0
-0500
@@ -0,0 +1,22 @@
+--- a/bin/psgr/psgr.h
b/bin/psgr/psgr.h
+@@ -48,7 +48,7 @@
+int bottom;
+int left;
+int right;
+-} bbm;
++};
+
+ struct page_media {
+char *size;
+--- a/bin/psgr/psgr.c
b/bin/psgr/psgr.c
+@@ -106,6 +106,8 @@
+"Landscape",
+ };
+
++struct bbmargin bbm;
++
+
+ /* Default Values */
+ #define MEDIA "FALSE"
diff -Nru sptk-3.9/debian/patches/series sptk-3.9/debian/patches/series
--- sptk-3.9/debian/patches/series 2018-05-08 09:13:22.0 -0400
+++ sptk-3.9/debian/patches/series 2021-01-09 17:36:16.0 -0500
@@ -2,3 +2,4 @@
1005_support_stdin_and_stout_on_getfp.patch
1008_add_peak_cross_correlation_output_to_pitch.patch
1009_add_nacorr_and_str_commands.patch
+gcc-10.patch
Bug#978227: marked as done (vala-panel-appmenu: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1))
Your message dated Sat, 09 Jan 2021 23:19:34 + with message-id and subject line Bug#978227: fixed in vala-panel-appmenu 0.7.6+dfsg1-2 has caused the Debian Bug report #978227, regarding vala-panel-appmenu: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1) 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.) -- 978227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vala-panel-appmenu Version: 0.7.6+dfsg1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: budgie-core-dev, meson (>= 0.51.0), debhelper-compat (= > 13), libbamf3-dev (>= 0.5.0), bamfdaemon (>= 0.5.0), libglib2.0-dev (>= > 2.52.0), libgtk-3-dev (>= 3.22.0), libmate-panel-applet-dev (>= 1.20), > libvalapanel-dev (>= 0.4.92), libwnck-3-dev (>= 3.4.8), > libxfce4panel-2.0-dev, libxfconf-0-dev, valac (>= 0.24.0), xfce4-panel-dev > (>= 4.11.2), build-essential, fakeroot > Filtered Build-Depends: budgie-core-dev, meson (>= 0.51.0), debhelper-compat > (= 13), libbamf3-dev (>= 0.5.0), bamfdaemon (>= 0.5.0), libglib2.0-dev (>= > 2.52.0), libgtk-3-dev (>= 3.22.0), libmate-panel-applet-dev (>= 1.20), > libvalapanel-dev (>= 0.4.92), libwnck-3-dev (>= 3.4.8), > libxfce4panel-2.0-dev, libxfconf-0-dev, valac (>= 0.24.0), xfce4-panel-dev > (>= 4.11.2), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [498 B] > Get:5 copy:/<>/apt_archive ./ Packages [588 B] > Fetched 2043 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > xfce4-panel-dev : Depends: xfce4-panel (= 4.14.4-1) but it is not going to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/12/26/vala-panel-appmenu_0.7.6+dfsg1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: vala-panel-appmenu Source-Version: 0.7.6+dfsg1-2 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of vala-panel-appmenu, 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. Mike Gabriel (supplier of updated vala-panel-appmenu package) (This message was generated automatically at their request; if you believe that there
Processed: severity of 966647 is grave
Processing commands for cont...@bugs.debian.org: > severity 966647 grave Bug #966647 [src:libetpan] libetpan: CVE-2020-15953 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 966647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978227: marked as pending in vala-panel-appmenu
Control: tag -1 pending Hello, Bug #978227 in vala-panel-appmenu 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-ayatana-team/vala-panel-appmenu/-/commit/bce81c7e17086e69a3ab22eff0eb3f82b51b3162 debian/control: Drop B-D xfce4-panel-dev. Pkg not available anymore since XFCE4 4.16. (Closes: #978227). (this message was generated automatically) -- Greetings https://bugs.debian.org/978227
Processed: Bug#978227 marked as pending in vala-panel-appmenu
Processing control commands: > tag -1 pending Bug #978227 [src:vala-panel-appmenu] vala-panel-appmenu: FTBFS: build-dependency not installable: xfce4-panel (= 4.14.4-1) Added tag(s) pending. -- 978227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056
Processing control commands: > clone -1 -2 -3 -4 -5 -6 Bug #979670 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug 979670 cloned as bugs 979671-979675 > reassign -2 src:nvidia-graphics-drivers-legacy-340xx Bug #979671 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-340xx'. Ignoring request to alter found versions of bug #979671 to the same values previously set Ignoring request to alter fixed versions of bug #979671 to the same values previously set > retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE‑2021‑1056 Bug #979671 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Changed Bug title to 'nvidia-graphics-drivers-legacy-340xx: CVE‑2021‑1056' from 'nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056'. > reassign -3 src:nvidia-graphics-drivers-legacy-390xx Bug #979672 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-390xx'. Ignoring request to alter found versions of bug #979672 to the same values previously set Ignoring request to alter fixed versions of bug #979672 to the same values previously set > retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056 Bug #979672 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Changed Bug title to 'nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056' from 'nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056'. > reassign -4 src:nvidia-graphics-drivers-tesla-418 Bug #979673 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-tesla-418'. Ignoring request to alter found versions of bug #979673 to the same values previously set Ignoring request to alter fixed versions of bug #979673 to the same values previously set > retitle -4 nvidia-graphics-drivers-tesla-418: CVE‑2021‑1056 Bug #979673 [src:nvidia-graphics-drivers-tesla-418] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Changed Bug title to 'nvidia-graphics-drivers-tesla-418: CVE‑2021‑1056' from 'nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056'. > reassign -5 src:nvidia-graphics-drivers-tesla-440 Bug #979674 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-tesla-440'. Ignoring request to alter found versions of bug #979674 to the same values previously set Ignoring request to alter fixed versions of bug #979674 to the same values previously set > retitle -5 nvidia-graphics-drivers-tesla-440: CVE‑2021‑1056 Bug #979674 [src:nvidia-graphics-drivers-tesla-440] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Changed Bug title to 'nvidia-graphics-drivers-tesla-440: CVE‑2021‑1056' from 'nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056'. > reassign -6 src:nvidia-graphics-drivers-tesla-450 Bug #979675 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-tesla-450'. Ignoring request to alter found versions of bug #979675 to the same values previously set Ignoring request to alter fixed versions of bug #979675 to the same values previously set > retitle -6 nvidia-graphics-drivers-tesla-450: CVE‑2021‑1052, CVE‑2021‑1053, > CVE‑2021‑1056 Bug #979675 [src:nvidia-graphics-drivers-tesla-450] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Changed Bug title to 'nvidia-graphics-drivers-tesla-450: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056' from 'nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056'. > found -1 340.24-1 Bug #979670 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Marked as found in versions nvidia-graphics-drivers/340.24-1. > found -1 343.22-1 Bug #979670 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Marked as found in versions nvidia-graphics-drivers/343.22-1. > found -1 396.18-1 Bug #979670 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Marked as found in versions nvidia-graphics-drivers/396.18-1. > found -1 430.14-1 Bug #979670 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 Marked as found in versions nvidia-graphics-drivers/430.14-1. >
Bug#979670: nvidia-graphics-drivers: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056
Source: nvidia-graphics-drivers Severity: serious Tags: security upstream Control: clone -1 -2 -3 -4 -5 -6 Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE‑2021‑1056 Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE‑2021‑1056 Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE‑2021‑1056 Control: reassign -5 src:nvidia-graphics-drivers-tesla-440 Control: retitle -5 nvidia-graphics-drivers-tesla-440: CVE‑2021‑1056 Control: reassign -6 src:nvidia-graphics-drivers-tesla-450 Control: retitle -6 nvidia-graphics-drivers-tesla-450: CVE‑2021‑1052, CVE‑2021‑1053, CVE‑2021‑1056 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 https://nvidia.custhelp.com/app/answers/detail/a_id/5142 CVE‑2021‑1052 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape or IOCTL in which user-mode clients can access legacy privileged APIs, which may lead to denial of service, escalation of privileges, and information disclosure. CVE‑2021‑1053 NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape or IOCTL in which improper validation of a user pointer may lead to denial of service. CVE‑2021‑1056 NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer (nvidia.ko) in which it does not completely honor operating system file system permissions to provide GPU device-level isolation, which may lead to denial of service or information disclosure. CVE‑2021‑1052 and CVE‑2021‑1053 affect R460 and R450 driver branches only. Andreas
Bug#961302: Processed: bug 961302 is forwarded to https://gitlab.com/sane-project/backends/-/issues/279
Am Mon, Jun 01, 2020 at 09:33:48PM +0200 schrieb Salvatore Bonaccorso: > Hi Jörg, > > On Mon, Jun 01, 2020 at 09:27:14PM +0200, Jörg Frings-Fürst wrote: > > Hi Salvatore, > > > > I get always "You need to sign in or sign up before continuing." > > heh okay, not from here which seem strange as I have (withouth signing > in) and get presented an issue with subject: > > memory corruption bugs in libsane > GitHub Security Lab (GHSL) Vulnerability Report: GHSL-2020-075, GHSL-2020-079, > GHSL-2020-080, GHSL-2020-081, GHSL-2020-082, GHSL-2020-083, GHSL-2020-084 > > Anyway, I think it's okay to not mark it forwarded there if this is prefered, > but I'm suprised we get different results (as I'm not logged in either to > gitlab). > > Btw, thanks for your work. I guess you will next move the experimental upload > to unstable at some point so the issuess are fixed for bullseye? What's the status, can you please fix this for unstable in time of the freeze? Cheers, Moritz
Bug#957971: marked as done (xblast-tnt: ftbfs with GCC-10)
Your message dated Sat, 09 Jan 2021 22:37:05 + with message-id and subject line Bug#957971: fixed in xblast-tnt 2.10.4-4.1 has caused the Debian Bug report #957971, regarding xblast-tnt: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xblast-tnt Version: 2.10.4-4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/xblast-tnt_2.10.4-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] /usr/bin/ld: com_central.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: com_central.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: user.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: user.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: dat_rating.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: dat_rating.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: cfg_main.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: cfg_main.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: cfg_level.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: cfg_level.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: cfg_player.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: cfg_player.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: cfg_game.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: cfg_game.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld: cfg_control.o:./build_xblast-tnt-mini/../network.h:108: multiple definition of `teamColors'; xblast.o:./build_xblast-tnt-mini/../network.h:108: first defined here /usr/bin/ld: cfg_control.o:./build_xblast-tnt-mini/../cfg_control.h:32: multiple definition of `keyEventType'; xblast.o:./build_xblast-tnt-mini/../cfg_control.h:32: first defined here /usr/bin/ld:
Processed: Re: rust-rand-core-0.3: Unaligned memory access resulting in undefined behavior
Processing commands for cont...@bugs.debian.org: > severity 970186 grave Bug #970186 [src:rust-rand-core-0.3] rust-rand-core-0.3: Unaligned memory access resulting in undefined behavior Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 970186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977552: marked as done (gnutls28: Time bomb in testpkcs11.sh triggered)
Your message dated Sat, 09 Jan 2021 22:33:22 + with message-id and subject line Bug#977552: fixed in gnutls28 3.6.7-4+deb10u6 has caused the Debian Bug report #977552, regarding gnutls28: Time bomb in testpkcs11.sh triggered 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.) -- 977552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnutls28 Version: 3.6.15-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1135 autopkgtests and build fail now due to an expired certificate Not After : Dec 13 08:24:54 2020 GMT cu Andreas --- End Message --- --- Begin Message --- Source: gnutls28 Source-Version: 3.6.7-4+deb10u6 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of gnutls28, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated gnutls28 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 Jan 2021 18:10:33 +0100 Source: gnutls28 Architecture: source Version: 3.6.7-4+deb10u6 Distribution: buster Urgency: medium Maintainer: Debian GnuTLS Maintainers Changed-By: Andreas Metzler Closes: 977552 Changes: gnutls28 (3.6.7-4+deb10u6) buster; urgency=medium . * 45_4.7.0plus-01_testpkcs11-use-datefudge-to-trick-certificate-expiry.patch Fix test suite error caused by expired certificate. Closes: #977552 Checksums-Sha1: 6cff0aaf5f1875704f90d0910b2f1b75abee00be 3354 gnutls28_3.6.7-4+deb10u6.dsc fbf94198f7055f3c3159c97ff07e2d718079b12f 90436 gnutls28_3.6.7-4+deb10u6.debian.tar.xz Checksums-Sha256: 206f6f03abd5d6c83ddb6a454af7e96dcdee14156f877e6b311ceed9e2a2115e 3354 gnutls28_3.6.7-4+deb10u6.dsc 6158e0ebb12a23ca44ce90d8e677af355d04bdf66d97ca1d5a59049c1b455b3c 90436 gnutls28_3.6.7-4+deb10u6.debian.tar.xz Files: a94833ccff6dc8c05573e19d21943647 3354 libs optional gnutls28_3.6.7-4+deb10u6.dsc 7a92f337c6e9dbf33aa29d350bbe3a98 90436 libs optional gnutls28_3.6.7-4+deb10u6.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl/wrssACgkQpU8BhUOC FIQUzxAAnt6CyG0apuVTAduUtCeoDrd/hXLEYvifhMxKvWaNqvru2Gyc1Mi8xQ89 UOijs+x1JfKcMCFxoDQ/tGvePpYur3eyZ/SQ13VWJ3MYJVyjU80n5Gu3JV8uQGDj ISqCIVZuRANiCQ07xHiMijJNW9kYJ5wLDOz4eAOV3+EYlm8s92xt2dWmnjjnfJvV 19f1Aj0sd6dfSmgHqlJv8hMiR4tGmUmHLk2zAXwpMCHLjKwOJVqYDmSixDkD/rO/ /h33nQ6PIKuAQ985REjLxJpAu5Fe5g79NPxLMIV6h7duw3sTprTHSQbUQZUOPREy rShEIuQZV0hT+/ZWLshCqkfj/Yol6tzMUX+5yw8/aY2lHOOpIHoaQ4EbzIrx9/dV XbLJ1sx5I+GkPAQAJAeh7UC+7jDjtp32uiNZbXA6ugxQEOiokYrnHGcUeQNdQv5e 0ZqbS2rHhLkmxNSmD3evGtlEKYZdaExZjg4wVPoeRJR2jSYASS6f+yMiCZhM6FpR zEXNr6dPBxyqKghhtSbC82kPKH3H9OlZquEpvT3Dphvj4iZsGK7GvB0wHbwkuNLy +Gsbt9v5LYcmIV8KZjOlGr4ZCytakpKCS3YtjHJ3ESgSxnkQo2Meqep+j7Hxd7qu 6ac5cVRF9NqKJlKfDGHALUj4t8iMdBYvS3x94VC8Qs2csZOV/KE= =M/FW -END PGP SIGNATURE End Message ---
Bug#975372: marked as done (minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge)
Your message dated Sat, 09 Jan 2021 22:33:34 + with message-id and subject line Bug#975372: fixed in minidlna 1.2.1+dfsg-2+deb10u2 has caused the Debian Bug report #975372, regarding minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge 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.) -- 975372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minidlna Version: 1.2.1+dfsg-2 Severity: serious Tags: patch Hi, Purging the package currently fails with the following error: Purging configuration files for minidlna (1.2.1+dfsg-2) ... rm: cannot remove '/var/log/minidlna': Is a directory dpkg: error processing package minidlna (--purge): installed minidlna package post-removal script subprocess returned error exit status 1 Errors were encountered while processing: minidlna E: Sub-process /usr/bin/dpkg returned an error code (1) Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-diff --git a/debian/minidlna.postrm b/debian/minidlna.postrm index 0e9114d..5cde64c 100644 --- a/debian/minidlna.postrm +++ b/debian/minidlna.postrm @@ -5,8 +5,8 @@ set -e case "$1" in purge) - rm -rf /var/cache/minidlna -rm -f /var/log/minidlna.log* /var/log/minidlna + rm -rf /var/cache/minidlna /var/log/minidlna +rm -f /var/log/minidlna.log* ;; remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear) --- End Message --- --- Begin Message --- Source: minidlna Source-Version: 1.2.1+dfsg-2+deb10u2 Done: Alexander GQ Gerasiov We believe that the bug you reported is fixed in the latest version of minidlna, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander GQ Gerasiov (supplier of updated minidlna package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 03 Jan 2021 19:16:43 +0300 Source: minidlna Architecture: source Version: 1.2.1+dfsg-2+deb10u2 Distribution: buster-security Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Alexander GQ Gerasiov Closes: 975372 Changes: minidlna (1.2.1+dfsg-2+deb10u2) buster-security; urgency=medium . * d/minidlna.postrm: Do not fail on purge (Closes: #975372). This fixes the regression (from 1.2.1+dfsg-2) in stable archive after accidentially uploaded 1.2.1+dfsg-2+deb10u1. Checksums-Sha1: c3ff70f038e6c0e816ad31ab06b4e1d04f40b5fc 1738 minidlna_1.2.1+dfsg-2+deb10u2.dsc 9acd54f5e4c00cef1ee5b301736331bd318c0856 26124 minidlna_1.2.1+dfsg-2+deb10u2.debian.tar.xz 301a98a59474044dbe5081fca43c5f2a1efeba2d 9054 minidlna_1.2.1+dfsg-2+deb10u2_source.buildinfo Checksums-Sha256: 5cad1242c64d73b9899cd53b0641a1fdb25b17f271dfd7e37d63127d23532a5a 1738 minidlna_1.2.1+dfsg-2+deb10u2.dsc 11c1f9d536bebedefacede5a1ce2ad0e85af23149fbb7f8c992af2a5918bdc20 26124 minidlna_1.2.1+dfsg-2+deb10u2.debian.tar.xz ab1ababe399649d816daad0c30a2dc910fa5bdccdf1f9fc9e01b9e553e1c9edc 9054 minidlna_1.2.1+dfsg-2+deb10u2_source.buildinfo Files: 7a39d8bb787bb6bb5f7c6f059ddc50c0 1738 net optional minidlna_1.2.1+dfsg-2+deb10u2.dsc 43ba250e0319e97268732782b22ebb02 26124 net optional minidlna_1.2.1+dfsg-2+deb10u2.debian.tar.xz db4d9c04a2ce49fd0724d560dab9a0b5 9054 net optional minidlna_1.2.1+dfsg-2+deb10u2_source.buildinfo -BEGIN PGP SIGNATURE- iQFCBAEBCgAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAl/x7jgOHGdxQGRlYmlh bi5vcmcACgkQyofp6CqsM/EgOwgAsAwHrEUkvQlvKbLubIU7Alx9Z4GQwXQ5KX4t y8tC9hJS325qABpVg43o+FSCisQbq6636i20DxouT6gY4XDd0gjzHnazPKX3xMwI uzXmCzf4Ml8i+V4Ro9BOSnhvF+RzyXj/4euFctEwBoAA9k63PFqyWLsuSWSDJdv3 +o36qiArNchymiZLUH1IQcdHaOELoe7zkiXcmWUidVJH/HvCOOoztO0JpHAqrkok Ex7WVoC8fWWjb4UluazHdbHrhNxNZVYIopbGJhGl9sywqM7O/2QgzIOwYAJVtrwZ QbOgyVYTBr8R0FanVdU6mlrfesJvRl6Hb+ryWaH7j7WbR3yceg== =rdJ9 -END PGP SIGNATURE End Message ---
Bug#958497: marked as done (geoclue-2.0 violates GDPR)
Your message dated Sat, 09 Jan 2021 22:33:22 + with message-id and subject line Bug#958497: fixed in geoclue-2.0 2.5.2-1+deb10u1 has caused the Debian Bug report #958497, regarding geoclue-2.0 violates GDPR 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.) -- 958497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geoclue-2.0 Version: 2.5.6-1 Severity: serious The geoclue package collects SSIDs in the neighborhood and sends them to Mozilla location services. The SSID of an adhoc network (which for instance is set up for tethering via a mobile phone) is personally identifiable information. Sending this information about a third person without his or her explicit consent to another party especially one outside of the European Union is in breach of the German law Datenschutz-Grundverordnung which is the German implementation of the European General Data Protection Regulation (GDPR). The easiest remedy would be to remove the package from the repository until it is fixed upstream to be compliant. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924516 src/gclue-config.c:219: #define DEFAULT_WIFI_URL "https://location.services.mozilla.com/v1/geolocate?key=; MOZILLA_API_KEY #define DEFAULT_WIFI_SUBMIT_URL "https://location.services.mozilla.com/v1/submit?key=; MOZILLA_API_KEY Best regards Heinrich Schuchardt --- End Message --- --- Begin Message --- Source: geoclue-2.0 Source-Version: 2.5.2-1+deb10u1 Done: Laurent Bigonville We believe that the bug you reported is fixed in the latest version of geoclue-2.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laurent Bigonville (supplier of updated geoclue-2.0 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, 25 Dec 2020 17:19:50 +0100 Source: geoclue-2.0 Architecture: source Version: 2.5.2-1+deb10u1 Distribution: buster Urgency: medium Maintainer: Laurent Bigonville Changed-By: Laurent Bigonville Closes: 924516 958497 Changes: geoclue-2.0 (2.5.2-1+deb10u1) buster; urgency=medium . * debian/README.Debian: Add information about MLS and a link to the service Privacy Notice page * Check the maximum allowed accuracy level even for system applications. Respect the value of the user preference concerning the usage of their geolocation. This should fix the privacy and GDPR conformity concerns as the user explicitly needs to enable the option. Note that there is no distinction between the system applications anymore, turning on the option is allowing them all to get the location. (Closes: #924516, #958497) * d/p/: Add a patch to make the Mozilla API key configurable * debian/rules: Use the key that has been allocated to debian for MLS queries * d/p: Add an upstream patch to fix the display of the usage indicator * Fix crash if submission-url is not set in the config, patch from upstream Checksums-Sha1: 996a74e4d02b62c7211c7378e62ec3bceb2a90fa 2465 geoclue-2.0_2.5.2-1+deb10u1.dsc 2d541a66cff4eb8e403774f788673d5f097df00c 14068 geoclue-2.0_2.5.2-1+deb10u1.debian.tar.xz 00085f1af2e2ee9caaa615503cb1fa2ed4bd48e3 9660 geoclue-2.0_2.5.2-1+deb10u1_source.buildinfo Checksums-Sha256: 3176a0e3929a49bd8f36b2281f87539efe1a0e1f49890d47d9a9e23c2943346e 2465 geoclue-2.0_2.5.2-1+deb10u1.dsc 6d98621c6e9f68d369fe06334f1f11dd45396682e69103a60b15e186eccd2adc 14068 geoclue-2.0_2.5.2-1+deb10u1.debian.tar.xz 4e1d6c98818859d22e266858fd0b4c740bb630b9dadc23b2f176ee601e27dd87 9660 geoclue-2.0_2.5.2-1+deb10u1_source.buildinfo Files: bc8b7b3eb01c0105b7512af796360e3a 2465 utils optional geoclue-2.0_2.5.2-1+deb10u1.dsc 40c9f88dc8ed7fa3d54062e23236941f 14068 utils optional geoclue-2.0_2.5.2-1+deb10u1.debian.tar.xz cc2f02fa3a98b3ad65c9fbd039d53d49 9660 utils optional geoclue-2.0_2.5.2-1+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl/mWf8RHGJpZ29uQGRl Ymlhbi5vcmcACgkQH8WJHrqwQ9XlGQf/ar8i3s4/Q3km6PFDRHFcnvo0gBEilTTV
Bug#943695: marked as done (didjvu: FTBFS: ERROR: tests.test_timestamp.test_timezones)
Your message dated Sat, 09 Jan 2021 22:32:15 +
with message-id
and subject line Bug#943695: fixed in didjvu 0.8.2-2+deb10u1
has caused the Debian Bug report #943695,
regarding didjvu: FTBFS: ERROR: tests.test_timestamp.test_timezones
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.)
--
943695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: didjvu
Version: 0.8.2-2
Severity: serious
Justification: fails to build from source
didjvu FTBFS in a minimal chroot:
| ==
| ERROR: tests.test_timestamp.test_timezones
| --
| Traceback (most recent call last):
| File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
| self.test(*self.arg)
| File "/build/didjvu-w3wqV9/didjvu-0.8.2/tests/test_timestamp.py", line 51,
in test_timezones
| t(1261171514, 'Europe/Warsaw', '2009-12-18T22:25:14+01:00')
| File "/build/didjvu-w3wqV9/didjvu-0.8.2/tests/tools.py", line 212, in
wrapper
| raise IsolatedError('\n\n' + msg)
| IsolatedError:
|
| Traceback (most recent call last):
| File "/build/didjvu-w3wqV9/didjvu-0.8.2/tests/tools.py", line 189, in
wrapper
| f(*args, **kwargs)
| File "/build/didjvu-w3wqV9/didjvu-0.8.2/tests/test_timestamp.py", line 44,
in t
| assert_equal(str(result), expected)
| AssertionError: '2009-12-18T21:25:14Z' != '2009-12-18T22:25:14+01:00'
|
| --
The test in question needs the time zone database to work correctly, but
it was not available in the build environment.
Please add "tzdata" to Build-Depends to fix this.
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: didjvu
Source-Version: 0.8.2-2+deb10u1
Done: Santiago Vila
We believe that the bug you reported is fixed in the latest version of
didjvu, 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 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Santiago Vila (supplier of updated didjvu 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, 04 Jan 2021 20:11:00 +0100
Source: didjvu
Architecture: source
Version: 0.8.2-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Santiago Vila
Closes: 943695
Changes:
didjvu (0.8.2-2+deb10u1) buster; urgency=medium
.
* Add missing build-dependency on tzdata. Closes: #943695.
* Package is orphaned, set Maintainer to "Debian QA Group".
Checksums-Sha1:
ddda3a263e0428bf565834304792cdcab52a2eb4 1956 didjvu_0.8.2-2+deb10u1.dsc
e5dc42b9dedb9e71d23e7e40e1bf9170bebcd4c4 27196
didjvu_0.8.2-2+deb10u1.debian.tar.xz
7903becd38ddca7c3c32bd7ef7f60999d926dddc 7251
didjvu_0.8.2-2+deb10u1_source.buildinfo
Checksums-Sha256:
a60a153f2a67a63d1afc2133901389f9a65a3926046884814b7437f0db829df9 1956
didjvu_0.8.2-2+deb10u1.dsc
38a907659123386082e93cac0b3335d30655a30c4182ea7903057e410a94c313 27196
didjvu_0.8.2-2+deb10u1.debian.tar.xz
abb70d75d841f37492e12ccd7ea8c9785f1f62fa5bd8fde00af5aee2a8fd8c51 7251
didjvu_0.8.2-2+deb10u1_source.buildinfo
Files:
96c7e980ea9b9881d31e54fea54e0372 1956 graphics optional
didjvu_0.8.2-2+deb10u1.dsc
f385a08c3d4a78024c8784a4a9677184 27196 graphics optional
didjvu_0.8.2-2+deb10u1.debian.tar.xz
b8c8527590ba3794453cbe620a21961d 7251 graphics optional
didjvu_0.8.2-2+deb10u1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAl/zaawACgkQQc5/C58b
izJQeQf/aAIVtPP1dAYAgPo+9yLd4yBbkI37iSWfIS02JlJ5ZQ4rKIioYh1p7cEz
YDD+8FQXOfb4/L/irDtm3imP+QqgvpF0mvorpWnTb4Oit/rmBV11i19aZBHxmfFb
YddlfJpXwWLF5MC/9w+wvKbUDnA6jEZC7ObE1kEUBMyYi6Al3MFaNceNc1mVeBI3
pCmpus4zM3gox9u4LJGCxVDH5ifP4/I0UIr/RsXetRt6ZFWCNtTpmu8gUND7trnF
g/vILNBkQo7BPv2qsUzVZi68KhfwKDTHoaw6536Y4X92xFz4xKx/42nzateSNDjJ
Jwq5NG9bCTVxK0SjkYFu0Glke7BdzQ==
=AaDL
-END PGP SIGNATURE End Message ---
Bug#979334: Useless in Debian
Hi David, > Because of the above, I don’t believe it’s useful to keep it around > (please download the severity with a rationale if you disagree). I agree with you and I asked to remove magpierss package as you can see at #979667 Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org https://metaldot.alucinados.com signature.asc Description: This is a digitally signed message part
Bug#979334: RM: magpierss -- ROM; no longer used anywhere in Debian
Package: ftp.debian.org Severity: normal Hi, As subject says, please drop magpierss from unstable, as it is no longer used anywhere in Debian. Cheers, -- Marcelo Jorge Vieira xmpp:me...@jabber-br.org https://metaldot.alucinados.com https://movimente.me signature.asc Description: This is a digitally signed message part
Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default
On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > Note: in case we do not agree on this topic this will be the text I'll > send to the > tech-ctte. Thanks for taking the time to draft some text. If we can come closer to agreement on the proposed text, that would probably take a bit of the load off of the tech-ctte. Hopefully some of my comments move in that direction, although I also have added some counterpoint text as well... > Let me start by noting that I have nothing against reproducibility. In fact > quite the opposite: I love the idea... as long as it's properly implemented. It is even "recommended" in Debian Policy policy to build reproducibly with different build paths. > The problem here is that __FILE__ is a public, well defined API with very > valid > use cases (more on this below), even if the current implementation of all the > major compilers go against reproducibility. At least two major compilers, GCC and Clang provide the -ffile-prefix-map feature to do exactly that(which is what dpkg is enabling), so it seems a bit overstated to say that all major compilers "go against" reproducibility. They do not enable reproducibility by default. > So if we want to mangle __FILE__ > (thus breaking API) this should be done by an opt-in, and **never** by opting > out. Else we risk breaking a valid implementation, be it already on the > archive > any new package added afterwards. While I understand that may be how you feel, it would be appreciated if we could use something a little less loaded than "mangle". perhaps: So if we want to enable features using __FILE__ in a way which arguably breaks API > Even more: we library maintainers continuously ask our upstreams to keep their > API as stable as possible, and if not possible following some rules > (SONAME change, for example). I will present an option to do the same > ourselves > without breaking API/ABI. > > # __FILE__ is a public, well defined API > > During the course of #876901 many reasons were used to both say that __FILE__ > is or not a well defined API. In fact one of the evidences used where the > compiler's documentation. For example > https://gcc.gnu.org/onlinedocs/cpp/Standard-Predefined-Macros.html > (enphasis mine): > > This macro expands to the name of the current input file, in the form of a C > string constant. **This is the path by which the preprocessor opened > the file**, > not the short name specified in ‘#include’ or as the input file name > argument. > For example, "/usr/local/include/myheader.h" is a possible expansion of this > macro. > > This definition says that it's up to the preprocessor to define the path. So, > what has been the behaviour of all major compilers during all these years? > Using > the full path. The proof of this is Qt itself. Check > https://sources.debian.org/src/qtbase-opensource-src/5.15.2+dfsg-2/src/testlib/qtestcase.h/#L216 > > This code has been working on **every** platform Qt works without any change. > Qt is compiled in a myriad of OSs, using a myriad of compilers. They all do > the exact same thing. So developers depend on a very stable definition > of an API. > > And we all know that breaking API is bad, except if done carefully (read > below). > > # Doing the right thing > > This is just an idea of "doing the right thing", like bumping SONAME > on a library. > It definitely doesn't have to be the only one. I understand your position is fundamentally about "Doing the right thing" but I would say that we are all trying to do the right thing. > I understand that the reproducibility people do not want to consider > providing the > same build path. While this is arguable I do understand that > reproducibility without > depending on the build path is a good thing. So I've tried to come up with a > path to achieve this. > ## New macro and warning (if they do not exist already) > > This would be the first step. The idea is to provide a new macro that, > by definition > and documentation, it can be mangled with the help of the build > system, much as you > are currently doing with __FILE__ now. > > The second step in this is to make compilers create a reproducibility warning > if > some code uses __FILE__. This will have three effects effects: We haven't proposed an alternate macro, which would surely take years at best, possibly decades. That doesn't seem too realistic. > - discouraging it's use > - creating awareness on reproducibility. We've discouraged the use of __FILE__ for years, have done plenty of outreach on the subject of reproducibility, and gotten traction with various upstream projects. > - making other distros jump into reproducibility in a much easier way. Arguably some distros (e.g. archlinux) are passing us by when it comes to real-world reproducibility; I'm not sure Debian is the example by which all other distros should be measured anymore. Which is good in some ways, but somewhat disappointing to see Debian start something
Bug#979620: marked as done (sonic-pi: flaky armhf and arm64 autopkgtest on ci.debian.net: unknown bpm)
Your message dated Sat, 09 Jan 2021 21:49:05 + with message-id and subject line Bug#979620: fixed in sonic-pi 3.2.2~repack-7 has caused the Debian Bug report #979620, regarding sonic-pi: flaky armhf and arm64 autopkgtest on ci.debian.net: unknown bpm 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.) -- 979620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sonic-pi Version: 3.2.2~repack-6 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of your package turned up as blocking xorg-server. I looked into the history of your autopkgtest and it fails regularly on arm64 and armhf [1, 2]. I copied some of the output at the bottom of this report. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please do get in touch if we need to dive into this together. Or if you want to discuss this issue. Paul [1] https://ci.debian.net/packages/s/sonic-pi/testing/arm64/ [2] https://ci.debian.net/packages/s/sonic-pi/testing/armhf/ https://ci.debian.net/data/autopkgtest/testing/arm64/s/sonic-pi/9392735/log.gz Source: sonic-pi Version: 3.2.2~repack-6 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of your package turned up as blocking xorg-server. I looked into the history of your autopkgtest and it fails regularly on arm64 and armhf [1, 2]. I copied some of the output at the bottom of this report. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please do get in touch if we need to dive into this together. Or if you want to discuss this issue. Paul [1] https://ci.debian.net/packages/s/sonic-pi/testing/arm64/ [2] https://ci.debian.net/packages/s/sonic-pi/testing/armhf/ https://ci.debian.net/data/autopkgtest/testing/arm64/s/sonic-pi/9392735/log.gz [32mBuffer: 4.03s./4.03sTime: 0.09m. DHP: [ ] Overruns: 0 Xruns: 0[0m [3A[0m[36m00:| | 01:| | [32mBuffer: 4.03s./4.03sTime: 0.09m. DHP: [ ] Overruns: 0 Xruns: 0[0m [3A[0m[36m00:| | 01:| | [32mBuffer: 4.03s./4.03sTime: 0.09m. DHP: [ ] Overruns: 0 Xruns: 0[0m [3A[0m[1A[31m [1A>>> Please wait while writing all data to disk. (shouldn't take long) [36m |"| [0m[36m00:| | 01:| | [32mBuffer: 4.05s./4.05sTime: 0.10m. DHP: [ ] Overruns: 0 Xruns: 0[0m [3A[0m[36m00:| | 01:| | [32mBuffer: 4.05s./4.05sTime: 0.10m. DHP: [ ] Overruns: 0 Xruns: 0[0m [31mFinished.[0m unknown bpm autopkgtest [17:56:12]: test gui: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: sonic-pi Source-Version: 3.2.2~repack-7 Done: Valentin Vidic We believe that the bug you reported is fixed in the latest version of sonic-pi, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Valentin Vidic (supplier of updated sonic-pi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jan 2021 21:47:54 +0100 Source: sonic-pi Architecture: source Version: 3.2.2~repack-7 Distribution: unstable Urgency: medium Maintainer:
Bug#979666: cross-toolchain-base_50_all-buildd.changes REJECTED
Source: cross-toolchain-base Version: 50 Severity: serious - Forwarded message from Debian FTP Masters - From: Debian FTP Masters To: all / amd64 / i386 Build Daemon Date: Sat, 09 Jan 2021 21:18:45 + Subject: cross-toolchain-base_50_all-buildd.changes REJECTED Message-Id: Version check failed: Your upload included the binary package libc6-amd64-cross, version 2.31-9cross1, for all, however unstable already has version 2.31-9cross1. Uploads to unstable must have a higher version than present in unstable. Mapping sid to unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. - End forwarded message -
Bug#979041: marked as done (libopempi3: aborts python code due to libfabric fork() issues)
Your message dated Sat, 09 Jan 2021 21:19:21 + with message-id and subject line Bug#979041: fixed in openmpi 4.1.0-5 has caused the Debian Bug report #979041, regarding libopempi3: aborts python code due to libfabric fork() issues 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.) -- 979041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libopenmpi3 Version: 4.1.0-3 Severity: serious The revert of pmix has fixed some issues, but python packages still show autopkgtest regressions in dolfin[1], gpaw[2], gyoto[3] and mshr[4] . The error is always like this: |A process has executed an operation involving a call |to the fork() system call to create a child process. | |As a result, the libfabric EFA provider is operating in |a condition that could result in memory corruption or |other system errors. | |For the libfabric EFA provider to work safely when fork() |is called, you will need to set the following environment |variable: | RDMAV_FORK_SAFE | |However, setting this environment variable can result in |signficant performance impact to your application due to |increased cost of memory registration. | |You may want to check with your application vendor to see |if an application-level alternative (of not using fork) |exists. | |Your job will now abort. If I export RDMAV_FORK_SAFE=1, the tests run fine, but (i) it seems something in OpenMPI has changed so that those programs no longer run and (ii) the warnings about performance issues are to be considered. Also note that it seems those errors only happen on amd64/i386, the ARM ports run fine, maybe because of missing libfabric-related features/packages? Michael [1] https://ci.debian.net/data/autopkgtest/testing/amd64/d/dolfin/9184050/log.gz [2] https://ci.debian.net/data/autopkgtest/testing/amd64/g/gpaw/9302177/log.gz [3] https://ci.debian.net/data/autopkgtest/testing/amd64/g/gyoto/9303088/log.gz [4] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mshr/9300183/log.gz --- End Message --- --- Begin Message --- Source: openmpi Source-Version: 4.1.0-5 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of openmpi, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated openmpi 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, 09 Jan 2021 19:42:23 + Source: openmpi Architecture: source Version: 4.1.0-5 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 979041 Changes: openmpi (4.1.0-5) unstable; urgency=medium . * libfabric-dev now available on all bar hurd, kfreebsd * libnuma-dev now available on all bar hurd, kfreebsd * Exclude openib by default, update README.Debian to explain. * Patch to detect pmix 4. Closes: #979041 Checksums-Sha1: 360da5355ab8983e3033f791ca863ce4921571ef 2670 openmpi_4.1.0-5.dsc 5f55290657516474722a6d7deb2688167010b7b9 68048 openmpi_4.1.0-5.debian.tar.xz Checksums-Sha256: 0a0ae64633730621024c544ac510dc11983e42140cab6c5e4459ff3d751ca9a4 2670 openmpi_4.1.0-5.dsc 150672c5026753b3aa5e3188069cd6ced3bbf34cbc81bc83cc91b99379ae0777 68048 openmpi_4.1.0-5.debian.tar.xz Files: cfcd8c9ea24d17806713d32aa7cc0189 2670 net optional openmpi_4.1.0-5.dsc 54f46b015f327efadd1c4ed605350ad1 68048 net optional openmpi_4.1.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl/6GDcACgkQy+a7Tl2a 06W77Q//fMp9vrUS9PJv0pXf8Ay/W68KdQnWIEJuaGCV0a1I4ldWQg6jJrJ6CPBr gXBnl6ULloArVKYqN7C52CyCc1FrQPl7+ZvuiHjY7Z81Wl5JWVTjEkgRzmbhAJt9 bAihpyiUr4e85qbURQKWEWkGlyXhUymRbEXf3fHskD5dsCp1i4D44nbMOub1dKJm 1R4c+SzOH0DgXt5aNVgpJ/U5OQ5qfiHq9j0vJme3NtdjE2UiH2DsEA8YwEY6uCzY gXvxXMipelg9S55Vr9jZVqSKZwiuvzjwRAvaehhoPu9VyFJFDhrnDZefBDMzQQwV 1TbvKRPdgiqxulJHCyiWim6J4/Td/AwoZIdQHU1KpsLYO3EDVZyvKS6tMV8Z8ni3 6KU/zsC49MCDVT+HLj99kGvXTeyyVxn/LZz1dnk2wkxqJe2dTBxgUWdqX5l6Yuth wbdch+ODrT53d09ujqMu93+TqyVALwn5H1L1n0F4sffS0MNSUGvB3KspNfDYzn5L
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Adrian, On 09-01-2021 21:37, Adrian Bunk wrote: > you are saying the version in unstable passes all tests for migration, > and needs only this bug closed? Yes. Otherwise the excuses would have mentioned the issues. Looking at the excuses_yaml I see this: - 'Migration status for bagel (- to 1.2.2-1): BLOCKED: Rejected/violates migration policy/introduces a regression' - 'Issues preventing migration:' - 'Updating bagel introduces new bugs: https://bugs.debian.org/952463;>#952463' - 'Additional info:' - Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bagel.html;>https://piuparts.debian.org/sid/source/b/bagel.html - Required age reduced by 3 days because of autopkgtest - 740 days old (needed 2 days) is-candidate: false item-name: bagel maintainer: Debichem Team migration-policy-verdict: REJECTED_PERMANENTLY new-version: 1.2.2-1 old-version: '-' policy_info: age: age-requirement: 2 current-age: 740 verdict: PASS autopkgtest: bagel/1.2.2-1: amd64: - PASS - https://ci.debian.net/data/autopkgtest/testing/amd64/b/bagel/4806582/log.gz - https://ci.debian.net/packages/b/bagel/testing/amd64 - null - null arm64: - PASS - https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/5589842/log.gz - https://ci.debian.net/packages/b/bagel/testing/arm64 - null - null ppc64el: - PASS - https://ci.debian.net/data/autopkgtest/testing/ppc64el/b/bagel/7273182/log.gz - https://ci.debian.net/packages/b/bagel/testing/ppc64el - null - null verdict: PASS block: verdict: PASS build-depends: verdict: PASS built-using: verdict: PASS builtonbuildd: signed-by: amd64: buildd_amd64-x86-conova...@buildd.debian.org arm64: buildd_arm64-arm-ubc...@buildd.debian.org mips64el: buildd_mips64el-mipsel-manda...@buildd.debian.org ppc64el: buildd_ppc64el-ppc64el-unicamp...@buildd.debian.org s390x: buildd_s390x-zando...@buildd.debian.org verdict: PASS depends: verdict: PASS implicit-deps: verdict: PASS piuparts: piuparts-test-url: https://piuparts.debian.org/sid/source/b/bagel.html test-results: pass verdict: PASS rc-bugs: shared-bugs: [] unique-source-bugs: - '952463' unique-target-bugs: [] verdict: REJECTED_PERMANENTLY reason: [] source: bagel So it's only held back because of the bug. > At least I am not seeing any problem that has been observed during the > past 8 months that needs action. Paul PS: I did have a hint in place, but that was only to ignore failures on arm64. I've removed that just now. OpenPGP_signature Description: OpenPGP digital signature
Bug#979614: seamly2d: virtually dead fork of valentina
Hi, > Since then, he continued develop under original project name Valentina, > whereas Seamly2D virtually stalled with no substantial code changes , > only superficial changes to build infrastructure, locales, and icons. well, compared to valentina it seems to have way more pull requests and is at least very responsive to requests. Looking on valentina it seems to be a one-man-show - more or less. > I recommend that Debian does not carry Seamly3D, and encourage helping > out with maintaining Valentina instead. Would have been nice to know about that after I've opened the RFP bug - to be hones I haven't even been able to find valentina with apt, maybe I've searched for the wrong words. > If you disagree, then I just wish you the best of luck with Seamly3D. > I admit the severity is bloated - feel free to lower as you see fit. I think keeping one of them in Debian is the better option, but for now I'm not sure whats the best option. I'd be very happy to co-maintain one. Never planned to put seamly2d into bullseye, so don't worry about severities. Any idea why there is a fork at all? (feel free to reply in private...) Cheers, Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#971755: marked as done (shovill: built on architectures for which it's uninstallable)
Your message dated Sat, 09 Jan 2021 21:04:17 + with message-id and subject line Bug#971755: fixed in shovill 1.1.0-4 has caused the Debian Bug report #971755, regarding shovill: built on architectures for which it's uninstallable 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.) -- 971755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: shovill Version: 1.1.0-2 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy Hi Nilesh, The shovill package is not migratable to testing because it depends on a number of packages that are not portable and unavailable on !amd64 (spades, skesa, megahit) but a binary is built on these architectures. Since these per-arch binaries exist, they are expected by the archive policy to be installable. It looks to me like this is solvable by making shovill an Arch: all package instead of an Arch: any package, since shovill is a simple perl script with no compiled binaries. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: shovill Source-Version: 1.1.0-4 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of shovill, 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. Andreas Tille (supplier of updated shovill 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, 09 Jan 2021 21:35:13 +0100 Source: shovill Architecture: source Version: 1.1.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 971755 Changes: shovill (1.1.0-4) unstable; urgency=medium . * Team upload. * Add Build-Depends-Arch to prevent building on arm64 and enable migration (Thanks for the hint to Juhani Numminen) Closes: #971755 * Standards-Version: 4.5.1 (routine-update) Checksums-Sha1: d342d14a44aaf3d0c4dd2c2b11d07b83e266d7a3 2044 shovill_1.1.0-4.dsc e8c3259edde6563afd41a2ec89c2e6d0c683d871 3720 shovill_1.1.0-4.debian.tar.xz ceed4fbcb92836594e2b7b3063c9ca569734d424 7529 shovill_1.1.0-4_amd64.buildinfo Checksums-Sha256: a39a90280be8caa6f1861d60fe455644f5f72447c59df0af0296c94babae49fc 2044 shovill_1.1.0-4.dsc 82462a42b448f1282d1fb5b5388ec2cbc404af325f27b7308a4c0f4bad76772f 3720 shovill_1.1.0-4.debian.tar.xz d3be63bf167aff65a084086cd441e141234a94f22e5138d5e6c07987c3929b5a 7529 shovill_1.1.0-4_amd64.buildinfo Files: 37379e0938889ea57e1cced6c1e4d73c 2044 science optional shovill_1.1.0-4.dsc 9d3bed2fa1b156f3f830370e0bc27829 3720 science optional shovill_1.1.0-4.debian.tar.xz ef57f3e8eee18ecbba64acbff89126c2 7529 science optional shovill_1.1.0-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl/6FBcRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGKAxAAkMGUwygZ2tl4hTHWoM2gD+D40rLhjOB/ Ml5b5yz1r9mq3JzcdZCMbURhnu4MrTaVE9Gp2rAKFyvm4vnmUqup2g4CchbrXoIN 1E307vuTq4I8oijsRlbWIO82jGucjvLwEiXwE/IbTykiLFFdRLB17dAuBZdDVWy4 2UfjnpiK+HHbXSuxtrdmIXLIbAh1PDm6kkEgicVc87WKnXo4ZSUY2Be2KJzM1ZbG ZDnXZG6TqJBCcTs+tWV3xicgbKt35bp9CYhI0wy7lNKkpR/eYuh7JX/i8n5xlUSo Kxpuko89B2I4TUVY6HG5qKXkIuainyEM+QcuV4cmYMVJ0WNsUlMTsIJ+jBZK6DM9 tgwONAielQM/sIjJoA6jqLRTCLR7pGXdUArRn9PdoS2VvI9HoAVqaxSQ2wye+pQg N0R67guGemWKANjVbRaYGIGZZkHGrrdX8/TkQkFkXClkjXARjq+hTvXrLSYsrg5E M5Z4vp0uZ8+2dT5rABMFeUUaaIfYBwq67HXx4mwXRKA3dRPoRiAzNmCb3hO3Y/7t g/iAbRzWJoppIhVrJ8FI5kHdqiM6/wwJgOc9fEy3AiGPaxOx7IM2z/TCO+oDQQKP BuGU4bb7KjZ1cpjd9Ej78jlx8smoOSrWRz+684oVEq9cpB/ANMVvXg+ewJqAOCxH XL3HIu0VX4Q= =iTdL -END PGP SIGNATURE End Message ---
Bug#972958: marked as done (pipemeter FTBFS: error: format not a string literal and no format arguments)
Your message dated Sat, 09 Jan 2021 21:04:06 +
with message-id
and subject line Bug#972958: fixed in pipemeter 1.1.5-1
has caused the Debian Bug report #972958,
regarding pipemeter FTBFS: error: format not a string literal and no format
arguments
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.)
--
972958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pipemeter
Version: 1.1.4-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pipemeter=sid
...
dh_auto_build -a
make -j4
make[1]: Entering directory '/<>'
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
-DHAVE_CONFIG_H pipemeter.c -o pipemeter -Wl,-z,relro
pipemeter.c: In function ‘show_just_rate’:
pipemeter.c:400:5: error: format not a string literal and no format arguments
[-Werror=format-security]
400 | fprintf(stderr,trailer);
| ^~~
pipemeter.c: In function ‘show_progress’:
pipemeter.c:490:3: error: format not a string literal and no format arguments
[-Werror=format-security]
490 | fprintf(stderr, progressbar);
| ^~~
pipemeter.c:500:5: error: format not a string literal and no format arguments
[-Werror=format-security]
500 | fprintf(stderr,trailer);
| ^~~
pipemeter.c: In function ‘parseopts’:
pipemeter.c:577:22: warning: cast from pointer to integer of different size
[-Wpointer-to-int-cast]
577 | while(listdone=(int)fgets(listline,MAX_LINE,listfile)) {
| ^
cc1: some warnings being treated as errors
make[1]: *** [Makefile:10: pipemeter] Error 1
--- End Message ---
--- Begin Message ---
Source: pipemeter
Source-Version: 1.1.5-1
Done: Clint Byrum
We believe that the bug you reported is fixed in the latest version of
pipemeter, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Clint Byrum (supplier of updated pipemeter package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 09 Jan 2021 11:51:04 -0800
Source: pipemeter
Architecture: source
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Clint Byrum
Changed-By: Clint Byrum
Closes: 972958
Changes:
pipemeter (1.1.5-1) unstable; urgency=medium
.
* New upstream release (Closes: #972958)
Checksums-Sha1:
b1db81991d589acf9f5ce2d0217b7c2043df7495 1459 pipemeter_1.1.5-1.dsc
4389154052d5a05ce8632a0f54389db95f6063a2 149052 pipemeter_1.1.5.orig.tar.gz
ee949f7e04d2946d5d41ae84633316a8e66fc793 1848 pipemeter_1.1.5-1.debian.tar.xz
4bb9eb737bcc284e2ce9af34161df1d6b3c1846f 5888
pipemeter_1.1.5-1_source.buildinfo
Checksums-Sha256:
e6507ad51289506437a43ecd0deb5f73fdaa162fe3a2443f193250bd65ab2b3c 1459
pipemeter_1.1.5-1.dsc
e470ac5f3e71b5eee1a925d7174a6fa8f0753f2107e067fbca3f383fab2e87d8 149052
pipemeter_1.1.5.orig.tar.gz
79a24a68c3a7ddb2fa8f0cdf68f99d992e0f61714fe109fe31682629cb9006ca 1848
pipemeter_1.1.5-1.debian.tar.xz
f93a62fa2e4d6ccf9e7d198ec2cc4445e2b85372cfceb20a709ccb2f9ba6698e 5888
pipemeter_1.1.5-1_source.buildinfo
Files:
23082734c4aca2f61ac009f6ecee68b0 1459 admin extra pipemeter_1.1.5-1.dsc
3900d8a848eaed2e9f5bfd6af0491173 149052 admin extra pipemeter_1.1.5.orig.tar.gz
c3f15efd7f21b1915b47fe63f15a8076 1848 admin extra
pipemeter_1.1.5-1.debian.tar.xz
8020111bac7a5b4499070dd72b638006 5888 admin extra
pipemeter_1.1.5-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQFHBAEBCgAxFiEE8AyfL09+txSvrRpCU4wHZvS8s44FAl/6D1ITHHNwYW1hcHNA
ZGViaWFuLm9yZwAKCRBTjAdm9Lyzjm6VCAC1xwxZFGhWT5MlyvAhVJQvkHv9vuhF
0g8IpMAPAowhlYriY2FFuHNmE9vmu1nqiq8MeH2TK9zeaVl6mv8fgyjPzG5vLL0h
DS0C3iMYGHEKp6v1XzRKIueai3SAaOeWS3dd/XrqEU3f7wEzXfyeR59+h1W3VTNQ
rMZ9eNgxw5x2NJT/Fa++zpI2gCCZ9ndVgtUcMzQGJ159h/Zm6oQwed5QD7jwpr+S
rjuhxP9Qw2MSZX7udsv8BNZQHzqhPfw9JQ9j+9x35pf6OBto+TgSm2qUJidtX+RP
D36NeS0A3icB1djPtviC3TtJhih9zwmHVoprUTTt3cB3OEjo8m4vX9fD
=UkvL
-END PGP SIGNATURE End Message ---
Bug#979664: apache2: autopkgtest regression in testing: Failed test 2 in t/modules/data.t at line 21
Source: apache2 Version: 2.4.46-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent change in testing the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/a/apache2/9549366/log.gz # Failed test 2 in t/modules/data.t at line 21 t/modules/data.t Failed 1/2 subtests [...] Test Summary Report --- t/modules/data.t (Wstat: 0 Tests: 2 Failed: 1) Failed test: 2 Files=134, Tests=10102, 318 wallclock secs ( 3.23 usr 0.30 sys + 201.11 cusr 50.96 csys = 255.60 CPU) Result: FAIL Failed 1/134 test programs. 1/10102 subtests failed. [warning] server localhost:8529 shutdown [ error] error running tests (please examine t/logs/error_log) OpenPGP_signature Description: OpenPGP digital signature
Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default
Hi (again)! On Sat, 9 Jan 2021 at 17:53, Vagrant Cascadian wrote: > > On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > > Oh, I have sadly forgotten to mention another thing. > > > > On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer > > wrote: > >> # __FILE__ is a public, well defined API > > > > According to: > > Adrian Bunks mentions it in > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#10 > > Holger Levsen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#42 > > Mattia Rizzolo on > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#192 > > > > The ability of gcc to change __FILE__ was a patch that, at the time of > > those writings, wasn't yet accepted. > > That is no longer the case. The fixfilepath feature enabled in dpkg only > uses features (e.g. -ffile-prefix-map) available in both upstream GCC > (>=9? or 8? ~2018) and Clang (>= 10), possibly other compilers as > well. There are no special patches to toolchains needed to enable this > feature. This is actually good to read! > > Even more, Ximion Luo wrote on > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#212 > > > > The GCC patch (neither the previous nor the planned version) does > > not change the default behaviour of __FILE__, and was never intended > > to. Instead, it gives users the ability to rewrite __FILE__, more > > specifically a prefix of it. > > > > makes it clear that the default behaviour is not changed. So if the > > patch got accepted (did it get accepted?) it was only to allow > > reproducible people to break API in order to get reproducibility. > > Since then an alternate implementation was implemented that the > reproducible=+fixfilepath feature in dpkg takes advantage of, in order > to implement this feature in another distribution, if I recall > correctly. > > It didn't address all the cases of the old GCC patches that Ximin > submitted, but the Reproducible Builds team decided in 2018 to make use > of upstream supported features only and dropped all of our patches to > GCC. > > The notable difference is that it not longer makes use of an environment > variable; it requires passing the -ffile-prefix-map option to the > compiler. The dpkg patch simply adds this to the default relevent *FLAGS > variables. > > (For historical completeness, though somewhat an aside to the topic at > hand, the -ffile-prefix-map approach does not address all the cases of > the former patches to GCC as the compiler flags sometimes end up in > various shipped artifacts in *some* cases, though certainly not all.) Again, good to read. > > This in itself, if something has not changed in the meantime, marks > > another reference that __FILE__ is a public, well defined API. > > I think reading #876901 demonstrates that the case can be made either > way; it not as well defined as you make it out to be. As stated in my previous mail I was wrong here, as demonstrated by Mattias. I even just updated the base Qt bug accordingly. Thanks for being so informative too! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default
On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > Oh, I have sadly forgotten to mention another thing. > > On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer > wrote: >> # __FILE__ is a public, well defined API > > According to: > Adrian Bunks mentions it in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#10 > Holger Levsen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#42 > Mattia Rizzolo on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#192 > > The ability of gcc to change __FILE__ was a patch that, at the time of > those writings, wasn't yet accepted. That is no longer the case. The fixfilepath feature enabled in dpkg only uses features (e.g. -ffile-prefix-map) available in both upstream GCC (>=9? or 8? ~2018) and Clang (>= 10), possibly other compilers as well. There are no special patches to toolchains needed to enable this feature. > Even more, Ximion Luo wrote on > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#212 > > The GCC patch (neither the previous nor the planned version) does > not change the default behaviour of __FILE__, and was never intended > to. Instead, it gives users the ability to rewrite __FILE__, more > specifically a prefix of it. > > makes it clear that the default behaviour is not changed. So if the > patch got accepted (did it get accepted?) it was only to allow > reproducible people to break API in order to get reproducibility. Since then an alternate implementation was implemented that the reproducible=+fixfilepath feature in dpkg takes advantage of, in order to implement this feature in another distribution, if I recall correctly. It didn't address all the cases of the old GCC patches that Ximin submitted, but the Reproducible Builds team decided in 2018 to make use of upstream supported features only and dropped all of our patches to GCC. The notable difference is that it not longer makes use of an environment variable; it requires passing the -ffile-prefix-map option to the compiler. The dpkg patch simply adds this to the default relevent *FLAGS variables. (For historical completeness, though somewhat an aside to the topic at hand, the -ffile-prefix-map approach does not address all the cases of the former patches to GCC as the compiler flags sometimes end up in various shipped artifacts in *some* cases, though certainly not all.) > This in itself, if something has not changed in the meantime, marks > another reference that __FILE__ is a public, well defined API. I think reading #876901 demonstrates that the case can be made either way; it not as well defined as you make it out to be. live well, vagrant signature.asc Description: PGP signature
Bug#979583: marked as done (golang-github-spf13-cobra: autopkgtest regression in testing: date of execution is capture in comparison)
Your message dated Sat, 09 Jan 2021 20:48:48 + with message-id and subject line Bug#979583: fixed in golang-github-spf13-cobra 1.1.1-2 has caused the Debian Bug report #979583, regarding golang-github-spf13-cobra: autopkgtest regression in testing: date of execution is capture in comparison 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.) -- 979583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-spf13-cobra Version: 1.1.1-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With time moving the year to 2021, the autopkgtest of your package started to fail. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-spf13-cobra/9459756/log.gz === RUN TestGoldenAddCmd add_test.go:26: "/tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go" and "testdata/test.go.golden" are not equal! $ diff -u /tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go testdata/test.go.golden --- /tmp/autopkgtest-lxc.0dv6r0gd/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/spf13/cobra/cobra/cmd/testproject/cmd/test.go 2021-01-06 19:13:34.418670146 + +++ testdata/test.go.golden 2020-10-24 09:28:37.0 + @@ -1,5 +1,5 @@ /* -Copyright © 2021 NAME HERE +Copyright © 2020 NAME HERE Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. exit status 1 --- FAIL: TestGoldenAddCmd (0.00s) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-github-spf13-cobra Source-Version: 1.1.1-2 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of golang-github-spf13-cobra, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated golang-github-spf13-cobra 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: Sun, 10 Jan 2021 04:28:49 +0800 Source: golang-github-spf13-cobra Architecture: source Version: 1.1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 979583 Changes: golang-github-spf13-cobra (1.1.1-2) unstable; urgency=medium . * Team upload. * Add patch to set year to fixed value in golden tests (Closes: #979583) * Update Section to golang * Update Standards-Version to 4.5.1 * Bump uscan watch file version to 4 Checksums-Sha1: 9a39afc24166f11a07726daf11e3357091698428 1954 golang-github-spf13-cobra_1.1.1-2.dsc 526c8ceb003e5d896cb1a3709f1b2412920da050 7500 golang-github-spf13-cobra_1.1.1-2.debian.tar.xz 6a59b9f8839eae5eeca2dc4fc2fab71f3b56e047 7399 golang-github-spf13-cobra_1.1.1-2_amd64.buildinfo Checksums-Sha256: b678b87f2c9a107164bfd3522e39a39abf5a4567b636f422632ce49cc493a152 1954 golang-github-spf13-cobra_1.1.1-2.dsc b348ceeaa50a6dcefcaf97dfe22660a52746754058f21823f4371516ae4c6809 7500 golang-github-spf13-cobra_1.1.1-2.debian.tar.xz 9286d60ba523472cc44e09e667336b0b2c20a410e047649901dacca4b6a6ff5a 7399 golang-github-spf13-cobra_1.1.1-2_amd64.buildinfo Files: 72bae4047a5161c8e8eca255d2a4c68d 1954 golang optional golang-github-spf13-cobra_1.1.1-2.dsc f2300d7241337d355e52d2d59391ea50 7500 golang optional golang-github-spf13-cobra_1.1.1-2.debian.tar.xz 2e7b29feddefb6e5e0250890b71f125c 7399 golang optional golang-github-spf13-cobra_1.1.1-2_amd64.buildinfo -BEGIN
Bug#979570: marked as done (dpkg: Breaks perfectly valid usage of __FILE__)
Your message dated Sat, 9 Jan 2021 17:47:09 -0300
with message-id
and subject line Re: Updating dpkg-buildflags to enable
reproducible=+fixfilepath by default
has caused the Debian Bug report #979570,
regarding dpkg: Breaks perfectly valid usage of __FILE__
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.)
--
979570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpkg
Version: 1.20.6
Severity: serious
Justification: Breaks well defined functionality
X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net,
reproducible-bui...@lists.alioth.debian.org
Hi! As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901
mangling __FILE__, even if for reproducible builds, breaks a perfectly valid
usage of __FILE__.
Please revert #974087 until someone provides a valid patch for QFINDTESTDATA
and it's well tested.
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf
Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Sat, 9 Jan 2021 at 16:52, Mattia Rizzolo wrote:
>
> On Sat, Jan 09, 2021 at 08:37:48PM +0100, Samuel Thibault wrote:
> > Lisandro Damián Nicanor Pérez Meyer, le sam. 09 janv. 2021 15:53:41 -0300,
> > a ecrit:
> > > # __FILE__ is a public, well defined API
> >
> > ? My copy of C11 says
> >
> > “
> > __FILE__ The presumed name of the current source file (a character string
> > literal)
> > ”
> >
> > that's not so well-defined. I would not expect it to necessarily
> > contain the path to it.
>
> In fact, empirically I've seen that __FILE__ is expanded to whatever
> path gets passed to the compiler.
> You can easily see how stuff build with cmake get a full path in there,
> whereas stuff built with make gets a path relative to the Makefile.
Mattias has just showed me that in fact __FILE__ is too malleable:
mattia@warren /tmp/tmp % cat test.c
#include
int main() {
printf("%s\n", __FILE__);
}
mattia@warren /tmp/tmp % gcc test.c ; ./a.out
test.c
mattia@warren /tmp/tmp % gcc ./test.c ; ./a.out
./test.c
mattia@warren /tmp/tmp % gcc /tmp/tmp/./test.c ; ./a.out
/tmp/tmp/./test.c
So yes, the cornerstone of my assumption was totally wrong. My
apologies for all the noise, all I can say is: today I learned
something new.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/--- End Message ---
Processed: Bug#979583 marked as pending in golang-github-spf13-cobra
Processing control commands: > tag -1 pending Bug #979583 [src:golang-github-spf13-cobra] golang-github-spf13-cobra: autopkgtest regression in testing: date of execution is capture in comparison Added tag(s) pending. -- 979583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979583: marked as pending in golang-github-spf13-cobra
Control: tag -1 pending Hello, Bug #979583 in golang-github-spf13-cobra 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/go-team/packages/golang-github-spf13-cobra/-/commit/99b7f2093b5bfecd14d140a6867c7f9a4da468ca Add patch to set year to fixed value in golden tests (Closes: #979583) (this message was generated automatically) -- Greetings https://bugs.debian.org/979583
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
On Sat, Jan 09, 2021 at 09:25:56PM +0100, Paul Gevers wrote: > Hi Adrian, Hi Paul, > On 09-01-2021 20:45, Adrian Bunk wrote: > > Considering the fact that noone ever understood what the problem was, > > could you re-enable the autopkgtest to see whether any problems are > > still present? > > Why do you think it's disabled (it's not AFAICT)? you are saying the version in unstable passes all tests for migration, and needs only this bug closed? At least I am not seeing any problem that has been observed during the past 8 months that needs action. > Paul cu Adrian
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
Hi Adrian, On 09-01-2021 20:45, Adrian Bunk wrote: > Considering the fact that noone ever understood what the problem was, > could you re-enable the autopkgtest to see whether any problems are > still present? Why do you think it's disabled (it's not AFAICT)? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#957166: marked as done (efingerd: ftbfs with GCC-10)
Your message dated Sat, 09 Jan 2021 20:17:52 +
with message-id
and subject line Bug#957166: fixed in efingerd 1.6.5+nmu1
has caused the Debian Bug report #957166,
regarding efingerd: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:efingerd
Version: 1.6.5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/efingerd_1.6.5_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package efingerd
dpkg-buildpackage: info: source version 1.6.5
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Radovan Garabík
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp install-stamp
debconf-updatepo
# Add here commands to clean up after the build process.
/usr/bin/make -f Makefile.debian clean
make[1]: Entering directory '/<>'
rm -f *~ *.o efingerd
make[1]: Leaving directory '/<>'
dh_clean
debian/rules build
dh_testdir
# Add here commands to compile the package.
/usr/bin/make -f Makefile.debian
make[1]: Entering directory '/<>'
gcc -O2 -Wall -c efingerd.c
gcc -O2 -Wall -c child.c
child.c: In function ‘inetd_service’:
child.c:193:54: warning: pointer targets in passing argument 3 of ‘getpeername’
differ in signedness [-Wpointer-sign]
193 | if (getpeername(sd_in, (struct sockaddr *) , ) == -1) {
| ^~~~
| |
| int *
In file included from efingerd.h:25,
from child.c:16:
/usr/include/x86_64-linux-gnu/sys/socket.h:131:26: note: expected ‘socklen_t *
restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
131 |socklen_t *__restrict __len) __THROW;
|~~^
child.c:200:54: warning: pointer targets in passing argument 3 of ‘getsockname’
differ in signedness [-Wpointer-sign]
200 | if (getsockname(sd_in, (struct sockaddr *) , ) == -1) {
| ^~~~
| |
| int *
In file included from efingerd.h:25,
from child.c:16:
/usr/include/x86_64-linux-gnu/sys/socket.h:117:26: note: expected ‘socklen_t *
restrict’ {aka ‘unsigned int * restrict’} but argument is of type ‘int *’
117 |socklen_t *__restrict __len) __THROW;
|~~^
child.c:184:9: warning: variable ‘reqstat’ set but not used
[-Wunused-but-set-variable]
184 | int reqstat;
| ^~~
child.c:180:20: warning: variable ‘laddr’ set but not used
[-Wunused-but-set-variable]
180 | struct in_addr laddr, raddr;
|^
gcc -O2 -Wall efingerd.o child.o -o efingerd -lident
/usr/bin/ld: child.o:(.bss+0x0): multiple definition of `display_full_name';
efingerd.o:(.bss+0x0): first defined here
/usr/bin/ld: child.o:(.bss+0x5): multiple definition of `ignore_user';
Processed: tagging 975535
Processing commands for cont...@bugs.debian.org: > tags 975535 + ftbfs Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:r-cran-testthat: fails to migrate to testing for too long: (Build-)Depends on non-migrating r-cran-brio
Processing control commands: > close -1 3.0.0-1 Bug #979659 [src:r-cran-testthat] src:r-cran-testthat: fails to migrate to testing for too long: (Build-)Depends on non-migrating r-cran-brio Marked as fixed in versions r-cran-testthat/3.0.0-1. Bug #979659 [src:r-cran-testthat] src:r-cran-testthat: fails to migrate to testing for too long: (Build-)Depends on non-migrating r-cran-brio Marked Bug as done -- 979659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979659: src:r-cran-testthat: fails to migrate to testing for too long: (Build-)Depends on non-migrating r-cran-brio
Source: r-cran-testthat Version: 2.3.2-2 Severity: serious Control: close -1 3.0.0-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:r-cran-testthat in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=r-cran-testthat OpenPGP_signature Description: OpenPGP digital signature
Bug#957068: marked as done (cavezofphear: ftbfs with GCC-10)
Your message dated Sat, 09 Jan 2021 19:48:22 + with message-id and subject line Bug#957068: fixed in cavezofphear 0.5.1-1.1 has caused the Debian Bug report #957068, regarding cavezofphear: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cavezofphear Version: 0.5.1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/cavezofphear_0.5.1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-bbe41f8c-fbd7-4c4d-9a89-9eca5c12783b SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package cavezofphear dpkg-buildpackage: info: source version 0.5.1-1 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Håkon Nessjøen dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh: warning: Compatibility levels before 9 are deprecated (level 8 in use) dh_auto_clean dh_auto_clean: warning: Compatibility levels before 9 are deprecated (level 8 in use) make -j1 clean make[1]: Entering directory '/<>' rm -f phear editor make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 9 are deprecated (level 8 in use) debian/rules build dh build dh: warning: Compatibility levels before 9 are deprecated (level 8 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 9 are deprecated (level 8 in use) dh_auto_build dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 8 in use) make -j1 make[1]: Entering directory '/<>' cd src && make make[2]: Entering directory '/<>/src' gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c main.c -o main.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c frame.c -o frame.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c isready.c -o isready.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c loadmap.c -o loadmap.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c misc.c -o misc.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c gplot.c -o gplot.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c splash.c -o splash.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c chk.c -o chk.o
Processed: found 979590 in 2:1.7.0-1 ...
Processing commands for cont...@bugs.debian.org: > found 979590 2:1.7.0-1 Bug #979590 [libx11] libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome Bug #979618 [libx11] chromium freezes on start, triggering a force quit by gnome There is no source info for the package 'libx11' at version '2:1.7.0-1' with architecture '' Unable to make a source version for version '2:1.7.0-1' Marked as found in versions 2:1.7.0-1. Marked as found in versions 2:1.7.0-1. > retitle 979590 libx11 possible ABI break in libx11 breaks libx11-xcb1 and > that breaks chromium Bug #979590 [libx11] libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome Bug #979618 [libx11] chromium freezes on start, triggering a force quit by gnome Changed Bug title to 'libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium' from 'libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome'. Changed Bug title to 'libx11 possible ABI break in libx11 breaks libx11-xcb1 and that breaks chromium' from 'chromium freezes on start, triggering a force quit by gnome'. > outlook 979590 see message #34 describing how > https://github.com/freedesktop/xorg-libX11/commit/dbb55e1 broke the internal > ABI Outlook recorded from message bug 979590 message Outlook recorded from message bug 979590 message > thanks Stopping processing here. Please contact me if you need assistance. -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#971755: shovill: built on architectures for which it's uninstallable
Processing control commands:
> reopen -1
Bug #971755 {Done: Andreas Tille } [shovill] shovill: built
on architectures for which it's uninstallable
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions shovill/1.1.0-3.
--
971755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971755: shovill: built on architectures for which it's uninstallable
Control: reopen -1 Hi, On Tue, 6 Oct 2020 06:56:57 -0700 Steve Langasek wrote: > Hi Nilesh, > > The shovill package is not migratable to testing because it depends on a > number of packages that are not portable and unavailable on !amd64 (spades, > skesa, megahit) but a binary is built on these architectures. > > Since these per-arch binaries exist, they are expected by the archive policy > to be installable. > > It looks to me like this is solvable by making shovill an Arch: all package > instead of an Arch: any package, since shovill is a simple perl script with > no compiled binaries. An Arch: all package that is uninstallable on _arm64_ is not allowed to migrate either, as specified in the configuration: https://salsa.debian.org/release-team/britney2/-/blob/master/britney.conf#L31 excuses (https://tracker.debian.org/pkg/shovill): > Issues preventing migration: > shovill/arm64 has unsatisfiable dependency My suggestion is adding dummy "Build-Depends-Arch: spades, skesa, megahit", and making the binary package Arch: any. Then the package will probably not be built on architectures where it is uninstallable. More robust but verbose solution could be to additionally copy all the rest of the Depends into Build-Depends-Arch, not just the three mentioned. -- Juhani
Bug#952463: [Debichem-devel] Bug#952463: bagel: flaky arm64 autopkgtest: terminate called without an active exception
On Thu, Mar 19, 2020 at 10:16:32AM +0100, Paul Gevers wrote:
>...
> On 25-02-2020 15:56, Michael Banck wrote:
>...
> > On Mon, Feb 24, 2020 at 08:57:40PM +0100, Paul Gevers wrote:
> >> https://ci.debian.net/data/autopkgtest/testing/arm64/b/bagel/4258642/log.gz
> >>
> >> running test case 'hf_sto3g_relfci_gaunt'... terminate called without an
> >> active exception
> >> /tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh:
> >> line 85: 15487 Aborted BAGEL test/${testname}.json >
> >> ${testname}.out
> >> /tmp/autopkgtest-lxc.q3t4znog/downtmp/build.F1y/src/debian/tests/testsuite.sh:
> >> fork: retry: Resource temporarily unavailable
> >> FAILED.
> >
> > This looks like the arm64 authobuilder has not enough memory or
> > something?
>
> autopkgtest don't run on the autobuilders, but I the message is of
> course still relevant. The arm64 workers have plenty of memory, so if
> the memory is exhausted, the test should implement a check and fail
> gracefully if there isn't enough to run the test. Interestingly, in the
> logs I check I see different tests and different amount of tests fail.
> Are the tests run in parallel? Could this be turned off (at least to see
> if things become more stable) or the amount of parallelism be reduced?
The results from accidental builds in recent months look good:
https://ci.debian.net/packages/b/bagel/unstable/arm64/
Considering the fact that noone ever understood what the problem was,
could you re-enable the autopkgtest to see whether any problems are
still present?
> Side note which warrants it's own bug; bagel (at least the autopkgtest)
> needs an update due to the new mpich (seen both on arm64 and amd64):
> running test case 'hf_sto3g_relfci_coulomb'... BAGEL: error while
> loading shared libraries: libmpichcxx.so.12: cannot open shared object
> file: No such file or directory
>...
This was a bug in libmpich12 that was fixed/reverted in April.
> Paul
cu
Adrian
Bug#966861: marked as done (vilistextum: FTBFS: ld: html.o:./src/text.h:16: multiple definition of `ch'; charset.o:./src/text.h:16: first defined here)
Your message dated Sat, 09 Jan 2021 19:36:01 + with message-id and subject line Bug#966861: fixed in vilistextum 2.6.9-1.3 has caused the Debian Bug report #966861, regarding vilistextum: FTBFS: ld: html.o:./src/text.h:16: multiple definition of `ch'; charset.o:./src/text.h:16: first defined here 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.) -- 966861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vilistextum Version: 2.6.9-1.2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wall -O2 -ansi -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -I/usr/local/include -Wl,-z,relro -L/usr/local/lib -o vilistextum charset.o > html.o latin1.o html_tag.o lists.o microsoft.o text.o fileio.o main.o util.o > unicode_entities.o > /usr/bin/ld: html.o:./src/text.h:16: multiple definition of `ch'; > charset.o:./src/text.h:16: first defined here > /usr/bin/ld: html.o:./src/main.h:9: multiple definition of > `convert_characters'; charset.o:./src/main.h:9: first defined here > /usr/bin/ld: html.o:./src/main.h:8: multiple definition of `errorlevel'; > charset.o:./src/main.h:8: first defined here > /usr/bin/ld: html.o:./src/text.h:12: multiple definition of `LEFT'; > charset.o:./src/text.h:12: first defined here > /usr/bin/ld: html.o:./src/text.h:13: multiple definition of `CENTER'; > charset.o:./src/text.h:13: first defined here > /usr/bin/ld: html.o:./src/text.h:14: multiple definition of `RIGHT'; > charset.o:./src/text.h:14: first defined here > /usr/bin/ld: html.o:./src/text.h:19: multiple definition of `div_test'; > charset.o:./src/text.h:19: first defined here > /usr/bin/ld: html.o:./src/text.h:18: multiple definition of `paragraph'; > charset.o:./src/text.h:18: first defined here > /usr/bin/ld: html.o:./src/main.h:12: multiple definition of `option_links'; > charset.o:./src/main.h:12: first defined here > /usr/bin/ld: html.o:./src/main.h:13: multiple definition of > `option_links_inline'; charset.o:./src/main.h:13: first defined here > /usr/bin/ld: html.o:./src/main.h:11: multiple definition of > `remove_empty_alt'; charset.o:./src/main.h:11: first defined here > /usr/bin/ld: html.o:./src/main.h:19: multiple definition of `option_no_alt'; > charset.o:./src/main.h:19: first defined here > /usr/bin/ld: html.o:./src/main.h:18: multiple definition of > `option_no_image'; charset.o:./src/main.h:18: first defined here > /usr/bin/ld: html.o:./src/text.h:20: multiple definition of `nooutput'; > charset.o:./src/text.h:20: first defined here > /usr/bin/ld: html.o:./src/text.h:28: multiple definition of `spaces'; > charset.o:./src/text.h:28: first defined here > /usr/bin/ld: html.o:./src/text.h:27: multiple definition of `tab'; > charset.o:./src/text.h:27: first defined here > /usr/bin/ld: html.o:./src/text.h:23: multiple definition of `hr_breite'; > charset.o:./src/text.h:23: first defined here > /usr/bin/ld: html.o:./src/text.h:22: multiple definition of `breite'; > charset.o:./src/text.h:22: first defined here > /usr/bin/ld: html.o:./src/main.h:22: multiple definition of `default_image'; > charset.o:./src/main.h:22: first defined here > /usr/bin/ld: html.o:./src/main.h:20: multiple definition of > `option_output_utf8'; charset.o:./src/main.h:20: first defined here > /usr/bin/ld: html.o:./src/main.h:16: multiple definition of > `transliteration'; charset.o:./src/main.h:16: first defined here > /usr/bin/ld: html.o:./src/main.h:15: multiple definition of `sevenbit'; > charset.o:./src/main.h:15: first defined here > /usr/bin/ld: html.o:./src/main.h:14: multiple definition of `option_title'; > charset.o:./src/main.h:14: first defined here > /usr/bin/ld: html.o:./src/main.h:10: multiple definition of `shrink_lines'; > charset.o:./src/main.h:10: first defined here > /usr/bin/ld: html.o:./src/main.h:7: multiple definition of `convert_tags'; > charset.o:./src/main.h:7: first defined here > /usr/bin/ld: html.o:./src/main.h:6: multiple definition of `palm'; > charset.o:./src/main.h:6: first defined here > /usr/bin/ld: latin1.o:./src/main.h:8: multiple definition of `errorlevel'; > charset.o:./src/main.h:8: first defined here > /usr/bin/ld: latin1.o:./src/main.h:22: multiple definition of > `default_image'; charset.o:./src/main.h:22: first defined here > /usr/bin/ld:
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 979590 libx11 Bug #979590 [chromium] libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome Bug #979618 [chromium] chromium freezes on start, triggering a force quit by gnome Bug reassigned from package 'chromium' to 'libx11'. Bug reassigned from package 'chromium' to 'libx11'. No longer marked as found in versions chromium/87.0.4280.88-0.4. No longer marked as found in versions chromium/87.0.4280.88-0.4. Ignoring request to alter fixed versions of bug #979590 to the same values previously set Ignoring request to alter fixed versions of bug #979618 to the same values previously set > End of message, stopping processing here. Please contact me if you need assistance. -- 979590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979590 979618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979656: Patch for llvm-toolchain-7
Additional note: I actually tested the patches on two different machines to be sure (with and without the patch) and built the package in interactive mode (i.e. dpkg-buildpackage, not sbuild). In the machine where I didn't apply the patch, this is what was shown on screen at the moment of hangup: [100%] Running lld test suite cd /home/sanvila/llvm-toolchain-7-7.0.1/build-llvm/tools/clang/stage2-bins/tools/lld/test && /usr/bin/python2.7 /home/sanvila/llvm-toolchain-7-7.0.1/build-llvm/tools/clang/stage2-bins/./bin/llvm-lit -sv --param lld_site_config=/home/sanvila/llvm-toolchain-7-7.0.1/build-llvm/tools/clang/stage2-bins/tools/lld/test/lit.site.cfg --param lld_unit_site_config=/home/sanvila/llvm-toolchain-7-7.0.1/build-llvm/tools/clang/stage2-bins/tools/lld/test/Unit/lit.site.cfg /home/sanvila/llvm-toolchain-7-7.0.1/build-llvm/tools/clang/stage2-bins/tools/lld/test -- Testing: 1808 tests, 1 threads -- 92% [--] ETA: 00:00:10 lld :: mach-o/write-final-sections.yaml I agree that this is for historical interest only, as I guess that nobody here wants to investigate the failure, and everybody here probably agrees that disabling the tests is a much better course of action. Thanks.
Processed: Re: Bug#971755: shovill: built on architectures for which it's uninstallable
Processing commands for cont...@bugs.debian.org:
> unarchive 971755
Bug #971755 {Done: Andreas Tille } [shovill] shovill: built
on architectures for which it's uninstallable
Unarchived Bug 971755
> stop
Stopping processing here.
Please contact me if you need assistance.
--
971755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: version tracking for llvm bugs
Processing commands for cont...@bugs.debian.org:
> reassign 979655 src:llvm-toolchain-6.0
Bug #979655 {Done: Debian FTP Masters }
[llvm-toolchain-6.0] llvm-toolchain-6.0: Test suite hangs the autobuilder on
single-CPU systems
Bug reassigned from package 'llvm-toolchain-6.0' to 'src:llvm-toolchain-6.0'.
Ignoring request to alter found versions of bug #979655 to the same values
previously set
Ignoring request to alter fixed versions of bug #979655 to the same values
previously set
> reassign 979656 src:llvm-toolchain-7
Bug #979656 {Done: Debian FTP Masters }
[llvm-toolchain-7] llvm-toolchain-7: Test suite hangs the autobuilder on
single-CPU systems
Bug reassigned from package 'llvm-toolchain-7' to 'src:llvm-toolchain-7'.
Ignoring request to alter found versions of bug #979656 to the same values
previously set
Ignoring request to alter fixed versions of bug #979656 to the same values
previously set
> found 979655 1:6.0.1-10
Bug #979655 {Done: Debian FTP Masters }
[src:llvm-toolchain-6.0] llvm-toolchain-6.0: Test suite hangs the autobuilder
on single-CPU systems
Marked as found in versions llvm-toolchain-6.0/1:6.0.1-10 and reopened.
> found 979656 1:7.0.1-8+deb10u2
Bug #979656 {Done: Debian FTP Masters }
[src:llvm-toolchain-7] llvm-toolchain-7: Test suite hangs the autobuilder on
single-CPU systems
Marked as found in versions llvm-toolchain-7/1:7.0.1-8+deb10u2 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979655
979656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979656: Patch for llvm-toolchain-7
tags 979656 + patch
thanks
Dear LLVM maintainers:
Please apply the following patch for Debian 10.8.
Thanks.diff --git a/debian/rules b/debian/rules
index 53e229673..1016f3b48 100755
--- a/debian/rules
+++ b/debian/rules
@@ -22,7 +22,8 @@ SONAME_OPENMP := 5
# Manage the case when the version is 3.5~svn213052-1~exp1 or 3.4.2-1
DEBIAN_REVISION := $(shell dpkg-parsechangelog | sed -rne "s,^Version: 1:([0-9.]+)(~|-)(.*),\3,p")
ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
- NJOBS := -j $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
+ NPARALLEL := $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
+ NJOBS := -j $(NPARALLEL)
endif
VENDOR=$(shell lsb_release -is)
@@ -762,10 +763,13 @@ endif
# Clang extra tests (ex: clang-tidy)
$(MAKE) $(NJOBS) -C $(TARGET_BUILD_STAGE2) check-clang-tools || true
+# The test suite is known to hang if there is only one CPU
+ifneq (1,$(NPARALLEL))
# LLD tests
ifeq (${LLD_ENABLE},yes)
$(MAKE) $(NJOBS) -C $(TARGET_BUILD_STAGE2) check-lld || true
endif
+endif
# Sanitizer
$(MAKE) $(NJOBS) -C $(TARGET_BUILD_STAGE2) check-sanitizer || true
Processed: Patch for llvm-toolchain-7
Processing commands for cont...@bugs.debian.org:
> tags 979656 + patch
Bug #979656 {Done: Debian FTP Masters }
[llvm-toolchain-7] llvm-toolchain-7: Test suite hangs the autobuilder on
single-CPU systems
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default
Oh, I have sadly forgotten to mention another thing. On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer wrote: > # __FILE__ is a public, well defined API According to: Adrian Bunks mentions it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#10 Holger Levsen in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#42 Mattia Rizzolo on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#192 The ability of gcc to change __FILE__ was a patch that, at the time of those writings, wasn't yet accepted. Even more, Ximion Luo wrote on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#212 The GCC patch (neither the previous nor the planned version) does not change the default behaviour of __FILE__, and was never intended to. Instead, it gives users the ability to rewrite __FILE__, more specifically a prefix of it. makes it clear that the default behaviour is not changed. So if the patch got accepted (did it get accepted?) it was only to allow reproducible people to break API in order to get reproducibility. This in itself, if something has not changed in the meantime, marks another reference that __FILE__ is a public, well defined API.
Processed: Patch for llvm-toolchain-6.0
Processing commands for cont...@bugs.debian.org:
> tags 979655 + patch
Bug #979655 {Done: Debian FTP Masters }
[llvm-toolchain-6.0] llvm-toolchain-6.0: Test suite hangs the autobuilder on
single-CPU systems
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979655: Patch for llvm-toolchain-6.0
tags 979655 + patch
thanks
Dear LLVM maintainers:
Please apply the following patch for Debian 10.8.
Thanks.diff --git a/debian/rules b/debian/rules
index 8a12bb32..58d55a4f 100755
--- a/debian/rules
+++ b/debian/rules
@@ -17,7 +17,8 @@ SONAME_EXT := 1
# Manage the case when the version is 1:3.5~svn213052-1~exp1 or 1:3.4.2-1
DEBIAN_REVISION := $(shell dpkg-parsechangelog | sed -rne "s,^Version: 1:([0-9.]+)(~|-)(.*),\3,p")
ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
- NJOBS := -j $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
+ NPARALLEL := $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS
+ NJOBS := -j $(NPARALLEL)
endif
VENDOR=$(shell lsb_release -is)
@@ -559,10 +560,13 @@ endif
# Clang extra tests (ex: clang-tidy)
$(MAKE) $(NJOBS) -C $(TARGET_BUILD) check-clang-tools || true
+# The test suite is known to hang if there is only one CPU
+ifneq (1,$(NPARALLEL))
# LLD tests
ifeq (${LLD_ENABLE},yes)
$(MAKE) $(NJOBS) -C $(TARGET_BUILD) check-lld || true
endif
+endif
# Sanitizer
$(MAKE) $(NJOBS) -C $(TARGET_BUILD) check-sanitizer || true
Processed: clone for buster
Processing commands for cont...@bugs.debian.org:
> severity 819278 serious
Bug #819278 {Done: Debian FTP Masters }
[src:llvm-toolchain-3.8] llvm-toolchain-3.8: Build not reliable
Severity set to 'serious' from 'normal'
> clone 819278 -1
Bug #819278 {Done: Debian FTP Masters }
[src:llvm-toolchain-3.8] llvm-toolchain-3.8: Build not reliable
Bug 819278 cloned as bug 979655
> clone 819278 -2
Bug #819278 {Done: Debian FTP Masters }
[src:llvm-toolchain-3.8] llvm-toolchain-3.8: Build not reliable
Bug 819278 cloned as bug 979656
> reassign -1 llvm-toolchain-6.0
Bug #979655 {Done: Debian FTP Masters }
[src:llvm-toolchain-3.8] llvm-toolchain-3.8: Build not reliable
Bug reassigned from package 'src:llvm-toolchain-3.8' to 'llvm-toolchain-6.0'.
No longer marked as found in versions llvm-toolchain-3.8/1:3.8-2.
No longer marked as fixed in versions 1:3.8.1-27+rm.
> reassign -2 llvm-toolchain-7
Bug #979656 {Done: Debian FTP Masters }
[src:llvm-toolchain-3.8] llvm-toolchain-3.8: Build not reliable
Bug reassigned from package 'src:llvm-toolchain-3.8' to 'llvm-toolchain-7'.
No longer marked as found in versions llvm-toolchain-3.8/1:3.8-2.
No longer marked as fixed in versions 1:3.8.1-27+rm.
> retitle -1 llvm-toolchain-6.0: Test suite hangs the autobuilder on single-CPU
> systems
Bug #979655 {Done: Debian FTP Masters }
[llvm-toolchain-6.0] llvm-toolchain-3.8: Build not reliable
Changed Bug title to 'llvm-toolchain-6.0: Test suite hangs the autobuilder on
single-CPU systems' from 'llvm-toolchain-3.8: Build not reliable'.
> retitle -2 llvm-toolchain-7: Test suite hangs the autobuilder on single-CPU
> systems
Bug #979656 {Done: Debian FTP Masters }
[llvm-toolchain-7] llvm-toolchain-3.8: Build not reliable
Changed Bug title to 'llvm-toolchain-7: Test suite hangs the autobuilder on
single-CPU systems' from 'llvm-toolchain-3.8: Build not reliable'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
819278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819278
979655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979655
979656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default
Note: in case we do not agree on this topic this will be the text I'll send to the tech-ctte. Let me start by noting that I have nothing against reproducibility. In fact quite the opposite: I love the idea... as long as it's properly implemented. The problem here is that __FILE__ is a public, well defined API with very valid use cases (more on this below), even if the current implementation of all the major compilers go against reproducibility. So if we want to mangle __FILE__ (thus breaking API) this should be done by an opt-in, and **never** by opting out. Else we risk breaking a valid implementation, be it already on the archive any new package added afterwards. Even more: we library maintainers continuously ask our upstreams to keep their API as stable as possible, and if not possible following some rules (SONAME change, for example). I will present an option to do the same ourselves without breaking API/ABI. # __FILE__ is a public, well defined API During the course of #876901 many reasons were used to both say that __FILE__ is or not a well defined API. In fact one of the evidences used where the compiler's documentation. For example https://gcc.gnu.org/onlinedocs/cpp/Standard-Predefined-Macros.html (enphasis mine): This macro expands to the name of the current input file, in the form of a C string constant. **This is the path by which the preprocessor opened the file**, not the short name specified in ‘#include’ or as the input file name argument. For example, "/usr/local/include/myheader.h" is a possible expansion of this macro. This definition says that it's up to the preprocessor to define the path. So, what has been the behaviour of all major compilers during all these years? Using the full path. The proof of this is Qt itself. Check https://sources.debian.org/src/qtbase-opensource-src/5.15.2+dfsg-2/src/testlib/qtestcase.h/#L216 This code has been working on **every** platform Qt works without any change. Qt is compiled in a myriad of OSs, using a myriad of compilers. They all do the exact same thing. So developers depend on a very stable definition of an API. And we all know that breaking API is bad, except if done carefully (read below). # Doing the right thing This is just an idea of "doing the right thing", like bumping SONAME on a library. It definitely doesn't have to be the only one. I understand that the reproducibility people do not want to consider providing the same build path. While this is arguable I do understand that reproducibility without depending on the build path is a good thing. So I've tried to come up with a path to achieve this. ## New macro and warning (if they do not exist already) This would be the first step. The idea is to provide a new macro that, by definition and documentation, it can be mangled with the help of the build system, much as you are currently doing with __FILE__ now. The second step in this is to make compilers create a reproducibility warning if some code uses __FILE__. This will have three effects effects: - discouraging it's use - creating awareness on reproducibility. - making other distros jump into reproducibility in a much easier way. ## Mangling by opting-in, or what to do in the meantime Of course we want to make things reproducible as fast as possible too. This is why mangling __FILE__ was considered and implemented. But this is breaking API, no matter how you look at it. But that doesn't means it can not be used: if a package can be built mangling __FILE__ in order to get a reproducible way then the maintainer should really consider opting *in* for the change, but never ever should the maintainer be forced to opt *out* using a broken API. In fact I consider all the "fixes" of opting in a bug, and forcing this change a couple of weeks before freeze even worse. So I propose you to undo the change in dpkg and, after the release, starting to work on letting maintainers opting in. Regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#979600: marked as done (src:ucx: invalid maintainer address)
Your message dated Sat, 09 Jan 2021 17:41:59 + with message-id and subject line Bug#979600: fixed in ucx 1.10.0~rc1-2 has caused the Debian Bug report #979600, regarding src:ucx: invalid maintainer address 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.) -- 979600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ucx Version: 1.10.0~rc1-1 Severity: serious X-Debbugs-Cc: Alastair McKinstry The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Fri, 08 Jan 2021 19:49:42 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: debian-science-maintain...@lists.alioth.debian.net Unrouteable address Reporting-MTA: dns; mailly.debian.org Action: failed Final-Recipient: rfc822;debian-science-maintainers@lists.alioth.debian.net Status: 5.0.0 --- End Message --- --- Begin Message --- Source: ucx Source-Version: 1.10.0~rc1-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of ucx, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated ucx 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, 09 Jan 2021 17:05:15 + Source: ucx Architecture: source Version: 1.10.0~rc1-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 979600 Changes: ucx (1.10.0~rc1-2) unstable; urgency=medium . * Update maintainer list address (net->d.org). Closes: #979600 Checksums-Sha1: 761ecf0f52c1bf3a110f7f8a099677ac75346aae 2350 ucx_1.10.0~rc1-2.dsc 5c6a9606e6ac50ce7cee9cae663b620fd9fdef0d 5164 ucx_1.10.0~rc1-2.debian.tar.xz Checksums-Sha256: f7d05e0da0808b01e772a665dbead7b865a5284a72e01d995470cfd9915e8f64 2350 ucx_1.10.0~rc1-2.dsc 956da8c2382b4dea8c44a2fb3c8188999bb3f2d522e1ed8b16c8b3476fc89353 5164 ucx_1.10.0~rc1-2.debian.tar.xz Files: 81c937b5aa932054cad500763c09d14d 2350 science optional ucx_1.10.0~rc1-2.dsc dd02f859c00b6ef086a41cc1573807ef 5164 science optional ucx_1.10.0~rc1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl/55QAACgkQy+a7Tl2a 06XwUQ//TqAlUfZKNvl96oaO9Oez5YRh6g1V1g2ra85kvBMKTdtt5CdrF5c7FLAy Dscx3ur+/L7xePXdYC+HfHqhmmxy8FIgdZOfVPrhqaq3pA4J6NGMK5xlfXQLDt7Q ktik7+GTXeZV1OZNHB9Hut10RcaIbrn3/Agj4G4BLSX6FBrvZORliqxrL7Qwgmbi dxewIkxfIiRvAuDuwyz7Z572ZeqAFvYwufb4wR+jIf4GVTMmsr3IKMTQ/Wvjnzaq hG6ayDUN9rjt2RWWQUcpCkf1oK8+W7VqGOQEUiu5wta1JlJ3HYPB15rMgjQx2w3I 248RHilOnJjCt4BSTOo4B4DLv0Ic7YMUmkjifSd1Uv45cjb8ra2WjFnKTWO5edFS qI/Qi4bOYKHnShoxXj8BQjMluoAFBGaIpa1eGj6Pnepm3BlwUfzXMsDMrLM3j7Jg ovwaUUeOWbzL28sjCS3HjkYVjD0H9NH6BYMhiym6GEyiMwIyrr00vcbHttzQQD4J eFPSOVOjIsGyQH1fKsxC6p+avzsjcxCrsjyXLb3tKtYuRc38q8DOqt7+TNmabG9p L0exkaVGTT+DXZoB7bvBO0jaHAnpPRtqp6D5MqlmkXVISrbE7JMxNpOUnZVROjqo l/SmwsmjD/S9XkPljUatEdSJGK0LvBOMaPtB7qjVfzq+1tJ0ORI= =V/hS -END PGP SIGNATURE End Message ---
Bug#969372: marked as done (uwsgi-emperor: SysV init script does nothing)
Your message dated Sat, 09 Jan 2021 17:21:32 + with message-id and subject line Bug#969372: fixed in uwsgi 2.0.19.1-5 has caused the Debian Bug report #969372, regarding uwsgi-emperor: SysV init script does nothing 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.) -- 969372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: uwsgi-emperor Version: 2.0.18-1 Severity: grave Justification: renders package unusable Dear Maintainer, After installing uwsgi-emperor 2.0.18 it's impossible to change the running state of the service, as the provided init-script is doing nothing. This can be easily seen by the script being all of 27 lines long, ending just after setting up the variables, where the one from the 2.0.7 version has a total of 136 lines. As there is no SystemD unit present (as discussed in #833067) this means there is actually no way to start this service. Checking, it seems that this issue is also present in 2.0.14 from stretch, and is present in 2.0.19 for bullseye. -- System Information: Debian Release: 10.5 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages uwsgi-emperor depends on: ii uwsgi-core 2.0.18-1 uwsgi-emperor recommends no packages. uwsgi-emperor suggests no packages. -- Configuration Files: /etc/default/uwsgi-emperor changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: uwsgi Source-Version: 2.0.19.1-5 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of uwsgi, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated uwsgi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jan 2021 17:54:19 +0100 Source: uwsgi Architecture: source Version: 2.0.19.1-5 Distribution: unstable Urgency: medium Maintainer: uWSGI packaging team Changed-By: Jonas Smedegaard Closes: 969372 Changes: uwsgi (2.0.19.1-5) unstable; urgency=medium . * update git-buildpackage settings: + use DEP-14 git branch names + add usage comment * add uwsgi-emperor systemd service; closes: bug#969372, thanks to Rens Houben, Thomas Goirand, Peter Ludikovsky and others * copyright: + use only canonical Source URL + update coverage * declare compliance with Debian Policy 4.5.1 * drop obsolete lintian overrides Checksums-Sha1: f0f4e3b5402492a0fe21491a0c557f78ad37baca 7030 uwsgi_2.0.19.1-5.dsc caa0e3f6072ef94b4ced40c45b02c2a25a4d0c71 71636 uwsgi_2.0.19.1-5.debian.tar.xz de7bdb60ac8ae23470d0ff37d16e98e40a1af1ab 37007 uwsgi_2.0.19.1-5_amd64.buildinfo Checksums-Sha256: de7673a0d2629b03034283e91bbe939543ce219481d8ddc2f7f067f4434a0b60 7030 uwsgi_2.0.19.1-5.dsc d3f446f0af92f465bd1bc9e2cb184cc84437161ca869397a56d469f5c3c6dcfd 71636 uwsgi_2.0.19.1-5.debian.tar.xz c4d9f2f467113db75dd60d2bc39e16c781fea11a3589ac8304f4d2ca8820b014 37007 uwsgi_2.0.19.1-5_amd64.buildinfo Files: 5acc52d3e2f4b128ce1e5628d9dfc165 7030 httpd optional uwsgi_2.0.19.1-5.dsc b8eed6d993814ad210fe51e891585f56 71636 httpd optional uwsgi_2.0.19.1-5.debian.tar.xz 21031b8de38214d742e5858a2772453f 37007 httpd optional uwsgi_2.0.19.1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl/54e0ACgkQLHwxRsGg ASFFlA//byQi3+MtKLV3bqer6/WV6xW5igLYs5f2HykpCd7PMgWHj05pkdF1DUzo dCLWqvsR8920Y6vS41QDOUK6AZwBGu85IufHzT0xnt7dIz/SHKSxCwzp4GzRjczv E6a+88M9WGzsHnuYzDUQTSlPQvsgqeKYQ0dAyGwEQVPFNNibtphjOqE4X4Gg3pkh tJ6nkjoXZsJLEtmt5PFFuOB36RzgDbUQGha8j7UzHI3W4vtWDFekIOyo+ojsiL0a 4Dt68hECgVz8ZHWRb9kEiNwmyP0FWS6E8cf/Trqjn0wFidfWR6QnuUuDISL+EXgS
Bug#979641: src:kboot-utils: invalid maintainer address
Source: kboot-utils Version: 0.4-1 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Sat, 09 Jan 2021 16:49:56 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: osp...@studenti.unina.it host fmvip.unina.it [192.132.34.7] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 ... User unknown Reporting-MTA: dns; muffat.debian.org Action: failed Final-Recipient: rfc822;ospite@studenti.unina.it Status: 5.0.0 Remote-MTA: dns; fmvip.unina.it Diagnostic-Code: smtp; 550 5.1.1 ... User unknown
Bug#979640: src:adv-17v35x: invalid maintainer address
Source: adv-17v35x Version: 5.0.3.0-2 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Alexander Gerasiov , Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Sat, 09 Jan 2021 16:33:34 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: immortalguard...@redlab-i.ru host mx.redlab-i.ru [195.16.34.155] SMTP error from remote mail server after RCPT TO:: 550 5.1.1 : Recipient address rejected: User unknown in local recipient table Reporting-MTA: dns; muffat.debian.org Action: failed Final-Recipient: rfc822;immortalguardian@redlab-i.ru Status: 5.0.0 Remote-MTA: dns; mx.redlab-i.ru Diagnostic-Code: smtp; 550 5.1.1 : Recipient address rejected: User unknown in local recipient table
Bug#976508: Build failure solved
On Tue, 29 Dec 2020, Hilmar Preuße wrote: > This issue has been solved by latest texlive-extra upload (#977646). Sorry for > the inconvenience. What about stable? I believe that muttprint also FTBFS in stable.
Bug#979639: src:sauce: invalid maintainer address
Source: sauce Version: 0.9.0 Severity: serious Tags: bullseye sid X-Debbugs-Cc: Holger Levsen The maintainer address is invalid, see below. Ansgar Start of forwarded message From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Sat, 09 Jan 2021 16:53:55 + This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: i...@davenant.greenend.org.uk Unrouteable address Reporting-MTA: dns; muffat.debian.org Action: failed Final-Recipient: rfc822;ian@davenant.greenend.org.uk Status: 5.0.0
Bug#975492: marked as done (scummvm: FTBFS on big-endian platforms)
Your message dated Sat, 09 Jan 2021 16:54:01 + with message-id and subject line Bug#975492: fixed in scummvm 2.2.0+dfsg1-3 has caused the Debian Bug report #975492, regarding scummvm: FTBFS on big-endian platforms 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.) -- 975492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: scummvm Version: 2.2.0+dfsg1-1 Severity: serious Tags: upstream Justification: ftbfs Dear Maintainer, On big-endian platforms, test/engines/ultima/ultima8/misc/memset_n.h fails because the memset_n functions assume they're running on a little-endian platform. On a big-endian platform, the value written to memory will depend on the alignment: if the value is aligned, it will be written as expected (MSB first), but if it's not aligned, it will be written in a mixture of little- and big-endian. The tests always use the host memory order. Regards, Stephen -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), (100, 'unstable-debug'), (100, 'testing-debug'), (100, 'unstable'), (100, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages scummvm depends on: ii libasound2 1.1.8-1 ii libc62.28-10 ii libfaad2 2.8.8-3 ii libflac8 1.3.2-3 ii libfluidsynth1 1.1.11-1 ii libfreetype6 2.9.1-3+deb10u2 ii libgcc1 1:8.3.0-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libmad0 0.15.1b-10 ii libmpeg2-4 0.5.1-8 ii libogg0 1.3.2-1+b1 ii libpng16-16 1.6.36-6 ii libsdl2-2.0-02.0.9+dfsg1-1 ii libsndio7.0 1.5.0-3 ii libstdc++6 8.3.0-6 ii libtheora0 1.1.1+dfsg.1-15 ii libvorbis0a 1.3.6-2 ii libvorbisfile3 1.3.6-2 ii scummvm-data 2.0.0+dfsg-2 ii zlib1g 1:1.2.11.dfsg-1 scummvm recommends no packages. Versions of packages scummvm suggests: ii beneath-a-steel-sky 0.0372-7 ii drascula1.0+ds3-1 ii flight-of-the-amazon-queen 1.0.0-8 ii fluidsynth 1.1.11-1 ii lure-of-the-temptress 1.1+ds2-3 ii timidity2.14.0-8 -- no debconf information --- End Message --- --- Begin Message --- Source: scummvm Source-Version: 2.2.0+dfsg1-3 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of scummvm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated scummvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jan 2021 17:33:51 +0100 Source: scummvm Architecture: source Version: 2.2.0+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Stephen Kitt Closes: 975492 Changes: scummvm (2.2.0+dfsg1-3) unstable; urgency=medium . * Disable Ultima on platforms where its tests fail. The next release will include a revamped engine which should fix this correctly. Closes: #975492. Checksums-Sha1: 2c96e80474b84c6b3af6408208264a6747544b86 2434 scummvm_2.2.0+dfsg1-3.dsc 344d74e63e6629139772807e0d2b91da5dce6fb9 17676 scummvm_2.2.0+dfsg1-3.debian.tar.xz 53ab61d2e93a052c42cc16d84d7670ac2aeb674a 12718 scummvm_2.2.0+dfsg1-3_source.buildinfo Checksums-Sha256: c0663466c96dee608176e0d05ab9441c5d6d3666af6c3bea4a301741fee2bef8 2434 scummvm_2.2.0+dfsg1-3.dsc 56f35334607ff904555aec407c8c16aaa7a5c3a8e4cf624aeb35cb7c2a72dbf5 17676 scummvm_2.2.0+dfsg1-3.debian.tar.xz 0c47d65f771335c5a7e4d9e97370b95817ae84db59eb36a4ea849f1580c33908 12718 scummvm_2.2.0+dfsg1-3_source.buildinfo Files: d3ffa176062798684f5f2709cee04d36 2434
Bug#978201: Add link to upstream patch/commit
The necessary fix seems to be at https://github.com/crossbario/autobahn-cpp/commit/eac22bd61117ac18b5efee3c6da16a97835055de, applying this fixes building the package.
Processed: Marking as fixed in unstable
Processing commands for cont...@bugs.debian.org: > fixed 977552 3.7.0-5 Bug #977552 [src:gnutls28] gnutls28: Time bomb in testpkcs11.sh triggered Marked as fixed in versions gnutls28/3.7.0-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 977552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977552 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: hg-git: FTBFS: tests failed
Processing commands for cont...@bugs.debian.org: > found 978361 0.8.12-1 Bug #978361 [src:hg-git] hg-git: FTBFS: tests failed Marked as found in versions hg-git/0.8.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 978361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978361: hg-git: FTBFS: tests failed
found 978361 0.8.12-1 thanks Also happens in buster, the current stable distribution.
Bug#977552: Processed: Re: Bug#977552: fixed in gnutls28 3.7.0-5
Oops, sorry, didn't realize that this is already fixed in stable-new. (I assume this will eventually be closed anyway by ftpmaster when accepting into stable).
Bug#975492: marked as pending in scummvm
Control: tag -1 pending Hello, Bug #975492 in scummvm 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/games-team/scummvm/-/commit/5b455c4a8d589593f35d86cd54642345f8cc68b3 Disable Ultima on platforms where its tests fail Closes: #975492 (this message was generated automatically) -- Greetings https://bugs.debian.org/975492
Processed: Bug#975492 marked as pending in scummvm
Processing control commands: > tag -1 pending Bug #975492 [scummvm] scummvm: FTBFS on big-endian platforms Added tag(s) pending. -- 975492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#977552: fixed in gnutls28 3.7.0-5
Processing commands for cont...@bugs.debian.org:
> found 977552 3.6.7-4+deb10u5
Bug #977552 {Done: Andreas Metzler } [src:gnutls28]
gnutls28: Time bomb in testpkcs11.sh triggered
Marked as found in versions gnutls28/3.6.7-4+deb10u5.
> reopen 977552
Bug #977552 {Done: Andreas Metzler } [src:gnutls28]
gnutls28: Time bomb in testpkcs11.sh triggered
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnutls28/3.7.0-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977552: fixed in gnutls28 3.7.0-5
found 977552 3.6.7-4+deb10u5 reopen 977552 thanks Reopening because the time bomb is still exploding in buster, the currently supported stable distribution. Thanks.
Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome
On Fri, Jan 08, 2021 at 07:30:03PM +0100, Michel Le Bihan wrote:
> After updating libx11-xcb1 chromium and google chrome UI is not
> responding to any input and clicking anywhere on the app window causes
> the GNOME app is not responding dialog to appear. The app actually is
> not frozen because if you pass a URL with dynamic web content as a
> parameter, it will be constantly updated. I didn't notice any other
> affected app, but I didn't test much.
I was experiencing the same. Both Chromium (87.0.4280.88-0.4) and Google
Chrome (87.0.4280.141-1) were entirely unusable for me.
It turned out that for me, the cause was a disparity between libx11-xcb1
and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at
2:1.6.12-1 (don't ask why...). Any of the following are addressing the
issue for me:
* Upgrading libx11-xcb1 + libx11-6 to 2:1.7.0-1 (duh)
* Downgrading libx11-xcb1 (+ libx11-6) to 2:1.6.12-1
* Reverting to an older version of Chromium (83.0.4103.116)
* Google Chrome Beta (88.0.4324.79-1)
Before I realized that the issue was a version disparity, I bisected
libx11, and found that commit dbb55e1 ("Fix poll_for_response race
condition") to be the "bad" commit. Reverting that commit on top of
1.7.0-1, made the issue disappear as well.
At minimum, it looks like libx11-xcb1 and libx11-6 need to be at the
same version, so perhaps libx11-xcb1 should have a versioned depends on
libx11-6 (= ${binary:Version}). On that note, libx11-xcb1 doesn't seem
to even Depend on libc6, with libX11-xcb.so.1 being statically linked;
perhaps that's an issue of its own?
#979443 may or may not be a related bug here.
Faidon
Bug#961932: marked as pending in nethack
Control: tag -1 pending Hello, Bug #961932 in nethack 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/games-team/nethack/-/commit/45befa799333f1e2787ba222c307b8a4222b7684 Drop nethack-lisp which is broken and unmaintained Closes: #961932 (this message was generated automatically) -- Greetings https://bugs.debian.org/961932
Processed: Bug#961932 marked as pending in nethack
Processing control commands: > tag -1 pending Bug #961932 [nethack-lisp] nethack-lisp: broken and unmaintained Added tag(s) pending. -- 961932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979590: libx11-xcb1: Updating to 1.7.0-1 from 1.6.12-1 breaks chromium and google chrome
Hello,
All of your solutions besides downgrading Chromium that I didn't try
work for me.
Michel Le Bihan
Le samedi 09 janvier 2021 à 17:08 +0200, Faidon Liambotis a écrit :
> On Fri, Jan 08, 2021 at 07:30:03PM +0100, Michel Le Bihan wrote:
> > After updating libx11-xcb1 chromium and google chrome UI is not
> > responding to any input and clicking anywhere on the app window
> > causes
> > the GNOME app is not responding dialog to appear. The app actually
> > is
> > not frozen because if you pass a URL with dynamic web content as a
> > parameter, it will be constantly updated. I didn't notice any other
> > affected app, but I didn't test much.
>
> I was experiencing the same. Both Chromium (87.0.4280.88-0.4) and
> Google
> Chrome (87.0.4280.141-1) were entirely unusable for me.
>
> It turned out that for me, the cause was a disparity between libx11-
> xcb1
> and libx11-6 -- the former was at 2:1.7.0-1, while the latter was at
> 2:1.6.12-1 (don't ask why...). Any of the following are addressing
> the
> issue for me:
> * Upgrading libx11-xcb1 + libx11-6 to 2:1.7.0-1 (duh)
> * Downgrading libx11-xcb1 (+ libx11-6) to 2:1.6.12-1
> * Reverting to an older version of Chromium (83.0.4103.116)
> * Google Chrome Beta (88.0.4324.79-1)
>
> Before I realized that the issue was a version disparity, I bisected
> libx11, and found that commit dbb55e1 ("Fix poll_for_response race
> condition") to be the "bad" commit. Reverting that commit on top of
> 1.7.0-1, made the issue disappear as well.
>
> At minimum, it looks like libx11-xcb1 and libx11-6 need to be at the
> same version, so perhaps libx11-xcb1 should have a versioned depends
> on
> libx11-6 (= ${binary:Version}). On that note, libx11-xcb1 doesn't
> seem
> to even Depend on libc6, with libX11-xcb.so.1 being statically
> linked;
> perhaps that's an issue of its own?
>
> #979443 may or may not be a related bug here.
>
> Faidon
Processed: check disabled as workaround
Processing control commands: > severity -1 important Bug #977484 [src:linux] armel/marvell: FTBFS: Uncompressed Image size 7481720/7340032, using 101.93%. Too large. Refusing to continue. Severity set to 'important' from 'serious' > tags -1 help Bug #977484 [src:linux] armel/marvell: FTBFS: Uncompressed Image size 7481720/7340032, using 101.93%. Too large. Refusing to continue. Added tag(s) help. -- 977484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977484: check disabled as workaround
Control: severity -1 important Control: tags -1 help I disabled the check in 5.10.1-1~exp1. There is no way to make the kernel fit again without disabling major parts of it. Downgrading the bug as nothing can be done. Bastian -- Lots of people drink from the wrong bottle sometimes. -- Edith Keeler, "The City on the Edge of Forever", stardate unknown
Bug#979590: Working fine for me
Package: chromium Version: 87.0.4280.88-0.4 Followup-For: Bug #979590 X-Debbugs-Cc: frustra...@karthek.com For me its working fine Im using X not wayland Package: libx11-xcb1 Version: 2:1.7.0-1 Priority: optional Section: libs Source: libx11 Maintainer: Debian X Strike Force Installed-Size: 268 kB Tag: role::shared-lib Download-Size: 203 kB APT-Manual-Installed: no APT-Sources: https://deb.debian.org/debian unstable/main amd64 Packages Description: Xlib/XCB interface library libX11-xcb provides functions needed by clients which take advantage of Xlib/XCB to mix calls to both Xlib and XCB over the same X connection. . More information about X.Org can be found at: https://www.X.org> . More information about XCB can be found at: https://xcb.freedesktop.org> . This module can be found at git://anongit.freedesktop.org/git/xorg/lib/libX11 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 87.0.4280.88-0.4 ii libasound2 1.2.4-1.1 ii libatk-bridge2.0-0 2.38.0-1 ii libatk1.0-0 2.36.0-2 ii libatomic1 10.2.1-5 ii libatspi2.0-02.38.0-2 ii libavcodec58 7:4.3.1-5 ii libavformat587:4.3.1-5 ii libavutil56 7:4.3.1-5 ii libc62.31-9 ii libcairo21.16.0-5 ii libcups2 2.3.3op1-5 ii libdbus-1-3 1.12.20-1 ii libdrm2 2.4.103-2 ii libevent-2.1-7 2.1.12-stable-1 ii libexpat12.2.10-1 ii libflac8 1.3.3-2 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgbm1 20.3.2-1 ii libgcc-s110.2.1-5 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.4-1 ii libgtk-3-0 3.24.24-1 ii libharfbuzz0b2.6.7-1 ii libicu67 67.1-5 ii libjpeg62-turbo 1:2.0.5-2 ii libjsoncpp24 1.9.4-4 ii liblcms2-2 2.9-4+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.29-1 ii libnss3 2:3.60-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3.1-0.1 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpng16-16 1.6.37-3 ii libpulse014.0-2 ii libre2-9 20201101+dfsg-2 ii libsnappy1v5 1.1.8-1 ii libstdc++6 10.2.1-5 ii libwebp6 0.6.1-2+b1 ii libwebpdemux20.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.7.0-1 ii libx11-xcb1 2:1.7.0-1 ii libxcb1 1.14-2.1 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.3-1.1 ii libxfixes3 1:5.0.3-2 ii libxml2 2.9.10+dfsg-6.3+b1 ii libxrandr2 2:1.5.1-1 ii libxslt1.1 1.1.34-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium recommends: ii chromium-sandbox 87.0.4280.88-0.4 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii libc6 2.31-9 ii libstdc++6 10.2.1-5 ii libx11-62:1.7.0-1 ii libxext62:1.3.3-1.1 ii x11-utils 7.7+5 ii xdg-utils 1.1.3-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages chromium-common recommends: ii chromium-sandbox 87.0.4280.88-0.4 ii fonts-liberation 1:1.07.4-11 ii gnome-shell [notification-daemon] 3.38.2-1 ii libgl1-mesa-dri20.3.2-1 ii libu2f-udev1.1.10-1.1 ii notification-daemon3.20.0-4 pn system-config-printer ii upower 0.99.11-2 Versions of packages chromium-sandbox depends on: ii libc6 2.31-9 -- Configuration Files: /etc/chromium.d/default-flags changed [not included] -- no debconf information
Bug#976997: marked as done (haproxy: flaky ppc64el autopkgtest on ci.debian.net: 503 Service Unavailable)
Your message dated Sat, 09 Jan 2021 14:33:47 + with message-id and subject line Bug#976997: fixed in haproxy 2.3.3-1 has caused the Debian Bug report #976997, regarding haproxy: flaky ppc64el autopkgtest on ci.debian.net: 503 Service Unavailable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mpi4py Version: 3.0.3-7 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), The autopkgtest of your package turned up as blocking gcc-10. I looked into the history of your autopkgtest and it fails regularly on ppc64el [1]. I copied the output at the bottom of this report. I noticed that all the failures in testing were the same and all ran on our ci-worker-ppc64el-01. This worker is a bit slower than the rest, so I suspect your test (or code) just fails to wait for the service to come up properly. All the successful runs that I checked were on other workers. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Please do get in touch if we need to dive into this together. Or if you want to discuss this issue. Paul [1] https://ci.debian.net/packages/h/haproxy/testing/ppc64el/ https://ci.debian.net/data/autopkgtest/testing/ppc64el/h/haproxy/8726704/log.gz autopkgtest [18:08:36]: test proxy-localhost: [--- + cat + service haproxy restart + wget -t1 http://localhost:8080+ cmp /var/www/html/index.html - -O- --2020-12-08 18:09:02-- http://localhost:8080/ Resolving localhost (localhost)... ::1, 127.0.0.1 Connecting to localhost (localhost)|::1|:8080... failed: Connection refused. Connecting to localhost (localhost)|127.0.0.1|:8080... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2020-12-08 18:09:05 ERROR 503: Service Unavailable. cmp: EOF on - which is empty + echo FAIL: downloaded index.html via haproxy is different from the + echo file delivered by apache. + exit 1 FAIL: downloaded index.html via haproxy is different from the file delivered by apache. OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: haproxy Source-Version: 2.3.3-1 Done: Vincent Bernat We believe that the bug you reported is fixed in the latest version of haproxy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Bernat (supplier of updated haproxy 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, 09 Jan 2021 15:18:10 +0100 Source: haproxy Architecture: source Version: 2.3.3-1 Distribution: experimental Urgency: medium Maintainer: Debian HAProxy Maintainers Changed-By: Vincent Bernat Closes: 974977 976997 Changes: haproxy (2.3.3-1) experimental; urgency=medium . * d/tests: sleep before test to let Apache2 start. Closes: #976997. * New upstream release: - BUG/MAJOR: ring: tcp forward on ring can break the reader counter. - BUG/MAJOR: spoa/python: Fixing return None - BUG/MEDIUM: local log format regression. Closes: #974977. Checksums-Sha1: 7fae9414f804510cb12f9f7f2a5d240912a2b26b 2308 haproxy_2.3.3-1.dsc 92a26361bdac68655be18471a5a154a9d67feaa1 2910244 haproxy_2.3.3.orig.tar.gz 2fa764985821f43eb6e11138b2da77ead3bfad9c 71412 haproxy_2.3.3-1.debian.tar.xz 1c92f7fded1379f3525a8441726883c8077f1908 8889 haproxy_2.3.3-1_amd64.buildinfo Checksums-Sha256: 34c79ca71c5075ba7ffc39deb805a7beacf9bc8fb5fe01039c73e03b83fc5ff0 2308 haproxy_2.3.3-1.dsc 0671f7197e1218f262641bdfc97639ccdbe0cd7cd67d362fb05f04620cd7d971 2910244 haproxy_2.3.3.orig.tar.gz 45be2835e5530bfdf72bba02bab0ba37d304c573285b2de29a8bb01349c2c396 71412 haproxy_2.3.3-1.debian.tar.xz
