Bug#1038764: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all
Source: crosshurd Version: 1.7.58 Severity: serious Control: close -1 1.7.59 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:crosshurd has been trying to migrate for 31 days [2]. Hence, I am filing this bug, but see my last paragraph. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=crosshurd OpenPGP_signature Description: OpenPGP digital signature
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 01:59 +, solneman33 wrote: > I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and > reinstalled xserver-xorg and xinit. That resolved the issue for me on both > machines. > > I've never reported a bug before, my apologies if this is incorrect > procedure. Well, can you check by reinstalling lightdm 1.32 but making sure you have xserver-xorg? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSnMIACgkQ3rYcyPpX RFs1Hwf9HgLiSwVwW4gMRS2ajXiUXmTRcgNe/jF5libmZllhhKXrMGlq2W/Whf7q 9oIjZ8BYq2x5M3y/VVCH9vYihxFRT6D9Fpg2yw9ojFmJDt0shJuYf2ErJ/2Ymbpy n5JO/1MXtEKbczhmu1ngc23Z9LzOxeuEiZwGJWZoFmhQDlkitD6uOWYByYA4LdA1 W+OsL7tVdE6rUMX9WPJ75mcIgp5+U8mC05Y/pH5+m40/55ZvD1mJotkt4ME6V6f7 fKggPqz8rVZukvXEiTp4oW5CGy/C4zqC5nWiPF8hY8rhZrwpEo9/VFBneEi5Ouze vzSQCUzeQvxMbA1VdXB4EL03t3rt2w== =Fg2s -END PGP SIGNATURE-
Processed: src:crosshurd: fails to migrate to testing for too long: uploader built arch:all
Processing control commands: > close -1 1.7.59 Bug #1038764 [src:crosshurd] src:crosshurd: fails to migrate to testing for too long: uploader built arch:all Marked as fixed in versions crosshurd/1.7.59. Bug #1038764 [src:crosshurd] src:crosshurd: fails to migrate to testing for too long: uploader built arch:all Marked Bug as done -- 1038764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037351: rust-base64 migration dependency adjustment
Hi Ian, On 21-06-2023 02:30, Ian Jackson wrote: Therefore I am tagging this bug trixie-ignore to avoid getting autoremoval warnings etc. As the rust-base64 migration seems to be just waiting (AFAIK at this moment) on rust-ruma-common autopkgtest-ing on ppc64el, I agree that this is OK. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > I tried to use 1.32 again and it only > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > greeter.log and x-0.lo. From the log attached below, one difference is that > 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 > and X does not even start from 1.32. In the log there's definitely a bad sign: [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0 Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, the journal, dmesg...) so we have more information? Also is there something peculiar about your hardware (Nvidia/AMD GPU for example?) or software (specific configuration or something). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== =4Egr -END PGP SIGNATURE-
Bug#1038648: marked as done (Xspice crashes on start)
Your message dated Wed, 21 Jun 2023 06:20:26 + with message-id and subject line Bug#1038648: fixed in xserver-xorg-video-qxl 0.1.6-1 has caused the Debian Bug report #1038648, regarding Xspice crashes on start 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.) -- 1038648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xserver-xspice Version: 0.1.5+git20200331-3 Severity: grave Justification: renders package unusable Since upgrading to bookworm, Xspice always crashes when I try to start it: Xspice --config xspice.1.conf :25 (EE) Caught signal 6 (Aborted). Server aborting Full log: xspice.1.log https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/-/issues/14 describes a similar problem and suggest to add some options in the config file. When I do this, I get a segfault instead: Xspice --config xspice.2.conf :25 (EE) Caught signal 11 (Segmentation fault). Server aborting Full log: xspice.2.log The page above mentions this too and refers to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1967719 That report was closed since they were "confident it was fixed in https://launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/0.1.5+git20200331-3";. However, the same version seems to be in bookworm (unless Debian made its own changes to it), and the problem does occur. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages xserver-xspice depends on: ii libc6 2.36-9 ii libspice-server1 0.15.1-1 ii libxfont2 1:2.0.6-1 ii python33.11.2-1+b1 ii xserver-xorg 1:7.7+23 ii xserver-xorg-core [xorg-video-abi-25] 2:21.1.7-3 xserver-xspice recommends no packages. xserver-xspice suggests no packages. -- no debconf information xspice.1.conf Description: Binary data xspice.1.log Description: Binary data xspice.2.conf Description: Binary data xspice.2.log Description: Binary data --- End Message --- --- Begin Message --- Source: xserver-xorg-video-qxl Source-Version: 0.1.6-1 Done: Timo Aaltonen We believe that the bug you reported is fixed in the latest version of xserver-xorg-video-qxl, 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. Timo Aaltonen (supplier of updated xserver-xorg-video-qxl 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 08:58:45 +0300 Source: xserver-xorg-video-qxl Built-For-Profiles: noudeb Architecture: source Version: 0.1.6-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Closes: 1038648 Changes: xserver-xorg-video-qxl (0.1.6-1) unstable; urgency=medium . * New upstream release. * patches: Drop obsolete patches. (Closes: #1038648) * watch: Updated. * Update signing-key.asc. Checksums-Sha1: 23a067a1d70d146e8366686d405f71e8ebdd216a 2305 xserver-xorg-video-qxl_0.1.6-1.dsc b6a097e30b9edc19291bb5b9e155859f8e5c4453 654220 xserver-xorg-video-qxl_0.1.6.orig.tar.gz 3a670f9b1f71177729dc771f2b495b5344a4f97e 16899 xserver-xorg-video-qxl_0.1.6-1.diff.gz a6c86e43cc294ed531956b96bbf8e90858ef392f 9883 xserver-xorg-video-qxl_0.1.6-1_source.buildinfo Checksums-Sha256: 6696faf82c2324e9e5866d806957c919b45bc820f6f5bd266113361649d4bd34 2305 xserver-xorg-video-qxl_0.1.6-1.dsc d582a4602b29baba1237d2da920825389249e92d060b183e27a5de90547aac54 654220 xserver-xorg-video-qxl_0.1.6.orig.tar.gz 2fcd6ef440c9517664ef3df9831ce4e1802802c8399ed4c192efdb7305c45f8e 16899 xserver-xorg-video-qxl_0.1.6-1.di
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Hi Adrian, Initially, thanks for your help. Em ter., 20 de jun. de 2023 às 18:18, Adrian Bunk escreveu: > > 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&arch=amd64&ver=2.4.86%2Bdfsg-5&stamp=1687282110&raw=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 I packaged this lib after the freeze and I sent it to NEW queue in June, 13. The package was approved in June, 15. However, the upstream dropped the libjodycode2 in June, 16, releasing libjodycode3. The jdupes in stable don't depend on a lib. jdupes 1.24 depends on the libjodycode2 and the new jdupes 1.25 depends on the libjodycode3. I uploaded libjodycode3 to unstable this morning, but jdupes was 1.24, depending on the libjdupes2. Some hours after this, I uploaded jdupes 1.25. > 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. In at the moment, only jdupes depends of the libjodycode"X" on Debian, so I think that libjodycode2 (transitional) must be dropped, right? (jdupes 1.24 was replaced by jdupes 1.25, that depends of the libjodycode3). > 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. What is the right way to make this? Renaming to libjodycode-dev, dropping libjodycode3-dev and sending again to NEW? Should I use Breaks and Replaces to make a reference to libjodycode3-dev? Thanks for your attention. Cheers, Eriberto
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
I was able to reproduce with two of my machines running unstable. xserver-xorg and xinit were removed during the upgrade and I wasn't aware. I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and reinstalled xserver-xorg and xinit. That resolved the issue for me on both machines. I've never reported a bug before, my apologies if this is incorrect procedure. Regards, Sent with [Proton Mail](https://proton.me/) secure email.
Bug#1038762: [src:systemd]: login (gnome) uses wrong keyboard layout
Am 21.06.23 um 03:02 schrieb Michael Biebl: Am 21.06.23 um 02:34 schrieb Lyndon Brown: The latest package update (to unstable) has broken login keyboard- layout support. I'm marking this as critical due to the chaotic potential for locking many users out of their accounts / systems, some of whom unlike myself may have no clue what's wrong and how to get around it, if they can. Afaics, this only affects gdm, which directly queries localed, which no longer reports the keymap state: $ localectl System Locale: LANG=C.UTF-8 VC Keymap: (unset) X11 Layout: (unset) This is a result of https://salsa.debian.org/systemd-team/systemd/-/commit/8d0405b0cfb9c84791da5b8f7288453e23624acf Hm, actually, it seems to be the result of dropping debian/patches/debian/Use-Debian-specific-config-files.patch See the discussion in https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189 As a quick/temporary workaround, you can run ln -s /etc/default/keyboard /etc/vconsole.conf OpenPGP_signature Description: OpenPGP digital signature
Bug#1038762: [src:systemd]: login (gnome) uses wrong keyboard layout
Am 21.06.23 um 02:34 schrieb Lyndon Brown: The latest package update (to unstable) has broken login keyboard- layout support. I'm marking this as critical due to the chaotic potential for locking many users out of their accounts / systems, some of whom unlike myself may have no clue what's wrong and how to get around it, if they can. Afaics, this only affects gdm, which directly queries localed, which no longer reports the keymap state: $ localectl System Locale: LANG=C.UTF-8 VC Keymap: (unset) X11 Layout: (unset) This is a result of https://salsa.debian.org/systemd-team/systemd/-/commit/8d0405b0cfb9c84791da5b8f7288453e23624acf See the discussion in https://salsa.debian.org/systemd-team/systemd/-/merge_requests/189 OpenPGP_signature Description: OpenPGP digital signature
Bug#1038648: Xspice crashes on start
Control: tags patch
I think I found the problem. It seems to be
Fix-a-build-error-with-Xorg-master.patch
To be honest, I don't really understand the patch. According to the
comment, instead of just changing one renamed parameter, it changes
the calling conventions at the cost of an unnecessary "slight
performance drop" in not one but three functions "for consistency"
and goes on to explain why it should work which sounds questionable
to me and apparently doesn't work after all.
So instead doing the simple thing seems to work. I suggest replacing
the patch with this one:
Index: xserver-xorg-video-qxl-0.1.5+git20200331/src/qxl_option_helpers.c
===
--- xserver-xorg-video-qxl-0.1.5+git20200331.orig/src/qxl_option_helpers.c
+++ xserver-xorg-video-qxl-0.1.5+git20200331/src/qxl_option_helpers.c
@@ -34,7 +34,7 @@ int get_bool_option(OptionInfoPtr option
const char* value = getenv(env_name);
if (!value) {
-return options[option_index].value.bool;
+return options[option_index].value.boolean;
}
if (strcmp(value, "0") == 0 ||
strcasecmp(value, "off") == 0 ||
Bug#1038762: [src:systemd]: login (gnome) uses wrong keyboard layout
package: src:systemd version: 253-3 severity: critical The latest package update (to unstable) has broken login keyboard- layout support. I'm marking this as critical due to the chaotic potential for locking many users out of their accounts / systems, some of whom unlike myself may have no clue what's wrong and how to get around it, if they can. I'm from the UK and my locale / keyboard-layout is setup accordingly. Systemd packages were updated from 252.11-1 to 253-3 today on my unstable/sid system. I happened to hit an OOM condition that killed my user session a little while after having installed these updates, kicking me back to the Gnome login screen. I tried to log back in but I couldn't. After many tries, confident I was typing in my password correctly, and rebooting having made no difference, I toggled the feature to see what I was typing and discovered that a certain special character was not matching what I typed. I was able to find a key with which to enter the correct symbol and thus was able to get back in. I presume it's defaulting to US layout for some reason. I checked out the updates that had been installed today and I then tried downgrading all of the systemd packages (listed below) to those from testing (252.11-1). This solves the problem. With 253-3 installed, if I lock my account it seems to be using the correct layout, but if I logout or reboot then it's using the wrong one. With the 252.11-1 downgrade everything uses the correct layout again. Reinstating 253-3 the problem is back, confirming that the problem relates to the upgrade of systemd packages. Apt package log (systemd only): Install: systemd-dev:amd64 (253-3, automatic) Upgrade: udev:amd64 (252.11-1, 253-3), systemd-container:amd64 (252.11- 1, 253-3), libnss-myhostname:amd64 (252.11-1, 253-3), libpam- systemd:amd64 (252.11-1, 253-3), libsystemd0:amd64 (252.11-1, 253-3), libudev-dev:amd64 (252.11-1, 253-3), systemd:amd64 (252.11-1, 253-3), libudev1:amd64 (252.11-1, 253-3), libnss-mymachines:amd64 (252.11-1, 253-3), libsystemd-shared:amd64 (252.11-1, 253-3), systemd-sysv:amd64 (252.11-1, 253-3), libsystemd-dev:amd64 (252.11-1, 253-3) Apt term log (systemd only): Preparing to unpack .../0-libnss-mymachines_253-3_amd64.deb ... Unpacking libnss-mymachines:amd64 (253-3) over (252.11-1) ... Preparing to unpack .../1-systemd-container_253-3_amd64.deb ... Unpacking systemd-container (253-3) over (252.11-1) ... Preparing to unpack .../2-systemd-oomd_253-3_amd64.deb ... Unpacking systemd-oomd (253-3) over (252.11-1) ... Preparing to unpack .../3-libpam-systemd_253-3_amd64.deb ... Unpacking libpam-systemd:amd64 (253-3) over (252.11-1) ... Preparing to unpack .../4-systemd_253-3_amd64.deb ... Unpacking systemd (253-3) over (252.11-1) ... Preparing to unpack .../5-libsystemd-shared_253-3_amd64.deb ... Unpacking libsystemd-shared:amd64 (253-3) over (252.11-1) ... Preparing to unpack .../6-libsystemd0_253-3_amd64.deb ... Unpacking libsystemd0:amd64 (253-3) over (252.11-1) ... Setting up libsystemd0:amd64 (253-3) ... Preparing to unpack .../archives/udev_253-3_amd64.deb ... Unpacking udev (253-3) over (252.11-1) ... Selecting previously unselected package systemd-dev. Preparing to unpack .../systemd-dev_253-3_all.deb ... Unpacking systemd-dev (253-3) ... Setting up systemd-dev (253-3) ... Setting up libsystemd-shared:amd64 (253-3) ... Setting up systemd (253-3) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/system.conf ... Installing new version of config file /etc/systemd/user.conf ... Preparing to unpack .../systemd-sysv_253-3_amd64.deb ... Unpacking systemd-sysv (253-3) over (252.11-1) ... Preparing to unpack .../libsystemd-dev_253-3_amd64.deb ... Unpacking libsystemd-dev:amd64 (253-3) over (252.11-1) ... Preparing to unpack .../libudev-dev_253-3_amd64.deb ... Unpacking libudev-dev:amd64 (253-3) over (252.11-1) ... Preparing to unpack .../libudev1_253-3_amd64.deb ... Unpacking libudev1:amd64 (253-3) over (252.11-1) ... Setting up libudev1:amd64 (253-3) ... Preparing to unpack .../libnss-myhostname_253-3_amd64.deb ... Unpacking libnss-myhostname:amd64 (253-3) over (252.11-1) ... Setting up systemd-sysv (253-3) ... Setting up udev (253-3) ... Setting up libnss-myhostname:amd64 (253-3) ... Setting up libudev-dev:amd64 (253-3) ... Setting up systemd-container (253-3) ... Setting up libpam-systemd:amd64 (253-3) ... Setting up systemd-oomd (253-3) ... Setting up libsystemd-dev:amd64 (253-3) ... Setting up libnss-mymachines:amd64 (253-3) ... Processing triggers for initramfs-tools (0.142) ... update-initramfs: Generating /boot/initrd.img-6.3.0-1-amd64 Processing triggers for libc-bin (2.36-9) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for dbus (1.14.8-1) ... I noticed that the systemd changelog for 253-rc2-1 states "make /etc/default/locale a symlink to /etc/locale.conf". With 253-3 installed I indeed have this symlink (with owner root:ro
Processed: rust-base64 migration dependency adjustment
Processing control commands:
> tags -1 + trixie-ignore
Bug #1037351 {Done: Ian Jackson } [hippotat]
hippotat: ftbfs with rust-base64 0.21
Added tag(s) trixie-ignore.
--
1037351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1037351: rust-base64 migration dependency adjustment
Control: tags -1 + trixie-ignore hippotat 1.1.7 FTBFS with rust-base64 0.21. hippotat 1.1.9 build-depends on rust-base64 0.21. So the plan is for these to migrate together, and ISTM from reading tracker that that is what will happen as soon as the remaining blockers for rust-bsee64 migration are disposed of. In principle hippotat's build-dependencies could have been adjusted to depend on rust-base64 0.13, and then we could have waited for that to enter testing, and then done the update. But thst seems otiose, given that the plan is that trixie should have base64 0.21. Therefore I am tagging this bug trixie-ignore to avoid getting autoremoval warnings etc. I hope I'm not overstepping the mark. PS, with my upstream hat on: It is a shame that the Rust base64 crate has such a cavalier approach to API stability. I am considering my options in this area for hippotat (eg data-encoding or base64ct), but without better tests and test vectors I am reluctant to switch right now. Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#1038760: aflplusplus: gcc-multilib is not available on all architectures
Source: aflplusplus Version: 4.07c-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=aflplusplus The list of architectures where gcc-multilib is currently available is at: https://salsa.debian.org/toolchain-team/gcc-defaults/-/blob/master/debian/control#L46
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Hi Yves-Alexis, I tried to use 1.32 again and it only generates /var/log/lightdm/lightdm.log. It doesn't generate seat0-greeter.log and x-0.lo. From the log attached below, one difference is that 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 and X does not even start from 1.32. Regards, Adilson Em ter., 20 de jun. de 2023 às 18:13, Yves-Alexis Perez escreveu: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > > Package: lightdm > > Followup-For: Bug #1038611 > > > > Can't reproduce, starts up just fine for me. > > > > Could you perhaps include the logs from `/var/log/lightdm/´? > > Hi Adilson, > > I'm running 1.32 just fine since it was uploaded to experimental so I can't > reproduce either. Logs would help indeed, and if you can investigate a bit > more on your side (the info about downgrading helps identifying lightdm but > besides that...) > > Regards, > - -- > Yves-Alexis > -BEGIN PGP SIGNATURE- > > iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX > RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF > zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg > D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA > Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 > 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 > PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== > =SArv > -END PGP SIGNATURE- > -- Adilson dos Santos Dantas http://www.adilson.net.br http://twitter.com/adilsond [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=30230 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) [+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Loading users from org.freedesktop.Accounts [+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1004 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1005 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0
Bug#1038758: pymupdf FTBFS with mupdf 1.22.1
Source: pymupdf
Version: 1.21.1+ds1-1
Severity: serious
Tags: ftbfs trixie sid
https://buildd.debian.org/status/logs.php?pkg=pymupdf&ver=1.21.1%2Bds1-1%2Bb3
...
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g
-fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/mupdf -I/usr/local/include/mupdf -I/usr/include/freetype2
-I/usr/include/python3.11 -c fitz/fitz_wrap.c -o
build/temp.linux-x86_64-cpython-311/fitz/fitz_wrap.o
-Wno-incompatible-pointer-types -Wno-pointer-sign -Wno-sign-compare
fitz/fitz_wrap.c: In function ‘JM_filter_content_stream’:
fitz/fitz_wrap.c:9228:27: error: ‘pdf_filter_options’ has no member named
‘sanitize’
9228 | if (filter->sanitize) {
| ^~
fitz/fitz_wrap.c:9230:39: warning: implicit declaration of function
‘pdf_new_filter_processor’; did you mean ‘pdf_new_buffer_processor’?
[-Wimplicit-function-declaration]
9230 | proc_filter = pdf_new_filter_processor(ctx,
doc, proc_buffer, in_res, *out_res, struct_parents, transform, filter);
| ^~~~
| pdf_new_buffer_processor
fitz/fitz_wrap.c:9230:37: warning: assignment to ‘pdf_processor *’ from ‘int’
makes pointer from integer without a cast [-Wint-conversion]
9230 | proc_filter = pdf_new_filter_processor(ctx,
doc, proc_buffer, in_res, *out_res, struct_parents, transform, filter);
| ^
fitz/fitz_wrap.c:9231:25: error: too few arguments to function
‘pdf_process_contents’
9231 | pdf_process_contents(ctx, proc_filter, doc,
in_res, in_stm, NULL);
| ^~~~
In file included from /usr/include/mupdf/pdf/page.h:26,
from /usr/include/mupdf/pdf.h:38,
from fitz/fitz_wrap.c:3077:
/usr/include/mupdf/pdf/interpret.h:403:6: note: declared here
403 | void pdf_process_contents(fz_context *ctx, pdf_processor *proc,
pdf_document *doc, pdf_obj *obj, pdf_obj *res, fz_cookie *cookie, pdf_obj
**out_res);
| ^~~~
fitz/fitz_wrap.c:9235:25: error: too few arguments to function
‘pdf_process_contents’
9235 | pdf_process_contents(ctx, proc_buffer, doc,
in_res, in_stm, NULL);
| ^~~~
/usr/include/mupdf/pdf/interpret.h:403:6: note: declared here
403 | void pdf_process_contents(fz_context *ctx, pdf_processor *proc,
pdf_document *doc, pdf_obj *obj, pdf_obj *res, fz_cookie *cookie, pdf_obj
**out_res);
| ^~~~
fitz/fitz_wrap.c: In function ‘JM_image_reporter’:
fitz/fitz_wrap.c:9259:11: error: ‘pdf_filter_options’ has no member named
‘text_filter’
9259 | filter.text_filter = NULL;
| ^
fitz/fitz_wrap.c:9260:11: error: ‘pdf_filter_options’ has no member named
‘image_filter’
9260 | filter.image_filter = JM_image_filter;
| ^
fitz/fitz_wrap.c:9261:11: error: ‘pdf_filter_options’ has no member named
‘end_page’
9261 | filter.end_page = NULL;
| ^
fitz/fitz_wrap.c:9264:11: error: ‘pdf_filter_options’ has no member named
‘sanitize’
9264 | filter.sanitize = 1;
| ^
fitz/fitz_wrap.c: In function ‘Document_has_xref_streams’:
fitz/fitz_wrap.c:11958:20: error: ‘pdf_document’ {aka ‘struct pdf_document’}
has no member named ‘has_xref_streams’
11958 | if (pdf->has_xref_streams) Py_RETURN_TRUE;
|^~
fitz/fitz_wrap.c: In function ‘Document_has_old_style_xrefs’:
fitz/fitz_wrap.c:11964:20: error: ‘pdf_document’ {aka ‘struct pdf_document’}
has no member named ‘has_old_style_xrefs’
11964 | if (pdf->has_old_style_xrefs) Py_RETURN_TRUE;
|^~
fitz/fitz_wrap.c: In function ‘Page_clean_contents’:
fitz/fitz_wrap.c:14662:17: warning: initialization of ‘int’ from ‘void *’ makes
integer from pointer without a cast [-Wint-conversion]
14662 | NULL, // opaque
| ^~~~
fitz/fitz_wrap.c:14662:17: note: (near initialization for ‘filter.recurse’)
fitz/fitz_wrap.c:14663:17: warning: initialization of ‘int’ from ‘void *’ makes
integer from pointer without a cast [-Wint-conversion]
14663 | NULL, // image filter
| ^~~~
fitz/fitz_wrap.c:14663:17: note: (near initialization for
‘filter.instance_forms’)
fitz/fitz_wrap.c:14664:17: warning: initialization of ‘int’ from ‘void *’ makes
integer from pointer without a cast [-Wint-conversion]
14664 | NULL, // text filter
| ^~~~
fitz/fitz_wrap.c:14664:17: note: (near initialization for ‘filter.ascii’)
fitz/fitz_wrap.c:14665:17: warning: initi
Bug#1004581: marked as done (ccextractor: FTBFS with ffmpeg 5.0)
Your message dated Tue, 20 Jun 2023 22:05:56 + with message-id and subject line Bug#1004581: fixed in ccextractor 0.94+ds1-2 has caused the Debian Bug report #1004581, regarding ccextractor: FTBFS with ffmpeg 5.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.) -- 1004581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ccextractor Version: 0.93+ds2-1 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 ccextractor FTBFS with ffmpeg 5.0: | gcc-10 -DPACKAGE_NAME=\"CCExtractor\" -DPACKAGE_TARNAME=\"ccextractor\" -DPACKAGE_VERSION=\"0.93\" -DPACKAGE_STRING=\"CCExtractor\ 0.93\" -DPACKAGE_BUGREPORT=\"car...@ccextractor.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"ccextractor\" -DVERSION=\"0.93\" -DHAVE_LIBM=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1 -DHAVE_ARPA_INET_H=1 -DHAVE_FCNTL_H=1 -DHAVE_FLOAT_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_LOCALE_H=1 -DHAVE_MALLOC_H=1 -DHAVE_NETDB_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_STDDEF_H=1 -DHAVE_STDINT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYS_SOCKET_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMEB_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DHAVE__BOOL=1 -DHAVE_PTRDIFF_T=1 -DHAVE_FSEEKO=1 -DHAVE_MALLOC=1 -DHAVE_ALARM=1 -DHAVE_REALLOC=1 -DHAVE_DECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_FLOOR=1 -DHAVE_FTRUNCATE=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_INET_NTOA=1 -DHAVE_MBLEN=1 -DHAVE_MEMCHR=1 -DHAVE_MEMMOVE=1 -DHAVE_MEMSET=1 -DHAVE_MKDIR=1 -DHAVE_MODF=1 -DHAVE_POW=1 -DHAVE_REALPATH=1 -DHAVE_RMDIR=1 -DHAVE_SELECT=1 -DHAVE_SETLOCALE=1 -DHAVE_SOCKET=1 -DHAVE_SQRT=1 -DHAVE_STRCASECMP=1 -DHAVE_STRCHR=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_STRNDUP=1 -DHAVE_STRRCHR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -I. -I../src/lib_ccx/ -I../src/thirdparty/zvbi/ -I../src/thirdparty/lib_hash/ -I../src/thirdparty/protobuf-c/ -I../src/thirdparty -I../src/ -I/usr/include/freetype2 -I/usr/include/gpac -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/tesseract -I/usr/include/leptonica -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -Wno-write-strings -Wno-pointer-sign -D_FILE_OFFSET_BITS=64 -DVERSION_FILE_PRESENT -DGPAC_DISABLE_VTT -DGPAC_DISABLE_OD_DUMP -DGPAC_DISABLE_REMOTERY -DNO_GZIP -O3 -DGPAC_CONFIG_LINUX -DGPAC_64_BITS -DENABLE_HARDSUBX -DENABLE_OCR -DPN3G_NO_CONFIG_H -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o ../src/lib_ccx/ccextractor-hardsubx_imgops.o `test -f '../src/lib_ccx/hardsubx_imgops.c' || echo './'`../src/lib_ccx/hardsubx_imgops.c | ../src/lib_ccx/hardsubx.c: In function ‘hardsubx_process_data’: | ../src/lib_ccx/hardsubx.c:16:2: warning: implicit declaration of function ‘av_register_all’ [-Wimplicit-function-declaration] |16 | av_register_all(); | | ^~~ | ../src/lib_ccx/hardsubx.c:35:34: error: ‘AVStream’ has no member named ‘codec’ |35 | if (ctx->format_ctx->streams[i]->codec->codec_type == AVMEDIA_TYPE_VIDEO) | | ^~ | ../src/lib_ccx/hardsubx.c:46:65: error: ‘AVStream’ has no member named ‘codec’ |46 | ctx->codec_ctx = ctx->format_ctx->streams[ctx->video_stream_id]->codec; | | ^~ | ../src/lib_ccx/hardsubx.c:47:13: warning: assignment discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] |47 | ctx->codec = avcodec_find_decoder(ctx->codec_ctx->codec_id); | | ^ | ../src/lib_ccx/hardsubx.c: In function ‘_init_hardsubx’: | ../src/lib_ccx/hardsubx.c:224:15: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers] | 224 | char *lang = options->ocrlang; | | ^~~ | make[1]: *** [Makefile:1927: ../src/lib_ccx/ccextractor-hardsubx.o] Error 1 | make[1]: *** Waiting for unfinished jobs | ../src/lib_ccx/hardsubx_decoder.c: In function ‘hardsubx_process_frames_tickertext’: | ../src/lib_ccx/hardsubx_decoder.c:385:4: warning: implicit declaration of function ‘avcodec_decode_video2’; did you mean ‘avcodec_decode_subtitle2’? [-Wimplicit-function-declaration] | 385 |avcodec_decode_video2(ctx->codec_ctx, ctx->frame, &got_frame, &ctx->packet); | |^
Bug#1038756: librust-zbus-dev: impossible to install: depends on missing librust-quick-xml-0.26-dev
Package: librust-zbus-dev Version: 3.12.0-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package depends on librust-quick-xml-0.26 which is gone. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSSHhsACgkQLHwxRsGg ASGMhQ//c542ccb2CiKa1t60dmlpXTHy5hQ9QzqKDmFbTlvku4qJfwnnUp1QPyTH iwU5CVvNFWRdexTxDnyqCIOts4lTlMv59eOeWJq2mMT9ZnWOtfv2j9glarISS3fs xhbWYxowDv1nuASYS2WvBN8LGcBi4yIN7mdx7AzitXaLhkHfHy1puoshpZcQjrZc SE4ZK9XBXyeIPwNm9Yr5nBkdIOzajdFcymVSypIyOqqMJ+rg0jDGy+7YtVKcd0Bq m/0Q45gg8JwnzhqJkm1+vlTIpMzYnE/QYrQWJ2tt+NxQB8GjLjH6UHQfMfbJ4njV RrdH26cESFxBOy7X30dxhMR3otiX1tRHfFewfctwHadbvE38eRF9+nH0NRrKXoS2 BvlSRim0UbchiMYPHdO2WZUQpup12+WrGA6pACT4BftqO++wlWIifN/bqVBolpK2 JYUNpOFfuWMiGjm005U97o0Jewij7YDZRVPOzElBl9xcR048XPhyPC4ReUnR3BNY kBeTqLzSSkNCrMh6dZ7rq5jHVaEFoxx7RYBZe/gDyYCsmUE9c4xKUz2CIsXFqEIv vqfTsXKs/5M/RnqDWr4WF4plC/glwluSVpbyr8uzS87rNnleqJW8h1Y2S13UQojJ 81SkxBP6Z9mP38diurUZx61uaahDrz0kKX+ryIOdSiIvwwfJiJ0= =29YD -END PGP SIGNATURE-
Processed: Re: Bug#1038747: gnome-software may overwrite debian-security with invalid entry
Processing control commands: > reassign -1 software-properties-gtk 0.99.30-4 Bug #1038747 [gnome-software] gnome-software may overwrite debian-security with invalid entry Bug reassigned from package 'gnome-software' to 'software-properties-gtk'. No longer marked as found in versions gnome-software/43.4-1. Ignoring request to alter fixed versions of bug #1038747 to the same values previously set Bug #1038747 [software-properties-gtk] gnome-software may overwrite debian-security with invalid entry Marked as found in versions software-properties/0.99.30-4. > retitle -1 software-properties-gtk: may overwrite debian-security with > non-working entry Bug #1038747 [software-properties-gtk] gnome-software may overwrite debian-security with invalid entry Changed Bug title to 'software-properties-gtk: may overwrite debian-security with non-working entry' from 'gnome-software may overwrite debian-security with invalid entry'. > affects -1 + gnome-software Bug #1038747 [software-properties-gtk] software-properties-gtk: may overwrite debian-security with non-working entry Added indication that 1038747 affects gnome-software -- 1038747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038747: gnome-software may overwrite debian-security with invalid entry
Control: reassign -1 software-properties-gtk 0.99.30-4 Control: retitle -1 software-properties-gtk: may overwrite debian-security with non-working entry Control: affects -1 + gnome-software On Tue, 20 Jun 2023 at 15:21:42 -0400, Jesse Rhodes wrote: > I was alerted to this issue by an IRC user and was able to reproduce > it in a clean bookworm vm. > > Steps to reproduce: > 1 - install bookworm from 12.0.0 media, selecting the gnome desktop task > 2 - log in and run Software from the Activites menu > 3 - select Software Repositories from the upper right menu > 4 - select any option in the "Download from:" menu, press close, and > press refresh > > This results in an error dialog from gnome-software, with the relevant line > "E: The repository 'https://deb.debian.org/debian bookworm-security > Release' does not have a Release file." > > The correct entry would be deb.debian.org/debian-security bookworm-security. > > Marked as critical severity because it disables all updates from > debian-security. The "Software & Updates" window opened by gnome-software's "Software Repositories" menu item isn't actually part of gnome-software, so I'm reassigning this to the package that seems to provide it. smcv
Bug#1038752: libjodycode2: A shared library package cannot be a transitional package on a different soversion
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&arch=amd64&ver=2.4.86%2Bdfsg-5&stamp=1687282110&raw=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.
Processed: libjodycode2: A shared library package cannot be a transitional package on a different soversion
Processing control commands: > affects -1 src:phcpack jdupes Bug #1038752 [libjodycode2] libjodycode2: A shared library package cannot be a transitional package on a different soversion Added indication that 1038752 affects src:phcpack and jdupes -- 1038752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038752 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > Package: lightdm > Followup-For: Bug #1038611 > > Can't reproduce, starts up just fine for me. > > Could you perhaps include the logs from `/var/log/lightdm/´? Hi Adilson, I'm running 1.32 just fine since it was uploaded to experimental so I can't reproduce either. Logs would help indeed, and if you can investigate a bit more on your side (the info about downgrading helps identifying lightdm but besides that...) Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== =SArv -END PGP SIGNATURE-
Processed: libgpaste-2-common: missing Breaks+Replaces: libgpaste6 (<< 3.24)
Processing control commands: > affects -1 + gnome-shell-extensions-gpaste Bug #1038751 [libgpaste-2-common] libgpaste-2-common: missing Breaks+Replaces: libgpaste6 (<< 3.24) Added indication that 1038751 affects gnome-shell-extensions-gpaste -- 1038751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038450: patch probably available
On Tue, Jun 20, 2023, julien.pu...@gmail.com wrote: > Hi, > > Le mardi 20 juin 2023 à 15:35 +0200, Adrien Nader a écrit : > > I was looking at the migration for coq on Ubuntu and a build failure > > on armhf is preventing it. > > > > I expect that this issue is fixed by the following commit: > > > > https://github.com/UniMath/UniMath/commit/1716c078b00c18dcabf63f671e414d7ba33cb23c > > > > Split the proof of associators_equiv to make sure it fits inside 32 > > b… > > > > …its (#1687) > > > > This is necessary to create a jscoq addon for UniMath > > (https://github.com/UniMath/UniMath-jsCoq). > > > > I haven't tried the patch yet and wanted to ask first if you're > > interested in restoring support for 32-bit arches. I honestly don't > > know > > if there's a lot of users on these (except maybe for JS). > > If you can confirm that commit solves the issue, I'll add it as a patch > to the Debian packaging and drop my latest change. I'm interested in > having different platforms to detect subtle breakages. > > Notice that I also reported to Coq upstream: > https://github.com/coq/coq/issues/17749 The patch seems to fix the issue. I say "seem" because the build compiled the file that was failing to build but the build is not done yet: emulated armhf isn't fast. :) But since I reprocued the build failure before, I am fairly confident this build will succeed. -- Adrien
Bug#1037511: marked as done (silverjuke: FTBFS with libupnp17)
Your message dated Tue, 20 Jun 2023 19:46:13 +
with message-id
and subject line Bug#1037511: fixed in silverjuke 18.2.1-4.1
has caused the Debian Bug report #1037511,
regarding silverjuke: FTBFS with libupnp17
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.)
--
1037511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: silverjuke
Version: 18.2.1-4
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=silverjuke&arch=amd64&ver=18.2.1-4%2Bb3&stamp=1686650401&raw=0
g++ -DPACKAGE_NAME=\"silverjuke\" -DPACKAGE_TARNAME=\"silverjuke\"
-DPACKAGE_VERSION=\"18.2.1\" -DPACKAGE_STRING=\"silverjuke\ 18.2.1\"
-DPACKAGE_BUGREPORT=\"r...@b44t.com\" -DPACKAGE_URL=\"\"
-DPACKAGE=\"silverjuke\" -DVERSION=\"18.2.1\" -DENABLE_NLS=1 -DHAVE_GETTEXT=1
-DHAVE_DCGETTEXT=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DSTDC_HEADERS=1 -DHAVE_ENDIAN_H=1 -I.
-Isrc -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2
-I/usr/include/wx-3.2 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu
-pthread-DPKGDATADIR=\"/usr/share/silverjuke\"
-DPKGDOCDIR=\"/usr/share/doc/silverjuke\" -Wdate-time -D_FORTIFY_SOURCE=2 -Isrc
-Wall -Wno-unused-but-set-variable -g
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -I/usr/include/wx-3.2
-D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o src/sjmodules/silverjuke-viewsettings.o `test -f
'src/sjmodules/viewsettings.cpp' || echo './'`src/sjmodules/viewsettings.cpp
src/sjmodules/upnp.cpp: In member function ‘bool SjUpnpModule::InitLibupnp()’:
src/sjmodules/upnp.cpp:181:20: error: ‘UpnpInit’ was not declared in this
scope; did you mean ‘UpnpInit2’?
181 | if( (error=UpnpInit(NULL, 0)) != UPNP_E_SUCCESS ) {
|^~~~
|UpnpInit2
make[2]: *** [Makefile:3616: src/sjmodules/silverjuke-upnp.o] Error 1
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: silverjuke
Source-Version: 18.2.1-4.1
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
silverjuke, 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.
Bastian Germann (supplier of updated silverjuke 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: Tue, 20 Jun 2023 20:55:56 +0200
Source: silverjuke
Architecture: source
Version: 18.2.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer
Changed-By: Bastian Germann
Closes: 1037511
Changes:
silverjuke (18.2.1-4.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Use newer UpnpInit2 API (Closes: #1037511)
.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
Checksums-Sha1:
e913cb883c91171c8b2d82f5614d23e458686aea 1862 silverjuke_18.2.1-4.1.dsc
5de62e7eb9468f28cf9594bdf688c73e49e72200 13696
silverjuke_18.2.1-4.1.debian.tar.xz
a47e32a5e070a2ac20d88b5418626741fb39e84e 13102
silverjuke_18.2.1-4.1_source.buildinfo
Checksums-Sha256:
71fab4f7493d86f2618e2d7402e0f03cdab644c4844e013938540ba21a8ca645 1862
silverjuke_18.2.1-4.1.dsc
7590a3d6a0ccf82dd1ee7284ebb98d8511941e9593e0ef2b714c6a4ee504464e 13696
silverjuke_18.2.1-4.1.debian.tar.xz
51a0d13de5373b6ad2670f38ad7a8ce04d2f489c16091b231881b3f57d968da3 13102
silverjuke_18.2.1-4.1_source.buildinfo
Files:
30bd827e86d8043497a43dc65b132377 1862 sound optional silverjuke_18.2.1-4.1.dsc
056d9f1283eefc336b1d9d427d0bf964 13696 sound optional
silverjuke_18.2.1-4.1.debian.tar.xz
de40b38a1ffe29cc37f4a5b55e65260f 13102 soun
Bug#1033703: marked as done (gffread: autopkgtest regression: test dependency not in testing)
Your message dated Tue, 20 Jun 2023 19:34:56 + with message-id and subject line Bug#1033703: fixed in gffread 0.12.7-4 has caused the Debian Bug report #1033703, regarding gffread: autopkgtest regression: test dependency 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.) -- 1033703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gffread Version: 0.12.7-3 Severity: serious Control: tags -1 bookworm User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails in testing since trinityrnaseq-examples was removed on 2022-04-05. Can you please investigate the situation and fix it? The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. [Release Team member hat on] Because we're currently in the hard freeze, I've marked this bug as bookworm-ignore, but targeted fixes are welcome. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gffread Source-Version: 0.12.7-4 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of gffread, 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 1033...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated gffread 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: Tue, 20 Jun 2023 21:03:42 +0200 Source: gffread Architecture: source Version: 0.12.7-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1033703 Changes: gffread (0.12.7-4) unstable; urgency=medium . * Team upload. * d/t/*: work around uninstallable packages. The change involves not testing gffread anymore against trinityrnaseq until it is back to testing, and not testing against R BioC modules until libboost 1.81 transition is finished. (Closes: #1033703) * Update standards version to 4.6.2, no changes needed. Checksums-Sha1: c8073208903ba24c437b5b298ef5081cf0cf6504 2440 gffread_0.12.7-4.dsc 9e913617549c92c3c7b83936d72b22740cbeef93 8828 gffread_0.12.7-4.debian.tar.xz Checksums-Sha256: 4f1abe060a1a4a11ccb32a88e1a4c3d31ed776c9325360ab28c36f31a97a86fc 2440 gffread_0.12.7-4.dsc 5589db070fe18a904eb4323955355a28464753b77ce39adb1dc7773a795e7742 8828 gffread_0.12.7-4.debian.tar.xz Files: 32f45634eddd3620e113353c5990405b 2440 science optional gffread_0.12.7-4.dsc c306b7afcf06a54da9b8123fc161c8c8 8828 science optional gffread_0.12.7-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmSR+x0UHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdrkig//cK3lsx7ib0izPCrlITnUAqEN54Oa VXm8LPpeWdZHWyRgxAM7c/+Lo5eb5SZAajqVko8TGFK4gcXgiHkTT7G9AviKkvad bhEv8pMfFThUjim89DALWYMV9TKO6V1Pd5nzULXo2GsoHxBJdhq+h5Kw10iQIevU FxaoUB14LPrlYE6i4EocEvIPfABBnPQdzqHmgXfySm7lEeTji9i9iRBcTSqCrI6B j66+wba+3sDiMdzYOaCn+eYz5Jxu560s6RWtnI3PJu4zYYg5L6XNHChVtlzHTO7e W9OTUzlKs61Visz34RBY7dKfpJA0w68FWk9LL3zUFLZabJ83dn6RKHN4/zY27s2Z j6zD5wmKcweHOZmiv1BuG368a5bt8GtP6onD68mOnHZAaLNh1+PM+/ZEURQLnY81 WcitKbyMuDEAZEEL6kuaivZzMLKyeqJYMf3PELDceopkxEXyydzNaEDkxwYjL+Py vvGxhAA211his6drDKYLcmodqOd0MW7fNXzgJ+ZVdV/KXmViVMs+r2toqvwG3s1Y m6XJ8O4HupFKtaeJlEC6KINfe+Td+h1SIo0tQcVLGWQNDkYChA6gkdIs4qjCG91P JxagmQnUE/KqLq35mtRA2MIy8WAT4BEfbc5TVae5+GrUvYaY0ORdTnfMgGZgghLi vMsTzCaRWMb7Jhw= =e3DZ -END PGP SIGNATURE End Message ---
Bug#1038747: gnome-software may overwrite debian-security with invalid entry
Package: gnome-software Version: 43.4-1 Severity: critical X-Debbugs-Cc: je...@sney.ca Dear Maintainer, I was alerted to this issue by an IRC user and was able to reproduce it in a clean bookworm vm. Steps to reproduce: 1 - install bookworm from 12.0.0 media, selecting the gnome desktop task 2 - log in and run Software from the Activites menu 3 - select Software Repositories from the upper right menu 4 - select any option in the "Download from:" menu, press close, and press refresh This results in an error dialog from gnome-software, with the relevant line "E: The repository 'https://deb.debian.org/debian bookworm-security Release' does not have a Release file." The correct entry would be deb.debian.org/debian-security bookworm-security. Marked as critical severity because it disables all updates from debian-security. sney -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 gnome-software depends on: ii appstream0.16.1-2 ii apt-config-icons 0.16.1-2 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 pn gnome-software-common ii gsettings-desktop-schemas43.0-1 pn libadwaita-1-0 ii libappstream40.16.1-2 ii libc62.36-9 ii libcairo21.16.0-7 ii libfwupd21.8.12-2 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 ii libgtk-4-1 4.8.3+ds-2 pn libgtk3-perl ii libgudev-1.0-0 237-2 ii libjson-glib-1.0-0 1.6.6-1 pn libmalcontent-0-0 ii libpackagekit-glib2-18 1.2.6-5 ii libpango-1.0-0 1.50.12+ds-1 ii libpolkit-gobject-1-0122-3 ii libsoup-3.0-03.2.2-2 ii libxmlb2 0.3.10-2 ii packagekit 1.2.6-5 pn software-properties-gtk Versions of packages gnome-software recommends: ii fwupd 1.8.12-2 Versions of packages gnome-software suggests: pn apt-config-icons-hidpi pn gnome-software-plugin-flatpak pn gnome-software-plugin-snap
Bug#1037538: gerbera: FTBFS with libupnp17
Hi Adrian, On Sun, 18 Jun 2023 13:20:17 +0300 Adrian Bunk wrote: There is also a later build error, but updating to the latest upstream version 1.12.1 gave me a build: 1. uscan finds the correct version after updating debian/watch to https://github.com/gerbera/gerbera/tags 2. build dependencies need some adjustment 3. debian/gerbera.docs needs some adjustment I haven't done 2. and 3. properly and haven't tested the resulting package. This is the last package that prevents fulfilling the pupnp transition. Would you please go ahead with a team upload? I do not think James is still around. Thanks, Bastian
Bug#1038709: marked as done (sccache - build dependency updates/fixes)
Your message dated Tue, 20 Jun 2023 19:15:00 +
with message-id
and subject line Bug#1038709: fixed in sccache 0.5.3-1
has caused the Debian Bug report #1038709,
regarding sccache - build dependency updates/fixes
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.)
--
1038709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sccache
Version: 0.4.0~~pre8-8
Severity: serious
Tags: patch
Recent updates to the rust crates in Debian mean that sccache needs a few
tweaks.
Firstly sccache has a dependency on librust-bstr+default-dev which seems
to be unused, we would appreciate it if you could drop this as it's
preventing decrufting after rust-bstr switched to collapse_features and
the cruft package seems to be causing spurious reports of puiparts
regressions.
Secondly base64 has been updated to 0.21, fixing sccache to build with
this means dropping the existing base64 patch and picking a new patch
from upstream.
Thirdly, there is an inconsistency between the Cargo dependency on
the semver crate and the Debian dependency. It looks like said
inconsistency was previously covered up by the Package being pulled in
indirectly but this is no longer the case.
A debdiff fixing all these issues is attached, If I get no response I
will probably NMU this in a few days.diff -Nru sccache-0.4.0~~pre8/debian/changelog
sccache-0.4.0~~pre8/debian/changelog
--- sccache-0.4.0~~pre8/debian/changelog2023-03-03 00:45:46.0
+
+++ sccache-0.4.0~~pre8/debian/changelog2023-06-20 08:08:00.0
+
@@ -1,3 +1,15 @@
+sccache (0.4.0~~pre8-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop build-dependency on librust-bstr+default-dev, the crate doesn't
+seem to use it directly and it's blocking decrufting.
+ * Drop patch for base64 0.13, add patch from upstream git for base64
+0.21 and update build-dependency accordingly.
+ * Update build-dependency from librust-semver-0.9+default-dev
+to librust-semver-1.0+default-dev to match dependency in Cargo.toml.
+
+ -- Peter Michael Green Tue, 20 Jun 2023 08:08:00 +
+
sccache (0.4.0~~pre8-8) unstable; urgency=medium
* fix pass cargo arguments also to subcommand install
diff -Nru sccache-0.4.0~~pre8/debian/control sccache-0.4.0~~pre8/debian/control
--- sccache-0.4.0~~pre8/debian/control 2023-02-12 15:34:42.0 +
+++ sccache-0.4.0~~pre8/debian/control 2023-06-20 08:08:00.0 +
@@ -13,10 +13,9 @@
librust-assert-cmd-2+default-dev ,
librust-async-trait-0.1+default-dev (>= 0.1.52),
librust-atty-0.2+default-dev,
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
librust-bincode-1+default-dev,
librust-blake3-1+default-dev,
- librust-bstr+default-dev,
librust-byteorder-1+default-dev,
librust-bytes-1+default-dev,
librust-chrono-0.4+default-dev,
@@ -49,7 +48,7 @@
librust-reqwest-0.11+json-dev,
librust-reqwest-0.11+stream-dev,
librust-retry-2+default-dev,
- librust-semver-0.9+default-dev,
+ librust-semver-1.0+default-dev,
librust-serde-1+default-dev,
librust-serde-derive-1+default-dev,
librust-serde-json-1+default-dev,
diff -Nru sccache-0.4.0~~pre8/debian/patches/0001_base64.patch
sccache-0.4.0~~pre8/debian/patches/0001_base64.patch
--- sccache-0.4.0~~pre8/debian/patches/0001_base64.patch1970-01-01
00:00:00.0 +
+++ sccache-0.4.0~~pre8/debian/patches/0001_base64.patch2023-06-20
08:08:00.0 +
@@ -0,0 +1,133 @@
+This patch contains the parts of the upstream commit described below that
+relate to the update of the base64 crate. Cargo.lock changes are also excluded
+since Debian doesn't use Cargo.lock.
+
+commit 408ae947d7c36f0510695bc991438ce2e180d099
+Author: Xuanwo
+Date: Sun Feb 26 15:09:53 2023 +0800
+
+deps: Bump toml and base64 (#1619)
+
+Signed-off-by: Xuanwo
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 964efa8..67fad6b 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -27,7 +27,7 @@ anyhow = "1.0"
+ ar = "0.9"
+ async-trait = "0.1"
+ atty = "0.2.6"
+-base64 = "0.20"
++base64 = "0.21"
+ bincode = "1"
+ blake3 = "1"
+ byteorder = "1.0"
+diff --git a/src/bin/sccache-dist/main.rs b/src/bin/sccache-dist/main.rs
+index effdb98..5975aeb 100644
+--- a/src/bin/sccache-dist/main.rs
b/src/bin/sccache-dist/main.rs
+@@ -22,6 +22,7 @@ extern crate tar;
+ extern crate void;
+
+ use anyhow::{bail, Context, Error, Result};
++use base64::Engine;
+ use rand::{rngs::OsRng, RngCore};
+ use sccache::config::{
+ scheduler as sched
Bug#1037511: silverjuke: FTBFS with libupnp17
I am uploading a NMU with a trivial patch to fix this. The debdiff is attached
and also available in the git repo.diff -Nru silverjuke-18.2.1/debian/changelog silverjuke-18.2.1/debian/changelog
--- silverjuke-18.2.1/debian/changelog 2022-09-18 20:21:55.0 +0200
+++ silverjuke-18.2.1/debian/changelog 2023-06-20 20:55:56.0 +0200
@@ -1,3 +1,13 @@
+silverjuke (18.2.1-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use newer UpnpInit2 API (Closes: #1037511)
+
+ [ Debian Janitor ]
+ * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
+
+ -- Bastian Germann Tue, 20 Jun 2023 20:55:56 +0200
+
silverjuke (18.2.1-4) unstable; urgency=medium
[ Dr. Tobias Quathamer ]
diff -Nru silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch
silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch
--- silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch
1970-01-01 01:00:00.0 +0100
+++ silverjuke-18.2.1/debian/patches/0003-Use-newer-UpnpInit2-API.patch
2023-06-20 20:54:09.0 +0200
@@ -0,0 +1,21 @@
+From: Bastian Germann
+Date: Tue, 20 Jun 2023 20:52:15 +0200
+Subject: Use newer UpnpInit2 API
+
+---
+ src/sjmodules/upnp.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sjmodules/upnp.cpp b/src/sjmodules/upnp.cpp
+index a41b0e3..fa80f25 100644
+--- a/src/sjmodules/upnp.cpp
b/src/sjmodules/upnp.cpp
+@@ -178,7 +178,7 @@ bool SjUpnpModule::InitLibupnp()
+
+ // init library - NB: we may be in a working thread here (eg.
ImgThread), however, this seems not to be a problem
+ int error;
+- if( (error=UpnpInit(NULL, 0)) != UPNP_E_SUCCESS ) {
++ if( (error=UpnpInit2(NULL, 0)) != UPNP_E_SUCCESS ) {
+ LogUpnpError("Cannot init", error);
+ ExitLibupnp();
+ return false; // error
diff -Nru silverjuke-18.2.1/debian/patches/series
silverjuke-18.2.1/debian/patches/series
--- silverjuke-18.2.1/debian/patches/series 2022-09-18 20:21:40.0
+0200
+++ silverjuke-18.2.1/debian/patches/series 2023-06-20 20:53:15.0
+0200
@@ -1,3 +1,4 @@
0001-Force-X11-for-wxGLCanvas.patch
0002-Replace-URL-of-freedb-with-gnudb.gnudb.org.patch
+0003-Use-newer-UpnpInit2-API.patch
wx3.2-compat.patch
diff -Nru silverjuke-18.2.1/debian/upstream/metadata
silverjuke-18.2.1/debian/upstream/metadata
--- silverjuke-18.2.1/debian/upstream/metadata 1970-01-01 01:00:00.0
+0100
+++ silverjuke-18.2.1/debian/upstream/metadata 2023-06-20 20:37:25.0
+0200
@@ -0,0 +1,5 @@
+---
+Bug-Database: https://github.com/silverjuke/silverjuke/issues
+Bug-Submit: https://github.com/silverjuke/silverjuke/issues/new
+Repository: https://github.com/silverjuke/silverjuke.git
+Repository-Browse: https://github.com/silverjuke/silverjuke
Bug#1038746: build dependency missing in testing
Source: python-cryptography Version: 38.0.4-3 Severity: serious User: debian...@lists.debian.org Usertag: edos-uninstallable Dear maintainer(s), Dose [1] is reporting issues with your packages. Normally your build dependencies shouldn't be removed from testing without removal all reverse build dependencies too, nor should a package be allowed to migrate unless all build dependencies are candidate for migration too. However, somehow we ended up in the current state and your source package is missing some Build-Depends for now. Not being able to build from source in a suite is an RC bug in that suite. Can you please solve the situation by either helping the maintainer of your Build-Depends to enable migration to testing, or by working around the lack of this build dependency? Paul [1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html OpenPGP_signature Description: OpenPGP digital signature
Bug#1034732: fixed in gpac 2.2.1+dfsg1-1
Am Tue, Jun 20, 2023 at 06:06:26PM + schrieb Debian FTP Masters: > Source: gpac > Source-Version: 2.2.1+dfsg1-1 > Done: Reinhard Tartler > Changes: > gpac (2.2.1+dfsg1-1) experimental; urgency=medium > . >* New upstream version, > closes: #1033116, #1034732, #1034187, #1036701, #1034890 A single upload a week after the release doesn't change the fact that gpac isn't supportable unless you massively step up in maintenance (which would also involve taking care of bullseye-security), so #1034732 should not be closed with the upload to unstable. If GPAC magically becomes more stable over the next 1.5 years, we can reconsider. Cheers, Moritz
Bug#1035875: Arbitrary code execution vulnerability in versions < 2.3
Hi, I requested a CVE at cveform.mitre.org so we can start a discussion with upstream on clear grounds, and possibly involve other distros :) From https://github.com/mtrojnar/osslsigncode/compare/2.2...2.3 there are a lot of commits that fixes memory issues, e.g. fix double free in msi_dirent_new() Fix more fuzzer errors etc. so most probably there isn't a single clean patch to apply :/ We might want to just bump to buster and bullseye to 2.3, there's only one rdep AFAICS. Cheers! Sylvain Beucler Debian LTS Team (this week's Front-Desk person)
Processed: src:ruby-prometheus-client-mmap: fails to migrate to testing for too long: FTBFS on ppc64el
Processing control commands:
> close -1 0.19.1-2
Bug #1038743 [src:ruby-prometheus-client-mmap] src:ruby-prometheus-client-mmap:
fails to migrate to testing for too long: FTBFS on ppc64el
Marked as fixed in versions ruby-prometheus-client-mmap/0.19.1-2.
Bug #1038743 [src:ruby-prometheus-client-mmap] src:ruby-prometheus-client-mmap:
fails to migrate to testing for too long: FTBFS on ppc64el
Marked Bug as done
> block -1 by 1034565
Bug #1038743 {Done: Paul Gevers }
[src:ruby-prometheus-client-mmap] src:ruby-prometheus-client-mmap: fails to
migrate to testing for too long: FTBFS on ppc64el
1038743 was not blocked by any bugs.
1038743 was not blocking any bugs.
Added blocking bug(s) of 1038743: 1034565
--
1038743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038743: src:ruby-prometheus-client-mmap: fails to migrate to testing for too long: FTBFS on ppc64el
Source: ruby-prometheus-client-mmap Version: 0.16.2-1 Severity: serious Control: close -1 0.19.1-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1034565 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:ruby-prometheus-client-mmap has been trying to migrate for 64 days [2]. Hence, I am filing this bug. The package fails to build from source on ppc64el, which was reported in bug 1034565. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-prometheus-client-mmap OpenPGP_signature Description: OpenPGP digital signature
Bug#1036356: stress-ng: autopkgtest failures on 32 bit architectures
Version: 0.15.10-1 Hi, On Sat, 20 May 2023 16:50:39 +0100 "Colin King (gmail)" wrote: Thanks for the update, I'm planning to make a stress-ng release that contains this fix before the end of next week to address this and several other issues. At least the last upload doesn't fail its autopkgtest on 32 bit architectures anymore, so let's close this bug. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1036356: marked as done (stress-ng: autopkgtest failures on 32 bit architectures)
Your message dated Tue, 20 Jun 2023 20:32:26 +0200
with message-id <808d5eb3-b319-6722-fbcf-3d3021c73...@debian.org>
and subject line Re: Bug#1036356: stress-ng: autopkgtest failures on 32 bit
architectures
has caused the Debian Bug report #1036356,
regarding stress-ng: autopkgtest failures on 32 bit architectures
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.)
--
1036356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stress-ng
Version: 0.15.07-1
Severity: serious
Tags: patch
Justification: autopkgtest failures
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: bdr...@debian.org
Dear Maintainer,
The autopkg tests on 32 bit architectures fail. In Ubuntu, the attached
patch was applied to fix the autopkgtest:
* Cherry-pick upstream commit "stress-pthread: use 64 bit tid_addr to fix
stack clobbering on 32 bit platforms" and "stress-pthread: fix big endian
tid addr for 32 bit systems" to fix test failures on 32 bit architectures
(LP: #2019079)
Thanks for considering the patch.
--
Benjamin Drung
Debian & Ubuntu Developer
diff -Nru stress-ng-0.15.07/debian/patches/series
stress-ng-0.15.07/debian/patches/series
--- stress-ng-0.15.07/debian/patches/series 1970-01-01 01:00:00.0
+0100
+++ stress-ng-0.15.07/debian/patches/series 2023-05-17 18:45:53.0
+0200
@@ -0,0 +1,2 @@
+stress-pthread_use_64_bit_tid_addr.patch
+stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
diff -Nru
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
---
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
1970-01-01 01:00:00.0 +0100
+++
stress-ng-0.15.07/debian/patches/stress-pthread_fix_big_endian_tid_addr_for_32_bit_systems.patch
2023-05-17 18:45:53.0 +0200
@@ -0,0 +1,46 @@
+From 63c0b414f6ec70dbd0498d59ca34fffbf2642b61 Mon Sep 17 00:00:00 2001
+From: Colin Ian King
+Date: Wed, 10 May 2023 20:39:13 +0100
+Subject: [PATCH] stress-pthread: fix big endian tid addr for 32 bit systems
+
+The PR_GET_TID_ADDR does not have 32 bit compat, so it always returns
+a 64 bit tid addr. For 32 bit systems this needs to be either truncated
+for 32 little endian or shifted down to the bottom 32 bits for big endian
+systems such as big endian HPPA or MIPS32.
+
+Signed-off-by: Colin Ian King
+Origin: upstream,
https://github.com/ColinIanKing/stress-ng/commit/63c0b414f6ec70dbd0498d59ca34fffbf2642b61
+---
+ stress-pthread.c | 13 +++--
+ 1 file changed, 11 insertions(+), 2 deletions(-)
+
+diff --git a/stress-pthread.c b/stress-pthread.c
+index 5c0ee9e4..2190c333 100644
+--- a/stress-pthread.c
b/stress-pthread.c
+@@ -177,14 +177,23 @@ static void OPTIMIZE3 stress_pthread_tid_address(const
stress_args_t *args)
+ uint64_t tid_addr = 0;
+
+ if (LIKELY(prctl(PR_GET_TID_ADDRESS, &tid_addr, 0, 0, 0) == 0)) {
+- if (tid_addr) {
++ unsigned long set_tid_addr;
++
++ if (sizeof(void *) == 4) {
++ set_tid_addr = stress_little_endian() ?
++ (tid_addr & 0x) : (tid_addr >> 32);
++ } else {
++ set_tid_addr = (unsigned long)tid_addr;
++ }
++
++ if (set_tid_addr) {
+ pid_t tid1, tid2;
+
+ /* Nullify */
+ VOID_RET(pid_t, (pid_t)syscall(__NR_set_tid_address,
NULL));
+
+ /* This always succeeds */
+- tid1 = (pid_t)syscall(__NR_set_tid_address, tid_addr);
++ tid1 = (pid_t)syscall(__NR_set_tid_address,
set_tid_addr);
+
+ errno = 0;
+ tid2 = shim_gettid();
diff -Nru
stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch
stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch
--- stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch
1970-01-01 01:00:00.0 +0100
+++ stress-ng-0.15.07/debian/patches/stress-pthread_use_64_bit_tid_addr.patch
2023-05-17 16:07:26.0 +0200
@@ -0,0 +1,37 @@
+From 637662d92865fbf5f3469d7754584f6d810fb902 Mon Sep 17 00:00:00 2001
+From: Colin Ian King
+Date: Wed, 19 Apr 2023 08:46:17 +0100
+Subject: [PATCH] stress-pthread: us
Processed: unarchiving 1018730, reassign 1038731 to lvm2, forcibly merging 1018730 1038731
Processing commands for cont...@bugs.debian.org:
> unarchive 1018730
Bug #1018730 {Done: Bastian Blank } [lvm2] lvm2: Initramfs
does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot
failure
Bug #1034836 {Done: Bastian Blank } [lvm2] initramfs-tools:
After bullseye -> bookworm upgrade boot stuck in the initramfs shell
Unarchived Bug 1018730
Unarchived Bug 1034836
> reassign 1038731 lvm2
Bug #1038731 [cryptsetup-initramfs] initramfs-tools: LVM setup becomes
unbootable when adding to the VG additional encrypted PVs
Bug reassigned from package 'cryptsetup-initramfs' to 'lvm2'.
Ignoring request to alter found versions of bug #1038731 to the same values
previously set
Ignoring request to alter fixed versions of bug #1038731 to the same values
previously set
> forcemerge 1018730 1038731
Bug #1018730 {Done: Bastian Blank } [lvm2] lvm2: Initramfs
does not activate root LVs if VG is incomplete since 2.03.15 or 2.03.16, boot
failure
Bug #1034836 {Done: Bastian Blank } [lvm2] initramfs-tools:
After bullseye -> bookworm upgrade boot stuck in the initramfs shell
Bug #1038731 [lvm2] initramfs-tools: LVM setup becomes unbootable when adding
to the VG additional encrypted PVs
Severity set to 'serious' from 'important'
Marked Bug as done
Added indication that 1038731 affects cryptsetup-initramfs
Marked as found in versions lvm2/2.03.15-1 and lvm2/2.03.16-1.
Added tag(s) patch.
Bug #1034836 {Done: Bastian Blank } [lvm2] initramfs-tools:
After bullseye -> bookworm upgrade boot stuck in the initramfs shell
Merged 1018730 1034836 1038731
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1018730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018730
1034836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034836
1038731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1036094: nss: libnss3 libnss3-dev fails to debuild -us -uc
Hi, On 17-06-2023 20:33, Paul Gevers wrote: It think this problem solved itself, but the reproducible-builds infrastructure [1] claims nss still FTBFS. I'm not understanding what the tail of the log means thought. I understand that this was "fixed" on the reproducible build side of the infrastructure, and nss now builds in unstable on amd64 there. I propose to close this bug. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1034732: marked as done (Keep out of testing)
Your message dated Tue, 20 Jun 2023 18:06:26 + with message-id and subject line Bug#1034732: fixed in gpac 2.2.1+dfsg1-1 has caused the Debian Bug report #1034732, regarding Keep out of 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.) -- 1034732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpac Version: 2.0.0+dfsg1-2+b1 Severity: serious In some discussion between Reinhard, Sebastian and the Security team we've come to the conclusion that gpac isn't suitable to be included in a stable release. The massive influx of security issues makes that untenable (and there's no suitable LTS branch we could use, which e.g. makes ffmpeg manageable). Sebastian has already updated x264 to no longer depend on it, when x264 2:0.164.3095+gitbaee400-3 has reached testing, gpac can be dropped. The only other rdep in ccextractor, which is already out of testing due to a lack of support for ffmpeg 5. Cheers, Moritz --- End Message --- --- Begin Message --- Source: gpac Source-Version: 2.2.1+dfsg1-1 Done: Reinhard Tartler We believe that the bug you reported is fixed in the latest version of gpac, 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 1034...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler (supplier of updated gpac 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: Mon, 19 Jun 2023 17:26:45 -0400 Binary: gpac gpac-dbgsym gpac-modules-base gpac-modules-base-dbgsym libgpac12 libgpac12-dbgsym libgpac-dev Source: gpac Architecture: amd64 source Version: 2.2.1+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Reinhard Tartler Closes: 1033116 1034187 1034732 1034890 1036701 Description: gpac - GPAC Project on Advanced Content - utilities gpac-modules-base - GPAC Project on Advanced Content - modules libgpac12 - GPAC Project on Advanced Content - shared libraries libgpac-dev - GPAC Project on Advanced Content - development files Changes: gpac (2.2.1+dfsg1-1) experimental; urgency=medium . * New upstream version, closes: #1033116, #1034732, #1034187, #1036701, #1034890 * soname bump libgpac11 -> libgpac12 Checksums-Sha1: cc824358adc4d1735882f368b73535f8cf28a58e 2656 gpac_2.2.1+dfsg1-1.dsc 2d5f9416520529a971b177393dec4bc8b7248757 6671912 gpac_2.2.1+dfsg1.orig.tar.xz 60065b475d03083521ca44782ae2b64d91b06bb4 36952 gpac_2.2.1+dfsg1-1.debian.tar.xz 64a7f8eaaf558f935fc7d5b23fbaf3951b93ba91 529848 gpac-dbgsym_2.2.1+dfsg1-1_amd64.deb 731b424a9830f0213f27b2820524e90754259f0c 167400 gpac-modules-base-dbgsym_2.2.1+dfsg1-1_amd64.deb 1252028d4e1c453e505b25d82e7e2f28f00d6eb7 84424 gpac-modules-base_2.2.1+dfsg1-1_amd64.deb a1d0496f8430a33e85121da1bcdefa380f8544bb 16692 gpac_2.2.1+dfsg1-1_amd64.buildinfo bcf0c8f51347d6ebf6f1e136b198f11575afd6a7 967624 gpac_2.2.1+dfsg1-1_amd64.deb 93de586650e3b51b7783c82ad2a8b3fd4cf3bb02 3953732 libgpac-dev_2.2.1+dfsg1-1_amd64.deb e5e87af6075db34f58d10efdf1256b3135abc41b 9686240 libgpac12-dbgsym_2.2.1+dfsg1-1_amd64.deb 0aa6f9997fe86f8213e7bfd88a8f0512dff3f025 3178572 libgpac12_2.2.1+dfsg1-1_amd64.deb Checksums-Sha256: 9f5a7129ef0bcf23089434d6201eb50192fd1192dc24bdccc2fec1634ad84863 2656 gpac_2.2.1+dfsg1-1.dsc 28bebf095d82cc641c126c934c54690def60090f13a3ca6cdb17f671f1fd91f6 6671912 gpac_2.2.1+dfsg1.orig.tar.xz 159a799edc9be37cc828e762ab7376e8ac78f36a52dd99b02b02654a2c39d2be 36952 gpac_2.2.1+dfsg1-1.debian.tar.xz e47b1db665c215932a3192c4a79392fd21b3a11367d3f9286ccbc5ac59251ddf 529848 gpac-dbgsym_2.2.1+dfsg1-1_amd64.deb 6335fdfa17a942e7bcdbd7a06c5635ff39191a80fceb839d95b897d4cb1c81b1 167400 gpac-modules-base-dbgsym_2.2.1+dfsg1-1_amd64.deb 06b838216422cf333a315b71f5742b732ac10177ef5eadfa8324993b74a07746 84424 gpac-modules-base_2.2.1+dfsg1-1_amd64.deb 806ba5997568efa90bbca7986a69c18209c54b0d5469f7cd00cd9a856f877a5d 16692 gpac_2.2.1+dfsg1-1_amd64.buildinfo 80140d7fdb312060994931ea1f3f1bd12b1389f5175ef05771cef5a2840024f5 967624 gpac_2.2.1+dfsg1-1_amd64.deb d7eca8b105fc9407a552
Bug#1033116: marked as done (gpac: CVE-2022-3222 CVE-2023-0866 CVE-2022-4202 CVE-2022-43039 CVE-2023-23143 CVE-2023-23144 CVE-2023-23145 CVE-2022-43040 CVE-2022-43042 CVE-2022-43043 CVE-2022-43044 CVE
Your message dated Tue, 20 Jun 2023 18:06:26 + with message-id and subject line Bug#1033116: fixed in gpac 2.2.1+dfsg1-1 has caused the Debian Bug report #1033116, regarding gpac: CVE-2022-3222 CVE-2023-0866 CVE-2022-4202 CVE-2022-43039 CVE-2023-23143 CVE-2023-23144 CVE-2023-23145 CVE-2022-43040 CVE-2022-43042 CVE-2022-43043 CVE-2022-43044 CVE-2022-43045 CVE-2022-45202 CVE-2022-45283 CVE-2022-45343 CVE-2022-46489 CVE-2022-46490 CVE-2022-47086 CVE-2022-47087 CVE-2022-47088 CVE-2022-47089 CVE-2022-47091 CVE-2022-47092 CVE-2022-47093 CVE-2022-47094 CVE-2022-47095 CVE-2022-47653 CVE-2022-47654 CVE-2022-47656 CVE-2022-47657 CVE-2022-47658 CVE-2022-47659 CVE-2022-47660 CVE-2022-47661 CVE-2022-47662 CVE-2022-47663 CVE-2023-0358 CVE-2023-0760 CVE-2023-0770 CVE-2023-0817 CVE-2023-0818 CVE-2023-0819 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.) -- 1033116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gpac X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for gpac. CVE-2022-3222[0]: | Uncontrolled Recursion in GitHub repository gpac/gpac prior to | 2.1.0-DEV. https://huntr.dev/bounties/b29c69fa-3eac-41e4-9d4f-d861aba18235/ https://github.com/gpac/gpac/commit/4e7736d7ec7bf64026daa611da951993bb42fdaf CVE-2023-0866[2]: | Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to | 2.3.0-DEV. https://huntr.dev/bounties/7d3c5792-d20b-4cb6-9c6d-bb14f3430d7f https://github.com/gpac/gpac/commit/b964fe4226f1424cf676d5822ef898b6b01f5937 CVE-2022-4202[3]: | A vulnerability, which was classified as problematic, was found in | GPAC 2.1-DEV-rev490-g68064e101-master. Affected is the function | lsr_translate_coords of the file laser/lsr_dec.c. The manipulation | leads to integer overflow. It is possible to launch the attack | remotely. The exploit has been disclosed to the public and may be | used. The name of the patch is | b3d821c4ae9ba62b3a194d9dcb5e99f17bd56908. It is recommended to apply a | patch to fix this issue. VDB-214518 is the identifier assigned to this | vulnerability. https://github.com/gpac/gpac/issues/2333 https://github.com/gpac/gpac/commit/b3d821c4ae9ba62b3a194d9dcb5e99f17bd56908 CVE-2022-43039[4]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_isom_meta_restore_items_ref | at /isomedia/meta.c. https://github.com/gpac/gpac/issues/2281 https://github.com/gpac/gpac/commit/62dbd5caad6b89b33535dfa19ef65419f0378303 CVE-2023-23143[5]: | Buffer overflow vulnerability in function avc_parse_slice in file | media_tools/av_parsers.c. GPAC version 2.3-DEV-rev1-g4669ba229-master. https://github.com/gpac/gpac/commit/af6a5e7a96ee01a139cce6c9e4edfc069aad17a6 CVE-2023-23144[6]: | Integer overflow vulnerability in function Q_DecCoordOnUnitSphere file | bifs/unquantize.c in GPAC version 2.2-rev0-gab012bbfb-master. https://github.com/gpac/gpac/commit/3a2458a49b3e6399709d456d7b35e7a6f50cfb86 CVE-2023-23145[7]: | GPAC version 2.2-rev0-gab012bbfb-master was discovered to contain a | memory leak in lsr_read_rare_full function. https://github.com/gpac/gpac/commit/4ade98128cbc41d5115b97a41ca2e59529c8dd5f CVE-2022-43040[8]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a heap | buffer overflow via the function gf_isom_box_dump_start_ex at | /isomedia/box_funcs.c. https://github.com/gpac/gpac/issues/2280 https://github.com/gpac/gpac/commit/f17dae31ebf6ea7af8c512165d9b954c2a6ea46e CVE-2022-43042[9]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a heap | buffer overflow via the function FixSDTPInTRAF at | isomedia/isom_intern.c. https://github.com/gpac/gpac/issues/2278 https://github.com/gpac/gpac/commit/3661da280b3eba75490e75ff20ad440c66e24de9 CVE-2022-43043[10]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function BD_CheckSFTimeOffset at | /bifs/field_decode.c. https://github.com/gpac/gpac/issues/2276 https://github.com/gpac/gpac/commit/6bff06cdb8e9b4e8ed2e789ee9340877759536fd CVE-2022-43044[11]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation via the function gf_isom_get_meta_item_info at | /isomedia/meta.c. https://github.com/gpac/gpac/issues/2282 https://github.com/gpac/gpac/commit/8a0e8e4ab13348cb1ab8e93b950a03d93f158a35 CVE-2022-43045[12]: | GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a | segmentation violation v
Bug#1038710: src:procmail: fails to migrate to testing for too long: unresolved RC bug
Hi, On 20-06-2023 14:47, Santiago Vila wrote: Because the release was close, I raised the bug to "serious" to prevent the migration. Full ack, and thanks for doing that. In either case, I've just (privately) forwarded this (by email) to the author to see if he can help to fix the regression, as the github issue I opened for that is still unanswered. That's a good outcome already from me filing this bug (pinging relevant stakeholders to think about the problem). Thanks again. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1038735: marked as done (python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py)
Your message dated Tue, 20 Jun 2023 17:50:53 + with message-id and subject line Bug#1038735: fixed in mapserver 8.0.1-2 has caused the Debian Bug report #1038735, regarding python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py 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.) -- 1038735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-mapscript Version: 8.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: "Packages must not require the existence of any files in /usr/share/doc/ in order to function." https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. >From the attached log (scroll to the bottom...): Setting up python3 (3.11.2-1+b1) ... [Errno 2] No such file or directory: '/usr/share/doc/python3-mapscript/examples/__init__.py'error running python rtupdate hook python3-mapscript dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 Setting up libgdal32 (3.6.4+dfsg-1) ... dpkg: dependency problems prevent configuration of python3-mapscript: python3-mapscript depends on python3 (<< 3.12); however: Package python3 is not configured yet. In this case it's probably sufficient to exclude the examples from the hook. Cheers, Andreas python3-mapscript_8.0.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: mapserver Source-Version: 8.0.1-2 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of mapserver, 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 mapserver 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: Tue, 20 Jun 2023 19:24:25 +0200 Source: mapserver Architecture: source Version: 8.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Bas Couwenberg Closes: 1038735 Changes: mapserver (8.0.1-2) unstable; urgency=medium . * Don't run dh_python3 on example scripts. (closes: #1038735) * Update symbols for amd64. Checksums-Sha1: 5c79f5720781566320c3494da202053f4f22abe8 3039 mapserver_8.0.1-2.dsc 0ff6a38b8391e277a9e3b2777c179109823db348 57472 mapserver_8.0.1-2.debian.tar.xz 2e550d8d6c14b11e48b6a84226399cfe47de1a92 21411 mapserver_8.0.1-2_amd64.buildinfo Checksums-Sha256: ee20011a508bf91723eaab75f5db6b284b93f277642772f4c4d906c1a0ca 3039 mapserver_8.0.1-2.dsc 1086e444decce22fc57798b308f45b1d8a51f7c90bcbb330f89c200178a0773b 57472 mapserver_8.0.1-2.debian.tar.xz a0b3bde279ea3a28cebdc9e77a264fc5012286f050ae548e74a34a058200c780 21411 mapserver_8.0.1-2_amd64.buildinfo Files: 04898fd7aa6ebbf1d041706fcd89f5fb 3039 devel optional mapserver_8.0.1-2.dsc 385b65e9911bbf12f38708d5bfdd5607 57472 devel optional mapserver_8.0.1-2.debian.tar.xz e39372d43d89d6d47bdc991f0ed1c0a9 21411 devel optional mapserver_8.0.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmSR4zcACgkQZ1DxCuiN SvGscA//RhpkALL0gCkZSOWN5/iSkkN4oz+nxGpcrXv1xcNmLdcCIrNlFzcq5gJG RD+eY+6nw36Bu+JA92uvoC5EapUWbl7rXX2lOoc7gAV9TPz3zasUnNXazZphtUxo ZLzBXmAq0GSpFifOIqxOXL1z8G7YR4L+dCLbPaX4xvYh+Ymfgv3FiFXGa+b49lrz PsfGkrLVrQHvsOxoWy9IIREemMHMA33O/GXswlVD4gtIqLYoMMjOcwrrq93OnE1h UJPWidTh36tk++DIjcc+t0GKP+Mc4V5ZM3x4aainos1AtvUSaKkD0eWkDcTlISUS NEQ6cZrDS/pkoqqEEcUfFxluZfez9+RYa5FP2i6nFyhV90WU3/8LFxE21yxQsmmT 9YL4clk8TwEmhypN1mmhOsPKNuIC+Qa2mKWhBoiOh+gMK4cngKlk7A5za6H3++i7 z4H76AMVkxKaaO/Pg2yTvlajrO14wWqXJhK4qsVs5embP
Bug#1038703: dtkcore: FTBFS: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported
Control: tags -1 + patch
On Tue, Jun 20, 2023 at 12:52:53PM +0300, Dmitry Shachnev wrote:
> [...]
>
> googletest 1.13 was uploaded to unstable recently, and it dropped support
> for C++ versions less than C++14:
>
> https://github.com/google/googletest/releases/tag/v1.13.0
>
> But dtkcore sets CONFIG += c++11 in its .pro files.
Attaching a patch that fixes the build failure.
--
Dmitry Shachnev
Description: don't force old C++ version for tests
Author: Dmitry Shachnev
Forwarded: no
Last-Update: 2023-06-20
--- a/tests/ddesktopentry/ddesktopentry.pro
+++ b/tests/ddesktopentry/ddesktopentry.pro
@@ -3,7 +3,6 @@ QT -= gui
TARGET = tst_ddesktopentrytest
TEMPLATE = app
-CONFIG += c++11
CONFIG -= app_bundle
!isEmpty(DTK_STATIC_LIB){
--- a/tests/dthreadutils/dthreadutils.pro
+++ b/tests/dthreadutils/dthreadutils.pro
@@ -2,7 +2,6 @@ QT += testlib concurrent
QT -= gui
TEMPLATE = app
-CONFIG += c++11
!isEmpty(DTK_STATIC_LIB){
DEFINES += DTK_STATIC_LIB
--- a/tests/dutils/dutils.pro
+++ b/tests/dutils/dutils.pro
@@ -2,7 +2,6 @@ QT += testlib dbus
QT -= gui
TEMPLATE = app
-CONFIG += c++11
!isEmpty(DTK_STATIC_LIB){
DEFINES += DTK_STATIC_LIB
--- a/tests/dvtablehook/dvtablehook.pro
+++ b/tests/dvtablehook/dvtablehook.pro
@@ -2,7 +2,6 @@ QT += testlib
QT -= gui
TEMPLATE = app
-CONFIG += c++11
# TODO: vtabhook release test failed
QMAKE_CXXFLAGS_RELEASE -= -O2
--- a/tests/tests.pro
+++ b/tests/tests.pro
@@ -1,6 +1,6 @@
TEMPLATE = app
QT += core dbus xml testlib concurrent
-CONFIG += thread c++11 link_pkgconfig
+CONFIG += thread link_pkgconfig
CONFIG -= app_bundle
QMAKE_LFLAGS += -Wl,--export-dynamic
signature.asc
Description: PGP signature
Processed: Re: Bug#1038703: dtkcore: FTBFS: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported
Processing control commands: > tags -1 + patch Bug #1038703 [src:dtkcore] dtkcore: FTBFS: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported Added tag(s) patch. -- 1038703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038737: FTBFS on mips64el: Unable to import PyChromecast
Source: photoqt Version: 3.3+ds-1 Severity: serious Tags: ftbfs patch Justification: fails to build from source (but built successfully in the past) Dear Maintainer, The latest photoqt upload failed to build on mips64el, m68k and riscv64. mips64el is a release architecture, this I set severity to serious. The error is: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'pychromecast' CMake Error at CMakeLists.txt:386 (message): ** Unable to import PyChromecast, make sure it is installed. Enabling the CHROMECAST_PIPINSTALL option allows CMake to try to install it locally using pip. -- Configuring incomplete, errors occurred! I have attached a patch which should fix this problem. At least it seems to do so on riscv64. Also, I think with my change you can drop disable-pychromecast patch which is currently commented out anyway. -- Dmitry Shachnev --- photoqt-3.3+ds/debian/rules +++ photoqt-3.3+ds/debian/rules @@ -13,10 +13,7 @@ ifeq ($(DEB_BUILD_ARCH_OS),kfreebsd) MAGICK = -DGRAPHICSMAGICK=OFF -DIMAGEMAGICK=OFF endif -ifeq ($(DEB_BUILD_ARCH_OS),ia64) -CHROMECAST = -DCHROMECAST=OFF -endif -ifeq ($(DEB_BUILD_ARCH_OS),x86_64) +ifneq (,$(filter $(DEB_BUILD_ARCH),ia64 kfreebsd-amd64 kfreebsd-i386 sparc64 sh4 riscv64 m68k hppa mips64el)) CHROMECAST = -DCHROMECAST=OFF endif ifeq ($(DEB_BUILD_ARCH_OS),hppa) signature.asc Description: PGP signature
Processed: Re: Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py
Processing control commands: > tags -1 pending Bug #1038735 [python3-mapscript] python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py Added tag(s) pending. -- 1038735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py
Control: tags -1 pending On 6/20/23 19:05, Andreas Beckmann wrote: This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Setting up python3 (3.11.2-1+b1) ... [Errno 2] No such file or directory: '/usr/share/doc/python3-mapscript/examples/__init__.py'error running python rtupdate hook python3-mapscript dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 Setting up libgdal32 (3.6.4+dfsg-1) ... dpkg: dependency problems prevent configuration of python3-mapscript: python3-mapscript depends on python3 (<< 3.12); however: Package python3 is not configured yet. In this case it's probably sufficient to exclude the examples from the hook. This is done by dh_python3: # Automatically added by dh_python3 if command -v py3compile >/dev/null 2>&1; then py3compile -p python3-mapscript:amd64 /usr/share/doc/python3-mapscript/examples fi if command -v pypy3compile >/dev/null 2>&1; then pypy3compile -p python3-mapscript:amd64 /usr/share/doc/python3-mapscript/examples || true fi dh_python3 is used to rewrite the shebang, we'll just ignore the example-unusual-interpreter lintian issue then. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1038735: python3-mapscript: python hook /usr/share/doc content (Policy 12.3): /usr/share/doc/python3-mapscript/examples/__init__.py
Package: python3-mapscript Version: 8.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: "Packages must not require the existence of any files in /usr/share/doc/ in order to function." https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. >From the attached log (scroll to the bottom...): Setting up python3 (3.11.2-1+b1) ... [Errno 2] No such file or directory: '/usr/share/doc/python3-mapscript/examples/__init__.py'error running python rtupdate hook python3-mapscript dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 Setting up libgdal32 (3.6.4+dfsg-1) ... dpkg: dependency problems prevent configuration of python3-mapscript: python3-mapscript depends on python3 (<< 3.12); however: Package python3 is not configured yet. In this case it's probably sufficient to exclude the examples from the hook. Cheers, Andreas python3-mapscript_8.0.1-1.log.gz Description: application/gzip
Bug#1038732: ara-server: fails to install: AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Package: ara-server Version: 1.5.8-1.1 Severity: serious Tags: sid trixie 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 ara-server (1.5.8-1.1) ... [ara] No setting found for SECRET_KEY. Generating a random key... Traceback (most recent call last): File "/usr/bin/ara-manage", line 10, in sys.exit(main()) ^^ File "/usr/lib/python3/dist-packages/ara/server/__main__.py", line 43, in main if not os.path.exists(settings.ARA_SETTINGS): ^ File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 82, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 69, in _setup self._wrapped = Settings(settings_module) ^ File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 170, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) ^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1204, in _gcd_import File "", line 1176, in _find_and_load File "", line 1147, in _find_and_load_unlocked File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/ara/server/settings.py", line 216, in LOCAL_TIME_ZONE = tzlocal.get_localzone().zone AttributeError: 'zoneinfo.ZoneInfo' object has no attribute 'zone' [ESC][0mdpkg: error processing package ara-server (--configure): installed ara-server package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Errors were encountered while processing: ara-server cheers, Andreas ara-server_1.5.8-1.1.log.gz Description: application/gzip
Bug#1038690: marked as done (liborcus: autopkgtest failures)
Your message dated Tue, 20 Jun 2023 16:05:41 + with message-id and subject line Bug#1038690: fixed in liborcus 0.18.1-2 has caused the Debian Bug report #1038690, regarding liborcus: autopkgtest failures 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.) -- 1038690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liborcus Version: 0.18.1-1 Severity: serious tags: patch Hello, in experimental the autopkgtest is still referring the old library. Please update it or add some code to automatically detect this kind of mismatches. Note: this is not really failing right now, until the old library is decrufted by ftpmasters. --- liborcus-0.18.1/debian/tests/control2023-01-13 18:37:59.0 + +++ liborcus-0.18.1/debian/tests/control2023-06-20 06:45:15.0 + @@ -5,8 +5,8 @@ Tests: unit Depends: - liborcus-0.17-0, - liborcus-spreadsheet-model-0.17-0, + liborcus-0.18-0, + liborcus-spreadsheet-model-0.18-0, python3-orcus, @builddeps@, Restrictions: build-needed, rw-build-tree OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: liborcus Source-Version: 0.18.1-2 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of liborcus, 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. Rene Engelhard (supplier of updated liborcus 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: Tue, 20 Jun 2023 17:39:51 +0200 Source: liborcus Architecture: source Version: 0.18.1-2 Distribution: experimental Urgency: medium Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Closes: 1038690 Changes: liborcus (0.18.1-2) experimental; urgency=medium . * Update tests/control: 0.17->0.18 (closes: #1038690) Checksums-Sha1: b7c1d01b27dbc47e4ca1dbc5d595cb8b9d803c9b 2975 liborcus_0.18.1-2.dsc 4c07529d7e9a39e0939191daefb20fca216d0f2e 8976 liborcus_0.18.1-2.debian.tar.xz 26b7e7c96694e3352d98296af5df229b62c22ed1 8035 liborcus_0.18.1-2_source.buildinfo Checksums-Sha256: 032f04762627b25f15b0d3481ad95b84c14a6ca51a6a73011f544e930ac26a65 2975 liborcus_0.18.1-2.dsc 3c1561d482ea9f7f8d16d5d663a0f751129445490e6305d7000bc06eeb0faa47 8976 liborcus_0.18.1-2.debian.tar.xz f56f87dcce734d7691a3cefe0026fe6abe4fcc1acd09f53161270bec9fb875ee 8035 liborcus_0.18.1-2_source.buildinfo Files: 4a28d8f343b02437f2057a2e9b10a1ab 2975 libs optional liborcus_0.18.1-2.dsc b9dff07734322807a1c6735f13e65c96 8976 libs optional liborcus_0.18.1-2.debian.tar.xz 4d0659a2f7870e5bc17901b06b86ed28 8035 libs optional liborcus_0.18.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmSRyMEQHHJlbmVAZGVi aWFuLm9yZwAKCRAKoEVx0D4+cKEqD/4wlmvxOa6doOsbkXN0H+sSpQ3omAF0a+Ap rkMGmIWLsNjSgnmcO8F4WIVo28NZz/hjQFa2Cm+/YCPb4NbWdZKdAuZWZrpzlDa3 GCc0HPdq77ody3JtPCk5n7QNpkLf4aS9jKIMcaGSbft31rpTXROX4cHqzXS+nOwD bmg40aQ8CGzO5hJRtQoyXRmqjmTxIFgaxeGaqGMh4LRnDHcNM6UFxGwKsQfOQYDd 3xnIhv8Xu2NzzXQzT4AJqqTFRQz/Kle2jqGyD1L4AJ7cXktW8qVIWbQ/jl1PvQYU r2umCjIWNbS5aFtf/xuo5NFuiV5ks0Rg7Olq/AdcH7V4S1Vlr+ytysVttqTxXvCj MlPCnmH5mrQVahdQY0qwhMwtWgGOBjAwojHoYLWqlDq5FUZMUNTS4n2KdcMYOCVp tQgt2rOXc5p+DAt4J5nrPfpXUgWB+xweaX77SLLhQJpFEzhtSiL37U/TpJODG7As oF0+EvmoFEAJxKpzyvNzBm+N5oGguKe8CodsQ5e1U+MLdeoZRWjai5gP1hRffh0/ KlFa35CFpgJmRiBOTiKEPKH6KLJku8j8/woNBtn0fz/X5xEra6hxFe/TEuYly+dm NYtpLaTdpgbTJIvcsrcjs6rhAeqKJUKrlHnn5hKx6Rs4drp83G2UGAUAkxrRXhzi gYQVK8uHXg== =JNCv -END PGP SIGNATURE End Message ---
Bug#1036677: marked as done (astra-toolbox: FTBFS with CUDA 12: ../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template)
Your message dated Tue, 20 Jun 2023 15:49:21 + with message-id and subject line Bug#1036677: fixed in astra-toolbox 2.1.0-3 has caused the Debian Bug report #1036677, regarding astra-toolbox: FTBFS with CUDA 12: ../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template 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.) -- 1036677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: astra-toolbox Version: 2.1.0-2 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 ... /usr/bin/nvcc -Wno-deprecated-gpu-targets -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_75,code=sm_75 -gencode=arch=compute_80,code=sm_80 -gencode=arch=compute_86,code=sm_86 -gencode=arch=compute_86,code=compute_86 -I../build/linux/../../include -DASTRA_CUDA -c ../build/linux/../../cuda/2d/par_bp.cu -Xcompiler -fPIC -DPIC -o cuda/2d/.libs/par_bp.o ../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template 1 error detected in the compilation of "../build/linux/../../cuda/2d/par_bp.cu". make[2]: *** [Makefile:373: cuda/2d/par_bp.lo] Error 2 Andreas --- End Message --- --- Begin Message --- Source: astra-toolbox Source-Version: 2.1.0-3 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of astra-toolbox, 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 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated astra-toolbox 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: Tue, 20 Jun 2023 17:36:46 +0200 Source: astra-toolbox Architecture: source Version: 2.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Bastian Germann Closes: 1036677 Changes: astra-toolbox (2.1.0-3) unstable; urgency=medium . * Team upload * Fix build with CUDA 12 (Closes: #1036677) Checksums-Sha1: 2f0f117d49c29fe75f3d484d66386e972e38cba8 2191 astra-toolbox_2.1.0-3.dsc b38e5779d6e364ca5daaf43e0997c86653737191 6136 astra-toolbox_2.1.0-3.debian.tar.xz c36d4042ccd93a0922bb8ebdcef9286bc49352c8 18257 astra-toolbox_2.1.0-3_source.buildinfo Checksums-Sha256: 6bf422c191f7d00d26e2077f74897f851bcab87c165fa79710329beeb64652aa 2191 astra-toolbox_2.1.0-3.dsc aa85415f07e58b25b4bcabedf8fc79770c743765623f359c2a151469a1496de5 6136 astra-toolbox_2.1.0-3.debian.tar.xz 3cbbc40089b0ecaeecc8a91550f6e570e7f7cc86f6b503572d74921ec3fa3a60 18257 astra-toolbox_2.1.0-3_source.buildinfo Files: c5b9fb2d8f96a9cadcc36cff06e378c7 2191 contrib/python optional astra-toolbox_2.1.0-3.dsc f944278e2c990c7ffbf3be6f9622b1c0 6136 contrib/python optional astra-toolbox_2.1.0-3.debian.tar.xz f2ef77ddb459e793dfe9359bf317b427 18257 contrib/python optional astra-toolbox_2.1.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmSRyFQQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFKGaC/4+CCAzqZEJLwRznxtjO67uuEpK8jwsVw1I ggUfbRBDK9sLqD8A2xspJq+4RD8za2oYf0rvSWUH1JFWUCfu3LL3leCkTolL9p7e 0tyKRv4p/ZmwYBZOaU819hruQa7BdrSadqvBCWSCMTETGsLBMv4LLtReahWpzrAa 21wqQ/4AyHi3iTknpSyoZcVA2fKBBSz2mjWXr/ZzXiBGvT88VJa2Ws3BEQlGTQmq j13OIvFztgu1cEJw0qAo33oYJ+j+laujfXYOqw7A78ibOrYNGDUiUxa9eqOpxmIH CqRQJzxmV+PuuV/HS+gIDjNIUGhTcgEteRho74psKR/XHRyOpKIaU62yBuPYkFVa EYRlPxVi/VQVDrqIB+du/4W5uBaIqXEWAUdUNwGYAYPJyESnEv7sjsNDKk+NKIO2 hlXEj1+iqqXyNVr8FKBeCSh0V8AlcyqptZiOy1ORgID4JIT5fsTNah5O8SKgQqOo ZIEXcngQv7R0PnqbgpJu8UuN/yazCmI= =AamG -END PGP SIGNATURE End Message ---
Bug#1038608: marked as done (rust-coretuils: FTBFS: error: no matching package named `remove_dir_all` found)
Your message dated Tue, 20 Jun 2023 14:55:46 + with message-id and subject line Bug#1038608: fixed in rust-coreutils 0.0.17-4 has caused the Debian Bug report #1038608, regarding rust-coretuils: FTBFS: error: no matching package named `remove_dir_all` found 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.) -- 1038608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-coreutils Version: 0.0.17-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=rust-coreutils&arch=amd64&ver=0.0.17-3&stamp=1686775495&raw=0 cargo build --features "arch base32 base64 basename basenc cat chcon chgrp chmod chown chroot cksum comm cp csplit cut date dd df dir dircolors dirname du echo env expand expr factor false fmt fold groups hashsum head hostid hostname id install join kill link ln logname ls mkdir mkfifo mknod mktemp more mv nice nl nohup nproc numfmt od paste pathchk pinky pr printenv printf ptx pwd readlink realpath relpath rm rmdir runcon seq shred shuf sleep sort split stat stdbuf sum sync tac tail tee test timeout touch tr true truncate tsort tty uname unexpand uniq unlink uptime users vdir wc who whoami yes" --release --no-default-features error: no matching package named `remove_dir_all` found location searched: registry `crates-io` required by package `uu_rm v0.0.17 (/<>/src/uu/rm)` make[2]: *** [GNUmakefile:283: build-coreutils] Error 101 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: rust-coreutils Source-Version: 0.0.17-4 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-coreutils, 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. Peter Michael Green (supplier of updated rust-coreutils 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: Tue, 20 Jun 2023 10:54:23 + Source: rust-coreutils Architecture: source Version: 0.0.17-4 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1038608 Changes: rust-coreutils (0.0.17-4) unstable; urgency=medium . * Team upload. * Add missing build-dependency on librust-remove-dir-all-0.7+default-dev (Closes: #1038608) Checksums-Sha1: 1f0b8f7f27e1724571163146306c8ec12129fe3d 4796 rust-coreutils_0.0.17-4.dsc b351ebc667810642c0bc1637c27d47bd850653cb 13844 rust-coreutils_0.0.17-4.debian.tar.xz d909ab044d51c794ef8c6fc8ca5db75e05964368 23533 rust-coreutils_0.0.17-4_source.buildinfo Checksums-Sha256: b6cd85f7d7000f48fcbde0a05e120a3f623bb7f874367ccb29597dee7ab0e8fd 4796 rust-coreutils_0.0.17-4.dsc 07bbb00c343b7de268701f981d0456d04e3e185e5c42b6421af8c8f844cae5e6 13844 rust-coreutils_0.0.17-4.debian.tar.xz f92d62993cf9be3d16e4f936cdebc8b51c45eb4d0ba4c456906d30d9c708f2a1 23533 rust-coreutils_0.0.17-4_source.buildinfo Files: e35253c16b8efa4b18ed183e397b433b 4796 utils optional rust-coreutils_0.0.17-4.dsc b21588afa40a921fa0a301c7874dbe4e 13844 utils optional rust-coreutils_0.0.17-4.debian.tar.xz b108b44d39ad7626d5b7191001a5d66a 23533 utils optional rust-coreutils_0.0.17-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmSRtrsUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xv9Aw/+J0k1x2IHPs2KFzJ+xZnPz+/riq+C JQzYakkbkbt7ImQ5W8Z9Y6Om6hMUI5ni4Uu8IkVppKHjCSypIKln3n4NEYbAy8/b GA3D9AtJa1QtNP9dWEs5i/ix3yXz+kbASfD4rOEHDM4W7k9re6HTs3ki7tg8wzqk Fp0uroominNwLVyR9csS+81RX99oPzskS7JZfJw2gOr0JVVH/4n6zTSBm/tdhQUY QYwZXFt6//+DxG49N/2c1XSUaQNq9vcV1zrncQqtVYrJEun6u8ZR5kSyQ5bnmb+O CxG504OquW6gCkGLPagwF8MatUP/IGZBxIpo5eI/Kni/DsFY0pxT0hsiY97BChY7 9b+y67gDhsM/ZUkXErZmoN9B8qDHEwgYZDu1VyDCaipRsnLzIcP/2BmSVZvuJgBm mtHpVjQD8dPV5PxSKf8co+n4OAm549i00hHQePfEFHUSbOl9sKjE3bjakOKyS3s/ VwpiJ0Jh/IpXSzT6IHzNfhHsPQs9J8Yw1vhmGUbu2RHTLc+HXNmOWYx+Vu6nTbQ2 ON4ku0tqszIRuXA6Lf4Fxw9TI2ElHH2OcmJPj2GrHKHLw/esj3bsMczwtAna1Za5 FRCeZZo
Bug#1038450: patch probably available
Hi, Le mardi 20 juin 2023 à 15:35 +0200, Adrien Nader a écrit : > I was looking at the migration for coq on Ubuntu and a build failure > on armhf is preventing it. > > I expect that this issue is fixed by the following commit: > > https://github.com/UniMath/UniMath/commit/1716c078b00c18dcabf63f671e414d7ba33cb23c > > Split the proof of associators_equiv to make sure it fits inside 32 > b… > > …its (#1687) > > This is necessary to create a jscoq addon for UniMath > (https://github.com/UniMath/UniMath-jsCoq). > > I haven't tried the patch yet and wanted to ask first if you're > interested in restoring support for 32-bit arches. I honestly don't > know > if there's a lot of users on these (except maybe for JS). If you can confirm that commit solves the issue, I'll add it as a patch to the Debian packaging and drop my latest change. I'm interested in having different platforms to detect subtle breakages. Notice that I also reported to Coq upstream: https://github.com/coq/coq/issues/17749 Thanks! J
Bug#1038723: tiktoken FTBFS: error: failed to select a version for the requirement `pyo3 = "^0.17.3"`
Source: tiktoken
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=tiktoken&ver=0.4.0-1
...
running build_ext
running build_rust
cargo rustc --lib --message-format=json-render-diagnostics --manifest-path
Cargo.toml --release -v --features pyo3/extension-module -- --crate-type cdylib
error: failed to select a version for the requirement `pyo3 = "^0.17.3"`
candidate versions found which didn't match: 0.19.0
location searched: directory source `/usr/share/cargo/registry` (which is
replacing registry `crates-io`)
required by package `tiktoken v0.4.0 (/<>)`
perhaps a crate was updated and forgotten to be re-vendored?
error: `cargo rustc --lib --message-format=json-render-diagnostics
--manifest-path Cargo.toml --release -v --features pyo3/extension-module --
--crate-type cdylib` failed with code 101
ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:388: build: plugin pyproject failed with: exit code=1:
python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir
/<>/.pybuild/cpython3_3.11_tiktoken
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit
code 13
make: *** [debian/rules:9: binary-arch] Error 25
Processed: 1037472 is forwarded
Processing commands for cont...@bugs.debian.org: > forwarded 1037472 https://github.com/samuelflores/molmodel/issues/10 Bug #1037472 [src:molmodel] molmodel: FTBFS with gemmi 0.6.2+ds-1 Set Bug forwarded-to-address to 'https://github.com/samuelflores/molmodel/issues/10'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038450: patch probably available
Hi, I was looking at the migration for coq on Ubuntu and a build failure on armhf is preventing it. I expect that this issue is fixed by the following commit: https://github.com/UniMath/UniMath/commit/1716c078b00c18dcabf63f671e414d7ba33cb23c Split the proof of associators_equiv to make sure it fits inside 32 b… …its (#1687) This is necessary to create a jscoq addon for UniMath (https://github.com/UniMath/UniMath-jsCoq). I haven't tried the patch yet and wanted to ask first if you're interested in restoring support for 32-bit arches. I honestly don't know if there's a lot of users on these (except maybe for JS). -- Adrien
Bug#1035720: marked as done (fails to compress with Django 4.x)
Your message dated Tue, 20 Jun 2023 13:23:03 +
with message-id
and subject line Bug#1035720: fixed in python-django-compressor 4.0-2
has caused the Debian Bug report #1035720,
regarding fails to compress with Django 4.x
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.)
--
1035720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-dashboard
Version: 3:23.1.0-1
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...):
...
2713 static files copied to '/var/lib/openstack-dashboard/static'.
/usr/lib/python3/dist-packages/django/conf/__init__.py:267:
RemovedInDjango50Warning: The USE_L10N setting is deprecated. Starting with
Django 5.0, localized formatting of data will always be enabled. For example
Django will display numbers and dates using the format of the current locale.
warnings.warn(USE_L10N_DEPRECATED_MSG, RemovedInDjango50Warning)
/usr/lib/python3/dist-packages/debreach/__init__.py:6: DeprecationWarning:
distutils Version classes are deprecated. Use packaging.version instead.
version_info = version.StrictVersion(__version__).version
Traceback (most recent call last):
File "/usr/share/openstack-dashboard/manage.py", line 23, in
execute_from_command_line(sys.argv)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 442, in execute_from_command_line
utility.execute()
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 436, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
^^
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 275, in fetch_command
klass = load_command_class(app_name, subcommand)
File "/usr/lib/python3/dist-packages/django/core/management/__init__.py",
line 49, in load_command_class
return module.Command()
File "/usr/lib/python3/dist-packages/django/core/management/base.py", line
284, in __init__
raise TypeError("requires_system_checks must be a list or tuple.")
TypeError: requires_system_checks must be a list or tuple.
dpkg: error processing package openstack-dashboard (--configure):
installed openstack-dashboard package post-installation script subprocess
returned error exit status 1
Processing triggers for ca-certificates (20230311) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
openstack-dashboard
cheers,
Andreas
openstack-dashboard_3:23.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-django-compressor
Source-Version: 4.0-2
Done: Thomas Goirand
We believe that the bug you reported is fixed in the latest version of
python-django-compressor, 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 1035...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-django-compressor
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: Tue, 20 Jun 2023 14:42:49 +0200
Source: python-django-compressor
Architecture: source
Version: 4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack
Changed-By: Thomas Goirand
Closes: 1035720
Changes:
python-django-compressor (4.0-2) unstable; urgency=medium
.
* Fix Command.requires_system_checks to make it work under Django 4.x.
(Closes: #1035720).
Checksums-Sha1:
2d19adf79361e06e378fb2a143dcef5108ae97a6 2581
python-django-compressor_4.0-2.dsc
a9bca598d12165bee6d703e6c7760575befcafd3 4828
python-django-compressor_4.0-2.debian.tar.xz
acca42b5bc6a36518447421e26a4b8854d704807 8
Bug#1038690: marked as pending in liborcus
Control: tag -1 pending Hello, Bug #1038690 in liborcus 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/libreoffice-team/liborcus/-/commit/ac02b408cdc74e04b936b83013778ddc26d1c2a1 Update tests/control: 0.17->0.18 (closes: #1038690) (this message was generated automatically) -- Greetings https://bugs.debian.org/1038690
Processed: Bug#1038690 marked as pending in liborcus
Processing control commands: > tag -1 pending Bug #1038690 [src:liborcus] liborcus: autopkgtest failures Added tag(s) pending. -- 1038690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037924: marked as done (systemd-dev: missing Breaks+Replaces: udev (<< 253-2~))
Your message dated Tue, 20 Jun 2023 12:53:26 + with message-id and subject line Bug#1037924: fixed in systemd 253-3 has caused the Debian Bug report #1037924, regarding systemd-dev: missing Breaks+Replaces: udev (<< 253-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.) -- 1037924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-dev Version: 253-2 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 .../systemd-dev_253-2_all.deb ... Unpacking systemd-dev (253-2) ... dpkg: error processing archive /var/cache/apt/archives/systemd-dev_253-2_all.deb (--unpack): trying to overwrite '/usr/share/pkgconfig/udev.pc', which is also in package udev 252.11-1 Errors were encountered while processing: /var/cache/apt/archives/systemd-dev_253-2_all.deb cheers, Andreas udev=252.11-1_systemd-dev=253-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: systemd Source-Version: 253-3 Done: Luca Boccassi We believe that the bug you reported is fixed in the latest version of systemd, 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. Luca Boccassi (supplier of updated systemd 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: Tue, 20 Jun 2023 11:45:22 +0100 Source: systemd Architecture: source Version: 253-3 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Closes: 917549 945922 1037924 Changes: systemd (253-3) unstable; urgency=medium . * systemd-dev: add missing breaks/replaces with udev. (Closes: #1037924) * Run the systemd-binfmt trigger unconditionally. * Upload to unstable. . systemd (253-2) experimental; urgency=medium . * Add systemd-dev package for pkg-config files. Move systemd.pc and udev.pc to systemd-dev, so that packages can build-depend on a small package instead of the whole set of binaries. (Closes: #945922, #917549) . systemd (253-1) experimental; urgency=medium . * New upstream version 253. For a full list of changes, see: https://github.com/systemd/systemd/releases/tag/v253 * d/watch: switch back to stable repository. * Update symbols file . systemd (253~rc3-1) experimental; urgency=medium . * New upstream version 253~rc3 * Refresh patches . systemd (253~rc2-1) experimental; urgency=medium . * New upstream version 253~rc2 * systemd: make /etc/default/locale a symlink to /etc/locale.conf. Let's match upstream's filename and keep a backward-compatibility symlink for older tools. The content of the files match anyway. * Update timedated autopkgtest. We no longer support /etc/timezone, as /etc/localtime is always available * Drop patches merged upstream * Drop Don-t-enable-audit-by-default.patch. We can disable the socket now * Drop Use-Debian-specific-config-files.patch, no longer needed * systemd-boot-system-token was renamed to systemd-boot-random-seed * Add new libsystemd symbols * Update Lintian override for new so bump * Remove systemd-localed drop-in, no longer needed. The change was merged upstream * Drop udev-drop-SystemCallArchitectures-native-from-systemd-ude.patch and use a drop-in * Drop Re-enable-journal-forwarding-to-syslog.patch and use a drop-in * Drop TuxOnIce out-of-tree patch. The SYSTEMD_BYPASS_HIBERNATION_MEMORY_CHECK environment variable can be used to skip the check, so it is no longer necessary to maintain a patch. * Drop autopkgtest denylist patches. No longer needed, the tests are working now *
Bug#1038450: marked as done (coq-unimath FTBFS on 32bit)
Your message dated Tue, 20 Jun 2023 12:49:18 +
with message-id
and subject line Bug#1038450: fixed in coq-unimath 20230420-3
has caused the Debian Bug report #1038450,
regarding coq-unimath FTBFS on 32bit
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.)
--
1038450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coq-unimath
Version: 20230420-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=coq-unimath&ver=20230420-2
...
COQC
UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.v
File
"./UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.v",
line 333, characters 2-10:
Error: Anomaly "Uncaught exception Invalid_argument("String.create")."
Please report at http://coq.inria.fr/bugs/.
make[4]: *** [build/CoqMakefile.make:844:
UniMath/CategoryTheory/Monoidal/AlternativeDefinitions/EquivalenceWhiskeredNonCurriedMonoidalCategories.vo]
Error 129
--- End Message ---
--- Begin Message ---
Source: coq-unimath
Source-Version: 20230420-3
Done: Julien Puydt
We believe that the bug you reported is fixed in the latest version of
coq-unimath, 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.
Julien Puydt (supplier of updated coq-unimath 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: Tue, 20 Jun 2023 14:21:21 +0200
Source: coq-unimath
Architecture: source
Version: 20230420-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers
Changed-By: Julien Puydt
Closes: 1038450
Changes:
coq-unimath (20230420-3) unstable; urgency=medium
.
* Drop 32-bits architecture (too big for the VM there) (Closes: #1038450).
Checksums-Sha1:
ccf71ccc8635b2a0964d54107d35a5335084e24f 2171 coq-unimath_20230420-3.dsc
d3f546c7057d4ac77cb2950c64489c15c8753e4c 1940
coq-unimath_20230420-3.debian.tar.xz
def7d03f2961952e2da656d67537091d74b4eb29 7435
coq-unimath_20230420-3_source.buildinfo
Checksums-Sha256:
c743acf4677b861a08d8c65c66c0cf3351de1befaef3930c06521076ce01dfb1 2171
coq-unimath_20230420-3.dsc
7e9ebc987108dcf253384241fe5d02a5d11bcb928e3fa7a39c3a6811ea245db0 1940
coq-unimath_20230420-3.debian.tar.xz
2c22959a39d952ce8b8a2e52f33a0e907f4c1cdeff944746657de4120ec984f8 7435
coq-unimath_20230420-3_source.buildinfo
Files:
b51ac104cdc363505e9752a8ba98300c 2171 ocaml optional coq-unimath_20230420-3.dsc
c7cb9c7231ecbeb3bcf98bafb9cb1d6a 1940 ocaml optional
coq-unimath_20230420-3.debian.tar.xz
27844cded54229870b68a62f586b0f0f 7435 ocaml optional
coq-unimath_20230420-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmSRmewSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRa10P/3XtbMiFkb7ZxbwUL8IKwYAf4Gu8U/ag
yhkYN7oKAYIfJbq5I7LU9KJDdadx4faWYC5aVJvAIJMen/VVWWP+nFUBFsqPbRHx
FsbKrXup0M88UD8elrGg7JSCqRKHvO4sjBAkeQyemu4I3KTxglo28oeqrxHH9bWI
d0sc7zRv1cORgVnVplRAFRaEBo2isg+efOwIL5FN79dwGUuMULBil6KrPi6xKZts
Mg6CNm0B9sKtLE0z+ZPDGq96nyhN5AV548rMkKvkJkTli+xgDu4DWxqeoD+JBzjG
EZap/uC8KT6jf7dq9XYfcOq7Pr4iAray6X2Lauy5q+uDuI6oU0YzlLNpbfygGx8l
vyVITkvKq6Y+/1g8PftVo6xTvFXioNmWAd1HMCSzevmZQ2SE4PKPzmfYgp8Z/Zbm
6FA7iRuD6yNaKHoklnt3JTI0YRyUlVKR7c99PUPlk6tYSl7oKgMY8ENDZeRQdVHb
qnt6jNYWmtxBJWPp/RmfNHaPePJTMPNDi831+w2aOuc4ZqF8ORDqeG1MrBE1Dk/7
b+Y87CpdoS67vV/vxnN1ECDHQSAxMmDoAjXnqs2x8/ZAXM91d1mZEQZUn9efhlax
mIrcgOtH0hSRws/duE5R/UOmEjXEQCoxtnwJ8dEr+MhXg7bWkMT2SyGgLUja3Vii
krRzLaUKoVSf
=oIc9
-END PGP SIGNATURE End Message ---
Bug#1038710: src:procmail: fails to migrate to testing for too long: unresolved RC bug
El 20/6/23 a las 12:43, Paul Gevers escribió: procmail is a key package, so it will not be autoremoved. This bug is merely to make the out-of-sync-ness visible. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Hello. The issue with procmail is that I packaged the long awaited 3.24 version from the author, but it had a regression (Bug #1028356). Because the release was close, I raised the bug to "serious" to prevent the migration. Downgrading the bug and letting the package migrate to testing would probably fix this bug you have just filed, but somehow I feel that the current version in trixie is still "better" than the version in sid, so I don't see how that would improve anything from the point of view of the end user. In either case, I've just (privately) forwarded this (by email) to the author to see if he can help to fix the regression, as the github issue I opened for that is still unanswered. Thanks.
Bug#1035720: marked as pending in python-django-compressor
Control: tag -1 pending Hello, Bug #1035720 in python-django-compressor 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/openstack-team/python/python-django-compressor/-/commit/7dbd0fe49afddff258731122c5d4dd9ce87945b1 * Fix Command.requires_system_checks to make it work under Django 4.x. (Closes: #1035720). (this message was generated automatically) -- Greetings https://bugs.debian.org/1035720
Processed: Bug#1035720 marked as pending in python-django-compressor
Processing control commands: > tag -1 pending Bug #1035720 [python3-django-compressor] fails to compress with Django 4.x Added tag(s) pending. -- 1035720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037924: marked as pending in systemd
Control: tag -1 pending Hello, Bug #1037924 in systemd 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/systemd-team/systemd/-/commit/26c9d15ece64b9dc8f55a40aa6d40fa6d2f35ec8 systemd-dev: add missing breaks/replaces with udev Closes: #1037924 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037924
Processed: Bug#1037924 marked as pending in systemd
Processing control commands: > tag -1 pending Bug #1037924 [systemd-dev] systemd-dev: missing Breaks+Replaces: udev (<< 253-2~) Added tag(s) pending. -- 1037924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038717: rust-erbium FTBFS: dh_installexamples: error: Cannot find (any matches for) "erbium.conf.example"
Source: rust-erbium Version: 1.0.4-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=rust-erbium&ver=1.0.4-2 ... dh_installexamples -a -O--buildsystem=cargo dh_installexamples: error: Cannot find (any matches for) "erbium.conf.example" (tried in ., debian/tmp) make: *** [debian/rules:3: binary-arch] Error 25
Processed: Reassign to python3-django-compressor
Processing commands for cont...@bugs.debian.org: > reassign 1035720 python3-django-compressor Bug #1035720 [openstack-dashboard] openstack-dashboard: fails to install: TypeError: requires_system_checks must be a list or tuple. Bug reassigned from package 'openstack-dashboard' to 'python3-django-compressor'. No longer marked as found in versions horizon/3:23.1.0-1. Ignoring request to alter fixed versions of bug #1035720 to the same values previously set > retitle 1035720 fails to compress with Django 4.x Bug #1035720 [python3-django-compressor] openstack-dashboard: fails to install: TypeError: requires_system_checks must be a list or tuple. Changed Bug title to 'fails to compress with Django 4.x' from 'openstack-dashboard: fails to install: TypeError: requires_system_checks must be a list or tuple.'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1035720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1004184: gcc-11: generate bad code for matplotlib with -O1/-O2 on mips64el
Hi YunQiang, mips porters, On 28-04-2023 15:51, YunQiang Su wrote: Paul Gevers 于2023年4月27日周四 04:26写道： On Fri, 24 Feb 2023 23:10:29 + James Addison wrote: Hi Frederic: I'm linking a forwarded GCC GNU bug report that I _think_ is the upstream report matching this bug. I found it from a related GitHub issue[1] for matplotlib. The GCC bug reporter has done some work to create a minimal reproducer case. Could you check whether the issue reported there is the same one as here? (I will do eventually, but am not familiar with C and do not have mips hardware available so it may take some time) [1] - https://github.com/matplotlib/matplotlib/issues/21789 We're you ever made aware of this bug in gcc-11 and gcc-12? Maybe a bit of your help is appropriate. Sorry about that I forget this bug... I will dig it. Did anything happen here? Lagging progress (reporting) on bugs like this isn't great for architectures in the the architecture qualification. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: src:chaos-marmosets: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 0.1.2-1
Bug #1038713 [src:chaos-marmosets] src:chaos-marmosets: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions chaos-marmosets/0.1.2-1.
Bug #1038713 [src:chaos-marmosets] src:chaos-marmosets: fails to migrate to
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1037962
Bug #1038713 {Done: Paul Gevers } [src:chaos-marmosets]
src:chaos-marmosets: fails to migrate to testing for too long: autopkgtest
regression
1038713 was not blocked by any bugs.
1038713 was not blocking any bugs.
Added blocking bug(s) of 1038713: 1037962
--
1038713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038713: src:chaos-marmosets: fails to migrate to testing for too long: autopkgtest regression
Source: chaos-marmosets Version: 0.1.1-1 Severity: serious Control: close -1 0.1.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1037962 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:chaos-marmosets has been trying to migrate for 64 days [2]. Hence, I am filing this bug. The autopkgtest of this package regressed as reported in bug 1037962. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=chaos-marmosets OpenPGP_signature Description: OpenPGP digital signature
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
Package: lightdm Followup-For: Bug #1038611 Can't reproduce, starts up just fine for me. Could you perhaps include the logs from `/var/log/lightdm/´? -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'proposed-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.8-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.2-2 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.11-1 ii libpam0g 1.5.2-6 ii libxcb11.15-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-3 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+23 Versions of packages lightdm suggests: ii accountsservice 22.08.8-6 ii upower 0.99.20-2 ii xserver-xephyr 2:21.1.7-3 -- debconf information: * shared/default-x-display-manager: gdm3 lightdm/daemon_name: /usr/sbin/lightdm
Processed: src:tomopy: fails to migrate to testing for too long: unresolved RC bugs
Processing control commands:
> close -1 1.10.4+ds1-9
Bug #1038712 [src:tomopy] src:tomopy: fails to migrate to testing for too long:
unresolved RC bugs
Marked as fixed in versions tomopy/1.10.4+ds1-9.
Bug #1038712 [src:tomopy] src:tomopy: fails to migrate to testing for too long:
unresolved RC bugs
Marked Bug as done
> block -1 by 1032045 1036684
Bug #1038712 {Done: Paul Gevers } [src:tomopy] src:tomopy:
fails to migrate to testing for too long: unresolved RC bugs
1038712 was not blocked by any bugs.
1038712 was not blocking any bugs.
Added blocking bug(s) of 1038712: 1032558, 1032045, and 1036684
--
1038712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038712: src:tomopy: fails to migrate to testing for too long: unresolved RC bugs
Source: tomopy Version: 1.10.4+ds1-7 Severity: serious Control: close -1 1.10.4+ds1-9 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1032045 1036684 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:tomopy has been trying to migrate for 119 days [2]. Hence, I am filing this bug. There are two outstanding RC bugs that block the migration. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=tomopy OpenPGP_signature Description: OpenPGP digital signature
Processed: src:beaker: fails to migrate to testing for too long: FTBFS
Processing control commands:
> close -1 1.12.1-1
Bug #1038711 [src:beaker] src:beaker: fails to migrate to testing for too long:
FTBFS
The source 'beaker' and version '1.12.1-1' do not appear to match any binary
packages
Marked as fixed in versions beaker/1.12.1-1.
Bug #1038711 [src:beaker] src:beaker: fails to migrate to testing for too long:
FTBFS
Marked Bug as done
> block -1 by 1037035
Bug #1038711 {Done: Paul Gevers } [src:beaker] src:beaker:
fails to migrate to testing for too long: FTBFS
1038711 was not blocked by any bugs.
1038711 was not blocking any bugs.
Added blocking bug(s) of 1038711: 1037035
--
1038711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038711: src:beaker: fails to migrate to testing for too long: FTBFS
Source: beaker Version: 1.11.0-3 Severity: serious Control: close -1 1.12.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1037035 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:beaker has been trying to migrate for 122 days [2]. Hence, I am filing this bug. The package fails to build from source, which was reported in bug 1037035. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=beaker OpenPGP_signature Description: OpenPGP digital signature
Bug#1031765: ganeti-testsuite: autopkgtest failure with procps 2:4.0.3-1
Hi, On Mon, 27 Feb 2023 13:37:38 +0200 Apollon Oikonomopoulos wrote: We could probably question the usefulness of negative UID/PID/SIDs here, on the other hand this had been working for at least 15 years before breaking in a minor release. I'm reassigning this bug to procps for further discussion. I'm under the impression that ganeti and ganeti-testsuite are fixed for this issue. We also just had the bookworm release. If this change isn't going to be reverted, now might be a good moment to expose the change to a bigger audience (by either closing the bug, or lowering it's severity). Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: src:procmail: fails to migrate to testing for too long: unresolved RC bug
Processing control commands: > close -1 3.24-1 Bug #1038710 [src:procmail] src:procmail: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions procmail/3.24-1. Bug #1038710 [src:procmail] src:procmail: fails to migrate to testing for too long: unresolved RC bug Marked Bug as done -- 1038710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038710: src:procmail: fails to migrate to testing for too long: unresolved RC bug
Source: procmail Version: 3.22-27 Severity: serious Control: close -1 3.24-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:procmail has been trying to migrate for 165 days [2]. I know that's mostly because of the freeze, and thanks for not having the RC bug slip into bookworm. But now after the release, it's time to look at it again. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. procmail is a key package, so it will not be autoremoved. This bug is merely to make the out-of-sync-ness visible. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=procmail OpenPGP_signature Description: OpenPGP digital signature
Bug#1038696: marked as done (libjpegli62: missing Conflicts/Replaces/Provides: libjpeg62)
Your message dated Tue, 20 Jun 2023 10:35:49 + with message-id and subject line Bug#1038696: fixed in jpeg-xl 0.9.0~git20230612.38b629f-4 has caused the Debian Bug report #1038696, regarding libjpegli62: missing Conflicts/Replaces/Provides: libjpeg62 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.) -- 1038696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjpegli62 Version: 0.9.0~git20230612.38b629f-3 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 .../libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb ... Unpacking libjpegli62:amd64 (0.9.0~git20230612.38b629f-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.62', which is also in package libjpeg62:amd64 1:6b2-3.1 Errors were encountered while processing: /var/cache/apt/archives/libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb There is still a libjpeg62 package in sid. Please check libjpeg62-turbo for the C/R/P against libjpeg62 and model yours similarily. cheers, Andreas libjpeg62=1:6b2-3.1_libjpegli62=0.9.0~git20230612.38b629f-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: jpeg-xl Source-Version: 0.9.0~git20230612.38b629f-4 Done: Mathieu Malaterre We believe that the bug you reported is fixed in the latest version of jpeg-xl, 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. Mathieu Malaterre (supplier of updated jpeg-xl 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: Tue, 20 Jun 2023 12:15:35 +0200 Source: jpeg-xl Architecture: source Version: 0.9.0~git20230612.38b629f-4 Distribution: experimental Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Mathieu Malaterre Closes: 1038696 Changes: jpeg-xl (0.9.0~git20230612.38b629f-4) experimental; urgency=medium . * d/control: Make sure to use latest testdata * d/control: Conflicts with libjpeg62. Closes: #1038696 Checksums-Sha1: a30cfa55166cd6745de011190c9a2112925633c6 3504 jpeg-xl_0.9.0~git20230612.38b629f-4.dsc 071b9132772a679315858257784f72d059dcd94f 13924 jpeg-xl_0.9.0~git20230612.38b629f-4.debian.tar.xz c22d26d74e32c03ed7b673a0ef6b5166a7d84271 12058 jpeg-xl_0.9.0~git20230612.38b629f-4_source.buildinfo Checksums-Sha256: 3c4167157a1d7a58fc3456002cadac4cb62cacf31e1e1031c994f99c8809e8f1 3504 jpeg-xl_0.9.0~git20230612.38b629f-4.dsc 3252fe9453ad22219c6a5b6ef7daa779ec492414891ec9a4fa8632d36468f81c 13924 jpeg-xl_0.9.0~git20230612.38b629f-4.debian.tar.xz fa7d2b45645e4ffefa62b9c6bd83282f01de13c5d5cb35553bd0c1dae53af81d 12058 jpeg-xl_0.9.0~git20230612.38b629f-4_source.buildinfo Files: fb3de7b099eb548f46adfeb59ded2818 3504 graphics optional jpeg-xl_0.9.0~git20230612.38b629f-4.dsc e499fb6d8136d70d177033c7f3faa182 13924 graphics optional jpeg-xl_0.9.0~git20230612.38b629f-4.debian.tar.xz d54121309992248e77d91aab7792f17e 12058 graphics optional jpeg-xl_0.9.0~git20230612.38b629f-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmSRfJIRHG1hbGF0QGRl Ymlhbi5vcmcACgkQAXHhgorgk0WrAA/+M8gPMzL/ZaOMYMOG7Jb4TrAYxSrWzZba EFoJI2UENF9Cd8Tw+RK77lZwq9yNRoVQLVG7JlTU3TdRSPs1wufGr1ePuUHMYR5p UP5+qPH0R2YpKexuoIrcnh+9p/6R+14xOpR+4EdM9X3iSxom/Zswv9DJwf++YOVM RrU4NX2e/jGOB3bEZBOYenHzZvOaoLoQQWKJhLFmqh3Wh+/mQUbjLbWLlNwG5A0P P8DdAVb+/hY8CLSjfi9Jg5OoJtyyaSbEyo/6QNxnxvzSdRLw0K1gmThex6iawfYb d+Dd7PCM6m9zryE2AEZpTYuOYYeKaWfsOhZ9ixEflU78ZZJ9m9lwXdKwjEdTrwwt 9XMLNjPFpEAugrnZLXgxjdo2eHRssKHu/WyoyPGOxx2B111H/0XfCEUrYSdtnZOQ 84+CYZ3Kl8
Bug#1038709: sccache - build dependency updates/fixes
Package: sccache
Version: 0.4.0~~pre8-8
Severity: serious
Tags: patch
Recent updates to the rust crates in Debian mean that sccache needs a few
tweaks.
Firstly sccache has a dependency on librust-bstr+default-dev which seems
to be unused, we would appreciate it if you could drop this as it's
preventing decrufting after rust-bstr switched to collapse_features and
the cruft package seems to be causing spurious reports of puiparts
regressions.
Secondly base64 has been updated to 0.21, fixing sccache to build with
this means dropping the existing base64 patch and picking a new patch
from upstream.
Thirdly, there is an inconsistency between the Cargo dependency on
the semver crate and the Debian dependency. It looks like said
inconsistency was previously covered up by the Package being pulled in
indirectly but this is no longer the case.
A debdiff fixing all these issues is attached, If I get no response I
will probably NMU this in a few days.diff -Nru sccache-0.4.0~~pre8/debian/changelog
sccache-0.4.0~~pre8/debian/changelog
--- sccache-0.4.0~~pre8/debian/changelog2023-03-03 00:45:46.0
+
+++ sccache-0.4.0~~pre8/debian/changelog2023-06-20 08:08:00.0
+
@@ -1,3 +1,15 @@
+sccache (0.4.0~~pre8-8.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop build-dependency on librust-bstr+default-dev, the crate doesn't
+seem to use it directly and it's blocking decrufting.
+ * Drop patch for base64 0.13, add patch from upstream git for base64
+0.21 and update build-dependency accordingly.
+ * Update build-dependency from librust-semver-0.9+default-dev
+to librust-semver-1.0+default-dev to match dependency in Cargo.toml.
+
+ -- Peter Michael Green Tue, 20 Jun 2023 08:08:00 +
+
sccache (0.4.0~~pre8-8) unstable; urgency=medium
* fix pass cargo arguments also to subcommand install
diff -Nru sccache-0.4.0~~pre8/debian/control sccache-0.4.0~~pre8/debian/control
--- sccache-0.4.0~~pre8/debian/control 2023-02-12 15:34:42.0 +
+++ sccache-0.4.0~~pre8/debian/control 2023-06-20 08:08:00.0 +
@@ -13,10 +13,9 @@
librust-assert-cmd-2+default-dev ,
librust-async-trait-0.1+default-dev (>= 0.1.52),
librust-atty-0.2+default-dev,
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
librust-bincode-1+default-dev,
librust-blake3-1+default-dev,
- librust-bstr+default-dev,
librust-byteorder-1+default-dev,
librust-bytes-1+default-dev,
librust-chrono-0.4+default-dev,
@@ -49,7 +48,7 @@
librust-reqwest-0.11+json-dev,
librust-reqwest-0.11+stream-dev,
librust-retry-2+default-dev,
- librust-semver-0.9+default-dev,
+ librust-semver-1.0+default-dev,
librust-serde-1+default-dev,
librust-serde-derive-1+default-dev,
librust-serde-json-1+default-dev,
diff -Nru sccache-0.4.0~~pre8/debian/patches/0001_base64.patch
sccache-0.4.0~~pre8/debian/patches/0001_base64.patch
--- sccache-0.4.0~~pre8/debian/patches/0001_base64.patch1970-01-01
00:00:00.0 +
+++ sccache-0.4.0~~pre8/debian/patches/0001_base64.patch2023-06-20
08:08:00.0 +
@@ -0,0 +1,133 @@
+This patch contains the parts of the upstream commit described below that
+relate to the update of the base64 crate. Cargo.lock changes are also excluded
+since Debian doesn't use Cargo.lock.
+
+commit 408ae947d7c36f0510695bc991438ce2e180d099
+Author: Xuanwo
+Date: Sun Feb 26 15:09:53 2023 +0800
+
+deps: Bump toml and base64 (#1619)
+
+Signed-off-by: Xuanwo
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 964efa8..67fad6b 100644
+--- a/Cargo.toml
b/Cargo.toml
+@@ -27,7 +27,7 @@ anyhow = "1.0"
+ ar = "0.9"
+ async-trait = "0.1"
+ atty = "0.2.6"
+-base64 = "0.20"
++base64 = "0.21"
+ bincode = "1"
+ blake3 = "1"
+ byteorder = "1.0"
+diff --git a/src/bin/sccache-dist/main.rs b/src/bin/sccache-dist/main.rs
+index effdb98..5975aeb 100644
+--- a/src/bin/sccache-dist/main.rs
b/src/bin/sccache-dist/main.rs
+@@ -22,6 +22,7 @@ extern crate tar;
+ extern crate void;
+
+ use anyhow::{bail, Context, Error, Result};
++use base64::Engine;
+ use rand::{rngs::OsRng, RngCore};
+ use sccache::config::{
+ scheduler as scheduler_config, server as server_config,
INSECURE_DIST_CLIENT_TOKEN,
+@@ -144,7 +145,7 @@ fn run(command: Command) -> Result {
+ let mut bytes = vec![0; num_bytes];
+ OsRng.fill_bytes(&mut bytes);
+ // As long as it can be copied, it doesn't matter if this is
base64 or hex etc
+-println!("{}", base64::encode_engine(&bytes,
&BASE64_URL_SAFE_ENGINE));
++println!("{}", BASE64_URL_SAFE_ENGINE.encode(bytes));
+ Ok(0)
+ }
+ Command::Auth(AuthSubcommand::JwtHS256ServerToken {
+@@ -152,7 +153,7 @@ fn run(command: Command) -> Result {
+ server_id,
+ }) => {
+ let header = jwt::Header::new(jwt::Algorithm::HS256);
+-let secret_key = base64::decode_engine(&secret_key,
&BASE64_URL
Bug#1038708: src:python-socks: fails to migrate to testing for too long: autopkgtest regression
Source: python-socks Version: 2.0.3-2 Severity: serious Control: close -1 2.1.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-socks has been trying to migrate for 122 days [2]. Hence, I am filing this bug. The autopgtest of this version fails. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-socks OpenPGP_signature Description: OpenPGP digital signature
Processed: src:python-socks: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 2.1.1-1 Bug #1038708 [src:python-socks] src:python-socks: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions python-socks/2.1.1-1. Bug #1038708 [src:python-socks] src:python-socks: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1038708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038695: marked as done (mathcomp-multinomials: autopkgtest regression with coq 8.17.0)
Your message dated Tue, 20 Jun 2023 10:07:06 + with message-id and subject line Bug#1038695: fixed in mathcomp-multinomials 1.6.0-2 has caused the Debian Bug report #1038695, regarding mathcomp-multinomials: autopkgtest regression with coq 8.17.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.) -- 1038695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mathcomp-multinomials Version: 1.5.5-8 Severity: serious https://ci.debian.net/packages/m/mathcomp-multinomials/testing/amd64/ ... 36s autopkgtest [07:23:05]: test command1: coqtop -batch -rifrom SsrMultinomials mpoly 36s autopkgtest [07:23:05]: test command1: [--- 36s Error: Cannot find a physical path bound to logical path 36s mpoly with prefix SsrMultinomials. 36s 36s autopkgtest [07:23:05]: test command1: ---] 36s autopkgtest [07:23:05]: test command1: - - - - - - - - - - results - - - - - - - - - - 36s command1 FAIL non-zero exit status 1 ... --- End Message --- --- Begin Message --- Source: mathcomp-multinomials Source-Version: 1.6.0-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of mathcomp-multinomials, 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. Julien Puydt (supplier of updated mathcomp-multinomials 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: Tue, 20 Jun 2023 11:39:20 +0200 Source: mathcomp-multinomials Architecture: source Version: 1.6.0-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 1038695 Changes: mathcomp-multinomials (1.6.0-2) unstable; urgency=medium . * Fix autopkgtest (Closes: #1038695). Checksums-Sha1: 30a00c6eb5c69a9de2a4f3cc92fb1aa447028f7b 2274 mathcomp-multinomials_1.6.0-2.dsc 6f9115c4006ad3bd1d46bdc9815859253f048dc7 8792 mathcomp-multinomials_1.6.0-2.debian.tar.xz b70f709d4bc5eae2b8ff69cd7107a5f888cb7049 7460 mathcomp-multinomials_1.6.0-2_source.buildinfo Checksums-Sha256: c17b74f5b8db433fd9ee657fce8e4e9182f5740b24b4ebe71a0b163b8749fdc3 2274 mathcomp-multinomials_1.6.0-2.dsc e56bbd4e081b4a456244fc85f9d9a6ee7fe585592f8d171176660f9f662559d9 8792 mathcomp-multinomials_1.6.0-2.debian.tar.xz cc6858fdaa5f74830c258a18916e9b04bcf4b9a5b5656b8bbb01279a0f6978f7 7460 mathcomp-multinomials_1.6.0-2_source.buildinfo Files: 6a64d0fb3ecad4b2a9cebd8767b2d766 2274 ocaml optional mathcomp-multinomials_1.6.0-2.dsc 478f1b3249c042194be2b7949f719cf4 8792 ocaml optional mathcomp-multinomials_1.6.0-2.debian.tar.xz c0fdd42e6a1c3ca156b1de955b69ff26 7460 ocaml optional mathcomp-multinomials_1.6.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmSRdA0SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRNy0P+N+asz87qzVzTAVBSfVdPDXJUHB12LGn nns+dzsKF1cdvvzQ9GOP977kbL1/PjlnDMenaPxOz5cu33Myvgr9j1p+QA0B8a3m v2ur/XsNK+kxJbOwf5SlHWJasaDgJO/iwDeDaCUUmDmVGCRvLu+jP4N9PmwSsUyT 9rqrq6cpLUlOw6cH6X824cAJTkRTBeJkLNasKmYYJ11t9cyl9w2KrVWb+C4MmBGj 0Y3nF0FsqIBeKZm92ZbNMznYHe9LNq4tmhiRKdTjGVK9Y+8GpxroOMLYh2FiUa2R LdZF9ROWHG6pf6OhQd22xIV4MG9YJCIJT6xiLNflgl2r29G0rk5DHOAMkqycziMI ld7PuXlxzyAIl1RVV6w1QGthN3a27PiZMbC3GzbmQshzMO7+nPZS55jKbERsiBRV 8YorkpwgoifPDUPfDpjRB8/3n9Hl1qg2AUFbvOBjbs6hy+HAuHqbiClfw79ClycS Nnwh1b+xeYHBXS9uZB6l9FV0wOb8VTqvXmS5N5sFxbtsU/atMIEpoPVSlkQQiRgL b1dPz1t5Bu0ZFOAsoV1l2aIofyv05zCROActF+bR5V4RMzBdw7kKheFoNd7nIJAE Tol+I3+7YdCYm5I2kRFnw3sgAeVIRauNW/fjspXiRuc2mUJfe+vBn86TJ/TAASzN +TktHbwO9aY= =cR9j -END PGP SIGNATURE End Message ---
Bug#1038672: marked as done (mathcomp-abel FTBFS: Error: The reference fact_smonotone was not found in the current environment.)
Your message dated Tue, 20 Jun 2023 10:06:59 + with message-id and subject line Bug#1038672: fixed in mathcomp-abel 1.2.1-2 has caused the Debian Bug report #1038672, regarding mathcomp-abel FTBFS: Error: The reference fact_smonotone was not found in the current environment. 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.) -- 1038672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mathcomp-abel Version: 1.2.1-1 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/logs.php?pkg=mathcomp-abel&ver=1.2.1-1%2Bb6 ... dh_auto_build -a make -j4 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' coq_makefile -f _CoqProject -o Makefile.coq make --no-print-directory -f Makefile.coq COQDEP VFILES COQC theories/xmathcomp/various.v COQC theories/xmathcomp/char0.v File "./theories/xmathcomp/char0.v", line 104, characters 14-21: Warning: Notation rmorphX is deprecated since mathcomp 1.17.0. Use rmorphXn instead. [deprecated-syntactic-definition,deprecated] File "./theories/xmathcomp/char0.v", line 104, characters 14-21: Warning: Notation rmorphX is deprecated since mathcomp 1.17.0. Use rmorphXn instead. [deprecated-syntactic-definition,deprecated] File "./theories/xmathcomp/various.v", line 1168, characters 34-48: Error: The reference fact_smonotone was not found in the current environment. make[3]: *** [Makefile.coq:844: theories/xmathcomp/various.vo] Error 1 --- End Message --- --- Begin Message --- Source: mathcomp-abel Source-Version: 1.2.1-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of mathcomp-abel, 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. Julien Puydt (supplier of updated mathcomp-abel 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: Tue, 20 Jun 2023 11:45:39 +0200 Source: mathcomp-abel Architecture: source Version: 1.2.1-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 1038672 Changes: mathcomp-abel (1.2.1-2) unstable; urgency=medium . * Bump standards-version to 4.6.2. * Add patch to fix compilation with mathcomp >= 1.17. * Add patch to fix compilation with coq >= 8.17. * Add versioned dep on coq and ssreflect (Closes: #1038672). Checksums-Sha1: c392dfe9ec4752032d0752778850ab1e36f17895 2251 mathcomp-abel_1.2.1-2.dsc 83e39fa9fb813c8c463bfe58b4aeb8e9a91b196a 9732 mathcomp-abel_1.2.1-2.debian.tar.xz 570d813f442c71e2aedf48aa18ef1676ed05c36c 7510 mathcomp-abel_1.2.1-2_source.buildinfo Checksums-Sha256: 6ac963e519a9c366977db0244e882ed505f2b0008978a4ed00cd3f78c30e711e 2251 mathcomp-abel_1.2.1-2.dsc faf3be97536c6b26b352dc869062ed21002f186fea4e87df3835722457b9d4ff 9732 mathcomp-abel_1.2.1-2.debian.tar.xz 27c07f3bb82b346ac7976ff70d9df1ac85925036ccc39f8ece80ea6bdf6e64bd 7510 mathcomp-abel_1.2.1-2_source.buildinfo Files: 4168b87cfeef1f474562ee8cf82dc90a 2251 ocaml optional mathcomp-abel_1.2.1-2.dsc f58ac79c41afc1109e9378d24b3eea0e 9732 ocaml optional mathcomp-abel_1.2.1-2.debian.tar.xz a0bbc4b853fee3894577c8b512c781a1 7510 ocaml optional mathcomp-abel_1.2.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmSRdW0SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRB6gP/3UIopu0GH9Vpp+OTaIfn0nPaqb++P/y Cgz83IzcVXqk8WSYA+LmCQkWNw0y1N5/99RadZQoNCEYSdLQBoCQb2lBn0dp9iB2 kuQZzIsquFgldQlq14Z4leSj0ZSW/9hmRVodrtFlInMswtvadHA5asZEBIJzz2f5 E9KU9ZeF6fCEWrMMHS2Jr0O/4UQcxq7DKtfXnk/va+c0nXJUVt6HXzwZY/Fds4jk +AqLlzEIg62/6YepCBnQsXuke51G4JAuOoH6/F9S6+nvwScu1gC13MqCDL0B44p5 lMuiaoVYQqK6HCoMJ0eAoAKUfGo0ux/DiUlSsrZgUFjif+5pfK3gSuB/D98D9boL JGmA9luyg6KsXyM+f5B/G4DM2axVGBV5XTiULk8sHQZOhRby9jtF2NwdJKplfaU7 G/1QAp8BcCwch1OF9tq6TBmKYJMT6fxdpRxc+P71BWGtngyXLJrcnR78zuXuaHty Vf+0YCSPY23dJkbeoZoweA55XPB5ySSq5bEjdPKtqZxbR2nP2w6rHWDEbKy6kdAP YsLW7UZ75JL+z/ZESaqxbs+VUEwGUIM8ieQb6Zi6Qw3cmEr2OhtT2wc8MHuSZ30s Ex+KG4O0E7BXIIUCKmbKW+tOof1eirLme93e2mQJIHQxNuRfVig2Gu8438BNNaus T+7B4JqG1Jpg =O
Bug#1038675: marked as done (coqeal FTBFS: Error: Cannot find a physical path bound to logical path mpoly with prefix SsrMultinomials.)
Your message dated Tue, 20 Jun 2023 10:04:49 + with message-id and subject line Bug#1038675: fixed in coqeal 1.1.3-1 has caused the Debian Bug report #1038675, regarding coqeal FTBFS: Error: Cannot find a physical path bound to logical path mpoly with prefix SsrMultinomials. 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.) -- 1038675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coqeal Version: 1.1.1-3 Severity: serious Tags: ftbfs trixie sid https://buildd.debian.org/status/logs.php?pkg=coqeal&ver=1.1.1-3%2Bb2 ... COQC refinements/bareiss_eff.v File "./refinements/seqmx_complements.v", line 46, characters 0-58: Warning: The default value for Typeclasses Opaque and Typeclasses Transparent locality is currently "local" in a section and "global" otherwise, but is scheduled to change in a future release. For the time being, adding typeclass transparency hints outside of sections without specifying an explicit locality attribute is therefore deprecated. It is recommended to use "export" whenever possible. Use the attributes #[local], #[global] and #[export] depending on your choice. For example: "#[export] Typeclasses Transparent foo.". This is supported since Coq 8.15. [deprecated-typeclasses-transparency-without-locality,deprecated] COQC refinements/multipoly.v File "./refinements/multipoly.v", line 13, characters 0-48: Error: Cannot find a physical path bound to logical path mpoly with prefix SsrMultinomials. make[3]: *** [Makefile.coq:844: refinements/multipoly.vo] Error 1 --- End Message --- --- Begin Message --- Source: coqeal Source-Version: 1.1.3-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of coqeal, 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. Julien Puydt (supplier of updated coqeal 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: Tue, 20 Jun 2023 11:49:18 +0200 Source: coqeal Architecture: source Version: 1.1.3-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Julien Puydt Closes: 1038675 Changes: coqeal (1.1.3-1) unstable; urgency=medium . * New upstream release. * Bump standards-version to 4.6.2. * Bump depend on mathcomp-multinomials (Closes: #1038675). Checksums-Sha1: 7afdd35dfc8e02cba0648e270e0e0f93298d7d2c 2179 coqeal_1.1.3-1.dsc 1b9af210527afbc4a72fdb79157d741c990f58da 217753 coqeal_1.1.3.orig.tar.gz 1e50659e618cd82dd44722311ea278a6b7ee71ef 2224 coqeal_1.1.3-1.debian.tar.xz d42cfab47f49dc7789ecb48877a3a331ea1f054e 7830 coqeal_1.1.3-1_source.buildinfo Checksums-Sha256: 617fcc5cfb44904836eeefdf96fb06e9a44eed738d7830f45b306afcd3bd4d47 2179 coqeal_1.1.3-1.dsc a81c21d31fdc888621570ba39a7d1e9bbf4695c112e4e0f8be638296d96dcba1 217753 coqeal_1.1.3.orig.tar.gz 792529f1529ee0cf65a9d27eddd2848e62c8548417008c6615c81f86471ae7d9 2224 coqeal_1.1.3-1.debian.tar.xz daa516b87896a24f0f6adb5ce38c0ad9a54b061d0f916a337233e16e0b9006d8 7830 coqeal_1.1.3-1_source.buildinfo Files: 780100a2d89f54a0cc73d35f7805a965 2179 ocaml optional coqeal_1.1.3-1.dsc 3c901c58e24e003b268c9984e02403af 217753 ocaml optional coqeal_1.1.3.orig.tar.gz c0dec2deb1bd4bba7a538da39bf84e1d 2224 ocaml optional coqeal_1.1.3-1.debian.tar.xz de57d8085fbce87cf45583bab7009fd2 7830 ocaml optional coqeal_1.1.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmSRdjcSHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVR280P/AnhPAgoSlurjaw4jeKTYxzg1LavGexo 6SjzjAITY4yxduXZfTo23fRq1yYdt6rC6MApf9jAtmpL43U1OgRpH1WAOlFR68Vu EV9Pqc12SNMBTw7QG1Bnqh3lBHSwtRd1m6H4i8T9F/lpbYht4GIv84bVlHuPuPTQ BfTDjGVfXj7RV+WZL1Gsnuq4ZUadYYPyirSEzJmFbyrWEoSJxQ9/2EovyVLc7O84 pipUu513mGDH/nFWXDCXSnWAYfIwGX5uwN1XwMjcX0wnwQ63kBpdosVj4DgwFqRY aMZs2t7+ULLC/6ie3zeBeRRbYishrVLyAjgD72EvbOrsfWWphUpYsWMeGHVCmcgI XPm2r0KSUoVNZ1M768UzoSkisxhJAgssiRovhYwNR/BaQ7ME/G5uGvuf0uo/TpKa 0AgAjN4K90q8rZzVz++PE9TarRsSBEwpaHrq69KIvB+A743tAXIgyMY+kNkXRjEr /s2c8Fs2ZRxZO1QOYnNQQ9d+Vf/8Nx6mpZ+sts3R/eO2A36l33vUZiOy3TdOX
Processed: src:ruby-celluloid: fails to migrate to testing for too long: causes autopkgtest regressions
Processing control commands: > close -1 0.18.0-2 Bug #1038707 [src:ruby-celluloid] src:ruby-celluloid: fails to migrate to testing for too long: causes autopkgtest regressions Marked as fixed in versions ruby-celluloid/0.18.0-2. Bug #1038707 [src:ruby-celluloid] src:ruby-celluloid: fails to migrate to testing for too long: causes autopkgtest regressions Marked Bug as done -- 1038707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038707: src:ruby-celluloid: fails to migrate to testing for too long: causes autopkgtest regressions
Source: ruby-celluloid Version: 0.16.0-5 Severity: serious Control: close -1 0.18.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:ruby-celluloid has been trying to migrate for 130 days [2]. Hence, I am filing this bug. The new version causes autopkgtest regressions in multiple reverse dependencies. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-celluloid OpenPGP_signature Description: OpenPGP digital signature
Processed: src:afnix: fails to migrate to testing for too long: FTBFS on 32 bit
Processing control commands:
> close -1 3.8.0-1
Bug #1038705 [src:afnix] src:afnix: fails to migrate to testing for too long:
FTBFS on 32 bit
Marked as fixed in versions afnix/3.8.0-1.
Bug #1038705 [src:afnix] src:afnix: fails to migrate to testing for too long:
FTBFS on 32 bit
Marked Bug as done
> block -1 by 1031749
Bug #1038705 {Done: Paul Gevers } [src:afnix] src:afnix:
fails to migrate to testing for too long: FTBFS on 32 bit
1038705 was not blocked by any bugs.
1038705 was not blocking any bugs.
Added blocking bug(s) of 1038705: 1031749
--
1038705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1038705: src:afnix: fails to migrate to testing for too long: FTBFS on 32 bit
Source: afnix Version: 3.7.0-1 Severity: serious Control: close -1 3.8.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1031749 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:afnix has been trying to migrate for 124 days [2]. Hence, I am filing this bug. The package fails to build from source, which was reported in bug 1031749. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=afnix OpenPGP_signature Description: OpenPGP digital signature
Bug#1038704: src:guestfs-tools: fails to migrate to testing for too long: Build-Depends missing on armhf and i386
Source: guestfs-tools Version: 1.48.2-1 Severity: serious Control: close -1 1.50.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:guestfs-tools has been trying to migrate for 159 days [2]. Hence, I am filing this bug. This package seems to be Build-Depending on *versioned* package from itself, but it seems that the build from the previous version on i386 and armhf were too late to satisfy the builds from the current version. Please investigate how to rebootstrap i386 and armhf again. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=guestfs-tools OpenPGP_signature Description: OpenPGP digital signature
Processed: src:guestfs-tools: fails to migrate to testing for too long: Build-Depends missing on armhf and i386
Processing control commands: > close -1 1.50.1-1 Bug #1038704 [src:guestfs-tools] src:guestfs-tools: fails to migrate to testing for too long: Build-Depends missing on armhf and i386 Marked as fixed in versions guestfs-tools/1.50.1-1. Bug #1038704 [src:guestfs-tools] src:guestfs-tools: fails to migrate to testing for too long: Build-Depends missing on armhf and i386 Marked Bug as done -- 1038704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038700: src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386
Source: r-cran-igraph Version: 1.3.5-3 Severity: serious Control: close -1 1.4.1-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:r-cran-igraph has been trying to migrate for 114 days [2]. Hence, I am filing this bug. The autopkgtest of this package regressed on i386. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=r-cran-igraph OpenPGP_signature Description: OpenPGP digital signature
Processed: src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386
Processing control commands: > close -1 1.4.1-1 Bug #1038700 [src:r-cran-igraph] src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386 Marked as fixed in versions r-cran-igraph/1.4.1-1. Bug #1038700 [src:r-cran-igraph] src:r-cran-igraph: fails to migrate to testing for too long: autopkgtest regression on i386 Marked Bug as done -- 1038700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1038695
Processing commands for cont...@bugs.debian.org: > tags 1038695 + trixie sid Bug #1038695 [src:mathcomp-multinomials] mathcomp-multinomials: autopkgtest regression with coq 8.17.0 Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1038695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038696: libjpegli62: missing Conflicts/Replaces/Provides: libjpeg62
Package: libjpegli62 Version: 0.9.0~git20230612.38b629f-3 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 .../libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb ... Unpacking libjpegli62:amd64 (0.9.0~git20230612.38b629f-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.62', which is also in package libjpeg62:amd64 1:6b2-3.1 Errors were encountered while processing: /var/cache/apt/archives/libjpegli62_0.9.0~git20230612.38b629f-3_amd64.deb There is still a libjpeg62 package in sid. Please check libjpeg62-turbo for the C/R/P against libjpeg62 and model yours similarily. cheers, Andreas libjpeg62=1:6b2-3.1_libjpegli62=0.9.0~git20230612.38b629f-3.log.gz Description: application/gzip
Bug#1038695: mathcomp-multinomials: autopkgtest regression with coq 8.17.0
Source: mathcomp-multinomials Version: 1.5.5-8 Severity: serious https://ci.debian.net/packages/m/mathcomp-multinomials/testing/amd64/ ... 36s autopkgtest [07:23:05]: test command1: coqtop -batch -rifrom SsrMultinomials mpoly 36s autopkgtest [07:23:05]: test command1: [--- 36s Error: Cannot find a physical path bound to logical path 36s mpoly with prefix SsrMultinomials. 36s 36s autopkgtest [07:23:05]: test command1: ---] 36s autopkgtest [07:23:05]: test command1: - - - - - - - - - - results - - - - - - - - - - 36s command1 FAIL non-zero exit status 1 ...
