[Debian-med-packaging] jaligner_1.0-1_amd64.changes is NEW

[Andreas Tille]

Hi ftpmasters,

this package went into new as a result of our Debian Med sprint in
Winter.  It is now hanging in new since way longer than any other
package we injected way later.  I wonder whether there is a reason that
this package takes that long.  We have several other packages in the
queue where jaligner is a Build-Dependency and thus the current
situation is blocking further work.

We would be happy to work on any issue of this package but we simply
have no idea why this package is dealt differently.

Thanks for enlightening us and also thanks for your work as ftpmaster

        Andreas.

On Mon, Feb 16, 2015 at 09:19:20AM +0000, Debian FTP Masters wrote:
> binary:jaligner is NEW.
> source:jaligner is NEW.
> 
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process. The upload was otherwise valid (it had a good
> OpenPGP signature and file hashes are valid), so please be patient.
> 
> Packages are routinely processed through to the archive, and do feel
> free to browse the NEW queue[1].
> 
> If there is an issue with the upload, you will recieve an email from a
> member of the ftpteam.
> 
> If you have any questions, you may reply to this email.
> 
> [1]: https://ftp-master.debian.org/new.html
> 
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de