Bug#556671: marked as done (FTBFS with binutils-gold)
Your message dated Thu, 23 Jun 2011 14:34:53 +0900 (JST) with message-id 20110623.143453.306658922.ko...@pm.tokushima-u.ac.jp and subject line Re: Bug#556671: FTBFS with binutils-gold has caused the Debian Bug report #556671, regarding FTBFS with binutils-gold 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.) -- 556671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: texworks Version: 0.2.3-2 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking g++ -Wl,-O1 -o texworks obj/main.o obj/TWApp.o obj/TWUtils.o obj/TeXDocument.o obj/CompletingEdit.o obj/TeXHighlighter.o obj/TeXDocks.o obj/PDFDocument.o obj/PDFDocks.o obj/FindDialog.o obj/PrefsDialog.o obj/TemplateDialog.o obj/HardWrapDialog.o obj/ConfirmDelete.o obj/synctex_parser.o obj/synctex_parser_utils.o obj/moc_TWApp.o obj/moc_TWUtils.o obj/moc_TeXDocument.o obj/moc_CompletingEdit.o obj/moc_TeXHighlighter.o obj/moc_TeXDocks.o obj/moc_PDFDocument.o obj/moc_PDFDocks.o obj/moc_FindDialog.o obj/moc_PrefsDialog.o obj/moc_TemplateDialog.o obj/moc_HardWrapDialog.o obj/moc_ConfirmDelete.o obj/qrc_resources.o obj/qrc_resfiles.o-L/usr/lib -lhunspell-1.2 -lpoppler-qt4 -ldbus-1 -lrt -lQtDBus -lQtXml -lQtGui -lQtCore -lpthread /usr/bin/ld: obj/synctex_parser.o: in function synctex_scanner_free:synctex_parser.c(.text+0x1772): error: undefined reference to 'gzclose' /usr/bin/ld: obj/synctex_parser.o: in function synctex_updater_free:synctex_parser.c(.text+0x1aa7): error: undefined reference to 'gzclose' /usr/bin/ld: obj/synctex_parser.o: in function __synctex_open:synctex_parser.c(.text+0x37fc): error: undefined reference to 'gzopen' /usr/bin/ld: obj/synctex_parser.o: in function __synctex_open:synctex_parser.c(.text+0x3815): error: undefined reference to 'gzclose' /usr/bin/ld: obj/synctex_parser.o: in function __synctex_open:synctex_parser.c(.text+0x3850): error: undefined reference to 'gzopen' /usr/bin/ld: obj/synctex_parser.o: in function __synctex_open:synctex_parser.c(.text+0x3891): error: undefined reference to 'gzopen' /usr/bin/ld: obj/synctex_parser.o: in function __synctex_open:synctex_parser.c(.text+0x3971): error: undefined reference to 'gzopen' /usr/bin/ld: obj/synctex_parser.o: in function synctex_updater_new_with_output_file:synctex_parser.c(.text+0x3c2c): error: undefined reference to 'gzclose' /usr/bin/ld: obj/synctex_parser.o: in function synctex_updater_new_with_output_file:synctex_parser.c(.text+0x3c73): error: undefined reference to 'gzprintf' /usr/bin/ld: obj/synctex_parser.o: in function _synctex_buffer_get_available_size:synctex_parser.c(.text+0x3d93): error: undefined reference to 'gzread' /usr/bin/ld: obj/synctex_parser.o: in function _synctex_buffer_get_available_size:synctex_parser.c(.text+0x3e3b): error: undefined reference to 'gzerror' /usr/bin/ld: obj/synctex_parser.o: in function _synctex_match_string:synctex_parser.c(.text+0x4226): error: undefined reference to 'gztell' /usr/bin/ld: obj/synctex_parser.o: in function _synctex_match_string:synctex_parser.c(.text+0x42bc): error: undefined reference to 'gzseek' collect2: ld returned 1 exit status make[1]: *** [texworks] Error 1 ---End Message--- ---BeginMessage--- Version: 0.5~svn843 On Tue, 17 Nov 2009 01:55:06 +0100, Peter Fritzsche wrote: Source: texworks Version: 0.2.3-2 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking I tried to build the package 1) adding --no-add-neede (on real system) 2) with binutils-gold (on a system in VirtualBox) and found no problem with 0.5~svn843. So I believe this was fixed already and close this. If I misunderstand something, please reopen this bug. Thanks for your contribution. Best regards,
Bug#631299: dpkg: upgrade to multiarch packages removed locally diverted files
Hi, On Wed, 22 Jun 2011, Daniel Stone wrote: Hmm. Seems plausible, but I went through quite a few libX11 uploads without losing my diversion: I would've noticed quite quickly, as the failure mode (which prompted the xkbcomp 1.2.2 and 1.2.3 releases) with my local XKB dataset and any distribution-shipped libX11 involved my entire keyboard doing nothing at all under X. Would you notice it instantly or only when you restart X? Do you have any backups of the /var/lib/dpkg/diversions file? Unfortunately not, I'm afraid. Is there any more information I can provide? If you can't give us a hint on how they might have disappeared from /var/lib/dpkg/diversions, there's not much we can do. dpkg itself when dealing with upgrades only uses /var/lib/dpkg/diversions in a read-only mode and there's no way a simple package upgrade would have resulted in the loss of those entries. Is there anything else that uses dpkg-divert and that could have resulted in this behaviour ? Maybe look around in /var/lib/dpkg/info/* for maintainer scripts (of local packages?) which could have some weird usage of dpkg-divert ? How did you put in place all your diversions, do you have script for this? Maybe it did not work as you thought it did. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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: reassign 631347 src:php5 Bug #631347 [php5] CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash Bug reassigned from package 'php5' to 'src:php5'. forcemerge 631286 631347 Bug#631286: CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash Bug#631347: CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash Forcibly Merged 631286 631347. thank you Stopping processing here. Please contact me if you need assistance. -- 631286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631286 631347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555579: marked as done (FTBFS with binutils-gold)
Your message dated Thu, 23 Jun 2011 15:27:29 +0900 (JST) with message-id 20110623.152729.492310766.ko...@pm.tokushima-u.ac.jp and subject line Re: Bug#79: #79 FTBFS with binutils-gold has caused the Debian Bug report #79, regarding FTBFS with binutils-gold 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.) -- 79: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=79 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: lynx-cur Version: 2.8.8dev.1-1 Severity: minor User: peter.fritzs...@gmx.de Usertags: no-add-needed Tried to build your package and it fails to build with GNU binutils-gold. The important difference is that --no-add-needed is the default behavior of of GNU binutils-gold. Please provide all needed libraries to the linker when building your executables. More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking Linking and creating Lynx executable gcc -DHAVE_CONFIG_H -DLOCALEDIR=\/usr/share/locale\ -I. -I.. -Ichrtrans -I./chrtrans -I.. -I../src -I.././WWW/Library/Implementation-D_GNU_SOURCE -DLINUX -I/usr/include/ncursesw -I/usr/lib -O2 -o lynx.cur LYebcdic.o LYClean.o LYShowInfo.o LYEdit.o LYStrings.o LYMail.o HTAlert.o GridText.o LYGetFile.o LYMain.o LYMainLoop.o LYCurses.o LYBookmark.o LYmktime.o LYUtils.o LYOptions.o LYReadCFG.o LYSearch.o LYHistory.o LYForms.o LYPrint.o LYrcFile.o LYDownload.o LYNews.o LYKeymap.o HTML.o HTFWriter.o HTInit.o DefaultStyle.o LYUpload.o LYLeaks.o LYexit.o LYJump.o LYList.o LYCgi.o LYTraversal.o LYEditmap.o LYCharSets.o LYCharUtils.o LYMap.o LYCookie.o LYStyle.o LYHash.o LYPrettySrc.o TRSTable.o parsdate.o UCdomap.o UCAux.o UCAuto.o tidy_tls.o LYExtern.o LYLocal.o .././WWW/Library/Implementation/libwww.a -lz -L/usr/lib -lncursesw -lgnutls -lcrypt -lbsd /usr/bin/ld: tidy_tls.o: in function RAND_bytes:tidy_tls.c(.text+0xb2d): error: undefined reference to 'gcry_randomize' collect2: ld returned 1 exit status make[2]: *** [lynx.cur] Error 1 ---End Message--- ---BeginMessage--- I built the package with binutils-gold (on a system in VirtualBox) and found no problem anymore. It seems generated makefile used -lgcrypt now and it worked fine for me. So I close this. If I misunderstand something, please reopen this. Thanks. Best regards, 2011-6-23(Thu) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima ---End Message---
Bug#555579: #555579 FTBFS with binutils-gold
I built the package with binutils-gold (on a system in VirtualBox) and found no problem anymore. It seems generated makefile used -lgcrypt now and it worked fine for me. So I close this. If I misunderstand something, please reopen this. Thanks. Best regards, 2011-6-23(Thu) -- Debian Developer - much more I18N of Debian Atsuhito Kohda kohda AT debian.org Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630864: rheolef and freefem++: error when trying to install together
Hi, Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/bamg Could you consider to create some specific debian package(s) for the bamg mesh generator (bin lib) ? Then, both freefem++ rheolef could depend on ? Notice that rheolef depends only upon the binary /usr/bin/bamg Pierre Saramito Maintainer for rheolef -- pierre.saram...@imag.fr Directeur de Recherche CNRS Laboratoire Jean Kuntzmann, Grenoble, France http://www-ljk.imag.fr/membres/Pierre.Saramito -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630864: marked as done (rheolef and freefem++: error when trying to install together)
Your message dated Thu, 23 Jun 2011 08:47:35 + with message-id e1qzfzx-0007sn...@franck.debian.org and subject line Bug#630864: fixed in freefem++ 3.13-2 has caused the Debian Bug report #630864, regarding rheolef and freefem++: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 630864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: freefem++,rheolef Version: freefem++/3.13-1 Version: rheolef/5.93-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2011-06-18 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! multiarch-support gcc-4.6-base libgcc1 libstdc++6 libdrm2 libquadmath0 libgfortran3 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libxfixes3 libxdamage1 libxext6 libxxf86vm1 libgl1-mesa-glx libglu1-mesa libxi6 freeglut3 libamd2.2.0 libblas3gf liblapack3gf libibverbs1 libnuma1 libtorque2 libopenmpi1.3 libarpack2 libumfpack5.4.0 libxpm4 freefem++ librheolef1 rheolef Extracting templates from packages: 90% Extracting templates from packages: 100% Preconfiguring packages ... Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package multiarch-support. (Reading database ... 9216 files and directories currently installed.) Unpacking multiarch-support (from .../multiarch-support_2.13-7_amd64.deb) ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up multiarch-support (2.13-7) ... Can not write log, openpty() failed (/dev/pts not mounted?) (Reading database ... 9220 files and directories currently installed.) Preparing to replace gcc-4.6-base 4.6.0-11 (using .../gcc-4.6-base_4.6.0-14_amd64.deb) ... Unpacking replacement gcc-4.6-base ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up gcc-4.6-base (4.6.0-14) ... Can not write log, openpty() failed (/dev/pts not mounted?) (Reading database ... 9218 files and directories currently installed.) Preparing to replace libgcc1 1:4.6.0-11 (using .../libgcc1_1%3a4.6.0-14_amd64.deb) ... Unpacking replacement libgcc1 ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up libgcc1 (1:4.6.0-14) ... Can not write log, openpty() failed (/dev/pts not mounted?) (Reading database ... 9218 files and directories currently installed.) Preparing to replace libstdc++6 4.6.0-11 (using .../libstdc++6_4.6.0-14_amd64.deb) ... Unpacking replacement libstdc++6 ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up libstdc++6 (4.6.0-14) ... Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libdrm2. (Reading database ... 9218 files and directories currently installed.) Unpacking libdrm2 (from .../libdrm2_2.4.25-3_amd64.deb) ... Selecting previously deselected package libquadmath0. Unpacking libquadmath0 (from .../libquadmath0_4.6.0-14_amd64.deb) ... Selecting previously deselected package libgfortran3. Unpacking libgfortran3 (from .../libgfortran3_4.6.0-14_amd64.deb) ... Selecting previously deselected package libxau6. Unpacking libxau6 (from .../libxau6_1%3a1.0.6-3_amd64.deb) ... Selecting previously deselected package libxdmcp6. Unpacking libxdmcp6 (from .../libxdmcp6_1%3a1.1.0-3_amd64.deb) ... Selecting previously deselected package libxcb1. Unpacking libxcb1 (from .../libxcb1_1.7-3_amd64.deb) ... Selecting previously deselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.4.3-2_all.deb) ... Selecting previously deselected package libx11-6. Unpacking libx11-6 (from .../libx11-6_2%3a1.4.3-2_amd64.deb) ... Selecting previously deselected package libxfixes3. Unpacking libxfixes3 (from .../libxfixes3_1%3a5.0-4_amd64.deb) ... Selecting previously deselected package libxdamage1. Unpacking libxdamage1 (from .../libxdamage1_1%3a1.1.3-2_amd64.deb) ... Selecting previously deselected package libxext6. Unpacking libxext6 (from .../libxext6_2%3a1.3.0-3_amd64.deb) ... Selecting previously deselected package libxxf86vm1. Unpacking libxxf86vm1 (from .../libxxf86vm1_1%3a1.1.1-2_amd64.deb) ... Selecting previously deselected package libgl1-mesa-glx. Unpacking libgl1-mesa-glx (from .../libgl1-mesa-glx_7.10.3-2_amd64.deb) ... Selecting previously deselected package libglu1-mesa.
Bug#618068: updated patch
Hello again,
attached is an updated patch to fix this FTBFS. The original patch was
flawed because it added the libraries to LDFLAGS, which is wrong. Now
the libraries are in LDADD which is appended after the objects/sources.
This also fixes a bug when building with ld --as-needed, see
https://bugs.launchpad.net/ubuntu/+source/audtty/+bug/765955
Thanks for considering the patch.
Cheers,
Andreas
Description: Fix FTBFS due to indirect linking
Author: Andreas Moog am...@ubuntu.com
Bug-Ubuntu: https://bugs.launchpad.net/749143
Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618068
Index: audtty/Makefile.in
===
--- audtty.orig/Makefile.in 2011-06-23 09:35:45.224190999 +
+++ audtty/Makefile.in 2011-06-23 09:36:31.844191736 +
@@ -8,6 +8,7 @@
AUDACIOUS_CFLAGS=@AUDACIOUS_CFLAGS@ -I/usr/include/dbus-1.0
+LDADD=-ldbus-glib-1 -lncursesw -laudclient
SOURCES=main.c curses_printf.c playlist.c playlist_jump.c playlist_addurl.c settings.c connect.c browse.c playlist_create.c
BINS=$(SOURCES:.c=.o)
@@ -17,7 +18,7 @@
all: audtty
audtty: ${BINS}
- cc -g -O2 -g2 -Wall -Werror -lncursesw -laudclient ${LDFLAGS} -o audtty $(BINS)
+ cc -g -O2 -g2 -Wall -Werror ${LDFLAGS} -o audtty $(BINS) $(LDADD)
.c.o:
cc -g -Wall ${AUDACIOUS_CFLAGS} ${CFLAGS} -o $@ -c $
signature.asc
Description: OpenPGP digital signature
Bug#630777: depends on iputils-ping which is not available on kfreebsd
inetutils-ping should be a better replacement. The package I've rebuilded is downloadable here: http://dl.dropbox.com/u/630394/backuppc_3.1.0-9_all.deb -- Giovanni Toraldo http://www.libersoft.it/ signature.asc Description: OpenPGP digital signature
Bug#629815: No rule to make target `/usr/lib/libdl.so'
Hi again, to give an update to this problem: On Fri, Jun 10, 2011 at 11:37:00AM +0200, Mathieu Malaterre wrote: On Thu, Jun 9, 2011 at 11:27 PM, Andreas Tille andr...@an3as.eu wrote: On Thu, Jun 09, 2011 at 01:02:56PM +0200, Sven Joachim wrote: The problem is that libdl.so has been moved to the multiarch paths in libc6-dev 2.13-5. You must upgrade cmake to 2.8.4+dfsg.1-3, have you done that already? I'm building an unstable pbuilder chroot. It is using the cmake version you are mentioning: $ grep cmake.2\.8 ginkgocadx_2.4.1.1-1_amd64.build Unpacking cmake (from .../cmake_2.8.4+dfsg.1-3_amd64.deb) ... Might be worth retrying with cmake 2.8.4+dfsg.1-4, currently in incoming. It has a different multiarch implementation. $ grep cmake.2\.8 ginkgocadx_2.4.1.1-1_amd64.build Unpacking cmake (from .../cmake_2.8.4+dfsg.1-4_amd64.deb) ... I: new cache content cmake_2.8.4+dfsg.1-4_amd64.deb added No change. :-(( Any further hint? I think the issue is being worked on at the moment upstream: http://public.kitware.com/Bug/view.php?id=12037#c26801 ... Modestas Vainius wrote: 2) Will those patches be part of 2.8.5? I want to emphasize that released Ubuntu 11.04 (natty) already has this multiarch enabled so upstream cmake up to and including 2.8.4 is basically unusable on those systems. That's because libc6 package is multiarch enabled and e.g. vanilla cmake 2.8.4 is not even able to set CMAKE_DL_LIBS properly. ... IMHO cmake (current git master) does not handle this new libc6 layout for multiarch support I tried to rebuild gofigure2 (which is affected by #629815) now I do not get the No rule to make target `/usr/lib/libdl.so', needed by `lib/libvtkRenderingAddOn2.so.0.8' any more but rather No rule to make target `/usr/lib/libXt.so', needed by `lib/libPoissonReconstruction.so.0.8' and thus I assume my action to reopen #630167 (which is unfortunately not properly documented in the bug log) was not the right thing to do. It rather seems that certain library packages need to be adapted to the multiarch build and libc6-dev *now* works together with cmake but libxt-dev does not. Similarly I can confirm that when trying to build ginkgocadx I do not run any more in the missing libdl.so but rather into No rule to make target `/lib/libwrap.so.0', needed by `src/cadxcore/libCADxCore.so.2.4.1.1' which somehow smells like libwrap0 is guilty for the problem. I admit that this multiarch stuff is above my horizon and I hope that somebody might be able to clarify what might be the correct way of action now. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631373: (no subject)
Package: vim-gtk Version: 2:7.3.154+hg~74503f6ee649-2+b1 Severity: grave Justification: renders package unusable Following an upgrade in Sid today I get this with gvim: arcadia:~:$ gvim gvim: symbol lookup error: /usr/lib/libcairo.so.2: undefined symbol: FT_GlyphSlot_Embolden I realise this is probably a bug in libcairo.so.2 but I can't identify which package is causing it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (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 Versions of packages vim-gtk depends on: ii libacl1 2.2.49-5 Access control list shared library ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libgdk-pi 2.23.3-3 GDK Pixbuf library ii libglib2. 2.28.6-1 The GLib library of C routines ii libgpm2 1.20.4-3.4 General Purpose Mouse - shared lib ii libgtk2.0 2.24.4-3 The GTK+ graphical user interface ii libice6 2:1.0.7-2 X11 Inter-Client Exchange library ii liblua5.1 5.1.4-5Simple, extensible, embeddable pro ii libncurse 5.9-1 shared libraries for terminal hand ii libpango1 1.28.3-6 Layout and rendering of internatio ii libperl5. 5.12.3-7+b1shared Perl library ii libpython 2.6.7-1Shared Python runtime library (ver ii libruby1. 1.8.7.334-5Libraries necessary to run Ruby 1. ii libselinu 2.0.98-1.1 SELinux runtime shared libraries ii libsm62:1.2.0-2 X11 Session Management library ii libx11-6 2:1.4.3-2 X11 client-side library ii libxt61:1.1.1-2 X11 toolkit intrinsics library ii tcl8.58.5.9-2Tcl (the Tool Command Language) v8 ii vim-commo 2:7.3.154+hg~74503f6ee649-2+b1 Vi IMproved - Common files ii vim-gui-c 2:7.3.154+hg~74503f6ee649-2Vi IMproved - Common GUI files ii vim-runti 2:7.3.154+hg~74503f6ee649-2Vi IMproved - Runtime files vim-gtk recommends no packages. Versions of packages vim-gtk suggests: pn cscope none (no description available) ii gnome-icon-t 3.0.0-3 GNOME Desktop icon theme ii ttf-dejavu 2.33-1 Metapackage to pull in ttf-dejavu- ii vim-doc 2:7.3.154+hg~74503f6ee649-2 Vi IMproved - HTML documentation -- 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#625593: (no subject)
Cc Bcc: cont...@bugs.debian.org Subject: Re: Bug#625593: Intention to NMU for imagemagick library transition Reply-To: In-Reply-To: banlktimgc_bgf4skfelgyhza1jdb4r_...@mail.gmail.com reopen 625593 found 625593 0.31.1-15.1 thanks On 0, Vincent Fourmond fourm...@debian.org wrote: --- autotrace-0.31.1/debian/control +++ autotrace-0.31.1/debian/control @@ -3,7 +3,8 @@ Priority: optional Maintainer: Tony Palma xbyt...@gmail.com Build-Depends: debhelper (= 5), autotools-dev, pkg-config, - libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagick9-dev + libpng12-dev, libpstoedit-dev (= 3.42-1.1), + libmagickcore-dev This is not enough to fix the problem since libautotrace-dev still depends on libmagick9-dev. I'm considering removing this package temporarily from testing if not fixed during the next couple of days. If you intend to NMU it, please upload it without delay in order to to get ready to migrate sooner. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631299: dpkg: upgrade to multiarch packages removed locally diverted files
Hi, On Thu, Jun 23, 2011 at 08:24:07AM +0200, Raphael Hertzog wrote: On Wed, 22 Jun 2011, Daniel Stone wrote: Hmm. Seems plausible, but I went through quite a few libX11 uploads without losing my diversion: I would've noticed quite quickly, as the failure mode (which prompted the xkbcomp 1.2.2 and 1.2.3 releases) with my local XKB dataset and any distribution-shipped libX11 involved my entire keyboard doing nothing at all under X. Would you notice it instantly or only when you restart X? Only when I restart, but I do this twice a day at a bare minimum (as suspend/resume is broken), and usually quite a few times more than that, as I do all my X development on my live running server. I usually dist-upgrade every couple of weeks or so, so I'd be pretty stunned if I just managed not to manage it until multiarch came along. Do you have any backups of the /var/lib/dpkg/diversions file? Unfortunately not, I'm afraid. Is there any more information I can provide? If you can't give us a hint on how they might have disappeared from /var/lib/dpkg/diversions, there's not much we can do. Hmm. dpkg itself when dealing with upgrades only uses /var/lib/dpkg/diversions in a read-only mode and there's no way a simple package upgrade would have resulted in the loss of those entries. Sounds reasonable. Is there anything else that uses dpkg-divert and that could have resulted in this behaviour ? Maybe look around in /var/lib/dpkg/info/* for maintainer scripts (of local packages?) which could have some weird usage of dpkg-divert ? I can't see anything obvious, no. I don't have any local packages; if I did, I'd just have packaged my self-built X libraries with an epoch, rather than diversions. How did you put in place all your diversions, do you have script for this? Maybe it did not work as you thought it did. By hand: for i in /usr/lib/libX11.*; do sudo dpkg-divert --add $i; done Seems to have worked just fine since May 2010, and I've not touched it since then. It's a shame there's not more information I can give you. Cheers, Daniel signature.asc Description: Digital signature
Bug#625593: (no subject)
On 23/06/2011 14:28, Mehdi Dogguy wrote:
Cc
Bcc: cont...@bugs.debian.org
Subject: Re: Bug#625593: Intention to NMU for imagemagick library transition
Reply-To:
In-Reply-To: banlktimgc_bgf4skfelgyhza1jdb4r_...@mail.gmail.com
Well done, mutt!
reopen 625593
found 625593 0.31.1-15.1
thanks
On 0, Vincent Fourmond fourm...@debian.org wrote:
--- autotrace-0.31.1/debian/control
+++ autotrace-0.31.1/debian/control
@@ -3,7 +3,8 @@
Priority: optional
Maintainer: Tony Palma xbyt...@gmail.com
Build-Depends: debhelper (= 5), autotools-dev, pkg-config,
- libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagick9-dev
+ libpng12-dev, libpstoedit-dev (= 3.42-1.1),
+ libmagickcore-dev
This is not enough to fix the problem since libautotrace-dev still
depends on libmagick9-dev.
I'm considering removing this package temporarily from testing if not
fixed during the next couple of days. If you intend to NMU it, please
upload it without delay in order to to get ready to migrate sooner.
Regards,
--
Mehdi Dogguy مهدي الدڤي
mehdi@{dogguy.org,debian.org}
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 625584 serious Bug #625584 [zbar] transition: libmagick4 Severity set to 'serious' from 'normal' found 625584 0.10+doc-6 Bug #625584 [zbar] transition: libmagick4 There is no source info for the package 'zbar' at version '0.10+doc-6' with architecture '' Unable to make a source version for version '0.10+doc-6' Bug Marked as found in versions 0.10+doc-6. thanks Stopping processing here. Please contact me if you need assistance. -- 625584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 625593
Processing commands for cont...@bugs.debian.org:
reopen 625593
Bug #625593 {Done: Vincent Fourmond fourm...@debian.org} [src:autotrace]
transition: libmagick4 and old depend on libmagick9-dev
Bug #629770 {Done: Vincent Fourmond fourm...@debian.org} [src:autotrace]
autotrace: FTBFS: build-dependency not installable: libmagick9-dev
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
625593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 625593 in 0.31.1-15.1
Processing commands for cont...@bugs.debian.org: found 625593 0.31.1-15.1 Bug #625593 [src:autotrace] transition: libmagick4 and old depend on libmagick9-dev Bug #629770 [src:autotrace] autotrace: FTBFS: build-dependency not installable: libmagick9-dev Bug Marked as found in versions autotrace/0.31.1-15.1. Bug Marked as found in versions autotrace/0.31.1-15.1. thanks Stopping processing here. Please contact me if you need assistance. -- 625593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625584: (no subject)
Mehdi Dogguy me...@dogguy.org wrote: In order to get this bug fixed, you have to make libzbar-dev depend on libmagick++9-dev instead of libmagick++-dev. arg, the reverse of course! (i.e. s/libmagick++9-dev/libmagick++-dev/) Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629776: RFS: UPDATE: geda-xgsch2pcb 0.1.3-2
Please sponsor the updated package geda-xgsch2pcb. It closes bug: 629776 The latest entry in the Debian changelog is: geda-xgsch2pcb (0.1.3-2) unstable; urgency=low * debian/control: + Updated my email address + Added DMUA after sponsors consent (http://lists.alioth.debian.org/pipermail/pkg-electronics-devel/2010-April/001827.html) + Bumped Standards-Version to 3.9.2 + Depend/Build-Dep on python-gobject | python-gtk2 (2.10) to fix FTBFS on wheezy (Closes: #629776) * Removed debian/pyversions * Bumped compat level to 8 * Converted to 3.0 (quilt) source format. As required, I tested the package against unstable's version of lintian and it has the following lintian issues: I: geda-xgsch2pcb: desktop-entry-contains-encoding-key usr/share/applications/geda-xgsch2pcb.desktop:3 Encoding W: geda-xgsch2pcb: desktop-entry-lacks-main-category usr/share/applications/geda-xgsch2pcb.desktop The package can be found on Git: ssh://git.debian.org/git/pkg-electronics/geda-xgsch2pcb.git Kind regards, -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: Digital signature
Bug#631299: dpkg: upgrade to multiarch packages removed locally diverted files
tag 631299 + unreproducible severity 631299 important thanks On Thu, 23 Jun 2011, Daniel Stone wrote: By hand: for i in /usr/lib/libX11.*; do sudo dpkg-divert --add $i; done Hum, this doesn't rename the existing file. So when you install your custom lib, you overwrite the packaged files. The diverted file are only installed on the next package upgrade. Seems to have worked just fine since May 2010, and I've not touched it since then. It's a shame there's not more information I can give you. Hum I remember Steve Langasek saying that diverting libraries in the same directory causes troubles because ldconfig/ld.so doesn't care of the extension and might be confused by seeing the same SONAME twice. I don't see how it could have resulted in loosing files and/or diversions but maybe someone else can. Maybe we should also add some sort logging to dpkg-divert just like we added logging to update-alternatives. This would at least give some supplementary information for cases like this one. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- 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#631299: dpkg: upgrade to multiarch packages removed locally diverted files
Processing commands for cont...@bugs.debian.org: tag 631299 + unreproducible Bug #631299 [dpkg] dpkg: upgrade to multiarch packages removed locally diverted files Added tag(s) unreproducible. severity 631299 important Bug #631299 [dpkg] dpkg: upgrade to multiarch packages removed locally diverted files Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 631299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622995: Patches welcome
# Drop pending since the patches don't quite work tag 622995 - pending + help tag 622996 - pending + help # Kobby (995) needs libqinfinity (996) to be fixed first block 622995 by 622996 thanks Hi, Seeing that both libqinfinity and kobby are uninstallable, I asked Phil Kern to remove them from testing. Patches are welcome for both and will duly be applied. Phil has provided most of the work, all that appears to be left is to figure out why kobby/libqinfinity don't send changes to the server. Kind regards, Ryan -- |_)|_/ Ryan Kavanagh | GnuPG key | \| \ http://ryanak.ca/ | 4A11C97A (Transitioning from E95EDDC9) () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments signature.asc Description: Digital signature
Processed: Patches welcome
Processing commands for cont...@bugs.debian.org: # Drop pending since the patches don't quite work tag 622995 - pending + help Bug #622995 [kobby] Build-Depends on missing libinfinity-0.4-dev Ignoring request to alter tags of bug #622995 to the same tags previously set Bug #622995 [kobby] Build-Depends on missing libinfinity-0.4-dev Added tag(s) help. tag 622996 - pending + help Bug #622996 [libqinfinity] Build-Depends on missing libinfinity-0.4-dev Removed tag(s) pending. Bug #622996 [libqinfinity] Build-Depends on missing libinfinity-0.4-dev Added tag(s) help. # Kobby (995) needs libqinfinity (996) to be fixed first block 622995 by 622996 Bug #622995 [kobby] Build-Depends on missing libinfinity-0.4-dev Was not blocked by any bugs. Added blocking bug(s) of 622995: 622996 thanks Stopping processing here. Please contact me if you need assistance. -- 622995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622995 622996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628281: libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found
reassign 628281 vala-0.12 0.12.0-4 affects 628281 + libchamplain thanks Hi, It seems that gobject-introspection has changed the way gunichar is handled and thus causing this FTBFS. Please update to 0.12.1 to fix this. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found
Processing commands for cont...@bugs.debian.org: reassign 628281 vala-0.12 0.12.0-4 Bug #628281 [src:libchamplain] libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found Bug reassigned from package 'src:libchamplain' to 'vala-0.12'. Bug No longer marked as found in versions libchamplain/0.10.0-2. Bug #628281 [vala-0.12] libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found There is no source info for the package 'vala-0.12' at version '0.12.0-4' with architecture '' Unable to make a source version for version '0.12.0-4' Bug Marked as found in versions 0.12.0-4. affects 628281 + libchamplain Bug #628281 [vala-0.12] libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found Added indication that 628281 affects libchamplain thanks Stopping processing here. Please contact me if you need assistance. -- 628281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630392: marked as done (empathy: Dependencies failed, libedataserver-1.2.so.13 libebook-1.2.so.9)
Your message dated Thu, 23 Jun 2011 16:33:07 +0200 with message-id 20110623163307.59836...@eldamar.bigon.be and subject line Re: empathy: Dependencies failed, libedataserver-1.2.so.13 libebook-1.2.so.9 has caused the Debian Bug report #630392, regarding empathy: Dependencies failed, libedataserver-1.2.so.13 libebook-1.2.so.9 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.) -- 630392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: empathy Version: 2.30.3 Severity: grave Tags: wheezy Justification: renders package unusable I just upgraded from squeeze the whole system, but this dependency hasn't been fixed. I had installed libebook-1.2.so.10 instead of libebook-1.2.so.9, and libedataserver-1.2.so.14 instead of libedataserver-1.2.so.13. I solved it simply creating a link called with the carrect name to the library already installed. For now it works... -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Hi, Looks like a binNMU has been schedule and now empathy is depending on the correct version of libebook and libedataserver. Closing this bug then. Cheers Laurent Bigonville ---End Message---
Processed: tagging 630392
Processing commands for cont...@bugs.debian.org:
tags 630392 - wheezy
Bug #630392 {Done: Laurent Bigonville bi...@debian.org} [empathy] empathy:
Dependencies failed, libedataserver-1.2.so.13 libebook-1.2.so.9
Removed tag(s) wheezy.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
630392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628245: aptsh: patch for the issue
Package: aptsh Version: 0.0.7+nmu1 Followup-For: Bug #628245 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu oneiric ubuntu-patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 *** /tmp/tmpb5Yt6Z In Ubuntu, the attached patch was applied to achieve the following: src/Makefile.am/in: remove -avoid-version option which isn't used anymore. Thanks for considering the patch. - -- System Information: Debian Release: wheezy/sid APT prefers oneiric APT policy: (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-999-generic (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJOA16yAAoJEGHzRCZ03mYkiPkQAKEC+OHfPOqAt9SccSOaez8K NjvN/74yFxYRq10WQEorvER4xGcL4DCXB8xZnA6ntV88a9/tkeWxjxqomnU7iOS0 RVaY4ShWcCIavdZL6WoDgpktOqYWZ7440fjDpb/A/K7NuJIaFYwqwTwRdCvVZRVd RsSpSkwS0XhQ9RQH7EsHq2gwsgPpTc3iSJXPWmBZxdcINiCyfr/pCLy/5xx/cSk+ vjFEi/dTCNHIPk3EoO/IdHRA1/mRzRshJi49p86iqv66NBSzz5NqFF8u5ifSNBfy 4uW9S+Ww3slzHl4qwvMPdR9Ge+j2su1ovWgtIWO4ZB2uRiiJBB44nxzTsJOJe8VR g8ATHNzbApWLVJbvEX1cQ1WDutk+SFGlp5GIWn4Pru9no1JcsOkyvJbcWqXzDz/c oorhTIraq8W73406Wg6oF8mbNP04205oZx6ahf+41sQwUC7hfpgl7gxU+MA6rlBO ELvGOpVvQ/W9tLewPTvcdSRM5AMwwjFbPla5rrL/ub3N6UqZc+Q3BDbAkM9BAZYk 64qVP6HcX3EGfdAWiQvjzAZrsXl8tMhhi4Jr81LqR502vAd8aIuywqjHAqAHw0nO PRKRSZe0oYqrLVu3OUT2AqO4BmVpmZJDahaD8gJr+I/diiDv/r1R7koNzv/e0wAR rpEKDQVkG94uBzPub3l+ =3ha4 -END PGP SIGNATURE- === modified file 'src/Makefile.am' --- src/Makefile.am 2008-03-15 21:44:10 + +++ src/Makefile.am 2011-06-23 15:37:15 + @@ -42,8 +42,7 @@ main.cc\ main.h -aptsh_LDFLAGS = \ - -avoid-version +aptsh_LDFLAGS = aptsh_LDADD = \ -lreadline -lapt-pkg === modified file 'src/Makefile.in' --- src/Makefile.in 2008-03-15 21:44:10 + +++ src/Makefile.in 2011-06-23 15:37:24 + @@ -206,8 +206,7 @@ main.cc\ main.h -aptsh_LDFLAGS = \ - -avoid-version +aptsh_LDFLAGS = aptsh_LDADD = \ -lreadline -lapt-pkg
Processed: tagging 628245
Processing commands for cont...@bugs.debian.org: reassign 628245 src:aptsh Bug #628245 [src:aptsh] aptsh: FTBFS: g++: error: unrecognized option '-avoid-version' Ignoring request to reassign bug #628245 to the same package tags 628245 + patch upstream Bug #628245 [src:aptsh] aptsh: FTBFS: g++: error: unrecognized option '-avoid-version' Added tag(s) upstream and patch. user ubuntu-de...@lists.ubuntu.com Setting user to ubuntu-de...@lists.ubuntu.com (was am...@ubuntu.com). usertags 628245 origin-ubuntu oneiric ubuntu-patch Bug#628245: aptsh: FTBFS: g++: error: unrecognized option '-avoid-version' There were no usertags set. Usertags are now: ubuntu-patch origin-ubuntu oneiric. thanks Stopping processing here. Please contact me if you need assistance. -- 628245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package bzr
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package bzr # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #630913 (http://bugs.debian.org/630913) # * https://bugs.launchpad.net/bugs/799212 # * remote status changed: (?) - Fix-Released # * closed upstream tags 630913 + fixed-upstream Bug #630913 [bzr] fails to commit if commiter name's contains non-ascii characters Added tag(s) fixed-upstream. usertags 630913 + status-Fix-Released Bug#630913: fails to commit if commiter name's contains non-ascii characters There were no usertags set. Usertags are now: status-Fix-Released. thanks Stopping processing here. Please contact me if you need assistance. -- 630913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630592: marked as done (fglrx-glx: recent multiarch changes break fglrx)
Your message dated Thu, 23 Jun 2011 17:18:18 + with message-id e1qznxm-0006uc...@franck.debian.org and subject line Bug#630592: fixed in fglrx-driver 1:11-6-1 has caused the Debian Bug report #630592, regarding fglrx-glx: recent multiarch changes break fglrx 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.) -- 630592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fglrx-glx Version: 1:11-4-2 Severity: important Tags: wheezy Hello, The recent multiarch changes with Mesa (http://blog.mraw.org/2011/06/14/mesa_a_disturbance_in_the_Force/) broke also fglrx. On my system, libGL.so moved to /usr/lib/i386-linux-gnu, so the libGL supplied by fglrx did not get used anymore, so glxinfo gave this error: Error: couldn't find RGB GLX visual or fbconfig I did confirm this issue and worked around it by making couple symlinks back to /usr/lib. -- Package-specific info: VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Barts XT [ATI Radeon HD 6800 Series] DRM and fglrx Informations from dmesg: [1.236856] Linux agpgart interface v0.103 [ 17.000637] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel. [ 17.078322] [fglrx] Maximum main memory to use for locked dma buffers: 3856 MBytes. [ 17.078420] [fglrx] vendor: 1002 device: 6738 count: 1 [ 17.078809] [fglrx] ioport: bar 4, base 0xb000, size: 0x100 [ 17.079155] [fglrx] Kernel PAT support is enabled [ 17.079173] [fglrx] module loaded - fglrx 8.84.5 [Apr 5 2011] with 1 minors [ 27.871351] Modules linked in: powernow_k8 mperf cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace joydev fglrx(P) snd_emu10k1_synth snd_emux_synth snd_ice1724 snd_seq_virmidi snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_seq_midi_emul snd_ak4114 snd_pt2258 snd_emu10k1 snd_i2c snd_ak4113 snd_ac97_codec ac97_bus snd_util_mem snd_hwdep psmouse snd_seq_midi processor snd_rawmidi i2c_piix4 snd_seq_midi_event snd_pcm_oss snd_seq snd_mixer_oss snd_pcm i2c_core snd_seq_device asus_atk0110 k10temp parport_pc parport snd_timer emu10k1_gp serio_raw pcspkr gameport evdev snd snd_page_alloc thermal_sys soundcore button ext3 jbd mbcache dm_mod raid456 md_mod async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx usbhid hid sg sr_mod sd_mod cdrom crc_t10dif ata_generic ohci_hcd ahci libahci pata_pdc2027x pata_atiixp libata floppy firewire_ohci ehci_hcd usbcore scsi_mod r8169 firewire_core crc_itu_t mii nls_base [last unloaded: scsi_wait_scan] [ 64.519770] fglrx_pci :01:00.0: irq 43 for MSI/MSI-X [ 64.520395] [fglrx] Firegl kernel thread PID: 2442 [ 64.520482] [fglrx] Firegl kernel thread PID: 2443 [ 64.520537] [fglrx] Firegl kernel thread PID: 2444 [ 64.521003] [fglrx] IRQ 43 Enabled [ 65.618316] [fglrx:drm_parse_option] *ERROR* locked-userpages is not a valid option [ 65.618321] [fglrx] Maximum main memory to use for locked dma buffers: 3856 MBytes. [ 65.618414] [fglrx] Gart USWC size:1280 M. [ 65.618416] [fglrx] Gart cacheable size:508 M. [ 65.618421] [fglrx] Reserved FB block: Shared offset:0, size:100 [ 65.618423] [fglrx] Reserved FB block: Unshared offset:fbfd000, size:403000 [ 65.618426] [fglrx] Reserved FB block: Unshared offset:3fff4000, size:c000 [ 1163.564740] [fglrx] IRQ 43 Disabled [ 1165.767883] fglrx_pci :01:00.0: irq 43 for MSI/MSI-X [ 1165.768535] [fglrx] Firegl kernel thread PID: 6029 [ 1165.768585] [fglrx] Firegl kernel thread PID: 6030 [ 1165.768637] [fglrx] Firegl kernel thread PID: 6031 [ 1165.769064] [fglrx] IRQ 43 Enabled [ 1166.042978] [fglrx:drm_parse_option] *ERROR* locked-userpages is not a valid option [ 1166.042984] [fglrx] Maximum main memory to use for locked dma buffers: 3856 MBytes. [ 1166.043067] [fglrx] Gart USWC size:1280 M. [ 1166.043070] [fglrx] Gart cacheable size:508 M. [ 1166.043075] [fglrx] Reserved FB block: Shared offset:0, size:100 [ 1166.043077] [fglrx] Reserved FB block: Unshared offset:fbfd000, size:403000 [ 1166.043080] [fglrx] Reserved FB block: Unshared offset:3fff4000, size:c000 Xorg X server configuration file status: -rw-r--r-- 1 root root 2970 Nov 29 2010 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. #
Bug#627020: marked as done (qa.debian.org: With update of kernel 2.6.38-2, xserver-xorg-core 2:1.10.1-2, fglrx no longer works (11-4, 11-5))
Your message dated Thu, 23 Jun 2011 17:18:18 + with message-id e1qznxm-0006uc...@franck.debian.org and subject line Bug#630592: fixed in fglrx-driver 1:11-6-1 has caused the Debian Bug report #630592, regarding qa.debian.org: With update of kernel 2.6.38-2, xserver-xorg-core 2:1.10.1-2, fglrx no longer works (11-4, 11-5) 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.) -- 630592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qa.debian.org Severity: important After upgrading (yesterday, 5/15) to 2.6.38-2, xserver-xorg-core 2:1.10.1-2, fglrx no longer works. X reports only No protocol specified. I've tried the packaged fglrx (11-4-2), direct installer from ati.com of 11-4 and 11-5(DKMS fails due to kernel lock change). Also tried reverting to 2.6.32-5 kernel, un/reinstalling driver each time. Results are the same: blank/black screen, No protocol specified. I've got a Radeon HD 4250; radeon module hard-locks the display (can still ssh in and reboot, but that's about it). I.e., 'radeon' driver isn't an option. I know fglrx is binary/non-free, but would appreciate any work-arounds. -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-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 ---End Message--- ---BeginMessage--- Source: fglrx-driver Source-Version: 1:11-6-1 We believe that the bug you reported is fixed in the latest version of fglrx-driver, which is due to be installed in the Debian FTP archive: fglrx-atieventsd_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-atieventsd_11-6-1_amd64.deb fglrx-control_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-control_11-6-1_amd64.deb fglrx-driver_11-6-1.debian.tar.gz to non-free/f/fglrx-driver/fglrx-driver_11-6-1.debian.tar.gz fglrx-driver_11-6-1.dsc to non-free/f/fglrx-driver/fglrx-driver_11-6-1.dsc fglrx-driver_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-driver_11-6-1_amd64.deb fglrx-driver_11-6.orig.tar.bz2 to non-free/f/fglrx-driver/fglrx-driver_11-6.orig.tar.bz2 fglrx-glx-ia32_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-glx-ia32_11-6-1_amd64.deb fglrx-glx_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-glx_11-6-1_amd64.deb fglrx-modules-dkms_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-modules-dkms_11-6-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 630...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated fglrx-driver 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: SHA256 Format: 1.8 Date: Thu, 23 Jun 2011 18:24:12 +0200 Source: fglrx-driver Binary: fglrx-driver fglrx-glx fglrx-glx-ia32 fglrx-modules-dkms fglrx-control fglrx-atieventsd Architecture: source amd64 Version: 1:11-6-1 Distribution: experimental Urgency: high Maintainer: Fglrx packaging team pkg-fglrx-de...@lists.alioth.debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: fglrx-atieventsd - external events daemon for the non-free ATI/AMD RadeonHD display fglrx-control - control panel for the non-free ATI/AMD RadeonHD display driver fglrx-driver - non-free ATI/AMD RadeonHD display driver fglrx-glx - proprietary libGL for the non-free ATI/AMD RadeonHD display drive fglrx-glx-ia32 - proprietary libGL for the non-free ATI/AMD display driver (ia32 l fglrx-modules-dkms - dkms module source for the non-free ATI/AMD RadeonHD display driv Closes: 610022 627100 630592 Changes: fglrx-driver (1:11-6-1) experimental; urgency=high . * New upstream release. Closes: #627100 - Refresh patch 02-dkms-arch_compat.diff. * Remove old comments from maintainer scripts. * Remove debconf question about ACPI Powerstates, it is handled by fglrx itself. * Wrap control fields in debian/control. * Depend on xserver-xorg 1:7.6+7 to ensure, that a multiarch xorg is present. * Try to mess with multiarch: Closes: #630592 - Rework many packaging parts.
Bug#630728: marked as done (mesa-utils: glxgears and glxinfo does not work)
Your message dated Thu, 23 Jun 2011 17:18:18 + with message-id e1qznxm-0006uc...@franck.debian.org and subject line Bug#630592: fixed in fglrx-driver 1:11-6-1 has caused the Debian Bug report #630592, regarding mesa-utils: glxgears and glxinfo does not work 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.) -- 630592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mesa-utils Version: 8.0.1-2 Severity: grave Justification: renders package unusable When i start glxgears : Error: couldn't get an RGB, Double-buffered visual glxinfo : name of display: :0 Error: couldn't find RGB GLX visual or fbconfig -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 mesa-utils depends on: ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libgl1-mesa-glx [libgl1] 7.10.3-1 free implementation of the OpenGL ii libglew1.51.5.8-3The OpenGL Extension Wrangler - ru ii libglu1-mesa [libglu1]7.10.3-1 The OpenGL utility library (GLU) ii libx11-6 2:1.4.3-2 X11 client-side library ii libxext6 2:1.3.0-3 X11 miscellaneous extension librar mesa-utils recommends no packages. mesa-utils suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: fglrx-driver Source-Version: 1:11-6-1 We believe that the bug you reported is fixed in the latest version of fglrx-driver, which is due to be installed in the Debian FTP archive: fglrx-atieventsd_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-atieventsd_11-6-1_amd64.deb fglrx-control_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-control_11-6-1_amd64.deb fglrx-driver_11-6-1.debian.tar.gz to non-free/f/fglrx-driver/fglrx-driver_11-6-1.debian.tar.gz fglrx-driver_11-6-1.dsc to non-free/f/fglrx-driver/fglrx-driver_11-6-1.dsc fglrx-driver_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-driver_11-6-1_amd64.deb fglrx-driver_11-6.orig.tar.bz2 to non-free/f/fglrx-driver/fglrx-driver_11-6.orig.tar.bz2 fglrx-glx-ia32_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-glx-ia32_11-6-1_amd64.deb fglrx-glx_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-glx_11-6-1_amd64.deb fglrx-modules-dkms_11-6-1_amd64.deb to non-free/f/fglrx-driver/fglrx-modules-dkms_11-6-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 630...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Patrick Matthäi pmatth...@debian.org (supplier of updated fglrx-driver 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: SHA256 Format: 1.8 Date: Thu, 23 Jun 2011 18:24:12 +0200 Source: fglrx-driver Binary: fglrx-driver fglrx-glx fglrx-glx-ia32 fglrx-modules-dkms fglrx-control fglrx-atieventsd Architecture: source amd64 Version: 1:11-6-1 Distribution: experimental Urgency: high Maintainer: Fglrx packaging team pkg-fglrx-de...@lists.alioth.debian.org Changed-By: Patrick Matthäi pmatth...@debian.org Description: fglrx-atieventsd - external events daemon for the non-free ATI/AMD RadeonHD display fglrx-control - control panel for the non-free ATI/AMD RadeonHD display driver fglrx-driver - non-free ATI/AMD RadeonHD display driver fglrx-glx - proprietary libGL for the non-free ATI/AMD RadeonHD display drive fglrx-glx-ia32 - proprietary libGL for the non-free ATI/AMD display driver (ia32 l fglrx-modules-dkms - dkms module source for the non-free ATI/AMD RadeonHD display driv Closes: 610022 627100 630592 Changes: fglrx-driver (1:11-6-1) experimental; urgency=high . * New upstream release. Closes: #627100 - Refresh patch 02-dkms-arch_compat.diff. * Remove old comments from maintainer scripts. * Remove debconf question about ACPI Powerstates, it is handled by fglrx itself. * Wrap control fields in debian/control. * Depend on xserver-xorg 1:7.6+7 to ensure, that a
Bug#631050: chmsee: FTBFS against iceweasel 4.0 or 5.0
chmsee 1.3.1.1 http://code.google.com/p/chmsee/downloads/detail?name=chmsee-1.3.1.1.tar.gzcan=2q= is compatible with xulrunner-2.0. Please update this package. Thanks.
Bug#631422: does not use SSL on identi.ca / ignores SSL certificates on Twitter
Package: turpial Version: 1.5.0-1 Severity: grave Tags: security Hi, Inspired by the same bug in gwibber (https://bugs.launchpad.net/gwibber/+bug/705363), heybuddy (https://bugs.launchpad.net/heybuddy/+bug/798300) and pino (http://code.google.com/p/pino-twitter/issues/detail?id=339) I checked turpial and it failed the same way :( For identi.ca HTTPS is not even used (username/password are sent as plaintext to the server). Editing api/protocols/identica/identica.py to use https://identi.ca/api as API endpoint does not help much, SSL is used but certificates aren't checked, making man in the middle attacks possible. For Twitter HTTPS is used, but the same no-cert-verify flaw applies here. regards Evgeni Golov -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-rc3+ (SMP w/4 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 turpial depends on: ii gstreamer0.10-plugins-base 0.10.34-1GStreamer plugins from the base ii python 2.6.6-14 interactive high-level object-orie ii python-gst0.10 0.10.21-2+b1 generic media-playing framework (P ii python-gtk2 2.24.0-2 Python bindings for the GTK+ widge ii python-gtkspell 2.25.3-10Python bindings for the GtkSpell l ii python-notify 0.1.1-2+b3 Python bindings for libnotify ii python-oauth1.0.1-3 Python library implementing of the ii python-pkg-resources0.6.16-1 Package Discovery and Resource Acc ii python-simplejson 2.1.6-1 simple, fast, extensible JSON enco ii python-webkit 1.1.8-2 WebKit/Gtk Python bindings ii python2.6 2.6.7-1 An interactive high-level object-o ii python2.7 2.7.2-1 An interactive high-level object-o turpial recommends no packages. turpial 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#631373: vim-gtk fails to run
Hi Anthony, this looks just like #325526. Could it be that you also have an old libfreetype in /usr/local/lib? At least I can't reproduce the problem on an up-to-date sid box. Kind regards, -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature
Bug#625593:
On Thu, Jun 23, 2011 at 2:28 PM, Mehdi Dogguy me...@dogguy.org wrote:
On 0, Vincent Fourmond fourm...@debian.org wrote:
--- autotrace-0.31.1/debian/control
+++ autotrace-0.31.1/debian/control
@@ -3,7 +3,8 @@
Priority: optional
Maintainer: Tony Palma xbyt...@gmail.com
Build-Depends: debhelper (= 5), autotools-dev, pkg-config,
- libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagick9-dev
+ libpng12-dev, libpstoedit-dev (= 3.42-1.1),
+ libmagickcore-dev
This is not enough to fix the problem since libautotrace-dev still
depends on libmagick9-dev.
I'm considering removing this package temporarily from testing if not
fixed during the next couple of days. If you intend to NMU it, please
upload it without delay in order to to get ready to migrate sooner.
On its way.
Thanks !
Vincent
PS: debdiff to the last maintainer release attached.
diff -u autotrace-0.31.1/debian/changelog autotrace-0.31.1/debian/changelog
--- autotrace-0.31.1/debian/changelog
+++ autotrace-0.31.1/debian/changelog
@@ -1,3 +1,20 @@
+autotrace (0.31.1-15.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * ... and replace references to the old libmagick9-dev from
+libautotrace-dev (closes: #625593, again...)
+ * Urgency medium to fix RC bugs and help the imagemagick transition
+along.
+
+ -- Vincent Fourmond fourm...@debian.org Thu, 23 Jun 2011 20:34:19 +0200
+
+autotrace (0.31.1-15.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Build with recent imagemagick libraries (closes: #625593)
+
+ -- Vincent Fourmond fourm...@debian.org Mon, 06 Jun 2011 12:10:05 +0200
+
autotrace (0.31.1-15) unstable; urgency=low
* New maintainer. Closes: #525919
diff -u autotrace-0.31.1/debian/control autotrace-0.31.1/debian/control
--- autotrace-0.31.1/debian/control
+++ autotrace-0.31.1/debian/control
@@ -3,7 +3,8 @@
Priority: optional
Maintainer: Tony Palma xbyt...@gmail.com
Build-Depends: debhelper (= 5), autotools-dev, pkg-config,
- libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagick9-dev
+ libpng12-dev, libpstoedit-dev (= 3.42-1.1),
+ libmagickcore-dev
Standards-Version: 3.8.3
Homepage: http://autotrace.sourceforge.net/
@@ -28,7 +29,7 @@
Package: libautotrace-dev
Architecture: any
Section: libdevel
-Depends: libautotrace3 (= ${binary:Version}), libc6-dev | libc-dev,
libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagick9-dev
+Depends: libautotrace3 (= ${binary:Version}), libc6-dev | libc-dev,
libpng12-dev, libpstoedit-dev (= 3.42-1.1), libmagickcore-dev
Recommends: pkg-config (= 0.18)
Description: bitmap to vector graphics converter, development files
Static library and header include files needed for developing programs
Bug#625593: marked as done (transition: libmagick4 and old depend on libmagick9-dev)
Your message dated Thu, 23 Jun 2011 18:47:13 + with message-id e1qzovp-0003wd...@franck.debian.org and subject line Bug#625593: fixed in autotrace 0.31.1-15.2 has caused the Debian Bug report #625593, regarding transition: libmagick4 and old depend on libmagick9-dev 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.) -- 625593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: autotrace Severity: normal block: 625544 Hi, We would like to perform the transition from libmagickcore3, libmagick++3, libmagickwand3 to libmagickcore4, libmagick++4, libmagickwand4 This transition will requires sourcefull uploads as there is a (minimal) API change. Packages are in experimental. Please not in your case a binNMU will not work because you depend on old library libmagick9-dev instead of ibmagickcore- dev/libmagickwand-dev Thanks Bastien ---End Message--- ---BeginMessage--- Source: autotrace Source-Version: 0.31.1-15.2 We believe that the bug you reported is fixed in the latest version of autotrace, which is due to be installed in the Debian FTP archive: autotrace_0.31.1-15.2.diff.gz to main/a/autotrace/autotrace_0.31.1-15.2.diff.gz autotrace_0.31.1-15.2.dsc to main/a/autotrace/autotrace_0.31.1-15.2.dsc autotrace_0.31.1-15.2_amd64.deb to main/a/autotrace/autotrace_0.31.1-15.2_amd64.deb libautotrace-dev_0.31.1-15.2_amd64.deb to main/a/autotrace/libautotrace-dev_0.31.1-15.2_amd64.deb libautotrace3_0.31.1-15.2_amd64.deb to main/a/autotrace/libautotrace3_0.31.1-15.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 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Fourmond fourm...@debian.org (supplier of updated autotrace 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: Thu, 23 Jun 2011 20:34:19 +0200 Source: autotrace Binary: autotrace libautotrace3 libautotrace-dev Architecture: source amd64 Version: 0.31.1-15.2 Distribution: unstable Urgency: medium Maintainer: Tony Palma xbyt...@gmail.com Changed-By: Vincent Fourmond fourm...@debian.org Description: autotrace - bitmap to vector graphics converter libautotrace-dev - bitmap to vector graphics converter, development files libautotrace3 - bitmap to vector graphics converter, shared library files Closes: 625593 Changes: autotrace (0.31.1-15.2) unstable; urgency=medium . * Non-maintainer upload. * ... and replace references to the old libmagick9-dev from libautotrace-dev (closes: #625593, again...) * Urgency medium to fix RC bugs and help the imagemagick transition along. Checksums-Sha1: b0ed15c88d6cc466d5c698c000762ac32779e0ba 1148 autotrace_0.31.1-15.2.dsc 3693080aaefaf284f4f63dd1a611bdf27f5ada92 355408 autotrace_0.31.1-15.2.diff.gz 163bd61b369f90f25fad2caa850680f74f0a82ea 41636 autotrace_0.31.1-15.2_amd64.deb 52d405dec85703d632c3d861a4724c6d5d694556 113818 libautotrace3_0.31.1-15.2_amd64.deb 6753b681ae4d04d11254110cbc69d64327179d95 139714 libautotrace-dev_0.31.1-15.2_amd64.deb Checksums-Sha256: d8dabcadce430df8a2306bd6ed682842c590207db4fdf64fa694dc4c81f4b146 1148 autotrace_0.31.1-15.2.dsc 204205422aca10176441af21b91c8cfd78849ba7f36c8c91dcfdaa67eb205fbd 355408 autotrace_0.31.1-15.2.diff.gz 20ad253585244660510942209f7753a070f5570047641e64c2861d1e48c2cc53 41636 autotrace_0.31.1-15.2_amd64.deb 929f741d85312f116a73e272ca022a0632808c863357de09cf81a9de1eaea819 113818 libautotrace3_0.31.1-15.2_amd64.deb 263eeb8019a6eec2a2ef4dd0d5738d3facdb60ef1a946dbdb4105408a56b5df5 139714 libautotrace-dev_0.31.1-15.2_amd64.deb Files: 544101ecccb303ff8b629debdcf47c59 1148 graphics optional autotrace_0.31.1-15.2.dsc 64c5a9afb4715489ed689974596cd998 355408 graphics optional autotrace_0.31.1-15.2.diff.gz aaba888b4fec31277c5be1aec53034dc 41636 graphics optional autotrace_0.31.1-15.2_amd64.deb 914238b6fc7e54d56ac18c3a6f5c45a6 113818 libs optional libautotrace3_0.31.1-15.2_amd64.deb 736fc2679c3c1be5c503834831f2cfb7 139714 libdevel optional libautotrace-dev_0.31.1-15.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)
Bug#629770: marked as done (autotrace: FTBFS: build-dependency not installable: libmagick9-dev)
Your message dated Thu, 23 Jun 2011 18:47:13 + with message-id e1qzovp-0003wd...@franck.debian.org and subject line Bug#625593: fixed in autotrace 0.31.1-15.2 has caused the Debian Bug report #625593, regarding autotrace: FTBFS: build-dependency not installable: libmagick9-dev 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.) -- 625593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: autotrace Version: 0.31.1-15 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install autotrace build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-autotrace-dummy : Depends: libmagick9-dev but it is not installable E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/autotrace_0.31.1-15_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: autotrace Source-Version: 0.31.1-15.2 We believe that the bug you reported is fixed in the latest version of autotrace, which is due to be installed in the Debian FTP archive: autotrace_0.31.1-15.2.diff.gz to main/a/autotrace/autotrace_0.31.1-15.2.diff.gz autotrace_0.31.1-15.2.dsc to main/a/autotrace/autotrace_0.31.1-15.2.dsc autotrace_0.31.1-15.2_amd64.deb to main/a/autotrace/autotrace_0.31.1-15.2_amd64.deb libautotrace-dev_0.31.1-15.2_amd64.deb to main/a/autotrace/libautotrace-dev_0.31.1-15.2_amd64.deb libautotrace3_0.31.1-15.2_amd64.deb to main/a/autotrace/libautotrace3_0.31.1-15.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 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Fourmond fourm...@debian.org (supplier of updated autotrace 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: Thu, 23 Jun 2011 20:34:19 +0200 Source: autotrace Binary: autotrace libautotrace3 libautotrace-dev Architecture: source amd64 Version: 0.31.1-15.2 Distribution: unstable Urgency: medium Maintainer: Tony Palma xbyt...@gmail.com Changed-By: Vincent Fourmond fourm...@debian.org Description: autotrace - bitmap to vector graphics converter libautotrace-dev - bitmap to vector graphics converter, development files libautotrace3 - bitmap to vector graphics converter, shared library files Closes: 625593 Changes: autotrace (0.31.1-15.2) unstable; urgency=medium . * Non-maintainer upload. * ... and replace references to the old libmagick9-dev from libautotrace-dev (closes: #625593, again...) * Urgency medium to fix RC bugs and help the imagemagick transition along. Checksums-Sha1: b0ed15c88d6cc466d5c698c000762ac32779e0ba 1148 autotrace_0.31.1-15.2.dsc 3693080aaefaf284f4f63dd1a611bdf27f5ada92 355408 autotrace_0.31.1-15.2.diff.gz 163bd61b369f90f25fad2caa850680f74f0a82ea 41636 autotrace_0.31.1-15.2_amd64.deb 52d405dec85703d632c3d861a4724c6d5d694556 113818
Bug#628332: marked as done (openssl-blacklist: FTBFS: tests failed)
Your message dated Thu, 23 Jun 2011 18:48:40 + with message-id e1qzoxe-0004ci...@franck.debian.org and subject line Bug#628332: fixed in openssl-blacklist 0.5-3 has caused the Debian Bug report #628332, regarding openssl-blacklist: FTBFS: tests failed 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.) -- 628332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: openssl-blacklist Version: 0.5-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: /usr/bin/fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. dh_clean dpkg-source -b openssl-blacklist-0.5 dpkg-source: warning: no source format specified in debian/source/format, see dpkg-source(1) dpkg-source: info: using source format `1.0' dpkg-source: info: building openssl-blacklist using existing openssl-blacklist_0.5.orig.tar.gz dpkg-source: info: building openssl-blacklist in openssl-blacklist_0.5-2.diff.gz dpkg-source: warning: the diff modifies the following upstream files: examples/bad_req.csr examples/bad_rsa.key examples/bad_rsa_4096.pem examples/bad_rsa_password_is_pass.key examples/bad_x509.pem examples/bad_x509_4096.pem examples/gen_certs.sh examples/getpid.c examples/good_req.csr examples/good_rsa.key examples/good_x509.pem openssl-vulnkey openssl-vulnkey.1 test.sh dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) dpkg-source: info: building openssl-blacklist in openssl-blacklist_0.5-2.dsc debian/rules build dh_testdir # Add here commands to configure the package. touch configure-stamp dh_testdir # Add here commands to compile the package. sh ./test.sh no args: PASS no modulus: PASS no bits: PASS bad_req.csr: Skipped: 'examples/bad_req.csr' has unsupported bit size FAIL bad_req.csr (stdin): Skipped: '-' has unsupported bit size FAIL bad_x509.pem: Skipped: 'examples/bad_x509.pem' has unsupported bit size FAIL bad_x509.pem (stdin): Skipped: '-' has unsupported bit size FAIL bad_rsa.key: COMPROMISED: 58dce70acfd4dc1a9d28722fc62edb8d30110778 examples/bad_rsa.key PASS bad_rsa.key (stdin): COMPROMISED: 58dce70acfd4dc1a9d28722fc62edb8d30110778 - PASS bad_rsa_4096.pem: COMPROMISED: 35f8546394046fea00ad767812827a90debb78b5 examples/bad_rsa_4096.pem PASS bad_rsa_4096.pem (stdin): COMPROMISED: 35f8546394046fea00ad767812827a90debb78b5 - PASS bad_x509_4096.pem: Skipped: 'examples/bad_x509_4096.pem' has unsupported bit size FAIL bad_x509_4096.pem (stdin): Skipped: '-' has unsupported bit size FAIL all bad files (examples/bad_req.csr examples/bad_x509.pem examples/bad_rsa.key examples/bad_rsa_4096.pem examples/bad_x509_4096.pem): Skipped: 'examples/bad_req.csr' has unsupported bit size Skipped: 'examples/bad_x509.pem' has unsupported bit size Skipped: 'examples/bad_x509_4096.pem' has unsupported bit size COMPROMISED: 58dce70acfd4dc1a9d28722fc62edb8d30110778 examples/bad_rsa.key COMPROMISED: 35f8546394046fea00ad767812827a90debb78b5 examples/bad_rsa_4096.pem PASS bad modulus: COMPROMISED: ff64d7f83c9701d5fa7958ef2c82003451fa91ee PASS good_req.csr: Skipped: 'examples/good_req.csr' has unsupported bit size PASS good_req.csr (stdin): Skipped: '-' has unsupported bit size PASS good_x509.pem: Skipped: 'examples/good_x509.pem' has unsupported bit size PASS good_x509.pem (stdin): Skipped: '-' has unsupported bit size PASS good_rsa.key: Not blacklisted: 00844cdcf275a7ee6f73bdfab27af607f8c78f5b examples/good_rsa.key PASS good_rsa.key (stdin): Not blacklisted: 00844cdcf275a7ee6f73bdfab27af607f8c78f5b - PASS all good files (examples/good_req.csr examples/good_x509.pem examples/good_rsa.key): Skipped: 'examples/good_req.csr' has unsupported bit size Skipped: 'examples/good_x509.pem' has unsupported bit size Not blacklisted: 00844cdcf275a7ee6f73bdfab27af607f8c78f5b examples/good_rsa.key PASS some bad files, some good files (examples/bad_req.csr examples/bad_x509.pem examples/bad_rsa.key examples/bad_rsa_4096.pem examples/bad_x509_4096.pem examples/good_req.csr examples/good_x509.pem examples/good_rsa.key): Skipped: 'examples/bad_req.csr' has unsupported
Bug#630747: sun-java6-jre depends on sun-java6-bin, but it doesn't exist in the ia64 repository
Le jeudi 16 juin 2011 à 23:32 +0200, Alberto Aparici a écrit : Package: sun-java6-jre Version: 6.24-1~squeeze1 Severity: grave Justification: renders package unusable Otherwise, if sun-java6-bin is missing because the ia64 binaries have not been released, then the package sun-java6-jre should be deleted from the repository, as it cannot be installed. It is probably what we should do... We cannot use JDK from the url you sent. We have to use http://jdk-distros.java.net/ And the ia64 version has been failing for a while: https://buildd.debian.org/status/logs.php?pkg=sun-java6arch=ia64 I don't have time to track the reason of the seg fault under ia64 but I would be happy to apply any patch. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629917: code generated for python modules fails to compile with gcc 4.6
reassign 629917 swig1.3 thanks Since swig2.0 now provides swig and this is only a bug with swig1.3 I'm reassigning this bug to swig1.3 Kind regards, -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#629917: code generated for python modules fails to compile with gcc 4.6
Processing commands for cont...@bugs.debian.org: reassign 629917 swig1.3 Bug #629917 [swig] code generated for python modules fails to compile with gcc 4.6 Bug reassigned from package 'swig' to 'swig1.3'. Bug No longer marked as found in versions swig1.3/1.3.40-3.1. thanks Stopping processing here. Please contact me if you need assistance. -- 629917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631041: mozvoikko: FTBFS against iceweasel 4.0 or 5.0
New upstream release candidate version 1.10.0rc1 fixes this bug[1] (with a small patch to modify Makefile a bit). When the final version is released (probably quite soon) I will update this package. [1] http://www.puimula.org/htp/testing/mozvoikko-1.10.0rc1.tar.gz -- Heikki Mäntysaari -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unblock
Processing commands for cont...@bugs.debian.org: # fixed with swig2/2.0.4-2 unblock 624982 with 629917 Bug #624982 [src:csound] csound: FTBFS: interfaces/python_interface_wrap.cc:3402:13: error: 'ptrdiff_t' does not name a type Was blocked by: 629917 Removed blocking bug(s) of 624982: 629917 unblock 625087 with 629917 Bug #625087 [src:dballe] dballe: FTBFS: dballe_wrap_python.cc:2865:13: error: 'ptrdiff_t' does not name a type Was blocked by: 629917 Removed blocking bug(s) of 625087: 629917 thanks Stopping processing here. Please contact me if you need assistance. -- 625087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625087 624982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625087: marked as done (dballe: FTBFS: dballe_wrap_python.cc:2865:13: error: 'ptrdiff_t' does not name a type)
Your message dated Thu, 23 Jun 2011 22:27:20 +0200
with message-id 4e03a1a8.2070...@gmx.at
and subject line builds again
has caused the Debian Bug report #625087,
regarding dballe: FTBFS: dballe_wrap_python.cc:2865:13: error: 'ptrdiff_t' does
not name a type
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.)
--
625087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: dballe
Version: 4.0.18-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
/bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I..
-I/usr/include/python2.6 -I..-g -O2 -g -O2 -Wall -c -o
dballe_wrap_python.lo dballe_wrap_python.cc
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/python2.6 -I..
-g -O2 -g -O2 -Wall -c dballe_wrap_python.cc -fPIC -DPIC -o
.libs/dballe_wrap_python.o
dballe_wrap_python.cc:2865:13: error: 'ptrdiff_t' does not name a type
dballe_wrap_python.cc:2902:21: error: expected ';' at end of member
declaration
dballe_wrap_python.cc:2902:39: error: expected ')' before 'n'
dballe_wrap_python.cc:2917:34: error: declaration of 'operator+=' as
non-function
dballe_wrap_python.cc:2917:30: error: expected ';' at end of member
declaration
dballe_wrap_python.cc:2917:44: error: expected ')' before 'n'
dballe_wrap_python.cc:2922:34: error: declaration of 'operator-=' as
non-function
dballe_wrap_python.cc:2922:30: error: expected ';' at end of member
declaration
dballe_wrap_python.cc:2922:44: error: expected ')' before 'n'
dballe_wrap_python.cc:2927:33: error: declaration of 'operator+' as
non-function
dballe_wrap_python.cc:2927:30: error: expected ';' at end of member
declaration
dballe_wrap_python.cc:2927:43: error: expected ')' before 'n'
dballe_wrap_python.cc:2932:33: error: declaration of 'operator-' as
non-function
dballe_wrap_python.cc:2932:30: error: expected ';' at end of member
declaration
dballe_wrap_python.cc:2932:43: error: expected ')' before 'n'
dballe_wrap_python.cc:2937:5: error: 'ptrdiff_t' does not name a type
dballe_wrap_python.cc:3093:23: error: 'SWIG_From_ptrdiff_t' declared as an
'inline' variable
dballe_wrap_python.cc:3093:23: error: 'ptrdiff_t' was not declared in this
scope
dballe_wrap_python.cc:3093:23: note: suggested alternatives:
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
dballe_wrap_python.cc:3094:1: error: expected ',' or ';' before '{' token
dballe_wrap_python.cc:3146:39: error: 'ptrdiff_t' has not been declared
dballe_wrap_python.cc: In function 'int SWIG_AsVal_ptrdiff_t(PyObject*,
int*)':
dballe_wrap_python.cc:3150:50: error: expected type-specifier before
'ptrdiff_t'
dballe_wrap_python.cc:3150:50: error: expected '' before 'ptrdiff_t'
dballe_wrap_python.cc:3150:50: error: expected '(' before 'ptrdiff_t'
dballe_wrap_python.cc:3150:50: error: 'ptrdiff_t' was not declared in this
scope
dballe_wrap_python.cc:3150:50: note: suggested alternatives:
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
dballe_wrap_python.cc:3150:64: error: expected ')' before ';' token
dballe_wrap_python.cc: In function 'PyObject*
_wrap_SwigPyIterator_distance(PyObject*, PyObject*)':
dballe_wrap_python.cc:3709:3: error: 'ptrdiff_t' was not declared in this
scope
dballe_wrap_python.cc:3709:3: note: suggested alternatives:
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
/usr/include/c++/4.6/x86_64-linux-gnu/bits/c++config.h:156:28: note:
'std::ptrdiff_t'
dballe_wrap_python.cc:3709:13: error: expected ';' before 'result'
dballe_wrap_python.cc:3726:5: error: 'result' was not declared in this scope
dballe_wrap_python.cc:3726:52: error: 'const struct swig::SwigPyIterator' has
no member named 'distance'
dballe_wrap_python.cc:3732:48: error: expected type-specifier before
'ptrdiff_t'
dballe_wrap_python.cc:3732:48: error: expected '' before 'ptrdiff_t'
dballe_wrap_python.cc:3732:48: error: expected '(' before 'ptrdiff_t'
dballe_wrap_python.cc:3732:60: error: 'result' was not declared in this scope
dballe_wrap_python.cc: In function 'PyObject*
Bug#624982: csound: FTBFS: interfaces/python_interface_wrap.cc:3402:13: error:, 'ptrdiff_t' does not name a type
The build failure due to swig is fixed now. But csounds fails to build nevertheless. It fails with: x86_64-linux-gnu-g++ -o libCsoundAC.so.5.2 -Wl,-Bdynamic -Wl,-rpath-link,. -shared --no-export-all-symbols -Wl,-soname=libCsoundAC.so.5.2 frontends/CsoundAC/Cell.os frontends/CsoundAC/ChordLindenmayer.os frontends/CsoundAC/Composition.os frontends/CsoundAC/Conversions.os frontends/CsoundAC/Counterpoint.os frontends/CsoundAC/CounterpointNode.os frontends/CsoundAC/Event.os frontends/CsoundAC/Hocket.os frontends/CsoundAC/ImageToScore.os frontends/CsoundAC/Lindenmayer.os frontends/CsoundAC/MCRM.os frontends/CsoundAC/Midifile.os frontends/CsoundAC/MusicModel.os frontends/CsoundAC/Node.os frontends/CsoundAC/Random.os frontends/CsoundAC/Rescale.os frontends/CsoundAC/Score.os frontends/CsoundAC/ScoreModel.os frontends/CsoundAC/ScoreNode.os frontends/CsoundAC/Sequence.os frontends/CsoundAC/Shell.os frontends/CsoundAC/Soundfile.os frontends/CsoundAC/StrangeAttractor.os frontends/CsoundAC/System.os frontends/CsoundAC/Voicelead.os frontends/CsoundAC/VoiceleadingNode.os -L. -L. -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu -L/usr/local/lib -L/usr/lib -L/usr/lib/python2.6/config libcsound64.so.5.2 -lsndfile libcsnd.so.5.2 -lsndfile -lgomp -lasound -llo -lpng -ldl -lstdc++ -lpthread -lm -lfltk_images -lfltk -lutil -ldl -lm -lfltk_images x86_64-linux-gnu-g++: error: unrecognized option '--no-export-all-symbols' scons: *** [libCsoundAC.so.5.2] Error 1 scons: building terminated because of errors. make: *** [debian/stamp-scons-build] Error 2 I've attached the build log. Kind regards, -- Sebastian Ramacher csound.build.log.gz Description: application/gzip signature.asc Description: OpenPGP digital signature
Bug#631373: marked as done ((no subject))
Your message dated Thu, 23 Jun 2011 22:41:48 +0200 with message-id 4e03a50c.3040...@gmx.at and subject line Re: vim-gtk fails to run has caused the Debian Bug report #631373, regarding (no subject) 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.) -- 631373: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: vim-gtk Version: 2:7.3.154+hg~74503f6ee649-2+b1 Severity: grave Justification: renders package unusable Following an upgrade in Sid today I get this with gvim: arcadia:~:$ gvim gvim: symbol lookup error: /usr/lib/libcairo.so.2: undefined symbol: FT_GlyphSlot_Embolden I realise this is probably a bug in libcairo.so.2 but I can't identify which package is causing it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (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 Versions of packages vim-gtk depends on: ii libacl1 2.2.49-5 Access control list shared library ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libgdk-pi 2.23.3-3 GDK Pixbuf library ii libglib2. 2.28.6-1 The GLib library of C routines ii libgpm2 1.20.4-3.4 General Purpose Mouse - shared lib ii libgtk2.0 2.24.4-3 The GTK+ graphical user interface ii libice6 2:1.0.7-2 X11 Inter-Client Exchange library ii liblua5.1 5.1.4-5Simple, extensible, embeddable pro ii libncurse 5.9-1 shared libraries for terminal hand ii libpango1 1.28.3-6 Layout and rendering of internatio ii libperl5. 5.12.3-7+b1shared Perl library ii libpython 2.6.7-1Shared Python runtime library (ver ii libruby1. 1.8.7.334-5Libraries necessary to run Ruby 1. ii libselinu 2.0.98-1.1 SELinux runtime shared libraries ii libsm62:1.2.0-2 X11 Session Management library ii libx11-6 2:1.4.3-2 X11 client-side library ii libxt61:1.1.1-2 X11 toolkit intrinsics library ii tcl8.58.5.9-2Tcl (the Tool Command Language) v8 ii vim-commo 2:7.3.154+hg~74503f6ee649-2+b1 Vi IMproved - Common files ii vim-gui-c 2:7.3.154+hg~74503f6ee649-2Vi IMproved - Common GUI files ii vim-runti 2:7.3.154+hg~74503f6ee649-2Vi IMproved - Runtime files vim-gtk recommends no packages. Versions of packages vim-gtk suggests: pn cscope none (no description available) ii gnome-icon-t 3.0.0-3 GNOME Desktop icon theme ii ttf-dejavu 2.33-1 Metapackage to pull in ttf-dejavu- ii vim-doc 2:7.3.154+hg~74503f6ee649-2 Vi IMproved - HTML documentation -- no debconf information ---End Message--- ---BeginMessage--- On 06/23/2011 10:26 PM, Anthony Campbell wrote: On 23 Jun 2011, Sebastian Ramacher wrote: Hi Anthony, this looks just like #325526. Could it be that you also have an old libfreetype in /usr/local/lib? At least I can't reproduce the problem on an up-to-date sid box. Kind regards, -- Sebastian Ramacher Yes, indeed I did, and removing it (along with all the other old stuff there) has made gvim work again. Sincere thanks indeed! You're welcome. So I'm closing this bug. What I find odd is that this has only just now bitten me, although the old files must have been there for ages. Anyway, thanks again for the quick respose. I would guess that your $PATH might have changed. But that's just a wild guess. Kind regards, -- Sebastian Ramacher signature.asc Description: OpenPGP digital signature ---End Message---
Bug#628281: marked as done (libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found)
Your message dated Thu, 23 Jun 2011 20:57:12 + with message-id e1qzqxc-0002ud...@franck.debian.org and subject line Bug#628281: fixed in vala-0.12 0.12.1-1 has caused the Debian Bug report #628281, regarding libchamplain: FTBFS: Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found 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.) -- 628281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libchamplain Version: 0.10.0-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110528 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g-ir-scanner: link: /bin/bash ../libtool --mode=link --tag=CC --silent gcc -o /build/user-libchamplain_0.10.0-2-amd64-v6EMq8/libchamplain-0.10.0/champlain/tmp-introspectPygso3/Champlain-0.10 -export-dynamic -g -O2 -g -O2 -Wall -L. libchamplain-0.10.la -pthread -lgio-2.0 -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 /build/user-libchamplain_0.10.0-2-amd64-v6EMq8/libchamplain-0.10.0/champlain/tmp-introspectPygso3/Champlain-0.10.o ( /usr/bin/vapigen --library champlain-0.10 --pkg clutter-1.0 --pkg atk ./Champlain-0.10.gir ) Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found Json-1.0.gir:0.0-0.0: error: The type name `gunichar' could not be found Generation failed: 2 error(s), 0 warning(s) make[4]: *** [champlain-0.10.vapi] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/28/libchamplain_0.10.0-2_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: vala-0.12 Source-Version: 0.12.1-1 We believe that the bug you reported is fixed in the latest version of vala-0.12, which is due to be installed in the Debian FTP archive: libvala-0.12-0-dbg_0.12.1-1_i386.deb to main/v/vala-0.12/libvala-0.12-0-dbg_0.12.1-1_i386.deb libvala-0.12-0_0.12.1-1_i386.deb to main/v/vala-0.12/libvala-0.12-0_0.12.1-1_i386.deb libvala-0.12-dev_0.12.1-1_i386.deb to main/v/vala-0.12/libvala-0.12-dev_0.12.1-1_i386.deb vala-0.12-doc_0.12.1-1_all.deb to main/v/vala-0.12/vala-0.12-doc_0.12.1-1_all.deb vala-0.12_0.12.1-1.debian.tar.gz to main/v/vala-0.12/vala-0.12_0.12.1-1.debian.tar.gz vala-0.12_0.12.1-1.dsc to main/v/vala-0.12/vala-0.12_0.12.1-1.dsc vala-0.12_0.12.1.orig.tar.bz2 to main/v/vala-0.12/vala-0.12_0.12.1.orig.tar.bz2 valac-0.12-dbg_0.12.1-1_i386.deb to main/v/vala-0.12/valac-0.12-dbg_0.12.1-1_i386.deb valac-0.12_0.12.1-1_i386.deb to main/v/vala-0.12/valac-0.12_0.12.1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 628...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated vala-0.12 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: SHA256 Format: 1.8 Date: Thu, 23 Jun 2011 21:26:03 +0200 Source: vala-0.12 Binary: valac-0.12 vala-0.12-doc libvala-0.12-0 libvala-0.12-dev valac-0.12-dbg libvala-0.12-0-dbg Architecture: source all i386 Version: 0.12.1-1 Distribution: unstable Urgency: low Maintainer: Maintainers of Vala packages pkg-vala-maintain...@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: libvala-0.12-0 - C# like language for the GObject system - library libvala-0.12-0-dbg - C# like language for the GObject system - library symbols libvala-0.12-dev - C# like language for the GObject system - development headers vala-0.12-doc - C# like language for the GObject system - documentation valac-0.12 - C# like language for the GObject system valac-0.12-dbg - C# like language for the GObject system Closes:
Bug#631437: movabletype-opensource: information disclosure vulnerability fixed in 4.37
Package: movabletype-opensource Version: 4.3.6.1+dfsg-1 Severity: grave Tags: security Justification: user security hole As reported in: http://www.movabletype.org/documentation/appendices/release-notes/512.html Movable Type 5.12, 5.06, 4.37 were released as mandatory security updates. These updates resolve multiple vulnerabilities discovered in Movable Type 5.x and Movable Type 4.x. All users must upgrade to the latest release immediately. Under certain circumstances, a user who has Create Entries or Manage Blog pemissions may be able to read known files on the local file system. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631347: [php-maint] Bug#631347: CVE-2011-2483 crypt_blowfish: 8-bit character mishandling allows different password pairs to produce the same hash
On Thu, Jun 23, 2011 at 07:42:01AM +0200, Ondřej Surý wrote: forcemerge 631286 631347 tags 631286 +squeeze wheezy sid Thank you Hi, I already notice the bug when you reported it in postgresql and cloned the bug. Yes, the php5 is affected, but only squeeze and onwards (writing this from top of my head, so I will better double check). Security team, can you remove the last not yet published security upload of php5? I'll bundle this CVE in and we will finally release the security update. You can simply upload with an increased version number, the dak install will supercede all older versions. 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#629815: Bug#630167: Bug#629815: No rule to make target `/usr/lib/libdl.so'
close 630167 2.8.4+dfsg.1-5
thanks
Hello,
On ketvirtadienis 23 Birželis 2011 14:20:59 Andreas Tille wrote:
I tried to rebuild gofigure2 (which is affected by #629815) now I do
not get the
No rule to make target `/usr/lib/libdl.so', needed by
`lib/libvtkRenderingAddOn2.so.0.8'
any more but rather
No rule to make target `/usr/lib/libXt.so', needed by
`lib/libPoissonReconstruction.so.0.8'
$ grep -rn -e '/usr/lib/libXt.so' /usr/lib/vtk-5.6/
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:76: SET(vtkRendering_LIB_DEPENDS
general;vtkGraphics;general;vtkImaging;general;vtkIO;general;vtkftgl;general;QtGui;general;QtCore;general;/usr/lib/libgl2ps.so;general;/usr/lib/libz.so;general;/usr/lib/libpng.so;general;/usr/lib/libz.so;general;/usr/lib/libGL.so;general;/usr/lib/libXt.so;general;X11;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:186: SET(vtkRendering_LIB_DEPENDS
vtkGraphics;vtkImaging;vtkIO;vtkftgl;QtGui;QtCore;/usr/lib/libgl2ps.so;/usr/lib/libz.so;/usr/lib/libpng.so;/usr/lib/libz.so;/usr/lib/libGL.so;/usr/lib/libXt.so;X11;)
$ grep -rn -e '/usr/lib/libdl.so' /usr/lib/vtk-5.6/
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:5: SET(Cosmo_LIB_DEPENDS
general;vtksys;general;vtkCommon;general;/usr/lib/openmpi/lib/libmpi_cxx.so;general;/usr/lib/openmpi/lib/libmpi.so;general;/usr/lib/openmpi/lib/libopen-
rte.so;general;/usr/lib/openmpi/lib/libopen-
pal.so;general;/usr/lib/libdl.so;general;/usr/lib/libnsl.so;general;/usr/lib/libutil.so;general;/usr/lib/libm.so;general;/usr/lib/libdl.so;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:6: SET(MapReduceMPI_LIB_DEPENDS
general;/usr/lib/openmpi/lib/libmpi_cxx.so;general;/usr/lib/openmpi/lib/libmpi.so;general;/usr/lib/openmpi/lib/libopen-
rte.so;general;/usr/lib/openmpi/lib/libopen-
pal.so;general;/usr/lib/libdl.so;general;/usr/lib/libnsl.so;general;/usr/lib/libutil.so;general;/usr/lib/libm.so;general;/usr/lib/libdl.so;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:9: SET(VPIC_LIB_DEPENDS
general;vtksys;general;/usr/lib/openmpi/lib/libmpi_cxx.so;general;/usr/lib/openmpi/lib/libmpi.so;general;/usr/lib/openmpi/lib/libopen-
rte.so;general;/usr/lib/openmpi/lib/libopen-
pal.so;general;/usr/lib/libdl.so;general;/usr/lib/libnsl.so;general;/usr/lib/libutil.so;general;/usr/lib/libm.so;general;/usr/lib/libdl.so;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:115: SET(Cosmo_LIB_DEPENDS
vtksys;vtkCommon;/usr/lib/openmpi/lib/libmpi_cxx.so;/usr/lib/openmpi/lib/libmpi.so;/usr/lib/openmpi/lib/libopen-
rte.so;/usr/lib/openmpi/lib/libopen-
pal.so;/usr/lib/libdl.so;/usr/lib/libnsl.so;/usr/lib/libutil.so;/usr/lib/libm.so;/usr/lib/libdl.so;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:116: SET(MapReduceMPI_LIB_DEPENDS
/usr/lib/openmpi/lib/libmpi_cxx.so;/usr/lib/openmpi/lib/libmpi.so;/usr/lib/openmpi/lib/libopen-
rte.so;/usr/lib/openmpi/lib/libopen-
pal.so;/usr/lib/libdl.so;/usr/lib/libnsl.so;/usr/lib/libutil.so;/usr/lib/libm.so;/usr/lib/libdl.so;)
/usr/lib/vtk-5.6/VTKLibraryDepends.cmake:119: SET(VPIC_LIB_DEPENDS
vtksys;/usr/lib/openmpi/lib/libmpi_cxx.so;/usr/lib/openmpi/lib/libmpi.so;/usr/lib/openmpi/lib/libopen-
rte.so;/usr/lib/openmpi/lib/libopen-
pal.so;/usr/lib/libdl.so;/usr/lib/libnsl.so;/usr/lib/libutil.so;/usr/lib/libm.so;/usr/lib/libdl.so;)
$ dpkg -S VTKLibraryDepends.cmake
libvtk5-dev: /usr/lib/vtk-5.6/VTKLibraryDepends.cmake
$ dpkg -l libvtk5-dev | grep ii
ii libvtk5-dev5.6.1-6 VTK header files for building C++ code
So you can reassign your bug where it belongs (libvtk5-dev). Unfortunately, VTK
has one of the most hackish (and outdated in places) cmake code. Good luck
fixing it.
and thus I assume my action to reopen #630167 (which is unfortunately
not properly documented in the bug log) was not the right thing to do.
Yes, it was not the right thing to do because:
1) the bug is not related to your problem. It was about kfreebsd and armel
while your package fails on all arches.
2) I had no clue what happened because original explanation didn't say
much at all. I have no idea how you managed to reopen it in such a cryptic
way.
Similarly I can confirm that when trying to build ginkgocadx I do not
run any more in the missing libdl.so but rather into
No rule to make target `/lib/libwrap.so.0', needed by
`src/cadxcore/libCADxCore.so.2.4.1.1'
which somehow smells like libwrap0 is guilty for the problem. I admit
that this multiarch stuff is above my horizon and I hope that somebody
might be able to clarify what might be the correct way of action now.
Always grep the source before blaming something else :-)
$ grep -rn '/lib/libwrap.so.0' .
./src/cadxcore/CMakeLists.txt:171: TARGET_LINK_LIBRARIES(${PROJECT_NAME}
dcmdsig oflog
/lib/libwrap.so.0)
--
Modestas Vainius mo...@debian.org
signature.asc
Description: This is a digitally signed message part.
Bug#624975: fix available upstream
On Thu, Jun 9, 2011 at 18:55:52 +0200, Sebastian Ramacher wrote: tag 624975 + patch thanks There is a fix available from upstream [1]. Kind regards, [1] http://trac.openturns.org/changeset/1920/trunk/lib/src/Base/Common/StorageManager.hxx For the lazy (i.e. me tomorrow), that's: Index: trunk/lib/src/Base/Common/StorageManager.hxx === --- a/trunk/lib/src/Base/Common/StorageManager.hxx +++ b/trunk/lib/src/Base/Common/StorageManager.hxx @@ -30,6 +30,7 @@ #include vector // for std::vector #include set // for std::set #include map // for std::map +#include cstddef // for ptrdiff_t #include Object.hxx #include Pointer.hxx #include Exception.hxx Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615545: Bug in libmail-mboxparser-perl fixed in revision 76418
tag 615545 + pending thanks Some bugs are closed in revision 76418 by Salvatore Bonaccorso (carnil) Commit message: * Team upload. * Add perl-Mail-MboxParser-0.55-Fix-garbled-attachment-name-RT-66576.patch patch to patch the attachment name in t/10_qpnames.t which is not valid UTF-8 and thus does not match text stored in the mbox. Fixes FTBFS (Closes: #615545). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug in libmail-mboxparser-perl fixed in revision 76418
Processing commands for cont...@bugs.debian.org: tag 615545 + pending Bug #615545 [src:libmail-mboxparser-perl] libmail-mboxparser-perl: failing tests in unstable Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 615545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631252: marked as done (File conflict between libwrap0 and tcpd)
Your message dated Thu, 23 Jun 2011 22:33:26 + with message-id e1qzssk-0007pd...@franck.debian.org and subject line Bug#631252: fixed in tcp-wrappers 7.6.q-21 has caused the Debian Bug report #631252, regarding File conflict between libwrap0 and tcpd 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.) -- 631252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libwrap0 Version: 7.6.q-20 Severity: serious libwrap0 fails to upgrade because there is a file conflict between tcpd and libwrap0 for the man pages that were moved from tcpd to libwrap0. There is missing a Breaks/Replaces. That said, moving the man pages into the library package is not a good idea as it will make a potential future soname bump harder and especially since you converted the library package to multi-arch. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwrap0 depends on: ii libc6 2.13-7 Embedded GNU C Library: Shared lib Versions of packages libwrap0 recommends: ii tcpd 7.6.q-20 Wietse Venema's TCP wrapper utilit libwrap0 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: tcp-wrappers Source-Version: 7.6.q-21 We believe that the bug you reported is fixed in the latest version of tcp-wrappers, which is due to be installed in the Debian FTP archive: libwrap0-dev_7.6.q-21_i386.deb to main/t/tcp-wrappers/libwrap0-dev_7.6.q-21_i386.deb libwrap0_7.6.q-21_i386.deb to main/t/tcp-wrappers/libwrap0_7.6.q-21_i386.deb tcp-wrappers_7.6.q-21.debian.tar.gz to main/t/tcp-wrappers/tcp-wrappers_7.6.q-21.debian.tar.gz tcp-wrappers_7.6.q-21.dsc to main/t/tcp-wrappers/tcp-wrappers_7.6.q-21.dsc tcpd_7.6.q-21_i386.deb to main/t/tcp-wrappers/tcpd_7.6.q-21_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 631...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri m...@linux.it (supplier of updated tcp-wrappers 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: Fri, 24 Jun 2011 00:21:44 +0200 Source: tcp-wrappers Binary: tcpd libwrap0 libwrap0-dev Architecture: source i386 Version: 7.6.q-21 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description: libwrap0 - Wietse Venema's TCP wrappers library libwrap0-dev - Wietse Venema's TCP wrappers library, development files tcpd - Wietse Venema's TCP wrapper utilities Closes: 631247 631252 631311 Changes: tcp-wrappers (7.6.q-21) unstable; urgency=medium . * Added the proper Breaks/Replaces directives to deal with the man pages moved in 7.6.q-20. (Closes: #631252, #631311) * Enabled IPv6 support for the Hurd build. (Closes: #631247) * Enabled hardening with hardening-includes. * Checksums-Sha1: dcf7da1a0da3d799cc79ba62742ae6921e2dfe9e 1067 tcp-wrappers_7.6.q-21.dsc d781f1b835faeb370c67c712fc4895240b0b8c52 42675 tcp-wrappers_7.6.q-21.debian.tar.gz ef96fe9a4136eb9380557dbacc5c1fbbecb49e20 26400 tcpd_7.6.q-21_i386.deb 7070ce9ae702cf69daab018fb95fa3fe65ee216a 61384 libwrap0_7.6.q-21_i386.deb dd1e1498454852d8f8165edf1fa0df1074db9303 23068 libwrap0-dev_7.6.q-21_i386.deb Checksums-Sha256: 8819dc275c66cd60970c8d93e703fcdb49693614388b0aee37c268ea46debe14 1067 tcp-wrappers_7.6.q-21.dsc 4cfc73744c4538d852af04bd0043aeb521db671073af87b88a03aff59a163f62 42675 tcp-wrappers_7.6.q-21.debian.tar.gz db9d438e5d157e86f5a7be518c768b4a33ddb77a6e86e27634abee523b1ae102 26400 tcpd_7.6.q-21_i386.deb e5bf51ebedf0d51e374cc1a18a1a8c82ec53a6b97fba3efcf2db24a8cf8e92cf 61384 libwrap0_7.6.q-21_i386.deb 211744395f8c2eae3941aa81bfc70bd5ba92e3f6cd61bfc3fe6dac83c6630058 23068 libwrap0-dev_7.6.q-21_i386.deb Files: 6cd2d10ac7025c18cb4d8ccc6836331a 1067 net important tcp-wrappers_7.6.q-21.dsc 257d1688c422bf77df072deb8fa35fb8 42675 net important
Bug#631311: marked as done (tcp-wrappers: file conflict in libwrap0_7.6.q-20 with tcpd 7.6.q-19)
Your message dated Thu, 23 Jun 2011 22:33:26 + with message-id e1qzssk-0007ph...@franck.debian.org and subject line Bug#631311: fixed in tcp-wrappers 7.6.q-21 has caused the Debian Bug report #631311, regarding tcp-wrappers: file conflict in libwrap0_7.6.q-20 with tcpd 7.6.q-19 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.) -- 631311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tcp-wrappers Version: 7.6.q-20 Severity: serious While updating my cowbuilder chroot, I get this: Unpacking replacement libwrap0 ... dpkg: error processing /var/cache/apt/archives/libwrap0_7.6.q-20_i386.deb (--unpack): trying to overwrite '/usr/share/man/man5/hosts_options.5.gz', which is also in package tcpd 7.6.q-19 configured to not write apport reports Preparing to replace iptables 1.4.11.1-1 (using .../iptables_1.4.11.1-2_i386.deb) ... Unpacking replacement iptables ... Preparing to replace rsyslog 5.8.1-1 (using .../rsyslog_5.8.2-1_i386.deb) ... Unpacking replacement rsyslog ... Preparing to replace tcpd 7.6.q-19 (using .../tcpd_7.6.q-20_i386.deb) ... Unpacking replacement tcpd ... Probably libwrap0 is missing a Replaces for that file - or a Conflicts with tcpd 7.6.q-20 Regards, Frank -- HOST System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable'), (99, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash -- Frank Küster Sprecher B90/Grüne OV Miltenberg und Umgebung VCD Miltenberg, ADFC Aschaffenburg-Miltenberg Debian Developer (TeXLive) ---End Message--- ---BeginMessage--- Source: tcp-wrappers Source-Version: 7.6.q-21 We believe that the bug you reported is fixed in the latest version of tcp-wrappers, which is due to be installed in the Debian FTP archive: libwrap0-dev_7.6.q-21_i386.deb to main/t/tcp-wrappers/libwrap0-dev_7.6.q-21_i386.deb libwrap0_7.6.q-21_i386.deb to main/t/tcp-wrappers/libwrap0_7.6.q-21_i386.deb tcp-wrappers_7.6.q-21.debian.tar.gz to main/t/tcp-wrappers/tcp-wrappers_7.6.q-21.debian.tar.gz tcp-wrappers_7.6.q-21.dsc to main/t/tcp-wrappers/tcp-wrappers_7.6.q-21.dsc tcpd_7.6.q-21_i386.deb to main/t/tcp-wrappers/tcpd_7.6.q-21_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 631...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marco d'Itri m...@linux.it (supplier of updated tcp-wrappers 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: Fri, 24 Jun 2011 00:21:44 +0200 Source: tcp-wrappers Binary: tcpd libwrap0 libwrap0-dev Architecture: source i386 Version: 7.6.q-21 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri m...@linux.it Changed-By: Marco d'Itri m...@linux.it Description: libwrap0 - Wietse Venema's TCP wrappers library libwrap0-dev - Wietse Venema's TCP wrappers library, development files tcpd - Wietse Venema's TCP wrapper utilities Closes: 631247 631252 631311 Changes: tcp-wrappers (7.6.q-21) unstable; urgency=medium . * Added the proper Breaks/Replaces directives to deal with the man pages moved in 7.6.q-20. (Closes: #631252, #631311) * Enabled IPv6 support for the Hurd build. (Closes: #631247) * Enabled hardening with hardening-includes. * Checksums-Sha1: dcf7da1a0da3d799cc79ba62742ae6921e2dfe9e 1067 tcp-wrappers_7.6.q-21.dsc d781f1b835faeb370c67c712fc4895240b0b8c52 42675 tcp-wrappers_7.6.q-21.debian.tar.gz ef96fe9a4136eb9380557dbacc5c1fbbecb49e20 26400 tcpd_7.6.q-21_i386.deb 7070ce9ae702cf69daab018fb95fa3fe65ee216a 61384 libwrap0_7.6.q-21_i386.deb dd1e1498454852d8f8165edf1fa0df1074db9303 23068 libwrap0-dev_7.6.q-21_i386.deb Checksums-Sha256: 8819dc275c66cd60970c8d93e703fcdb49693614388b0aee37c268ea46debe14 1067 tcp-wrappers_7.6.q-21.dsc 4cfc73744c4538d852af04bd0043aeb521db671073af87b88a03aff59a163f62 42675 tcp-wrappers_7.6.q-21.debian.tar.gz db9d438e5d157e86f5a7be518c768b4a33ddb77a6e86e27634abee523b1ae102 26400 tcpd_7.6.q-21_i386.deb e5bf51ebedf0d51e374cc1a18a1a8c82ec53a6b97fba3efcf2db24a8cf8e92cf 61384
Bug#631437: marked as done (movabletype-opensource: information disclosure vulnerability fixed in 4.37)
Your message dated Thu, 23 Jun 2011 22:33:12 + with message-id e1qzssw-0007jl...@franck.debian.org and subject line Bug#631437: fixed in movabletype-opensource 4.3.7+dfsg-1 has caused the Debian Bug report #631437, regarding movabletype-opensource: information disclosure vulnerability fixed in 4.37 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.) -- 631437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: movabletype-opensource Version: 4.3.6.1+dfsg-1 Severity: grave Tags: security Justification: user security hole As reported in: http://www.movabletype.org/documentation/appendices/release-notes/512.html Movable Type 5.12, 5.06, 4.37 were released as mandatory security updates. These updates resolve multiple vulnerabilities discovered in Movable Type 5.x and Movable Type 4.x. All users must upgrade to the latest release immediately. Under certain circumstances, a user who has Create Entries or Manage Blog pemissions may be able to read known files on the local file system. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) ---End Message--- ---BeginMessage--- Source: movabletype-opensource Source-Version: 4.3.7+dfsg-1 We believe that the bug you reported is fixed in the latest version of movabletype-opensource, which is due to be installed in the Debian FTP archive: movabletype-opensource_4.3.7+dfsg-1.debian.tar.gz to main/m/movabletype-opensource/movabletype-opensource_4.3.7+dfsg-1.debian.tar.gz movabletype-opensource_4.3.7+dfsg-1.dsc to main/m/movabletype-opensource/movabletype-opensource_4.3.7+dfsg-1.dsc movabletype-opensource_4.3.7+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-opensource_4.3.7+dfsg-1_all.deb movabletype-opensource_4.3.7+dfsg.orig.tar.gz to main/m/movabletype-opensource/movabletype-opensource_4.3.7+dfsg.orig.tar.gz movabletype-plugin-core_4.3.7+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-plugin-core_4.3.7+dfsg-1_all.deb movabletype-plugin-zemanta_4.3.7+dfsg-1_all.deb to main/m/movabletype-opensource/movabletype-plugin-zemanta_4.3.7+dfsg-1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 631...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves d...@earth.li (supplier of updated movabletype-opensource 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: Thu, 23 Jun 2011 22:53:29 +0100 Source: movabletype-opensource Binary: movabletype-opensource movabletype-plugin-core movabletype-plugin-zemanta Architecture: source all Version: 4.3.7+dfsg-1 Distribution: unstable Urgency: high Maintainer: Dominic Hargreaves d...@earth.li Changed-By: Dominic Hargreaves d...@earth.li Description: movabletype-opensource - A well-known blogging engine movabletype-plugin-core - Core Movable Type plugins movabletype-plugin-zemanta - Zemanta Movable Type plugin Closes: 631437 Changes: movabletype-opensource (4.3.7+dfsg-1) unstable; urgency=high . * New upstream release - fixes information disclosure vulnerability (closes: #631437) Checksums-Sha1: ecfdcd4740dce1cb2c0d4724754e05b1525a756b 1275 movabletype-opensource_4.3.7+dfsg-1.dsc 315299dd8cc121cbb0f7a3ab943f7b54b9f97f01 4739190 movabletype-opensource_4.3.7+dfsg.orig.tar.gz 12500753768d1bf0b67e96027d0088ee61893895 29020 movabletype-opensource_4.3.7+dfsg-1.debian.tar.gz 3b2e61f944dd638e3e256621e00c72204221bf8f 2897122 movabletype-opensource_4.3.7+dfsg-1_all.deb 111e061fb1b79662943893173c27f6687b2406b7 170588 movabletype-plugin-core_4.3.7+dfsg-1_all.deb 272beaf12906d0f02d5825301a5a76523bd4582c 14760 movabletype-plugin-zemanta_4.3.7+dfsg-1_all.deb Checksums-Sha256: d131c10084a83fb0f0706e52dc4773ebb7ac3ff9eb1d943a22a1c00aa373bebd 1275 movabletype-opensource_4.3.7+dfsg-1.dsc e22ef99817907c03165137d8b7391d084d2ebc3b449baffce8626237fbb54be9 4739190 movabletype-opensource_4.3.7+dfsg.orig.tar.gz 5e44dd248d4d4573ec7be8ec764a87c0fe15feed3fdfa8ceb3b05741b85ab071 29020 movabletype-opensource_4.3.7+dfsg-1.debian.tar.gz 023b0b8c4cfc50a1b2df41a586ee0258bb89417c44da43527f3671cb1c88b9f6 2897122
Processed: unblock 622279 with 621829 626020 628831
Processing commands for cont...@bugs.debian.org: # not in testing: ggz-python, zookeeper, wiican unblock 622279 with 621829 626020 628831 Bug #622279 [release.debian.org] transition: python-defaults (switching default: 2.6 - 2.7) Was blocked by: 628860 629085 621829 628243 625676 623587 622966 623578 629087 625171 606363 622912 625153 624917 625040 624940 621879 625880 625027 624824 625151 624901 621993 626800 618094 624975 599127 622976 614498 608640 622154 628827 553961 625677 625108 629091 623418 622001 618055 622072 625722 625853 628831 622070 626020 621992 555767 625137 606006 624810 616364 626259 605875 623165 621402 628820 625678 622978 618084 628826 553930 624889 621948 628830 629122 624787 626199 628839 629817 623927 625707 624950 625115 554552 629148 628852 629145 624740 626421 618159 629090 606681 622027 625011 624811 626416 624982 606642 625679 624597 625087 625135 610777 628828 624429 621932 Removed blocking bug(s) of 622279: 621829, 628831, and 626020 thanks Stopping processing here. Please contact me if you need assistance. -- 622279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631445: asterisk; AST-2011-009 - crash on malformed SIP packet
Package: asterisk Version: 1:1.8.4.2-1 Severity: grave Tags: security upstream patch Justification: user security hole A remote user sending a SIP packet containing a Contact header with a missing left angle bracket () causes Asterisk to access a null pointer. This applies only to Asterisk 1.8 in Wheezy/Sid and not to the versions in Squeeze and in Lenny. For more information, see http://downloads.asterisk.org/pub/security/AST-2011-009.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631446: asterisk: AST-2011-008 (CVE-2011-2529) - remote unauthenticated (null character)
Package: asterisk Version: 1:1.8.4.2-1 Severity: grave Tags: security upstream patch Justification: user security hole If a remote user sends a SIP packet containing a null, Asterisk assumes available data extends past the null to the end of the packet when the buffer is actually truncated when copied. This causes SIP header parsing to modify data past the end of the buffer altering unrelated memory structures. This vulnerability does not affect TCP/TLS connections. Issue applies to the versions in Squeeze and Wheezy/Sid, but not to Asterisk version 1.4 in Lenny. For more information, see http://downloads.asterisk.org/pub/security/AST-2011-008.html (for patches as well) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages asterisk depends on: ii adduser 3.112+nmu2 add and remove users and groups ii asterisk-config 1:1.8.4.2-1 Configuration files for Asterisk ii asterisk-modules1:1.8.4.2-1 loadable modules for the Asterisk ii asterisk-sounds-mai 1:1.6.2.9-2+squeeze1 Core Sound files for Asterisk (Eng ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libcap2 1:2.21-1 support for getting/setting POSIX. ii libgcc1 1:4.6.0-10 GCC support library ii libncurses5 5.9-1shared libraries for terminal hand ii libssl1.0.0 1.0.0d-2 SSL shared libraries ii libstdc++6 4.6.0-10 The GNU Standard C++ Library v3 ii libxml2 2.7.8.dfsg-3 GNOME XML library Versions of packages asterisk recommends: ii asterisk-moh-opsound-gsm 2.03-1 asterisk extra sound files - Engli ii asterisk-voicemail 1:1.8.4.2-1 simple voicemail support for the A ii sox 14.3.2-1Swiss army knife of sound processi Versions of packages asterisk suggests: pn asterisk-dahdi none (no description available) ii asterisk-dev 1:1.8.4.2-1 Development files for Asterisk ii asterisk-doc 1:1.8.4.2-1 Source code documentation for Aste pn asterisk-ooh323 none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631448: asterisk: AST-2011-010 (CVE-2011-2535) - crash due to using remote pointers
Package: asterisk Version: 1:1.8.4.2-1 Severity: grave Tags: security upstream patch Justification: user security hole A memory address was inadvertently transmitted over the network via IAX2 via an option control frame and the remote party would try to access it. This applies only to version 1.8 in Wheezy/Sid and not to the versions in Lenny and Squeeze. The advisory does apply to some newer versions of Asterisk 1.4 and 1.6.2, but not to the older versions used in Lenny and Squeeze, respectively. For more information, see http://downloads.asterisk.org/pub/security/AST-2011-010.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625094: marked as done (dmtcp: FTBFS: dmtcpalloc.h:52:13: error: 'ptrdiff_t' does not name a type)
Your message dated Thu, 23 Jun 2011 19:57:19 -0400 with message-id banlktikwbykq7dkng7u_q2nchyeyv0x...@mail.gmail.com and subject line Re: Bug#625094: dmtcp: FTBFS: dmtcpalloc.h:52:13: error: 'ptrdiff_t' does not name a type has caused the Debian Bug report #625094, regarding dmtcp: FTBFS: dmtcpalloc.h:52:13: error: 'ptrdiff_t' does not name a type 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.) -- 625094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dmtcp Version: 1.2.1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110502 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: g++ -DHAVE_CONFIG_H -I.-fPIC -g -O2 -MT connectionstate.o -MD -MP -MF .deps/connectionstate.Tpo -c -o connectionstate.o connectionstate.cpp In file included from connectionstate.h:25:0, from connectionstate.cpp:23: dmtcpalloc.h:52:13: error: 'ptrdiff_t' does not name a type In file included from /usr/include/c++/4.6/string:54:0, from dmtcpalloc.h:29, from connectionstate.h:25, from connectionstate.cpp:23: /usr/include/c++/4.6/bits/basic_string.h: In instantiation of 'std::basic_stringchar, std::char_traitschar, dmtcp::DmtcpAllocchar ': /usr/include/c++/4.6/sstream:75:50: instantiated from 'std::basic_stringbufchar, std::char_traitschar, dmtcp::DmtcpAllocchar ' /usr/include/c++/4.6/sstream:392:24: instantiated from 'std::basic_ostringstreamchar, std::char_traitschar, dmtcp::DmtcpAllocchar ' ../jalib/jassert.h:126:28: instantiated from here /usr/include/c++/4.6/bits/basic_string.h:117:61: error: no type named 'difference_type' in 'std::basic_stringchar, std::char_traitschar, dmtcp::DmtcpAllocchar ::_CharT_alloc_type' make[3]: *** [connectionstate.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/05/02/dmtcp_1.2.1-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- dmtcp_1.2.1-2 contains the fix for this bug. Closing it. --Kapil ---End Message---
Bug#629776: RFS: UPDATE: geda-xgsch2pcb 0.1.3-2
On Thursday, June 23, 2011 07:04:36 أحمد المحمودي wrote: Please sponsor the updated package geda-xgsch2pcb. It closes bug: 629776 I will take care of uploading this. Thanks for your work! signature.asc Description: This is a digitally signed message part.
Bug#629776: marked as done (geda-xgsch2pcb: FTBFS: unsatisfiable build-dependency: python-gtk2 ( 2.10) but 2.24.0-2 is to be installed)
Your message dated Fri, 24 Jun 2011 02:47:11 + with message-id e1qzwqj-0008gx...@franck.debian.org and subject line Bug#629776: fixed in geda-xgsch2pcb 0.1.3-2 has caused the Debian Bug report #629776, regarding geda-xgsch2pcb: FTBFS: unsatisfiable build-dependency: python-gtk2 ( 2.10) but 2.24.0-2 is to be installed 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.) -- 629776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: geda-xgsch2pcb Version: 0.1.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110607 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ┌──┐ │ Install geda-xgsch2pcb build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-geda-xgsch2pcb-dummy : Depends: python-gtk2 ( 2.10) but 2.24.0-2 is to be installed E: Broken packages The full build log is available from: http://people.debian.org/~lucas/logs/2011/06/07/geda-xgsch2pcb_0.1.3-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: geda-xgsch2pcb Source-Version: 0.1.3-2 We believe that the bug you reported is fixed in the latest version of geda-xgsch2pcb, which is due to be installed in the Debian FTP archive: geda-xgsch2pcb_0.1.3-2.debian.tar.gz to main/g/geda-xgsch2pcb/geda-xgsch2pcb_0.1.3-2.debian.tar.gz geda-xgsch2pcb_0.1.3-2.dsc to main/g/geda-xgsch2pcb/geda-xgsch2pcb_0.1.3-2.dsc geda-xgsch2pcb_0.1.3-2_all.deb to main/g/geda-xgsch2pcb/geda-xgsch2pcb_0.1.3-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 629...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@sabily.org (supplier of updated geda-xgsch2pcb 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: Thu, 23 Jun 2011 14:17:50 +0200 Source: geda-xgsch2pcb Binary: geda-xgsch2pcb Architecture: source all Version: 0.1.3-2 Distribution: unstable Urgency: low Maintainer: Debian Electronics Team pkg-electronics-de...@lists.alioth.debian.org Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@sabily.org Description: geda-xgsch2pcb - GPL EDA -- Electronics design software -- gschem - PCB workflow Closes: 629776 Changes: geda-xgsch2pcb (0.1.3-2) unstable; urgency=low . * debian/control: + Updated my email address + Added DMUA after sponsors consent (http://lists.alioth.debian.org/pipermail/pkg-electronics-devel/2010-April/001827.html) + Bumped Standards-Version to 3.9.2 + Depend/Build-Dep on python-gobject | python-gtk2 (2.10) to fix FTBFS on wheezy (Closes: #629776) * Removed debian/pyversions * Bumped compat level to 8 * Converted to 3.0 (quilt) source format. Checksums-Sha1: eb12ba4895e4fe8ddaff63c933399bd04aedc93d 1616 geda-xgsch2pcb_0.1.3-2.dsc 904f9d6e42d37d9d22641e47c03a3d811903b11b 3903 geda-xgsch2pcb_0.1.3-2.debian.tar.gz 53e1f25dd4b4a36e1f95a3cf78e4528477224577 47882 geda-xgsch2pcb_0.1.3-2_all.deb
Processed: Re: Bug#631452: Acknowledgement (Does not find libraries from multiarch directories)
Processing commands for cont...@bugs.debian.org: severity 631452 serious Bug #631452 [gobject-introspection] Does not find libraries from multiarch directories Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 631452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631452 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
