Bug#999989: poco 1.12 uses PCRE2
According to upstream changelog, upgrading the package to 1.12.x should allow to fix this RC bug.
Bug#965025: gpsshogi-data: data does not seem to be provided in the preferred format for modification
Package: gpsshogi Version: 0.7.0-2 Severity: serious The .bin and .dat files in gpsshogi-data come as-is in SVN, with no information as to what they are generated from. This does not look DFSG-compliant. As to the impact on my work on resurrecting the package (#964730), if this issue is not solve it looks to me like at the minimum the data would have to be split into non-free, and gpsshogi itself move to contrib. -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (990, 'stable'), (900, 'testing'), (500, 'stable-debug'), (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gpsshogi depends on: ii gpsshogi-data 0.7.0-2 ii libboost-date-time1.67.01.67.0-13+deb10u1 ii libboost-filesystem1.67.0 1.67.0-13+deb10u1 ii libboost-iostreams1.67.01.67.0-13+deb10u1 ii libboost-program-options1.67.0 1.67.0-13+deb10u1 ii libboost-serialization1.67.01.67.0-13+deb10u1 ii libboost-system1.67.0 1.67.0-13+deb10u1 ii libboost-thread1.67.0 1.67.0-13+deb10u1 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libgl1 1.1.0-1 ii libgsl232.5+dfsg-6 ii libosl1v5 0.8.0-2~deb10u0 ii libpocofoundation60 1.9.0-5+b1 ii libpoconet601.9.0-5+b1 ii libqt5core5a5.11.3+dfsg1-1+deb10u3 ii libqt5gui5 5.11.3+dfsg1-1+deb10u3 ii libqt5network5 5.11.3+dfsg1-1+deb10u3 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u3 ii libqt5xml5 5.11.3+dfsg1-1+deb10u3 ii libreadline77.0-5 ii libstdc++6 8.3.0-6 ii libtcmalloc-minimal42.7-1 gpsshogi recommends no packages. gpsshogi suggests no packages. -- no debconf information
Bug#801866: update-flashplugin-nonfree and new versions
It is a bit awkward to have --status report a new version, and --install just not say anything by default. With --install --verbose one can finally understand with some effort that the version it downloads is the one that's already installed. But why just not telling the user something like "We need to do some work to make the new update available, please be patient and understand what needs to be done at http://wiki.debian.org/FlashPlayer#maintainance"; ... so that we can all avoid whining in our own corner :) Best regards, -- Yann
Bug#785840: gcompris: Please update to GStreamer 1.x
On Sun, Sep 20, 2015 at 10:22:59PM +0200, Sebastian Dröge wrote: > Is gcompris-qt still using GStreamer, or are they just going via > QtMultimedia then (which for Debian would still be GStreamer)? It's using libQt5Multimedia.
Bug#785840: gcompris: Please update to GStreamer 1.x
On Sun, Sep 20, 2015 at 08:36:06PM +0200, Sebastian Dröge wrote:
> On So, 2015-09-20 at 19:17 +0200, Sebastian Dröge wrote:
> > On So, 2015-09-20 at 15:33 +0200, Sebastian Dröge wrote:
> > > Hi again,
> > >
> > > I shortly looked at the code in git in gstreamer.c. Not a single
> > > change other than the build system and package dependencies should
> > > be
> > > necessary here.
> >
> > FWIW, I'll send you a patch soonish. Seem to have something almost
> > working now.
>
> Patch attached, please upload or should I do an NMU? Whatever you
> prefer :)
You seem pretty ready to upload, feel free :)
And thanks for your contribution !
> Untested except for compilation!
Well, it should not be much more than just checking if you have sound
on startup :)
> diff -Nru gcompris-15.02/debian/changelog gcompris-15.02/debian/changelog
> --- gcompris-15.02/debian/changelog 2015-05-05 22:57:06.0 +0200
> +++ gcompris-15.02/debian/changelog 2015-09-20 19:51:19.0 +0200
> @@ -1,3 +1,10 @@
> +gcompris (15.02-1.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Update to GStreamer 1.0 (Closes: #785840).
> +
> + -- Sebastian Dröge Sun, 20 Sep 2015 19:09:08 +0200
> +
> gcompris (15.02-1) unstable; urgency=medium
>
>* New upstream release.
> diff -Nru gcompris-15.02/debian/control gcompris-15.02/debian/control
> --- gcompris-15.02/debian/control 2014-12-30 18:30:43.00000 +0100
> +++ gcompris-15.02/debian/control 2015-09-20 20:18:51.0 +0200
> @@ -3,14 +3,14 @@
> Priority: optional
> Maintainer: Yann Dirson
> Homepage: http://gcompris.net/
> -Build-Depends: debhelper (>= 9), autotools-dev, dh-buildinfo, dpkg-dev (>=
> 1.13.19), libxml2-dev, python-dev, python-gtk2-dev, libxml-parser-perl,
> libxrandr-dev, libxxf86vm-dev, libsqlite3-dev, libgtk2.0-dev (>= 2.4.0),
> libgstreamer0.10-dev, intltool, librsvg2-dev, python-cairo-dev
> +Build-Depends: debhelper (>= 9), dh-autoreconf, autoconf, automake, libtool,
> autotools-dev, gnome-common, dh-buildinfo, dpkg-dev (>= 1.13.19),
> libxml2-dev, python-dev, python-gtk2-dev, libxml-parser-perl, libxrandr-dev,
> libxxf86vm-dev, libsqlite3-dev, libgtk2.0-dev (>= 2.4.0),
> libgstreamer1.0-dev, intltool, librsvg2-dev, python-cairo-dev
> Standards-Version: 3.9.3
> Vcs-git: git://anonscm.debian.org/collab-maint/gcompris.git
> Vcs-browser:
> http://anonscm.debian.org/gitweb/?p=collab-maint/gcompris.git;a=summary
>
> Package: gcompris
> Architecture: any
> -Depends: gcompris-data (= ${source:Version}), ${shlibs:Depends},
> ${python:Depends}, python-pysqlite2, python-gtk2, gstreamer0.10-alsa |
> gstreamer0.10-audiosink, gstreamer0.10-plugins-base,
> gstreamer0.10-plugins-good, librsvg2-common (>= 2.18), python-cairo,
> ${misc:Depends}
> +Depends: gcompris-data (= ${source:Version}), ${shlibs:Depends},
> ${python:Depends}, python-pysqlite2, python-gtk2, gstreamer1.0-alsa |
> gstreamer1.0-audiosink, gstreamer1.0-plugins-base, gstreamer1.0-plugins-good,
> librsvg2-common (>= 2.18), python-cairo, ${misc:Depends}
> Suggests: gnucap, tuxpaint
> Replaces: gcompris-data (<< 8.4.1)
> Description: Educational games for small children
> diff -Nru gcompris-15.02/debian/patches/01_gstreamer-1.0.patch
> gcompris-15.02/debian/patches/01_gstreamer-1.0.patch
> --- gcompris-15.02/debian/patches/01_gstreamer-1.0.patch 1970-01-01
> 01:00:00.0 +0100
> +++ gcompris-15.02/debian/patches/01_gstreamer-1.0.patch 2015-09-20
> 20:28:27.0 +0200
> @@ -0,0 +1,11 @@
> +--- gcompris-15.02.orig/configure.ac
> gcompris-15.02/configure.ac
> +@@ -389,7 +389,7 @@ if test x$with_sdlmixer = xyes; then
> + AUDIO_LIBS="$AUDIO_LIBS -lSDL_mixer"
> + else
> + dnl Default is gstreamer
> +- PKG_CHECK_MODULES(AUDIO, gstreamer-0.10,, AC_MSG_ERROR([*** GSTREAMER not
> found!]))
> ++ PKG_CHECK_MODULES(AUDIO, gstreamer-1.0 gmodule-no-export-2.0,,
> AC_MSG_ERROR([*** GSTREAMER not found!]))
> + AC_DEFINE([USE_GSTREAMER], 1,[gstreamer is enabled])
> + fi
> + AC_SUBST(AUDIO_CFLAGS)
> diff -Nru gcompris-15.02/debian/patches/series
> gcompris-15.02/debian/patches/series
> --- gcompris-15.02/debian/patches/series 2014-12-30 18:12:20.0
> +0100
> +++ gcompris-15.02/debian/patches/series 2015-09-20 19:10:46.0
> +0200
> @@ -0,0 +1 @@
> +01_gstreamer-1.0.patch
> diff -Nru gcompris-15.02/debian/rules gcompris-15.02/debian/rules
> --- gcompris-15.02/debian/rules 2014-09-06 12:32:52.0 +0200
> +++ gcompris-15.02/debian/rules 2015-09-20 19:09:31.0 +0200
> @@ -10,7 +10,7 @@
> #export DH_VERBOSE=1
>
> %:
> - dh $@ --with autotools_dev --with python2
> + dh $@ --with autoreconf,autotools_dev --with python2
>
> SOUNDLANGS=$(shell grep '^Package: gcompris-sound-' debian/control | cut -d-
> -f3)
>
Bug#785840: gcompris: Please update to GStreamer 1.x
On Sun, Sep 20, 2015 at 02:55:35PM +0200, Sebastian Dröge wrote: > Hi, > > I forwarded this upstream a while ago without any response. Is gcompris still > actively developed? > https://bugzilla.gnome.org/show_bug.cgi?id=747949 Yes it is, although the current codebase is bound to get replaced by gcompris-qt (I have to resubmit a package for it), once all the boards have been ported. > Basically, replace the 0.10 build dependencies with 1.0. Then make things > compile and work again. See this small porting guide here > http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/random/porting-to-1.0.txt > > If you have any further questions please ask :) > > > If you can point me to the code that uses gstreamer, I can also take a short > look.
Bug#793137: tulip: FTBFS on armel and armhf - blocks testing migration
Submitted https://bugs.debian.org/798408 on libgles2-mesa-dev and libglew-dev, affecting those 2 FTBFS bugs.
Bug#793137: tulip: FTBFS on armel and armhf - blocks testing migration
On Tue, Jul 21, 2015 at 06:08:45PM +0200, Niels Thykier wrote: > Source: tulip > Version: 4.7.0dfsg-1 > Severity: serious > > The tulip package FTBFS on armel and armhf. Since it has built there > in the past, this is a regression and by extension prevents migration > to testing. Here is a (possibly) relevant part of the build log for > armhf. The first error to appear in the log, repeated several times, is: In file included from /usr/include/arm-linux-gnueabi/qt5/QtGui/qopengl.h:97:0, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qgl.h:39, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qglframebufferobject.h:37, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/QGLFramebufferObject:1, from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:26: /usr/include/GLES3/gl3.h:69:25: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr' typedef khronos_ssize_t GLsizeiptr; ^ In file included from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:24:0: /usr/include/GL/glew.h:1663:19: note: previous declaration as 'typedef ptrdiff_t GLsizeiptr' typedef ptrdiff_t GLsizeiptr; ^ Those look like conflicting declaration between 2 OpenGL headers, which on my amd64 box come from libgles2-mesa-dev and libglew-dev. Isn't there here an arm-specific mismatch between those 2 packages ?
Bug#783545: #783545
Hello, > The (annoyingly ever displayed) extra tab explains very well what should > be done, but I don’t get the Automatic Save Folder menu under the “What > should Firefox do with this file?” box. > > Am I missing something? I don't remember ever seing an "Automatic Save Folder" menu as long as I've used this extension, but the standard "save" menu does remember the save folders, according to file type, and other info. At least it always defaults to my datasheets/ folder when requesting to save a PDF datasheet, and my taxes/ folder when saving tax documents, and that still works with 38.0.1. The only annoying behaviour I see, is all those "help/update" tabs it opens in each open window, every time I restart FF. Is that what you're refering to with "(annoyingly ever displayed) extra tab" ? I stumbled onto this report while checking that very problem had not been reported already... Isn't there anything refering to that help/update.xhtml in the source ? Many other extensions display such a page once on upgrade, it should not be too hard to bring it in line with what others are doing ? Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742873: Patch for #742873
On Tue, Dec 16, 2014 at 05:05:53PM -0500, Yaroslav Halchenko wrote: > > On Sat, 15 Nov 2014, ydir...@free.fr wrote: > > > tags 742873 + patch > > thanks > > > Too bad it's too late for jessie... > > > >From 18bbc237763955c150da72daf9be2b9702fefb0a Mon Sep 17 00:00:00 2001 > > From: Yann Dirson > > Date: Sat, 15 Nov 2014 16:45:50 + > > Subject: [PATCH] Fix CVE-2013-1953 > > thanks for the patch -- would you mind uploading this NMU? or you need > sponsorship? I had meant to upload it, but somehow forgot, will do ! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772692: tau: More bashisms
On Sat, Dec 13, 2014 at 09:25:50AM +0100, Yann Dirson wrote: > On Wed, Dec 10, 2014 at 06:50:07AM +0100, Niels Thykier wrote: > > Package: tau > > Version: 2.17.3.1.dfsg-4 > > Severity: serious > > > > Hi, > > > > I saw you uploaded a new version of tau to fix bashisms. Unfortunately, > > there are still some left. > > > > E.g. in echoIfVerbose (tools/src/tau_compiler.sh) > > """ > > + if [ $isDebug == $TRUE ] || [ $isVerbose == $TRUE ]; then > > """ > > > > Which should have been using only one "=" in each of the [ ]. > > I'm a bit confused here: tools/src/tau_compiler.sh has been using bash > upstream since ages, and checkbashisms accordingly does not complain > on that file. I've been touching it in the "Replace 'echo -e'" patch > solely because I let sed do the work and did not bother checking that > it was absolutely necessary in all of the impacted scripts. I could > possibly remove that useless part of the patch to be on the extra-safe > side, but that seems unnecessary. > > OK to close this bug ? To be complete, the only remaining report from << find -name "*.sh"|xargs checkbashisms >> is a buggy "[^] should be [!]" about a sed regexp, and all files containing a ref to /bin/sh do have a name ending with .sh. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772692: tau: More bashisms
On Wed, Dec 10, 2014 at 06:50:07AM +0100, Niels Thykier wrote: > Package: tau > Version: 2.17.3.1.dfsg-4 > Severity: serious > > Hi, > > I saw you uploaded a new version of tau to fix bashisms. Unfortunately, > there are still some left. > > E.g. in echoIfVerbose (tools/src/tau_compiler.sh) > """ > + if [ $isDebug == $TRUE ] || [ $isVerbose == $TRUE ]; then > """ > > Which should have been using only one "=" in each of the [ ]. I'm a bit confused here: tools/src/tau_compiler.sh has been using bash upstream since ages, and checkbashisms accordingly does not complain on that file. I've been touching it in the "Replace 'echo -e'" patch solely because I let sed do the work and did not bother checking that it was absolutely necessary in all of the impacted scripts. I could possibly remove that useless part of the patch to be on the extra-safe side, but that seems unnecessary. OK to close this bug ? > I think the safe choice for Jessie would be to mark any remaining > scripts with bashisms as bash scripts. You can always properly fix them > in Stretch. Yes - the goal in stretch would be to make it possible to package the most recent version, anyway. Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: #726799: not a shared-mime-info bug726...@bugs.debian.org
On Sun, Sep 14, 2014 at 01:44:01PM +0200, Pino Toscano wrote: > On 2014-09-14 13:28, Yann Dirson wrote: > >On Sun, Sep 14, 2014 at 10:12:41AM +0200, Pino Toscano wrote: > >>Hi, > >> > >>first of all, the behaviour of update-mime-database is correct: it > >>deletes files in *generated* directories. > >> > >>Yes, the various application, audio, text, subdirectories under > >>/usr/share/mime are business of update-mime-database, where it places > >>the XML mimetypes generated from the XML definitions in > >>/usr/share/mime/packages. It is exactly in this directory where > >>applications should install XML definitions of mime types to have them > >>registered in the XDG mime type system. > >>Installing stuff directly to e.g. /usr/share/mime/text is like > >>installing to, say, /var/cache (i.e., you shouldn't). > >> > >>Furthermore, qgo is installing wrong things, and I will send the > >>proper explanation and fix to #749582. > >> > >>This is not a bug in shared-mime-info, hence closing. > > > >Ah, that's interesting. But then: > > > >* why are those directories in /usr/ and not in /var/ in the first > > place ? Isn't this part of the shared-mime-info spec against the > > spirit of the FHS ? > > Possibly, although changing at this point is not exactly an easy > task. Well, if it's just a cache, there should not be too much problems, I guess. If any of this has to be used externally (ie. has been made part of an official API), then probably symlinks to /var would have to be generated for some transition period - but we've been through a number of more disruptive transitions, I'd say :) > >* if it is deemed the right place for generated files, then we > > surely want a lintian check to spot the problem early > > Feel free to file a wishlist bug for lintian. Done. > >* the update-mime-database manpage is quite terse, and does not > > explain that different parts of MIME-DIR have different roles. > > It is awkward to have to read the spec to get such important > > information > > I guess you are referring to the update-mime-database man page, right? > This seems just specific to the tool itself, so IMHO what it lacks is > pointers to the specifications. > Another option would be having the specifications themselves as man > page. > > -- > Pino Toscano -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: #726799: not a shared-mime-info bug726...@bugs.debian.org
On Sun, Sep 14, 2014 at 10:12:41AM +0200, Pino Toscano wrote: > Hi, > > first of all, the behaviour of update-mime-database is correct: it > deletes files in *generated* directories. > > Yes, the various application, audio, text, subdirectories under > /usr/share/mime are business of update-mime-database, where it places > the XML mimetypes generated from the XML definitions in > /usr/share/mime/packages. It is exactly in this directory where > applications should install XML definitions of mime types to have them > registered in the XDG mime type system. > Installing stuff directly to e.g. /usr/share/mime/text is like > installing to, say, /var/cache (i.e., you shouldn't). > > Furthermore, qgo is installing wrong things, and I will send the > proper explanation and fix to #749582. > > This is not a bug in shared-mime-info, hence closing. Ah, that's interesting. But then: * why are those directories in /usr/ and not in /var/ in the first place ? Isn't this part of the shared-mime-info spec against the spirit of the FHS ? * if it is deemed the right place for generated files, then we surely want a lintian check to spot the problem early * the update-mime-database manpage is quite terse, and does not explain that different parts of MIME-DIR have different roles. It is awkward to have to read the spec to get such important information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753627: Please accept proposed patch for memtest86+ 5.01 or fix grave bug in anotger way
On Wed, Sep 10, 2014 at 11:02:02AM +0300, UAB 'Bona Mens' wrote: > > On Sun, Aug 31, 2014, Yann Dirson wrote: > > > If nobody has the detailed info, I'll try to find the time this week > > to identify the faulty flag. > > Please accept proposed patch for memtest86+ 5.01 or fix grave bug in > anotger way :) Right, it does not much good to wait - let's see how that one will break ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753627: memtest86+: Bug #753627 confirmed
On Sun, Aug 31, 2014 at 01:09:31AM +0100, Jose M Calhariz wrote: > > I can confirm the Bug. Following the discussion in > http://forum.canardpc.com/threads/83443-Memtest86-V5.01-crashes-with-gcc-4.7.2-or-later > reducing the optimization from -O1 to -O0 and a small patch to the > file io.h make memtest86 work again. Thanks for finding this! http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/4/SRPMS/core/release/memtest86+-5.01-5.mga4.src.rpm also have other interesting fixes, BTW. However I have issues with the patch: -O0 disables quite a lot of optimisations, and we surely don't want to disable all those that are not buggy. I haven't looked in depth, but the additional required changes are probably a consequence of this. Additionally, we don't even know what the gcc problem is, ir even if it has been reported to the gcc team. Having more detailed information would allow to link to 2 problems. If nobody has the detailed info, I'll try to find the time this week to identify the faulty flag. Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#753516: Acknowledgement (xscorch: fails to parse its data file)
tags 753516 + patch upstream
thanks
The problem is caused by a use of strcpy for overlapping regions.
Patch attached, uploading NMU to the DELAYED queue.
Description: Use memmove instead of memcpy for overlapping src/dst
Author: Yann Dirson
Bug-Debian: http://bugs.debian.org/753516
--- xscorch-0.2.1.orig/libj/jstr/str_trim.c
+++ xscorch-0.2.1/libj/jstr/str_trim.c
@@ -47,7 +47,7 @@ char *trim(char *s) {
SET_LAST_NWS(ws, s);
/* Copy the non-ws characters in . */
- if(ws.fnws > d) MEMCPY(d, ws.fnws, NWS_SIZE(ws));
+ if(ws.fnws > d) MEMMOVE(d, ws.fnws, NWS_SIZE(ws));
*(d + NWS_SIZE(ws)) = '\0';
return(d);
@@ -93,7 +93,7 @@ char *ltrim(char *s) {
if(s != NULL) {
SKIM_WHITESPACE(s);
- MEMCPY(d, s, STRLEN(s) + 1);
+ MEMMOVE(d, s, STRLEN(s) + 1);
return(d);
}
return(NULL);
Bug#753516: xscorch: fails to parse its data file
Package: xscorch Version: 0.2.1-1+b1 Severity: grave Not sure since when it started to fail, but it does not start up at all today: $ xscorch XScorch version 0.2.1 Copyright(c) 2000-2004 Justin David Smith Copyright(c) 2000-2009 Jacob Luna Lundberg Licensed under the GNU General Public License, version 2 See the Help menu for the license and a list of contributors. /usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 11 13 /usr/share/games/xscorch//profiles.def:9: error: Failed to add variable "tetRadius" to block "Standard"(7) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "mob": t true /usr/share/games/xscorch//profiles.def:11: error: Failed to add variable "mob" to block "Standard"(7) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 11 13 /usr/share/games/xscorch//profiles.def:24: error: Failed to add variable "tetRadius" to block "DoubleTrack"(22) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "efiency": 1 115 /usr/share/games/xscorch//profiles.def:26: error: Failed to add variable "efiency" to block "DoubleTrack"(22) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "hness": 99 90 /usr/share/games/xscorch//profiles.def:27: error: Failed to add variable "hness" to block "DoubleTrack"(22) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "mob": t true /usr/share/games/xscorch//profiles.def:28: error: Failed to add variable "mob" to block "DoubleTrack"(22) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "tetRadius": 11 13 /usr/share/games/xscorch//profiles.def:41: error: Failed to add variable "tetRadius" to block "Fortification"(39) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "haess": 1 125 /usr/share/games/xscorch//profiles.def:43: error: Failed to add variable "haess" to block "Fortification"(39) (continuable error) /usr/share/games/xscorch//profiles.def: error: Malformed value for "mobi": falsese /usr/share/games/xscorch//profiles.def:44: error: Failed to add variable "mobi" to block "Fortification"(39) (continuable error) /usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class in this context, for variable "Standard". /usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class in this context, for variable "DoubleTrack". /usr/share/games/xscorch//profiles.def: warning: "__null" isn't a valid class in this context, for variable "Fortification". config_new: failed to build tanks_profile, or no tanks in def file. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xscorch depends on: ii libatk1.0-0 2.12.0-1 ii libc62.19-4 ii libcairo21.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libmikmod3 3.3.6-2 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-01.36.3-1 Versions of packages xscorch recommends: ii xfonts-100dpi 1:1.0.3 xscorch suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml
found 726799 shared-mime-info/1.2-1 thanks On Sat, Jun 21, 2014 at 03:40:34PM +0200, intrigeri wrote: > Hi, > > is there any indication that this bug does *not* affect the version > currently in testing (1.2-1)? As impacting 1.0 and 1.3, it would be have been funny not to affect 1.2. Just downgraded it for a check, and I confirm 1.2-1 is impacted too. > If not, maybe we should mark it as affected too, so that this bug > doesn't block the migration of 1.3-1 to testing for wrong reasons. > > Cheers, > -- > intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734318: [amd64/g++] Suspected toolchain bug causing dlopen to segfault
Thanks much Aurelien for the analysis!
Just had a look, and there are several things to note:
* the cpuid calls occur from OGDF, and the latest snapshot still has
the same code
* the variables set using cpuid info are never used in the OGDF subset
shipped with tulip
* the code calling cpuid is inside "#if !defined(OGDF_DLL) ||
!defined(OGDF_SYSTEM_UNIX)". OGDF_DLL is defined only for win32 for
some reason, and strangely OGDF_SYSTEM_UNIX is not: we're apparently
just using that useless faulty code by mistake...
But setting OGDF_DLL causes other errors in basic.cpp: the case where
OGDF_DLL is defined but not OGDF_SYSTEM_WINDOWS is obviously missing
the closing brace for 'extern "C"' clause - this problem is fixed in
the latest OGDF snapshot (by removing this useless extra clause).
After all this, it finally builds, and as expected does not crash any
more.
On Tue, May 06, 2014 at 10:25:45PM +0200, Aurelien Jarno wrote:
> reassign 723982 tulip
> thanks
>
> On Sat, Feb 01, 2014 at 02:27:49PM +0100, Yann Dirson wrote:
> > [resend with bugs CC'd]
> >
> > Hello,
> >
> > Context:
> >
> > http://bugs.debian.org/734318 - tulip: [amd64] segfaults inside dlopen when
> > loading plugins
> > http://bugs.debian.org/723982 - dlopen: segfaults right inside call_init
> >
> > What we get here is a number of plugins that when dlopen'd cause an
> > obscure segfault inside libc code. Upstream (CC'd) say they have
> > heard of such problems (on Ubuntu 13.10), that people have worked
> > around by downgrading the compiler.
> >
> > This sounds like either a toolchain regression, or possibly some
> > edge-case that worked by chance with old compilers and now fail.
>
> This is exactly that the bug is in tulip and up to know it worked only by
> chance on x86_64. The segfault occurs in dl-init.c when call_init is
> calling all the init functions from DT_INIT_ARRAY. This is done in C by
> this code:
>
> | addrs = (ElfW(Addr) *) (init_array->d_un.d_ptr + l->l_addr);
> | for (j = 0; j < jm; ++j)
> |((init_t) addrs[j]) (argc, argv, env);
>
> which is translated in assembly code into:
>
> |0x77deb926 <+134>: lea0x8(%rbx,%rax,8),%r14
> |0x77deb92b <+139>: nopl 0x0(%rax,%rax,1)
> |0x77deb930 <+144>: mov%r13,%rdx
> |0x77deb933 <+147>: mov%r12,%rsi
> |0x77deb936 <+150>: mov%ebp,%edi
> |0x77deb938 <+152>: callq *(%rbx)
> |0x77deb93a <+154>: add$0x8,%rbx
> |0x77deb93e <+158>: cmp%r14,%rbx
> |0x77deb941 <+161>: jne0x77deb930
> |0x77deb943 <+163>: pop%rbx
> |0x77deb944 <+164>: pop%rbp
> |0x77deb945 <+165>: pop%r12
> |0x77deb947 <+167>: pop%r13
> |0x77deb949 <+169>: pop%r14
> |0x77deb94b <+171>: retq
>
>
> As you can see the value of addrs is stored in %rbx and is incremented
> by 8 at each loop. The segfault occurs at address 0x77deb938
> when trying to dereference %rbx. When it happens, %rbx has its upper
> 32 bits clobbered and thus point to the lower 32-bit of addrs[j].
>
> Tracing that with GDB, it appeared %rbx is clobbered in the System::init
> constructor from tulip. This code probes among other things uses the
> CPUID instruction using assembly code:
>
> |__asm__ __volatile__ ("xchgl%%ebx,%0\n\t"
> |"cpuid \n\t"
> |"xchgl %%ebx,%0\n\t"
> |: "+r" (b), "=a" (a), "=c"
> (c), "=d" (d)
> |: "1" (infoType), "2" (c));
>
> As you can see %ebx is saved with xchgl before the %cpuid instruction
> and restored after the same way. While that works correctly on x86, on
> x86_64 the 32 upper bits get zeroed. BOOM !
>
> I would suggest to use (which is available since GCC 4.4)
> instead of this buggy assembly code to probe the CPU. In the meantime I
> am reassigning the bug to tulip.
>
> Aurelien
>
> --
> Aurelien Jarno GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: Cannot reproduce, lowering severity
tags + 726799 unreproducible moreinfo severity 726799 important thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743729: ruby: badly handle transition away from alternatives, breaks dependant packages
reassign 743729 ruby retitle 743729 ruby: badly handles transition away from alternatives, breaks dependant packages found 743729 ruby/1:2.0.0.1 thanks The problem is not as simple as I originally thought (trused updatedb locate cache too much): strace reveals the ruby version for which debian_version is looking for is 1.8, and current ruby-debian only ships modules for 1.9.1 and 2.0.0. # ls -l /usr/bin/ruby lrwxrwxrwx 1 root root 22 Apr 5 18:15 /usr/bin/ruby -> /etc/alternatives/ruby # update-alternatives --config ruby There is only one alternative in link group ruby (providing /usr/bin/ruby): /usr/bin/ruby1.8 Nothing to configure. I guess the problem comes from stopping using alternatives, without properly declares a "Conflicts" with obsolete ruby versions ? Well, #740733 seems to show that this was done in the past, and this issue is already discussed in its followup... As for unbreaking the impacted machines: * purging ruby1.8 leaves the system without /usr/bin/ruby or any of the symlinks previously managed as alternatives * although those symlinks are still listed as part of the ruby package, no mechanism seems to prevent this deadly interference with alternatives * creating a ruby -> ruby2.0 manually allows to easily require reinstallation of the "ruby" package Isn't the real problem that dpkg allowed unpacking of conflicting symlinks in the first place ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743729: ruby-debian: lacks ruby2.0 support, breaks dependant packages
Even worse, the apt-listbugs hook is impacted, and prevents installation of any package: /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load -- debian_version (LoadError) from /usr/lib/ruby/vendor_ruby/debian.rb:24 from /usr/sbin/apt-listbugs:289:in `require' from /usr/sbin/apt-listbugs:289 E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (1) E: Failure running script /usr/sbin/apt-listbugs apt Failed to perform requested operation on package. Trying to recover: Press Return to continue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743729: ruby-debian: lacks ruby2.0 support, breaks dependant packages
Package: ruby-debian Version: 0.3.8+b2 Severity: grave I guess this should have been spotted before ruby2.0 reaches testing :} $ how-can-i-help /usr/lib/ruby/vendor_ruby/debian.rb:24:in `require': no such file to load -- debian_version (LoadError) from /usr/lib/ruby/vendor_ruby/debian.rb:24 from /usr/bin/how-can-i-help:20:in `require' from /usr/bin/how-can-i-help:20 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ruby-debian depends on: ii libapt-pkg4.120.9.16.1 ii libc6 2.18-4 ii libgcc1 1:4.8.2-16 ii libruby1.9.1 1.9.3.484-2 ii libruby2.02.0.0.484+really457-1 ii libstdc++64.8.2-16 ii ruby 1:2.0.0.1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-2 ii ruby2.0 [ruby-interpreter]2.0.0.484+really457-1 ruby-debian recommends no packages. ruby-debian suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741468: python-flufl.enum: includes symlink in docdir to contents of suggested -doc package
Package: python-flufl.enum Version: 3.3.2-1 Severity: serious /usr/share/doc/python-flufl.enum/rst is a symlink to html/_sources, which is even not installed by the -doc package, which puts everything under /usr/share/doc/python-flufl.enum-doc/. Instead, including a /usr/share/doc/python-flufl.enum/doc symlink to ../python-flufl.enum-doc/ in the -doc package itself would be much more interesting. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-flufl.enum depends on: ii python 2.7.5-5 ii python2.6 2.6.8-2 ii python2.7 2.7.6-7 python-flufl.enum recommends no packages. Versions of packages python-flufl.enum suggests: pn python-flufl.enum-doc -- 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#741132: lives: opening a file makes the program crash
seen 741132 2.2.0~ds0-1 thanks I can reproduce this problem in testing, with the mp4 fetched using youtube-dl from http://www.youtube.com/watch?v=wE3fmFTtP9g * when run as "lives foo.mp4" I get a dialog telling "LiVES was unable to open it" and the terminal window just says "failed" * when using the File/Open menu, I get the same crash. More precisely: Failed to open file - I tried: LANGUAGE=en LANG=en "/usr/bin/mplayer" -quiet -osdlevel 0 -vo png:z=1:alpha -lavdopts o=threads=4 -noframedrop -ao pcm:fast:nowaveheader -mc 0 "WildCat-wE3fmFTtP9g.mp4" https://lists.ffmpeg.org/pipermail/ffmpeg-cvslog/2011-August/039866.html LiVES could be trying to use an old API call, but I don't see anything about that in the libavformat changelog. I could downgrade to 2.0.6~ds0-2 and open the file through "File/Open", but still get the same puzzling behaviour when requesting the file on commandline. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740111: Fixed in unstable
fixed 740111 1.4.2-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740111: Fixed in unstable
notfound 740111 1.4.2-1 thanks The problem does not happen with 1.4.2-1, currently in unstable. Works well with both openjdk 6 and 7. Sidenote: trying to install 1.4-3~deb7u2, it wanted to deinstall icedtea-6-plugin, so I did not test that one after all. Isn't that another bug ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740111: icedtea-netx: NullPointerException in SwingUtilities.appContextGet
Package: icedtea-netx Version: 1.3.2-1 Severity: serious Tring to understand why the KGS Go client at http://files.gokgs.com/javaBin/cgoban.jnlp would not start: * default javaws (using openjdk-6) even explodes when passed no argument: $ /usr/lib/jvm/java-6-openjdk-amd64/bin/javaws Exception in thread "main" java.lang.NullPointerException at javax.swing.SwingUtilities.appContextGet(SwingUtilities.java:1859) at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1829) at javax.swing.JWindow.(JWindow.java:185) at javax.swing.JWindow.(JWindow.java:137) at net.sourceforge.jnlp.runtime.JNLPSecurityManager.(JNLPSecurityManager.java:121) at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:231) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:181) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:51) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:172) * using openjdk-7, the same call produces a usage message, but when launching against cgoban.jnlp the same NPE occurs, so I guess it is not specific to this particular app (hence the severity): $ /usr/lib/jvm/java-7-openjdk-amd64/bin/javaws /tmp/cgoban.jnlp Exception in thread "main" java.lang.NullPointerException at javax.swing.SwingUtilities.appContextGet(SwingUtilities.java:1859) at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1829) at javax.swing.JWindow.(JWindow.java:185) at javax.swing.JWindow.(JWindow.java:137) at net.sourceforge.jnlp.runtime.JNLPSecurityManager.(JNLPSecurityManager.java:121) at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:231) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:181) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:51) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:172) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.3.2-1 ii openjdk-6-jre6b30-1.13.1-1 ii openjdk-7-jre7u21-2.3.9-5 icedtea-netx recommends no packages. icedtea-netx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml
Hi Andreas, Did you find the time systemtap this issue ? On Fri, Jan 10, 2014 at 10:41:39PM +0100, Yann Dirson wrote: > Hi Andreas, > > On Fri, Dec 13, 2013 at 11:11:32PM +0100, Yann Dirson wrote: > > On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote: > > > On 2013-12-03 22:30, Yann Dirson wrote: > > > > I'm wondering if that could not be caused by a bug in the mime > > > > trigger, that would have been fixed already. > > > > > > That would be easier to test - what package is it? > > > > I was thinking about the mime-support trigger, but that package has > > not been changed for 6 months, so the problem must be somewhere else. > > > > > > Can you please retry the test, > > > > > > reproducible in jessie-> sid and wheezy->sid updates to version > > > 2.0~git-20131123-1 > > > > > > > and if it still fails, run it while the > > > > following stap script is running: > > > > > > That may take some time ... I'll need to rerun the piuparts test > > > manually in a chroot ... and on a different machine ... > > Any news on your side ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734318: [amd64/g++] Suspected toolchain bug causing dlopen to segfault
[resend with bugs CC'd] Hello, Context: http://bugs.debian.org/734318 - tulip: [amd64] segfaults inside dlopen when loading plugins http://bugs.debian.org/723982 - dlopen: segfaults right inside call_init What we get here is a number of plugins that when dlopen'd cause an obscure segfault inside libc code. Upstream (CC'd) say they have heard of such problems (on Ubuntu 13.10), that people have worked around by downgrading the compiler. This sounds like either a toolchain regression, or possibly some edge-case that worked by chance with old compilers and now fail. Any insights ? Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735121: [tulip] Non free files
On Sun, Jan 12, 2014 at 09:46:19PM +, bastien ROUCARIES wrote: > Package: tulip > Severity: serious > x-cc-debug: ftpmas...@ftp-master.debian.org > > The following file are not free: Gasp. Those bundle-everything project are a real hell to maintain... I'll nuke those fonts from the orig tarball. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml
Hi Andreas, On Fri, Dec 13, 2013 at 11:11:32PM +0100, Yann Dirson wrote: > On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote: > > On 2013-12-03 22:30, Yann Dirson wrote: > > > I'm wondering if that could not be caused by a bug in the mime > > > trigger, that would have been fixed already. > > > > That would be easier to test - what package is it? > > I was thinking about the mime-support trigger, but that package has > not been changed for 6 months, so the problem must be somewhere else. > > > > Can you please retry the test, > > > > reproducible in jessie-> sid and wheezy->sid updates to version > > 2.0~git-20131123-1 > > > > > and if it still fails, run it while the > > > following stap script is running: > > > > That may take some time ... I'll need to rerun the piuparts test > > manually in a chroot ... and on a different machine ... Any news on your side ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734318: tulip: [amd64] segfaults inside dlopen when loading plugins
Package: tulip Version: 4.4.0dfsg-1 Severity: serious This happens on amd64, but not in an i386 chroot, or when running the i386 binary on an amd64 machine. See http://bugs.debian.org/723982 for what's happening inside the dlopen call. With an additional trace to identify the plugin being loaded we get: | loadPlugins info: /home/yann/.local/share/data//Tulip 4.4/plugins//lib/tulip/ - No such file or directory | [Thread 0x7fffe6c7a700 (LWP 29463) exited] | dlopening '/usr/lib/../lib/tulip//libreverseedges-4.4.0.so' aka '/usr/lib/../lib/tulip//libreverseedges-4.4.0.so' | dlopening '/usr/lib/../lib/tulip//libogdfvisibility-4.4.0.so' aka '/usr/lib/../lib/tulip//libogdfvisibility-4.4.0.so' | | Program received signal SIGSEGV, Segmentation fault. | | (gdb) bt | #0 0x77de99c4 in call_init (env=0x7fffdd28, argv=0x7fffdd18, argc=1, l=) at dl-init.c:84 | #1 call_init (l=, argc=1, argv=0x7fffdd18, env=0x7fffdd28) at dl-init.c:34 | #2 0x77de9aaa in _dl_init (main_map=main_map@entry=0x822a40, argc=1, argv=0x7fffdd18, env=0x7fffdd28) at dl-init.c:133 | #3 0x77dedb09 in dl_open_worker (a=a@entry=0x7fffd2d8) at dl-open.c:577 | #4 0x77de9806 in _dl_catch_error (objname=objname@entry=0x7fffd2c8, errstring=errstring@entry=0x7fffd2d0, mallocedp=mallocedp@entry=0x7fffd2c7, | operate=operate@entry=0x77ded790 , args=args@entry=0x7fffd2d8) at dl-error.c:177 | #5 0x77ded339 in _dl_open (file=0x71d648 "/usr/lib/../lib/tulip//libogdfvisibility-4.4.0.so", mode=-2147483646, caller_dlopen=, nsid=-2, argc=1, argv=0x7fffdd18, | env=0x7fffdd28) at dl-open.c:667 | #6 0x71c7b026 in dlopen_doit (a=a@entry=0x7fffd4e0) at dlopen.c:66 | #7 0x77de9806 in _dl_catch_error (objname=0x6b56e0, errstring=0x6b56e8, mallocedp=0x6b56d8, operate=0x71c7afc0 , args=0x7fffd4e0) at dl-error.c:177 | #8 0x71c7b5ec in _dlerror_run (operate=operate@entry=0x71c7afc0 , args=args@entry=0x7fffd4e0) at dlerror.c:163 | #9 0x71c7b0c1 in __dlopen (file=, mode=) at dlopen.c:87 | #10 0x77aa6194 in tlp::PluginLibraryLoader::loadPluginLibrary (filename=..., loader=loader@entry=0x7900d0) | at /work/yann/deb/tulip/tulip/library/tulip-core/src/PluginLibraryLoader.cpp:121 | #11 0x77aa63ea in tlp::PluginLibraryLoader::initPluginDir (this=0x698030, loader=loader@entry=0x7900d0) | at /work/yann/deb/tulip/tulip/library/tulip-core/src/PluginLibraryLoader.cpp:261 | #12 0x77aa73d4 in tlp::PluginLibraryLoader::loadPlugins (loader=loader@entry=0x7900d0, folder=...) at /work/yann/deb/tulip/tulip/library/tulip-core/src/PluginLibraryLoader.cpp:67 | #13 0x77593ac8 in tlp::initTulipSoftware (loader=loader@entry=0x7900d0, removeDiscardedPlugins=removeDiscardedPlugins@entry=true) | at /work/yann/deb/tulip/tulip/library/tulip-gui/src/TlpQtTools.cpp:211 | #14 0x0041cb56 in main (argc=1, argv=) at /work/yann/deb/tulip/tulip/software/tulip/src/main.cpp:169 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tulip depends on: ii binutils 2.24-2 ii libc6 2.17-97 ii libfreetype6 2.5.2-1 ii libftgl2 2.1.3~rc5-4+nmu1 ii libgcc1 1:4.8.2-10 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglew1.10 1.10.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libgzstream-tulip4.4.04.4.0dfsg-1 ii libogdf-tulip4.4.04.4.0dfsg-1 ii libpython2.7 2.7.6-4 ii libqt4-network4:4.8.5+git192-g085f851+dfsg-2 ii libqt4-opengl 4:4.8.5+git192-g085f851+dfsg-2 ii libqt4-xml4:4.8.5+git192-g085f851+dfsg-2 ii libqt4-xmlpatterns4:4.8.5+git192-g085f851+dfsg-2 ii libqtcore44:4.8.5+git192-g085f851+dfsg-2 ii libqtgui4 4:4.8.5+git192-g085f851+dfsg-2 ii libqtwebkit4 2.2.1-7 ii libquazip-tulip4.4.0 4.4.0dfsg-1 ii libqxt-tulip4.4.0 4.4.0dfsg-1 ii libstdc++64.8.2-10 ii libtulip-core-4.4 4.4.0dfsg-1 ii libtulip-gui-4.4 4.4.0dfsg-1 ii libtulip-ogdf-4.4 4.4.0dfsg-1 ii libtulip-ogl-4.4 4.4.0dfsg-1 ii libtulip-python-4.4 4.4.0dfsg-1 ii libyajl-tulip4.4.04.4.0dfsg-1 ii ttf-dejavu-core 2.33+svn2514-3 ii zlib1g1:1.2.8.dfsg-1 tulip recommends no packages. tulip suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact
Bug#718100: ftgl: diff for NMU version 2.1.3~rc5-4+nmu1
tags 697863 + pending
tags 701732 + pending
tags 718100 + patch
tags 718100 + pending
tags 734159 + patch
tags 734159 + pending
thanks
Dear maintainer,
I've prepared an NMU for ftgl (versioned as 2.1.3~rc5-4+nmu1) and
uploaded it to DELAYED/8. Please feel free to tell me if I
should delay it longer.
Note: a collab-maint repo would have allowed me to independently
commit diffs for all changes.
Regards.
diff -Nru ftgl-2.1.3~rc5/debian/changelog ftgl-2.1.3~rc5/debian/changelog
--- ftgl-2.1.3~rc5/debian/changelog 2011-11-26 11:15:46.0 +0100
+++ ftgl-2.1.3~rc5/debian/changelog 2014-01-05 17:20:22.0 +0100
@@ -1,3 +1,15 @@
+ftgl (2.1.3~rc5-4+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS at generation of pdf doc (Closes: #718100).
+ * Switch to multiarch (Closes: #734159), but don't mark the -dev package
+as such, as it was not tested as such.
+ * Include debian/watch from Nick Black (Closes: #697863).
+ * Update libtool at build time using dh-autoreconf, in order to fix a
+build failure on x32 (Daniel Schepler, Closes: #701732).
+
+ -- Yann Dirson Sun, 05 Jan 2014 17:20:22 +0100
+
ftgl (2.1.3~rc5-4) unstable; urgency=low
* drop doxygen and texlive-* (except texlive-fonts-recommended) and
diff -Nru ftgl-2.1.3~rc5/debian/control ftgl-2.1.3~rc5/debian/control
--- ftgl-2.1.3~rc5/debian/control 2011-11-26 11:09:37.0 +0100
+++ ftgl-2.1.3~rc5/debian/control 2014-01-05 17:17:32.0 +0100
@@ -2,7 +2,7 @@
Section: libs
Priority: optional
Maintainer: Sam Hocevar
-Build-Depends: debhelper (>= 5.0), quilt, libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev, libfreetype6-dev (>> 2.0.9), doxygen-latex, freeglut3-dev, libcppunit-dev, imagemagick, texlive-fonts-recommended, ghostscript
+Build-Depends: debhelper (>= 8.1.3), quilt, libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev, libfreetype6-dev (>> 2.0.9), doxygen-latex, freeglut3-dev, libcppunit-dev, imagemagick, texlive-fonts-recommended, ghostscript, dh-autoreconf
Standards-Version: 3.9.2
Vcs-Svn: svn://svn.debian.org/sam-hocevar/pkg-misc/unstable/ftgl
Vcs-Browser: http://svn.debian.org/wsvn/sam-hocevar/pkg-misc/unstable/ftgl/
@@ -24,7 +24,9 @@
Package: libftgl2
Section: libs
Architecture: any
+Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
+Pre-Depends: ${misc:Pre-Depends}
Description: library to render text in OpenGL using FreeType
FTGL binds OpenGL and FreeType together in order to offer and easy to use
and flexible text rendering library. It offers several rendering modes:
diff -Nru ftgl-2.1.3~rc5/debian/libftgl-dev.install ftgl-2.1.3~rc5/debian/libftgl-dev.install
--- ftgl-2.1.3~rc5/debian/libftgl-dev.install 2008-06-15 17:28:51.0 +0200
+++ ftgl-2.1.3~rc5/debian/libftgl-dev.install 2014-01-04 14:30:54.0 +0100
@@ -1,7 +1,7 @@
usr/include
-usr/lib/lib*.a
-usr/lib/lib*.so
-usr/lib/pkgconfig/*.pc
+usr/lib/*/lib*.a
+usr/lib/*/lib*.so
+usr/lib/*/pkgconfig/*.pc
usr/share/doc/libftgl-dev/html
usr/share/doc/libftgl-dev/ftgl.pdf
usr/share/doc/libftgl-dev/*.txt
diff -Nru ftgl-2.1.3~rc5/debian/libftgl2.install ftgl-2.1.3~rc5/debian/libftgl2.install
--- ftgl-2.1.3~rc5/debian/libftgl2.install 2008-06-15 17:28:51.0 +0200
+++ ftgl-2.1.3~rc5/debian/libftgl2.install 2014-01-04 14:29:45.0 +0100
@@ -1 +1 @@
-usr/lib/lib*.so.*
+usr/lib/*/lib*.so.*
diff -Nru ftgl-2.1.3~rc5/debian/patches/fix-pdf-generation ftgl-2.1.3~rc5/debian/patches/fix-pdf-generation
--- ftgl-2.1.3~rc5/debian/patches/fix-pdf-generation 1970-01-01 01:00:00.0 +0100
+++ ftgl-2.1.3~rc5/debian/patches/fix-pdf-generation 2014-01-04 16:25:45.0 +0100
@@ -0,0 +1,33 @@
+Description: Fix PDF refman generation
+ This just remove a pre-latex-processing hack that just breaks nowadays.
+ The Makefile.in was updated by hand, since autostuff is way old and
+ apparently more work is needed to make regeneration work properly.
+Author: Yann Dirson
+Bug-Debian: http://bugs.debian.org/718100
+
+--- ftgl-2.1.3~rc5.orig/docs/Makefile.am
ftgl-2.1.3~rc5/docs/Makefile.am
+@@ -33,9 +33,7 @@ stamp-doxygen: doxygen.cfg stamp-eps
+
+ latex/ftgl.pdf: stamp-latex
+ stamp-latex: stamp-doxygen
+- rm -f latex/ftgl.tex latex/ftgl.pdf
+- mv latex/refman.tex latex/ftgl.tex
+- sed 's/setlength{/renewcommand{/' latex/ftgl.tex > latex/refman.tex
++ rm -f latex/ftgl.pdf
+ cd latex && $(MAKE) $(AM_CFLAGS) refman.pdf || (cat refman.log; exit 1)
+ mv latex/refman.pdf latex/ftgl.pdf
+ touch stamp-latex
+--- ftgl-2.1.3~rc5.orig/docs/Makefile.in
ftgl-2.1.3~rc5/docs/Makefile.in
+@@ -460,9 +460,7 @@ stamp-doxygen: doxygen.cfg stamp-eps
+
+ latex/ftgl.pdf: stamp-latex
+ stamp-latex: stamp-doxygen
+- rm -f latex/ftgl.tex latex/ftgl.pdf
+- mv latex/refman.tex latex/ftgl.tex
+- sed 's/setlength{/renewcommand{/' latex/ftgl.tex > latex/refman.tex
++ rm -f latex/ftgl.pdf
+ cd latex && $(MAKE) $(AM_CFLAGS) refman
Bug#718100: ftgl: FTBFS: manual build failed
The log shows:
| LaTeX Warning: There were undefined references.
|
| LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
As warnings, they could be innocuous (although the 1st one remains
even if we force the latex runs, and probably should not be there
anyway), but there loads of other strange things starting with:
| ! Missing number, treated as zero.
|
|\relax
| l.104 \begin{center}
| %
| A number should have been here; I inserted `0'.
| (If you can't figure out why I needed to see a number,
| look up `weird error' in the index to The TeXbook.)
... and latex inserts lots of "Ocm" and similar texts as printable in
the pdf, the first of which seems to occur within the "\begin{center}"
expansion in refman.tex:
| %= C O N T E N T S =
|
| \begin{document}
|
| % Titlepage & ToC
| \pagenumbering{roman}
| \begin{titlepage}
| \vspace*{7cm}
| \begin{center}%
| {\Large F\-T\-G\-L \\[1ex]\large 2.\-1.\-3$\sim$rc5 }\\
In fact the problem seems to stem with a strange processing done on
doxygen output before feeding it to latex:
mv latex/refman.tex latex/ftgl.tex
sed 's/setlength{/renewcommand{/' latex/ftgl.tex > latex/refman.tex
Getting rid of those lines allows the build to proceed, but that
requires autoreconfiguration. Will push a fix to svn if I can get
something clean.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734170: ftgl: "make clean" fails
Package: libftgl2 Version: 2.1.3~rc5-4 Severity: serious $ debuild clean dh_testdir dh_testroot rm -f build-stamp configure-stamp [ ! -f Makefile ] || /usr/bin/make distclean make[1]: Entering directory `/work/yann/deb/tulip/ftgl-2.1.3~rc5' Making distclean in msvc make[2]: Entering directory `/work/yann/deb/tulip/ftgl-2.1.3~rc5/msvc' make[2]: *** No rule to make target `distclean'. Stop. make[2]: Leaving directory `/work/yann/deb/tulip/ftgl-2.1.3~rc5/msvc' make[1]: *** [distclean-recursive] Error 1 make[1]: Leaving directory `/work/yann/deb/tulip/ftgl-2.1.3~rc5' make: *** [clean] Error 2 debuild: fatal error at line 1346: couldn't exec fakeroot debian/rules: The use of "SUBDIRS" is obviously violating the way automake should be used. Adding "msvc" to SUBDIRS at it probably should is probably enough, given the lack of build targets in this dir. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libftgl2 depends on: ii libc6 2.17-97 ii libfreetype6 2.5.1-1 ii libgcc1 1:4.8.2-10 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libstdc++64.8.2-10 ii zlib1g1:1.2.8.dfsg-1 libftgl2 recommends no packages. libftgl2 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml
On Fri, Dec 13, 2013 at 01:58:31AM +0100, Andreas Beckmann wrote: > On 2013-12-03 22:30, Yann Dirson wrote: > > I'm wondering if that could not be caused by a bug in the mime > > trigger, that would have been fixed already. > > That would be easier to test - what package is it? I was thinking about the mime-support trigger, but that package has not been changed for 6 months, so the problem must be somewhere else. > > Can you please retry the test, > > reproducible in jessie-> sid and wheezy->sid updates to version > 2.0~git-20131123-1 > > > and if it still fails, run it while the > > following stap script is running: > > That may take some time ... I'll need to rerun the piuparts test > manually in a chroot ... and on a different machine ... OK -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml
On Sat, Oct 19, 2013 at 01:09:39PM +0200, Andreas Beckmann wrote:
> Package: qgo
> Version: 2.0~git-20130914-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package deletes one of its
> shipped files during upgrades.
>
> debsums reports modification of the following files,
> from the attached log (scroll to the bottom...):
>
> 0m50.7s ERROR: FAIL: debsums reports modifications inside the chroot:
> debsums: missing file /usr/share/mime/text/x-sgf.xml (from qgo
> package)
This is very strange. When I started to investigate, that file had
disappeared from my system too, so it looks like there *is* a bug
somewhere.
However, after reinstalling the testing version, then upgrading to the
sid one, then reinstalling the sid version (under supervision of a
stap script sending SIGSTOP to anyone unlinking that file), I could
not reproduce the problem: only dpkg itself ever gets caught, once,
unlinking the file, which looks reasonable, and the file is there at
the end of the run.
I'm wondering if that could not be caused by a bug in the mime
trigger, that would have been fixed already.
Can you please retry the test, and if it still fails, run it while the
following stap script is running:
--- >8 --- sgf.stap ---
probe begin { println("go...") }
probe syscall.unlink {
if (isinstr(pathname, "/x-sgf.xml")) {
println("unlink ", kernel_string($pathname))
printf("process traceback:\n %s\n", pstrace(task_current()))
raise(19) # SIGSTOP
}
}
--- >8 ---
(run as "stap -g sgf.stap" as a user in groups stapdev and stapusr,
with the linux-image-*-dbg matching you running kernel installed)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729738: arguments in macro changed
Hi,
I have started to work on tulip 4.x, but the resulting binary from the
4.3 package (source in git on alioth) is completely unusable, and I
have not located the problem yet. 4.4 has been released recently,
I'll update and we'll see...
(that is, don't spend too much time on 3.7 :)
On Sat, Nov 23, 2013 at 12:57:29PM +0100, Andreas B. Mundt wrote:
> Hi,
>
> the number of arguments in QT4_CREATE_MOC_COMMAND seems to have
> changed [1]. I tried to fix this by applying the following patch:
>
> --- tulip-3.7.0dfsg.orig/UseTulip.cmake
> +++ tulip-3.7.0dfsg/UseTulip.cmake
> @@ -47,7 +47,7 @@ MACRO (TULIP_QT4_WRAP_CPP outfiles )
> GET_FILENAME_COMPONENT(outfile ${it} NAME_WE)
> GET_FILENAME_COMPONENT(it ${it} ABSOLUTE)
> SET(outfile ${CMAKE_CURRENT_BINARY_DIR}/moc_${outfile}.cpp)
> -QT4_CREATE_MOC_COMMAND(${it} ${outfile} "${moc_flags}" "${moc_options}")
> +QT4_CREATE_MOC_COMMAND(${it} ${outfile} "${moc_flags}" "${moc_options}"
> "${moc_target}")
> SET(${outfiles} ${${outfiles}} ${outfile})
>ENDFOREACH(it)
> ENDMACRO (TULIP_QT4_WRAP_CPP)
> --- tulip-3.7.0dfsg.orig/FindTULIP3.cmake
> +++ tulip-3.7.0dfsg/FindTULIP3.cmake
> @@ -228,7 +228,7 @@ MACRO (TULIP_QT4_WRAP_CPP outfiles )
> GET_FILENAME_COMPONENT(outfile ${it} NAME_WE)
> GET_FILENAME_COMPONENT(it ${it} ABSOLUTE)
> SET(outfile ${CMAKE_CURRENT_BINARY_DIR}/moc_${outfile}.cpp)
> -QT4_CREATE_MOC_COMMAND(${it} ${outfile} "${moc_flags}" "${moc_options}")
> +QT4_CREATE_MOC_COMMAND(${it} ${outfile} "${moc_flags}" "${moc_options}"
> "${moc_target}")
> SET(${outfiles} ${${outfiles}} ${outfile})
>ENDFOREACH(it)
> ENDMACRO (TULIP_QT4_WRAP_CPP)
>
> However, the build still fails (perhaps) unrelated, see below. As I
> have no idea about cmake and my machine takes ages to compile the
> sources, I stop here for the time being and hope the provided
> information is helpful to fix this thoroughly.
>
> Best Regards,
>
> Andi
>
>
> [1]
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9ce60ff509c4ff27fe861fc5b2080f50897a68c4>
>
>
> 8<
> [ 62%] Building CXX object
> library/tulip-qt/src/CMakeFiles/tulip-qt4-3.7.dir/MainController.cpp.o
> cd /tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu/library/tulip-qt/src
> && /usr/bin/c++ -DQT_CORE_LIB -DQT_DLL -DQT_GUI_LIB -DQT_NO_DEBUG
> -DQT_OPENGL_LIB -DQT_THREAD_SUPPORT -Dtulip_qt4_3_7_EXPORTS -g -O2
> -fstack-protector --param=ssp-buffer-size=4 -Wformat
> -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wunused
> -DHAVE_LIBJPEG -DHAVE_LIBPNG -D_LINUX -DQT_ASSISTANT='"assistant"'
> -DI64 -Wno-deprecated -Wno-deprecated-declarations -O2 -g -DNDEBUG
> -fPIC -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtGui
> -isystem /usr/include/qt4/QtCore -isystem /usr/include/qt4/QtOpenGL
> -I/tmp/buildd/tulip-3.7.0dfsg/library/tulip-qt/src/../include
> -I/tmp/buildd/tulip-3.7.0dfsg/library/tulip-qt/src/../include/tulip
> -I/tmp/buildd/tulip-3.7.0dfsg/library/tulip/include
> -I/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu/library/tulip/include
> -I/tmp/buildd/tulip-3.7.0dfsg/library/tulip-ogl/include
> -I/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu/library/tulip-qt/include
> -I/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu/library/tulip-qt/include/tulip
> -o CMakeFiles/tulip-qt4-3.7.dir/MainController.cpp.o -c
> /tmp/buildd/tulip-3.7.0dfsg/library/tulip-qt/src/MainController.cpp
> In file included from
> /tmp/buildd/tulip-3.7.0dfsg/library/tulip-qt/src/MainController.cpp:51:0:
> /tmp/buildd/tulip-3.7.0dfsg/library/tulip-qt/src/../include/tulip/TabWidget.h:33:33:
> fatal error: tulip/TabWidgetData.h: No such file or directory
> #include "tulip/TabWidgetData.h"
> ^
> compilation terminated.
> make[4]: ***
> [library/tulip-qt/src/CMakeFiles/tulip-qt4-3.7.dir/MainController.cpp.o]
> Error 1
> make[4]: Leaving directory
> `/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu'
> make[3]: *** [library/tulip-qt/src/CMakeFiles/tulip-qt4-3.7.dir/all]
> Error 2
> make[3]: Leaving directory
> `/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/tmp/buildd/tulip-3.7.0dfsg/obj-x86_64-linux-gnu'
> dh_auto_build: make -j1 returned exit code 2
> make[1]: *** [override_dh_auto_build-arch] Error 2
> make[1]: Leaving directory `/tmp/buildd/tulip-3.7.0dfsg'
> make: *** [binary] Error 2
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729987: lives: missing dep on libmjpegutils-2.1-0
Package: lives Version: 2.0.6~ds0-1 Severity: serious $ lives test.mov /usr/lib/lives/lives-exe: error while loading shared libraries: libmjpegutils-2.1.so.0: cannot open shared object file: No such file or directory Installing libmjpegutils-2.1-0 fixes the problem. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lives depends on: ii frei0r-plugins1.1.22git20091109-1.4 ii imagemagick 8:6.7.7.10-6 ii libasound21.0.27.2-3 ii libatk1.0-0 2.10.0-2 ii libavc1394-0 0.5.4-2 ii libavcodec54 6:9.10-1 ii libavformat54 6:9.10-1 ii libavutil52 6:9.10-1 ii libc6 2.17-93 ii libcairo-gobject2 1.12.16-2 ii libcairo2 1.12.16-2 ii libdv41.0.0-6 ii libgcc1 1:4.8.2-1 ii libgdk-pixbuf2.0-02.28.2-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglee0d15.4.0-2 ii libglib2.0-0 2.36.4-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgtk-3-03.8.4-1 ii libjack-jackd2-0 [libjack-0.116] 1.9.9.5+20130622git7de15e7a-1 ii libmjpegutils-2.0-0 1:2.0.0+debian-2 ii libogg0 1.3.1-1 ii liboil0.3 0.3.17-2 ii libpango-1.0-01.36.0-1 ii libpangocairo-1.0-0 1.36.0-1 ii libpng12-01.2.49-5 ii libpulse0 4.0-6+b1 ii libraw1394-11 2.1.0-1 ii libsdl1.2debian 1.2.15-8 ii libstdc++64.8.2-1 ii libswscale2 6:9.10-1 ii libtheora01.1.1+dfsg.1-3.1 ii libunicap20.9.12-2 ii libweed0 2.0.6~ds0-1 ii libx11-6 2:1.6.2-1 ii libxrender1 1:0.9.8-1 ii lives-data2.0.6~ds0-1 ii mplayer 2:1.0~rc4.dfsg1+svn34540-1+b2 ii ogmtools 1:1.5-3+b1 ii perl 5.18.1-4 ii procps1:3.3.4-2 ii python2.7.5-5 ii sox 14.4.1-3 ii zlib1g1:1.2.8.dfsg-1 Versions of packages lives recommends: pn dvgrab pn icedax ii libtheora-bin 1.1.1+dfsg.1-3.1 ii mencoder 2:1.0~rc4.dfsg1+svn34540-1+b2 pn mkvtoolnix ii pulseaudio 4.0-6+b1 ii x11-utils 7.7+1 ii youtube-dl 2013.10.23-1 Versions of packages lives suggests: ii ffmpeg 6:0.8.9-1 pn libdv-bin pn mjpegtools -- 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#666525: trying to disable ccache locally, failing
tags 666525 + patch
thanks
On Sat, Aug 31, 2013 at 06:42:01PM +0200, Joel Rosdahl wrote:
> Hi,
>
> > ccache seems to ignore the request [...] Is there some ccache subtlety
> I'm missing?
>
> ccache doesn't ignore the request, it just happens to make sure that the
> ccache directory exists before reacting to CCACHE_DISABLE (or
> CCACHE_READONLY)... Looks like it has been that way since day one (well,
> day two, actually:
> http://gitweb.samba.org/?p=ccache.git;a=commit;h=10920460b5b00b77316602eb4e7c998a80464a88
> ).
>
> I've fixed the bug now (upstream), but there's no workaround in currently
> released ccache versions, I'm afraid.
Well, here is one that, although arguably kludgy, does works for me:
simply forcing the dpkg-architecture run to write somewhere else.
--- /usr/lib/pbuilder/pbuilder-satisfydepends.orig 2013-08-29
23:34:32.0 +0200
+++ /usr/lib/pbuilder/pbuilder-satisfydepends 2013-08-31 19:35:14.0
+0200
@@ -59,7 +59,7 @@
function checkbuilddep_internal () {
# Use this function to fulfill the dependency (almost)
-local ARCH=$($CHROOTEXEC dpkg-architecture -qDEB_HOST_ARCH)
+local ARCH=$($CHROOTEXEC env CCACHE_DIR=${TMPDIR:-/tmp}/faraway/ccache
dpkg-architecture -qDEB_HOST_ARCH)
local BUILD_DEP_DEB_DIR
local BUILD_DEP_DEB_CONTROL
local DEPENDS
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#713764: gcompris: FTBFS: rsvg-cairo.h:27:2: error: #warning "Including directly is deprecated." [-Werror=cpp]
On Sat, Jun 22, 2013 at 03:27:50PM +0200, David Suárez wrote: > Source: gcompris > Version: 12.01-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20130620 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[5]: Entering directory `/«PKGBUILDDIR»/src/algebra_by-activity' > > CC algebra.lo > > In file included from ../../src/goocanvas/src/goocanvassvg.h:13:0, > > from ../../src/goocanvas/src/goocanvas.h:22, > > from ../../src/gcompris/gcompris.h:26, > > from algebra.c:22: > > /usr/include/librsvg-2.0/librsvg/rsvg-cairo.h:27:2: error: #warning > > "Including directly is deprecated." [-Werror=cpp] > > #warning "Including directly is deprecated." > > ^ > > cc1: all warnings being treated as errors > > make[5]: *** [algebra.lo] Error 1 > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. Hm, did you inject -Werror through dpkg-buildflags ? In pbuilder I get the warning for 12.11-1 as well but there is no -Werror to make it fatal. Makes me wonder if this qualifies for FTBFS at all... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666525: trying to disable ccache locally, failing
By tuning the stap script to SIGSTOP the offending process, we can get
a much better view of the situation - here using pstree:
pbuilder,4611 /usr/sbin/pbuilder --build --buildresult .. --debbuildopts
--debbuildopts -i ../cssc_1.3.0-1.dsc
└─pbuilder-buildp,4612 /usr/lib/pbuilder/pbuilder-buildpackage --buildresult
.. --debbuildopts --debbuildopts -i ../cssc_1.3.0-1.dsc
└─pbuilder-satisf,5767 /usr/lib/pbuilder/pbuilder-satisfydepends
--control ../cssc_1.3.0-1.dsc --chroot /work/pbuilder/build//4612
--internal-chrootexec chroot /work/pbuilder/build//4612 --binary-all
└─pbuilder-satisf,5768 /usr/lib/pbuilder/pbuilder-satisfydepends
--control ../cssc_1.3.0-1.dsc --chroot /work/pbuilder/build//4612
--internal-chrootexec chroot /work/pbuilder/build//4612 --binary-all
└─dpkg-architectu,5769 /usr/bin/dpkg-architecture -qDEB_HOST_ARCH
└─sh,5770 -c ${CC:-gcc} -dumpmachine
└─gcc,5771 -dumpmachine
A quick test can be done of reqesting disabling of ccache while calling
dpkg-architecture.
Test:
--- /usr/lib/pbuilder/pbuilder-satisfydepends.orig 2013-08-29
23:34:32.0 +0200
+++ /usr/lib/pbuilder/pbuilder-satisfydepends 2013-08-29 23:36:23.0
+0200
@@ -59,7 +59,7 @@
function checkbuilddep_internal () {
# Use this function to fulfill the dependency (almost)
-local ARCH=$($CHROOTEXEC dpkg-architecture -qDEB_HOST_ARCH)
+local ARCH=$($CHROOTEXEC env CCACHE_DISABLE=1 dpkg-architecture
-qDEB_HOST_ARCH)
local BUILD_DEP_DEB_DIR
local BUILD_DEP_DEB_CONTROL
local DEPENDS
For some reason, the stap script still traps a mkdir done as root,
while I can check through /proc that dpkg-architecture and gcc do have
CCACHE_DISABLE=1 in their env.
Another try: if ccache ignores the disable request, maybe we can ask
it not to touch the cache ?
--- /usr/lib/pbuilder/pbuilder-satisfydepends.orig 2013-08-29
23:34:32.0 +0200
+++ /usr/lib/pbuilder/pbuilder-satisfydepends 2013-08-29 23:56:48.0
+0200
@@ -59,7 +59,7 @@
function checkbuilddep_internal () {
# Use this function to fulfill the dependency (almost)
-local ARCH=$($CHROOTEXEC dpkg-architecture -qDEB_HOST_ARCH)
+local ARCH=$($CHROOTEXEC env CCACHE_READONLY=1
CCACHE_TEMPDIR=${TMPDIR:-/tmp} dpkg-architecture -qDEB_HOST_ARCH)
local BUILD_DEP_DEB_DIR
local BUILD_DEP_DEB_CONTROL
local DEPENDS
... but similarly, ccache seems to ignore the request, which can be
seen in the processes' env.
Is there some ccache subtlety I'm missing ? Could ccache maints lend a hand
here ?
Best regards,
--
Yann
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666525: culprit located as dpkg-architecture ?
Running a build with systemtap set to intercept:
* calls to mkdir() as root under ccache
* mkdir failures with EACCESS
... reveals quite constant shape of the process tree leading to the
suspect mkdir's, and strong correlation with the EACCESS problems (and
with the actual ccache subdirs owned by root, as expected):
$ stap /work/yann/deb/cssc/mkdir.stap
go...
mkdir /work/pbuilder/ccache/tmp
process traceback:
gcc(32018) sh(32017) dpkg-architectu(32016) pbuilder-satisf(32015)
pbuilder-satisf(32014) pbuilder-buildp(30987) pbuilder(30986) sudo(30985)
pdebuild(29971) bash(4485) screen(4306)
mkdir /work/pbuilder/ccache/2
process traceback:
gcc(32018) sh(32017) dpkg-architectu(32016) pbuilder-satisf(32015)
pbuilder-satisf(32014) pbuilder-buildp(30987) pbuilder(30986) sudo(30985)
pdebuild(29971) bash(4485) screen(4306)
mkdir /work/pbuilder/ccache/2/4 => EACCESS
mkdir /work/pbuilder/ccache/2/5 => EACCESS
mkdir /work/pbuilder/ccache/2/d => EACCESS
mkdir /work/pbuilder/ccache/2/6 => EACCESS
mkdir /work/pbuilder/ccache/2/e => EACCESS
mkdir /work/pbuilder/ccache/2/e => EACCESS
...
dpkg-architecture launching gcc ? Now that's a funny surprise :)
I hope this information will be of some help...
probe begin { println("go...") }
probe syscall.mkdir.return {
err = errno_p(returnval())
if (err == 13) {
println("mkdir ", kernel_string($pathname), " => EACCESS")
}
}
probe syscall.mkdir {
if ((uid() == 0) && isinstr(pathname, "/ccache/")) {
println("mkdir ", kernel_string($pathname))
printf("process traceback:\n %s\n", pstrace(task_current()))
}
}
Bug#666525: not fixed yet in pbuilder 0.215
found 666525 pbuilder/0.215 thanks I regularly got in the previous weeks, when working on gcompris, qgo, and today with tagua: [ 36%] Building CXX object src/CMakeFiles/tagua.dir/hlvariant/minichess5/variant.o ccache: FATAL: Failed to create /work/pbuilder/ccache/b/0: Permission denied make[3]: *** [src/CMakeFiles/tagua.dir/hlvariant/minichess5/variant.o] Error 1 Trying to avoid the problem, I had just regenerated by base.tgz from scratch, but it obviously did not help. I am using the "shell on failure" hook from http://bazaar.launchpad.net/%7Ekubuntu-members/pbuilder/pbuilder-hooks/, which helps me see what's wrong: # ls -l /work/pbuilder/ccache total 72 drwxr-xr-x 6 pbuilder pbuilder 4096 Aug 18 13:30 0 ... drwxr-xr-x 5 pbuilder pbuilder 4096 Aug 18 13:30 9 -rw-r--r-- 1 root root 190 Aug 18 13:22 CACHEDIR.TAG drwxr-xr-x 5 pbuilder pbuilder 4096 Aug 18 13:30 a drwxr-xr-x 2 root root 4096 Aug 18 13:22 b drwxr-xr-x 5 pbuilder pbuilder 4096 Aug 18 13:30 c drwxr-xr-x 3 pbuilder pbuilder 4096 Aug 18 13:30 d drwxr-xr-x 9 pbuilder pbuilder 4096 Aug 18 13:30 e drwxr-xr-x 3 pbuilder pbuilder 4096 Aug 18 13:30 f drwxr-xr-x 2 root root 4096 Aug 18 13:22 tmp The workaround I use is very far from satisfactory, but far less costly than rerunning the build from scratch: from the hook's shell run: chown -R pbuilder.pbuilder /work/pbuilder/ccache then let the build go on: dpkg-buildpackage -us -uc -nc ... and manually copy the generated files from the chroot before exiting the shell. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717291: smemcap: undeclared conflicts with previous smem
Package: smemcap Version: 1.3-2 Severity: serious Unpacking smemcap (from .../smemcap_1.3-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/smemcap_1.3-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man8/smemcap.8.gz', which is also in package smem 1.3-1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages smemcap depends on: ii libc6 2.17-7 smemcap recommends no packages. smemcap suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707831: Broken UUID detection code makes another system unbootable
retitle 707831 Broken UUID detection code makes LVM systems unbootable after adding a new PV severity 707831 critical thanks I also got bitten by this issue, like others as seen in #612402. Since it makes (at least some) LVM systems unbootable, it surely deserves a higher severity. Now what happens ? As Daniel said, grub-probe is failing. More specifically: # /usr/sbin/grub-probe --device /dev/mapper/home-root --target=abstraction /usr/sbin/grub-probe: error: Couldn't find PV pv1. Check your device.map. So what does that message mean, ie. what does this "pv1" comes from ? A bit of googling shows that the problem is linked to me having added a PV to the machine. The previous reboot was certainly the one during which I have plugged the drive, and the machine had had no need to reboot since its inclusion as PV into my VG. So well, does moving away the old map and running grub-mkdevicemap fix the problem ? Not really, since I now see many dozens of "physical volume pv0 not found" lines, where I used to have a single complaint about "pv1". What happened ? If I look at the generated grub.cfg now, the linux commandline has changed back to using the correct /dev/mapper/ path, but the UUID used for "search --set=root" is now that of my /usr partition instead of that of the (non-LVM) /boot. Is this *only* used to load the background image and font from /usr ? In short: * grub-probe issues completely unhelpful messages about PVs, where it could surely give their Linux names, and give a hint that *checking* the device map is not going to be sufficient, and that grub-mkdevicemap may come handy * I surely missed something, or the use grub-mkdevicemap should not have generated a situation that just looks more messy * As the original report says, such problems should surely not propagate to grub.cfg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693257: wine and win-unstable conflict over manpages
Package: libwine-bin Version: 1.4.1-4 Severity: serious Unpacking libwine (from .../libwine_1.4.1-4_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libwine_1.4.1-4_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/wineserver.1.gz', which is also in package libwine-unstable:i386 1.5.6-2 Selecting previously unselected package libwine-bin:i386. Unpacking libwine-bin:i386 (from .../libwine-bin_1.4.1-4_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libwine-bin_1.4.1-4_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/regedit.1.gz', which is also in package libwine-bin-unstable:i386 1.5.6-2 Selecting previously unselected package wine-bin. Unpacking wine-bin (from .../wine-bin_1.4.1-4_i386.deb) ... dpkg: error processing /var/cache/apt/archives/wine-bin_1.4.1-4_i386.deb (--unpack): trying to overwrite '/usr/share/man/man1/wine-safe.1.gz', which is also in package wine-bin-unstable 1.5.6-2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libwine-bin depends on: ii libc62.13-35 ii libncurses5 5.9-10 ii libtinfo55.9-10 pn libwine libwine-bin recommends no packages. libwine-bin suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680084: postinst script gets stuck
On Wed, Jul 04, 2012 at 08:48:59AM +0200, Harald Dunkel wrote: > On 07/03/12 23:57, Yann Dirson wrote: > > > > This seems to show the debconf "frontend" script not dealing handling > > the termination of the memtest86+.postinst script. If any, it seems > > more plausible that the bug would be in debconf. Which debconf > > version is this ? Are you running squeeze or sid ? > > > > Testing. debconf is version 1.5.45 > > > If I run "dpkg-reconfigure memtest86+" here (wheezy/amd64), however, > > things go perfectly fine: > > > > | Generating grub.cfg ... > > | Found background image: /usr/share/images/desktop-base/desktop-grub.png > > | Found linux image: /boot/vmlinuz-3.2.0-2-amd64 > > | Found initrd image: /boot/initrd.img-3.2.0-2-amd64 > > [...] > > | Found memtest86 image: /memtest86.bin > > | Found memtest86+ image: /memtest86+.bin > > | Found memtest86+ multiboot image: /memtest86+_multiboot.bin > > | done > > | root# > > > > It would be interesting to know what the frontend process is doing > > when that happens. Can you retry, and show > > > > 1. the output of "ps l " > > root@ppcl007:~# ps l 3648 > F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND > 0 0 3648 3636 20 0 50532 11132 - S+ pts/1 0:00 > /usr/bin/perl -w /usr/share/debconf/frontend > /var/lib/dpkg/info/memtest86+.postinst configure > > > 2. the output of "strace -p " > > > > root@ppcl007:~# strace -p 3648 > Process 3648 attached - interrupt to quit > read(11, In that case, we'll need to know what's hidden behind file descriptor 11. You can use "ls -l /proc//fd/" to find out. You can also get info from debconf itself. Setting DEBCONF_DEBUG=developer while running dpkg can help. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680084: postinst script gets stuck
On Tue, Jul 03, 2012 at 03:21:33PM +0200, Harald Dunkel wrote: > The postinst script gets stuck on builing grub.cfg: > > : > Selecting previously unselected package memtest86+. > (Reading database ... 29792 files and directories currently installed.) > Unpacking memtest86+ (from .../memtest86+_4.20-1.1_amd64.deb) ... > Setting up memtest86+ (4.20-1.1) ... > Generating grub.cfg ... > Found linux image: /boot/vmlinuz-3.2.0-3-amd64 > Found initrd image: /boot/initrd.img-3.2.0-3-amd64 > Found linux image: /boot/vmlinuz-3.2.0-0.bpo.2-amd64 > Found initrd image: /boot/initrd.img-3.2.0-0.bpo.2-amd64 > Found linux image: /boot/vmlinuz-2.6.32-5-amd64 > Found initrd image: /boot/initrd.img-2.6.32-5-amd64 > Found memtest86+ image: /memtest86+.bin > Found memtest86+ multiboot image: /memtest86+_multiboot.bin > File descriptor 3 (pipe:[7342]) leaked on lvs invocation. Parent PID 2698: > /bin/sh > grub-probe: error: no such disk. > done > > > "done" is the last line. > > ps -ef shows: ... > root 2206 2202 0 14:58 pts/000:00:02 | \_ aptitude > root 2252 2206 0 14:59 pts/100:00:00 | \_ /usr/bin/dpkg > --status-fd 23 --configure memtest86+:amd64 > root 2253 2252 0 14:59 pts/100:00:00 | \_ > /usr/bin/perl -w /usr/share/debconf/frontend > /var/lib/dpkg/info/memtest86+.postinst configure > root 2259 2253 0 14:59 pts/100:00:00 | \_ > [memtest86+.post] This seems to show the debconf "frontend" script not dealing handling the termination of the memtest86+.postinst script. If any, it seems more plausible that the bug would be in debconf. Which debconf version is this ? Are you running squeeze or sid ? If I run "dpkg-reconfigure memtest86+" here (wheezy/amd64), however, things go perfectly fine: | Generating grub.cfg ... | Found background image: /usr/share/images/desktop-base/desktop-grub.png | Found linux image: /boot/vmlinuz-3.2.0-2-amd64 | Found initrd image: /boot/initrd.img-3.2.0-2-amd64 [...] | Found memtest86 image: /memtest86.bin | Found memtest86+ image: /memtest86+.bin | Found memtest86+ multiboot image: /memtest86+_multiboot.bin | done | root# It would be interesting to know what the frontend process is doing when that happens. Can you retry, and show 1. the output of "ps l " 2. the output of "strace -p " -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678207: screen: (uncaught) compare-version errors at install
Package: screen Version: 4.1.0~20120320gitdb59704-3 Severity: serious See below install log in a pbuilder sid chroot. At the very least, $2 is used unquoted in debconf script. # aptitude install screen The following NEW packages will be installed: screen 0 packages upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 670 kB of archives. After unpacking 984 kB will be used. Get: 1 ftp://ftp.debian.org/debian/ sid/main screen amd64 4.1.0~20120320gitdb59704-3 [670 kB] Fetched 670 kB in 1s (522 kB/s) Preconfiguring packages ... dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through `less' or `more' ! Selecting previously unselected package screen. (Reading database ... 22422 files and directories currently installed.) Unpacking screen (from .../screen_4.1.0~20120320gitdb59704-3_amd64.deb) ... dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through `less' or `more' ! Processing triggers for install-info ... Processing triggers for man-db ... Setting up screen (4.1.0~20120320gitdb59704-3) ... dpkg: error: --compare-versions takes three arguments: Type dpkg --help for help about installing and deinstalling packages [*]; Use `dselect' or `aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through `less' or `more' ! root@home:/tmp/buildd# -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages screen depends on: ii dpkg 1.16.3 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-33 ii libncursesw5 5.9-8 ii libpam0g 1.1.3-7.1 screen recommends no packages. screen suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673297: libxml2 and gzopen64@ZLIB_1.2.3.3 (Was: Please reschedule tagua 1.0~alpha2-10 on armel)
On Sat, May 26, 2012 at 12:32:50PM +0200, Julien Cristau wrote: > On Wed, May 23, 2012 at 22:23:11 +0200, Yann Dirson wrote: > > > Prev build was hit by the same problem as > > http://bugs.debian.org/673297, so it should work now. > > > I guess you meant mips, not armel? Anyway, given back. Right, thanks :) However, looks like the new build attempt failed with the same issue. And https://buildd.debian.org/status/package.php?p=shelxle also shows the same error on other archs. Shouldn't #673297 be reopenned ? Note that according to google, the same "libxml2.so.2: undefined reference to `gzopen64@ZLIB_1.2.3.3'" error is not even Debian-specific. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671929: ccache: trigger not multi-arch safe, prevents proper gcc upgrade
On Wed, May 09, 2012 at 08:54:18PM +0200, Joel Rosdahl wrote: > Hi, > > I don't see anything in the triggered ccache postinst script that could > cause this. > > Can you reproduce the problem? Well, it was systematic, and I have now purged the 3 foreign packages remaining from my first experiment with multi-arch - so things are now back in order. I suspect that the way to reproduce would be: * downgrade eg. libgcc1 * activate multiarch * install foreign libgcc1 (thus same version) * upgrade native libgcc1 (possibly while same foreign version still unavail, or make it unavail by disabling foreign ach in apt.conf ?) > Could it be that something other than > ccache's trigger that causes this? See for instance bug#665727. Hm, it *does* look like the same issue, it is definitely the same message (and I got this exact one with libgcc1 once I purged gcc-4.7-base:armel). It is perfectly possible that the message from ccache in the context was here purely by chance - sorry about misfiling. > -- Joel > > On 8 May 2012 11:10, Yann Dirson wrote: > > > Package: ccache > > Version: 3.1.7-1 > > Severity: grave > > > > Cannot configure the new gcc-4.7-base: > > > > |Preparing to replace gcc-4.7-base:amd64 4.7.0-3 (using > > .../gcc-4.7-base_4.7.0-7_amd64.deb) ... > > |De-configuring gcc-4.7-base:armel ... > > |Unpacking replacement gcc-4.7-base:amd64 ... > > |Processing triggers for ccache ... > > |Updating symlinks in /usr/lib/ccache ... > > |dpkg: error: --configure needs a valid package name but 'gcc-4.7-base' is > > not: ambiguous package name 'gcc-4.7-base' with more than one installed > > instance > > > > I have: > > > > |# dpkg -l 'gcc-4.7-base' > > |iU gcc-4.7-base:amd64 4.7.0-7 > > |iF gcc-4.7-base:armel 4.7.0-3 > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers testing > > APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, > > 'experimental') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) > > Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/bash > > > > Versions of packages ccache depends on: > > ii libc6 2.13-32 > > ii zlib1g 1:1.2.6.dfsg-2 > > > > ccache recommends no packages. > > > > Versions of packages ccache suggests: > > pn distcc > > > > -- 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#671929: ccache: trigger not multi-arch safe, prevents proper gcc upgrade
Package: ccache Version: 3.1.7-1 Severity: grave Cannot configure the new gcc-4.7-base: |Preparing to replace gcc-4.7-base:amd64 4.7.0-3 (using .../gcc-4.7-base_4.7.0-7_amd64.deb) ... |De-configuring gcc-4.7-base:armel ... |Unpacking replacement gcc-4.7-base:amd64 ... |Processing triggers for ccache ... |Updating symlinks in /usr/lib/ccache ... |dpkg: error: --configure needs a valid package name but 'gcc-4.7-base' is not: ambiguous package name 'gcc-4.7-base' with more than one installed instance I have: |# dpkg -l 'gcc-4.7-base' |iU gcc-4.7-base:amd64 4.7.0-7 |iF gcc-4.7-base:armel 4.7.0-3 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ccache depends on: ii libc6 2.13-32 ii zlib1g 1:1.2.6.dfsg-2 ccache recommends no packages. Versions of packages ccache suggests: pn distcc -- 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#616011: no mediawiki exporter
found 616011 1.1.1+LibO3.4.5-2 tags 616011 + patch thanks On current wheezy, I get the same problem: the exporter is not listed, and attempting to use the "send to" feature yields the same result as OP. How are exporters supposed to be registered ? Can we manually request a re-registration of that exporter, possibly with verbose traces ? Since the last time this worked on this machine (that was last september, and I did not attempt to use it since then), the following upgrades were done according to aptitude logs: [UPGRADE] libreoffice 1:3.3.3-4+b1 -> 1:3.4.3-1 [UPGRADE] libreoffice-wiki-publisher 1.1.1+LibO3.3.3-4 -> 1.1.1+LibO3.4.3-1 [UPGRADE] libreoffice 1:3.4.3-1 -> 1:3.4.3-3 [UPGRADE] libreoffice-wiki-publisher 1.1.1+LibO3.4.3-1 -> 1.1.1+LibO3.4.3-3 I get the problem with sun jre 1.6.0_26 and (openjdk from testing but listed as sun) _24, the previous success was probably with another version, since no jre was selected any more (this mechanism *does* suck, btw). Switching to "FSF 1.5.0" (for which there are two identical lines in the dialog...) results in the "send to mediawiki" turning to non-selectable after restart. Since it used to work for me with 3.3.3 and problems have been reported with previous versions, I don't believe that downgrading would be of any help. René wrote: >Please don't tell me you did intrusive changes like a complete LibO package >upgrade while LibO was running? (Extension registration should be ok if >done via unopkg, but I don't think it will work with the new "preregistered" >way) Err... are you saying that no LibO or OOo program should be running during the upgrade or there is any risk of getting broken in ways noone imagines ? That would sound pretty broken, and a bold warning should be displayed from preinst, should that be the case. That said, I regularly launch upgrades while I'm continuing to work, and it surely occured that LibO got upgrade while it was running. Now what can be done to recover if that was the source of the breakage ? Looking at the various installed filters .xcu files, it looks like this one is the only one using <>, other (writer2latex, pdfimport) rather use <>. Now I tried to replace "fuse" with "replace" for a test, and reregistering the thing: mv /usr/lib/libreoffice/share/extensions/wiki-publisher / /var/lib/dpkg/info/libreoffice-common.postinst triggered /usr/lib/libreoffice/share/extensions mv /wiki-publisher/ /usr/lib/libreoffice/share/extensions/ $EDITOR /usr/lib/libreoffice/share/extensions/wiki-publisher/Filter.xcu /var/lib/dpkg/info/libreoffice-common.postinst triggered /usr/lib/libreoffice/share/extensions ... and guess what ? it just worked :) Now the export filter is selectable in the export dialog, and "send to" finds it as well... So one question remains, what was this "fuse" supposed to do ? -- Yann Dirson - Bertin Technologies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657751: gdm3: error on package purge
Package: gdm3 Version: 3.0.4-4 Severity: serious Removing gdm3 ... Purging configuration files for gdm3 ... insserv: warning: script 'K02evms' missing LSB tags and overrides insserv: warning: script 'S20LOCAL-fw' missing LSB tags and overrides insserv: warning: script 'evms' missing LSB tags and overrides insserv: warning: script 'LOCAL-fw' missing LSB tags and overrides Removing user `Debian-gdm' ... Warning: group `Debian-gdm' has no more members. userdel: user Debian-gdm is currently logged in /usr/sbin/deluser: `/usr/sbin/userdel Debian-gdm' returned error code 8. Exiting. Could not remove Debian-gdm user. /usr/sbin/delgroup: `Debian-gdm' still has `Debian-gdm' as their primary group! Could not remove Debian-gdm group. insserv: warning: script 'K02evms' missing LSB tags and overrides insserv: warning: script 'S20LOCAL-fw' missing LSB tags and overrides insserv: warning: script 'evms' missing LSB tags and overrides insserv: warning: script 'LOCAL-fw' missing LSB tags and overrides userdel: user Debian-gdm is currently logged in /usr/sbin/deluser: `/usr/sbin/userdel Debian-gdm' returned error code 8. Exiting. /usr/sbin/delgroup: `Debian-gdm' still has `Debian-gdm' as their primary group! dpkg: error processing gdm3 (--purge): subprocess installed post-removal script returned error exit status 128 Processing triggers for man-db ... configured to not write apport reports Processing triggers for gconf2 ... Processing triggers for hicolor-icon-theme ... Errors were encountered while processing: gdm3 E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gdm3 depends on: ii accountsservice0.6.15-2 ii adduser3.113 ii awesome [x-window-manager] 3.4.11-1 ii dconf-gsettings-backend0.10.0-3 ii debconf [debconf-2.0] 1.5.41 ii flwm [x-window-manager]1.02+cvs20080422-9 ii fvwm [x-window-manager]1:2.5.30.ds-1 ii gconf2 2.32.4-1 ii gnome-session-bin 3.2.1-1 ii gsettings-desktop-schemas 3.2.0-2 ii libaccountsservice00.6.15-2 ii libatk1.0-02.2.0-2 ii libattr1 1:2.4.46-5 ii libaudit0 1.7.18-1 ii libc6 2.13-24 ii libcairo-gobject2 1.10.2-6.2 ii libcairo2 1.10.2-6.2 ii libcanberra-gtk3-0 0.28-3 ii libcanberra0 0.28-3 ii libdbus-1-31.4.16-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.8.0-3 ii libfreetype6 2.4.8-1 ii libgconf2-42.32.4-1 ii libgdk-pixbuf2.0-0 2.24.0-2 ii libglib2.0-0 2.30.2-4 ii libglib2.0-bin 2.30.2-4 ii libgtk-3-0 3.2.3-1 ii libpam-modules 1.1.3-6 ii libpam-runtime 1.1.3-6 ii libpam0g 1.1.3-6 ii libpango1.0-0 1.29.4-2 ii librsvg2-common2.34.2-2 ii libselinux12.1.0-4 ii libupower-glib10.9.15-1 ii libwrap0 7.6.q-22 ii libx11-6 2:1.4.4-4 ii libxau61:1.0.6-4 ii libxdmcp6 1:1.1.0-4 ii libxklavier16 5.1-3 ii libxrandr2 2:1.3.2-2 ii lsb-base 3.2-28 ii lxsession [x-session-manager] 0.4.6.1-1 ii openbox [x-window-manager] 3.5.0-2 ii policykit-1-gnome 0.105-1 ii upower 0.9.15-1 ii xfce4-session [x-session-manager] 4.8.2-3 ii xfwm4 [x-window-manager] 4.8.3-1 ii xterm [x-terminal-emulator]276-2 Versions of packages gdm3 recommends: ii at-spi 1.32.0-1 ii desktop-base 6.0.7 ii gnome-icon-theme 3.2.1.2-1 ii gnome-power-manager ii gnome-settings-daemon ii x11-xkb-utils 7.6+4 ii xserver-xephyr 2:1.11.3.901-2 ii xserver-xorg 1:7.5+8 ii zenity 3.2.0-1 Versions of packages gdm3 suggests: pn gnome-mag pn gnome-orca pn gok pn libpam-gnome-keyring 3.2.2-1 pn metacity -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Cont
Bug#657746: prolix: under- and wrongly-documented, not working interactively at all
Package: prolix Version: 0.01-1 Severity: serious * the manpage does not give a synopsis or explanation of options, only example uses not directly usable on standard files. No proper documentation of interactive mode either. * trying a simple thing like: strings /usr/bin/gdmflexiserver|prolix -r '[a-z]' ... does filter, but I'm back to the shell without any possibility of interactive use * "prolix -h" tells that "-v" is --verbose, but attempting to use it makes it obvious that it is an alias to (undocumented) --version flag instead, and it does not even give prolix' version * "-l" says "Option log requires an argument", which -h does not tell about well... that makes it *far* less useful than "grep -v" in its current state - looking forward to see it in better shape... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages prolix depends on: ii libdata-munge-perl 0.04-1 ii libipc-run-perl0.90-1 ii libjson-perl 2.53-1 ii libmoose-perl 2.0401-1 ii libmoosex-configfromfile-perl 0.04-1 ii libmoosex-getopt-perl 0.37-1 ii libstring-shellquote-perl 1.03-1 ii libterm-readkey-perl 2.30-4+b2 ii libtry-tiny-perl 0.11-1 ii perl 5.14.2-6 prolix recommends no packages. prolix suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644855: xye: lacks dep on xye-data
Package: xye Version: 0.11.1-1 Severity: serious $ xye Will look on /usr/share/xye/ for data files (non-user levels, skins) Exception: Can't open/find data folder -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xye depends on: ii libc62.13-21 ii libgcc1 1:4.6.1-4 ii libsdl-image1.2 1.2.10-2.1+b1 ii libsdl-ttf2.0-0 2.0.9-1.1 ii libsdl1.2debian 1.2.14-6.4 ii libstdc++6 4.6.1-4 xye recommends no packages. xye suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644001: mozilla-imagezoom: not compatible with ff 6 and later
Package: mozilla-imagezoom Version: 0.4.4-1 Severity: serious It just does not work with the version in testing, and not with ff7 either. The upstream 0.4.5/0.4.6 changelog does not seem to indicate any sort of improvement, but who knows... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mozilla-imagezoom depends on: ii iceweasel 6.0.2-1 mozilla-imagezoom recommends no packages. mozilla-imagezoom suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643572: gnushogi: FTBFS: book.c:296:13: error: format not a string literal and no format arguments [-Werror=format-security]
On Wed, Sep 28, 2011 at 12:18:45AM +0200, Yann Dirson wrote: > On Tue, Sep 27, 2011 at 02:29:24PM +0200, Didier Raboud wrote: > > Source: gnushogi > > Version: 1.3.2-7 > > Severity: serious > > Tags: wheezy sid > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening > > Justification: FTBFS on amd64 > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > I have fixed the -Wformat-security issues, and gnushogi appears to > work fine both in xboard and curses modes, but gnuminishogi seems to > have issues not seen in 1.3.2-7, still to be investigated: > > * segfault after entering one move in curses mode > * unresponsive in xboard mode, and not killed on frontend deconnexion Both come from hardening flags, fix under way. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643572: gnushogi: FTBFS: book.c:296:13: error: format not a string literal and no format arguments [-Werror=format-security]
On Tue, Sep 27, 2011 at 02:29:24PM +0200, Didier Raboud wrote: > Source: gnushogi > Version: 1.3.2-7 > Severity: serious > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20110923 qa-ftbfs hardening-format-security hardening > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. I have fixed the -Wformat-security issues, and gnushogi appears to work fine both in xboard and curses modes, but gnuminishogi seems to have issues not seen in 1.3.2-7, still to be investigated: * segfault after entering one move in curses mode * unresponsive in xboard mode, and not killed on frontend deconnexion Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624263: grub-pc: stuck in grub-mkdevicemap at configure time
On Fri, Aug 19, 2011 at 05:18:41PM -0500, Jonathan Nieder wrote: > Hi Yann, > > Yann Dirson wrote: > > > Got it again, when upgrading to 1.99-9, running under a 2.6.38.4 > > kernel. kern.log reads the following, maybe it will give more ideas > > about what's going on ? Concurency issue in kernel space ? > > Yeah, looks like it. Next time you get a chance in this state, could > you try something like the following? > > echo d >/proc/sysrq-trigger; # list all locks held > # or: > echo w >/proc/sysrq-trigger; # list all blocked tasks > > Also, is it reproducible (e.g., with "dpkg-reconfigure grub-pc")? > If so, trying a more recent kernel to compare results would be > interesting, too. Unfortunately, not completely. OTOH, I get more reproducible problems when attempting to use the PATA cdrom. > Trace left unsnipped for the kernel team's benefit. Well, that kernel does not come from the package, it's a vanilla one with some changes - the VIA VT6415 chipset on my motherboard prevents the system to boot when a HD is connected to it, with the libata driver, so I'm using the old one. Maybe there was a regression in via82cxxx I did not notice before. Will dig. > Jonathan > > > INFO: task grub-mkdevicema:24535 blocked for more than 120 seconds. > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > grub-mkdevicema D 0001034e66cc 0 24535 24534 0x > > 88008e95db28 0082 8800 000134c0 > > 000134c0 000134c0 000134c0 880001ad5100 > > 000134c0 88008e95dfd8 88008e95dfd8 000134c0 > > Call Trace: > > [] __mutex_lock_common.clone.5+0x131/0x198 > > [] ? exact_match+0x0/0xa > > [] __mutex_lock_slowpath+0xe/0x10 > > [] mutex_lock+0x1e/0x38 > > [] __blkdev_get+0x71/0x339 > > [] ? blkdev_open+0x0/0x6b > > [] blkdev_get+0x1b4/0x28f > > [] ? blkdev_open+0x0/0x6b > > [] blkdev_open+0x67/0x6b > > [] __dentry_open+0x15e/0x278 > > [] ? _raw_spin_lock+0x9/0xb > > [] ? mntget+0x1b/0x21 > > [] nameidata_to_filp+0x5b/0x62 > > [] finish_open+0x9c/0x15a > > [] ? do_path_lookup+0xe8/0x113 > > [] do_filp_open+0x184/0x696 > > [] ? handle_mm_fault+0x131/0x146 > > [] ? might_fault+0x9/0xb > > [] ? __strncpy_from_user+0x1a/0x49 > > [] ? alloc_fd+0x6f/0x11a > > [] do_sys_open+0x5b/0xed > > [] sys_open+0x1b/0x1d > > [] system_call_fastpath+0x16/0x1b -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624263: grub-pc: stuck in grub-mkdevicemap at configure time
Got it again, when upgrading to 1.99-9, running under a 2.6.38.4 kernel. kern.log reads the following, maybe it will give more ideas about what's going on ? Concurency issue in kernel space ? Aug 11 22:26:59 home kernel: [222362.080164] INFO: task grub-mkdevicema:24535 blocked for more than 120 seconds. Aug 11 22:26:59 home kernel: [222362.080176] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 11 22:26:59 home kernel: [222362.080183] grub-mkdevicema D 0001034e66cc 0 24535 24534 0x Aug 11 22:26:59 home kernel: [222362.080196] 88008e95db28 0082 8800 000134c0 Aug 11 22:26:59 home kernel: [222362.080206] 000134c0 000134c0 000134c0 880001ad5100 Aug 11 22:26:59 home kernel: [222362.080215] 000134c0 88008e95dfd8 88008e95dfd8 000134c0 Aug 11 22:26:59 home kernel: [222362.080224] Call Trace: Aug 11 22:26:59 home kernel: [222362.080241] [] __mutex_lock_common.clone.5+0x131/0x198 Aug 11 22:26:59 home kernel: [222362.080254] [] ? exact_match+0x0/0xa Aug 11 22:26:59 home kernel: [222362.080263] [] __mutex_lock_slowpath+0xe/0x10 Aug 11 22:26:59 home kernel: [222362.080271] [] mutex_lock+0x1e/0x38 Aug 11 22:26:59 home kernel: [222362.080282] [] __blkdev_get+0x71/0x339 Aug 11 22:26:59 home kernel: [222362.080291] [] ? blkdev_open+0x0/0x6b Aug 11 22:26:59 home kernel: [222362.080300] [] blkdev_get+0x1b4/0x28f Aug 11 22:26:59 home kernel: [222362.080309] [] ? blkdev_open+0x0/0x6b Aug 11 22:26:59 home kernel: [222362.080317] [] blkdev_open+0x67/0x6b Aug 11 22:26:59 home kernel: [222362.080325] [] __dentry_open+0x15e/0x278 Aug 11 22:26:59 home kernel: [222362.080334] [] ? _raw_spin_lock+0x9/0xb Aug 11 22:26:59 home kernel: [222362.080343] [] ? mntget+0x1b/0x21 Aug 11 22:26:59 home kernel: [222362.080351] [] nameidata_to_filp+0x5b/0x62 Aug 11 22:26:59 home kernel: [222362.080360] [] finish_open+0x9c/0x15a Aug 11 22:26:59 home kernel: [222362.080368] [] ? do_path_lookup+0xe8/0x113 Aug 11 22:26:59 home kernel: [222362.080376] [] do_filp_open+0x184/0x696 Aug 11 22:26:59 home kernel: [222362.080387] [] ? handle_mm_fault+0x131/0x146 Aug 11 22:26:59 home kernel: [222362.080396] [] ? might_fault+0x9/0xb Aug 11 22:26:59 home kernel: [222362.080404] [] ? __strncpy_from_user+0x1a/0x49 Aug 11 22:26:59 home kernel: [222362.080413] [] ? alloc_fd+0x6f/0x11a Aug 11 22:26:59 home kernel: [222362.080421] [] do_sys_open+0x5b/0xed Aug 11 22:26:59 home kernel: [222362.080428] [] sys_open+0x1b/0x1d Aug 11 22:26:59 home kernel: [222362.080437] [] system_call_fastpath+0x16/0x1b -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624263: grub-pc: stuck in grub-mkdevicemap at configure time
On Wed, Apr 27, 2011 at 09:27:25AM +0100, Colin Watson wrote: > On Wed, Apr 27, 2011 at 12:52:44AM +0200, Yann Dirson wrote: > > [UPGRADE] grub-pc 1.98+20100804-14 -> 1.99~rc1-13 > > > > When upgrading, aptitude gets stuck with: > > > > Setting up grub-pc (1.99~rc1-13) ... > > Installing new version of config file /etc/grub.d/05_debian_theme ... > > Replacing config file /etc/default/grub with new version > > > > $ pstree -alp 6275 > > grub-pc.postins,6275 /var/lib/dpkg/info/grub-pc.postinst configure > > 1.98+20100804-14 > > ââgrep,6277 -v ^(fd[0-9]\\+) > > ââgrub-mkdevicema,6276 -m - > > > > $ ps l 6275 6277 6276 > > F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND > > 1 0 6275 6180 20 0 10884 752 wait S+ pts/5 0:00 > > /bin/bash /var/lib/dpkg/info/grub-pc.postinst configure 1.98+20100804-14 > > 0 0 6276 6275 20 0 18288 928 blkdev D+ pts/5 0:00 > > grub-mkdevicemap -m - > > 0 0 6277 6275 20 0 7592 572 pipe_w S+ pts/5 0:00 grep > > -v ^(fd[0-9]\+) > > > > $ ps -o pid,wchan=WIDE-WCHAN-COLUMN -o comm 6276 > > PID WIDE-WCHAN-COLUMN COMMAND > > 6276 blkdev_getgrub-mkdevicema > > > > > > Nothing suspect from dmesg - any idea how to quickly get more precise > > info ? Not sure I can get out of this to retry except by rebooting, > > which would be quite a shame... > > It may be difficult retrospectively. Can you attach strace to find out > what system call it's stuck in, and attach gdb (you may need to build > grub2 locally for symbols) to get a backtrace? Unfortunately, neither can complete attaching to the process, and I even have to use kill -9 to get rid of strace and gdb afterwards. Looks like I'd have to reboot and add the strace call to the postinst before retrying ? Bad bad bad :} Maybe we can get some info from the kernel about the syscall details. I have a couple of debugging features activated in this kernel (kgdb notably), I could try to peek via this channel. Other ideas ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624263: grub-pc: stuck in grub-mkdevicemap at configure time
Package: grub-pc
Version: 1.99~rc1-13
Severity: serious
[UPGRADE] grub-pc 1.98+20100804-14 -> 1.99~rc1-13
When upgrading, aptitude gets stuck with:
Setting up grub-pc (1.99~rc1-13) ...
Installing new version of config file /etc/grub.d/05_debian_theme ...
Replacing config file /etc/default/grub with new version
$ pstree -alp 6275
grub-pc.postins,6275 /var/lib/dpkg/info/grub-pc.postinst configure
1.98+20100804-14
ââgrep,6277 -v ^(fd[0-9]\\+)
ââgrub-mkdevicema,6276 -m -
$ ps l 6275 6277 6276
F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
1 0 6275 6180 20 0 10884 752 wait S+ pts/5 0:00 /bin/bash
/var/lib/dpkg/info/grub-pc.postinst configure 1.98+20100804-14
0 0 6276 6275 20 0 18288 928 blkdev D+ pts/5 0:00
grub-mkdevicemap -m -
0 0 6277 6275 20 0 7592 572 pipe_w S+ pts/5 0:00 grep -v
^(fd[0-9]\+)
$ ps -o pid,wchan=WIDE-WCHAN-COLUMN -o comm 6276
PID WIDE-WCHAN-COLUMN COMMAND
6276 blkdev_getgrub-mkdevicema
Nothing suspect from dmesg - any idea how to quickly get more precise
info ? Not sure I can get out of this to retry except by rebooting,
which would be quite a shame...
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/home-root / ext3
rw,relatime,errors=remount-ro,barrier=0,data=ordered 0 0
/dev/sda1 /boot ext2 rw,relatime,errors=continue 0 0
/dev/mapper/home-home /home ext3
rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/mapper/home-tmp /tmp ext3
rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/mapper/home-usr /usr ext3
rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/mapper/home-var /var ext3
rw,relatime,errors=continue,barrier=0,data=ordered 0 0
/dev/mapper/home-work /work ext3
rw,relatime,errors=continue,barrier=0,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST3500412AS_5VV1SRD9
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod lvm
insmod part_msdos
insmod ext2
set root='(home-usr)'
search --no-floppy --fs-uuid --set 0224f60f-7f2b-4de0-863a-f7e8f2fbfeee
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod lvm
insmod part_msdos
insmod ext2
set root='(home-usr)'
search --no-floppy --fs-uuid --set 0224f60f-7f2b-4de0-863a-f7e8f2fbfeee
insmod png
if background_image /share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.37.2' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set faa4559f-ec7a-4c73-8ce9-0dc55f589906
echo'Loading Linux 2.6.37.2 ...'
linux /vmlinuz-2.6.37.2 root=/dev/mapper/home-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.37.2
}
menuentry 'Debian GNU/Linux, with Linux 2.6.37.2 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set faa4559f-ec7a-4c73-8ce9-0dc55f589906
echo'Loading Linux 2.6.37.2 ...'
linux /vmlinuz-2.6.37.2 root=/dev/mapper/home-root ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.37.2
}
menuentry 'Debian GNU/Linux, with Linux 2.6.37ata' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set faa4559f-ec7a-4c73-8ce9-0dc55f589906
echo'Loading Linux 2.6.37ata ...'
linux /vmlinuz-2.6.37ata root=/dev/mapper/home-root ro quiet
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.37ata
}
menuentry 'Debian GNU/Linux, with Linux 2.6
Bug#622406: xorg: crash in drmmode_output_detect() on console switch
Package: xserver-xorg-core Version: 2:1.9.5-1 Severity: grave If I open a second X server, close it, reopen one, re-close it, then my original X server segfault with (remotely attached gdb): Program received signal SIGSEGV, Segmentation fault. drmmode_output_detect (output=) at ../../src/drmmode_display.c:1709 1709../../src/drmmode_display.c: No such file or directory. in ../../src/drmmode_display.c (gdb) bt #0 drmmode_output_detect (output=) at ../../src/drmmode_display.c:1709 #1 0x0048ca83 in xf86ProbeOutputModes (scrn=0x9c9e80, maxX=, maxY=) at ../../../../hw/xfree86/modes/xf86Crtc.c:1580 #2 0x00491f74 in xf86RandR12GetInfo12 (pScreen=0x9d6150, rotations=) at ../../../../hw/xfree86/modes/xf86RandR12.c:1552 #3 0x004c8251 in RRGetInfo (pScreen=0x9d6150, force_query=) at ../../randr/rrinfo.c:202 #4 0x7f8c28fa5c4c in glxDRIEnterVT (index=0, flags=0) at ../../glx/glxdri2.c:617 #5 0x00476a12 in xf86VTSwitch (blockData=, err=, pReadmask=) at ../../../../hw/xfree86/common/xf86Events.c:531 #6 xf86Wakeup (blockData=, err=, pReadmask=) at ../../../../hw/xfree86/common/xf86Events.c:284 #7 0x0042a7db in WakeupHandler (result=-1, pReadmask=0x7e2b20) at ../../dix/dixutils.c:419 #8 0x0045f087 in WaitForSomething ( pClientsReady=) at ../../os/WaitFor.c:232 #9 0x00448602 in Dispatch () at ../../dix/dispatch.c:368 #10 0x004257ab in main (argc=9, argv=0x7fffa9e42ad8, envp=) at ../../dix/main.c:291 Never seen this before today, with an upgrade yesterday night to the recently-migrated-to-wheezy xorg and gcc. Though, my own X server had been running for quite some time before the upgrade, and segfaulted this morning (presumably when the kids switched between their sessions, which seem to imply things can get wrong without even closing an X server, but just by switching). [UPGRADE] lib32gcc1 1:4.5.2-4 -> 1:4.6.0-2 [UPGRADE] libgcc1 1:4.5.2-4 -> 1:4.6.0-2 [UPGRADE] libgl1-mesa-dri 7.7.1-4 -> 7.10-4 [UPGRADE] libgl1-mesa-glx 7.7.1-4 -> 7.10-4 [UPGRADE] libglu1-mesa 7.7.1-4 -> 7.10-4 [UPGRADE] x11-common 1:7.5+8 -> 1:7.6+6 [UPGRADE] xbase-clients 1:7.5+8 -> 1:7.6+6 [UPGRADE] xorg 1:7.5+8 -> 1:7.6+6 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 23 2010 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1926464 Mar 26 04:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS880 [Radeon HD 4250] [1002:9715] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.37.2 (yann@home) (gcc version 4.4.5 (Debian 4.4.5-12) ) #1 SMP Wed Mar 9 21:44:59 CET 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 34158 Feb 10 19:20 /var/log/Xorg.24.log -rw-r--r-- 1 root root 34133 Apr 9 09:42 /var/log/Xorg.22.log -rw-r--r-- 1 root root 34069 Apr 12 07:58 /var/log/Xorg.23.log -rw-r--r-- 1 root root 441554 Apr 12 21:16 /var/log/Xorg.21.log -rw-r--r-- 1 root root 37562 Apr 12 22:01 /var/log/Xorg.20.log -rw-r--r-- 1 root root 37135 Apr 12 22:03 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 794.755] X.Org X Server 1.9.5 Release Date: 2011-03-17 [ 794.756] X Protocol Version 11, Revision 0 [ 794.756] Build Operating System: Linux 2.6.38-1-amd64 x86_64 Debian [ 794.756] Current Operating System: Linux home 2.6.37.2 #1 SMP Wed Mar 9 21:44:59 CET 2011 x86_64 [ 794.756] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.37.2 root=/dev/mapper/home-root ro quiet [ 794.756] Build Date: 26 March 2011 03:32:34AM [ 794.756] xorg-server 2:1.9.5-1 (Cyril Brulebois ) [ 794.756] Current version of pixman: 0.21.4 [ 794.756]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 794.756] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 794.756] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 12 22:03:23 2011 [ 794.756] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 794.757] (==) No Layout section. Using the first Screen section. [ 794.757] (==) No screen section available. Using defaults. [ 794.757] (**) |-->Screen "Default Screen Section" (0) [ 794.757] (**) | |-->Monitor "" [ 794.757] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 794.757] (==) Auto
Bug#614092: guayadeque crashes
Well, it turns out 0.2.5 is not immune, as somewhat expected. Here is a backtrace of the 0.2.5 in squeeze: #0 0x7f7074986732 in addbyter () from /usr/lib/libcurl-gnutls.so.4 #1 0x7f7074986dbd in dprintf_formatf () from /usr/lib/libcurl-gnutls.so.4 #2 0x7f7074987eb5 in curl_mvsnprintf () from /usr/lib/libcurl-gnutls.so.4 #3 0x7f707497921f in Curl_failf () from /usr/lib/libcurl-gnutls.so.4 #4 0x7f707496fa2c in Curl_resolv_timeout () from /usr/lib/libcurl-gnutls.so.4 #5 0x7f7074bd9b2e in pcache1Fetch (p=0x7f705a51820f, iKey=1515291151, createFlag=1515289824) at sqlite3.c:33975 #6 0x7f7074bcd536 in sqlite3PcacheFetch (pCache=0xf681b0, pgno=8927, createFlag=, ppPage=0x7f705a517d30) at sqlite3.c:32956 #7 0x7f7074beaa44 in sqlite3PagerAcquire (pPager=0xf680b8, pgno=1515288944, ppPage=0x7f705a517d30, noContent=0) at sqlite3.c:39626 #8 0x7f7074bf08b7 in accessPayload (pCur=0x7f7074bc36cd, offset=, amt=24, pBuf=, eOp=) at sqlite3.c:49133 #9 0x0510 in ?? () #10 0x7f705478 in ?? () #11 0x7f705488 in ?? () #12 0x00f632f8 in ?? () #13 0x0500 in ?? () #14 0x0044 in ?? () #15 0x7f705a517df8 in ?? () #16 0x0530 in ?? () #17 0x005174bdc7e2 in ?? () #18 0x7f70540363b8 in ?? () #19 0x04f8 in ?? () #20 0x7f705420 in ?? () #21 0x0500 in ?? () #22 0x0004 in ?? () #23 0x0001 in ?? () #24 0x7f70540a5fb8 in ?? () #25 0x7f7073586930 in __libc_malloc (bytes=140120948228692) at malloc.c:3661 #26 0x7f7074bfad9f in sqlite3MemMalloc (nByte=1272) at sqlite3.c:14221 #27 0x7f7074bc1398 in sqlite3MallocSize (n=, pp=0x7f705a517e78) at sqlite3.c:17902 #28 mallocWithAlarm (n=, pp=0x7f705a517e78) at sqlite3.c:17738 #29 0x7f7074bc1474 in sqlite3Malloc (n=1272) at sqlite3.c:17764 #30 0x7f7074bc3320 in sqlite3MallocSize (nByte=) at sqlite3.c:17902 #31 pcache1Alloc (nByte=) at sqlite3.c:33496 #32 0x7f7074bd9b2e in pcache1Fetch (p=0x7f70540a5fb8, iKey=4, createFlag=16134904) at sqlite3.c:33975 #33 0x7f7054033198 in ?? () #34 0x7f70542973a8 in ?? () #35 0x7f70540331e0 in ?? () #36 0x7f705a518290 in ?? () #37 0x7f7074be9806 in pager_write (pPg=0x7f70542974a0) at sqlite3.c:40040 #38 0x7f7074beb231 in sqlite3PagerWrite (pDbPage=) at sqlite3.c:40153 #39 0x7f7074bed566 in insertCell (pPage=0x7f70540335e0, i=0, pCell=0x7f705418ff90 "\264Q\177\231c\005\006\b\201\070\331\065\t\217\205\267d\224\024\002\061\001\001\001\002\001\001C\002\002\001\b", sz=, pTemp=, iChild=, pRC=0x7f705a518290) at sqlite3.c:50702 #40 0x7f7074bd9b2e in pcache1Fetch (p=0x7f70540b2438, iKey=1410016312, createFlag=1958491224) at sqlite3.c:33975 #41 0x7f7074bcd536 in sqlite3PcacheFetch (pCache=0x7f70542974a0, pgno=4, createFlag=, ppPage=0x7f705a5180e8) at sqlite3.c:32956 #42 0x0005 in ?? () #43 0x7f705a518200 in ?? () #44 0x7f7074bf72a7 in sqlite3VdbeRecordCompare (nKey1=, pKey1=0x0, pPKey2=0x2) at sqlite3.c:58061 #45 0x7f7074bf76f6 in sqlite3BtreeMovetoUnpacked (pCur=0x7f705405aa90, pIdxKey=, intKey=, biasRight=, pRes=) at sqlite3.c:49706 #46 0x7f7074bf788f in btreeMoveto (pCur=0x69, pKey=, nKey=140120971719217, bias=1409657488, pRes=0x7f70540be9b8) at sqlite3.c:45871 #47 0x7f705a518378 in ?? () #48 0x7f705a518330 in ?? () #49 0x00f56d10 in ?? () #50 0x in ?? () -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#614092: guayadeque crashes
I am also experiencing seemingly-random crashes, namely segfaults. Roughly since the squeeze release I have switched to guayadeque 0.2.7, so the trigger of the bug may be either the new guayadeque, or a lib that entered testing post-squeeze. It would be great to have a guayadeque-dbg package to provide accurate backtraces. In the meantime here is my best offer: #0 0x7fa314375732 in addbyter () from /usr/lib/libcurl-gnutls.so.4 #1 0x7fa314375dbd in dprintf_formatf () from /usr/lib/libcurl-gnutls.so.4 #2 0x7fa314376eb5 in curl_mvsnprintf () from /usr/lib/libcurl-gnutls.so.4 #3 0x7fa31436821f in Curl_failf () from /usr/lib/libcurl-gnutls.so.4 #4 0x7fa31435ea2c in Curl_resolv_timeout () from /usr/lib/libcurl-gnutls.so.4 #5 0x0058 in ?? () #6 0x1ff3 in ?? () #7 0x7fa3145d946f in ?? () from /usr/lib/libsqlite3.so.0 #8 0x7fa3145df8b7 in ?? () from /usr/lib/libsqlite3.so.0 #9 0x in ?? () The fact there is a "Curl_resolv_timeout" call makes me quite suspicious of a library issue of some sort, see http://bugs.debian.org/614070 for a familiar-looking pattern. Nothing looking vaguely related from a quick search in the libc6 bug list, however. Downgrading to 0.2.5 for now to check what happens... Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611306: libreoffice-gcj: undeclared overlap with openoffice.org-gcj
Package: libreoffice-gcj Version: 1:3.3.0-1 Severity: serious Unpacking libreoffice-gcj (from .../libreoffice-gcj_1%3a3.3.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libreoffice-gcj_1%3a3.3.0-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/gcj/openoffice/xmerge.jar.so', which is also in package openoffice.org-gcj 1:3.2.1-11 configured to not write apport reports dpkg-deb: subprocess paste killed by signal (Broken pipe) -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34.1-3-ge5b0813-dirty (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libreoffice-gcj depends on: ii bsh-gcj 2.0b4-12 Java scripting environment (BeanSh ii gcj-jre [java-gcj-compa 4:4.4.5-1Java runtime environment using GIJ ii libc6 2.11.2-9 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8GCC support library ii libgcj-bc 4.4.5-1 Link time only library for use wit ii libgcj-common 1:4.4.5-1Java runtime library (common files ii libhsqldb-java-gcj 1.8.0.10-9 Java SQL database engine (native c pn libreoffice-core (no description available) pn libreoffice-java-common(no description available) ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libreoffice-gcj recommends no packages. libreoffice-gcj suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#599474: policykit-1: should surely conflict with policykit
Package: policykit-1 Version: 0.96-3 Severity: serious Trying to investigate an issue with permissions on removable drives, and with the stable repo available from my squeeze box, a quick search fro "policykit" in aptitude brings a "policykit" package (which I did not notice was only available from stable). Thinking polkit had not been installed for an obscure reason, I installed the package successfully, just to notice by chance that the new package is policykit-1. * this is confusing * it may possibly break something * we surely don't want that old package to be left isntalled when upgrading from lenny I hope that makes the severity adequate. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34.1-3-ge5b0813-dirty (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages policykit-1 depends on: ii consolekit0.4.1-4framework for defining and trackin ii dbus 1.2.24-3 simple interprocess messaging syst ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libeggdbus-1-00.6-1 D-Bus bindings for GObject ii libexpat1 2.0.1-7XML parsing C library - runtime li ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libpam0g 1.1.1-6Pluggable Authentication Modules l ii libpolkit-backend-1-0 0.96-3 PolicyKit backend API ii libpolkit-gobject-1-0 0.96-3 PolicyKit Authorization API policykit-1 recommends no packages. policykit-1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#587178: git-importdeb: fails with current git
Package: gitpkg
Version: 0.14
Severity: serious
Tags: patch
"git status" used to be synonymous to "git commit --dry-run", and is used that
way
in git-importdeb. The script now fails because "-a" is not understood by "git
status"
any more because of this.
commit 6a7b93ccfe1127de3e8398eeaa0b5e9e9a88c352
Author: Yann Dirson
Date: Fri Jun 25 23:18:59 2010 +0200
Use "git commit --dry-run" not "git status", now that they are different.
This probably breaks with old git versions ?
diff --git a/git-debimport b/git-debimport
index 3ffc955..8781dda 100755
--- a/git-debimport
+++ b/git-debimport
@@ -213,7 +213,7 @@ if [ -n "$PACKAGE_TARS" ]; then
EMAIL=\<$(dpkg-parsechangelog | sed -n 's/Maintainer: //p' | cut -d\<
-f2)
git add .
- if git --no-pager status -a > /dev/null 2>&1; then
+ if git --no-pager commit --dry-run -a > /dev/null 2>&1; then
GIT_AUTHOR_NAME="$AUTHOR" GIT_COMMITTER_NAME="$AUTHOR" \
GIT_AUTHOR_EMAIL="$EMAIL" GIT_COMMITTER_EMAIL="$EMAIL" \
GIT_AUTHOR_DATE="$DATE" GIT_COMMITTER_DATE="$DATE" \
@@ -288,7 +288,7 @@ for f in $PACKAGE_DIFFS; do
DATE=$(file -L
$PKG_ROOT$PACKAGES_DIR/${PACKAGE_NAME}_${UPSTREAM_VERSION}.orig.tar.gz | sed -n
"s/.*, last modified: \([^,]*\),*.*/\1/p")
git add .
- if git --no-pager status -a > /dev/null 2>&1; then
+ if git --no-pager commit --dry-run -a > /dev/null 2>&1; then
GIT_AUTHOR_DATE="$DATE" GIT_COMMITTER_DATE="$DATE" \
git commit -a -m "git-debimport
${PACKAGE_NAME}_${UPSTREAM_VERSION}.orig.tar.gz"
else
@@ -320,7 +320,7 @@ for f in $PACKAGE_DIFFS; do
DATE=$(file -L
$PKG_ROOT$PACKAGES_DIR/${PACKAGE_NAME}_${UPSTREAM_VERSION}.orig.tar.gz | sed -n
"s/.*, last modified: \([^,]*\),*.*/\1/p")
git add .
- if git --no-pager status -a > /dev/null 2>&1; then
+ if git --no-pager commit --dry-run -a > /dev/null 2>&1; then
GIT_AUTHOR_DATE="$DATE" GIT_COMMITTER_DATE="$DATE" \
git commit -a -m "git-debimport
${PACKAGE_NAME}_${UPSTREAM_VERSION}.orig.tar.gz"
else
@@ -352,7 +352,7 @@ for f in $PACKAGE_DIFFS; do
EMAIL=\<$(dpkg-parsechangelog | sed -n 's/Maintainer: //p' | cut -d\< -f2)
git add .
-if git --no-pager status -a > /dev/null 2>&1; then
+if git --no-pager commit --dry-run -a > /dev/null 2>&1; then
GIT_AUTHOR_NAME="$AUTHOR" GIT_COMMITTER_NAME="$AUTHOR" \
GIT_AUTHOR_EMAIL="$EMAIL" GIT_COMMITTER_EMAIL="$EMAIL" \
GIT_AUTHOR_DATE="$DATE" GIT_COMMITTER_DATE="$DATE" \
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.13-evms (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gitpkg depends on:
ii dpkg-dev 1.15.7.2 Debian package development tools
ii git [git-core]1:1.7.1-1 fast, scalable, distributed revisi
ii git-core 1:1.7.1-1 fast, scalable, distributed revisi
gitpkg recommends no packages.
Versions of packages gitpkg suggests:
ii devscripts2.10.64scripts to make the life of a Debi
-- 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#577303: gcompris: FTBFS: goocanvasatk.c:429: error: implicit declaration of function 'GTK_WIDGET_HAS_FOCUS'
According to upstream changelog, GTK_WIDGET_HAS_FOCUS has been recently deprecated (between 2.18 and 2.20), and goocanvas is built with -DGTK_DISABLE_DEPRECATED. Question is, why does goocanvas use this flag for a release version ? That does not look friendly towards users... Following https://bugzilla.gnome.org/show_bug.cgi?id=69872 : * replacing GTK_WIDGET_HAS_FOCUS with gtk_widget_has_focus But it looks like the following change should also be applied: * GTK_WIDGET_SET_FLAGS (widget, GTK_HAS_FOCUS) => GTK_OBJECT_FLAGS (widget) |= GTK_HAS_FOCUS; (don't ask...) On Sun, Apr 11, 2010 at 09:44:39AM +0200, Lucas Nussbaum wrote: > Source: gcompris > Version: 9.2-2-1 > Severity: serious > Tags: squeeze sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20100410 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[6]: Entering directory > > `/build/user-gcompris_9.2-2-1-amd64-wHdMpb/gcompris-9.2-2/src/goocanvas/src' > > CC goocanvasatk.lo > > cc1: warnings being treated as errors > > goocanvasatk.c: In function 'goo_canvas_item_accessible_ref_state_set': > > goocanvasatk.c:429: error: implicit declaration of function > > 'GTK_WIDGET_HAS_FOCUS' > > make[6]: *** [goocanvasatk.lo] Error 1 > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2010/04/10/gcompris_9.2-2-1_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 | > > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#577811: debreaper: reportbug has no find_package_for function
Package: debreaper Version: 0.2.1+nmu1 Severity: grave Symptoms are the same as 510325, but since it looks like any exception causes this behaviour, here is a report for a particular one. .xsession-errors reads: Traceback (most recent call last): File "/usr/share/debreaper/debreaper", line 64, in status = lookup_package (path) File "/usr/share/debreaper/bug_iface.py", line 12, in lookup_package (foundfile, packages) = reportbug.find_package_for (path) AttributeError: 'module' object has no attribute 'find_package_for' -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28.10-smp-smp-2-g0fee61b (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages debreaper depends on: ii bsd-mailx [mail-r 8.1.2-0.20090911cvs-2 simple mail user agent ii debconf [debconf- 1.5.30 Debian configuration management sy ii emacs [mail-reade 23.1+1-5 The GNU Emacs editor (metapackage) ii emacs22-gtk [mail 22.3+1-1.2 The GNU Emacs editor (with GTK use ii emacs23 [mail-rea 23.1+1-5 The GNU Emacs editor (with GTK+ us ii eterm [x-terminal 0.9.5-2Enlightened Terminal Emulator ii gdb 7.0.1-2The GNU Debugger ii konsole [x-termin 4:4.3.4-1 X terminal emulator for KDE 4 ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii mlterm [x-termina 2.9.4-6MultiLingual TERMinal ii mutt [mail-reader 1.5.20-7 text-based mailreader supporting M ii python2.5.4-9An interactive high-level object-o ii python-gtk2 2.16.0-2 Python bindings for the GTK+ widge ii python-support1.0.7 automated rebuilding support for P ii reportbug 4.10.2 reports bugs in the Debian distrib ii terminal.app [x-t 0.9.4+cvs20051125-5+b1 Terminal Emulator for GNUstep ii xdg-utils 1.0.2+cvs20100307-1desktop integration utilities from debreaper recommends no packages. debreaper suggests no packages. -- debconf information: * debreaper/use_viaticum: All X sessions -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#569813: rumors of death slightly exagerated
severity 569813 normal tags 569813 + help thanks Whereas make-kpkg does not support those patches itself, they are still apparently useful to some people - and as Manoj says in [1] simple tools can even be written to make it convenient to use them again. Tagging as "help" as I don't have the itch to write such a script myself - it would however fit well into kernel-patch-scripts. http://lists.debian.org/debian-devel/2010/03/msg00746.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575386: accerciser: missing dependency
Package: accerciser Version: 1.8.0-1 Severity: serious accerciser hits a failed assertion when trying to load module "gail". It looks like it lacks a dep on libgail-common (if not on libgail-gnome-module). -- Yann -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573495: dos2unix: should conflict/replace old versions of tofrodos
Package: dos2unix Version: 5.0-1 Severity: serious This will surely be needed for smooth upgrade from lenny. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28.10-smp-smp-2-g0fee61b (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) 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#566913: twisted-doc: recommends obsolete twisted-doc-api
Package: twisted-doc Version: 9.0.0-1 Severity: serious Aside of being an unsatisfiable-in-squeeze Recommends, this can cause an obsolete version of this doc to be pulled from oldstable. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28.10-smp-smp-2-g0fee61b (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash twisted-doc depends on no packages. Versions of packages twisted-doc recommends: ii elinks [www-browser]0.12~pre5-2 advanced text-mode WWW browser ii evince-gtk [postscript- 2.28.2-1 Document (postscript, pdf) viewer ii ghostscript [postscript 8.70~dfsg-2 The GPL Ghostscript PostScript/PDF ii gv [postscript-viewer] 1:3.6.8-1PostScript and PDF viewer for X ii iceweasel [www-browser] 3.5.6-1 lightweight web browser based on M ii kghostview [postscript- 4:3.5.9-3+lenny1 PostScript viewer for KDE ii konqueror [www-browser] 4:4.3.2-1KDE 4's advanced file manager, web ii kpdf [pdf-viewer] 4:3.5.9-3+lenny1 PDF viewer for KDE ii links [www-browser] 2.2-1+b1 Web browser running in text mode ii lynx-cur [www-browser] 2.8.8dev.2-1 Text-mode WWW Browser with NLS sup ii okular [postscript-view 4:4.3.4-1+b1 document viewer for KDE 4 pn twisted-doc-api(no description available) ii viewpdf.app [pdf-viewer 1:0.2dfsg1-3+b2 Portable Document Format (PDF) vie ii w3m [www-browser] 0.5.2-2.1WWW browsable pager with excellent ii xemacs21-mule [www-brow 21.4.22-2highly customizable text editor -- ii xemacs21-nomule [www-br 21.4.22-2highly customizable text editor -- ii xpdf-reader [pdf-viewer 3.02-1.4+lenny1 Portable Document Format (PDF) sui ii xpdf-utils [pdf-viewer] 3.02-1.4+lenny1 Portable Document Format (PDF) sui Versions of packages twisted-doc suggests: pn twisted(no description available) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564059: an: recommends obsolete wenglish
Package: an Version: 0.95-3.1 Severity: serious Should probably recommend wbritish as default wordlist instead. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28.10-smp-smp-2-g0fee61b (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages an depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries Versions of packages an recommends: ii wamerican [wordlist] 6-3American English dictionary words ii wbritish [wordlist] 6-3British English dictionary words f ii wenglish 5-4American English dictionary words ii wfrench [wordlist]1.2.3-7French dictionary words for /usr/s an suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564058: k3b: recommends obsolete kdebase-kio-plugins
Package: k3b Version: 1.0.5-3+b1 Severity: serious kdebase-kio-plugins doesnot exist in kde4 and has been removed from the archive. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.28.10-smp-smp-2-g0fee61b (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages k3b depends on: ii cdparanoia 3.10.2+debian-9 audio extraction tool for sampling ii cdrdao 1:1.2.2-18.1records CDs in Disk-At-Once (DAO) ii genisoimage 9:1.1.10-1 Creates ISO-9660 CD-ROM filesystem ii k3b-data 1.0.5-3 A sophisticated KDE CD burning app ii kdelibs-data 4:3.5.10.dfsg.1-2.1 core shared data for all KDE appli ii kdelibs4c2a 4:3.5.10.dfsg.1-2.1 core libraries and binaries for al ii libacl1 2.2.49-1Access control list shared library ii libart-2.0-2 2.3.20-2Library of functions for 2D graphi ii libattr1 1:2.4.44-1 Extended attribute shared library ii libaudio21.9.2-3 Network Audio System - shared libr ii libc62.10.2-2GNU C Library: Shared libraries ii libdbus-1-3 1.2.16-2simple interprocess messaging syst ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst ii libdvdread4 4.1.3-7 library for reading DVDs ii libexpat12.0.1-6 XML parsing C library - runtime li ii libfam0 2.7.0-16.1 Client library to control the FAM ii libfontconfig1 2.8.0-2 generic font configuration library ii libfreetype6 2.3.11-1FreeType 2 font engine, shared lib ii libgcc1 1:4.4.2-8 GCC support library ii libhal1 0.5.14-1Hardware Abstraction Layer - share ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library ii libidn11 1.15-2 GNU Libidn library, implementation ii libjpeg626b-15 The Independent JPEG Group's JPEG ii libk3b3 1.0.5-3+b1 The KDE cd burning application lib ii libmusicbrainz4c2a 2.1.5-3 Second generation incarnation of t ii libpng12-0 1.2.41-1PNG library - runtime ii libqt3-mt3:3.3.8b-6 Qt GUI Library (Threaded runtime v ii libsm6 2:1.1.1-1 X11 Session Management library ii libstdc++6 4.4.2-8 The GNU Standard C++ Library v3 ii libx11-6 2:1.3.2-1 X11 client-side library ii libxcursor1 1:1.1.10-1 X cursor management library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft2 2.1.14-1FreeType-based font drawing librar ii libxi6 2:1.2.1-2 X11 Input extension library ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library ii libxrandr2 2:1.3.0-2 X11 RandR extension library ii libxrender1 1:0.9.5-1 X Rendering Extension client libra ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library ii wodim9:1.1.10-1 command line CD/DVD writing tool ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages k3b recommends: ii dvd+rw-tools 7.1-6 DVD+-RW/R tools pn kcontrol (no description available) ii kdebase-kio-plugins4:3.5.10.dfsg.1-2 core I/O slaves for KDE ii libk3b3-extracodecs1.0.5-3+b1The KDE cd burning application lib ii vcdimager 0.7.23-4+b2 A VideoCD (VCD) image mastering an Versions of packages k3b suggests: pn k3b-i18n (no description available) pn movixmaker-2 (no description available) pn normalize-audio(no description available) ii sox 14.3.0-1.1 Swiss army knife of sound processi ii toolame 02l-7 MPEG-1 layer 2 audio encoder -- 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#557781: apt-proxy: lacks dep on zope.interface
Package: apt-proxy Version: 1.9.36.3+nmu2 Severity: serious While updating today both apt-proxy and zope.interface, I got the following error. It looks like apt-proxy requires zope.interface but does not declare a dependency on it. Shouldn't lintian detect such problems ? Paramétrage de apt-proxy (1.9.36.3+nmu2) ... update-rc.d: warning: apt-proxy stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (1) insserv: warning: current stop runlevel(s) (0 1 6) of script `apt-proxy' overwrites defaults (1). insserv: warning: current stop runlevel(s) (0 1 6) of script `pwrkap' overwrites defaults (empty). insserv: warning: current stop runlevel(s) (0 1 6) of script `cpufrequtils' overwrites defaults (empty). Starting apt-proxy:Traceback (most recent call last): File "/usr/bin/twistd", line 20, in from twisted.scripts.twistd import run File "/usr/lib/python2.5/site-packages/twisted/scripts/twistd.py", line 11, in from twisted.application import app File "/usr/lib/python2.5/site-packages/twisted/application/app.py", line 7, in from twisted.python import runtime, log, usage, failure, util, logfile File "/usr/lib/python2.5/site-packages/twisted/python/log.py", line 17, in from zope.interface import Interface ImportError: No module named interface failed! [...] Paramétrage de python-zope.interface (3.5.2-2) ... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt-proxy depends on: ii adduser 3.111 add and remove users and groups ii bzip21.0.5-3 high-quality block-sorting file co ii debconf [debconf-2.0]1.5.28 Debian configuration management sy ii logrotate3.7.8-4 Log rotation utility ii python 2.5.4-2 An interactive high-level object-o ii python-apt 0.7.13.3Python interface to libapt-pkg ii python-central 0.6.12+nmu1 register and build utility for Pyt ii python-twisted-web 8.2.0-2 An HTTP protocol implementation to apt-proxy recommends no packages. Versions of packages apt-proxy suggests: ii rsync 3.0.6-1fast remote file copy program (lik -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#557652: gct: git support is outdated (still uses dash-form of commands)
Package: commit-tool Version: 0.4-4 Severity: serious Justification: Policy 3.5 gct will not work with versions of git-core 1.6.0 and newer, since the "git-" form of commands is not installed any more since this version: $ gct Traceback (most recent call last): File "/usr/bin/gct", line 45, in ? main.main() File "main.py", line 513, in main File "git.py", line 34, in initialize File "ctcore.py", line 108, in runProgram ctcore.ProgramError: git-diff-files --name-only -z: No such file or directory It should be pretty easy to hunt the code for occurences of "git-" and adapt it (although the peculiar packaging used prevents quickly testing this on-site with a substitution). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages commit-tool depends on: ii git-core 1:1.6.5.3-1 fast, scalable, distributed revisi ii mercurial1.3.1-1 scalable distributed version contr ii python-qt3 3.18.1-2Qt3 bindings for Python ii python-support 1.0.4 automated rebuilding support for P ii python2.42.4.6-2.2 An interactive high-level object-o commit-tool recommends no packages. commit-tool suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#557054: tulip-doc and libmesh-doc: error when trying to install together
On Fri, Nov 20, 2009 at 01:29:36PM -0500, Adam C Powell IV wrote: > Hi, > > It seems that it would not be hard to resolve this by using > /etc/alternatives to select between the four files in these two > packages. Here's what I propose (for postinst): > > update-alternatives --install /usr/share/man/man3/std.3.gz std.3.gz > /usr/share/man/man3/std_libmesh.3.gz 10 \ > --slave /usr/share/man/man3/Point.3.gz Point.3.gz > usr/share/man/man3/Point_libmesh.3.gz \ > --slave /usr/share/man/man3/Sphere.3.gz Sphere.3.gz > usr/share/man/man3/Sphere_libmesh.3.gz \ > --slave /usr/share/man/man3/Triangle.3.gz Triangle.3.gz > usr/share/man/man3/Triangle_libmesh.3.gz > > and you can change _libmesh to _tulip, and we both undo them in prerm. > What do you think? When I saw all these manpages generated upstream, my 1st thought was that they would be better suited asi .3tulip section. That way at the same time we avoid namespace clutter, and we retain the "man Point" that may get suggested in other places (docs, forums, etc). That's even something for which we could push patches to our respective upstreams. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550715: gmchess: package split lacks Conflict/Replace decl
Package: eleeye, libeval0 Version: 0.20.3-1 Severity: serious (Lecture de la base de données... 319095 fichiers et répertoires déjà installés.) Dépaquetage de libeval0 (à partir de .../libeval0_0.20.3-1_i386.deb) ... dpkg : erreur de traitement de /var/cache/apt/archives/libeval0_0.20.3-1_i386.deb (--unpack) : tentative de remplacement de « /usr/lib/libeval.so.0.0.0 », qui appartient aussi au paquet gmchess Sélection du paquet eleeye précédemment désélectionné. Dépaquetage de eleeye (à partir de .../eleeye_0.20.3-1_i386.deb) ... dpkg : erreur de traitement de /var/cache/apt/archives/eleeye_0.20.3-1_i386.deb (--unpack) : tentative de remplacement de « /usr/games/eleeye_engine », qui appartient aussi au paquet gmchess Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libeval0_0.20.3-1_i386.deb /var/cache/apt/archives/eleeye_0.20.3-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#547283: nm plasmoid: completely unusable since upgrade
Package: plasma-widget-networkmanagement Version: 0.1~svn1013816-1 Severity: serious Since I have updated the nm plasmoid (not sure it is the last update that caused the problem), it is completely broken: - displays an icon looking like a cellular phone (but a zoomed low-res B&W icon) - no network-managing functionnality when clicking on it What happenned ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#546764: d-feet: should depend on hicolor-icon-theme
Package: d-feet Version: 0.1.8-2 Severity: serious Without this package installed, d-feet spits out tons of exceptions about missing icons when connecting to a bus, selected a given busname performs similarly, and the "object paths" list for the selected busname stays empty. Installing hicolor-icon-theme solves all of this. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526538: marked as pending
On Mon, May 04, 2009 at 07:07:40PM +, Raphael Hertzog wrote: > Bug #526538 reported by you has been fixed in the Git repository. You can > see the changelog below, and you can check the diff of the fix at: > > http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=45a7adc Thanks. Wouldn't it make sense as well to issue a warning when the alternative is registered but something by that name already exists ? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526837: Acknowledgement (libsynopsis0.12: conflict with 0.10)
After checking, it looks like the .so.0 symlinks is useless. It can simply be dropped from the 0.12 package, so no declaration of conflict will be required. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526837: libsynopsis0.12: conflict with 0.10
Package: libsynopsys0.12 Version: 0.12-1 Severity: serious Unpacking libsynopsis0.12 (from .../libsynopsis0.12_0.12-1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsynopsis0.12_0.12-1_i386.deb (--unpack): trying to overwrite `/usr/lib/libSynopsis.so.0', which is also in package libsynopsis0.10 I do not remember if I spotted that before, but that seems to imply the lib package does not patch the soname, and possibly that the soname is too fuzzy. We should check this with Stafan (CC'd). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) 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#526538: update-alternatives --remove: deletes file without checking it is a symlink
Package: dpkg Version: 1.14.26 Severity: critical When aptitude-gtk appeared in experimental I installed it just to test, but kept aptitude itself from sid or testing. When the new version added a versionned dep on aptitude, I decided to remove it rather than upgrading aptitude itself to experimental. Then I was left with /usr/bin/aptitude non existent. Looking at the new postinst I noticed the experimental packages now use alternatives, so I sorta replayed what had happenned: * at install time: # update-alternatives --install /usr/bin/aptitude aptitude /bin/ls 60 # ls -l /usr/bin/aptitude -rwxr-xr-x 1 root root 2113556 Nov 20 05:10 /usr/bin/aptitude # ls -l /etc/alternatives/aptitude lrwxrwxrwx 1 root root 7 May 1 22:13 /etc/alternatives/aptitude -> /bin/ls It is dubious that --install would even not issue a warning that /usr/bin/aptitude was already there without being a symlink at first. I even think it should be made an error. * then at uninstall time: # update-alternatives --remove aptitude /bin/ls # ls -l /etc/alternatives/aptitude ls: cannot access /etc/alternatives/aptitude: No such file or directory # ls -l /usr/bin/aptitude ls: cannot access /usr/bin/aptitude: No such file or directory Unconditionnal removal of an unrelated file without any check was surely not wanted. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 7.2-1 The GNU core utilities ii libc6 2.9-4 GNU C Library: Shared libraries ii lzma 4.43-14Compression method of 7z format in dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.7.20.2 Advanced front-end for dpkg -- 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#525406: git-core: needs conflict with build-cola
Package: git-core Version: 1:1.6.3~rc1-1 Severity: serious Preparing to replace git-core 1:1.6.2.4-1 (using .../git-core_1%3a1.6.3~rc1-1_i386.deb) ... Unpacking replacement git-core ... dpkg: error processing /var/cache/apt/archives/git-core_1%3a1.6.3~rc1-1_i386.deb (--unpack): trying to overwrite `/usr/share/man/man1/git-difftool.1.gz', which is also in package git-cola dpkg-deb: subprocess paste killed by signal (Broken pipe) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#476008: Tulip unbuildable
On Sat, Feb 28, 2009 at 04:26:19PM +0200, Riku Voipio wrote: > Yann Dirson wrote: > > Hm, looks like it would be a better idea to upgrade to the final > > release, which was released last week. I'll have more time for this > > next week. > > Hi, any time to update tulip? It would be a shame to have to ask for > removal of this package. Tulip seems to provide unique functionality > and have a active upstream. Yes, I'll try to update it soon. I just hope I'll have less problems than the last time I wanted to, where it did not build at all on my box :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#489510: tailor: syntax error in bzr.py with python 2.4
Package: tailor Version: 0.9.35-1 Severity: serious Processing triggers for python-support ... Compiling /var/lib/python-support/python2.4/vcpx/repository/bzr.py ... File "/var/lib/python-support/python2.4/vcpx/repository/bzr.py", line 276 yield self._changesetFromRevision(parent_branch, revision) SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages tailor depends on: ii python2.5.2-1An interactive high-level object-o ii python-support0.8.1 automated rebuilding support for P Versions of packages tailor recommends: ii rsync 3.0.2-2fast remote file copy program (lik -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486112: k3b: file conflict in libk3b3-extracodecs
Package: libk3b3-extracodecs Version: 1.0.5-2 Severity: serious Dépaquetage de libk3b3-extracodecs (à partir de .../libk3b3-extracodecs_1.0.5-2_i386.deb) ... dpkg : erreur de traitement de /var/cache/apt/archives/libk3b3-extracodecs_1.0.5-2_i386.deb (--unpack) : tentative de remplacement de « /usr/lib/kde3/libk3bmaddecoder.la », qui appartient aussi au paquet libk3b3 Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libk3b3-extracodecs_1.0.5-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) libk3b3 on system is 1.0.4-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#485752: dogtail: [DoS] use of /tmp/dogtail prevents use by multiple users
Package: python-dogtail Version: 0.6.1-3 Severity: serious Dogtail systematically create logfiles in /tmp/dogtail/. The 1st user to run a script using dogtail (including the sniff gui) wins, and no other user can use dogtail any more until that dir is manually removed. >>> from dogtail import * Creating /tmp/dogtail ... Creating /tmp/dogtail/logs ... Creating /tmp/dogtail/data ... Creating logfile at /tmp/dogtail/logs/log_20080611-101107_debug ... Detecting distribution: Debian (or derived distribution) Warning: AT-SPI's desktop is visible but it has no children. Are you running any AT-SPI-aware applications? Creating logfile at /tmp/dogtail/logs/log_20080611-101108_results ... >>> $ ls -ld /tmp/dogtail drwxr-xr-x 4 yann yann 80 jun 11 10:11 /tmp/dogtail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480948: boost 1.35: missing dependencies
Package: libboost1.35-dev Version: 1.35.0-1 Severity: serious There seem to be numerous dependency problems in the current 1.35 packaging - compiling synopsis --with-boost I hit the following ones: * -filesystem requires -system: In file included from conftest.cpp:10: /usr/include/boost/filesystem/path.hpp:16:41: error: boost/system/system_error.hpp: No such file or directory * -thread requires -date-time: In file included from /usr/include/boost/thread/locks.hpp:11, from /usr/include/boost/thread/pthread/mutex.hpp:11, from /usr/include/boost/thread/mutex.hpp:16, from /usr/include/boost/thread/pthread/thread.hpp:14, from /usr/include/boost/thread/thread.hpp:17, from /usr/include/boost/thread.hpp:12, from conftest.cpp:10: /usr/include/boost/thread/thread_time.hpp:9:51: error: boost/date_time/microsec_time_clock.hpp: No such file or directory /usr/include/boost/thread/thread_time.hpp:10:59: error: boost/date_time/posix_time/posix_time_types.hpp: No such file or directory * stuff in -dev itself references -serialization: In file included from /usr/include/boost/multi_index/detail/node_type.hpp:23, from /usr/include/boost/multi_index/detail/index_base.hpp:21, from /usr/include/boost/multi_index/detail/base_type.hpp:21, from /usr/include/boost/multi_index_container.hpp:33, from /usr/include/boost/wave/util/cpp_include_paths.hpp:21, from /usr/include/boost/wave/cpp_context.hpp:32, from /usr/include/boost/wave.hpp:21, from conftest.cpp:10: /usr/include/boost/multi_index/detail/index_node_base.hpp:22:42: error: boost/serialization/access.hpp: No such file or directory This seems to be because of the strange ifdef reproduced below, which unless defined adds an unsuspected dep in a core module: #if !defined(BOOST_MULTI_INDEX_DISABLE_SERIALIZATION) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libboost-filesystem1.35-dev depends on: ii libboost-filesystem1.35.0 1.35.0-1 filesystem operations (portable pa ii libboost1.35-dev 1.35.0-1 Boost C++ Libraries development fi libboost-filesystem1.35-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479327: tulip misses dependencies and crashes
On Sun, May 04, 2008 at 12:44:00PM +0200, Sam Hocevar wrote: >Hi! I have been unable to get the Debian tulip packages to work: > dependencies are missing, and the program crashes. Hm, that looks like an annoying consequence of the split of qt4 into more binary packages. A rebuild is likely enough to fix it. I'll also have to package the final 3.0.0 one day - but since I have had problems with B7, I'm not sure it will go that smoothly, so better make B6 suitable for release first :) Best regards, -- Yann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476158: found 476158 in 0.8.0-5
# Automatically generated email from bts, devscripts version 2.10.25 # let's help debbugs graph thins right found 476158 0.8.0-5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476158: fixed 476158 in 0.10-0.1
# Automatically generated email from bts, devscripts version 2.10.25 # fixed upstream in 0.10 fixed 476158 0.10-0.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#476008: tulip: FTBFS: ../../../../software/tulip/src/viewGl.cpp:190: error: 'icon' is not a member of 'Ui_TulipData'
On Tue, Apr 15, 2008 at 11:55:18PM +0100, Ben Hutchings wrote: > Unfortunately the resulting executable crashes. Seems like there's > another incompatibility with Qt 4.4. Hm, looks like it would be a better idea to upgrade to the final release, which was released last week. I'll have more time for this next week. Best regards, -- Yann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
