Your message dated Fri, 9 Jan 2026 21:33:48 +0100 with message-id <389f8398-bcc6-4ec2-8b0c-58a030acbd98@debian.org> and subject line Re: #145257 Re: [britney] migrations can break build-depends has caused the Debian Bug report #145257, regarding [britney] migrations can break build-depends 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 owner@bugs.debian.org immediately.) -- 145257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=145257 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [britney2] Does not consider B-D for migration to testing
- From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
- Date: Wed, 19 Dec 2018 23:02:31 +0100
- Message-id: <20181219220229.by74ffuu4m3veabu@breakpoint.cc>
Package: release.debian.org User: release.debian.org@packages.debian.org Usertags: britney Severity: normal Britney does not look at build dependencies before migrating a package. Therefore it can migrate a package to testing which build-depends did not yet migrate. As a result this package can be built in testing. As an example: pass-tomb 1.1-2 migrated to testing while kcov was not in testing. It has been pointed out on #d-release that there are checks this |< h01ger> https://qa.debian.org/dose/debcheck.html has links Sebastian
--- End Message ---
--- Begin Message ---
- To: 145257-done@bugs.debian.org
- Subject: Re: #145257 Re: [britney] migrations can break build-depends
- From: Paul Gevers <elbrus@debian.org>
- Date: Fri, 9 Jan 2026 21:33:48 +0100
- Message-id: <389f8398-bcc6-4ec2-8b0c-58a030acbd98@debian.org>
- In-reply-to: <[🔎] 83ad5da8-3a3e-4972-82cf-e369e33c9a31@debian.org>
- References: <f22f4651-f0e7-1ffa-3daf-e7839e36cfe1@zoho.com> <df5fe8b6-e6c6-9716-01dc-af0ba1b701e9@debian.org> <df5fe8b6-e6c6-9716-01dc-af0ba1b701e9@debian.org> <2e60b9d2-9ec9-4475-b61d-3c144b3b7bb0@debian.org> <[🔎] 83ad5da8-3a3e-4972-82cf-e369e33c9a31@debian.org>
Hi, On 1/4/26 16:43, Paul Gevers wrote:I'm trying to figure out what's special about that situation.It turns out that there was a flaw in the original code. It would fail to block migration if the to-be-broken package in the target suite was already fixed in the source suite. I have fixed that in commit 9843775 and now I consider this bug done.Paul PS: deployment is pending, probably tomorrowAttachment: OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---