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

Re: Bug#944116: tasksel: Please make another source-only upload



Hi,

Boyuan Yang <byang@debian.org> wrote:
> 在 2019-11-21四的 20:54 +0100,Holger Wansing写道:
> > Hi,
> > 
> > Ansgar <ansgar@43-1.org> wrote:
> > > We had an issue where old arch:all packages were detected as cruft
> > > when
> > > buildds had not built the new version yet (which should no longer
> > > happen
> > > thanks to Ivo De Decker's patch[1]), but here these are
> > > maintainer-provided packages :/
> > > 
> > > Maybe a race between dak accepting the package from NEW (so it's
> > > only
> > > half-installed) and a parallel process generating the cruft report
> > > based
> > > on that half-installed state? (If this is the case, then the patch
> > > from
> > > above should also help.)
> > > 
> > >   [1]: https://salsa.debian.org/ftp-team/dak/merge_requests/163
> > > 
> > > I don't have resources to look into this in more detail currently
> > > though. So I suggest to do an extra upload to NEW for now.
> > 
> > Does that mean I can do an extra upload for the 3.57 version (that
> > version
> > which was rejected yesterday) or do I need to create a new 3.58
> > version 
> > for that?
> > (This is the first time I have to do such thing, sorry.)
> 
> I guess we need a 3.57 upload, a non-source-only upload, which needs to
> go through NEW to add those missing packages back. After that, a
> source-only 3.58 upload is also needed. I can help sponsor packages if
> you find that necessary.

I have upload rights for d-i packages, so sponsoring not needed.
But I need help with such an non-source-only upload, as it seems :-|

My amd64 binary upload was just rejected, I suspect because it does go
through NEW:


=================================================================================
Date: Sun, 24 Nov 2019 10:53:57 +0000
From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
To: Holger Wansing <hwansing@mailbox.org>, Anton Zinoviev <zinoviev@debian.org>
Subject: tasksel_3.57_amd64.changes REJECTED




ACL dm: NEW uploads are not allowed

binary:task-chinese-s is NEW.
binary:task-cyrillic-kde-desktop is NEW.
binary:task-hebrew-desktop is NEW.
binary:task-macedonian is NEW.
binary:task-slovenian-kde-desktop is NEW.
binary:task-chinese-s is NEW.
binary:task-hebrew-desktop is NEW.
binary:task-slovenian-kde-desktop is NEW.
binary:task-cyrillic-kde-desktop is NEW.
binary:task-macedonian is NEW.

=================================================================================



But I cannot find any documentation about how to define, if such upload
should go through NEW (or maybe I have overlooked it?)

In the past, I have only done source-only uploads.



Holger



-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076


Reply to: