Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: britney
Hi, Britney has code for dealing with "hijacked" binaries. Right now, Britney has two "modes" for dealing with hijacked binaries. * Unconditionally assume the "hijacked" binaries will migrate * Unconditionally assume the "hijacked" binaries will *not* migrate However, this seems a bit over-simplified. In reality, a binary is hijacked if and only if: * The source package migrating will bring a *newer* version of an existing binary from a *different* source. In other words, whether a migration will successfully hijack a binary is a property of the current state of "testing". This bug is a reminder to look into this and patch Britney as necessary to handle this situation correctly (or document why the current practise is correct, if this is the case). ~Niels -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150719163838.22672.14970.report...@mangetsu.thykier.net
