Hi Abou, On 30-10-2021 12:46, Abou Al Montacir wrote: >> "Just" rebuilding is not the solution to paper over such an issue, we'd >> need to prevent it from going unnoticed next time. It should show up on >> https://release.debian.org/transitions/ >> <https://release.debian.org/transitions/> with an auto-upperlimit-fpc >> transition such that the release team is automatically warned that >> rebuilds are needed and to prevent fpc from migrating until the rebuild >> happened and is ready to migrate too. > I don't know for now how to handle this efficiently. but the easiest way > is to say, each new upload of FPC triggers all libraries (not programs) > rebuild.
So all libraries need a Depends on a binary from src:fpc with an upper limit (generated during the build). In that way, the Debian infrastructure knows that a rebuild (or potentially manual action) is needed. We don't want it to be too tight. When you said "any new version of FPC" do you mean each patch level too, or on only minor level? How about Debian new uploads? Paul
OpenPGP_signature
Description: OpenPGP digital signature
