+++ Jakub Wilk [2014-04-04 01:21 +0200]: > * Emilio Pozuelo Monfort <po...@debian.org>, 2014-04-04, 00:49: > >>Setting up python3-gi (3.10.2-2) ... > >>Traceback (most recent call last): > >> File "/usr/bin/py3compile", line 290, in <module> > >> main() > >> File "/usr/bin/py3compile", line 270, in main > >> options.force, options.optimize, e_patterns) > >> File "/usr/bin/py3compile", line 172, in compile > >> interpreter.magic_number(version), mtime) > >>struct.error: 'l' format requires -2147483648 <= number <= 2147483647 > > Probably something to do with bogus timestamps in the deb: > > drwxr-xr-x root/root 0 2063-05-01 14:32 ./
Well spotted. Some repacking has just proved that that is indeed the problem. I did have a load of stuff built in '2021' earlier in this project (due to the hwclocks not being settable on the early arm64 hardware/kernels). I hadn't realised I have some thing from '2063' too. What's somewhat odd is that this packaged worked fine for quite some time (on 1st machine), and this issue only came up on a new machine. Possibly because it's due to time-difference, not absolute time. Anyway, glad to have that mystery cleared up. And it unbungs a pile of builds. thanks. > Of course, it would be better if dh_python3 was Y2038-compliant. :) yes. Is there any point filing a wishlist for that, to remind someone to do something about it before it's a real issue? Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140404000204.gw10...@stoneboat.aleph1.co.uk
