Bug#543351: [Python-modules-team] Bug#543351: logilab.astng cannot be imported after upgrade from stable
On Thursday 03 September 2009 12:25:00 Sandro Tosi wrote: Hi Chris, thanks for your report. On Mon, Aug 24, 2009 at 14:43, Chris Lambla...@debian.org wrote: Package: python-logilab-astng Severity: serious Version: 0.19.0-2 ... I can make it work by manually removing /usr/lib/python2.5/site-packages/logilab Since all the packages sharing logilab namespace have a new upstream version to package, it's a good time to try to fix this on all of them. The preinst file of logilab-astng is [1]: we already try to fix the migration (central-support) problem but we don't remove to common logilab/ directory. [1] http://svn.debian.org/viewsvn/python-modules/packages/logilab-astng/trunk/d ebian/python-logilab-astng.preinst?view=markup I'd like to know what would be the best solution for this (hence -python in the loop): - logilab-common is the lower level of logilab* packages, so we can add conflict there with all the other logilab-* packages and then remove logilab/ completely from its preinst - add extra logic to all logilab* packages to check if /usr/lib/python*/site-packages/logilab is empty and then remove it (could there be cases where it left hanging dirs?) I'm considering teh second solution a bit better, but I'd like to hear from your what youi think. The problem I can see with removing blindly from the postinst is that potentially you're going to delete files belonging to other packages (e.g. older packages installed from Logilab's Debian repositories). Could the following work: logilab-common postinst removes /usr/lib/python*/site- packages/logilab/__init__.py*, and issues a warning if there are other stuff in the directory : this will stop packages installed under that tree from working without deleting the files themselves (enabling the administrator to find out what's broken with that installation). -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524303: [Python-modules-team] Bug#524303: python-elementtree: Fails to configure properly in Testing
Le Friday 17 April 2009 15:33:00 Dale Schroeder, vous avez écrit : I am still receiving the error. Has the fix been pushed to the testing repository? Short answer is 'No'. Longer answer is check http://packages.qa.debian.org/e/elementtree.html. -- Alexandre Fayolle -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523445: python-qscintilla2: cannot import module with python-qt4 4.4.6 installed
Package: python-qscintilla2 Version: 2.2-4 Severity: grave Justification: renders package unusable python-qt4's packaging has changed and now uses python-support. As a result, packages shipping submodules of PyQt4 must be updated to use python-support too, or they cannot be imported: Traceback (most recent call last): File /home/syt/bin/hgqv, line 24, in module from hgview.qt4 import hgview_qt4 as hgview File /home/syt/src/hgview/qt4/hgview_qt4.py, line 16, in module from PyQt4 import QtCore, QtGui, Qsci ImportError: cannot import name Qsci -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (800, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-qscintilla2 depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libgcc1 1:4.3.3-3 GCC support library ii libqscintilla2-3 2.2-4 The Qt4 port of the Scintilla sour ii libqtcore44.4.3-2Qt 4 core module ii libqtgui4 4.4.3-2Qt 4 GUI module ii libstdc++64.3.3-3The GNU Standard C++ Library v3 ii python2.5.2-3An interactive high-level object-o ii python-qt44.4.2-4Python bindings for Qt4 python-qscintilla2 recommends no packages. python-qscintilla2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523107: python-constraint: package should be names python-logilab-constraint
Package: python-constraint Version: 0.4.0-2 Severity: serious Justification: debian python policy the package installs logilab.constraint and therefore should be called python-logilab-constraint. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (70, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-constraint depends on: ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt ii python-logilab-common 0.39.0-1 useful miscellaneous modules used python-constraint recommends no packages. Versions of packages python-constraint suggests: ii python-psyco 1.6-1 Python specializing compiler -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513853: stack at segfault
For what it's worth, here's what I get when running with -gdb: (gdb) bt #0 0xb7e5d3b3 in strlen () from /lib/i686/cmov/libc.so.6 #1 0x08096eda in PyString_FromString () #2 0xb406c975 in initmulti_polynomial_libsingular () from /usr/lib/python2.5/site-packages/sage/rings/polynomial/multi_polynomial_libsingular.so #3 0x080e6b67 in _PyImport_LoadDynamicModule () #4 0x080e4ac0 in ?? () #5 0xbfcb7b87 in ?? () #6 0xbfcb6b13 in ?? () #7 0x0a948230 in ?? () #8 0x0808bcf9 in PyObject_GetAttrString () #9 0x080e52a7 in ?? () #10 0x0003 in ?? () #11 0x in ?? () -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#476161: xmldiff - FTBFS: SyntaxError: from __future__ imports must occur at the beginning of the file
tag 476161 +pending On Mon, Apr 14, 2008 at 09:05:02PM +0200, Bastian Blank wrote: Package: xmldiff Version: 0.6.8-3+b1 Severity: serious There was an error while trying to autobuild your package: Automatic build of xmldiff_0.6.8-3+b1 on lxdebian.bfinv.de by sbuild/s390 98 [...] debian/rules build dh_testdir python setup.py -q build File setup.py, line 23 from __future__ import nested_scopes SyntaxError: from __future__ imports must occur at the beginning of the file make: *** [build-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 ** Build finished at 20080414-0223 FAILED [dpkg-buildpackage died] Thanks for the report and patch, I'll upload a fixed version today. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#462008: FTBFS on 64bit archs
tag 462008 =fixed-upstream thanks After discussing the issue with upstream, it seems that it has recently been fixed in subversion. I don't have the time to update the package to use a more recent subversion branch right now, but I'll do so next week. Thanks for your patience. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#462008: pypy: FTBFS on 64 bit arches: expects INT got Signed
tag 462008 +upstream
forwarded 462008 https://codespeak.net/issue/pypy-dev/issue353
thanks
On Mon, Jan 21, 2008 at 11:03:27PM +0100, Kurt Roeckx wrote:
Package: pypy
Version: 1.0.0-svn50146-2
Severity: serious
Hi,
Your package is failing to build on the 64 bit arches with this error:
[translation:ERROR] Error:
[translation:ERROR] Traceback (most recent call last):
[translation:ERROR]File pypy/translator/goal/translate.py, line 273, in
main
[translation:ERROR] drv.proceed(goals)
[...]
[translation:ERROR] TypeError': Struct tm { c_tm_sec, c_tm_min, c_tm_hour,
c_tm_mday, c_tm_mon, c_tm_year, c_tm_wday, c_tm_yday, c_tm_isdst, c__pad0,
c__pad1, c__pad2, c__pad3, c_tm_gmtoff, c_tm_zone } instance field
'c_tm_mon':[translation:ERROR] expects INT
[translation:ERROR] got Signed
[translation:ERROR] .. v3635 = setattr((* struct tm { c_tm_se...=...
}), ('c_tm_mon'), v3634)
[translation:ERROR] .. '(pypy.module.rctime.interp_time:189)_gettmarg'
All members of the C struct tm type should be int's, and I'm not sure
what the difference between an INT and Signed is.
Hi,
Last time I checked, 64bit archs were not well supported by upstream. I've
reported the issue to the pypy core team. Patches solving this issue are
welcome.
--
Alexandre Fayolle LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/services
Informatique scientifique: http://www.logilab.fr/science
signature.asc
Description: Digital signature
Bug#460696: pypy - FTBFS: error: zlib.h: No such file or directory
On Mon, Jan 14, 2008 at 05:07:23PM +0100, Bastian Blank wrote: Package: pypy Version: 1.0.0-svn50146-1 Severity: serious There was an error while trying to autobuild your package: Looks like I'm in for a brown paper bag -2 release... That's what you get when you bypass pbuilder... I'm off triplechecking my build dependencies. Cheers -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#426012: downgrading severity to normal
unblock 426012 by 435591 severity 435591 normal thanks Setting back the severity to normal as #426012 has been fixed by a recent upload of python-scipy. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#431197: pypy - FTBFS: OSError: [Errno 12] Cannot allocate memory
Hi, Pypy requires a significant amount of memory to build (1GB). Furthermore, s390 is not supported by upstream. I'm closing this bug. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#431197: pypy - FTBFS: OSError: [Errno 12] Cannot allocate memory
On Mon, Jul 02, 2007 at 12:58:34PM +0200, Bastian Blank wrote: reopen 431197 thanks On Mon, Jul 02, 2007 at 12:44:12PM +0200, Alexandre Fayolle wrote: Pypy requires a significant amount of memory to build (1GB). It fails on many buildds, this is a bug. Furthermore, s390 is not supported by upstream. So the architecture settings are wrong, fix them. I thought I had done that in debian/control, but it looks like dpkg-source -b lost the information when generating the .dsc file. Is it ok to manually change that file and upload again, or am I missing something obvious ? -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#423725: pypy FTBFS: libgc problem ?
Hi, I think the GC_local_malloc symbol which the linker complains about is defined in libgc, which is specified on the command line. Do you know which version of libgc is installed on the autobuilder? -- Alexandre Fayolle
Bug#396840: using pyversions in debian/rules is not reliable
On Fri, Nov 10, 2006 at 10:58:02AM +0100, Loïc Minier wrote: Hi, On Thu, Nov 09, 2006, Alexandre Fayolle wrote: I'm trying to build and upload a new release of python-psyco, and the built package is wrong because `pyversions -r debian/control` returns python2.4 even though debian/control says that XS-Python-Version is =2.2, 2.6. I have python-all installed, so I would expect the call to pyversions to return python2.3 python2.4 python2.5 I think what you describe is correct behavior. pyversions was changed so that we can get rid of python2.3, and this means we should not build any new packages against python2.3, and rebuilds will hence lose their python2.3- virtual provide. Concerning python2.5, it's not enabled yet because it's not expected to be the default version in etch, but I suppose it could be now that it is officially released and in sync in etch. In my opinion, shipping etch with python2.5 (even as non default) and no extension module compiled for python2.5 is a bit strange. Any package building C extension modules rebuilt with the current setup will only compile the C extension for python2.4, which is not what we want. I think it is. :) I'd like real python2.5 support in etch... /me goes to reupload python-psyco without python2.3 support. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#396840: using pyversions in debian/rules is not reliable
On Fri, Nov 10, 2006 at 06:04:40PM +0100, Matthias Klose wrote: Alexandre Fayolle writes: In my opinion, shipping etch with python2.5 (even as non default) and no extension module compiled for python2.5 is a bit strange. you can explicitely add support for 2.5 in the package, i.e. PYVERSIONS = $(sort $(shell pyversions -vr) 2.5) Thanks for the tip. The reason I didn't add this by default would be random breakage for all extensions which don't build/work for 2.5, which doesn't seem appropriate at this point of the release schedule. If we want to I get it. I am afraid we will get complaints about that post-etch release, though... /me goes to reupload python-psyco without python2.3 support. shouldn't be necessary, binNMU should do it. No, I had completely shunted pyversions in debian/rules :-/ -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#396840: using pyversions in debian/rules is not reliable
I think this is the same problem as mentioned in the bug. I'm trying to build and upload a new release of python-psyco, and the built package is wrong because `pyversions -r debian/control` returns python2.4 even though debian/control says that XS-Python-Version is =2.2, 2.6. I have python-all installed, so I would expect the call to pyversions to return python2.3 python2.4 python2.5 Any package building C extension modules rebuilt with the current setup will only compile the C extension for python2.4, which is not what we want. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#393431: bittorrent-gui: incorrect dependency: does not work with python-wxgtk2.6
Package: bittorrent-gui Version: 3.4.2-8.1 Severity: serious Justification: Policy 7.2 Hi, bittorrent-gui depends on python-wxgtk2.4 | python-wxgtk2.6 but will not work if python-wxgtk2.6 is installed and python-wxgtk2.4 is not. $ LANG=C btdownloadgui.bittorrent foobar.torrent Could not load wxPython. In order to use this script, you must have wxPython installed. It is available in the package libwxgtk2.4-python. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages bittorrent-gui depends on: ii bittorrent 3.4.2-8.1 Scatter-gather network file transf ii python-wxgtk2.6 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI t ii python2.32.3.5-15An interactive high-level object-o bittorrent-gui recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392831: exim4-config: colons or semi colons as separators (debconf templates issue)
Package: exim4-config Version: 4.63-5 Severity: grave Justification: renders package unusable Hi, I'm having to reinstall my mail server (HD died on the previous one), and the debconf questions in exim4-config caused me to fill in wrong values, which broke the mail server. I'm using an RC severity because this will certainly bite users installing a fresh mail server with Debian/etch. The problematic templates are the one which ask for a list of values: * IP adresses to listen on for incoming SMTP connections says in the help: Please enter a semicolon-separated list of IP addresses. This is correct. * Other destinations for which mail is accepted says in the help: Please enter a semicolon-separated list of recipient domains This does not work: the destinations should be a colon-separated list of recipient domains. The symptom is undeliverable mails with lines like 2006-10-13 21:03:41 1GYSJp-0003Su-JV unknown lookup type fayauffre.org in paniclog. An easy patch is to change the wording of the debconf template and the translations. But it is probably better to have both lists use the same separator. If exim4 expects colons, the config script could sed s/;/:/ that line before writing it in the update-exim4.conf.conf file. The attached update-exim4.conf.conf was generated using a semicolon separated list at the debconf prompt. Thanks for your time and work. -- Package-specific info: Exim version 4.63 #1 built 10-Oct-2006 16:53:10 Copyright (c) University of Cambridge 2006 Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' dc_eximconfig_configtype='smarthost' dc_other_hostnames=''fayauffre.org;merlin;merlin.fayauffre.org' dc_local_interfaces='127.0.0.1;192.168.74.101' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='192.168.74.0/24' dc_smarthost='smtp.free.fr' CFILEMODE='644' dc_use_split_config='true' dc_hide_mailname='false' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:fayauffre.org -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages exim4-config depends on: ii adduser 3.95 Add and remove users and groups ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy exim4-config recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385946: fmit: crashes at startup
On Mon, Sep 04, 2006 at 11:19:44AM +0200, Ludovic RESLINGER wrote: Hello, Thank you for the bug report. The problem seem to be known by upstream, I will contact him today or tomorrow to have more informations, and to solve it. Great. fmit looks like a nice tool, and I was feeling a bit frustrated. If you need sponsoring for your upload, you can ask me. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#385946: fmit: crashes at startup
Package: fmit Version: 0.96.5-1 Severity: grave Justification: renders package unusable Hi, fmit segfaults at startup, before any application window is displayed on screen: $ fmit Free Music Instrument Tuner version 0.96.5 built at Sep 2 2006 15:25:55 Install directory '/usr' CaptureThread: INFO: Built in transports CaptureThread: INFO:JACK unavailable CaptureThread: INFO:ALSA available CaptureThread: INFO: Auto detecting a working transport ... using ALSA CaptureThread: INFO: ALSA: try to set format to Signed 16 bit Little Endian success CaptureThread: WARNING: ALSA: cannot set channel count to one. channels will be mixed CaptureThread: INFO: ALSA: try to set sampling rate to 96000 failed CaptureThread: INFO: ALSA: try to set sampling rate to 48000 success CaptureThread: WARNING: ALSA: cannot set channel count to one. channels will be mixed Segmentation fault Running with gdb shows that the stacktrace at crash time is the following: #0 0xe410 in __kernel_vsyscall () #1 0xa71e6821 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xa71e7fb9 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xa721bc4a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6 #4 0xa72234df in mallopt () from /lib/tls/i686/cmov/libc.so.6 #5 0xa7223582 in free () from /lib/tls/i686/cmov/libc.so.6 #6 0xa7d7b9cd in XFree () from /usr/lib/libX11.so.6 #7 0xa7e806e0 in __glXSendLargeImage () from /usr/lib/libGL.so.1 #8 0xa7e5ad0a in glGetString () from /usr/lib/libGL.so.1 #9 0xa7e66aa1 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1 #10 0xa7e66b43 in glXMakeCurrent () from /usr/lib/libGL.so.1 #11 0xa798e0c5 in QGLContext::makeCurrent () from /usr/lib/libqt-mt.so.3 #12 0xa798a3be in QGLWidget::makeCurrent () from /usr/lib/libqt-mt.so.3 #13 0xa798f0a3 in QGLWidget::resizeEvent () from /usr/lib/libqt-mt.so.3 #14 0xa7736976 in QWidget::event () from /usr/lib/libqt-mt.so.3 #15 0xa7697aea in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #16 0xa769a49a in QApplication::notify () from /usr/lib/libqt-mt.so.3 #17 0xa762b3d1 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #18 0xa7698b12 in QApplication::sendPostedEvents () from /usr/lib/libqt-mt.so.3 #19 0xa7738cef in QWidget::show () from /usr/lib/libqt-mt.so.3 #20 0xa7735b5c in QWidget::showChildren () from /usr/lib/libqt-mt.so.3 #21 0xa7738f76 in QWidget::show () from /usr/lib/libqt-mt.so.3 #22 0xa7735b5c in QWidget::showChildren () from /usr/lib/libqt-mt.so.3 #23 0xa7738f76 in QWidget::show () from /usr/lib/libqt-mt.so.3 #24 0xa780b660 in QMainWindow::show () from /usr/lib/libqt-mt.so.3 #25 0x08065148 in QLabel::metaObject () #26 0xa71d2ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #27 0x08055531 in ?? () -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages fmit depends on: ii freeglut32.4.0-5 OpenGL Utility Toolkit ii libasound2 1.0.11-7ALSA library ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libgl1-mesa-glx [libgl1] 6.4.2-1.1 A free implementation of the OpenG ii libglu1-mesa [libglu1] 6.4.2-1.1 The OpenGL utility library (GLU) ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library ii libjack0.100.0-0 0.101.1-1 JACK Audio Connection Kit (librari ii libqt3-mt3:3.3.6-4 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-2 X11 Session Management library ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 ii libx11-6 2:1.0.0-8 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxi6 1:1.0.1-3 X11 Input extension library ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library fmit recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383500: xmldiff: fails to install due to Python transition
tag 383500 +pending On Thu, Aug 17, 2006 at 07:05:57PM +0200, Bastian Kleineidam wrote: Package: xmldiff Version: 0.6.8-2 Severity: serious Justification: uninstallable, Python transition policy Hi, since the default python updated to 2.4, xmldiff is not installable anymore since it depends on python ( 2.4). Please upgrade the package according to the Python transition howto [1] to make it installable again. [1] http://wiki.debian.org/DebianPython/NewPolicy Hi, xmldiff has been updated to the new python policy on june 15th (unless I'm mistaken). However it supports only the current python version, and therefore requires a binary NMU which should happen in the coming days [1] I will close this bug when the package is rebuilt. Cheers, [1] http://lists.debian.org/debian-python/2006/08/msg00092.html -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#375836: python2.4-gnome2-extras: versioned dependency on virtual package python2.4-gtk2
Package: python2.4-gnome2-extras Severity: serious Tags: patch Justification: makes package uninstalable on sid Hi, The python-gtk2 package has been updated to the new Python policy, and therefore the python2.4-gtk2 package is now a virtual package, on which no versionned dependencies should exist. Your package should be updated to depend on python2.4, python-gtk2 (=2.4), python2.4-gtk2 to be installable. Thanks -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#375836: python2.4-gnome2-extras: versioned dependency on virtual package python2.4-gtk2
On Wed, Jun 28, 2006 at 04:03:59PM +0200, Marco Cabizza wrote: Il giorno mer, 28/06/2006 alle 14.04 +0200, Alexandre Fayolle ha scritto: Package: python2.4-gnome2-extras Severity: serious Tags: patch Justification: makes package uninstalable on sid Hi, The python-gtk2 package has been updated to the new Python policy, and therefore the python2.4-gtk2 package is now a virtual package, on which no versionned dependencies should exist. Your package should be updated to depend on python2.4, python-gtk2 (=2.4), python2.4-gtk2 to be installable. Thanks The fix is currently in SVN, the package is to be uploaded soon. Great, thanks. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#375260: python-unit: FTBFS: Missing Build-Depends
tag 375260 +pending thanks On Sat, Jun 24, 2006 at 04:32:36PM -0400, Daniel Schepler wrote: Package: python-unit Version: 1.4.1-14 Severity: serious Tags: patch From my pbuilder build log: ... dh_testdir dh_testroot dh_pysupport make: dh_pysupport: Command not found make: *** [binary-indep] Error 127 Adding python-support to the Build-Depends allows the package to build successfully. Thanks. I'll upload an updated version today. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#375606: undo/redo can cause denemo to crash, loosing data
Package: denemo Version: 0.7.5-1 Severity: grave Justification: causes non-serious data loss Hi, I tried to use denemo tonight to transcribe some music I had composed. Unfortunately, the undo/redo feature seems very unstable, and caused the application to crash (with core dump) after 15 minutes working on my transcription :-( I investigated a bit, and found a very easy way to produce such a core dump : 1. launch denemo 2. hit space bar 4 times to produce 4 C quarter notes 3. hit Ctrl-Z twice, to erase the last two notes 4. hit Ctrl-Y once, which I expect should put the last C quarter note back on screen but does not (I suppose thinks get bad in memory at this point) 5. hit space once - on my machine, I get a floating point exception, and core dump. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages denemo depends on: ii libasound2 1.0.11-7 ALSA library ii libatk1.0-01.11.4-2 The ATK accessibility toolkit ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libcairo2 1.0.4-2 The Cairo 2D vector graphics libra ii libfontconfig1 2.3.2-7 generic font configuration library ii libfreetype6 2.2.1-2 FreeType 2 font engine, shared lib ii libglib2.0-0 2.10.3-1 The GLib library of C routines ii libgtk2.0-02.8.18-1 The GTK+ graphical user interface ii libpango1.0-0 1.12.3-1 Layout and rendering of internatio ii libpng12-0 1.2.8rel-5.1 PNG library - runtime ii libx11-6 2:1.0.0-6 X11 client-side library ii libxcursor11.1.5.2-5 X cursor management library ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar ii libxfixes3 1:3.0.1.2-4 X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.0-5 X11 Input extension library ii libxinerama1 1:1.0.1-4 X11 Xinerama extension library ii libxml22.6.26.dfsg-1 GNOME XML library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender11:0.9.0.2-4 X Rendering Extension client libra ii zlib1g 1:1.2.3-12compression library - runtime Versions of packages denemo recommends: ii csound 1:4.23f13-1 powerful and versatile sound synth ii lilypond 2.6.3-10A program for typesetting sheet mu -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374799: python2.3-tables: has versioned dependency on virtual package python2.3-numarray
Package: python2.3-tables Severity: serious Tags: patch Justification: Policy 7.2 Hi, python2.3-tables is uninstallable on a sid distribution, because it depends on python2.3-numarray (= 1.5). With the new python policy, python2.3-numarray is a virtual package provided by python-numarray. A simple fix is the change the dependency in the control file to python-numarray (=1.5.1-4) for python2.3-tables and python2.4-tables. Thanks, -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374801: python-scientific: wrong versionned dependency on python-netcdf
Package: python-scientific
Severity: serious
Tags: patch
Justification: makes package uninstallable
Hi,
The python-scientific package version 2.4.9-5 depends on python-netcdf (=
2.4.11). Since
both packages are built with the same source, this means that the dependency
will never be
satisfied.
A simple fix is to set the version in the dependency to Source-Version:
Package: python-scientific
Architecture: all
- Depends: ${python:Depends}, python-numeric-ext (= 24.2-3), python-netcdf (=
2.4.11)
+ Depends: ${python:Depends}, python-numeric-ext (= 24.2-3), python-netcdf (=
${Source-Version})
Thanks for your work,
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-amd64-k8-smp
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374799: python2.3-tables: has versioned dependency on virtual package python2.3-numarray
On Wed, Jun 21, 2006 at 02:00:56PM +0200, Francesc Altet wrote: Hi Alexandre, I'm aware of this problem, but the fix is not so easy because I should transition the pytables packge to adopt the new Python policy: http://wiki.debian.org/DebianPython/NewPolicy I've tried to do this yesterday with the new 1.3.2 pytables version, but not completely succeeded. So, as I'm a bit busy lately, I'll probably ask for a NMU version until I can get the package properly transitioned. I'll try to come up with a detailed patch, and send it to the bug tracker for your inspection and approval. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Bug#373946: python-scipy: won't byte compile on installation
On Fri, Jun 16, 2006 at 08:40:45AM -0500, Carlo Segre wrote:
Package: python-scipy
Version: 0.3.2-9
Severity: grave
Justification: renders package unusable
On installation (with python-central 0.4.17) produces the following error
message:
Setting up python-scipy (0.3.2-9) ...
Compiling /usr/lib/python2.3/site-packages/scipy/stats/distributions.py ...
Sorry: IndentationError: ('unindent does not match any outer indentation
level', ('/usr/lib/python2.3/site-packages/scipy/stats/distributions.py',
733, 27, ' args = args[:-1]\n'))
pycentral: pycentral pkginstall: error byte-compiling files (267)
pycentral pkginstall: error byte-compiling files (267)
dpkg: error processing python-scipy (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
python-scipy
E: Sub-process /usr/bin/dpkg returned an error code (1)
The error is due to improper indentation on line 733 but when this is
corrected, there are two further errors on lines 736 and 739 as well. I
think that htis is due to messed up tabbing in the editor
/me puts on a brown paper bag.
Thanks for the notice. I rebuilt once more to reformat the changelog
yesterday, and didn't test the installation of that last build. I must
have goofed something with emacs :-(
I'm fixing this, and will upload an updated version within a few
minutes.
--
Alexandre Fayolle LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/services
Informatique scientifique: http://www.logilab.fr/science
signature.asc
Description: Digital signature
Bug#373165: python-matplotlib: depends on non existing pythonX.Y-numarray
Package: python-matplotlib Version: 0.86.2-4 Severity: serious Justification: package uninstallable Due to the recent changes in the python policy, python-matplotlib is not installable because it has dependencies on pythonX.Y-numarray and pythonX.Y-numarray-ext which are not available in unstable (python-numarray does not provide pythonX.Y-numarray) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357782: python-f2py: FTBFS: rest2html not found
tag 357782 +pending thanks On Sun, Mar 19, 2006 at 03:37:53PM +0100, [EMAIL PROTECTED] wrote: Package: python-f2py Version: 2.45.241+1926-2 Severity: serious Tags: patch Hi, building the package python-f2py in a clean sid build environment (with pbuilder) on i386 results in: snip rest2html has been renamed to rst2html. Changing it in debian/rules fixes the issue. Ok. Not entirely my fault then (I build with pbuilder before uploading). Thanks for considering. Fixed package will be uploaded today. Thanks for your bug report. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org Retrait du projet de loi DADVSI: http://eucd.info/petitions/index.php?petition=2 signature.asc Description: Digital signature
Bug#353512: python-logilab-common: garbage left on upgrade makes module useless
On Sun, Feb 19, 2006 at 12:39:03AM -0600, Joe Wreschnig wrote: Package: python-logilab-common Version: 0.13.1-3 Severity: serious After upgrading from the separate packages in 0.12.0-3, to 0.13.1-3, I still have a /usr/lib/python2.3/site-python/logilab/__init__.py (and pyc/pyo) file. Thus any attempt to import the module fails, so e.g. pylint crashes on startup. Thanks for the notice. I'll upload a fixed version later Incidentally, the new packaging doesn't do what you want. It compiles bytecode on install but doesn't have a strong version dep, meaning the compiled bytecode is useless for anything other than the version it was compiled with. So it will just be dead hard drive space after a Python transition. I expect that when the default python version migrates to 2.4 the python package will byte-compile all packages in /usr/lib/site-python. The issue of whether a package should or should not byte compile its modules has not yet been decided in the python policy. I'll leave it that way until a decision is made. -- Alexandre Fayolle LOGILAB, Paris (France). signature.asc Description: Digital signature
Bug#349627: installation of twisted-doc-2.1.0-2 fails
Package: twisted-doc Version: 2.1.0-2 Severity: serious Justification: makes package uninstallable Hi, When upgrading my computer, I got the following error: Setting up twisted-doc (2.1.0-2) ... cannot create dhelp file '/usr/share/doc/twisted-doc/core/howto/.dhelp': No such file or directory dpkg: error processing twisted-doc (--configure): subprocess post-installation script returned error exit status 2 Thanks for your time. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) twisted-doc depends on no packages. Versions of packages twisted-doc recommends: ii evince [postscript-viewe 0.4.0-1 Document (postscript, pdf) viewer ii firefox [www-browser]1.5.dfsg-4 lightweight web browser based on M ii gs-esp [postscript-viewe 8.15.1.dfsg.1-1 The Ghostscript PostScript interpr pn twisted-doc-api none (no description available) ii w3m [www-browser]0.5.1-4 WWW browsable pager with excellent ii xpdf-reader [pdf-viewer] 3.01-5 Portable Document Format (PDF) sui ii xpdf-utils [pdf-viewer] 3.01-5 Portable Document Format (PDF) sui -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321545: patch closing RC bugs on iripdb
tag 341341 +patch tag 321545 +patch thanks The attached patch closes the 2 RC bugs on iripdb. Could you please apply it and upload the resulting package? These RC bugs currently block iripdb from getting in testing and make it uninstallable in sid. Thanks for your time. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org Retrait du projet de loi DADVSI: http://eucd.info/petitions/index.php?petition=2 Signez cette pétition, et faites-la circuler autour de vous, avant le 20 décembre diff -u iripdb-0.1.3b/debian/changelog iripdb-0.1.3b/debian/changelog --- iripdb-0.1.3b/debian/changelog +++ iripdb-0.1.3b/debian/changelog @@ -1,3 +1,12 @@ +iripdb (0.1.3b-1.1) unstable; urgency=low + + * NMU + * Updated standards to 3.6.2 + * Versioned libtag1-dev build dependency (Closes: #321545) + * Versioned libid3-dev build dependency (Closes: #341341) + + -- Alexandre Fayolle [EMAIL PROTECTED] Tue, 13 Dec 2005 10:19:58 +0100 + iripdb (0.1.3b-1) unstable; urgency=low * New upstream release (Closes: #263166, #260751) diff -u iripdb-0.1.3b/debian/control iripdb-0.1.3b/debian/control --- iripdb-0.1.3b/debian/control +++ iripdb-0.1.3b/debian/control @@ -2,8 +2,8 @@ Section: sound Priority: optional Maintainer: Christoph Siess (CHS) [EMAIL PROTECTED] -Build-Depends: debhelper (= 4.0.0), libid3-3.8.3-dev, libvorbis-dev, libtag1-dev -Standards-Version: 3.6.1 +Build-Depends: debhelper (= 4.0.0), libid3-3.8.3-dev (= 3.8.3-5), libvorbis-dev, libtag1-dev (=1.4-3) +Standards-Version: 3.6.2 Package: iripdb Architecture: any signature.asc Description: Digital signature
Bug#338978: python2.3-pylint: Depends on unavailable package python2.3-logilab-astng
tag 338978 +pending On Mon, Nov 14, 2005 at 07:09:01PM +1300, Jamie Norrish wrote: Package: python2.3-pylint Version: 0.8.1-1 Severity: grave The new release of python2.3-pylint in unstable added a dependency on python2.3-logilab-astng, but there is no such package in the archive. The same appears true of the 2.2 and 2.4 versions of pylint. astng is in the NEW queue, waiting for the ftp-masters' approval. Please be patient. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org signature.asc Description: Digital signature
Bug#334374: python2.4-psyco: raises ImportError: undefined symbol PyFPE_jbuf (version mismatch?)
Hi, Sorry for the delayed answer, I was on vacation and somehow failed to see your mail when I came back last week. I shall investigate the issue this week and try to see what is wrong. Thanks for your report. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org signature.asc Description: Digital signature
Bug#333795: This is an FTBFS bug
tag 333795 +pending thanks On Fri, Nov 04, 2005 at 01:31:13PM +0100, Daniel Schepler wrote: package python-scipy severity 333795 serious thanks This bug should be RC since it makes the package unbuildable. Thanks for the notice. I'll upload an updated package fixing the problem shortly. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org signature.asc Description: Digital signature
Bug#337443: python2.1-logilab-common: Uninstallable due to unavailable python2.1-optik
tag 337443 +pending thanks On Fri, Nov 04, 2005 at 01:12:02PM +0100, Luk Claes wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: python2.1-logilab-common Severity: grave Version: 0.12.0-2 Hi python2.1-logilab-common is not installable in sid anymore as python2.1-optik is unavailable. Maybe python2.1-logilab-common can be dropped? I will probably drop python2.1-logilab-common in the next upload of the package. Thanks for the notice. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org signature.asc Description: Digital signature
Bug#327802: mozilla-firefox: Buffer overflow published on security-protocols.com
On Mon, Sep 12, 2005 at 01:24:28PM +0200, Mike Hommey wrote: Version: 1.0.6-5 Version: 1.4.99+1.5beta1-2 Please do not file duplicates. This is the same as #327452, and has already been taken a care of. Sorry about that. #327452 was not in the BTS when I filed the bug on friday evening, but my email was delayed over the week end (probably my ISP's email server was unreachable at that time, and the mail was only delivered this morning when I restarted my computer. Cheers, -- Alexandre Fayolle LOGILAB, Paris (France). signature.asc Description: Digital signature
Bug#315712: gnome-lokkit: depends on unavailable libc6 = 2.3.5-1
Package: gnome-lokkit Version: 0.50.22-5 Severity: serious Justification: package in sid depends on experimental libc6 Hi, gnome-lokkit 0.50.22-5 depends on libc6 = 2.3.5-1 which is only available in the experimental distribution, not in unstable. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
