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

Bug#759030: marked as done (DDPO: showing a sponsored package as NEW and unstable/testing)

Your message dated Mon, 25 Aug 2014 23:26:13 +0200
with message-id <20140825212613.GC19017@msg.df7cb.de>
and subject line Re: Bug#758289: package in NEW not listed as pending upload
has caused the Debian Bug report #758289,
regarding DDPO: showing a sponsored package as NEW and unstable/testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
758289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758289
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal

Dear Maintainer,

My QA page is showing the package 'buildnotify' as NEW and testing at the
same time. I uploaded this package to NEW (as sponsor) on 2014-08-03 and
it was accepted in unstable on 2014-08-04.

Thanks in advance.

Regards,

Eriberto

--- End Message ---
--- Begin Message --- 
Re: David Prévot 2014-08-22 <[🔎] 53F74278.4090007@debian.org>
> > On 22 August 2014 12:29, Jonas Smedegaard <dr@jones.dk> wrote:
> 
> >> The package libmoox-cmd-perl is in the NEW queue:
> >> https://ftp-master.debian.org/new/libmoox-cmd-perl_0.009-1.html
> >>
> >> ...but still - after several days - lists as "Owned WNPP bugs", not
> >> "Pending uploads" at my DDPO page:
> >> https://qa.debian.org/developer.php?login=dr@jones.dk&comaint=yes
> 
> There is already a bug report about it, replying to it right now.
> 
> As an additional data point, it seems to have stopped working early this
> month, probably Mon, 04 Aug 2014, since php-symfony-icu is marked as NEW
> for 20 hours [0] while it was uploaded on Sun, 03 Aug 2014.

I'm not sure what the problem was, but it seems there was an
incoming-new.db file which was probably broken and let the cronjob
fail and hence hindered the incoming.db update. The bad file is gone
now.

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: