Hi Adam, sorry for the late reply… On Fri, May 05, 2017 at 08:41:30AM +0100, Adam D. Barratt wrote: > Recently I've noticed that a few packages from proposed-updates seem to be > ending up in a state of "cannot be tested", with logs that suggest an issue > locating the package. [...] > The previous packages that I saw in this state resolved themselves within a > day or so, so I assume were rescheduled. not exactly rescheduled, but when something in the archive changes and their state changes, they get scheduled… > I don't remember seeing this behaviour before. Have I just been unobservant, > or has something changed (or possible broken) with the testing? I've done nothing on this since May 5th and today there are 0 packages in the "cannot be tested" state for jessie-pu… -- cheers, Holger
Attachment:
signature.asc
Description: Digital signature