Bug#567554: [Pkg-samba-maint] Bug#567554: Privilege escalation in mount.cifs
On Sun, Jan 31, 2010 at 01:09:22PM +0100, Christian PERRIER wrote: > Quoting Moritz Muehlenhoff (j...@debian.org): > > Package: smbfs > > Severity: grave > > Tags: security > > > > This is CVE-2009-3297: > > https://bugzilla.samba.org/show_bug.cgi?id=6853 > > > > /usr/share/doc/smbfs/TODO.Debian states: > > There is concern about the setuid status of binaries in this package. > > The audit status of the concerned binaries is unclear. We should > > figure out whether it is reasonable to provide the flexible user mount > > capabilities or whether a more restricted setup is better, at least by > > default. > > Given that Jeremy Allison writes in the bug above you should probably > > drop the setuid for Squeeze: > My concern here is that it would definitely be a regression for users > who rely on user mounting of CIFS volumes. > A compromise could be a debconf question about adding the setuid bit > to mount.cifs (with a default to False, of course). > Steve, your advice? Upstream has been increasingly unsupportive of this configuration over time, and given Jeremy's latest comments on this bug, I think the only reasonable action here is to drop support for this is the package entirely and document it in NEWS.Debian on upgrade. (Users who must have this continue to work can use dpkg-statoverride to set the suid bit; but I wouldn't even suggest that in NEWS.Debian, because users shouldn't be encouraged to set programs suid when they're not meant to be used that way.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: reassign 567915 to iceweasel, cloning 567915, cloning 567915, cloning 567915, cloning 567915 ...
Processing commands for cont...@bugs.debian.org: > reassign 567915 iceweasel Bug #567915 [iceweasel,iceape,icedove,iceowl] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel,iceape,icedove,iceowl' to 'iceweasel'. > clone 567915 -1 Bug#567915: iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug 567915 cloned as bug 567917. > clone 567915 -2 Bug#567915: iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug 567915 cloned as bug 567918. > clone 567915 -3 Bug#567915: iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug 567915 cloned as bug 567919. > clone 567915 -4 Bug#567915: iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug 567915 cloned as bug 567920. > reassign -1 icedove Bug #567917 [iceweasel] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel' to 'icedove'. > reassign -2 iceape Bug #567918 [iceweasel] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel' to 'iceape'. > reassign -3 iceowl Bug #567919 [iceweasel] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel' to 'iceowl'. > reassign -4 xulrunner Bug #567920 [iceweasel] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel' to 'xulrunner'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: cloning 567915, reassign -1 to kompozer
Processing commands for cont...@bugs.debian.org: > clone 567915 -1 Bug#567915: iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug 567915 cloned as bug 567922. > reassign -1 kompozer Bug #567922 [iceweasel] iceweasel, iceape, icedove, iceowl: Contains non-free data in the source tarball Bug reassigned from package 'iceweasel' to 'kompozer'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567860: php-net-ping: Package installation is trying to overwrite '/usr/share/php/doc'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dario Minnucci wrote: > Hi Maintainer, > > It's not possible to instal php-net-ping because is trying > to overwrite '/usr/share/php/doc', which is also in > package php-pear. > > Here is the install log. Hi, If I had upload rights, it would be months that all issues would be fixed on that package. I've been searching for a sponsor for MONTHS to have it uploaded. The URL for the updated package is: http://ftparchive.gplhost.com/debian/pool/lenny/main/p/php-net-ping/php-net-ping_2.4.5-1.dsc I'd be glad if someone uploaded the package for me, until I am approved to be a DD by my AM. Please consider. Also note that the updated package also contains the latest security patch made by the security team, and some more that I added myself to check if the give parameter is really an IP. So since SID has been updated to php 5.3, I'd have to use preg_match instead of ereg, as this will create a notice. Apart from that the package is ready ... I'll be uploading the fix to use preg_match soon. Thomas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktmjboACgkQl4M9yZjvmkkRDQCg2UD3hLfu3uuoOZ2Z08xjFBdy 5KoAniLVycS9qfl+LKOpSLD60pzseB3y =iR7i -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 562606 is serious
Processing commands for cont...@bugs.debian.org: > severity 562606 serious Bug #562606 [ocaml] FTBFS: unknown options to dh_ocaml Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567696: emms: diff for NMU version 3.0-5.1
Arnaud Fontaine wrote: > Hi, > > I have already prepared a package with a patch for #567696 too. I will > upload it tomorrow. Hope that's ok. > Sure. I'm happy to see this bug go away :-) Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562606: FTBFS: unknown options to dh_ocaml
Hi Mehdi, On Saturday 30 January 2010 14:47:34 Mehdi Dogguy wrote: > > Who should do backports in your eyes? Debian Developers? Maintainers? > > Nobody? > > Certainly, not users. And, let's make that clear: it's not "in my eyes". > Ask other DDs or DMs about this particular question if you want to have > another opinion. At least, ask the usual maintainer for review before > proposing a backport. Doing otherwise seems wrong to me (unless you are > very confident with the code). thats you POV, there maybe others. Most maintainers don't care about backporting (like about their packages in stable and even old-stable). > > Anyways ... you should provide correct (build-)dependencies, even if it > > would be better, if debhelper would provide a way to define such > > versioned dep for its own. > > We already provide correct build-dependencies. Here, the only missing > thing is that our dh_ocaml uses features from debhleper 7.1.0. The > package dh-ocaml do not contain only the dh_ocaml script and ocaml > sequence, but also some other dev-tools. I see two solutions: > > - Make dh-ocaml depend on debhelper >= 7.1.0 (the exact version that > introduced the desired feature). But, I'm not really convinced that this > is the right solution because we may use all what dh-ocaml ships but > dh_ocaml. > > - Make dh-ocaml conflicts with debhelper << 7.1.0. But this solution > seems also wrong for the same reason I mentioned before. Sorry, I strongly disagree. I don't see any reason to not provide the correct versioned build-dep. You package is failing to build from source, if you need special versions of a package, you have to provide a correct control file. > If you have a better/real solution, please share with us. > If not, I will not accept any of the solutions I've mentioned because > the problem arises *only* for the backport. Sorry ... this is exactly the point, why people mostly don't contact maintainers _before_ creating backports ... the ignorance of package maintainers about backporting. You are a good example for such behavior. With kind regards, Jan. -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part.
Bug#567882: gnucash: Postinst broken due to invalid schema file
Hi Javier,
I cannot reproduce your problem here, even with your locales (to exclude
locale specific errors):
(sid)ian:~# locale
LANG=es_AR.UTF-8
LC_CTYPE="es_AR.UTF-8"
LC_NUMERIC="es_AR.UTF-8"
LC_TIME="es_AR.UTF-8"
LC_COLLATE="es_AR.UTF-8"
LC_MONETARY="es_AR.UTF-8"
LC_MESSAGES="es_AR.UTF-8"
LC_PAPER="es_AR.UTF-8"
LC_NAME="es_AR.UTF-8"
LC_ADDRESS="es_AR.UTF-8"
LC_TELEPHONE="es_AR.UTF-8"
LC_MEASUREMENT="es_AR.UTF-8"
LC_IDENTIFICATION="es_AR.UTF-8"
LC_ALL=
(sid)ian:~# aptitude --without-recommends install gnucash
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Leyendo la información de estado extendido... Hecho
Inicializando el estado de los paquetes... Hecho
Se instalarán los siguiente paquetes NUEVOS:
gnucash gnucash-common{a} libdate-manip-perl{a}
Se RECOMIENDAN los siguientes paquetes, pero NO se instalarán:
gnucash-docs
0 paquetes actualizados, 3 nuevos instalados, 0 para eliminar y 37 sin
actualizar.
Necesito descargar 0B/9.133kB de ficheros. Después de desempaquetar se
usarán 42,8MB.
¿Quiere continuar? [Y/n/?]
Escribiendo información de estado extendido... Hecho
No se pudo escbribir en el registro, falló la llamada a «openpty()»
(¿está montado /dev/pts?)
Seleccionando el paquete gnucash-common previamente no seleccionado.
(Leyendo la base de datos ... 00%
101487 ficheros y directorios instalados actualmente.)
Desempaquetando gnucash-common (de .../gnucash-common_2.2.9-3_all.deb) ...
Seleccionando el paquete libdate-manip-perl previamente no seleccionado.
Desempaquetando libdate-manip-perl (de
.../libdate-manip-perl_6.05-1_all.deb) ...
Seleccionando el paquete gnucash previamente no seleccionado.
Desempaquetando gnucash (de .../gnucash_2.2.9-3_i386.deb) ...
Procesando disparadores para man-db ...
Procesando disparadores para install-info ...
Procesando disparadores para hicolor-icon-theme ...
Procesando disparadores para menu ...
No se pudo escbribir en el registro, falló la llamada a «openpty()»
(¿está montado /dev/pts?)
Configurando gnucash-common (2.2.9-3) ...
Configurando libdate-manip-perl (6.05-1) ...
Configurando gnucash (2.2.9-3) ...
Procesando disparadores para menu ...
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Leyendo la información de estado extendido... Hecho
Inicializando el estado de los paquetes... Hecho
Escribiendo información de estado extendido... Hecho
(sid)ian:~#
Do you have enough space on all of your hard disk partitions?
Regards
Micha
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567877: vtk: source package will not build
severity 567877 normal thanks 2010/1/31 Lee Azzarello : > Package: vtk > Version: vtk-5.4.2 > Severity: serious > Justification: Policy 4.2 > > Fails to build from source. Error when linking to the TCL executable. > > make[3]: Entering directory `/home/lee/bsp/vtk-5.4.2/Build' > [100%] Building CXX object > Wrapping/Tcl/CMakeFiles/pvtk.dir/vtkParaTkAppInit.cxx.o > Linking CXX executable ../../bin/pvtk > ../../bin/libvtkIOTCL.so.5.4.2: undefined reference to `dirac_decoder_close' > ../../bin/libvtkIOTCL.so.5.4.2: undefined reference to `dirac_encoder_close' > ../../bin/libvtkIOTCL.so.5.4.2: undefined reference to `theora_info_clear' > ../../bin/libvtkIOTCL.so.5.4.2: undefined reference to `dirac_parse' [...] Hi, I am downgrading severity; VTK obviously builds fine, see https://buildd.debian.org/build.cgi?pkg=vtk Either there is an error on your side, or some build dependencies must be versioned. Did you install ffmpeg related packages from another source? Denis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#567877: vtk: source package will not build
Processing commands for cont...@bugs.debian.org: > severity 567877 normal Bug #567877 [vtk] vtk: source package will not build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#460338: It renders apt-proxy unusable
Hi, Le Wed, 27 Jan 2010 22:43:31 +0100, "Francesco P. Lovergine" a écrit : > severity 460338 grave > thanks > I agree to raise the severity of this bug as it renders the package unusable. > I finally removed today apt-proxy in my work LAN because this hanging > onto update is a too common pattern and renders the package unusable > since lenny release. > > I found apt-cacher-ng much more usable, and I'm inclined in proposing > removal of the package if none had something to say against that. > In the past month, I've tried to have apt-proxy's package in a better shape, but the number of bugs related to the core part of the application is really high and really requires a core developer to fix them. As apt-proxy do not have anymore any active developper but only some package maintainers, and taking into account the number of bugs filed for apt-proxy, I think it's a reasonable proposition to remove apt-proxy from the archive. Is anyone against this proposition ? Cheer, Xavier -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567925: gdbserver: File conflict with gdb; need Replaces
Package: gdbserver Version: 7.0.1-1 Severity: serious Justification: Policy 7.6 Unpacking gdbserver (from .../gdbserver_7.0.1-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/gdbserver_7.0.1-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/gdbserver.1.gz', which is also in package gdb 0:7.0-1 - Josh Triplett -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdbserver depends on: ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib gdbserver recommends no packages. gdbserver 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#562606: FTBFS: unknown options to dh_ocaml
Jan Wagner wrote: > Hi Mehdi, > > On Saturday 30 January 2010 14:47:34 Mehdi Dogguy wrote: >>> Who should do backports in your eyes? Debian Developers? Maintainers? >>> Nobody? >> Certainly, not users. And, let's make that clear: it's not "in my eyes". >> Ask other DDs or DMs about this particular question if you want to have >> another opinion. At least, ask the usual maintainer for review before >> proposing a backport. Doing otherwise seems wrong to me (unless you are >> very confident with the code). > > thats you POV, there maybe others. Most maintainers don't care about > backporting (like about their packages in stable and even old-stable). > It requires more work! That's the main reason. Most of the time, we don't have time for that because we want to dedicate free time to fix RC bugs or to prepare the next stable release. Sometimes, we do some backports when it's really needed (e.g. when another team needs a particular version of a package in Stable (or whatever)). We are happy to do it when there is valid reasons behind. Most people are happy with Stable and Old-stable exactly how they are because they are feature-frozen and only security/important bugs are fixed in those versions. And, please don't make false assumptions. In our team, we try very hard to fix any problem that arises in any of our packages in stable or old-stable. >>> Anyways ... you should provide correct (build-)dependencies, even if it >>> would be better, if debhelper would provide a way to define such >>> versioned dep for its own. >> We already provide correct build-dependencies. Here, the only missing >> thing is that our dh_ocaml uses features from debhleper 7.1.0. The >> package dh-ocaml do not contain only the dh_ocaml script and ocaml >> sequence, but also some other dev-tools. I see two solutions: >> >> - Make dh-ocaml depend on debhelper >= 7.1.0 (the exact version that >> introduced the desired feature). But, I'm not really convinced that this >> is the right solution because we may use all what dh-ocaml ships but >> dh_ocaml. >> >> - Make dh-ocaml conflicts with debhelper << 7.1.0. But this solution >> seems also wrong for the same reason I mentioned before. > > Sorry, I strongly disagree. I don't see any reason to not provide the correct > versioned build-dep. You package is failing to build from source, if you need > special versions of a package, you have to provide a correct control file. > Just recalling the problem so that other members can follow more easily: OCaml is failing to build from source because dh-ocaml needs a particular version of Debhelper at *runtime*. OCaml already depends on the good version of dh-ocaml which provides runtime-map and checksum options. Dh-ocaml indeed needs Debhelper 7.1.0 to have these options working correctly. dh-ocaml will not see his depends changing (just like the quilt package do). We might correct to build-dep for OCaml (and we will certainly need to make a lintian warning which says that Debhelper 7.1.0 is needed when using "dh --with ocaml"). >> If you have a better/real solution, please share with us. >> If not, I will not accept any of the solutions I've mentioned because >> the problem arises *only* for the backport. > > Sorry ... this is exactly the point, why people mostly don't contact > maintainers _before_ creating backports ... the ignorance of package > maintainers about backporting. You are a good example for such behavior. > I'm sorry but I disagree. I do care about my packages (for any version). But, sometimes the correct fix is not obvious. It doesn't mean I don't want to fix the bug but that I looking for a good fix. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567926: gpgsm: passphrase changing issue with X509 certificates (Werner Koch 26th of January 2010)
Package: gpgsm Version: 2.0.14-1 Severity: grave Justification: causes non-serious data loss Werner Koch discovered a problem with passphrases for x509 certificates in 2.0.14, he also send around a patch on 2010-01-26, e.g. see: http://marc.info/?l=gnupg-users&m=126451730710129&w=2 This has a data loss scenario, given a few conditions you cannot use your keys anymore: | If you now try to use the key and enter the passphrase, | gpg-agent uses the wrong iteration count from the file (65536) and thus | can't unprotect the key. Bernhard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#545849: gnudatalanguage: FTBFS: muldefs: No such file or directory
Here's an updated package, possibly fixing the bug (can't test it without hppa) http://gnu.ethz.ch/debian/gnudatalanguage/new/gnudatalanguage_0.9~rc3+20091203-1.dsc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567318: gnome-screensaver causes X session crash
Hello Josselin, Josselin Mouette a écrit: > Have you correctly checked Xorg.0.log.old after the crash? The > Xorg.0.log file is reset each time the server starts, and when it > crashes, it restarts. Shame on me! You are right! There was a fatal error logged in the Xorg.0.log.old but, I don't know why, I didn't see it before. :( You can find the whole log file at the url below: http://sebastien.dinot.free.fr/Xorg.0.log.old The fatal error is: Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0af8] 1: /usr/bin/X (0x40+0x641c9) [0x4641c9] 2: /lib/libpthread.so.0 (0x7ff97105a000+0xe990) [0x7ff971068990] 3: /usr/bin/X (xf86GetGammaRampSize+0x75) [0x527475] 4: /usr/lib/xorg/modules/extensions/libextmod.so (0x7ff96ddbe000+0xbdc5) [0x7ff96ddc9dc5] 5: /usr/bin/X (0x40+0x31524) [0x431524] 6: /usr/bin/X (0x40+0x25bca) [0x425bca] 7: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7ff96f950abd] 8: /usr/bin/X (0x40+0x25779) [0x425779] Segmentation fault at address 0x1b8 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Sebastien
Bug#562606: FTBFS: unknown options to dh_ocaml
On Monday 01 February 2010 10:39:50 Mehdi Dogguy wrote: > Jan Wagner wrote: > > On Saturday 30 January 2010 14:47:34 Mehdi Dogguy wrote: > >> Certainly, not users. And, let's make that clear: it's not "in my eyes". > >> Ask other DDs or DMs about this particular question if you want to have > >> another opinion. At least, ask the usual maintainer for review before > >> proposing a backport. Doing otherwise seems wrong to me (unless you are > >> very confident with the code). > > > > thats you POV, there maybe others. Most maintainers don't care about > > backporting (like about their packages in stable and even old-stable). > > It requires more work! That's the main reason. Most of the time, we > don't have time for that because we want to dedicate free time to fix RC > bugs or to prepare the next stable release. > Sometimes, we do some backports when it's really needed (e.g. when > another team needs a particular version of a package in Stable (or > whatever)). We are happy to do it when there is valid reasons behind. > Most people are happy with Stable and Old-stable exactly how they are > because they are feature-frozen and only security/important bugs are > fixed in those versions. Thats totally fine and I don't belive anybody is making a backport of ocaml just for fun. In my case it was a build-dep, needed by another package. > And, please don't make false assumptions. In our team, we try very hard > to fix any problem that arises in any of our packages in stable or > old-stable. I didn't jundged about your team nor was my intention to make false assumptions, it's just a fact for the whole project itself, see the list[1] of rc-bugs in stable. > Just recalling the problem so that other members can follow more easily: > OCaml is failing to build from source because dh-ocaml needs a > particular version of Debhelper at *runtime*. OCaml already depends on > the good version of dh-ocaml which provides runtime-map and checksum > options. Dh-ocaml indeed needs Debhelper 7.1.0 to have these options > working correctly. > > dh-ocaml will not see his depends changing (just like the quilt package > do). We might correct to build-dep for OCaml (and we will certainly need > to make a lintian warning which says that Debhelper 7.1.0 is needed when > using "dh --with ocaml"). > > >> If you have a better/real solution, please share with us. > >> If not, I will not accept any of the solutions I've mentioned because > >> the problem arises *only* for the backport. > > > > Sorry ... this is exactly the point, why people mostly don't contact > > maintainers _before_ creating backports ... the ignorance of package > > maintainers about backporting. You are a good example for such behavior. > > I'm sorry but I disagree. I do care about my packages (for any version). > But, sometimes the correct fix is not obvious. It doesn't mean I don't > want to fix the bug but that I looking for a good fix. So maybe I did missinterpret "I will not accept any of the solutions [...] because the problem arises *only* for the backport." Of course, looking for a good fix is indeed a strategy I strongly support. In my eyes, raising the build-dep of debhelper to ">= 7.1.0" just fixes ocaml, correct me, if I'm wrong. But adding a lintian check for the use dh_ocaml looks indeed like smart solution. Thanks and with kind regards, Jan. [1] http://bugs.debian.org/release-critical/other/stable.html -- Never write mail to , you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part.
Bug#567932: schroot: chroot failed, cleaned up my host /etc
Package: schroot Version: 1.4.0-1 Severity: critical Justification: causes serious data loss I upgraded schroot from 1.2.3-1+b1 to 1.4.0-1, which wanted to replace some config files, which I have customised. I declined, intending to fix it later. I started an schroot into an old sid 32-bit chroot (from my sid 64-bit host), and didn't notice any error messages, but found I was still running 64-bit binaries. I think the actual chroot() failed. Later after exitting, I found that a bunch of files in /etc were now empty: passwd, group, shadow, hosts, protocols, services. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages schroot depends on: ii libboost-filesystem1.40.01.40.0-6+b1 filesystem operations (portable pa ii libboost-program-options1.40 1.40.0-6+b1 program options library for C++ ii libboost-regex1.40.0 1.40.0-6+b1 regular expression library for C++ ii libboost-system1.40.01.40.0-6+b1 Operating system (e.g. diagnostics ii libc62.10.2-5Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.3-1 GCC support library ii liblockdev1 1.0.3-1.3 Run-time shared library for lockin ii libpam0g 1.1.0-4 Pluggable Authentication Modules l ii libstdc++6 4.4.3-1 The GNU Standard C++ Library v3 ii libuuid1 2.16.2-0Universally Unique ID library ii schroot-common 1.4.0-1 common files for schroot schroot recommends no packages. Versions of packages schroot suggests: pn aufs-modules | unionfs-module (no description available) ii debootstrap 1.0.20 Bootstrap a basic Debian system ii lvm2 2.02.54-1 The Linux Logical Volume Manager ii unzip 6.0-1 De-archiver for .zip files -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#567318: gnome-screensaver causes X session crash
Processing commands for cont...@bugs.debian.org: > reassign 567318 xserver-xorg Bug #567318 [gnome-screensaver] gnome-screensaver causes X session crash Bug reassigned from package 'gnome-screensaver' to 'xserver-xorg'. Bug No longer marked as found in versions gnome-screensaver/2.28.0-2. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567318: gnome-screensaver causes X session crash
reassign 567318 xserver-xorg thanks Le lundi 01 février 2010 à 10:20 +0100, Sebastien Dinot a écrit : > You can find the whole log file at the url below: > > http://sebastien.dinot.free.fr/Xorg.0.log.old > > The fatal error is: > > __ > Backtrace: > 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0af8] > 1: /usr/bin/X (0x40+0x641c9) [0x4641c9] > 2: /lib/libpthread.so.0 (0x7ff97105a000+0xe990) [0x7ff971068990] > 3: /usr/bin/X (xf86GetGammaRampSize+0x75) [0x527475] > 4: /usr/lib/xorg/modules/extensions/libextmod.so (0x7ff96ddbe000 > +0xbdc5) [0x7ff96ddc9dc5] > 5: /usr/bin/X (0x40+0x31524) [0x431524] > 6: /usr/bin/X (0x40+0x25bca) [0x425bca] > 7: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7ff96f950abd] > 8: /usr/bin/X (0x40+0x25779) [0x425779] > Segmentation fault at address 0x1b8 OK, reassigning. I guess the X maintainers will ask you for more debugging information. -- .''`. Josselin Mouette : :' : `. `' “A handshake with whitnesses is the same `- as a signed contact.” -- Jörg Schilling -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566518: nvidia-vdpau-driver: bad /usr/lib/libvdpau_nvidia.so symlink
Package: nvidia-vdpau-driver Version: 190.53-1 Severity: grave Hello, I finally got vdpa work on my debian box with the 190.53-1 nvidia driver !! Here is the way to go : 1. Install all nvidia packages except nvidia-libvdpau1, it isn't needed. 2. Install libvdpau1 package instead. It provides the libvdpau wrapper library, the libvdpau_trace debugging library and the header files. It is a freely licensed alternative to the nvidia-libvdpau1 package. 3. Modify /usr/lib/libvdpau_nvidia.so symlink to link to /usr/lib/vdpau/libvdpau.so.190.5. Thanks Remi Vanicat for this one :) Really important links to understand what happens : * http://lists.freedesktop.org/archives/xorg-announce/2009-September/001036.html * http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/9cfd7bf03f52d806/f0027a1e9cb69c4b?lnk=gst&q=547248#f0027a1e9cb69c4b Thanks, Jonathan Dray -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (90, 'testing') Architecture: i686 Kernel: Linux 2.6.32-trunk-i686 (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/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551250: Fix for libmatio FTBFS
Hello, as the package also FTBFS in Ubuntu lucid I looked if I can find the cause and a possible fix for it. The problem is ,[ excerpt from doxygen/latex/refman.log ]- | ! LaTeX Error: File `a4.sty' not found. ` Thus the fix is simple: add texlive-latex-recommended to Build-Depends. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562606: FTBFS: unknown options to dh_ocaml
Jan Wagner wrote: > > So maybe I did missinterpret "I will not accept any of the solutions [...] > because the problem arises *only* for the backport." I'd translate it by "None of solutions I've mentioned are satisfying. It's not clear to me how to fix it". I agree that it wasn't clear[1] :) Regards, [1] at all. -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#536352: closing 536352
# the bts thinks the bug is still open, fix it close 536352 thanks -- Mit freundlichen GrüÃen, Christoph Berg -- Tel.: +49 (0)21 61 / 46 43-187 credativ GmbH, HRB Mönchengladbach 12080 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: closing 536352
Processing commands for cont...@bugs.debian.org: > # the bts thinks the bug is still open, fix it > close 536352 Bug#536352: â¯ettercap: FTBFS due to missing B-D 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Cyril Brulebois > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: insserv blocks packages upgrade, permission denied
Package: insserv Version: 1.12.0-14 Severity: grave Justification: renders package unusable Upgrade of many packages failes because of these errors: insserv: fopen(K01exim4): Permission denied update-rc.d: error: insserv rejected the script header Packages, producing errors: sane-utils (1.0.20-13) ... module-init-tools (3.12~pre1-1) ... privoxy (3.0.15-3) ... procps (1:3.2.8-3) ... netbase (4.40) ... openbsd-inetd (0.20080125-4) ... and so on. insserv hwclock.sh from util-linux package also fails. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.7 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages insserv depends on: ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib insserv recommends no packages. Versions of packages insserv suggests: pn bootchart (no description available) -- debconf information: insserv/enable: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562606: FTBFS: unknown options to dh_ocaml
Jan Wagner a écrit : > Thats totally fine and I don't belive anybody is making a backport of ocaml > just for fun. In my case it was a build-dep, needed by another package. Backporting ocaml isn't an easy task, since you'll have to have all OCaml libraries recompiled. Besides, the workflow used in Lenny doesn't help to spot easily what needs to be recompiled. This should be fixed with the approach now used in Squeeze. We often use versioned dependencies to ocaml to ease OCaml transitions even though the package being compiled would also work with the previous version of OCaml. This should be explicit in the Debian changelog. Did you try to remove the versioned dependency? Best regards, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#547511: python-scientific: rename task_manager and fix missing dependency
On Sun, Jan 31, 2010 at 04:18:40PM -0500, Richard Darst wrote: I also renamed task_manager to task_manager_pyscientific to close 547511. This is only referenced as an example, but seems generic enough to keep in an executable directory. Sounds reasonable. Thanks! - Jonas Co-maintainer of sympa -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#562575: Bug still present [Re: Bug#562575: installation-reports: Buisnesscard PowerPC installer loops with Segmentation faults]
Hello, On Mon, Feb 1, 2010 at 1:53 AM, Rick Thomas wrote: > > On Jan 31, 2010, at 6:45 PM, Otavio Salvador wrote: > >> Hello, >> >> On Sun, Jan 31, 2010 at 9:41 PM, Norberto Feliberty >> wrote: >>> >>> That's great to hear Hopefully this will get things rolling again since I >>> see that the latest daily squeeze build has stopped on Jan 11. >> >> This is also fixed now. > > Wonderful! > > Please let us know when it appears in an ISO we can test! > > Rick > > PS: If you can describe it in terms I can understand, for future reference, > what was the bug? In fact it was not a bug; probably it was affected by a compiler or a library issue that was solved, in my tests, just recompiling the cdebconf package. Let's see if it will really fix it. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562437: marked as done (jakarta-ecs: FTBFS: java errors)
Your message dated Mon, 01 Feb 2010 11:46:25 +
with message-id
and subject line Bug#562437: fixed in jakarta-ecs 1.4.2-1.2
has caused the Debian Bug report #562437,
regarding jakarta-ecs: FTBFS: java errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
562437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jakarta-ecs
Version: 1.4.2-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091223 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[1]: Entering directory
> `/build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory
> `/build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2'
> cd . && /usr/lib/jvm/default-java/bin/java -classpath
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/lib/jvm/default-java/lib/tools.jar
> -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true
> -Dcompile.optimize=true -buildfile build/build-ecs.xml jar
> Buildfile: build/build-ecs.xml
>
> env:
> [echo] build.compiler = classic
> [echo] java.home = /usr/lib/jvm/java-6-openjdk/jre
> [echo] user.home = /home/user
> [echo] java.class.path =
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/lib/jvm/default-java/lib/tools.jar
> [echo]
>
> prepare:
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/classes
> [mkdir] Created dir:
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src
> [copy] Copying 387 files to
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org
>
> compile:
> [javac] Compiling 381 source files to
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/classes
> [javac] This version of java does not support the classic compiler;
> upgrading to modern
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:62:
> package org.apache.regexp does not exist
> [javac] import org.apache.regexp.RE;
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:63:
> package org.apache.regexp does not exist
> [javac] import org.apache.regexp.RESyntaxException;
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:124:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = (RE)enumerate.nextElement();
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:124:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = (RE)enumerate.nextElement();
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:142:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac] ^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:142:
> cannot find symbol
> [javac] symbol : class RE
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] RE r = new RE(expression);
> [javac]^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter/RegexpFilter.java:145:
> cannot find symbol
> [javac] symbol : class RESyntaxException
> [javac] location: class org.apache.ecs.filter.RegexpFilter
> [javac] catch (RESyntaxException e) {
> [javac]^
> [javac]
> /build/user-jakarta-ecs_1.4.2-1.1-amd64-gIFq1R/jakarta-ecs-1.4.2/bin/src/org/apache/ecs/filter
Bug#567775: marked as done (gst-plugins-bad0.10: Unsatisfiable build-depends on libsvga1-dev [!i386 !amd64])
Your message dated Mon, 01 Feb 2010 11:45:12 + with message-id and subject line Bug#567775: fixed in gst-plugins-bad0.10 0.10.17-4 has caused the Debian Bug report #567775, regarding gst-plugins-bad0.10: Unsatisfiable build-depends on libsvga1-dev [!i386 !amd64] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 567775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gst-plugins-bad0.10 Version: 0.10.17-3 Severity: serious libsvga1-dev only exists on i386 and amd64, which makes this package unbuildable on all other architecture. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.0-1-amd64 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: gst-plugins-bad0.10 Source-Version: 0.10.17-4 We believe that the bug you reported is fixed in the latest version of gst-plugins-bad0.10, which is due to be installed in the Debian FTP archive: gst-plugins-bad0.10_0.10.17-4.diff.gz to main/g/gst-plugins-bad0.10/gst-plugins-bad0.10_0.10.17-4.diff.gz gst-plugins-bad0.10_0.10.17-4.dsc to main/g/gst-plugins-bad0.10/gst-plugins-bad0.10_0.10.17-4.dsc gstreamer0.10-plugins-bad-dbg_0.10.17-4_amd64.deb to main/g/gst-plugins-bad0.10/gstreamer0.10-plugins-bad-dbg_0.10.17-4_amd64.deb gstreamer0.10-plugins-bad-doc_0.10.17-4_all.deb to main/g/gst-plugins-bad0.10/gstreamer0.10-plugins-bad-doc_0.10.17-4_all.deb gstreamer0.10-plugins-bad_0.10.17-4_amd64.deb to main/g/gst-plugins-bad0.10/gstreamer0.10-plugins-bad_0.10.17-4_amd64.deb gstreamer0.10-sdl_0.10.17-4_amd64.deb to main/g/gst-plugins-bad0.10/gstreamer0.10-sdl_0.10.17-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 567...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated gst-plugins-bad0.10 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Feb 2010 05:35:12 +0100 Source: gst-plugins-bad0.10 Binary: gstreamer0.10-plugins-bad-doc gstreamer0.10-plugins-bad gstreamer0.10-sdl gstreamer0.10-plugins-bad-dbg Architecture: source all amd64 Version: 0.10.17-4 Distribution: unstable Urgency: low Maintainer: Maintainers of GStreamer packages Changed-By: Sebastian Dröge Description: gstreamer0.10-plugins-bad - GStreamer plugins from the "bad" set gstreamer0.10-plugins-bad-dbg - GStreamer plugins from the "bad" set (debug symbols) gstreamer0.10-plugins-bad-doc - GStreamer documentation for plugins from the "bad" set gstreamer0.10-sdl - GStreamer plugin for SDL output Closes: 567775 Changes: gst-plugins-bad0.10 (0.10.17-4) unstable; urgency=low . * debian/build-deps.in: + And remove the unnecessary build dependencies for SDL again as bug #565579 is fixed now (Closes: #567775). Checksums-Sha1: 10ebdec18fae007e8d6ede65f566c6fba33e4ee6 2803 gst-plugins-bad0.10_0.10.17-4.dsc 787d9331a0479b72a79b7a1096286ab8197e4b66 17590 gst-plugins-bad0.10_0.10.17-4.diff.gz 3f2061c26933ba2f36b678755f606d22d87c41ea 179444 gstreamer0.10-plugins-bad-doc_0.10.17-4_all.deb 7837c3157f2bb849da6a2f914fd484617c29d0a3 1557740 gstreamer0.10-plugins-bad_0.10.17-4_amd64.deb 9126dff76fc65e8b8832f5ab3e580af9a6c516da 47858 gstreamer0.10-sdl_0.10.17-4_amd64.deb 8af669040f5a215df7f413cc713377e0df1da5ed 3706102 gstreamer0.10-plugins-bad-dbg_0.10.17-4_amd64.deb Checksums-Sha256: f4fdb1c9461e3b3e6993bf235787789f1afed40db3a2e64e6ea450652c066d35 2803 gst-plugins-bad0.10_0.10.17-4.dsc 77cda0d281460f95f9872a4a9223bbed58bed0efb8c5d642b1d4e5cbab1f9023 17590 gst-plugins-bad0.10_0.10.17-4.diff.gz 572cb0b765374826ec763b9ebccde70a0cd18b13bbdf48201212fc15bbcd9648 179444 gstreamer0.10-plugins-bad-doc_0.10.17-4_all.deb a7788a15ffeb64c8c59f1962cbcdaf4c9224db1335e1a290e94af2bd40c1ca33 1557740 gstreamer0.10-plugins-bad_0.10.17-4_amd64.deb 3f41a6e3c5584980fccbf873431c612435470ab59a1b37eb18dc71a097dad439 47858 gstreamer0.10-sdl_0.10.17-4_amd64.deb 5913b9950a353328940f24c8e0da442f63d73f437264f1825d75b472f418f1
Bug#567937: insserv blocks packages upgrade, permission denied
[Artur ??uva??ov] > Upgrade of many packages failes because of these errors: > > insserv: fopen(K01exim4): Permission denied > update-rc.d: error: insserv rejected the script header Why isn't K01exim4 readable? Please provide a verbatim copy of the error messages you see when the upgrade fail? What did you upgrade from and to? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566971: patch
Adding /usr/lib/ssl as libdir seems to fix the issue. --- engine-pkcs11-0.1.8/debian/rules 2010-01-10 09:46:27.0 +0100 +++ engine-pkcs11-0.1.8.new/debian/rules 2010-02-01 13:00:14.711062380 +0100 @@ -6,7 +6,8 @@ override_dh_auto_configure: dh_auto_configure -- \ --htmldir=/usr/share/doc/libengine-pkcs11-openssl/html \ - --enable-doc + --enable-doc \ + --libdir=/usr/lib/ssl override_dh_installchangelogs: dh_installchangelogs doc/nonpersistent/ChangeLog
Bug#567945: lsh-server: Does not configure on mipsel
Package: lsh-server Version: 2.0.4-dfsg-6+b1 Severity: grave Justification: fails to configure Greetings, lsh-server fails to configure on mipsel, as can be seen in the buildd log for scalapack: Setting up lsh-server (2.0.4-dfsg-6+b1) ... Creating lsh random seed file (this may take a while) ... done. Creating lsh host key ... .. done. Starting secure shell v2 server: lshdClosed spurious fd 3 failed! invoke-rc.d: initscript lsh-server, action "start" failed. dpkg: error processing lsh-server (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lam-runtime: lam-runtime depends on ssh-server | rsh-server; however: Package ssh-server is not installed. Package lsh-server which provides ssh-server is not configured yet. Package rsh-server is not installed. This prevents the building of any package depending on ssh-server, including all MPI-related scientific packages. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Bug#567881: Acknowledgement (ufraw: Postint fails due to invalid schema file)
Problem went away after running aptitude safe-upgrade, sorry for the noise. On Mon, Feb 1, 2010 at 00:09, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Hubert Chathi > > If you wish to submit further information on this problem, please > send it to 567...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 567881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567881 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#567881: closing 567881
close 567881 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567882: Acknowledgement (gnucash: Postinst broken due to invalid schema file)
Problem went away after running aptitude safe-upgrade. On Mon, Feb 1, 2010 at 00:09, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > t...@debian.org (Thomas Bushnell, BSG) > > If you wish to submit further information on this problem, please > send it to 567...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 567882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567882 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Processed: closing 567882
Processing commands for cont...@bugs.debian.org: > close 567882 Bug#567882: gnucash: Postinst broken due to invalid schema file 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Javier Kohen > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551250: marked as done (libmatio: FTBFS: mv: cannot stat `latex/refman.pdf': No such file or directory)
Your message dated Mon, 01 Feb 2010 12:19:20 + with message-id and subject line Bug#551250: fixed in libmatio 1.3.3-6 has caused the Debian Bug report #551250, regarding libmatio: FTBFS: mv: cannot stat `latex/refman.pdf': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 551250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmatio Version: 1.3.3-5 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091016 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[1]: Entering directory > `/build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/doxygen' > (cat ./doxygen.config; echo "INPUT=../src";echo "LATEX_HEADER=./header.tex"; > echo "EXCLUDE=../scats"; echo "IMAGE_PATH=."; echo "PROJECT_NUMBER=1.3.3") | > doxygen - > Warning: Tag `USE_WINDOWS_ENCODING' at line 64 of file - has become obsolete. > To avoid this warning please update your configuration file using "doxygen -u" > Warning: Tag `DETAILS_AT_TOP' at line 155 of file - has become obsolete. > To avoid this warning please update your configuration file using "doxygen -u" > Warning: Tag `MAX_DOT_GRAPH_WIDTH' at line 1122 of file - has become obsolete. > To avoid this warning please update your configuration file using "doxygen -u" > Warning: Tag `MAX_DOT_GRAPH_HEIGHT' at line 1130 of file - has become > obsolete. > To avoid this warning please update your configuration file using "doxygen -u" > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:57: > Conditional section does not have a corresponding \endcond command within > this file. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/matio.h:163: > Warning: documentation for unknown define MEM_CONSERVE found. > > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/fortran/matio_internal.c:67: > Warning: Compound fmatvar_t is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/fortran/matio_internal.c:62: > Warning: Compound fmat_t is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/endian.c:217: > Warning: Member SIZEOF_DOUBLE (define) of file endian.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:54: > Warning: Member asprintf (define) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:43: > Warning: Member snprintf (define) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:32: > Warning: Member va_copy(d, s) (define) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:51: > Warning: Member vasprintf (define) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:35: > Warning: Member vsnprintf (define) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:47: > Warning: Member snprintf(char *str, size_t size, const char *format,...) > (function) of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/io.c:39: > Warning: Member vsnprintf(char *, size_t, const char *, va_list) (function) > of file io.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat.c:748: > Warning: Member Mat_VarFree2(matvar_t *matvar) (function) of file mat.c is > not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat4.c:382: > Warning: Member Mat_VarPrint4(matvar_t *matvar, int printdata) (function) of > file mat4.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat4.c:271: > Warning: Member Mat_VarReadNextInfo4(mat_t *mat) (function) of file mat4.c is > not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat4.c:52: > Warning: Member Read4(mat_t *mat, matvar_t *matvar) (function) of file mat4.c > is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat4.c:203: > Warning: Member ReadData4(mat_t *mat, matvar_t *matvar, void *data, int > *start, int *stride, int *edge) (function) of file mat4.c is not documented. > /build/user-libmatio_1.3.3-5-amd64-GEGi6I/libmatio-1.3.3/src/mat5.c:586: > Warning: Member WriteEmptyData(mat_t *mat, int N, int data_type) (function) > of file mat5.c is not documented. > /build/user-li
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 567345 567720 Bug#567345: python-gnome2: Depends: python2.6-gtk2 but it is not installable Bug#567720: Require: python2.6-gtk2 but it is not installable Forcibly Merged 567345 567720. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567882: closing 567882
close 567882 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567882: gnucash: Postinst broken due to invalid schema file
Hi Micha, I ran aptitude safe-upgrade and the problem went away. Sorry for
the noise.
2010/2/1 Micha Lenk
> Hi Javier,
>
> I cannot reproduce your problem here, even with your locales (to exclude
> locale specific errors):
>
> (sid)ian:~# locale
> LANG=es_AR.UTF-8
> LC_CTYPE="es_AR.UTF-8"
> LC_NUMERIC="es_AR.UTF-8"
> LC_TIME="es_AR.UTF-8"
> LC_COLLATE="es_AR.UTF-8"
> LC_MONETARY="es_AR.UTF-8"
> LC_MESSAGES="es_AR.UTF-8"
> LC_PAPER="es_AR.UTF-8"
> LC_NAME="es_AR.UTF-8"
> LC_ADDRESS="es_AR.UTF-8"
> LC_TELEPHONE="es_AR.UTF-8"
> LC_MEASUREMENT="es_AR.UTF-8"
> LC_IDENTIFICATION="es_AR.UTF-8"
> LC_ALL=
> (sid)ian:~# aptitude --without-recommends install gnucash
> Leyendo lista de paquetes... Hecho
> Creando árbol de dependencias
> Leyendo la información de estado... Hecho
> Leyendo la información de estado extendido... Hecho
> Inicializando el estado de los paquetes... Hecho
> Se instalarán los siguiente paquetes NUEVOS:
> gnucash gnucash-common{a} libdate-manip-perl{a}
> Se RECOMIENDAN los siguientes paquetes, pero NO se instalarán:
> gnucash-docs
> 0 paquetes actualizados, 3 nuevos instalados, 0 para eliminar y 37 sin
> actualizar.
> Necesito descargar 0B/9.133kB de ficheros. Después de desempaquetar se
> usarán 42,8MB.
> ¿Quiere continuar? [Y/n/?]
> Escribiendo información de estado extendido... Hecho
> No se pudo escbribir en el registro, falló la llamada a «openpty()»
> (¿está montado /dev/pts?)
> Seleccionando el paquete gnucash-common previamente no seleccionado.
> (Leyendo la base de datos ... 00%
> 101487 ficheros y directorios instalados actualmente.)
> Desempaquetando gnucash-common (de .../gnucash-common_2.2.9-3_all.deb) ...
> Seleccionando el paquete libdate-manip-perl previamente no seleccionado.
> Desempaquetando libdate-manip-perl (de
> .../libdate-manip-perl_6.05-1_all.deb) ...
> Seleccionando el paquete gnucash previamente no seleccionado.
> Desempaquetando gnucash (de .../gnucash_2.2.9-3_i386.deb) ...
> Procesando disparadores para man-db ...
> Procesando disparadores para install-info ...
> Procesando disparadores para hicolor-icon-theme ...
> Procesando disparadores para menu ...
> No se pudo escbribir en el registro, falló la llamada a «openpty()»
> (¿está montado /dev/pts?)
> Configurando gnucash-common (2.2.9-3) ...
> Configurando libdate-manip-perl (6.05-1) ...
> Configurando gnucash (2.2.9-3) ...
> Procesando disparadores para menu ...
> Leyendo lista de paquetes... Hecho
> Creando árbol de dependencias
> Leyendo la información de estado... Hecho
> Leyendo la información de estado extendido... Hecho
> Inicializando el estado de los paquetes... Hecho
> Escribiendo información de estado extendido... Hecho
>
> (sid)ian:~#
>
> Do you have enough space on all of your hard disk partitions?
>
> Regards
> Micha
>
Processed: closing 567881
Processing commands for cont...@bugs.debian.org: > close 567881 Bug#567881: ufraw: Postint fails due to invalid schema file 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Javier Kohen > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: (no subject)
It is readable 0 lrwxrwxrwx 1 root root15 Aug 4 11:13 K01exim4 -> ../init.d/exim4 8 -rwxr-xr-x 1 root root 6604 Feb 1 12:21 exim4 This is a full output: Preparing to replace menu-xdg 0.4 (using .../archives/menu-xdg_0.5_all.deb) ... Unpacking replacement menu-xdg ... rm: cannot remove `/var/lib/menu-xdg/applications': Permission denied rm: cannot remove `/var/lib/menu-xdg/menus': Permission denied rm: cannot remove `/var/lib/menu-xdg/desktop-directories': Permission denied dpkg: warning: old post-removal script returned error exit status 1 dpkg - trying script from the new package instead ... rm: cannot remove `/var/lib/menu-xdg/applications': Permission denied rm: cannot remove `/var/lib/menu-xdg/menus': Permission denied rm: cannot remove `/var/lib/menu-xdg/desktop-directories': Permission denied dpkg: error processing /var/cache/apt/archives/menu-xdg_0.5_all.deb (--unpack): subprocess new post-removal script returned error exit status 1 rm: cannot remove `/var/lib/menu-xdg/applications': Permission denied rm: cannot remove `/var/lib/menu-xdg/menus': Permission denied rm: cannot remove `/var/lib/menu-xdg/desktop-directories': Permission denied dpkg: error while cleaning up: subprocess new post-removal script returned error exit status 1 Preparing to replace libcups2-dev 1.4.2-4 (using .../libcups2-dev_1.4.2-7_amd64.deb) ... rm: cannot remove `/usr/share/doc/libcups2-dev/examples': Permission denied dpkg: error processing /var/cache/apt/archives/libcups2-dev_1.4.2-7_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Processing triggers for menu ... Errors were encountered while processing: /var/cache/apt/archives/menu-xdg_0.5_all.deb /var/cache/apt/archives/libcups2-dev_1.4.2-7_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover:
Processed: Bug #567882 is not reproducible
Processing commands for cont...@bugs.debian.org:
> tags 567882 + unreproducible
Bug #567882 {Done: Javier Kohen } [gnucash]
gnucash: Postinst broken due to invalid schema file
Added tag(s) unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567882: gnucash: Postinst broken due to invalid schema file
Hi Javier, I wrote: So, do you agree to close the bug as not reproducible? Ooops, it's already closed. Thanks for your feedback. Regards Micha -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567882: Bug #567882 is not reproducible
tags 567882 + unreproducible thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562067: marked as done (libxtrap: should be removed)
Your message dated Mon, 1 Feb 2010 13:36:59 +0100 with message-id <8b2d7b4d1002010436l6d6f8fc9h7ff71d3302c43...@mail.gmail.com> and subject line Package removed from Debian unstable has caused the Debian Bug report #562067, regarding libxtrap: should be removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 562067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxtrap Severity: serious Justification: maintainer says so Tags: sid squeeze We should remove this package some time before squeeze. I'll mark this as blocked by the bugs filed on its reverse dependencies. Cheers, Julien --- End Message --- --- Begin Message --- Version: 2:1.0.0-5+rm Package removed from Debian unstable: http://bugs.debian.org/566979 -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi --- End Message ---
Bug#567947: libempathy30: Unistallable, depends on libnm-glib0 which is not available.
Package: libempathy30 Version: 2.28.2-2 Severity: grave Justification: renders package unusable Hi, libempathy30 2.28.2-2 depends on libnm-glib0 which is not available in sid. This makes empathy itself unistallable. Regards, Antonio Ospite http://ao2.it -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: (no subject)
Moreover, I had some problems with upgrading util-linux recently. I was able to complete the process only after commenting update-rc.d lines from the postinst code. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567619: xserver-xorg: After upgrading squeeze xserver stops responding
I could confirm it here too. For me, it freeze whole system (can't even ping it) and also after some prolonged idle period (maybe some problem with dpms?). But not everytime DPMS suspend my pc it occure, so I can't reproduce it on will. (amd64, kernel 2.6.32-trunk) -Ph -- Premysl "Anydot" Hruby, https://www.redrum.cz/ - I'm a signature virus. Please add me to your signature and help me spread! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: retitle 562606 to should build-depend on debhelper (>= 7.1.0~), severity of 562606 is important
Processing commands for cont...@bugs.debian.org: > retitle 562606 should build-depend on debhelper (>= 7.1.0~) Bug #562606 [ocaml] FTBFS: unknown options to dh_ocaml Changed Bug title to 'should build-depend on debhelper (>= 7.1.0~)' from 'FTBFS: unknown options to dh_ocaml' > severity 562606 important Bug #562606 [ocaml] should build-depend on debhelper (>= 7.1.0~) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566931: marked as done (src:vidalia: FTBFS on GNU/kFreeBSD: ZlibByteArray.cpp:59:24: error: #elif with no expression)
Your message dated Mon, 01 Feb 2010 13:02:48 +
with message-id
and subject line Bug#566931: fixed in vidalia 0.2.7-1
has caused the Debian Bug report #566931,
regarding src:vidalia: FTBFS on GNU/kFreeBSD: ZlibByteArray.cpp:59:24: error:
#elif with no expression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
566931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vidalia
Version: 0.2.4-2
Severity: serious
Tags: patch
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS on GNU/kFreeBSD because of a faulty #elif statement:
| [ 7%] Building CXX object src/common/CMakeFiles/common.dir/ZlibByteArray.o
|
/build/buildd-vidalia_0.2.4-2-kfreebsd-amd64-XFX9mP/vidalia-0.2.4/src/common/ZlibByteArray.cpp:59:24:
error: #elif with no expression
| make[3]: *** [src/common/CMakeFiles/common.dir/ZlibByteArray.o] Error 1
Full build logs:
https://buildd.debian.org/status/package.php?suite=experimental&p=vidalia
Please find attached a patch to fix this. Thanks for considering.
Mraw,
KiBi.
--- a/src/common/ZlibByteArray.cpp
+++ b/src/common/ZlibByteArray.cpp
@@ -56,7 +56,7 @@
#ifdef HAVE_LIMITS_H
#include
-#elif HAVE_SYS_LIMITS_H
+#elif defined HAVE_SYS_LIMITS_H
#include
#endif
--- End Message ---
--- Begin Message ---
Source: vidalia
Source-Version: 0.2.7-1
We believe that the bug you reported is fixed in the latest version of
vidalia, which is due to be installed in the Debian FTP archive:
vidalia_0.2.7-1.diff.gz
to main/v/vidalia/vidalia_0.2.7-1.diff.gz
vidalia_0.2.7-1.dsc
to main/v/vidalia/vidalia_0.2.7-1.dsc
vidalia_0.2.7-1_amd64.deb
to main/v/vidalia/vidalia_0.2.7-1_amd64.deb
vidalia_0.2.7.orig.tar.gz
to main/v/vidalia/vidalia_0.2.7.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 566...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ulises Vitulli (supplier of updated vidalia package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 31 Jan 2010 17:11:20 -0300
Source: vidalia
Binary: vidalia
Architecture: source amd64
Version: 0.2.7-1
Distribution: unstable
Urgency: low
Maintainer: Vern Sun
Changed-By: Ulises Vitulli
Description:
vidalia- controller GUI for the Tor software
Closes: 566931
Changes:
vidalia (0.2.7-1) unstable; urgency=low
.
* New upstream release (Closes: #566931).
- Droping pkg from experimental, now going to unstable.
- Drop 0.1.x stable branch in favor of 0.2.x, due to devel matureness.
- Removing kFreeBSD-gcc4.4-fix.patch. Patch accepted and applied on
upstream side before this package to be uploaded (check #566931).
- Added upstream uploader into the about-to-dissappear repacking
source target gpg keyring ('source-repkg').
* The 'All systems are go!' upload.
Checksums-Sha1:
0b7fbc06dfbe8f52642c02981c2cbcdede0347db 1430 vidalia_0.2.7-1.dsc
a4fa7dac6ffc116582c6d84e0b0dda05caf6c7f8 2695858 vidalia_0.2.7.orig.tar.gz
f54ac273f3055ae6c95fb835f9dfd0917a2c79d8 43373 vidalia_0.2.7-1.diff.gz
e885ee5250e7506b3db14ebe5a9c319b88c91edf 2506172 vidalia_0.2.7-1_amd64.deb
Checksums-Sha256:
d2ed63f61ae8f5c121bd98a67258e712e4ca20e7d18e3d67b9a5c86f35c8534d 1430
vidalia_0.2.7-1.dsc
33122ef47b83926b5f2f6f5446173f2e12a09b424df3870fd6aa73a6c2307c02 2695858
vidalia_0.2.7.orig.tar.gz
b8a4dd6f706656c446404744ce5a56d1dc431768b894c26c8528e33b2fabad3c 43373
vidalia_0.2.7-1.diff.gz
6fbec96120b960279b8075de294e723c307abd2f0b6e0dd2c70f008386db18a4 2506172
vidalia_0.2.7-1_amd64.deb
Files:
496d8befe228cbc389998dcee93924c1 1430 net extra vidalia_0.2.7-1.dsc
5f4a40775016ed5af8d38ab402139e18 2695858 net extra vidalia_0.2.7.orig.tar.gz
a16dd36b112287bc6f11c6c1587710bb 43373 net extra vidalia_0.2.7-1.diff.gz
b74cec46faecbe491901985235f71ee7 2506172 net extra vidalia_0.2.7-1_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJLZs2fAAoJEEFvBhBj/uZZlecH/j2UhNGLPKRAjtNMce8jzyIb
Xn3CsuhHrEZeSpJ+VrwNEnRYwkzFbg0jONOzgRQT+VJ2689vmrVFwcLu8iyksO2b
FOoP0vXGpN8DvT4L6jo8NzZKJKeOAbQfeikiihzDervD4pSkyRFhFt6RiQ/zEbCq
ACoQ04m/4dN6o5sFYyHW8lx6BjG6Me
Processed: severity of 563941 is important
Processing commands for cont...@bugs.debian.org: > severity 563941 important Bug #563941 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: unexpected system hangups Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: your mail
[Artur ??uva??ov] > It is readable > 0 lrwxrwxrwx 1 root root15 Aug 4 11:13 K01exim4 -> ../init.d/exim4 > 8 -rwxr-xr-x 1 root root 6604 Feb 1 12:21 exim4 Is your file system mounted read-only because of file system corruption detected by the kernel? It would explain all the errors about permission denied for files that should be writable by the root user. This seem to be a kernel problem and not a user application problem. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#563941: Additional information
On Wed, 06 Jan 2010, irb250 irb250 wrote: > Jan 5 22:49:01 localhost kernel: [17744.647218] [ cut here > ] > Jan 5 22:49:01 localhost kernel: [17744.647230] WARNING: at lib/kref.c:43 > kref_get+0x17/0x1c() > Jan 5 22:49:01 localhost kernel: [17744.647233] Modules linked in: nls_utf8 > nls_cp437 vfat fat nls_base sd_mod usb_storage usbhid hid ff_memless > xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ip_tables x_tables pppoe pppox > ppp_generic slhc radeon drm ppdev lp acpi_cpufreq speedstep_lib > cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_ondemand > freq_table cpufreq_powersave ipv6 fuse loop joydev pcmcia firmware_class > parport_pc parport serio_raw psmouse video output bay pcspkr battery > snd_ali5451 snd_ac97_codec ac97_bus container snd_pcm snd_timer snd > snd_page_alloc yenta_socket rsrc_nonstatic pcmcia_core ac trident i2c_ali1535 > i2c_ali15x3 gameport button soundcore ac97_codec i2c_core shpchp pci_hotplug > ali_agp agpgart evdev ext3 jbd mbcache ide_cd_mod cdrom ide_disk ata_generic > libata scsi_mod ide_pci_generic floppy alim15x3 ide_core 8139cp 8139too mii > dock ohci_hcd usbcore thermal processor fan thermal_sys [last unloaded: > scsi_wait_scan] > Jan 5 22:49:01 localhost kernel: [17744.647341] Pid: 3377, comm: Xorg > Tainted: GW 2.6.26-2-686 #1 can you reproduce with 2.6.26-21 that got pushed that weekend? it has several fixes. also we can't help with tainted kernel. is it reproducible without? thanks for the report -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: your mail
Mount output: /dev/sda5 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sda1 on /boot type ext3 (rw) /dev/sda6 on /home type ext3 (rw) /dev/sda8 on /usr type ext3 (rw) /dev/sda9 on /var type ext3 (rw) //MASTER1/NEWSPAPER on /mnt/newspaper type cifs (rw,mand) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/sdb1 on /mnt/backup type xfs (rw) none on /proc/fs/vmblock/mountPoint type vmblock (rw) I am able to make changes to those files either. > [Artur ??uva??ov] > > It is readable > > 0 lrwxrwxrwx 1 root root15 Aug 4 11:13 K01exim4 -> ../init.d/exim4 > > 8 -rwxr-xr-x 1 root root 6604 Feb 1 12:21 exim4 > > Is your file system mounted read-only because of file system > corruption detected by the kernel? It would explain all the errors > about permission denied for files that should be writable by the root > user. > > This seem to be a kernel problem and not a user application problem. > > Happy hacking, > -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567687: marked as done (FTBFS: error: 'bft_file_t' has no member named 'sh')
Your message dated Mon, 01 Feb 2010 13:32:11 + with message-id and subject line Bug#567687: fixed in libbft 1.1.2-3 has caused the Debian Bug report #567687, regarding FTBFS: error: 'bft_file_t' has no member named 'sh' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 567687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbft Version: 1.1.2-2 Severity: serious Justification: FTBFS User: debian-...@lists.debian.org Usertags: kfreebsd Hi, it looks like your package is going to need some porting for kfreebsd-amd64: | libtool: compile: cc -DHAVE_CONFIG_H -I. -I.. -DNDEBUG -g -O2 -g -Wall -O2 -c bft_file.c -fPIC -DPIC -o .libs/bft_file.o | bft_file.c: In function 'bft_file_seek': | bft_file.c:1110: error: 'bft_file_t' has no member named 'sh' | make[3]: *** [bft_file.lo] Error 1 Build logs: https://buildd.debian.org/status/package.php?suite=experimental&p=libbft Mraw, KiBi. --- End Message --- --- Begin Message --- Source: libbft Source-Version: 1.1.2-3 We believe that the bug you reported is fixed in the latest version of libbft, which is due to be installed in the Debian FTP archive: libbft-dev_1.1.2-3_i386.deb to main/libb/libbft/libbft-dev_1.1.2-3_i386.deb libbft1-dbg_1.1.2-3_i386.deb to main/libb/libbft/libbft1-dbg_1.1.2-3_i386.deb libbft1_1.1.2-3_i386.deb to main/libb/libbft/libbft1_1.1.2-3_i386.deb libbft_1.1.2-3.diff.gz to main/libb/libbft/libbft_1.1.2-3.diff.gz libbft_1.1.2-3.dsc to main/libb/libbft/libbft_1.1.2-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 567...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated libbft package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Feb 2010 14:19:28 +0100 Source: libbft Binary: libbft-dev libbft1 libbft1-dbg Architecture: source i386 Version: 1.1.2-3 Distribution: experimental Urgency: low Maintainer: Debian Science Team Changed-By: Sylvestre Ledru Description: libbft-dev - Code_Saturne Base Functions and Types library libbft1- Code_Saturne Base Functions and Types library libbft1-dbg - Code_Saturne Base Functions and Types library Closes: 567687 Changes: libbft (1.1.2-3) experimental; urgency=low . * Fix a FTBFS - bft_file.diff (Closes: #567687) * Standards-Version updated to version 3.8.4 Checksums-Sha1: a9e86e55788eda4e4b5e7875a5e3721733fa77d2 1250 libbft_1.1.2-3.dsc 879e697ce70ec822bf1d0deeb92ec25a5c2600e7 3026 libbft_1.1.2-3.diff.gz 2c05a59bb823f343480bac229ec7ddc9821d642c 32958 libbft-dev_1.1.2-3_i386.deb 344474b26e08b02a770df1d507f7ab2b091246e2 19088 libbft1_1.1.2-3_i386.deb cde73c482ec6a1d34f3a30a6db6cf9c868db8f97 27704 libbft1-dbg_1.1.2-3_i386.deb Checksums-Sha256: 33abc2cca6d019f9a1607eb0d41bc26b8c6ad8aa22631986a53581d976253301 1250 libbft_1.1.2-3.dsc 1aba493338172c22b23bf2bdfd251c6a2f04991fdb0a6fe1e77a9f53080f20e9 3026 libbft_1.1.2-3.diff.gz 45aa2adc998c77c751ce5aca45b8260bda5918a26017bef151005ee12d2f44cc 32958 libbft-dev_1.1.2-3_i386.deb 0159329d360bed2a57337b36b8768563a18f25893f72e427ff6e62f612a5c71d 19088 libbft1_1.1.2-3_i386.deb f54e0485962bdeec8debd0894ca16af8c1daefd9904391446dbc59e554493741 27704 libbft1-dbg_1.1.2-3_i386.deb Files: 31a8a5bfe156a367a9e7de1b3395da0b 1250 libs optional libbft_1.1.2-3.dsc ecf64deec8f17f1180d91f8b49415e81 3026 libs optional libbft_1.1.2-3.diff.gz 556b12efb1269465660b648cc85bee50 32958 libdevel optional libbft-dev_1.1.2-3_i386.deb f5d61939795f0708619b411d584597fa 19088 libs optional libbft1_1.1.2-3_i386.deb a58180db5269384c46b8e8182b77926f 27704 debug extra libbft1-dbg_1.1.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAktm1ZAACgkQiOXXM92JlhDgUwCffrge6hZhEyZNYt/mDSb0s4Gq //YAoNFO2/k7qnGpwWSSnnwOWx6oz88R =1A0I -END PGP SIGNATURE- --- End Message ---
Bug#567473: Workaround
Hi, this seems to be caused by knetworkmanager's liberal interpretation of the term 'uuid'. I stopped knetworkmanager, went to my ~/.kde/share/config/knetworkmanagerrc and replaced lines of the form [ConnectionSetting_1NCFiIxMwpU6DxST_connection] ... Value_uuid=1NCFiIxMwpU6DxST\n ... with valid UUIDs (produced by uuidgen or cat //proc/sys/kernel/random/uuid) like Value_uuid=7166eb59-84e9-4d72-a734-83a138e394d4\n and I can use the entries where I've made the substituion again. ciao, -- [*Thomas Themel*] Es scheint da eine starke Korrelation zwischen technischer [extended contact] Ahnungslosigkeit, offenherzigem Gemüt und der Installation [info provided in] von Gentoo zu geben. Linux für Kleinkinder so zu sagen. [*message header*] - Alexander Bartolich in at.linux -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 548303 in 1.4.12-5
Processing commands for cont...@bugs.debian.org:
> found 548303 1.4.12-5
Bug #548303 {Done: Jan Wagner } [nagios-plugins]
missrepresented license information
Bug Marked as found in versions nagios-plugins/1.4.12-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 548303
Processing commands for cont...@bugs.debian.org:
> tags 548303 + lenny-ignore
Bug #548303 {Done: Jan Wagner } [nagios-plugins]
missrepresented license information
Added tag(s) lenny-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562388: soprano: FTBFS: cp: cannot stat `debian/tmp/usr/lib/soprano/libsoprano_raptorserializer.so': No such file or directory
On Thu, Dec 24, 2009 at 11:35:38AM +0100, Lucas Nussbaum wrote: > Source: soprano > Version: 2.3.1+dfsg.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20091213 qa-ftbfs > Justification: FTBFS on amd64 > ... Fixed in SVN, it will be fixed in next release of soprano for KDE 4.4. Ana -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567958: wicd-daemon fails to start
Package: wicd-daemon Version: 1.7.0-2 Severity: grave Justification: renders package unusable Hi, Since the last update wicd refuses to start : $ sudo /etc/init.d/wicd start Starting Network connection manager: wicd failed When I try to start wicd manually it seems some python packages are missing : $ wicd Traceback (most recent call last): File "/usr/share/wicd/daemon/wicd-daemon.py", line 61, in from wicd.logfile import ManagedStdio ImportError: No module named logfile But python-wicd 1.7.0-2 is installed on my system. I have the same error on a non 64 architecture following the last update of the package. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (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/dash Versions of packages wicd-daemon depends on: ii adduser 3.112add and remove users and groups ii dbus1.2.16-2 simple interprocess messaging syst ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii dhcp3-client3.1.3-2 DHCP client ii iproute 20091226-1 networking and traffic control too ii iputils-ping3:20071127-2 Tools to test the reachability of ii lsb-base3.2-23 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ii psmisc 22.10-1 utilities that use the proc file s ii python 2.5.4-9 An interactive high-level object-o ii python-dbus 0.83.0-1+b1 simple interprocess messaging syst ii python-gobject 2.20.0-1+b1 Python bindings for the GObject li ii python-wicd 1.7.0-2 wired and wireless network manager ii wireless-tools 30~pre9-3Tools for manipulating Linux Wirel ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (I Versions of packages wicd-daemon recommends: ii wicd-gtk [wicd-client]1.7.0-2wired and wireless network manager Versions of packages wicd-daemon suggests: ii pm-utils 1.2.6.1-3 utilities and scripts for power ma -- debconf information: * wicd/users: ustilago -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 559921 normal Bug #559921 [aish] aish: should this package be removed? Severity set to 'normal' from 'serious' > reassign 559921 ftp.debian.org Bug #559921 [aish] aish: should this package be removed? Bug reassigned from package 'aish' to 'ftp.debian.org'. Bug No longer marked as found in versions aish/1.13-5. > retitle 559921 RM: aish -- RoM; no longer needed Bug #559921 [ftp.debian.org] aish: should this package be removed? Changed Bug title to 'RM: aish -- RoM; no longer needed' from 'aish: should this package be removed?' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Hi! * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: > I am currently working on getting 1.4.4 ready to go and remove David > Gil from the package per (#551636) Actually, I'm not sure, does this address Moritz' concerns, from a security team's point of view, especially with respect to stable? I don't see any update that would have fixed the security issues for lenny, what is your plan for that? Thanks, Rhonda -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567962: needs to be rebuilt against libhdf5-1.8.4
Package: octave-specfun Version: 1.0.8-3 Severity: serious octave-specfun is currently uninstallable in sid, as it depends on libhdf5-1.8.3, while octave3.2 depends on libhdf5-1.8.4. Please rebuild octave-specfun against libhdf5-1.8.4. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567963: yagiuda: -t and -T can't be specified together as indicated in doc
Package: yagiuda Version: 1.19-6 Severity: grave Justification: renders package unusable tags patch optimise -t and -T options can't be specified together as established in the manual page. Problem seems to be a setting in optimize.c prior to checking command line options. Since this package is currently orphaned, I'll will upload to mentors.debian.net a new package closing this bug. There is no upstream new version of this software. Thanks. Here's a patch that seems to work: diff -r yagiuda-1.19/src/optimise.c yagiuda-1.19_fer/src/optimise.c 45,46d44 < flag.eflg=31;/* set elements to move */ < flag.oflg=32805; /* Set things to optimise for */ 50a49,51 > /* set these _after_ check_flags, FMM 20100131 */ > flag.eflg=31;/* set elements to move */ > flag.oflg=32805; /* Set things to optimise for */ -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yagiuda depends on: ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib yagiuda recommends no packages. yagiuda 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#567962: needs to be rebuilt against libhdf5-1.8.4
Hi! > octave-specfun is currently uninstallable in sid, as it depends on > libhdf5-1.8.3, while octave3.2 depends on libhdf5-1.8.4. > Please rebuild octave-specfun against libhdf5-1.8.4. Actually, on further inspection, it seems that there is no need at all to link against libhdf (and zlib, and libfftw3, and libcurses5, etc). The package itself doesn't use these symbols, so it shouldn't be linked against them. This seems to be an issue for all octave packages, BTW. Bas. -- +--+ | Bas Zoetekouw | Sweet day, so cool, so calm, so bright, | || The bridall of the earth and skie: | | b...@zoetekouw.net | The dew shall weep thy fall tonight;| +|For thou must die. | +-+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567937: your mail
[Artur ??uva??ov] > Mount output: Mount use the info in /etc/mtab, and do not reflect the kernels understanding of the mounted file systems. Is there any related information in the output from dmesg? Do these commands work: touch /etc/init.d/foo~ rm /etc/init.d/foo~ cat /etc/rc*.d/K01exim4 If the problem is with the file system, I recommend a full backup before moving ahead, to have something to recover from if using the system breaks it further. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567364: Copyright and license for Perl module XML::Filter::XSLT
Hi, Matt Sergeant writes: > I can confirm the license. If I ever get to updating the module I'll > add the claim. Thank you very much for your fast response. Regards, Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Gerfried Fuchs wrote: > Hi! > > * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: >> I am currently working on getting 1.4.4 ready to go and remove David >> Gil from the package per (#551636) > > Actually, I'm not sure, does this address Moritz' concerns, from a > security team's point of view, especially with respect to stable? I > don't see any update that would have fixed the security issues for > lenny, what is your plan for that? > > Thanks, > Rhonda 1.4.4 reportedly fixes all current outstanding CVS reports. Short of going and simply upgrading the old versions trying to go through the code and find the specific fixes to these issues, as I've found no patch files specific to the problem, would take much more time than I have available when a fixed upstream version is already available in the repository. 1.4.4-1 hit the unstable repository in late November and I had a few fixes until 1.4.4-3 was migrated to testing just before Christmas. signature.asc Description: OpenPGP digital signature
Processed: libxml-filter-xslt-perl: license is ok, just missing a note in d/copyright
Processing commands for cont...@bugs.debian.org: > severity 567364 important Bug #567364 [src:libxml-filter-xslt-perl] libxml-filter-xslt-perl: Where does copyright information come from? Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Hi! * Jeremy T. Bouse [2010-02-01 16:12:06 CET]: > Gerfried Fuchs wrote: > > * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: > >>I am currently working on getting 1.4.4 ready to go and remove David > >> Gil from the package per (#551636) > > > > Actually, I'm not sure, does this address Moritz' concerns, from a > > security team's point of view, especially with respect to stable? I > > don't see any update that would have fixed the security issues for > > lenny, what is your plan for that? > > 1.4.4 reportedly fixes all current outstanding CVS reports. Short of > going and simply upgrading the old versions trying to go through the > code and find the specific fixes to these issues, as I've found no patch > files specific to the problem, would take much more time than I have > available when a fixed upstream version is already available in the > repository. 1.4.4-1 hit the unstable repository in late November and I > had a few fixes until 1.4.4-3 was migrated to testing just before Christmas. You are aware that maintaining a package doesn't mean only taking care for it in unstable but also to at least try to give the security team a helping hand for trying to get things straight in a stable release? I wonder, how severe are the issues actually? Is it better to pull the package from the stable release (like Moritz suggested already) if you don't see the posibility to get the issues fixed for stable, or do you consider the issues minor enough to ignore them for this time - but what will happen when more severe ones pop up? Thanks, Rhonda -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567364: libxml-filter-xslt-perl: license is ok, just missing a note in d/copyright
severity 567364 important thanks As the license information from debian/copyright is correct and only a note that the copyright holder confirmed that needs to be added, I will downgrade the severity to important. In any case I will try to finish cleaning up the package in the next few days. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Gerfried Fuchs wrote: > Hi! > > * Jeremy T. Bouse [2010-02-01 16:12:06 CET]: >> Gerfried Fuchs wrote: >>> * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: I am currently working on getting 1.4.4 ready to go and remove David Gil from the package per (#551636) >>> Actually, I'm not sure, does this address Moritz' concerns, from a >>> security team's point of view, especially with respect to stable? I >>> don't see any update that would have fixed the security issues for >>> lenny, what is your plan for that? >> 1.4.4 reportedly fixes all current outstanding CVS reports. Short of >> going and simply upgrading the old versions trying to go through the >> code and find the specific fixes to these issues, as I've found no patch >> files specific to the problem, would take much more time than I have >> available when a fixed upstream version is already available in the >> repository. 1.4.4-1 hit the unstable repository in late November and I >> had a few fixes until 1.4.4-3 was migrated to testing just before Christmas. > > You are aware that maintaining a package doesn't mean only taking care > for it in unstable but also to at least try to give the security team a > helping hand for trying to get things straight in a stable release? I > wonder, how severe are the issues actually? Is it better to pull the > package from the stable release (like Moritz suggested already) if you > don't see the posibility to get the issues fixed for stable, or do you > consider the issues minor enough to ignore them for this time - but what > will happen when more severe ones pop up? > > Thanks, > Rhonda If I knew exactly what fixes occurred between 1.3.9 and 1.4.4 that fixed the CVS reported problems I'd be more than happy to fix them and get a new 1.3.9 version made available for the security team to release. However, there are no patches that specifically identify fixing the problem and trying to perform a diff between 1.3.9 and 1.4.4 garners so many changes in the code base that identifying will take much more time than I currently have. All I know of the problem is from the vague information given in the CVS reports which are all listed as medium or high as they report cross-site scripting and SQL injection issues. BASE itself confirmed the problem and released 1.4.4 to fix them. If security team wants to simply pull 1.2.7-4 from etch (oldstable) and 1.3.9-1 from lenny (stable) go ahead and recommend pulling acidbase from squeeze/testing if it's required to be installed on any systems running stable or oldstable. PopCon shows low numbers of installs though doesn't distinquish if they are oldstable, stable, testing or unstable installations. signature.asc Description: OpenPGP digital signature
Bug#567860: php-net-ping: Package installation is trying to overwrite '/usr/share/php/doc'
Hi Thomas, Thomas Goirand wrote: > > Hi, > > If I had upload rights, it would be months that all issues would be > fixed on that package. I've been searching for a sponsor for MONTHS to > have it uploaded. The URL for the updated package is: > > http://ftparchive.gplhost.com/debian/pool/lenny/main/p/php-net-ping/php-net-ping_2.4.5-1.dsc > > I'd be glad if someone uploaded the package for me, until I am approved > to be a DD by my AM. Please consider. The quickest way to get your packages sponsored is via http://mentors.debian.net You can upload you package there and it will be sponsored in a short time. Cheers. -- Dario Minnucci Phone: +34 902021030 | Fax: +34 902024417 | Support: +34 80745 Key fingerprint = 62FF F60F CE79 9CE4 EBA8 523F FC84 1B2D 82C8 B711 signature.asc Description: OpenPGP digital signature
Bug#567977: galeon: needs some kind of xulrunner
Package: galeon Version: 2.0.7-1.2 Severity: grave Justification: renders package unusable Version 2.0.7-1.2 dropped dependency on xulrunner-1.9.1 and starting it without some xulrunner installed makes it exit after saying something about some MOZ_GRE_CONF or MOZILLA_FIVE_HOME environment variable (I really don't remember, sorry). Riccardo -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: lang=it...@euro, lc_ctype=it...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages galeon depends on: ii galeon-common2.0.7-1.2 data for the galeon web browser ii gconf2 2.28.0-1GNOME configuration database syste ii libbonobo2-0 2.24.2-1Bonobo CORBA interfaces library ii libbonoboui2-0 2.24.2-1The Bonobo UI library ii libc62.10.2-5Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.3-1 GCC support library ii libgconf2-4 2.28.0-1GNOME configuration database syste ii libglade2-0 1:2.6.4-1 library to load .glade files at ru ii libglib2.0-0 2.22.4-1The GLib library of C routines ii libgnome-desktop-2-112.28.2-1Utility library for loading .deskt ii libgnome2-0 2.28.0-1The GNOME library - runtime files ii libgnomeui-0 2.24.2-1The GNOME libraries (User Interfac ii libgnomevfs2-0 1:2.24.2-1 GNOME Virtual File System (runtime ii libgtk2.0-0 2.18.6-1The GTK+ graphical user interface ii libnspr4-0d 4.8.3-1 NetScape Portable Runtime Library ii liborbit21:2.14.17-2 libraries for ORBit2 - a CORBA ORB ii libpango1.0-01.26.2-1Layout and rendering of internatio ii libpopt0 1.15-1 lib for parsing cmdline parameters ii libstdc++6 4.4.3-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-1 X11 client-side library ii libxml2 2.7.6.dfsg-2+b1 GNOME XML library ii procps 1:3.2.8-2 /proc file system utilities Versions of packages galeon recommends: pn gnome-control-center (no description available) ii gnome-icon-theme 2.28.0-1 GNOME Desktop icon theme ii iso-codes 3.12.1-1 ISO language, territory, currency, ii rarian-compat [scrollkeeper] 0.8.1-4Documentation meta-data library (c ii scrollkeeper 0.8.1-4Transitional package for scrollkee pn yelp (no description available) Versions of packages galeon suggests: pn mozplugger (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567977: galeon: needs some kind of xulrunner
On Mon, Feb 01, 2010 at 04:48:40PM +0100, Riccardo Stagni wrote: > Package: galeon > Version: 2.0.7-1.2 > Severity: grave > Justification: renders package unusable > > Version 2.0.7-1.2 dropped dependency on xulrunner-1.9.1 and starting it > without some xulrunner installed makes it exit after saying something about > some MOZ_GRE_CONF or MOZILLA_FIVE_HOME environment variable (I really don't > remember, sorry). This is a bug in dh_xulrunner, see #567746. Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567240: script fails without configuration file
Tags: patch
Attached is a patch for the halevt initscript which checks for the
config file to exist before starting halevt. It only checks for the
default location where the Debian package installs the config file
(/etc/halevt/halevt.xml) but not the other places halevt allows to store
the config file ($HOME/.halevt and /usr/share/halevt) which I guess is
ok.
One note though: I was not able to reproduce the bug here with a fresh
install of halevt 0.1.5-3 on sid:
tklau...@krypton:~ % sudo apt-get install halevt
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
halevt
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/59.8kB of archives.
After this operation, 307kB of additional disk space will be used.
Selecting previously deselected package halevt.
(Reading database ... 109185 files and directories currently installed.)
Unpacking halevt (from .../halevt_0.1.5-3_i386.deb) ...
Processing triggers for readahead-fedora ...
Processing triggers for man-db ...
Processing triggers for install-info ...
Setting up halevt (0.1.5-3) ...
Creating a user 'halevt'...
adduser: Warning: The home directory `/var/lib/halevt' does not belong to the
user you are currently creating.
Starting halevt daemon: OK.
sudo apt-get install halevt 4.39s user 1.10s system 77% cpu 7.087 total
tklau...@krypton:~ %
Cheers, Tobias
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-rc5-tk.krypton (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages halevt depends on:
ii adduser 3.112 add and remove users and groups
ii dpkg 1.15.5.6Debian package management system
ii hal 0.5.14-2Hardware Abstraction Layer
ii install-info 4.13a.dfsg.1-5 Manage installed documentation in
ii libboolstuff-0.1-0 0.1.12-3library for operating on boolean e
ii libc62.10.2-5Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.16-2simple interprocess messaging syst
ii libdbus-glib-1-2 0.82-2 simple interprocess messaging syst
ii libglib2.0-0 2.22.4-1The GLib library of C routines
ii libhal1 0.5.14-2Hardware Abstraction Layer - share
ii libxml2 2.7.6.dfsg-2+b1 GNOME XML library
halevt recommends no packages.
halevt suggests no packages.
-- no debconf information
Index: halevt-0.1.5/halevt-initscript
===
--- halevt-0.1.5.orig/halevt-initscript 2010-01-31 20:02:38.0 +0100
+++ halevt-0.1.5/halevt-initscript 2010-01-31 22:55:33.0 +0100
@@ -34,7 +34,9 @@
[ -e /etc/default/halevt ] && . /etc/default/halevt
halevt_start() {
-if [ "$START_DAEMON" = "yes" ]; then
+if [ ! -e /etc/halevt/halevt.xml ]; then
+log_warning_msg "Not starting halevt daemon; configuration file missing"
+elif [ "$START_DAEMON" = "yes" ]; then
echo -n "Starting halevt daemon: "
start-stop-daemon --start --oknodo --pidfile $PIDFILE \
Bug#554790: grub-pc: store grub-pc/install_devices using by-id
Colin Watson wrote: > UUIDs are properties of filesystems, not disks or partitions, and the > MBR of a hard disk does not have a UUID. For disks, the choices for > stable identifiers are based on either the hardware serial number or the > bus path taken to reach the disk. What about block device emulations, e.g. software RAIDs, LVM, etc? Not to mention that GPT _does_ support UUIDs in the disk and partition headers. Just my $0.02. Regards Harri signature.asc Description: OpenPGP digital signature
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Gerfried Fuchs wrote: > Hi! > > * Jeremy T. Bouse [2010-02-01 16:12:06 CET]: > > Gerfried Fuchs wrote: > > > * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: > > >> I am currently working on getting 1.4.4 ready to go and remove David > > >> Gil from the package per (#551636) > > > > > > Actually, I'm not sure, does this address Moritz' concerns, from a > > > security team's point of view, especially with respect to stable? I > > > don't see any update that would have fixed the security issues for > > > lenny, what is your plan for that? > > > > 1.4.4 reportedly fixes all current outstanding CVS reports. Short of > > going and simply upgrading the old versions trying to go through the > > code and find the specific fixes to these issues, as I've found no patch > > files specific to the problem, would take much more time than I have > > available when a fixed upstream version is already available in the > > repository. 1.4.4-1 hit the unstable repository in late November and I > > had a few fixes until 1.4.4-3 was migrated to testing just before Christmas. > > You are aware that maintaining a package doesn't mean only taking care > for it in unstable but also to at least try to give the security team a > helping hand for trying to get things straight in a stable release? I > wonder, how severe are the issues actually? Is it better to pull the > package from the stable release (like Moritz suggested already) if you > don't see the posibility to get the issues fixed for stable, or do you > consider the issues minor enough to ignore them for this time - but what > will happen when more severe ones pop up? An additional possibility might be to limit the scope of security support to local, trusted users behind an authenticated HTTP zone. We're doing that for a few applications already, e.g. sql-ledger or ocsinventory. You wouldn't expose your accounting or hardware inventory to untrusted users and the same should apply to IDS results. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552235: acidbase: multiple security flaws, needs maintenance or removal?
Moritz Muehlenhoff wrote: > Gerfried Fuchs wrote: >> Hi! >> >> * Jeremy T. Bouse [2010-02-01 16:12:06 CET]: >>> Gerfried Fuchs wrote: * Jeremy T. Bouse [2009-11-27 19:30:47 CET]: > I am currently working on getting 1.4.4 ready to go and remove David > Gil from the package per (#551636) Actually, I'm not sure, does this address Moritz' concerns, from a security team's point of view, especially with respect to stable? I don't see any update that would have fixed the security issues for lenny, what is your plan for that? >>> 1.4.4 reportedly fixes all current outstanding CVS reports. Short of >>> going and simply upgrading the old versions trying to go through the >>> code and find the specific fixes to these issues, as I've found no patch >>> files specific to the problem, would take much more time than I have >>> available when a fixed upstream version is already available in the >>> repository. 1.4.4-1 hit the unstable repository in late November and I >>> had a few fixes until 1.4.4-3 was migrated to testing just before Christmas. >> You are aware that maintaining a package doesn't mean only taking care >> for it in unstable but also to at least try to give the security team a >> helping hand for trying to get things straight in a stable release? I >> wonder, how severe are the issues actually? Is it better to pull the >> package from the stable release (like Moritz suggested already) if you >> don't see the posibility to get the issues fixed for stable, or do you >> consider the issues minor enough to ignore them for this time - but what >> will happen when more severe ones pop up? > > An additional possibility might be to limit the scope of security support > to local, trusted users behind an authenticated HTTP zone. We're doing that > for a few applications already, e.g. sql-ledger or ocsinventory. > You wouldn't expose your accounting or hardware inventory to untrusted > users and the same should apply to IDS results. > > Cheers, > Moritz In which case this is a non-issue to anyone who uses the default Apache configuration which limits access to localhost and has since 1.2.7. 1 2 Alias /acidbase "/usr/share/acidbase" 3 4 5 6 Options +FollowSymLinks 7 AllowOverride None 8 order deny,allow 9 deny from all 10 allow from 127.0.0.0/255.0.0.0 11 12 php_flag magic_quotes_gpc Off 13 php_flag track_vars On 14 php_value include_path .:/usr/share/php 15 16 signature.asc Description: OpenPGP digital signature
Bug#539750: marked as done (emacs22: must stop generating the emacs metapackage)
Your message dated Mon, 01 Feb 2010 17:18:04 + with message-id and subject line Bug#539750: fixed in emacs22 22.3+1-1.2 has caused the Debian Bug report #539750, regarding emacs22: must stop generating the emacs metapackage to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 539750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs22 Version: 22.3+1-1.1 Severity: serious #433861¹ redux: the `emacs' metapackage is now provided by the emacs23 source package. The emacs22 package has to stop shipping it, else further uploads will be rejected by dak. ¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433861 --- End Message --- --- Begin Message --- Source: emacs22 Source-Version: 22.3+1-1.2 We believe that the bug you reported is fixed in the latest version of emacs22, which is due to be installed in the Debian FTP archive: emacs22-bin-common_22.3+1-1.2_amd64.deb to main/e/emacs22/emacs22-bin-common_22.3+1-1.2_amd64.deb emacs22-common_22.3+1-1.2_all.deb to main/e/emacs22/emacs22-common_22.3+1-1.2_all.deb emacs22-el_22.3+1-1.2_all.deb to main/e/emacs22/emacs22-el_22.3+1-1.2_all.deb emacs22-gtk_22.3+1-1.2_amd64.deb to main/e/emacs22/emacs22-gtk_22.3+1-1.2_amd64.deb emacs22-nox_22.3+1-1.2_amd64.deb to main/e/emacs22/emacs22-nox_22.3+1-1.2_amd64.deb emacs22_22.3+1-1.2.diff.gz to main/e/emacs22/emacs22_22.3+1-1.2.diff.gz emacs22_22.3+1-1.2.dsc to main/e/emacs22/emacs22_22.3+1-1.2.dsc emacs22_22.3+1-1.2_amd64.deb to main/e/emacs22/emacs22_22.3+1-1.2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 539...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (supplier of updated emacs22 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 25 Jan 2010 15:05:36 +0100 Source: emacs22 Binary: emacs22 emacs22-nox emacs22-gtk emacs22-bin-common emacs22-common emacs22-el Architecture: source all amd64 Version: 22.3+1-1.2 Distribution: unstable Urgency: low Maintainer: Rob Browning Changed-By: Alexander Reichle-Schmehl Description: emacs22- The GNU Emacs editor emacs22-bin-common - The GNU Emacs editor's shared, architecture dependent files emacs22-common - The GNU Emacs editor's shared, architecture independent infrastru emacs22-el - GNU Emacs LISP (.el) files emacs22-gtk - The GNU Emacs editor (with GTK user interface) emacs22-nox - The GNU Emacs editor (without X support) Closes: 534002 539750 545497 Changes: emacs22 (22.3+1-1.2) unstable; urgency=low . * Non-maintainer upload. * Drop emacs metapackage (Closes: #539750) * Force removals of various stuff in debian/rules (Closes: #545497) * Apply patch by Ulrich Mueller to solve potential FTBFS by "intermittent unexec failure" problem (Closes: #534002) Checksums-Sha1: 29601b76e28c1b04dc5250b981e50acc15cf3bf9 1405 emacs22_22.3+1-1.2.dsc ed0ec0ebcefab744e430a429bd07c453f7c0024c 121923 emacs22_22.3+1-1.2.diff.gz 9daf4e614b11ddd9501fe84614fc425aeb635234 14768546 emacs22-common_22.3+1-1.2_all.deb 900a77555c10273fd6751469efb7e60ba025fb08 11488188 emacs22-el_22.3+1-1.2_all.deb f5779464485fb46c7b980587414a64d4e745d4f8 2898834 emacs22_22.3+1-1.2_amd64.deb 1af4be347f7768c238c206aa24c46725b6813812 2596276 emacs22-nox_22.3+1-1.2_amd64.deb 6ef760123ffdc10fc4a872c5a5cffc07d71e6ae3 2893320 emacs22-gtk_22.3+1-1.2_amd64.deb 9966383cf2a9bae80b02e87dd04d54d682e112c4 186366 emacs22-bin-common_22.3+1-1.2_amd64.deb Checksums-Sha256: 11617878a35360aa86868be05ba7c7b570ef92b1a9232c401f88c44c75b49aa4 1405 emacs22_22.3+1-1.2.dsc 72808f5c1d36b57246c5d40c172f023c8866744e7553609ffbbb877ca22573ff 121923 emacs22_22.3+1-1.2.diff.gz 2c55a6751ae213ac4decbde50a9f5621ea795c440d9c0b0da18ca2d7a5bf4c7b 14768546 emacs22-common_22.3+1-1.2_all.deb e9f3e884cbfb8d50af4fcb4106e3f33bdc7a54380add173cc82b34e7e46c813a 11488188 emacs22-el_22.3+1-1.2_all.deb b7e5facf9b907332364b07b9c7b319546192c8ca2511b8a61f4d58ba54004529 2898834 emacs22_22.3+1-1.2_amd64.deb 165a0886ea9806eb684d1e86f150ff6dae3fd0969fa80020b812896eace787f6 2596276 emacs22-nox_22.3+1-1.2_amd64.deb 8c0edb68708ad9e6c4be2a756163d3e3
Bug#545497: marked as done (emacs23: FTBFS: rm: cannot remove `/tmp/buildd/emacs23-23.1+1/debian/emacs23-common/usr/share/info/emacs-23/dir.old': No such file or directory)
Your message dated Mon, 01 Feb 2010 17:18:04 + with message-id and subject line Bug#545497: fixed in emacs22 22.3+1-1.2 has caused the Debian Bug report #545497, regarding emacs23: FTBFS: rm: cannot remove `/tmp/buildd/emacs23-23.1+1/debian/emacs23-common/usr/share/info/emacs-23/dir.old': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 545497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545497 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs23 Version: 23.1+1-3 Severity: serious Tags: patch >From my pbuilder log: , | set -o pipefail; cd /tmp/buildd/emacs23-23.1+1/debian/emacs23-common && \ | find -name "*.elc" | perl -pe 's/\.elc$/\.el/o' | xargs rm -f | set -o pipefail; cd /tmp/buildd/emacs23-23.1+1/debian/emacs23-common && \ | find -name "*.elc" | perl -pe 's/\.elc$/\.el\.gz/o' | xargs rm -f | rm /tmp/buildd/emacs23-23.1+1/debian/emacs23-common/usr/share/info/emacs-23/dir | rm /tmp/buildd/emacs23-23.1+1/debian/emacs23-common/usr/share/info/emacs-23/dir.old | rm: cannot remove `/tmp/buildd/emacs23-23.1+1/debian/emacs23-common/usr/share/info/emacs-23/dir.old': No such file or directory | make: *** [install] Error 1 ` This happens since the upload of dpkg 1.15.4 to unstable. The following patch takes care of this, but there are many other cases in debian/rules where "rm" should really be replaced with "rm -f": --8<---cut here---start->8--- diff -u emacs23-23.1+1/debian/rules emacs23-23.1+1/debian/rules --- emacs23-23.1+1/debian/rules +++ emacs23-23.1+1/debian/rules @@ -779,8 +779,8 @@ find -name "*.elc" | perl -pe 's/\.elc$$/\.el\.gz/o' | xargs rm -f # Remove extraneous info dir file. - rm $(pkgdir_common)/usr/share/info/emacs-$(major_ver)/dir - rm $(pkgdir_common)/usr/share/info/emacs-$(major_ver)/dir.old + rm -f $(pkgdir_common)/usr/share/info/emacs-$(major_ver)/dir + rm -f $(pkgdir_common)/usr/share/info/emacs-$(major_ver)/dir.old # Remove the shared game score directory to as a simple way to avoid # a conflict with other flavors of Emacs. Since Debian's --8<---cut here---end--->8--- -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 2.6.30.5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages emacs23 depends on: ii emacs23-bin-common 23.1+1-3 The GNU Emacs editor's shared, arc ii install-info 4.13a.dfsg.1-4Manage installed documentation in ii libasound2 1.0.20-4 shared library for ALSA applicatio ii libatk1.0-01.26.0-1 The ATK accessibility toolkit ii libc6 2.9-26GNU C Library: Shared libraries ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra ii libdbus-1-31.2.16-2 simple interprocess messaging syst ii libfontconfig1 2.6.0-4 generic font configuration library ii libfreetype6 2.3.9-5 FreeType 2 font engine, shared lib ii libgif44.1.6-8 library for GIF images (library) ii libglib2.0-0 2.20.5-1 The GLib library of C routines ii libgpm21.20.4-3.2General Purpose Mouse - shared lib ii libgtk2.0-02.16.6-1 The GTK+ graphical user interface ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libjpeg62 6b-15 The Independent JPEG Group's JPEG ii libm17n-0 1.5.4-1+b1a multilingual text processing lib ii libncurses55.7+20090906-1shared libraries for terminal hand ii libotf00.9.9-1 A Library for handling OpenType Fo ii libpango1.0-0 1.24.5-1 Layout and rendering of internatio ii libpng12-0 1.2.39-1 PNG library - runtime ii librsvg2-2 2.26.0-1 SAX-based renderer library for SVG ii libsm6 2:1.1.1-1 X11 Session Management library ii libtiff4 3.9.1-1 Tag Image File Format (TIFF) libra ii libx11-6 2:1.2.2-1 X11 client-side library ii libxft22.1.13-3 FreeType-based font drawing librar ii libxpm41:3.5.7-2
Bug#565635: [Pkg-net-snmp-devel] Bug#565635: Crashes when queried
Hi Simon, Package: snmpd Version: 5.4.2.1~dfsg-5 Severity: grave since the last upgrade, about any GETNEXT request makes snmpd crash, first logging an assertion failure, then stumbling over what looks like a null pointer dereference (address 0x20c). > ii libsnmp15 5.4.2.1~dfsg-4 SNMP (Simple Network Management Pr Does this still happen with libsnmp15 5.4.2.1~dfsg-5? Thanks, Jochen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#534002: marked as done (emacs22: FTBFS: make[2]: *** [emacs] Segmentation fault)
Your message dated Mon, 01 Feb 2010 17:18:04 + with message-id and subject line Bug#534002: fixed in emacs22 22.3+1-1.2 has caused the Debian Bug report #534002, regarding emacs22: FTBFS: make[2]: *** [emacs] Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 534002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: emacs22 Version: 22.3+1-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20090620 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[2]: Entering directory > `/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/debian/build-nox/src' > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/pre-crt0.c > touch stamp-oldxmenu > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/dispnew.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/frame.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/scroll.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/xdisp.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/xmenu.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/window.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/charset.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/coding.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/category.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/ccl.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/cm.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/term.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src -D_BSD_SOURCE > -I/usr/include/alsa -DDEBIAN -g -O2 > /build/user-emacs22_22.3+1-1-amd64-XN4ZEt/emacs22-22.3+1/src/xfaces.c > x86_64-linux-gnu-gcc -c -D_BSD_SOURCE -Demacs -DHAVE_CONFIG_H -I. > -I/build/user-emacs22
Processed: Netenv 0.94.3-26 is going to be uploaded soon
Processing commands for cont...@bugs.debian.org: > tags 547394 + pending Bug #547394 [netenv] netenv: deletes rcS.d symlink on upgrade Added tag(s) pending. > tags 554354 + pending Bug #554354 [netenv] netenv: [INTL:ru] Russian debconf templates translation Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567958: wicd-daemon fails to start
forcemerge 566023 567958 severity 566023 serious tags 566023 confirmed pending thanks Hello, On Monday 01 February 2010 15:15:32, Sébastien wrote: > When I try to start wicd manually it seems some python packages are missing > : $ wicd > Traceback (most recent call last): > File "/usr/share/wicd/daemon/wicd-daemon.py", line 61, in > from wicd.logfile import ManagedStdio > ImportError: No module named logfile > > But python-wicd 1.7.0-2 is installed on my system. This is the same as #566023, please don't file duplicated bugreports :) I'll upload a package fixing this as soon as possible. Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: This is a digitally signed message part.
Processed (with 1 errors): Re: Bug#567958: wicd-daemon fails to start
Processing commands for cont...@bugs.debian.org: > forcemerge 566023 567958 Bug#566023: python-wicd is not pulled in with the dependencies Bug#567958: wicd-daemon fails to start Mismatch - only Bugs in the same package can be forcibly merged: Bug 567958 is not in the same package as 566023 > severity 566023 serious Bug #566023 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566027 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566030 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566203 [src:wicd] python-wicd is not pulled in with the dependencies Severity set to 'serious' from 'grave' Severity set to 'serious' from 'grave' Severity set to 'serious' from 'grave' Severity set to 'serious' from 'grave' > tags 566023 confirmed pending Bug #566023 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566027 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566030 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566203 [src:wicd] python-wicd is not pulled in with the dependencies Ignoring request to alter tags of bug #566023 to the same tags previously set Ignoring request to alter tags of bug #566027 to the same tags previously set Ignoring request to alter tags of bug #566030 to the same tags previously set Ignoring request to alter tags of bug #566203 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Uhm, fixing it
Processing commands for cont...@bugs.debian.org: > reassign 567958 src:wicd Bug #567958 [wicd-daemon] wicd-daemon fails to start Bug reassigned from package 'wicd-daemon' to 'src:wicd'. Bug No longer marked as found in versions wicd/1.7.0-2. > forcemerge 566023 567958 Bug#566023: python-wicd is not pulled in with the dependencies Bug#567958: wicd-daemon fails to start Bug#566027: python-wicd is not pulled in with the dependencies Bug#566030: python-wicd is not pulled in with the dependencies Bug#566203: python-wicd is not pulled in with the dependencies Forcibly Merged 566023 566027 566030 566203 567958. > severity 566023 serious Bug #566023 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566027 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566030 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566203 [src:wicd] python-wicd is not pulled in with the dependencies Bug #567958 [src:wicd] wicd-daemon fails to start Ignoring request to change severity of Bug 566023 to the same value. Ignoring request to change severity of Bug 566027 to the same value. Ignoring request to change severity of Bug 566030 to the same value. Ignoring request to change severity of Bug 566203 to the same value. Ignoring request to change severity of Bug 567958 to the same value. > retitle 566023 stale files in PYTHONPATH Bug #566023 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566027 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566030 [src:wicd] python-wicd is not pulled in with the dependencies Bug #566203 [src:wicd] python-wicd is not pulled in with the dependencies Bug #567958 [src:wicd] wicd-daemon fails to start Changed Bug title to 'stale files in PYTHONPATH' from 'python-wicd is not pulled in with the dependencies' Changed Bug title to 'stale files in PYTHONPATH' from 'python-wicd is not pulled in with the dependencies' Changed Bug title to 'stale files in PYTHONPATH' from 'python-wicd is not pulled in with the dependencies' Changed Bug title to 'stale files in PYTHONPATH' from 'python-wicd is not pulled in with the dependencies' Changed Bug title to 'stale files in PYTHONPATH' from 'wicd-daemon fails to start' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567991: root-system: Root-system uninstallable
Package: root-system Severity: grave Tags: patch Justification: renders package unusable root-system requires libkrb53, which is now libkrb5-3. [1] Ubuntu have patched this, so you can just use that and rebuild. [2] [1] http://packages.qa.debian.org/k/krb5.html [2] https://bugs.launchpad.net/ubuntu/+source/root-system/+bug/462059 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages root-system depends on: pn libroot-dev(no description available) pn root-system-bin(no description available) Versions of packages root-system recommends: pn libroot-ldap-dev (no description available) pn libroot-mathmore-dev (no description available) pn libroot-minuit-dev (no description available) pn libroot-mlp-dev(no description available) pn libroot-quadp-dev (no description available) pn libroot-tmva-dev (no description available) pn libroot-unuran-dev (no description available) pn root-plugin-asimage(no description available) pn root-plugin-fftw3 (no description available) pn root-plugin-fumili (no description available) pn root-plugin-gl (no description available) pn root-plugin-hbook (no description available) pn root-plugin-krb5 (no description available) pn root-plugin-minuit2(no description available) pn root-plugin-netx (no description available) pn root-plugin-odbc (no description available) pn root-plugin-proof (no description available) pn root-plugin-qt (no description available) pn root-plugin-sql(no description available) pn root-plugin-xml(no description available) pn root-plugin-xproof (no description available) pn root-system-doc(no description available) pn root-system-proofd (no description available) pn root-system-rootd (no description available) pn root-system-xrootd (no description available) Versions of packages root-system suggests: pn libroot-clarens-dev(no description available) pn libroot-python-dev (no description available) pn libroot-roofit-dev (no description available) pn libroot-ruby-dev (no description available) pn root-plugin-mysql (no description available) pn root-plugin-peac (no description available) pn root-plugin-pgsql (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#565635: [Pkg-net-snmp-devel] Bug#565635: Crashes when queried
On 01.02.10 Jochen Friedrich (joc...@scram.de) wrote: Hi Jochen, > >Package: snmpd > >Version: 5.4.2.1~dfsg-5 > >Severity: grave > > > >since the last upgrade, about any GETNEXT request makes snmpd crash, > >first logging an assertion failure, then stumbling over what looks like > >a null pointer dereference (address 0x20c). > > > >ii libsnmp15 5.4.2.1~dfsg-4 SNMP (Simple Network > >Management Pr > > Does this still happen with libsnmp15 5.4.2.1~dfsg-5? > I see crashes after running for 3-4 hours, yes with 5.4.2.1~dfsg-5+b1 too. Not sure If I see the same problem as Simon, I didn't analyze it yet. H. -- sigmentation fault -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567977: galeon: needs some kind of xulrunner
On Mon, Feb 01, 2010 at 04:59:49PM +0100, Mike Hommey wrote: > This is a bug in dh_xulrunner, see #567746. oh, sorry! Please reassign/re-severity appropriately! (or it could be used as a reminder when binNMU-ing packages build-depending on xulrunner-dev) ciao Riccardo signature.asc Description: Digital signature
Processed: submitter 563916
Processing commands for cont...@bugs.debian.org: > submitter 563916 ! Bug #563916 [libghc6-haskelldb-hdbc-dev] Depend on unavailable packages libghc6-hdbc-dev (< 2.1.0+) and libghc6-convertible-dev (< 1.0.2+). Changed Bug submitter to 'Marco Túlio Gontijo e Silva ' from 'Marco Túlio Gontijo e Silva ' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562791: Bug#562607: Patch for NMU
On Sun, Jan 31, 2010 at 01:21:54PM -0800, Bruce Korb wrote: > Kurt Roeckx wrote: > > Hi, > > > > I've NMU'd your package. Please find the patch that I used > > attached. > > > > Some comments: > > - You might want to use something like: > > dh_makeshlibs -V "libopts25 (>= 1:5.10)" > > This would require that you update this properly on new release. > > I've just used -V would would just base it on the upstream > > version. > > Probably something to always do. I'm not a Debian packaging person, > so I don't really know what "dh_makeshlibs" does. dh_makeshlibs will create a file (shlibs) that it shipped with a library that tells other libraries which dependecies it should use in case they link to that library. The -V option will create the most strict requirements by default, which isn't always needed. If you release a 5.10.1 version, it might be fully compatible with 5.10 and just contain bug fixes. It could be that anything linked against a 5.10.x version should work with the 5.10 version, so a depedency on that or higher might be enough. But 5.10.1 might also introduce new symbols for instance, and then we'd need to make sure that packages depend on 5.10.1. Anyway, how this works is probably not that interesting for you. What we'd like to know is which versions are fully compatible with each others. I assume that 5.10.x will keep compatibilty and that if you change something in a way that it's not fully compatible that you change it to 5.11. But it's not important that you do it like that, any system that you use should work for us. > > - I've just removed some code from autoopts-config.in. It says > > it's autogenerated, but I can't find the source for that. > > Upstream probably added this code for some reason, so might want > > a better patch. In any case, there is no reason to add the > > rpath on a Debian system since it's configured for /usr/lib and > > that's always in the dynamic linker's search path. I didn't > > remove the -L/usr/lib because it doesn't hurt anything. > > That stuff is there because without it, when you run a build and > "make check", the executables will link against the installed version. > Sometimes it causes breakage, but most times it silently tests the > installed libraries instead of what you think you're testing. > I need a reliable way to ensure that "make check" finds the autoopts/.libs/... > stuff before any installed versions. Portably. Not just for Debian. :( Doesn't libtool do that for you? If you're linking against a non-installed library it should create an rpath. If something is broken, feel free to file a bug against the libtool package. (I'm Debian's libtool maintainer.) Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: submitter 566331
Processing commands for cont...@bugs.debian.org:
> submitter 566331 !
Bug #566331 {Done: Kari Pahula } [ghc6] ghc6-6.12.1-2 FTBFS in
s390.
Changed Bug submitter to 'Marco Túlio Gontijo e Silva '
from 'Marco Túlio Gontijo e Silva '
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567977: galeon: needs some kind of xulrunner
On Mon, Feb 01, 2010 at 07:09:20PM +0100, Riccardo Stagni wrote: > On Mon, Feb 01, 2010 at 04:59:49PM +0100, Mike Hommey wrote: > > This is a bug in dh_xulrunner, see #567746. > > oh, sorry! Please reassign/re-severity appropriately! > (or it could be used as a reminder when binNMU-ing packages > build-depending on xulrunner-dev) Don't be sorry, the bug was only reported a few hours ago, while the broken dh_xulrunner has been around for more than a month unnoticed. Let's just keep the bug this way for now. I'll probably upload the fixed xulrunner tomorrow and will request binNMUs following that (spotted 5 packages affected, already) Cheers, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566203: marked as done (stale files in PYTHONPATH)
Your message dated Mon, 01 Feb 2010 18:54:00 + with message-id and subject line Bug#566023: fixed in wicd 1.7.0-3 has caused the Debian Bug report #566023, regarding stale files in PYTHONPATH to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 566023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd Version: 1.7.0-2 Severity: grave Justification: renders package unusable Hello, I even reported it to the wicd guys but they told me that the problem is in the Debian packages: https://bugs.launchpad.net/wicd/+bug/510589 Thank you. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd depends on: ii wicd-daemon 1.7.0-2wired and wireless network manager ii wicd-gtk [wicd-client]1.7.0-2wired and wireless network manager wicd recommends no packages. wicd suggests no packages. -- debconf information: * wicd/users: --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.0-3 We believe that the bug you reported is fixed in the latest version of wicd, which is due to be installed in the Debian FTP archive: python-wicd_1.7.0-3_all.deb to main/w/wicd/python-wicd_1.7.0-3_all.deb wicd-cli_1.7.0-3_all.deb to main/w/wicd/wicd-cli_1.7.0-3_all.deb wicd-curses_1.7.0-3_all.deb to main/w/wicd/wicd-curses_1.7.0-3_all.deb wicd-daemon_1.7.0-3_all.deb to main/w/wicd/wicd-daemon_1.7.0-3_all.deb wicd-gtk_1.7.0-3_all.deb to main/w/wicd/wicd-gtk_1.7.0-3_all.deb wicd_1.7.0-3.debian.tar.gz to main/w/wicd/wicd_1.7.0-3.debian.tar.gz wicd_1.7.0-3.dsc to main/w/wicd/wicd_1.7.0-3.dsc wicd_1.7.0-3_all.deb to main/w/wicd/wicd_1.7.0-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 566...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino (supplier of updated wicd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Feb 2010 18:43:38 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.0-3 Distribution: unstable Urgency: low Maintainer: David Paleino Changed-By: David Paleino Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable cli client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 565637 566023 567070 567665 Changes: wicd (1.7.0-3) unstable; urgency=low . * Remove .pyo and .pyc files upon package removal (Closes: #565637) - debian/wicd-daemon.postrm updated - debian/wicd-cli.postrm, debian/wicd-curses.postrm, debian/wicd-gtk.postrm added * debian/control: - removed trailing comma in wicd-daemon Recommends - Standards-Version bumped to 3.8.4, no changes needed * debian/wicd-daemon.postinst: better handle upgrades (Closes: #566023) * debian/wicd-daemon.wicd.init: correctly handle the exit code for the "status" command (Closes: #567070) * debian/patches/: - 03-fix_typo_wicd-cli.patch added, fixes typo preventing wicd-cli from working at all (Closes: #567665) Checksums-Sha1: 6dd65a7cf3367988296e67ca45590419026fb16c 1241 wicd_1.7.0-3.dsc 25cdb0b6a4c0a146f4c7827fb382382d649e83f5 22662 wicd_1.7.0-3.debian.tar.gz 8aad2e7348f2cd3ba2b68c5f8dc6bc4cfda3ab6f 39402 wicd_1.7.0-3_all.deb 18b40bcf840a9ea8016c42f8fdb9994d885b61e5 272516 wicd-daemon_1.7.0-3_all.deb e90f9d0807e7d1fbbb0aeffd07ca2d5e9da57c6b 146042 wicd-gtk_1.7.0-3_all.deb 0fd10c31c13bf7a2e6dc5e551eb3c0c594689b28 69450 wicd-curses_1.7.0-3_all.deb f29345c54a307748682f4b3b3128c56aabd95703 43116 wicd-cli_1.7.0-3_all.deb e2c8a2330346ac50e609cb455adab19762abb79c 75680 python-wicd_1.7.0-3_all.de
Bug#566027: marked as done (stale files in PYTHONPATH)
Your message dated Mon, 01 Feb 2010 18:54:00 + with message-id and subject line Bug#566023: fixed in wicd 1.7.0-3 has caused the Debian Bug report #566023, regarding stale files in PYTHONPATH to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 566023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd-curses Version: 1.7.0-2 Severity: important Hi, After upgrade, wicd-curses fails to start and gives the following : st...@localhost:~$ wicd-curses Traceback (most recent call last): File "/usr/share/wicd/curses/wicd-curses.py", line 52, in from wicd import dbusmanager ImportError: cannot import name dbusmanager Purging and reinstalling it didn't do the trick. Cheers -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (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 wicd-curses depends on: ii python2.5.4-5An interactive high-level object-o ii python-urwid 0.9.9-2curses-based UI/widget library for ii wicd-daemon 1.7.0-2wired and wireless network manager Versions of packages wicd-curses recommends: ii sudo 1.7.2p1-1 Provide limited super user privile wicd-curses suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.0-3 We believe that the bug you reported is fixed in the latest version of wicd, which is due to be installed in the Debian FTP archive: python-wicd_1.7.0-3_all.deb to main/w/wicd/python-wicd_1.7.0-3_all.deb wicd-cli_1.7.0-3_all.deb to main/w/wicd/wicd-cli_1.7.0-3_all.deb wicd-curses_1.7.0-3_all.deb to main/w/wicd/wicd-curses_1.7.0-3_all.deb wicd-daemon_1.7.0-3_all.deb to main/w/wicd/wicd-daemon_1.7.0-3_all.deb wicd-gtk_1.7.0-3_all.deb to main/w/wicd/wicd-gtk_1.7.0-3_all.deb wicd_1.7.0-3.debian.tar.gz to main/w/wicd/wicd_1.7.0-3.debian.tar.gz wicd_1.7.0-3.dsc to main/w/wicd/wicd_1.7.0-3.dsc wicd_1.7.0-3_all.deb to main/w/wicd/wicd_1.7.0-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 566...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino (supplier of updated wicd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Feb 2010 18:43:38 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.0-3 Distribution: unstable Urgency: low Maintainer: David Paleino Changed-By: David Paleino Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired and wireless network manager - scriptable cli client wicd-curses - wired and wireless network manager - Curses client wicd-daemon - wired and wireless network manager - daemon wicd-gtk - wired and wireless network manager - GTK+ client Closes: 565637 566023 567070 567665 Changes: wicd (1.7.0-3) unstable; urgency=low . * Remove .pyo and .pyc files upon package removal (Closes: #565637) - debian/wicd-daemon.postrm updated - debian/wicd-cli.postrm, debian/wicd-curses.postrm, debian/wicd-gtk.postrm added * debian/control: - removed trailing comma in wicd-daemon Recommends - Standards-Version bumped to 3.8.4, no changes needed * debian/wicd-daemon.postinst: better handle upgrades (Closes: #566023) * debian/wicd-daemon.wicd.init: correctly handle the exit code for the "status" command (Closes: #567070) * debian/patches/: - 03-fix_typo_wicd-cli.patch added, fixes typo preventing wicd-cli from working at all (Closes: #567665) Checksums-Sha1: 6dd65a7cf3367988296e67ca45590419026fb16c 1241 wicd_1.7.0-3.dsc 25cdb0b6a4c0a146f4c7827fb382382d649e83f5 22662 wicd_1.7.0-3.debian.tar.gz 8aad2e7348f2cd3ba2b68c5f8dc6bc4cfda3ab6f 39402 wicd_1.7.0-3_all.deb 18b40bcf840a9ea8016c42f8fdb9994d885b61e5 2725
Bug#567958: marked as done (stale files in PYTHONPATH)
Your message dated Mon, 01 Feb 2010 18:54:00 + with message-id and subject line Bug#566023: fixed in wicd 1.7.0-3 has caused the Debian Bug report #566023, regarding stale files in PYTHONPATH to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 566023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wicd-daemon Version: 1.7.0-2 Severity: grave Justification: renders package unusable Hi, Since the last update wicd refuses to start : $ sudo /etc/init.d/wicd start Starting Network connection manager: wicd failed When I try to start wicd manually it seems some python packages are missing : $ wicd Traceback (most recent call last): File "/usr/share/wicd/daemon/wicd-daemon.py", line 61, in from wicd.logfile import ManagedStdio ImportError: No module named logfile But python-wicd 1.7.0-2 is installed on my system. I have the same error on a non 64 architecture following the last update of the package. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (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/dash Versions of packages wicd-daemon depends on: ii adduser 3.112add and remove users and groups ii dbus1.2.16-2 simple interprocess messaging syst ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii dhcp3-client3.1.3-2 DHCP client ii iproute 20091226-1 networking and traffic control too ii iputils-ping3:20071127-2 Tools to test the reachability of ii lsb-base3.2-23 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ii psmisc 22.10-1 utilities that use the proc file s ii python 2.5.4-9 An interactive high-level object-o ii python-dbus 0.83.0-1+b1 simple interprocess messaging syst ii python-gobject 2.20.0-1+b1 Python bindings for the GObject li ii python-wicd 1.7.0-2 wired and wireless network manager ii wireless-tools 30~pre9-3Tools for manipulating Linux Wirel ii wpasupplicant 0.6.9-3 client support for WPA and WPA2 (I Versions of packages wicd-daemon recommends: ii wicd-gtk [wicd-client]1.7.0-2wired and wireless network manager Versions of packages wicd-daemon suggests: ii pm-utils 1.2.6.1-3 utilities and scripts for power ma -- debconf information: * wicd/users: ustilago --- End Message --- --- Begin Message --- Source: wicd Source-Version: 1.7.0-3 We believe that the bug you reported is fixed in the latest version of wicd, which is due to be installed in the Debian FTP archive: python-wicd_1.7.0-3_all.deb to main/w/wicd/python-wicd_1.7.0-3_all.deb wicd-cli_1.7.0-3_all.deb to main/w/wicd/wicd-cli_1.7.0-3_all.deb wicd-curses_1.7.0-3_all.deb to main/w/wicd/wicd-curses_1.7.0-3_all.deb wicd-daemon_1.7.0-3_all.deb to main/w/wicd/wicd-daemon_1.7.0-3_all.deb wicd-gtk_1.7.0-3_all.deb to main/w/wicd/wicd-gtk_1.7.0-3_all.deb wicd_1.7.0-3.debian.tar.gz to main/w/wicd/wicd_1.7.0-3.debian.tar.gz wicd_1.7.0-3.dsc to main/w/wicd/wicd_1.7.0-3.dsc wicd_1.7.0-3_all.deb to main/w/wicd/wicd_1.7.0-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 566...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino (supplier of updated wicd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Feb 2010 18:43:38 +0100 Source: wicd Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd Architecture: source all Version: 1.7.0-3 Distribution: unstable Urgency: low Maintainer: David Paleino Changed-By: David Paleino Description: python-wicd - wired and wireless network manager - Python module wicd - wired and wireless network manager - metapackage wicd-cli - wired
