Your message dated Tue, 19 Mar 2024 20:34:38 +0100
with message-id
and subject line Re: Bug#1064428: [Britney] does not migrate new arch:all
packages after initial migration of same source
has caused the Debian Bug report #1064428,
regarding [Britney] does not migrate new arch:all packages after
To copy comments from our discussion in IRC...
In my case, blocking a migration until the entire Package-List is filled out or
waiting for arch: all binaries if the source package lists all as an
architecture does not solve the problem. I regularly put Britney2 in situations
where a package doe
Hi Paul,
Thanks very much for your reply.
For what it's worth, I don't necessarily need britney2 to handle these
migrations "correctly", and I don't think Debian does either. However,
there is some behavior instability when arch-indep and arch-dep packages
are proposed in different ways in the sa
Hi Dalton,
Good to have this discussion. I'll add a few remarks on behavior in
Debian in this e-mail.
On 21-02-2024 23:50, Dalton Durst wrote:
test-src migrated after its amd64 and i386 binaries appeared. It also
has architecture-independent binaries that miraculously only showed up
after mig
Sorry, missed the links mentioned by [1] and [2] in the above mail.
[1]
https://salsa.debian.org/release-team/britney2/-/commit/b1603db2e459a2499de76d38179e49107d46be9d#7440b429abaafd59360558493c5473fab20e5088_0_425
[2]
https://salsa.debian.org/release-team/britney2/-/blob/7544ecb2b24e00344f7491
Package: release.debian.org
Severity: normal
Usertags: britney
Consider the following situation:
test-src migrated after its amd64 and i386 binaries appeared. It also
has architecture-independent binaries that miraculously only showed up
after migration was complete (maybe someone hinted through
6 matches
Mail list logo
