Bug#1028659: angband-audio: should this package be removed?
Hi, I pretty much salvaged Angband, I need a sponsor now for an upload. The mp3 files is the one reason I need to repack yet again. https://salsa.debian.org/games-team/angband Yes it will still be usefull after this. Greetings
Bug#1037928: marked as done (libmsgpack-c-dev: missing Breaks+Replaces: libmsgpack-dev (<< 6))
Your message dated Sat, 24 Jun 2023 01:05:03 + with message-id and subject line Bug#1037928: fixed in msgpack-c 6.0.0-2 has caused the Debian Bug report #1037928, regarding libmsgpack-c-dev: missing Breaks+Replaces: libmsgpack-dev (<< 6) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmsgpack-c-dev Version: 6.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmsgpack-c-dev_6.0.0-1_amd64.deb ... Unpacking libmsgpack-c-dev:amd64 (6.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/msgpack/fbuffer.h', which is also in package libmsgpack-dev:amd64 4.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb cheers, Andreas libmsgpack-dev=4.0.0-3_libmsgpack-c-dev=6.0.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: msgpack-c Source-Version: 6.0.0-2 Done: James McCoy We believe that the bug you reported is fixed in the latest version of msgpack-c, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James McCoy (supplier of updated msgpack-c 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, 23 Jun 2023 20:33:37 -0400 Source: msgpack-c Architecture: source Version: 6.0.0-2 Distribution: experimental Urgency: medium Maintainer: James McCoy Changed-By: James McCoy Closes: 1037928 Changes: msgpack-c (6.0.0-2) experimental; urgency=medium . * Add Breaks/Replaces for libmsgpack-dev < 6.0.0-1~ (Closes: #1037928) * Remove "Provides: libmsgpack-dev" from libmsgpack-c-dev Checksums-Sha1: 2895c8e16f6cd325d97ada7568b47bcf8e2367ac 2548 msgpack-c_6.0.0-2.dsc c940a52b4bec007cb2d754b5630480c18ef5a92a 7440 msgpack-c_6.0.0-2.debian.tar.xz Checksums-Sha256: cba1d572037f33fb9344e2c69c5806eceed75c79c2c06afb46acf16291270b57 2548 msgpack-c_6.0.0-2.dsc cc24e5d85d6e8d3f9ccf73d028edd35fbefefb1b175e8af2b6e86410c36428ba 7440 msgpack-c_6.0.0-2.debian.tar.xz Files: 9955ed87a630105aef0c95e06488b7b8 2548 libs optional msgpack-c_6.0.0-2.dsc 76b04a1d3806a371a3a7c815e553f0f5 7440 libs optional msgpack-c_6.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmSWOkZfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9scGA/+OGgckl7V1HE5l1VEk4tTnRu+rxJp K/RN6l3oTrxMZUn5v1Y7Lw9Lej0onIzHRhauhK/Q39ThxdwFVCL9Xyxodj7Z/mQ1 Z0m7TGc1pijBHA6UEfUGgpXgTmC/rXoDasIn2Ct8p+KnAaQvZwtceNIBrjY5XCph bHy2iAJszfvpQZO9cCRKPt2SUdvGlzBL1jP/lPz0VSRKpyi+VvRxRsznRAw2ERV+ ThiK8JnecnzIcADRS+BCgxechVcMzGdtFG9ivhKWcq4iup6WNEvVN3nB6uDZ6Dwn 1K6mOL0g1aFyxNloCymeGqrtYDghpwsTIxhn9fuoHo7Je5+5ux1tKby7VDZiWPQK YZeVLtvI1W4kGqp6R8Dl0zek5yZvqkm0m1FGzW092Uj/Evm7vQWJvttfHSRZc1dy V4iBPbGTAyGXSQt4nIQQbI8TVHMIcbXJ3mj1TcvqsTh6CMgxElVu5DqBkqvSG3i0 MZGFCoJt3j1VXm1/kz447mFh/RBNVqpjh2xAMJkc9inox33bqwZekGPoR9LZfYd1 xS//SGHb/S1gMFGk4/0DOT19IRSQWVHc3EYiK/AKG/Ip9E/v2yM3AdtaUT+vQODm 83gpvxeF4OfrjEeaUeI758Raqx1rhLAfbSoH2waIPv0Jh0itlxpl22bFY77Y++BA Hq3FMjP5xGbVfRo= =S72X -END PGP SIGNATURE End Message ---
Processed: Re: Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Processing control commands: > tag -1 + patch Bug #1038935 [schleuder] schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable=' Added tag(s) patch. -- 1038935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Control: tag -1 + patch Hi, Thanks for the report! On 23-06-23 11:20:28, Andreas Beckmann wrote: > Package: schleuder > > during a test with piuparts I noticed your package fails to upgrade > from 'buster' to 'bullseye' to 'bookworm'. > It installed fine in 'buster', and upgraded to 'bullseye' > successfully, but then the upgrade to 'bookworm' failed. I believe that's caused by ruby-arel, the attached patches fix the issue in my tests. Andreas, are you able to test these in your environment? All the best, Georg >From 45bc5cfff9adbacef1174d6bb9cd49ba8a90d860 Mon Sep 17 00:00:00 2001 From: Georg Faerber Date: Sat, 24 Jun 2023 00:14:47 + Subject: [PATCH 1/2] debian/control: add Conflicts: ruby-arel --- debian/control | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/control b/debian/control index 0f08e89..80a6f0c 100644 --- a/debian/control +++ b/debian/control @@ -32,6 +32,7 @@ Rules-Requires-Root: no Package: schleuder Architecture: all +Conflicts: ruby-arel, Depends: adduser, cron | cron-daemon, default-mta | postfix | mail-transport-agent, -- 2.30.2 >From 009d8af740408deccafd477bbbeaf8eaa6d54ec1 Mon Sep 17 00:00:00 2001 From: Georg Faerber Date: Sat, 24 Jun 2023 00:15:10 + Subject: [PATCH 2/2] debian/changelog: Debian release 4.0.3-8 --- debian/changelog | 9 + 1 file changed, 9 insertions(+) diff --git a/debian/changelog b/debian/changelog index edb2aa8..9bda664 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +schleuder (4.0.3-8) unstable; urgency=medium + + * debian/control: +- Declare that schleuder conflicts with ruby-arel. Before, database + migration failed during an upgrade, if ruby-arel was installed. + (Closes: #1038935) + + -- Georg Faerber Sat, 24 Jun 2023 00:05:14 + + schleuder (4.0.3-7) unstable; urgency=medium * Team upload -- 2.30.2
Bug#1038983: cppcheck FTBFS on architectures where char is unsigned
Source: cppcheck Version: 2.11-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=cppcheck=2.11-1 ... Testing Complete Number of tests: 4379 Number of todos: 346 Tests failed: 1 ./test/testcondition.cpp:4483(TestCondition::alwaysTrue): Assertion failed. Expected: [test.cpp:6]: (style) Condition 'o[1]=='\0'' is always false\n Actual: [test.cpp:4] -> [test.cpp:6]: (style) Condition 'o[1]=='\0'' is always false\n _ make[1]: *** [debian/rules:51: override_dh_auto_test] Error 1
Bug#1037999: marked as done (jool-dkms: module fails to build for Linux 6.3)
Your message dated Fri, 23 Jun 2023 17:02:03 -0600 with message-id and subject line jool-dkms: module fails to build for Linux 6.3 has caused the Debian Bug report #1037999, regarding jool-dkms: module fails to build for Linux 6.3 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.) -- 1037999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jool-dkms Version: 4.1.9-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for jool-dkms-4.1.9 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 10:07:23 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/4to6.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/6to4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/common.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address_xlat.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/dev.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_netfilter.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_iptables.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/log.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/atomic_config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/icmp_wrapper.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/init.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/ipv6_hdr_iterator.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/joold.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/packet.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc6052.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rtrie.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/stats.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/types.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/translation_state.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/route_out.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/skbuff.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/error_pool.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/timer.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/trace.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wkmalloc.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-global.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-types.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/xlator.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/steps/send_packet.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/address.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/atomic_config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/attribute.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/bib.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/denylist4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/eam.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/global.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/instance.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/joold.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_common.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/pool4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/session.o /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:205:21: error: initialization of 'int (*)(const struct genl_split_ops *, struct sk_buff *, struct genl_info *)' from incompatible pointer type 'int (*)(const struct genl_ops *, struct sk_buff *, struct genl_info *)' [-Werror=incompatible-pointer-types] 205 | .pre_doit = pre_handle_request, |
Bug#1037998: marked as done (gost-crypto-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'crypto_tfm_ctx')
Your message dated Fri, 23 Jun 2023 22:52:23 + with message-id and subject line Bug#1037998: fixed in gost-crypto 0.3.5-1 has caused the Debian Bug report #1037998, regarding gost-crypto-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'crypto_tfm_ctx' 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.) -- 1037998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gost-crypto-dkms Version: 0.3.4-4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for gost-crypto-0.3.4 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 10:04:49 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_basic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_modes.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gosthash94_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/kuznyechik_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/streebog_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/testmgr.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost-test-main.o /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_set_key': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: error: implicit declaration of function 'crypto_tfm_ctx' [-Werror=implicit-function-declaration] 25 | struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); |^~ /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: warning: initialization of 'struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_encrypt': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:39:46: warning: initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 39 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); | ^~ /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_decrypt': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:52:46: warning: initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 52 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); | ^~ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o] Error 1 make[1]: *** Waiting for unfinished jobs make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: /var/lib/dkms/gost-crypto/0.3.4/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64' Andreas --- End Message --- --- Begin Message --- Source: gost-crypto Source-Version: 0.3.5-1 Done: Dmitry Baryshkov We believe that the bug you reported is fixed in the latest version of gost-crypto, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Baryshkov (supplier of updated gost-crypto 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, 24 Jun 2023 01:36:19 +0300 Source: gost-crypto Architecture: source Version: 0.3.5-1 Distribution: unstable Urgency: medium Maintainer: Dmitry Baryshkov Changed-By: Dmitry Baryshkov Closes: 1037998 Changes: gost-crypto (0.3.5-1) unstable; urgency=medium . * New upstream version 0.3.5 (Closes: #1037998) Checksums-Sha1: 2360001debe4ec31bb3803cca0fd44609d6ffe0f 1610 gost-crypto_0.3.5-1.dsc 427015584ba0e29e2039606212637bf16d0c7df9 417173 gost-crypto_0.3.5.orig.tar.gz 0cff2a1f050928f0624d13f5ed0829da0e4814b2 3464 gost-crypto_0.3.5-1.debian.tar.xz
Processed: tagging 1038935
Processing commands for cont...@bugs.debian.org: > tags 1038935 + confirmed bookworm Bug #1038935 [schleuder] schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable=' Added tag(s) bookworm and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038003: xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags'
Hi all,
I've fixed this bug.
I plan to do NMU after 10 days if no one complains.
It will be uploaded to delay/10 queue.
The debdiff is as attachment.
Yours,
Paul
diff -Nru xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog
--- xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog2023-01-21
03:20:02.0 +0800
+++ xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/changelog2023-06-24
04:22:04.0 +0800
@@ -1,3 +1,11 @@
+xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix dkms build failure with kernel 6.3 (Closes: #1038003)
+- add debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
+
+ -- Ying-Chun Liu (PaulLiu) Sat, 24 Jun 2023 04:22:04
+0800
+
xtrx-dkms (0.0.1+git20190320.5ae3a3e-3.2) unstable; urgency=low
* Non-maintainer upload.
diff -Nru
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0002-xtrx.c-fix-build-error-with-kernel-6.1.patch
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0002-xtrx.c-fix-build-error-with-kernel-6.1.patch
---
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0002-xtrx.c-fix-build-error-with-kernel-6.1.patch
2023-01-21 03:20:02.0 +0800
+++
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0002-xtrx.c-fix-build-error-with-kernel-6.1.patch
2023-06-24 04:22:04.0 +0800
@@ -4,6 +4,7 @@
const pointer when building with kernel version >= 6.1
Forwarded: https://github.com/xtrx-sdr/xtrx_linux_pcie_drv/pull/15
Author: Ying-Chun Liu (PaulLiu)
+Bug-Debian: http://bugs.debian.org/1029135
Last-Update: 2023-01-21
Index: xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
===
diff -Nru
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
---
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
1970-01-01 08:00:00.0 +0800
+++
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/0003-xtrx.c-fix-build-error-with-kernel-6.3.patch
2023-06-24 04:22:04.0 +0800
@@ -0,0 +1,58 @@
+From 68d80b30a74db6c767f9b4d555d7243930c955c4 Mon Sep 17 00:00:00 2001
+From: "Ying-Chun Liu (PaulLiu)"
+Date: Sat, 24 Jun 2023 04:19:51 +0800
+Forwarded: https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/17
+Bug-Debian: http://bugs.debian.org/1038003
+Last-Update: 2023-06-24
+Subject: [PATCH] xtrx.c: fix build error with kernel 6.3
+
+vma->vm_flags is now read-only. We need to use vm_flags_set() instead.
+
+Please refer kernel commit bc292ab00f6c
+("mm: introduce vma->vm_flags wrapper functions")
+
+Signed-off-by: Ying-Chun Liu (PaulLiu)
+---
+ xtrx.c | 12
+ 1 file changed, 12 insertions(+)
+
+Index: xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
+===
+--- xtrx-dkms-0.0.1+git20190320.5ae3a3e.orig/xtrx.c
xtrx-dkms-0.0.1+git20190320.5ae3a3e/xtrx.c
+@@ -1072,7 +1072,11 @@ static int xtrxfd_mmap(struct file *filp
+ return -EINVAL;
+ }
+ //vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
++#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 3, 0)
+ vma->vm_flags |= VM_LOCKED;
++#else
++ vm_flags_set(vma, VM_LOCKED);
++#endif
+
+ if (remap_pfn_range(vma, vma->vm_start,
+
virt_to_phys((void*)((unsigned long)xtrxdev->shared_mmap)) >> PAGE_SHIFT,
+@@ -1087,7 +1091,11 @@ static int xtrxfd_mmap(struct file *filp
+ unsigned long pfn;
+ int bar = (region == REGION_CTRL) ? 0 : 1;
+ vma->vm_page_prot = pgprot_device(vma->vm_page_prot);
++#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 3, 0)
+ vma->vm_flags |= VM_IO;
++#else
++ vm_flags_set(vma, VM_IO);
++#endif
+ pfn = pci_resource_start(xtrxdev->pdev, bar) >> PAGE_SHIFT;
+
+ if (io_remap_pfn_range(vma, vma->vm_start, pfn,
+@@ -1112,7 +1120,11 @@ static int xtrxfd_mmap(struct file *filp
+ }
+
+ //vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
++#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 3, 0)
+ vma->vm_flags |= VM_LOCKED;
++#else
++ vm_flags_set(vma, VM_LOCKED);
++#endif
+
+ for (i = 0, off = 0; i < BUFS; ++i, off += bufsize) {
+ #ifdef VA_DMA_ADDR_FIXUP
diff -Nru xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series
xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series
--- xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series 2023-01-21
03:20:02.0 +0800
+++ xtrx-dkms-0.0.1+git20190320.5ae3a3e/debian/patches/series 2023-06-24
04:21:41.0 +0800
@@ -1,2 +1,3 @@
Processed: Re: xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags'
Processing commands for cont...@bugs.debian.org: > forwarded 1038003 https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/17 Bug #1038003 [xtrx-dkms] xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags' Set Bug forwarded-to-address to 'https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/17'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038003: xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags'
fowarded 1038003 https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/17 thanks Hi all, I've fixed this bug. The pull request is created in the upstream. I'll prepare an NMU very soon. Yours, Paul OpenPGP_0x44173FA13D05.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Processed (with 1 error): Re: Bug#1036950: schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)
Processing control commands: > tag -1 + confirmed bullseye Bug #1036950 [schleuder] schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6) Added tag(s) confirmed and bullseye. > X-Debbugs-CC: gitcom...@henk.geekmail.org Unknown command or malformed arguments to command. -- 1036950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036950: schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)
Control: tag -1 + confirmed bullseye Control: X-Debbugs-CC: gitcom...@henk.geekmail.org Hi, Thanks for reporting this, and sorry for my delay in answering: On 23-06-23 09:34:13, Andreas Beckmann wrote: > Followup-For: Bug #1036950 > Control: tag -1 patch > Control: retitle -1 schleuder: fails to upgrade from 'buster': insufficient > dependency on ruby-activerecord (>= 2:6) > > I'm currently testing the attached patch ... This makes sense -- thanks a lot. Actually, Hendrik Jäger (Cc:ed) reported this issue and provided a patch [1], which was uploaded to unstable on 2022/12/26 via 4.0.3-7. After a review of the patch, I also noticed this only targeted Build-Depends, but not Depends. Unfortunately, up until now, there wasn't a proposed update targeting bullseye. Andreas, how do you want to proceed? Do you have any spare cycles to handle this? This would be great -- but please don't hesitate to tell me if that's not the case, if so, I'll take over. Also, another, related question, looking at #1038935, which will require an update targeting bookworm: I assume, as Debian, qua definition, only supports upgrades from one release to the next, fixing the ruby-activerecord issue in bullseye is sufficient? All the best, Georg [1] https://salsa.debian.org/ruby-team/schleuder/-/commit/307f8f5e4125dec9d3a9b2bce5a721394c9657fa
Processed: Bug#1037494 marked as pending in redmine
Processing control commands: > tag -1 pending Bug #1037494 [src:redmine] FTBFS, fails to install on sid due to updated nokogiri Ignoring request to alter tags of bug #1037494 to the same tags previously set -- 1037494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037494: marked as pending in redmine
Control: tag -1 pending Hello, Bug #1037494 in redmine 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/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Processed: Bug#1037494 marked as pending in redmine
Processing control commands: > tag -1 pending Bug #1037494 [src:redmine] FTBFS, fails to install on sid due to updated nokogiri Ignoring request to alter tags of bug #1037494 to the same tags previously set -- 1037494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037494: marked as pending in redmine
Control: tag -1 pending Hello, Bug #1037494 in redmine 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/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Bug#1038752: marked as done (libjodycode2: A shared library package cannot be a transitional package on a different soversion)
Your message dated Fri, 23 Jun 2023 18:07:07 + with message-id and subject line Bug#1038752: fixed in libjodycode 3.0.1-3 has caused the Debian Bug report #1038752, regarding libjodycode2: A shared library package cannot be a transitional package on a different soversion 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.) -- 1038752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjodycode2 Version: 3.0.1-1 Severity: serious Tags: ftbfs Control: affects -1 src:phcpack jdupes https://buildd.debian.org/status/fetch.php?pkg=phcpack=amd64=2.4.86%2Bdfsg-5=1687282110=0 ... jdupes -l src/Python/PHCpy3/doc/build/html/_images/math jdupes: error while loading shared libraries: libjodycode.so.2: cannot open shared object file: No such file or directory make[1]: *** [debian/rules:44: override_dh_auto_build-arch] Error 127 A shared library package libjodycode2 provides the shared library libjodycode.so.2, and not providing it breaks reverse dependencies. libjodycode2 must either provide libjodycode.so.2 by shipping it or depending on a package that does ship it, or libjodycode2 must be dropped. Anything other than dropping it would be highly unusual. A transitional package libjodycode2-dev would be possible, but there is no real benefit for a just created package. The -dev package should be named libjodycode-dev, which is a stable name. --- End Message --- --- Begin Message --- Source: libjodycode Source-Version: 3.0.1-3 Done: Joao Eriberto Mota Filho We believe that the bug you reported is fixed in the latest version of libjodycode, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated libjodycode 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: Wed, 21 Jun 2023 23:26:52 -0300 Source: libjodycode Binary: libjodycode-dev libjodycode3 libjodycode3-dbgsym Architecture: source amd64 Version: 3.0.1-3 Distribution: experimental Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Description: libjodycode-dev - shared lib for programs written by Jody Bruchon (development file libjodycode3 - shared lib for programs written by Jody Bruchon (runtime) Closes: 1038752 Changes: libjodycode (3.0.1-3) experimental; urgency=medium . * Solving some mistakes in packaging of this lib. Consequently: - debian/control: ~ Dropped transitional packages libjodycode2-dev and libjodycode2. ~ Renamed libjodycode3-dev to libjodycode-dev. - debian/libjodycode3-dev.install: renamed to libjodycode-dev.install. - debian/libjodycode3.symbols: updated the Build-Depends-Package field. - Thanks to Adrian Bunk . - Closes: #1038752 Checksums-Sha1: 50689c1f72f1e98563c1069b91e12eb368a6ee4e 1962 libjodycode_3.0.1-3.dsc 8f2a2e25e18e4bdeff9cde501a2c8be46a422023 11048 libjodycode_3.0.1-3.debian.tar.xz ba7f532191c42e1834c861794e9cb783c0c95598 14004 libjodycode-dev_3.0.1-3_amd64.deb bd0fedf59cdcc69691662d0555d030cc11f13d0a 21600 libjodycode3-dbgsym_3.0.1-3_amd64.deb 6c642630c6b65f6b17c9da1fb8eaa003063f5f28 17040 libjodycode3_3.0.1-3_amd64.deb 82c3e7efa3d425ee32464b401b0d7ec5dbd20df1 6858 libjodycode_3.0.1-3_amd64.buildinfo Checksums-Sha256: 5b46f440ad17135f11f2aef03d5102044483e02e9d112aebe7a239fb43219896 1962 libjodycode_3.0.1-3.dsc 8ae4a1533dc7c14c7f5c4a387487b9ae4814af2f6e955649af02a16e7c5c4fdd 11048 libjodycode_3.0.1-3.debian.tar.xz 86ab8daf4a6e8efa1cbc74a9b89987150cb83c933ae34d63278b7ebd7a0770b3 14004 libjodycode-dev_3.0.1-3_amd64.deb 88bcc160b62899d6f1e8f6512c28492048f37577dd71d2fae80eee8842f45bc1 21600 libjodycode3-dbgsym_3.0.1-3_amd64.deb a5a6027d405c58331a4868291bd01a54e5de30e201cf80f7b904078597592f93 17040 libjodycode3_3.0.1-3_amd64.deb f2ad8a2d382dc43e66693b6caf5d2e494e757347611a783318b5fa8bd810a582 6858 libjodycode_3.0.1-3_amd64.buildinfo Files: 41a246ed0ff791b884c1f9203a7afbce 1962 libs optional libjodycode_3.0.1-3.dsc
Bug#1017919: firefox: All firefox tabs crash at startup and cannot be restored
Package: firefox
Version: 114.0-1
Followup-For: Bug #1017919
Dear Maintainer,
Confirming this, I can't open firefox here. It starts, but rapidly a
window asking for sending an error report to Mozilla shows up.
Here is the output when opening firefox from a shell:
~$ firefox
Gtk-Message: 14:40:46.947: Failed to load module "xapp-gtk3-module"
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ExceptionHandler::GenerateDump cloned child 4100
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Gtk-Message: 14:40:50.438: Failed to load module "xapp-gtk3-module"
Exiting due to channel error.
GConf Error: Failed to activate configuration server: The name
org.gnome.GConf was not provided by any .service files
Failed to open curl lib from binary, use libcurl.so instead
If any further information helps, please tell me how to provide it.
Best, Alexandre
-- Package-specific info:
-- Extensions information
Name: Add-ons Restricted Domains
Location:
/home/lymber/.mozilla/firefox/7oigojvt.default/features/{2b4fe81d-cbbd-4b4c-b450-f1bb72823e53}/addons-restricted-doma...@mozilla.com.xpi
Status: enabled
Name: Add-ons Search Detection
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Cookie AutoDelete
Location: ${PROFILE_EXTENSIONS}/cookieautodel...@kennydo.com.xpi
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: DuckDuckGo Privacy Essentials
Location: ${PROFILE_EXTENSIONS}/jid1-zadieub7xoz...@jetpack.xpi
Status: enabled
Name: eBay
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: Facebook Container
Location: ${PROFILE_EXTENSIONS}/@contain-facebook.xpi
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org.xpi
Status: enabled
Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled
Name: Picture-In-Picture
Location: /usr/lib/firefox/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: Privacy Badger
Location: ${PROFILE_EXTENSIONS}/jid1-mnnxcxisbpn...@jetpack.xpi
Status: enabled
Name: System theme — auto theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: user-disabled
Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled
Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled
-- Addons package information
ii firefox114.0-1 amd64Mozilla Firefox web browser
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox depends on:
ii debianutils 5.7-0.4
ii fontconfig 2.14.1-4
ii libasound2 1.2.9-1
ii libatk1.0-0 2.48.3-1
ii libc62.36-9
ii libcairo-gobject21.16.0-7
ii libcairo21.16.0-7
ii libdbus-1-3 1.14.8-1
ii libdbus-glib-1-2 0.112-3
ii libevent-2.1-7 2.1.12-stable-8
ii libffi8 3.4.4-1
ii libfontconfig1 2.14.1-4
ii libfreetype6 2.12.1+dfsg-5
ii libgcc-s112.2.0-14
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.74.6-2
ii libgtk-3-0 3.24.37-2
ii libnspr4 2:4.35-1.1
ii libnss3 2:3.90-2
ii libpango-1.0-0
Bug#1038954: python3-pdbfixer depends on python3-simtk no longer built by src:openmm
Package: python3-pdbfixer Version: 1.8.1-2 Severity: serious openmm (8.0.0~beta+dfsg-1) experimental; urgency=medium ... * Rename Python package python3-simtk -> python3-openmm. ... -- Andrius Merkys Tue, 25 Oct 2022 06:59:05 -0400
Bug#1037494: marked as pending in redmine
Control: tag -1 pending Hello, Bug #1037494 in redmine 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/ruby-team/redmine/-/commit/6dad08aa478f4f521b0b18ccb0887c99ad72abd5 Bump nokogiri (Closes: #1037494) (this message was generated automatically) -- Greetings https://bugs.debian.org/1037494
Processed: Bug#1037494 marked as pending in redmine
Processing control commands: > tag -1 pending Bug #1037494 [src:redmine] FTBFS, fails to install on sid due to updated nokogiri Ignoring request to alter tags of bug #1037494 to the same tags previously set -- 1037494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038897: marked as done (sumo: FTBFS with googletest 1.13 (requires C++14))
Your message dated Fri, 23 Jun 2023 14:46:21 + with message-id and subject line Bug#1038897: fixed in sumo 1.17.0+dfsg-1 has caused the Debian Bug report #1038897, regarding sumo: FTBFS with googletest 1.13 (requires C++14) 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.) -- 1038897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sumo Version: 1.15.0+dfsg-1 Severity: serious Tags: ftbfs Control: block 1038115 by -1 Dear Maintainer, Your package FTBFS with googletest 1.13 in unstable: In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /<>/unittest/src/netbuild/NBHeightMapperTest.cpp:23: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ See also: https://lists.debian.org/debian-devel/2023/06/msg00262.html Kind Regards, Bas --- End Message --- --- Begin Message --- Source: sumo Source-Version: 1.17.0+dfsg-1 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of sumo, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated sumo 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, 23 Jun 2023 12:10:37 +0200 Source: sumo Architecture: source Version: 1.17.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Bas Couwenberg Closes: 1038897 Changes: sumo (1.17.0+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream release. * Add patch to fix FTBFS with googletest 1.13. (closes: #1038897) * Update copyright file. * Refresh patches. * Exclude Windows devel file from repacked upstream release. * Bump Standards-Version to 4.6.2, no changes. * Add patch to not used deprecated distutils module. Checksums-Sha1: 1f2613e388b029e918fa1145f3549753015ae241 2381 sumo_1.17.0+dfsg-1.dsc 31cff9c87d33c5f421ccf9e76845dc72d1ff6e90 80709844 sumo_1.17.0+dfsg.orig.tar.xz 9c499554c5474e08d69a7d36008f259a635b5c92 151784 sumo_1.17.0+dfsg-1.debian.tar.xz e4e4a4e7c31d8db053d472e691281d4d3d2b117a 20904 sumo_1.17.0+dfsg-1_amd64.buildinfo Checksums-Sha256: 8b380a61d62b2f682e744e179bab6e1df5c8497463662ba94e29a4dcfe19f745 2381 sumo_1.17.0+dfsg-1.dsc 77f01421ddd47baa53a34c0921563b9239dba009c7fd26f47305a2d09f936c1d 80709844 sumo_1.17.0+dfsg.orig.tar.xz 6563b789503b831651625497c5c328352bce8e5393fb4dd27b0fa7a3262d4e0b 151784 sumo_1.17.0+dfsg-1.debian.tar.xz 73c0f3bc82eb0906910b5a2871525842342dc83b2dd592adabc56148acf0eb6b 20904 sumo_1.17.0+dfsg-1_amd64.buildinfo Files: e43d300cbf4837be7d630c7fe19dc22c 2381 science optional sumo_1.17.0+dfsg-1.dsc 42676b093c3ba0ed4e5db7aa219cbd58 80709844 science optional sumo_1.17.0+dfsg.orig.tar.xz 1ec81c08bca02c738f9f9fe040386dea 151784 science optional sumo_1.17.0+dfsg-1.debian.tar.xz 0c0b59c4b7978f3655d478595722c276 20904 science optional sumo_1.17.0+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmSVqp8ACgkQZ1DxCuiN SvECIBAA1dNszXIHlrZ+viWKJlAQ0eH86/G/qsnOsq0yujekBj4TLm/fAgII5SAL zYkIQ+gBUmcD/vUyr3SFHxkQUtMBVPK3Vs0abLiouUHgYS9wFWm+6o4plDWrbQFm zba7/KnpMxLzyA7OmnO8QT97/25ZWeE4U9g7DhlTSoq8Gi4wNHoSgMrRfB1552zv mYIB5ZRAFOgCdBGpo4lUfilnw2ktyHKrlHPlxDKJZR63l/LZu4BMGjlAqPoG2tPz REjdnzDGn1KvOFSwvZr+S39+RFtzVHd/J8lkUcCPTP8koGJ53iyOYwk13DP95iMm Up+0s5vA1sLgdSxgETDdvKTV5xLOgHysfJdowbJdS7bht3zX3bXIbSwLq10pM3c7 ZoF4fdWkNPlSzzPsUbSxD/06IDDzufV7YsAotSror37LHSJl5zbBg5n9m5C6/fsl JcOMX9da4LGDLJZprI+a7ZCK+cjEYhuCrDhriSltUmHFMH/qeH8RX5ZEwRdPz8G6 Vn8BfStLDkcvQYcwOg/ogts3qYZXPIa0zoh9WBeTbiG9wVNnzTrDN3lP5mfjXj2M Ikp6TlXQhHiqCooDEH3033Mpvuco/+2f9k+6uWBKnWG49IKATQeHEYVM9PV36ran VDzYQk2BKTzCM2P7XBR6aGQFJoYpUxv3Ev0PZW4DA7DU2vn9VK0= =MGqm -END PGP SIGNATURE End
Bug#1038896: marked as done (sumo FTBFS with googletest 1.13.0)
Your message dated Fri, 23 Jun 2023 14:46:21 + with message-id and subject line Bug#1038897: fixed in sumo 1.17.0+dfsg-1 has caused the Debian Bug report #1038897, regarding sumo FTBFS with googletest 1.13.0 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.) -- 1038897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sumo Version: 1.15.0+dfsg-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/fetch.php?pkg=sumo=armel=1.15.0%2Bdfsg-1%2Bb2=1687460689=0 ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from /<>/unittest/src/netbuild/NBHeightMapperTest.cpp:23: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... --- End Message --- --- Begin Message --- Source: sumo Source-Version: 1.17.0+dfsg-1 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of sumo, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated sumo 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, 23 Jun 2023 12:10:37 +0200 Source: sumo Architecture: source Version: 1.17.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Bas Couwenberg Closes: 1038897 Changes: sumo (1.17.0+dfsg-1) unstable; urgency=medium . * Team upload. * New upstream release. * Add patch to fix FTBFS with googletest 1.13. (closes: #1038897) * Update copyright file. * Refresh patches. * Exclude Windows devel file from repacked upstream release. * Bump Standards-Version to 4.6.2, no changes. * Add patch to not used deprecated distutils module. Checksums-Sha1: 1f2613e388b029e918fa1145f3549753015ae241 2381 sumo_1.17.0+dfsg-1.dsc 31cff9c87d33c5f421ccf9e76845dc72d1ff6e90 80709844 sumo_1.17.0+dfsg.orig.tar.xz 9c499554c5474e08d69a7d36008f259a635b5c92 151784 sumo_1.17.0+dfsg-1.debian.tar.xz e4e4a4e7c31d8db053d472e691281d4d3d2b117a 20904 sumo_1.17.0+dfsg-1_amd64.buildinfo Checksums-Sha256: 8b380a61d62b2f682e744e179bab6e1df5c8497463662ba94e29a4dcfe19f745 2381 sumo_1.17.0+dfsg-1.dsc 77f01421ddd47baa53a34c0921563b9239dba009c7fd26f47305a2d09f936c1d 80709844 sumo_1.17.0+dfsg.orig.tar.xz 6563b789503b831651625497c5c328352bce8e5393fb4dd27b0fa7a3262d4e0b 151784 sumo_1.17.0+dfsg-1.debian.tar.xz 73c0f3bc82eb0906910b5a2871525842342dc83b2dd592adabc56148acf0eb6b 20904 sumo_1.17.0+dfsg-1_amd64.buildinfo Files: e43d300cbf4837be7d630c7fe19dc22c 2381 science optional sumo_1.17.0+dfsg-1.dsc 42676b093c3ba0ed4e5db7aa219cbd58 80709844 science optional sumo_1.17.0+dfsg.orig.tar.xz 1ec81c08bca02c738f9f9fe040386dea 151784 science optional sumo_1.17.0+dfsg-1.debian.tar.xz 0c0b59c4b7978f3655d478595722c276 20904 science optional sumo_1.17.0+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmSVqp8ACgkQZ1DxCuiN SvECIBAA1dNszXIHlrZ+viWKJlAQ0eH86/G/qsnOsq0yujekBj4TLm/fAgII5SAL zYkIQ+gBUmcD/vUyr3SFHxkQUtMBVPK3Vs0abLiouUHgYS9wFWm+6o4plDWrbQFm zba7/KnpMxLzyA7OmnO8QT97/25ZWeE4U9g7DhlTSoq8Gi4wNHoSgMrRfB1552zv mYIB5ZRAFOgCdBGpo4lUfilnw2ktyHKrlHPlxDKJZR63l/LZu4BMGjlAqPoG2tPz REjdnzDGn1KvOFSwvZr+S39+RFtzVHd/J8lkUcCPTP8koGJ53iyOYwk13DP95iMm Up+0s5vA1sLgdSxgETDdvKTV5xLOgHysfJdowbJdS7bht3zX3bXIbSwLq10pM3c7 ZoF4fdWkNPlSzzPsUbSxD/06IDDzufV7YsAotSror37LHSJl5zbBg5n9m5C6/fsl JcOMX9da4LGDLJZprI+a7ZCK+cjEYhuCrDhriSltUmHFMH/qeH8RX5ZEwRdPz8G6 Vn8BfStLDkcvQYcwOg/ogts3qYZXPIa0zoh9WBeTbiG9wVNnzTrDN3lP5mfjXj2M Ikp6TlXQhHiqCooDEH3033Mpvuco/+2f9k+6uWBKnWG49IKATQeHEYVM9PV36ran VDzYQk2BKTzCM2P7XBR6aGQFJoYpUxv3Ev0PZW4DA7DU2vn9VK0= =MGqm -END PGP SIGNATURE End Message ---
Bug#1018730: lvm2: Initramfs does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot failure
I would like to share some more info. Yesterday I had a look at how dracut (version 059-4) manages LVM activation. It uses the older LVM way that allows partial VG activation: - mkdir /var/tmp/dracut cd /var/tmp/dracut/ lsinitrd --unpack /boot/initrd.img-6.1.0-9-amd64 cat etc/udev/rules.d/64-lvm.rules ... RUN+="/sbin/initqueue --settled --onetime --unique /sbin/lvm_scan" RUN+="/sbin/initqueue --timeout --name 51-lvm_scan --onetime --unique /sbin/lvm_scan --activationmode degraded" ... - On one AlmaLinux 9 VM I have for tests, the exact same udev rules are present for the initramfs, so it seems dracut-based distros still support partial VG activation (or at least some of them do). I've done some initial tests to check if those partial VGs can actually be activated by dracut. The preliminary answer is yes, they can. But I intend to do further tests to check there are no issues with complex storage architectures that involve a combination of RAID, LVM, LUKS, etc. If reopening this bug and allowing for initramfs-tools to use partial VG activation seems inappropriate, maybe dracut could be a suitable alternative for the users affected by this issue. Best wishes. -- Javier Miqueleiz (ethereal) -- "Since the best man could not be obtained, mediocre ones would have to be accepted." -- Leipzig mayor Abraham Platz, 1723, commenting on appointing Bach as the Cantor of St Thomas School, Leipzig, when Graupner refused the post (Graupner is a now long-forgotten minor musician); quoted in Werner Neuman, Bach (1961) OpenPGP_signature Description: OpenPGP digital signature
Bug#1038936: marked as done (icheck FTBFS: test failure)
Your message dated Fri, 23 Jun 2023 14:36:58 +
with message-id
and subject line Bug#1038936: fixed in icheck 0.9.7-6.6
has caused the Debian Bug report #1038936,
regarding icheck FTBFS: test failure
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.)
--
1038936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icheck
Version: 0.9.7-6.5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Bastian Germann
https://buildd.debian.org/status/logs.php?pkg=icheck=0.9.7-6.5
...
/usr/bin/make test
make[1]: Entering directory '/<>'
./test.pl t
Processing t/00_empty...
Processing t/01_fundamental...
Processing t/02_struct...
Processing t/03_baseline...
Processing t/04_align...
Differences in compare output
@@ -1,16 +0,0 @@
-ABI mismatch: size of 64 versus 136
-ABI mismatch: alignment of 32 versus 136
- in type defined at t/04_align/source/foo.c:1:
-struct __attribute__((aligned(__alignof__(int foo1
- {
-int a;
-char b;
- };
- versus type defined at t/04_align/source/foo.c:1:
-struct __attribute__((aligned(17), aligned(__alignof__(int foo1
- {
-int a;
-char b;
- };
-
-ABI is not compatible
Test t/04_align failed
4/5 (80%) tests passed
make[1]: *** [Makefile:191: test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: debian/build-stamp] Error 2
--- End Message ---
--- Begin Message ---
Source: icheck
Source-Version: 0.9.7-6.6
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
icheck, 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 1038...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann (supplier of updated icheck 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, 23 Jun 2023 16:02:35 +0200
Source: icheck
Architecture: source
Version: 0.9.7-6.6
Distribution: unstable
Urgency: medium
Maintainer: Erinn Clark
Changed-By: Bastian Germann
Closes: 1038936
Changes:
icheck (0.9.7-6.6) unstable; urgency=medium
.
* Non-maintainer upload.
* Add missing patch to suppress test case 04's diff. (Closes: #1038936)
Checksums-Sha1:
119d9649bc478ab8c2dbd0ae03e9b4a9834ef558 1521 icheck_0.9.7-6.6.dsc
d290298f774058de2a4fe0186fc8065bcf0b6219 4064 icheck_0.9.7-6.6.debian.tar.xz
0c7079d9f9799d3e59fb01178cd5ac8986b162cb 5724 icheck_0.9.7-6.6_source.buildinfo
Checksums-Sha256:
03486fe38673de3cdd5933d45d1067b3cb873c82907b3fc446db0b5b2d9e4874 1521
icheck_0.9.7-6.6.dsc
ee58eb0babfe2f7908d946a94354f0fdc8fa4fce2d72e8e15887e1ae0102f44b 4064
icheck_0.9.7-6.6.debian.tar.xz
208da2684a30ab9ae7bcaa824b3fe56d8eb55e5e8cea84d7586cbee7e67b5dfa 5724
icheck_0.9.7-6.6_source.buildinfo
Files:
2d75e74999b6f127c9ff0b8330d4c65f 1521 devel optional icheck_0.9.7-6.6.dsc
d9be8f29cdea90eb502f7e2093f0fbfa 4064 devel optional
icheck_0.9.7-6.6.debian.tar.xz
89606e37197a46760969eee2db190786 5724 devel optional
icheck_0.9.7-6.6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmSVpnsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAaIDAD3V7kTCIci5tYybiIBd2mbOXuKNPArUN0c
l7gjUg8YJI0L/bnhZDOfDJwwW9i4Sg4hOuEre8/zuMe8wZa3ydUh45294+/RVWRY
qVCpPYo1fpQksZOIevYuKFwiJ0WZU0xHf/757SVGou0dVTEcLGV4N8HmGeBg2+Kv
lo0XHkI3D8w4Beh+yz8iDXuN2r38Vns8EMk+MCtlHsK3CpmF6Po/bD6Xq85/THD7
sKAlhMuUoWcv1IKi7pQcb396hX7KZTV24Qh3KdhiZ5JwUA4X9COeMLv/wIVLJEMJ
Vqx6d4EMFxbSYoSOP0evYabGUUoZjtEJTiblEDrY5aO1loP3KdZjk9aTx88DRMXx
/L06Td162dbAAKW1t5rqG7hO2K2kpiQaK3eQ3elWVd9ngv9lPg0bVjgdAr2QI3tX
rukCNSfpny2M9UmNJ0LDE1rKtcRDUG/KNiHtjAeHwFKgKsEZswxboFex3fggi1PF
3tWkJ87milbWbDgqb8HoFF+iAXPS118=
=FjyZ
-END PGP SIGNATURE End Message ---
Bug#1038944: automake1.11: Keep out of testing
Source: automake1.11 Version: 1:1.11.6-6 Severity: serious Please keep automake1.11 out of testing. It is very old and not needed anymore by packages other than libjpeg6b which people want to keep in unstable.
Processed: tagging 1004184
Processing commands for cont...@bugs.debian.org: > tags 1004184 + trixie Bug #1004184 [src:gcc-11] gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el Added tag(s) trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1038896 is forwarded to https://github.com/eclipse/sumo/issues/13095
Processing commands for cont...@bugs.debian.org: > forwarded 1038896 https://github.com/eclipse/sumo/issues/13095 Bug #1038896 [src:sumo] sumo FTBFS with googletest 1.13.0 Bug #1038897 [src:sumo] sumo: FTBFS with googletest 1.13 (requires C++14) Set Bug forwarded-to-address to 'https://github.com/eclipse/sumo/issues/13095'. Set Bug forwarded-to-address to 'https://github.com/eclipse/sumo/issues/13095'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038896 1038897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038936: icheck FTBFS: test failure
Source: icheck
Version: 0.9.7-6.5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Bastian Germann
https://buildd.debian.org/status/logs.php?pkg=icheck=0.9.7-6.5
...
/usr/bin/make test
make[1]: Entering directory '/<>'
./test.pl t
Processing t/00_empty...
Processing t/01_fundamental...
Processing t/02_struct...
Processing t/03_baseline...
Processing t/04_align...
Differences in compare output
@@ -1,16 +0,0 @@
-ABI mismatch: size of 64 versus 136
-ABI mismatch: alignment of 32 versus 136
- in type defined at t/04_align/source/foo.c:1:
-struct __attribute__((aligned(__alignof__(int foo1
- {
-int a;
-char b;
- };
- versus type defined at t/04_align/source/foo.c:1:
-struct __attribute__((aligned(17), aligned(__alignof__(int foo1
- {
-int a;
-char b;
- };
-
-ABI is not compatible
Test t/04_align failed
4/5 (80%) tests passed
make[1]: *** [Makefile:191: test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: debian/build-stamp] Error 2
Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Package: schleuder Version: 4.0.3-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster' to 'bullseye' to 'bookworm'. It installed fine in 'buster', and upgraded to 'bullseye' successfully, but then the upgrade to 'bookworm' failed. >From the attached log (scroll to the bottom...): Setting up schleuder (4.0.3-7) ... Installing new version of config file /etc/postfix/schleuder_sqlite.cf ... Installing new version of config file /etc/schleuder/schleuder.yml ... rake aborted! NoMethodError: undefined method `preparable=' for #, @right=#> collector.preparable = true ^ /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/database_statements.rb:27:in `to_sql_and_binds' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/database_statements.rb:64:in `select_all' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/connection_adapters/abstract/query_cache.rb:103:in `select_all' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation/calculations.rb:200:in `block in pluck' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation.rb:861:in `skip_query_cache_if_necessary' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/relation/calculations.rb:196:in `pluck' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/schema_migration.rb:46:in `all_versions' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1282:in `load_migrated' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1278:in `migrated' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1314:in `ran?' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `block in runnable' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `reject' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1260:in `runnable' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1302:in `migrate_without_lock' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1253:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1086:in `up' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/migration.rb:1061:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/tasks/database_tasks.rb:237:in `migrate' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:92:in `block (3 levels) in ' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:90:in `each' /usr/share/rubygems-integration/all/gems/activerecord-6.1.7.3/lib/active_record/railties/databases.rake:90:in `block (2 levels) in ' Tasks: TOP => db:migrate (See full trace by running task with --trace) dpkg: error processing package schleuder (--configure): installed schleuder package post-installation script subprocess returned error exit status 1 This does not happen on the bullseye -> bookworm upgrade path. This is unrelated to bug #1036950: "schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)", i.e. it is reproducible even if that bug is fixed in bullseye. cheers, Andreas schleuder_4.0.3-7.log.gz Description: application/gzip
Processed: Re: Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Processing control commands: > severity -1 important Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0 Severity set to 'important' from 'grave' > retitle -1 lightdm 1.32 fails to start X on nvidia binary driver Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0 Changed Bug title to 'lightdm 1.32 fails to start X on nvidia binary driver' from 'lightdm: Lightdm fails to start X after upgrade to 1.32.0'. -- 1038611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
control: severity -1 important control: retitle -1 lightdm 1.32 fails to start X on nvidia binary driver On Thu, Jun 22, 2023 at 01:10:41AM -0300, Adilson dos Santos Dantas wrote: > I tested with the nouveau driver and it worked. > > Maybe there is something between 1.26 and 1.32 that conflicts with nvidia > driver. Yes it's likely. > > And it is also similar to #996503 which affects sddm and it worked too with > nouveau. Ack. As I understand it, X doesn't even start at all so it's likely unrelated to LightDM or sddm actually. Could you try in a terminal to just start X (with the `X` command), with NVidia and with Nouveau drivers, and report back? > > I tried to fix this by removing some module options from > https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 > but it had no effect. > > Maybe forwarding this to nvidia-driver should get some hints about this Yes, feel free to do it and report back any progress. I'm lowering the bug severity as well so it does migrate. Regards, -- Yves-Alexis Perez
Processed: Re: Bug#1038902: docker.io: FTBFS skip btrfs
Processing control commands: > severity -1 wishlist Bug #1038902 [src:docker.io] docker.io: FTBFS skip btrfs Severity set to 'wishlist' from 'serious' > tags -1 patch Bug #1038902 [src:docker.io] docker.io: FTBFS skip btrfs Ignoring request to alter tags of bug #1038902 to the same tags previously set -- 1038902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038902: docker.io: FTBFS skip btrfs
Control: severity -1 wishlist Control: tags -1 patch On Fri, Jun 23, 2023 at 5:33 AM Bastien Roucariès wrote: > > Source: docker.io > Severity: serious > Tags: ftbfs > control: tags -1 + patch > Justification: FTBFS > > Dear Maintainer, > > I had applied the following patch for compiling under btrfs for buster. Could > you refresh and apply for other version The patch doesn't apply to the current version. Meanwhile it doesn't FTBFS on buildd. -- Shengjing Zhu
Bug#1037463: marked as done (macromoleculebuilder: FTBFS with gemmi 0.6.2+ds-1)
Your message dated Fri, 23 Jun 2023 08:35:56 + with message-id and subject line Bug#1037463: fixed in macromoleculebuilder 4.0.0+dfsg-3 has caused the Debian Bug report #1037463, regarding macromoleculebuilder: FTBFS with gemmi 0.6.2+ds-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.) -- 1037463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: macromoleculebuilder Severity: serious Version: 4.0.0+dfsg-2 Hello, macromoleculebuilder FTBFS after recent update of gemmi to 0.6.2+ds-1: /home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp: In function 'void SimTK::CIFOut::reWriteOutCif(const gemmi::Model&, const std::string&, const std::string&, ParameterReader&, const SimTK::CompoundSystem&, bool)': /home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp:113:81: error: cannot bind rvalue reference of type 'gemmi::cif::Document&&' to lvalue of type 'gemmi::cif::Document' 113 | gemmi::Structure myTrajectoryOutputFile = gemmi::make_structure ( doc ); | ^~~ The issue is better fixed upstream, I will forward the report. In the meantime it is OK to remove macromoleculebuilder from testing to not obstruct the upcoming openmm transition. Andrius --- End Message --- --- Begin Message --- Source: macromoleculebuilder Source-Version: 4.0.0+dfsg-3 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of macromoleculebuilder, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated macromoleculebuilder 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, 23 Jun 2023 01:37:57 -0400 Source: macromoleculebuilder Architecture: source Version: 4.0.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1037463 Changes: macromoleculebuilder (4.0.0+dfsg-3) unstable; urgency=medium . * Fix gemmi 0.6.2 support (Closes: #1037463) * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: be6010b5eca7704bded5f58bf4c02a3fb604d44d 2439 macromoleculebuilder_4.0.0+dfsg-3.dsc 3ec554546b6f7771683933a1361395b3d1041ae8 5516 macromoleculebuilder_4.0.0+dfsg-3.debian.tar.xz 876495039493727e2142454ba68ecc2dd224fc29 7561 macromoleculebuilder_4.0.0+dfsg-3_source.buildinfo Checksums-Sha256: 44beb49968252728871d49265ade6936c3d75ba566cc5bd566e18949d76f18af 2439 macromoleculebuilder_4.0.0+dfsg-3.dsc dbfc562c55656860cd3e98291291175bee9b654847aab244b995dedf79dad3a2 5516 macromoleculebuilder_4.0.0+dfsg-3.debian.tar.xz 144ab44a9133692772d10dd5fcd705b64668e2fd0a8cc5afc62c7f05497ac33f 7561 macromoleculebuilder_4.0.0+dfsg-3_source.buildinfo Files: a66e5d9755ca20cd517af307c179947d 2439 science optional macromoleculebuilder_4.0.0+dfsg-3.dsc 76909a88a61f7e5e101aa53cafc0e9e0 5516 science optional macromoleculebuilder_4.0.0+dfsg-3.debian.tar.xz a81aa620f437c24daa987e5463ec5383 7561 science optional macromoleculebuilder_4.0.0+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmSVTpASHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHHwcQAIZNDcKiqLdDrBmMVlXEvWD672w8XHK8 GxBZ5ObzNrBIxdzeC+PYzZyow7aDCErEj3DBEUlA042pkHJ7C/3lmG89EivJCGJG PWoFbdlewXRjaDEK+actbIp4cHCYRUUXPAGoH6p6s0q4P8PSADlvQ9xYi+bhsjKx pv+b2KqTCea7ivjqrY0fL3/uBzVTvaOtJx2ZmivBxz2mDOtQbLWYje8ejJSrYcRI Cj/CUTxasNUfUjmqVMprzNmyaYejRc8wy5ooP69k7oTI/ct9RdzG5QTpthNZ/ik0 udc+lbxoE4oh4WBvDTKq3mmJEJYk04yu+mAnLgUsviWtdL5avA/q3QQFpdiSi1m9 mBYx7AOpbPv9n9OxpqHzShg0CPFwpnUFE84zdJS3bgMky/Q9yjM/q6VY1M8plBtM coCtZqLHWZ/cdVfq+iZFfdrMKdV++ulVn0LHUkzQE5CdjhcW7lQvxgx1zH2HbR5g UmF/n4Zgz7g+X46GgBC9rLFf5w8E5ObMntlXRarLg6WYXiy6sSCN3tAT91VfvelT G7Uipbj46H+L6gX6fVnWoD/rfQ3jigUBThqQ/nyrskeWQ+gipYbXsWkuM3TxDLe5 e1wDIIR8+zz3Nai5fPN6tuZDl/4Yr5tfC0L+wpP/PDekEDGl1MUJ8g++f9Vr3GCX HoiuhwqfFzV7 =zzXK -END PGP SIGNATURE End Message ---
Bug#1038929: icingaweb2-module-graphite: fails to install: ln: failed to create symbolic link '/etc/icingaweb2/enabledModules/graphite': No such file or directory
Package: icingaweb2-module-graphite Version: 1.2.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up icingaweb2-module-graphite (1.2.2-2) ... ln: failed to create symbolic link '/etc/icingaweb2/enabledModules/graphite': No such file or directory dpkg: error processing package icingaweb2-module-graphite (--configure): installed icingaweb2-module-graphite package post-installation script subprocess returned error exit status 1 cheers, Andreas icingaweb2-module-graphite_1.2.2-2.log.gz Description: application/gzip
Processed: Re: schleuder: fails to upgrade from 'buster': fails during apt-get upgrade
Processing control commands: > tag -1 patch Bug #1036950 [schleuder] schleuder: fails to upgrade from 'buster': fails during apt-get upgrade Added tag(s) patch. > retitle -1 schleuder: fails to upgrade from 'buster': insufficient dependency > on ruby-activerecord (>= 2:6) Bug #1036950 [schleuder] schleuder: fails to upgrade from 'buster': fails during apt-get upgrade Changed Bug title to 'schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)' from 'schleuder: fails to upgrade from 'buster': fails during apt-get upgrade'. -- 1036950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036950: schleuder: fails to upgrade from 'buster': fails during apt-get upgrade
Followup-For: Bug #1036950 Control: tag -1 patch Control: retitle -1 schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6) I'm currently testing the attached patch ... Andreas >From e166f1194cb4c6e13a183cffeaf42d7554c5ba56 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Fri, 23 Jun 2023 09:08:31 +0200 Subject: [PATCH] bump the dependency to ruby-activerecord (>= 2:6) --- debian/changelog | 9 + debian/control | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index d385cc3..7f4a0bc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +schleuder (3.6.0-3+deb11u2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Bump the dependency to ruby-activerecord (>= 2:6) since the boolean vs. +integer patch made it incompatible with earlier versions. Needed for +correct upgrade ordering from buster to bullseye. (Closes: #1036950) + + -- Andreas Beckmann Fri, 23 Jun 2023 09:03:33 +0200 + schleuder (3.6.0-3+deb11u1) bullseye; urgency=medium * debian/patches: diff --git a/debian/control b/debian/control index eef5376..e73060b 100644 --- a/debian/control +++ b/debian/control @@ -39,7 +39,7 @@ Depends: adduser, lsb-base, rake, ruby | ruby-interpreter, - ruby-activerecord, + ruby-activerecord (>= 2:6), ruby-charlock-holmes, ruby-gpgme, ruby-mail, -- 2.20.1
Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken
Package: python3-certbot-dns-gandi Version: 1.4.3-1 Severity: serious Dear Maintainer, with the update of certbot and the DNS Gandi plugin, the command line arguments for requesting a certificate have changed. This is not taken into account during upgrade, which left all domains that are normally being renewed via the gandi plugin broken. Above that, no warning email was sent to the admin user about this problem. The letsencrypt.log file contains 2023-06-18 00:49:00,298:ERROR:certbot._internal.renewal:Renewal configuration file /etc/letsencrypt/renewal/SOOME.DOMAIN.conf (cert: SOME.DOMAIN) produced an unexpected error: 'Namespace' object has no attribute 'certbot_plugin_gandi:dns_credentials'. Skipping. 2023-06-18 00:49:00,302:DEBUG:certbot._internal.renewal:Traceback was: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 501, in handle_renewal_request renewal_candidate = _reconstitute(lineage_config, renewal_file) ^^^ File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 103, in _reconstitute _restore_plugin_configs(config, renewalparams) File "/usr/lib/python3/dist-packages/certbot/_internal/renewal.py", line 173, in _restore_plugin_configs if config_item.startswith(plugin_prefix + "_") and not cli.set_by_cli(config_item): ^^^ File "/usr/lib/python3/dist-packages/certbot/_internal/cli/__init__.py", line 489, in set_by_cli if not isinstance(getattr(detector, var), _Default): ^^ AttributeError: 'Namespace' object has no attribute 'certbot_plugin_gandi:dns_credentials' Solution is to run **once** per domain the correct renew line certbot certonly --authenticator dns-gandi --dns-gandi-credentials /etc/letsencrypt/gandi/gandi.ini -d SOME.DOMAIN Best regards Norbert -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-certbot-dns-gandi depends on: ii certbot 2.1.0-4 ii python3 3.11.2-1+b1 ii python3-certbot [python3-certbot-abi-2] 2.1.0-4 ii python3-requests 2.28.1+dfsg-1 python3-certbot-dns-gandi recommends no packages. python3-certbot-dns-gandi suggests no packages. -- no debconf information
