Hi Santiago, Quoting Santiago Vila (2024-08-30 14:25:39) > My use case is that sometimes I need to know in which date > some package stopped failing to build in testing because > an unknown build-dependency finally propagated to testing. > > For that to happen I need either: > > (A) Create a usr-merged buildd chroot of bookworm, then upgrade to the > desired trixie at some unspecified date using snapshot.debian.org. > > (B) Create a non-usr-merged buildd chroot of bookworm, usr-merge it, > then upgrade to snapshot.debian.org. > > What is the route that I'm supposed to follow? > > Do you disagree that at least one of those two options should be fully > supported?
Why the upgrade step? Why do you not create a trixie buildd chroot from a given snapshot.d.o timestamp directly? Do you do that because you also want to test the upgrade scenario? If you do not need the upgrade part, there is the tool debootsnap which creates a chroot with precisely the package versions you require without upgrading, for example from a buildinfo file. There is also the tool "debbisect" which I usually use to track down when a package started to FTBFS in unstable (but you can use it for testing all the same). Just recently I ran this to track down #1077452: $ DEBIAN_BISECT_SRCPKG=picolibc debbisect --cache=./cache 2024-02-26 2024-08-27 /usr/share/doc/devscripts/examples/debbisect_buildsrc.sh That this is possible does of course not invalidate your question whether either of your options above should be fully supported. I just wanted to let you know that maybe there is a practical solution for your use-case that works better than what you are currently doing. Thanks! cheers, josch
signature.asc
Description: signature
