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

Re: mentors.debian.net: upload stuck



On Sun, Nov 13, 2022 at 07:11:54PM +0100, Alec Leamas wrote:
> I did something I should not have done: I uploaded a package without sources
> to mentors. Now, I cannot upload the correct package with sources, it seems
> that the bad one is in the way.

Is it, now?

When I logged in 3 minutes ago, I could see only this in the upload
queue:

-rw------- 1 expo ftp  4356 Nov 13 18:05 ddupdate_0.6.6-2.debian.tar.xz
-rw------- 1 expo ftp  1882 Nov 13 18:05 ddupdate_0.6.6-2.dsc
-rw------- 1 expo ftp  7058 Nov 13 18:05 ddupdate_0.6.6-2_source.buildinfo
-rw------- 1 expo ftp  2158 Nov 13 18:05 ddupdate_0.6.6-2_source.changes
-rw------- 1 expo ftp 37716 Nov 13 18:06 ddupdate_0.6.6.orig.tar.gz


And at 18:18:22 the importer task started and ate them successfully :>

Nov 13 18:18:30 wv-debian-mentors1 celery[1129]: [2022-11-13 18:18:30,512: INFO/ForkPoolWorker-2] Package ddupdate_0.6.6-2 accepted into unstable


> The package is ddupdate-0.6.6-2. Is there anyone listening who can clear
> things on the mentors incoming queue? Or, will it happen automatically over
> time?

I'm not sure what you were seeing earlier (and I haven't dug the logs
for it), but I reckon everything's fine.

Also, the people who can mess with mentors.d.n can be reached privately
at support@mentors.debian.net - we are all also on debian-mentors@l.d.o,
but we might be a tad more responsive there (can't speak for the others,
but mails to support@mentors.d.n are high-priority notified to me, mails
to d-mentors@l.d.o are very much hidden in the background).

-- 
regards,
                        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: