On Tuesday 05 June 2007 09:39:27 Axel Thimm wrote: > No, you also got it wrong. I'm not talking rebuilding from scratch, > but against rawhide. That's what all mass-rebuild were like until now. > > Both rebuilds will succeed (unless there is a bug in the package and > that would be good, so we can fix it): the first one will have > buildrequires from FC6->F7 since that's what the repo looked like, the > second will have fresh buildrequires from the previous pass. No need > to look at N-folded-recusion. You're still not getting it as well. Are you talking about building one package a day so that said rebuilt package is assured to be in the buildroot? If you rebuild A, the rebuilt A (well call it A.1) isn't available in the buildroot for another 20+ minutes. Quite a bit more if there are 4K other builds queued up. So B which is next on the list rebuilds against the old A, not A.1, C rebuilds against B, not B.1, D against A, and B, not the .1's. The next time you build, you get A.2, B.2 rebuilt against A.1, C.2 rebuilt against A.1 and B.1 (which is still a build against A, not A.1), so on and so forth. The only way to ensure that everything is up to date is to insert delays inside the chain (using something like chain-build) so that A builds to A.1, pause for it to be in the buildroot, B rebuilds against A.1 to become B.1, pause for it to be in the buildroot, C rebuilds against B.1 and A.1 to become C.1, etc... This is just one chain, there are /many/. -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpPzx4swfel1.pgp
Description: PGP signature
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
