Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED
On 2023-07-19 13:38, PICCA Frederic-Emmanuel wrote: > > I am just the messenger here, if you disagree, please feel free to > > contact ftpmasters or lintian maintainers. > > This was not a rant about this, I just wanted to understand what is going on > :). > > > Your package has been built successfully on (some) buildds, but then the > > binaries upload got rejected by dak, that's why they are still in > > "Uploaded" state. Overall it's just like if pyfai hasn't been built or > > fails to build from source. > > So until a new upstream source is available with other timestamp, it will not > be uploadable. The problem is not in the upstream source tarball (the source got accepted), but rather in the binary packages produced during the build. The debian/rules file can somehow change the timestamp after copying the file into the debian/tmp hierarchy. > In you opinion, can we discuss about this on debian-devel ? > Yes, I don't see why it couldn't be discussed there. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED
> I am just the messenger here, if you disagree, please feel free to > contact ftpmasters or lintian maintainers. This was not a rant about this, I just wanted to understand what is going on :). > Your package has been built successfully on (some) buildds, but then the > binaries upload got rejected by dak, that's why they are still in > "Uploaded" state. Overall it's just like if pyfai hasn't been built or > fails to build from source. So until a new upstream source is available with other timestamp, it will not be uploadable. In you opinion, can we discuss about this on debian-devel ? Cheers Fred
Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED
Hi, On 2023-07-19 11:24, PICCA Frederic-Emmanuel wrote: > ok, it seems that I generated an orig.tag.gz with this (Thu Jan 1 00:00:00 > 1970). > > I can not remember which tool I used to generate this file. > > gbp import-orig --uscan > > or > > deb-new-upstream I am just the messenger here, if you disagree, please feel free to contact ftpmasters or lintian maintainers. > Nevertheless, why is it a serious bug ? Your package has been built successfully on (some) buildds, but then the binaries upload got rejected by dak, that's why they are still in "Uploaded" state. Overall it's just like if pyfai hasn't been built or fails to build from source. Regards Aurelien [1] https://buildd.debian.org/status/package.php?p=pyfai -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1041443: [Debian-pan-maintainers] Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED
ok, it seems that I generated an orig.tag.gz with this (Thu Jan 1 00:00:00 1970). I can not remember which tool I used to generate this file. gbp import-orig --uscan or deb-new-upstream Nevertheless, why is it a serious bug ? thanks Frederic
