On Fri, 2020-02-07 at 18:50 +0100, Cyril Brulebois wrote: > Hi, > > Andreas Beckmann <[email protected]> (2020-02-06): > > please do the right thing to help node-yarnpkg out of the Uploaded > > state > > in sid where it is for 50+ days already. > > > > Should there be some process that automatically reports stale > > Uploaded > > packages after x days? > > It seems to have reached dak just fine, but: > > kibi@coccia:~$ xzgrep node-yarnpkg /srv/ftp- > master.debian.org/log/2019-12.xz > 20191217121905|process-upload|dak|Processing changes file|node- > yarnpkg_1.21.1-1_source.changes > 20191217121933|process-upload|dak|REJECT|node-yarnpkg_1.21.1- > 1_source.changes > 20191217144608|process-upload|dak|Processing changes file|node- > yarnpkg_1.21.1-1_source.changes > 20191217144659|process-upload|dak|ACCEPT|node-yarnpkg_1.21.1- > 1_source.changes > 20191217144704|process-upload|dak|Archiving|node-yarnpkg_1.21.1- > 1_source.buildinfo > 20191217151914|process-upload|dak|Processing changes file|node- > yarnpkg_1.21.1-1_all.changes > 20191217151914|process-upload|dak|REJECT|node-yarnpkg_1.21.1- > 1_all.changes > 20191219145045|manage-build-queues|dak|removed source from build > queue|buildd-unstable|node-yarnpkg|1.21.1-1
The initial source REJECT was due to the upload apparently trying to add new packages while being uploaded by a DM. The subsequent arch:all reject was: yarnpkg_1.21.1-1_all.deb: has 2 file(s) with a timestamp too far in the past: usr/share/nodejs/yarn/node_modules/npm-logical-tree/index.js (Thu Jan 1 00:00:00 1970) usr/share/nodejs/yarn/node_modules/npm-logical- tree/package.json (Thu Jan 1 00:00:00 1970) So this might need fixing on the package side. Regards, Adam
