Processed: found 1039883 in 6.1.55-1
Processing commands for cont...@bugs.debian.org: > found 1039883 6.1.55-1 Bug #1039883 [src:linux] linux-image-6.3.0-1-amd64: ext4 corruption with symlinks Marked as found in versions linux/6.1.55-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1039883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054437: golang-ariga-atlas: website is build with Docusaurus not packaged for debian
Hi Bastien, Bastien Roucariès (2023-10-23): > Source: golang-ariga-atlas > Version: 0.7.2-2 > Severity: serious > Tags: ftbfs > Justification: FTBFS This doesn't make any sense. > Control: block -1 by 1054426 > > Dear Maintainer, > > The documentation is build with docusaurus. > > See website directory > https://sources.debian.org/src/golang-ariga-atlas/0.7.2-2/doc/website/ > > You should repack or package docusaurus and rebuild You're filing a serious bug report claiming this is about a failure to build from source, then mention repacking, without describing any actual issues. Please be more considerate when filing serious bug reports. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1054438: golang-entgo-ent: website is build with Docusaurus not packaged for debian
Bastien Roucariès (2023-10-23): > Source: golang-entgo-ent > Version: 0.11.3-4 > Severity: serious > Tags: ftbfs > Justification: FTBFS > Control: block -1 by 1054426 > > Dear Maintainer, > > The documentation is build with docusaurus. > > See website directory > https://sources.debian.org/data/main/g/golang-entgo-ent/0.11.3-4/doc/website > > You should repack or package docusaurus and rebuild That's bug report number 3 without any details… -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#1051181: marked as done (FTBFS: can't build package when user has more than 16 supplementary groups)
Your message dated Mon, 06 Nov 2023 00:34:08 +
with message-id
and subject line Bug#1051181: fixed in fapolicyd 1.3.2-1
has caused the Debian Bug report #1051181,
regarding FTBFS: can't build package when user has more than 16 supplementary
groups
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.)
--
1051181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fapolicyd
Version: 1.1.7-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
# TOTAL: 2
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: gid_proc_test
===
./gid_proc_test: Too many groups
FAIL gid_proc_test (exit status: 1)
Above are the relevant parts of the compile output when trying to build it by a
user with more than 16 supplementary groups.
Below is the patch to fix this:
Index: fapolicyd-1.1.7/src/tests/gid_proc_test.c
===
--- fapolicyd-1.1.7.orig/src/tests/gid_proc_test.c
+++ fapolicyd-1.1.7/src/tests/gid_proc_test.c
@@ -2,6 +2,7 @@
#include
#include
#include
+#include
#include
#include "attr-sets.h"
#include "process.h"
@@ -9,7 +10,7 @@
int main(void)
{
int res, num, i, check_intersect = 0;
- gid_t gid, gids[16];
+ gid_t gid, gids[NGROUPS_MAX];
attr_sets_entry_t *groups = get_gid_set_from_pid(getpid());
gid = getgid();
@@ -17,7 +18,7 @@ int main(void)
if (!res)
error(1, 0, "Group %d not found", gid);
- num = getgroups(16, gids);
+ num = getgroups(NGROUPS_MAX, gids);
if (num < 0)
error(1, 0, "Too many groups");
-- System Information:
Debian Release: trixie/sid
Architecture: amd64 (x86_64)
Kernel: Linux 6.4.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Source: fapolicyd
Source-Version: 1.3.2-1
Done: Nobuhiro Iwamatsu
We believe that the bug you reported is fixed in the latest version of
fapolicyd, 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 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu (supplier of updated fapolicyd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 06 Nov 2023 09:16:04 +0900
Source: fapolicyd
Architecture: source
Version: 1.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu
Changed-By: Nobuhiro Iwamatsu
Closes: 1051181
Changes:
fapolicyd (1.3.2-1) unstable; urgency=medium
.
* Update to 1.3.2.
* Fix FTBFS when user has more than 16 supplementary groups (Closes:
#1051181)
Add d/debian/patches/0008-Fix-FTBFS-cant-build-package-when-user.patch.
Thank to Russell Coker .
* Drop rpmdb drom trust variable from fapolicyd.conf.
+ Add d/patches/0009-fapolicyd.conf-Drop-rpmdb-from-trust-variable.patch.
* d/patches: Remove unnecessary patches.
* Refresh d/patches/0007-Install-service-file-to-usr-lib-systemd.patch
* Add support deb package.
+ d/rules: Set --with-deb to configure.
+ d/control: Add dpkg-dev to Build-Depends.
* Fix build issue by libmd linkng.
Add d/patches/0010-configure.ac-Swap-checkong-libmd-and-libdpkg.patch.
* d/rules: Do not copy 90-deny-execute.rules to /etc/fapolicyd/rules.d.
* d/rules: Disable start fapolicyd.service.
* d/README.Debian: Update.
* d/patches: Add 0011-Fix-section-number-of-man-files.patch.
Checksums-Sha1:
67e1b2ff42d42905d1844b5e02c4f536f788170d 2051 fapolicyd_1.3.2-1.dsc
99dbe618f33bdb7671823d388453daa5d8cd61fb 135755 fapolicyd_1.3.2.orig.tar.gz
9a27088ae4388568a23a594e13ea448b5057686d 7056 fapolicyd_1.3.2-1.debian.tar.xz
78e5c19b28508fff1cea21ab9375d69f240c2885 6431 fapolicyd_1.3.2-1_amd64.buildinfo
Checksums-Sha256:
Bug#1055432: kontact: Attaching file to email tries to mount filesystems
Package: kontact Version: 4:22.12.3-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, Kontact email composition window "Attach file" should not try to mount filesystems that aren't already mounted and the user does not explicitly try to enter. Reproduce: 1. Set up an automounted filesystem, e.g. at /mnt/foobar 2. Mount it 3. Add /mnt/foobar to the sidebar either in Places, Recent Locations, or Remote, do not enter the directory (or come out of it after so it's not the last one you were in while the dialog is open) 4. Close the compose window 5. Umount /mnt/foobar 6. Compose another email and attach a file: /mnt/foobar gets mounted. I appreciate this is an attempt to be helpful, gathering information about known mountpoints, but the nature of autofs mountpoints is that they are not guaranteed to be always available to be mounted so causing an attempt to mount them without user explicitly asking for it is not good. This is especially bad when the mountpoint is an NFS mount: kontact will hang until autofs succeeds in mounting it. If the NFS server is never coming back, data loss follows as kontact will never recover from an uninterruptible system call. This is also highly annoying even when the server is available but /mnt/foobar is not yet mounted: opening the file selection dialog takes as long as it takes for the mount to finish, which is long enough to be annoying. Kontact needs to be selective in its helpfulness: avoid causing autofs mounts to be triggered if they are not yet mounted unless explicitly requested by the user. Cheers, Juha -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kontact depends on: ii kdepim-runtime 4:22.12.3-2 ii libc62.37-12 ii libkf5configcore55.107.0-1 ii libkf5configgui5 5.107.0-1 ii libkf5configwidgets5 5.107.0-2 ii libkf5coreaddons55.107.0-1 ii libkf5crash5 5.107.0-1 ii libkf5grantleetheme5 [libkf5grantleetheme5-22.12]22.12.3-2+b1 ii libkf5guiaddons5 5.107.0-1 ii libkf5i18n5 5.107.0-1+b1 ii libkf5jobwidgets55.107.0-1 ii libkf5kcmutils5 5.107.0-2 ii libkf5kiogui55.107.0-1 ii libkf5kontactinterface5 [libkf5kontactinterface5-22.12] 22.12.3-1 ii libkf5libkdepim5 [libkf5libkdepim5-22.12]4:22.12.3-1 ii libkf5parts5 5.107.0-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-22.12]4:22.12.3-1 ii libkf5service-bin5.107.0-1 ii libkf5service5 5.107.0-1 ii libkf5widgetsaddons5 5.107.0-1 ii libkf5windowsystem5 5.107.0-1 ii libkf5xmlgui55.107.0-1+b1 ii libqt5core5a 5.15.10+dfsg-4 ii libqt5dbus5 5.15.10+dfsg-4 ii libqt5gui5 5.15.10+dfsg-4 ii libqt5webengine5 5.15.15+dfsg-2+b1 ii libqt5webenginecore5 5.15.15+dfsg-2+b1 ii libqt5webenginewidgets5 5.15.15+dfsg-2+b1 ii libqt5widgets5 5.15.10+dfsg-4 ii libstdc++6 13.2.0-6 Versions of packages kontact recommends: ii accountwizard 4:22.12.3-1 ii akregator 4:22.12.3-1 ii kaddressbook 4:22.12.3-1 ii kmail 4:22.12.3-1 ii knotes 4:22.12.3-1 ii korganizer 4:22.12.3-1 Versions of packages kontact suggests: pn gnokii -- no debconf information
Bug#793668: marked as done (angband-audio: maintainer scripts mishandle angband-data's /usr/share/angband/xtra/sound/sound.cfg)
Your message dated Sun, 05 Nov 2023 23:34:09 + with message-id and subject line Bug#793668: fixed in angband-audio 1:3.1.0-2 has caused the Debian Bug report #793668, regarding angband-audio: maintainer scripts mishandle angband-data's /usr/share/angband/xtra/sound/sound.cfg 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.) -- 793668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: angband-audio Version: 1:3.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts TL;DR: Use dpkg-divert. No Replaces. No manual moving. Be idempotent. Hi, during a test with piuparts I noticed your package does something wrong since angband-data loses ownership of /usr/share/angband/xtra/sound/sound.cfg Looking at the maintainer scripts, what you want to accomplish is the perfect task for dpkg-divert. Adding Replaces is wrong. Also the maintainer script actions are not idempotent, but they are performed (nearly) each time the script is called, so after apt-get install angband-audio apt-get install --reinstall angband-audio the sound.cfg.orig is gone. Once this is fixed in angband-audio, angband-data needs to add versioned Breaks against the buggy angband-audio version. Andreas --- End Message --- --- Begin Message --- Source: angband-audio Source-Version: 1:3.1.0-2 Done: Chris Carr We believe that the bug you reported is fixed in the latest version of angband-audio, 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 793...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Carr (supplier of updated angband-audio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Nov 2023 13:47:02 - Source: angband-audio Binary: angband-audio Architecture: source all Version: 1:3.1.0-2 Distribution: unstable Urgency: low Maintainer: Debian Games Team Changed-By: Chris Carr Description: angband-audio - Sound files for the roguelike game angband Closes: 793452 793668 1028659 Changes: angband-audio (1:3.1.0-2) unstable; urgency=low . [ Alexandre Detiste ] * Move to salsa.debian.org and put under Debian Games Team . [ Chris Carr ] * Update for Angband version 4.2.5. (Closes: #793452, #793668, #1028659) . [ Bastian Germann ] * Make the package reproducible * Set Rules-Requires-Root: no Checksums-Sha1: 95ab2759fe5079f57b6e0dcffcc9314df453aecb 1834 angband-audio_3.1.0-2.dsc d1477caa075121c333029fba385b4947fc34b798 6844 angband-audio_3.1.0-2.debian.tar.xz 8253c32238de571fdea166505769f43ea951d9c1 2921420 angband-audio_3.1.0-2_all.deb 0f345199b1f4bd284803b1802cb56235914ab9de 6479 angband-audio_3.1.0-2_i386.buildinfo Checksums-Sha256: 739eda2d975490ceb0cc53afd2e45f1f7615c933780c95f5d0ae048bfa7215c7 1834 angband-audio_3.1.0-2.dsc 359200916b5c4dc0e058177248c612f04cc634662bf0470e97b8324235afe50f 6844 angband-audio_3.1.0-2.debian.tar.xz f8654bc056c5f6ac76512be85f1fa0a38c08644c4fc2e4f6182033e01a84a7fd 2921420 angband-audio_3.1.0-2_all.deb 1b51a514d3b0b2d3e184de43a7f423f49a21abc0a093eb697b4d721280e8a056 6479 angband-audio_3.1.0-2_i386.buildinfo Files: c5c1d36aeb8cb56ccbea792dcb2acf12 1834 non-free/games optional angband-audio_3.1.0-2.dsc 6316c4155f926f69cd96bb94a75514ff 6844 non-free/games optional angband-audio_3.1.0-2.debian.tar.xz 5e7a8500248a070865ad61047faed691 2921420 non-free/games optional angband-audio_3.1.0-2_all.deb e62f81a6988e4b1e839c80059cc2532d 6479 non-free/games optional angband-audio_3.1.0-2_i386.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmVIJEEQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFPueDADIspLqU57qUTg+18/fPaWmuyEVr75sAykb KmQQGlUJNFaguOsSbhmlly2IXuaA5kvbssW25MMeKVofmYJlh/Qnt4MY9wnI2vkN NXVxjRT/YVL8SIR1d0JOBiwK46P5/8dlHqU6lueO728cyzZnK3zkz5LHO1eIGsvJ P3u11SQmEVABn16bFx26DuCnaUXbAsH2MGp4m4L4E/IO0DGt5vknwLbqhlWiy5d1 qpvKn54bBqgVX7lhHk6CV1ku1ulOFgyTbOjDWLSQ8/EofEtAHn7MMk6IoFQ7VR3h BNgTg0L3F9FcZAJBzoG+plWFxHgflNIMCj5MCdUxg6LHbXshLGs+4ahi7pejAIBM +y7h111WOAyFXQyRMQjtr5cD49vPePA0ZyqBCogMY2ZRneqTq/uJkI0hHG8LYJsI
Bug#1028659: marked as done (angband-audio: should this package be removed?)
Your message dated Sun, 05 Nov 2023 23:34:09 + with message-id and subject line Bug#1028659: fixed in angband-audio 1:3.1.0-2 has caused the Debian Bug report #1028659, regarding angband-audio: should this package be removed? 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.) -- 1028659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: angband-audio Version: 1:3.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: proposed-removal X-Debbugs-CC: p...@debian.org Hi, I did find the package angband-audio in a QA list I am cleaning up. It seems like angband is a packaged that is still maintained. This made me unsure about requesting a FTP RM for angband-audio. Is the package angband-audio still useful given it's only in unstable and has no upload since 2016 ? -- William Desportes --- End Message --- --- Begin Message --- Source: angband-audio Source-Version: 1:3.1.0-2 Done: Chris Carr We believe that the bug you reported is fixed in the latest version of angband-audio, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Carr (supplier of updated angband-audio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Nov 2023 13:47:02 - Source: angband-audio Binary: angband-audio Architecture: source all Version: 1:3.1.0-2 Distribution: unstable Urgency: low Maintainer: Debian Games Team Changed-By: Chris Carr Description: angband-audio - Sound files for the roguelike game angband Closes: 793452 793668 1028659 Changes: angband-audio (1:3.1.0-2) unstable; urgency=low . [ Alexandre Detiste ] * Move to salsa.debian.org and put under Debian Games Team . [ Chris Carr ] * Update for Angband version 4.2.5. (Closes: #793452, #793668, #1028659) . [ Bastian Germann ] * Make the package reproducible * Set Rules-Requires-Root: no Checksums-Sha1: 95ab2759fe5079f57b6e0dcffcc9314df453aecb 1834 angband-audio_3.1.0-2.dsc d1477caa075121c333029fba385b4947fc34b798 6844 angband-audio_3.1.0-2.debian.tar.xz 8253c32238de571fdea166505769f43ea951d9c1 2921420 angband-audio_3.1.0-2_all.deb 0f345199b1f4bd284803b1802cb56235914ab9de 6479 angband-audio_3.1.0-2_i386.buildinfo Checksums-Sha256: 739eda2d975490ceb0cc53afd2e45f1f7615c933780c95f5d0ae048bfa7215c7 1834 angband-audio_3.1.0-2.dsc 359200916b5c4dc0e058177248c612f04cc634662bf0470e97b8324235afe50f 6844 angband-audio_3.1.0-2.debian.tar.xz f8654bc056c5f6ac76512be85f1fa0a38c08644c4fc2e4f6182033e01a84a7fd 2921420 angband-audio_3.1.0-2_all.deb 1b51a514d3b0b2d3e184de43a7f423f49a21abc0a093eb697b4d721280e8a056 6479 angband-audio_3.1.0-2_i386.buildinfo Files: c5c1d36aeb8cb56ccbea792dcb2acf12 1834 non-free/games optional angband-audio_3.1.0-2.dsc 6316c4155f926f69cd96bb94a75514ff 6844 non-free/games optional angband-audio_3.1.0-2.debian.tar.xz 5e7a8500248a070865ad61047faed691 2921420 non-free/games optional angband-audio_3.1.0-2_all.deb e62f81a6988e4b1e839c80059cc2532d 6479 non-free/games optional angband-audio_3.1.0-2_i386.buildinfo -BEGIN PGP SIGNATURE- iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmVIJEEQHGJhZ2VAZGVi aWFuLm9yZwAKCRAfXHqLRVZDFPueDADIspLqU57qUTg+18/fPaWmuyEVr75sAykb KmQQGlUJNFaguOsSbhmlly2IXuaA5kvbssW25MMeKVofmYJlh/Qnt4MY9wnI2vkN NXVxjRT/YVL8SIR1d0JOBiwK46P5/8dlHqU6lueO728cyzZnK3zkz5LHO1eIGsvJ P3u11SQmEVABn16bFx26DuCnaUXbAsH2MGp4m4L4E/IO0DGt5vknwLbqhlWiy5d1 qpvKn54bBqgVX7lhHk6CV1ku1ulOFgyTbOjDWLSQ8/EofEtAHn7MMk6IoFQ7VR3h BNgTg0L3F9FcZAJBzoG+plWFxHgflNIMCj5MCdUxg6LHbXshLGs+4ahi7pejAIBM +y7h111WOAyFXQyRMQjtr5cD49vPePA0ZyqBCogMY2ZRneqTq/uJkI0hHG8LYJsI hafrHQDK1JgcoAatriE93aa4sv+8dat2yJ4nC15fn/ch6S/C4+36sPAj3hMkoRqa P/7McZBtMBLVNmE45D5dd89hvknLD9M= =s42z -END PGP SIGNATURE End Message ---
Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl
Am Sonntag, dem 05.11.2023 um 20:35 + schrieb Adam D. Barratt: > [...] > After a bit of searching, I happened across a discussion of a similar > change in a different product that mentioned the > SslContextFactory$Server syntax, so gave that a try. The resulting > package is now installed on handel.d.o and seems to work - at least, > it's been running for 45 minutes now (whereas the broken versions > lasted less than 5 minutes) and at least one client has successfully > made a "puppet agent" run in the meantime. > > I've attached a debdiff of the package we're now running, with the > revised patch. Great, thanks for the update. I feared the Java dot syntax couldn't be applied one-to-one to Clojure. I suggest we wait another 24h to confirm it works and if you don't see another regression then I'll release a new update tomorrow. Regards, Markus signature.asc Description: This is a digitally signed message part
Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
Hi Paul, On Sun, Nov 05, 2023 at 01:45:34PM +0100, Paul Gevers wrote: > Source: wasmedge > Version: 0.13.4+dfsg-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > Your package has an autopkgtest, great. However, it fails. Can you please > investigate the situation and fix it? I copied some of the output at the > bottom of this report. > > The release team has announced [1] that failing autopkgtest on amd64 and > arm64 are considered RC in testing. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > [...] > > 140s # `clang++ --target=wasm32-wasi -o fibonacci.wasm > -mexec-model=reactor script/fibonacci.cpp' failed > 140s # In file included from script/fibonacci.cpp:1: > 140s # script/fibonacci.h:3:10: fatal error: 'cstdint' file not found Thank you for your report. This is caused #1052002, which I had marked as affects: wasmedge previously. Basically, the autopkgtest compiles a piece of code (with Clang) and tries to run it (with WasmEdge). The Clang++ regression means the code cannot be built. I don't know how you'd like ot handle this w.r.t. the BTS, and testing migrations. I'm inclined to just reassign/merge it to the bug above, but I'll wait for your opinion first. Also, I'm not sure I understand how clang migrated to testing when it introduced an autopkgtest regression in another package. Isn't autopkgtest integration in britney supposed to prevent this kind of thing from happening? Looking for your guidance, Faidon
Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl
On Sun, 2023-11-05 at 19:18 +0100, Markus Koschany wrote: > Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt: > > [...] > > Do you have an idea how simple rebuilding the bullseye package on > > buster would be? I'm happy to try that in general, but I've not > > really > > looked at the Java ecosystem in Debian much. > > Sorry, I missed those new or updated dependencies. That complicates > the matter a little. We also have to deal with clojure here, a LISP > dialect of the Java language with a different build system > (leiningen), but if all dependencies were in place a rebuild would be > pretty simple. As a last resort I could bundle all those dependencies > together with trapperkeeper-* the Java way TM but I hope we can avoid > that. > > The most ideal solution is a patch for the current version in Buster. > I have uploaded a new revision to people.debian.org with minimal > changes here: > > https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/ > > dget -x > https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/trapperkeeper-webserver-jetty9-clojure_1.7.0-2+deb10u1.1.dsc > > > should work as expected. I'm attaching the debdiff as well. > > My solution is to replace the old SslContextFactory class with the > new inner SslContextFactory.Server class but I don't know if this > change has the desired effect because I couldn't test it. Thanks for the patch. Unfortunately it didn't work as-is: Nov 5 18:39:14 handel/handel java[2393]: Exception in thread "main" java.lang.AssertionError: Assert failed: (keyword? kw) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.kitchensink.core$without_ns.invokeStatic(core.clj:613) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.kitchensink.core$without_ns.invoke(core.clj:613) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.trapperkeeper.core$main.invokeStatic(core.clj:175) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.trapperkeeper.core$main.doInvoke(core.clj:159) Nov 5 18:39:14 handel/handel java[2393]: at clojure.lang.RestFn.applyTo(RestFn.java:137) Nov 5 18:39:14 handel/handel java[2393]: at clojure.core$apply.invokeStatic(core.clj:665) Nov 5 18:39:14 handel/handel java[2393]: at clojure.core$apply.invoke(core.clj:660) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.puppetdb.cli.services$provide_services.invokeStatic(services.clj:570) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.puppetdb.cli.services$provide_services.invoke(services.clj:558) Nov 5 18:39:14 handel/handel java[2393]: at puppetlabs.puppetdb.cli.services$cli$fn__41585.invoke(services.clj:578) ... After a bit of searching, I happened across a discussion of a similar change in a different product that mentioned the SslContextFactory$Server syntax, so gave that a try. The resulting package is now installed on handel.d.o and seems to work - at least, it's been running for 45 minutes now (whereas the broken versions lasted less than 5 minutes) and at least one client has successfully made a "puppet agent" run in the meantime. I've attached a debdiff of the package we're now running, with the revised patch. Regards, Adam diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog 2019-09-13 10:00:50.0 +0100 +++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog 2023-11-05 19:28:22.0 + @@ -1,3 +1,11 @@ +trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1+dsa1) buster; urgency=medium + + * Non-maintainer upload. + * Replace deprecated class SslContextFactory with SslContextFactory.Server. +Largely based on a patch by Markus Koschany. (Hopefully Closes:#1055348) + + -- Adam D. Barratt Sun, 05 Nov 2023 19:28:22 + + trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1) buster; urgency=medium [ Manfred Stock ] diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series 2019-09-13 09:54:48.0 +0100 +++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series 2023-11-05 19:28:22.0 + @@ -3,3 +3,4 @@ 0003-TK-369-Add-LifeCycleImplementingRequestLogImpl.patch 0004-Implement-LifeCycle-methods-missing-from-RequestLogI.patch 0005-maint-Disable-EndpointIdentification.patch +SslContextFactory.Server.patch diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.Server.patch 1970-01-01 01:00:00.0 +0100 +++
Processed: found 1054427 in 9.2.2+ds-1
Processing commands for cont...@bugs.debian.org:
> found 1054427 9.2.2+ds-1
Bug #1054427 {Done: Jean Baptiste Favre }
[src:trafficserver] trafficserver: CVE-2023-41752 CVE-2023-39456 CVE-2023-44487
Marked as found in versions trafficserver/9.2.2+ds-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1054427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042300: marked as done (glib-d: FTBFS: ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d(324): Error: constructor `glib.ArrayG.ArrayG.this(void*[] data, bool clear, ulong elementSize)` conflicts wi
Your message dated Sun, 5 Nov 2023 19:44:13 +0100 with message-id and subject line Re: glib-d: FTBFS: ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d(324) has caused the Debian Bug report #1042300, regarding glib-d: FTBFS: ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d(324): Error: constructor `glib.ArrayG.ArrayG.this(void*[] data, bool clear, ulong elementSize)` conflicts with previous declaration at ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d(281) 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.) -- 1042300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib-d Version: 2.3.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with gnome >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 1.2.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: GlibD > Project version: 2.4.0 > D compiler for the host machine: ldc2 (llvm 1.30.0 "LDC - the LLVM D compiler > (1.30.0):") > D linker for the host machine: ldc2 ld.bfd 2.40.90.20230720 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Found pkg-config: /usr/bin/pkg-config (1.8.1) > Run-time dependency glib-2.0 found: YES 2.76.4 > Run-time dependency gmodule-2.0 found: YES 2.76.4 > Run-time dependency gobject-2.0 found: YES 2.76.4 > Run-time dependency gio-2.0 found: YES 2.76.4 > Run-time dependency gobject-introspection-1.0 found: YES 1.76.1 > Program girtod found: YES (/usr/bin/girtod) > Message: Generating D interfaces from GIR... > Build targets in project: 4 > > GlibD 2.4.0 > > User defined options > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > > Found ninja-1.11.1 at /usr/bin/ninja >dh_auto_build > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/349] ldc2 -I=libglibd-2.0.so.2.4.0.p -I=. -I=.. -I=generated > -I=../generated -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -enable-color -wi -O -g -release -wi > -relocation-model=pic > -makedeps=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_gtkd_paths.d.o.deps > -of=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_gtkd_paths.d.o -c > ../obj-x86_64-linux-gnu/generated/gtkd/paths.d > [2/349] ldc2 -I=libglibd-2.0.so.2.4.0.p -I=. -I=.. -I=generated > -I=../generated -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -enable-color -wi -O -g -release -wi > -relocation-model=pic > -makedeps=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_c_functions.d.o.deps > > -of=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_c_functions.d.o > -c ../obj-x86_64-linux-gnu/generated/glib/c/functions.d > [3/349] ldc2 -I=libglibd-2.0.so.2.4.0.p -I=. -I=.. -I=generated > -I=../generated -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount > -I/usr/include/blkid -enable-color -wi -O -g -release -wi > -relocation-model=pic > -makedeps=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_ArrayG.d.o.deps > -of=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_ArrayG.d.o > -c ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d > FAILED: > libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_ArrayG.d.o > ldc2 -I=libglibd-2.0.so.2.4.0.p -I=. -I=.. -I=generated -I=../generated > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/libmount -I/usr/include/blkid -enable-color -wi -O -g -release > -wi -relocation-model=pic > -makedeps=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_ArrayG.d.o.deps > -of=libglibd-2.0.so.2.4.0.p/obj-x86_64-linux-gnu_generated_glib_ArrayG.d.o > -c ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d > ../obj-x86_64-linux-gnu/generated/glib/ArrayG.d(324): Error: constructor > `glib.ArrayG.ArrayG.this(void*[] data, bool clear, ulong
Bug#1055173: marked as done (src:lwip: fails to migrate to testing for too long: FTBFS on s390x)
Your message dated Sun, 05 Nov 2023 18:35:13 + with message-id and subject line Bug#1055173: fixed in lwip 2.1.3+dfsg1-4 has caused the Debian Bug report #1055173, regarding src:lwip: fails to migrate to testing for too long: FTBFS on s390x 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.) -- 1055173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lwip Version: 2.1.3+dfsg1-2 Severity: serious Control: close -1 2.1.3+dfsg1-3 Tags: sid trixie ftbfs 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:lwip has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable failed to build on s390x. 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=lwip OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lwip Source-Version: 2.1.3+dfsg1-4 Done: Samuel Thibault We believe that the bug you reported is fixed in the latest version of lwip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated lwip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 05 Nov 2023 19:08:47 +0100 Source: lwip Architecture: source Version: 2.1.3+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Joan Lledó Changed-By: Samuel Thibault Closes: 1055173 Changes: lwip (2.1.3+dfsg1-4) unstable; urgency=medium . * Team upload. * patches/empty_block_last: Fix out-of-bound access when looking for empty blocks (Closes: Bug#1055173) Checksums-Sha1: d6c5907e3448d322ca720aa522ae3e06cf51e227 1994 lwip_2.1.3+dfsg1-4.dsc db706a23d8d87892182f84f9c7bc9f752b4f5c06 30356 lwip_2.1.3+dfsg1-4.debian.tar.xz b802532c0aebecb32afbbfc1bc8df1ad16b142dc 7618 lwip_2.1.3+dfsg1-4_amd64.buildinfo Checksums-Sha256: c5d77972258f1df1d0cbb2f3c6fdd15c81bb8a046df6bb1346209f1449714ec3 1994 lwip_2.1.3+dfsg1-4.dsc 9e03d539cf2df3e401c2280ed9eb2ff3d177d1e00d8d6a36698cf8eef335fbfe 30356 lwip_2.1.3+dfsg1-4.debian.tar.xz 566be0e637bd7f08ee9126fd32fa951d11330b919f49b38debaf0ca6da3bc7e2 7618 lwip_2.1.3+dfsg1-4_amd64.buildinfo Files: eabd1dfcf37a1b5fc938a1be87eb9310 1994 libs optional lwip_2.1.3+dfsg1-4.dsc 2ac0db839b496a6fd5b4ebfe1c0cc830 30356 libs optional lwip_2.1.3+dfsg1-4.debian.tar.xz dc76d9127776c04307e43eef02eb02d8 7618 libs optional lwip_2.1.3+dfsg1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi6MnFvk67auaclLJ5pG0tXV4H2IFAmVH3GsACgkQ5pG0tXV4 H2JLlw//RGvtoJoubX57d40uw9HUtk9tTOQv4ceUnRSwWr8iqhp4AuA5Zmy5TZBn g3dTCO4KT23ONIMT+EBQnNTvbiJRrwPNNAOBEP2qABB5LlPOvnDVILjd/H6yvEBG /FvnNg2Ags4eOiRMUewRE1jMy8A6fxR9QUtDOvVol9Kv3C8smxqJCXXNd6gTZpcX
Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl
Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt: > [...] > Do you have an idea how simple rebuilding the bullseye package on > buster would be? I'm happy to try that in general, but I've not really > looked at the Java ecosystem in Debian much. Sorry, I missed those new or updated dependencies. That complicates the matter a little. We also have to deal with clojure here, a LISP dialect of the Java language with a different build system (leiningen), but if all dependencies were in place a rebuild would be pretty simple. As a last resort I could bundle all those dependencies together with trapperkeeper-* the Java way TM but I hope we can avoid that. The most ideal solution is a patch for the current version in Buster. I have uploaded a new revision to people.debian.org with minimal changes here: https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/ dget - x https://people.debian.org/~apo/lts/buster/trapperkeeper-webserver-jetty9-clojure/ trapperkeeper-webserver-jetty9-clojure_1.7.0-2+deb10u1.1.dsc should work as expected. I'm attaching the debdiff as well. My solution is to replace the old SslContextFactory class with the new inner SslContextFactory.Server class but I don't know if this change has the desired effect because I couldn't test it. FTR, the already applied 0005-maint-Disable-EndpointIdentification.patch (new in version +deb10u1) is related to the problem. Actually back then it did "fix" the SSL problem and I'm a bit surprised it resurfaced now. There is also a third alternative. I could revert the split change in jetty9. https://github.com/jetty/jetty.project/pull/3480/files#diff-58640db0f8f2cd84b7e653d1c1540913 If the new revision doesn't work for you, please send me your puppetdb config, and I try to figure out a solution myself without the feedback loop delay. Thanks in advance. Regards, Markus diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog 2019-09-13 11:00:50.0 +0200 +++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/changelog 2023-11-05 18:06:31.0 +0100 @@ -1,3 +1,10 @@ +trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1.1) buster-security; urgency=medium + + * Non-maintainer upload. + * Replace deprecated class SslContextFactory with SslContextFactory.Server. + + -- Markus Koschany Sun, 05 Nov 2023 18:06:31 +0100 + trapperkeeper-webserver-jetty9-clojure (1.7.0-2+deb10u1) buster; urgency=medium [ Manfred Stock ] diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch 2019-09-13 10:54:48.0 +0200 +++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/0005-maint-Disable-EndpointIdentification.patch 2023-11-05 18:06:31.0 +0100 @@ -1,4 +1,3 @@ -From 9db4170381e07165078e544340e12b38676c2613 Mon Sep 17 00:00:00 2001 From: Justin Stoller Date: Fri, 24 May 2019 16:10:44 -0700 Subject: [PATCH] (maint) Disable EndpointIdentification @@ -30,10 +29,10 @@ 1 file changed, 1 insertion(+) diff --git a/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj b/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj -index 3a577bb..02e7c7d 100644 +index 99c9885..28cfef7 100644 --- a/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj +++ b/src/puppetlabs/trapperkeeper/services/webserver/jetty9_core.clj -@@ -197,6 +197,7 @@ +@@ -192,6 +192,7 @@ (.setKeyStore (:keystore keystore-config)) (.setKeyStorePassword (:key-password keystore-config)) (.setTrustStore (:truststore keystore-config)) @@ -41,6 +40,3 @@ ;; Need to clear out the default cipher suite exclude list so ;; that Jetty doesn't potentially remove one or more ciphers ;; that we want to be included. --- -2.20.1 - diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series --- trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series 2019-09-13 10:54:48.0 +0200 +++ trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/series 2023-11-05 18:06:31.0 +0100 @@ -3,3 +3,4 @@ 0003-TK-369-Add-LifeCycleImplementingRequestLogImpl.patch 0004-Implement-LifeCycle-methods-missing-from-RequestLogI.patch 0005-maint-Disable-EndpointIdentification.patch +SslContextFactory.patch diff -Nru trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.patch trapperkeeper-webserver-jetty9-clojure-1.7.0/debian/patches/SslContextFactory.patch
Processed: bug 1055173 is forwarded to https://savannah.nongnu.org/patch/index.php?10410
Processing commands for cont...@bugs.debian.org:
> forwarded 1055173 https://savannah.nongnu.org/patch/index.php?10410
Bug #1055173 {Done: Paul Gevers } [src:lwip] src:lwip: fails
to migrate to testing for too long: FTBFS on s390x
Set Bug forwarded-to-address to
'https://savannah.nongnu.org/patch/index.php?10410'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1055173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042597: python-amqp: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:20: override_dh_sphinxdoc] Error 2
Dear Maintainer, I can reproduce this issue with python3-sphinx 7.2.3-1 from snapshots.d.o but not with python3-sphinx 7.2.6-1 just uploaded in sid. I guess this upstream commit [1] fixed reported issue. Anyway your package still FTBFS with this message: Exception occurred: File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 112, in role title = caption % part This is caused by sphinx-celery not compatible with newer Sphinx. Please see this commit that fixes the problem [2] Kind Regards [1] https://github.com/sphinx-doc/sphinx/commit/2a631f97ef7f4b0edc247 [2] https://github.com/celery/sphinx_celery/commit/e2f88da7ad7c400dc5
Bug#1054946: marked as done (distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)
Your message dated Sun, 05 Nov 2023 17:47:25 + with message-id and subject line Bug#1054946: fixed in distro-info 1.5+deb12u1 has caused the Debian Bug report #1054946, regarding distro-info: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054946 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: distro-info Version: 1.6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./test-debian-distro-info > cd perl && ./test.pl > testAlias > testAll > py3versions: no X-Python3-Version in control file, using supported versions > testDevel > cd python && python3.11 setup.py test > 1..35 > ok 1 - unique: Matching lists > ok 2 - symmetric_difference: Matching lists > ok 3 - unique: 1 Unique Item > ok 4 - unique: 1 Unique Item in the haystack > ok 5 - symmetric_difference: 1 Unique Item > ok 6 - Debian all > ok 7 - Debian devel > ok 8 - Debian oldstable > ok 9 - Debian stable > ok 10 - Debian testing > ok 11 - Debian valid > ok 12 - Debian valid > ok 13 - Debian invalid > ok 14 - Debian supported > ok 15 - Debian LTS > ok 16 - Debian ELTS > ok 17 - Debian unsupported > ok 18 - Debian codename, invalid > ok 19 - Debian codename > ok 20 - Debian version, invalid > ok 21 - Debian version > testOldstable > ok 22 - Ubuntu all > ok 23 - Ubuntu version > ok 24 - Ubuntu LTS version > ok 25 - Ubuntu devel > ok 26 - Ubuntu LTS > ok 27 - Ubuntu stable > ok 28 - Ubuntu valid > ok 29 - Ubuntu invalid > ok 30 - Ubuntu is_lts > ok 31 - Ubuntu !is_lts > ok 32 - Ubuntu !is_lts > ok 33 - Ubuntu supported > ok 34 - Ubuntu ESM > ok 35 - Ubuntu unsupported > testStable > testSupported > testLTS > testELTS > testUnsupported > testTesting > testFullname > running test > WARNING: Testing via this command is deprecated and will be removed in a > future version. Users looking for a generic test entry point independent of > test runner are encouraged to use tox. > /usr/lib/python3/dist-packages/setuptools/command/test.py:193: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > ir_d = dist.fetch_build_eggs(dist.install_requires) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:194: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > tr_d = dist.fetch_build_eggs(dist.tests_require or []) > WARNING: The wheel package is not available. > /usr/lib/python3/dist-packages/setuptools/command/test.py:195: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > !! > > > > Requirements should be satisfied by a PEP 517 installer. > If you are using pip, you can try `pip install --use-pep517`. > > > > !! > er_d = dist.fetch_build_eggs( > WARNING: The wheel package is not available. > running egg_info > creating distro_info.egg-info > writing distro_info.egg-info/PKG-INFO > writing dependency_links to distro_info.egg-info/dependency_links.txt > writing top-level names to distro_info.egg-info/top_level.txt > writing manifest file 'distro_info.egg-info/SOURCES.txt' > testRelease > reading manifest file 'distro_info.egg-info/SOURCES.txt' > writing manifest file 'distro_info.egg-info/SOURCES.txt' > running build_ext > testSeries > testCombinedShortform > test_flake8 (distro_info_test.test_flake8.Flake8TestCase.test_flake8) > Test: Run flake8 on Python source
Bug#1051729: marked as done (pmix: CVE-2023-41915)
Your message dated Sun, 05 Nov 2023 17:47:28 + with message-id and subject line Bug#1051729: fixed in pmix 4.2.2-1+deb12u1 has caused the Debian Bug report #1051729, regarding pmix: CVE-2023-41915 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.) -- 1051729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pmix Version: 5.0.0~rc1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for pmix. CVE-2023-41915[0]: | OpenPMIx PMIx before 4.2.6 and 5.0.x before 5.0.1 allows attackers | to obtain ownership of arbitrary files via a race condition during | execution of library code with UID 0. As mentioned in [2]: | A filesystem race condition could permit a malicious user | to obtain ownership of an arbitrary file on the filesystem | when parts of the PMIx library are called by a process | running as uid 0. This may happen under the default | configuration of certain workload managers, including Slurm. (fs.protected_symlinks not protecting in such a case) Please downgrade the severity if you do not agree on the assessment, but at a very start the unstable version should be fixed. We can have a look what need to be done for bookworm and bullseye in next step. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-41915 https://www.cve.org/CVERecord?id=CVE-2023-41915 [1] https://github.com/openpmix/openpmix/commit/0bf9801a3017eb6ca411e158da39570ccb998c17 [2] https://github.com/openpmix/openpmix/releases/tag/v5.0.1 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: pmix Source-Version: 4.2.2-1+deb12u1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of pmix, 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 1051...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated pmix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 Oct 2023 17:04:42 +0200 Source: pmix Architecture: source Version: 4.2.2-1+deb12u1 Distribution: bookworm-security Urgency: high Maintainer: Alastair McKinstry Changed-By: Salvatore Bonaccorso Closes: 1051729 Changes: pmix (4.2.2-1+deb12u1) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * Do not follow links when doing "chown" (CVE-2023-41915) (Closes: #1051729) Checksums-Sha1: 609d86679a40e4f219cef96b3d5287f550391352 2497 pmix_4.2.2-1+deb12u1.dsc f4f89bbe2b8c703a085f77e35410a149dd1a98b3 885680 pmix_4.2.2.orig.tar.xz 8b28c97042fea0d3d2c5a3cc2bf3faf3ef90dd25 11992 pmix_4.2.2-1+deb12u1.debian.tar.xz 02f45da205536acdc4055ef3d8a467a94e5885cc 7879 pmix_4.2.2-1+deb12u1_source.buildinfo Checksums-Sha256: fea5e777fff0ef7afa76117573bc5629c349cfcedf64b3370dc4d05a6646ef3e 2497 pmix_4.2.2-1+deb12u1.dsc 4a534a8f87220c6f0d1b4b3195820f585ffaf3ceb8e21e40460d58439b81d47b 885680 pmix_4.2.2.orig.tar.xz 92a012d218f08c3e8868ec5c1d2e23f23051c7805f56dccf6d852df84569a1de 11992 pmix_4.2.2-1+deb12u1.debian.tar.xz d940ca5f926ac0990f9a67683e635442d61f5bf2d58432bc6acb0bfe1a1885dd 7879 pmix_4.2.2-1+deb12u1_source.buildinfo Files: a4b8f258d79514d1d58541cf88b8846e 2497 net optional pmix_4.2.2-1+deb12u1.dsc c288751ba1c98de2b070f7ac64d07281 885680 net optional pmix_4.2.2.orig.tar.xz 28803d1047a7c9c754a292cb2d51c9f0 11992 net optional pmix_4.2.2-1+deb12u1.debian.tar.xz b14294d7b21c885c5c5c4c7107d2882e 7879 net optional pmix_4.2.2-1+deb12u1_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmU9Mv9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
Processed: reopen 1042668
Processing commands for cont...@bugs.debian.org:
> reopen 1042668
Bug #1042668 {Done: Thomas Goirand } [src:python-pbr]
python-pbr: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command
'build_sphinx'pbr.tests.test_core.TestCore.test_setup_py_build_sphinx
Bug reopened
Ignoring request to alter fixed versions of bug #1042668 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1042668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1055348: jetty9: Update from DLA 3641 breaks puppetdb ("Exception in thread "main" java.lang.IllegalStateException: KeyStores with multiple certificates are not supported on the base class org.ecl
On Sat, 2023-11-04 at 20:33 +0100, Markus Koschany wrote: > Could you install the version of trapperkeeper-webserver-jetty9- > clojure from Bullseye and reinstall the jetty9 security update and > report back if this solves your problem? Doing that directly doesn't "just work": libtrapperkeeper-webserver-jetty9-clojure : Depends: libkitchensink-clojure (>= 3.1.1-2) but 2.3.0-2 is to be installed Depends: libprismatic-schema-clojure (>= 1.1.12) but 1.1.6-1 is to be installed Depends: libpuppetlabs-i18n-clojure (>= 0.9.0-2) but 0.8.0-1 is to be installed Depends: libring-codec-clojure (>= 1.1.2) but 1.0.1-1 is to be installed Depends: libssl-utils-clojure (>= 3.1.0) but 0.8.3-2 is to be installed Depends: libtrapperkeeper-clojure (>= 3.1.0) but 1.5.2-2 is to be installed Depends: libtrapperkeeper-filesystem-watcher-clojure (>= 1.2.2-2) but it is not installable Depends: libordered-clojure but it is not installable Adding a bullseye APT source ends up at "19 upgraded, 5 newly installed". Do you have an idea how simple rebuilding the bullseye package on buster would be? I'm happy to try that in general, but I've not really looked at the Java ecosystem in Debian much. Regards, Adam
Bug#1039883: The issue impacts SSD disks as well
Hello
I'm sorry for the delay.
> Are you able to reliably preoeduce the issue and can bisect it to the
> introducing commit?
I faced this issue on real data but I struggled to find a reliable scenario to
reproduce it. Here is what I just came up with:
sudo mkfs -t ext4 -O fast_commit,inline_data /dev/sdb
sudo mount /dev/sdb /mnt/
sudo install -d -o myuser /mnt/annex
cd /mnt/annex
git init && git annex init
for i in {1..2}; do
for i in {1..1}; do
dd if=/dev/urandom of=file-${i} bs=1K count=1 2>/dev/null
done
git annex add -J cpus . >/dev/null && git annex sync -J cpus && git annex
fsck -J cpus >/dev/null
git rm * && git annex sync && git annex dropunused all
done
Then at some point the following error appears:
EXT4-fs error (device sdb): ext4_map_blocks:577: inode #3942343: block 4:
comm git-annex:w: lblock 1 mapped to illegal pblock 4 (length 1)
Some observations:
- Contrary to what I implied in my first message, using the option
inline_data alone doesn't seem to trigger the error.
- Working with less than 10K files doesn't seem to trigger the error
- Sometimes the commands just run fine that's why I run the whole thing twice
- I also tried with various file size, in particular 1B, but it does not seem
to have any impact
- The disk I was using is a 5400RPM HDD
I'm running the kernel 6.5.0-3-amd64.
I'm also getting this issue on Debian stable's kernel (6.1.0-13-amd64) so I'm
not aware of any working kernel version.
Regards
Hervé
Bug#1054757: marked as done (blends: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1)
Your message dated Sun, 05 Nov 2023 16:04:02 +
with message-id
and subject line Bug#1054757: fixed in blends 0.7.6
has caused the Debian Bug report #1054757,
regarding blends: FTBFS: make[1]: *** [debian/rules:20: override_dh_auto_test]
Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blends
Version: 0.7.5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pytest-3 --doctest-modules
> = test session starts
> ==
> platform linux -- Python 3.11.6, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 8 items
>
> blends.py F..F
> [100%]
>
> === FAILURES
> ===
> [doctest] blends.Task.fix_dependencies
>
> 469 celestia-gnome | celestia-glut
> 470 starplot
> 471 gravit
> 472 >>> for dep in task.suggests:
> 473 ... print(dep.rawstr)
> 474 sunclock
> 475 xtide
> 476 >>> task += apt.Cache()
> 477 >>> missing = task.fix_dependencies()
> 478 >>> for dep in task.recommends:
> Expected:
> starplot
> gravit
> Got:
> gravit
>
> /<>/blends.py:478: DocTestFailure
> _ [doctest] blends.Task.update
> _
> 434 Instead of using ``update()``, also the ``+=`` operator can be
> used:
> 435
> 436 >>> import apt
> 437 >>> with open('education') as fp:
> 438 ... task = Task('debian-astro', 'education', fp)
> 439 >>> dep = task.recommends[1][0]
> 440 >>> print(dep.name + ": ", dep.summary)
> 441 starplot: None
> 442 >>> task += apt.Cache()
> 443 >>> print(dep.name + ": ", dep.summary)
> Expected:
> starplot: 3-dimensional perspective star map viewer
> Got:
> starplot: None
>
> /<>/blends.py:443: DocTestFailure
> === short test summary info
>
> FAILED blends.py::blends.Task.fix_dependencies
> FAILED blends.py::blends.Task.update
> = 2 failed, 6 passed in 0.95s
> ==
> make[1]: *** [debian/rules:20: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/blends_0.7.5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: blends
Source-Version: 0.7.6
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
blends, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated blends package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 Nov 2023 16:23:11 +0100
Source: blends
Architecture: source
Version: 0.7.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Pure Blend Team
Changed-By: Ole Streicher
Closes: 1050621 1054757
Changes:
blends (0.7.6)
Bug#1055418: systemtap: autopkgtest regression: Pass 4: compilation failed. [man error::pass4]
Source: systemtap Version: 4.9-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails since a couple of months. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. 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 https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/39374282/log.gz 223s /usr/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct module’ has no member named ‘core_text_size’; did you mean ‘kprobes_text_size’? 223s 367 |(unsigned long) (THIS_MODULE->core_text_size)/1024, 223s | ^~ 223s /usr/src/linux-headers-6.5.0-3-common/include/linux/printk.h:427:33: note: in definition of macro ‘printk_index_wrap’ 223s 427 | _p_func(_fmt, ##__VA_ARGS__); \ 223s | ^~~ 223s /usr/share/systemtap/runtime/linux/print.c:348:9: note: in expansion of macro ‘printk’ 223s 348 | printk(KERN_DEBUG 223s | ^~ 223s cc1: all warnings being treated as errors 223s make[1]: *** [/usr/src/linux-headers-6.5.0-3-common/scripts/Makefile.build:248: /tmp/stapUiwpzl/hello_src.o] Error 1 223s make: *** [/usr/src/linux-headers-6.5.0-3-common/Makefile:2059: /tmp/stapUiwpzl] Error 2 223s WARNING: kbuild exited with status: 2 223s Pass 4: compiled C into "hello.ko" in 35730usr/7150sys/22477real ms. 223s Pass 4: compilation failed. [man error::pass4] 223s Tip: /usr/share/doc/systemtap/README.Debian should help you get started. 224s autopkgtest [08:12:49]: test build-hello: ---] OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054433: node-puppeteer: website is build with Docusaurus not packaged for debian
Control: severity -1 important Hi, It seems that already repacked. Surely regenerating omitted content (website and docs) may be recommended in the future, so marked as important. Regards,
Processed: Re: node-puppeteer: website is build with Docusaurus not packaged for debian
Processing control commands: > severity -1 important Bug #1054433 [src:fasttext] fasttext: website is build with Docusaurus not packaged for debian Severity set to 'important' from 'serious' -- 1054433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4.
Processing control commands: > affects -1 src:openssl Bug #1055416 [nodejs] nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4. Added indication that 1055416 affects src:openssl -- 1055416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055416: nodejs: Testsuite failure in test-crypto-dh since OpenSSL 3.0.12/3.1.4.
Package: nodejs
Version: 18.13.0+dfsg1-1
Severity: Serious
Tags: patch
control: affects -1 src:openssl
OpenSSL 3.0.12 and 3.1.4 changed the error response resulting a failure
in test parallel/test-crypto-dh.
This has been addressed in the master branch in commit
8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")
An additional problem is that the check compares OpenSSL from compile
time not runtime. Which means I couldn't test upstream's version as-is.
The attached version takes always the 3.0.12/3.1.4 variant. Given that
the new upload picks up the new OpenSSL vesion then it should be okay to
apply the original commit.
Sebastian
From: Sebastian Andrzej Siewior
Date: Sun, 5 Nov 2023 13:08:23 +0100
Subject: [PATCH] test: Alter error message.
This is variant of upstream's commit
8eea2d3709090 ("test: fix crypto-dh error message for OpenSSL 3.x")
It does not work as-is in Debian because the testsuite may run against a
different version than the compiled once and the constant version check
does not apply.
Signed-off-by: Sebastian Andrzej Siewior
---
test/parallel/test-crypto-dh.js | 4 +---
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/test/parallel/test-crypto-dh.js b/test/parallel/test-crypto-dh.js
index 18721fcf289e..506780db4cbe 100644
--- a/test/parallel/test-crypto-dh.js
+++ b/test/parallel/test-crypto-dh.js
@@ -165,9 +165,7 @@ if (common.hasOpenSSL3) {
assert.throws(() => {
dh3.computeSecret('');
-}, { message: common.hasOpenSSL3 ?
- 'error:02800080:Diffie-Hellman routines::invalid secret' :
- 'Supplied key is too small' });
+}, { message: 'Supplied key is too small' });
// Invalid test: curve argument is undefined
assert.throws(
--
2.42.0
Bug#1054960: marked as done (lambdabot: FTBFS: unsatisfiable build-dependencies)
Your message dated Sun, 05 Nov 2023 15:10:00 + with message-id and subject line Bug#1054960: fixed in lambdabot 5.3.1.1-1 has caused the Debian Bug report #1054960, regarding lambdabot: FTBFS: unsatisfiable build-dependencies 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.) -- 1054960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lambdabot Version: 5.3.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cdbs, haskell-devscripts (>= 0.13), debhelper (>= 10), > ghc (>= 8.4.3), libghc-lambdabot-core-dev (>= 5.3), libghc-lambdabot-core-dev > (<< 5.4), libghc-lambdabot-haskell-plugins-dev (>= 5.3), > libghc-lambdabot-haskell-plugins-dev (<< 5.4), > libghc-lambdabot-irc-plugins-dev (>= 5.3), libghc-lambdabot-irc-plugins-dev > (<< 5.4), libghc-lambdabot-misc-plugins-dev (>= 5.3), > libghc-lambdabot-misc-plugins-dev (<< 5.4), > libghc-lambdabot-novelty-plugins-dev (>= 5.3), > libghc-lambdabot-novelty-plugins-dev (<< 5.4), > libghc-lambdabot-reference-plugins-dev (>= 5.3), > libghc-lambdabot-reference-plugins-dev (<< 5.4), > libghc-lambdabot-social-plugins-dev (>= 5.3), > libghc-lambdabot-social-plugins-dev (<< 5.4), build-essential, fakeroot > Filtered Build-Depends: cdbs, haskell-devscripts (>= 0.13), debhelper (>= > 10), ghc (>= 8.4.3), libghc-lambdabot-core-dev (>= 5.3), > libghc-lambdabot-core-dev (<< 5.4), libghc-lambdabot-haskell-plugins-dev (>= > 5.3), libghc-lambdabot-haskell-plugins-dev (<< 5.4), > libghc-lambdabot-irc-plugins-dev (>= 5.3), libghc-lambdabot-irc-plugins-dev > (<< 5.4), libghc-lambdabot-misc-plugins-dev (>= 5.3), > libghc-lambdabot-misc-plugins-dev (<< 5.4), > libghc-lambdabot-novelty-plugins-dev (>= 5.3), > libghc-lambdabot-novelty-plugins-dev (<< 5.4), > libghc-lambdabot-reference-plugins-dev (>= 5.3), > libghc-lambdabot-reference-plugins-dev (<< 5.4), > libghc-lambdabot-social-plugins-dev (>= 5.3), > libghc-lambdabot-social-plugins-dev (<< 5.4), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1287 B] > Get:5 copy:/<>/apt_archive ./ Packages [1319 B] > Fetched 3221 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libghc-lambdabot-core-dev : Depends: libghc-base-dev-4.15.1.0-6a406 but it > is not installable > Depends: libghc-binary-dev-0.8.8.0-507cc but it > is not installable > Depends: libghc-bytestring-dev-0.10.12.1-ced9a > but it is not installable > Depends: libghc-containers-dev-0.6.4.1-31c3b but > it is not installable > Depends: libghc-dependent-map-dev-0.4.0.0-f824e > but it is not installable > Depends: libghc-dependent-sum-dev-0.7.1.0-2fd03 > but it is not installable > Depends: > libghc-dependent-sum-template-dev-0.1.1.1-62abf but it is not installable > Depends: libghc-directory-dev-1.3.6.2-311c9 but > it is not installable > Depends: libghc-edit-distance-dev-0.2.2.1-cc475 > but it is not installable > Depends:
Bug#1054802: marked as done (mate-menu: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_clean] Error 25)
Your message dated Sun, 05 Nov 2023 14:47:09 +
with message-id
and subject line Bug#1054802: fixed in mate-menu 22.04.2-2
has caused the Debian Bug report #1054802,
regarding mate-menu: FTBFS: make[1]: *** [debian/rules:18:
override_dh_auto_clean] Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-menu
Version: 22.04.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> test -f po/mate-menu.pot.bak && mv po/mate-menu.pot.bak po/mate-menu.pot ||
> true
> rm -Rf mate_menu.egg-info/
> # dh_auto_clean with pybuild/distutils only works if setup.py is
> # present
> if [ -f setup.py ]; then \
> dh_auto_clean; \
> fi
> I: pybuild base:310: python3.11 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/dist.py:508: InformationOnly:
> Normalizing '22.04.1' to '22.4.1'
> self.metadata.version = self._normalize_version(
> running clean
> error: error in /<>/.pybuild/cpython3_3.11/.pydistutils.cfg:
> command 'clean_i18n' has no such option 'all'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make[1]: *** [debian/rules:18: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/mate-menu_22.04.2-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: mate-menu
Source-Version: 22.04.2-2
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
mate-menu, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated mate-menu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 05 Nov 2023 14:02:54 +
Source: mate-menu
Architecture: source
Version: 22.04.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team
Changed-By: Mike Gabriel
Closes: 1054802
Changes:
mate-menu (22.04.2-2) unstable; urgency=medium
.
* debian/patches:
+ Add 0001_fix-upstream-version.patch, 0002_fix-categories-without-
icon.patch (cherry-picked from upstream PRs).
+ Add 1001_py-setup-clean-i18n.patch: Stop using clean_i18n class from
distutils.extra. (Closes: #1054802).
* debian/control:
+ Bump Standards-Version: to 4.6.2. No changes needed.
Checksums-Sha1:
35603b8c43ed0475956295ba4fa258b303046c88 2125 mate-menu_22.04.2-2.dsc
5da3377e27e2bf2f4fe18e2b50544b885573a01f 7840 mate-menu_22.04.2-2.debian.tar.xz
55c4ebcf6205c95fab4f8d676db6b3390624c829 8290
mate-menu_22.04.2-2_source.buildinfo
Checksums-Sha256:
b8dccfca6bda70f5a70e5d2f010c037e081e315f461a02d0675ffe14ac491d73 2125
mate-menu_22.04.2-2.dsc
5362d7d05fedfe1ec96e2a0aa937e8bfcda4f03950046acb566cd2815f92437f 7840
mate-menu_22.04.2-2.debian.tar.xz
2566d95bcc4e57997ed4e3f9b485f719034cbbc857bdc11088ba6561b9664197 8290
mate-menu_22.04.2-2_source.buildinfo
Files:
ce3c871065fdda86a6efa805a51306b3 2125 x11 optional
Bug#1054785: marked as done (magnus: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25)
Your message dated Sun, 05 Nov 2023 14:47:00 +
with message-id
and subject line Bug#1054785: fixed in magnus 1:1.0.3-4
has caused the Debian Bug report #1054785,
regarding magnus: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean]
Error 25
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1054785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: magnus
Version: 1:1.0.3-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -Rf Magnus.egg-info/
> # dh_auto_clean with pybuild/distutils only works if setup.py is
> # present
> if [ -f setup.py ]; then \
> dh_auto_clean; \
> fi
> I: pybuild base:310: python3.11 setup.py clean
> running clean
> error: error in /<>/.pybuild/cpython3_3.11/.pydistutils.cfg:
> command 'clean_i18n' has no such option 'all'
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/10/27/magnus_1.0.3-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: magnus
Source-Version: 1:1.0.3-4
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
magnus, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1054...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated magnus package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 05 Nov 2023 13:46:40 +
Source: magnus
Architecture: source
Version: 1:1.0.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team
Changed-By: Mike Gabriel
Closes: 1054785
Changes:
magnus (1:1.0.3-4) unstable; urgency=medium
.
* debian/control:
+ Add Rules-Requires-Root: field and set it to no.
+ Bump Standards-Version: to 4.6.2. No changes needed.
* debian/upstream/metadata:
+ Drop obsolete fields Contact: and Name:.
* debian/patches:
+ Add 1001_py-setup-no-i18n.patch. Fix FTBFS issue due to clean_i18n target
by dropping all i18n functionality. The 'magnus' tool does not come with
translation files. (Closes: #1054785).
Checksums-Sha1:
e5a640f44d5be8ba5de88b70a97db89c1b957d26 2042 magnus_1.0.3-4.dsc
6c5afbb7322b49d1ee75650d29754191fa5d1b74 3632 magnus_1.0.3-4.debian.tar.xz
92da0ff1cbb5345561ab1aa0ccf2caadda3e6c2d 8272 magnus_1.0.3-4_source.buildinfo
Checksums-Sha256:
59f68ac3086a6d4422720eea149921e2f88ebbef11a4c4505734e358754d3593 2042
magnus_1.0.3-4.dsc
7d68c17be9827cc26d48e6041b4f0be3348687a0fadaf16cec70cf4e66ac29e3 3632
magnus_1.0.3-4.debian.tar.xz
735892ee84f4b23e398475f1e1dcad23255b0861ab04ca0413fe678fab8aac83 8272
magnus_1.0.3-4_source.buildinfo
Files:
f9409664c5f0bf7f591f37b7eb1ee83c 2042 utils optional magnus_1.0.3-4.dsc
4ff561eef58e9dcf15228a9c978ab4a8 3632 utils optional
magnus_1.0.3-4.debian.tar.xz
7ed421f978c99d9415f4b74286c91db1 8272 utils optional
magnus_1.0.3-4_source.buildinfo
-BEGIN PGP SIGNATURE-
Bug#1055414: bedtools: FTBFS on i386: "intersect" tool failure
Source: bedtools Version: 2.31.0+dfsg-1 Severity: serious Tags: ftbfs Justification: ftbfs Dear Maintainer, While making a routine metadata update on a Debian patch against bedtools, Salsa CI caught a build failure on i386[1] which I could reproduce multiple times in sid and in testing with the unmodified version of the package. [1]: https://salsa.debian.org/med-team/bedtools/-/jobs/4891166 The relevant part of the build log shows the following differences in the test suite of the "intersect" tool: intersect.t22.p...0a1 > chr1 0 30 one_block_one_exon_30bp 40 - 0 30 0,0,0 1 30, 0, chr1 0 100 exon1 1 + 30 fail intersect.t22.q...1a2 > chr1 80 110 one_block_one_exon_20bp 40 - 80 110 0,0,0 1 30, 0, chr1 0 100 exon1 1 + 20 fail The tests are started from test/intersect/test-intersect.sh. I'm not sure what change caused the build failure to appear. The issue is not affecting amd64, nor armhf, which suggest something very i386 specific. I have not checked closely the other CPU architectures yet. The relevant upstream change that introduced this code begins to date back from quite some time ago[2] and the package builds with -ffloat-store for a while, so this may be caused by a dependency, or a compiler change. [2]: https://github.com/arq5x/bedtools2/commit/9d22ccb24f258553b0eff31e689b09563227331b Hope this helps pinpointing what's up, Étienne. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.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 -- .''`. Étienne Mollier : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/7, please excuse my verbosity `-on air: Condition Red - Let It All Come Out signature.asc Description: PGP signature
Bug#1054802: marked as pending in mate-menu
Control: tag -1 pending Hello, Bug #1054802 in mate-menu reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-mate-team/mate-menu/-/commit/0cace887f7a70559375c37c397d26fe6dba572ac debian/patches: Add 0001_fix-upstream-version.patch, 0002_fix-categories-without-icon.patch (cherry-picked from upstream PRs). Add 1001_py-setup-clean-i18n.patch: Stop using clean_i18n class from distutils.extra. (Closes: #1054802). (this message was generated automatically) -- Greetings https://bugs.debian.org/1054802
Processed: Bug#1054802 marked as pending in mate-menu
Processing control commands: > tag -1 pending Bug #1054802 [src:mate-menu] mate-menu: FTBFS: make[1]: *** [debian/rules:18: override_dh_auto_clean] Error 25 Added tag(s) pending. -- 1054802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1054785 marked as pending in magnus
Processing control commands: > tag -1 pending Bug #1054785 [src:magnus] magnus: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25 Added tag(s) pending. -- 1054785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054785: marked as pending in magnus
Control: tag -1 pending Hello, Bug #1054785 in magnus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-mate-team/magnus/-/commit/51b5020293e6403ef91001e7cf2c32cf66458697 debian/patches: Add 1001_py-setup-no-i18n.patch. Fix FTBFS issue due to clean_i18n target by dropping all i18n functionality. The 'magnus' tool does not come with translation files. (Closes: #1054785). (this message was generated automatically) -- Greetings https://bugs.debian.org/1054785
Processed: src:python-pymemcache: fails to migrate to testing for too long: autopkgtest regression on 32 bits
Processing control commands: > close -1 4.0.0-5 Bug #1055394 [src:python-pymemcache] src:python-pymemcache: fails to migrate to testing for too long: autopkgtest regression on 32 bits Marked as fixed in versions python-pymemcache/4.0.0-5. Bug #1055394 [src:python-pymemcache] src:python-pymemcache: fails to migrate to testing for too long: autopkgtest regression on 32 bits Marked Bug as done -- 1055394: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055394: src:python-pymemcache: fails to migrate to testing for too long: autopkgtest regression on 32 bits
Source: python-pymemcache Version: 3.5.2-2 Severity: serious Control: close -1 4.0.0-5 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-pymemcache has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable fails its own autopkgtest on 32 bit architectures: armel, armhf and i386. armhf and i386 also fail on reproducible-builds.org with the same test error. 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-pymemcache OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051863: marked as done (ldc: FTBFS with llvm-toolchain-16 as default)
Your message dated Sun, 05 Nov 2023 13:00:13 +
with message-id
and subject line Bug#1051863: fixed in ldc 1:1.35.0-1
has caused the Debian Bug report #1051863,
regarding ldc: FTBFS with llvm-toolchain-16 as default
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.)
--
1051863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldc
Version: 1:1.30.0-1
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=ldc=amd64=1%3A1.30.0-1%2Bb2=1694629363=0
[ 14%] Building CXX object CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o
/usr/bin/c++ -DLDC_ENABLE_PLUGINS -DLDC_LLVM_SUPPORTED_TARGET_AArch64=1
-DLDC_LLVM_SUPPORTED_TARGET_AMDGPU=1 -DLDC_LLVM_SUPPORTED_TARGET_ARM=1
-DLDC_LLVM_SUPPORTED_TARGET_AVR=1 -DLDC_LLVM_SUPPORTED_TARGET_BPF=1
-DLDC_LLVM_SUPPORTED_TARGET_Hexagon=1 -DLDC_LLVM_SUPPORTED_TARGET_Lanai=1
-DLDC_LLVM_SUPPORTED_TARGET_LoongArch=1 -DLDC_LLVM_SUPPORTED_TARGET_M68k=1
-DLDC_LLVM_SUPPORTED_TARGET_MSP430=1 -DLDC_LLVM_SUPPORTED_TARGET_Mips=1
-DLDC_LLVM_SUPPORTED_TARGET_NVPTX=1 -DLDC_LLVM_SUPPORTED_TARGET_PowerPC=1
-DLDC_LLVM_SUPPORTED_TARGET_RISCV=1 -DLDC_LLVM_SUPPORTED_TARGET_Sparc=1
-DLDC_LLVM_SUPPORTED_TARGET_SystemZ=1 -DLDC_LLVM_SUPPORTED_TARGET_VE=1
-DLDC_LLVM_SUPPORTED_TARGET_WebAssembly=1 -DLDC_LLVM_SUPPORTED_TARGET_X86=1
-DLDC_LLVM_SUPPORTED_TARGET_XCore=1 -DLDC_LLVM_SUPPORTED_TARGET_Xtensa=1
-I/<>/. -I/<>/dmd -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DDMDV2
-I/usr/lib/llvm-16/include -std=c++17 -fno-exceptions -D_GNU_SOURCE
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -fno-rtti
-Wall -Wextra -Wno-unused-parameter -Wno-comment
-Wno-missing-field-initializers -Wno-non-virtual-dtor -Wno-pedantic
-fvisibility-inlines-hidden -DLDC_POSIX -DIN_LLVM -DOPAQUE_VTBLS
"-DLDC_INSTALL_PREFIX=R\"(/usr)\"" -DLDC_LLVM_VER=1600
"-DLDC_LIBDIR_SUFFIX=R\"()\"" -DLDC_HOST_GDMD=1 -DLDC_HOST_FE_VER=2103
"-DLDC_LLVM_LIBDIR=R\"(/usr/lib/llvm-16/lib)\"" -DNDEBUG -MD -MT
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o -MF
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o.d -o
CMakeFiles/LDCShared.dir/gen/asm-gcc.cpp.o -c /<>/gen/asm-gcc.cpp
In file included from /<>/gen/abi-x86.cpp:12:
/<>/./gen/abi-generic.h: In member function ‘virtual llvm::Value*
BaseBitcastABIRewrite::put(DValue*, bool, bool)’:
/<>/./gen/abi-generic.h:142:68: warning: ‘llvm::Type*
llvm::Type::getPointerElementType() const’ is deprecated: Deprecated without
replacement, see https://llvm.org/docs/OpaquePointers.html for context and
migration instructions [-Wdeprecated-declarations]
142 | LLType *pointeeType = address->getType()->getPointerElementType();
| ~^~
In file included from /<>/./gen/llvm.h:20,
from /<>/./gen/attributes.h:12,
from /<>/./gen/tollvm.h:22,
from /<>/./gen/dibuilder.h:12,
from /<>/./gen/irstate.h:18,
from /<>/./gen/abi-generic.h:17:
/usr/lib/llvm-16/include/llvm/IR/Type.h:409:9: note: declared here
409 | Type *getPointerElementType() const {
| ^
/<>/gen/abi-x86.cpp: In member function ‘void
X86TargetABI::workaroundIssue1356(std::vector&) const’:
/<>/gen/abi-x86.cpp:270:41: error: ‘struct llvm::MaybeAlign’ has
no member named ‘getValueOr’
270 | if (arg->attrs.getAlignment().getValueOr(align4) > align4)
| ^~
make[4]: *** [CMakeFiles/LDCShared.dir/build.make:219:
CMakeFiles/LDCShared.dir/gen/abi-x86.cpp.o] Error 1
make[4]: *** Waiting for unfinished jobs
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ldc
Source-Version: 1:1.35.0-1
Done: Matthias Klumpp
We believe that the bug you reported is fixed in the latest version of
ldc, 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 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klumpp
Bug#1033512: marked as done (zc.buildout: autopkgtest fails: cannot open /usr/share/python3-zope.testing/test_helper)
Your message dated Sun, 05 Nov 2023 12:51:13 + with message-id and subject line Bug#1033512: fixed in zc.buildout 2.13.2-5 has caused the Debian Bug report #1033512, regarding zc.buildout: autopkgtest fails: cannot open /usr/share/python3-zope.testing/test_helper 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.) -- 1033512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zc.buildout Version: 2.13.2-4 Severity: serious Tags: bookworm-ignore User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. 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 https://ci.debian.net/data/autopkgtest/testing/amd64/z/zc.buildout/32140722/log.gz autopkgtest [06:23:21]: test all: [--- /tmp/autopkgtest-lxc.4d5588j5/downtmp/build.MKN/src/debian/tests/all: 2: .: cannot open /usr/share/python3-zope.testing/test_helper: No such file autopkgtest [06:23:22]: test all: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: zc.buildout Source-Version: 2.13.2-5 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of zc.buildout, 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. Paul Gevers (supplier of updated zc.buildout package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Nov 2023 13:29:23 +0100 Source: zc.buildout Architecture: source Version: 2.13.2-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Paul Gevers Closes: 1033512 Changes: zc.buildout (2.13.2-5) unstable; urgency=medium . * QA upload * tests: drop test, needed support file doesn't exist (Closes: #1033512) * d/control: drop ancient XS-Testsuite: autopkgtest Checksums-Sha1: 003bd7692cca78ba46ebbacf4b94988fdf230e31 1585 zc.buildout_2.13.2-5.dsc a9ed14ade4c4cc9f1346460117f9295b8c0978c9 4116 zc.buildout_2.13.2-5.debian.tar.xz Checksums-Sha256: a742b4b09e32a5138fd1868811ba76200d697b6f061d5390cefc8bd39709e239 1585 zc.buildout_2.13.2-5.dsc bfa28d45f5e522c29c25730f90d063aef6e4fdd7ce496c4048e91621dd01b229 4116 zc.buildout_2.13.2-5.debian.tar.xz Files: a6004703502b5cd704bfe8805858f182 1585 zope optional zc.buildout_2.13.2-5.dsc 301bec5b8cc623bfe09988ad492acb13 4116 zope optional zc.buildout_2.13.2-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmVHjIQACgkQnFyZ6wW9 dQoNqggAhszALv/mWEZ3ZaR5SW6YoXza9cRnXIN+qsov7GBuV41P9cNIPp3aD1Jo kADbKo053DtwD24iqKBMjrigeHfRYwYmlg2kOdzzmJebIgyb5RiSWcRxoHP/404J cCEArAkwK/wNmg9iEpgPkqXTDGfL79xh61k+dHK/tvnINA6E3xZkeEI1qxH2tbAQ 8zGMXsbVdDwW24lIHixi1kuNZcQfal2JYhFfhz/vc6aV0tgFZLUkVffhZFti8+RK GsgA2bGBwdafiAti/9Q57fEWQspT02piesFyXi+NZ69eWkR1L3nut/RR66P/NKwM DAW/rbJMuqUa1ysseuKOHxAHOcFlag== =58x5 -END PGP SIGNATURE End Message ---
Bug#1055393: undertime: autopkgtest regression: 'NoneType' object has no attribute 'utcoffset'
Source: undertime Version: 3.2.0 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. 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 https://ci.debian.net/data/autopkgtest/testing/amd64/u/undertime/39061593/log.gz 31s ** 31s File "/usr/bin/undertime", line 1079, in __main__.uniq_zones 31s Failed example: 31s list(uniq_zones(zones, now)) 31s Exception raised: 31s Traceback (most recent call last): 31s File "/usr/lib/python3.11/doctest.py", line 1351, in __run 31s exec(compile(example.source, filename, "single", 31s File "", line 1, in 31s list(uniq_zones(zones, now)) 31s File "/usr/bin/undertime", line 1086, in uniq_zones 31s offset = zone.utcoffset(now) 31s ^^ 31s AttributeError: 'NoneType' object has no attribute 'utcoffset' 31s ** OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found
Source: wasmedge Version: 0.13.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. 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 https://ci.debian.net/data/autopkgtest/testing/amd64/w/wasmedge/39560218/log.gz 140s autopkgtest [15:12:57]: test embed-cxx: [--- 140s 1..4 140s not ok 1 build fibonacci.cpp to wasm 140s # (in test file debian/tests/embed-cxx, line 12) 140s # `clang++ --target=wasm32-wasi -o fibonacci.wasm -mexec-model=reactor script/fibonacci.cpp' failed 140s # In file included from script/fibonacci.cpp:1: 140s # script/fibonacci.h:3:10: fatal error: 'cstdint' file not found 140s # #include 140s # ^ 140s # 1 error generated. 140s ok 2 build fibonacci/cpp to native 141s ok 3 build embed_cxx 141s not ok 4 run embed_cxx and test for valid output 141s # (in test file debian/tests/embed-cxx, line 27) 141s # `assert_line --index 2 --partial "3524578"' failed 141s # 141s # -- line does not contain substring -- 141s # index : 2 141s # substring : 3524578 141s # line : [2023-11-04 15:12:58.648] [error] loading failed: invalid path, Code: 0x20 141s # -- 141s # 141s autopkgtest [15:12:58]: test embed-cxx: ---] OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055391: willow: autopkgtest regression: test_save_webp_quality
Source: willow Version: 1.6.2-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it recently started to fail in testing. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/w/willow/39598331/log.gz 44s autopkgtest [12:34:41]: test runtests: [--- 55s s...sssx..x.x...s...x.sssxxx.x.x.s.s..x..x.ss..F... 55s == 55s FAIL: test_save_webp_quality (tests.test_wand.TestWandOperations.test_save_webp_quality) 55s -- 55s Traceback (most recent call last): 55s File "/tmp/autopkgtest-lxc.exbm9v5i/downtmp/autopkgtest_tmp/tests/test_wand.py", line 333, in test_save_webp_quality 55s self.assertTrue(low_quality.f.tell() < high_quality.f.tell()) 55s AssertionError: False is not true 55s 55s -- 55s Ran 219 tests in 10.791s 55s 55s FAILED (failures=1, skipped=28, expected failures=11) 56s autopkgtest [12:34:53]: test runtests: ---] OpenPGP_signature.asc Description: OpenPGP digital signature
Processed: src:gnudatalanguage: fails to migrate to testing for too long: triggers autopkgtest failure
Processing control commands: > close -1 1.0.3-1 Bug #1055390 [src:gnudatalanguage] src:gnudatalanguage: fails to migrate to testing for too long: triggers autopkgtest failure Marked as fixed in versions gnudatalanguage/1.0.3-1. Bug #1055390 [src:gnudatalanguage] src:gnudatalanguage: fails to migrate to testing for too long: triggers autopkgtest failure Marked Bug as done -- 1055390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055390: src:gnudatalanguage: fails to migrate to testing for too long: triggers autopkgtest failure
Source: gnudatalanguage Version: 1.0.1-4 Severity: serious Control: close -1 1.0.3-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:gnudatalanguage has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable triggers an autopkgtest failure in sr:coyote on ppc64el (the test times out now). 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=gnudatalanguage OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054862: marked as done (debomatic: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_install] Error 1)
Your message dated Sun, 05 Nov 2023 12:04:03 + with message-id and subject line Bug#1054862: fixed in debomatic 0.26-3 has caused the Debian Bug report #1054862, regarding debomatic: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_install] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debomatic Version: 0.26-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs/_build/latex' > latexmk -pdf -dvi- -ps- 'Deb-o-Matic.tex' > Rc files read: > /etc/LatexMk > latexmkrc > Latexmk: This is Latexmk, John Collins, 4 Apr. 2023. Version 4.80. > No existing .aux file, so I'll make a simple one, and require run of *latex. > Latexmk: applying rule 'pdflatex'... > Rule 'pdflatex': Reasons for rerun > Category 'other': > Rerun of 'pdflatex' forced or previously required > > > Run number 1 of rule 'pdflatex' > > > Running 'pdflatex -recorder "Deb-o-Matic.tex"' > > This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) > (preloaded format=pdflatex) > restricted \write18 enabled. > entering extended mode > (./Deb-o-Matic.tex > LaTeX2e <2023-06-01> patch level 1 > L3 programming layer <2023-08-29> > (./sphinxmanual.cls > Document Class: sphinxmanual 2019/12/01 v2.3.0 Document class (Sphinx manual) > (/usr/share/texlive/texmf-dist/tex/latex/base/report.cls > Document Class: report 2023/05/17 v1.4n Standard LaTeX document class > (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))) > (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty) > (/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty<>) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty > For additional information on amsmath, use the `?' option. > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) > (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty > (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty)) > (/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty > (/usr/share/texlive/texmf-dist/tex/generic/babel/txtbabel.def) > (/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf)) > (/usr/share/texlive/texmf-dist/tex/generic/babel/locale/en/babel-english.tex) > (/usr/share/texmf/tex/latex/tex-gyre/tgtermes.sty > (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty) > (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty) > (/usr/share/texlive/texmf-dist/tex/latex/kvsetkeys/kvsetkeys.sty))) > (/usr/share/texmf/tex/latex/tex-gyre/tgheros.sty) > (/usr/share/texlive/texmf-dist/tex/latex/fncychap/fncychap.sty) (./sphinx.sty > (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/mathcolor.ltx)) > (./sphinxoptionshyperref.sty) (./sphinxoptionsgeometry.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty) > (/usr/share/texlive/texmf-dist/tex/latex/float/float.sty) > (/usr/share/texlive/texmf-dist/tex/latex/wrapfig/wrapfig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/capt-of/capt-of.sty) > (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty > (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) > (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg))) > (./sphinxlatexgraphics.sty) (./sphinxpackageboxes.sty) > (./sphinxlatexadmonitions.sty > (/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)) > (./sphinxlatexliterals.sty > (/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty) > (/usr/share/texlive/texmf-dist/tex/latex/base/alltt.sty) > (/usr/share/texlive/texmf-dist/tex/latex/upquote/upquote.sty) >
Bug#1042680: marked as done (sphinxcontrib-trio: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')
Your message dated Sun, 05 Nov 2023 11:49:45 +
with message-id
and subject line Bug#1042680: fixed in sphinxcontrib-trio 1.1.2-3
has caused the Debian Bug report #1042680,
regarding sphinxcontrib-trio: FTBFS with Sphinx 7.1, docutils 0.20:
AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
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.)
--
1042680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-trio
Version: 1.1.2-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
sphinxcontrib-trio fails to build with Sphinx 7.1 and docutils 0.20, both of
which
are currently available in experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m sphinx docs/source debian/html
> Running Sphinx v7.1.1
> WARNING: Invalid configuration value found: 'language = None'. Update your
> configuration to a valid language code. Falling back to 'en' (English).
> making output directory... done
>
> Exception occurred:
> File "/<>/docs/source/conf.py", line 41, in setup
> app.add_stylesheet("hack.css")
> ^^
> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
> The full traceback has been saved in /tmp/sphinx-err-_b3yn6g9.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[1]: *** [debian/rules:10: execute_after_dh_auto_build] Error 2
The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/sphinxcontrib-trio_1.1.2-2_unstable_sphinx-exp.log
Please see [1] for Sphinx changelog and [2] for Docutils changelog.
Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.
Some notable changes in Sphinx 6 and Sphinx 7:
- Sphinx no longer includes jquery.js and underscore.js by default.
Please use python3-sphinxcontrib.jquery package if you are using a custom
template and it still needs jquery.
- The setup.py build_sphinx command was removed. Please instead call
sphinx-build or "python3 -m sphinx" directly.
- For packages using the extlinks extension, the caption should contain
exactly one "%s" placeholder (if caption is not None).
In case you have questions, please Cc sph...@packages.debian.org on reply.
[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]:
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]:
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=sphinx7.1=python-modules-t...@lists.alioth.debian.org=1=1=1=1#results
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: sphinxcontrib-trio
Source-Version: 1.1.2-3
Done: Jeroen Ploemen
We believe that the bug you reported is fixed in the latest version of
sphinxcontrib-trio, 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 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeroen Ploemen (supplier of updated sphinxcontrib-trio
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 Nov 2023 11:14:55 +
Source: sphinxcontrib-trio
Built-For-Profiles: noudeb
Architecture: source
Version: 1.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Jeroen Ploemen
Closes: 1042680
Changes:
sphinxcontrib-trio (1.1.2-3) unstable; urgency=medium
.
* Team upload.
* Patches: add 01 to remove usage of sphinx's add_stylesheet, replaced
by add_css_file. (Closes:
Bug#1054958: marked as done (haskell-lambdabot-haskell-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.
Your message dated Sun, 05 Nov 2023 11:34:31 + with message-id and subject line Bug#1054958: fixed in haskell-lambdabot-haskell-plugins 5.3.1.1-1 has caused the Debian Bug report #1054958, regarding haskell-lambdabot-haskell-plugins: FTBFS: unsatisfiable build-dependencies: libghc-base-dev-4.15.1.0-6a406, libghc-binary-dev-0.8.8.0-507cc, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, libghc-dependent-map-dev-0.4.0.0-f824e, libghc-dependent-sum-dev-0.7.1.0-2fd03, libghc-dependent-sum-template-dev-0.1.1.1-62abf, libghc-directory-dev-1.3.6.2-311c9, libghc-edit-distance-dev-0.2.2.1-cc475, libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, libghc-haskeline-dev-0.8.2-83f75, libghc-hslogger-dev-1.3.1.0-d393e, libghc-http-dev-4000.3.16-b345c, libghc-lifted-base-dev-0.2.3.12-e0695, libghc-monad-control-dev-1.0.3.1-20361, libghc-mtl-dev-2.2.2-e3bae, libghc-network-bsd-dev-2.8.1.0-726d3, libghc-network-dev-3.1.2.7-bb8a0, libghc-parsec-dev-3.1.14.0-377f0, libghc-prim-uniq-dev-0.2-b082a, libghc-random-dev-1.2.1.1-f840d, libghc-random-fu-dev-0.3.0.0-f7738, libghc-regex-tdfa-dev-1.3.2-1c748, libghc-safesemaphore-dev-0.10.1-b4f2a, libghc-split-dev-0.2.3.5-0c13f, libghc-syb-dev-0.7.2.2-ec1fd, libghc-template-haskell-dev-2.17.0.0-7274a, libghc-time-dev-1.9.3-bda76, libghc-transformers-base-dev-0.4.6-a0a78, libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unix-dev-2.7.2.2-bdab4, libghc-utf8-string-dev-1.0.2-a50cd, libghc-zlib-dev-0.6.3.0-57e0e, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, libghc-binary-prof-0.8.8.0-507cc, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, libghc-dependent-map-prof-0.4.0.0-f824e, libghc-dependent-sum-prof-0.7.1.0-2fd03, libghc-dependent-sum-template-prof-0.1.1.1-62abf, libghc-directory-prof-1.3.6.2-311c9, libghc-edit-distance-prof-0.2.2.1-cc475, libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, libghc-haskeline-prof-0.8.2-83f75, libghc-hslogger-prof-1.3.1.0-d393e, libghc-http-prof-4000.3.16-b345c, libghc-lifted-base-prof-0.2.3.12-e0695, libghc-monad-control-prof-1.0.3.1-20361, libghc-mtl-prof-2.2.2-e3bae, libghc-network-bsd-prof-2.8.1.0-726d3, libghc-network-prof-3.1.2.7-bb8a0, libghc-parsec-prof-3.1.14.0-377f0, libghc-prim-uniq-prof-0.2-b082a, libghc-random-fu-prof-0.3.0.0-f7738, libghc-random-prof-1.2.1.1-f840d, libghc-regex-tdfa-prof-1.3.2-1c748, libghc-safesemaphore-prof-0.10.1-b4f2a, libghc-split-prof-0.2.3.5-0c13f, libghc-syb-prof-0.7.2.2-ec1fd, libghc-template-haskell-prof-2.17.0.0-7274a, libghc-time-prof-1.9.3-bda76, libghc-transformers-base-prof-0.4.6-a0a78, libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unix-prof-2.7.2.2-bdab4, libghc-utf8-string-prof-1.0.2-a50cd, libghc-zlib-prof-0.6.3.0-57e0e, libghc-base-dev-4.15.1.0-6a406, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-containers-dev-0.6.4.1-31c3b, libghc-http-dev-4000.3.16-b345c, libghc-mtl-dev-2.2.2-e3bae, libghc-network-dev-3.1.2.7-bb8a0, libghc-network-uri-dev-2.6.4.1-35b94, libghc-process-dev-1.6.13.2-9f25f, libghc-regex-tdfa-dev-1.3.2-1c748, libghc-split-dev-0.2.3.5-0c13f, libghc-tagsoup-dev-0.14.8-eee5a, libghc-utf8-string-dev-1.0.2-a50cd, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-containers-prof-0.6.4.1-31c3b, libghc-http-prof-4000.3.16-b345c, libghc-mtl-prof-2.2.2-e3bae, libghc-network-prof-3.1.2.7-bb8a0, libghc-network-uri-prof-2.6.4.1-35b94, libghc-process-prof-1.6.13.2-9f25f, libghc-regex-tdfa-prof-1.3.2-1c748, libghc-split-prof-0.2.3.5-0c13f, libghc-tagsoup-prof-0.14.8-eee5a, libghc-utf8-string-prof-1.0.2-a50cd, libghc-base-dev-4.15.1.0-6a406, libghc-quickcheck-dev-2.14.2-eab42, libghc-quickcheck-safe-dev-0.1.0.6-2f552, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, libghc-quickcheck-prof-2.14.2-eab42, libghc-quickcheck-safe-prof-0.1.0.6-2f552, libghc-base-dev-4.15.1.0-6a406, libghc-http-dev-4000.3.16-b345c, libghc-network-dev-3.1.2.7-bb8a0, libghc-network-uri-dev-2.6.4.1-35b94, haddock-interface-38, libghc-base-prof-4.15.1.0-6a406, libghc-http-prof-4000.3.16-b345c, libghc-network-prof-3.1.2.7-bb8a0, libghc-network-uri-prof-2.6.4.1-35b94 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.) -- 1054958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-lambdabot-haskell-plugins Version: 5.3.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags:
Bug#1054954: marked as done (haskell-copilot-theorem: FTBFS: unsatisfiable build-dependencies: haddock-interface-38, haddock-interface-38, libghc-async-dev-2.2.4-7edea, libghc-attoparsec-dev-0.14.4-9b
Your message dated Sun, 05 Nov 2023 11:34:21 + with message-id and subject line Bug#1054954: fixed in haskell-copilot-theorem 3.16.1-1 has caused the Debian Bug report #1054954, regarding haskell-copilot-theorem: FTBFS: unsatisfiable build-dependencies: haddock-interface-38, haddock-interface-38, libghc-async-dev-2.2.4-7edea, libghc-attoparsec-dev-0.14.4-9b901, libghc-base-dev-4.15.1.0-6a406, libghc-bifunctors-dev-5.5.13-864ee, libghc-bimap-dev-0.5.0-e16f1, libghc-bv-sized-dev-1.0.4-82727, libghc-bytestring-dev-0.10.12.1-ced9a, libghc-concurrent-extra-dev-0.7.0.12-20bc1, libghc-config-value-dev-0.8.3-b90da, libghc-containers-dev-0.6.4.1-31c3b, libghc-data-binary-ieee754-dev-0.4.4-bdd42, libghc-deepseq-dev-1.4.5.0-118cf, libghc-deriving-compat-dev-0.6.1-d03ae, libghc-directory-dev-1.3.6.2-311c9, libghc-exceptions-dev-0.10.4-c14ff, libghc-filepath-dev-1.4.2.1-4459f, libghc-fingertree-dev-0.1.5.0-14910, libghc-ghc-prim-dev-0.7.0-65cf5, libghc-hashable-dev-1.3.5.0-3fad8, libghc-hashtables-dev-1.2.4.2-4be59, libghc-io-streams-dev-1.5.2.2-20c45, libghc-lens-dev-5.0.1-5039c, libghc-libbf-dev-0.6.5.1-82182, libghc-mtl-dev-2.2.2-e3bae, libghc-panic-dev-0.4.0.1-95384, libghc-parameterized-utils-dev-2.1.5.0-7c4ad, libghc-prettyprinter-dev-1.7.1-c341b, libghc-process-dev-1.6.13.2-9f25f, libghc-scientific-dev-0.3.7.0-de1a8, libghc-template-haskell-dev-2.17.0.0-7274a, libghc-temporary-dev-1.3-5f386, libghc-text-dev-1.2.5.0-8553e, libghc-th-abstraction-dev-0.4.5.0-4048c, libghc-th-lift-dev-0.8.2-fd5f2, libghc-th-lift-instances-dev-0.1.20-ef320, libghc-transformers-dev-0.5.6.2-fc6f3, libghc-unordered-containers-dev-0.2.17.0-1d16d, libghc-utf8-string-dev-1.0.2-a50cd, libghc-vector-dev-0.12.3.1-f377c, libghc-versions-dev-5.0.3-f2263, libghc-zenc-dev-0.1.2-d8c5c, haddock-interface-38, libghc-async-prof-2.2.4-7edea, libghc-attoparsec-prof-0.14.4-9b901, libghc-base-prof-4.15.1.0-6a406, libghc-bifunctors-prof-5.5.13-864ee, libghc-bimap-prof-0.5.0-e16f1, libghc-bv-sized-prof-1.0.4-82727, libghc-bytestring-prof-0.10.12.1-ced9a, libghc-concurrent-extra-prof-0.7.0.12-20bc1, libghc-config-value-prof-0.8.3-b90da, libghc-containers-prof-0.6.4.1-31c3b, libghc-data-binary-ieee754-prof-0.4.4-bdd42, libghc-deepseq-prof-1.4.5.0-118cf, libghc-deriving-compat-prof-0.6.1-d03ae, libghc-directory-prof-1.3.6.2-311c9, libghc-exceptions-prof-0.10.4-c14ff, libghc-filepath-prof-1.4.2.1-4459f, libghc-fingertree-prof-0.1.5.0-14910, libghc-ghc-prim-prof-0.7.0-65cf5, libghc-hashable-prof-1.3.5.0-3fad8, libghc-hashtables-prof-1.2.4.2-4be59, libghc-io-streams-prof-1.5.2.2-20c45, libghc-lens-prof-5.0.1-5039c, libghc-libbf-prof-0.6.5.1-82182, libghc-mtl-prof-2.2.2-e3bae, libghc-panic-prof-0.4.0.1-95384, libghc-parameterized-utils-prof-2.1.5.0-7c4ad, libghc-prettyprinter-prof-1.7.1-c341b, libghc-process-prof-1.6.13.2-9f25f, libghc-scientific-prof-0.3.7.0-de1a8, libghc-template-haskell-prof-2.17.0.0-7274a, libghc-temporary-prof-1.3-5f386, libghc-text-prof-1.2.5.0-8553e, libghc-th-abstraction-prof-0.4.5.0-4048c, libghc-th-lift-instances-prof-0.1.20-ef320, libghc-th-lift-prof-0.8.2-fd5f2, libghc-transformers-prof-0.5.6.2-fc6f3, libghc-unordered-containers-prof-0.2.17.0-1d16d, libghc-utf8-string-prof-1.0.2-a50cd, libghc-vector-prof-0.12.3.1-f377c, libghc-versions-prof-5.0.3-f2263, libghc-zenc-prof-0.1.2-d8c5c 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.) -- 1054954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-copilot-theorem Version: 3.13-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231028 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-bimap-dev, > libghc-bimap-prof, libghc-bv-sized-dev (>= 1.0.2), libghc-bv-sized-dev (<< > 1.1), libghc-bv-sized-prof, libghc-copilot-core-dev (>= 3.13), > libghc-copilot-core-dev (<< 3.14), libghc-copilot-core-prof, > libghc-copilot-prettyprinter-dev (>= 3.13), libghc-copilot-prettyprinter-dev > (<< 3.14),
Bug#1052831: marked as done (python-agate: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13)
Your message dated Sun, 05 Nov 2023 11:36:22 +
with message-id
and subject line Bug#1052831: fixed in python-agate 1.6.3-3
has caused the Debian Bug report #1052831,
regarding python-agate: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.11 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-agate
Version: 1.6.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> LC_ALL=C.UTF-8 LC_NUMERIC=C.UTF-8 dh_auto_test
> I: pybuild pybuild:314: cp -r /<>/examples
> /<>/.pybuild/cpython3_3.11_agate/build
> I: pybuild base:291: cd /<>/.pybuild/cpython3_3.11_agate/build;
> python3.11 -m unittest discover -v
> test_agate (tests.test_agate.TestCSV.test_agate) ... ok
> test_all (tests.test_aggregations.TestBooleanAggregation.test_all) ... ok
> test_any (tests.test_aggregations.TestBooleanAggregation.test_any) ... ok
> test_max (tests.test_aggregations.TestDateTimeAggregation.test_max) ... ok
> test_max_all_nulls
> (tests.test_aggregations.TestDateTimeAggregation.test_max_all_nulls) ... ok
> test_max_time_delta
> (tests.test_aggregations.TestDateTimeAggregation.test_max_time_delta) ... ok
> test_min (tests.test_aggregations.TestDateTimeAggregation.test_min) ... ok
> test_min_all_nulls
> (tests.test_aggregations.TestDateTimeAggregation.test_min_all_nulls) ... ok
> test_min_time_delta
> (tests.test_aggregations.TestDateTimeAggregation.test_min_time_delta) ... ok
> test_sum (tests.test_aggregations.TestDateTimeAggregation.test_sum) ... ok
> test_sum_all_nulls
> (tests.test_aggregations.TestDateTimeAggregation.test_sum_all_nulls) ... ok
> test_deciles (tests.test_aggregations.TestNumberAggregation.test_deciles) ...
> ok
> test_deciles_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_deciles_all_nulls) ... ok
> test_iqr (tests.test_aggregations.TestNumberAggregation.test_iqr) ... ok
> test_irq_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_irq_all_nulls) ... ok
> test_mad (tests.test_aggregations.TestNumberAggregation.test_mad) ... ok
> test_mad_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_mad_all_nulls) ... ok
> test_max (tests.test_aggregations.TestNumberAggregation.test_max) ... ok
> test_max_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_max_all_nulls) ... ok
> test_max_precision
> (tests.test_aggregations.TestNumberAggregation.test_max_precision) ... ok
> test_max_precision_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_max_precision_all_nulls)
> ... ok
> test_mean (tests.test_aggregations.TestNumberAggregation.test_mean) ... ok
> test_mean_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_mean_all_nulls) ... ok
> test_mean_with_nulls
> (tests.test_aggregations.TestNumberAggregation.test_mean_with_nulls) ... ok
> test_median (tests.test_aggregations.TestNumberAggregation.test_median) ... ok
> test_median_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_median_all_nulls) ... ok
> test_min (tests.test_aggregations.TestNumberAggregation.test_min) ... ok
> test_min_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_min_all_nulls) ... ok
> test_mode (tests.test_aggregations.TestNumberAggregation.test_mode) ... ok
> test_mode_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_mode_all_nulls) ... ok
> test_percentiles
> (tests.test_aggregations.TestNumberAggregation.test_percentiles) ... ok
> test_percentiles_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_percentiles_all_nulls)
> ... ok
> test_percentiles_locate
> (tests.test_aggregations.TestNumberAggregation.test_percentiles_locate) ... ok
> test_population_stdev
> (tests.test_aggregations.TestNumberAggregation.test_population_stdev) ... ok
> test_population_stdev_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_population_stdev_all_nulls)
> ... ok
> test_population_variance
> (tests.test_aggregations.TestNumberAggregation.test_population_variance) ...
> ok
> test_population_variance_all_nulls
> (tests.test_aggregations.TestNumberAggregation.test_population_variance_all_nulls)
> ... ok
> test_quartiles (tests.test_aggregations.TestNumberAggregation.test_quartiles)
Bug#1054745: marked as done (haskell-copilot-interpreter: FTBFS: build-dependency not installable: haddock-interface-38)
Your message dated Sun, 05 Nov 2023 11:34:12 + with message-id and subject line Bug#1054745: fixed in haskell-copilot-interpreter 3.16.1-1 has caused the Debian Bug report #1054745, regarding haskell-copilot-interpreter: FTBFS: build-dependency not installable: haddock-interface-38 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.) -- 1054745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-copilot-interpreter Version: 3.13-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 10), haskell-devscripts-minimal | > haskell-devscripts (>= 0.13), cdbs, ghc, ghc-prof, libghc-copilot-core-dev > (>= 3.13), libghc-copilot-core-dev (<< 3.14), libghc-copilot-core-prof, > libghc-quickcheck2-dev, libghc-quickcheck2-prof, > libghc-copilot-prettyprinter-dev, libghc-copilot-prettyprinter-prof, > libghc-test-framework-dev, libghc-test-framework-prof, > libghc-test-framework-quickcheck2-dev, > libghc-test-framework-quickcheck2-prof, build-essential, fakeroot, ghc-doc, > libghc-copilot-core-doc, libghc-quickcheck2-doc, libghc-test-framework-doc, > libghc-test-framework-quickcheck2-doc > Filtered Build-Depends: debhelper (>= 10), haskell-devscripts-minimal, cdbs, > ghc, ghc-prof, libghc-copilot-core-dev (>= 3.13), libghc-copilot-core-dev (<< > 3.14), libghc-copilot-core-prof, libghc-quickcheck2-dev, > libghc-quickcheck2-prof, libghc-copilot-prettyprinter-dev, > libghc-copilot-prettyprinter-prof, libghc-test-framework-dev, > libghc-test-framework-prof, libghc-test-framework-quickcheck2-dev, > libghc-test-framework-quickcheck2-prof, build-essential, fakeroot, ghc-doc, > libghc-copilot-core-doc, libghc-quickcheck2-doc, libghc-test-framework-doc, > libghc-test-framework-quickcheck2-doc > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [615 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [1183 B] > Get:5 copy:/<>/apt_archive ./ Packages [1165 B] > Fetched 2963 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libghc-copilot-core-doc : Depends: haddock-interface-38 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/10/27/haskell-copilot-interpreter_3.13-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: haskell-copilot-interpreter Source-Version: 3.16.1-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-copilot-interpreter, which is due to be installed in the
Bug#1052804: marked as done (ycmd: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1)
Your message dated Sun, 05 Nov 2023 11:36:34 +
with message-id
and subject line Bug#1052804: fixed in ycmd 0+20230611+git3392251+ds-2
has caused the Debian Bug report #1052804,
regarding ycmd: FTBFS: make[1]: *** [debian/rules:28: override_dh_auto_test]
Error 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1052804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ycmd
Version: 0+20230611+git3392251+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> [ FAILED ] 7 tests, listed below:
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1177, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क्त", { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क्त" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1178, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क््त", { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क््त" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1179, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA5\x8D\xE2\x80\x8D\xE0\xA4\xA4"
> As Text: "क्त", { "\xE0\xA4\x95\xE0\xA5\x8D\xE2\x80\x8D\xE0\xA4\xA4"
> As Text: "क्त" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1180, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA4\xBC\xE2\x80\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क़्त", {
> "\xE0\xA4\x95\xE0\xA4\xBC\xE2\x80\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क़्त" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1181, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA4\xBC\xE0\xA5\x8D\xE2\x80\x8D\xE0\xA4\xA4"
> As Text: "क़्त", {
> "\xE0\xA4\x95\xE0\xA4\xBC\xE0\xA5\x8D\xE2\x80\x8D\xE0\xA4\xA4"
> As Text: "क़्त" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1182, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA4\xA4\xE0\xA5\x8D\xE0\xA4\xAF"
> As Text: "क्त्य", {
> "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA4\xA4\xE0\xA5\x8D\xE0\xA4\xAF"
> As Text: "क्त्य" }
> [ FAILED ] UnicodeTest/WordTest.BreakIntoCharacters/1186, where GetParam()
> = { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क््त", { "\xE0\xA4\x95\xE0\xA5\x8D\xE0\xA5\x8D\xE0\xA4\xA4"
> As Text: "क््त" }
>
> 7 FAILED TESTS
> make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/09/25/ycmd_0+20230611+git3392251+ds-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ycmd
Source-Version: 0+20230611+git3392251+ds-2
Done: David Kalnischkies
We believe that the bug you reported is fixed in the latest version of
ycmd, 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 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Kalnischkies (supplier of updated ycmd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 Nov 2023 11:41:38 +0100
Source: ycmd
Architecture: source
Version: 0+20230611+git3392251+ds-2
Distribution: unstable
Urgency: medium
Maintainer: David Kalnischkies
Changed-By: David Kalnischkies
Closes: 1052804
Changes:
ycmd (0+20230611+git3392251+ds-2) unstable;
Processed: Bug#1052831 marked as pending in python-agate
Processing control commands:
> tag -1 pending
Bug #1052831 [src:python-agate] python-agate: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.
--
1052831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1042680 marked as pending in sphinxcontrib-trio
Processing control commands: > tag -1 pending Bug #1042680 [src:sphinxcontrib-trio] sphinxcontrib-trio: FTBFS with Sphinx 7.1, docutils 0.20: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) pending. -- 1042680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052831: marked as pending in python-agate
Control: tag -1 pending Hello, Bug #1052831 in python-agate reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-agate/-/commit/2108a2a6cb79afe7a5defb6092d6695439ba006d Update TZ used in tests for tzdata 2023c-8. Closes: #1052831. (this message was generated automatically) -- Greetings https://bugs.debian.org/1052831
Bug#1042680: marked as pending in sphinxcontrib-trio
Control: tag -1 pending Hello, Bug #1042680 in sphinxcontrib-trio reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/sphinxcontrib-trio/-/commit/58a8055503729c4134045a1bbe95382ec18bc3d4 Patches: add 01 to remove usage of sphinx's add_stylesheet, replaced by add_css_file. (Closes: #1042680) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042680
Processed: Bug #1042695: Forwarded to upstream issue
Processing commands for cont...@bugs.debian.org: > forwarded 1042695 https://github.com/celery/vine/issues/82 Bug #1042695 [src:vine] vine: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2 Set Bug forwarded-to-address to 'https://github.com/celery/vine/issues/82'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1054711: marked as done (metview: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to `metkit::mars::MarsRequest::dump(std::ostream&, char const*, char const*) const')
Your message dated Sun, 05 Nov 2023 10:50:00 + with message-id and subject line Bug#1054711: fixed in metview 5.20.0-2 has caused the Debian Bug report #1054711, regarding metview: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to `metkit::mars::MarsRequest::dump(std::ostream&, char const*, char const*) const' 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.) -- 1054711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: metview Version: 5.20.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -fcf-protection -Wall > -pedantic -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -pipe -O3 -DNDEBUG > -Wl,-z,relro -Wl,-z,now-Wl,--disable-new-dtags > CMakeFiles/marsgen.dir/marsgen.c.o -o ../../../bin/marsgen > -Wl,-rpath,/<>/debian/build/lib: > ../../../lib/libmarsclient.so.0.0.0 /usr/lib/x86_64-linux-gnu/libtirpc.so > /usr/lib/x86_64-linux-gnu/libeccodes.so.0 -lm > -Wl,-rpath-link,/<>/debian/build/lib > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::mars::MarsRequest::dump(std::ostream&, char const*, char const*) > const' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::hypercube::HyperCube::vacantRequests() const' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::mars::MarsRequest::dump(std::ostream&, char const*, char const*) > const' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::mars::MarsRequest::dump(std::ostream&, char const*, char const*) > const' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::hypercube::HyperCube::vacantRequests() const' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libfdb5.so.0d: undefined reference to > `metkit::hypercube::HyperCube::vacantRequests() const' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2023/10/27/metview_5.20.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: metview Source-Version: 5.20.0-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of metview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated metview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Nov 2023 10:25:19 + Source: metview Architecture: source Version: 5.20.0-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 1054711 Changes: metview (5.20.0-2) unstable; urgency=medium . * Change B-D on fdb-dev to >= 5.11.25. Closes: #1054711 Checksums-Sha1: cbcc60359a91ceddd8d01040f4216b8325ba30c6 3510 metview_5.20.0-2.dsc f22378a20d829679bbecce65f09f06e16c602e08 40112 metview_5.20.0-2.debian.tar.xz Checksums-Sha256: c5b72012241aecf6f6837f0ca02940081f1132f460c1ebc62bf07dde1d240473 3510 metview_5.20.0-2.dsc
Processed: Bug #1052770: Forwarded to upstream commit that fixes tests with flask-babel 3
Processing commands for cont...@bugs.debian.org:
> forwarded 1052770 https://github.com/wtforms/flask-wtf/pull/549
Bug #1052770 [src:flask-wtf] flask-wtf: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/wtforms/flask-wtf/pull/549'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1052770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 1053799 is serious
Processing commands for cont...@bugs.debian.org: > severity 1053799 serious Bug #1053799 [src:golang-github-libgit2-git2go] golang-github-libgit2-git2go: no upstream support for latest libgit2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1053799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
