[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: krb5 in 'Uploaded' state for 7d+



Hi,

Cyril Brulebois wrote:
> Steven Chamberlain <steven@pyro.eu.org> (2016-03-02):
> > Please could you check why krb5 has stayed 'Uploaded' for 7d+
> > and now 'Installed' yet?
> > 
> > https://buildd.debian.org/status/package.php?p=krb5
> 
> It's in now.

Thank you.

> Looking at queued log for the rest, except dak for the last one:
> 
> > And there are some others too, but less important for now:
> >   * modglue [kfreebsd-i386]
> 
> /srv/upload.debian.org/queued/log.2015-09.xz:Sep 15 00:29:57 modglue_1.17-2.4_kfreebsd-i386.changes: does not start with a clearsigned message
> /srv/upload.debian.org/queued/log.2015-09.xz:Sep 15 00:29:57 /modglue_1.17-2.4_kfreebsd-i386.changes has bad PGP/GnuPG signature!
> 
> >   * sunclock [kfreebsd-i386]
> 
> /srv/upload.debian.org/queued/log.2015-11.xz:Nov 25 23:12:02 sunclock_3.57-6_kfreebsd-i386.changes: does not start with a clearsigned message
> /srv/upload.debian.org/queued/log.2015-11.xz:Nov 25 23:12:02 /sunclock_3.57-6_kfreebsd-i386.changes has bad PGP/GnuPG signature!

Maybe the buildd ran out of disk space, or had some network issue.
They are built and installed now, thank you.

> >   * mate-media [kfreebsd-amd64]

That one is built again although still in 'Uploaded' state.  Will keep
an eye on it.

> >   * libvncserver [kfreebsd-amd64]

Also fixed.

> >   * tripwire [kfreebsd-amd64,kfreebsd-i386]
> 20151201172428|process-upload|dak|Processing changes file|tripwire_2.4.2.2-5_kfreebsd-i386.changes
> 20151201172428|process-upload|dak|REJECT|tripwire_2.4.2.2-5_kfreebsd-i386.changes
> 20151209002403|process-upload|dak|Processing changes file|tripwire_2.4.2.2-5_kfreebsd-amd64.changes
> 20151209002403|process-upload|dak|REJECT|tripwire_2.4.2.2-5_kfreebsd-amd64.changes

I don't understand what that means, but the package is RC-buggy in any
case.

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org

Attachment: signature.asc
Description: Digital signature


Reply to: