Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2011-01-04 Thread Sandro Tosi
On Tue, Jan 4, 2011 at 03:06, Jonathan Nieder jrnie...@gmail.com wrote: ii  python-central                                   0.6.16+nmu1 There goes that theory.  Alternatively this could be a bug in packages that moved from dh_pycentral to dh_python2 as Sandro suggested.  If so, does anyone

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2011-01-04 Thread dave b
That specific grep has no results -- (for the 2nd). However, for the 3rd the results are listed below: /var/log/dpkg.log.1:2010-12-03 23:55:11 status triggers-pending python-central 0.6.16+nmu1 /var/log/dpkg.log.1:2010-12-03 23:55:11 trigproc python-central 0.6.16+nmu1 0.6.16+nmu1

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2011-01-03 Thread Jonathan Nieder
severity 607988 grave retitle 607988 python: OSError: [Errno 2] byte-compiling packages on upgrade (dangling symlinks) quit dave b wrote: Setting up python (2.6.6-3+squeeze4) ... Linking and byte-compiling packages for runtime python2.6... Traceback (most recent call last): File

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2011-01-03 Thread dave b
well it was 1. reportlab and 2. bzr (gtk). I am not sure on the exact packages - isn't there an easier way to simply check for every python package (available). ii python-central 0.6.16+nmu1 register and build utility for Python packages

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2011-01-03 Thread Jonathan Nieder
dave b wrote: well it was 1. reportlab and 2. bzr (gtk). Just to confirm, old python-central was not installed when you sent the report, right? What does zgrep 2010-12-2.*python-central /var/log/dpkg.log* say? ii python-central 0.6.16+nmu1 There

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2010-12-27 Thread Philipp Dreimann
@Dave: is /usr/lib/python2.6/dist-packages/bzrlib/plugins/gtk/merge.py on your system also a dangling symlink? /usr/lib/python2.6/dist-packages/reportlab contains all the dangling symlinks on my system- I may removed the package a while ago. You can scan for them using the symlinks program in the

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2010-12-26 Thread Philipp Dreimann
same problem here(?): Linking and byte-compiling packages for runtime python2.6... Traceback (most recent call last): File /usr/bin/pycompile, line 314, in module main() File /usr/bin/pycompile, line 300, in main options.force, options.optimize, e_patterns) File /usr/bin/pycompile,

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2010-12-25 Thread david b
Package: python2.6 Version: 2.6.6-6 Severity: critical The latest update is totally broken and can't byte compile *modules* (squeeze). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel:

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2010-12-25 Thread Julien Cristau
On Sun, Dec 26, 2010 at 05:19:39 +1100, david b wrote: Package: python2.6 Version: 2.6.6-6 Severity: critical The latest update is totally broken and can't byte compile *modules* (squeeze). It works for everyone else. Please provide some details... Cheers, Julien signature.asc

Bug#607988: python2.6: the latest update is totally broken and can't byte compile *modules*

2010-12-25 Thread dave b
Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. 8 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up python (2.6.6-3+squeeze4) ... Linking and byte-compiling packages for runtime