Bug#852289: [Python-modules-team] Bug#852289: python-passlib: please make the build reproducible (timestamps)
On Jan 31, 2017, at 09:43 AM, Eli Collins wrote: >Passlib 1.7.1 is out, which should fix #852289; I'll try to keep an eye on >the reproducible build status for a bit in case there's any other hiccups. Thanks! I'm working on the new upstream in git right now. It looks like we can also drop the 0001-Disable-Django-support.patch since https://bitbucket.org/ecollins/passlib/issues/68/tests-fail-with-django-19 is resolved upstream. I'm not a Django expert though so please let me know if this is not correct. Cheers, -Barry pgpaSH_AHEkxO.pgp Description: OpenPGP digital signature
Bug#852289: [Python-modules-team] Bug#852289: python-passlib: please make the build reproducible (timestamps)
Passlib 1.7.1 is out, which should fix #852289; I'll try to keep an eye on the reproducible build status for a bit in case there's any other hiccups. - Eli On Mon, Jan 23, 2017 at 5:12 PM, Barry Warsaw wrote: > On Jan 23, 2017, at 04:40 PM, Eli Collins wrote: > > >In case this helps the debian package maintainer decide on this patch / > >schedule things, the timestamp problem this addresses is due to a bug in > >the passlib 1.7.0 setup script, which should be fixed in the 1.7.1 > upstream > >release (due out next weekend). > > Thanks for the status Eli. If the bug is fixed upstream, I think it makes > sense to just wait until 1.7.1. Feel free to drop us a ping when that's > available (though I'll eventually notice it anyway). If Brian doesn't > beat me > to it, I'm happy to update to 1.7.1 once it's available. >
Bug#852289: [Python-modules-team] Bug#852289: python-passlib: please make the build reproducible (timestamps)
On Jan 23, 2017, at 04:40 PM, Eli Collins wrote: >In case this helps the debian package maintainer decide on this patch / >schedule things, the timestamp problem this addresses is due to a bug in >the passlib 1.7.0 setup script, which should be fixed in the 1.7.1 upstream >release (due out next weekend). Thanks for the status Eli. If the bug is fixed upstream, I think it makes sense to just wait until 1.7.1. Feel free to drop us a ping when that's available (though I'll eventually notice it anyway). If Brian doesn't beat me to it, I'm happy to update to 1.7.1 once it's available.
