exim4_4.84~RC1-1_i386.changes is NEW

Andreas Metzler ametzler at bebt.de
Sat Aug 2 11:58:05 UTC 2014


On 2014-08-02 Ansgar Burchardt <ansgar at debian.org> wrote:
> Andreas Metzler <ametzler at bebt.de> writes:
> > On 2014-08-02 Debian FTP Masters <ftpmaster at ftp-master.debian.org> wrote:
> >> binary:exim4-daemon-custom is NEW.
> >> binary:exim4-daemon-custom-dbg is NEW.
> > [...]
> > Please reject this upload. The NEW detection is a false positive,
> > probably due to changes to the archive infrastructure related to
> > source-only uloads.
> >
> > I will need to find a proper way to work around this.

> Yes, it's related to the recent changes for source-only uploads: dak now
> looks at the list of packages built by the source to consider NEW
> binaries. exim4 lists exim4-daemon-custom{,dbg} as packages it builds.

> The fix is to not list exim4-daemon-custom{,dbg} in d/control in the
> package uploaded to Debian.

Thanks for the heads-up. That is exactly what I did in 4.84~RC1-3,
however it still ended in NEW since exim4_4.84~RC1.orig.tar.bz2 is in
NEW.

Could you please fix this situation, either by rejecting -1 -2 and -3
(allowing me to re-upload -3 unchanged) or by rejecting -1 and -2 and
accepting -3?

thanks, cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the Pkg-exim4-maintainers mailing list