Matt McCutchen (matt(a)mattmccutchen.net) said:
> At the moment, we 'solve' this by doing update pushes in
a certain
> order such that this should not happen. (Basically, any number of
> testing pushes, then a stable push, then the branched tree.)
In order to avoid packages temporarily disappearing, the stable push
should happen before the testing push, right? Am I missing something?
No, that would be what would *cause* the issue. The issue happens when
a stable push untags the packages from testing, and then a new testing
compose is done without those packages before they appear somewhere
else.
Bill