[Piuparts-devel] Packages from p-u in "cannot be tested"

Holger Levsen holger at layer-acht.org
Tue May 23 01:38:52 UTC 2017

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…

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170523/e754944e/attachment.sig>

More information about the Piuparts-devel mailing list