Hello Adam, Adam D. Barratt wrote on 2012-11-21 11:53:
> Ugh, what a mess. > > The two RC bugs you mention are merged, so closing one will by > definition close the other. However, they appear to refer to different > issues, so I'm not sure why they're merged in the first place. Both RC bugs concern a kernel 3.x problem, but technically they concern two different problems. I would be logical to unmerge these RC bugs. I want to do this before my upload. > If #642209 and #691340 are the same bug, they should *be* the same bug > (i.e. merged). As it is, the earlier bug will still be marked as > outstanding in testing after the above upload, whereas the newer RC bug > is still marked as applying to unstable, which it logically cannot. > #628919 claims to be fixed in testing already, due to the unversioned > -done. You are right, that's a mess. I will try to "repair" the flags of these bugs. > Please feel free to go ahead with the upload, and file an unblock bug > afterwards. The state of the bugs against chrony will need fixing up, > however, as above. Thank you. So I will do the next steps. --- Have a nice day. Joachim (Germany) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
