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
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
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
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
4 matches
Mail list logo
