Re: dpkg_1.18.10~bpo8+1_amd64.changes is NEW
On Sun, Oct 16, 2016 at 8:44 PM, Guillem Joverwrote: > Hi! > > On Sun, 2016-10-16 at 06:18:40 +, Debian FTP Masters wrote: >> binary:dpkg is NEW. >> binary:dpkg-dev is NEW. >> binary:dselect is NEW. >> binary:libdpkg-dev is NEW. >> binary:libdpkg-perl is NEW. >> source:dpkg 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. > >> If you have any questions, you may reply to this email. > > Unfortunately I'd like to request for this uncoordinated upload to be > rejected. I think it might have been rejected anyway, as it has been > the case in the past for potential dpkg backports, but still. > > YunQiang, this seems to be due to the MIPS ports, and the newish > requirements from DAK to know all architectures present in packaging, > or they get rejected. :( In any case, sorry I've not handled that > before, the proper course of action here is to cherry-pick those > changes into a stable update, which I'll be doing now. Thank you very much for this help. > > Thanks, > Guillem
Re: dpkg_1.18.10~bpo8+1_amd64.changes is NEW
Hi! On Sun, 2016-10-16 at 06:18:40 +, Debian FTP Masters wrote: > binary:dpkg is NEW. > binary:dpkg-dev is NEW. > binary:dselect is NEW. > binary:libdpkg-dev is NEW. > binary:libdpkg-perl is NEW. > source:dpkg 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. > If you have any questions, you may reply to this email. Unfortunately I'd like to request for this uncoordinated upload to be rejected. I think it might have been rejected anyway, as it has been the case in the past for potential dpkg backports, but still. YunQiang, this seems to be due to the MIPS ports, and the newish requirements from DAK to know all architectures present in packaging, or they get rejected. :( In any case, sorry I've not handled that before, the proper course of action here is to cherry-pick those changes into a stable update, which I'll be doing now. Thanks, Guillem
dpkg_1.18.10~bpo8+1_amd64.changes is NEW
binary:dpkg is NEW. binary:dpkg-dev is NEW. binary:dselect is NEW. binary:libdpkg-dev is NEW. binary:libdpkg-perl is NEW. source:dpkg 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 receive 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