Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup
On Fri, 2021-02-26 at 15:41 +0100, Bernhard Übelacker wrote: > The attached patch is an attempt to grow the buffer size > if the header changes on a new page. > This is just tested for the given crash, nothing more, therefore > there might be side effects on replacing this buffer? It doesn't look unreasonable to me, although the related shuffling of pointers between rgbRaster, kRaster and m_pPrinterBuffer makes my head hurt a bit (this code could really do with a dollop of modern c++ memory management idiom). Do you think there is a need to preserve the current contents (e.g. something approximating realloc rather than delete+new)? Or maybe it is fine to simply unconditionally allocate a new buffer each time round the loop? It could almost be a local variable like *Raster at that point... But I think if you are looking for a minimal fix your patch seems pretty sensible to me (speaking as a competent enough C/C++ programmer but not someone familiar with this codebase before today). Ian.
Bug#983365: Info received (Bug#983365: linphone-desktop: chat messages)
Okay, I do see a difference in behaviour now in sqlitebrowser: with my soci-enabled liblinphone packages installed I see entries being added to table ~/.local/share/linphone/linphone.db:chat_message_content and other tables. The timestamps in chat_message_participant also line up perfectly with the time of installation. I even downgraded again to the current bullseye packages for comparison, and with them installed nothing was added to the database when sending messages. So compiling that in certainly had some effect. And it could actually mean that a new upload of linphone-desktop can be avoided (at least for now). I don't see the message history reappearing in the app though, but that could be because my SIP gateway doesn't relay the messages correctly. I think linphone might only show in its history messages whose reception was acknowledged by the other side. Until then they might be stored in the DB to be delivered once the other side becomes reachable again. What puzzles me a bit is that the submitter saw messages in the DB. But maybe those were from when he (presumably) used the appimage version. I'll try to get asterisk to work and see if I can find out more with that.
Processed: found 983596 in 2.8.104-2
Processing commands for cont...@bugs.debian.org: > found 983596 2.8.104-2 Bug #983596 [gsoap] CVE-2020-13574 CVE-2020-13575 CVE-2020-13576 CVE-2020-13577 CVE-2020-13578 Marked as found in versions gsoap/2.8.104-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 983596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 983596
Processing commands for cont...@bugs.debian.org: > tags 983596 + upstream Bug #983596 [gsoap] CVE-2020-13574 CVE-2020-13575 CVE-2020-13576 CVE-2020-13577 CVE-2020-13578 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 983596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983373: marked as done (gzip-win32: Link gzip.exe with static libssp library)
Your message dated Sat, 27 Feb 2021 05:33:26 + with message-id and subject line Bug#983373: fixed in gzip 1.10-3 has caused the Debian Bug report #983373, regarding gzip-win32: Link gzip.exe with static libssp library 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.) -- 983373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gzip-win32 Version: 1.10-2 Severity: serious Affects: win32-loader Tags: d-i pending Owner: Milan Kupcevic Submitter: Thomas Gaugler Merge request opened 6 months ago by Thomas Gaugler: I noticed that gzip-win32 1.10-2 depends on the libssp-0.dll dynamic link library. Therefore gzip.exe is no longer able to run standalone within win32-loader.exe. wine also exhibits the issue: $ wine gzip.exe 0009:err:module:import_dll Library libssp-0.dll (which is needed by L"Z:\\tmp\\gzip.exe") not found 0009:err:module:attach_dlls Importing dlls for L"Z:\\tmp\\gzip.exe" failed, status c135 The proposed patch links gzip.exe with the static libssp library. From: Thomas Gaugler Date: Wed, 5 Aug 2020 20:32:39 +0200 Subject: [PATCH] Link gzip.exe with static libssp library --- debian/rules | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/rules b/debian/rules index 2861a82..a82aacf 100755 --- a/debian/rules +++ b/debian/rules @@ -76,7 +76,7 @@ configure-indep-stamp: reconf-stamp dh_testdir mkdir -p builddir-indep cd builddir-indep && ../configure --host=i686-w64-mingw32 \ - LIBS="-Wl,--as-needed -lssp" --disable-silent-rules + LIBS="-l:libssp.a" --disable-silent-rules :>$@ build: build-stamp build-indep-stamp -- 2.20.1 --- End Message --- --- Begin Message --- Source: gzip Source-Version: 1.10-3 Done: Milan Kupcevic We believe that the bug you reported is fixed in the latest version of gzip, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Milan Kupcevic (supplier of updated gzip 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, 26 Feb 2021 21:11:52 -0500 Source: gzip Architecture: source Version: 1.10-3 Distribution: sid Urgency: medium Maintainer: Milan Kupcevic Changed-By: Milan Kupcevic Closes: 958425 976304 983373 Changes: gzip (1.10-3) sid; urgency=medium . * Many thanks to Bdale Garbee for a quarter of a century worth of contributions to this package. * new maintainer (closes: #976304) * link static ssp library when building with mingw (closes: #983373) * gzexe: fix count of lines to skip (closes: #958425) Checksums-Sha1: e64d0093f9d2ed9578b65d98409f708e41c4443c 1780 gzip_1.10-3.dsc 3e321e48d12a5ced58dc7f582c4e181aea697432 19052 gzip_1.10-3.debian.tar.xz 6be0e803f29dc2570d5c6fa33059b7d996e0708f 7235 gzip_1.10-3_amd64.buildinfo Checksums-Sha256: 6454a9b545f0e1cd1a51f0a9d0d7c7aa54017bded0749cf02cc8ec4ce974e754 1780 gzip_1.10-3.dsc ff870897d01d7c400aaa6e13f9fc01c0d3a9ffb6c35eb75d3bf9b39523a36659 19052 gzip_1.10-3.debian.tar.xz bac9d3e483850a10c79252e17cb214115cab40d28a6222d06d1901afa1e804c7 7235 gzip_1.10-3_amd64.buildinfo Files: b68a0aa6acda899290be1477473dfb59 1780 utils required gzip_1.10-3.dsc 2752583b8ea8fc784709baa3bae3011a 19052 utils required gzip_1.10-3.debian.tar.xz 484bd393be2ce45a169e81a61985b2a2 7235 utils required gzip_1.10-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHFBAEBCgAvFiEEVkf/m69krCYf+z+G6e1ngbRVCQ4FAmA51aYRHG1pbGFuQGRl Ymlhbi5vcmcACgkQ6e1ngbRVCQ5qRgv/R3rD2PR1rkv7XtwsilaLH7LEvwftr+1p ictu8dBL3+Leutxko0JxTGaGJQQR8MDdn6vngL6xpF9xwSESrHorNzsC0520/41g ae0iOA/t6SA0c+RIrPB7oljfrI2/4QA5R7H5z0qRKD2mrW4LQ6UOzgHwMQjc+yms b3rg1g1+SQyIDuGKXuOXZ7mUcKludADi5+Ym/Qts6OdmTN2Cv+eufFSR/WTyS7wx w5NI7EJ5ypXxjkkwruQDL6n4wKdKX1dMzbrUOvF56Enn2Aum3Dn+84Og06GXqTQX AAc8iAnvdipKu31UnS6NgOmIsgV1QlR4cQ1nRMVz5819aAK+lQdpg3bkZQFF1rJZ 3y70cDcZo5LDcGU179FP4BE8kU8jolX1eCDJyTcMqo6SAWctdnygI0GybNFzL7sW PT7sjwnzhrSZ5JNr711UyZTi1hCMtmF0llCEpZ0K3tyBW5mqmT0ijqXLiiEgQ5jy ELxs1mZvDNS+QxaCyzrI0vuCBVMmZ25y =UkOk -END PGP SIGNATURE---
Bug#983471: rspamd should depend libjs-jquery
On Wed, Feb 24, 2021 at 07:09:20PM (+0100), Jean Charles Delépine wrote: > Versions of packages rspamd depends on: > ii adduser 3.118 > ii ca-certificates 20200601 > ii fonts-glyphicons-halflings 1.009~3.4.1+dfsg-1 > ii init-system-helpers 1.60 > ii libc6 2.31-9 > ii libgcc-s1 10.2.1-6 > ii libglib2.0-02.66.4-1 > ii libhyperscan5 5.4.0-2 > ii libicu6767.1-5 > ii libjs-bootstrap44.5.2+dfsg1-4 > ii libjs-jquery3.5.1+dfsg+~3.5.5-7 > ii libjs-requirejs 2.3.6+ds-1 > ii libluajit-5.1-2 2.1.0~beta3+dfsg-5.3 > ii libpcre2-8-010.36-2 > ii libsodium23 1.0.18-1 > ii libsqlite3-03.34.0-1 > ii libssl1.1 1.1.1i-1 > ii libstdc++6 10.2.1-6 > ii libunwind8 1.3.2-2 > ii lsb-base11.1.0 > ii perl5.30.3-4 > ii zlib1g 1:1.2.11.dfsg-2 Hello Jean Charles, Thank you for this bug report ! Could you please post the full installation log ? As mentioned by your reportbug log, libjs-jquery package is already a dependency of rspamd. - https://packages.debian.org/unstable/rspamd Debian CI seems ok and piupart too - https://ci.debian.net/packages/r/rspamd/testing/amd64/ - https://piuparts.debian.org/sid/source/r/rspamd.html I can't reproduce your issue for the moment, your installation log will help. Thanks in advance ! Sebastien
Processed: severity of 983471 is normal
Processing commands for cont...@bugs.debian.org: > severity 983471 normal Bug #983471 [rspamd] rspamd should depend libjs-jquery Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 983471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#982740: marked as done (pulseaudio: FTBFS on ppc64el)
Your message dated Fri, 26 Feb 2021 23:04:04 +
with message-id
and subject line Bug#982740: fixed in pulseaudio 14.2-2
has caused the Debian Bug report #982740,
regarding pulseaudio: FTBFS on ppc64el
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.)
--
982740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 14.2-1
Severity: serious
Pulseaudio is failing to build on ppc64el. The version of pulseaudio in
bullseye suffers from a pretty serious usability bug (see #980836)
which should arguably be a higher severity, but let's focus on getting
14.2-1 built properly.
https://buildd.debian.org/status/logs.php?pkg=pulseaudio&arch=ppc64el
Here's where the ppc64el build fails:
FAIL: cpu-volume-test
=
Running suite(s): CPU
0%: Checks: 1, Failures: 1, Errors: 0
tests/cpu-volume-test.c:81:F:svolume:svolume_orc_test:0: Failed
FAIL cpu-volume-test (exit status: 1)
It's worth noting that 14.1-1 built just fine on ppc64el, and the only
non-debian change between 14.1 and 14.2 is this:
dilinger@e7470:/home/dev/pulseaudio$ git diff v14.1..v14.2
diff --git a/NEWS b/NEWS
index 308eedb17..72dd76fda 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,14 @@
+PulseAudio 14.2
+
+A bug fix release.
+
+ * Fix port switching when unplugging headphones
+
+Contributors
+
+ Tanu Kaskinen
+
+
PulseAudio 14.1
A bug fix release.
diff --git a/src/modules/module-switch-on-port-available.c
b/src/modules/module-switch-on-port-available.c
index f450004ca..99d61a4b8 100644
--- a/src/modules/module-switch-on-port-available.c
+++ b/src/modules/module-switch-on-port-available.c
@@ -278,8 +278,10 @@ static void switch_from_port(pa_device_port *port, struct
port_pointers pp) {
* profile is still available in the
* PA_CORE_HOOK_CARD_PROFILE_AVAILABLE_CHANGED callback, as at this point
* the profile availability hasn't been updated yet. */
-if (best_port)
-switch_to_port(best_port, pp);
+if (best_port) {
+struct port_pointers best_pp = find_port_pointers(best_port);
+switch_to_port(best_port, best_pp);
+}
}
It doesn't appear to be a temporary thing, as there were multiple
build attempts that all fail in the same spot.
It's likely something that changed in the build environment. For
example, there were some major changes with the check package
between the version that PA 14.1-1 built with (check 0.12.0-0.2)
and the version that PA 14.2-1 built with (check 0.15.2-2). And in
particular, #961781 looks very suspect as a difference in
precision between ppc64el and other architectures, but we also don't
appear to be using long doubles in that specific liborc test. So
¯\_(ツ)_/¯
The version of liborc didn't change between the two builds. There
was only 5 days between the successful and failed builds, so it's
pretty easy to see which packages changed. The check package
seems the most suspect, so it might be worth someone getting on a
ppc64el porter box and trying to build PA 14.2-1 with the older
version of the check package.
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 14.2-2
Done: Felipe Sateler
We believe that the bug you reported is fixed in the latest version of
pulseaudio, 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 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Felipe Sateler (supplier of updated pulseaudio 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, 26 Feb 2021 19:51:50 -0300
Source: pulseaudio
Architecture: source
Version: 14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Pulseaudio maintenance team
Changed-By: Felipe Sateler
Closes: 854327 982740
Changes:
pulseaudio (14.2-2) unstable; urgency=medium
.
* Stop installing the console kit module.
ConsoleKit was removed from debian, so it no longer brings any purpose
(Closes: #854327)
* Fix test failure in ppc64el.
Thanks to Faidon Liambotis for the patch.
(Closes: #982740)
* Move the home directory of pulseaudio user to /run/p
Bug#982740: marked as pending in pulseaudio
Control: tag -1 pending Hello, Bug #982740 in pulseaudio 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/pulseaudio-team/pulseaudio/-/commit/d11d6825e023e818fde8bf1f664fdb98eec7f601 Fix test failure in ppc64el Thanks to Faidon Liambotis for the patch. Closes: #982740 (this message was generated automatically) -- Greetings https://bugs.debian.org/982740
Processed: Bug#982740 marked as pending in pulseaudio
Processing control commands: > tag -1 pending Bug #982740 [pulseaudio] pulseaudio: FTBFS on ppc64el Ignoring request to alter tags of bug #982740 to the same tags previously set -- 982740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to pulseaudio, tagging 982740, tagging 854327
Processing commands for cont...@bugs.debian.org: > limit source pulseaudio Limiting to bugs with field 'source' containing at least one of 'pulseaudio' Limit currently set to 'source':'pulseaudio' > tags 982740 + pending Bug #982740 [pulseaudio] pulseaudio: FTBFS on ppc64el Added tag(s) pending. > tags 854327 + pending Bug #854327 [pulseaudio] pulseaudio: default configuration depends on consolekit Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 854327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854327 982740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982740 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: commands
Processing commands for cont...@bugs.debian.org: > tag 974828 + patch Bug #974828 [printer-driver-hpcups] printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 974828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983596: CVE-2020-13574 CVE-2020-13575 CVE-2020-13576 CVE-2020-13577 CVE-2020-13578
Package: gsoap Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team CVE-2020-13574 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1185 CVE-2020-13575 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1186 CVE-2020-13576 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1187 CVE-2020-13577 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1188 CVE-2020-13578 https://talosintelligence.com/vulnerability_reports/TALOS-2020-1189 Cheers, Moritz
Processed: severity of 964796 is grave
Processing commands for cont...@bugs.debian.org: > severity 964796 grave Bug #964796 [src:bsdiff] bsdiff: CVE-2020-14315 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 964796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980641: marked as done (nml: FTBFS: dh_auto_test: error: make -j4 test _V= returned exit code 2)
Your message dated Fri, 26 Feb 2021 20:48:43 + with message-id and subject line Bug#980641: fixed in nml 0.5.3-2 has caused the Debian Bug report #980641, regarding nml: FTBFS: dh_auto_test: error: make -j4 test _V= returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nml Version: 0.5.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/regression' > echo "Running test 001_action8" > echo "Running test 002_sounds" > echo "Running test 003_assignment" > Running test 001_action8 > mkdir -p output nml_output output2 > Running test 002_sounds > echo "Running test 004_deactivate" > Running test 003_assignment > mkdir -p output nml_output output2 > mkdir -p output nml_output output2 > Running test 004_deactivate > mkdir -p output nml_output output2 > /<>/nmlc -s -c --verbosity=1 --nfo output/001_action8.nfo --grf > output/001_action8.grf 001_action8.nml --nml nml_output/001_action8.nml > /<>/nmlc -s -c --verbosity=1 --nfo output/002_sounds.nfo --grf > output/002_sounds.grf 002_sounds.nml --nml nml_output/002_sounds.nml > /<>/nmlc -s -c --verbosity=1 --nfo output/003_assignment.nfo > --grf output/003_assignment.grf 003_assignment.nml --nml > nml_output/003_assignment.nml > /<>/nmlc -s -c --verbosity=1 --nfo output/004_deactivate.nfo > --grf output/004_deactivate.grf 004_deactivate.nml --nml > nml_output/004_deactivate.nml > diff -u --strip-trailing-cr expected/004_deactivate.nfo > output/004_deactivate.nfo > diff -u --strip-trailing-cr expected/003_assignment.nfo > output/003_assignment.nfo > diff -u --strip-trailing-cr expected/001_action8.nfo output/001_action8.nfo > diff -u --strip-trailing-cr expected/002_sounds.nfo output/002_sounds.nfo > diff expected/004_deactivate.grf output/004_deactivate.grf > diff expected/003_assignment.grf output/003_assignment.grf > diff expected/001_action8.grf output/001_action8.grf > diff expected/002_sounds.grf output/002_sounds.grf > /<>/nmlc -s -c --verbosity=1 -n --nfo output2/004_deactivate.nfo > --grf output2/004_deactivate.grf nml_output/004_deactivate.nml > /<>/nmlc -s -c --verbosity=1 -n --nfo output2/003_assignment.nfo > --grf output2/003_assignment.grf nml_output/003_assignment.nml > /<>/nmlc -s -c --verbosity=1 -n --nfo output2/001_action8.nfo > --grf output2/001_action8.grf nml_output/001_action8.nml > /<>/nmlc -s -c --verbosity=1 -n --nfo output2/002_sounds.nfo > --grf output2/002_sounds.grf nml_output/002_sounds.nml > diff -u --strip-trailing-cr expected/004_deactivate.nfo > output2/004_deactivate.nfo > diff expected/004_deactivate.grf output2/004_deactivate.grf > diff -u --strip-trailing-cr expected/001_action8.nfo output2/001_action8.nfo > diff -u --strip-trailing-cr expected/002_sounds.nfo output2/002_sounds.nfo > diff -u --strip-trailing-cr expected/003_assignment.nfo > output2/003_assignment.nfo > echo "Running test 005_error" > diff expected/001_action8.grf output2/001_action8.grf > diff expected/002_sounds.grf output2/002_sounds.grf > Running test 005_error > diff expected/003_assignment.grf output2/003_assignment.grf > mkdir -p output nml_output output2 > echo "Running test 006_vehicle" > echo "Running test 007_townnames" > echo "Running test 008_railtypes" > Running test 006_vehicle > /<>/nmlc -s -c --verbosity=1 --nfo output/005_error.nfo --grf > output/005_error.grf 005_error.nml --nml nml_output/005_error.nml > Running test 007_townnames > mkdir -p output nml_output output2 > Running test 008_railtypes > mkdir -p output nml_output output2 > mkdir -p output nml_output output2 > /<>/nmlc -s -c --verbosity=1 --nfo output/006_vehicle.nfo --grf > output/006_vehicle.grf 006_vehicle.nml --nml nml_output/006_vehicle.nml > /<>/nmlc -s -c --verbosity=1 --nfo output/007_townnames.nfo > --grf output/007_townnames.grf 007_townnames.nml --nml > nml_output/007_townnames.nml > /<>/nmlc -s -c --verbosity=1 --nfo output/008_railtypes.nfo > --grf output/008_railtypes.grf 008_railtypes.nml --nml > nml_output/008_railtypes.nml > diff -u --strip-trailing-cr expected/008_railtypes.nfo > output/008_railtypes.nfo > diff -u --strip-trailing-cr expected/005_error.nfo output/005_error.nfo > diff -u --strip-trailing-cr expected/007_townnames.nfo > output/007_townnames.nfo > diff expected/00
Bug#983590: freecad: autopkgtest regression
Source: freecad Version: 0.19+dfsg1-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/f/freecad/10706923/log.gz ... ** run FEM TestObjectOpen tests load old document objects #0 /lib/x86_64-linux-gnu/libc.so.6(+0x3bd60) [0x7fa5d2e14d60] #1 0x7fa5c321a0c2 in Fem::Constraint::getDirection(App::PropertyLinkSub const&) from /usr/lib/freecad-python3/lib/Fem.so+0x42 #2 0x7fa5c3223973 in Fem::ConstraintFluidBoundary::onChanged(App::Property const*) from /usr/lib/freecad-python3/lib/Fem.so+0x223 #3 0x7fa5d3c0c965 in App::Property::hasSetValue() from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x75 #4 0x7fa5d3c3eca8 in App::PropertyLinkSub::Restore(Base::XMLReader&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x688 #5 0x7fa5d3c0f45e in App::PropertyContainer::Restore(Base::XMLReader&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0xeee #6 0x7fa5d3ad9718 in App::Document::readObjects(Base::XMLReader&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x718 #7 0x7fa5d3ae698e in App::Document::Restore(Base::XMLReader&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x21e #8 0x7fa5d3ae8563 in App::Document::restore(char const*, bool, std::set, std::allocator >, std::less, std::allocator > >, std::allocator, std::allocator > > > const&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x383 #9 0x7fa5d3c9482b in App::Application::openDocumentPrivate(char const*, char const*, char const*, bool, bool, std::set, std::allocator >, std::less, std::allocator > >, std::allocator, std::allocator > > > const&) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x6fb #10 0x7fa5d3c9537e in App::Application::openDocuments(std::vector, std::allocator >, std::allocator, std::allocator > > > const&, std::vector, std::allocator >, std::allocator, std::allocator > > > const*, std::vector, std::allocator >, std::allocator, std::allocator > > > const*, std::vector, std::allocator >, std::allocator, std::allocator > > >*, bool) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x65e #11 0x7fa5d3c964ef in App::Application::openDocument(char const*, bool) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0x11f #12 0x7fa5d3ca94c3 in App::Application::sOpenDocument(_object*, _object*, _object*) from /usr/lib/freecad-python3/lib/libFreeCADApp.so+0xe3 #13 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x10cc93) [0x7fa5d3291c93] #14 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x90) [0x7fa5d324ba50] #15 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x8632) [0x7fa5d31fd2f2] #16 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x6f033) [0x7fa5d31f4033] #17 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0xc9728) [0x7fa5d324e728] #18 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x6456) [0x7fa5d31fb116] #19 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x6f033) [0x7fa5d31f4033] #20 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x77f7) [0x7fa5d31fc4b7] #21 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1a4ddc) [0x7fa5d3329ddc] #22 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyFunction_Vectorcall+0x9d) [0x7fa5d3246c7d] #23 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0xc96a4) [0x7fa5d324e6a4] #24 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x4a59) [0x7fa5d31f9719] #25 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1a4ddc) [0x7fa5d3329ddc] #26 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyFunction_Vectorcall+0x9d) [0x7fa5d3246c7d] #27 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_FastCallDictTstate+0x53) [0x7fa5d324df23] #28 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_Call_Prepend+0xe0) [0x7fa5d324e140] #29 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x12f609) [0x7fa5d32b4609] #30 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_MakeTpCall+0x90) [0x7fa5d324ba50] #31 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x7248) [0x7fa5d31fbf08] #32 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1a4ddc) [0x7fa5d3329ddc] #33 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyFunction_Vectorcall+0x9d) [0x7fa5d3246c7d] #34 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0xc96a4) [0x7fa5d324e6a4] #35 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyEval_EvalFrameDefault+0x4a59) [0x7fa5d31f9719] #36 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1a4ddc) [0x7fa5d3329ddc] #37 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyFunction_Vectorcall+0x9d) [0x7fa5d3246c7d] #38 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_FastCallDictTstate+0x53) [0x7fa5d324df23] #39 /lib/x86_64-linux-gnu/libpython3.9.so.1.0(_PyObject_Call_Prepend+0xe0) [0x7fa5d324e140] #40 /lib/x86_64-linux-gnu/
Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup
Dear Maintainer,
with the original PPD and input files from Ian I could
reproduce the issue and with the help of rr-debugger
this is what I assume what happens:
- The buffer m_pPrinterBuffer is allocated here with
the current sizes inside cups_header. [1]
- The first page got processed and for the second page
a new cups_header record gets copied. [2]
Unfortunately now the header contains higher sizes,
but the buffer is not grown accordingly.
- Now to this buffer is written by a read function, and beyond
where the management information of malloc got overwritten for
some other random memory. [3]
- The defect in the management information of malloc is detected
and the process is aborted. [4]
The attached patch is an attempt to grow the buffer size
if the header changes on a new page.
This is just tested for the given crash, nothing more, therefore
there might be side effects on replacing this buffer?
Kind regards,
Bernhard
[1]
500 m_pPrinterBuffer = new BYTE[cups_header->cupsWidth * 4 + 32];
(rr) bt
#0 HPCupsFilter::startPage (this=0x556369c551c0 ,
cups_header=0x7ffe94b8e030) at prnt/hpcups/HPCupsFilter.cpp:500
#1 0x556369bf4793 in HPCupsFilter::processRasterData
(this=this@entry=0x556369c551c0 , cups_raster=,
cups_raster@entry=0x55636ac39d00) at prnt/hpcups/HPCupsFilter.cpp:668
#2 0x556369bf4de9 in HPCupsFilter::StartPrintJob (this=0x556369c551c0
, argc=, argv=0x7ffe94b8ecf8) at
prnt/hpcups/HPCupsFilter.cpp:597
...
(rr) when
Current event: 898
[2]
#0 0x7f504dcaa190 in memcpy (__len=1796, __src=0x564615c8cd1c,
__dest=0x7ffc2a13f080) at
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:34
#1 cupsRasterReadHeader2 (r=0x564615c8cd00, h=h@entry=0x7ffc2a13f080) at
raster-stubs.c:209
#2 0x5646141d356d in HPCupsFilter::processRasterData
(this=this@entry=0x5646142341c0 , cups_raster=,
cups_raster@entry=0x564615c8cd00) at prnt/hpcups/HPCupsFilter.cpp:661
#3 0x5646141d3de9 in HPCupsFilter::StartPrintJob (this=0x5646142341c0
, argc=, argv=0x7ffc2a13fd48) at
prnt/hpcups/HPCupsFilter.cpp:597
#4 0x7f504d83fd0a in __libc_start_main (main=0x5646141d0e10 , argc=6,
argv=0x7ffc2a13fd48, init=, fini=, rtld_fini=, stack_end=0x7ffc2a13fd38) at ../csu/libc-start.c:308
#5 0x5646141d0efa in _start ()
(rr) when
Current event: 1230
[3]
...
#9 0x7f504dcaa00d in read (__nbytes=19220, __buf=0x564615cb1ca0,
__fd=0) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#10 cups_read_fd (ctx=, buf=0x564615cb1ca0 '\377' ..., bytes=19220) at raster-stubs.c:323
#11 0x7f504dca9340 in cups_raster_io (bytes=19220, buf=0x564615cb1ca0 '\377'
..., r=0x564615c8cd00) at raster-stream.c:1372
#12 _cupsRasterReadPixels (r=0x564615c8cd00, p=0x564615cb1ca0 '\377' ..., len=19220) at raster-stream.c:782
#13 0x7f504dcaa1e5 in cupsRasterReadPixels (r=, p=, len=) at raster-stubs.c:228
#14 0x5646141d36e8 in HPCupsFilter::processRasterData
(this=this@entry=0x5646142341c0 , cups_raster=,
cups_raster@entry=0x564615c8cd00) at prnt/hpcups/HPCupsFilter.cpp:758
#15 0x5646141d3de9 in HPCupsFilter::StartPrintJob (this=0x5646142341c0
, argc=, argv=0x7ffc2a13fd48) at
prnt/hpcups/HPCupsFilter.cpp:597
...
[4]
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x7f504d83e537 in __GI_abort () at abort.c:79
#2 0x7f504d897768 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f504d9a5e31 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x7f504d89ea5a in malloc_printerr (str=str@entry=0x7f504d9a8258 "free():
invalid next size (normal)") at malloc.c:5347
#4 0x7f504d89ff2c in _int_free (av=0x7f504d9d7b80 ,
p=0x564615cb1c90, have_lock=) at malloc.c:4322
#5 0x5646141d15c6 in HPCupsFilter::cleanup (this=this@entry=0x5646142341c0
) at prnt/hpcups/HPCupsFilter.cpp:227
#6 0x5646141d3e1b in HPCupsFilter::closeFilter (this=0x5646142341c0
) at prnt/hpcups/HPCupsFilter.cpp:221
#7 HPCupsFilter::StartPrintJob (this=0x5646142341c0 , argc=, argv=0x7ffc2a13fd48) at prnt/hpcups/HPCupsFilter.cpp:617
...
Description: Grow m_pPrinterBuffer if needed on each page
Author: Bernhard Übelacker
Bug-Debian: https://bugs.debian.org/974828
Bug-Ubuntu: https://launchpad.net/bugs/1904318
Last-Update: 2021-02-26
Index: hplip-3.20.11+dfsg0/prnt/hpcups/HPCupsFilter.cpp
===
--- hplip-3.20.11+dfsg0.orig/prnt/hpcups/HPCupsFilter.cpp
+++ hplip-3.20.11+dfsg0/prnt/hpcups/HPCupsFilter.cpp
@@ -199,7 +199,7 @@ void HPCupsFilter::WriteKBMPRaster (FILE
fwrite (black_raster, 1, adj_k_width, fp);
}
-HPCupsFilter::HPCupsFilter() : m_pPrinterBuffer(NULL)
+HPCupsFilter::HPCupsFilter() : m_pPrinterBuffer(NULL), m_PrinterBufferSize(0)
{
setbuf (stderr, NULL);
@@ -226,6 +226,7 @@ void HPCupsFilter::cleanup()
if (m_pPrinterBuff
Bug#983583: FTBFS on mips64el and mipsel
Source: golang-github-sylabs-sif Version: 1.0.9-2 Severity: serious X-Debbugs-Cc: z...@debian.org Tried 3 times on buildd and failed at same test. === RUN TestAddDelObject unexpected fault address 0xffc8a0c000 fatal error: fault [signal SIGSEGV: segmentation violation code=0x2 addr=0xffc8a0c000 pc=0x12007ebe4] goroutine 22 [running]: runtime.throw(0x1201b74ed, 0x5) /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c fp=0xce3430 sp=0xce3408 pc=0x120040afc runtime.sigpanic() Since it has been built on mipsx before, the failure will cause it impossible to fix issue later on these arch. It should either be removed from these arch or get fixed.
Bug#983365: linphone-desktop: chat messages
Hi, > Have you reached out to the SOCI maintainer in private already? I don't > see a bug report on this. If we can get a targeted fix uploaded for this > within the next days (next step of the freeze is on March 10th, with a > migration time of 10 days right now) I will attempt to push through a > new src:linphone upload. Do you know whether we need a new > src:linphone-desktop upload as well? I'm the SOCI maintainer. Dennis did email me and explain the situation, and I don't see an issue making the change. I'll prepare the upload today. If someone would please file a bug against SOCI regarding this, I would appreciate it. Best regards, Bill -- GPG: 5CDD 0C9C F446 BC1B 2509 8791 1762 E022 7034 CF84
Bug#971713: marked as done (sysstat: init or systemd file has overlapping runlevels)
Your message dated Fri, 26 Feb 2021 18:03:45 +
with message-id
and subject line Bug#971713: fixed in insserv 1.21.0-1.1
has caused the Debian Bug report #971713,
regarding sysstat: init or systemd file has overlapping runlevels
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.)
--
971713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sysstat
Version: 12.4.0-1
Severity: normal
When installing any package that has an init.d file, I get the
following warning message about sysstat:
insserv: Script sysstat has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Best wishes,
Julian
--- End Message ---
--- Begin Message ---
Source: insserv
Source-Version: 1.21.0-1.1
Done: Matthew Vernon
We believe that the bug you reported is fixed in the latest version of
insserv, 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.
Matthew Vernon (supplier of updated insserv 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, 21 Feb 2021 17:13:07 +
Source: insserv
Binary: insserv
Architecture: source
Version: 1.21.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian sysvinit maintainers
Changed-By: Matthew Vernon
Description:
insserv- boot sequence organizer using LSB init.d script dependency inform
Closes: 971713
Changes:
insserv (1.21.0-1.1) unstable; urgency=medium
.
* Non-maintainer upload
* Apply patches from Trek to only check LSB headers for overlapping
run-levels and document Default-{Start,Stop} more clearly
(Closes: #971713)
Checksums-Sha1:
091c7b08a01ff966a87d6a618c165dc82d9e32b1 2439 insserv_1.21.0-1.1.dsc
94245580c9eba691628059c8b4c475387be1779b 47632 insserv_1.21.0-1.1.debian.tar.xz
Checksums-Sha256:
4d846a96586d8c263f6409569fa935605bf6534ac9c8dda1088b8c39cc0d1283 2439
insserv_1.21.0-1.1.dsc
0480446f3b408d8294ca16ec3af28ebaf0c84108161df93845ef899288acb875 47632
insserv_1.21.0-1.1.debian.tar.xz
Files:
a4850e5c363b9f06f41244076d130e99 2439 misc optional insserv_1.21.0-1.1.dsc
08dc6771f5e4579ac7cdb515012a25ca 47632 misc optional
insserv_1.21.0-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJHBAEBCgAxFiEEuk75yE35bTfYoeLUEvTSHI9qY8gFAmAylaITHG1hdHRoZXdA
ZGViaWFuLm9yZwAKCRAS9NIcj2pjyPiID/9HC2l14RybU1FiaBtlbyHZ9UPnlEij
+zZvDR8FI8UxTD1+TX+vyiIXFfOullefV2ndQQA/th9utvkBBY4QFmfTJd6eBo5E
P0BLXnjHMYcm1QOY2x0U8jvuxWa/ji04DtISDQMMrnQtomGPJRiD1FsRJyTx5d3B
wZpd3uRMqSmVp31ls/A/Gkdx4HCZ9I7dxvA2gwI9Mte39Z5w74RJEzQYK9U6WUwp
8UYClNYvepgZNbJYo2OqiWO0euOu9h64YrsGcKBUuIILes+ZfcxagWptBIuMLu88
aKZjp0UxLUkHURpeWOvFPQB4xdRxMGz2bZMovfKyYrHdfS36ldi2KFj6ASPex/9U
utdZqQXhmtU7hAcvWqOw0E2alsMk/UE6AmR1jPbvhYsRBHa8HJZ40g6rGv6yBz4U
L7uAuXYwIcDWqvHYg62YgC80pmTrtj97bXu6LA2CRTeKUeoc+g85ACKhl04y3fOm
lmCXAX3InQvnsDYMz1V8XjIeRRMXyp7kqDGBx6G92v9WT3oSfkZ7b2wi04GruAfS
pAE+SgNH1KURuApGawiDSatwKd/EJ/E9ID6h5g5E0UwVE0de3imDvbCCiGA+OEZs
ovaHhqNoft1SB/G2YlDKJEDShBWtgS6s1VhCjS4xVmuE0D0dDWBA5zOBgytzT2sk
h3wjdEEmcvuAaA==
=0sKj
-END PGP SIGNATURE End Message ---
Bug#983577: FTBFS: src/github.com/future-architect/vuls/oval/util.go:239:43: not enough arguments in call to driver.GetByPackName
Package: vuls Version: 0.6.1-2 Severity: serious X-Debbugs-Cc: z...@debian.org Recently goval-dictionary was upgraded 0.2.0-4, causes this package FTBFS. https://buildd.debian.org/status/fetch.php?pkg=vuls&arch=amd64&ver=0.6.1-2%2Bb2&stamp=1614218113&raw=0 # github.com/future-architect/vuls/oval src/github.com/future-architect/vuls/oval/util.go:239:43: not enough arguments in call to driver.GetByPackName have (string, string) want (string, string, string, string)
Bug#983365: linphone-desktop: chat messages
On Fri, Feb 26, 2021 at 10:23:04AM +0100, Bernhard Schmidt wrote: > Have you confirmed already that the whole soci/linphone dance really > fixes this issue? No. I installed my liblinphone* packages with soci support and I don't see a difference in behaviour yet. I must state though that I haven't been able to get chat to work at all yet, so it might mean nothing. I may have to set up an asterisk server. > Do you know whether we need a new src:linphone-desktop upload as > well? After installing the liblinphone* packages libsoc_core showed up in the output of "ldd /usr/bin/linphone" and it started without crashing. I don't know if any subtle template magic could cause problems. I keep stumbling into segfaults both in Qt and liblinphone and I can never tell if they are due to something I changed or just lingering bugs. I'll keep looking into this throughout the weekend and will post any new findings. Regards, Dennis.
Bug#983511: marked as done (cdebootstrap: autopkgtest needs update for new version of debian-archive-keyring:)
Your message dated Fri, 26 Feb 2021 16:18:28 + with message-id and subject line Bug#983511: fixed in cdebootstrap 0.7.8 has caused the Debian Bug report #983511, regarding cdebootstrap: autopkgtest needs update for new version of debian-archive-keyring: 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.) -- 983511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cdebootstrap Version: 0.7.7 Severity: serious Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:debian-archive-keyring [X-Debbugs-CC: debian...@lists.debian.org, debian-archive-keyr...@packages.debian.org] Dear maintainer(s), With a recent upload of debian-archive-keyring the autopkgtest of cdebootstrap fails in testing when that autopkgtest is run with the binary packages of debian-archive-keyring from unstable. It passes when run with only packages from testing. In tabular form: passfail debian-archive-keyring from testing2021.1 cdebootstrap from testing0.7.7 all others from testingfrom testing I copied some of the output at the bottom of this report. The signing key for jessie has been removed. Currently this regression is blocking the migration of debian-archive-keyring to testing [1]. Of course, debian-archive-keyring shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in debian-archive-keyring was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from debian-archive-keyring should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=debian-archive-keyring https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdebootstrap/10673330/log.gz autopkgtest [03:12:13]: test jessie-standard: [--- D: Read suites config from /usr/share/cdebootstrap D: Searching initial config, using origin Debian and codename jessie D: Found initial config, specifies keyring debian-archive-keyring.gpg, mirror http://deb.debian.org/debian D: Using mirror http://deb.debian.org/debian D: Using keyring /usr/share/keyrings/debian-archive-keyring.gpg P: Retrieving Release D: Downloading http://deb.debian.org/debian/dists/jessie/Release P: Retrieving Release.gpg D: Downloading http://deb.debian.org/debian/dists/jessie/Release.gpg P: Validating Release D: Execute "gpgv …" D: GNUPG Status: [GNUPG:] NEWSIG gpgv: Signature made Sat Jul 6 09:36:55 2019 UTC gpgv:using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010 D: GNUPG Status: [GNUPG:] ERRSIG 7638D0442B90D010 1 8 00 1562405815 9 126C0D24BD8A2942CC7DF8AC7638D0442B90D010 D: GNUPG Status: [GNUPG:] NO_PUBKEY 7638D0442B90D010 gpgv: Can't check signature: No public key D: GNUPG Status: [GNUPG:] NEWSIG gpgv: Signature made Sat Jul 6 09:43:49 2019 UTC gpgv:using RSA key CBF8D6FD518E17E1 D: GNUPG Status: [GNUPG:] ERRSIG CBF8D6FD518E17E1 1 2 00 1562406229 9 - D: GNUPG Status: [GNUPG:] NO_PUBKEY CBF8D6FD518E17E1 gpgv: Can't check signature: No public key D: Status: 512 E: Couldn't validate Release! autopkgtest [03:12:13]: test jessie-standard: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: cdebootstrap Source-Version: 0.7.8 Done: Bastian Blank We believe that the bug you reported is fixed in the latest version of cdebootstrap, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank (supplier of updated cdebootstrap 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.
Bug#887649: cdebconf-gtk-terminal: Please don't depend on unmaintained vte
On Thu, 03 Sep 2020 at 11:46:56 +0200, Cyril Brulebois wrote: > Simon McVittie (2020-09-03): > > One way to resolve [needing a libstdc++ udeb] > > might be to build the vte2.91 udeb with > > -static-libstdc++, which makes it about 200K larger than it would > > otherwise have been, but avoids needing a 1.5M shared libstdc++. vte > > exports a C ABI, and only uses C++ internally. > > This looks like a nice plan, thanks for the heads-up! This happened a while ago. However, since we're already in soft freeze, a GTK 3 port of the graphical installer interface is clearly not something to start on right now - so I think this has to slip to Debian 12. Release team: I think #887649 is going to need to be bullseye-ignore. smcv
Bug#983365: linphone-desktop: chat messages
Am 26.02.21 um 15:19 schrieb Bill Blough: Hi Bill, > Hi, > >> Have you reached out to the SOCI maintainer in private already? I don't >> see a bug report on this. If we can get a targeted fix uploaded for this >> within the next days (next step of the freeze is on March 10th, with a >> migration time of 10 days right now) I will attempt to push through a >> new src:linphone upload. Do you know whether we need a new >> src:linphone-desktop upload as well? > > I'm the SOCI maintainer. Dennis did email me and explain the > situation, and I don't see an issue making the change. > > I'll prepare the upload today. If someone would please file a bug > against SOCI regarding this, I would appreciate it. Thanks, I've opened Bug#983572 for this. Bernhard
Processed: block 983365 with 983573
Processing commands for cont...@bugs.debian.org: > block 983365 with 983573 Bug #983365 [linphone-desktop] linphone-desktop: chat messages 983365 was not blocked by any bugs. 983365 was not blocking any bugs. Added blocking bug(s) of 983365: 983573 > thanks Stopping processing here. Please contact me if you need assistance. -- 983365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983533: Fix for #983533, fix session startup of RDP session in vinagre's RDP plugin
Control: tags -1 patch
I have done more tests with vinagre. I have attached a .debdiff that
fixes Vinagre's connection initialization and gives me a working RDP
session.
Upstream authors of FreeRDP mentioned that Vinagre's way of using the
FreeRDP API is rather old and it should be reworked by Vinagre
upstream maintainers.
However, session startup now works, but maybe more flaws are ahead.
See attached .debdiff for the proposed fix (and ignore the patch that
was attached to my earlier post).
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
diff -Nru vinagre-3.22.0/debian/changelog vinagre-3.22.0/debian/changelog
--- vinagre-3.22.0/debian/changelog 2021-01-01 01:09:52.0 +0100
+++ vinagre-3.22.0/debian/changelog 2021-02-25 19:48:08.0 +0100
@@ -1,3 +1,11 @@
+vinagre (3.22.0-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches:
++ Add 0003-fix-hangs-with-recent-FreeRDP-version.patch. (Closes: -1).
+
+ -- Mike Gabriel Thu, 25 Feb 2021 19:48:08 +0100
+
vinagre (3.22.0-8) unstable; urgency=medium
* Team upload.
diff -Nru
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch
---
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch
1970-01-01 01:00:00.0 +0100
+++
vinagre-3.22.0/debian/patches/0003-fix-hangs-with-recent-FreeRDP-version.patch
2021-02-25 19:48:08.0 +0100
@@ -0,0 +1,78 @@
+From 404a56a11469ef24a1df632847465030d81db091 Mon Sep 17 00:00:00 2001
+From: Ondrej Holy
+Date: Fri, 15 May 2020 15:43:37 +0200
+Subject: [PATCH] plugins/rdp: Fix hangs with recent FreeRDP versions
+
+Connection to all my testing servers fails with "SERVER BUG: The support
+for this feature was not announced! Use /relax-order-checks to ignore"
+currently. This happens always with current FreeRDP versions after
+https://github.com/FreeRDP/FreeRDP/pull/4926 has been merged. This can be
+fixed by the usage of /relax-order-checks option, however, this option
+should be used only if necessary needed and it should not be needed in
+most of the cases. This currenlty happens always as it interfere with our
+custom OrderSupports settings. Let's use the default OrderSupports
+settings to fix this issue, which is possible thanks to
+https://github.com/FreeRDP/FreeRDP/pull/5057.
+
+See: https://gitlab.gnome.org/GNOME/gtk-frdp/-/issues/27
+---
+ configure.ac | 2 +-
+ plugins/rdp/vinagre-rdp-tab.c | 27 ---
+ 2 files changed, 1 insertion(+), 28 deletions(-)
+
+--- a/configure.ac
b/configure.ac
+@@ -58,7 +58,7 @@
+ AM_CONDITIONAL([VINAGRE_ENABLE_SSH], [test "x$have_ssh" = "xyes"])
+
+ # Whether to enable support for RDP.
+-RDP_DEPS="freerdp2 x11"
++RDP_DEPS="freerdp2 >= 2.0.0 x11"
+ AC_ARG_ENABLE([rdp],
+ [AS_HELP_STRING([--disable-rdp],
+ [Disable Remote Desktop Protocol (RDP) support])])
+--- a/plugins/rdp/vinagre-rdp-tab.c
b/plugins/rdp/vinagre-rdp-tab.c
+@@ -524,32 +524,7 @@ frdp_pre_connect (freerdp *instance)
+ {
+ rdpSettings *settings = instance->settings;
+
+-#if HAVE_FREERDP_1_1
+- settings->OrderSupport[NEG_DSTBLT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_PATBLT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_SCRBLT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_OPAQUE_RECT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_DRAWNINEGRID_INDEX] = FALSE;
+- settings->OrderSupport[NEG_MULTIDSTBLT_INDEX] = FALSE;
+- settings->OrderSupport[NEG_MULTIPATBLT_INDEX] = FALSE;
+- settings->OrderSupport[NEG_MULTISCRBLT_INDEX] = FALSE;
+- settings->OrderSupport[NEG_MULTIOPAQUERECT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_MULTI_DRAWNINEGRID_INDEX] = FALSE;
+- settings->OrderSupport[NEG_LINETO_INDEX] = TRUE;
+- settings->OrderSupport[NEG_POLYLINE_INDEX] = TRUE;
+- settings->OrderSupport[NEG_MEMBLT_INDEX] = TRUE;
+- settings->OrderSupport[NEG_MEM3BLT_INDEX] = FALSE;
+- settings->OrderSupport[NEG_MEMBLT_V2_INDEX] = TRUE;
+- settings->OrderSupport[NEG_MEM3BLT_V2_INDEX] = FALSE;
+- settings->OrderSupport[NEG_SAVEBITMAP_INDEX] = FALSE;
+- settings->OrderSupport[NEG_GLYPH_INDEX_INDEX] = TRUE;
+- settings->OrderSupport[NEG_FAST_INDEX_INDEX] = TRUE;
+- settings->OrderSupport[NEG_FAST_GLYPH_INDEX] = FALSE;
+- settings->OrderSupport[NEG_POLYGON_SC_INDEX] = FALSE;
+- settings->OrderSupport[NEG_POLYGON_CB_INDEX] = FALSE;
+- settings->OrderSupport[NEG_ELLIPSE_SC_INDEX] = FALSE;
+- settings->OrderSupport[NEG_ELLIPSE_CB_INDEX] = FALSE;
+-#else
++#if !HAVE_FREERDP_1_1
+ settings->order_support[NEG_DSTBLT_INDEX] = true;
+ settings->order_support[NEG_PATBLT_INDEX] = true;
+
Bug#983560: marked as done (qdbus: not upgradable: no longer M-A:foreign)
Your message dated Fri, 26 Feb 2021 12:35:13 + with message-id and subject line Bug#983560: fixed in qttools-opensource-src 5.15.2-5 has caused the Debian Bug report #983560, regarding qdbus: not upgradable: no longer M-A:foreign 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.) -- 983560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qdbus Version: 4:5.15.2-4 Severity: serious Justification: unupgradable The new qdbus arch:all package is no longer Multi-Arch:foreign, making it uninstallable on, for example, an amd64 system which has an i386 package with Depends: qdbus installed. Given qdbus 4:4.8.7+dfsg-20 (arch:any) was already M-A:foreign it should be trivial to add. --- End Message --- --- Begin Message --- Source: qttools-opensource-src Source-Version: 5.15.2-5 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of qttools-opensource-src, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qttools-opensource-src 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, 26 Feb 2021 15:03:50 +0300 Source: qttools-opensource-src Architecture: source Version: 5.15.2-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 983560 Changes: qttools-opensource-src (5.15.2-5) unstable; urgency=medium . * Make qdbus transitional package Multi-Arch: foreign (closes: #983560). Checksums-Sha1: c9526b66a05a5753c59254e9cc39c76f189f9139 4091 qttools-opensource-src_5.15.2-5.dsc 6016bc982acc1a06970d8bada5a8e89cf896a1e4 47528 qttools-opensource-src_5.15.2-5.debian.tar.xz 2819d508be2a5fedbdbfbac7ceac823643ab55be 13295 qttools-opensource-src_5.15.2-5_source.buildinfo Checksums-Sha256: d9494ec1aa9ae57bd7a1f9e29ecfdd0d06bde6717d0718f1f217d30bda801797 4091 qttools-opensource-src_5.15.2-5.dsc 2faa1ff69e1cef5fe831958f0bfd0f6874fe93c02d84de731b42983ff76f26ee 47528 qttools-opensource-src_5.15.2-5.debian.tar.xz db9393964401b53624069d37ea3654da3873b937cc83090d44aaa829c60b0756 13295 qttools-opensource-src_5.15.2-5_source.buildinfo Files: 357d389b2b0141fb30d39d08c2abae3e 4091 libs optional qttools-opensource-src_5.15.2-5.dsc 8692000fa0c209f6982d17ef9940c674 47528 libs optional qttools-opensource-src_5.15.2-5.debian.tar.xz 173731cee23ac0beae8b096fae027cc6 13295 libs optional qttools-opensource-src_5.15.2-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmA45GgTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy+/3D/40U9lpJnb3mgmth3rEI/eIyzqmCm0T mp8cR2bv9uMRz+xKgic5zsbYfTAd9DlyrKghh8qkF6oRJ68419dKZRw9sbgFhihI q1Ox7siZLwiPoTcZSzAKLDnF44jr/Z1O+c+V753WkLUSGglt0otjb8oPTXzNuJR9 rMtI6XFCZlsw5ePpglB4W2Jmp38ce2/4yBZ+5q180v7SNteFeKHX9VEBT9Inxm3O vpYT2pAuTe7sNc7xSFXdVWbX2tQ6lbceNpgFP56KUUbieeh7r3d095d/K3G3xQ0U APw4FVReSH89EtOUekJTksZE6x5a469csXkk488dyxRpkk83zESKKajNMOdY8EHn BnVVWlEIf9goQH3raa6aUAJgi+BrugKzqzrKCzR8Jt/cfHTGPFwG0USEuQbbGFPq eor73F92V9P6rXw29mkAtThsi6zUFpzcR6I2BGWYsxluC+bFZ9vjbJ/tzOgU+jLD hGhQ4xet3ABhGqf52WGsQDwUk6RDzoIhW3JLnNH0JdqK21pPelKXOVOWQc5/QgnP Qhek4LHR0eK1GM9wS0GJghKAbBYGqyBMuPv72bTQy9Qyc7DoDfaHQGGXmkgmBfQ0 EKkJ//OkTOj9MGvvQxfg3w8KB8pRiEdQH5aCNS5Sc378B6vLf/qSbCJmRsnWdWNC b0WILdvAjLfTAg== =B4Rd -END PGP SIGNATURE End Message ---
Bug#983560: marked as pending in qttools-opensource-src
Control: tag -1 pending Hello, Bug #983560 in qttools-opensource-src 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/qt-kde-team/qt/qttools/-/commit/18e8206b41ed1d8d458388740fbbe03663b99a80 Make qdbus transitional package Multi-Arch: foreign. Closes: #983560. (this message was generated automatically) -- Greetings https://bugs.debian.org/983560
Processed: Bug#983560 marked as pending in qttools-opensource-src
Processing control commands: > tag -1 pending Bug #983560 [qdbus] qdbus: not upgradable: no longer M-A:foreign Added tag(s) pending. -- 983560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983560: qdbus: not upgradable: no longer M-A:foreign
Hi Thorsten! On Fri, Feb 26, 2021 at 09:09:50AM +, Thorsten Glaser wrote: > The new qdbus arch:all package is no longer Multi-Arch:foreign, > making it uninstallable on, for example, an amd64 system which > has an i386 package with Depends: qdbus installed. > > Given qdbus 4:4.8.7+dfsg-20 (arch:any) was already M-A:foreign > it should be trivial to add. Ok, I will fix it, but nothing should really depend on qdbus because it's a transitional package. Please also fix your dependencies. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: tagging 983010
Processing commands for cont...@bugs.debian.org: > tags 983010 + ftbfs Bug #983010 [debiman] mdocml breaks debiman autopkgtest: different output Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 983010 to src:debiman
Processing commands for cont...@bugs.debian.org: > reassign 983010 src:debiman 0.0~git20200217.fc82521-1 Bug #983010 [debiman] mdocml breaks debiman autopkgtest: different output Bug reassigned from package 'debiman' to 'src:debiman'. No longer marked as found in versions debiman/0.0~git20200217.fc82521-1. Ignoring request to alter fixed versions of bug #983010 to the same values previously set Bug #983010 [src:debiman] mdocml breaks debiman autopkgtest: different output Marked as found in versions debiman/0.0~git20200217.fc82521-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fix for #983533, fix session startup of RDP session in vinagre's RDP plugin
Processing control commands: > tags -1 patch Bug #983533 [src:vinagre] [vinagre] black screen when launching RDP session Added tag(s) patch. -- 983533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 982993 to src:python-molotov, fixed 982993 in 2.1-2, affects 982993
Processing commands for cont...@bugs.debian.org:
> reassign 982993 src:python-molotov 2.1-1
Bug #982993 {Done: Andrej Shadura } [src:python-aiohttp,
src:python-molotov] python-aiohttp breaks python-molotov autopkgtest: result
changed
Bug reassigned from package 'src:python-aiohttp, src:python-molotov' to
'src:python-molotov'.
No longer marked as found in versions python-molotov/2.1-1 and
python-aiohttp/3.7.3-1.
No longer marked as fixed in versions python-molotov/2.1-2.
Bug #982993 {Done: Andrej Shadura } [src:python-molotov]
python-aiohttp breaks python-molotov autopkgtest: result changed
Marked as found in versions python-molotov/2.1-1.
> fixed 982993 2.1-2
Bug #982993 {Done: Andrej Shadura } [src:python-molotov]
python-aiohttp breaks python-molotov autopkgtest: result changed
Marked as fixed in versions python-molotov/2.1-2.
> affects 982993 + src:python-aiohttp
Bug #982993 {Done: Andrej Shadura } [src:python-molotov]
python-aiohttp breaks python-molotov autopkgtest: result changed
Added indication that 982993 affects src:python-aiohttp
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#983365: linphone-desktop: chat messages
Hi Dennis, thanks a lot for debugging this! BTW, linphone is in desperate need of co-maintainers :-) That's a lot more useful than complaining about the package not being tested (it is, but I do not know anyone using the Chat feature, and I certainly don't). Honestly I don't know why there is ENABLE_DB_STORAGE=NO, it sneaked in during the packaging attempts. Possibly because libsoci wasn't usable without the C++11 option you found. Have you reached out to the SOCI maintainer in private already? I don't see a bug report on this. If we can get a targeted fix uploaded for this within the next days (next step of the freeze is on March 10th, with a migration time of 10 days right now) I will attempt to push through a new src:linphone upload. Do you know whether we need a new src:linphone-desktop upload as well? Have you confirmed already that the whole soci/linphone dance really fixes this issue? Bernhard Am 25.02.21 um 18:58 schrieb Dennis Filder: > Control: tag -1 + confirmed sid bullseye > > I looked into this the past days, and I think this is actually a bug > in d/rules in src:linphone. I'm beginning to suspect that this is due > to this line: > > -DENABLE_DB_STORAGE=NO \ > > Apparently the code for the once separate chat history and call > history DBs has been merged into a single DB with special logic to > handle the migration -- since I have no files from a previous version > linphone-desktop 4.2.5 here does not even create anymore the sqlite3 > database linphone.db in ~/.local/share/linphone/ that David mentions, > only call-history.db and friends.db are created (which matches the > source code). However, if the database storage isn't configured and > compiled in then that new database is not going to work of course. > Was there a specific reason for disabling this? I could get > linphone-4.4.21 to build with -DENABLE_DB_STORAGE=YES, but I had to > first build+install a version of libsoci-dev that was compiled with > -DSOCI_CXX11=YES. I'll contact the soci maintainer to see if he can > change that in time. > > linphone-4.4.21/cmake/FindSoci.cmake calls the soci support > experimental, but the official appimage ships with both libsoci_core.0 > and libsoci_sqlite3.0, so it should be stable enough for us, too. > That warning is probably outdated. I attached a diff of the linked-in > shared libraries in Debian's and the AppImage's /usr/bin/linphone > (4.2.5) to illustrate where else we deviate. > > Another issue I ran into: during dh_auto_configure a CMake macro tries > to invoke "git describe" to look up the tag for the build's branch. > Setting GIT_EXECUTABLE to a shell script that emits the expected tag > worked around that. I used $(shell pwd) there to point to the script, > but I don't know if this is the right way to do it. Fix it if it's > wrong. > > I'll keep digging into this and let you know if I learn something new. > > Regards, > Dennis >
Bug#983516: marked as done (python2.7: autopkgtest regression on amd64, i386 and ppc64el: test_ctypes fails)
Your message dated Fri, 26 Feb 2021 09:19:16 + with message-id and subject line Bug#983516: fixed in python2.7 2.7.18-4 has caused the Debian Bug report #983516, regarding python2.7: autopkgtest regression on amd64, i386 and ppc64el: test_ctypes fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python2.7 Version: 2.7.18-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python2.7 the autopkgtest of python2.7 fails in testing when that autopkgtest is run with the binary packages of python2.7 from unstable. It passes when run with only packages from testing. In tabular form: passfail python2.7 from testing2.7.18-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. 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 [1] https://qa.debian.org/excuses.php?package=python2.7 https://ci.debian.net/data/autopkgtest/testing/amd64/p/python2.7/10659876/log.gz == FAIL: test_parameter_repr (ctypes.test.test_parameters.SimpleTypesTestCase) -- Traceback (most recent call last): File "/usr/lib/python2.7/ctypes/test/test_parameters.py", line 244, in test_parameter_repr self.assertEqual(repr(c_float.from_param(1.5)), "") AssertionError: "" != "" -- Ran 457 tests in 1.220s FAILED (failures=1, skipped=86) test test_ctypes failed -- Traceback (most recent call last): File "/usr/lib/python2.7/ctypes/test/test_parameters.py", line 244, in test_parameter_repr self.assertEqual(repr(c_float.from_param(1.5)), "") AssertionError: "" != "" 1 test failed again: test_ctypes == Tests result: FAILURE then FAILURE == 356 tests OK. 1 test failed: test_ctypes 40 tests skipped: test_aepack test_al test_applesingle test_bsddb185 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_dl test_gdb test_gl test_idle test_imageop test_imgfile test_kqueue test_linuxaudiodev test_macos test_macostools test_msilib test_ossaudiodev test_scriptpackages test_smtpnet test_socketserver test_startfile test_sunaudiodev test_tcl test_timeout test_tk test_tools test_ttk_guionly test_ttk_textonly test_turtle test_urllib2net test_urllibnet test_winreg test_winsound test_zipfile64 8 skips unexpected on linux2: test_gdb test_idle test_tcl test_tk test_tools test_ttk_guionly test_ttk_textonly test_turtle 1 re-run test: test_ctypes Total duration: 12 min 14 sec Tests result: FAILURE then FAILURE OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python2.7 Source-Version: 2.7.18-4 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python2.7, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python2.7 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, 26 Feb 2021 07:17:59 +0100 Source: python2.7 Architecture: source Version: 2.7.18-4 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 983516 Changes: python2.7 (2.7.18-4) unstable; urgency=medium . * Update the patch for issue #42938 (Marc Deslauriers). Closes: #983516. Checksums-Sha1: d69825e15b94e898c3c7eb8a91188fb32c74a8b5 3313 python2.7_2.7.18-4.dsc d
Bug#983516: marked as done (python2.7: autopkgtest regression on amd64, i386 and ppc64el: test_ctypes fails)
Your message dated Fri, 26 Feb 2021 09:19:10 + with message-id and subject line Bug#983516: fixed in python2.7 2.7.18-3 has caused the Debian Bug report #983516, regarding python2.7: autopkgtest regression on amd64, i386 and ppc64el: test_ctypes fails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python2.7 Version: 2.7.18-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python2.7 the autopkgtest of python2.7 fails in testing when that autopkgtest is run with the binary packages of python2.7 from unstable. It passes when run with only packages from testing. In tabular form: passfail python2.7 from testing2.7.18-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. 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 [1] https://qa.debian.org/excuses.php?package=python2.7 https://ci.debian.net/data/autopkgtest/testing/amd64/p/python2.7/10659876/log.gz == FAIL: test_parameter_repr (ctypes.test.test_parameters.SimpleTypesTestCase) -- Traceback (most recent call last): File "/usr/lib/python2.7/ctypes/test/test_parameters.py", line 244, in test_parameter_repr self.assertEqual(repr(c_float.from_param(1.5)), "") AssertionError: "" != "" -- Ran 457 tests in 1.220s FAILED (failures=1, skipped=86) test test_ctypes failed -- Traceback (most recent call last): File "/usr/lib/python2.7/ctypes/test/test_parameters.py", line 244, in test_parameter_repr self.assertEqual(repr(c_float.from_param(1.5)), "") AssertionError: "" != "" 1 test failed again: test_ctypes == Tests result: FAILURE then FAILURE == 356 tests OK. 1 test failed: test_ctypes 40 tests skipped: test_aepack test_al test_applesingle test_bsddb185 test_cd test_cl test_codecmaps_cn test_codecmaps_hk test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_dl test_gdb test_gl test_idle test_imageop test_imgfile test_kqueue test_linuxaudiodev test_macos test_macostools test_msilib test_ossaudiodev test_scriptpackages test_smtpnet test_socketserver test_startfile test_sunaudiodev test_tcl test_timeout test_tk test_tools test_ttk_guionly test_ttk_textonly test_turtle test_urllib2net test_urllibnet test_winreg test_winsound test_zipfile64 8 skips unexpected on linux2: test_gdb test_idle test_tcl test_tk test_tools test_ttk_guionly test_ttk_textonly test_turtle 1 re-run test: test_ctypes Total duration: 12 min 14 sec Tests result: FAILURE then FAILURE OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python2.7 Source-Version: 2.7.18-3 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python2.7, 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 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated python2.7 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, 26 Feb 2021 07:17:59 +0100 Source: python2.7 Architecture: source Version: 2.7.18-3 Distribution: unstable Urgency: medium Maintainer: Matthias Klose Changed-By: Matthias Klose Closes: 983516 Changes: python2.7 (2.7.18-3) unstable; urgency=medium . * Update the patch for issue #42938 (Marc Deslauriers). Closes: #983516. Checksums-Sha1: 377b0cece554668b43e57ff0f669589533eff788 3313 python2.7_2.7.18-3.dsc c
Bug#983560: qdbus: not upgradable: no longer M-A:foreign
Package: qdbus Version: 4:5.15.2-4 Severity: serious Justification: unupgradable The new qdbus arch:all package is no longer Multi-Arch:foreign, making it uninstallable on, for example, an amd64 system which has an i386 package with Depends: qdbus installed. Given qdbus 4:4.8.7+dfsg-20 (arch:any) was already M-A:foreign it should be trivial to add.
Bug#982482: marked as done (libnettle8: chacha breakage on ppc64(el))
Your message dated Fri, 26 Feb 2021 09:04:18 + with message-id and subject line Bug#982482: fixed in nettle 3.7-2.1 has caused the Debian Bug report #982482, regarding libnettle8: chacha breakage on ppc64(el) 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.) -- 982482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnettle8 Version: 3.7-1 Severity: serious Tags: upstream patch fixed-upstream nettle 3.7 breaks GnuTLS testsuite on ppc64(el). I had forwarded this upstream https://lists.lysator.liu.se/pipermail/nettle-bugs/2021/009418.html and there is now a fix (+ testsuite coverage) in nettle GIT master. I am submitting with severity serious because chacha (assembly) does not work correctly on ppc64(el). Technically you might see this as "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." (important). - I chose to err on the side of caution to (temporarily) delay testing migration. Please downgrade if you disagree. If you want me to do so I can also do NMU. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- End Message --- --- Begin Message --- Source: nettle Source-Version: 3.7-2.1 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of nettle, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated nettle 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, 13 Feb 2021 08:34:20 +0100 Source: nettle Architecture: source Version: 3.7-2.1 Distribution: unstable Urgency: low Maintainer: Magnus Holmgren Changed-By: Andreas Metzler Closes: 982482 Changes: nettle (3.7-2.1) unstable; urgency=low . * Non-maintainer upload. * Fix chacha breakage on ppc64(el). Closes: #982482 + 0001-Improve-chacha-test-coverage.patch + 0002-Fix-chacha-counter-update-for-_4core-variants.patch Checksums-Sha1: c5b4251bc23f8ab18876b6e83e354e1b265c0cec 2262 nettle_3.7-2.1.dsc a96a960b91f5f4254c3fd1b4f9dae539f0518c40 30880 nettle_3.7-2.1.debian.tar.xz Checksums-Sha256: 13661e99da0ef9455e5c7a0716a93c2918349539e2681db232b8ca2b27409c87 2262 nettle_3.7-2.1.dsc 343ab79dbe2907eb276b756ad6a90ba8775cf41b49b5cdffc149e142a9d269fb 30880 nettle_3.7-2.1.debian.tar.xz Files: b04b325a0c2dc4b7c303d0147119a555 2262 libs optional nettle_3.7-2.1.dsc 7da627d76df5c2cd4c4d87f6897a6d2b 30880 libs optional nettle_3.7-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmAyF80ACgkQpU8BhUOC FIQc+w//cWa0hKmgfe5x8G6urE5ZsH88igRU13dNX+W96z73EM0h28KAXPG18qZI slIjwO5z+OnXN9jenygNvnj2TVwavDDKHAI1k/ZgWMeehSKYaGzTKGkozjzDJFMi V/JeRhlAYu0DAIkLNnwCzK02oQ35XeoEZyPTB2nNvcrbOKUiuxdQEVk7NJIpjP41 GOL+GHn9axrtsDUPB1r72/3gRM9k7kf21U0S0ThJUah/6ERTqi9xyIeUuiQBDmxl JiQUTQyI0hxFYtwtx4j8Y3CtRz1smSqjBC4WIlUI/nR3uVBILJYUgtPPmAp6sUR3 ctKAdabkQw/+CAbZHt5o1Bru4k9fYyr6/vEqxW1HIggY7eFawGxqLnKCmRceHNZf 0l0MGY33cnSIGKeNVPoASFPwBjSL/WvCKgLhaPP16Jo39XVA/f1CWVn17KhNF7A5 LqioHiY7+Wx9sJYue3HZbwb/7qzMcsp861kuU1OQvxYgUhzxtRWMkS/gUXvYF9I5 RV4A+fPRvkg+uHf13RYg1B4VH56BmLlcDHg3HNOAPRrS/n3TJXP6XYqSI/CMXDLy qsJsRUonhOVj4C3n21DyaOwJgk7gUZshZX0oDa4vKkXicNtXLz0OV2K1XT2CGGlF kg8a99oJ4N57I11aF9xhkKbcpnwyZZQu8l41Xk3g95agbLOWsA0= =zB6I -END PGP SIGNATURE End Message ---
Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster
Dixi quod… >Downgrading *only* the package ipxe-qemu to 1.0.0+git-20161027.b991c67-1 (the version in stretch) >on that very sid system… > >… doesn’t make this succeed either. Huh. Downgrading seabios along (need to remove -nographic to make that work) also doesn’t yield netboot success, so there’s something more complex involved in between stretch and buster… so please reassign to, once it is known, the culprit ☻ bye, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"...
Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster
Package: ipxe-qemu Version: 1.0.0+git-20190125.36a4c85-5.1 Followup-For: Bug #929983 X-Debbugs-Cc: t...@mirbsd.de This is also broken on an up-to-date-enough sid system. $ qemu-system-x86_64 -device virtio-net-pci,netdev=net0 -netdev user,id=net0 -nographic boots. $ qemu-system-x86_64 -device virtio-net-pci,netdev=net0 -netdev user,id=net0 -nographic -machine pc-1.1 fails to boot. Downgrading *only* the package ipxe-qemu to 1.0.0+git-20161027.b991c67-1 on that very sid system… … doesn’t make this succeed either. Huh. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) -- no debconf information
Bug#982993: marked as done (python-aiohttp breaks python-molotov autopkgtest: result changed)
Your message dated Fri, 26 Feb 2021 08:18:17 + with message-id and subject line Bug#982993: fixed in python-molotov 2.1-2 has caused the Debian Bug report #982993, regarding python-aiohttp breaks python-molotov autopkgtest: result changed 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.) -- 982993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-aiohttp, python-molotov Control: found -1 python-aiohttp/3.7.3-1 Control: found -1 python-molotov/2.1-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of python-aiohttp the autopkgtest of python-molotov fails in testing when that autopkgtest is run with the binary packages of python-aiohttp from unstable. It passes when run with only packages from testing. In tabular form: passfail python-aiohttp from testing3.7.3-1 python-molotov from testing2.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python-aiohttp to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-aiohttp https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-molotov/10531551/log.gz === FAILURES === TestRunner.test_delay _ self = @dedicatedloop def test_delay(self): with catch_sleep() as delay: @scenario(weight=10, delay=0.1) async def here_three(session): _RES.append(3) stdout, stderr, rc = self._test_molotov( "--delay", ".6", "--console-update", "0", "-cx", "--max-runs", "2", "-s", "here_three", "molotov.tests.test_run", ) wanted = "SUCCESSES: 2" self.assertTrue(wanted in stdout, stdout) > self.assertEqual(delay, [1, 0.1, 1, 0.6, 1, 0.1, 1, 0.6, 1]) E AssertionError: Lists differ: [1, 0.1, 1, 0.6, 1, 0.1, 1, 0.6, 1, 1] != [1, 0.1, 1, 0.6, 1, 0.1, 1, 0.6, 1] E E First list contains 1 additional elements. E First extra element 9: E 1 E E - [1, 0.1, 1, 0.6, 1, 0.1, 1, 0.6, 1, 1] E ? --- E E + [1, 0.1, 1, 0.6, 1, 0.1, 1, 0.6, 1] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-molotov Source-Version: 2.1-2 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of python-molotov, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated python-molotov 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, 26 Feb 2021 09:08:17 +0100 Source: python-molotov Architecture: source Version: 2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Andrej Shadura Closes: 982993 Changes: python-molotov (2.1-2) unstable; urgency=medium . * Add an upstream patch to unbreak tests (Closes: #982993). Checksums-Sha1: 393ab065e90fd82f3606ff34cd751c412c21ea0e 1743 python-molotov_2.1-2.dsc 468a22c38987324030f1b3e13654e079e282febe 4152 python-molotov_2.1-2.debian.tar.xz Checksums-Sha256: 189ebc4356467e017d0f349ba5bd9ee2609b38b05bdf2f2d7d8dd81f231d36b1 1743 python-molotov_
Bug#982993: marked as pending in python-molotov
Control: tag -1 pending Hello, Bug #982993 in python-molotov reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-molotov/-/commit/f3c3ab12b776a66809c5678e6b3fe29e18eba878 Add an upstream patch to unbreak tests Closes: #982993 (this message was generated automatically) -- Greetings https://bugs.debian.org/982993
Processed: Bug#982993 marked as pending in python-molotov
Processing control commands: > tag -1 pending Bug #982993 [src:python-aiohttp, src:python-molotov] python-aiohttp breaks python-molotov autopkgtest: result changed Added tag(s) pending. -- 982993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972656: closing 972656
close 972656 0.11.1-2 thanks -- Cheers, Andrej
Processed: closing 972656
Processing commands for cont...@bugs.debian.org: > close 972656 0.11.1-2 Bug #972656 [src:hypercorn] hypercorn FTBFS: test failures Ignoring request to alter fixed versions of bug #972656 to the same values previously set Bug #972656 [src:hypercorn] hypercorn FTBFS: test failures Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 972656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
