vlevel_0.5-1_amd64.changes REJECTED with python backtrace, then ACCEPTED, but still not in the package list

Ansgar Burchardt ansgar at debian.org
Fri Feb 20 07:15:45 UTC 2015


Hi,

Axel Beckert <abe at debian.org> writes:
> I've uploaded vlevel again signed with my new key and it got accepted
> on 13th of February 2015, i.e. like five days ago. This is more than
> enough time to propagate to the buildds, but the package hasn't been
> built yet on any buildd.
>
> Nevertheless the package never seems to have hit the archive and the
> common places where I can track a package's state look inconsistent:

Hmm, looks like it was accepted from NEW the second time without having
an override added which means it was missing from Packages/Sources
indices. I added the missing override.

I think this can happen since I fixed handling of components in NEW
processing for source-only uploads. We probably should not process
ACCEPTED.* files for the NEW queue and/or check for overrides to exist
when processing policy queues.

Ansgar



More information about the pkg-multimedia-maintainers mailing list