Control: clone -1 -2 Control: reassign -2 valgrind Control: retitle -2 valgrind: armhf is broken On Sat, Dec 23, 2023 at 08:46:27AM +0100, Paul Gevers wrote: > Source: apt > Version: 2.7.6 > Severity: serious > Control: close -1 2.7.7 > Tags: sid trixie > User: release.debian.org@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:apt has been trying to migrate for 31 days [2]. Hence, > I am filing this bug. The version in unstable fails its own autopkgtest on > armhf. > > 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/msg00001.html > [2] https://qa.debian.org/excuses.php?package=apt > This is a release critical bug in valgrind. valgrind does not understand the new toolchain defaults like stack clash protection on armhf and just segfaults (in Ubuntu we have partially recovered by disabling stack clash protection but it crashes on invalid writes there, I suppose we need to rebuild some more apt dependencies without the flag...). As there doesn't appear to be any progress on the valgrind or toolchain sides to fix these issues, I'll go and disable valgrind on armhf in the next apt upload, but I am cloning this to valgrind to make it clear that it's horribly borked. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Attachment:
signature.asc
Description: PGP signature