Bug#635938: emacs23: Missing sources, violates GPL, non-distributable
On 2011-07-29 23:56 +0200, Rob Browning wrote: Julian Andres Klode j...@debian.org writes: emacs23 includes parsers generated from bison grammars, but does not include the grammars itself, causing Debian to violate the GPL by distributing it. This bug is affecting all emacs version starting with 23.2 according to upstream. See http://lists.gnu.org/archive/html/emacs-devel/2011-07/msg01155.html for information. Thanks. It may be two weeks before I can handle this. I'll be traveling and may or may not have much net access. An NMU would be fine, if deemed appropriate. I had thought about working on one, based on the new tarballs that have just appeared on ftp.gnu.org. But since the recipe of creating the Debian .orig.tar.bz2 from upstream tarballs appears to be top secret, I'll refrain from doing so. Anyway, since I happened to have the original 23.3 tarball around, here is a summary of the differences between old and new: , | $ LANG=C diff -qr emacs-23.3.old emacs-23.3 | Only in emacs-23.3/etc: grammars | Files emacs-23.3.old/lisp/cedet/semantic/bovine/c-by.el and emacs-23.3/lisp/cedet/semantic/bovine/c-by.el differ | Files emacs-23.3.old/lisp/cedet/semantic/bovine/make-by.el and emacs-23.3/lisp/cedet/semantic/bovine/make-by.el differ | Files emacs-23.3.old/lisp/cedet/semantic/bovine/scm-by.el and emacs-23.3/lisp/cedet/semantic/bovine/scm-by.el differ | Files emacs-23.3.old/lisp/cedet/semantic/wisent/js-wy.el and emacs-23.3/lisp/cedet/semantic/wisent/js-wy.el differ | Files emacs-23.3.old/lisp/cedet/semantic/wisent/python-wy.el and emacs-23.3/lisp/cedet/semantic/wisent/python-wy.el differ ` Full diff is attached. Cheers, Sven emacs-23.3.diff.bz2 Description: Binary data
Bug#636077: marked as done ([firmware-b43-installer] Firmware-b43-installer fails on recognized chip after upgrade to linux 3.0)
Your message dated Mon, 01 Aug 2011 07:02:14 + with message-id e1qnmvy-00065r...@franck.debian.org and subject line Bug#636077: fixed in b43-fwcutter 1:014-6 has caused the Debian Bug report #636077, regarding [firmware-b43-installer] Firmware-b43-installer fails on recognized chip after upgrade to linux 3.0 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.) -- 636077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-b43-installer Version: 1:014-5 Severity: grave --- Please enter the report below this line. --- --- System information. --- Architecture: powerpc Kernel: Linux 3.0.0-1-powerpc Debian Release: wheezy/sid 500 unstableftp.es.debian.org 500 unstableftp.debian-multimedia.org 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-= b43-fwcutter (= 1:014-5) | 1:014-5 bzip2 | 1.0.5-6 wget | 1.12-5 Recommends (Version) | Installed ==-+-=== linux-image| Package's Suggests field is empty. Hello: After last upgrade, on Sid, to Linux 3.0, firmware-b43-installer fails on recognized chip card and suggest to install firmware-b43legacy-installer. --- Cut from console - Configurando firmware-b43-installer (1:014-5) ... An unsupported BCM4301, BCM4303, BCM4306 or BCM4306/2 device was found. Use b43legacy firmware (firmware-b43legacy-installer package) instead. Aborting. end of cut My chip card is BCM4306 rev3: 0001:10:12.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Apple Computer Inc. AirPort Extreme [106b:004e] Flags: bus master, fast devsel, latency 16, IRQ 52 Memory at a0006000 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] Power Management version 2 Kernel driver in use: b43-pci-bridge mark as b43 firmware on http://wireless.kernel.org/en/users/Drivers/b43#device_firmware_installation Before read it, I was think that firmware is move to b43legacy on new versions and try to install it, I fall on b43-phy0 ERROR: YOUR FIRMWARE IS TOO OLD fail. Installing firmware manually, wifi runs again. Please, tell me if you need some more data. Salud y Revolución. Lobo. -- Libertad es poder elegir en cualquier momento. Ahora yo elijo GNU/Linux, para no atar mis manos con las cadenas del soft propietario. - Desde El Ejido, en Almería, usuario registrado Linux #294013 http://www.counter.li.org ---End Message--- ---BeginMessage--- Source: b43-fwcutter Source-Version: 1:014-6 We believe that the bug you reported is fixed in the latest version of b43-fwcutter, which is due to be installed in the Debian FTP archive: b43-fwcutter_014-6.debian.tar.gz to contrib/b/b43-fwcutter/b43-fwcutter_014-6.debian.tar.gz b43-fwcutter_014-6.dsc to contrib/b/b43-fwcutter/b43-fwcutter_014-6.dsc b43-fwcutter_014-6_amd64.deb to contrib/b/b43-fwcutter/b43-fwcutter_014-6_amd64.deb firmware-b43-installer_014-6_all.deb to contrib/b/b43-fwcutter/firmware-b43-installer_014-6_all.deb firmware-b43-lpphy-installer_014-6_all.deb to contrib/b/b43-fwcutter/firmware-b43-lpphy-installer_014-6_all.deb firmware-b43legacy-installer_014-6_all.deb to contrib/b/b43-fwcutter/firmware-b43legacy-installer_014-6_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 636...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabrizio Regalli fab...@fabreg.it (supplier of updated b43-fwcutter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 31 Jul 2011 01:40:29 +0200 Source: b43-fwcutter Binary: b43-fwcutter firmware-b43-installer firmware-b43-lpphy-installer firmware-b43legacy-installer Architecture: source all amd64 Version: 1:014-6 Distribution: unstable Urgency: low Maintainer: Fabrizio Regalli fab...@fabreg.it Changed-By: Fabrizio Regalli fab...@fabreg.it
Bug#618239: ijs: FTBFS: /bin/bash: ijs_spec.ps: command not found
On Sun, Mar 13, 2011 at 06:40:50PM +0100, Lucas Nussbaum wrote:
Source: ijs
Version: 0.35-7
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110313 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[1]: Entering directory `/build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35'
/usr/bin/db2ps ijs_spec.sgml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35/ijs_spec.sgml
x -i print -d /usr/share/docbook-utils/docbook-utils.dsl#print -V
paper-type=A4 /build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35/ijs_spec.sgml
Done.
ijs_spec.ps
/bin/bash: ijs_spec.ps: command not found
make[1]: *** [ijs_spec.pdf] Error 127
I have just done an NMU to fix this longstanding issue. Please find the
diff below.
diff -u ijs-0.35/debian/changelog ijs-0.35/debian/changelog
--- ijs-0.35/debian/changelog
+++ ijs-0.35/debian/changelog
@@ -1,3 +1,10 @@
+ijs (0.35-7.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Build-Depend on ghostscript. Closes: #618239.
+
+ -- Aurelien Jarno aure...@debian.org Mon, 01 Aug 2011 09:14:55 +0200
+
ijs (0.35-7) unstable; urgency=low
* Update config.{sub,guess}.
diff -u ijs-0.35/debian/control ijs-0.35/debian/control
--- ijs-0.35/debian/control
+++ ijs-0.35/debian/control
@@ -2,7 +2,7 @@
Section: text
Priority: optional
Maintainer: Bradley Smith bradsm...@debian.org
-Build-Depends: debhelper (= 7), gs-common, docbook, docbook-utils,
autotools-dev
+Build-Depends: debhelper (= 7), ghostscript, gs-common, docbook,
docbook-utils, autotools-dev
Standards-Version: 3.8.1
Homepage: http://www.linuxprinting.org/ijs/
Vcs-Git: http://git.brad-smith.co.uk/git/debian/pkg-ijs.git
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618239: marked as done (ijs: FTBFS: /bin/bash: ijs_spec.ps: command not found)
Your message dated Mon, 01 Aug 2011 07:33:01 + with message-id e1qnmzl-0008jo...@franck.debian.org and subject line Bug#618239: fixed in ijs 0.35-7.1 has caused the Debian Bug report #618239, regarding ijs: FTBFS: /bin/bash: ijs_spec.ps: command not 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.) -- 618239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ijs Version: 0.35-7 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110313 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35' /usr/bin/db2ps ijs_spec.sgml Using catalogs: /etc/sgml/catalog Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print Working on: /build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35/ijs_spec.sgml x -i print -d /usr/share/docbook-utils/docbook-utils.dsl#print -V paper-type=A4 /build/user-ijs_0.35-7-amd64-FNpjj_/ijs-0.35/ijs_spec.sgml Done. ijs_spec.ps /bin/bash: ijs_spec.ps: command not found make[1]: *** [ijs_spec.pdf] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2011/03/13/ijs_0.35-7_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: ijs Source-Version: 0.35-7.1 We believe that the bug you reported is fixed in the latest version of ijs, which is due to be installed in the Debian FTP archive: ijs_0.35-7.1.diff.gz to main/i/ijs/ijs_0.35-7.1.diff.gz ijs_0.35-7.1.dsc to main/i/ijs/ijs_0.35-7.1.dsc libijs-0.35_0.35-7.1_amd64.deb to main/i/ijs/libijs-0.35_0.35-7.1_amd64.deb libijs-dev_0.35-7.1_amd64.deb to main/i/ijs/libijs-dev_0.35-7.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 618...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aurelien Jarno aure...@debian.org (supplier of updated ijs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 01 Aug 2011 09:14:55 +0200 Source: ijs Binary: libijs-dev libijs-0.35 Architecture: source amd64 Version: 0.35-7.1 Distribution: unstable Urgency: low Maintainer: Bradley Smith bradsm...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: libijs-0.35 - IJS raster image transport protocol: shared library libijs-dev - IJS raster image transport protocol: development files Closes: 618239 Changes: ijs (0.35-7.1) unstable; urgency=low . * Non-maintainer upload. * Build-Depend on ghostscript. Closes: #618239. Checksums-Sha1: 93981146b0f33e1502f4adeeaec8d5dd39e759c2 1156 ijs_0.35-7.1.dsc 53df06b6540c9bb02b386fe68308758271baeeda 3971 ijs_0.35-7.1.diff.gz 39b91ffd315f94a920be2fbb6af65656eca5c89d 90034 libijs-dev_0.35-7.1_amd64.deb aa9082b1900a3bf87e72cd5187856cfc62831d86 15814 libijs-0.35_0.35-7.1_amd64.deb Checksums-Sha256: a4cc6f09bbb713396793525001c05eb6fb9c7acc37af0e7a965ebe4b221943fa 1156 ijs_0.35-7.1.dsc cf65310f445c275c907f4dfe7067a6691f266dc8b3f13f110dec5e33a2ff82ab 3971 ijs_0.35-7.1.diff.gz eda029e545d6c319f772838e1b4799173b7d4250dfd98630fdcacd636b14f248 90034 libijs-dev_0.35-7.1_amd64.deb 4dc90769d6d673a2ff4d5b8ca747529ad120bdc70875360e81e51dc037af4cf4 15814 libijs-0.35_0.35-7.1_amd64.deb Files: bbb7ba77e8619b6bdc955548994f8d51 1156 text optional ijs_0.35-7.1.dsc 737a21e0988cbc325825fee07edcc0da 3971 text optional ijs_0.35-7.1.diff.gz 0837310e1eec78f31a24af3ba2c5ecde 90034 libdevel optional libijs-dev_0.35-7.1_amd64.deb f0a3bc495e8b3c553a3c48dc6f8fa724 15814 libs optional libijs-0.35_0.35-7.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux)
Bug#636188: xscorch: Please transition to use libreadline6-dev
Package: xscorch Severity: serious Please transition to use libreadline6-dev instead of libreadline5-dev, the readline maintainer has said everyone should use version 6 except your package's license does not allow. Package libreadline5-dev has gone from unstable, so your package on mentors.debian.net FTBFS because missing dependency and cannot be sponsored. Note: buildd only consider the first candidate in Build-Depends list, which means libreadline5-dev | libreadline6-dev in build-dep equals to simply libreadline5-dev. Please drop me a line when you have updated it, don't forget to add RFS at the beginning of the mail's subject line. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636190: yubikey-personalization: FTBFS on many arches, tests fail
Package: yubikey-personalization Version: 1.5.1-1 Severity: serious According to https://buildd.debian.org/status/package.php?p=yubikey-personalizationsuite=unstable and http://buildd.debian-ports.org/status/package.php?p=yubikey-personalizationsuite=unstable your package fails to build on many arches. Please look into this. Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636193: wesnoth-1.9: FTBFS, undefined reference to SDLNet_Read32
Package: wesnoth-1.9 Version: 1:1.9.8-1 Severity: serious According to: https://buildd.debian.org/status/package.php?p=wesnoth-1.9suite=unstable the package fails to build because of a missing reference: wesnoth-1.9-1.9.8/src/network_worker.cpp:603: undefined reference to `SDLNet_Read32' Maybe this is is an SDL bug instead? Regards Konstantinos -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630268: [Evolution] Bug#630268: evolution: Please transition to libnotify 0.7
On jeu., 2011-07-21 at 10:47 +0200, Jérémy Bobbio wrote: tags 630268 + fixed-upstream thanks On Sun, Jun 12, 2011 at 09:38:07PM +0200, bi...@debian.org wrote: We are planning to transition[0] libnotify to version 0.7 which breaks its API. It looks like this has been fixed upstream in commit 8854c727c1c0 [1], included in releases since 2.91.2. [1] http://git.gnome.org/browse/evolution/commit/?id=8854c727c1c0 Well, yes, it's even fixed in experimental. I didn't touch anything in evolution 3 but it seems that it'll have to wait a bit more since gdata 0.7+ is not yet available in unstable (preventing evolution-data-server to be built, and thus evolution). Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#633789: guake: Guake doesnt start at all - Confirmed
I updated my SID to latest packages and fall in this bug. -- Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633789: guake: Guake doesnt start at all - Confirmed
Le lundi 01 août 2011 à 10:57 +0200, Daniel Huhardeaux a écrit : I updated my SID to latest packages and fall in this bug. I have libnotify4 version 0.7.3-2 installed and guake is working without any problem. (but i am running testing with some sid packages) Do you know which other packages have been updated ? S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633789: guake: Guake doesnt start at all - Confirmed
Le 01/08/2011 11:27, Sylvestre Ledru a écrit : Le lundi 01 août 2011 à 10:57 +0200, Daniel Huhardeaux a écrit : I updated my SID to latest packages and fall in this bug. I have libnotify4 version 0.7.3-2 installed and guake is working without any problem. (but i am running testing with some sid packages) Do you know which other packages have been updated ? A lot :-( From aptitude show guake - depend -rw-r--r-- 1 root root 4322668 31 juil. 05:32 libc6_2.13-13_amd64.deb -rw-r--r-- 1 root root 947652 29 juil. 19:17 libcairo2_1.10.2-6.1_amd64.deb -rw-r--r-- 1 root root 660248 28 juil. 19:03 libgdk-pixbuf2.0-0_2.23.5-3_amd64.deb -rw-r--r-- 1 root root 7214968 28 juil. 17:02 libgtk2.0-common_2.24.5-4_all.deb -rw-r--r-- 1 root root 440140 29 juil. 18:47 libpango1.0-0_1.28.4-2_amd64.deb -rw-r--r-- 1 root root 888958 30 juil. 23:06 libx11-6_2%3a1.4.4-1_amd64.deb -rw-r--r-- 1 root root59918 31 juil. 01:03 notification-daemon_0.7.1-3_amd64.deb -rw-r--r-- 1 root root29852 31 juil. 00:32 libnotify4_0.7.3-2_amd64.deb -rw-r--r-- 1 root root 175454 28 juil. 01:47 python_2.6.7-2_all.deb -rw-r--r-- 1 root root 250410 25 juil. 18:17 python-dbus_0.84.0-2_amd64.deb Regards -- Daniel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): change severity
Processing commands for cont...@bugs.debian.org: # Severity justification: makes package uninstallable severity 635456 grave Bug #635456 [redmine] redmine configure fails with recent rails upgrade Severity set to 'grave' from 'important' # Reporter's request to merge merge 635456 635460 Bug#635456: redmine configure fails with recent rails upgrade Bug#635460: redmine configure fails with recent rails upgrade Mismatch - only Bugs in same state can be merged: Values for `severity' don't match: #635456 has `grave'; #635460 has `important' thanks Stopping processing here. Please contact me if you need assistance. -- 635460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635460 635456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635456 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: severity change
Processing commands for cont...@bugs.debian.org: # Severity justification: makes package uninstallable severity 635460 grave Bug #635460 [redmine] redmine configure fails with recent rails upgrade Severity set to 'grave' from 'important' # Reporter's request to merge merge 635456 635460 Bug#635456: redmine configure fails with recent rails upgrade Bug#635460: redmine configure fails with recent rails upgrade Merged 635456 635460. thanks Stopping processing here. Please contact me if you need assistance. -- 635456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635456 635460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635460 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#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory
Package: flightgear Version: 2.0.0-4 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, flightgear appears to be FTBFS on several architectures with the following: [...] mv -f .deps/hud_labl.Tpo .deps/hud_labl.Po g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -MT hud_ladr.o -MD -MP -MF .deps/hud_ladr.Tpo -c -o hud_ladr.o hud_ladr.cxx mv -f .deps/hud_ladr.Tpo .deps/hud_ladr.Po g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -MT hud_rwy.o -MD -MP -MF .deps/hud_rwy.Tpo -c -o hud_rwy.o hud_rwy.cxx hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory compilation terminated. make[4]: *** [hud_rwy.o] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 make[4]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit' make[3]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit' make[2]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src' See https://buildd.debian.org/status/package.php?p=flightgear ~Niels - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJONp5JAAoJEAVLu599gGRC1eAP/3/hH46eGwuNywNhbmDgLzhY 5xQqjtfJQ76gCK64HlVbRa/3Ytej57FB8MDvfedDEseLsCMHR1vjKEMxjf1ozKBv NmTHR6aml6aRxAFK/WV3x+ZyWgUhheaXGAGOd4e9wErnFTD2FapTDwl+qzzjac1+ +cvG4HWsk2QtBXtveoY2IP0wRBtU2vG27Y2ISejyuzTbEugjm2eKbM2PEDJPfExO tlJ5jEpT0tOglT0rrg18dmR30LffTRJ3a4GmGPNZ8cJffHVAxQPvZfhCiM0JD1YE MU5AVTPHYzT2gprWUtSiQmbMytVJKvMiHsadqfNww+iHVbRnReUorU85E5gopdg6 hkf0DyQtT8MvNAJ1SLMTndyeOMQBZ6bb35V1pooq2mjEXNBZAm48qA51Mkakv3Ji Ffk1wvt8U3zKdoU5piKCIfB0uYEHy3wYqctMC5povh7+sLcHXDkx2rP2Em1c3S5t 2rRl6ba29iw7VWpvjRmytESzlAnPlzNlfP6cGpZ1P9J2P5VqiQK4u6VG8K2xjTBz 386ZwTdWCPxgZnQAki3DjAsBnJjpMoMdgsGQMul0hH4nY2UUFf8dPRNAdj3oyZEU qGGiqWuUP9HxePR6CD+1lNPpnVmupVfXbNHFr/Fykq0RpcDqJnOApY0NGJ93SvbP Xd2ZxZSZ811XQQ2y9K3y =7Mk0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636188: xscorch: Please transition to use libreadline6-dev
# Not including a version on RC bugs _really_ isn't helpful # Setting to the current testing / unstable version, as this # won't be changed in stable found 636188 0.2.1~pre2-3 thanks On Mon, 2011-08-01 at 15:43 +0800, Aron Xu wrote: Package: xscorch Severity: serious This should have been filed with an affected version; see above. Please transition to use libreadline6-dev instead of libreadline5-dev, the readline maintainer has said everyone should use version 6 except your package's license does not allow. Package libreadline5-dev has gone from unstable, so your package on mentors.debian.net FTBFS because missing dependency and cannot be sponsored. The copyright file of the version of xscorch currently in the archive says that the software is released under GPL-2 only. Assuming that's correct, then it's not possible to link it against the GPL-3 licensed libreadline6. Regards, Adam -- 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#636188: xscorch: Please transition to use libreadline6-dev
Processing commands for cont...@bugs.debian.org: # Not including a version on RC bugs _really_ isn't helpful # Setting to the current testing / unstable version, as this # won't be changed in stable found 636188 0.2.1~pre2-3 Bug #636188 [xscorch] xscorch: Please transition to use libreadline6-dev Bug Marked as found in versions xscorch/0.2.1~pre2-3. thanks Stopping processing here. Please contact me if you need assistance. -- 636188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636188 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#636188: xscorch: Please transition to use libreadline6-dev
retitle 636188 Please use libreadline-gplv2-dev instead of libreadline5-dev thanks On Mon, Aug 1, 2011 at 20:51, Adam D. Barratt a...@adam-barratt.org.uk wrote: # Not including a version on RC bugs _really_ isn't helpful # Setting to the current testing / unstable version, as this # won't be changed in stable found 636188 0.2.1~pre2-3 thanks On Mon, 2011-08-01 at 15:43 +0800, Aron Xu wrote: Package: xscorch Severity: serious This should have been filed with an affected version; see above. Please read again what I have written in the first message. It's not a report for your packages in the archive, but for your package on mentors.debian.net. Please transition to use libreadline6-dev instead of libreadline5-dev, the readline maintainer has said everyone should use version 6 except your package's license does not allow. Package libreadline5-dev has gone from unstable, so your package on mentors.debian.net FTBFS because missing dependency and cannot be sponsored. The copyright file of the version of xscorch currently in the archive says that the software is released under GPL-2 only. Assuming that's correct, then it's not possible to link it against the GPL-3 licensed libreadline6. Then you are still wrong, because libreadline5-dev is gone, your package FTBFS. Please check your package with pbuilder before you upload and ask for sponsoring. What you really need is libreadline-gplv2-dev, not libreadline5-dev (gone from archive), nor libreadline6-dev (license issue). Again, please check your package is buildable with pbuilder/cowbuilder or even in a plain sid chroot. As the package's maintainer, it's your responsibility to make sure all of the problems do not exist before you ask for sponsorship. Please make sure you have read and understand what I've written, if you have questions just ask back and I'll try to help. I'll be happy to sponsor your package when you have made it fit. -- Regards, Aron Xu -- 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#636188: xscorch: Please transition to use libreadline6-dev
Processing commands for cont...@bugs.debian.org: retitle 636188 Please use libreadline-gplv2-dev instead of libreadline5-dev Bug #636188 [xscorch] xscorch: Please transition to use libreadline6-dev Changed Bug title to 'Please use libreadline-gplv2-dev instead of libreadline5-dev' from 'xscorch: Please transition to use libreadline6-dev' thanks Stopping processing here. Please contact me if you need assistance. -- 636188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636188 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#636188: xscorch: Please transition to use libreadline6-dev
Well, I should apologize that Adam is not the maintainer of this package. But the maintainer surely has the responsibility of checking the package builds. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636210: [pkg-fgfs-crew] Bug#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory
On 08/01/2011 02:38 PM, Niels Thykier wrote: Hi, flightgear appears to be FTBFS on several architectures with the following: I suppose they need to be built against simgear-dev = 2.0.0-3, not simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just to force the build-dep version, or is it enough to just wait for the buildds to build the newest simgear and flightgear after that? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636188: xscorch: Please transition to use libreadline6-dev
On Mon, 2011-08-01 at 21:07 +0800, Aron Xu wrote: In Mon, Aug 1, 2011 at 20:51, Adam D. Barratt a...@adam-barratt.org.uk wrote: On Mon, 2011-08-01 at 15:43 +0800, Aron Xu wrote: Package: xscorch Severity: serious This should have been filed with an affected version; see above. Please read again what I have written in the first message. It's not a report for your packages in the archive, but for your package on mentors.debian.net. That's irrelevant. The bug as you filed it applies to _all versions of the package in Debian_, which is wrong and will just annoy the Release Team (as this message indicates...). Either don't use the BTS to file issues which only affect mentors.d.n packages, or use sane found versions. If the bug doesn't apply to any version currently in the archive, then please close it now and use an alternative means to contact the maintainer; the BTS is for tracking issues with packages in Debian. Also, as looking at the package for slightly longer would have shown, *I'm not the maintainer*. [...] The copyright file of the version of xscorch currently in the archive says that the software is released under GPL-2 only. Assuming that's correct, then it's not possible to link it against the GPL-3 licensed libreadline6. Then you are still wrong, because libreadline5-dev is gone, your package FTBFS. Please check your package with pbuilder before you upload and ask for sponsoring. Again, it's not my package, and I'm not wrong. And yes, libreadline5-dev is gone and many people (including at least parts of the release team) aren't overly happy about that. Please make sure you have read and understand what I've written, if you have questions just ask back and I'll try to help. I'll be happy to sponsor your package when you have made it fit. *giggle* Please also make sure you understand what I wrote. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636210: [pkg-fgfs-crew] Bug#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory
On 2011-08-01 15:09, Ove Kåven wrote: On 08/01/2011 02:38 PM, Niels Thykier wrote: Hi, flightgear appears to be FTBFS on several architectures with the following: I suppose they need to be built against simgear-dev = 2.0.0-3, not simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just to force the build-dep version, or is it enough to just wait for the buildds to build the newest simgear and flightgear after that? The can be scheduled against simgear-dev = 2.0.0-3; I have asked for a give-back on affected architectures and will follow up once the builds complete. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636147: jupp: removes /etc/joe/editorrc, breaking joe
Piotr Engelking dixit: Jupp hijacks the editorrc alternative from joe, moving it from /etc/joe/editorrc to /etc/jupp/editorrc. This breaks joe if it is set Do you think it would work if I just add /etc/jupp/editorrc@ - ../joe/editorrc and then manage /etc/joe/editorrc with update-alternatives just like joe does? bye, //mirabilos -- ch you introduced a merge commit│mika % g rebase -i HEAD^^ mika sorry, no idea and rebasing just fscked │mika Segmentation ch should have cloned into a clean repo │ fault (core dumped) ch if I rebase that now, it's really ugh │mika:#grml wuahh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636215: translation pane not shown
Package: gtranslator Version: 2.90.5-2 Severity: grave After the upgrade from version 1.9.11-1 to version 2.90.5-2, gtranslator no longer shows. Where it used to be now is only empty space. The navigation buttons seem to work, as indicated on the status bar. See attached image. This makes gtranslator useless, as no translation can be viewed/modified. There are two messages on the terminal: Gtk-Message: Failed to load module gnomebreakpad (gtranslator:27015): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.utf8, LC_CTYPE=bg_BG.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gtranslator depends on: ii dconf-gsettings-backend [gs 0.7.5-3 simple configuration storage syste ii gettext [libgettextpo0] 0.18.1.1-3 GNU Internationalization utilities ii gir1.2-atk-1.0 2.0.1-2 ATK accessibility toolkit (GObject ii gir1.2-freedesktop 0.10.8-2 Introspection data for some FreeDe ii gir1.2-gdkpixbuf-2.02.23.5-3 GDK Pixbuf library - GObject-Intro ii gir1.2-glib-2.0 0.10.8-2 Introspection data for GLib, GObje ii gir1.2-gtk-3.0 3.0.12-1 GTK+ graphical user interface libr ii gir1.2-gtksource-3.03.0.4-1 gir files for the GTK+ syntax high ii gir1.2-gucharmap-2.90 1:3.0.1-1GObject introspection data for the ii gir1.2-pango-1.01.28.4-2 Layout and rendering of internatio ii gir1.2-peas-1.0 1.1.0-1 Application plugin library (intros ii gsettings-desktop-schemas 3.0.1-1 GSettings deskop-wide schemas ii iso-codes 3.27-1 ISO language, territory, currency, ii libatk1.0-0 2.0.1-2 ATK accessibility toolkit ii libc6 2.13-13 Embedded GNU C Library: Shared lib ii libcairo-gobject2 1.10.2-6.1 The Cairo 2D vector graphics libra ii libcairo2 1.10.2-6.1 The Cairo 2D vector graphics libra ii libffi5 3.0.9-7 Foreign Function Interface library ii libfontconfig1 2.8.0-3 generic font configuration library ii libfreetype62.4.4-2 FreeType 2 font engine, shared lib ii libgda-4.0-44.2.8-2 data abstraction library based on ii libgdict-1.0-6 3.0.1-5 GNOME Dictionary base library - ru ii libgdk-pixbuf2.0-0 2.23.5-3 GDK Pixbuf library ii libgdl-3-1 3.0.2-1 GNOME DevTool libraries ii libgirepository-1.0-1 0.10.8-2 Library for handling GObject intro ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgtk-3-0 3.0.12-1 GTK+ graphical user interface libr ii libgtksourceview-3.0-0 3.0.4-1 shared libraries for the GTK+ synt ii libjson-glib-1.0-0 0.13.4-2 GLib JSON manipulation library ii libpango1.0-0 1.28.4-2 Layout and rendering of internatio ii libpeas-1.0-0 1.1.0-1 Application plugin library ii libxml2 2.7.8.dfsg-4 GNOME XML library ii python 2.6.7-2 interactive high-level object-orie ii python-support 1.0.14 automated rebuilding support for P gtranslator recommends no packages. gtranslator 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
Processed: tagging 634861
Processing commands for cont...@bugs.debian.org: tags 634861 + pending Bug #634861 [python-qscintilla2] Please switch python-qscintilla2 to dh_python2 Bug #636085 [python-qscintilla2] tortoisehg: Fails to start. Qsci module not found. Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 634861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634861 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#634198: hiredis: FTBFS (kfreebsd): Testsuite failures
Hi,
sorry for the late reply, I've been on holiday for the past couple of weeks.
On Sun, Jul 17, 2011 at 06:52:30PM +0200, Christoph Egger wrote:
Your package failed to build on the kfreebsd-* buildds:
#44 Can handle nested multi bulk replies: PASSED
#45 Returns I/O error when the connection is lost: PASSED
#46 Returns I/O error on socket timeout: PASSED
#47 Throughput:
(1000x PING: 0.038s)
(1000x LRANGE with 500 elements: 0.210s)
(1x PING (pipelined): 0.014s)
(1x LRANGE with 500 elements (pipelined): 1.922s)
*** 1 TESTS FAILED ***
make[2]: *** [test] Error 1
make[2]: Leaving directory
`/build/buildd-hiredis_0.10.1-2-kfreebsd-amd64-a6Qsiq/hiredis-0.10.1'
dh_auto_test: make -j1 test returned exit code 2
make[1]: *** [override_dh_auto_test] Error 29
make[1]: Leaving directory
`/build/buildd-hiredis_0.10.1-2-kfreebsd-amd64-a6Qsiq/hiredis-0.10.1'
make: *** [build] Error 2
Full build log at
https://buildd.debian.org/status/fetch.php?pkg=hiredisarch=kfreebsd-i386ver=0.10.1-2stamp=1309770541
Thanks for reporting, I think I'll disable that test in the next upload, if
I won't find any better solution.
Cheers
--
perl -E'$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636215: [gtranslator] translation pane not shown
-=| Damyan Ivanov, Mon, Aug 01, 2011 at 04:50:33PM +0300 |=- After the upgrade from version 1.9.11-1 to version 2.90.5-2, gtranslator no longer shows. Where it used to be now is only empty space. The navigation buttons seem to work, as indicated on the status bar. It appears this is not related to gtranslator upgrade, but to some of the dependencies. Downgrading gtranslator to 1.9.11-1 made no difference :/ Any ideas? signature.asc Description: Digital signature
Bug#622794: atop: diff for NMU version 1.23-1.1
tags 622794 + patch
tags 622794 + pending
thanks
Dear maintainer,
I've prepared an NMU for atop (versioned as 1.23-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Be advised that if no problems are found, I will be applying to the Release
Team for permission to upload the same fixes to stable and oldstable.
Regards.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff -u atop-1.23/acctproc.c atop-1.23/acctproc.c
--- atop-1.23/acctproc.c
+++ atop-1.23/acctproc.c
@@ -126,7 +126,7 @@
#include photoproc.h
#include acctproc.h
-#define ACCTDIR /tmp/atop.d
+#define ACCTDIR /var/run/atop
#define ACCTFILE atop.acct
#define ACCTENV ATOPACCT
@@ -331,7 +331,7 @@
if (semctl(semid, 1, GETVAL, 0) == SEMTOTAL)
{
/*
- ** create a new separate directory below /tmp
+ ** create a new separate directory below /var/run
** for the accounting file;
** if this directory exists (e.g. previous atop-run killed)
** it will be cleaned and newly created
diff -u atop-1.23/debian/changelog atop-1.23/debian/changelog
--- atop-1.23/debian/changelog
+++ atop-1.23/debian/changelog
@@ -1,3 +1,10 @@
+atop (1.23-1.1) unstable; urgency=high
+
+ * Fix CVE-2011-: Insecure use of a temporary files rawlog.c and
+acctproc.c (Closes: #622794)
+
+ -- Jonathan Wiltshire j...@debian.org Mon, 01 Aug 2011 15:35:16 +0100
+
atop (1.23-1) unstable; urgency=low
* fixed typo (Closes: #467447)
diff -u atop-1.23/rawlog.c atop-1.23/rawlog.c
--- atop-1.23/rawlog.c
+++ atop-1.23/rawlog.c
@@ -477,18 +477,18 @@
*/
fprintf(stderr, Decompressing logfile \n);
- snprintf(tmpname2, sizeof tmpname2, /tmp/atopwrk%d, getpid());
- snprintf(command, sizeof command, gunzip -c %s %s,
- tmpname1, tmpname2);
- system (command);
+ snprintf(tmpname2, sizeof tmpname2, /tmp/atopwrkXX);
- if ( (rawfd = open(tmpname2, O_RDONLY)) == -1)
+ if ( (rawfd = mkstemp(tmpname2)) == -1)
{
fprintf(stderr, %s - , rawname);
perror(open decompressed raw file);
cleanstop(7);
}
+ snprintf(command, sizeof command, gunzip -c %s %s,
+ tmpname1, tmpname2);
+ system (command);
unlink(tmpname2);
}
signature.asc
Description: Digital signature
Processed: atop: diff for NMU version 1.23-1.1
Processing commands for cont...@bugs.debian.org: tags 622794 + patch Bug #622794 [atop] atop: vulnerable to symlink attack via insecure /tmp directory or file Added tag(s) patch. tags 622794 + pending Bug #622794 [atop] atop: vulnerable to symlink attack via insecure /tmp directory or file Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 622794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622794 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#554646: marked as done (FTBFS with binutils-gold)
Your message dated Mon, 01 Aug 2011 14:48:06 + with message-id e1qntmo-0007xk...@franck.debian.org and subject line Bug#554646: fixed in gnome-applets 2.30.0-4 has caused the Debian Bug report #554646, 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.) -- 554646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnome-applets Version: 2.28.0-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 /bin/bash ../libtool --tag=CC --mode=link cc -g -O2 -g -Wall -O2 -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -o stickynotes_applet util.o stickynotes.o stickynotes_callbacks.o stickynotes_applet.o stickynotes_applet_callbacks.o -pthread -lpanel-applet-2 -lgconf-2 -lbonoboui-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lbonobo-2 -lbonobo-activation -lgmodule-2.0 -lORBit-2 -lgthread-2.0 -lrt -lgobject-2.0 -lglib-2.0 -lwnck-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0-lxml2 libtool: link: cc -g -O2 -g -Wall -O2 -Wl,-z -Wl,defs -Wl,-O1 -o stickynotes_applet util.o stickynotes.o stickynotes_callbacks.o stickynotes_applet.o stickynotes_applet_callbacks.o -pthread -Wl,--as-needed -lpanel-applet-2 /usr/lib/libgconf-2.so /usr/lib/libbonoboui-2.so /usr/lib/libgnomecanvas-2.so /usr/lib/libgnome-2.so /usr/lib/libpopt.so /usr/lib/libart_lgpl_2.so /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBit-2.so /usr/lib/libgthread-2.0.so -lrt -lwnck-1 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libpangocairo-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so -lfontconfig /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libglib-2.0.so /usr/lib/libxml2.so -pthread /usr/bin/ld: util.o: in function xstuff_atom_get:util.c:68: error: undefined reference to 'XInternAtom' /usr/bin/ld: util.o: in function xstuff_change_workspace:util.c:142: error: undefined reference to 'XSendEvent' /usr/bin/ld: util.o: in function xstuff_get_current_workspace:util.c:97: error: undefined reference to 'XGetWindowProperty' /usr/bin/ld: util.o: in function xstuff_get_current_workspace:util.c:114: error: undefined reference to 'XFree' /usr/bin/ld: util.o: in function xstuff_get_current_workspace:util.c:108: error: undefined reference to 'XFree' /usr/bin/ld: stickynotes.o: in function stickynote_set_visible:stickynotes.c:56: error: undefined reference to 'XChangeProperty' collect2: ld returned 1 exit status make[4]: *** [stickynotes_applet] Error 1 ---End Message--- ---BeginMessage--- Source: gnome-applets Source-Version: 2.30.0-4 We believe that the bug you reported is fixed in the latest version of gnome-applets, which is due to be installed in the Debian FTP archive: gnome-applets-data_2.30.0-4_all.deb to main/g/gnome-applets/gnome-applets-data_2.30.0-4_all.deb gnome-applets-dbg_2.30.0-4_i386.deb to main/g/gnome-applets/gnome-applets-dbg_2.30.0-4_i386.deb gnome-applets_2.30.0-4.debian.tar.gz to main/g/gnome-applets/gnome-applets_2.30.0-4.debian.tar.gz gnome-applets_2.30.0-4.dsc to main/g/gnome-applets/gnome-applets_2.30.0-4.dsc gnome-applets_2.30.0-4_i386.deb to main/g/gnome-applets/gnome-applets_2.30.0-4_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 554...@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 gnome-applets package) (This message was generated automatically at their request; if you believe that there is a problem with it
Bug#622572: marked as done (gnome-applets: FTBFS -- undefined reference to XFree in stickynotes)
Your message dated Mon, 01 Aug 2011 14:48:06 + with message-id e1qntmo-0007xk...@franck.debian.org and subject line Bug#554646: fixed in gnome-applets 2.30.0-4 has caused the Debian Bug report #554646, regarding gnome-applets: FTBFS -- undefined reference to XFree in stickynotes 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.) -- 554646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-applets Version: 2.30.0-3 Severity: serious Justification: FTBFS I was trying to track down a suspected memory leak related to the weather applet and when I tried to rebuild I received a linker error. I reverted my change and found that the package fails to build from source. The relevant lines are (full log attached): /bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -march=native -g -O2 -march=native -Wl,-z,defs -Wl,-O1 -Wl,--as-needed -o stickynotes_applet util.o stickynotes.o stickynotes_callbacks.o stickynotes_applet.o stickynotes_applet_callbacks.o -pthread -lpanel-applet-2 -lgconf-2 -lbonoboui-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lbonobo-2 -lbonobo-activation -lgmodule-2.0 -lORBit-2 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread -lwnck-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lxml2 libtool: link: gcc -g -O2 -march=native -g -O2 -march=native -Wl,-z -Wl,defs -Wl,-O1 -o stickynotes_applet util.o stickynotes.o stickynotes_callbacks.o stickynotes_applet.o stickynotes_applet_callbacks.o -pthread -pthread -Wl ,--as-needed -lpanel-applet-2 /usr/lib/libgconf-2.so /usr/lib/libbonoboui-2.so /usr/lib/libgnomecanvas-2.so /usr/lib/libgnome-2.so /usr/lib/libpopt.so /usr/lib/libart_lgpl_2.so /usr/lib/libbonobo-2.so /usr/lib/libbonobo- activation.so /usr/lib/libORBit-2.so -lwnck-1 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libgdk_pixbuf-2.0.so -lm /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so -lfontconfig /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/libgthread-2.0.so -lrt /usr/lib/libglib-2.0.so /usr/lib/libxml2.so -pthread /usr/bin/ld: util.o: undefined reference to symbol 'XFree' /usr/bin/ld: note: 'XFree' is defined in DSO //usr/lib64/libX11.so.6 so try adding it to the linker command line //usr/lib64/libX11.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status I see that the version in experimental has a patch (02_link_X11.patch) which I applied by simply adding those two lines to the proper Makefile.am lines. That patch did not help resolve the issue. I also note that there is a similar bug that deals with binutils-gold, but I am not using the gold version. Best regards, Nathan A. Stine -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') 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/bash Versions of packages gnome-applets depends on: ii gconf2 2.28.1-6 GNOME configuration database syste ii gnome-applets-data 2.30.0-3 Various applets for the GNOME pane ii gnome-icon-theme2.30.3-2 GNOME Desktop icon theme ii gnome-panel 2.30.2-4 launcher and docking facility for ii gstreamer0.10-alsa 0.10.32-2GStreamer plugin for ALSA ii gvfs1.6.4-3 userspace virtual filesystem - ser ii libatk1.0-0 2.0.0-1 The ATK accessibility toolkit ii libbonobo2-02.24.3-1 Bonobo CORBA interfaces library ii libbonoboui2-0 2.24.3-1 The Bonobo UI library ii libc6 2.11.2-13Embedded GNU C Library: Shared lib ii libcpufreq0 007-1shared library to deal with the cp ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst ii libdbus-glib-1-20.92-1 simple interprocess messaging syst ii libgconf2-4 2.28.1-6 GNOME configuration database syste ii libglib2.0-0
Bug#634861: marked as done (Please switch python-qscintilla2 to dh_python2)
Your message dated Mon, 01 Aug 2011 14:49:29 +
with message-id e1qnto9-0008oh...@franck.debian.org
and subject line Bug#634861: fixed in qscintilla2 2.4.5-1
has caused the Debian Bug report #634861,
regarding Please switch python-qscintilla2 to dh_python2
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.)
--
634861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: python-qscintilla2
Severity: important
Tags: patch
User: debian-qt-...@lists.debian.org
Usertags: dh_python2-qt4
Hello,
As far as I know the Debian Python Team started a transition to drop python-
support and use dh_python2 instead[1].
To switch python-qscintilla2 to dh_python2 you should wait until python-qt4
switchs to dh_python2 as well, otherwise python-qscintilla2 will be broken.
This bug will become RC once python-qt4 switches to dh_python2.
Last but not least, note that I don't actually work on python stuff, please
review the patch carefully. Also when applying the patch, please replace my
dummy changelog entry with a proper one.
[1] http://lists.debian.org/debian-python/2011/02/msg8.html
Cheers.
diff -Nru qscintilla2-2.4.3/debian/changelog qscintilla2-2.4.3/debian/changelog
--- qscintilla2-2.4.3/debian/changelog 2011-03-31 08:44:25.0 +0200
+++ qscintilla2-2.4.3/debian/changelog 2011-07-20 16:28:24.0 +0200
@@ -1,3 +1,8 @@
+qscintilla2 (2.4.3-3~santa1) UNRELEASED; urgency=low
+
+
+ -- José Manuel Santamaría Lema panfa...@gmail.com Wed, 20 Jul 2011 16:28:09 +0200
+
qscintilla2 (2.4.3-2) unstable; urgency=low
* Rebuilding (Closes: #619096)
diff -Nru qscintilla2-2.4.3/debian/control qscintilla2-2.4.3/debian/control
--- qscintilla2-2.4.3/debian/control 2011-03-31 08:44:09.0 +0200
+++ qscintilla2-2.4.3/debian/control 2011-07-20 16:38:37.0 +0200
@@ -2,7 +2,7 @@
Priority: optional
Maintainer: Torsten Marek shlo...@debian.org
Uploaders: Gudjon I. Gudjonsson gud...@gudjon.org
-Build-Depends: debhelper (= 7.0.1), libqt4-dev, python-all-dev, python-support (= 0.9), python-sip-dev (= 4.10), python-qt4 (= 4.7), python-qt4-dev (= 4.7)
+Build-Depends: debhelper (= 7.0.1), libqt4-dev, python-all-dev (= 2.6.6-3~), python-sip-dev (= 4.10), python-qt4 (= 4.8.3-3~), python-qt4-dev (= 4.8.3-3~)
Standards-Version: 3.9.1
Section: libs
Homepage: http://www.riverbankcomputing.co.uk/qscintilla/index.php
@@ -59,7 +59,7 @@
Package: python-qscintilla2
Section: python
Architecture: any
-Depends: ${python:Depends}, ${shlibs:Depends}, python-qt4 (= 4.7), ${sip:Depends}, ${misc:Depends}
+Depends: ${python:Depends}, ${shlibs:Depends}, python-qt4 (= 4.8.3-3~), ${sip:Depends}, ${misc:Depends}
Description: Python bindings for QScintilla 2
QScintilla is a text editor for Qt4 with features especially useful when
writing and debugging source code. These include support for syntax
diff -Nru qscintilla2-2.4.3/debian/rules qscintilla2-2.4.3/debian/rules
--- qscintilla2-2.4.3/debian/rules 2010-04-18 18:56:25.0 +0200
+++ qscintilla2-2.4.3/debian/rules 2011-07-20 16:39:12.0 +0200
@@ -81,7 +81,7 @@
dh_strip
dh_compress
dh_fixperms
- dh_pysupport
+ dh_python2
dh_sip
dh_makeshlibs
dh_installdeb
---End Message---
---BeginMessage---
Source: qscintilla2
Source-Version: 2.4.5-1
We believe that the bug you reported is fixed in the latest version of
qscintilla2, which is due to be installed in the Debian FTP archive:
libqscintilla2-5_2.4.5-1_i386.deb
to main/q/qscintilla2/libqscintilla2-5_2.4.5-1_i386.deb
libqscintilla2-designer_2.4.5-1_i386.deb
to main/q/qscintilla2/libqscintilla2-designer_2.4.5-1_i386.deb
libqscintilla2-dev_2.4.5-1_all.deb
to main/q/qscintilla2/libqscintilla2-dev_2.4.5-1_all.deb
libqscintilla2-doc_2.4.5-1_all.deb
to main/q/qscintilla2/libqscintilla2-doc_2.4.5-1_all.deb
python-qscintilla2_2.4.5-1_i386.deb
to main/q/qscintilla2/python-qscintilla2_2.4.5-1_i386.deb
qscintilla2_2.4.5-1.debian.tar.gz
to main/q/qscintilla2/qscintilla2_2.4.5-1.debian.tar.gz
qscintilla2_2.4.5-1.dsc
to main/q/qscintilla2/qscintilla2_2.4.5-1.dsc
qscintilla2_2.4.5.orig.tar.gz
to main/q/qscintilla2/qscintilla2_2.4.5.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 634...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Scott Kitterman sc...@kitterman.com (supplier of updated
Bug#636085: marked as done (tortoisehg: Fails to start. Qsci module not found.)
Your message dated Mon, 01 Aug 2011 14:49:29 +
with message-id e1qnto9-0008oh...@franck.debian.org
and subject line Bug#634861: fixed in qscintilla2 2.4.5-1
has caused the Debian Bug report #634861,
regarding tortoisehg: Fails to start. Qsci module not 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.)
--
634861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tortoisehg
Version: 2.1.1-1
Severity: grave
Tags: sid
Justification: renders package unusable
Hello:
I recently upgraded mercurial and tortoisehg to latest sid versions. After
this I'm unable to start tortoisehg, see the error below:
{{{
#!python
** Mercurial version (1.9). TortoiseHg version (2.1.1)
** Command: log
** CWD: /home/rasasi/debs/calligra/calligra-debian
** Extensions loaded: transplant, rebase, svn, record, children, fetch, mq,
convert, graphlog, git, extdiff, purge
** Python version: 2.6.7 (r267:88850, Jul 10 2011, 08:11:54) [GCC 4.6.1]
** Qt-4.7.3 PyQt-4.8.3
Traceback (most recent call last):
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 50, in
dispatch
return _runcatch(u, args)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 236, in
_runcatch
return runcommand(ui, args)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 309, in
runcommand
return _runcommand(lui, options, cmd, d)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 360, in
_runcommand
return checkargs()
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 314, in
checkargs
return cmdfunc()
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 308, in
lambda
d = lambda: util.checksignature(func)(ui, *args, **cmdoptions)
File /usr/lib/pymodules/python2.6/mercurial/util.py, line 385, in check
return func(*args, **kwargs)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py, line 692, in
log
from tortoisehg.hgqt.workbench import run
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 85, in
_demandimport
return _origimport(name, globals, locals, fromlist)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/workbench.py, line
19, in module
from tortoisehg.hgqt.repowidget import RepoWidget
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 109, in
_demandimport
mod = _origimport(name, globals, locals)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/repowidget.py, line
28, in module
from tortoisehg.hgqt.revdetails import RevDetailsWidget
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 109, in
_demandimport
mod = _origimport(name, globals, locals)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/revdetails.py, line
18, in module
from tortoisehg.hgqt.fileview import HgFileView
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 109, in
_demandimport
mod = _origimport(name, globals, locals)
File /usr/lib/python2.6/dist-packages/tortoisehg/hgqt/fileview.py, line 23,
in module
qsci = Qsci.QsciScintilla
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 75, in
__getattribute__
self._load()
File /usr/lib/pymodules/python2.6/mercurial/demandimport.py, line 47, in
_load
mod = _origimport(head, globals, locals)
ImportError: No module named Qsci
}}}
Beside this issue, I really appreciate your work on tortoisehg. Thanks
and regards,
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (900, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39.3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tortoisehg depends on:
ii mercurial 1.9-1 scalable distributed version contr
ii python2.6.7-2interactive high-level object-orie
ii python-gobject2.28.6-4 Python bindings for the GObject li
ii python-qscintilla22.4.3-2+b1 Python bindings for QScintilla 2
ii python-qt44.8.3-3Python bindings for Qt4
ii python2.6 2.6.7-3An interactive high-level object-o
ii python2.7 2.7.2-3An interactive high-level object-o
Versions of packages tortoisehg recommends:
ii libjs-jquery 1.6.2-1JavaScript library for dynamic web
ii python-iniparse
Bug#622794: atop: diff for NMU version 1.23-1.1
On Mon, Aug 01, 2011 at 03:41:57PM +0100, Jonathan Wiltshire wrote:
I've prepared an NMU for atop (versioned as 1.23-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Sorry, here is the correct patch.
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
diff --git a/acctproc.c b/acctproc.c
index 067ace8..3b71c42 100644
--- a/acctproc.c
+++ b/acctproc.c
@@ -126,7 +126,7 @@ static const char rcsid[] = $Id: acctproc.c,v 1.26
2008/03/06 08:37:25 gerlof E
#include photoproc.h
#include acctproc.h
-#defineACCTDIR /tmp/atop.d
+#defineACCTDIR /var/run/atop
#defineACCTFILEatop.acct
#defineACCTENV ATOPACCT
@@ -331,7 +331,7 @@ acctswon(void)
if (semctl(semid, 1, GETVAL, 0) == SEMTOTAL)
{
/*
- ** create a new separate directory below /tmp
+ ** create a new separate directory below /var/run
** for the accounting file;
** if this directory exists (e.g. previous atop-run killed)
** it will be cleaned and newly created
diff --git a/debian/changelog b/debian/changelog
index e33c0c1..b890434 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+atop (1.23-1.1) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * Fix CVE-2011-: Insecure use of a temporary files rawlog.c and
+acctproc.c (Closes: #622794)
+
+ -- Jonathan Wiltshire j...@debian.org Mon, 01 Aug 2011 15:35:16 +0100
+
atop (1.23-1) unstable; urgency=low
* fixed typo (Closes: #467447)
diff --git a/rawlog.c b/rawlog.c
index 31f93a2..086d93c 100644
--- a/rawlog.c
+++ b/rawlog.c
@@ -477,18 +477,18 @@ rawread(unsigned int begintime, unsigned int endtime)
*/
fprintf(stderr, Decompressing logfile \n);
- snprintf(tmpname2, sizeof tmpname2, /tmp/atopwrk%d, getpid());
- snprintf(command, sizeof command, gunzip -c %s %s,
- tmpname1, tmpname2);
- system (command);
+ snprintf(tmpname2, sizeof tmpname2, /tmp/atopwrkXX);
- if ( (rawfd = open(tmpname2, O_RDONLY)) == -1)
+ if ( (rawfd = mkstemp(tmpname2)) == -1)
{
fprintf(stderr, %s - , rawname);
perror(open decompressed raw file);
cleanstop(7);
}
+ snprintf(command, sizeof command, gunzip -c %s %s,
+ tmpname1, tmpname2);
+ system (command);
unlink(tmpname2);
}
signature.asc
Description: Digital signature
Bug#636147: jupp: removes /etc/joe/editorrc, breaking joe
Thorsten Glaser t...@mirbsd.de wrote: Do you think it would work if I just add /etc/jupp/editorrc@ - ../joe/editorrc and then manage /etc/joe/editorrc with update-alternatives just like joe does? There seems to be no point of jupp sharing the editorrc alternative with joe, especially considering that neither program is compatible with the shipped rc files of the other anymore. Apparently, at the moment, jupp uses only one alternative for /etc/jupp/editorrc. Do you plan to include the rc files from joe-jupp as alternatives as well? If so, the correct fix is to use an alternative name different from the one used by joe. If not, you don't need to use the alternatives system for /etc/jupp/editorrc at all, and can symlink the file to /etc/jupp/jupprc unconditionally. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636147: jupp: removes /etc/joe/editorrc, breaking joe
Piotr Engelking dixit: There seems to be no point of jupp sharing the editorrc alternative with joe, especially considering that neither program is compatible with the shipped rc files of the other anymore. The problem is that joe/jupp use argv[0] + rc as name to look for, so it’s editorrc for both of them. Apparently, at the moment, jupp uses only one alternative for /etc/jupp/editorrc. Do you plan to include the rc files from joe-jupp as alternatives as well? They are already included, joe-jupp contains its own maintainer scripts enabling them. If so, the correct fix is to use an alternative name different from the one used by joe. But the name must still be editorrc… (which, by the way, could be a slave to editor, couldn’t it?) I think using /etc/joe/editorrc makes most sense – as editorrc is only used by editor, which can only point to one of either joe or jupp at the same time. Will try if that works. bye, //mirabilos -- FWIW, I'm quite impressed with mksh interactively. I thought it was much *much* more bare bones. But it turns out it beats the living hell out of ksh93 in that respect. I'd even consider it for my daily use if I hadn't wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 636220 is serious
Processing commands for cont...@bugs.debian.org: severity 636220 serious Bug #636220 [rhythmbox-plugins] rhythmbox-plugins: Status icon plugin stopped working in 0.12.8-4 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 636220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636220 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#636229: glide: FTBFS on i386: unrecognized option '-$'
Source: glide Version: 2002.04.10ds1-7 Severity: serious From my pbuilder build log: ... libtool --mode=compile gcc -g -Wall -O3 -march=i486 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DBIG_OPT -$ -I. -DUSE_PACKET_FIFO=1 -c -o cpudtect.lo /tmp/buildd/glide-2002.04.10ds1/glide3x/h3/glide3/src/cpudtect.S libtool: compile: gcc -g -Wall -O3 -march=i486 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DBIG_OPT -\$ -I. -DUSE_PACKET_FIFO=1 -c /tmp/buildd/glide-2002.04.10ds1/glide3x/h3/glide3/src/cpudtect.S - fPIC -DPIC -o .libs/cpudtect.o gcc: error: unrecognized option '-$' make[4]: *** [cpudtect.lo] Error 1 make[4]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3/glide3/src' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3/glide3' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3' Filesystem 1K-blocks Used Available Use% Mounted on /dev/disk/by-uuid/a4992605-9cb9-44cf--7f5d0818dda0 38448304595188 35900016 2% / Time Elapsed: 0 Years, 0 Days, 0 Hours, 1 Minutes, 7 Seconds Disk usage: -6.44 Mb ... # libglide3 install -m 644 /tmp/buildd/glide-2002.04.10ds1/debian/tmp.h3/usr/lib/libglide3.so.3.10.0 \ /tmp/buildd/glide-2002.04.10ds1/debian/libglide3/usr/lib/glide3/libglide3_h3.so.3.10.0 install: cannot stat `/tmp/buildd/glide-2002.04.10ds1/debian/tmp.h3/usr/lib/libglide3.so.3.10.0': No such file or directory make: *** [binary-arch] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 (Also, why is the build failure being ignored until it causes other problems later? Maybe you forgot to set -e in a subscript in a Makefile?) -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636188: xscorch: Please transition to use libreadline6-dev
Hi, On Mon, Aug 01, 2011 at 09:07:37PM +0800, Aron Xu wrote: retitle 636188 Please use libreadline-gplv2-dev instead of libreadline5-dev thanks I will prepare a new version using libreadline-gplv2-dev. Thank you for pointing out the license issue. Again, please check your package is buildable with pbuilder/cowbuilder or even in a plain sid chroot. As the package's maintainer, it's your responsibility to make sure all of the problems do not exist before you ask for sponsorship. I don't appreciate this comment. The package built on my sid desktop and using pbuilder on sid both i386 and amd64 yesterday. I still have the logs and here's what it said about that dep: pbuilder-satisfydepends-dummy depends on libreadline5-dev | libreadline6-dev; however: Package libreadline5-dev is not installed. Package libreadline6-dev is not installed. [...] Get: 95 http://http.us.debian.org/debian/ sid/main libreadline6-dev i386 6.2-2 [247 kB] [...] Selecting previously deselected package libreadline6-dev. Unpacking libreadline6-dev (from .../libreadline6-dev_6.2-2_amd64.deb) ... [...] dpkg-buildpackage: full upload (original source is included) You seem to have some mistaken information about pbuilder, or at least specific to your own installation of it. BTW I also ran it through lintian. Thanks, -Jacob -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636147: marked as done (jupp: removes /etc/joe/editorrc, breaking joe)
Your message dated Mon, 01 Aug 2011 16:17:22 +
with message-id e1qnvbc-0008mg...@franck.debian.org
and subject line Bug#636147: fixed in jupp 3.1.17-3
has caused the Debian Bug report #636147,
regarding jupp: removes /etc/joe/editorrc, breaking joe
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.)
--
636147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: jupp
Version: 3.1.17-2
Severity: serious
Justification: wheezy RC policy §3
Jupp hijacks the editorrc alternative from joe, moving it from
/etc/joe/editorrc to /etc/jupp/editorrc. This breaks joe if it is set
as the default system editor:
# dpkg-query -W joe
joe 3.7-2
# ls -F /etc/joe/
editorrc@ ftyperc jicerc.ru jmacsrc joerc jpicorc jstarrc rjoerc
# apt-get install -qq --trivial-only jupp
Selecting previously deselected package jupp.
(Reading database ... 465741 files and directories currently installed.)
Unpacking jupp (from .../jupp_3.1.17-2_i386.deb) ...
Processing triggers for man-db ...
Setting up jupp (3.1.17-2) ...
update-alternatives: renaming editorrc link from /etc/joe/editorrc to
/etc/jupp/editorrc.
# ls -F /etc/joe/
ftyperc jicerc.ru jmacsrc joerc jpicorc jstarrc rjoerc
# file /etc/alternatives/editor{,rc}
/etc/alternatives/editor: symbolic link to `/usr/bin/joe'
/etc/alternatives/editorrc: symbolic link to `/etc/joe/joerc'
# editor
Couldn't open '*editorrc'
#
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.0.0-00150-gb3626c5 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages jupp depends on:
ii libc6 2.13-10Embedded GNU C Library: Shared lib
ii libncurses5 5.9-1 shared libraries for terminal hand
ii libselinux1 2.0.98-1.1 SELinux runtime shared libraries
jupp recommends no packages.
jupp suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: jupp
Source-Version: 3.1.17-3
We believe that the bug you reported is fixed in the latest version of
jupp, which is due to be installed in the Debian FTP archive:
joe-jupp_3.1.17-3_all.deb
to main/j/jupp/joe-jupp_3.1.17-3_all.deb
jupp_3.1.17-3.diff.gz
to main/j/jupp/jupp_3.1.17-3.diff.gz
jupp_3.1.17-3.dsc
to main/j/jupp/jupp_3.1.17-3.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 636...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thorsten Glaser t...@mirbsd.de (supplier of updated jupp 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: SHA384
Format: 1.8
Date: Mon, 01 Aug 2011 15:54:28 +
Source: jupp
Binary: jupp joe-jupp
Architecture: source all
Version: 3.1.17-3
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser t...@mirbsd.de
Changed-By: Thorsten Glaser t...@mirbsd.de
Description:
joe-jupp - reimplement the joe Debian package using jupp
jupp - user friendly full screen text editor
Closes: 636147
Changes:
jupp (3.1.17-3) unstable; urgency=low
.
* Do not take over the location of the editorrc alternative,
symlink to it instead and collaborate with joe managing it
(Closes: #636147)
Checksums-Sha1:
f15cea5f86462152a33561b5a2247fa6148280bb 1856 jupp_3.1.17-3.dsc
0d2d85ee50df9c1557f0f233f7b23eebde247afd 6692 jupp_3.1.17-3.diff.gz
81e2227ea090aeceee72e95c4915fe8fdcd71427 20170 joe-jupp_3.1.17-3_all.deb
Checksums-Sha256:
d14f2bd33ac2bb167b8db6da936f7dfe91e1140a3164f7d3d5d70732e4820a5a 1856
jupp_3.1.17-3.dsc
66195c589d99d91e85bba334e60a4577aa173a9b7418cad4a2e570d0794b5ada 6692
jupp_3.1.17-3.diff.gz
d9a82fec347bf458ea31bd971516d3c8cb6f1d86b60c3e673573602aa4a16789 20170
joe-jupp_3.1.17-3_all.deb
Files:
f9c59bc92b630cfa0ce2f81c3463f65b 1856 editors optional jupp_3.1.17-3.dsc
3a6cc1cd80276e1a70598519998f32f6 6692 editors optional jupp_3.1.17-3.diff.gz
86bdbda1fb08509b78748cf14cb006dd 20170 editors optional
joe-jupp_3.1.17-3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MirBSD)
Processed: forcibly merging 627211 632238
Processing commands for cont...@bugs.debian.org: forcemerge 627211 632238 Bug#627211: libshell-perl: Should not enter testing yet Bug#632238: libshell-perl: not installable in sid Forcibly Merged 627211 632238. thanks Stopping processing here. Please contact me if you need assistance. -- 627211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627211 632238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632238 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#636229: marked as done (glide: FTBFS on i386: unrecognized option '-$')
Your message dated Mon, 1 Aug 2011 18:35:24 +0200 with message-id 20110801163524.ga22...@gaara.hadrons.org and subject line Re: Bug#636229: glide: FTBFS on i386: unrecognized option '-$' has caused the Debian Bug report #636229, regarding glide: FTBFS on i386: unrecognized option '-$' 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.) -- 636229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: glide Version: 2002.04.10ds1-7 Severity: serious From my pbuilder build log: ... libtool --mode=compile gcc -g -Wall -O3 -march=i486 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DBIG_OPT -$ -I. -DUSE_PACKET_FIFO=1 -c -o cpudtect.lo /tmp/buildd/glide-2002.04.10ds1/glide3x/h3/glide3/src/cpudtect.S libtool: compile: gcc -g -Wall -O3 -march=i486 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DBIG_OPT -\$ -I. -DUSE_PACKET_FIFO=1 -c /tmp/buildd/glide-2002.04.10ds1/glide3x/h3/glide3/src/cpudtect.S - fPIC -DPIC -o .libs/cpudtect.o gcc: error: unrecognized option '-$' make[4]: *** [cpudtect.lo] Error 1 make[4]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3/glide3/src' make[3]: *** [install-recursive] Error 1 make[3]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3/glide3' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3/h3' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/tmp/buildd/glide-2002.04.10ds1/glide3x/build.h3' Filesystem 1K-blocks Used Available Use% Mounted on /dev/disk/by-uuid/a4992605-9cb9-44cf--7f5d0818dda0 38448304595188 35900016 2% / Time Elapsed: 0 Years, 0 Days, 0 Hours, 1 Minutes, 7 Seconds Disk usage: -6.44 Mb ... # libglide3 install -m 644 /tmp/buildd/glide-2002.04.10ds1/debian/tmp.h3/usr/lib/libglide3.so.3.10.0 \ /tmp/buildd/glide-2002.04.10ds1/debian/libglide3/usr/lib/glide3/libglide3_h3.so.3.10.0 install: cannot stat `/tmp/buildd/glide-2002.04.10ds1/debian/tmp.h3/usr/lib/libglide3.so.3.10.0': No such file or directory make: *** [binary-arch] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 (Also, why is the build failure being ignored until it causes other problems later? Maybe you forgot to set -e in a subscript in a Makefile?) -- Daniel Schepler ---End Message--- ---BeginMessage--- Version: 2002.04.10ds1-7 On Mon, 2011-08-01 at 09:02:31 -0700, Daniel Schepler wrote: Source: glide Version: 2002.04.10ds1-7 Severity: serious I'm assuming you built 2002.04.10ds1-6, but reported against 2002.04.10ds1-7, where I had already fixed this: ,--- glide (2002.04.10ds1-7) unstable; urgency=low * Use “-fdollars-in-identifiers -x assembler-with-cpp” instead of “-$” to preprocess assembler code through gcc, the later just stopped working recently. -- Guillem Jover guil...@debian.org Mon, 01 Aug 2011 05:13:22 +0200 `--- As it seemed to build fine locally and on the buildd: https://buildd.debian.org/status/fetch.php?pkg=glidearch=i386ver=2002.04.10ds1-7stamp=1312170246 (Also, why is the build failure being ignored until it causes other problems later? Maybe you forgot to set -e in a subscript in a Makefile?) Yeah I noticed too, should fix it in the Makefile and several of the shell scripts invoked from it. thanks, guillem ---End Message---
Bug#636147: jupp: removes /etc/joe/editorrc, breaking joe
Thorsten Glaser t...@mirbsd.de wrote: There seems to be no point of jupp sharing the editorrc alternative with joe, especially considering that neither program is compatible with the shipped rc files of the other anymore. The problem is that joe/jupp use argv[0] + rc as name to look for, so it’s editorrc for both of them. Yes, I am aware of it, but the point is that a combination like joe selected as the alternative for editor, and /etc/jupp/jupprc for editorrc (or the other way around) won't work. Apparently, at the moment, jupp uses only one alternative for /etc/jupp/editorrc. Do you plan to include the rc files from joe-jupp as alternatives as well? They are already included, joe-jupp contains its own maintainer scripts enabling them. Sorry, I checked in the wrong place. If so, the correct fix is to use an alternative name different from the one used by joe. But the name must still be editorrc… No, the alternative name can be different from from the name of the file referring to it. (which, by the way, could be a slave to editor, couldn’t it?) According to the changelog entry for joe 3.5-1, sadly not: * Stop shipping fixed /etc/joe/editorrc and instead add all our versions as alternatives to it. Unfortunately it doesn't work as a slave alternative to the main editor alternative, but this is as close as it can get, closes: #269334. (Unless, perhaps, update-alternatives changed in the meantime?) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628771: marked as done (Please update for tracker-0.10)
Your message dated Mon, 01 Aug 2011 16:47:15 + with message-id e1qnve7-0002sm...@franck.debian.org and subject line Bug#628771: fixed in bognor-regis 0.6.12+git20101007.02c25268-3 has caused the Debian Bug report #628771, regarding Please update for tracker-0.10 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.) -- 628771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bognor-regis Version: 0.6.12+git20101007.02c25268-1 Severity: normal User: bi...@debian.org Usertags: tracker-0.10 Hi, your package uses tracker 0.8 via libtracker-client-0.8 I'd like to update tracker to version 0.10 in unstable, so please prepare your package to be ready when we start the transition, ideally by uploading a updated package to experimental. tracker 0.10 packages are available from experimental. The library name for libtracker-client-0.8 has changed to libtracker-client-0.10 (including the pkg-config file) so updating the configure check might be sufficient. Yet, libtracker-client has been declared obsolete [1] and ideally your package is updated to use libtracker-sparql [2]. Regards, Michael [1] http://developer.gnome.org/libtracker-client/unstable/ [2] http://developer.gnome.org/libtracker-sparql/unstable/ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-1-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: bognor-regis Source-Version: 0.6.12+git20101007.02c25268-3 We believe that the bug you reported is fixed in the latest version of bognor-regis, which is due to be installed in the Debian FTP archive: bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz bognor-regis_0.6.12+git20101007.02c25268-3.dsc to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3.dsc bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-0.6-0-dbg_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-0.6-0-dbg_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-dev_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-dev_0.6.12+git20101007.02c25268-3_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. Ying-Chun Liu (PaulLiu) paul...@debian.org (supplier of updated bognor-regis 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: SHA512 Format: 1.8 Date: Mon, 01 Aug 2011 23:05:02 +0800 Source: bognor-regis Binary: bognor-regis libbognor-regis-0.6-0 libbognor-regis-dev libbognor-regis-0.6-0-dbg Architecture: source i386 Version: 0.6.12+git20101007.02c25268-3 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org Changed-By: Ying-Chun Liu (PaulLiu) paul...@debian.org Description: bognor-regis - Media daemon and play queue manager libbognor-regis-0.6-0 - Media daemon and play queue manager library libbognor-regis-0.6-0-dbg - Media daemon and play queue manager library (debug symbols) libbognor-regis-dev - Media daemon and play queue manager library (development files) Closes: 628771 630265 Changes: bognor-regis (0.6.12+git20101007.02c25268-3) unstable; urgency=low . * experimental - unstable - Uses libnotify 0.7 (Closes: #630265) - Update to tracker-0.10 (Closes: #628771) Checksums-Sha1: c50e4a0c588e92cf299b74f8a73432ce315f1adc 2132 bognor-regis_0.6.12+git20101007.02c25268-3.dsc 9fb5f67270fa2dd6ee4cef843c42a8427244d146 4343 bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz 5ba789399918eabb0de6bc6d9be8c1006bdaf92b 42612 bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb 7273acdbfd8322bfba74acec5de781ef95903fdf 15056
Bug#630265: marked as done (bognor-regis: Please transition to libnotify 0.7)
Your message dated Mon, 01 Aug 2011 16:47:15 + with message-id e1qnve7-0002sp...@franck.debian.org and subject line Bug#630265: fixed in bognor-regis 0.6.12+git20101007.02c25268-3 has caused the Debian Bug report #630265, regarding bognor-regis: Please transition to libnotify 0.7 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.) -- 630265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bognor-regis Version: 0.6.12+git20101007.02c25268-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libnotify0.7-transition Hi, We are planning to transition[0] libnotify to version 0.7 which breaks its API. Unfortunately, after a rebuild it seems that your package FTBFS with the newer version. Packages of the 0.7 version can be currently found in experimental. API changes (shamelessly taken from[1]): notify_notification_new_with_status_icon is gone notify_notification_attach_to_status_icon is gone notify_notification_attach_to_widget is gone notify_notification_set_geometry_hints is gone notify_notification_new has lost its widget argument All rebuild logs can be found at: http://people.debian.org/~bigon/libnotify0.7_rebuildlog/ Cheers Laurent Bigonville [0] http://release.debian.org/transitions/html/libnotify.html [1] http://lists.fedoraproject.org/pipermail/devel/2010-November/144914.html ---End Message--- ---BeginMessage--- Source: bognor-regis Source-Version: 0.6.12+git20101007.02c25268-3 We believe that the bug you reported is fixed in the latest version of bognor-regis, which is due to be installed in the Debian FTP archive: bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz bognor-regis_0.6.12+git20101007.02c25268-3.dsc to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3.dsc bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-0.6-0-dbg_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-0.6-0-dbg_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-3_i386.deb libbognor-regis-dev_0.6.12+git20101007.02c25268-3_i386.deb to main/b/bognor-regis/libbognor-regis-dev_0.6.12+git20101007.02c25268-3_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 630...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) paul...@debian.org (supplier of updated bognor-regis 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: SHA512 Format: 1.8 Date: Mon, 01 Aug 2011 23:05:02 +0800 Source: bognor-regis Binary: bognor-regis libbognor-regis-0.6-0 libbognor-regis-dev libbognor-regis-0.6-0-dbg Architecture: source i386 Version: 0.6.12+git20101007.02c25268-3 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) paul...@debian.org Changed-By: Ying-Chun Liu (PaulLiu) paul...@debian.org Description: bognor-regis - Media daemon and play queue manager libbognor-regis-0.6-0 - Media daemon and play queue manager library libbognor-regis-0.6-0-dbg - Media daemon and play queue manager library (debug symbols) libbognor-regis-dev - Media daemon and play queue manager library (development files) Closes: 628771 630265 Changes: bognor-regis (0.6.12+git20101007.02c25268-3) unstable; urgency=low . * experimental - unstable - Uses libnotify 0.7 (Closes: #630265) - Update to tracker-0.10 (Closes: #628771) Checksums-Sha1: c50e4a0c588e92cf299b74f8a73432ce315f1adc 2132 bognor-regis_0.6.12+git20101007.02c25268-3.dsc 9fb5f67270fa2dd6ee4cef843c42a8427244d146 4343 bognor-regis_0.6.12+git20101007.02c25268-3.debian.tar.gz 5ba789399918eabb0de6bc6d9be8c1006bdaf92b 42612 bognor-regis_0.6.12+git20101007.02c25268-3_i386.deb 7273acdbfd8322bfba74acec5de781ef95903fdf 15056 libbognor-regis-0.6-0_0.6.12+git20101007.02c25268-3_i386.deb f321f158f74e704eb741ae392104645644e92ec9 16172
Bug#636188: marked as done (Please use libreadline-gplv2-dev instead of libreadline5-dev)
Your message dated Mon, 1 Aug 2011 09:50:46 -0700
with message-id 20110801165046.gk...@lunixsys.com
and subject line Re: Bug#636188: Please use libreadline-gplv2-dev instead of
libreadline5-dev
has caused the Debian Bug report #636188,
regarding Please use libreadline-gplv2-dev instead of libreadline5-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.)
--
636188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xscorch
Severity: serious
Please transition to use libreadline6-dev instead of libreadline5-dev,
the readline maintainer has said everyone should use version 6 except
your package's license does not allow. Package libreadline5-dev has
gone from unstable, so your package on mentors.debian.net FTBFS
because missing dependency and cannot be sponsored.
Note: buildd only consider the first candidate in Build-Depends list,
which means libreadline5-dev | libreadline6-dev in build-dep equals
to simply libreadline5-dev.
Please drop me a line when you have updated it, don't forget to add
RFS at the beginning of the mail's subject line.
--
Regards,
Aron Xu
---End Message---
---BeginMessage---
Actually, this bug is not found in any version in Debian. If you check
the control file for the previous versions here are the dependencies:
Build-Depends: debhelper (= 7), groff, libglib2.0-dev, libgtk2.0-dev,
libmikmod2-dev, libx11-dev, libxext-dev, libxi-dev
Depends: ${shlibs:Depends}, ${misc:Depends}
This is because the readline support is a soft dependency (an
enhancement) and the package builds fine without it. The dependency had
been missed in previous versions and was just added in the version on
mentors.d.n.
Since the bug is not actually found in Debian, I am closing it.
Regarding the GPL issue, before I submit an update I will see if we can
change to GPL v3, which I assume would resolve the issue in a more
satisfactory manner anyway.
Thanks,
-Jacob
---End Message---
Bug#636210: marked as done (flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory)
Your message dated Mon, 01 Aug 2011 19:01:35 +0200 with message-id 4e36dbef.8000...@thykier.net and subject line Re: [pkg-fgfs-crew] Bug#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory has caused the Debian Bug report #636210, regarding flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 636210: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flightgear Version: 2.0.0-4 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, flightgear appears to be FTBFS on several architectures with the following: [...] mv -f .deps/hud_labl.Tpo .deps/hud_labl.Po g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -MT hud_ladr.o -MD -MP -MF .deps/hud_ladr.Tpo -c -o hud_ladr.o hud_ladr.cxx mv -f .deps/hud_ladr.Tpo .deps/hud_ladr.Po g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../.. -I../../src -I/usr/local/include -MT hud_rwy.o -MD -MP -MF .deps/hud_rwy.Tpo -c -o hud_rwy.o hud_rwy.cxx hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory compilation terminated. make[4]: *** [hud_rwy.o] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 make[4]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit' make[3]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src/Cockpit' make[2]: Leaving directory `/build/buildd-flightgear_2.0.0-4-armel-M6Aue6/flightgear-2.0.0/src' See https://buildd.debian.org/status/package.php?p=flightgear ~Niels - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJONp5JAAoJEAVLu599gGRC1eAP/3/hH46eGwuNywNhbmDgLzhY 5xQqjtfJQ76gCK64HlVbRa/3Ytej57FB8MDvfedDEseLsCMHR1vjKEMxjf1ozKBv NmTHR6aml6aRxAFK/WV3x+ZyWgUhheaXGAGOd4e9wErnFTD2FapTDwl+qzzjac1+ +cvG4HWsk2QtBXtveoY2IP0wRBtU2vG27Y2ISejyuzTbEugjm2eKbM2PEDJPfExO tlJ5jEpT0tOglT0rrg18dmR30LffTRJ3a4GmGPNZ8cJffHVAxQPvZfhCiM0JD1YE MU5AVTPHYzT2gprWUtSiQmbMytVJKvMiHsadqfNww+iHVbRnReUorU85E5gopdg6 hkf0DyQtT8MvNAJ1SLMTndyeOMQBZ6bb35V1pooq2mjEXNBZAm48qA51Mkakv3Ji Ffk1wvt8U3zKdoU5piKCIfB0uYEHy3wYqctMC5povh7+sLcHXDkx2rP2Em1c3S5t 2rRl6ba29iw7VWpvjRmytESzlAnPlzNlfP6cGpZ1P9J2P5VqiQK4u6VG8K2xjTBz 386ZwTdWCPxgZnQAki3DjAsBnJjpMoMdgsGQMul0hH4nY2UUFf8dPRNAdj3oyZEU qGGiqWuUP9HxePR6CD+1lNPpnVmupVfXbNHFr/Fykq0RpcDqJnOApY0NGJ93SvbP Xd2ZxZSZ811XQQ2y9K3y =7Mk0 -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- On 2011-08-01 15:09, Ove Kåven wrote: On 08/01/2011 02:38 PM, Niels Thykier wrote: Hi, flightgear appears to be FTBFS on several architectures with the following: I suppose they need to be built against simgear-dev = 2.0.0-3, not simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just to force the build-dep version, or is it enough to just wait for the buildds to build the newest simgear and flightgear after that? Worked, thanks for the hint. :) ~Niels ---End Message---
Bug#630280: Processed: severity of 630305 is serious, severity of 630280 is serious, severity of 630265 is serious
Hello Laurent, On Sun, Jul 31, 2011 at 09:25:56PM +0200, Laurent Bigonville wrote: Le Sun, 31 Jul 2011 20:32:06 +0200, Helge Kreutzmann deb...@helgefjell.de a écrit : Hello Laurent, Hello, Is there anything you want me/need me to do? Then please instead of fiddeling with closed bugs send those information to me. Well the bug is not closed in unstable and testing yet :) Fine with me, but a mail like this would have been much clearer :-)) For the record: goobox is ready to be uploaded with inotify 0.7 support *iff* 629566 is resolved, i.e. libbrasero-media3-dev is uploaded to unstable. Unfortunately the maintainer of libbrasero-media3-dev seems inactive, i.e. has not responded for almost 2 month regarding his timeframe. Until then the version in experimental has to suffice, unfortunately. Well that pretty annoying. Do you think you could create a patch to fix this in the unstable version? The API has minimal changes and that shouldn't be to complicated. Otherwise the release will remove it from testing to allow the transition of libnotify. I'd rather fix this in one step. Do you know any reason why 629566 can't be resolved? Unfortunately they (you? see below) do not respond to the bug report, and currently I cannot mail them directly (582765). Of course I could see if I could do an upload just fixing your transition, but it's not like I'm bored and do not have anything else to do. And if I knew a reason/timeframe for the libbrasero-media3-dev upload, then I could of course adjust. But I would not be very happy to do the extra work for an upload fixing the libnotify transition alone just to find out two days later that libbrasero-media3-dev was uploaded. And especially given that both libnotify *and* libbrasero-media3-dev have the same maintainer I find it somewhat strange that the intermix (which I denoted by the proper blocks in the BTS) cannot be resolved! (And not even a simple ack to my bug report almost 2 month ago is possible). And removing goobox from unstable would punish the wrong guy/would be quite discouraging. I uploaded to experimental the same day you reported the transition (btw. without a set timeframe), i.e. it's not like I'm not responsive. I even talked with my previous sponsor about this bug before I went on vacation some weeks ago, in case something was happening with 629566. I hope you can talk to your team and check about libbrasero-media3-dev. Depending on the day of the week I can quickly do the upload if necessary. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#636188: xscorch: Please transition to use libreadline6-dev
On Mon, Aug 1, 2011 at 23:59, Jacob Luna Lundberg ja...@gnifty.net wrote: Hi, On Mon, Aug 01, 2011 at 09:07:37PM +0800, Aron Xu wrote: retitle 636188 Please use libreadline-gplv2-dev instead of libreadline5-dev thanks I will prepare a new version using libreadline-gplv2-dev. Thank you for pointing out the license issue. Thanks, :-) Again, please check your package is buildable with pbuilder/cowbuilder or even in a plain sid chroot. As the package's maintainer, it's your responsibility to make sure all of the problems do not exist before you ask for sponsorship. I don't appreciate this comment. The package built on my sid desktop and using pbuilder on sid both i386 and amd64 yesterday. I still have the logs and here's what it said about that dep: pbuilder-satisfydepends-dummy depends on libreadline5-dev | libreadline6-dev; however: Package libreadline5-dev is not installed. Package libreadline6-dev is not installed. [...] Get: 95 http://http.us.debian.org/debian/ sid/main libreadline6-dev i386 6.2-2 [247 kB] [...] Selecting previously deselected package libreadline6-dev. Unpacking libreadline6-dev (from .../libreadline6-dev_6.2-2_amd64.deb) ... [...] dpkg-buildpackage: full upload (original source is included) You seem to have some mistaken information about pbuilder, or at least specific to your own installation of it. BTW I also ran it through lintian. But it is true that Debian buildd only takes the first candidate. Even now you have pbuilder tested, it will eventually FTBFS on buildd if it get uploaded. When I meet this problem for the first time I argued that it was something wrong with buildd, and debian-policy said we could do this - but buildd is an exception because it needs to produce certain results from certain build-dep, so I gave up arguing. I'm not blaming you, and if my words let you think I was blaming, then I'd apologize. But what you have done in the packaging reveals some problems: As you have written libreadline5-dev | libreadline6-dev, then I assume you have the sense that there is probably license issue with libreadline6-dev, so you choose libreadline5-dev over it by default, and you keep the latter one because it might be useful for those who want to compile binary packages themselves. OK, then you need to check whether your build is correct, by running lintian *and* checking the build log at least. You have tested it with lintian already, then you forgot to check your log. IMHO checking the log can probably discover some sensitive (legal) problems and/or technical problems (for example, unusual warnings or errors, but the build system are mis-configured to not fail). So, please do it from now on. (PS: we are all aware that lintian is a piece of software, is just a tool, it can help us check errors, but that's not all we need to do.) -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630590: Fixed
This has been fixed upstream in https://github.com/mono/mono-addins/commit/2bf0f4b5c56c56473e0a055f0f987309f3dd366a -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636210: [pkg-fgfs-crew] Bug#636210: Bug#636210: flightgear: FTBFS: hud_rwy.cxx:36:36: fatal error: simgear/math/project.hxx: No such file or directory
I think the fgrun package is also broken (on amd64 at least) and not building on kfreebsd-* because of this issue. Chris On Mon, 2011-08-01 at 15:37 +0200, Niels Thykier wrote: On 2011-08-01 15:09, Ove Kåven wrote: On 08/01/2011 02:38 PM, Niels Thykier wrote: Hi, flightgear appears to be FTBFS on several architectures with the following: I suppose they need to be built against simgear-dev = 2.0.0-3, not simgear-dev 2.0.0-2. Will it be necessary to upload new flightgear just to force the build-dep version, or is it enough to just wait for the buildds to build the newest simgear and flightgear after that? The can be scheduled against simgear-dev = 2.0.0-3; I have asked for a give-back on affected architectures and will follow up once the builds complete. ~Niels ___ pkg-fgfs-crew mailing list pkg-fgfs-c...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fgfs-crew signature.asc Description: This is a digitally signed message part
Bug#630280: Processed: severity of 630305 is serious, severity of 630280 is serious, severity of 630265 is serious
Le Mon, 1 Aug 2011 19:22:45 +0200, Helge Kreutzmann deb...@helgefjell.de a écrit : Hello Laurent, Hi, On Sun, Jul 31, 2011 at 09:25:56PM +0200, Laurent Bigonville wrote: Well that pretty annoying. Do you think you could create a patch to fix this in the unstable version? The API has minimal changes and that shouldn't be to complicated. Otherwise the release will remove it from testing to allow the transition of libnotify. I'd rather fix this in one step. Do you know any reason why 629566 can't be resolved? Unfortunately they (you? see below) do not respond to the bug report, and currently I cannot mail them directly (582765). Well uploading brasero 3 requires other packages to be uploaded in unstable first (mainly nautilus) and would requires all packages using libbrasero-media to be updated to gtk3. So that's not that easy. Of course I could see if I could do an upload just fixing your transition, but it's not like I'm bored and do not have anything else to do. And if I knew a reason/timeframe for the libbrasero-media3-dev upload, then I could of course adjust. But I would not be very happy to do the extra work for an upload fixing the libnotify transition alone just to find out two days later that libbrasero-media3-dev was uploaded. And especially given that both libnotify *and* libbrasero-media3-dev have the same maintainer I find it somewhat strange that the intermix (which I denoted by the proper blocks in the BTS) cannot be resolved! (And not even a simple ack to my bug report almost 2 month ago is possible). That's the game of the soname transition, the release team try to make a transition at a time, to avoid to much contention.. And as said, brasero 3 requires a lot of new libraries from GNOME3 and some of them also require transitions that's why the upload of GNOME 3 in unstable is slow. And removing goobox from unstable would punish the wrong guy/would be quite discouraging. I uploaded to experimental the same day you reported the transition (btw. without a set timeframe), i.e. it's not like I'm not responsive. I even talked with my previous sponsor about this bug before I went on vacation some weeks ago, in case something was happening with 629566. Well the the removal of a package from testing is in release team hands, so I cannot speak for them, but the best to ensure that the package stay in testing is to patch it to use the new API of libnotify. If you need help for the patch feel free to ask on the #debian-gnome on OTFC irc network, or I'll see if I can have a look at it. Regards Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only `return' from a function or sourced script
Package: laptop-mode-tools Version: 1.58-2 Severity: grave failed (disabled, not active). ... failed (enabled, not active). Package promises much, but is (sadly) unusable :( Thus removed. Now, it's essential scripting stuff. You just don't do: return 0; Maybe: exit 0 which would mean ignore all errors that may have occured, but how smart would that be? Just skip that all together and handle errors as they may occur, instead. That would be smarter, indeed. That script is in a deplorable hackish state :( I doubt _all_ those forked subshells '(...)' are really necessary, for example. Would you be intrested in getting patches? Is there a debian repository you keep the code in? -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages laptop-mode-tools depends on: ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii psmisc22.14-1utilities that use the proc file s ii util-linux2.19.1-4 Miscellaneous system utilities Versions of packages laptop-mode-tools recommends: ii acpid 1:2.0.10-1 Advanced Configuration and Power I ii ethtool 1:2.6.39-1 display or change Ethernet device ii hal 0.5.14-6 Hardware Abstraction Layer ii hdparm9.32-1 tune hard disk parameters for high ii net-tools 1.60-24.1 The NET-3 networking toolkit ii sdparm1.06-3 Output and modify SCSI device para ii udev 172-1 /dev/ and hotplug management daemo ii wireless-tools30~pre9-5 Tools for manipulating Linux Wirel laptop-mode-tools suggests no packages. -- no debconf information Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#630280: Processed: severity of 630305 is serious, severity of 630280 is serious, severity of 630265 is serious
Hello Laurent, On Mon, Aug 01, 2011 at 08:34:11PM +0200, Laurent Bigonville wrote: Le Mon, 1 Aug 2011 19:22:45 +0200, Helge Kreutzmann deb...@helgefjell.de a écrit : On Sun, Jul 31, 2011 at 09:25:56PM +0200, Laurent Bigonville wrote: Well that pretty annoying. Do you think you could create a patch to fix this in the unstable version? The API has minimal changes and that shouldn't be to complicated. Otherwise the release will remove it from testing to allow the transition of libnotify. I'd rather fix this in one step. Do you know any reason why 629566 can't be resolved? Unfortunately they (you? see below) do not respond to the bug report, and currently I cannot mail them directly (582765). Well uploading brasero 3 requires other packages to be uploaded in unstable first (mainly nautilus) and would requires all packages using libbrasero-media to be updated to gtk3. So that's not that easy. Ok, this makes sense. So from this I gather that this upload is some time off. Of course I could see if I could do an upload just fixing your transition, but it's not like I'm bored and do not have anything else to do. And if I knew a reason/timeframe for the libbrasero-media3-dev upload, then I could of course adjust. But I would not be very happy to do the extra work for an upload fixing the libnotify transition alone just to find out two days later that libbrasero-media3-dev was uploaded. And especially given that both libnotify *and* libbrasero-media3-dev have the same maintainer I find it somewhat strange that the intermix (which I denoted by the proper blocks in the BTS) cannot be resolved! (And not even a simple ack to my bug report almost 2 month ago is possible). That's the game of the soname transition, the release team try to make a transition at a time, to avoid to much contention.. No problem, but somehow dependencies do exist when upstream upgrades all dependencies (ports to modern libraries). And as said, brasero 3 requires a lot of new libraries from GNOME3 and some of them also require transitions that's why the upload of GNOME 3 in unstable is slow. Ok. And removing goobox from unstable would punish the wrong guy/would be quite discouraging. I uploaded to experimental the same day you reported the transition (btw. without a set timeframe), i.e. it's not like I'm not responsive. I even talked with my previous sponsor about this bug before I went on vacation some weeks ago, in case something was happening with 629566. Well the the removal of a package from testing is in release team hands, so I cannot speak for them, but the best to ensure that the package stay in testing is to patch it to use the new API of libnotify. I understand. Given the information you just provided I'll see if I can decouple the transitions in goobox as well, as less as I like it, though. My wish for next time would be to responde to bugs/e-mails with text much sooner, this avoids confusion and speeds things up (goobox would probably be in Testing already). Especially when a lonley bug asks for an upload. If you need help for the patch feel free to ask on the #debian-gnome on OTFC irc network, or I'll see if I can have a look at it. I'll see how far I get myself. I vaguely remember seeing a simple patch in the git repository before the upstream tarball was created, so I might grab that one. Tonight I'll probably do not manage to check it out and tomorrow I'll be probably offline. So probabyl on Wednesday I'll see if I can prepare a new version. To be on the safe side, would an upload at the latest on the weekend be soon enough? (I'll probably would like to check out the resulted binary before upload, given that I do not use the new upstream version). Thanks! Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#636258: firmware-b43-installer: exits from postinst with error code 1
Package: firmware-b43-installer Version: 1:014-6 Severity: grave Tags: patch lakeview no % sudo dpkg --configure -a Setting up firmware-b43-installer (1:014-6) ... dpkg: error processing firmware-b43-installer (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: firmware-b43-installer Running the shell script under sh -x produces: lakeview no % sudo sh -x /var/lib/dpkg/info/firmware-b43-installer.postinst configure + set -e + uname -r + cut -d- -f1 + dpkg --compare-versions 2.6.25 gt 3.0.0 + + grep -o 14e4:4320 (rev 03) lspci -n + chip= So basically, the grep is failing, and so under set -e, the script fails. I've tested this theory by doing: lakeview ok % chip=`lspci -n | grep -o 14e4:4320 (rev 03)` bmc@lakeview:/tmp (2011-08-01/19:15:21)(pts/7)(ac+100%)(failed:1:none) And this causes a failure with error 1 (as you can see by failed:1). Adding || true to the end of the line makes it succeed, and I've attached a patch that does that. I've marked this grave since the package fails to install for any b43 user other than those using 14e4:4320 rev 3. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages firmware-b43-installer depends on: ii b43-fwcutter 1:014-6Utility for extracting Broadcom 43 ii bzip2 1.0.5-6high-quality block-sorting file co ii wget 1.12-5 retrieves files from the web Versions of packages firmware-b43-installer recommends: ii linux-image-2 2.6.39-3 Linux 2.6.39 for 64-bit PCs ii linux-image-3 3.0.0-1Linux 3.0.0 for 64-bit PCs ii linux-image-3 3.0.0-1Linux 3.0.0 for 64-bit PCs, PREEMP ii linux-image-3 3.0.0~rc6-1~experimental.1 Linux 3.0.0-rc6 for 64-bit PCs firmware-b43-installer suggests no packages. -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 --- /tmp/firmware-b43-installer.postinst 2011-08-01 19:19:39.427865365 + +++ /var/lib/dpkg/info/firmware-b43-installer.postinst 2011-08-01 19:19:46.0 + @@ -38,7 +38,7 @@ } # Fix for BCM4306/3 [14e4:4320] (rev 03) -chip=`lspci -n | grep -o 14e4:4320 (rev 03)` +chip=`lspci -n | grep -o 14e4:4320 (rev 03)` || true if [ $chip ] ; then echo Your card is BCM4306/3 [14e4:4320] (rev 03), firwmare 5.10.56.27.3 will be used latest_firmware signature.asc Description: Digital signature
Bug#633545: marked as done (glitch: broken package after rebuild)
Your message dated Mon, 01 Aug 2011 19:32:10 + with message-id e1qnydi-0002au...@franck.debian.org and subject line Bug#633545: fixed in glitch 0.6-2.1 has caused the Debian Bug report #633545, regarding glitch: broken package after rebuild 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.) -- 633545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: glitch Version: 0.6-1 Severity: serious I rebuilt glitch in a clean chroot. The resulting binary package was virtually empty: $ dpkg -c python-glitch_0.6-1_all.deb | grep -v '/share/doc/' drwxr-xr-x root/root 0 2011-07-11 14:53 ./ drwxr-xr-x root/root 0 2011-07-11 14:53 ./usr/ drwxr-xr-x root/root 0 2011-07-11 14:53 ./usr/share/ The interesting part of the build log: | dh build |dh_testdir |dh_auto_configure |dh_auto_build | Can't exec pyversions: No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 120. | Use of uninitialized value $python_default in substitution (s///) at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 121. | Use of uninitialized value $python_default in substitution (s///) at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 122. |dh_auto_test | fakeroot debian/rules binary | dh binary |dh_testroot |dh_prep |dh_installdirs |dh_auto_install | Can't exec pyversions: No such file or directory at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 120. | Use of uninitialized value $python_default in substitution (s///) at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 121. | Use of uninitialized value $python_default in substitution (s///) at /usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm line 122. Let me guess, missing build-dependency on python (and python-support)? -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: glitch Source-Version: 0.6-2.1 We believe that the bug you reported is fixed in the latest version of glitch, which is due to be installed in the Debian FTP archive: glitch_0.6-2.1.debian.tar.gz to main/g/glitch/glitch_0.6-2.1.debian.tar.gz glitch_0.6-2.1.dsc to main/g/glitch/glitch_0.6-2.1.dsc python-glitch_0.6-2.1_all.deb to main/g/glitch/python-glitch_0.6-2.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 633...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jakub Wilk jw...@debian.org (supplier of updated glitch 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: Wed, 27 Jul 2011 20:51:18 +0200 Source: glitch Binary: python-glitch Architecture: source all Version: 0.6-2.1 Distribution: unstable Urgency: low Maintainer: Dafydd Harries d...@debian.org Changed-By: Jakub Wilk jw...@debian.org Description: python-glitch - Python library for OpenGL graphics programming Closes: 633545 Changes: glitch (0.6-2.1) unstable; urgency=low . * Non-maintainer upload. * Add build-dependency on python-all and python-support (closes: #633545). Checksums-Sha1: 6d12f8d3a7de2b3a6c22d321ecd7a0c16f9218f3 1823 glitch_0.6-2.1.dsc 459a8ebc6db4f132abb03102f40f1ab59fa89427 1535 glitch_0.6-2.1.debian.tar.gz f3c438dbf9aa50e566bfd6932c5017d447262915 34816 python-glitch_0.6-2.1_all.deb Checksums-Sha256: d02798c24814f0f06c171afc9278fdd00c08751f394808da8b272f1813a6106c 1823 glitch_0.6-2.1.dsc 7f92add32ce055219bc49214fd9fc5d712c1575ade70f4820a5c1ee12790c03c 1535 glitch_0.6-2.1.debian.tar.gz 08fa8bb8951a1441a1898de458732b119aaf12d0a6f8ad46361a4714e8690566 34816 python-glitch_0.6-2.1_all.deb Files: 6ead244a1102e19e75459917fa055603 1823 python optional glitch_0.6-2.1.dsc 6984abb80953207269b0c86690a9e668 1535 python optional glitch_0.6-2.1.debian.tar.gz 497f7b3d47e25099b8b5db4acbf84cf7 34816 python optional python-glitch_0.6-2.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOMGJdAAoJEC1Os6YBVHX1becP/0N79uS7Rk/5y85iKjOgsjlW PWeWtT+3AHVdBDlZd0r99q6sLiFv3Sz5T7llCOVXP8VbpLplEPs6xM8NGdaMOVzk
Bug#626667: marked as done ([nvidia-glx-legacy-96xx] conflicts with Xorg 1.10)
Your message dated Mon, 01 Aug 2011 19:32:54 + with message-id e1qnyeq-0002ah...@franck.debian.org and subject line Bug#626667: fixed in nvidia-graphics-drivers-legacy-96xx 96.43.20-1 has caused the Debian Bug report #626667, regarding [nvidia-glx-legacy-96xx] conflicts with Xorg 1.10 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.) -- 626667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nvidia-glx-legacy-96xx Version: 96.43.19-1 Severity: grave Version 96xx has not been updated for X.org server 1.10, which could transition to testing soon: # LANG=C apt-get install nvidia-glx-legacy-96xx Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: nvidia-glx-legacy-96xx : Depends: xorg-video-abi-8 or xorg-video-abi-6.0 but it is not installable or xserver-xorg-core ( 2:1.7.7) but 2:1.10.1-2 is to be installed E: Broken packages root@vinci:/etc/modprobe.d# --- System information. --- Architecture: i386 Kernel: Linux 2.6.37-1-686-bigmem Debian Release: wheezy/sid 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org 1 experimental ftp.ca.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Source: nvidia-graphics-drivers-legacy-96xx Source-Version: 96.43.20-1 We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-legacy-96xx, which is due to be installed in the Debian FTP archive: libgl1-nvidia-legacy-96xx-glx-ia32_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/libgl1-nvidia-legacy-96xx-glx-ia32_96.43.20-1_amd64.deb libgl1-nvidia-legacy-96xx-glx_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/libgl1-nvidia-legacy-96xx-glx_96.43.20-1_amd64.deb nvidia-alternative-legacy-96xx_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-alternative-legacy-96xx_96.43.20-1_amd64.deb nvidia-glx-legacy-96xx-ia32_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-glx-legacy-96xx-ia32_96.43.20-1_amd64.deb nvidia-glx-legacy-96xx_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-glx-legacy-96xx_96.43.20-1_amd64.deb nvidia-graphics-drivers-legacy-96xx_96.43.20-1.debian.tar.gz to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-graphics-drivers-legacy-96xx_96.43.20-1.debian.tar.gz nvidia-graphics-drivers-legacy-96xx_96.43.20-1.dsc to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-graphics-drivers-legacy-96xx_96.43.20-1.dsc nvidia-graphics-drivers-legacy-96xx_96.43.20.orig.tar.gz to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-graphics-drivers-legacy-96xx_96.43.20.orig.tar.gz nvidia-kernel-legacy-96xx-dkms_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-kernel-legacy-96xx-dkms_96.43.20-1_amd64.deb nvidia-kernel-legacy-96xx-source_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/nvidia-kernel-legacy-96xx-source_96.43.20-1_amd64.deb xserver-xorg-video-nvidia-legacy-96xx_96.43.20-1_amd64.deb to non-free/n/nvidia-graphics-drivers-legacy-96xx/xserver-xorg-video-nvidia-legacy-96xx_96.43.20-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 626...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann deb...@abeckmann.de (supplier of updated nvidia-graphics-drivers-legacy-96xx 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: Mon, 01 Aug 2011 21:00:17 +0200 Source: nvidia-graphics-drivers-legacy-96xx Binary:
Bug#631068: nyquist: Commercial use of xlisp not allowed
On Sat, Jul 23, 2011 at 01:05:51AM -0500, Steve M. Robbins wrote: On Sat, Jun 25, 2011 at 07:52:01PM +0200, Sam Geeraerts wrote: The file xlisp/xlbfun.c contains the following license notice: /* Copyright (c) 1985, by David Michael Betz All Rights Reserved Permission is granted for unrestricted non-commercial use */ This clearly does not permit commercial use. In the worst interpretation it also doesn't allow modification or distribution. Nearly the same file is also used in Audacity, see bug 631068. I've just checked and found the latest release of xlisp [ http://www.xlisp.org/ ] has a new license that is compatible the DFSG. After an email conversation with the authors of nyquist and xlisp, I learned that the Mr. Betz had, in fact, relicensed xlisp under the terms that appear in the second part of the copyright statement, reproduced below. Since this is compatible with DFSG, I'm closing this bug for nyquist. -Steve COPYRIGHT AND LICENSE INFORMATION FOR XLISP Copyright (c) 1984-2002, by David Michael Betz All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of David Michael Betz nor the names of any contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. What follows is not a part of the license: Please send bug fixes and improvements to me at the address below. In addition, as a courtesy, I ask that you send me a copy of any product that makes substantial use of XLISP. Please contact me at the address below for my current mailing address. I am asking this because I enjoy learning about applications of my software. David Betz db...@xlisper.mv.com signature.asc Description: Digital signature
Bug#631646: marked as done (nyquist: Commercial use of xlisp not allowed)
Your message dated Mon, 1 Aug 2011 14:42:26 -0500 with message-id 20110801194226.ga3...@sumost.ca and subject line Re: nyquist: Commercial use of xlisp not allowed has caused the Debian Bug report #631646, regarding nyquist: Commercial use of xlisp not allowed 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.) -- 631646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nyquist Version: 2.29-6 Severity: serious Justification: Policy 2.1.6 User: gnewsense-...@nongnu.org Usertags: gnewsense libreplanet The file xlisp/xlbfun.c contains the following license notice: /* Copyright (c) 1985, by David Michael Betz All Rights Reserved Permission is granted for unrestricted non-commercial use */ This clearly does not permit commercial use. In the worst interpretation it also doesn't allow modification or distribution. Nearly the same file is also used in Audacity, see bug 631068. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nyquist depends on: ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-3 shared libraries for terminal hand ii libreadline5 5.2-7 GNU readline and history libraries nyquist recommends no packages. nyquist suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Sat, Jul 23, 2011 at 01:05:51AM -0500, Steve M. Robbins wrote: On Sat, Jun 25, 2011 at 07:52:01PM +0200, Sam Geeraerts wrote: The file xlisp/xlbfun.c contains the following license notice: /* Copyright (c) 1985, by David Michael Betz All Rights Reserved Permission is granted for unrestricted non-commercial use */ This clearly does not permit commercial use. In the worst interpretation it also doesn't allow modification or distribution. Nearly the same file is also used in Audacity, see bug 631068. I've just checked and found the latest release of xlisp [ http://www.xlisp.org/ ] has a new license that is compatible the DFSG. After an email conversation with the authors of nyquist and xlisp, I learned that the Mr. Betz had, in fact, relicensed xlisp under the terms that appear in the second part of the copyright statement, reproduced below. Since this is compatible with DFSG, I'm closing this bug for nyquist. -Steve COPYRIGHT AND LICENSE INFORMATION FOR XLISP Copyright (c) 1984-2002, by David Michael Betz All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of David Michael Betz nor the names of any contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. What follows is not a part of the license: Please send bug fixes and improvements to me at the address below. In addition, as a courtesy, I ask that you send me a copy of any product that makes substantial use of XLISP. Please contact me at the address below for my current mailing address. I am asking
Bug#615018: Please fix this
Hi, Could somebody please fix this soon? It's been over 5 months! I'm happy to help if needed (I have packaged a few debs before for personal use). Saman -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636188: xscorch: Please transition to use libreadline6-dev
Hi, On Tue, Aug 02, 2011 at 01:31:46AM +0800, Aron Xu wrote: As you have written libreadline5-dev | libreadline6-dev, then I assume you have the sense that there is probably license issue with libreadline6-dev, so you choose libreadline5-dev over it by default, and you keep the latter one because it might be useful for those who want to compile binary packages themselves. Actually, I was unaware of the license issue and don't really care what version of readline is used. XScorch works fine with both. I looked for libreadline-dev which would have been most convenient and when I didn't find it, I wrote a dep on both so I could still compile the package on older systems. The issue with the buildds using only the first dep is new to me and I really appreciate the information. I will start writing deps newest-to-oldest in my control files. OK, then you need to check whether your build is correct, by running lintian *and* checking the build log at least. You have tested it with lintian already, then you forgot to check your log. I checked the log. It built fine. I didn't see any output I considered significant. However, I wasn't aware of the GPL issue. My omniscience level has been a bit low lately. Thanks, -Jacob -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636220: marked as done (rhythmbox-plugins: Status icon plugin stopped working in 0.12.8-4)
Your message dated Mon, 01 Aug 2011 19:48:59 + with message-id e1qnytz-0004xl...@franck.debian.org and subject line Bug#636220: fixed in rhythmbox 0.12.8-5 has caused the Debian Bug report #636220, regarding rhythmbox-plugins: Status icon plugin stopped working in 0.12.8-4 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.) -- 636220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rhythmbox-plugins Version: 0.12.8-4 Severity: normal Since recent 0.12.8-4 update, status icon plugin fails to load because of the undefined symbol notify_notification_attach_to_status_icon: (rhythmbox:3918): Rhythmbox-WARNING **: /usr/lib/rhythmbox/plugins/status-icon/libstatus-icon.so: undefined symbol: notify_notification_attach_to_status_icon (rhythmbox:3918): Rhythmbox-WARNING **: Could not load plugin status-icon (rhythmbox:3918): Rhythmbox-WARNING **: Error, impossible to activate plugin 'Status Icon' -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rhythmbox-plugins depends on: ii libatk1.0-0 2.0.1-2 ATK accessibility toolkit ii libavahi-client30.6.30-5 Avahi client library ii libavahi-common30.6.30-5 Avahi common library ii libavahi-glib1 0.6.30-5 Avahi glib integration library ii libc6 2.13-13 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6.1 The Cairo 2D vector graphics libra ii libdbus-1-3 1.4.14-1 simple interprocess messaging syst ii libdbus-glib-1-20.94-4 simple interprocess messaging syst ii libfontconfig1 2.8.0-3 generic font configuration library ii libfreetype62.4.4-2 FreeType 2 font engine, shared lib ii libgconf2-4 2.32.4-1 GNOME configuration database syste ii libgdk-pixbuf2.0-0 2.23.5-3 GDK Pixbuf library ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgnome-keyring0 3.0.3-1 GNOME keyring services library ii libgnome-media0 2.30.0-1 runtime libraries for the GNOME me ii libgpod40.8.0-3 library to read and write songs an ii libgstreamer-plugins-ba 0.10.35-1GStreamer libraries from the base ii libgstreamer0.10-0 0.10.35-1Core GStreamer libraries and eleme ii libgtk2.0-0 2.24.5-4 GTK+ graphical user interface libr ii libgudev-1.0-0 172-1GObject-based wrapper library for ii liblircclient0 0.9.0~pre1-1 infra-red remote control support - ii libmtp8 1.0.6-7 Media Transfer Protocol (MTP) libr ii libmusicbrainz4c2a 2.1.5-5 Second generation incarnation of t ii libnotify4 0.7.3-2 sends desktop notifications to a n ii libpango1.0-0 1.28.4-2 Layout and rendering of internatio ii libsoup-gnome2.4-1 2.34.3-1 HTTP library implementation in C - ii libsoup2.4-12.34.3-1 HTTP library implementation in C - ii libtotem-plparser17 2.32.5-2 Totem Playlist Parser library - ru ii libusb-0.1-42:0.1.12-18 userspace USB programming library ii libxml2 2.7.8.dfsg-4 GNOME XML library ii python 2.6.7-2 interactive high-level object-orie ii python-gnomekeyring 2.32.0-1 Python bindings for the GNOME keyr ii python-mako 0.4.1-2 fast and lightweight templating fo ii python-support 1.0.14 automated rebuilding support for P ii python-webkit 1.1.8-2 WebKit/Gtk Python bindings ii rhythmbox 0.12.8-4 music player and organizer for GNO ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages rhythmbox-plugins recommends: ii nautilus-sendto 2.28.4-2+b1 integrates Evolution and Pidgin in rhythmbox-plugins suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: rhythmbox Source-Version: 0.12.8-5 We believe that the bug you reported is fixed in the latest version of rhythmbox, which is due to
Bug#636251: laptop-mode-tools: Enabling laptop mode.../usr/sbin/laptop_mode: line 1143: return: can only `return' from a function or sourced script
On 08/02/2011 12:10 AM, Cristian Ionescu-Idbohrn wrote: failed (disabled, not active). ... failed (enabled, not active). Package promises much, but is (sadly) unusable :( Thus removed. 22:55:01 rrs@champaran:~/devel/apt-offline/apt-offline (debian)$ sudo /etc/init.d/laptop-mode restart [sudo] password for rrs: Disabling laptop mode...done (8514 disabled, not active). Enabling laptop mode...done (enabled, not active). 01:20:27 rrs@champaran:~/devel/apt-offline/apt-offline (debian)$ sudo /etc/init.d/laptop-mode restart Disabling laptop mode...done (20610 disabled, not active 20610). Enabling laptop mode...done (20610 enabled, active 20610). Now, it's essential scripting stuff. You just don't do: return 0; Maybe: exit 0 which would mean ignore all errors that may have occured, but how smart would that be? Exactly. Can you test and report this? Just skip that all together and handle errors as they may occur, instead. That would be smarter, indeed. This would be better. I haven't tested what the default return is. If you can test, that'll be great. With the new 1.58 release, the last snippet in the laptop_mode script is the lm-polling-daemon invocation. Now its exit status could be different depending on the various circumstances (number of events, invocations etc). So you testing will help here. That script is in a deplorable hackish state :( I doubt _all_ those forked subshells '(...)' are really necessary, for example. Would you be intrested in getting patches? Is there a debian repository you keep the code in? Yes. https://github.com/rickysarraf/laptop-mode-tools Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Debian defaults to dash. And that is what laptop-mode-tools tries to adhere to. But that doesn't mean it shouldn't work with bash. Can you try with dash as your system default shell? -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#636251: [Bug 815201] Re: /usr/sbin/laptop_mode: line 1143: return: can only `return' from a function or sourced script
On 07/28/2011 04:10 AM, Ritesh Raj Sarraf wrote: On 07/28/2011 02:57 AM, Eric Belanger wrote: That would work but I'm not sure if the shell will interpret the return value as being for the script rather than for the function itself. How about replacing 'return 0' by 'exit 0' ? That seems to be better suited for the situation as we are exiting the script at that point. And it is accepted by bash. Great. Thanks. I'll test it out I think I'll go with exit 0. Line #1089 in 1.58 laptop-mode script already did exit 0 gracefully. We already log/print error message if any, so we don't worry about the final exit code. It just got ignored now because of the polling fix I did. I need to add locking for the polling code also. For now, please use exit 0 and report back if it causes any other problems. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: OpenPGP digital signature
Bug#635382: latex-unicode sources and licensing
Norbert Preining prein...@logic.at wrote: Hi everyone, 1) Include that license in debian/copyright, document which part it applies to. Just to make one thing clear. *I* will not go down this road. I will *never* collect the license statements 15000+ files. [...] I take the license statement of the TeX Live compilation as reference ppint. Please don't overreact. Upstream has a fine mechanism to record licenses of packages and even individual files, and all we need to do is to find someone with write access to The Catalogue (like you or me) to record the information there - and it will find its way into Debian. Lionel is not aware of this mechanism, so it is only natural what he suggests. Which is essentially what we do, just not by firing up an editor on debian/copyright. Regards, Frank -- Frank Küster Sprecher B90/Grüne OV Miltenberg und Umgebung VCD Miltenberg, ADFC Aschaffenburg-Miltenberg Debian Developer (TeXLive) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopen
Processing commands for cont...@bugs.debian.org:
reopen 615263
Bug #615263 {Done: Tino Keitel tino.kei...@tikei.de} [src:syncevolution]
syncevolution: FTBFS due to gcc-4.4 / linker changes
Bug #615782 {Done: Tino Keitel tino.kei...@tikei.de} [src:syncevolution]
syncevolution: ftbfs with gold or ld --no-add-needed
Bug #618113 {Done: Tino Keitel tino.kei...@tikei.de} [src:syncevolution]
syncevolution: FTBFS: libsmltk.so.0: could not read symbols: Invalid operation
thanks
Stopping processing here.
Please contact me if you need assistance.
--
615263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615263
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: Upstream
Processing commands for cont...@bugs.debian.org: tag 636001 upstream Bug #636001 [clementine] clementine: FTBFS in qFuzzyCompare on armel, armhf and sh4 Added tag(s) upstream. forwarded 636001 http://code.google.com/p/clementine-player/issues/detail?id=2120 Bug #636001 [clementine] clementine: FTBFS in qFuzzyCompare on armel, armhf and sh4 Set Bug forwarded-to-address to 'http://code.google.com/p/clementine-player/issues/detail?id=2120'. thanks Stopping processing here. Please contact me if you need assistance. -- 636001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636001 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#636001: Upstream
tag 636001 upstream forwarded 636001 http://code.google.com/p/clementine-player/issues/detail?id=2120 thanks While we will surely apply this patch, I am also forwarding it upstream. -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#636147: /etc/editorrc ?
Hi, I just ran into a funny problem regarding update-alternatives and editorrc: if joe is installed, it wants /etc/joe/editorrc whereas jupp reads /etc/jupp/editorrc (I’ll use joe’s for now and symlink to it but that will break when joe was installed, jupp is selected and joe is then removed… probably, that is – not RC severity but to be fixed before the release – I think, /etc/joe will simply still exist and dpkg not rmdir.) Can we agree to move the 'editorrc' alternative to /etc and symlink to that from /etc/joe/editorrc and /etc/jupp/editorrc both? Can we also prod the update-alternatives people to make editorrc a slave to editor, since that’s really the only way? (What didn’t work? You only wrote it didn’t work in joe-3.5’s changelog entry.) Thanks, //mirabilos -- Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL. -- Henry Nelson, March 1999 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615018: [Evolution] Bug#615018: Please fix this
On lun., 2011-08-01 at 19:25 +, Saman Ghannadzadeh wrote: I'm happy to help if needed (I have packaged a few debs before for personal use). Definitely. Please go ahead. -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#636270: FTBFS: test failure: Failed test 'direct split (yahoo) (rows)'
Source: libfinance-quotehist-perl Version: 1.16-1 Severity: serious Justification: fails to build from source (but built successfully in the past) This package FTBFS with a clean sid chroot: WARNING: Could not fetch split for some symbols (CPKI). Abandoning request for t hese symbols. Don't worry, though, we were looking for splits. These are less li kely to exist compared to quotes. # Failed test 'direct split (yahoo) (rows)' # at t/30_splits.t line 35. # got: 0 # expected: 1 # Failed test 'direct split (yahoo) (content)' # at t/30_splits.t line 39. # Structures begin differing at: # $got-[0] = Does not exist # $expected-[0] = 'CPKI:2007/06/19:3:2' # Looks like you failed 2 tests of 6. This is upstream https://rt.cpan.org/Public/Bug/Display.html?id=69724 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 636270 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=69724
Processing commands for cont...@bugs.debian.org: forwarded 636270 https://rt.cpan.org/Public/Bug/Display.html?id=69724 Bug #636270 [src:libfinance-quotehist-perl] FTBFS: test failure: Failed test 'direct split (yahoo) (rows)' Set Bug forwarded-to-address to 'https://rt.cpan.org/Public/Bug/Display.html?id=69724'. thanks Stopping processing here. Please contact me if you need assistance. -- 636270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636270 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#636147: marked as done (jupp: removes /etc/joe/editorrc, breaking joe)
Your message dated Mon, 01 Aug 2011 21:04:49 +
with message-id e1qnzfn-0001cq...@franck.debian.org
and subject line Bug#636147: fixed in jupp 3.1.17-4
has caused the Debian Bug report #636147,
regarding jupp: removes /etc/joe/editorrc, breaking joe
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.)
--
636147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: jupp
Version: 3.1.17-2
Severity: serious
Justification: wheezy RC policy §3
Jupp hijacks the editorrc alternative from joe, moving it from
/etc/joe/editorrc to /etc/jupp/editorrc. This breaks joe if it is set
as the default system editor:
# dpkg-query -W joe
joe 3.7-2
# ls -F /etc/joe/
editorrc@ ftyperc jicerc.ru jmacsrc joerc jpicorc jstarrc rjoerc
# apt-get install -qq --trivial-only jupp
Selecting previously deselected package jupp.
(Reading database ... 465741 files and directories currently installed.)
Unpacking jupp (from .../jupp_3.1.17-2_i386.deb) ...
Processing triggers for man-db ...
Setting up jupp (3.1.17-2) ...
update-alternatives: renaming editorrc link from /etc/joe/editorrc to
/etc/jupp/editorrc.
# ls -F /etc/joe/
ftyperc jicerc.ru jmacsrc joerc jpicorc jstarrc rjoerc
# file /etc/alternatives/editor{,rc}
/etc/alternatives/editor: symbolic link to `/usr/bin/joe'
/etc/alternatives/editorrc: symbolic link to `/etc/joe/joerc'
# editor
Couldn't open '*editorrc'
#
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.0.0-00150-gb3626c5 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages jupp depends on:
ii libc6 2.13-10Embedded GNU C Library: Shared lib
ii libncurses5 5.9-1 shared libraries for terminal hand
ii libselinux1 2.0.98-1.1 SELinux runtime shared libraries
jupp recommends no packages.
jupp suggests no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: jupp
Source-Version: 3.1.17-4
We believe that the bug you reported is fixed in the latest version of
jupp, which is due to be installed in the Debian FTP archive:
joe-jupp_3.1.17-4_all.deb
to main/j/jupp/joe-jupp_3.1.17-4_all.deb
jupp_3.1.17-4.diff.gz
to main/j/jupp/jupp_3.1.17-4.diff.gz
jupp_3.1.17-4.dsc
to main/j/jupp/jupp_3.1.17-4.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 636...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thorsten Glaser t...@mirbsd.de (supplier of updated jupp 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: SHA384
Format: 1.8
Date: Mon, 01 Aug 2011 20:08:11 +
Source: jupp
Binary: jupp joe-jupp
Architecture: source all
Version: 3.1.17-4
Distribution: unstable
Urgency: low
Maintainer: Thorsten Glaser t...@mirbsd.de
Changed-By: Thorsten Glaser t...@mirbsd.de
Description:
joe-jupp - reimplement the joe Debian package using jupp
jupp - user friendly full screen text editor
Closes: 636147
Changes:
jupp (3.1.17-4) unstable; urgency=low
.
* Work also when joe is not installed (Really Closes: #636147)
Checksums-Sha1:
455efbf050a0be01d20cf98678960682383e4493 1856 jupp_3.1.17-4.dsc
bf6e9ed88f8e4ca73222f191f695147b57b9988f 6734 jupp_3.1.17-4.diff.gz
ee13798a5226c725f3577ef87a526b5341013a5f 20174 joe-jupp_3.1.17-4_all.deb
Checksums-Sha256:
2334aef740fdd5726bbdb70f4e1569fd85a00726cdf5b8eec65d751ec7c924aa 1856
jupp_3.1.17-4.dsc
d288500b5e0854b117fd309d2b8ae4f122e500543c423618789af986e4a75a88 6734
jupp_3.1.17-4.diff.gz
a1bf81ed3508dd636380326c653587fa4d0aacd0dbe2f67d50f82ebdfb01fbff 20174
joe-jupp_3.1.17-4_all.deb
Files:
8a958e360c3427c9887f3e3804378d8e 1856 editors optional jupp_3.1.17-4.dsc
cacf2b5de2fd0e0cc96ebddbdb8fa5d3 6734 editors optional jupp_3.1.17-4.diff.gz
5f8fb08b28d0d6e2008aaae04a20a858 20174 editors optional
joe-jupp_3.1.17-4_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MirBSD)
iQIcBAEBCQAGBQJONwi3AAoJEHa1NLLpkAfg8lYQAMnth3CEiwspRDr5A1COrXwL
Bug#636274: i3-wm: FTBFS: fatal error: i3/ipc.h: No such file or directory
Package: src:i3-wm Version: 4.0-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: MAKE i3bar make[2]: Entering directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0/i3bar' CC src/child.c CC src/ipc.c src/ipc.c:18:20: fatal error: i3/ipc.h: No such file or directory compilation terminated. make[2]: *** [src/ipc.o] Error 1 make[2]: Leaving directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0/i3bar' make[1]: *** [subdirs] Error 2 make[1]: Leaving directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0' make: *** [build-stamp] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=i3-wmarch=kfreebsd-i386ver=4.0-1stamp=1312151907 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629665: marked as done (gcc-3.3: FTBFS: ld: cannot find crti.o: No such file or directory)
Your message dated Mon, 01 Aug 2011 21:47:23 +
with message-id e1qo0kz-0006zw...@franck.debian.org
and subject line Bug#629665: fixed in gcc-3.3 1:3.3.6ds1-24
has caused the Debian Bug report #629665,
regarding gcc-3.3: FTBFS: ld: cannot find crti.o: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
629665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: gcc-3.3
Version: 1:3.3.6ds1-23
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:
gcc -DIN_GCC -DHAVE_CONFIG_H -g -O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic
-Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic
-Wno-long-long -I. -I.. -I../../../src/gcc/fixinc
-I../../../src/gcc/fixinc/.. -I../../../src/gcc/fixinc/../config
-I../../../src/gcc/fixinc/../../include -o fixincl fixincl.o fixtests.o
fixfixes.o server.o procopen.o gnu-regex.o fixlib.o
/«BUILDDIR»/gcc-3.3-3.3.6ds1/build/gcc/../libiberty/libiberty.a
echo timestamp full-stamp
./fixincl -v /dev/null
'fixincl version 1.1'
chmod 755 ../fixinc.sh
make[5]: Leaving directory `/«BUILDDIR»/gcc-3.3-3.3.6ds1/build/gcc/fixinc'
rm -rf include; mkdir include
chmod a+rx include
(TARGET_MACHINE='x86_64-pc-linux-gnu'; srcdir=`cd ../../src/gcc;
${PWDCMD-pwd}`; \
SHELL='/bin/sh' ;\
export TARGET_MACHINE srcdir SHELL ; \
/bin/sh ./fixinc.sh `${PWDCMD-pwd}`/include /usr/include ; \
rm -f include/syslimits.h; \
if [ -f include/limits.h ]; then \
mv include/limits.h include/syslimits.h; \
else \
cp ../../src/gcc/gsyslimits.h include/syslimits.h; \
fi; \
chmod a+r include/syslimits.h)
Fixing headers into /«BUILDDIR»/gcc-3.3-3.3.6ds1/build/gcc/include for
x86_64-pc-linux-gnu target
Finding directories and links to directories
Searching /usr/include/.
Searching /usr/include/./c++/4.6.1
Making symbolic directory links
Fixing directory /usr/include into
/«BUILDDIR»/gcc-3.3-3.3.6ds1/build/gcc/include
Applying io_quotes_useto video/sisfb.h
Applying io_quotes_useto sys/mount.h
Applying io_quotes_useto sys/raw.h
Applying io_quotes_useto asm/mtrr.h
Applying sysv68_stringto string.h
Applying hpux8_bogus_inlines to math.h
Applying io_quotes_useto mtd/ubi-user.h
Applying limits_ifndefs to limits.h
Applying io_quotes_useto linux/input.h
Applying io_quotes_defto linux/ppp-comp.h
Applying io_quotes_defto linux/soundcard.h
Applying io_quotes_useto linux/fs.h
Applying io_quotes_useto linux/random.h
Applying io_quotes_useto linux/synclink.h
Applying io_quotes_useto linux/ipmi.h
Applying io_quotes_useto linux/raid/md_u.h
Applying io_quotes_useto linux/mmtimer.h
Applying io_quotes_useto linux/kvm.h
Applying io_quotes_useto linux/cciss_ioctl.h
Applying io_quotes_useto linux/rfkill.h
Applying io_quotes_useto linux/atmbr2684.h
Applying io_quotes_useto linux/raw.h
Applying io_quotes_useto linux/omapfb.h
Applying io_quotes_useto linux/cm4000_cs.h
Applying io_quotes_useto linux/auto_fs4.h
Applying io_quotes_useto linux/nbd.h
Applying io_quotes_useto linux/suspend_ioctls.h
Applying io_quotes_defto linux/pci_regs.h
Applying io_quotes_useto linux/vhost.h
Applying io_quotes_useto linux/auto_fs.h
Applying io_quotes_defto linux/version.h
Applying io_quotes_useto linux/dm-ioctl.h
Applying io_quotes_useto linux/if_pppox.h
Applying io_quotes_useto linux/i2o-dev.h
Applying io_quotes_useto linux/phantom.h
Applying io_quotes_useto linux/blkpg.h
Applying io_quotes_useto linux/usb/tmc.h
Applying io_quotes_useto linux/fd.h
Applying io_quotes_useto linux/dn.h
Applying io_quotes_useto linux/uinput.h
Applying io_quotes_useto linux/watchdog.h
Applying io_quotes_useto linux/gigaset_dev.h
Bug#636274: marked as done (i3-wm: FTBFS: fatal error: i3/ipc.h: No such file or directory)
Your message dated Mon, 01 Aug 2011 21:47:43 + with message-id e1qo0kt-000761...@franck.debian.org and subject line Bug#636274: fixed in i3-wm 4.0.1-1 has caused the Debian Bug report #636274, regarding i3-wm: FTBFS: fatal error: i3/ipc.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 636274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:i3-wm Version: 4.0-1 Severity: serious Tags: sid wheezy Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the buildds: MAKE i3bar make[2]: Entering directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0/i3bar' CC src/child.c CC src/ipc.c src/ipc.c:18:20: fatal error: i3/ipc.h: No such file or directory compilation terminated. make[2]: *** [src/ipc.o] Error 1 make[2]: Leaving directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0/i3bar' make[1]: *** [subdirs] Error 2 make[1]: Leaving directory `/build/buildd-i3-wm_4.0-1-kfreebsd-i386-9sygOI/i3-wm-4.0' make: *** [build-stamp] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=i3-wmarch=kfreebsd-i386ver=4.0-1stamp=1312151907 Regards Christoph -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? ---End Message--- ---BeginMessage--- Source: i3-wm Source-Version: 4.0.1-1 We believe that the bug you reported is fixed in the latest version of i3-wm, which is due to be installed in the Debian FTP archive: i3-wm-dbg_4.0.1-1_amd64.deb to main/i/i3-wm/i3-wm-dbg_4.0.1-1_amd64.deb i3-wm_4.0.1-1.diff.gz to main/i/i3-wm/i3-wm_4.0.1-1.diff.gz i3-wm_4.0.1-1.dsc to main/i/i3-wm/i3-wm_4.0.1-1.dsc i3-wm_4.0.1-1_amd64.deb to main/i/i3-wm/i3-wm_4.0.1-1_amd64.deb i3-wm_4.0.1.orig.tar.gz to main/i/i3-wm/i3-wm_4.0.1.orig.tar.gz i3_4.0.1-1_amd64.deb to main/i/i3-wm/i3_4.0.1-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 636...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg mich...@stapelberg.de (supplier of updated i3-wm 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: Mon, 01 Aug 2011 23:31:06 +0200 Source: i3-wm Binary: i3 i3-wm i3-wm-dbg Architecture: source amd64 Version: 4.0.1-1 Distribution: unstable Urgency: low Maintainer: Michael Stapelberg mich...@stapelberg.de Changed-By: Michael Stapelberg mich...@stapelberg.de Description: i3 - metapackage (i3 window manager, screen locker, menu, statusbar) i3-wm - improved dynamic tiling window manager i3-wm-dbg - Debugging symbols for the i3 window manager Closes: 636274 Changes: i3-wm (4.0.1-1) unstable; urgency=low . * Fix the build process of i3bar (Closes: #636274) * Fix the build process on Mac OS X * i3-config-wizard: also start i3bar in the keycode config template * userguide: Remove the obsolete bar.* colors * userguide: Use i3bar instead of dzen2 in the 'exec' example Checksums-Sha1: 6921ce32064c1e59a7588d1a31e28671a776f36b 1951 i3-wm_4.0.1-1.dsc a9b5f7cfcde940a9272eabcaba28d294a02f7dd4 564261 i3-wm_4.0.1.orig.tar.gz 36d52dfde250544a8acc315cff4fca39a9415b9e 9484 i3-wm_4.0.1-1.diff.gz 6077767a947d3754fd0e32381114383bef8a5ec2 8986 i3_4.0.1-1_amd64.deb 2df4146612fbe761010b4277e16d981405d82469 420358 i3-wm_4.0.1-1_amd64.deb 35dbf025cfddef8cfcee0b01b83f0d7208b82f08 2104354 i3-wm-dbg_4.0.1-1_amd64.deb Checksums-Sha256: cbc1c0cacfe4bb9d68aada6b9af5f39ae61f6c1c210f280caec9a8a5c19827b3 1951 i3-wm_4.0.1-1.dsc 19955ca769573c55420400879cfe3972a46da509b9376f741d823fecc342a58c 564261 i3-wm_4.0.1.orig.tar.gz 5058612e99de0322d4af72c7d81ab1a96c9c8a52f8f614fadd2fe5dac9b9e0e1 9484 i3-wm_4.0.1-1.diff.gz 89c076e44164e154c0aa40f12def09bf17842e7bd316b30d3826e52fa818519b 8986 i3_4.0.1-1_amd64.deb becedfcd16d2425ca36d2bb73d06c02055442d1b42ed75f0676d7faf161c0c5b 420358 i3-wm_4.0.1-1_amd64.deb 2a18728f201d5b32da49ef9cbae94b5eab481c0f6df4fd1c2175a04bc27f013c 2104354 i3-wm-dbg_4.0.1-1_amd64.deb Files:
Bug#630268: marked as done (evolution: Please transition to libnotify 0.7)
Your message dated Mon, 01 Aug 2011 22:02:48 + with message-id e1qo0zu-0001ta...@franck.debian.org and subject line Bug#630268: fixed in evolution 2.32.3-3 has caused the Debian Bug report #630268, regarding evolution: Please transition to libnotify 0.7 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.) -- 630268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: evolution Version: 2.32.3-1 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libnotify0.7-transition Hi, We are planning to transition[0] libnotify to version 0.7 which breaks its API. Unfortunately, after a rebuild it seems that your package FTBFS with the newer version. Packages of the 0.7 version can be currently found in experimental. API changes (shamelessly taken from[1]): notify_notification_new_with_status_icon is gone notify_notification_attach_to_status_icon is gone notify_notification_attach_to_widget is gone notify_notification_set_geometry_hints is gone notify_notification_new has lost its widget argument All rebuild logs can be found at: http://people.debian.org/~bigon/libnotify0.7_rebuildlog/ Cheers Laurent Bigonville [0] http://release.debian.org/transitions/html/libnotify.html [1] http://lists.fedoraproject.org/pipermail/devel/2010-November/144914.html ---End Message--- ---BeginMessage--- Source: evolution Source-Version: 2.32.3-3 We believe that the bug you reported is fixed in the latest version of evolution, which is due to be installed in the Debian FTP archive: evolution-common_2.32.3-3_all.deb to main/e/evolution/evolution-common_2.32.3-3_all.deb evolution-dbg_2.32.3-3_amd64.deb to main/e/evolution/evolution-dbg_2.32.3-3_amd64.deb evolution-dev_2.32.3-3_amd64.deb to main/e/evolution/evolution-dev_2.32.3-3_amd64.deb evolution-plugins-experimental_2.32.3-3_amd64.deb to main/e/evolution/evolution-plugins-experimental_2.32.3-3_amd64.deb evolution-plugins_2.32.3-3_amd64.deb to main/e/evolution/evolution-plugins_2.32.3-3_amd64.deb evolution_2.32.3-3.debian.tar.gz to main/e/evolution/evolution_2.32.3-3.debian.tar.gz evolution_2.32.3-3.dsc to main/e/evolution/evolution_2.32.3-3.dsc evolution_2.32.3-3_amd64.deb to main/e/evolution/evolution_2.32.3-3_amd64.deb libevolution_2.32.3-3_amd64.deb to main/e/evolution/libevolution_2.32.3-3_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. Yves-Alexis Perez cor...@debian.org (supplier of updated evolution 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: SHA512 Format: 1.8 Date: Mon, 01 Aug 2011 23:21:31 +0200 Source: evolution Binary: evolution libevolution evolution-common evolution-dev evolution-dbg evolution-plugins evolution-plugins-experimental Architecture: source all amd64 Version: 2.32.3-3 Distribution: unstable Urgency: low Maintainer: Debian Evolution Maintainers pkg-evolution-maintain...@lists.alioth.debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: evolution - groupware suite with mail client and organizer evolution-common - architecture independent files for Evolution evolution-dbg - debugging symbols for Evolution evolution-dev - development library files for Evolution evolution-plugins - standard plugins for Evolution evolution-plugins-experimental - experimental plugins for Evolution libevolution - evolution libraries Closes: 630268 Changes: evolution (2.32.3-3) unstable; urgency=low . * debian/rules: - 03_port-notify-0.7 added, fix build with notify 0.7. closes: #630268 * debian/control: - update libnotify-dev build-dep. Checksums-Sha1: dd2935e3ccf0001579de4c69355cc18f23824fe6 3435 evolution_2.32.3-3.dsc 0747bd4a3d85d8bfd746d2b1097416e1b26dc709 46514 evolution_2.32.3-3.debian.tar.gz 5fc8949cfbba6c04c9b21686844e961e1139dd9d 28908156 evolution-common_2.32.3-3_all.deb 11642b581d748901902c59f955ec2932a2558aa8 1321944 evolution_2.32.3-3_amd64.deb cf65c66b4b017dbbc09c80ff6ac247480c1e3bd5 2711066 libevolution_2.32.3-3_amd64.deb 83c36a857afeb092c8ede12909c8e2fb9f75d9b4 662032 evolution-dev_2.32.3-3_amd64.deb
Bug#635937: marked as done (TYPO3 Security Bulletin TYPO3-CORE-SA-2011-001: Multiple vulnerabilities in TYPO3 Core)
Your message dated Mon, 01 Aug 2011 22:04:21 + with message-id e1qo0az-0001g2...@franck.debian.org and subject line Bug#635937: fixed in typo3-src 4.5.4+dfsg1-1 has caused the Debian Bug report #635937, regarding TYPO3 Security Bulletin TYPO3-CORE-SA-2011-001: Multiple vulnerabilities in TYPO3 Core 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.) -- 635937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: typo3-src Severity: critical Tags: security Version: 4.5.3+dfsg1-1, 4.3.9+dfsg1-1 Component Type: TYPO3 Core Affected Versions: 4.3.11 and below, 4.4.8 and below, 4.5.3 and below Vulnerability Types: Cross-Site Scripting (XSS), Information Disclosure, Authentication Delay Bypass, Unserialize() vulnerability, Missing Access Control Overall Severity: High Release Date: July 27, 2011 Vulnerable subcomponent #1: Frontend Vulnerability Type: Cross-Site Scripting Severity: High Suggested CVSS v2.0: AV:N/AC:M/Au:N/C:N/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Failing to properly sanitize URL parameters the JSwindow property of the typolink function is susceptible to Cross-Site Scripting. The problem does not exist if the third party extension realurl is used and it's configuration parameter doNotRawUrlEncodeParameterNames is set to FALSE (default). Vulnerable subcomponent #2: Backend Vulnerability Type: Information Disclosure Severity: Low Suggested CVSS v2.0: AV:N/AC:M/Au:N/C:P/I:N/A:N/E:U/RL:OF/RC:C Problem Description: For authentication attempts with wrong credentials, TYPO3 sends different HTTP-Headers depending if provided username or provided password is wrong. Vulnerability Type: Authentication Delay Bypass Severity: Low Suggested CVSS v2.0: AV:N/AC:M/Au:N/C:P/I:N/A:N/E:U/RL:OF/RC:C Problem Description: The TYPO3 Backend login has a delay for authentication attempts with wrong credentials. By using a crafted request, an attacker is able to bypass the madantory delay in such cases. Vulnerability Type: Cross-Site Scripting Severity: Medium Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:N/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Failing to properly sanitize an username the admin panel is susceptible to Cross-Site Scripting. Vulnerability Type: Cross-Site Scripting Severity: Medium Suggested CVSS v2.0: AV:N/AC:H/Au:S/C:P/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Failing to properly sanitize a content element's link attribute the browse_links wizard is susceptible to Cross-Site Scripting. Exploiting requires an attacker to prepare a content element and trick its victim to open the browse_links wizard for this record. Vulnerability Type: Cross-Site Scripting Severity: Medium Suggested CVSS v2.0: AV:N/AC:H/Au:S/C:P/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Failing to properly sanitize a page title the system extension recycler is susceptible to Cross-Site Scripting. Exploiting requires an attacker to prepare a page and deleted page and trick its victim to visit the recycler. Vulnerability Type: Cross-Site Scripting Severity: Medium Suggested CVSS v2.0: AV:N/AC:H/Au:S/C:P/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Failing to properly sanitize a page title the tcemain flash message is susceptible to Cross-Site Scripting. Exploiting requires an attacker to prepare a page and trick its victim to copy/move the prepared page. Vulnerability Type: Information Disclosure Severity: Medium Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:P/I:N/A:N/E:U/RL:OF/RC:C Problem Description: A TYPO3 Backend user (editor) is able to see workspace changes of records in any languages - even for those he hasn't got granted access to. Vulnerability Type: Information Disclosure Severity: High Suggested CVSS v2.0: AV:N/AC:L/Au:S/C:C/I:P/A:N/E:U/RL:OF/RC:C Problem Description: Using getText feature on headlines of content elements it is possible to retrieve arbitrary data from TYPO3 database. The vulnerability results from an insecure configuration in css_styled_content system extension. Important Note: Having an adjusted fontTag property in the provided TypoScript (e.g. lib.stdheader.10.1.fontTag) or depending on headlines passed through fontTag might result in unexpected rendering results. Headline rendering is now handled through dataWrap (e.g. lib.stdheader.10.1.dataWrap). Make sure to check your TypoScript before the update and check the wesite rendering after it! Vulnerability Type: Unserialize() vulnerability Severity: High Suggested CVSS v2.0: AV:N/AC:M/Au:S/C:P/I:C/A:N/E:U/RL:OF/RC:C Problem Description: Special user input of
Bug#636147: /etc/editorrc ?
On Mon, Aug 01, 2011 at 08:20:21PM +, Thorsten Glaser wrote:
Hi,
I just ran into a funny problem regarding update-alternatives
and editorrc: if joe is installed, it wants /etc/joe/editorrc
whereas jupp reads /etc/jupp/editorrc (I???ll use joe???s for now
and symlink to it but that will break when joe was installed,
jupp is selected and joe is then removed??? probably, that is ???
not RC severity but to be fixed before the release ??? I think,
/etc/joe will simply still exist and dpkg not rmdir.)
Can we agree to move the 'editorrc' alternative to /etc and
symlink to that from /etc/joe/editorrc and /etc/jupp/editorrc
both? Can we also prod the update-alternatives people to make
editorrc a slave to editor, since that???s really the only way?
(What didn???t work? You only wrote it didn???t work in joe-3.5???s
changelog entry.)
What's with all the UTF-8 quotes? You're making your mails really hard to
read and for no apparent reason...
The problem with 'editorrc' is that it's really a joe-specific config file,
so it doesn't make sense to move it out of /etc/joe.
We would want editorrc to depend on editor in some way, since that is indeed
logical, but IIRC you can't just invent new slaves to editor out of the blue
and expect other editor alternatives to play along - they wouldn't know how.
Maybe simply coding it differently inside joe will be the best solution - if
it notices that $self is 'editor', then don't just look for /etc/joe/${self}rc
but instead look itself up once again through /etc/alternatives/editor to
see what actual $variant was chosen, and then use that /etc/joe/${variant}rc.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636147: /etc/editorrc ?
Josip Rodin dixit:
What's with all the UTF-8 quotes? You're making your mails really hard to
read and for no apparent reason...
Oh okay. UTF-8 works here.
The problem with 'editorrc' is that it's really a joe-specific config file,
so it doesn't make sense to move it out of /etc/joe.
Well, there's jupp now. It really is some fork of joe, which
I originally intended to rebase against later joe versions,
but I _really_ don't like some of the changes, and new bugs,
that come with it, so I don't think it'll happen again. Just
cherry-picking now. (The new syntax highlighting code is on
the list, and maybe the menu system, but I don't know if I
want to use it for the options, and besides that, many options
like XON/XOFF mode segfault joe…) I've not really been happy
with either upstream (the 2.9 one, and now that Joe is back).
We would want editorrc to depend on editor in some way, since that is indeed
logical, but IIRC you can't just invent new slaves to editor out of the blue
and expect other editor alternatives to play along - they wouldn't know how.
Hm, these other editors could just have it dangling.
We could ask the dpkg people for it.
Maybe simply coding it differently inside joe will be the best solution - if
it notices that $self is 'editor', then don't just look for /etc/joe/${self}rc
but instead look itself up once again through /etc/alternatives/editor to
see what actual $variant was chosen, and then use that /etc/joe/${variant}rc.
Ugh that is some major Debian specific source patching.
It can be done, but I'm not really comfortable with this
way out if we have another. I could hack it if really needed,
but the alternatives system is Debian specific, and we can't
even simply use realpath either, because the joe variants are
symbolic links (by design).
My plan is: have a coordinated upload of src:joe and src:jupp
whose binary packages (all three) Break the previous versions
of the other editor and move the alternative to /etc and have
a symlink to it. I can prepare a patch for joe if you want.
Parallel to that, we ask the dpkg people if we can move to a
slave, and include that in the upload if possible (since I've
fixed it for now, that upload isn't time critical).
bye,
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636280: wxwidgets2.8: FTBFS (multiarch breakage)
Package: wxwidgets2.8 Version: 2.8.10.1-3.1 Severity: serious The following clearly broke by the multiarch changes in other libraries (note that e.g. the checking for Xinerama... no is a symptom of the same problem): -- snip -- checking for X11/Xlib.h... yes checking for X11/XKBlib.h... yes checking for Xinerama... no configure: WARNING: Xinerama not found; disabling wxDisplay checking for -lSM - X11 session management... no configure: WARNING: libSM not found; disabling session management detection checking for OpenGL headers... found in /usr/include checking for GL/gl.h... yes checking GL/glu.h usability... yes checking GL/glu.h presence... yes checking for GL/glu.h... yes checking for -lGL... no checking for -lMesaGL... no configure: error: OpenGL libraries not available make: *** [configure-gtk-shared-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- snip -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39.3 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636281: wxwidgets2.8: FTBFS (libjpeg62-dev build dependency)
Package: wxwidgets2.8 Version: 2.8.10.1-3.1 Severity: serious - wxwidgets2.8 build depends on both libjpeg62-dev and libtiff4-dev - libtiff4-dev depends on libjpeg-dev - libjpeg-dev is now provided by libjpeg8-dev - libjpeg8-dev conflicts with libjpeg62-dev The fix is obvious (changing the build-dependency to libjpeg-dev). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39.3 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 636258
Processing commands for cont...@bugs.debian.org: tags 636258 + pending fixed Bug #636258 [firmware-b43-installer] firmware-b43-installer: exits from postinst with error code 1 Added tag(s) fixed and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 636258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636258 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#636258: firmware-b43-installer: exits from postinst with error code 1
Hi Brian, Il giorno lun, 01/08/2011 alle 19.23 +, brian m. carlson ha scritto: And this causes a failure with error 1 (as you can see by failed:1). Perfect analysis! Adding || true to the end of the line makes it succeed, and I've attached a patch that does that. Thank you very much for your patch. I've marked this grave since the package fails to install for any b43 user other than those using 14e4:4320 rev 3. I agree. The package is unusable so it's right to mark it as 'grave' However, it's now fixed. Thank you. Cheers, Fabrizio. signature.asc Description: This is a digitally signed message part
Bug#630302: marked as done (sflphone: Please transition to libnotify 0.7)
Your message dated Mon, 01 Aug 2011 23:33:15 + with message-id e1qo1z1-tn...@franck.debian.org and subject line Bug#630302: fixed in sflphone 0.9.13-3 has caused the Debian Bug report #630302, regarding sflphone: Please transition to libnotify 0.7 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.) -- 630302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: sflphone Version: 0.9.13-2 Severity: important User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libnotify0.7-transition Hi, We are planning to transition[0] libnotify to version 0.7 which breaks its API. Unfortunately, after a rebuild it seems that your package FTBFS with the newer version. Packages of the 0.7 version can be currently found in experimental. API changes (shamelessly taken from[1]): notify_notification_new_with_status_icon is gone notify_notification_attach_to_status_icon is gone notify_notification_attach_to_widget is gone notify_notification_set_geometry_hints is gone notify_notification_new has lost its widget argument All rebuild logs can be found at: http://people.debian.org/~bigon/libnotify0.7_rebuildlog/ Cheers Laurent Bigonville [0] http://release.debian.org/transitions/html/libnotify.html [1] http://lists.fedoraproject.org/pipermail/devel/2010-November/144914.html ---End Message--- ---BeginMessage--- Source: sflphone Source-Version: 0.9.13-3 We believe that the bug you reported is fixed in the latest version of sflphone, which is due to be installed in the Debian FTP archive: sflphone-daemon_0.9.13-3_amd64.deb to main/s/sflphone/sflphone-daemon_0.9.13-3_amd64.deb sflphone-data_0.9.13-3_all.deb to main/s/sflphone/sflphone-data_0.9.13-3_all.deb sflphone-gnome_0.9.13-3_amd64.deb to main/s/sflphone/sflphone-gnome_0.9.13-3_amd64.deb sflphone_0.9.13-3.debian.tar.gz to main/s/sflphone/sflphone_0.9.13-3.debian.tar.gz sflphone_0.9.13-3.dsc to main/s/sflphone/sflphone_0.9.13-3.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 630...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Francois Marier franc...@debian.org (supplier of updated sflphone 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: Mon, 01 Aug 2011 16:50:46 -0400 Source: sflphone Binary: sflphone-daemon sflphone-data sflphone-gnome Architecture: source amd64 all Version: 0.9.13-3 Distribution: unstable Urgency: low Maintainer: Francois Marier franc...@debian.org Changed-By: Francois Marier franc...@debian.org Description: sflphone-daemon - SIP and IAX2 compatible VoIP phone - core daemon sflphone-data - SIP and IAX2 compatible VoIP phone - common data sflphone-gnome - SIP and IAX2 compatible VoIP phone - GNOME client Closes: 611369 628608 630302 635425 Changes: sflphone (0.9.13-3) unstable; urgency=low . * Change build dependency on libwebkit-dev with libwebkitgtk-dev (closes: #635425) * Add libnotify 0.7 upstream patch and bump build-dependency (closes: #630302) * Replace dependency on gnome-icon-theme with just librsvg2-common (closes: #611369, #628608) * Add empty build-arch and build-indep targets in debian/rules Checksums-Sha1: 6e9df3c86c8b02738740993fddde9065bc2a6715 2382 sflphone_0.9.13-3.dsc 88bfefb423fe923f6f333e25181259c7b847afdd 9808 sflphone_0.9.13-3.debian.tar.gz 312c65b981f95509e4404094cbaf99d507b5ae23 808902 sflphone-daemon_0.9.13-3_amd64.deb e029a8f438654e41bcca26bb37a4816a3292ec4e 351932 sflphone-data_0.9.13-3_all.deb a9a3d731ac1f41bb849b1bfdaea9da23c58902ff 822680 sflphone-gnome_0.9.13-3_amd64.deb Checksums-Sha256: e8807d2209e4f9677d7f7dab496bd75e90b6d5632556ecaa67d819320421f0a3 2382 sflphone_0.9.13-3.dsc 4bc6457ab6713cb1265adb142668eba3242ab916c917fb0dcb8d9536610553b5 9808 sflphone_0.9.13-3.debian.tar.gz d1e81995798953c4358d8dce7ae682aac87b4c0e25c4d2cf8e28ba966170e529 808902 sflphone-daemon_0.9.13-3_amd64.deb 146ea4ee0b1222cd76bda62e970dc25adf3d9b03b28b8848531b77e06f6d8b0d 351932 sflphone-data_0.9.13-3_all.deb f183e9f64b5615413399baf9d08df44e75219a7d24fb5d0d0693704bdd3b1f9f 822680 sflphone-gnome_0.9.13-3_amd64.deb Files: 49b207e8212994abb363f4bae055d476
Processed: tagging 636263
Processing commands for cont...@bugs.debian.org: tags 636263 + moreinfo Bug #636263 [linux-2.6] linux-image-2.6.39-2-amd64: kernel panic when unmounting USB drives Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 636263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636263 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#636263: linux-image-2.6.39-2-amd64: kernel panic when unmounting USB drives
On Mon, 2011-08-01 at 16:32 -0400, Chris Capon wrote: Package: linux-2.6 Version: 2.6.39-3 Severity: critical Justification: breaks the whole system From Nautilus, right click on a mounted USB Drive icon and select Safely Remove Drive. Frequently, this causes a kernel panic which crashes the machine. This happens for both memory keys and external hard drive chassis. (see attached photograph) Please test linux-image-3.0.0-1-amd64 version 3.0.0-1. Ben. signature.asc Description: This is a digitally signed message part
Bug#634546: gnat-4.6: FTBFS: make[4]: *** No rule to make target `../gcc/ada/rts-shared-zcx/libgnat-.so', needed by `gnattools-native'. Stop.
tags 634546 unreproducible moreinfo thanks I have rebuilt gnat-4.6 successfully on amd64 on multiple occasions since you filed this bug, including the upload of 4.6.1-2. Please close the bug or provide more details. -- Ludovic Brenta. -- 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#634546: gnat-4.6: FTBFS: make[4]: *** No rule to make target `../gcc/ada/rts-shared-zcx/libgnat-.so', needed by `gnattools-native'. Stop.
Processing commands for cont...@bugs.debian.org: tags 634546 unreproducible moreinfo Bug #634546 [src:gnat-4.6] gnat-4.6: FTBFS: make[4]: *** No rule to make target `../gcc/ada/rts-shared-zcx/libgnat-.so', needed by `gnattools-native'. Stop. Added tag(s) unreproducible and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 634546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634546 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: This is now a FTBFS
Processing commands for cont...@bugs.debian.org: severity 634277 serious Bug #634277 [src:mplayer] mplayer: Please Build-Depends on libjpeg-dev, not libjpeg62-dev Severity set to 'serious' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 634277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634277 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#636270: FTBFS: test failure: Failed test 'direct split (yahoo) (rows)'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/01/2011 04:00 PM, Dominic Hargreaves wrote: Source: libfinance-quotehist-perl Version: 1.16-1 Severity: serious Justification: fails to build from source (but built successfully in the past) This package FTBFS with a clean sid chroot: Thanks for the report. I'm going to disable all of the remote tests in this package. That should bring it more in line with the policies the debian-perl team is following. http://pkg-perl.alioth.debian.org/policy.html#test_suites -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk43PGIACgkQBYeybkXz+/ns0wCfU0Ye+YlNAW8DSRjlSna0jMtr OZkAnito+nvhNXs2noKaQv3h0MkX2+WB =hASW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625567: gstreamer0.10-plugins-good must depend on -gconf for wheezy
retitle 625567 gstreamer0.10-plugins-good must depend on gstreamer0.10-gconf for wheezy thanks Common practice in Debian: When you split a package out of your package, you should depend on it for the next stable release. This ensures that everyone doing a dist-upgrade from the current stable to the next stable will have the splitted-out package installed if he had the original package installed. That avoids many possible problems, including helping non-packaged software to continue working after the upgrade. Debian has a reputation for working upgrades, and avoiding problems is more important than a few unnecessary packages installed. For gstreamer0.10-plugins-good that will only be temporary for wheezy, and after the release of wheezy gstreamer0.10-plugins-good can then drop the dependency on gstreamer0.10-gconf. cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: gstreamer0.10-plugins-good must depend on -gconf for wheezy
Processing commands for cont...@bugs.debian.org: retitle 625567 gstreamer0.10-plugins-good must depend on gstreamer0.10-gconf for wheezy Bug #625567 [gstreamer0.10-plugins-good] Need a transition plan for gstreamer0.10-gconf Changed Bug title to 'gstreamer0.10-plugins-good must depend on gstreamer0.10-gconf for wheezy' from 'Need a transition plan for gstreamer0.10-gconf' thanks Stopping processing here. Please contact me if you need assistance. -- 625567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625567 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#636291: gnat-4.6: FTBFS on kfreebsd-* with s-taprop.adb:717:32: lwp_self is undefined
Package: src:gnat-4.6 Version: 4.6.1-1 Severity: serious Tags: upstream /build/buildd-gnat-4.6_4.6.1-2-kfreebsd-amd64-Jts3n3/gnat-4.6-4.6.1/build/./gcc/xgcc -B/build/buildd-gnat-4.6_4.6.1-2-kfreebsd-amd64-Jts3n3/gnat-4.6-4.6.1/build/./gcc/ -c -g -O2 -W -Wall -gnatpg s-taprop.adb -o s-taprop.o s-taprop.adb:717:32: lwp_self is undefined s-taprop.adb:856:10: pthread_attr_setaffinity_np is undefined (more references follow) I have traced this to the following commit: commit a0d9619fa08b438aaeda58cb70100b803942e9fe Author: charlet charlet@138bc75d-0d04-0410-961f-82ee72b054a4 Date: Wed Apr 15 10:06:20 2009 + 2009-04-15 Nicolas Roche ro...@adacore.com * adaint.c: Add function __gnat_lwp_self that retrieves the LWP of the current thread. * s-osinte-linux.ads: Import the __gnat_lwp_self function as lwp_self * s-taprop-linux.adb (Enter_Task): Store the LWP in the TCB git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@146097 138bc75d-0d04-0410-961f-82ee72b054a4 The function __gnat_lwp_self exists in adaint.c only #if defined(linux), so it may not apply to kfreebsd-*. The problem exists because kfreebsd-* uses s-osinte-kfreebsd-gnu.ads, which does not import the function, but also uses s-taprop-linux.adb, which does use the function. I am not sure what to do: either introduce a new file s-taprop-kfreebsd-gnu.adb or provide the function __gnat_lwp_self also on kfreebsd-* and import it in s-osinte-kfreebsd-gnu.ads. -- Ludovic Brenta. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Forwarded Bug#636291: gnat-4.6: FTBFS on kfreebsd-* with s-taprop.adb:717:32: lwp_self is undefined
Processing commands for cont...@bugs.debian.org: forwarded 636291 http://gcc.gnu.org/PR49940 Bug #636291 [src:gnat-4.6] gnat-4.6: FTBFS on kfreebsd-* with s-taprop.adb:717:32: lwp_self is undefined Set Bug forwarded-to-address to 'http://gcc.gnu.org/PR49940'. thanks Stopping processing here. Please contact me if you need assistance. -- 636291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636291 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#636001: Clementine FTBS: how to proceed?
Hi everyone! The patch proposed by Nobuhiro has been merged upstream. The patch is actually trivial, but Thomas is on VAC until the weekend. So, we have some choices here: 1- Wait until Thomas comes back and reviews the patch. Would be my option if the patch weren't that trivial and already accepted upstream. 2- Let Nobuhiro make a NMU. 3- Either Jérémy (who is sponsoring Thomas) or I can apply the patch to the package and then Jérémy sponsor it. While I would normally don't heasitate to wait, in this case I want the package to reach testing, as there are multiple users asking for it mostly on #clementine (freenode). Kinds regards, Lisandro. -- 1: Una computadora sirve: * Para tratar de dominar el mundo, un caso conocido de esto fue el de Skinet Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: tag 636001 fixed-upstream Bug #636001 [clementine] clementine: FTBFS in qFuzzyCompare on armel, armhf and sh4 Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 636001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636001 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#636296: Please transition to libnotify 0.7
Source: boinc Version: 6.12.33+dfsg-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libnotify0.7-transition Hi, your package is part of the ongoing libnotify 0.7 transition [1]. It currently fails to build from source [2] and thus blocks the transtion.. Please update the package to correctly build against libnotify 0.7. API changes (shamelessly taken from[3]): notify_notification_new_with_status_icon is gone notify_notification_attach_to_status_icon is gone notify_notification_attach_to_widget is gone notify_notification_set_geometry_hints is gone notify_notification_new has lost its widget argument [1] http://release.debian.org/transitions/html/ongoing-libnotify.html [2] http://people.debian.org/~biebl/libnotify07-build-logs/boinc.build [3] http://lists.fedoraproject.org/pipermail/devel/2010-November/144914.html -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636297: Please transition to libnotify 0.7
Source: kerneloops Version: 0.12+git20090217-1 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: libnotify0.7-transition Hi, your package is part of the ongoing libnotify 0.7 transition [1]. It currently fails to build from source [2] and thus blocks the transtion. Please update the package to correctly build against libnotify 0.7. API changes (shamelessly taken from[3]): notify_notification_new_with_status_icon is gone notify_notification_attach_to_status_icon is gone notify_notification_attach_to_widget is gone notify_notification_set_geometry_hints is gone notify_notification_new has lost its widget argument [1] http://release.debian.org/transitions/html/ongoing-libnotify.html [2] http://people.debian.org/~biebl/libnotify07-build-logs/kerneloops.build [3] http://lists.fedoraproject.org/pipermail/devel/2010-November/144914.html -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 633973 is serious, user pkg-gnome-maintain...@lists.alioth.debian.org, usertagging 633973
Processing commands for cont...@bugs.debian.org: severity 633973 serious Bug #633973 [libgtk2-notify-perl] libgtk2-notify-perl: Needs porting for libnotify 0.7 API Severity set to 'serious' from 'normal' user pkg-gnome-maintain...@lists.alioth.debian.org Setting user to pkg-gnome-maintain...@lists.alioth.debian.org (was bi...@debian.org). usertags 633973 + libnotify0.7-transition Bug#633973: libgtk2-notify-perl: Needs porting for libnotify 0.7 API There were no usertags set. Usertags are now: libnotify0.7-transition. thanks Stopping processing here. Please contact me if you need assistance. -- 633973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633973 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
