Bug#1056709: node-nodemailer: FTBFS test proxy is stuck
Source: node-nodemailer Version: 6.9.4+~6.4.9-3 Severity: serious Hello, In my local machine, when I try a pbuilder sid build of the package, I get the build stuck 1) HTTP Proxy Client Tests should connect to a socket through proxy with auth: Uncaught AssertionError: expected Error: Invalid response from proxy: 500 to not exist at Assertion.assertExist (/usr/share/nodejs/chai/lib/chai/core/assertions.js:837:10) at Assertion.propertyGetter (/usr/share/nodejs/chai/lib/chai/utils/addProperty.js:62:29) at Object.proxyGetter [as get] (/usr/share/nodejs/chai/lib/chai/utils/proxify.js:98:22) at /build/node-nodemailer-6.9.4+~6.4.9/test/smtp-connection/http-proxy-client-test.js:55:39 at Socket.onSocketData (lib/smtp-connection/http-proxy-client.js:124:28) at Socket.emit (node:events:513:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) 2) HTTP Proxy Client Tests should should fail auth: Uncaught Error: listen EADDRINUSE: address already in use :::3129 at Server.setupListenHandle [as _listen2] (node:net:1727:16) at listenInCluster (node:net:1775:12) at Server.listen (node:net:1863:7) at SMTPServer.listen (debian/tests/test_modules/smtp-server/lib/smtp-server.js:104:28) at Context. (test/smtp-connection/http-proxy-client-test.js:74:20) at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21) at Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:666:10) at /usr/share/nodejs/mocha/lib/runner.js:789:12 at next (/usr/share/nodejs/mocha/lib/runner.js:581:14) at /usr/share/nodejs/mocha/lib/runner.js:591:7 at next (/usr/share/nodejs/mocha/lib/runner.js:474:14) at Immediate. (/usr/share/nodejs/mocha/lib/runner.js:559:5) at process.processImmediate (node:internal/timers:471:21) The same happens in Ubuntu builders, with a kill after 2.5 h of run https://launchpad.net/ubuntu/+source/node-nodemailer/6.9.4+~6.4.9-3/+build/27017382/+files/buildlog_ubuntu-noble-amd64.node-nodemailer_6.9.4+~6.4.9-3_BUILDING.txt.gz G. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050989: firmware-carl9170: undeclared file conflict with firmware-linux-free
User: helm...@debian.org Usertags: dep17p1 On Fri, Sep 01, 2023 at 07:13:13AM +0200, Helmut Grohne wrote: > firmware-carl9170 installs /lib/firmware/carl9170-1.fw, which is also > currently installed by firmware-linux-free. I see that this is quite > intentional as this piece of firmware is being split out from the larger > firmware package. On a packaging level, this needs to be addressed with > Replaces, Conflicts or diversions. Failing to do so, results in an > unpack error from dpkg. I understand that getting the firmware removed > from firmware-linux-free may take a bit and you can only then set up the > correct Breaks+Replaces. That's fine. Just keep this bug open until that > matter is resolved. As linux-firmware-free moves from / to /usr. This will become a DEP17 P1 file loss problem (the one that spurred the original file move moratorium). Situations like this is exactly why dumat is also reporting file conflicts: The resulting Breaks+Replaces may become insufficient. As you resolve this conflict, please do not use Breaks+Replaces and use versioned Conflicts instead. I suggest that you add a comment referencing "DEP17 P1 M7". https://subdivi.de/~helmut/dep17.html has sections explaining the problem and the chosen mitigation. Helmut
Bug#1056708: node-wikibase-cli: Using internet during tests
Source: node-wikibase-cli Version: 15.15.4-5 Severity: serious Hello, as said, there are multiple calls to wikidata.org, making the package FTBFS with tests disabled. Error: Command failed: export WB_CLIPBOARD=false WB_LANG=en WB_MAXLAG=100 ; ./bin/wd claims -c Q12569 P2586 FetchError: request to https://www.wikidata.org/w/api.php?action=wbgetentities&ids=Q12569&format=json&props=claims failed, reason: getaddrinfo ENOTFOUND www.wikidata.org https://launchpadlibrarian.net/699385263/buildlog_ubuntu-noble-amd64.node-wikibase-cli_15.15.4-5_BUILDING.txt.gz G. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1056705: marked as done (node-mqtt: Missing dependency to node-lru-cache)
Your message dated Sat, 25 Nov 2023 04:36:26 + with message-id and subject line Bug#1056705: fixed in node-mqtt 4.3.7-3 has caused the Debian Bug report #1056705, regarding node-mqtt: Missing dependency to node-lru-cache 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.) -- 1056705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-mqtt Version: 4.3.7-2 Severity: serious Tags: patch Justification: Failure X-Debbugs-Cc: y...@debian.org Hi, node-mqtt autopkgtest shows that this package requires node-lru-cache, however it is not listed in debian/control and then start to fail when one of its dependencies no more depend on node-lru-cache. Best regards, Yadd Ref: https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mqtt/40126282/log.gz --- End Message --- --- Begin Message --- Source: node-mqtt Source-Version: 4.3.7-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-mqtt, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-mqtt 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, 25 Nov 2023 07:36:53 +0400 Source: node-mqtt Architecture: source Version: 4.3.7-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1056705 Changes: node-mqtt (4.3.7-3) unstable; urgency=medium . * Team upload * Update standards version to 4.6.2, no changes needed * Add missing dependency to node-lru-cache (Closes: #1056705) Checksums-Sha1: 57d0850e0e9ae15029c41c917260c688795f237e 2087 node-mqtt_4.3.7-3.dsc ad13b46e39dbaa0076007c6a47c1a19aabffa3eb 8312 node-mqtt_4.3.7-3.debian.tar.xz Checksums-Sha256: 764f8c0e3cc9955155de0c4be072571b1afa5b159c68b47b0d3266e579aa1847 2087 node-mqtt_4.3.7-3.dsc 69aaf7064c7ca360e1fbe81303dabedcbeabd458b5b82625e1ecaa73eb80147c 8312 node-mqtt_4.3.7-3.debian.tar.xz Files: e6b4c37acd66db323728fa4a3799d636 2087 javascript optional node-mqtt_4.3.7-3.dsc cfea285eec5b1332cd4efeadcf76a936 8312 javascript optional node-mqtt_4.3.7-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmVhc68ACgkQ9tdMp8mZ 7un5EA/8DnbbJMXSOLvSg9d04SAq64gmEVbOqVBX68TF9cv96ZoH9nr3eVVT9mMR rBmcDQQzsxth53jgf1RBSAyRVZ+h4+va/6yJlsBqtVYITi7yT3ZydBV/g12GJMqX N2LpegSN3pQ/4qdyWEU7H7IJbNCPBV9+D8B2NDLtxdpYG43rYTNmvIav1M2Wt99Y 9/U8CN3I4Du4plx2yjqvwhXSFIiSRZkLq88seksLcW2uaz8luAtV4gZ2PGyUdais 56XHIAHbmsGBdXUNHER1JHIlCuEzS05kj3f7fTruDYIuVAIsXuda8yOzQkVEsrZE uCm2gi6NTqq8eTi7EYTNVxmwroTpa0xSpXLFIxdhLij+HB5o2UhDjwDRrRvbuMaH ItL4TohN1bASSmk8rI0wALL1EDd6GppcBj5TIrXODnYYqkWAWBgYKmbXAywnxwlR fJVMe7opfbmiRRaandw3jojKvnphuzKapNBi6PMsVvnDrN/5sCkam/8q2WdKAFjR A744ikQi0jcdiOFZ/J/FkgtNpu/7e8fgY8H1bfGmm0ulvERQmU4u9QavyTQEU7IU WfTZ/Qm2RHG5hQTslBBIyQDDXuZetFupgVLrt4GedOxxmoG6eNSeVCKbY7BLxIoM GgYAhCtLKlU49ka29p5+AhvNo9X/B3v7aeMirG1yWCVVsFmzFvA= =5psf -END PGP SIGNATURE End Message ---
Processed: Bug#1056705 marked as pending in node-mqtt
Processing control commands: > tag -1 pending Bug #1056705 [node-mqtt] node-mqtt: Missing dependency to node-lru-cache Added tag(s) pending. -- 1056705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056705: marked as pending in node-mqtt
Control: tag -1 pending Hello, Bug #1056705 in node-mqtt 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/js-team/node-mqtt/-/commit/c07f088318dcd26fd7a8c320d92a5ed442f77954 Add missing dependency to node-lru-cache Closes: #1056705 (this message was generated automatically) -- Greetings https://bugs.debian.org/1056705
Bug#1056705: node-mqtt: Missing dependency to node-lru-cache
Package: node-mqtt Version: 4.3.7-2 Severity: serious Tags: patch Justification: Failure X-Debbugs-Cc: y...@debian.org Hi, node-mqtt autopkgtest shows that this package requires node-lru-cache, however it is not listed in debian/control and then start to fail when one of its dependencies no more depend on node-lru-cache. Best regards, Yadd Ref: https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-mqtt/40126282/log.gz
Bug#1054808: marked as done (x-tile: FTBFS: make: *** [debian/rules:4: clean] Error 25)
Your message dated Sat, 25 Nov 2023 03:34:07 +
with message-id
and subject line Bug#1054808: fixed in x-tile 3.3+git20220708.9ec59c9-1
has caused the Debian Bug report #1054808,
regarding x-tile: FTBFS: make: *** [debian/rules:4: clean] Error 25
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.)
--
1054808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x-tile
Version: 3.3-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.11 setup.py clean
> error: Multiple top-level packages discovered in a flat-layout: ['linux',
> 'glade', 'locale', 'modules'].
>
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
>
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
>
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
>
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/x-tile_3.3-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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 mark 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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: x-tile
Source-Version: 3.3+git20220708.9ec59c9-1
Done: Fabio Augusto De Muzio Tobich
We believe that the bug you reported is fixed in the latest version of
x-tile, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich (supplier of updated x-tile
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, 25 Nov 2023 00:18:55 -0300
Source: x-tile
Architecture: source
Version: 3.3+git20220708.9ec59c9-1
Distribution: unstable
Urgency: medium
Maintainer: Fabio Augusto De Muzio Tobich
Changed-By: Fabio Augusto De Muzio Tobich
Closes: 1054808
Changes:
x-tile (3.3+git20220708.9ec59c9-1) unstable; urgency=medium
.
* New upstream release. (Closes: #1054808)
* debian/control: bumped Standards-Version to 4.6.2.
* debian/copyright: some years updated.
* debian/patches/: removed, no longer needed.
- 010_add-keywords.patch: removed, incorporated upstream.
- series: removed, no longer needed.
Checksums-Sha1:
1ae11680661f5d1ad1ce5dd4692d9b86b19776d1 2065
x-tile_3.3+git20220708.9ec59c9-1.dsc
e0af892e8c9d2ad95b8aabd77972f51749239082 78092
x-tile_3.3+git20220708.9ec59c9.orig.tar.xz
dd0bb3c6fc8c1cb8cd14a5040cbcce2e246fc4e0 4244
x-tile_3.3+git20220708.9ec59c9-1.debian.tar.xz
0cf47daed174d9f93074043a406a88a920f3a957 9652
x-tile_3.3+git20220708.9ec59c9-1_source
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
Hi Miguel, Le 2023-11-24 à 18 h 38, Miguel Landaeta a écrit : Thomas and Jérôme, Do you have any concerns with me uploading a fix for this issue? I'm working with some folks here in Cambridge MiniDebConf and I also have some cycles to spare to work on JRuby and maybe prepare a new upstream release for 9.3 and/or 9.4 series (experimental). I've been working on a 9.4 release, you can see the progress here: https://salsa.debian.org/lavamind/jruby I plan to upload this version to experimental within a few days, I still have some minor issues with the testsuite to iron out before. Thanks, -- Jérôme
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
Hi, On Mon, Nov 20, 2023 at 04:05:31PM +0100, Helmut Grohne wrote: > I've attached the prospective change to this mail. It passes piuparts > and it passes my own test cases. I definitely think it should be > reviewed before uploaded. One thing I already see for possible > improvement is that since we declare Breaks against all providers of > /sbin/halt, this diversion does not actually have to persist beyond > postinst. Once molly-guard is configured, we know that any broken > package is no longer installed nor unpacked. A molly-guard.postinst > could remove the diversion of /sbin/halt to > /sbin/halt.no-molly-guard.usr-is-merged. Then we are only left with one > diversion per command which also makes this a lot less confusing. I have implemented the removal of unnecessary diversions in postinst and attach an updated patch. It still passes all of the tests from my earlier mail and also piuparts. > More fundamentally, I'll also have to rework the DEP17 section M18 as it > doesn't work the way it is currently pictured. I updated it. Hope this is good. Would you mind uploading it to experimental? Helmut diff -Nru molly-guard-0.8.1/debian/changelog molly-guard-0.8.1+nmu1/debian/changelog --- molly-guard-0.8.1/debian/changelog 2023-11-11 23:02:55.0 +0100 +++ molly-guard-0.8.1+nmu1/debian/changelog 2023-11-20 09:18:25.0 +0100 @@ -1,3 +1,10 @@ +molly-guard (0.8.1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Attempt to fix the /usr-merge fallout. (Closes: #1056279) + + -- Helmut Grohne Mon, 20 Nov 2023 09:18:25 +0100 + molly-guard (0.8.1) unstable; urgency=medium * Upload to unstable diff -Nru molly-guard-0.8.1/debian/control molly-guard-0.8.1+nmu1/debian/control --- molly-guard-0.8.1/debian/control2023-11-11 23:02:55.0 +0100 +++ molly-guard-0.8.1+nmu1/debian/control 2023-11-20 09:18:25.0 +0100 @@ -23,6 +23,7 @@ systemd, sysvinit, upstart +Breaks: systemd-sysv (<< 255), sysvinit-core, finit-sysv, runit-init Description: protects machines from accidental shutdowns/reboots The package installs a shell script that overrides the existing shutdown/reboot/halt/poweroff/coldreboot/pm-hibernate/pm-suspend* commands diff -Nru molly-guard-0.8.1/debian/molly-guard.postinst molly-guard-0.8.1+nmu1/debian/molly-guard.postinst --- molly-guard-0.8.1/debian/molly-guard.postinst 1970-01-01 01:00:00.0 +0100 +++ molly-guard-0.8.1+nmu1/debian/molly-guard.postinst 2023-11-20 09:18:25.0 +0100 @@ -0,0 +1,14 @@ +#!/bin/sh +set -e + +# begin-remove-after: trixie +if test "$1" = configure; then +for cmd in halt poweroff reboot shutdown coldreboot; do +dpkg-divert --package molly-guard --no-rename --remove "/sbin/$cmd" +done +fi +# end-remove-after + +#DEBHELPER# + +exit 0 diff -Nru molly-guard-0.8.1/debian/molly-guard.postrm molly-guard-0.8.1+nmu1/debian/molly-guard.postrm --- molly-guard-0.8.1/debian/molly-guard.postrm 2023-11-11 23:02:55.0 +0100 +++ molly-guard-0.8.1+nmu1/debian/molly-guard.postrm2023-11-20 09:18:25.0 +0100 @@ -16,18 +16,19 @@ # for details, see http://www.debian.org/doc/debian-policy/ or # the debian-policy package - +# begin-remove-after: trixie case "$1" in -remove) -for cmd in halt poweroff reboot shutdown coldreboot ; do -dpkg-divert --package molly-guard --no-rename --remove /sbin/$cmd -dpkg-divert --package molly-guard --no-rename --remove "/usr/sbin/$cmd" - if test -e "/usr/lib/molly-guard/$cmd"; then -mv "/usr/lib/molly-guard/$cmd" "/usr/sbin/$cmd" -fi +abort-install|abort-upgrade|failed-upgrade) +for cmd in halt poweroff shutdown coldreboot; do +dpkg-divert --package molly-guard --rename --remove "/sbin/$cmd" done +;; +esac +# end-remove-after -for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do +case "$1" in +remove) +for cmd in halt poweroff reboot shutdown coldreboot pm-hibernate pm-suspend pm-suspend-hybrid ; do dpkg-divert --package molly-guard --rename --remove /usr/sbin/$cmd done diff -Nru molly-guard-0.8.1/debian/molly-guard.preinst molly-guard-0.8.1+nmu1/debian/molly-guard.preinst --- molly-guard-0.8.1/debian/molly-guard.preinst2023-11-11 23:02:55.0 +0100 +++ molly-guard-0.8.1+nmu1/debian/molly-guard.preinst 2023-11-20 09:18:25.0 +0100 @@ -14,35 +14,55 @@ case "$1" in install|upgrade) -mkdir -p /usr/lib/molly-guard - # Cleanup erroneous diversions added in 0.6.0 for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do dpkg-divert --package molly-guard --rename --remove /sbin/$cmd done for cmd in halt poweroff reboot shutdown coldreboot ; do -dpkg-divert --package molly-guard --divert "/usr/lib/molly-guard/$cmd" --no-rename --add "/usr/sbin/$c
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
Thomas and Jérôme, Do you have any concerns with me uploading a fix for this issue? I'm working with some folks here in Cambridge MiniDebConf and I also have some cycles to spare to work on JRuby and maybe prepare a new upstream release for 9.3 and/or 9.4 series (experimental).
Bug#1042129: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
tags 1042129 + patch
thanks
Upstream handled this when they upgraded Joni dependency to 2.2 on
JRuby 9.4 series.
https://github.com/jruby/jruby/commit/3c94d31f1e198f294e9bfcb96b4188c315252b6b
https://github.com/jruby/jruby/commit/783d14bcb140477bb2577310a90742d594a48896
See attached a fix for this issue.
diff -Nru jruby-9.3.9.0+ds/debian/changelog jruby-9.3.9.0+ds/debian/changelog
--- jruby-9.3.9.0+ds/debian/changelog 2023-01-16 21:08:51.0 +
+++ jruby-9.3.9.0+ds/debian/changelog 2023-11-24 11:48:05.0 +
@@ -1,3 +1,11 @@
+jruby (9.3.9.0+ds-9~miguel1) UNRELEASED; urgency=medium
+
+ * Fix FTBFS: adapt and backport changes from 9.4 releases
+to accomodate for changes in regexp library Joni 2.2.
+(Closes: #1042129)
+
+ -- Miguel Landaeta Fri, 24 Nov 2023 11:48:05 +
+
jruby (9.3.9.0+ds-8) unstable; urgency=medium
* d/tests: flag jirb test as flaky
diff -Nru
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
---
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
1970-01-01 01:00:00.0 +0100
+++
jruby-9.3.9.0+ds/debian/patches/0012-Use-Region-accessors-in-prep-for-privatizing-fields.patch
2023-11-24 11:48:05.0 +
@@ -0,0 +1,390 @@
+Subject: Use Region accessors in prep for privatizing fields
+Forwarded:
https://github.com/jruby/jruby/commit/3c94d31f1e198f294e9bfcb96b4188c315252b6b
+--
+diff --git a/core/src/main/java/org/jruby/RubyMatchData.java
b/core/src/main/java/org/jruby/RubyMatchData.java
+index 48fa92b..87e7c9d 100644
+--- a/core/src/main/java/org/jruby/RubyMatchData.java
b/core/src/main/java/org/jruby/RubyMatchData.java
+@@ -175,11 +175,11 @@ public class RubyMatchData extends RubyObject {
+ private void updateCharOffsetOnlyOneReg(ByteList value, Encoding
encoding) {
+ if (charOffsetUpdated) return;
+
+-if (charOffsets == null || charOffsets.numRegs < 1) charOffsets = new
Region(1);
++if (charOffsets == null || charOffsets.getNumRegs() < 1) charOffsets
= new Region(1);
+
+ if (encoding.maxLength() == 1) {
+-charOffsets.beg[0] = begin;
+-charOffsets.end[0] = end;
++charOffsets.setBeg(0, begin);
++charOffsets.setEnd(0, end);
+ charOffsetUpdated = true;
+ return;
+ }
+@@ -195,14 +195,14 @@ public class RubyMatchData extends RubyObject {
+ updatePairs(value, encoding, pairs);
+
+ if (begin < 0) {
+-charOffsets.beg[0] = charOffsets.end[0] = -1;
++charOffsets.setBeg(0, charOffsets.setEnd(0, -1));
+ return;
+ }
+ Pair key = new Pair();
+ key.bytePos = begin;
+-charOffsets.beg[0] = pairs[Arrays.binarySearch(pairs, key)].charPos;
++charOffsets.setBeg(0, pairs[Arrays.binarySearch(pairs, key)].charPos);
+ key.bytePos = end;
+-charOffsets.end[0] = pairs[Arrays.binarySearch(pairs, key)].charPos;
++charOffsets.setEnd(0, pairs[Arrays.binarySearch(pairs, key)].charPos);
+
+ charOffsetUpdated = true;
+ }
+@@ -211,14 +211,14 @@ public class RubyMatchData extends RubyObject {
+ if (charOffsetUpdated) return;
+
+ final Region regs = this.regs;
+-int numRegs = regs.numRegs;
++int numRegs = regs.getNumRegs();
+
+-if (charOffsets == null || charOffsets.numRegs < numRegs) charOffsets
= new Region(numRegs);
++if (charOffsets == null || charOffsets.getNumRegs() < numRegs)
charOffsets = new Region(numRegs);
+
+ if (encoding.maxLength() == 1) {
+ for (int i = 0; i < numRegs; i++) {
+-charOffsets.beg[i] = regs.beg[i];
+-charOffsets.end[i] = regs.end[i];
++charOffsets.setBeg(i, regs.getBeg(i));
++charOffsets.setEnd(i, regs.getEnd(i));
+ }
+ charOffsetUpdated = true;
+ return;
+@@ -229,23 +229,23 @@ public class RubyMatchData extends RubyObject {
+
+ int numPos = 0;
+ for (int i = 0; i < numRegs; i++) {
+-if (regs.beg[i] < 0) continue;
+-pairs[numPos++].bytePos = regs.beg[i];
+-pairs[numPos++].bytePos = regs.end[i];
++if (regs.getBeg(i) < 0) continue;
++pairs[numPos++].bytePos = regs.getBeg(i);
++pairs[numPos++].bytePos = regs.getEnd(i);
+ }
+
+ updatePairs(value, encoding, pairs);
+
+ Pair key = new Pair();
+-for (int i = 0; i < regs.numRegs; i++) {
+-if (regs.beg[i] < 0) {
+-charOffsets.beg[i] = charOffsets.end[i] = -1;
++for (int i = 0; i < regs.getNumRegs(); i++) {
++if (regs.getBeg(i) < 0) {
++charOffsets.setBeg(i, charOffsets.setEnd(i, -1));
+
Processed: Re: jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol
Processing commands for cont...@bugs.debian.org: > tags 1042129 + patch Bug #1042129 [src:jruby] jruby: FTBFS: [ERROR] /<>/core/src/main/java/org/jruby/ext/strscan/RubyStringScanner.java:[653,34] error: cannot find symbol Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1055984 in 2.10.22-4, found 1055984 in 2.10.34-1
Processing commands for cont...@bugs.debian.org:
> found 1055984 2.10.22-4
Bug #1055984 {Done: Jeremy Bícha } [src:gimp] gimp:
CVE-2023-1 CVE-2023-2 CVE-2023-3 CVE-2023-4
Marked as found in versions gimp/2.10.22-4.
> found 1055984 2.10.34-1
Bug #1055984 {Done: Jeremy Bícha } [src:gimp] gimp:
CVE-2023-1 CVE-2023-2 CVE-2023-3 CVE-2023-4
Ignoring request to alter found versions of bug #1055984 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1055984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1054812: marked as done (lybniz: FTBFS: make: *** [debian/rules:8: clean] Error 25)
Your message dated Fri, 24 Nov 2023 22:04:25 +
with message-id
and subject line Bug#1054812: fixed in lybniz 3.0.4-6
has caused the Debian Bug report #1054812,
regarding lybniz: FTBFS: make: *** [debian/rules:8: clean] Error 25
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.)
--
1054812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lybniz
Version: 3.0.4-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.11 setup.py clean
> error: Multiple top-level packages discovered in a flat-layout: ['po',
> 'locale', 'images', 'Archive'].
>
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
>
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
>
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
>
> To find more information, look for "package discovery" on setuptools docs.
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:8: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/lybniz_3.0.4-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20231027&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
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 mark 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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: lybniz
Source-Version: 3.0.4-6
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
lybniz, 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 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated lybniz 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, 24 Nov 2023 22:38:20 +0100
Source: lybniz
Architecture: source
Version: 3.0.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 1054812
Changes:
lybniz (3.0.4-6) unstable; urgency=medium
.
* debian patch setup_package.patch adds an empty packages entry into
the setup rule in setup.py. Required by current setuptools.
Closes: #1054812.
* Standards-Version: 4.6.2
Checksums-Sha1:
f1e4add11eae5cde0f244fc5e29b8654fdb7b34c 2053 lybniz_3.0.4-6.dsc
df5c94e07e7c4fc95a8d5acac8e01d6f72c4c971 4564 lybniz_3.0.4-6.debian.tar.xz
Checksums-Sha256:
12f6000aa3e6d713edb4d5ce43d20996411bb22f1a4f0f7929f208971d243c97 2053
lybniz_3.0.4-6.dsc
c0afa887ffe7bfbec132cc98657e2cb45babe53a9da89fb0530fca8c28ebeffb 4564
lybniz_3.0.4-6.debian.tar.xz
Files:
15fe1d8da427d6e7791877e3ad87a2ae 2053 math optional lybniz_3.0.4-6.dsc
aca8f11d65fae49086ef9b890896ef43 4564 math optional
lybniz_3.0.4-6.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aA
Bug#1052770: marked as done (flask-wtf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)
Your message dated Fri, 24 Nov 2023 21:21:52 +
with message-id
and subject line Bug#1052770: fixed in flask-wtf 1.2.1-1
has caused the Debian Bug report #1052770,
regarding flask-wtf: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flask-wtf
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:110: Building wheel for python3.11 with "build"
> module
> I: pybuild base:291: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_flaskext.wtf
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/flask_wtf
> copying src/flask_wtf/file.py -> build/lib/flask_wtf
> copying src/flask_wtf/__init__.py -> build/lib/flask_wtf
> copying src/flask_wtf/i18n.py -> build/lib/flask_wtf
> copying src/flask_wtf/form.py -> build/lib/flask_wtf
> copying src/flask_wtf/_compat.py -> build/lib/flask_wtf
> copying src/flask_wtf/csrf.py -> build/lib/flask_wtf
> creating build/lib/flask_wtf/recaptcha
> copying src/flask_wtf/recaptcha/__init__.py -> build/lib/flask_wtf/recaptcha
> copying src/flask_wtf/recaptcha/fields.py -> build/lib/flask_wtf/recaptcha
> copying src/flask_wtf/recaptcha/widgets.py -> build/lib/flask_wtf/recaptcha
> copying src/flask_wtf/recaptcha/validators.py -> build/lib/flask_wtf/recaptcha
> running egg_info
> creating src/Flask_WTF.egg-info
> writing src/Flask_WTF.egg-info/PKG-INFO
> writing dependency_links to src/Flask_WTF.egg-info/dependency_links.txt
> writing requirements to src/Flask_WTF.egg-info/requires.txt
> writing top-level names to src/Flask_WTF.egg-info/top_level.txt
> writing manifest file 'src/Flask_WTF.egg-info/SOURCES.txt'
> reading manifest file 'src/Flask_WTF.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files matching '*.pyc' found anywhere in
> distribution
> adding license file 'LICENSE.rst'
> writing manifest file 'src/Flask_WTF.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/flask_wtf
> copying build/lib/flask_wtf/file.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> copying build/lib/flask_wtf/__init__.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> copying build/lib/flask_wtf/i18n.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> copying build/lib/flask_wtf/form.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> copying build/lib/flask_wtf/_compat.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> creating build/bdist.linux-x86_64/wheel/flask_wtf/recaptcha
> copying build/lib/flask_wtf/recaptcha/__init__.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf/recaptcha
> copying build/lib/flask_wtf/recaptcha/fields.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf/recaptcha
> copying build/lib/flask_wtf/recaptcha/widgets.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf/recaptcha
> copying build/lib/flask_wtf/recaptcha/validators.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf/recaptcha
> copying build/lib/flask_wtf/csrf.py ->
> build/bdist.linux-x86_64/wheel/flask_wtf
> running install_egg_info
> Copying src/Flask_WTF.egg-info to
> build/bdist.linux-x86_64/wheel/Flask_WTF-1.1.1.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/Flask_WTF-1.1.1.dist-info/WHEEL
> creating
> '/<>/.pybuild/cpython3_3.11_flaskext.wtf/.tmp-_p4dd3uz/Flask_WTF-1.1.1-py3-none-any.whl'
> and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'flask_wtf/__init__.py'
> adding 'flask_wtf/_compat.py'
> adding 'flask_wtf/csrf.py'
> adding 'flask_wtf/file.py'
> adding 'flask_wtf/form.py'
> adding 'flask_wtf/i18n.py'
> adding 'fl
Bug#1055901: Acknowledgement (raspi-firmware: postinst fails, makes bad assumption about existence of /boot/firmware/)
Hi, this applies only to Raspian, not to Debian; in Debian, older releases used /boot/firmware as well. I suggest to go ask the Raspian people to fix what they broke. Mixing packages from other distributions (here Raspian) with Debian packages is not generally supported. bye, //mirabilos (not speaking for the maintainers of this package specifically)
Bug#1056699: node-wikibase-cli fails to build from source without Internet access
Source: node-wikibase-cli Version: 15.15.4-5 Severity: serious Tags: ftbfs sid trixie This is a follow up from https://bugs.debian.org/1042298 node-wikibase-cli still fails to build from source (during dh_auto_test) without Internet access. This can be seen in the Ubuntu build: https://launchpad.net/ubuntu/+source/node-wikibase-cli/15.15.4-5 Thank you, Jeremy Bícha
Bug#1054758: marked as done (sorl-thumbnail: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1)
Your message dated Fri, 24 Nov 2023 19:37:46 + with message-id and subject line Bug#1054758: fixed in sorl-thumbnail 12.10.0-1 has caused the Debian Bug report #1054758, regarding sorl-thumbnail: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 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.) -- 1054758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sorl-thumbnail Version: 12.9.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > mkdir -p tmp-locales > localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8 > set -e; \ > for python in python3.11; do \ > for name in pil pgmagick imagemagick graphicsmagick; do \ > LOCPATH=/<>/tmp-locales LC_ALL=en_US.UTF-8 PYTHONPATH=. > LOCAL_BUILD=1 DJANGO_SETTINGS_MODULE=tests.settings.$name $python -m pytest ; > \ > done; \ > done > = test session starts > == > platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 > django: settings: tests.settings.pil (from env) > rootdir: /<> > configfile: setup.cfg > testpaths: tests > plugins: django-4.5.2 > collected 76 items > > tests/thumbnail_tests/test_alternative_resolutions.py . [ > 1%] > tests/thumbnail_tests/test_backends.py [ > 17%] > tests/thumbnail_tests/test_commands.py [ > 22%] > tests/thumbnail_tests/test_engines.py ...ss [ > 60%] > tests/thumbnail_tests/test_filters.py s.s. [ > 65%] > tests/thumbnail_tests/test_storage.py [ > 71%] > tests/thumbnail_tests/test_templatetags.py ss. [ > 90%] > tests/thumbnail_tests/test_admin.py .[ > 92%] > tests/thumbnail_tests/test_kvstore.py . [ > 93%] > tests/thumbnail_tests/test_parsers.py . > [100%] > > === warnings summary > === > ../../../usr/lib/python3/dist-packages/django/conf/__init__.py:241 > /usr/lib/python3/dist-packages/django/conf/__init__.py:241: > RemovedInDjango50Warning: The default value of USE_TZ will change from False > to True in Django 5.0. Set USE_TZ to False in your project settings if you > want to keep the current default behavior. > warnings.warn( > > ../../../usr/lib/python3/dist-packages/django/conf/__init__.py:278 > /usr/lib/python3/dist-packages/django/conf/__init__.py:278: > RemovedInDjango51Warning: The DEFAULT_FILE_STORAGE setting is deprecated. Use > STORAGES instead. > warnings.warn(DEFAULT_FILE_STORAGE_DEPRECATED_MSG, > RemovedInDjango51Warning) > > sorl/__init__.py:1 > /<>/sorl/__init__.py:1: DeprecationWarning: pkg_resources is > deprecated as an API. See > https://setuptools.pypa.io/en/latest/pkg_resources.html > from pkg_resources import get_distribution, DistributionNotFound > > ../../../usr/lib/python3/dist-packages/django/conf/__init__.py:193 > /usr/lib/python3/dist-packages/django/conf/__init__.py:193: > RemovedInDjango51Warning: The DEFAULT_FILE_STORAGE setting is deprecated. Use > STORAGES instead. > self._show_deprecation_warning( > > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html > == 70 passed, 6 skipped, 4 warnings in 1.60s > === > = test session starts > == > platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0 > django: settings: tests.settings.pgmagick (from env) > rootdir: /<> > configfile: setup.cfg > testpaths: tests > plugins: django-4.5.2 > collected 76 items > > tests/thumbnail_tests/test_alternative_resolutions.py . [ > 1%] > tests/thumbnail_tests/test_backends.py [ > 17%] > tests/thumbnail_tests/test_commands.py [ > 22%] > tests/thumbnail_tests/test_engines.py .s..s...s..ss [ > 60%] > tests/thumbnail_tests/test_filters.py s.s. [ > 65%] > tests/thumbnail_tests/test_storag
Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Control: severity -1 normal On 24.11.23 19:22, Thorsten Glaser wrote: Control: severity -1 serious thanks Matthias Klose dixit: musl is not part of the standard toolchain, not even on mips64el. Please build your package with the default toolchain This isn’t (just) an issue with a package build. you can work around it, this is not an RC issue. Please stop playing bug ping pong.
Bug#1056399: marked as done (libcryptx-perl: invalid opcode in CryptX.so)
Your message dated Fri, 24 Nov 2023 18:34:19 + with message-id and subject line Bug#1056399: fixed in libcryptx-perl 0.080-2 has caused the Debian Bug report #1056399, regarding libcryptx-perl: invalid opcode in CryptX.so 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.) -- 1056399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcryptx-perl Version: 0.080-1 Severity: important X-Debbugs-Cc: b.spran...@linutronix.de Dear maintainer, spamd fail due to an invalid opcode in CryptX.so on an AMD Athlon(tm) II X2 255 machine: 2023-11-21T13:16:47.795562+00:00 tanja kernel: [1127566.199310] traps: spamd child[12938] trap invalid opcode ip:7fd302f0e3a4 sp:7fffbb5af1f8 error:0 in CryptX.so[7fd302ebb000+9b000] Regards Benedikt Spranger -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-4-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled # lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: AuthenticAMD BIOS Vendor ID:AMD Model name:AMD Athlon(tm) II X2 255 Processor BIOS Model name: AMD Athlon(tm) II X2 255 Processor CPU @ 3.1GHz BIOS CPU family: 29 CPU family: 16 Model: 6 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping:2 CPU(s) scaling MHz: 26% CPU max MHz: 3100, CPU min MHz: 800, BogoMIPS:6227,51 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mc a cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall n x mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow cons tant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pn i monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr 8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs s kinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save Virtualization features: Virtualization:AMD-V Caches (sum of all): L1d: 128 KiB (2 instances) L1i: 128 KiB (2 instances) L2:2 MiB (2 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0,1 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Spectre v2:Mitigation; Retpolines, STIBP disabled, RSB filling, PB RSB-eIBRS Not affected Srbds: Not affected Tsx async abort: Not affected Versions of packages libcryptx-perl depends on: ii libc6 2.37-12 ii perl [libmath-bigint-perl] 5.36.0-9 ii perl-base [perlapi-5.36.0] 5.36.0-9 Versions of packages libcryptx-perl recommends: ii libjson-perl 4.1-1 libcryptx-perl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libcryptx-perl Source-Version: 0.080-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libcryptx-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libcryptx-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive admi
Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Processing control commands: > severity -1 serious Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'serious' from 'normal' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056399: libcryptx-perl: invalid opcode in CryptX.so
On Fri, 24 Nov 2023 16:24:04 +0100, Benedikt Spranger wrote: > I rebuild the Package without these flags (-msse4.1 / -maes) and > everything works as expected. I also removed the -maes flag, since AES > is, like SSE4.1, is not part of the Debian amd64 architectural > baseline. Patch is attached. Thanks alot for the analysis and the patch! Patch applied, package uploaded. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: severity of 1056399 is serious, tagging 1056399
Processing commands for cont...@bugs.debian.org: > severity 1056399 serious Bug #1056399 [libcryptx-perl] libcryptx-perl: invalid opcode in CryptX.so Severity set to 'serious' from 'important' > tags 1056399 + patch Bug #1056399 [libcryptx-perl] libcryptx-perl: invalid opcode in CryptX.so Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1056282 to gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001
Processing commands for cont...@bugs.debian.org: > retitle 1056282 gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 > CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013 CVE-2023-48014 CVE-2023-5998 CVE-2023-46001 Ignoring request to change the title of bug#1056282 to the same title > thanks Stopping processing here. Please contact me if you need assistance. -- 1056282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042222: marked as done (markdown-callouts: FTBFS: AssertionError: assert '\n')
Your message dated Fri, 24 Nov 2023 17:07:57 +
with message-id
and subject line Bug#104: fixed in markdown-callouts 0.3.0+20231124-1
has caused the Debian Bug report #104,
regarding markdown-callouts: FTBFS: AssertionError: assert '\n'
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.)
--
104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: markdown-callouts
Version: 0.3.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest -v"
> I: pybuild base:240: python3.11 -m pytest -v
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 --
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>
> configfile: pyproject.toml
> plugins: golden-0.2.2
> collecting ... collected 41 items
>
> tests/test_extension.py::test_extension[blockquotes-many-joined.yml] FAILED [
> 2%]
> tests/test_extension.py::test_extension[blockquotes-together.yml] FAILED [
> 4%]
> tests/test_extension.py::test_extension[linebreak-after.yml] FAILED [
> 7%]
> tests/test_extension.py::test_extension[blockquotes-split-by-comments.yml]
> FAILED [ 9%]
> tests/test_extension.py::test_extension[nested-block.yml] FAILED [
> 12%]
> tests/test_extension.py::test_extension[basic.yml] FAILED[
> 14%]
> tests/test_extension.py::test_extension[adjacent-1.yml] FAILED [
> 17%]
> tests/test_extension.py::test_extension[adjacent-2.yml] FAILED [
> 19%]
> tests/test_extension.py::test_extension[just-callout.yml] FAILED [
> 21%]
> tests/test_extension.py::test_extension[with-list.yml] FAILED[
> 24%]
> tests/test_extension.py::test_extension[extra-space.yml] FAILED [
> 26%]
> tests/test_extension.py::test_extension[lowercase.yml] FAILED[
> 29%]
> tests/test_extension.py::test_extension[adjacent-nope.yml] FAILED[
> 31%]
> tests/test_extension.py::test_extension[adjacent-text-block.yml] FAILED [
> 34%]
> tests/test_extension.py::test_extension[one-letter.yml] FAILED [
> 36%]
> tests/test_extension.py::test_extension[newline-first.yml] FAILED[
> 39%]
> tests/test_extension.py::test_extension[adjacent-3.yml] FAILED [
> 41%]
> tests/test_extension.py::test_extension[adjacent-text-nope.yml] FAILED [
> 43%]
> tests/test_extension.py::test_extension[details/basic.yml] FAILED[
> 46%]
> tests/test_extension.py::test_extension[details/no-space.yml] FAILED [
> 48%]
> tests/test_extension.py::test_extension[details/extra-space-nope.yml] FAILED
> [ 51%]
> tests/test_extension.py::test_extension[details/basic-open.yml] FAILED [
> 53%]
> tests/test_extension.py::test_extension[details/nested.yml] FAILED [
> 56%]
> tests/test_extension.py::test_extension[title/blockstyle-interrupted.yml]
> FAILED [ 58%]
> tests/test_extension.py::test_extension[title/avoid-title.yml] FAILED[
> 60%]
> tests/test_extension.py::test_extension[title/link-ref-as-title.yml] FAILED [
> 63%]
> tests/test_extension.py::test_extension[title/blockstyle.yml] FAILED [
> 65%]
> tests/test_extension.py::test_extension[title/preserve-dot-escape.yml] FAILED
> [ 68%]
> tests/test_extension.py::test_extension[title/linebreak-after-title.yml]
> FAILED [ 70%]
> tests/test_extension.py::test_extension[title/no-dot.yml] FAILED [
> 73%]
> tests/test_extension.py::test_extension[title/nested-block.yml] FAILED [
> 75%]
> tests/test_extension.py::test_extension[title/basic.yml] FAILED [
> 78%]
> tests/test_extension.py::test_extension[title/multiline-title.yml] FAILED [
> 80%]
> tests/test_extension.py::test_extension[title/preserve-dot-double.yml] FAILED
> [ 82%]
> tests/test_extension.py::test_extension[title/preserve-dot-format.yml] FAILED
> [ 85%]
> tests/test_extension.py::test_extension[title/no-body.yml] FAILED[
&
Bug#1056348: FTBFS: tests fail in clean environment
Hello, I've forwarded the bug upstream [1] and they made a patch [2]. Can you test their patch on your package, to check if the problem is fixed on your CI? Also, if this works, I suggest to apply their patch rather than yours to make the code more consistent with upstream, do you agree? [1] https://github.com/libssh2/libssh2/issues/1240 [2] https://github.com/libssh2/libssh2/pull/1241
Bug#1053310: marked as done (exim4-base: Various severe CVE reports are outstanding)
Your message dated Fri, 24 Nov 2023 14:47:09 + with message-id and subject line Bug#1053310: fixed in exim4 4.96-15+deb12u3 has caused the Debian Bug report #1053310, regarding exim4-base: Various severe CVE reports are outstanding 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.) -- 1053310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: exim4-base Version: 4.94.2-7 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** There are various CVE report with a rating of 9.8/10. CVE-2023-42119 CVE-2023-42118 CVE-2023-42117 CVE-2023-42116 CVE-2023-42115 CVE-2023-42114 It would help if there would be a statement by the Debian exim maintainer team, by when updates are expected to arrive. This would at least help to judge, if I should migrate my systems to postfix or if I can wait for a bugfix. *** End of the template - remove these template lines *** -- Package-specific info: Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event I18N OCSP PIPE_CONNECT PRDR PROXY SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-25-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages exim4-base depends on: ii adduser3.118 ii cron [cron-daemon] 3.0pl1-137 ii debconf [debconf-2.0] 1.5.77 ii exim4-config [exim4-config-2] 4.94.2-7 ii libc6 2.31-13+deb11u6 ii libdb5.3 5.3.28+dfsg1-0.8 ii lsb-base 11.1.0 ii netbase6.3 ii systemd-sysv 247.3-7+deb11u4 Versions of packages exim4-base recommends: ii mailutils [mailx] 1:3.10-3+b1 ii psmisc 23.4-2 Versions of packages exim4-base suggests: ii emacs-gtk [mail-reader] 1:27.1+1-3.1+deb11u2 pn exim4-doc-html | exim4-doc-info pn eximon4 ii file 1:5.39-3+deb11u1 ii mailutils [mail-reader] 1:3.10-3+b1 ii openssl 1.1.1n-0+deb11u5 pn spf-tools-perl pn swaks -- Configuration Files: /etc/logrotate.d/exim4-base changed [not included] /etc/logrotate.d/exim4-paniclog changed [not included] -- debconf information excluded --- End Message --- --- Begin Message --- Source: exim4 Source-Version: 4.96-15+deb12u3 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of exim4, 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 1053...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated exim4 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.
Bug#1056627: marked as done (cython3 has an undeclared file conflict)
Your message dated Fri, 24 Nov 2023 14:34:48 + with message-id and subject line Bug#1056627: fixed in cython 0.29.36-3 has caused the Debian Bug report #1056627, regarding cython3 has an undeclared file conflict 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.) -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cython3 Version: 0.29.36-2 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + cython3-dbg cython3 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/python3/dist-packages/Cython/Compiler/FlowControl.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/FusedNode.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Scanning.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Visitor.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Actions.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Scanners.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Runtime/refnanny.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Tempita/_tempita.cpython-311d-x86_64-linux-gnu.so are contained in the packages * cython3/0.29.36-2 as present in unstable * cython3-dbg * 0.29.32-2+b1 as present in bookworm * 0.29.36-1 as present in trixie These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: cython Source-Version: 0.29.36-3 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of cython, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated cython 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, 24 Nov 2023 13:44:02 + Source: cython Architecture: source Version: 0.29.36-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1056627 Changes: cython (0.29.36-3) unstable; urgency=medium . * Team upload. * cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627) Checksums-Sha1: e307a4412a9ab636f5af9f9760db053561a24085 1718 cython_0.29.36-3.dsc 09d7a53cdc4aa7b57019631bf1f6db4276c05cba 25836 cython_0.29.36-3.debian.tar.xz 87cfa663178cd988f9530b8f19586cb366ded6c5 7608 cython_0.29.36-3_source.buildinfo Checksums-Sha256: 428853244dcc18d22c03448915fe6bd8fa2ceb24eb7877baeea7f5d403b76ea9 1718 cython_0.29.36-3.dsc 8ae04cbda7e0579ae01cf52ab218e62f643b3d9bab8826c40586595fd05ac9e5 25836 cython_0.29.36-3.debian.tar.xz 7393e01a289802828b960907e999c690842535ee210a2ab46bc255a7410dd229 7608 cython_0.29.36-3_source.buildinfo Files: 01f7cb5dfb64932d72d9387df031ff31 1718 python optional cython_0.29.36-3.dsc fa9d9d65f8071be83df94a66830f804a 25836 python optional cython_0.29.36-3.debian.tar.xz a54e66cc90bf244781776b58a3e42af5 7608 python optional cython_0.29.36-3_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZWCpHRQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2GfHAQDZVuvZUdlfdOtW6mZq1veaOUUA3k96 6otxzP/AdyfPKgD/aJVQGXT+jfiRCKSDWuoqSMEYWh15vFt1dObU7iAyBgg= =OwSz -END PGP SIGNATURE End Message ---
Bug#1056627: marked as done (cython3 has an undeclared file conflict)
Your message dated Fri, 24 Nov 2023 14:35:10 + with message-id and subject line Bug#1056627: fixed in cython 3.0.5-2 has caused the Debian Bug report #1056627, regarding cython3 has an undeclared file conflict 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.) -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cython3 Version: 0.29.36-2 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + cython3-dbg cython3 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/python3/dist-packages/Cython/Compiler/FlowControl.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/FusedNode.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Scanning.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Visitor.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Actions.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Scanners.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Runtime/refnanny.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Tempita/_tempita.cpython-311d-x86_64-linux-gnu.so are contained in the packages * cython3/0.29.36-2 as present in unstable * cython3-dbg * 0.29.32-2+b1 as present in bookworm * 0.29.36-1 as present in trixie These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: cython Source-Version: 3.0.5-2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of cython, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated cython 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, 24 Nov 2023 13:48:37 + Source: cython Architecture: source Version: 3.0.5-2 Distribution: experimental Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1056627 Changes: cython (3.0.5-2) experimental; urgency=medium . * Team upload. * cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627) Checksums-Sha1: f7d64657f98bdceecbf58b86581f254a0c6ff974 1748 cython_3.0.5-2.dsc 27cb8c5b0333cf96bbdcbf6775e01a9185c2a02a 25516 cython_3.0.5-2.debian.tar.xz 0f6411da952c35bc14a77e0c4a8d1faf311ab57c 7600 cython_3.0.5-2_source.buildinfo Checksums-Sha256: 9e5293f08ca09da47801626d1ffee92315048616ba23fae1fef74b470d63b277 1748 cython_3.0.5-2.dsc 16108eb426ab9adaa5fe9d656ecd3e917f33bb4852401bcf21a1e6164d80ae42 25516 cython_3.0.5-2.debian.tar.xz 779c122c4fa04af7ed3f8684f5549fac75d1c46b25807728902e5c3a953ca996 7600 cython_3.0.5-2_source.buildinfo Files: 63a7169bc2e165db54f54ed2b0ca2db1 1748 python optional cython_3.0.5-2.dsc fe08525be5239551a0cf950d319dfb3d 25516 python optional cython_3.0.5-2.debian.tar.xz 7ea867548a681ff4a131cf89e1c44333 7600 python optional cython_3.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZWCp2RQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2GfdAQDz2q/W0dtc62jg/o5bUNfQFSmQKLKN VYvoK8DFDCBOJwD7BQXb7Wi+2ZeT1iEX+OmgsA0hScp0Co7CJ3GeqK8grgM= =KV1e -END PGP SIGNATURE End Message ---
Processed: Close 1054750
Processing commands for cont...@bugs.debian.org: > close 1054750 Bug #1054750 [src:reuse] reuse: FTBFS: make: *** [debian/rules:4: binary] Error 1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036255: marked as done (python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check sy
Your message dated Fri, 24 Nov 2023 14:32:12 + with message-id and subject line Bug#1036255: fixed in python3-onelogin-saml2 1.12.0-2+deb12u1 has caused the Debian Bug report #1036255, regarding python3-onelogin-saml2: FTBFS in bookworm and above: AssertionError: "Invalid issuer in the Logout Request" does not match "Could not validate timestamp: expired. Check system clock.)" 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.) -- 1036255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036255 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python3-onelogin-saml2 Version: 1.12.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230517 ftbfs-bookworm Hi, During a rebuild of all packages in testing (bookworm), your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/onelogin > copying src/onelogin/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin > creating /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xml_templates.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/constants.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/logout_request.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/logout_response.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/compat.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/response.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/settings.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/auth.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/idp_metadata_parser.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/authn_request.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/errors.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xml_utils.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/utils.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/xmlparser.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > copying src/onelogin/saml2/metadata.py -> > /<>/.pybuild/cpython3_3.11/build/onelogin/saml2 > running egg_info > creating src/python3_saml.egg-info > writing src/python3_saml.egg-info/PKG-INFO > writing dependency_links to src/python3_saml.egg-info/dependency_links.txt > writing requirements to src/python3_saml.egg-info/requires.txt > writing top-level names to src/python3_saml.egg-info/top_level.txt > writing manifest file 'src/python3_saml.egg-info/SOURCES.txt' > reading manifest file 'src/python3_saml.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > adding license file 'LICENSE' > writing manifest file 'src/python3_saml.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: > SetuptoolsDeprecationWarning: Installing 'onelogin/saml2.schemas' as data > is deprecated, please list it in `packages`. > !! > > > > # Package would be ignored # > > Python recognizes 'onelogin/saml2.schemas' as an importable package, > but it is not listed in the `packages` configuration of setuptools. > > 'onelogin/saml2.schemas' has been automatically added to the distribution > only > because it may contain data files, but this behavior is likely to change > in future versions of setuptools (and therefore is considered deprecated). > > Please make sure that 'onelogin/saml2.schemas' is included as a packa
Bug#1055962: marked as done (intel-microcode: CVE-2023-23583: INTEL-SA-00950)
Your message dated Fri, 24 Nov 2023 14:32:09 + with message-id and subject line Bug#1055962: fixed in intel-microcode 3.20231114.1~deb12u1 has caused the Debian Bug report #1055962, regarding intel-microcode: CVE-2023-23583: INTEL-SA-00950 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.) -- 1055962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intel-microcode Version: 3.20230808.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 3.20230808.1~deb12u1 Control: found -1 3.20230808.1~deb11u1 Hi, The following vulnerability was published for intel-microcode. CVE-2023-23583[0]: | Sequence of processor instructions leads to unexpected behavior for | some Intel(R) Processors may allow an authenticated user to | potentially enable escalation of privilege and/or information | disclosure and/or denial of service via local access. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-23583 https://www.cve.org/CVERecord?id=CVE-2023-23583 [1] https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html Regards, Salvatore --- End Message --- --- Begin Message --- Source: intel-microcode Source-Version: 3.20231114.1~deb12u1 Done: Henrique de Moraes Holschuh We believe that the bug you reported is fixed in the latest version of intel-microcode, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Henrique de Moraes Holschuh (supplier of updated intel-microcode 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, 18 Nov 2023 16:13:39 -0300 Source: intel-microcode Architecture: source Version: 3.20231114.1~deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Henrique de Moraes Holschuh Changed-By: Henrique de Moraes Holschuh Closes: 1055962 Changes: intel-microcode (3.20231114.1~deb12u1) bookworm-security; urgency=high . * Build for bookworm (no changes) . intel-microcode (3.20231114.1) unstable; urgency=medium . * New upstream microcode datafile 20231114 (closes: #1055962) Mitigations for "reptar", INTEL-SA-00950 (CVE-2023-23583) Sequence of processor instructions leads to unexpected behavior for some Intel(R) Processors, may allow an authenticated user to potentially enable escalation of privilege and/or information disclosure and/or denial of service via local access. Note: "reptar" on 4th gen Xeon Scalable (sig 0x806f8 pfm 0x87), 12th gen Core mobile (sig 0x906a4 pfm 0x80), 13th gen Core desktop (sig 0xb0671 pfm 0x01) were already mitigated by a previous microcode update. * Fixes for unspecified functional issues * Updated microcodes: sig 0x000606a6, pf_mask 0x87, 2023-09-01, rev 0xd0003b9, size 299008 sig 0x000606c1, pf_mask 0x10, 2023-09-08, rev 0x1000268, size 290816 sig 0x000706e5, pf_mask 0x80, 2023-09-03, rev 0x00c2, size 113664 sig 0x000806c1, pf_mask 0x80, 2023-09-07, rev 0x00b4, size 111616 sig 0x000806c2, pf_mask 0xc2, 2023-09-07, rev 0x0034, size 98304 sig 0x000806d1, pf_mask 0xc2, 2023-09-07, rev 0x004e, size 104448 sig 0x000806f8, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0, size 572416 sig 0x000806f8, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f7, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f6, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f5, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f4, pf_mask 0x87, 2023-06-16, rev 0x2b0004d0 sig 0x000806f8, pf_mask 0x10, 2023-06-26, rev 0x2c000290, size 605184 sig 0x000806f8, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x000806f6, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x000806f5, pf_mask 0x10, 2023-06-26, rev 0x2c000290 sig 0x000806f4, pf_mask 0x10, 2023-06-26, rev 0x2c000290
Bug#1055874: marked as done (intel-graphics-compiler: FTBFS in bookworm with intel-vc-intrinsics-dev 0.11)
Your message dated Fri, 24 Nov 2023 14:32:09 + with message-id and subject line Bug#1055874: fixed in intel-graphics-compiler 1.0.12504.6-1+deb12u1 has caused the Debian Bug report #1055874, regarding intel-graphics-compiler: FTBFS in bookworm with intel-vc-intrinsics-dev 0.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1055874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:intel-graphics-compiler Version: 1.0.12504.6-1 Severity: serious Tags: ftbfs bookworm Control: close -1 1.0.15136.3-1 Dear maintainer: During a rebuild of all packages in bookworm, this package failed to build with the following error: cd /<>/build/IGC/VectorCompiler/lib/BiF && ../../../Release/vcb -o VCEmulation64_SKL.vc cg.bc -cpu SKL VCEmulation64.opt.bc cd /<>/build/IGC/VectorCompiler/lib/BiF && ../../../Release/vcb -o VCEmulation64_BDW.vc cg.bc -cpu BDW VCEmulation64.opt.bc vcb: ./GenXIntrinsics/lib/GenXIntrinsics/GenXIntrinsics.cpp:476: bool llvm::GenXIntrinsic::isSupport edPlatform(const std::string&, unsigned int): Assertion `SupportedIntrinsics.find(CPU) != SupportedI ntrinsics.end() && "Unknown Platform"' failed. vcb: ./GenXIntrinsics/lib/GenXIntrinsics/GenXIntrinsics.cpp:476: bool llvm::GenXIntrinsic::isSupport edPlatform(const std::string&, unsigned int): Assertion `SupportedIntrinsics.find(CPU) != SupportedI ntrinsics.end() && "Unknown Platform"' failed. Aborted Aborted make[3]: *** [IGC/VectorCompiler/lib/BiF/CMakeFiles/VCBiFPreparation.dir/build.make:230: IGC/VectorC ompiler/lib/BiF/VCEmulation64_SKL.vccg.bc] Error 134 make[3]: *** Waiting for unfinished jobs make[3]: *** [IGC/VectorCompiler/lib/BiF/CMakeFiles/VCBiFPreparation.dir/build.make:170: IGC/VectorCompiler/lib/BiF/VCEmulation64_BDW.vccg.bc] Error 134 make[3]: Leaving directory '/<>/build' I get this error on virtual machines from three different cloud vendors (Hetzner, GCP and AWS), and the same thing happens here: https://tests.reproducible-builds.org/debian/rbuild/bookworm/amd64/intel-graphics-compiler_1.0.12504.6-1.rbuild.log.gz so I believe this is a general problem. However, if you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. Also, if this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: intel-graphics-compiler Source-Version: 1.0.12504.6-1+deb12u1 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of intel-graphics-compiler, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated intel-graphics-compiler 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, 17 Nov 2023 13:34:30 +0100 Source: intel-graphics-compiler Architecture: source Version: 1.0.12504.6-1+deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian OpenCL team Changed-By: Andreas Beckmann Closes: 1055874 Changes: intel-graphics-compiler (1.0.12504.6-1+deb12u1) bookworm; urgency=medium . * Replace patches with cherry-picked upstream commits. * Cherry-pick fixes for compatibility with intel-vc-intrinsics 0.11.0. (Closes: #1055874) * Bump intel-vc-intrinsics build-dependency to 0.11.0. * Upload to bookworm. Checksums-Sha1: a7e9101ca23c99d9e54d50ff0a92f0876723ce2c 2704 intel-graphics-compiler_1.0.12504.6-1+deb12u1.dsc e1dd3241d6525db01c601b54eb68811d887c325d 48596 intel-graphics-compiler_1.0.12504.6-1+deb12u1.debian.tar.xz a0f96b581fde0ccde2609c80c6a88df681e782d2 8197 intel-graphics-compiler_1.0.12504.6-1+deb12u1_source.buildinfo Checksums-Sha256: a6c6c16da5ad6ceb6632b092764c909726fcab754f8444e210a4ec11ca079dd1 2704 intel-graphics-compiler_1.0.12504.6-1+deb12u1.dsc e8ae070ff55deedbb10981763e3846bb78ca6e40fb23900777272205f5e3243b 48596 intel-graphics-com
Processed: Bug#1056627 marked as pending in cython
Processing control commands: > tag -1 pending Bug #1056627 [cython3] cython3 has an undeclared file conflict Ignoring request to alter tags of bug #1056627 to the same tags previously set -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1056627 marked as pending in cython
Processing control commands: > tag -1 pending Bug #1056627 [cython3] cython3 has an undeclared file conflict Added tag(s) pending. -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056627: marked as pending in cython
Control: tag -1 pending Hello, Bug #1056627 in cython 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/cython/-/commit/05b85b1c9c465cf3e0c88d96a4cdafeaf31631f1 cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056627
Bug#1056627: marked as pending in cython
Control: tag -1 pending Hello, Bug #1056627 in cython 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/cython/-/commit/075c1237c5112a873fd93c12e28981b1b5f44398 cython3: Breaks + Replaces cython3-dbg. (Closes: #1056627) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056627
Processed: Re: ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)'
Processing control commands: > reassign -1 src:ros2-performance-test-fixture Bug #1054676 [src:ros2-rosidl] ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)' Bug reassigned from package 'src:ros2-rosidl' to 'src:ros2-performance-test-fixture'. No longer marked as found in versions ros2-rosidl/3.3.1-1. Ignoring request to alter fixed versions of bug #1054676 to the same values previously set -- 1054676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054676: ros2-rosidl: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: undefined reference to `benchmark::internal::Benchmark::Benchmark(char const*)'
Control: reassign -1 src:ros2-performance-test-fixture This bug can be resolved by a rebuild of ros2-performance-test-fixture. On Fri, 27 Oct 2023 21:15:54 +0200 Lucas Nussbaum wrote: > /usr/bin/ld: > /usr/lib/x86_64-linux-gnu/libperformance_test_fixture.so.0d: > undefined reference to > `benchmark::internal::Benchmark::Benchmark(char const*)' > collect2: error: ld returned 1 exit status -- ⢀⣴⠾⠻⢶⣦⠀ ╭╮ ⣾⠁⢠⠒⠀⣿⡁ │ Timo Röhling │ ⢿⡄⠘⠷⠚⠋⠀ │ 9B03 EBB9 8300 DF97 C2B1 23BF CC8C 6BDD 1403 F4CA │ ⠈⠳⣄ ╰╯ signature.asc Description: PGP signature
Bug#1056634: marked as done (rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev)
Your message dated Fri, 24 Nov 2023 12:20:15 + with message-id and subject line Bug#1056634: fixed in rust-unsigned-varint 0.8.0-1 has caused the Debian Bug report #1056634, regarding rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev 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.) -- 1056634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-unsigned-varint Version: 0.7.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package is impossible to install: Depends on missing package librust-asynchronous-codec-0.6+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVgXaMACgkQLHwxRsGg ASENWg//Q/GyJfMmwTkVUky7/DNnckQGWr9bBDBNE0KxQ9eME+LLqqk9YQe+lamt oHNDX/qXz/ajgaTi+g+jnI7Ye6d8NZUL2hVRp83cW0U7oxVqnn/wV71QgbvVE9fH pU6WtEkOundVk+cAYyAxXkWnU5lItZ9YW8CvpQpKWA80S4rECDpFQx2lOk3Pq4AZ mXgnUj3fJZl6rzEufAgmHYa/Ad4wB2wYFIikTYjFyaWYv9wv3xnl2MnNcOeo+l2R BUXNo0EtFIoZ75gNV2imVl/K9zD5xROAEC0pf2nQo+lbcqc4lt0mCEYGHlgBCpxd 58Bo2V/OaDmVTB41G4YGjE+gcq5X833Z5ZgEYQMr/PrBSlk2rwGX0iOxOLuGvyhP HmKQ2G7V4kCfcMBc8C46un4183AaQwPLT0bxgpj7C7zJTzQPFV5fQmhY7TpVm4yR STycyyFwfxa4I71LqTp6f5rNIuaOwk9wfyR3uiQemNwXd1Y1pERZiHLGEz/7J61W 0VzaK8XpY4RI5AVoKwXU1hZyyMkvKdzQK1XRBYWjtnvtJyj9N94FNv+BzgShUhtb gOAN0M7gO6rqV700N85Cz2I7ax8AFVU2BG7117s4CY40wSeO43Uxt4MVdAinwm1e Eds8D31sfgKVPv0ip2YLehk9czosKV2Sdyo+DtvxDRTsOUygtMM= =2d3j -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: rust-unsigned-varint Source-Version: 0.8.0-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-unsigned-varint, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-unsigned-varint 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, 24 Nov 2023 11:19:15 + Source: rust-unsigned-varint Architecture: source Version: 0.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1056634 Changes: rust-unsigned-varint (0.8.0-1) unstable; urgency=medium . * Team upload. * Package unsigned-varint 0.8.0 from crates.io using debcargo 2.6.1 (Closes: #1056634) * Drop bump-tokio-util.patch, no longer needed. Checksums-Sha1: 87871042199ef203036bb00ab3c32ca67d2b2501 2366 rust-unsigned-varint_0.8.0-1.dsc eaa8d005af41d9ef278d2eade793a6f6dfa01aaf 15955 rust-unsigned-varint_0.8.0.orig.tar.gz d688456bdbc110e6fe733d17ad96bab5e7077739 3452 rust-unsigned-varint_0.8.0-1.debian.tar.xz eb59690fe184cbf6fab3a6c4bd50e6879925bf31 7755 rust-unsigned-varint_0.8.0-1_source.buildinfo Checksums-Sha256: a003e0b16b41389ac7ac5e2c45e9cb5cf3c317f3b8318fc2de90f004c8f87b64 2366 rust-unsigned-varint_0.8.0-1.dsc eb066959b24b5196ae73cb057f45598450d2c5f71460e98c49b738086eff9c06 15955 rust-unsigned-varint_0.8.0.orig.tar.gz ab737c42e741c6ad95247f296dd653b885190c0ad7b90e57eac4581e43d3ddb9 3452 rust-unsigned-varint_0.8.0-1.debian.tar.xz 2d82d1aad7b6bac2ec979a7b689e9acad33137ce719ac7da4b017586decb61d4 7755 rust-unsigned-varint_0.8.0-1_source.buildinfo Files: ae38751651152e3ab648293b67c26bc3 2366 rust optional rust-unsigned-varint_0.8.0-1.dsc be0c5dbed9d869f6099045b346844add 15955 rust optional rust-unsigned-varint_0.8.0.orig.tar.gz 15ef75b2fb6efcf6d61075bdf274456b 3452 rust optional rust-unsigned-varint_0.8.0-1.debian.tar.xz 6ab58f6053c9f97d5339f4d68cc187b2 7755 rust optional rust-unsigned-varint_0.8.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmVgkLMUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtJdg//QDpmjdbv6n7zihX2dargI+FDUEUZ /HrFUS8B+v5i5nuGv09l48ppuedrOOYVlP2wMZZcQQ520HZAjVJgVysdEUK4dPUT QTEN/zXbGmMWbidp1McCRxANybb4/0eVgikTKcMeEbo3z5i724xZcUjq8xEVpXZr m18Yba6cLH1l/pyfoxCU/dgljrgxDaidOf/ITE8Toky/v4hA5WnZLR/3J5WQszrC KTPu8y/IlOtLSvFA4QCfSAX9lGoAuBo8tBmtRPGTx7eTf3ehhE311Wj1bw2obnw9
Bug#1056639: marked as done (FTBFS: requires network during mandatory build steps)
Your message dated Fri, 24 Nov 2023 11:36:48 +
with message-id
and subject line Bug#1056639: fixed in rust-urlshortener 3.0.2-2
has caused the Debian Bug report #1056639,
regarding FTBFS: requires network during mandatory build steps
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.)
--
1056639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-urlshortener
Version: 3.0.2-1
Severity: grave
Justification for severity: Policy violation
During a rebuild of Debian testing, we ran into this test failing during an
sbuild controlled build on a VM with limit network connectivity (only
configured APT repositories usable). See log excerpt below.
This network access is a violation of policy section 4.9:
For packages in the main archive, required targets must not attempt network
access, except, via loopback interface, to services on the build host that
have been started by the build.
Inspection of the source reveals that this test indeed tries to reach
targets in the internet.
client::tests::providers stdout
IsGd -> Connection
VGd -> Connection
BamBz -> Connection
TinyPh -> Connection
FifoCc -> Connection
SCoop -> Connection
Bmeo -> Connection
UrlShortenerIo -> Connection
HmmRs -> Connection
TnyIm -> Connection
SirBz -> Connection
Rlu -> Connection
HecSu -> Connection
Abv8 -> Connection
TinyUrl -> Connection
PsbeCo -> Connection
NowLinks -> Connection
thread 'client::tests::providers' panicked at 'There are no valid providers
to use.', src/client.rs:158:9
stack backtrace:
0: std::panicking::begin_panic
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
1: urlshortener::client::tests::providers
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:158:9
2: urlshortener::client::tests::providers::{{closure}}
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:144:20
3: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
--- End Message ---
--- Begin Message ---
Source: rust-urlshortener
Source-Version: 3.0.2-2
Done: Peter Michael Green
We believe that the bug you reported is fixed in the latest version of
rust-urlshortener, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Michael Green (supplier of updated
rust-urlshortener 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, 24 Nov 2023 11:12:10 +
Source: rust-urlshortener
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
Changed-By: Peter Michael Green
Closes: 1056639
Changes:
rust-urlshortener (3.0.2-2) unstable; urgency=medium
.
* Team upload.
* Package urlshortener 3.0.2 from crates.io using debcargo 2.6.1
* Disable test which requires internet (Closes: #1056639)
Checksums-Sha1:
3b428e3d5f412452ab66b33c68a1aa67a9e68937 2331 rust-urlshortener_3.0.2-2.dsc
69d602efc3a1ca1665883c3fe5dc1fdaeebd51f6 3016
rust-urlshortener_3.0.2-2.debian.tar.xz
f704b32e0f731ed4df92d4c1a009f959406cd488 8312
rust-urlshortener_3.0.2-2_source.buildinfo
Checksums-Sha256:
fea941db887f70c418f2d48ccb8c095f7cfce9312788f031d9c3fd9ec2fe5707 2331
rust-urlshortener_3.0.2-2.dsc
4f9b756291d070608760ef58dd5a346fd55bf15776d24cfde17647d183266ef7 3016
rust-urlshortener_3.0.2-2.debian.tar.xz
cdc817cba38fd66d1a87420355990562f158081c725977c317526990d6d3141b 8312
rust-urlshortener_3.0.2-2_source.buildinfo
Files:
8042d72009c71ac06930e1d0a415d5d8 2331 rust optional
rust-urlshortener_3.0.2-2.dsc
886d94b5f7dbe32acc0ebf3e86a63ea0 3016 rust optional
rust-urlshortener_3.0.2-2.debian.tar.xz
9c74e07e168ac6c7b71c71d6c5e45f55 8312 rust optional
rust-urlshortener_3.0.2-2_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#1051433: marked as done (mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’)
Your message dated Fri, 24 Nov 2023 11:04:41 + with message-id and subject line Bug#1051433: fixed in mysql-workbench 8.0.32+dfsg-2 has caused the Debian Bug report #1051433, regarding mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’ 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.) -- 1051433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mysql-workbench Version: 8.0.32+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, mysql-workbench fails to build from source. From my build log on amd64: | | cd /<>/obj-x86_64-linux-gnu/library/base && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -DGTK_DISABLE_SINGLE_INCLUDES -DRAPIDJSON_HAS_STDSTRING -D__STDC_FORMAT_MACROS -Dwbbase_EXPORTS -I/<>/library/base -I/<>/backend/wbprivate -I/<>/backend/wbprivate/workbench -isystem /usr/include/gtkmm-3.0 -isystem /usr/lib/x86_64-linux-gnu/gtkmm-3.0/include -isystem /usr/include/giomm-2.4 -isystem /usr/lib/x86_64-linux-gnu/giomm-2.4/include -isystem /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/libmount -isystem /usr/include/blkid -isystem /usr/include/glibmm-2.4 -isystem /usr/lib/x86_64-linux-gnu/glibmm-2.4/include -isystem /usr/include/sigc++-2.0 -isystem /usr/lib/x86_64-linux-gnu/sigc++-2.0/include -isystem /usr/include/gtk-3.0 -isystem /usr/include/pango-1.0 -isystem /usr/include/harfbuzz -isystem /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem /usr/include/fribidi -isystem /usr/include/cairo -isystem /usr/include/pixman-1 -isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/gio-unix-2.0 -isystem /usr/include/cloudproviders -isystem /usr/include/atk-1.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem /usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem /usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/cairomm-1.0 -isystem /usr/lib/x86_64-linux-gnu/cairomm-1.0/include -isystem /usr/include/pangomm-1.4 -isystem /usr/lib/x86_64-linux-gnu/pangomm-1.4/include -isystem /usr/include/atkmm-1.6 -isystem /usr/lib/x86_64-linux-gnu/atkmm-1.6/include -isystem /usr/include/gtk-3.0/unix-print -isystem /usr/include/gdkmm-3.0 -isystem /usr/lib/x86_64-linux-gnu/gdkmm-3.0/include -isystem /<>/res -isystem /usr/include/python3.11 -isystem /usr/include/libxml2 -isystem /usr/include/gdal -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-error=deprecated-declarations -Wno-error=maybe-uninitialized -std=gnu++17 -fPIC -Wall -Wextra -Wno-unused-parameter -Wno-deprecated -Wno-deprecated-copy -Wno-deprecated-declarations -Werror -Wno-nonnull -MD -MT library/base/CMakeFiles/wbbase.dir/util_functions.cpp.o -MF CMakeFiles/wbbase.dir/util_functions.cpp.o.d -o CMakeFiles/wbbase.dir/util_functions.cpp.o -c /<>/library/base/util_functions.cpp | In file included from /<>/library/base/util_functions.cpp:32: | /<>/library/base/base/string_utilities.h:48:12: error: ‘int64_t’ has not been declared in ‘std’ |48 | using std::int64_t; | |^~~ | In file included from /<>/library/base/util_functions.cpp:77: | /<>/library/base/base/util_functions.h:82:30: error: ‘int64_t’ in namespace ‘std’ does not name a type |82 | BASELIBRARY_PUBLIC_FUNC std::int64_t get_physical_memory_size(void); | | ^~~ | /<>/library/base/base/util_functions.h:84:30: error: ‘int64_t’ in namespace ‘std’ does not name a type |84 | BASELIBRARY_PUBLIC_FUNC std::int64_t get_file_size(const char *filename); | | ^~~ | /<>/library/base/util_functions.cpp:85:8: error: ‘int64_t’ in namespace ‘std’ does not name a type |85 | std::int64_t _memory_in_bytes; | |^~~ | /<>/library/base/util_functions.cpp: In function ‘int _get_hardware_info(hardware_info&)’: | /<>/library/base/util_functions.cpp:557:8: error: ‘struct hardware_info’ has no member named ‘_memory_in_bytes’ | 557 | info._memory_in_bytes = get_physical_memory_size(); | |^~~~ | /<>/library/base/util_functions.cpp:557:27: error: ‘get_physical_memory_size’ was not declared in this scope | 557 | info._memory_in_bytes = get_physical_memory_size(); | | ^~
Processed: Bug#1051433 marked as pending in mysql-workbench
Processing control commands: > tag -1 pending Bug #1051433 [src:mysql-workbench] mysql-workbench: FTBFS: error: ‘int64_t’ has not been declared in ‘std’ Added tag(s) pending. -- 1051433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1051433: marked as pending in mysql-workbench
Control: tag -1 pending Hello, Bug #1051433 in mysql-workbench 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/mysql-workbench/-/commit/e565f0533284beeffe450e5da36977aa9de0af70 New patch to fix FTBFS with GCC 13 (Closes: #1051433). Thanks, Bas Couwenberg. (this message was generated automatically) -- Greetings https://bugs.debian.org/1051433
Bug#1055841: marked as done (spyder-kernels: Build-Depends on python3-xarray which is not in testing)
Your message dated Fri, 24 Nov 2023 10:34:56 + with message-id and subject line Bug#1055841: fixed in spyder-kernels 2.5.0-1 has caused the Debian Bug report #1055841, regarding spyder-kernels: Build-Depends on python3-xarray which is not in testing 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.) -- 1055841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spyder-kernels Version: 2.4.4-2 Severity: serious Tags: ftbfs Hi Maintainer spyder-kernels has a build-dependency on python3-xarray which is no longer in testing. Please drop this build-dependency or help get python3-xarray back into testing. Regards Graham --- End Message --- --- Begin Message --- Source: spyder-kernels Source-Version: 2.5.0-1 Done: Julian Gilbey We believe that the bug you reported is fixed in the latest version of spyder-kernels, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Gilbey (supplier of updated spyder-kernels 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, 24 Nov 2023 09:12:20 + Source: spyder-kernels Architecture: source Version: 2.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Julian Gilbey Closes: 1055841 Changes: spyder-kernels (2.5.0-1) unstable; urgency=medium . * New upstream version * Drop tests depending on python3-xarray until it is back in testing (closes: #1055841) Checksums-Sha1: b3a82b97422a63bd1b5c23a887c27a12bc56de40 2891 spyder-kernels_2.5.0-1.dsc b6872d259cb913341d86fb8a0cc94afb4a13c61a 94769 spyder-kernels_2.5.0.orig.tar.gz 2dbd918e31a415f2f3cc3f0118b436f304896eab 4756 spyder-kernels_2.5.0-1.debian.tar.xz 202e071a6a2d1cf057c384bd95b141ca6b358b03 12729 spyder-kernels_2.5.0-1_amd64.buildinfo Checksums-Sha256: a3b795953a156e7c6a51579924b2cf1c986ba51e50a50271b7159a0bbe259912 2891 spyder-kernels_2.5.0-1.dsc d27467da14fa5e367040f8bbed6f26b7c954198c74e00d9cbbc00b145aea707a 94769 spyder-kernels_2.5.0.orig.tar.gz 5dae200c338720e19c5d9e18ea176c78b6528dd57b53ca8ac5bd33fe4589c066 4756 spyder-kernels_2.5.0-1.debian.tar.xz 7ceb6429873b48c8b55ff6d0d000260bf53100945431dcdb642efdd9a9f8f206 12729 spyder-kernels_2.5.0-1_amd64.buildinfo Files: 9dcac1b298df18d4679f8b33d9e69dd5 2891 python optional spyder-kernels_2.5.0-1.dsc c74e8bc491cb3a229f22caf686c48558 94769 python optional spyder-kernels_2.5.0.orig.tar.gz 1d98827a166c0054f3406badedced8c5 4756 python optional spyder-kernels_2.5.0-1.debian.tar.xz df736dadf41f64034c99d17818c250ce 12729 python optional spyder-kernels_2.5.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmVgdvAPHGpkZ0BkZWJp YW4ub3JnAAoJEGlcQpMWwHv+mX0P/ROSKOZLAgKUnhOsNHQ7Dzh6ke52qJGluqoW 1fUyzLvOMuL/k/9XaN6JSpLb5JsYKhHHjSkuowcxdnpyAeL14EiPQQU4xIDGTzn9 lzM1BTkHHtVhD34LqoWENkHj+uw9S42vBzUqppJGpfe3YVzo03IHhpJazxsaPXgw EOS9lfD/suLOZ5Enz2rZ0P6Nl06MOJKgAMlnCMcHZMdjPzoqAlpgWh1CAeiNtTaZ j4+ohQSAba+w2nvgn7d4pg2OmqXNCa6itV0CI7hUGmGMTlj6yQ8+VgoImz6SAzhp NQZqiT/Z475W1FHZI56sXV0Q9pv1F3ztNhTHwQhaGbGTKSd70u156qGaS/I7p2yP 3Uzsm0XyHXqqzgNJfwL9d+AKMW72Alb2SSXwOSZ/9/UZcloGLT6KHoCrMZMR7epP lhRL08uZHsvPiKi00jB6nDt3hLhpzcOxLoc1nJId6oDK9QD/bjtAS/Vg7uGx9AEt K00I0convuBb8VgQbPWLjI5sSNVhPc12zbPvhjPhD+rcwDhKfYEJwlZEKDA+nysw 5cxDiiFv30CJbcJXxfcLYYDlD9kw+ePL21/yFZyz9EMmGTP+NKFanKCybCK2Xx6h I6O6q9b5Tgn8ZaymJbEcQJ6cNC8aAPFjipTmax30yracz3J6lCSw7hhdTN2Z975d R97EAqtZ =T48V -END PGP SIGNATURE End Message ---
Processed: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance
Processing commands for cont...@bugs.debian.org: > fixed 1037258 curl/8.2.1-1 Bug #1037258 [curl] curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance Marked as fixed in versions curl/8.2.1-1. > -- Stopping processing here. Please contact me if you need assistance. -- 1037258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded issue
Processing commands for cont...@bugs.debian.org: > forwarded 1055159 https://github.com/regebro/svg.path/issues/103 Bug #1055159 [src:python-svg.path] python-svg.path's autopkg tests fail with pillow 10.1.0 Set Bug forwarded-to-address to 'https://github.com/regebro/svg.path/issues/103'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1055159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056608: timeshift: Timeshift cant restore RSYNC snapshots if your system installed on BTRFS with wrong subvolume
Note: By "upstream doesnt have that problem" i meant that Debian Testing and Debian Sid timeshift doesnt have that problem.
Bug#1055922: marked as done (rmatrix: ABI change in Matrix 1.6-2)
Your message dated Fri, 24 Nov 2023 10:28:35 + with message-id and subject line Re: Bug#1055922: rmatrix: ABI change in Matrix 1.6-2 has caused the Debian Bug report #1055922, regarding rmatrix: ABI change in Matrix 1.6-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.) -- 1055922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rmatrix Version: 1.6-2-1 Severity: serious X-Debbugs-Cc: debia...@lists.debian.org Hi Dirk I'm opening this bug as a place for discussion and to track the affected packages. It can be closed once rmatrix and its reverse-dependencies are ready to migrate. I've copied your email to the debian-r mailing list [1] below. Regards Graham [1] https://lists.debian.org/debian-r/2023/11/msg00033.html Package Matrix is having a new and energetic maintainer/contributor in Mikael Jagan who is tidying up a few loose corners (and inter alia sent me a patch to RcppEigen that resulted in a coordinated CRAN update of RcppEigen, lme4, and OpenMx). Mikael also identified two sets of packages needed a rebuild in messages to the r-package-devel list (the more-or-less official place in the R Project to ask / discuss package changes, it is a decent to be on) following private mails between him and me. See https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010051.html https://stat.ethz.ch/pipermail/r-package-devel/2023q4/010054.html The first concerns packages using a LinkingTo: Matrix and building against Matrix _headers_. The second concerns caching of S4 signatures (which bit us at work because of SeuratObject [not in Debian] and how I got onto this). Most of these are not in Debian but I think we need binary rebuilds of irlbabecause of headers OpenMx because of headers, a new upstream 2.21.10 is out too TMB because of headers MatrixModels because of S4 caching I would appreciate it if someone could tickle rebuilds. To me a quick informal touch of debian/changelog would do; if someone thinks this needs a formal transition go for it. The R Core team and the CRAN maintainers are aware of the implicit problem with signalling the need for binary rebuilds. They are discussing this, but do not have an answer. Historically, CRAN has informally rebuilt its binaries for windows and macOS, but that of course does not help binary distributors such as us, other Linux distros, Conda, r2u, ... at all. --- End Message --- --- Begin Message --- Closing now because there's nothing to be done in rmatrix. The remaining regressions seen are caused by unrelated uploads of r-cran-seurat/r-cran-seuratobject on 2023-11-01 and r-cran-rstan/r-cran-rstanarm on 2023-10-27 which have not yet migrated.--- End Message ---
Processed: Re: Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Processing control commands: > severity -1 normal Bug #1050429 [gcc-13] musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL' Severity set to 'normal' from 'serious' -- 1050429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050429: musl: unusable on mipsel, mips64el: mipsel-linux-gnu-gcc: unrecognised command-line option '-EL'
Control: severity -1 normal
musl is not part of the standard toolchain, not even on mips64el. Please
build your package with the default toolchain, and report any other
issues upstream yourself.
On 27.08.23 17:07, Thorsten Glaser wrote:
reassign 1050429 gcc-13 13.2.0-2
notfound 1050429 12.3.0-8
affects 1050429 musl-tools
thanks
Dixi quod…
The -EL is not even musl-specific?!
(sid_mips64el-dchroot)tg@eller:~$ cat
"/usr/lib/mips64el-linux-musl/musl-gcc.specs"
[…]
Worse, doing mips64el-linux-gnuabi64-gcc{,-12} -dumpspecs and
diffing the result, there’s no change regarding -EL either.
This looks like a genuine GCC bug? I’m reassigning.
bye,
//mirabilos
Bug#1056639: FTBFS: requires network during mandatory build steps
Package: rust-urlshortener
Version: 3.0.2-1
Severity: grave
Justification for severity: Policy violation
During a rebuild of Debian testing, we ran into this test failing during an
sbuild controlled build on a VM with limit network connectivity (only
configured APT repositories usable). See log excerpt below.
This network access is a violation of policy section 4.9:
For packages in the main archive, required targets must not attempt network
access, except, via loopback interface, to services on the build host that
have been started by the build.
Inspection of the source reveals that this test indeed tries to reach
targets in the internet.
client::tests::providers stdout
IsGd -> Connection
VGd -> Connection
BamBz -> Connection
TinyPh -> Connection
FifoCc -> Connection
SCoop -> Connection
Bmeo -> Connection
UrlShortenerIo -> Connection
HmmRs -> Connection
TnyIm -> Connection
SirBz -> Connection
Rlu -> Connection
HecSu -> Connection
Abv8 -> Connection
TinyUrl -> Connection
PsbeCo -> Connection
NowLinks -> Connection
thread 'client::tests::providers' panicked at 'There are no valid providers
to use.', src/client.rs:158:9
stack backtrace:
0: std::panicking::begin_panic
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:610:12
1: urlshortener::client::tests::providers
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:158:9
2: urlshortener::client::tests::providers::{{closure}}
at
/usr/share/cargo/registry/urlshortener-3.0.2/src/client.rs:144:20
3: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
4: core::ops::function::FnOnce::call_once
at /usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
Bug#1056281: closing 1056281
close 1056281 thanks According to upstream information the issue dovered in the one CVE is only affecting Snort Open Source 3.x. Still likely snort should be removed from the archive?
Processed: closing 1056281
Processing commands for cont...@bugs.debian.org: > close 1056281 Bug #1056281 [src:snort] snort: CVE-2023-20246 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1056281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056637: debian-multimedia: depends on removed mjpegtools-gtk
Source: debian-multimedia Version: 0.10 Severity: serious mjpegtools-gtk has been dropped but multimedia-video multimedia-recording and multimedia-players still depend on it. Please update thanks G. OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: affects 1056634
Processing commands for cont...@bugs.debian.org: > affects 1056634 librust-multihash-dev librust-cid-dev librust-rust-unixfs-dev Bug #1056634 [src:rust-unsigned-varint] rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev Added indication that 1056634 affects librust-multihash-dev, librust-cid-dev, and librust-rust-unixfs-dev > thanks Stopping processing here. Please contact me if you need assistance. -- 1056634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056634: rust-unsigned-varint: depends on missing package librust-asynchronous-codec-0.6+default-dev
Source: rust-unsigned-varint Version: 0.7.1-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package is impossible to install: Depends on missing package librust-asynchronous-codec-0.6+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVgXaMACgkQLHwxRsGg ASENWg//Q/GyJfMmwTkVUky7/DNnckQGWr9bBDBNE0KxQ9eME+LLqqk9YQe+lamt oHNDX/qXz/ajgaTi+g+jnI7Ye6d8NZUL2hVRp83cW0U7oxVqnn/wV71QgbvVE9fH pU6WtEkOundVk+cAYyAxXkWnU5lItZ9YW8CvpQpKWA80S4rECDpFQx2lOk3Pq4AZ mXgnUj3fJZl6rzEufAgmHYa/Ad4wB2wYFIikTYjFyaWYv9wv3xnl2MnNcOeo+l2R BUXNo0EtFIoZ75gNV2imVl/K9zD5xROAEC0pf2nQo+lbcqc4lt0mCEYGHlgBCpxd 58Bo2V/OaDmVTB41G4YGjE+gcq5X833Z5ZgEYQMr/PrBSlk2rwGX0iOxOLuGvyhP HmKQ2G7V4kCfcMBc8C46un4183AaQwPLT0bxgpj7C7zJTzQPFV5fQmhY7TpVm4yR STycyyFwfxa4I71LqTp6f5rNIuaOwk9wfyR3uiQemNwXd1Y1pERZiHLGEz/7J61W 0VzaK8XpY4RI5AVoKwXU1hZyyMkvKdzQK1XRBYWjtnvtJyj9N94FNv+BzgShUhtb gOAN0M7gO6rqV700N85Cz2I7ax8AFVU2BG7117s4CY40wSeO43Uxt4MVdAinwm1e Eds8D31sfgKVPv0ip2YLehk9czosKV2Sdyo+DtvxDRTsOUygtMM= =2d3j -END PGP SIGNATURE-
