Bug#546488: [xml/sgml-pkgs] Bug#546488: 2.7.4 breaks inkscape
On Sun, Sep 13, 2009 at 11:09:34PM -0400, Dylan Thurston wrote: severity 546488 grave thanks Package: libxml2 Version: 2.7.4.dfsg-1 Severity: normal Both default.svg and render_barcode.inx start with ?xml as the very first characters of the document. I've attached the files for reference. Presumably there's something funny about them. You forgot to attach the files... Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546559: gnumeric: keyboard control disabled after moving graph
Package: gnumeric Version: 1.9.12-1 Severity: grave Justification: renders package unusable Keyboard control is getting disabled again. The symptoms are the same as bug #544975 but the trigger is different. This time it's happening after I move an existing image to a different position in the window. Easy to reproduce, just put any numbers down Column A, 1 to 5 say. Copy them to Column B. Create a graph (Insert A Chart). Move the graph. After this there is no more normal keyboard control: arrow keys do not operate, typing does not start data entry into a cell. Control keys (C-w, C-c, C-v) do continue working. The bug occurs equally by inserting a chart via the menu or via the toolbar button. Marking as Grave for consistency with #544975. The bug prevents normal everyday use of the package. There seem to have been an unusually large number of these kinds of grave bugs recently, for instance with #544975, #542141. Has something gone seriously wrong upstream? Should we be reverting the whole thing back to v1.8 ? Thanks, Drew -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnumeric depends on: ii debconf [debc 1.5.27 Debian configuration management sy ii gconf22.26.2-3 GNOME configuration database syste ii gnumeric-comm 1.9.12-1 spreadsheet application for GNOME ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4 Fonts for the Ghostscript interpre ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit ii libc6 2.9-26 GNU C Library: Shared libraries ii libcairo2 1.8.8-2The Cairo 2D vector graphics libra ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.20.5-1 The GLib library of C routines ii libgoffice-0- 0.7.12-1 Document centric objects library - ii libgsf-1-114 1.14.15-1 Structured File Library - runtime ii libgtk2.0-0 2.16.6-1 The GTK+ graphical user interface ii libpango1.0-0 1.24.5-1 Layout and rendering of internatio ii libxml2 2.7.4.dfsg-1 GNOME XML library ii procps1:3.2.8-1 /proc file system utilities ii zlib1g1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages gnumeric recommends: ii evince2.26.2-2 Document (postscript, pdf) viewer Versions of packages gnumeric suggests: ii epiphany-browser 2.26.3-2 Intuitive web browser - dummy pack ii gnumeric-doc 1.9.12-1 spreadsheet application for GNOME ii gnumeric-plugins-extra1.9.12-1 spreadsheet application for GNOME ii ttf-liberation1.04.93-1 Free fonts with the same metrics a -- debconf information: * gnumeric/existing-process: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546488: [xml/sgml-pkgs] Bug#546488: 2.7.4 breaks inkscape
On Sun, Sep 13, 2009 at 11:09:34PM -0400, Dylan Thurston wrote: severity 546488 grave thanks Package: libxml2 Version: 2.7.4.dfsg-1 Severity: normal Both default.svg and render_barcode.inx start with ?xml as the very first characters of the document. I've attached the files for reference. Presumably there's something funny about them. I also think this is a grave bug (as it breaks an unrelated package), at least for the moment. Okay, I did trace inkscape startup, and it appears there appears to be a bug in libxml2, though I haven't determined what exactly yet. Until I find exactly what is broken, you can either downgrade libxml2, or remove the xml declarations from the files. That's what triggers the bug. A lot of other files don't have the declaration and are read fine. Cheers. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546561: python-glpk and python-debianbts: error when trying to install together
Package: python-debianbts,python-glpk Version: python-debianbts/0.4 Version: python-glpk/0.1.38-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-09-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libdb4.5 libsqlite3-0 mime-support python2.5-minimal python2.5 python-minimal python libgmp3c2 libltdl7 libglpk0 python-support python-fpconst python-glpk python-soappy python-debianbts Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libdb4.5. (Reading database ... 8826 files and directories currently installed.) Unpacking libdb4.5 (from .../libdb4.5_4.5.20-13_amd64.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.18-1_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.46-1_all.deb) ... Selecting previously deselected package python2.5-minimal. Unpacking python2.5-minimal (from .../python2.5-minimal_2.5.4-1_amd64.deb) ... Selecting previously deselected package python2.5. Unpacking python2.5 (from .../python2.5_2.5.4-1_amd64.deb) ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.5.4-2_all.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.5.4-2_all.deb) ... Selecting previously deselected package libgmp3c2. Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.3.1+dfsg-3_amd64.deb) ... Selecting previously deselected package libltdl7. Unpacking libltdl7 (from .../libltdl7_2.2.6a-4_amd64.deb) ... Selecting previously deselected package libglpk0. Unpacking libglpk0 (from .../libglpk0_4.38-1_amd64.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_1.0.3_all.deb) ... Selecting previously deselected package python-fpconst. Unpacking python-fpconst (from .../python-fpconst_0.7.2-4_all.deb) ... Selecting previously deselected package python-glpk. Unpacking python-glpk (from .../python-glpk_0.1.38-1_amd64.deb) ... Selecting previously deselected package python-soappy. Unpacking python-soappy (from .../python-soappy_0.12.0-4_all.deb) ... Selecting previously deselected package python-debianbts. Unpacking python-debianbts (from .../python-debianbts_0.4_all.deb) ... dpkg: error processing /var/cache/apt/archives/python-debianbts_0.4_all.deb (--unpack): trying to overwrite '/usr/share/pyshared/__init__.py', which is also in package python-glpk 0:0.1.38-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/python-debianbts_0.4_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/pyshared/__init__.py This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546562: parse-win32registry-utils and registry-tools: error when trying to install together
Package: registry-tools,parse-win32registry-utils Version: registry-tools/4.0.0~alpha8+git20090912-1 Version: parse-win32registry-utils/0.50-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-09-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! x11-common libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxfixes3 libmagic1 file libpcre3 libxml2 perl-modules perl ucf defoma libexpat1 libfreetype6 ttf-dejavu-core ttf-dejavu-extra ttf-dejavu fontconfig-config libfontconfig1 fontconfig libglib2.0-0 libatk1.0-0 libavahi-common-data libavahi-common3 libdbus-1-3 libavahi-client3 libsysfs2 tsconf libts-0.0-0 libdirectfb-1.2-0 libpixman-1-0 libpng12-0 libxcb-render0 libxcb-render-util0 libxrender1 libcairo2 libcairo-perl libcups2 libdatrie1 libglib-perl libgtk2.0-common libjpeg62 libjasper1 libpango1.0-common libthai-data libthai0 libxft2 libpango1.0-0 libtiff4 libxext6 libxcomposite1 libxcursor1 libxdamage1 libxi6 libxinerama1 libxrandr2 shared-mime-info libgtk2.0-0 libpango-perl libgtk2-perl libtalloc2 libtdb1 libtevent0 libldb0 parse-win32registry-utils registry-tools Extracting templates from packages: 43% Extracting templates from packages: 86% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package x11-common. (Reading database ... 8826 files and directories currently installed.) Unpacking x11-common (from .../x11-common_1%3a7.4+4_all.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.4-2_amd64.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.0.2-3_amd64.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.4-1_amd64.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.2.2-1_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.2.2-1_amd64.deb) ... Processing triggers for man-db ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up x11-common (1:7.4+4) ... Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libxfixes3. (Reading database ... 9129 files and directories currently installed.) Unpacking libxfixes3 (from .../libxfixes3_1%3a4.0.3-2_amd64.deb) ... Selecting previously deselected package libmagic1. Unpacking libmagic1 (from .../libmagic1_5.03-1_amd64.deb) ... Selecting previously deselected package file. Unpacking file (from .../archives/file_5.03-1_amd64.deb) ... Selecting previously deselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_7.8-2_amd64.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.7.4.dfsg-1_amd64.deb) ... Selecting previously deselected package perl-modules. Unpacking perl-modules (from .../perl-modules_5.10.0-25_all.deb) ... Selecting previously deselected package perl. Unpacking perl (from .../perl_5.10.0-25_amd64.deb) ... Selecting previously deselected package ucf. Unpacking ucf (from .../archives/ucf_3.0021_all.deb) ... Moving old data out of the way Selecting previously deselected package defoma. Unpacking defoma (from .../defoma_0.11.10-1_all.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-4_amd64.deb) ... Selecting previously deselected package libfreetype6. Unpacking libfreetype6 (from .../libfreetype6_2.3.9-5_amd64.deb) ... Selecting previously deselected package ttf-dejavu-core. Unpacking ttf-dejavu-core (from .../ttf-dejavu-core_2.30-1_all.deb) ... Selecting previously deselected package ttf-dejavu-extra. Unpacking ttf-dejavu-extra (from .../ttf-dejavu-extra_2.30-1_all.deb) ... Selecting previously deselected package ttf-dejavu. Unpacking ttf-dejavu (from .../ttf-dejavu_2.30-1_all.deb) ... Selecting previously deselected package fontconfig-config. Unpacking fontconfig-config (from .../fontconfig-config_2.6.0-4_all.deb) ... Selecting previously deselected package libfontconfig1. Unpacking libfontconfig1 (from .../libfontconfig1_2.6.0-4_amd64.deb) ... Selecting previously deselected package fontconfig. Unpacking fontconfig (from .../fontconfig_2.6.0-4_amd64.deb) ... Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.20.5-1_amd64.deb) ... Selecting previously deselected package libatk1.0-0. Unpacking libatk1.0-0 (from .../libatk1.0-0_1.26.0-1_amd64.deb) ... Selecting previously deselected package libavahi-common-data. Unpacking libavahi-common-data (from
Bug#516715: debreaper: ImportError: No module named reportbug
Daniel Leidert wrote: The reportbug module was shipped with reportbug 3.48, which was installed on your system at the time you wrote this report. Today it's shipped by python-reportbug but pulled in as dependency of reportbug. However, this looks more like a problem with reportbug 3.48 than a bug in debreaper. So I'm wondering if a) this report can be closed or b) a versioned dependency on reportbug is necessary? I could imagine that reportbug shipped its Python modules in a private modules directory, which was the right thing to do at that time. So you'd have to specify that modules directory in your sys.path. Now the proper thing would be a dependency onpython-reportbug I guess. -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546488: [xml/sgml-pkgs] Bug#546488: Bug#546488: 2.7.4 breaks inkscape
On Mon, Sep 14, 2009 at 08:44:02AM +0200, Mike Hommey wrote:
On Sun, Sep 13, 2009 at 11:09:34PM -0400, Dylan Thurston wrote:
severity 546488 grave
thanks
Package: libxml2
Version: 2.7.4.dfsg-1
Severity: normal
Both default.svg and render_barcode.inx start with ?xml as the very
first characters of the document. I've attached the files for
reference. Presumably there's something funny about them.
I also think this is a grave bug (as it breaks an unrelated package),
at least for the moment.
Okay, I did trace inkscape startup, and it appears there appears to be a
bug in libxml2, though I haven't determined what exactly yet.
Until I find exactly what is broken, you can either downgrade libxml2,
or remove the xml declarations from the files. That's what triggers the
bug. A lot of other files don't have the declaration and are read fine.
Found the culprit:
diff --git a/parser.c b/parser.c
index 0a10b0f..0d856b7 100644
--- a/parser.c
+++ b/parser.c
@@ -10109,8 +10109,9 @@ xmlParseDocument(xmlParserCtxtPtr ctxt) {
/*
* Check for the XMLDecl in the Prolog.
+ * do not GROW here to avoid the detected encoder to decode more
+ * than just the first line
*/
-GROW;
if ((CMP5(CUR_PTR, '', '?', 'x', 'm', 'l')) (IS_BLANK_CH(NXT(5 {
/*
I'll have to check with upstream on this one, as to why this change was done
exactly. I wouldn't like to break the other paths (inkscape using a special one,
which is why xmllint doesn't choke on the files where inkscape does)
Mike
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 546488, bug 546488 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=595128
Processing commands for cont...@bugs.debian.org: tags 546488 + upstream Bug #546488 [libxml2] libxml2: 2.7.4 breaks inkscape Added tag(s) upstream. forwarded 546488 https://bugzilla.gnome.org/show_bug.cgi?id=595128 Bug #546488 [libxml2] libxml2: 2.7.4 breaks inkscape Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=595128'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546518: bash: Still happens with 4.0.6
Package: bash Version: 4.0-6 Severity: normal I do have dash installed, but I chose not to use it as /bin/sh (my /bin/sh is bash), so I guess predepending on dash solves nothing in my case. It should be possible to upgrade bash cleanly, even if bash is used as /bin/sh. An install of bash 4.0-6 failed, (upgrading from 4.0-4) running --configure shows: $ sudo dpkg --configure -a [sudo] password for root: Processing triggers for menu ... dpkg (subprocess): unable to execute installed post-installation script: No such file or directory dpkg: error processing menu (--configure): subprocess installed post-installation script returned error exit status 2 Processing triggers for man-db ... dpkg (subprocess): unable to execute installed post-installation script: No such file or directory dpkg: error processing man-db (--configure): subprocess installed post-installation script returned error exit status 2 Setting up install-info (4.13a.dfsg.1-4) ... dpkg (subprocess): unable to execute installed post-installation script: No such file or directory dpkg: error processing install-info (--configure): subprocess installed post-installation script returned error exit status 2 Setting up bash (4.0-6) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode. Errors were encountered while processing: menu man-db install-info Running the configure again worked, since the symlink was already restored: $ sudo dpkg --pending --configure Setting up menu (2.1.41) ... Ignoring install-info called from maintainer script The package menu should be rebuild with new debhelper to get trigger support Setting up man-db (2.5.6-1) ... Building database of manual pages ... Setting up install-info (4.13a.dfsg.1-4) ... install-info: warning: no info dir entry in `/usr/share/info/ispell.info.gz' install-info: warning: no info dir entry in `/usr/share/info/menu.info.gz' install-info: warning: no info dir entry in `/usr/share/info/lilypond-learning.info.gz' install-info: warning: no info dir entry in `/usr/share/info/source-highlight.info.gz' install-info: warning: no info dir entry in `/usr/share/info/lilypond-program.info.gz' install-info: warning: no info dir entry in `/usr/share/info/lilypond-snippets.info-images-dir-dep.gz' install-info: warning: no info dir entry in `/usr/share/info/lilypond.info-images-dir-dep.gz' Processing triggers for menu .. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31 (SMP w/4 CPU cores; PREEMPT) 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 bash depends on: ii base-files5.0.0 Debian base system miscellaneous f ii dash 0.5.5.1-2.3POSIX-compliant shell ii debianutils 3.2.1 Miscellaneous utilities specific t ii libc6 2.9-26 GNU C Library: Shared libraries ii libncurses5 5.7+20090803-2 shared libraries for terminal hand Versions of packages bash recommends: ii bash-completion 1:1.0-3programmable completion for the ba Versions of packages bash suggests: ii bash-doc 4.0-4 Documentation and examples for the -- 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#523353: after upgrading xorg: no segfault anymore
Hi, after the latest upgrade of xorg to version 1:7.4+4, stellarium works fine again on my machine (squeeze). I guess this bug can be closed. Regards, Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546518: No /bin/sh between unpacking and configuring
Package: bash Version: 4.0-6 I experienced this problem when upgrading from 4.0-4 to 4.0-6. It immediately laid havoc to the rest of the upgrade process, and undoubtedly would have broken my system in interesting ways had I not intervened manually (by creating the sh link). -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-ibid-1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files5.0.0 Debian base system miscellaneous f ii dash 0.5.5.1-2.3POSIX-compliant shell ii debianutils 3.2.1 Miscellaneous utilities specific t ii libc6 2.9-26 GNU C Library: Shared libraries ii libncurses5 5.7+20090803-2 shared libraries for terminal hand Versions of packages bash recommends: ii bash-completion 1:1.0-3programmable completion for the ba Versions of packages bash suggests: pn bash-doc none (no description available) -- 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
Processed: requested removal of python-num{eric,array}, raising severity of packages depending on these
Processing commands for cont...@bugs.debian.org:
severity 478438 serious
Bug #478438 [aubio] aubio: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478440 serious
Bug #478440 [castle-combat] castle-combat: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478442 serious
Bug #478442 [gdeskcal] gdeskcal: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478446 serious
Bug #478446 [gnudatalanguage] gnudatalanguage: should use python-numpy instead
of python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478447 serious
Bug #478447 [gdesklets] gdesklets: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478453 serious
Bug #478453 [pykaraoke] pykaraoke: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478454 serious
Bug #478454 [pyracerz] pyracerz: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478456 serious
Bug #478456 [python-biggles] python-biggles: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478459 serious
Bug #478459 [python-stats] python-stats: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478460 serious
Bug #478460 [python-scientific] python-scientific: should use python-numpy
instead of python-num{eric,array}
Severity set to 'serious' from 'important'
severity 478463 serious
Bug #478463 [sixpack] sixpack: should use python-numpy instead of
python-num{eric,array}
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546578: widelands - FTBFS: scons: Command not found
Source: widelands Version: 1:14~rc1-1 Severity: serious There was an error while trying to autobuild your package: sbuild (Debian sbuild) 0.58.2 (15 Jun 2009) on lxdebian.bfinv.de [...] make: scons build=release build_id=Build14RC datadir=share/games/widelands scons: Command not found make: *** [build/widelands] Error 127 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543133: hpoj: FTBFS: Nonexistent build-dependency: ttf2pt1
The ttf2pt1 package was removed based on the request in URL: http://bugs.debian.org/503502 . I am not aware of any alternative, nor have I any idea what the package did, so I do not know what to propose as a workaround. I guess it was font related (ttf - true type font?), and hope some other tool can be used as a replacement. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: Installation/upgrade freezes when non-standard XKBLAYOUT used
Package: console-setup Version: 1.44 Severity: normal same here with Dvorak layout previously chosen though I just see it block and use 10% cpu and and no forking. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30.5 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-terminus 4.28-1 Fixed-width fonts for fast reading ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii xkb-data 1.6-1 X Keyboard Extension (XKB) configu Versions of packages console-setup recommends: ii kbd 1.15-1 Linux console font and keytable ut Versions of packages console-setup suggests: ii locales 2.9-25 GNU C Library: National Language ( ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip -- 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#544664: dma: auth.conf is readable by all users
On Sat, Sep 12, 2009 at 00:26:22 +0300, Peter Pentchev wrote: [...] Thus, I'm raising the severity of the world-readable auth.conf bug in the hope that this will prevent dma from migrating to testing, It's now in testing. Regards, Tino -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536693: mayavi segfault with tk8.5
The problem still appears to exist in Debian testing. However, installing the latest python-vtk package from unstable (which also pulls in libvtk5.2) appears to fix it. Francis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545674: tomcat6: Crashes when trying to run a web app, including admin
Hello Heikki and Jakub,
Thanks for this detailed error report. I believe that I have fixed this
issue, by adding a grant on /usr/share/maven-repo/ in the file
02debian.policy. Can you check that it is working? If you need, I have
created a new .deb in my PPA
(https://launchpad.net/~ludovicc/+archive/ppa/), and I will add those
fixes shortly to Debian.
02debian.policy:
// These permissions apply to all JARs from Debian packages
grant codeBase file:/usr/share/java/- {
permission java.security.AllPermission;
};
grant codeBase file:/usr/share/maven-repo/- {
permission java.security.AllPermission;
};
grant codeBase file:/usr/share/ant/lib/- {
permission java.security.AllPermission;
};
Ludovic
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546518: marked as done (bash: No /bin/sh between unpacking and configuring)
Your message dated Mon, 14 Sep 2009 10:35:13 + with message-id e1mn8tt-0004m4...@ries.debian.org and subject line Bug#546516: fixed in bash 4.0-7 has caused the Debian Bug report #546516, regarding bash: No /bin/sh between unpacking and configuring to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 546516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bash Version: 4.0-5 Severity: serious If dash is _not_ configured to be used as /bin/sh, installing bash 4.0-5 loses the /bin/sh symlink during the unpack phase which leads to interesting problems when other packages' postinst scripts are triggered: , | # LANG=C aptitude safe-upgrade | Reading package lists... Done | Building dependency tree | Reading state information... Done | Reading extended state information | Initializing package states... Done | The following packages will be upgraded: | bash | 1 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. | Need to get 0B/1098kB of archives. After unpacking 0B will be used. | Do you want to continue? [Y/n/?] | Writing extended state information... Done | (Reading database ... 20103 files and directories currently installed.) | Preparing to replace bash 4.0-4 (using .../archives/bash_4.0-5_i386.deb) ... | Unpacking replacement bash ... | Processing triggers for install-info ... | dpkg (subprocess): unable to execute installed post-installation script: No such file or directory | dpkg: subprocess installed post-installation script returned error exit status 2 | E: Sub-process /usr/bin/dpkg returned an error code (2) | A package failed to install. Trying to recover: | E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. | E: Could not regain the system lock! (Perhaps another apt or dpkg is running?) | E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. | Reading package lists... Done | Building dependency tree | Reading state information... Done | Reading extended state information | Initializing package states... Done ` Fortunately bash's postinst restores the /bin/sh symlink, so running dpkg --configure --pending fixed up things, although I had to run it twice to get all the triggers processed. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.30.6-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: bash Source-Version: 4.0-7 We believe that the bug you reported is fixed in the latest version of bash, which is due to be installed in the Debian FTP archive: bash-builtins_4.0-7_i386.deb to pool/main/b/bash/bash-builtins_4.0-7_i386.deb bash-doc_4.0-7_all.deb to pool/main/b/bash/bash-doc_4.0-7_all.deb bash-minimal_4.0-7_i386.deb to pool/main/b/bash/bash-minimal_4.0-7_i386.deb bash-static_4.0-7_i386.deb to pool/main/b/bash/bash-static_4.0-7_i386.deb bash_4.0-7.diff.gz to pool/main/b/bash/bash_4.0-7.diff.gz bash_4.0-7.dsc to pool/main/b/bash/bash_4.0-7.dsc bash_4.0-7_i386.deb to pool/main/b/bash/bash_4.0-7_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 546...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated bash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Sep 2009 08:11:58 +0200 Source: bash Binary: bash bash-minimal bash-static bash-builtins bash-doc bashdb Architecture: source all i386 Version: 4.0-7 Distribution: unstable Urgency: medium Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: bash - The GNU Bourne Again SHell bash-builtins - Bash loadable builtins - headers examples bash-doc - Documentation and examples for the The GNU Bourne Again SHell bash-minimal - The GNU Bourne Again SHell (minimal version) bash-static - The GNU Bourne Again SHell (static version) bashdb
Bug#546516: marked as done (bash: 4.0-5 failed to install)
Your message dated Mon, 14 Sep 2009 10:35:13 + with message-id e1mn8tt-0004m4...@ries.debian.org and subject line Bug#546516: fixed in bash 4.0-7 has caused the Debian Bug report #546516, regarding bash: 4.0-5 failed to install to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 546516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bash Version: 4.0-5 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Preparing to replace bash 4.0-4 (using .../archives/bash_4.0-5_amd64.deb) ... Unpacking replacement bash ... Processing triggers for install-info ... dpkg (subprocess): unable to execute installed post-installation script: No such file or directory dpkg: subprocess installed post-installation script returned error exit status 2 E: Problem executing scripts DPkg::Post-Invoke 'if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi' E: Sub-process returned an error code E: Sub-process /usr/bin/dpkg returned an error code (2) A package failed to install. Trying to recover: Press return to continue. - -- System Information: Debian Release: squeeze/sid Architecture: x86_64 Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=sv_SE (charmap=) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkqtQ1UACgkQw5UvgfnzqGqhngCeNRedD4gZwrmJvfMcbQEnNDNw GS4AnArJ/hj4fMK0fUnD7haiuG8JR0mq =52ua -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: bash Source-Version: 4.0-7 We believe that the bug you reported is fixed in the latest version of bash, which is due to be installed in the Debian FTP archive: bash-builtins_4.0-7_i386.deb to pool/main/b/bash/bash-builtins_4.0-7_i386.deb bash-doc_4.0-7_all.deb to pool/main/b/bash/bash-doc_4.0-7_all.deb bash-minimal_4.0-7_i386.deb to pool/main/b/bash/bash-minimal_4.0-7_i386.deb bash-static_4.0-7_i386.deb to pool/main/b/bash/bash-static_4.0-7_i386.deb bash_4.0-7.diff.gz to pool/main/b/bash/bash_4.0-7.diff.gz bash_4.0-7.dsc to pool/main/b/bash/bash_4.0-7.dsc bash_4.0-7_i386.deb to pool/main/b/bash/bash_4.0-7_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 546...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose d...@debian.org (supplier of updated bash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Sep 2009 08:11:58 +0200 Source: bash Binary: bash bash-minimal bash-static bash-builtins bash-doc bashdb Architecture: source all i386 Version: 4.0-7 Distribution: unstable Urgency: medium Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: bash - The GNU Bourne Again SHell bash-builtins - Bash loadable builtins - headers examples bash-doc - Documentation and examples for the The GNU Bourne Again SHell bash-minimal - The GNU Bourne Again SHell (minimal version) bash-static - The GNU Bourne Again SHell (static version) bashdb - The GNU Bourne Again SHell Debugger Closes: 546516 Changes: bash (4.0-7) unstable; urgency=medium . * Re-add the sh and sh(1) symlinks. Closes: #546516. Checksums-Sha1: 2f16a97e0725c69914abefde5a764aeb3fdfa8a8 1182 bash_4.0-7.dsc a08a28c7f7d5cab08d0a0783053e342b605e2941 100630 bash_4.0-7.diff.gz 63abb022187e1dc4b72fc6995e4c8051e79186b9 312326 bash-doc_4.0-7_all.deb 8d0b849eb37a4b68ceda01148919ad173aa88fb4 1097868 bash_4.0-7_i386.deb c22ff8d2b9e513f4c036bb87644cff3ce18b73b2 107088 bash-builtins_4.0-7_i386.deb 51de76f04dcff13a08b37b3093d33e7c52ccbd38 775710 bash-static_4.0-7_i386.deb 5f3c4a93f88d81a87b3155d1a8e51da166d33d94 223538 bash-minimal_4.0-7_i386.deb Checksums-Sha256: 978a203529b9a9e064c5696e6bb0f4172420dffcd233db21d35507056331fc6f 1182 bash_4.0-7.dsc eeda4292c72eaf4e27287dffce0f75f0262a985df655e74b0c05ba41f3f6153d 100630 bash_4.0-7.diff.gz 8c1a21674dff7b2bf0ab917f59b2b6051c16d537aeab53294d589d1ee8a0ffda 312326 bash-doc_4.0-7_all.deb 47356e2c4cee376791ec72fa13dc83eff52c2eec1c8fed61d12c2eefa062c412 1097868 bash_4.0-7_i386.deb
Bug#543369: marked as done (gnu-fdisk: ships /usr/share/info/dir.gz)
Your message dated Mon, 14 Sep 2009 10:37:33 + with message-id e1mn8w9-00055b...@ries.debian.org and subject line Bug#543369: fixed in gnu-fdisk 1.2.3-1.1 has caused the Debian Bug report #543369, regarding gnu-fdisk: ships /usr/share/info/dir.gz to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 543369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnu-fdisk Version: 1.2.3-1 Severity: normal error messages during attempted installation: trying to overwrite `/usr/share/info/dir.gz', which is also in package lightning trying to overwrite `/usr/share/info/dir.gz', which is also in package opencubicplayer -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages gnu-fdisk depends on: ii dpkg 1.15.3.1 Debian package management system ii install-info 4.13a.dfsg.1-4 Manage installed documentation in ii libc6 2.9-25 GNU C Library: Shared libraries ii libncurses5 5.7+20090803-1+b1 shared libraries for terminal hand ii libparted1.8-12 1.8.8.git.2009.07.19-5 The GNU Parted disk partitioning s ii libreadline5 5.2-6 GNU readline and history libraries ii libuuid1 2.16-3 Universally Unique ID library gnu-fdisk recommends no packages. gnu-fdisk suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gnu-fdisk Source-Version: 1.2.3-1.1 We believe that the bug you reported is fixed in the latest version of gnu-fdisk, which is due to be installed in the Debian FTP archive: gnu-fdisk_1.2.3-1.1.diff.gz to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.1.diff.gz gnu-fdisk_1.2.3-1.1.dsc to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.1.dsc gnu-fdisk_1.2.3-1.1_amd64.deb to pool/main/g/gnu-fdisk/gnu-fdisk_1.2.3-1.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 543...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes l...@debian.org (supplier of updated gnu-fdisk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Sep 2009 08:14:05 + Source: gnu-fdisk Binary: gnu-fdisk Architecture: source amd64 Version: 1.2.3-1.1 Distribution: unstable Urgency: high Maintainer: Parted Maintainer Team parted-maintain...@lists.alioth.debian.org Changed-By: Luk Claes l...@debian.org Description: gnu-fdisk - Linux fdisk replacement based on libparted Closes: 543369 Changes: gnu-fdisk (1.2.3-1.1) unstable; urgency=high . * Non-maintainer upload. * Don't ship info/dir.gz (Closes: #543369). Checksums-Sha1: 0a7bbc8ee58ad52fb7cf4fe8d3575fd0c313506c 1200 gnu-fdisk_1.2.3-1.1.dsc e2fce03ff3bca678b9a3bf6cff0991ce2d2c9dd5 19511 gnu-fdisk_1.2.3-1.1.diff.gz db6a8170bb46e8874e3c1ea5b5a7001c63f3ac4f 113168 gnu-fdisk_1.2.3-1.1_amd64.deb Checksums-Sha256: b2d5972954e8e866272af0db8ee633b19c7ef895bb4e089c7f8d2f80bebcc697 1200 gnu-fdisk_1.2.3-1.1.dsc 5c697d804ab1ab6eeb1cc954d1813f356be1524e9e12b09107e31cff655fdd6d 19511 gnu-fdisk_1.2.3-1.1.diff.gz ffcea75784ea95b3194dacadd9b164dda9ee61f30bf2a75f2847747d67d5c1c2 113168 gnu-fdisk_1.2.3-1.1_amd64.deb Files: 3665d6a88407a886640843d33275f42c 1200 utils extra gnu-fdisk_1.2.3-1.1.dsc ac80a27ebb97ecece208411cc3a98c7b 19511 utils extra gnu-fdisk_1.2.3-1.1.diff.gz 79ec329688d3137c35623aac3da66e64 113168 utils extra gnu-fdisk_1.2.3-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkqrWj0ACgkQ5UTeB5t8Mo2zzACeNX/bOnKizBEgZSemKfZURFe7 kRwAoKhVaW6uXvyrWGMWWo95IHQYJ8tJ =eBWo -END PGP SIGNATURE- ---End Message---
Bug#545029: assertion `GTK_IS_LIST_STORE (combo_box-priv-model)' failed
hello, could someone please try the new version (which is not ready for publication, I will publish it when this bug is closed): www.opbyte.it/release/grsync-0.9.2.tar.gz thanks very much! Piero Orsoni -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478459: marked as done (python-stats: should use python-numpy instead of python-num{eric,array})
Your message dated Mon, 14 Sep 2009 11:01:06 +
with message-id e1mn9iw-0007dq...@ries.debian.org
and subject line Bug#478459: fixed in python-stats 0.6-8
has caused the Debian Bug report #478459,
regarding python-stats: should use python-numpy instead of
python-num{eric,array}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
478459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-stats
Version: 0.6-6
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python-oldnum
Both python-numeric and python-numarray do not see new upstream releases
anymore; the currently maintained project is python-numpy. Please convert
the package to use python-numpy instead. This might require changes to
the upstream code.
---End Message---
---BeginMessage---
Source: python-stats
Source-Version: 0.6-8
We believe that the bug you reported is fixed in the latest version of
python-stats, which is due to be installed in the Debian FTP archive:
python-stats_0.6-8.diff.gz
to pool/main/p/python-stats/python-stats_0.6-8.diff.gz
python-stats_0.6-8.dsc
to pool/main/p/python-stats/python-stats_0.6-8.dsc
python-stats_0.6-8_all.deb
to pool/main/p/python-stats/python-stats_0.6-8_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 478...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python-stats package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 14 Sep 2009 08:19:49 +0200
Source: python-stats
Binary: python-stats
Architecture: source all
Version: 0.6-8
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
python-stats - A collection of statistical functions for Python
Closes: 478459
Changes:
python-stats (0.6-8) unstable; urgency=low
.
* Update modules for Numpy. Closes: #478459.
Checksums-Sha1:
45607da0be03baf78984af7162a77198362545a5 1145 python-stats_0.6-8.dsc
009d11762633bd0699be6d44d72c8bfefae324df 113139 python-stats_0.6-8.diff.gz
0485232d00e16fff6755d9ccc990b71b669004f4 68748 python-stats_0.6-8_all.deb
Checksums-Sha256:
dd883bc7bb887a7f8ee308610379b28fb8e0fa76e5c581fcfa763bf08edd0a0e 1145
python-stats_0.6-8.dsc
23957c581e33e9d4086ef91cac18c3fa0a20aa605f06b214773c6f8655289e5e 113139
python-stats_0.6-8.diff.gz
2349fed5e40212595e89ac2e7c8c4423970b94bd871f941514fa875544aeae0b 68748
python-stats_0.6-8_all.deb
Files:
9b6930fbcb05ae3bbe9efff84bd517f1 1145 python optional python-stats_0.6-8.dsc
62b15280b47de60947e8307cd264b96c 113139 python optional
python-stats_0.6-8.diff.gz
8b3954e85568d27ed95b6201007287c9 68748 python optional
python-stats_0.6-8_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqt/UYACgkQStlRaw+TLJzWfQCglLcq873xBfwTLhdVsU56AhLC
1rIAoLRWyEVgdwWdQInWe0lYtC+jjhmO
=Y3AL
-END PGP SIGNATURE-
---End Message---
Bug#529503: marked as done (postgis: Please remove build-dep on jikes-classpath)
Your message dated Mon, 14 Sep 2009 11:00:49 + with message-id e1mn9if-0007cr...@ries.debian.org and subject line Bug#529503: fixed in postgis 1.3.6-1 has caused the Debian Bug report #529503, regarding postgis: Please remove build-dep on jikes-classpath to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 529503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgis Version: 1.3.5-1 Severity: important Hi, jikes is orphaned, unmaintained, and buggy and therefore we are trying to remove it from the archive. postgis currently build-depends on jikes-classpath. Could you please try to build with one of the other java compilers and remove the jikes-classpath build-depends? Thank you, Barry deFreese Debian QA ---End Message--- ---BeginMessage--- Source: postgis Source-Version: 1.3.6-1 We believe that the bug you reported is fixed in the latest version of postgis, which is due to be installed in the Debian FTP archive: libpostgis-java_1.3.6-1_all.deb to pool/main/p/postgis/libpostgis-java_1.3.6-1_all.deb postgis_1.3.6-1.diff.gz to pool/main/p/postgis/postgis_1.3.6-1.diff.gz postgis_1.3.6-1.dsc to pool/main/p/postgis/postgis_1.3.6-1.dsc postgis_1.3.6-1_i386.deb to pool/main/p/postgis/postgis_1.3.6-1_i386.deb postgis_1.3.6.orig.tar.gz to pool/main/p/postgis/postgis_1.3.6.orig.tar.gz postgresql-8.3-postgis_1.3.6-1_i386.deb to pool/main/p/postgis/postgresql-8.3-postgis_1.3.6-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 529...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francesco Paolo Lovergine fran...@debian.org (supplier of updated postgis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Sep 2009 11:11:11 +0200 Source: postgis Binary: postgresql-8.3-postgis postgis libpostgis-java Architecture: source i386 all Version: 1.3.6-1 Distribution: unstable Urgency: medium Maintainer: Francesco Paolo Lovergine fran...@debian.org Changed-By: Francesco Paolo Lovergine fran...@debian.org Description: libpostgis-java - geographic objects support for PostgreSQL -- JDBC support postgis- geographic objects support for PostgreSQL -- common files postgresql-8.3-postgis - geographic objects support for PostgreSQL 8.3 Closes: 529503 Changes: postgis (1.3.6-1) unstable; urgency=medium . * New upstream release. * Now uses default-jdk instead of jikes-classpath. (closes: #529503) Checksums-Sha1: 1f3f3de5b4edcf3b89ea64ebb4557e2e47c40524 1503 postgis_1.3.6-1.dsc 1d4c34a31994b75ef79cf139543fc80fe0bd4438 2227317 postgis_1.3.6.orig.tar.gz 7de2e12083d494cb80897aa12ad62a1630fdea04 10338 postgis_1.3.6-1.diff.gz 20a0eac13175259b51067c40e04f0dff3bad7378 458084 postgresql-8.3-postgis_1.3.6-1_i386.deb 412226fb16ae171babb9a5760de705e394376507 213238 postgis_1.3.6-1_i386.deb 7828373c82105b1379497956f23dc3e5e8b8b747 317170 libpostgis-java_1.3.6-1_all.deb Checksums-Sha256: 528d3f257cefec6f6b1f326ebddf1b671808706562d889fd17ab4c652acefe4a 1503 postgis_1.3.6-1.dsc d3b04d4a3439596a1f6368b0627f21762347cef1e0694d5471ef17c6a3b7d144 2227317 postgis_1.3.6.orig.tar.gz a80f0c07f233fdbb9b0f2e39b883d312468978a88f2eea32706e21b2ec6517a0 10338 postgis_1.3.6-1.diff.gz 3a7f53b82e9010d0897e9407f4335a7fddc231582ca4ef546c38ecc65c5a1729 458084 postgresql-8.3-postgis_1.3.6-1_i386.deb e660dbd0885140944c5d6c60d1b95bc31c43090f81a98979d2905bb7d449dba5 213238 postgis_1.3.6-1_i386.deb 1b5896f6b7dd8fc8b27f8e2af18805e2601638c9e4d3eda0076427267c4c4a43 317170 libpostgis-java_1.3.6-1_all.deb Files: 0a6a4329c5872620320612f5e52bbf6b 1503 misc optional postgis_1.3.6-1.dsc da590f0e485335e9cdaeb66c3d68aa24 2227317 misc optional postgis_1.3.6.orig.tar.gz 05f3e35b2110cb79f60840f20d13583f 10338 misc optional postgis_1.3.6-1.diff.gz f4aa55fcf9b08999a185f2f9c4ab8924 458084 misc optional postgresql-8.3-postgis_1.3.6-1_i386.deb e6ede5eb333e3d2105284ffc5c5cf868 213238 misc optional postgis_1.3.6-1_i386.deb a42c7d12ac04e9847cc7eaac60daa0e6 317170 science optional libpostgis-java_1.3.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux)
Bug#546561: marked as done (python-glpk and python-debianbts: error when trying to install together)
Your message dated Mon, 14 Sep 2009 11:00:57 + with message-id e1mn9in-0007d6...@ries.debian.org and subject line Bug#546561: fixed in python-debianbts 0.5 has caused the Debian Bug report #546561, regarding python-glpk and python-debianbts: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 546561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-debianbts,python-glpk Version: python-debianbts/0.4 Version: python-glpk/0.1.38-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2009-09-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libdb4.5 libsqlite3-0 mime-support python2.5-minimal python2.5 python-minimal python libgmp3c2 libltdl7 libglpk0 python-support python-fpconst python-glpk python-soappy python-debianbts Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libdb4.5. (Reading database ... 8826 files and directories currently installed.) Unpacking libdb4.5 (from .../libdb4.5_4.5.20-13_amd64.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.6.18-1_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.46-1_all.deb) ... Selecting previously deselected package python2.5-minimal. Unpacking python2.5-minimal (from .../python2.5-minimal_2.5.4-1_amd64.deb) ... Selecting previously deselected package python2.5. Unpacking python2.5 (from .../python2.5_2.5.4-1_amd64.deb) ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.5.4-2_all.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.5.4-2_all.deb) ... Selecting previously deselected package libgmp3c2. Unpacking libgmp3c2 (from .../libgmp3c2_2%3a4.3.1+dfsg-3_amd64.deb) ... Selecting previously deselected package libltdl7. Unpacking libltdl7 (from .../libltdl7_2.2.6a-4_amd64.deb) ... Selecting previously deselected package libglpk0. Unpacking libglpk0 (from .../libglpk0_4.38-1_amd64.deb) ... Selecting previously deselected package python-support. Unpacking python-support (from .../python-support_1.0.3_all.deb) ... Selecting previously deselected package python-fpconst. Unpacking python-fpconst (from .../python-fpconst_0.7.2-4_all.deb) ... Selecting previously deselected package python-glpk. Unpacking python-glpk (from .../python-glpk_0.1.38-1_amd64.deb) ... Selecting previously deselected package python-soappy. Unpacking python-soappy (from .../python-soappy_0.12.0-4_all.deb) ... Selecting previously deselected package python-debianbts. Unpacking python-debianbts (from .../python-debianbts_0.4_all.deb) ... dpkg: error processing /var/cache/apt/archives/python-debianbts_0.4_all.deb (--unpack): trying to overwrite '/usr/share/pyshared/__init__.py', which is also in package python-glpk 0:0.1.38-1 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/python-debianbts_0.4_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/share/pyshared/__init__.py This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. ---End Message--- ---BeginMessage--- Source: python-debianbts Source-Version: 0.5 We believe that the bug you reported is fixed in the latest version of python-debianbts, which is due to be installed in the Debian FTP archive: python-debianbts_0.5.dsc to pool/main/p/python-debianbts/python-debianbts_0.5.dsc python-debianbts_0.5.tar.gz to
Bug#546595: zope.schema: Typo in debian/rules, Depends: inserted into Provides: making package unusable.
Package: zope.schema Version: 3.5.4-2 Severity: grave Tags: patch Justification: renders package unusable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu karmic ubuntu-patch Hi, it looks like there was a typo in debian/rules causing the Depends: to get inserted into the Provides:. *** /tmp/tmpb4Smxd In Ubuntu, we've applied the attached patch to achieve the following: * debian/rules: Don't insert Depends: into Provides (LP: #428098) We thought you might be interested in doing the same. -- System Information: Debian Release: squeeze/sid APT prefers karmic-updates APT policy: (500, 'karmic-updates'), (500, 'karmic') Architecture: i386 (i686) Kernel: Linux 2.6.31-10-generic-pae (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/dash diff -u zope.schema-3.5.4/debian/changelog zope.schema-3.5.4/debian/changelog diff -u zope.schema-3.5.4/debian/rules zope.schema-3.5.4/debian/rules --- zope.schema-3.5.4/debian/rules +++ zope.schema-3.5.4/debian/rules @@ -5,5 +5,5 @@ dependencies-python%: (echo -n 'setuptools:Depends=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars - (echo -n 'setuptools:Provides=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars + (echo -n 'setuptools:Provides=' van-pydeb provides --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars # docs and test to suggests (echo -n 'setuptools:Suggests=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --extra docs) debian/$(package).substvars
Bug#546595: marked as done (zope.schema: Typo in debian/rules, Depends: inserted into Provides: making package unusable.)
Your message dated Mon, 14 Sep 2009 14:40:35 +0200 with message-id 20090914124035.ga5...@mail.26dimensions.com and subject line Re: Bug#546595: zope.schema: Typo in debian/rules, Depends: inserted into Provides: making package unusable. has caused the Debian Bug report #546595, regarding zope.schema: Typo in debian/rules, Depends: inserted into Provides: making package unusable. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 546595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: zope.schema Version: 3.5.4-2 Severity: grave Tags: patch Justification: renders package unusable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu karmic ubuntu-patch Hi, it looks like there was a typo in debian/rules causing the Depends: to get inserted into the Provides:. *** /tmp/tmpb4Smxd In Ubuntu, we've applied the attached patch to achieve the following: * debian/rules: Don't insert Depends: into Provides (LP: #428098) We thought you might be interested in doing the same. -- System Information: Debian Release: squeeze/sid APT prefers karmic-updates APT policy: (500, 'karmic-updates'), (500, 'karmic') Architecture: i386 (i686) Kernel: Linux 2.6.31-10-generic-pae (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/dash diff -u zope.schema-3.5.4/debian/changelog zope.schema-3.5.4/debian/changelog diff -u zope.schema-3.5.4/debian/rules zope.schema-3.5.4/debian/rules --- zope.schema-3.5.4/debian/rules +++ zope.schema-3.5.4/debian/rules @@ -5,5 +5,5 @@ dependencies-python%: (echo -n 'setuptools:Depends=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars - (echo -n 'setuptools:Provides=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars + (echo -n 'setuptools:Provides=' van-pydeb provides --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars # docs and test to suggests (echo -n 'setuptools:Suggests=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --extra docs) debian/$(package).substvars ---End Message--- ---BeginMessage--- Version: 3.5.4-4 The bug is already closed with the upload 3.5.4-4. Thanks, Fabio * 2009-09-14 14:18, Elliot Murphy wrote: Package: zope.schema Version: 3.5.4-2 Severity: grave Tags: patch Justification: renders package unusable User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu karmic ubuntu-patch Hi, it looks like there was a typo in debian/rules causing the Depends: to get inserted into the Provides:. *** /tmp/tmpb4Smxd In Ubuntu, we've applied the attached patch to achieve the following: * debian/rules: Don't insert Depends: into Provides (LP: #428098) We thought you might be interested in doing the same. -- System Information: Debian Release: squeeze/sid APT prefers karmic-updates APT policy: (500, 'karmic-updates'), (500, 'karmic') Architecture: i386 (i686) Kernel: Linux 2.6.31-10-generic-pae (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/dash diff -u zope.schema-3.5.4/debian/changelog zope.schema-3.5.4/debian/changelog diff -u zope.schema-3.5.4/debian/rules zope.schema-3.5.4/debian/rules --- zope.schema-3.5.4/debian/rules +++ zope.schema-3.5.4/debian/rules @@ -5,5 +5,5 @@ dependencies-python%: (echo -n 'setuptools:Depends=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars - (echo -n 'setuptools:Provides=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars + (echo -n 'setuptools:Provides=' van-pydeb provides --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --exclude-extra hook --exclude-extra docs) debian/$(package).substvars # docs and test to suggests (echo -n 'setuptools:Suggests=' van-pydeb depends --egg-info debian/$(package)/$(call py_libdir,$*)/$(py_package).egg-info --extra docs) debian/$(package).substvars
Bug#542218: marked as done (backuppc: Security hole when using rsync and multiple users)
Your message dated Mon, 14 Sep 2009 12:32:07 + with message-id e1mnaj1-0006cw...@ries.debian.org and subject line Bug#542218: fixed in backuppc 3.1.0-7 has caused the Debian Bug report #542218, regarding backuppc: Security hole when using rsync and multiple users to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 542218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: backuppc Version: 3.1.0-4 Severity: critical Tags: security Justification: root security hole When using an SSH key and Rsync with BackupPC on a system with multiple users, Users (as opposed to admins) have the ability to change the ClientNameAlias on machines they are listed as owning. As BackupPC user has one ssh key, which can be in the authorized keys of many machines (often as root), this allows a user to backup from and restore to any machines that key gives access to, by changing the ClientNameAlias to the target machine and initiating a backup. I've just tested this, and as an unpriviledged user was able to change backing up /scratch on my desktop to /etc on a server and then read /etc/shadow from the server. Whilst I haven't tested this, I see no reason I couldn't restore to the server as well, thus changing arbitrary files as root (and gaining root access). -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages backuppc depends on: ii adduser 3.110 add and remove users and groups ii apache2 2.2.9-10+lenny2 Apache HTTP Server metapackage ii apache2-mpm-worker [http 2.2.9-10+lenny2 Apache HTTP Server - high speed th ii bzip21.0.5-1 high-quality block-sorting file co ii debconf [debconf-2.0]1.5.24 Debian configuration management sy ii dpkg 1.14.25 Debian package management system ii libarchive-zip-perl 1.18-1 Module for manipulation of ZIP arc ii libcompress-zlib-perl2.012-1 Perl module for creation and manip ii perl [libdigest-md5-perl 5.10.0-19 Larry Wall's Practical Extraction ii perl-suid5.10.0-19 Runs setuid Perl scripts ii samba-common 2:3.2.5-4lenny2 Samba common files used by both th ii smbclient2:3.2.5-4lenny2 a LanManager-like simple client fo ii tar 1.20-1 GNU version of the tar archiving u Versions of packages backuppc recommends: ii libfile-rsyncp-perl 0.68-1.1+b1 A perl based implementation of an ii openssh-client [ssh-client] 1:5.1p1-5 secure shell client, an rlogin/rsh ii postfix [mail-transport-agen 2.5.5-1.1 High-performance mail transport ag ii rrdtool 1.3.1-4 Time-series data storage and displ ii rsync3.0.3-2 fast remote file copy program (lik Versions of packages backuppc suggests: pn par2 none (no description available) ii w3m [www-browser] 0.5.2-2+b1 WWW browsable pager with excellent -- debconf information excluded ---End Message--- ---BeginMessage--- Source: backuppc Source-Version: 3.1.0-7 We believe that the bug you reported is fixed in the latest version of backuppc, which is due to be installed in the Debian FTP archive: backuppc_3.1.0-7.diff.gz to pool/main/b/backuppc/backuppc_3.1.0-7.diff.gz backuppc_3.1.0-7.dsc to pool/main/b/backuppc/backuppc_3.1.0-7.dsc backuppc_3.1.0-7_all.deb to pool/main/b/backuppc/backuppc_3.1.0-7_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 542...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ludovic Drolez ldro...@debian.org (supplier of updated backuppc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 01 Sep 2009 14:43:36 +0200 Source: backuppc Binary: backuppc Architecture: source all Version: 3.1.0-7 Distribution: unstable Urgency: high
Bug#546603: [xorg] have no mouse or keyboard after xorg upgrade
Package: xorg Version: 1:7.4+4 Severity: critical --- Please enter the report below this line. --- I upgraded my squeeze box this morning to the new xorg that just hit testing. When I get the gdm prompt I have no keyboard or mouse. I can connect to the computer remotely which is how I am submitting this bug report. The computer is an IBM thinkpad T42p. bre...@belmer:~$ lspci 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) 01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL Mobility T2] (rev 80) 02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01) 02:01.0 Ethernet controller: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) (rev 03) 02:02.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC (rev 01) You can see it has an ATI video card so X is trying to use the radeon driver. I see this in my Xorg.0.log: (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. I am attaching my Xorg.0.log and my xorg.conf. What do I need to do to make this work? I was previously using fglrx but the upgrade to xorg removed fglrx so I can't easily go back to fglrx which is okay if the radeon driver will work. --- System information. --- Architecture: i386 Kernel: Linux 2.6.30.090729 Debian Release: squeeze/sid 500 testing www.debian-multimedia.org 500 testing security.debian.org 500 testing debian.linux.ibm.com 500 jaunty ppa.launchpad.net --- Package information. --- Depends (Version) | Installed ==-+-=== xserver-xorg | 1:7.4+4 libgl1-mesa-glx| 7.5.1-1 OR libgl1 | libgl1-mesa-dri| 7.5.1-1 libglu1-mesa | 7.5.1-1 xfonts-base (= 1:1.0.0-1) | 1:1.0.0-6 xfonts-100dpi (= 1:1.0.0-1) | 1:1.0.0-4 xfonts-75dpi(= 1:1.0.0-1) | 1:1.0.0-4 xfonts-scalable (= 1:1.0.0-1) | 1:1.0.0-7 x11-apps | 7.4+2 x11-session-utils | 7.3+1 x11-utils | 7.4+1 x11-xfs-utils | 7.4+1 x11-xkb-utils | 7.4+3 x11-xserver-utils | 7.4+2 xauth | 1:1.0.3-2 xinit | 1.1.1-1 xfonts-utils | 1:7.4+2 xkb-data | 1.6-1 xorg-docs-core | 1:1.4-5 xterm | 246-1 OR x-terminal-emulator| Package's Recommends field is empty. Suggests (Version) | Installed -+-=== xorg-docs| 1:1.4-5 X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian Current Operating System: Linux belmer 2.6.30.090729 #1 PREEMPT Wed Jul 29 09:12:48 EDT 2009 i686 Build Date: 06 August 2009 04:49:57PM xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Mon Sep 14 09:21:49 2009 (==) Using config file: /etc/X11/xorg.conf (==) No Layout section.
Bug#523374: iscsitarget-source: FTBFS with 2.6.29
Hi! On Friday 11 September 2009 00:55:22 Michael Prokop wrote: [Cc-ing also Frederik Schüler who's in the uploader field of iscsitarget. Frederik, do you know anything about why Philipp doesn't react since more than 4 months?] I guess he might be busy with work... I've prepared a NMU package using a recent svn snapshot of upstream. Builds fine against 2.6.31 and package works for me. It's available at http://people.debian.org/~mika/nmu/iscsitarget/ What do you think how we should proceed? Please upload it. Best regards Frederik Schüler -- ENOSIG signature.asc Description: This is a digitally signed message part.
Bug#526579: elisa: diff for NMU version 0.3.5-3.1
On Mon, Sep 14, 2009 at 04:06:03PM +0200, Stefano Zacchiroli wrote:
The patch changes the CDBS hook at which register cleanup of upstream
files and namespace package registration; also, the patch ensures that
the cleanup is not executed more than once.
FWIW, I've checked also the experimental version and it is affected by
the very same problem. While the patch from the NMU will probably not
apply cleanly, the fix it's the same: change the CDBS target and use a
timestamp file for extra safety.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523692: Mixxx doesn't depend on glib
Mixxx doesn't depend on glib at the moment, according to one of the head developers. - This E-Mail message has been scanned for viruses and cleared by SmartMail from Smarter Technology, Inc. - -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535299: gambc: diff for NMU version 4.2.8-1.1
tags 535299 + pending
thanks
Dear maintainer,
I've prepared an NMU for gambc (versioned as 4.2.8-1.1) and uploaded it
to DELAYED/2, according to devref §5.11.1. The patch simply remove the
trailing backslash.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
diff -u gambc-4.2.8/debian/changelog gambc-4.2.8/debian/changelog
--- gambc-4.2.8/debian/changelog
+++ gambc-4.2.8/debian/changelog
@@ -1,3 +1,11 @@
+gambc (4.2.8-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove trailing backslash in debian/control, they are now forbidden
+and no longer needed. Patch from Cyril Brulebois. (Closes: #535299)
+
+ -- Stefano Zacchiroli z...@debian.org Mon, 14 Sep 2009 18:15:36 +0200
+
gambc (4.2.8-1) unstable; urgency=low
* New upstream release
diff -u gambc-4.2.8/debian/control gambc-4.2.8/debian/control
--- gambc-4.2.8/debian/control
+++ gambc-4.2.8/debian/control
@@ -11,7 +11,7 @@
Package: gambc
Architecture: any
-Depends: ${shlibs:Depends}, libgambc4 (= ${binary:Version}), \
+Depends: ${shlibs:Depends}, libgambc4 (= ${binary:Version}),
libgambc4-dev (= ${binary:Version})
Recommends: gambc-doc
Description: Gambit-C Scheme interpreter and compiler
Bug#533954: Pointers for fixing this
Hi Uwe, QA Team As I said earlier, this package suffers from more than one build problem, due to at least libtool2 and autoconf .63-64 transition. For the new libtool you need to pass -i to libtoolize for copying in config.* for the autotools issue a look at the recent lineakd fix (-5) by Barry should help. As for the undefined references stuff removing --no-undefined from at least ksimus-boolean/Makefile.am and potentially as well admin/acinclude.m4.in is a step forward and the symbols were unresolved for the version in the archive already so my assumption it is by design seems to be correct (it's intended to be used as a plugin). Regards Christoph -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : GPG 4096R : 0xD49AE731 X against HTML : Debian NM / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Bug#519330: [stellarium]: now I can launch it
Package: stellarium Version: 0.10.2-1 --- Please enter the report below this line. --- Hi, After last packages upgrading, stellarium can be launched again on my pc. If this also is true for Paul, the bug could be closed. Best Regards, Manolo --- System information. --- Architecture: amd64 Kernel: Linux 2.6.30 Debian Release: squeeze/sid 1001 testing ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libc6 (= 2.2.5) | 2.9-25 libfreetype6 (= 2.2.1) | 2.3.9-5 libgcc1 (= 1:4.1.1) | 1:4.4.1-1 libgl1-mesa-glx | 7.5.1-1 OR libgl1| libglu1-mesa | 7.5.1-1 OR libglu1 | libice6 (= 1:1.0.0) | 2:1.0.5-1 libjpeg62 | 6b-15 libpng12-0 (= 1.2.13-4) | 1.2.39-1 libqt4-network (= 4.4.3) | 4:4.5.2-2 libqt4-opengl (= 4.4.3) | 4:4.5.2-2 libqt4-script (= 4.4.3) | 4:4.5.2-2 libqtcore4 (= 4.4.3) | 4:4.5.2-2 libqtgui4 (= 4.4.3) | 4:4.5.2-2 libsm6| 2:1.1.1-1 libstdc++6 (= 4.1.1) | 4.4.1-1 libx11-6 | 2:1.2.2-1 libxext6 | 2:1.0.4-1 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-15 stellarium-data (= 0.10.2-1) | 0.10.2-1 Package's Recommends field is empty. Package's Suggests field is empty. -- Manolo Díaz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: elisa: diff for NMU version 0.3.5-3.1
Processing commands for cont...@bugs.debian.org: tags 526579 + patch pending Bug #526579 [elisa] elisa: FTBFS: cannot touch `/tmp/buildd/elisa-0.3.5/debian/tmp//usr/lib/python2.5/site-packages/elisa/__init__.py' Added tag(s) pending and patch. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523692: Current dependencies
An up-to-date list of dependencies can be found here: http://mixxx.org/wiki/doku.php/compiling_on_linux - This E-Mail message has been scanned for viruses and cleared by SmartMail from Smarter Technology, Inc. - -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 546609 is important, reassign 546609 to xserver-xorg-video-radeon
Processing commands for cont...@bugs.debian.org: severity 546609 important Bug #546609 [xserver-xorg] xserver-xorg: Blank screen if switching from vt7 to vt1 and back to vt7, after kdm login Severity set to 'important' from 'critical' reassign 546609 xserver-xorg-video-radeon Bug #546609 [xserver-xorg] xserver-xorg: Blank screen if switching from vt7 to vt1 and back to vt7, after kdm login Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-video-radeon'. Bug No longer marked as found in versions xorg/1:7.4+4. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: gambc: diff for NMU version 4.2.8-1.1
Processing commands for cont...@bugs.debian.org: tags 535299 + pending Bug #535299 [gambc] gambc: FTBFS with new dpkg-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526579: elisa: diff for NMU version 0.3.5-3.1
tags 526579 + patch pending
thanks
Dear maintainer,
I've prepared an NMU for elisa (versioned as 0.3.5-3.1) and uploaded it
to DELAYED/2, according to devref §5.11.1. The patch changes the CDBS
hook at which register cleanup of upstream files and namespace package
registration; also, the patch ensures that the cleanup is not executed
more than once.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
diff -u elisa-0.3.5/debian/changelog elisa-0.3.5/debian/changelog
--- elisa-0.3.5/debian/changelog
+++ elisa-0.3.5/debian/changelog
@@ -1,3 +1,11 @@
+elisa (0.3.5-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules: ensure upstream cleanup actions are executed after
+module files are installed in package build dir (Closes: #526579)
+
+ -- Stefano Zacchiroli z...@debian.org Mon, 14 Sep 2009 15:35:54 +0200
+
elisa (0.3.5-3) unstable; urgency=low
* Build-dep on python-pkg-resources and depend on both python-pkg-resources
diff -u elisa-0.3.5/debian/rules elisa-0.3.5/debian/rules
--- elisa-0.3.5/debian/rules
+++ elisa-0.3.5/debian/rules
@@ -11,6 +11,9 @@
-common-install-indep::
+binary-install/python-elisa:: upstream-cleanup-stamp
+upstream-cleanup-stamp:
rm -f $(DEB_DESTDIR)/usr/lib/python$(cdbs_python_current_version)/site-packages/*.pth
touch $(DEB_DESTDIR)/usr/lib/python$(cdbs_python_current_version)/site-packages/elisa/__init__.py
+ touch $@
clean::
-find . -name *\.mo -exec rm -fv {} \;
+ -rm -f upstream-cleanup-stamp
Bug#546285: python modules not in python search path
Plilipp, Thank you for the bug report. This is a known packaging bug in coherence. I am waiting on a new upstream release, which hopefully will be out sometime this week. If not I will go ahead and ask Arnaud to upload a fix for this. Best Regards Charlie Smotherman signature.asc Description: This is a digitally signed message part
Bug#546619: strace for hppa is critically broken
Package: strace
version: 4.5.18-1
Severity: grave
Architecture: hppa
Tags: Patch
Strace is *unusable* on hppa.
This bug supercedes bug #437928, updates the patches listed there, and
fixes the most recent issues.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437928
Problems:
* Traced process function descriptors are accessed causing faults.
* More than maximum number of syscall arguments accessed causing upeek failures.
* Missing syscalls.
* Incorrect processing of some IPC syscalls.
Please apply the attached patch to fix all of these issues.
It is critical that strace be fixed, the debian-porters are attempting
to track down buildd instability issues and without a working strace
this makes it difficult.
Cheers,
Carlos.
From: Carlos O'Donell car...@systemhalted.org
Miscellaneous hppa fixes
Add missing syscalls, handle IPC syscalls correctly,
avoid manipulationg function pointers, and handle
syscall arguments correctly.
This patch is based on work by Kyle McMartin and
Helge Deller.
* ipc.c (sys_shmat): hppa does not have a kernel
multiplexer for IPC.
* linux/hppa/syscallend.h: Add missing syscalls.
* signal.c (sys_sigaction): Avoid manipulating
function pointers.
(sys_rt_sigaction): Likewise.
Signed-off-by: Carlos O'Donell car...@systemhalted.org
---
diff -urN strace-4.5.18_orig/ipc.c strace-4.5.18/ipc.c
--- strace-4.5.18_orig/ipc.c 2007-01-15 15:25:52.0 -0500
+++ strace-4.5.18/ipc.c 2009-09-13 21:58:31.0 -0400
@@ -387,7 +387,8 @@
}
if (syserror(tcp))
return 0;
-#ifdef LINUX
+/* HPPA does not use an IPC multiplexer. */
+#ifdef LINUX !defined(HPPA)
if (umove(tcp, tcp-u_arg[2], raddr) 0)
return RVAL_NONE;
tcp-u_rval = raddr;
diff -urN strace-4.5.18_orig/linux/hppa/syscallent.h strace-4.5.18/linux/hppa/syscallent.h
--- strace-4.5.18_orig/linux/hppa/syscallent.h 2008-07-17 21:23:49.0 -0400
+++ strace-4.5.18/linux/hppa/syscallent.h 2009-09-13 22:06:20.0 -0400
@@ -197,10 +197,10 @@
{ 4, TI, sys_msgrcv, msgrcv }, /* 189 */
{ 4, TI, sys_msgget, msgget }, /* 190 */
{ 4, TI, sys_msgctl, msgctl }, /* 191 */
- { 4, TI, sys_shmat, shmat }, /* 192 */
- { 4, TI, sys_shmdt, shmdt }, /* 193 */
- { 4, TI, sys_shmget, shmget }, /* 194 */
- { 4, TI, sys_shmctl, shmctl }, /* 195 */
+ { 3, TI, sys_shmat, shmat }, /* 192 */
+ { 1, TI, sys_shmdt, shmdt }, /* 193 */
+ { 3, TI, sys_shmget, shmget }, /* 194 */
+ { 3, TI, sys_shmctl, shmctl }, /* 195 */
{ 5, 0, sys_getpmsg, getpmsg }, /* 196 */
{ 5, 0, sys_putpmsg, putpmsg }, /* 197 */
{ 2, TF, sys_lstat64, lstat64 }, /* 198 */
@@ -302,4 +302,25 @@
{ 4, TD, printargs, vmsplice }, /* 294 */
{ 6, 0, sys_move_pages, move_pages }, /* 295 */
{ 3, 0, sys_getcpu, getcpu }, /* 296 */
- { 5, TD, sys_epoll_pwait, epoll_pwait }, /* 297 */
+ { 6, TD, sys_epoll_pwait, epoll_pwait }, /* 297 */
+ { 3, TF, sys_statfs64, statfs64 }, /* 298 */
+ { 3, TD, sys_fstatfs64, fstatfs64 }, /* 299 */
+ { 4, 0, printargs, kexec_load }, /* 300 */
+ { 4, TD|TF, sys_utimensat, utimensat }, /* 301 */
+ { 3, TD, printargs, signalfd }, /* 302 */
+ { 4, TD, printargs, timerfd }, /* 303 */
+ { 1, TD, sys_eventfd, eventfd }, /* 304 */
+ { 6, TF, sys_fallocate, fallocate }, /* 305 */
+ { 2, TD, sys_timerfd_create, timerfd_create }, /* 306 */
+ { 4, TD, sys_timerfd_settime, timerfd_settime }, /* 307 */
+ { 2, TD, sys_timerfd_gettime, timerfd_gettime }, /* 308 */
+ { 4, TD|TS, printargs, signalfd4 }, /* 309 */
+ { 2, TD, printargs, eventfd2 }, /* 310 */
+ { 1, 0, printargs, epoll_create1 }, /* 311 */
+ { 3, TD, printargs, dup3 }, /* 312 */
+ { 2, TD, printargs, pipe2 }, /* 313 */
+ { 1, TD, printargs, inotify_init1 }, /* 314 */
+ { 5, TD, printargs, preadv }, /* 315 */
+ { 5, TD, printargs, pwritev }, /* 316 */
+ { 4, TP|TS, printargs, rt_tgsigqueueinfo }, /* 317 */
+ { 5, 0, printargs, perf_counter_open }, /* 318 */
diff -urN strace-4.5.18_orig/signal.c strace-4.5.18/signal.c
--- strace-4.5.18_orig/signal.c 2008-08-19 21:59:40.0 -0400
+++ strace-4.5.18/signal.c 2009-09-13 22:00:50.0 -0400
@@ -1120,11 +1120,19 @@
else if (umove(tcp, addr, sa) 0)
tprintf({...});
else {
- if (sa.SA_HANDLER == SIG_ERR)
+ /* Architectures using function pointers, like
+ * hppa, may need to manipulate the function pointer
+ * to compute the result of a comparison. However,
+ * the SA_HANDLER function pointer exists only in
+ * the address space of the traced process, and can't
+ * be manipulated by strace. In order to prevent the
+ * compiler from generating code to manipulate
+ * SA_HANDLER we cast the function pointers to long. */
+ if ((long)sa.SA_HANDLER == (long)SIG_ERR)
tprintf({SIG_ERR, );
- else if (sa.SA_HANDLER == SIG_DFL)
+ else if ((long)sa.SA_HANDLER == (long)SIG_DFL)
tprintf({SIG_DFL, );
- else if (sa.SA_HANDLER == SIG_DFL) {
+ else if ((long)sa.SA_HANDLER == (long)SIG_DFL) {
#ifndef USE_PROCFS
Bug#545720: marked as done (python-rpm: Always fails with ImportError: No module named _rpm)
Your message dated Mon, 14 Sep 2009 17:07:44 + with message-id e1mnf1k-0005w4...@ries.debian.org and subject line Bug#545720: fixed in rpm 4.7.1-5 has caused the Debian Bug report #545720, regarding python-rpm: Always fails with ImportError: No module named _rpm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 545720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-rpm Version: 4.7.0-9 Severity: grave Justification: renders package unusable The following simple test fails: $ python Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45) [GCC 4.3.3] on linux2 Type help, copyright, credits or license for more information. import rpm Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.5/site-packages/rpm/__init__.py, line 7, in module from _rpm import * ImportError: No module named _rpm -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-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/dash Versions of packages python-rpm depends on: ii libc6 2.9-25 GNU C Library: Shared libraries ii librpm0 4.7.0-9RPM shared library ii librpmbuild0 4.7.0-9RPM build shared library ii librpmio0 4.7.0-9RPM IO shared library ii python2.5.4-2An interactive high-level object-o ii python-support1.0.3 automated rebuilding support for P ii python2.4 2.4.6-2An interactive high-level object-o ii python2.5 2.5.4-1An interactive high-level object-o python-rpm recommends no packages. python-rpm suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: rpm Source-Version: 4.7.1-5 We believe that the bug you reported is fixed in the latest version of rpm, which is due to be installed in the Debian FTP archive: librpm-dbg_4.7.1-5_amd64.deb to pool/main/r/rpm/librpm-dbg_4.7.1-5_amd64.deb librpm-dev_4.7.1-5_amd64.deb to pool/main/r/rpm/librpm-dev_4.7.1-5_amd64.deb librpm0_4.7.1-5_amd64.deb to pool/main/r/rpm/librpm0_4.7.1-5_amd64.deb librpmbuild0_4.7.1-5_amd64.deb to pool/main/r/rpm/librpmbuild0_4.7.1-5_amd64.deb librpmio0_4.7.1-5_amd64.deb to pool/main/r/rpm/librpmio0_4.7.1-5_amd64.deb lsb-rpm_4.7.1-5_amd64.deb to pool/main/r/rpm/lsb-rpm_4.7.1-5_amd64.deb python-rpm_4.7.1-5_amd64.deb to pool/main/r/rpm/python-rpm_4.7.1-5_amd64.deb rpm-common_4.7.1-5_all.deb to pool/main/r/rpm/rpm-common_4.7.1-5_all.deb rpm-i18n_4.7.1-5_all.deb to pool/main/r/rpm/rpm-i18n_4.7.1-5_all.deb rpm2cpio_4.7.1-5_amd64.deb to pool/main/r/rpm/rpm2cpio_4.7.1-5_amd64.deb rpm_4.7.1-5.diff.gz to pool/main/r/rpm/rpm_4.7.1-5.diff.gz rpm_4.7.1-5.dsc to pool/main/r/rpm/rpm_4.7.1-5.dsc rpm_4.7.1-5_amd64.deb to pool/main/r/rpm/rpm_4.7.1-5_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 545...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michal Čihař ni...@debian.org (supplier of updated rpm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 14 Sep 2009 10:47:54 +0200 Source: rpm Binary: rpm rpm2cpio rpm-common rpm-i18n lsb-rpm librpm-dbg librpm0 librpmio0 librpmbuild0 librpm-dev python-rpm Architecture: source all amd64 Version: 4.7.1-5 Distribution: experimental Urgency: low Maintainer: Michal Čihař ni...@debian.org Changed-By: Michal Čihař ni...@debian.org Description: librpm-dbg - debugging symbols for RPM librpm-dev - RPM shared library, development kit librpm0- RPM shared library librpmbuild0 - RPM build shared library librpmio0 - RPM IO shared library lsb-rpm- RPM Package Manager for LSB package building python-rpm - Python bindings for RPM rpm- package manager for RPM rpm-common - common files for RPM rpm-i18n - localization and localized man pages for rpm rpm2cpio - tool to convert RPM package to CPIO archive
Bug#546547: 4.0-4 to 4.0-6 upgrade fails
By the way, here's what happens on a pure 4.0-4 to 4.0-6 upgrade: Preparing to replace bash 4.0-4 (using .../archives/bash_4.0-6_i386.deb) ... Unpacking replacement bash ... Processing triggers for install-info ... dpkg (subprocess): unable to execute installed post-installation script: No such file or directory dpkg: subprocess installed post-installation script returned error exit status 2 E: Sub-process /usr/bin/dpkg returned an error code (2) A package failed to install. Trying to recover: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. E: Could not regain the system lock! (Perhaps another apt or dpkg is running?) E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517060: marked as done (pythoncard: generates incorrect package with python-support in experimental)
Your message dated Mon, 14 Sep 2009 17:04:47 + with message-id e1mneyt-0005xg...@ries.debian.org and subject line Bug#517060: fixed in pythoncard 0.8.1-8.2 has caused the Debian Bug report #517060, regarding pythoncard: generates incorrect package with python-support in experimental to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 517060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517060 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pythoncard Version: 0.8.1-8.1 Hi, The wrapper scripts shipped in pythoncard look like the following: dir=/usr/share/python-support/python-pythoncard/PythonCard/tools/findfiles if [ -d $dir ]; then exec /usr/bin/python $dir/findfiles.py $@ With the upcoming version of python-support (currently in experimental), these scripts will stop working, since the files are now moved to a different directory (/usr/share/pyshared). The current package will still work, but as soon as it is rebuilt, the .deb produced will be non-functional. Since these scripts are installed into public modules directories, I suggest to use the following syntax instead: exec python -m PythonCard.tools.findfiles.findfiles This avoids to depend on the location of the installed scripts. As a general rule, please do not rely on the internals of python-support in the packaging; this will avoid such issues in the future (although hopefully there won’t be a need to change the paths any further). Thanks, -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `-me that if you don't install Lenny, he'd melt your brain. signature.asc Description: Ceci est une partie de message numériquement signée ---End Message--- ---BeginMessage--- Source: pythoncard Source-Version: 0.8.1-8.2 We believe that the bug you reported is fixed in the latest version of pythoncard, which is due to be installed in the Debian FTP archive: python-pythoncard_0.8.1-8.2_all.deb to pool/main/p/pythoncard/python-pythoncard_0.8.1-8.2_all.deb pythoncard-doc_0.8.1-8.2_all.deb to pool/main/p/pythoncard/pythoncard-doc_0.8.1-8.2_all.deb pythoncard-tools_0.8.1-8.2_all.deb to pool/main/p/pythoncard/pythoncard-tools_0.8.1-8.2_all.deb pythoncard_0.8.1-8.2.diff.gz to pool/main/p/pythoncard/pythoncard_0.8.1-8.2.diff.gz pythoncard_0.8.1-8.2.dsc to pool/main/p/pythoncard/pythoncard_0.8.1-8.2.dsc pythoncard_0.8.1-8.2_all.deb to pool/main/p/pythoncard/pythoncard_0.8.1-8.2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 517...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Falavigna dktrkr...@debian.org (supplier of updated pythoncard package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Sep 2009 17:39:58 +0200 Source: pythoncard Binary: pythoncard pythoncard-tools pythoncard-doc python-pythoncard Architecture: source all Version: 0.8.1-8.2 Distribution: unstable Urgency: low Maintainer: Ernesto Nadir Crespo Avila ecre...@debianvenezuela.org Changed-By: Luca Falavigna dktrkr...@debian.org Description: python-pythoncard - wxPython-based GUI construction framework (underlying Python libr pythoncard - wxPython-based GUI construction framework (meta-package) pythoncard-doc - wxPython-based GUI construction framework (documentation and samp pythoncard-tools - wxPython-based GUI construction framework (optional development t Closes: 517060 Changes: pythoncard (0.8.1-8.2) unstable; urgency=low . * Non-maintainer upload. * debian/findfiles, debian/codeEditor, debian/resourceEditor: - Do not rely on python-support internals, search for directories dynamically by looking at module path instead (Closes: #517060). Checksums-Sha1: 5601236e546aab84dd156ea14f7033316289004d 1158 pythoncard_0.8.1-8.2.dsc 81cffcda3403eafc4178b6776d7bb25d4bc3701a 10468 pythoncard_0.8.1-8.2.diff.gz 5a7974a22ca65542c454b065ba391e77f553c752 25496 pythoncard_0.8.1-8.2_all.deb b22523df7d2fbbf925a497da00c623f62f6be609 31278 pythoncard-tools_0.8.1-8.2_all.deb c9b83d05297fee9d2f805e275aead638c2ae0e18 968378 pythoncard-doc_0.8.1-8.2_all.deb 1484b1ec0cc40e96cc693a501c391e82b7e151c6
Bug#519330: marked as done (stellarium: Segfault just before creating GUI)
Your message dated Mon, 14 Sep 2009 19:49:55 +0200 with message-id 4aae8243.7090...@debian.org and subject line Re: Bug#519330: [stellarium]: now I can launch it has caused the Debian Bug report #519330, regarding stellarium: Segfault just before creating GUI to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 519330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: stellarium Version: 0.10.1-1 Severity: grave Hi, Reinstalling stellarium and stellarium-data after been purged or removing ~/.stellarium dir doesn't solve the problem. Previous version worked for me with no problem at all. Best Regards, Manolo Díaz - gdb output --- ~$ gdb stellarium GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (no debugging symbols found) (gdb) run Starting program: /usr/bin/stellarium [Thread debugging using libthread_db enabled] [New Thread 0x7f231e31f750 (LWP 6071)] [New Thread 0x7f2317250950 (LWP 6074)] --- [ This is Stellarium 0.10.1 - http://www.stellarium.org ] [ Copyright (C) 2000-2009 Fabien Chereau et al ] --- Writing log file to: /home/yo/.stellarium/log.txt File search paths: 0 . /home/yo/.stellarium 1 . /usr/share/stellarium Config file is: /home/yo/.stellarium/config.ini Sky language is es_ES Application language is es_ES Loading Solar System data ... Loaded 38 / 38 planet orbits Loading star data ... Loading stars_0_0v0_1.cat: 0_0v0_1; 5013 Loading stars_1_0v0_1.cat: 1_0v0_1; 21999 Loading stars_2_0v0_1.cat: 2_0v0_1; 151416 Loading stars_3_1v0_0.cat: 3_1v0_0; 434064 Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: 2.45151e+06 Loaded 10051 / 13226 NGC records Loading NGC name data ... Loaded 222 / 222 NGC name records successfully Loaded 88 / 88 constellation records successfully for culture western Loaded 85 / 85 constellation art records successfully for culture western Loaded 89 / 89 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Loading star names from /usr/share/stellarium/skycultures/western/star_names.fab Loaded 230 / 230 common star names Loading star names from /usr/share/stellarium/stars/default/name.fab Loaded 3215 / 4359 scientific star names Creating GUI ... [New Thread 0x7f230950 (LWP 6079)] [Thread 0x7f230950 (LWP 6079) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f231e31f750 (LWP 6071)] 0x7f231c1535a0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 (gdb) bt #0 0x7f231c1535a0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #1 0x7f231c15994f in ?? () from /usr/lib/libQtCore.so.4 #2 0x7f231c14dff3 in QObject::event () from /usr/lib/libQtCore.so.4 #3 0x7f231ce15a5d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #4 0x7f231ce1d7da in QApplication::notify () from /usr/lib/libQtGui.so.4 #5 0x7f231c13f391 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #6 0x7f231c16b266 in ?? () from /usr/lib/libQtCore.so.4 #7 0x7f231c1677bd in ?? () from /usr/lib/libQtCore.so.4 #8 0x7f2319919afb in IA__g_main_context_dispatch (context=0x2812520) at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2144 #9 0x7f231991d2bd in g_main_context_iterate (context=0x2812520, block=1, dispatch=1, self=value optimized out) at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2778 #10 0x7f231991d47b in IA__g_main_context_iteration (context=0x2812520, may_block=1) at /build/buildd/glib2.0-2.18.4/glib/gmain.c:2841 #11 0x7f231c16771f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #12 0x7f231cea747f in ?? () from /usr/lib/libQtGui.so.4 #13 0x7f231c13dcb2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #14 0x7f231c13de3d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #15 0x7f231c1402ed in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #16 0x00680436 in main () (gdb) quit --
Bug#523353: marked as done (stellarium: Segmentation fault while startup)
Your message dated Mon, 14 Sep 2009 19:49:20 +0200 with message-id 4aae8220.8060...@debian.org and subject line Re: Bug#523353: after upgrading xorg: no segfault anymore has caused the Debian Bug report #523353, regarding stellarium: Segmentation fault while startup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 523353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: stellarium Version: 0.10.2-1 Severity: grave Justification: renders package unusable The stellarium could not be startup. The ouput messages as follows, $ stellarium libGL error: open DRM failed (Operation not permitted) libGL error: reverting to (slow) indirect rendering --- [ This is Stellarium 0.10.2 - http://www.stellarium.org ] [ Copyright (C) 2000-2009 Fabien Chereau et al ] --- Writing log file to: /home/wgl/.stellarium/log.txt File search paths: 0 . /home/wgl/.stellarium 1 . /usr/share/stellarium Config file is: /home/wgl/.stellarium/config.ini Sky language is C Application language is C Loading Solar System data ... Loaded 38 / 38 planet orbits Loading star data ... Loading stars_0_0v0_1.cat: 0_0v0_1; 5013 Loading stars_1_0v0_1.cat: 1_0v0_1; 21999 Loading stars_2_0v0_1.cat: 2_0v0_1; 151416 Loading stars_3_1v0_0.cat: 3_1v0_0; 434064 Finished loading star catalogue data, max_geodesic_level: 3 navigation/preset_sky_time is a double - treating as jday: 2.45151e+06 Loaded 10051 / 13226 NGC records Loading NGC name data ... Loaded 222 / 222 NGC name records successfully Loaded 88 / 88 constellation records successfully for culture western Loaded 85 / 85 constellation art records successfully for culture western Loaded 89 / 89 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Loading star names from /usr/share/stellarium/skycultures/western/star_names.fab Loaded 230 / 230 common star names Loading star names from /usr/share/stellarium/stars/default/name.fab Loaded 3215 / 4359 scientific star names Creating GUI ... Segmentation fault Other opengl program worked fine on my debian, such as compiz, xserversaver-gl, etc. Only the stellarium runs failure. Thanks gulfstream -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-athena.1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages stellarium depends on: ii libc6 2.9-4 GNU C Library: Shared libraries ii libfreetype6 2.3.9-4 FreeType 2 font engine, shared lib ii libgcc11:4.3.3-3 GCC support library ii libgl1-mesa-glx [libgl 7.0.3-7 A free implementation of the OpenG ii libglu1-mesa [libglu1] 7.0.3-7 The OpenGL utility library (GLU) ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-0 1.2.35-1 PNG library - runtime ii libqt4-network 4.4.3-2 Qt 4 network module ii libqt4-opengl 4.4.3-2 Qt 4 OpenGL module ii libqt4-script 4.4.3-2 Qt 4 script module ii libqtcore4 4.4.3-2 Qt 4 core module ii libqtgui4 4.4.3-2 Qt 4 GUI module ii libsm6 2:1.1.0-2 X11 Session Management library ii libstdc++6 4.3.3-3 The GNU Standard C++ Library v3 ii libx11-6 2:1.2-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii stellarium-data0.10.2-1 datafiles for Stellarium, a real-t ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime stellarium recommends no packages. stellarium suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Andreas B. Mundt wrote: Hi, after the latest upgrade of xorg to version 1:7.4+4, stellarium works fine again on my machine (squeeze). I guess this bug can be closed. Ok, closing this bug. Cheers Luk ---End Message---
Bug#546629: nginx_0.6.32-3+lenny2_i386 uninstallable because of libpcre3 (= 7.7)
Package: nginx Version: 0.6.32-3+lenny2 Severity: grave Justification: renders package unusable Security release of nginx on i386 is uninstallable (amd64 is ok on the 64-bit machines I have) mshu...@linode:~$ apt-cache policy nginx nginx: Installed: 0.6.32-3 Candidate: 0.6.32-3+lenny2 Version table: 0.6.32-3+lenny2 0 900 http://security.debian.org lenny/updates/main Packages *** 0.6.32-3 0 900 http://ftp.us.debian.org lenny/main Packages 100 /var/lib/dpkg/status mshu...@linode:~$ sudo apt-get install nginx=0.6.32-3+lenny2 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nginx: Depends: libpcre3 (= 7.7) but 7.6-2.1 is to be installed E: Broken packages Thanks, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545910: updating to grub-pc fails to boot memtest+
On Thursday 10 September 2009, Felix Zielcke wrote: Am Mittwoch, den 09.09.2009, 19:20 -0400 schrieb Chris Knadle: ... If I understand you correctly, you're saying that booting Memtest86+ using a linux method _should_ work but doesn't because of a problem with Memtest86+ itself? Without any underlying reasoning it makes it seem like reassigning the bug to Memtest86+ may not be fitting; bug #539907 concerns not being able to boot Memtest86+ from grub2 (the same code as grub-pc), so how can we know that this isn't a problem with grub2/grub-pc? The /etc/grub.d/memtest86+ must use the linux16 command now. and that file is provides by the memtest86+ package, not at all by the grub2 ones. It's impossible to load it with the linux command. memtest86+.bin doestn't provide the 32bit booting protocol recent Linux kernels have. It even still uses zImage format and not the bzImage one, which was introduced with kernel 1.3.73. The changelog for the current Debian grub-pc package has an interesting entry: grub2 (1.95+20080105-1) ... - Fixes boot of Linux zImages (including memtest86+). (Closes: 436113) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436113 So last year grub-pc could boot memtest86+ zImage using the Linux command, but today it can't. :-/ Or they could just implement multiboot, but then the linux command needs to be changed to multiboot. Robert provided a patch though for memtest86 without + to implement multiboot. As I already said in my grub-devel mail: zImage doesn't suppoert 32-bit boot (try with linux16) grub tells you. Use linux16 /memtest86+-2.11.bin Is it possible to have grub-pc expect to use the linux16 command to boot memtest86+ in /etc/grub.d/20_memtest86+ by default? -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: downgrading severity
Processing commands for cont...@bugs.debian.org: # on second thoughts, these aren't RC before 5.10.1 is in sid severity 546221 important Bug #546221 [libxray-absorption-perl] libxray-absorption-perl: FTBFS with newer Test::Harness Severity set to 'important' from 'serious' severity 546224 important Bug #546224 [libemail-mime-createhtml-perl] libemail-mime-createhtml-perl: FTBFS with newer Pod::Simple Severity set to 'important' from 'serious' severity 546225 important Bug #546225 [libalien-wxwidgets-perl] libalien-wxwidgets-perl: FTBFS with newer Module::Build Severity set to 'important' from 'serious' severity 546226 important Bug #546226 [libclass-dbi-mysql-perl] libclass-dbi-mysql-perl: FTBFS with newer Test::Simple Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545910: updating to grub-pc fails to boot memtest+
Am Montag, den 14.09.2009, 14:09 -0400 schrieb Chris Knadle: On Thursday 10 September 2009, Felix Zielcke wrote: Am Mittwoch, den 09.09.2009, 19:20 -0400 schrieb Chris Knadle: ... If I understand you correctly, you're saying that booting Memtest86+ using a linux method _should_ work but doesn't because of a problem with Memtest86+ itself? Without any underlying reasoning it makes it seem like reassigning the bug to Memtest86+ may not be fitting; bug #539907 concerns not being able to boot Memtest86+ from grub2 (the same code as grub-pc), so how can we know that this isn't a problem with grub2/grub-pc? The /etc/grub.d/memtest86+ must use the linux16 command now. and that file is provides by the memtest86+ package, not at all by the grub2 ones. It's impossible to load it with the linux command. memtest86+.bin doestn't provide the 32bit booting protocol recent Linux kernels have. It even still uses zImage format and not the bzImage one, which was introduced with kernel 1.3.73. The changelog for the current Debian grub-pc package has an interesting entry: grub2 (1.95+20080105-1) ... - Fixes boot of Linux zImages (including memtest86+). (Closes: 436113) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436113 So last year grub-pc could boot memtest86+ zImage using the Linux command, but today it can't. :-/ 1.96+20090627-1 * patches/906_revert_to_linux16.diff: Remove, now that gfxpayload is supported. 1.96+20090523-1 * patches/906_revert_to_linux16.diff: Keep using linux16 for now. Upstream changed the default linux loader from the initial 16 bit one to a 32bit one which is also used with EFI and Coreboot. linux16 is the old loader that was since the beginning of grub2 there. Ok the upstream Changelog entry about this change isn't that clear for people not used to the GNU ChangeLog style. Or they could just implement multiboot, but then the linux command needs to be changed to multiboot. Robert provided a patch though for memtest86 without + to implement multiboot. As I already said in my grub-devel mail: zImage doesn't suppoert 32-bit boot (try with linux16) grub tells you. Use linux16 /memtest86+-2.11.bin Is it possible to have grub-pc expect to use the linux16 command to boot memtest86+ in /etc/grub.d/20_memtest86+ by default? What do you mean with that? We want to have that the memtest86(+) packages change their grub.d files to use linux16. Or do you want to suggest we edit their files for them? Well that would be a clear Debian policy violation. -- Felix Zielcke Proud Debian Maintainer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546635: xapian-bindings - FTBFS: /bin/sh: line 0: .: libtoolconfig.tmp: file not found
Source: xapian-bindings Version: 1.0.16-1 Severity: serious There was an error while trying to autobuild your package: sbuild (Debian sbuild) 0.58.2 (31 Jul 2009) on debian-31.osdl.marist.edu [...] /bin/sh ../libtool --tag=CXX --mode=link g++ -fno-strict-aliasing -Wall -Wno-unused -Wno-uninitialized -fvisibility=hidden -O2 -avoid-version -module -shrext .so -o _xapian.la -rpath /usr/lib/python2.4/site-packages xapian_wrap.lo -lxapian -lstdc++ g++ -shared -nostdlib /usr/lib/gcc/s390-linux-gnu/4.3.4/../../../../lib/crti.o /usr/lib/gcc/s390-linux-gnu/4.3.4/crtbeginS.o .libs/xapian_wrap.o /usr/lib/libxapian.so -L/usr/lib/gcc/s390-linux-gnu/4.3.4 -L/usr/lib/gcc/s390-linux-gnu/4.3.4/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/s390-linux-gnu/4.3.4/../../.. -L/usr/lib/s390-linux-gnu -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/s390-linux-gnu/4.3.4/crtendS.o /usr/lib/gcc/s390-linux-gnu/4.3.4/../../../../lib/crtn.o -Wl,-soname -Wl,_xapian.so -o .libs/_xapian.so creating _xapian.la (cd .libs rm -f _xapian.la ln -s ../_xapian.la _xapian.la) cp `test -f modern/xapian.py || echo '../../python/'`modern/xapian.py . /bin/sh ../libtool --config libtoolconfig.tmp . libtoolconfig.tmp; cp $objdir/_xapian.so . /bin/sh: line 0: .: libtoolconfig.tmp: file not found cp: cannot stat `/_xapian.so': No such file or directory make[5]: *** [_xapian.so] Error 1 make[4]: *** [all-recursive] Error 1 make[5]: Leaving directory `/build/buildd-xapian-bindings_1.0.16-1-s390-A3cFtx/xapian-bindings-1.0.16/build-python2.4/python' make[4]: Leaving directory `/build/buildd-xapian-bindings_1.0.16-1-s390-A3cFtx/xapian-bindings-1.0.16/build-python2.4/python' make[3]: *** [all] Error 2 make[2]: *** [all-recursive] Error 1 make[3]: Leaving directory `/build/buildd-xapian-bindings_1.0.16-1-s390-A3cFtx/xapian-bindings-1.0.16/build-python2.4/python' make[2]: Leaving directory `/build/buildd-xapian-bindings_1.0.16-1-s390-A3cFtx/xapian-bindings-1.0.16/build-python2.4' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd-xapian-bindings_1.0.16-1-s390-A3cFtx/xapian-bindings-1.0.16/build-python2.4' make: *** [debian/build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546336: Misses the glade file used to generate interface.{h,c}
So, you mean that to edit the interface you now normally hand-edit the glade-generated files? Effectively yes. Basically it is a copy and paste job. Parasite (a GTK firebug) is very useful. At one point or other this needs re-engineering. I had already planned to do this during my summer vacation but then I got an Arduino board and some other gadgets and my vacation was over before I started developing on tangogps. But hey, it is not the worst part of the code and actually the part where I find the quickest what I look for. Regards, Marcus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522313: WIP
Heya all! Just changing the dependency from liburl3-openssl-dev to libcurl4-gnutls-dev seems to produce a equally well binary without this problem. However I'm currently considering using the new upstream release for this QA upload (package is orphaned but not maintainer qa-team, will be changed on the way). Regards Christoph -- /\ ASCII Ribbon : GPG-Key ID: 0x0372275D \ /Campaign : GPG 4096R : 0xD49AE731 X against HTML : Debian NM / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ signature.asc Description: Digital signature
Bug#545910: updating to grub-pc fails to boot memtest+
On Monday 14 September 2009, Felix Zielcke wrote: Am Montag, den 14.09.2009, 14:09 -0400 schrieb Chris Knadle: ... Is it possible to have grub-pc expect to use the linux16 command to boot memtest86+ in /etc/grub.d/20_memtest86+ by default? What do you mean with that? We want to have that the memtest86(+) packages change their grub.d files to use linux16. Or do you want to suggest we edit their files for them? Well that would be a clear Debian policy violation. Ah that's my mistake -- I didn't realize /etc/grub.d/20_memtest86+ was part of the memtest86+ package. Now I finally understand why this is a memtest86+ bug. Thanks very much. -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516358: marked as done (python-dmidecode-dbg: tries to overwrite file owned by python-dmidecode)
Your message dated Mon, 14 Sep 2009 21:47:32 +0200 with message-id 20090914194732.gb4...@free.fr and subject line Re: python-dmidecode-dbg: tries to overwrite file owned by python-dmidecode has caused the Debian Bug report #516358, regarding python-dmidecode-dbg: tries to overwrite file owned by python-dmidecode to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 516358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python-dmidecode-dbg Version: 2.10.2-1 Severity: serious Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Date: 2009-02-20 Architecture: amd64 Distribution: sid Command: apt-get --assume-yes --allow-unauthenticated install python-dmidecode python-dmidecode-dbg Reading package lists... Building dependency tree... The following extra packages will be installed: libdb4.5 libsqlite3-0 mime-support python python-central python-dbg python-minimal python2.5 python2.5-dbg python2.5-minimal Suggested packages: python-doc python-tk python-profiler python2.5-doc python-gdbm-dbg python-tk-dbg binfmt-support Recommended packages: file The following NEW packages will be installed: libdb4.5 libsqlite3-0 mime-support python python-central python-dbg python-dmidecode python-dmidecode-dbg python-minimal python2.5 python2.5-dbg python2.5-minimal 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 13.6MB of archives. After this operation, 46.3MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! libdb4.5 libsqlite3-0 mime-support python2.5-minimal python2.5 python-minimal python python-central python-dmidecode python2.5-dbg python-dbg python-dmidecode-dbg Authentication warning overridden. Get:1 http://localhost sid/main libdb4.5 4.5.20-13 [555kB] Get:2 http://localhost sid/main libsqlite3-0 3.5.9-6 [253kB] Get:3 http://localhost sid/main mime-support 3.44-1 [33.3kB] Get:4 http://localhost sid/main python2.5-minimal 2.5.4-1 [1290kB] Get:5 http://localhost sid/main python2.5 2.5.4-1 [3041kB] Get:6 http://localhost sid/main python-minimal 2.5.2-3 [13.5kB] Get:7 http://localhost sid/main python 2.5.2-3 [139kB] Get:8 http://localhost sid/main python-central 0.6.8 [40.4kB] Get:9 http://localhost sid/main python-dmidecode 2.10.2-1 [94.0kB] Get:10 http://localhost sid/main python2.5-dbg 2.5.4-1 [8068kB] Get:11 http://localhost sid/main python-dbg 2.5.2-3 [986B] Get:12 http://localhost sid/main python-dmidecode-dbg 2.10.2-1 [100.0kB] Fetched 13.6MB in 16s (832kB/s) Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libdb4.5. (Reading database ... 7976 files and directories currently installed.) Unpacking libdb4.5 (from .../libdb4.5_4.5.20-13_amd64.deb) ... Selecting previously deselected package libsqlite3-0. Unpacking libsqlite3-0 (from .../libsqlite3-0_3.5.9-6_amd64.deb) ... Selecting previously deselected package mime-support. Unpacking mime-support (from .../mime-support_3.44-1_all.deb) ... Selecting previously deselected package python2.5-minimal. Unpacking python2.5-minimal (from .../python2.5-minimal_2.5.4-1_amd64.deb) ... Selecting previously deselected package python2.5. Unpacking python2.5 (from .../python2.5_2.5.4-1_amd64.deb) ... Selecting previously deselected package python-minimal. Unpacking python-minimal (from .../python-minimal_2.5.2-3_all.deb) ... Selecting previously deselected package python. Unpacking python (from .../python_2.5.2-3_all.deb) ... Selecting previously deselected package python-central. Unpacking python-central (from .../python-central_0.6.8_all.deb) ... Selecting previously deselected package python-dmidecode. Unpacking python-dmidecode (from .../python-dmidecode_2.10.2-1_amd64.deb) ... Selecting previously deselected package python2.5-dbg. Unpacking python2.5-dbg (from .../python2.5-dbg_2.5.4-1_amd64.deb) ... Selecting previously deselected package python-dbg. Unpacking python-dbg (from .../python-dbg_2.5.2-3_all.deb) ... Selecting previously deselected package python-dmidecode-dbg. Unpacking python-dmidecode-dbg (from .../python-dmidecode-dbg_2.10.2-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python-dmidecode-dbg_2.10.2-1_amd64.deb (--unpack): trying to overwrite `/usr/share/pyshared/dmidecode-2.10.2.egg-info', which is also in package python-dmidecode Processing triggers for man-db ... Errors were
Bug#546032: libjgrapht0.6-java-doc and libjgrapht-java-doc: error , when trying to install together
On Sat, Sep 12, 2009 at 5:12 PM, Niels Thykier ni...@thykier.net wrote: Shouldn't the libjgrapht0.6 then have the Replaces entry in the control file? No, the old package should get removed. Steffen filed the removal request #546040 and it will be removed as soon as the ftp team finds the time. Cheers, Torsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545616: libgtk2-perl: FTBFS: tests failed
Hi, I tried to reproduce in C, what the script does in Perl. The problem is (or seems to be) (in both cases), that the path returned by get_cursor() (gtk_tree_view_get_cursor) is NULL for some reason and this seems to fail in libgtk2-perl. I sent a mail to the gtk-app-devel list. Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546032: libjgrapht0.6-java-doc and libjgrapht-java-doc: error , when trying to install together
On Mon, Sep 14, 2009 at 10:01:04PM +0200, Torsten Werner wrote: On Sat, Sep 12, 2009 at 5:12 PM, Niels Thykier ni...@thykier.net wrote: Shouldn't the libjgrapht0.6 then have the Replaces entry in the control file? No, the old package should get removed. Steffen filed the removal request #546040 and it will be removed as soon as the ftp team finds the time. And what about people who have the old package already installed? A Replaces helps them and is needed in this case afaik. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 543351 to logilab-common, tagging 543351
Processing commands for cont...@bugs.debian.org: reassign 543351 logilab-common Bug #543351 [python-logilab-astng] logilab.astng cannot be imported after upgrade from stable Bug reassigned from package 'python-logilab-astng' to 'logilab-common'. Bug No longer marked as found in versions logilab-astng/0.19.0-2. tags 543351 pending Bug #543351 [logilab-common] logilab.astng cannot be imported after upgrade from stable Ignoring request to alter tags of bug #543351 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 543351 + pending Bug #543351 [python-logilab-astng] logilab.astng cannot be imported after upgrade from stable Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520189: marked as done (nspluginwrapper does not work on kernel 2.6.26)
Your message dated Mon, 14 Sep 2009 21:42:22 +0100 with message-id 20090914204222.ga9...@horizon.aphlor.org and subject line Re: Bug#520189: Working now after purging 'flashplayer-mozilla' has caused the Debian Bug report #520189, regarding nspluginwrapper does not work on kernel 2.6.26 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 520189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nspluginwrapper Version: 1.3.0-1 Severity: serious nspluginwrapper currently does not work at all on my system; I believe this has to do with a kernel 2.6.27-specific flag passed to socket() now, but I'm not entirely sure. This is especially bad given that the default kernel in both squeeze and sid is 2.6.26, but this package should work regardless of the particular 2.6 kernel version. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core) 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 nspluginwrapper depends on: ii debconf 1.5.26 Debian configuration management sy ii ia32-libs2.7 ia32 shared libraries for use on a ii ia32-libs-gtk2.7 GTK+ ia32 shared libraries ii lib32gcc11:4.3.3-3 GCC support library (32 bit Versio ii libatk1.0-0 1.22.0-1The ATK accessibility toolkit ii libc62.9-4 GNU C Library: Shared libraries ii libc6-i386 2.9-4 GNU C Library: 32bit shared librar ii libcairo21.8.6-2 The Cairo 2D vector graphics libra ii libcurl3-gnutls 7.18.2-8.1 Multi-protocol file transfer libra ii libglib2.0-0 2.18.4-2The GLib library of C routines ii libgtk2.0-0 2.14.7-4+b1 The GTK+ graphical user interface ii libpango1.0-01.22.4-2Layout and rendering of internatio ii libx11-6 2:1.1.5-2 X11 client-side library ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii util-linux [linux32] 2.13.1.1-1 Miscellaneous system utilities nspluginwrapper recommends no packages. nspluginwrapper suggests no packages. -- debconf information: * nspluginwrapper/auto_update: true ---End Message--- ---BeginMessage--- On 25-Aug-2009 20:56.24 (BST), Dominique Brazziel wrote: Had to manually delete old flash plugin from user directories and reinstall 'nspluginwrapper' and 'flashplugin-nonfree'. Apologies, have been busy getting married and being on honeymoon. It looks like at some point in the past, the plugin loader stub hasn't been updated. This is possibly down to debconf settings - I'd advise turning on automatic stub updating for globally installed plugins. Try: dpkg-reconfigure nspluginwrapper And answer yes to the debconf question. I'll close this bug, but please feel free to reopen if this bug resurfaces. Kind regards, rob. -- rob andrews :: pgp 0xd6c3e484 :: r...@choralone.org ---End Message---
Bug#520189: Working now after purging 'flashplayer-mozilla'
On 25-Aug-2009 20:56.24 (BST), Dominique Brazziel wrote: Had to manually delete old flash plugin from user directories and reinstall 'nspluginwrapper' and 'flashplugin-nonfree'. Apologies, have been busy getting married and being on honeymoon. It looks like at some point in the past, the plugin loader stub hasn't been updated. This is possibly down to debconf settings - I'd advise turning on automatic stub updating for globally installed plugins. Try: dpkg-reconfigure nspluginwrapper And answer yes to the debconf question. I'll close this bug, but please feel free to reopen if this bug resurfaces. Kind regards, rob. -- rob andrews :: pgp 0xd6c3e484 :: r...@choralone.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546032: libjgrapht0.6-java-doc and libjgrapht-java-doc: error , when trying to install together
On Mon, Sep 14, 2009 at 10:25 PM, Michael Koch konque...@gmx.de wrote: And what about people who have the old package already installed? A Replaces helps them and is needed in this case afaik. A Replaces won't hurt but I am not sure if it is really needed. Cheers, Torsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tag 546487 + pending Bug #546487 [logilab-common] New upstream version available Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 543661 is normal, retitle 543661 to fix some lintian issues
Processing commands for cont...@bugs.debian.org: severity 543661 normal Bug #543661 [gpr] FTBFS: build-depends cannot be met in Squeeze Severity set to 'normal' from 'serious' retitle 543661 fix some lintian issues Bug #543661 [gpr] FTBFS: build-depends cannot be met in Squeeze Changed Bug title to 'fix some lintian issues' from 'FTBFS: build-depends cannot be met in Squeeze' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546032: libjgrapht0.6-java-doc and libjgrapht-java-doc: error , when trying to install together
On Mon, Sep 14, 2009 at 10:43:57PM +0200, Torsten Werner wrote: On Mon, Sep 14, 2009 at 10:25 PM, Michael Koch konque...@gmx.de wrote: And what about people who have the old package already installed? A Replaces helps them and is needed in this case afaik. A Replaces won't hurt but I am not sure if it is really needed. It help apt-get/aptitude to make smarter decisions on dist-upgrades. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: bash execution trace
Hi there Michael and others.
(Please, keep me CC'ed)
On Aug 29 2009, Michael Gold wrote:
I added set -x to the beginning of the console-setup.config script,
and executed console-setup.config configure. The output is
attached.
Nice. I just did the same thing.
Searching for starting_state shows that the script gets stuck
switching between states 3 and 4, but I haven't figured out what this
code is trying to do.
I am too lazy to read what the code is trying to do (I'm actually
installing the -mini version), but I saw that it was looking for
xorg.conf and I moved it out of the way, dpkg -i console-blablah and
it installed.
Now, one thing to see is if all the people having this very serious
problem have any X configuration file or if they are starting with a
non-existent X config.
Please, let us know.
Regards, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#520189 closed by Rob Andrews r...@choralone.org (Re: Bug#520189: Working now after purging 'flashplayer-mozilla')
Processing commands for cont...@bugs.debian.org:
reopen 520189
Bug #520189 {Done: Rob Andrews r...@choralone.org} [nspluginwrapper]
nspluginwrapper does not work on kernel 2.6.26
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520189: closed by Rob Andrews r...@choralone.org (Re: Bug#520189: Working now after purging 'flashplayer-mozilla')
reopen 520189 thanks On Mon, 2009-09-14 at 20:51 +, Debian Bug Tracking System wrote: It looks like at some point in the past, the plugin loader stub hasn't been updated. This is possibly down to debconf settings - I'd advise turning on automatic stub updating for globally installed plugins. Try: dpkg-reconfigure nspluginwrapper And answer yes to the debconf question. I'll close this bug, but please feel free to reopen if this bug resurfaces. Er, that's not what this bug is about. It's about the flag passed to socket() that is only present on Linux kernels 2.6.27 and above, which is checked at compile-time instead of run-time. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 526522 with 545663
Processing commands for cont...@bugs.debian.org: block 526522 with 545663 Bug #526522 [ldaptor-utils] ldaptor-utils: ldaptor-ldap2passwd --help throws exception Was blocked by: 538309 530480 Added blocking bug(s) of 526522: 545663 End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: console-setup cannot be configured
I cannot install console-setup 1.45. dpkg --configure console-setup always hangs after I have entered the country of origin of my keyboard, no matter what I choose. The subprocess /var/lib/dpkg/info/console-setup.config configure seems to be in a loop, while frontend and console-setup.c use 18% of CPU. Regards, Martin PS: I run debian testing on a thinkpad R60 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: Info received (bash execution trace)
OK, now that I just sent the workaround in the earlier message, I dug in
a little further.
The problem seems to be related to the embedded awk script in the
configure script of the package.
In its stock version, when fed with my x configuration file, it prints
nothing.
When I change
,
| bin {
| $0 = tolower($0);
| sub(#.*,)
| xkb = ;
| }
`
to
,
| BEGIN {
| xkb = ;
| }
|
| {
| $0 = tolower($0);
| sub(#.*,)
| if ($0 != ) {
| print *** DEBUG: Line read: $0
| }
| }
`
I get the output attached.
I sincerely don't remember if bin is a particular expression in AWK
(it's been way more than a decade since I last wrote anything in AWK)
but I guess that it was meant to be BEGIN (if I am guessing it right).
If my guess is correct, then just normalizing the first line to be
lowercase does not seem correct and what I wrote above seems to be
better, but not good enough:
The script does not understand when the section containing the keyboard
has finished and, thus, it also gets the settings for the mouse and
interprets them as the settings for the keyboard also (which is not
always the right thing).
I will continue this bug-hunting here, but it seems to be coming to an
end. :-)
Regards, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
*** DEBUG: Line read: section inputdevice
*** DEBUG: Line read: identifier generic keyboard
*** DEBUG: Line read: driver kbd
*** DEBUG: Line read: option xkbrules xorg
*** DEBUG: Line read: option xkbmodel pc104
XKBMODEL=pc104
*** DEBUG: Line read: option xkblayout us_intl
layout_priority=medium
XKBLAYOUT=us_intl
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section inputdevice
*** DEBUG: Line read: identifier configured mouse
*** DEBUG: Line read: driver mouse
*** DEBUG: Line read: option protocol auto
XKBLAYOUT=auto
*** DEBUG: Line read: option device
/dev/input/mice
XKBLAYOUT=/dev/input/mice
*** DEBUG: Line read: option zaxismapping 4 5 6 7
XKBLAYOUT=4567
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section module
*** DEBUG: Line read: loadglcore
*** DEBUG: Line read: loadbitmap
*** DEBUG: Line read: loaddbe
*** DEBUG: Line read: loadddc
*** DEBUG: Line read: loaddri
*** DEBUG: Line read: loaddri2
*** DEBUG: Line read: loadextmod
*** DEBUG: Line read: loadfreetype
*** DEBUG: Line read: loadglx
*** DEBUG: Line read: loadrecord
*** DEBUG: Line read: loadspeedo
*** DEBUG: Line read: loadtype1
*** DEBUG: Line read: loadvbe
*** DEBUG: Line read: loadxv
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section device
*** DEBUG: Line read: identifier configured video device
*** DEBUG: Line read: driver intel
*** DEBUG: Line read: option agpmode 4
*** DEBUG: Line read: option agpfastwrite on
*** DEBUG: Line read: option renderaccel true
*** DEBUG: Line read: option accelmethod uxa
*** DEBUG: Line read: option xvmc true
*** DEBUG: Line read: option xvmcsurfaces 6
*** DEBUG: Line read: option dri true
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section monitor
*** DEBUG: Line read: identifier configured monitor
*** DEBUG: Line read: option dmps
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section screen
*** DEBUG: Line read: identifier default screen
*** DEBUG: Line read: monitor configured monitor
*** DEBUG: Line read: device configured video device
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section serverlayout
*** DEBUG: Line read: identifier x.org configured
*** DEBUG: Line read: screen default screen
*** DEBUG: Line read: inputdevice generic keyboard
corekeyboard
*** DEBUG: Line read: inputdevice configured mouse
corepointer
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section serverflags
*** DEBUG: Line read: option dontzap false
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section dri
*** DEBUG: Line read: mode0666
*** DEBUG: Line read: endsection
*** DEBUG: Line read: section extensions
*** DEBUG: Line read: option composite 1
*** DEBUG: Line read: option
Bug#536683: bash execution trace
Am Mon, 14 Sep 2009 17:59:11 -0300 schrieb Rogério Brito rbr...@ime.usp.br: Now, one thing to see is if all the people having this very serious problem have any X configuration file or if they are starting with a non-existent X config. Please, let us know. Hi! I'm suffering from that problem too (testing/unstable system). I have a Xorg config: Section ServerFlags Option DontZap false EndSection Section Device Identifier Configured Video Device Driver radeon Option monitor-DVI-1 17Zoll Option monitor-DVI-0 22Zoll #Option DefaultConnectorTable true Option ForceLowPowerMode true EndSection Section Monitor Identifier 22Zoll Option PreferredMode 1680x1050 EndSection Section Monitor Identifier 17Zoll Option PreferredMode 1280x1024 Option RightOf 22Zoll EndSection Section Screen Identifier Default Screen Monitor 22Zoll Device Configured Video Device SubSection Display Virtual 2960 1050 EndSubSection EndSection And here is my console setup: VERBOSE_OUTPUT=no ACTIVE_CONSOLES=/dev/tty[1-6] CHARMAP=UTF-8 CODESET=Lat15 FONTFACE=Fixed FONTSIZE=16 XKBMODEL=pc105 XKBLAYOUT=de,ru(phonetic) XKBVARIANT=nodeadkeys XKBOPTIONS=lv3:ralt_switch,grp:shifts_toggle I hope this helps... Best regards, Andreas signature.asc Description: PGP signature
Bug#501207: destar: python-quixote1 never upgraded in lenny?
Package: destar Version: 0.2.2-5.2 Followup-For: Bug #501207 Hi. I have the identical traceback as the original reporter. It looks like python-quixote1 1.2-4.1 never made it into stable, so destar is still unusable? -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages destar depends on: ii asterisk 1:1.4.21.2~dfsg-3 Open Source Private Branch Exchang ii debconf1.5.24Debian configuration management sy ii python 2.5.2-3 An interactive high-level object-o ii python-medusa 0.5.4+clean-2 Framework for implementing asynchr ii python-pychart 1.39-6Python library for creating high q ii python-pysqlite2 2.4.1-1 Python interface to SQLite 3 ii python-quixote11.2-4+b1 A highly Pythonic Web application ii sqlite33.5.9-6 A command line interface for SQLit Versions of packages destar recommends: pn op-panel none (no description available) destar suggests no packages. -- debconf information: destar/port: 8080 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501207: confirmed: upgrading to python-quixote1_1.2-4.1 (from squeeze) fixes the bug
Package: destar Followup-For: Bug #501207 upgrading to python-quixote1_1.2-4.1 (from squeeze) fixes the bug. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages destar depends on: ii asterisk 1:1.4.21.2~dfsg-3 Open Source Private Branch Exchang ii debconf1.5.24Debian configuration management sy ii python 2.5.2-3 An interactive high-level object-o ii python-medusa 0.5.4+clean-2 Framework for implementing asynchr ii python-pychart 1.39-6Python library for creating high q ii python-pysqlite2 2.4.1-1 Python interface to SQLite 3 ii python-quixote11.2-4.1 A highly Pythonic Web application ii sqlite33.5.9-6 A command line interface for SQLit Versions of packages destar recommends: pn op-panel none (no description available) destar suggests no packages. -- debconf information: destar/port: 8080 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: bash execution trace
Hi, Andreas.
On Sep 14 2009, Andreas Juch wrote:
Am Mon, 14 Sep 2009 17:59:11 -0300
schrieb Rogério Brito rbr...@ime.usp.br:
Please, let us know.
Hi!
I'm suffering from that problem too (testing/unstable system).
Right.
I have a Xorg config:
(...)
Thanks, this seems to be like a confirmation of my suspicion.
I hope this helps...
Nice.
Can you see if the problem goes away if you move your xorg config file
to another name, just before installing/upgrading/whatever
console-setup?
(You may want to backup your already existing console-setup
configuration just for the purpose of the test).
P.S.: Please, keep me at least in the Carbon Copies.
Regards,
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546665: l7-protocols: overwrites user configuration files
Package: l7-protocols Version: 20090528-1 Severity: serious Justification: Policy 10.8.3 l7-protocols would happily overwrite user configuration files: # ls -l /etc/l7-protocols/extra/http-itunes.pat -rw--- 1 root root 30 Sep 14 22:57 /etc/l7-protocols/extra/http-itunes.pat # dpkg -i /path/to/l7-protocols_20090528-1_all.deb [...] Unpacking l7-protocols (from .../l7-protocols_20090528-1_all.deb) ... Setting up l7-protocols (20090528-1) ... # ls -l /etc/l7-protocols/extra/http-itunes.pat* lrwxrwxrwx 1 root root 45 Sep 14 22:57 /etc/l7-protocols/extra/http-itunes.pat - /usr/share/l7-protocols/extra/http-itunes.pat -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546667: ayttm: gtkut_stock_button_new_with_label implicitly converted to pointer
Package: ayttm Version: 0.6.0-1 Severity: serious Tags: patch Usertags: implicit-pointer-conversion Our automated buildd log filter[1] detected a problem that is likely to cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64 and amd64. Function `gtkut_stock_button_new_with_label' implicitly converted to pointer at trigger.c:390 This is often due to a missing function prototype definition. For more information, see [2]. Though it is guaranteed that this codepath will cause a segfault on certain architectures, it is not guaranteed that this codepath would ever be executed (e.g., if the returned pointer is never dereferenced). However, this bug does prevent the ia64 buildd from successfully building this package, resulting in a practical FTBFS issue and warranting the serious severity. [1] http://people.debian.org/~dannf/check-implicit-pointer-functions [2] http://wiki.debian.org/ImplicitPointerConversions --- ayttm-0.6.0.orig/src/trigger.c 2009-09-06 21:49:25.0 -0600 +++ ayttm-0.6.0/src/trigger.c 2009-09-14 16:05:56.566011839 -0600 @@ -36,6 +36,7 @@ #include globals.h #include file_select.h #include messages.h +#include gtk/gtkutils.h static gint window_open = 0;
Bug#536683: bash execution trace
Dear Rogerio, I moved my xorg.conf out of the way and could configure console-setup without any problems. Thanks for the hint. In xorg.conf I had the line Option XkbLayout ziegler where ziegler is my own keyboard-layout, situated in /usr/share/X11/xkb/symbols. Maybe this caused the problem Regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536683: console-setup: getting it diagnosed
Hi, Martin.
On Sep 15 2009, Martin Ziegler wrote:
I moved my xorg.conf out of the way and could configure
console-setup without any problems. Thanks for the hint.
Glad that it worked.
As a workaround, you can change the file generated by console-setup by
hand, until a fix is incorporated in console-setup.
In xorg.conf I had the line
Option XkbLayout ziegler
where ziegler is my own keyboard-layout, situated in
/usr/share/X11/xkb/symbols. Maybe this caused the problem
No, as per my previous message, it seems that any presence of
xorg.conf creates a problem here.
The configure script of console-setup (in my case, console-setup-mini,
as I don't want to drag spurious dependencies) should be more resistant.
Thanks for testing my hypothesis, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#543369: [Parted-maintainers] Bug#543369: gnu-fdisk: diff for NMU version 1.2.3-1.1
On 10:22 Sat 12 Sep , Luk Claes wrote: Dear maintainer, I've prepared an NMU for gnu-fdisk (versioned as 1.2.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. You could maybe have asked me before doing this. But ok, Thanks! I was about to correct this info file mistake this night... Feel free to keep this NMU. Greetings, -- ,''`. ** Xavier Oswald xosw...@debian.org : :' : ** Research Engineer `. `' ** GNU/LINUX Debian Developer (http://debian.org) `-** Isaac Project Developer (http://isaacproject.u-strasbg.fr/) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#478460: marked as done (python-scientific: should use python-numpy instead of python-num{eric,array})
Your message dated Mon, 14 Sep 2009 23:04:58 +
with message-id e1mnkbs-0007ry...@ries.debian.org
and subject line Bug#478460: fixed in python-scientific 2.8-1
has caused the Debian Bug report #478460,
regarding python-scientific: should use python-numpy instead of
python-num{eric,array}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
478460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-scientific
Version: 2.4.11-1.2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python-oldnum
Both python-numeric and python-numarray do not see new upstream releases
anymore; the currently maintained project is python-numpy. Please convert
the package to use python-numpy instead. This might require changes to
the upstream code.
---End Message---
---BeginMessage---
Source: python-scientific
Source-Version: 2.8-1
We believe that the bug you reported is fixed in the latest version of
python-scientific, which is due to be installed in the Debian FTP archive:
lampython_2.8-1_i386.deb
to pool/main/p/python-scientific/lampython_2.8-1_i386.deb
mpichpython_2.8-1_i386.deb
to pool/main/p/python-scientific/mpichpython_2.8-1_i386.deb
python-mpi_2.8-1_all.deb
to pool/main/p/python-scientific/python-mpi_2.8-1_all.deb
python-netcdf_2.8-1_i386.deb
to pool/main/p/python-scientific/python-netcdf_2.8-1_i386.deb
python-scientific-doc_2.8-1_all.deb
to pool/main/p/python-scientific/python-scientific-doc_2.8-1_all.deb
python-scientific_2.8-1.diff.gz
to pool/main/p/python-scientific/python-scientific_2.8-1.diff.gz
python-scientific_2.8-1.dsc
to pool/main/p/python-scientific/python-scientific_2.8-1.dsc
python-scientific_2.8-1_all.deb
to pool/main/p/python-scientific/python-scientific_2.8-1_all.deb
python-scientific_2.8.orig.tar.gz
to pool/main/p/python-scientific/python-scientific_2.8.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 478...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose d...@debian.org (supplier of updated python-scientific package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 14 Sep 2009 23:37:22 +0200
Source: python-scientific
Binary: python-scientific python-netcdf python-scientific-doc python-mpi
mpichpython lampython
Architecture: source all i386
Version: 2.8-1
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose d...@debian.org
Changed-By: Matthias Klose d...@debian.org
Description:
lampython - MPI-enhanced Python interpreter (LAM based version)
mpichpython - MPI-enhanced Python interpreter (MPICH based version)
python-mpi - MPI module for Python
python-netcdf - A netCDF interface for Python
python-scientific - Python modules useful for scientific computing
python-scientific-doc - Python modules useful for scientific computing
Closes: 475996 475997 475999 478460
Changes:
python-scientific (2.8-1) unstable; urgency=low
.
* New upstream version.
* Build against NumPY. Closes: #478460.
* Complete sentences in package descriptions. Closes: #475997, #475996,
#475999.
Checksums-Sha1:
6e143a9fef71be2c3f19c9330c7a35b7a57ba608 1215 python-scientific_2.8-1.dsc
c0847eac6359d70b0e4687c5c65af49b3986e55b 559613
python-scientific_2.8.orig.tar.gz
4de211d998cfdebbe059f18eb8e065f7b038e3ff 6504 python-scientific_2.8-1.diff.gz
09ea7b76ab640948ab7d2331bbc0d93bb19be209 151026 python-scientific_2.8-1_all.deb
51b16e3d1d58522d210969c69ea6960e398c1042 392190
python-scientific-doc_2.8-1_all.deb
7983934ffefcdc881c45c07db1b68d57813f3a51 26182 python-mpi_2.8-1_all.deb
e892b48acdac3b6a8d0265983f8fc2b1f12bbccf 94738 python-netcdf_2.8-1_i386.deb
8f31b207d50ed0efc5ac60ff6fecc701af933046 153744 mpichpython_2.8-1_i386.deb
35ff4da9dde2f50fb3d7f93deec6320da72540cb 13132 lampython_2.8-1_i386.deb
Checksums-Sha256:
012e32b3e6fcebe6efe31d5cd53457b1fd76ecc1b912c9c3673a7d054ece971b 1215
python-scientific_2.8-1.dsc
4de6c8d1b28526d0f2db02f30e99a28a8340ee4cc06fa0a5c0d4b20096806908 559613
python-scientific_2.8.orig.tar.gz
95c3137ff572345065db52d9352e9dc3509a42935095bf8cca9217da79b60497 6504
python-scientific_2.8-1.diff.gz
Bug#543351: marked as done (logilab.astng cannot be imported after upgrade from stable)
Your message dated Mon, 14 Sep 2009 23:04:34 +
with message-id e1mnkb4-0007ne...@ries.debian.org
and subject line Bug#543351: fixed in logilab-common 0.45.0-1
has caused the Debian Bug report #543351,
regarding logilab.astng cannot be imported after upgrade from stable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
543351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-logilab-astng
Severity: serious
Version: 0.19.0-2
python-logilab-astng (and thus pylint, python-django-lint et. al) becomes
unusable when upgrading from stable. From a clean lenny chroot:
la...@sakaki(lenny-amd64):~% sudo apt-get install python-logilab-astng
[..]
la...@sakaki(lenny-amd64):~% python -c from logilab import astng
la...@sakaki(lenny-amd64):~% echo $?
0
Now, after dist-upgrading this chroot to squeeze:
la...@sakaki(lenny-amd64):~% python -c from logilab import astng
Traceback (most recent call last):
File string, line 1, in module
ImportError: cannot import name astng
I can make it work by manually removing
/usr/lib/python2.5/site-packages/logilab
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
---End Message---
---BeginMessage---
Source: logilab-common
Source-Version: 0.45.0-1
We believe that the bug you reported is fixed in the latest version of
logilab-common, which is due to be installed in the Debian FTP archive:
logilab-common_0.45.0-1.diff.gz
to pool/main/l/logilab-common/logilab-common_0.45.0-1.diff.gz
logilab-common_0.45.0-1.dsc
to pool/main/l/logilab-common/logilab-common_0.45.0-1.dsc
logilab-common_0.45.0.orig.tar.gz
to pool/main/l/logilab-common/logilab-common_0.45.0.orig.tar.gz
python-logilab-common_0.45.0-1_all.deb
to pool/main/l/logilab-common/python-logilab-common_0.45.0-1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 543...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi mo...@debian.org (supplier of updated logilab-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 14 Sep 2009 22:38:49 +0200
Source: logilab-common
Binary: python-logilab-common
Architecture: source all
Version: 0.45.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Sandro Tosi mo...@debian.org
Description:
python-logilab-common - useful miscellaneous modules used by Logilab projects
Closes: 543351 546487
Changes:
logilab-common (0.45.0-1) unstable; urgency=medium
.
* New upstream release; thanks to Chris Lamb for the report; Closes: #546487
* debian/copyright
- added packaging copyright for the work I do
* debian/control
- updated long description
- suggesting pyro, since there's new code using it
- bump Standards-Version to 3.8.3 (no changes needed)
- removed conflicts for packages never been in Debian
* debian/{control, python-logilab-common.preinst}
- handle pycentral-pysupport migration more aggressively:
+ on upgrades, remove the whole /usr/lib/python*/site-packages/logilab/
subtree; thanks to Chris Lamb for the report; Closes: #543351
+ add conflicts on all the depending packages with version less than the
new (pespective) package version
Checksums-Sha1:
5980e120a7f34057cdc2d0317eaa47ec3fa9681c 1553 logilab-common_0.45.0-1.dsc
18f1f6dc3575d190aa1d91a7e027d89ce89c90bb 173484
logilab-common_0.45.0.orig.tar.gz
a9e5d4c06e31a4c691bf1acc4f1522b6050619b7 6335 logilab-common_0.45.0-1.diff.gz
e529d68c35a72016c7e0c2caf324a457bb78acee 972620
python-logilab-common_0.45.0-1_all.deb
Checksums-Sha256:
40f02c1f02c880282fff3ef1b0deff3846abd63dc291e487bea417a437fa19d6 1553
logilab-common_0.45.0-1.dsc
1ed092ff5ef2cd82ad98a6a3f810f7aa34f4a438cf2449e26983d486de0472c1 173484
logilab-common_0.45.0.orig.tar.gz
71d09408b9c29b1d9e862e0488a00ba99acc79835f7b7e8e2e1d5d4bd6273780 6335
logilab-common_0.45.0-1.diff.gz
981cf5fba4e8cde412b42d711dee3037166c80ed4efd86fb9746010c9b87f3cd 972620
Bug#546487: marked as done (New upstream version available)
Your message dated Mon, 14 Sep 2009 23:04:34 +
with message-id e1mnkb4-0007ng...@ries.debian.org
and subject line Bug#546487: fixed in logilab-common 0.45.0-1
has caused the Debian Bug report #546487,
regarding New upstream version available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
546487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: logilab-common
Version: 0.39.0-1
Severity: serious
Justification: blocking #543380
Hi,
I just spent a few moments trying to fix #543380 (django-lint: Needs
porting to new pylint and logilab-astng), which is rendering django-lint
completely broken at the moment.
Even after making a couple of changes, I needed to upgrade logilab-common to
0.45.0 to get the type inference working correctly.
Looking through the ChangeLog, I can't actually identify the exact change
and thus what the minimum required version is, but this file doesn't exactly
tally with the VCS log anyway.
Anyway, please package this new version.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
---End Message---
---BeginMessage---
Source: logilab-common
Source-Version: 0.45.0-1
We believe that the bug you reported is fixed in the latest version of
logilab-common, which is due to be installed in the Debian FTP archive:
logilab-common_0.45.0-1.diff.gz
to pool/main/l/logilab-common/logilab-common_0.45.0-1.diff.gz
logilab-common_0.45.0-1.dsc
to pool/main/l/logilab-common/logilab-common_0.45.0-1.dsc
logilab-common_0.45.0.orig.tar.gz
to pool/main/l/logilab-common/logilab-common_0.45.0.orig.tar.gz
python-logilab-common_0.45.0-1_all.deb
to pool/main/l/logilab-common/python-logilab-common_0.45.0-1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 546...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sandro Tosi mo...@debian.org (supplier of updated logilab-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 14 Sep 2009 22:38:49 +0200
Source: logilab-common
Binary: python-logilab-common
Architecture: source all
Version: 0.45.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org
Changed-By: Sandro Tosi mo...@debian.org
Description:
python-logilab-common - useful miscellaneous modules used by Logilab projects
Closes: 543351 546487
Changes:
logilab-common (0.45.0-1) unstable; urgency=medium
.
* New upstream release; thanks to Chris Lamb for the report; Closes: #546487
* debian/copyright
- added packaging copyright for the work I do
* debian/control
- updated long description
- suggesting pyro, since there's new code using it
- bump Standards-Version to 3.8.3 (no changes needed)
- removed conflicts for packages never been in Debian
* debian/{control, python-logilab-common.preinst}
- handle pycentral-pysupport migration more aggressively:
+ on upgrades, remove the whole /usr/lib/python*/site-packages/logilab/
subtree; thanks to Chris Lamb for the report; Closes: #543351
+ add conflicts on all the depending packages with version less than the
new (pespective) package version
Checksums-Sha1:
5980e120a7f34057cdc2d0317eaa47ec3fa9681c 1553 logilab-common_0.45.0-1.dsc
18f1f6dc3575d190aa1d91a7e027d89ce89c90bb 173484
logilab-common_0.45.0.orig.tar.gz
a9e5d4c06e31a4c691bf1acc4f1522b6050619b7 6335 logilab-common_0.45.0-1.diff.gz
e529d68c35a72016c7e0c2caf324a457bb78acee 972620
python-logilab-common_0.45.0-1_all.deb
Checksums-Sha256:
40f02c1f02c880282fff3ef1b0deff3846abd63dc291e487bea417a437fa19d6 1553
logilab-common_0.45.0-1.dsc
1ed092ff5ef2cd82ad98a6a3f810f7aa34f4a438cf2449e26983d486de0472c1 173484
logilab-common_0.45.0.orig.tar.gz
71d09408b9c29b1d9e862e0488a00ba99acc79835f7b7e8e2e1d5d4bd6273780 6335
logilab-common_0.45.0-1.diff.gz
981cf5fba4e8cde412b42d711dee3037166c80ed4efd86fb9746010c9b87f3cd 972620
python-logilab-common_0.45.0-1_all.deb
Files:
3e11d23016f5222348ceed2ed031663b 1553 python optional
logilab-common_0.45.0-1.dsc
Bug#545602: marked as done (gnome-terminal: FTBFS: IndexError: list index out of range)
Your message dated Mon, 14 Sep 2009 23:32:27 +
with message-id e1mnl23-0001ti...@ries.debian.org
and subject line Bug#545602: fixed in gnome-terminal 2.26.3.1-1
has caused the Debian Bug report #545602,
regarding gnome-terminal: FTBFS: IndexError: list index out of range
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
545602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: gnome-terminal
Version: 2.26.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090907 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[4]: Entering directory
`/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory
`/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help'
if ! test -d da/; then mkdir da/; fi
if [ -f C/gnome-terminal.xml ]; then d=../; else
d=/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help/;
fi; \
(cd da/ \
`which xml2po` -e -p \
${d}da/da.po \
${d}C/gnome-terminal.xml gnome-terminal.xml.tmp \
cp gnome-terminal.xml.tmp gnome-terminal.xml rm -f
gnome-terminal.xml.tmp)
if ! test -d de/; then mkdir de/; fi
if [ -f C/gnome-terminal.xml ]; then d=../; else
d=/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help/;
fi; \
(cd de/ \
`which xml2po` -e -p \
${d}de/de.po \
${d}C/gnome-terminal.xml gnome-terminal.xml.tmp \
cp gnome-terminal.xml.tmp gnome-terminal.xml rm -f
gnome-terminal.xml.tmp)
if ! test -d ca/; then mkdir ca/; fi
if [ -f C/gnome-terminal.xml ]; then d=../; else
d=/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help/;
fi; \
(cd ca/ \
`which xml2po` -e -p \
${d}ca/ca.po \
${d}C/gnome-terminal.xml gnome-terminal.xml.tmp \
cp gnome-terminal.xml.tmp gnome-terminal.xml rm -f
gnome-terminal.xml.tmp)
if ! test -d cs/; then mkdir cs/; fi
if [ -f C/gnome-terminal.xml ]; then d=../; else
d=/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help/;
fi; \
(cd cs/ \
`which xml2po` -e -p \
${d}cs/cs.po \
${d}C/gnome-terminal.xml gnome-terminal.xml.tmp \
cp gnome-terminal.xml.tmp gnome-terminal.xml rm -f
gnome-terminal.xml.tmp)
if ! test -d el/; then mkdir el/; fi
if [ -f C/gnome-terminal.xml ]; then d=../; else
d=/build/user-gnome-terminal_2.26.2-2-amd64-Up6pBM/gnome-terminal-2.26.2/help/;
fi; \
(cd el/ \
`which xml2po` -e -p \
${d}el/el.po \
${d}C/gnome-terminal.xml gnome-terminal.xml.tmp \
cp gnome-terminal.xml.tmp gnome-terminal.xml rm -f
gnome-terminal.xml.tmp)
Traceback (most recent call last):
File /usr/bin/xml2po, line 185, in module
main(sys.argv[1:])
File /usr/bin/xml2po, line 171, in main
xml2po_main.merge(mofile, filenames[0])
File /usr/lib/pymodules/python2.5/xml2po/__init__.py, line 601, in merge
self.gt = gettext.GNUTranslations(mfile)
File /usr/lib/python2.5/gettext.py, line 180, in __init__
self._parse(fp)
File /usr/lib/python2.5/gettext.py, line 314, in _parse
plural = v[1].split('plural=')[1]
IndexError: list index out of range
make[3]: *** [el/gnome-terminal.xml] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/09/07/gnome-terminal_2.26.2-2_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
---End Message---
---BeginMessage---
Source: gnome-terminal
Source-Version: 2.26.3.1-1
We believe that the bug you reported is fixed in the latest version of
gnome-terminal, which is due to be installed in the Debian FTP archive:
gnome-terminal-data_2.26.3.1-1_all.deb
to pool/main/g/gnome-terminal/gnome-terminal-data_2.26.3.1-1_all.deb
gnome-terminal_2.26.3.1-1.diff.gz
to
Bug#545356: marked as done (initscripts: Missing dependency on sysvinit-utils)
Your message dated Mon, 14 Sep 2009 23:47:34 + with message-id e1mnlgg-0002nj...@ries.debian.org and subject line Bug#545356: fixed in sysvinit 2.87dsf-6 has caused the Debian Bug report #545356, regarding initscripts: Missing dependency on sysvinit-utils to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 545356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initscripts Version: 2.87dsf-2+b1 Severity: grave Justification: causes non-serious data loss I apt-geet install initscript and it failed to grab the corresponding sysvinit-utils package. This caused /sbin/fstab-decode to be missing and therefore /etc/init.d/umountfs would not properly umount the filesystems, causing an fsck on all of them at the next boot. There is probably a missing dependency between initscript and the sysvinit-utils package. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30.5 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii debianutils 2.23.1 Miscellaneous utilities specific t ii libc6 2.9-12 GNU C Library: Shared libraries ii lsb-base3.2-23 Linux Standard Base 3.2 init scrip ii mount 2.16-3 Tools for mounting and manipulatin ii sysvinit-utils 2.87dsf-2+b1 System-V-like utilities Versions of packages initscripts recommends: ii e2fsprogs 1.37-2sarge1 ext2 file system utilities and lib ii psmisc 20.2-2.1 Utilities that use the proc filesy initscripts suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: sysvinit Source-Version: 2.87dsf-6 We believe that the bug you reported is fixed in the latest version of sysvinit, which is due to be installed in the Debian FTP archive: initscripts_2.87dsf-6_i386.deb to pool/main/s/sysvinit/initscripts_2.87dsf-6_i386.deb sysv-rc_2.87dsf-6_all.deb to pool/main/s/sysvinit/sysv-rc_2.87dsf-6_all.deb sysvinit-utils_2.87dsf-6_i386.deb to pool/main/s/sysvinit/sysvinit-utils_2.87dsf-6_i386.deb sysvinit_2.87dsf-6.diff.gz to pool/main/s/sysvinit/sysvinit_2.87dsf-6.diff.gz sysvinit_2.87dsf-6.dsc to pool/main/s/sysvinit/sysvinit_2.87dsf-6.dsc sysvinit_2.87dsf-6_i386.deb to pool/main/s/sysvinit/sysvinit_2.87dsf-6_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 545...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen p...@debian.org (supplier of updated sysvinit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Sep 2009 01:28:19 +0200 Source: sysvinit Binary: sysvinit sysvinit-utils sysv-rc initscripts Architecture: source i386 all Version: 2.87dsf-6 Distribution: unstable Urgency: low Maintainer: Debian sysvinit maintainers pkg-sysvinit-de...@lists.alioth.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: initscripts - scripts for initializing and shutting down the system sysv-rc- System-V-like runlevel change mechanism sysvinit - System-V-like init utilities sysvinit-utils - System-V-like utilities Closes: 239342 265801 406361 545356 545368 545409 545949 546405 Changes: sysvinit (2.87dsf-6) unstable; urgency=low . * Correct code in sysv-rc postinst to avoid failing to install when no init.d scripts have been removed (Closes: #546405). * Start bootlogd before lvm2 too, to push it even further forward in the boot sequence. . sysvinit (2.87dsf-5) experimental; urgency=low . * Uploading to experimental, to test the new build rules. . * Make sysv-rc postinst report detected problems to stderr too when failing to migrate. * Fix typo in error message from postinst (Closes: #545409). * Make initscripts depend on sysvinit-utils (= 2.86.ds1-64), to make sure the fstab-decode program is available (Closes: #545356). * Make sure the calls to 'update-rc.d X remove'
Bug#546678: ecryptfs-utils: FTFBS - _FILE_OFFSET_BITS = 64
Package: ecryptfs-utils Version: 75-2 Severity: serious Tags: patch Justification: FTFBS Hi, I am now trying to run Debian on Renesas SH CPU(sh4). ecryptfs-utils FTBFS on sh4. When I built in the other architecture(i386), I became the same problem. snip libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -g -O2 -MT libecryptfs_key_mod_gpg_la-ecryptfs_key_mod_gpg.lo -MD -MP -MF .deps/libecryptfs_key_mod_gpg_la-ecryptfs_key_mod_gpg.Tpo -c ecryptfs_key_mod_gpg.c -fPIC -DPIC -o .libs/libecryptfs_key_mod_gpg_la-ecryptfs_key_mod_gpg.o In file included from ecryptfs_key_mod_gpg.c:30: /usr/include/gpgme.h:80:2: error: #error GPGME was compiled with _FILE_OFFSET_BITS = 64, please see the section Largefile support (LFS) in the GPGME manual. ecryptfs_key_mod_gpg.c: In function 'tf_gpg_enter': ecryptfs_key_mod_gpg.c:332: warning: passing argument 1 of 'gpgme_release' from incompatible pointer type make[4]: *** [libecryptfs_key_mod_gpg_la-ecryptfs_key_mod_gpg.lo] Error 1 make[4]: Leaving directory `/tmp/buildd/ecryptfs-utils-75/src/key_mod' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/buildd/ecryptfs-utils-75/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/ecryptfs-utils-75' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/ecryptfs-utils-75' make: *** [build-stamp] Error 2 /snip I made a patch to revise to be able to build. Would you apply it? Best regards, Nobuhiro -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ecryptfs-utils.patch Description: application/empty
Bug#546679: pyme: FTFBS - gpgme_wrap.c: No such file or directory
Package: pyme Version: 0.8.1+clean-1 Severity: serious Justification: FTFBS Hi, Current pyme package FTFBS. snip creating /tmp/buildd/pyme-0.8.1+clean/build/lib.linux-i686-2.5/pyme/constants/keylist copying pyme/constants/keylist/mode.py - /tmp/buildd/pyme-0.8.1+clean/./build/lib.linux-i686-2.5/pyme/constants/keylist copying pyme/constants/keylist/__init__.py - /tmp/buildd/pyme-0.8.1+clean/./build/lib.linux-i686-2.5/pyme/constants/keylist creating /tmp/buildd/pyme-0.8.1+clean/build/lib.linux-i686-2.5/pyme/constants/sig copying pyme/constants/sig/mode.py - /tmp/buildd/pyme-0.8.1+clean/./build/lib.linux-i686-2.5/pyme/constants/sig copying pyme/constants/sig/__init__.py - /tmp/buildd/pyme-0.8.1+clean/./build/lib.linux-i686-2.5/pyme/constants/sig running build_ext building 'pyme._pygpgme' extension creating /tmp/buildd/pyme-0.8.1+clean/build/temp.linux-i686-2.5 gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -O2 -g -Wall -O2 -fPIC -I/tmp/buildd/pyme-0.8.1+clean -I/usr/include/python2.5 -c gpgme_wrap.c -o /tmp/buildd/pyme-0.8.1+clean/./build/temp.linux-i686-2.5/gpgme_wrap.o gcc: gpgme_wrap.c: No such file or directory gcc: no input files error: command 'gcc' failed with exit status 1 make: *** [debian/python-module-stampdir/python-pyme] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 /snip Best regards, Nobuhiro -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546547: bash: 4.0-7 upgrade works
Package: bash Severity: normal This morning the upgrade worked: Preparing to replace bash 4.0-4 (using .../archives/bash_4.0-7_i386.deb) ... Unpacking replacement bash ... Processing triggers for install-info ... install-info: warning: no info dir entry in `/usr/share/info/ispell.info.gz' install-info: warning: no info dir entry in `/usr/share/info/menu.info.gz' Processing triggers for man-db ... Processing triggers for menu ... Setting up bash (4.0-7) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode. Processing triggers for menu ... Press return to continue. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.31-rc6 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bash depends on: ii base-files5.0.0 Debian base system miscellaneous f ii dash 0.5.5.1-2.3POSIX-compliant shell ii debianutils 3.2.1 Miscellaneous utilities specific t ii libc6 2.9-26 GNU C Library: Shared libraries ii libncurses5 5.7+20090803-2 shared libraries for terminal hand Versions of packages bash recommends: ii bash-completion 1:1.0-3programmable completion for the ba Versions of packages bash suggests: pn bash-doc none (no description available) -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546681: mcabber: FTFBS - _FILE_OFFSET_BITS = 64
Package: mcabber
Version: 0.9.9-0.1
Severity: serious
Tags: patch
Justification: FTFBS
Hi,
I am now trying to run Debian on Renesas SH CPU(sh4).
ecryptfs-utils FTBFS on sh4.
When I built in the other architecture(i386), I became the same problem.
snip
make[3]: Leaving directory `/tmp/buildd/mcabber-0.9.9/libjabber'
Making all in src
make[3]: Entering directory `/tmp/buildd/mcabber-0.9.9/src'
../hgcset.sh
/usr/bin/make all-am
make[4]: Entering directory `/tmp/buildd/mcabber-0.9.9/src'
i486-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -O2 -Wall -g -O2 -Wl,-z,defs -Wall
-I/usr -D_GNU_SOURCE -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o
main.c
In file included from pgp.h:9,
from roster.h:7,
from jabglue.h:6,
from main.c:34:
/usr/include/gpgme.h:80:2: error: #error GPGME was compiled with
_FILE_OFFSET_BITS = 64, please see the section Largefile support (LFS)
in the GPGME manual.
make[4]: *** [main.o] Error 1
make[4]: Leaving directory `/tmp/buildd/mcabber-0.9.9/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/tmp/buildd/mcabber-0.9.9/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/mcabber-0.9.9'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/mcabber-0.9.9'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
/snip
I made a patch to revise to be able to build.
Would you apply it?
Best regards,
Nobuhiro
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- debian/rules.old 2009-09-15 10:08:24.0 +0900
+++ debian/rules 2009-09-15 09:51:25.0 +0900
@@ -16,6 +16,9 @@
CFLAGS += -O2
endif
+# libgpgme need Largefile support
+CFLAGS += -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
+
config.status: patch
dh_testdir
CFLAGS=$(CFLAGS) -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --enable-gpgme --enable-aspell --enable-otr
Bug#546678: ecryptfs-utils: FTFBS - _FILE_OFFSET_BITS = 64
Hi, Sorry, I made a mistake in a patch to attach. I attach and re-send. -- Nobuhiro Iwamatsu ecryptfs-utils.patch Description: application/empty
Bug#546667: Fwd: Bug#546667: ayttm: gtkut_stock_button_new_with_label implicitly converted to pointer
forwarded 546667 ayttm-de...@lists.sourceforge.net
thanks
Hi Siddhesh,
Please check and adopt attached patch. I am adding it tonight..
Thanks to Dann for reporting this and patch!
-- Forwarded message --
From: dann frazier da...@debian.org
Date: Tue, Sep 15, 2009 at 3:36 AM
Subject: Bug#546667: ayttm: gtkut_stock_button_new_with_label
implicitly converted to pointer
To: sub...@bugs.debian.org
Package: ayttm
Version: 0.6.0-1
Severity: serious
Tags: patch
Usertags: implicit-pointer-conversion
Our automated buildd log filter[1] detected a problem that is likely to
cause your package to segfault on architectures where the size of a
pointer is greater than the size of an integer, such as ia64 and amd64.
Function `gtkut_stock_button_new_with_label' implicitly converted to
pointer at trigger.c:390
This is often due to a missing function prototype definition.
For more information, see [2].
Though it is guaranteed that this codepath will cause a segfault on certain
architectures, it is not guaranteed that this codepath would ever be executed
(e.g., if the returned pointer is never dereferenced). However, this bug
does prevent the ia64 buildd from successfully building this package, resulting
in a practical FTBFS issue and warranting the serious severity.
[1] http://people.debian.org/~dannf/check-implicit-pointer-functions
[2] http://wiki.debian.org/ImplicitPointerConversions
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Debian GNU/Linux Developer | Identica: @kartikm
Blogs: {ftbfs, kartikm}.wordpress.com
--- ayttm-0.6.0.orig/src/trigger.c 2009-09-06 21:49:25.0 -0600
+++ ayttm-0.6.0/src/trigger.c 2009-09-14 16:05:56.566011839 -0600
@@ -36,6 +36,7 @@
#include globals.h
#include file_select.h
#include messages.h
+#include gtk/gtkutils.h
static gint window_open = 0;
Bug#546667: [Ayttm-devel] Fwd: Bug#546667: ayttm: gtkut_stock_button_new_with_label implicitly converted to pointer
On Tue, Sep 15, 2009 at 9:03 AM, Kartik Mistry kartik.mis...@gmail.com wrote: forwarded 546667 ayttm-de...@lists.sourceforge.net thanks Hi Siddhesh, Please check and adopt attached patch. I am adding it tonight.. Thanks to Dann for reporting this and patch! Thanks. Committed fix. -- Siddhesh Poyarekar http://siddhesh.in -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#530032: Closing or downgrading severity
On Sat, 2009-09-12 at 15:57 +0200, Bas Wijnen wrote: I've written a patch which listens on everything returned by getaddrinfo. The call returns two structures, but the second bind fails with address already in use. It seems the problem doesn't occur in Debian, because it automatically listens on both IPv4 and IPv6(?) So I'm a bit confused: this is a Debian bug, so the problem presumably exists on Debian systems. This may be different on GNU/kFreeBSD, but the reporter is using GNU/Linux, like the system I'm testing on. Anyway, I'm attaching the patch. That patch does not work as advertised. I get the error, and the result (according to netstat) is that the server only listens on IPv4. Somewhere when I upgraded to kernel 2.6.30 Pioneers broke, so I assume that the automatic IPv6-IPv4 bridge was removed. I still think that this bug report now contains two bugs reports: 1) Fixing playing games with localhost (especially for computer players) 2) Making the server IPv6 compliant No 1. is fixed, and that fix alone should be enough to make a new release. It would be nice if no 2. would be fixed, but that can be done slightly later. With kind regards, Roland Clobus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
