Hello, next time better first reassign the bug to the right package, and affect it.
E.g. (untested) reassign 1090262 libequihash affects 1090262 src: pwdsphinx and then close in libequihash. Now I did play a little bit with bts marking the "affected version" as "not affected anymore", maybe this will let britney think they can migrate now. Otherwise you have to reassign both bugs to libequihash, forcemerge, mark as fixed, and this should do the trick G. Il mercoledì 1 gennaio 2025 alle ore 11:15:12 CET, Tobias Frost <t...@debian.org> ha scritto: On Wed, Jan 01, 2025 at 09:51:48AM +0100, Joost van Baal-Ilić wrote: > Hi, > > At https://tracker.debian.org/pkg/pwdsphinx > it says: "Updating pwdsphinx would introduce bugs in testing: #1090262" . > > And at https://tracker.debian.org/pkg/pyequihash it says: "Marked for > autoremoval on 14 January: #1090264" . > > However, afaiu, both https://bugs.debian.org/1090262 and > https://bugs.debian.org/1090264 are closed. > > (They are about "FTBFS: ValueError: Unable to find libequihash", which was > fixed in the libequihash 1.0.10-2 upload at december 15; I closed the bugs > manually after that.) > > What can I do to make sure both src:pwdsphinx and src:pyequihash will get > shipped with upcoming trixie release? What am I missing here? Best thing is of course to close bugs via debian/changelog. In this case, you need to tell the BTS when the bug has been fixed, for example by "bts fixed 1090262 1.99.2-beta-5", assuming your last upload. 1090264: The bug is filed against src:pyequihash, but fixed in src:pwdsphinx/1.99.2-beta-2? Is this intentional? 1090264#20 indicates it is not, so please fix the meta data and hint the bts about the right version it has been fixed, like shown above. -- tobi -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled fixed the issue. (see bts(1) for this nice tool.) > Thanks! Bye, > > Joost > > -- > happy 45² ! >
