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

Re: Accepted ncc 2.8-2.1 (source amd64) into unstable

On Sat, Jan 07, 2017 at 09:44:08PM +0000, Holger Levsen wrote:
> (truncated) from debian-deve-changes@l.d.o:
> On Sat, Jan 07, 2017 at 09:33:44PM +0000, John Paul Adrian Glaubitz wrote:
> > Source: ncc
> > Version: 2.8-2.1
> > Changes:
> >  ncc (2.8-2.1) UNRELEASED; urgency=medium
> UNRELEASED? how did that even work?

It happens every so often.

The archive software looks at the Distribution field of the .changes,
and doesn't care at all about what's in Changes (i.e. what's in
Usually this is caused by using the -d option of sbuild.

dput maintainers: this is one check that is present in dput-ng and I
find a must-have.

cbmuser: install dput-ng? :P

                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply to: