Bug#783787: devscripts: upgrade fails; ImportError: No module named '_sysconfigdata_m'

2015-04-30 Thread Daniel Andersson
Package: python3.4 Version: 3.4.3-4 Followup-For: Bug #783787 This seems to break Python 3 and with it all Python 3-dependent scripts on affected machines due to `_sysconfigdata_m.py` not existing in the import path when called from `/usr/lib/python3.4/_sysconfigdata.py`. The module exists in the

Bug#783787: devscripts: upgrade fails; ImportError: No module named '_sysconfigdata_m'

2015-04-30 Thread IOhannes m zmoelnig
Package: python3.4 Version: 3.4.3-4 Severity: critical Followup-For: Bug #783787 Reproduced on amd64. This makes *any* software that uses python3 unusable, so I'm escalating the severity. It also breaks the installation of packages (as this may use python3). The issue seems to be that python3

Bug#783787: devscripts: upgrade fails; ImportError: No module named '_sysconfigdata_m'

2015-04-29 Thread Adam D. Barratt
Control: reassign -1 python3.4 3.4.3-4 On Thu, 2015-04-30 at 14:59 +1000, Brian May wrote: This is under i386 only, amd64 seems to be fine. Preparing to unpack .../devscripts_2.15.4_i386.deb ... Failed to import the site module Traceback (most recent call last): File

Bug#783787: devscripts: upgrade fails; ImportError: No module named '_sysconfigdata_m'

2015-04-29 Thread Brian May
Package: devscripts Version: 2.15.3 Severity: important This is under i386 only, amd64 seems to be fine. Preparing to unpack .../devscripts_2.15.4_i386.deb ... Failed to import the site module Traceback (most recent call last): File /usr/lib/python3.4/site.py, line 586, in module main()

Bug#783787: devscripts: upgrade fails; ImportError: No module named '_sysconfigdata_m'

2015-04-29 Thread Brian May
notfound 783787 2.15.3 found 783787 2.15.4 thanks Supplied the wrong version by mistake :-( This happens with the version in sid.