Bug#1073170: marked as done (src:libabigail: fails to migrate to testing for too long: uploader built arch:all binaries)
Your message dated Fri, 28 Jun 2024 06:38:04 + with message-id and subject line Bug#1073170: fixed in libabigail 2.5-1.1 has caused the Debian Bug report #1073170, regarding src:libabigail: fails to migrate to testing for too long: uploader built arch:all binaries 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.) -- 1073170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libabigail Version: 2.4-3 Severity: serious Control: close -1 2.5-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:libabigail has been trying to migrate for 41 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=libabigail OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libabigail Source-Version: 2.5-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of libabigail, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated libabigail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Jun 2024 07:20:16 +0200 Source: libabigail Architecture: source Version: 2.5-1.1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Paul Gevers Closes: 1073170 Changes: libabigail (2.5-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1073170) Checksums-Sha1: 891d0e4a76d1e7c1eff04761d8a3910bead50c36 2091 libabigail_2.5-1.1.dsc 9358e0dfd0f0c2b95d892263beb902035fa78c68 4440 libabigail_2.5-1.1.debian.tar.xz Checksums-Sha256: e16fd6546d2ac1f24fa7e8b9e48bed48e6a95f98e263881296a8428a115393b5 2091 libabigail_2.5-1.1.dsc 61fe6f7178cb71275216f5ac84c3f2d47348b09fe41832c1667fc1778e0b4aa5 4440 libabigail_2.5-1.1.debian.tar.xz Files: 7a946e460bb9391c5c9dbd404bb5c0c0 2091 libs optional libabigail_2.5-1.1.dsc 55d049b19abc89a8589661d7f82be588 4440 libs optional libabigail_2.5-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZr1lAACgkQnFyZ6wW9 dQooeAf+JrKnEziI8ppuJPrkyh5OyX7d13LrOgEf0LOKBg/eKPC8PBzhEU1b96OL b8iSF83CUkQTGvNtr7PSlSFOnO3gHqzJ6XhD4gp4yDgZwISFHb/FTVM+Sly8vFaV 6Pcp+vbM6CH3m0KJGuHAzOkA8u2xLJ97GTwi49l285Iqn2pwh3NoFNG00Pc6lVaF IGyT8H4jjduGRG54X+RlTKW13oC+55PdZkAJ2hcih/WBiMEuQXa4opkqoPRQhFtW fCRsmpZ3HrPMOEExYxW/PfxuiKQWptzkV5hnY9G/qpPzaPguvBMKxF8Ip/I3j5wI yXpU34288r2d9O/E5/SZMftmxg/oKg== =7FK/ -
Processed: Re: Bug#1074370: ffmpeg: Fails to build on armel & armhf
Processing control commands: > forwarded -1 https://trac.ffmpeg.org/ticket/11074 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Set Bug forwarded-to-address to 'https://trac.ffmpeg.org/ticket/11074'. > tags -1 upstream Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Added tag(s) upstream. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074370: ffmpeg: Fails to build on armel & armhf
Control: forwarded -1 https://trac.ffmpeg.org/ticket/11074 Control: tags -1 upstream On 2024-06-28 01:40:25 +0100, Peter Green wrote: > On 27/06/2024 12:33, Jeremy Bícha wrote: > > Source: ffmpeg > > Version: 7:6.1.1-4 > > Severity: serious > > Tags: ftbfs > > User: debian-...@lists.debian.org > > Usertags: armel armhf > > X-Debbugs-CC: debian-...@lists.debian.org > > > > ffmpeg is failing to build on armel & armhf (but not arm64). This was > > noticed while rebuilding ffmpeg for the ongoing jpeg-xl 0.9 > > transition. I don't believe the build failure is related to the new > > version of jpeg-xl. The last successful official build before this was > > on June 9. > > I belive binutils has recently got stricter about assembler syntax > (see for example https://gitlab.com/postmarketOS/pmaports/-/issues/2401 ) > but given that this particular assembler involves macros, I don't feel > confident trying to fix this myself. This is also affects the 7.0.x branch. Issue reported upstream. Cheers -- Sebastian Ramacher
Processed: found 1074370 in 7:6.1.1-3
Processing commands for cont...@bugs.debian.org: > found 1074370 7:6.1.1-3 Bug #1074370 [src:ffmpeg] ffmpeg: Fails to build on armel & armhf Marked as found in versions ffmpeg/7:6.1.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074338: src:libxml2: fails to migrate to testing for too long: unresolved RC issue
Hi, On Thu, Jun 27, 2024 at 4:21 AM Paul Gevers wrote: > > Source: libxml2 > Version: 2.9.14+dfsg-1.3 > Severity: serious > Control: close -1 2.12.7+dfsg-3 > Tags: sid trixie > User: release.debian@packages.debian.org > Usertags: out-of-sync > Control: block -1 by 1073508 > > 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:libxml2 has been trying to migrate for 32 > days [2]. Hence, I am filing this bug. The version in unstable broke ABI > without a SONAME bump as reported in bug 1073508. > I would like to seek for your advice on how to handle this issue, the stuff looks a bit complicated: - upstream is responsive and helpful, but the current handling of API/ABI could be problematic - there is no plan to bump SONAME at this moment - need time to do in-depth check of API/ABI breakages Would like to know if such steps would help resolve the issue better: - revert to a previous version which does not have API/ABI breakage - apply/port security patches on a best effort basis - help upstream to check and fix API/ABI changes Or do you have any recommendations? Thanks, Aron
Bug#1074370: ffmpeg: Fails to build on armel & armhf
On 27/06/2024 12:33, Jeremy Bícha wrote: Source: ffmpeg Version: 7:6.1.1-4 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: armel armhf X-Debbugs-CC: debian-...@lists.debian.org ffmpeg is failing to build on armel & armhf (but not arm64). This was noticed while rebuilding ffmpeg for the ongoing jpeg-xl 0.9 transition. I don't believe the build failure is related to the new version of jpeg-xl. The last successful official build before this was on June 9. I belive binutils has recently got stricter about assembler syntax (see for example https://gitlab.com/postmarketOS/pmaports/-/issues/2401 ) but given that this particular assembler involves macros, I don't feel confident trying to fix this myself.
Bug#1067699: libllvm18:i386 contains files, also in libllvm18:amd64
Package: libllvm18 Version: 1:18.1.8-1 Followup-For: Bug #1067699 X-Debbugs-Cc: witold.bary...@gmail.com Dear Maintainer, Still happening amd64 Preparing to unpack .../libllvm18_1%3a18.1.8-1_i386.deb ... Unpacking libllvm18:i386 (1:18.1.8-1) ... dpkg: error processing archive /var/cache/apt/archives/libllvm18_1%3a18.1.8-1_i386.deb (--unpack): trying to overwrite shared '/usr/lib/llvm-18/lib/libLLVM.so.1', which is different from other instances of package libllvm18:i386 This makes it very tricky to cross-compile Mesa to i386 on amd64. This a regression, as it was working fine on llvm 16 and 17 (and probably earlier as far I remember for few years). Regards, Witold -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libllvm18:i386 depends on: ii libc6 2.38-13 ii libedit23.1-20230828-1+b1 ii libffi8 3.4.6-1 ii libgcc-s1 14-20240330-1 ii libstdc++6 14-20240330-1 ii libtinfo6 6.4+20240414-1 ii libxml2 2.9.14+dfsg-1.3+b3 ii libz3-4 4.8.12-3.1+b2 ii libzstd11.5.6+dfsg-1 ii zlib1g 1:1.3.dfsg+really1.3.1-1 libllvm18:i386 recommends no packages. libllvm18:i386 suggests no packages.
Bug#1074399: libcgi-application-plugin-authentication-perl: autopkgtest regression: libcgi-application-plugin-authentication-perl vs libcgi-pm-perl
Package: libcgi-application-plugin-authentication-perl Version: 0.24+~cs0.5-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: chris.peter...@canonical.com User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oracular ubuntu-patch libcgi-application-plugin-authentication-perl's build time tests fail due to a change in behavior in libcgi-pm-perl with trailing slashes in URLs. In particular, a test was failing which compared generated output with a reference output that was generated with an older version of libcgi-pm-perl. I applied the attached patch to fix the issue Ubuntu and also forwarded it upstream. Thanks for considering the patch. - cpete diff -Nru libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch --- libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch 1969-12-31 16:00:00.0 -0800 +++ libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/login-box-basic.patch 2024-06-27 16:02:21.0 -0700 @@ -0,0 +1,23 @@ +Description: Update test for CGI.pm >=4.66 + CGI.pm made changes to "restore the trailing slash in ->url" in 4.66[1], + which causes a test failure in one of the tests comparing output with + a reference generated by a previous version of CGI.pm. This patch + updates the reference file for compatibility with CGI.pm >= 4.66. + + [1] https://github.com/leejo/CGI.pm/commit/a5485b5f3b2b1cc85761b6781ff6660b4f377498 +Author: Chris Peterson +Forwarded: https://github.com/MicroTechnology-Services/cgi-application-plugin-authentication/pull/2 +Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libcgi-application-plugin-authentication-perl/+bug/2071369 +Last-Update: 2024-06-27 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/t/out/basic_login_box b/t/out/basic_login_box +@@ -28,6 +28,6 @@ + + + +- http://localhost"; /> ++ http://localhost/"; /> + + diff -Nru libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series --- libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 1969-12-31 16:00:00.0 -0800 +++ libcgi-application-plugin-authentication-perl-0.24+~cs0.5/debian/patches/series 2024-06-27 11:32:51.0 -0700 @@ -0,0 +1 @@ +login-box-basic.patch
Processed: Re: Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
Processing control commands: > tag -1 upstream, fixed-upstream patch Bug #1072971 [mesa] mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb Added tag(s) patch, upstream, and fixed-upstream. > forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360 > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837 Bug #1072971 [mesa] mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837'. -- 1072971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1072971: mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
Control: tag -1 upstream, fixed-upstream patch
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837
On 14 Jun 2024 13:36:54 +0200 Emilio Pozuelo Monfort wrote:
> Control: reassign -1 mesa 24.1.1-2
> Control: affects -1 kuserfeedback
> Control: retitle -1 mesa: fails to initialize OpenGL on s390x: Unexpected
> format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb
>
> Actually this looks like a regression in mesa in 24.1. A few rdeps are
> failing their autopkgtests with the same PIPE_FORMAT_X8B8G8R8_SRGB error,
> e.g.:
>
> https://ci.debian.net/packages/k/kodi/testing/s390x/47675600/
> https://ci.debian.net/packages/o/openscad/testing/s390x/47689316/
This is fixed in upstream commit 5ca85d75c05de9df7c3170122dfdb04bc795b43a
("dri: Fix BGR format exclusion"), which I attached for your convenience.
I haven't tried it as I don't have access to a s390x machine, so if
someone can verify it, that would be most welcome.
Cheers,
Diederik>From 5ca85d75c05de9df7c3170122dfdb04bc795b43a Mon Sep 17 00:00:00 2001
From: Daniel Stone
Date: Fri, 21 Jun 2024 11:24:31 +0100
Subject: [PATCH] dri: Fix BGR format exclusion
Origin: upstream, https://gitlab.freedesktop.org/mesa/mesa/-/commit/5ca85d75c05de9df7c3170122dfdb04bc795b43a
Bug-Debian: https://bugs.debian.org/1072971
The check we had for BGR vs. RGB formats was testing completely the
wrong thing. Fix it so we can restore the previous set of configs we
expose to the frontend, which also fixes surfaceless platform on s390x.
Signed-off-by: Daniel Stone
Fixes: ad0edea53a73 ("st/dri: Check format properties from format helpers")
Closes: mesa/mesa#11360
Part-of:
---
src/gallium/frontends/dri/dri_screen.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/src/gallium/frontends/dri/dri_screen.c b/src/gallium/frontends/dri/dri_screen.c
index 97d11f324ee0b..2e9ce01147a89 100644
--- a/src/gallium/frontends/dri/dri_screen.c
+++ b/src/gallium/frontends/dri/dri_screen.c
@@ -386,17 +386,21 @@ dri_fill_in_modes(struct dri_screen *screen)
uint8_t msaa_modes[MSAA_VISUAL_MAX_SAMPLES];
/* Expose only BGRA ordering if the loader doesn't support RGBA ordering. */
- if (!allow_rgba_ordering &&
- util_format_get_component_shift(pipe_formats[f],
- UTIL_FORMAT_COLORSPACE_RGB, 0)
+ if (!allow_rgba_ordering) {
+ unsigned sh_ax = util_format_get_component_shift(pipe_formats[f], UTIL_FORMAT_COLORSPACE_RGB, 3);
+ unsigned sh_b = util_format_get_component_shift(pipe_formats[f], UTIL_FORMAT_COLORSPACE_RGB, 2);
#if UTIL_ARCH_BIG_ENDIAN
- >
+ unsigned sz_b = util_format_get_component_bits(pipe_formats[f], UTIL_FORMAT_COLORSPACE_RGB, 2);
+
+ if (sz_b + sh_b == sh_ax)
+ continue;
#else
- <
+ unsigned sz_ax = util_format_get_component_bits(pipe_formats[f], UTIL_FORMAT_COLORSPACE_RGB, 3);
+
+ if (sz_ax + sh_ax == sh_b)
+ continue;
#endif
- util_format_get_component_shift(pipe_formats[f],
- UTIL_FORMAT_COLORSPACE_RGB, 2))
- continue;
+ }
if (!allow_rgb10 &&
util_format_get_component_bits(pipe_formats[f],
--
GitLab
signature.asc
Description: This is a digitally signed message part.
Processed: Re: node-yarnpkg: FTBFS: compat.h:155:2: error: unsupported size of off_t
Processing control commands: > tags -1 patch ftbfs Bug #1067283 [src:node-yarnpkg] node-yarnpkg: FTBFS: compat.h:155:2: error: unsupported size of off_t Added tag(s) patch. -- 1067283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1067283: node-yarnpkg: FTBFS: compat.h:155:2: error: unsupported size of off_t
Package: node-yarnpkg
Version: 4.0.2+dfsg-2
Followup-For: Bug #1067283
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oracular ubuntu-patch
Control: tags -1 patch ftbfs
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/rules: add a few LDFLAGS flags to workaround a bug in the Debian
Emscripten toolchain. Also remove some flags to avoid wasm-ld crashing
(LP: #2068769).
* d/p/fix-yarnpkg-libzip.patch: modify the patch so that it will not add
in unsupported Node.js options that got removed and stablized in Node.js 20
* d/p/disable-network-tests.patch: remove a test that requires Internet
to run properly
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers noble-updates
APT policy: (500, 'noble-updates'), (500, 'noble-security'), (500, 'noble'),
(100, 'noble-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.8.0-35-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru node-yarnpkg-4.0.2+dfsg/debian/patches/disable-network-tests.patch
node-yarnpkg-4.0.2+dfsg/debian/patches/disable-network-tests.patch
--- node-yarnpkg-4.0.2+dfsg/debian/patches/disable-network-tests.patch
1969-12-31 17:00:00.0 -0700
+++ node-yarnpkg-4.0.2+dfsg/debian/patches/disable-network-tests.patch
2024-06-17 12:52:18.0 -0600
@@ -0,0 +1,139 @@
+Description: Disable network tests
+ We can't reliably test those during the build as the build environment
+ does not have Internet connection.
+Author: Zixing Liu
+Forwarded: not-needed
+Last-Update: 2024-06-19
+---
+Index: node-yarnpkg/packages/plugin-compat/tests/patches.test.ts
+===
+--- node-yarnpkg.orig/packages/plugin-compat/tests/patches.test.ts
/dev/null
+@@ -1,127 +0,0 @@
+-import {Configuration, Descriptor, Project, ResolveOptions, ThrowReport,
structUtils, Locator, Cache, LocatorHash} from '@yarnpkg/core';
+-import {PortablePath, xfs, ppath}
from '@yarnpkg/fslib';
+-import NpmPlugin
from '@yarnpkg/plugin-npm';
+-import PatchPlugin
from '@yarnpkg/plugin-patch';
+-
+-import CompatPlugin
from '../sources/index';
+-
+-function getConfiguration(p: PortablePath) {
+- return Configuration.create(p, p, new Map([
+-[`@yarnpkg/plugin-compat`, CompatPlugin],
+-[`@yarnpkg/plugin-npm`, NpmPlugin],
+-[`@yarnpkg/plugin-patch`, PatchPlugin],
+- ]));
+-}
+-
+-async function createProject(configuration: Configuration, p: PortablePath,
manifest: object = {}) {
+- await xfs.writeFilePromise(ppath.join(p, `package.json`),
JSON.stringify(manifest));
+-
+- return Project.find(configuration, p);
+-}
+-
+-async function getDescriptorCandidates(descriptor: Descriptor) {
+- return await xfs.mktempPromise(async dir => {
+-const configuration = getConfiguration(dir);
+-const {project} = await createProject(configuration, dir);
+-
+-const resolver = configuration.makeResolver();
+-const resolveOptions: ResolveOptions = {project, resolver, report: new
ThrowReport()};
+-
+-const normalizedDescriptor =
configuration.normalizeDependency(descriptor);
+-const candidates = await resolver.getCandidates(normalizedDescriptor, {},
resolveOptions);
+-
+-return candidates;
+- });
+-}
+-
+-/**
+- * A Set used to keep track of the test candidates, so we only test each
candidate once.
+- */
+-const testedCandidates: Set = new Set();
+-
+-async function testCandidate(locator: Locator) {
+- if (testedCandidates.has(locator.locatorHash))
+-return;
+-
+- testedCandidates.add(locator.locatorHash);
+-
+- await xfs.mktempPromise(async dir => {
+-const configuration = getConfiguration(dir);
+-const {project} = await createProject(configuration, dir, {
+- dependencies: {
+-[structUtils.stringifyIdent(locator)]: locator.reference,
+- },
+-});
+-const cache = await Cache.find(configuration);
+-
+-await project.resolveEverything({
+- cache,
+- lockfileOnly: false,
+- report: new ThrowReport(),
+-});
+-
+-let error: Error | null = null;
+-
+-try {
+- await project.fetchEverything({
+-cache,
+-report: new ThrowReport(),
+- });
+-} catch (e) {
+- error = e;
+-}
+-
+-if (error) {
+- expect(error.message).not.toContain(`Canno
Processed: Re: librust-ashpd-dev: impossible to install
Processing control commands: > block -1 by 1069621 Bug #1074396 [librust-ashpd-dev] librust-ashpd-dev: impossible to install 1074396 was not blocked by any bugs. 1074396 was not blocking any bugs. Added blocking bug(s) of 1074396: 1069621 -- 1074396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074396: librust-ashpd-dev: impossible to install
Control: block -1 by 1069621 On Thu, 27 Jun 2024 23:48:44 +0200 Jonas Smedegaard wrote: Package: librust-ashpd-dev > Version: 0.6.7-1+b1 > Severity: grave > Justification: renders package unusable > Package is impossible to install: Depends on missing packages, including librust-gdk4-wayland-0.7+default-dev. I know; this was a somewhat deliberate choice as I wanted to push gtk4 into unstable when event-listener and affected packages were not ready. Once those are resolved I need to update zbus to 4.0 fixing this. best, werdahias
Bug#1074396: librust-ashpd-dev: impossible to install
Package: librust-ashpd-dev Version: 0.6.7-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package is impossible to install: Depends on missing packages, including librust-gdk4-wayland-0.7+default-dev. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ93jkACgkQLHwxRsGg ASFzkQ/+JXklHxlgZH6vKhldtUJKNdZaOLSqZpqIVKLpd/W0IQE0+NlBf2bEjR9s kS6VtrQDp6Um8RYqmZ26iLZmUKpTDqNpQGjW8nL0Fwks2Ur0ERqGTMzz/P8+nA9U hb34xfIQoTSqMPJ93qIOlPAJxBtfRfXBXr7/T4N/VL+KBFqx9ch5/BRGFyOS84KU 3Xx7jOK9B8sQ1jrDBwQRMYA9PK5zSmRR7OFZwNpssIQxzeMchkV40/DPy4CY746o Pq+1/2kYvuXhze8poGEMs0ZpLjkOQq59wsZAj8E13PHZhUgZ8ziV0S6uLUt+qMA5 ACcZchHWAkFZkMxviyKneKqNhPEE9V3tiBjVik6UYVRsz5fDVF3VSiL6g65Ms4tl dbXsb4BawKWzadKdiow3asCQVuyz8Puea82Txov4qPb/T7m7dZ/gJ/XOJnggrRBZ ZKjo+Mh3jE7p9VEP2NN5h12ErOSoVRafe3Tc/ZzAwk4qVIqvhCNnt5ImCpdJ8KXP QaBTF9h8lky0oKvpdRacxAmwhzlLpr/3FZz1hd1AOj5l5yh7QV+QqXqwvD0fFMG5 G4gWo183WPf/3dtTDgjKigtwEiep28HgYN6A8uT/81Y/m/AdCwR8oMmfa41TuGJo Gdhp1KLFkCtQtZ4qoIPZq4Lr3EPNCfrhehNbYIk8bUaT/oYcjc8= =hxpX -END PGP SIGNATURE-
Bug#1074351: marked as done (rust-curve25519-dalek: RUSTSEC-2024-0344)
Your message dated Thu, 27 Jun 2024 21:35:24 + with message-id and subject line Bug#1074351: fixed in rust-curve25519-dalek 4.1.3+20240618+dfsg-1 has caused the Debian Bug report #1074351, regarding rust-curve25519-dalek: RUSTSEC-2024-0344 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.) -- 1074351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-curve25519-dalek Version: 4+20240603+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/dalek-cryptography/curve25519-dalek/pull/659 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi There is RUSTSEC-2024-0344 provided for rust-curve25519-dalek, can you have a look for unstable? https://rustsec.org/advisories/RUSTSEC-2024-0344.html https://github.com/dalek-cryptography/curve25519-dalek/pull/659 Regards, Salvatore --- End Message --- --- Begin Message --- Source: rust-curve25519-dalek Source-Version: 4.1.3+20240618+dfsg-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of rust-curve25519-dalek, 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 1074...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated rust-curve25519-dalek 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: Thu, 27 Jun 2024 22:49:57 +0200 Source: rust-curve25519-dalek Architecture: source Version: 4.1.3+20240618+dfsg-1 Distribution: unstable Urgency: high Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1074351 Changes: rust-curve25519-dalek (4.1.3+20240618+dfsg-1) unstable; urgency=high . [ upstream ] * new release; fixes RUSTSEC-2024-0344; closes: bug#1074351, thanks to Salvatore Bonaccorso . [ Jonas Smedegaard ] * rename patch 1002, and update DEP-3 headers * update watch file: bump base version * set urgency=high due to security bugfix * bump project versions in virtual packages and autopkgtests Checksums-Sha1: 230c291c9da895f43be9e21e18ae0172b814153d 5684 rust-curve25519-dalek_4.1.3+20240618+dfsg-1.dsc b1c08044af821ad7e312e25011e61050ff1f902d 595456 rust-curve25519-dalek_4.1.3+20240618+dfsg.orig.tar.xz a03b48e5061cf16a96bd97cc54ba64212756c800 20056 rust-curve25519-dalek_4.1.3+20240618+dfsg-1.debian.tar.xz c03c62bfcbea819b8f9eeac64a9f865c97df9404 15627 rust-curve25519-dalek_4.1.3+20240618+dfsg-1_amd64.buildinfo Checksums-Sha256: cb25d486a7b1663d25594aef7a0043affbcb5171e3a694ca74e6a92a63f752b5 5684 rust-curve25519-dalek_4.1.3+20240618+dfsg-1.dsc dd943696774ac4f0d2bb00d9a4be7225d441661066089f466213c80cce2fa99d 595456 rust-curve25519-dalek_4.1.3+20240618+dfsg.orig.tar.xz e389b36e57fd020c07e9ba9f588622b18e077e03b2e5bd4543bfb2824efe82cd 20056 rust-curve25519-dalek_4.1.3+20240618+dfsg-1.debian.tar.xz 8939e6046b6e0071ab150573416576537551e8ded8a606a002abf46154cb09a3 15627 rust-curve25519-dalek_4.1.3+20240618+dfsg-1_amd64.buildinfo Files: 1af802eeb0f6f9b3b6d31309bd6a3fc8 5684 rust optional rust-curve25519-dalek_4.1.3+20240618+dfsg-1.dsc fa373ec02a39a0dc343a4e7fabdc6d35 595456 rust optional rust-curve25519-dalek_4.1.3+20240618+dfsg.orig.tar.xz e12862c2d420bc80ae779791f8adbe15 20056 rust optional rust-curve25519-dalek_4.1.3+20240618+dfsg-1.debian.tar.xz c574091e4eca3d247b120f228e395282 15627 rust optional rust-curve25519-dalek_4.1.3+20240618+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmZ90TYACgkQLHwxRsGg ASFahxAAgQhxVWg9RZlyKKXA0Y6kl/AkGWbk9r+W50NXtn3NhTVuK0JE22gmUfkh MPQXRX/objfmcFEaGztQdW8DsehK3YFkQ8UjQj9Ee1rE4l+1KdLHxPi7v1CAwIB4 YLu/TdwrzXIt84b2B4zGoyVGY2L0Xj9JdUrFk6+If1KWb+LS3Wm9mM9ZdmyZFVbH JV4NlDDUh6yS9nfxXS+BXfLbg8D6NRCg8yO1Gby0m4hoEz7lZme/0cKJilMTtcor K97PjOwP7+Zl6qaRYUQVxtCdhTIWkZXlxgw7WQCAonbQxscDKN2Orgbj0J1IZrij WkjWvvcCTPdmKYuof++7pq8LnMGKrI70qO/yHBTrGumgVsSjVIhtljl5sj9TNMyt HYxZEeCj9a8CULUKM9t57+I2KF2HQWdVvluhRvOMU+ZM/i5HhI+mvmOpmIsAgQdj 0wCM30Qd8mfFYV1sPq8NZcYzGYSHeoCR8DLjiJkJdmuSTKXYJ+NoLI7rp21McOS8 Aj9DJvYeKNX94/7QOTtbJojzw0cWXz
Bug#960638: marked as done (login no longer needs to be essential)
Your message dated Thu, 27 Jun 2024 23:25:38 +0200 with message-id and subject line #960638: make login non-essential has caused the Debian Bug report #960638, regarding login no longer needs to be essential 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.) -- 960638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: login Version: 1:4.8.1-1 Severity: wishlist Now that login no longer contains "su", it no longer needs to be an essential package. A system that doesn't run any getty processes or other means of logging in (such as a system using only ssh, or a chroot, or a system with no interactive users at all) may not need to have the login package installed. It should still have priority "required", and perhaps "Important: yes" so that apt makes sure the user doesn't remove it by accident, but it doesn't need "Essential: yes" anymore. - Josh Triplett -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages login depends on: ii libaudit1 1:2.8.5-3+b1 ii libc6 2.30-8 ii libcrypt1 1:4.4.16-1 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g1.3.1-5 login recommends no packages. login suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: shadow Source-Version: 1:4.15.2-3 I think the bugs have been shaken out where necessary. Let's hope this is true. Chris--- End Message ---
Bug#1074391: More information
Hi,
I get this backtrace (yadd could you get a glimpse)
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'esbuild' imported from
assemblyscript/assemblyscript/scripts/build.js
Did you mean to import
"file:///usr/lib/x86_64-linux-gnu/nodejs/esbuild/lib/main.js"?
at packageResolve (node:internal/modules/esm/resolve:854:9)
at moduleResolve (node:internal/modules/esm/resolve:927:18)
at defaultResolve (node:internal/modules/esm/resolve:1157:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
at ModuleWrap. (node:internal/modules/esm/module_job:87:39)
at link (node:internal/modules/esm/module_job:86:36) {
code: 'ERR_MODULE_NOT_FOUND'
In all the case maybe this package could be split between arch/not arch part
Bastien
signature.asc
Description: This is a digitally signed message part.
Bug#1074351: rust-curve25519-dalek: RUSTSEC-2024-0344
Quoting Salvatore Bonaccorso (2024-06-27 08:03:39) > There is RUSTSEC-2024-0344 provided for rust-curve25519-dalek, can you > have a look for unstable? > > https://rustsec.org/advisories/RUSTSEC-2024-0344.html > https://github.com/dalek-cryptography/curve25519-dalek/pull/659 Certainly - it is on its way now... Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: (No Subject)
Processing commands for cont...@bugs.debian.org: > retitle 1074379 wireplumber: Bluetooth profile switch crashes wireplumber Bug #1074379 [wireplumber] wireplumber: No sound on Jabra BT Headset Changed Bug title to 'wireplumber: Bluetooth profile switch crashes wireplumber' from 'wireplumber: No sound on Jabra BT Headset'. > severity 1074379 serious Bug #1074379 [wireplumber] wireplumber: Bluetooth profile switch crashes wireplumber Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 1074379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074391: esbuild: build esbuild main.js
Package: esbuild Version: 0.20.2-1 Severity: serious Justification: could not be imported from node Dear Maintainer, Could you build the node package esbuild ? Without it the package is broken from node point of view so serious bug. I can help here Bastien signature.asc Description: This is a digitally signed message part.
Processed: Re: [Pkg-clamav-devel] Bug#1073128: clamav: unaligned access on armhf architecture
Processing control commands: > forwarded -1 https://github.com/Cisco-Talos/clamav/pull/1293 Bug #1073128 [src:clamav] clamav: unaligned access on armhf architecture Set Bug forwarded-to-address to 'https://github.com/Cisco-Talos/clamav/pull/1293'. -- 1073128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073128 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073128: [Pkg-clamav-devel] Bug#1073128: clamav: unaligned access on armhf architecture
control: forwarded -1 https://github.com/Cisco-Talos/clamav/pull/1293 On 2024-06-24 22:10:27 [+0200], To Gianfranco Costamagna wrote: > Instead of arguing with me, you could forward it directly to upstream > and give a pointer to apply whatever upsteams did. Forwarded upstream. Would be nice if you could test it since it works for me eitherway… Sebastian
Bug#1073334: marked as done (recoll: FTBFS: internfile/mh_xslt.cpp:69:46: error: invalid conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’} [-fpermissive])
Your message dated Thu, 27 Jun 2024 18:09:03 +
with message-id
and subject line Bug#1073334: fixed in recoll 1.39.0-1
has caused the Debian Bug report #1073334,
regarding recoll: FTBFS: internfile/mh_xslt.cpp:69:46: error: invalid
conversion from ‘const xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka
‘_xmlError*’} [-fpermissive]
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.)
--
1073334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: recoll
Version: 1.36.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
> -I./common -Wall -Wno-unused -std=c++14 -I. -I./aspell -I./bincimapmime
> -I./common -I./index -I./internfile -I./rcldb -I./unac -I./utils -I./xaposix
> -DBUILDING_RECOLL -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2
> -DRECOLL_DATADIR=\"/usr/share/recoll\" -DREADFILE_ENABLE_ZLIB
> -DREADFILE_ENABLE_MINIZ -DREADFILE_ENABLE_MD5 -D_GNU_SOURCE -DHAVE_CONFIG_H
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c -o internfile/mh_xslt.lo
> internfile/mh_xslt.cpp
> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I./common -Wall -Wno-unused
> -std=c++14 -I. -I./aspell -I./bincimapmime -I./common -I./index
> -I./internfile -I./rcldb -I./unac -I./utils -I./xaposix -DBUILDING_RECOLL
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2
> -DRECOLL_DATADIR=\"/usr/share/recoll\" -DREADFILE_ENABLE_ZLIB
> -DREADFILE_ENABLE_MINIZ -DREADFILE_ENABLE_MD5 -D_GNU_SOURCE -DHAVE_CONFIG_H
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -fstack-clash-protection -Wformat
> -Werror=format-security -fcf-protection -c internfile/mh_xslt.cpp -fPIC
> -DPIC -o internfile/.libs/mh_xslt.o
> internfile/mh_xslt.cpp: In member function ‘xmlDoc* FileScanXML::getDoc()’:
> internfile/mh_xslt.cpp:69:46: error: invalid conversion from ‘const
> xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’}
> [-fpermissive]
>69 | xmlError *error = xmlGetLastError();
> | ~~~^~
> | |
> | const xmlError* {aka
> const _xmlError*}
> internfile/mh_xslt.cpp: In member function ‘virtual bool
> FileScanXML::data(const char*, int, std::string*)’:
> internfile/mh_xslt.cpp:98:46: error: invalid conversion from ‘const
> xmlError*’ {aka ‘const _xmlError*’} to ‘xmlError*’ {aka ‘_xmlError*’}
> [-fpermissive]
>98 | xmlError *error = xmlGetLastError();
> | ~~~^~
> | |
> | const xmlError* {aka
> const _xmlError*}
> internfile/mh_xslt.cpp: In constructor
> ‘MimeHandlerXslt::MimeHandlerXslt(RclConfig*, const std::string&, const
> std::vector >&)’:
> internfile/mh_xslt.cpp:162:33: warning: ‘int
> xmlSubstituteEntitiesDefault(int)’ is deprecated [-Wdeprecated-declarations]
> 162 | xmlSubstituteEntitiesDefault(0);
> | ^~~
> In file included from internfile/mh_xslt.cpp:25:
> /usr/include/libxml2/libxml/parser.h:953:17: note: declared here
> 953 | xmlSubstituteEntitiesDefault(int val);
> | ^~~~
> In file included from /usr/include/libxml2/libxml/parser.h:13:
> /usr/include/libxml2/libxml/xmlversion.h:500:44: warning: ‘int*
> __xmlLoadExtDtdDefaultValue()’ is deprecated [-Wdeprecated-declarations]
> 500 | #define XML_GLOBAL_MACRO(name) (*__##name())
> |^~
> /usr/include/libxml2/libxml/parser.h:900:37: note: in expansion of macro
> ‘XML_GLOBAL_MACRO’
> 900 | #define xmlLoadExtDtdDefaultValue
> XML_GLOBAL_MACRO(xmlLoadExtDtdDefaultValue)
> | ^~~~
> internfile/mh_xslt.cpp:163:5: note: in expansion of macro
> ‘xmlLoadExtDtdDefaultValue’
> 163 | xmlLoadExtDtdDefaultValue = 0;
> | ^
> /usr/include/libxml2/libxml/xmlversion.h:499:
Processed: This is a bug in gecode, not minizinc
Processing commands for cont...@bugs.debian.org: > retitle 1073819 flatzinc: mznlib is too old for current minizinc Bug #1073819 [minizinc-ide] minizinc-ide: Error at runtime on current testing/sid version. Changed Bug title to 'flatzinc: mznlib is too old for current minizinc' from 'minizinc-ide: Error at runtime on current testing/sid version.'. > reassign 1073819 flatzinc Bug #1073819 [minizinc-ide] flatzinc: mznlib is too old for current minizinc Bug reassigned from package 'minizinc-ide' to 'flatzinc'. No longer marked as found in versions minizinc-ide/2.8.2-1. Ignoring request to alter fixed versions of bug #1073819 to the same values previously set > found 1073819 6.2.0-5.1 Bug #1073819 [flatzinc] flatzinc: mznlib is too old for current minizinc Marked as found in versions gecode/6.2.0-5.1. > severity 1073819 important Bug #1073819 [flatzinc] flatzinc: mznlib is too old for current minizinc Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1073819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1069944: marked as done (purple-xmpp-http-upload: debian/shlibs.local hardcodes dependency on libpurple0)
Your message dated Thu, 27 Jun 2024 16:34:20 + with message-id and subject line Bug#1069944: fixed in purple-xmpp-http-upload 0.2.4-2.1 has caused the Debian Bug report #1069944, regarding purple-xmpp-http-upload: debian/shlibs.local hardcodes dependency on libpurple0 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.) -- 1069944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: purple-xmpp-carbons Version: 0.2.3-1 Severity: serious Tags: trixie sid debian/shlibs.local hardcodes a dependency on libpurple0, which makes the package uninstallable on armel/armhf due to the 64-bit time_t rename to libpurple0t64. --- End Message --- --- Begin Message --- Source: purple-xmpp-http-upload Source-Version: 0.2.4-2.1 Done: Arnaud Rebillout We believe that the bug you reported is fixed in the latest version of purple-xmpp-http-upload, 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 1069...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Rebillout (supplier of updated purple-xmpp-http-upload 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: Thu, 27 Jun 2024 23:12:00 +0700 Source: purple-xmpp-http-upload Architecture: source Version: 0.2.4-2.1 Distribution: unstable Urgency: medium Maintainer: DebianOnMobile Maintainers Changed-By: Arnaud Rebillout Closes: 1069944 Changes: purple-xmpp-http-upload (0.2.4-2.1) unstable; urgency=medium . * Non-maintainer upload. . [ Debian Janitor ] * Apply multi-arch hints. + purple-xmpp-http-upload: Add Multi-Arch: same. . [ Arnaud Rebillout ] * Fix shlibs.local file for t64 transition (Closes: #1069944) Checksums-Sha1: f1aca0fa634c5ad464f136bd1a50421a29850beb 2187 purple-xmpp-http-upload_0.2.4-2.1.dsc 7e8664e23032967786b1b4565e3e29cbe69e0be7 2644 purple-xmpp-http-upload_0.2.4-2.1.debian.tar.xz 4e7d4a978d5f33649e72d441c71c21412de33566 6117 purple-xmpp-http-upload_0.2.4-2.1_source.buildinfo Checksums-Sha256: 09cb6b1d70566a863155e989484e07f19b3d3ca302ae58753294870d08620aa9 2187 purple-xmpp-http-upload_0.2.4-2.1.dsc fcfc566dbe7fab8130e666bceafa2fb47cd71b0e5bbfe5b29980cfaec1a7b88b 2644 purple-xmpp-http-upload_0.2.4-2.1.debian.tar.xz c7cc2bb96a5f141230346676ae5545eec7f438b0abf0f43f87271fa6a13dbd0a 6117 purple-xmpp-http-upload_0.2.4-2.1_source.buildinfo Files: c6465316160bd2a333fd6333d87bf692 2187 net optional purple-xmpp-http-upload_0.2.4-2.1.dsc 6e0036821f643914efce3db9442f1d32 2644 net optional purple-xmpp-http-upload_0.2.4-2.1.debian.tar.xz 13c633d1ade2f8eaea0340b47394f1cc 6117 net optional purple-xmpp-http-upload_0.2.4-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmZ9kFURHGFybmF1ZHJA a2FsaS5vcmcACgkQ5yXoeRRgAhaEJg//ehtV8zxP6wI4yB9dKifwQtvaA9eXyvZM snEClXoNTX1ezFWWx335A2GDHHAPDle6ILBAWONvDUQW++UppMWz09U8kupf2rCD yQxijz8LsFBLMWHxdwlaYuGVa4seIEzdUEXgWlJxFinhGawVTzaZhzv9jgt40Fco hW/1qUT4bi0/HvRqlIy3hfmM6CieWF6gv38D+0vFu/m0SMe7MtTyHtJr5xgXx7Gn 9xbxIKhB+rNRvxGQG6Maj/vXdl35a5HU+tx/xRqlUnY35LXnL53yoY9dpaFoUeNP v5M84kCZCHXpWQGY2rzmG46GOapasHwow8VL2OOqKPnVNSY6sSDoePeQGklaq7qa rtnlg52wt7+BLtuS81Bs7mLUMLzQuhDVxqGiZj+iIm1NHbO7tzOiDreWh+wNdJXL QxhkacOrmnOAmwGWfdZj9xXDpIw5z9PpQOtoKjYqGHC6GVl0Ku31d8Bw7QIHI7ZX hgDxRvFodHo24arJiHnnYGk2XTJgJgMvpAb+Er8aC5ln6b2MLnAxThPV2Cpfv+kz W/1Rbxo2tp1zshsiPq3gE5ALUTWZQW8fumNn8l/3tNaMOkM0an7lyD1+2miY6EGf dHni3ZvANLW5WANj63wktizrzYDJEv7WkyfS/VOk7lt5lFpGrUhgW5Fv0C7JOK+x 26oIwUSj+bw= =Kdxn -END PGP SIGNATURE- pgpi61sNfD5x3.pgp Description: PGP signature --- End Message ---
Bug#1074384: slurm-wlm-basic-plugins, depends on 64-bit only library
Package: slurm-wlm-basic-plugins Version: 23.11.7-1 Severity: serious slurm-wlm-basic-plugins depends on libpmix2t64 and slum-wlm build-depends on , which is no longer available on 32-bit architectures. I notice that the build-dependency is already architecture restricted, but the runtime dependency is not, please investigate this discrepancy.
Bug#1072073: marked as done (python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py)
Your message dated Thu, 27 Jun 2024 15:10:50 + with message-id and subject line Bug#1072073: fixed in python-proto-plus 1.24.0-2 has caused the Debian Bug report #1072073, regarding python3-proto-plus has an undeclared file conflict on /usr/lib/python3/dist-packages/proto/__init__.py to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1072073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-proto-plus Version: 1.23.0-1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + nanopb python3-proto-plus has an undeclared file conflict. This may result in an unpack error from dpkg. The file /usr/lib/python3/dist-packages/proto/__init__.py is contained in the packages * nanopb * 0.4.4-2 as present in bullseye * 0.4.7-2 as present in bookworm * 0.4.8-1 as present in trixie|unstable * python3-proto-plus/1.23.0-1 as present in unstable These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected file. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. --- End Message --- --- Begin Message --- Source: python-proto-plus Source-Version: 1.24.0-2 Done: Yogeswaran Umasankar We believe that the bug you reported is fixed in the latest version of python-proto-plus, 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 1072...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yogeswaran Umasankar (supplier of updated python-proto-plus 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: Thu, 27 Jun 2024 10:00:00 + Source: python-proto-plus Architecture: source Version: 1.24.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Yogeswaran Umasankar Closes: 1072073 Changes: python-proto-plus (1.24.0-2) unstable; urgency=medium . * No source change upload to close bug issue that has already fixed. (Closes: #1072073) Checksums-Sha1: 6260cfb8420dac94f405e51b002023d83891d213 2375 python-proto-plus_1.24.0-2.dsc 518c5a313210e747193869f49e02aa0f531c6501 4468 python-proto-plus_1.24.0-2.debian.tar.xz 12f77a40e0ee0fd6459258f15937a73afec5759b 8037 python-proto-plus_1.24.0-2_arm64.buildinfo Checksums-Sha256: 786c1f3c6d1b084f99f8bf1aad2d806c34d923e194a93128ce9c04510c020344 2375 python-proto-plus_1.24.0-2.dsc bed09bdedfcee1c8fe33d3c36ce240af2da047a514dc7c9d59ce0e1042c85d9e 4468 python-proto-plus_1.24.0-2.debian.tar.xz 53eaabb24b1b0cf31f19246d3dc7b510300e343a5c40547f9d42cdebccf0746c 8037 python-proto-plus_1.24.0-2_arm64.buildinfo Files: 8929cd821f899927d8ec0b8f52b3b069 2375 python optional python-proto-plus_1.24.0-2.dsc 143e84d41a5a037bf040996418b5177e 4468 python optional python-proto-plus_1.24.0-2.debian.tar.xz 4a640c4fd2e0e96c552a66f0df6be795 8037 python optional python-proto-plus_1.24.0-2_arm64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/qLi99g13V/he2oYtIOKvyeCVXsFAmZ9duUACgkQtIOKvyeC VXuv8g//Xui9JYw0gK/H8CW326KueXF5Qqqig/ayrKYfruVWQAw8j5OYfAIiqyLE uf257x/PX17Pywz11CCpe+BI1KiEjmaGwGJfClSt9qfb6lHavXMFtMPNP8mixYkF ntyaL5C/AS6eLo8Kg2zil3XM8HWAO6Y6VpmAfFcrhm/XEJyijAoF6WLHoRjsztxa ++nBikDTeet3b9VYlhA6uhRuGzIQgV2obkcSG/j5SJ8RiZREunM7G7W4V4UIf+GR fDbXWGu9/VCDiFFH0Iehmt9MJDC3SPO7Iw6i2BUAsPl/oNJAuR9qxPIeRgL99tvM /IxNQVG3deFMmH7nrYzRzmWn/t/2hhN9ZqVU6PHgndb3yo8a5i2qamTBiNh/Mu0E Sg94iPrm1VXvXrGHI7DFQhEUDrDAjPfnAntO703eHYMoFsskwqyPcNGjojqB8Odj YJYy1wf2TKvmDRKIdkwL05o1RcN2z9BAXUNv6SraIP5kwwWAn2BrTubWQr4Qt816 9NnzaTWrzfGGh/Inl9a8EfV0mk9UUUSTtmQpQzbA/jiOUkmv7Nn0PVqqfx5qdBon FqOodIwrfqGO+9qwrK7cJg6mTu7GZVuuPbraw97F0fHn0IiejogJVd/uiScg/jTp VEvPi3xq+92ZvhnPViNz447P+NYp/G+qCHn827VUrM3QucZsz9s= =cdf4 -END PG
Bug#1073446: marked as done (python-pyfakefs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)
Your message dated Thu, 27 Jun 2024 12:35:44 +
with message-id
and subject line Bug#1073446: fixed in python-pyfakefs 5.5.0-1
has caused the Debian Bug report #1073446,
regarding python-pyfakefs: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.12 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.)
--
1073446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyfakefs
Version: 5.3.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build"
> module
> I: pybuild base:311: python3.12 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.12_pyfakefs
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pyfakefs
> copying pyfakefs/__init__.py -> build/lib/pyfakefs
> copying pyfakefs/fake_scandir.py -> build/lib/pyfakefs
> copying pyfakefs/fake_pathlib.py -> build/lib/pyfakefs
> copying pyfakefs/_version.py -> build/lib/pyfakefs
> copying pyfakefs/fake_filesystem_unittest.py -> build/lib/pyfakefs
> copying pyfakefs/fake_open.py -> build/lib/pyfakefs
> copying pyfakefs/fake_filesystem_shutil.py -> build/lib/pyfakefs
> copying pyfakefs/extra_packages.py -> build/lib/pyfakefs
> copying pyfakefs/fake_filesystem.py -> build/lib/pyfakefs
> copying pyfakefs/helpers.py -> build/lib/pyfakefs
> copying pyfakefs/fake_file.py -> build/lib/pyfakefs
> copying pyfakefs/patched_packages.py -> build/lib/pyfakefs
> copying pyfakefs/fake_io.py -> build/lib/pyfakefs
> copying pyfakefs/mox3_stubout.py -> build/lib/pyfakefs
> copying pyfakefs/fake_path.py -> build/lib/pyfakefs
> copying pyfakefs/pytest_plugin.py -> build/lib/pyfakefs
> copying pyfakefs/fake_os.py -> build/lib/pyfakefs
> creating build/lib/pyfakefs/tests
> copying pyfakefs/tests/mox3_stubout_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_os_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/__init__.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/import_as_example.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/patched_packages_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/dynamic_patch_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/mox3_stubout_example.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_filesystem_glob_test.py ->
> build/lib/pyfakefs/tests
> copying pyfakefs/tests/all_tests_without_extra_packages.py ->
> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_stat_time_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_pathlib_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/all_tests.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/example.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/example_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/test_utils.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_filesystem_unittest_test.py ->
> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_filesystem_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_tempfile_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_filesystem_shutil_test.py ->
> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_open_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/fake_filesystem_vs_real_test.py ->
> build/lib/pyfakefs/tests
> copying pyfakefs/tests/performance_test.py -> build/lib/pyfakefs/tests
> copying pyfakefs/tests/logsio.py -> build/lib/pyfakefs/tests
> creating build/lib/pyfakefs/pytest_tests
> copying pyfakefs/pytest_tests/pytest_module_fixture_test.py ->
> build/lib/pyfakefs/pytest_tests
> copying pyfakefs/pytest_tests/pytest_doctest_test.py ->
> build/lib/pyfakefs/pytest_tests
> copying pyfakefs/pytest_tests/__init__.py -> build/lib/pyfakefs/pytest_tests
> copying pyfakefs/pytest_tests/pytest_plugin_failing_helper.py ->
> build/lib/pyfakefs/pytest_tests
> copying pyfakefs/pytest_tests/pytest_
Bug#1074375: astra-toolbox: autopkgtest failure: ModuleNotFoundError: No module named 'six'
Source: astra-toolbox Version: 2.1.0-4 Severity: serious Tags: ftbfs https://ci.debian.net/packages/a/astra-toolbox/testing/amd64/47130959/ 35s autopkgtest [10:02:03]: test autodep8-python3: [--- 35s Testing with python3.11: 35s Traceback (most recent call last): 35s File "", line 1, in 35s File "/usr/lib/python3/dist-packages/astra/__init__.py", line 26, in 35s from . import matlab as m 35s File "/usr/lib/python3/dist-packages/astra/matlab.py", line 38, in 35s from . import astra_c 35s File "astra/astra_c.pyx", line 30, in init astra.astra_c 35s ModuleNotFoundError: No module named 'six' 35s autopkgtest [10:02:03]: test autodep8-python3: ---] 36s autodep8-python3 FAIL non-zero exit status 1 also reproducible with python3.12: autopkgtest [14:20:37]: test autodep8-python3: set -e ; for py in $(py3versions -d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import astra; print(astra)" ; done autopkgtest [14:20:37]: test autodep8-python3: [--- Testing with python3.12: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/astra/__init__.py", line 26, in from . import matlab as m File "/usr/lib/python3/dist-packages/astra/matlab.py", line 38, in from . import astra_c File "astra/astra_c.pyx", line 30, in init astra.astra_c ModuleNotFoundError: No module named 'six' autopkgtest [14:20:38]: test autodep8-python3: ---] autopkgtest [14:20:38]: test autodep8-python3: - - - - - - - - - - results - - - - - - - - - - autodep8-python3 FAIL non-zero exit status 1 autopkgtest [14:20:38]: summary autodep8-python3 FAIL non-zero exit status 1 Andreas
Bug#1073050: marked as done (rdma-core: Fails to build on several architectures: dh_install missing files)
Your message dated Thu, 27 Jun 2024 12:20:55 + with message-id and subject line Bug#1073050: fixed in rdma-core 52.0-2 has caused the Debian Bug report #1073050, regarding rdma-core: Fails to build on several architectures: dh_install missing files 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.) -- 1073050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdma-core Version: 52.0-1 Severity: serious Tags: ftbfs rdma-core is failing to build on multiple architectures including the release architectures armel and armhf. Build logs https://buildd.debian.org/status/package.php?p=rdma-core Build log excerpt -- dh_install: warning: ibverbs-providers missing files: usr/lib/*/libhns.so.* dh_install: warning: libibverbs-dev missing files: usr/include/infiniband/hnsdv.h dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.a dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.so dh_install: warning: libibverbs-dev missing files: usr/lib/*/pkgconfig/libhns.pc dh_install: warning: libibverbs-dev missing files: usr/share/man/man3/hnsdv_*.3 dh_install: warning: libibverbs-dev missing files: usr/share/man/man7/hnsdv.7 Thank you, Jeremy Bícha --- End Message --- --- Begin Message --- Source: rdma-core Source-Version: 52.0-2 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of rdma-core, 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 1073...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated rdma-core 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: Thu, 27 Jun 2024 13:49:34 +0200 Source: rdma-core Built-For-Profiles: noudeb Architecture: source Version: 52.0-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 1073050 Changes: rdma-core (52.0-2) unstable; urgency=medium . * Exclude hns provider on archs without coherent DMA (Closes: #1073050) Checksums-Sha1: a5df48097b801cd665c67f703d7b918800797a79 3201 rdma-core_52.0-2.dsc 20e8d5408226bff8e1e83052a4fa29238be77660 24268 rdma-core_52.0-2.debian.tar.xz e02373f683d6d79c531b8ef973a3137cf5d57f85 9266 rdma-core_52.0-2_source.buildinfo Checksums-Sha256: 50f8f58712bbfbd5be42a4edfa4c4f3a1aa274eebf56e513a1d8a7e8fc8c3902 3201 rdma-core_52.0-2.dsc 6e06ac02aab7586a841bc9e1fc4c2d0bf38f5e0f15cdefca50f5a95129f6280d 24268 rdma-core_52.0-2.debian.tar.xz f7c8615237c6c12641b92a0f372b43bda53e650a8b733c6617f3fb362a2d9665 9266 rdma-core_52.0-2_source.buildinfo Files: ec87ce38e9ca246e87ffbb04c064f693 3201 net optional rdma-core_52.0-2.dsc cfccbf7c71acaa5df87040fca569cb38 24268 net optional rdma-core_52.0-2.debian.tar.xz 0166a108c0146484c31618125d66d88d 9266 net optional rdma-core_52.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmZ9VX4ACgkQFZ61xO/I d0xNgw//Z6U4xdsQeYr2LPe6w/SsV83u9KnLr/0B9PgVYqwuMw+fYVQ2veeqGS0O x887pccWQeuxlE6BnqyOnzHBCNKbMSfc08zbwOA4B3fJhPO+zo9cQZzGjEGtDduW jvA82zr44jt6u5FLgDJzFdWwxqqWXS/rbIK/b3fPO3hCqlxAus9+pYqkyEk946jA XQhuBIGs1BPPGiva4AT0kU4qfjaJmYHTx8EaMaU/MApe/QVHNr/7IQuq911c/z5O 8Vk/3IcDC5cYbExp9o36zZdXQzXvYNgaevBnIvwusuS6C5Jd4dtB7XCXmHrJYukU zMWX5VFH2QaxIa7jCDosXxlwDmxuTSv2kk51tpQre3LOjtP9vvoYHnyfO6OQGf8R hatDwu53g8Yr241d/Pvdhz2/Xob41mcsZW5O5wrG0G+e9BGaO7Wz05kJCQkBfoTn ftfnNlFqsLm4+dRRXtR0TtKoKbx0OgfQUxfN0HHLJsOFn0jlATdEnwNGl8w0ttUY i7nJb/FjcNFkQj+gF22GNeIa16zg6dK1sRYiwkDOIg2MbzxYQyHABF6m0HHDLLH2 HrUPzf39FkzQVHohKl0wQeb9vj59xh1mN8reUe2F1MJgPKDsTTuSlwfTVB8EiCUO gMy7D9tHvZ8a1zfYDBCqyR0RJ1uzmazKEh4douNLlsJZf5avG80= =vrj5 -END PGP SIGNATURE- pgpIaUXLypYSP.pgp Description: PGP signature --- End Message ---
Bug#1073446: marked as pending in python-pyfakefs
Control: tag -1 pending Hello, Bug #1073446 in python-pyfakefs 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-pyfakefs/-/commit/9b2db88cc28daca4f7619fb150ec61cc46de32a4 New upstream version 5.5.0. (Closes: #1073446) (this message was generated automatically) -- Greetings https://bugs.debian.org/1073446
Processed: Bug#1073446 marked as pending in python-pyfakefs
Processing control commands:
> tag -1 pending
Bug #1073446 [src:python-pyfakefs] python-pyfakefs: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit
code 13
Added tag(s) pending.
--
1073446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1074370: ffmpeg: Fails to build on armel & armhf
Source: ffmpeg Version: 7:6.1.1-4 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: armel armhf X-Debbugs-CC: debian-...@lists.debian.org ffmpeg is failing to build on armel & armhf (but not arm64). This was noticed while rebuilding ffmpeg for the ongoing jpeg-xl 0.9 transition. I don't believe the build failure is related to the new version of jpeg-xl. The last successful official build before this was on June 9. Build log excerpt -- src/libavcodec/arm/mlpdsp_armv5te.S: Assembler messages: src/libavcodec/arm/mlpdsp_armv5te.S:232: Error: junk at end of line, first unrecognized character is `0' src/libavcodec/arm/mlpdsp_armv5te.S:367: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:393: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:414:Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:244: Error: garbage following instruction -- `bne 01b' src/libavcodec/arm/mlpdsp_armv5te.S:367: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:393: Info: macro invoked from here src/libavcodec/arm/mlpdsp_armv5te.S:414:Info: macro invoked from here Full build logs -- https://buildd.debian.org/status/package.php?p=ffmpeg Thank you, Jeremy Bícha
Bug#1073355: marked as done (ghmm: FTBFS: xmlwriter.c:1105:5: error: implicit declaration of function ‘xmlSubstituteEntitiesDefault’ [-Werror=implicit-function-declaration])
Your message dated Thu, 27 Jun 2024 09:57:43 + with message-id and subject line Bug#1073355: fixed in ghmm 0.9~rc3-7 has caused the Debian Bug report #1073355, regarding ghmm: FTBFS: xmlwriter.c:1105:5: error: implicit declaration of function ‘xmlSubstituteEntitiesDefault’ [-Werror=implicit-function-declaration] 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.) -- 1073355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghmm Version: 0.9~rc3-6 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20240615 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -c -o foba.lo foba.c > xmlwriter.c: In function ‘ghmm_xmlfile_write’: > xmlwriter.c:1105:5: error: implicit declaration of function > ‘xmlSubstituteEntitiesDefault’ [-Werror=implicit-function-declaration] > 1105 | xmlSubstituteEntitiesDefault(1); > | ^~~~ > xmlwriter.c:1166:3: error: implicit declaration of function > ‘xmlCleanupParser’ [-Werror=implicit-function-declaration] > 1166 | xmlCleanupParser(); > | ^~~~ > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -c -o viterbi.lo viterbi.c > model.c: In function ‘ghmm_dmodel_free’: > model.c:632:33: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > 632 | mes_check_ptr (mo, return (-1)); > | ^ > model.c:634:32: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > 634 | mes_check_ptr (m, return (-1)); > |^ > model.c: In function ‘ghmm_dstate_clean’: > model.c:1758:35: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > 1758 | mes_check_ptr (my_state, return;); > | ^ > /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -c -o reestimate.lo reestimate.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -c foba.c -fPIC -DPIC -o .libs/foba.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/libxml2 -c viterbi.c -fPIC -DPIC -o .libs/viterbi.o > foba.c: In function ‘ghmm_dmodel_backward’: > foba.c:286:37: warning: macro "__DATE__" might prevent reproducible builds > [-Wdate-time] > 286 | mes_check_0 (scale[t], goto STOP); > | ^ > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -DDTD_LOC=\"/usr/share/ghmm/ghmm.dtd.1.0\" -g -O2 > -Werror=implicit-function-declaration "-ffile-prefix-map=/<>=." > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -I/usr/include/x86_64-linux-gnu > -I/usr/include/li
Processed: src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary
Processing control commands: > close -1 0.22.2-1 Bug #1074362 [src:ruby-redis-client] src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions ruby-redis-client/0.22.2-1. Bug #1074362 [src:ruby-redis-client] src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary Marked Bug as done -- 1074362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1074362: src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary
Source: ruby-redis-client Version: 0.19.1-2 Severity: serious Control: close -1 0.22.2-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:ruby-redis-client has been trying to migrate for 31 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=ruby-redis-client OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1064135: bigmemory: fails to migrate to testing for too long: autopkgtest fails on arm*, ppc64el and s390x
Hi Michael, I've opened issue #115 on Github four months ago but there is no activity so far. Could you please confirm that you are watching the issue tracker on Github or are you possibly using some other development platform? Just asking since the tags lagging behind the versioned tarballs at CRAN. Kind regards Andreas. [1] https://github.com/kaneplusplus/bigmemory/issues/115 -- https://fam-tille.de
Processed: 1072971 also affects pyside2
Processing commands for cont...@bugs.debian.org: > affects 1072971 + src:pyside2 Bug #1072971 [mesa] mesa: fails to initialize OpenGL on s390x: Unexpected format PIPE_FORMAT_X8B8G8R8_SRGB in st_new_renderbuffer_fb Added indication that 1072971 affects src:pyside2 > thanks Stopping processing here. Please contact me if you need assistance. -- 1072971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1073338
Processing commands for cont...@bugs.debian.org:
> close 1073338 1.4.5-1
Bug #1073338 [src:r-cran-xslt] r-cran-xslt: FTBFS: xslt_init.cpp:36:37: error:
invalid conversion from ‘void (*)(void*, xmlError*)’ {aka ‘void (*)(void*,
_xmlError*)’} to ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void*, const
_xmlError*)’} [-fpermissive]
Marked as fixed in versions r-cran-xslt/1.4.5-1.
Bug #1073338 [src:r-cran-xslt] r-cran-xslt: FTBFS: xslt_init.cpp:36:37: error:
invalid conversion from ‘void (*)(void*, xmlError*)’ {aka ‘void (*)(void*,
_xmlError*)’} to ‘xmlStructuredErrorFunc’ {aka ‘void (*)(void*, const
_xmlError*)’} [-fpermissive]
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1073338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
On Wed, Jun 26, 2024 at 7:12 PM Adrian Bunk wrote: > > >... > > So could we rebuild it again? > > Still fails on the buildd: > https://buildd.debian.org/status/fetch.php?pkg=pycorrfit&arch=amd64&ver=1.1.7%2Bdfsg-2%2Bb2&stamp=1719400031&raw=0 > > Based on the error message, I wouldn't be surprised if the +b2 from the > binNMU version would be part of the problem. So if I understand correctly, the ftbfs should be fixed if we do a new upload. let me try it. BR, Bo > > > Regards, > > cu > Adrian
Bug#1074343: src:texlive-bin: fails to migrate to testing for too long: unresolved RC issue
Hi Hilmar, On 26-06-2024 11:33 p.m., Preuße, Hilmar wrote: As you noticed this bug is just an Migration blocker bug, the only reason is to present the migration to testing for now. I can close it at any point in time, when I think the time is up. Same for #1072054 and I would have done this in one of the next days. Thanks for the feedback. I *guessed* as much, but to say frankly that blocker bug is missing context for outsiders. Why did you want it blocked? What needs to happen for the bug to be closed? Can interested people follow the progress somewhere? It's absolutely fine to block bad packages (which is foremost a maintainer judgement call) and the release team is happy that you do that. And as long as there's progress, you can take all time needed. For non-key packages, the autoremoval timer is reset every time the RC bugs are updated. texlive-bin is (currently) a key package, so this bug serves only a tracking purpose [1] as it will not be autoremoved. Paul [1] https://udd.debian.org/dev/bugs.cgi?release=trixie&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=out-of-sync&fusertaguser=release.debian.org%40packages.debian.org&rc=1&ckeypackage=1&clastupload=1&cautormtime=1&sortby=lastupload_s&sorto=asc&format=html#results OpenPGP_signature.asc Description: OpenPGP digital signature
