Bug#657244: batik bundles a non free colour profile in pdf-transcoder.jar
clone 657244 -1 reassign -1 fop found -1 fop/1:1.0.dfsg2-6 retitle -1 src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free thanks On Tue, Jan 24, 2012 at 11:54 PM, Karl Goetz k...@kgoetz.id.au wrote: From [1], it seems the pdf-transcoder.jar in batik contains a colour profile with a crazy licence. ...permission to use, copy and distribute this file for any purpose is hereby granted without fee, provided that the file is not changed including the HP copyright notice tag, ... The file will need to be removed from the jar, or the jar (and pdf support) removed from batik :/ Actually, it's more annoying than this. As far as I can tell, batik doesn't use this binary jar (and it should have been stripped from the debian source ages ago). Unfortunately, the jar comes from fop, and the incriminated file is present in fop source, which makes it unsuitable for main... Thanks for your report, Vincent -- 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#657244: batik bundles a non free colour profile in pdf-transcoder.jar
Processing commands for cont...@bugs.debian.org: clone 657244 -1 Bug#657244: batik bundles a non free colour profile in pdf-transcoder.jar Bug 657244 cloned as bug 657281. reassign -1 fop Bug #657281 [batik] batik bundles a non free colour profile in pdf-transcoder.jar Bug reassigned from package 'batik' to 'fop'. found -1 fop/1:1.0.dfsg2-6 Bug #657281 [fop] batik bundles a non free colour profile in pdf-transcoder.jar Bug Marked as found in versions fop/1:1.0.dfsg2-6. retitle -1 src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free Bug #657281 [fop] batik bundles a non free colour profile in pdf-transcoder.jar Changed Bug title to 'src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free' from 'batik bundles a non free colour profile in pdf-transcoder.jar' thanks Stopping processing here. Please contact me if you need assistance. -- 657281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657281 657244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657244 -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 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#646474: What to do if FTBFS bug is not reproducible?
Hi! Am 25.01.2012 08:58, schrieb Vasudev Kamath: I'm working on to prepare QA upload for surf which is orphaned by its previous maintainer. There is a FTBFS bug reported against this package [1]. But I'm not able to reproduce this bug. Package builds fine on the pbuilder clean chroot. I've already reported this on the bug and also have provided my build log. How can I proceed shall I manually close this bug and prepare a normal QA upload or I need to wait for some reply on the bug. I just tried it, and verified, that the package indeed builds in pbuilder. You could try to compare your build log, and one from the build that failed (haven't taken a look at them). If you can't find any significant differences, which could explain the FTBFS, I would downgrade the bug to important (so it's no longer considered release critical) and tag it unreproducible, till the submitter confirms the problem has been solved somehow (and the bug can be closed). If you are going to do an QA upload keep an eye on the build logs: You'll see if the package can be build by the autobuilders. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 657165
Processing commands for cont...@bugs.debian.org: tags 657165 + pending Bug #657165 [src:gearmand] gearmand: FTBFS on 32-bit architectures: symbols file mismatch Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 657165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657165 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 important
Processing commands for cont...@bugs.debian.org: package resolvconf Limiting to bugs with field 'package' containing at least one of 'resolvconf' Limit currently set to 'package':'resolvconf' severity 657259 important Bug #657259 [resolvconf] resolvconf wipes out /run Severity set to 'important' from 'critical' stop Stopping processing here. Please contact me if you need assistance. -- 657259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657259 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#657165: marked as done (gearmand: FTBFS on 32-bit architectures: symbols file mismatch)
Your message dated Wed, 25 Jan 2012 09:47:19 + with message-id e1rpzrn-0005qe...@franck.debian.org and subject line Bug#657165: fixed in gearmand 0.27-2 has caused the Debian Bug report #657165, regarding gearmand: FTBFS on 32-bit architectures: symbols file mismatch 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.) -- 657165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gearmand Version: 0.27-1 Severity: serious Justification: fails to build from source (but built successfully in the past) 32-bit gearmand builds that don't encounter the test suite error I just reported as #657163 still fail because some symbol names vary with word size; you can find a list of discrepancies at https://buildd.debian.org/status/fetch.php?pkg=gearmandarch=i386ver=0.27-1stamp=1327353886 Could you please account for such variation? Thanks! ---End Message--- ---BeginMessage--- Source: gearmand Source-Version: 0.27-2 We believe that the bug you reported is fixed in the latest version of gearmand, which is due to be installed in the Debian FTP archive: gearman-job-server_0.27-2_amd64.deb to main/g/gearmand/gearman-job-server_0.27-2_amd64.deb gearman-tools_0.27-2_amd64.deb to main/g/gearmand/gearman-tools_0.27-2_amd64.deb gearman_0.27-2_all.deb to main/g/gearmand/gearman_0.27-2_all.deb gearmand_0.27-2.debian.tar.gz to main/g/gearmand/gearmand_0.27-2.debian.tar.gz gearmand_0.27-2.dsc to main/g/gearmand/gearmand_0.27-2.dsc libgearman-dbg_0.27-2_amd64.deb to main/g/gearmand/libgearman-dbg_0.27-2_amd64.deb libgearman-dev_0.27-2_amd64.deb to main/g/gearmand/libgearman-dev_0.27-2_amd64.deb libgearman-doc_0.27-2_all.deb to main/g/gearmand/libgearman-doc_0.27-2_all.deb libgearman6_0.27-2_amd64.deb to main/g/gearmand/libgearman6_0.27-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 657...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stig Sandbeck Mathisen s...@debian.org (supplier of updated gearmand 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: Wed, 25 Jan 2012 10:25:18 +0100 Source: gearmand Binary: libgearman6 libgearman-dev libgearman-dbg libgearman-doc gearman-job-server gearman-tools gearman Architecture: source amd64 all Version: 0.27-2 Distribution: unstable Urgency: low Maintainer: Stig Sandbeck Mathisen s...@debian.org Changed-By: Stig Sandbeck Mathisen s...@debian.org Description: gearman- Distributed job queue gearman-job-server - Job server for the Gearman distributed job queue gearman-tools - Tools for the Gearman distributed job queue libgearman-dbg - Debug symbols for the Gearman Client Library libgearman-dev - Development files for the Gearman Library libgearman-doc - API Documentation for the Gearman Library libgearman6 - Library providing Gearman client and worker functions Closes: 657165 657189 Changes: gearmand (0.27-2) unstable; urgency=low . [ Stig Sandbeck Mathisen ] * Add missing include/libgearman-1.0 (Closes: #657189) . [ Michael Fladischer ] * Tag varying symbols by architecture (Closes: #657165) Checksums-Sha1: 0e378cca8d0e04626adeec592db9a26f219df6da 1840 gearmand_0.27-2.dsc 07543ad0b562be1c836eb04eacd3e5f1db60980a 14755 gearmand_0.27-2.debian.tar.gz 189f1057b49087073c4c724976237b3c5cbd039b 59710 libgearman6_0.27-2_amd64.deb f6ef04787e0b99245b6a9c9d51cec79492a873fd 203228 libgearman-dev_0.27-2_amd64.deb dc183f3b802d4c91ec2be24cfb98ebed3e366a3b 889506 libgearman-dbg_0.27-2_amd64.deb 34618b867852fc880ba5ed05891b2fc33d6d5f3b 1798686 libgearman-doc_0.27-2_all.deb 2196f6e9dbea983c9d77508460e134ffea2258e7 112668 gearman-job-server_0.27-2_amd64.deb 8dffc02569ad92f5c74ce33163bcf9f3fa369de4 64986 gearman-tools_0.27-2_amd64.deb 7c0ff5aae29771114ff85e44eaf35d303708c48d 10542 gearman_0.27-2_all.deb Checksums-Sha256: 4da32f254195d9d528e1103fb1c86ef79f35787e0c51ea9c997b09df0cf9c233 1840 gearmand_0.27-2.dsc 97c917355746f7ec2322d45675d2c578f414dd8d1abd73e50861f81870fdd97e 14755 gearmand_0.27-2.debian.tar.gz 7a78970ca31645716e8b56bfd926f313aa391a68253556bc533efa4c349c1a63 59710 libgearman6_0.27-2_amd64.deb
Bug#656771: Should this package be removed?
reassign 656771 ftp.debian.org retitle 656771 RM: kazehakase -- RoM; RC-buggy, unmaintained upstream, low popcon, better alternatives available thanks At Sat, 21 Jan 2012 17:47:30 +0100, Moritz Muehlenhoff wrote: I propose to remove kazehakase from the archive: FWIW, I agree. I have a fixed package ready but I cannot recommend its usage to anyone wholeheartedly. Some of the features that made Kazehakase attractive (such as history search) are not working with the Webkit backend, basic functionality like password management is broken, etc. -- 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): reopen 599679 655789
Processing commands for cont...@bugs.debian.org:
reopen 599679 655789
Failed to reopen 599679: New submitter address 655789 is not a valid e-mail
address.
tags 599679 + fixed-in-experimental
Bug #599679 {Done: Dmitry Smirnov only...@member.fsf.org} [wv] Wv has newer
releases from abisource.com
Added tag(s) fixed-in-experimental.
tags 655789 + fixed-in-experimental
Bug #655789 {Done: Dmitry Smirnov only...@member.fsf.org} [src:wv] wv: FTBFS:
configure: error: * * * libwmf = 0.2.1 required * * *
Added tag(s) fixed-in-experimental.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
655789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655789
599679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599679
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: reopen 599679 655789
Processing commands for cont...@bugs.debian.org:
reopen 599679
Bug #599679 {Done: Dmitry Smirnov only...@member.fsf.org} [wv] Wv has newer
releases from abisource.com
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
reopen 655789
Bug #655789 {Done: Dmitry Smirnov only...@member.fsf.org} [src:wv] wv: FTBFS:
configure: error: * * * libwmf = 0.2.1 required * * *
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
--
Stopping processing here.
Please contact me if you need assistance.
--
655789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655789
599679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599679
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: tagging 657042
Processing commands for cont...@bugs.debian.org: tags 657042 + pending Bug #657042 [bind9] bind9: new installation fails because named.conf.options is not in /etc/bind Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 657042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657042 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#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)
tags 656755 +patch thanks While I really agree to this statement I think there is few chance that somebody else will step in. We are just needing to maintain this as a predependency for two important packages of the Debian Med team. Ok I took pity on you and took a look at the Makefile.am in that directory, turns out it wasn't that hard to disable building of the CPU with SSE plugin. You should really be able to do this kind of build-system modification yourself though, it's not like the package is using an exotic build system it's bog standard autotools. I have tested that the resulting package builds on i386, I have not tested whether it actually works. The attatched patch makes the aforementioned change and also makes debian/rules clean actually work. diff -urN libhmsbeagle-1.0/debian/patches/disable_cpu_sse_plugin.patch libhmsbeagle-1.0.new/debian/patches/disable_cpu_sse_plugin.patch --- libhmsbeagle-1.0/debian/patches/disable_cpu_sse_plugin.patch 1970-01-01 01:00:00.0 +0100 +++ libhmsbeagle-1.0.new/debian/patches/disable_cpu_sse_plugin.patch 2012-01-25 11:00:07.0 + @@ -0,0 +1,59 @@ +Description: Disable CPU_SSE plugin when building without SSE + The CPU_SSE plugin does not build without -msse +Author: Peter Green plugw...@p10link.net +Bug-Debian: http://bugs.debian.org/656755 + +--- +The information above should follow the Patch Tagging Guidelines, please +checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here +are templates for supplementary fields that you might want to add: + +Origin: vendor|upstream|other, url of original patch +Bug: url in upstream bugtracker +Bug-Debian: http://bugs.debian.org/bugnumber +Bug-Ubuntu: https://launchpad.net/bugs/bugnumber +Forwarded: no|not-needed|url proving that it has been forwarded +Reviewed-By: name and email of someone who approved the patch +Last-Update: -MM-DD + +Index: libhmsbeagle-1.0.new/libhmsbeagle/CPU/Makefile.am +=== +--- libhmsbeagle-1.0.new.orig/libhmsbeagle/CPU/Makefile.am 2012-01-25 10:09:40.0 + libhmsbeagle-1.0.new/libhmsbeagle/CPU/Makefile.am 2012-01-25 10:09:40.0 + +@@ -1,4 +1,4 @@ +-lib_LTLIBRARIES=libhmsbeagle-cpu.la libhmsbeagle-cpu-sse.la ++lib_LTLIBRARIES=libhmsbeagle-cpu.la + + BEAGLE_CPU_COMMON = Precision.h EigenDecomposition.h \ + EigenDecompositionCube.hpp EigenDecompositionCube.h \ +@@ -19,6 +19,8 @@ + # + # CPU plugin with custom SSE code + # ++if HAVE_SSE ++lib_LTLIBRARIES += libhmsbeagle-cpu-sse.la + libhmsbeagle_cpu_sse_la_SOURCES = $(BEAGLE_CPU_COMMON) \ + SSEDefinitions.h BeagleCPU4StateSSEImpl.hpp BeagleCPU4StateSSEImpl.h \ + BeagleCPUSSEImpl.hpp BeagleCPUSSEImpl.h \ +@@ -26,6 +28,7 @@ + + libhmsbeagle_cpu_sse_la_CXXFLAGS = $(AM_CXXFLAGS) + libhmsbeagle_cpu_sse_la_LDFLAGS= -version-info $(GENERIC_LIBRARY_VERSION) ++endif + + # + # CPU plugin with OpenMP parallel threads +Index: libhmsbeagle-1.0.new/configure.ac +=== +--- libhmsbeagle-1.0.new.orig/configure.ac 2012-01-25 10:41:40.0 + libhmsbeagle-1.0.new/configure.ac 2012-01-25 10:41:59.0 + +@@ -222,6 +222,9 @@ + if test $enable_sse = yes; then + SSE_CFLAGS+=-DENABLE_SSE + AM_CXXFLAGS=$AM_CXXFLAGS -msse2 ++AM_CONDITIONAL(HAVE_SSE,true) ++else ++AM_CONDITIONAL(HAVE_SSE,false) + fi + + # -- diff -urN libhmsbeagle-1.0/debian/patches/series libhmsbeagle-1.0.new/debian/patches/series --- libhmsbeagle-1.0/debian/patches/series 2012-01-21 16:36:24.0 + +++ libhmsbeagle-1.0.new/debian/patches/series 2012-01-25 10:41:51.0 + @@ -1 +1,2 @@ enable_static.patch +disable_cpu_sse_plugin.patch diff -urN libhmsbeagle-1.0/debian/rules libhmsbeagle-1.0.new/debian/rules --- libhmsbeagle-1.0/debian/rules 2012-01-21 12:54:33.0 + +++ libhmsbeagle-1.0.new/debian/rules 2012-01-25 10:53:59.0 + @@ -42,6 +42,61 @@ $(MAKE) -f Makefile distclean || true rm -rf doc .config configure rm -rf lib build + rm -f acinclude.m4 + rm -f INSTALL + rm -f libhmsbeagle/config.h.in + rm -f examples/*/Makefile.in + rm -f examples/Makefile.in + rm -f examples/*/*.o + rm -rf examples/*/.libs + rm -rf libhmsbeagle/*/.libs + rm -rf libhmsbeagle/.libs + rm -rf libhmsbeagle/*.o + rm -rf libhmsbeagle/*/*.o + rm -f Makefile + rm -f config.log + rm -f config.status + rm -f examples/Makefile + rm -f examples/complextest/Makefile + rm -f examples/complextest/complextest + rm -f examples/fourtaxon/Makefile + rm -f examples/fourtaxon/check_lnL_using_paup.nex + rm -f examples/fourtaxon/fourtaxon + rm -f examples/fourtaxon/fourtaxonrun.sh + rm -f examples/genomictest/Makefile + rm -f examples/genomictest/genomictest + rm -f examples/genomictest/genomictest.sh + rm -f
Bug#652482: marked as done (FTBFS on kfreebsd-*: No package 'libnm-glib' found)
Your message dated Wed, 25 Jan 2012 11:17:31 + with message-id e1rq0r5-0006ha...@franck.debian.org and subject line Bug#652482: fixed in gnome-shell 3.2.2.1-1 has caused the Debian Bug report #652482, regarding FTBFS on kfreebsd-*: No package 'libnm-glib' 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.) -- 652482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gnome-shell Version: 3.2.1-8 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Apparently, in gnome-shell 3.2, NetworkManager support is no longer optional: telepathy-glib = 0.15.5 telepathy-logger-0.2 = 0.2.4 polkit-agent-1 = 0.100 xfixes libnm-glib libnm-util gnome-keyring-1) were not met: No package 'libnm-glib' found No package 'libnm-util' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GNOME_SHELL_CFLAGS and GNOME_SHELL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [debian/stamp-autotools] Error 1 Full build log https://buildd.debian.org/status/fetch.php?pkg=gnome-shellarch=kfreebsd-amd64ver=3.2.1-8stamp=1324118587 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information ---End Message--- ---BeginMessage--- Source: gnome-shell Source-Version: 3.2.2.1-1 We believe that the bug you reported is fixed in the latest version of gnome-shell, which is due to be installed in the Debian FTP archive: gnome-shell-common_3.2.2.1-1_all.deb to main/g/gnome-shell/gnome-shell-common_3.2.2.1-1_all.deb gnome-shell_3.2.2.1-1.debian.tar.gz to main/g/gnome-shell/gnome-shell_3.2.2.1-1.debian.tar.gz gnome-shell_3.2.2.1-1.dsc to main/g/gnome-shell/gnome-shell_3.2.2.1-1.dsc gnome-shell_3.2.2.1-1_amd64.deb to main/g/gnome-shell/gnome-shell_3.2.2.1-1_amd64.deb gnome-shell_3.2.2.1.orig.tar.xz to main/g/gnome-shell/gnome-shell_3.2.2.1.orig.tar.xz 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 652...@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-shell 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, 25 Jan 2012 11:06:41 +0100 Source: gnome-shell Binary: gnome-shell gnome-shell-common Architecture: source all amd64 Version: 3.2.2.1-1 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Michael Biebl bi...@debian.org Description: gnome-shell - graphical shell for the GNOME desktop gnome-shell-common - common files for the GNOME graphical shell Closes: 580869 649583 652482 Changes: gnome-shell (3.2.2.1-1) unstable; urgency=low . [ Michael Biebl ] * debian/patches/10-make-NetworkManager-optional.patch: make NM optional, to fix build on kFreeBSD architectures. Closes: #652482 * debian/patches/11-no-gettext.patch: remove gettext macros, otherwise autoreconf fails due to incompatibilities with intltool. . [ Jordi Mallach ] * Enable dh_autoreconf. * Update Vcs-* URLs. . [ Josselin Mouette ] * Update repository URL. . [ Michael Biebl ] * New upstream release: - Fix a crash in gnome-shell-extension-tool. Closes: #649583 - Remove 05-NetworkMenu-don-t-query-DBus-properties-of-removed-o.patch. - Remove 06-NetworkMenu-fix-regression-in-access-point-removed.patch. - Refresh 07-NetworkMenu-fix-logic-for-updating-wifi-icon.patch. * debian/control.in: Bump dependency on python to (= 2.6) since we require JSON support. Closes: #580869 Checksums-Sha1: 9770c18583db41445d8b8ff86bff0b1ca31caa15 3126 gnome-shell_3.2.2.1-1.dsc
Bug#657299: arpwatch: Dependency hell with local libpcap
Package: arpwatch Version: 2.1a15-1.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I can't build arpwatch before I guessed to remove any of libnl-dev and libnl2-dev packages from the system. Also I have noticed this build need to use local libpcap build but not from system. There are last messages from build log gcc -O -DDEBUG -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_MEMORY_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_BCOPY=1 -DHAVE_STRERROR=1 -DRETSIGTYPE=void -DRETSIGVAL= -DHAVE_SIGSET=1 -Dsignal=sigset -DDECLWAITSTATUS=int -DHAVE_LIBRESOLV=1 -DARPDIR=\/var/lib/arpwatch\ -DPATH_SENDMAIL=\/usr/sbin/sendmail\ -DETHERCODES=\/usr/share/arpwatch/ethercodes.dat\ -I. -I../libpcap-1.2.1 -Ilinux-include -o arpwatch arpwatch.o db.o dns.o ec.o file.o intoa.o machdep.o util.o report.o localhost.o setsignal.o version.o ../libpcap-1.2.1/libpcap.a -lresolv .../libpcap-1.2.1/libpcap.a(pcap-linux.o): In function `nl80211_init': /usr/src/libpcap-1.2.1/./pcap-linux.c:600: undefined reference to `nl_socket_alloc' /usr/src/libpcap-1.2.1/./pcap-linux.c:607: undefined reference to `genl_connect' /usr/src/libpcap-1.2.1/./pcap-linux.c:613: undefined reference to `genl_ctrl_alloc_cache' /usr/src/libpcap-1.2.1/./pcap-linux.c:621: undefined reference to `genl_ctrl_search_by_name' /usr/src/libpcap-1.2.1/./pcap-linux.c:633: undefined reference to `nl_socket_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:615: undefined reference to `nl_geterror' /usr/src/libpcap-1.2.1/./pcap-linux.c:631: undefined reference to `nl_cache_free' .../libpcap-1.2.1/libpcap.a(pcap-linux.o): In function `nl80211_cleanup': /usr/src/libpcap-1.2.1/./pcap-linux.c:640: undefined reference to `genl_family_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:641: undefined reference to `nl_cache_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:642: undefined reference to `nl_socket_free' .../libpcap-1.2.1/libpcap.a(pcap-linux.o): In function `del_mon_if': /usr/src/libpcap-1.2.1/./pcap-linux.c:753: undefined reference to `nlmsg_alloc' /usr/src/libpcap-1.2.1/./pcap-linux.c:760: undefined reference to `genl_family_get_id' /usr/src/libpcap-1.2.1/./pcap-linux.c:760: undefined reference to `genlmsg_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:762: undefined reference to `nla_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:764: undefined reference to `nl_send_auto_complete' /usr/src/libpcap-1.2.1/./pcap-linux.c:772: undefined reference to `nl_wait_for_ack' /usr/src/libpcap-1.2.1/./pcap-linux.c:784: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:791: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:766: undefined reference to `nl_geterror' /usr/src/libpcap-1.2.1/./pcap-linux.c:777: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:774: undefined reference to `nl_geterror' .../libpcap-1.2.1/libpcap.a(pcap-linux.o): In function `add_mon_if': /usr/src/libpcap-1.2.1/./pcap-linux.c:657: undefined reference to `nlmsg_alloc' /usr/src/libpcap-1.2.1/./pcap-linux.c:664: undefined reference to `genl_family_get_id' /usr/src/libpcap-1.2.1/./pcap-linux.c:664: undefined reference to `genlmsg_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:666: undefined reference to `nla_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:667: undefined reference to `nla_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:668: undefined reference to `nla_put' /usr/src/libpcap-1.2.1/./pcap-linux.c:670: undefined reference to `nl_send_auto_complete' /usr/src/libpcap-1.2.1/./pcap-linux.c:698: undefined reference to `nl_wait_for_ack' /usr/src/libpcap-1.2.1/./pcap-linux.c:712: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:691: undefined reference to `nl_geterror' /usr/src/libpcap-1.2.1/./pcap-linux.c:722: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:730: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:737: undefined reference to `nlmsg_free' /usr/src/libpcap-1.2.1/./pcap-linux.c:719: undefined reference to `nl_geterror' collect2: ld returned 1 exit status make[1]: *** [arpwatch] Error 1 make[1]: Leaving directory `/srv/src/arpwatch-2.1a15' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (300, 'oldstable'), (50, 'unstable'), (10, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to
Bug#653310: Fix
This bug is in versions 1.13 and 1.14. In the file /usr/share/pyshared/LiveMagic/views/wizard.py change row 199 # Boot parameters data['bootappend_live'] = locale=%s keyb=%s % (locale, keyb) to # Boot parameters data['bootappend_live'] = locales=%s keyboard-layouts=%s % (locale,keyb) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657276: xfonts-traditional: can't cope with xfonts-unifont
Aaron M. Ucko writes (Bug#657276: xfonts-traditional: can't cope with xfonts-unifont): xfonts-traditional blows up when trying to process unifont.pcf.gz from xfonts-unifont: Thanks, I will look into this. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fix for #610256 was dropped
Processing commands for cont...@bugs.debian.org:
unarchive 610256
Bug #610256 {Done: Laurent Bigonville bi...@debian.org} [src:gjs] gjs: FTBFS:
./test/run-with-dbus: script gtester failed
Unarchived Bug 610256
found 610256 1.29.0-1
Bug #610256 {Done: Laurent Bigonville bi...@debian.org} [src:gjs] gjs: FTBFS:
./test/run-with-dbus: script gtester failed
Bug Marked as found in versions gjs/1.29.0-1 and reopened.
kthxbye
Stopping processing here.
Please contact me if you need assistance.
--
610256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610256
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#631034: marked as done (gluezilla: FTBFS against iceweasel 4.0 or 5.0)
Your message dated Wed, 25 Jan 2012 12:48:42 + with message-id e1rq2hk-00049o...@franck.debian.org and subject line Bug#657290: Removed package(s) from unstable has caused the Debian Bug report #631034, regarding gluezilla: FTBFS against iceweasel 4.0 or 5.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.) -- 631034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gluezilla Version: 2.6-2 Severity: serious Tags: sid wheezy User: pkg-mozilla-maintain...@lists.alioth.debian.org Usertags: xulrunner-2.0 Hi, your package fails to build against iceweasel 4.0 (currently in experimental). iceweasel 5.0 will soon be uploaded to unstable, so your package needs to be updated to cope with the new version, or will have to be removed. Build logs are available at http://people.debian.org/~glandium/iceweasel4-transition.logs.tbz2 Cheers, Julien ---End Message--- ---BeginMessage--- Version: 2.6-2+rm Dear submitter, as the package gluezilla has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/657290 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#657042: marked as done (bind9: new installation fails because named.conf.options is not in /etc/bind)
Your message dated Wed, 25 Jan 2012 12:47:39 + with message-id e1rq2gj-00045c...@franck.debian.org and subject line Bug#657042: fixed in bind9 1:9.8.1.dfsg.P1-2 has caused the Debian Bug report #657042, regarding bind9: new installation fails because named.conf.options is not in /etc/bind 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.) -- 657042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bind9 Version: 1:9.8.1.dfsg.P1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I initially encountered this bug on Ubuntu precise and filed the following bug report: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/920202 As I saw the package was directly synced from Debian unstable with no additional patches, I reproduced it successfully on an up-to-date. Debian sid installation. It seems the upgrades from previous versions of bind9 work, the problem just occurs when installing bind9 for the first time. The problem seems to be in this piece of code of the postinst script: case $UPDATE_OPTS in y) echo Updating named.conf.options to include DNSSEC enablement cp /usr/share/bind9/named.conf.options /etc/bind/named.conf.options $UPDATE_OPTS is equal to 'n' on a new installation so the file is not copied, but it is referenced in /etc/bind/named.conf: include /etc/bind/named.conf.local; And that's the reason why it fails to start. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bind9 depends on: ii adduser3.113 ii bind9utils 1:9.8.1.dfsg.P1-1 ii debconf [debconf-2.0] 1.5.41 ii libbind9-801:9.8.1.dfsg.P1-1 ii libc6 2.13-24 ii libcap21:2.22-1 ii libdns81 1:9.8.1.dfsg.P1-1 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libisc83 1:9.8.1.dfsg.P1-1 ii libisccc80 1:9.8.1.dfsg.P1-1 ii libisccfg821:9.8.1.dfsg.P1-1 ii liblwres80 1:9.8.1.dfsg.P1-1 ii libssl1.0.01.0.0g-1 ii libxml22.7.8.dfsg-6 ii lsb-base 3.2-28 ii net-tools 1.60-24.1 ii netbase4.47 bind9 recommends no packages. Versions of packages bind9 suggests: pn bind9-doc none pn dnsutilsnone pn resolvconf none pn ufw none -- debconf information: bind9/different-configuration-file: bind9/run-resolvconf: true bind9/start-as-user: bind ---End Message--- ---BeginMessage--- Source: bind9 Source-Version: 1:9.8.1.dfsg.P1-2 We believe that the bug you reported is fixed in the latest version of bind9, which is due to be installed in the Debian FTP archive: bind9-doc_9.8.1.dfsg.P1-2_all.deb to main/b/bind9/bind9-doc_9.8.1.dfsg.P1-2_all.deb bind9-host_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/bind9-host_9.8.1.dfsg.P1-2_amd64.deb bind9-host_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/bind9-host_9.8.1.dfsg.P1-2_i386.deb bind9_9.8.1.dfsg.P1-2.diff.gz to main/b/bind9/bind9_9.8.1.dfsg.P1-2.diff.gz bind9_9.8.1.dfsg.P1-2.dsc to main/b/bind9/bind9_9.8.1.dfsg.P1-2.dsc bind9_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/bind9_9.8.1.dfsg.P1-2_amd64.deb bind9_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/bind9_9.8.1.dfsg.P1-2_i386.deb bind9utils_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/bind9utils_9.8.1.dfsg.P1-2_amd64.deb bind9utils_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/bind9utils_9.8.1.dfsg.P1-2_i386.deb dnsutils_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/dnsutils_9.8.1.dfsg.P1-2_amd64.deb dnsutils_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/dnsutils_9.8.1.dfsg.P1-2_i386.deb host_9.8.1.dfsg.P1-2_all.deb to main/b/bind9/host_9.8.1.dfsg.P1-2_all.deb libbind-dev_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/libbind-dev_9.8.1.dfsg.P1-2_amd64.deb libbind-dev_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/libbind-dev_9.8.1.dfsg.P1-2_i386.deb libbind9-80_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/libbind9-80_9.8.1.dfsg.P1-2_amd64.deb libbind9-80_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/libbind9-80_9.8.1.dfsg.P1-2_i386.deb libdns81_9.8.1.dfsg.P1-2_amd64.deb to main/b/bind9/libdns81_9.8.1.dfsg.P1-2_amd64.deb libdns81_9.8.1.dfsg.P1-2_i386.deb to main/b/bind9/libdns81_9.8.1.dfsg.P1-2_i386.deb libisc83_9.8.1.dfsg.P1-2_amd64.deb to
Bug#656771: marked as done (RM: kazehakase -- RoM; RC-buggy, unmaintained upstream, low popcon, better alternatives available)
Your message dated Wed, 25 Jan 2012 12:52:10 + with message-id e1rq2kg-0004no...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #656771, regarding RM: kazehakase -- RoM; RC-buggy, unmaintained upstream, low popcon, better alternatives available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 656771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kazehakase Severity: serious I propose to remove kazehakase from the archive: - Unmaintained; last maintainer upload in June 2010, no followup to several RC bugs - RC buggy with multiple bugs - Dropped from testing since half a year - FTBFS even in stable - Low popcon Cheers, Moritz ---End Message--- ---BeginMessage--- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kazehakase |0.5.8-4 | source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc kazehakase-dbg |0.5.8-4 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc kazehakase-gecko |0.5.8-4 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc kazehakase-webkit |0.5.8-4 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- RoM; RC-buggy, unmaintained upstream, low popcon, better alternatives available -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close Bugs which have been reported against this package automatically. But please check all old bugs, if they where closed correctly or should have been re-assign to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 656...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/656771 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#614449: marked as done (kazehakase: FTBFS: nsNetUtil.h:1649: error: 'struct nsID' has no member named 'ToProvidedString')
Your message dated Wed, 25 Jan 2012 12:52:16 + with message-id e1rq2km-0004oy...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #614449, regarding kazehakase: FTBFS: nsNetUtil.h:1649: error: 'struct nsID' has no member named 'ToProvidedString' 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.) -- 614449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kazehakase Version: 0.5.8-4 Severity: serious Tags: squeeze sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110221 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[6]: Entering directory `/build/user-kazehakase_0.5.8-4-amd64-Ti3mq4/kazehakase-0.5.8/module/embed/gecko' ../../../doltcompile gcc -DHAVE_CONFIG_H -I. -I../../.. -DXPCOM_GLUE -I/usr/include/xulrunner-1.9.1/unstable -I/usr/include/xulrunner-1.9.1/unstable -I/usr/include/xulrunner-1.9.1/unstable/accessibility -I/usr/include/xulrunner-1.9.1/unstable/appcomps -I/usr/include/xulrunner-1.9.1/unstable/browser -I/usr/include/xulrunner-1.9.1/unstable/chardet -I/usr/include/xulrunner-1.9.1/unstable/commandhandler -I/usr/include/xulrunner-1.9.1/unstable/content -I/usr/include/xulrunner-1.9.1/unstable/cookie -I/usr/include/xulrunner-1.9.1/unstable/docshell -I/usr/include/xulrunner-1.9.1/unstable/dom -I/usr/include/xulrunner-1.9.1/unstable/embedcomponents -I/usr/include/xulrunner-1.9.1/unstable/embed_base -I/usr/include/xulrunner-1.9.1/unstable/exthandler -I/usr/include/xulrunner-1.9.1/unstable/find -I/usr/include/xulrunner-1.9.1/unstable/gfx -I/usr/include/xulrunner-1.9.1/unstable/helperAppDlg -I/usr/include/xulrunner-1.9.1/unstable/intl -I/usr/include/xulrunner-1.9.1/unstable/imglib2 -I/usr/include/xulrunner-1.9.1/unstable/java -I/usr/include/xulrunner-1.9.1/unstable/jsconsole -I/usr/include/xulrunner-1.9.1/unstable/layout -I/usr/include/xulrunner-1.9.1/unstable/locale -I/usr/include/xulrunner-1.9.1/unstable/loginmgr -I/usr/include/xulrunner-1.9.1/unstable/mimetype -I/usr/include/xulrunner-1.9.1/unstable/mozxfer -I/usr/include/xulrunner-1.9.1/unstable/necko -I/usr/include/xulrunner-1.9.1/unstable/necko2 -I/usr/include/xulrunner-1.9.1/unstable/nkcache -I/usr/include/xulrunner-1.9.1/unstable/oji -I/usr/include/xulrunner-1.9.1/unstable/pipnss -I/usr/include/xulrunner-1.9.1/unstable/pipboot -I/usr/include/xulrunner-1.9.1/unstable/pref -I/usr/include/xulrunner-1.9.1/unstable/profdirserviceprovider -I/usr/include/xulrunner-1.9.1/unstable/progressDlg -I/usr/include/xulrunner-1.9.1/unstable/passwordmgr -I/usr/include/xulrunner-1.9.1/unstable/sidebar -I/usr/include/xulrunner-1.9.1/unstable/shistory -I/usr/include/xulrunner-1.9.1/unstable/string -I/usr/include/xulrunner-1.9.1/unstable/thebes -I/usr/include/xulrunner-1.9.1/unstable/txtsvc -I/usr/include/xulrunner-1.9.1/unstable/uconv -I/usr/include/xulrunner-1.9.1/unstable/uriloader -I/usr/include/xulrunner-1.9.1/unstable/unicharutil -I/usr/include/xulrunner-1.9.1/unstable/wallet -I/usr/include/xulrunner-1.9.1/unstable/webbrowserpersist -I/usr/include/xulrunner-1.9.1/unstable/webbrwsr -I/usr/include/xulrunner-1.9.1/unstable/webshell -I/usr/include/xulrunner-1.9.1/unstable/widget -I/usr/include/xulrunner-1.9.1/unstable/windowwatcher -I/usr/include/xulrunner-1.9.1/unstable/xmlextras -I/usr/include/xulrunner-1.9.1/unstable/xpcom -I../../../src -I../../../src -I../../../src/bookmarks -I../../../src/dialogs -I../../../src/net -I../../../libegg/pixbufthumbnail -I../../../src/utils -I../../../module/embed/gecko -DMOZILLA_HOME=\/usr/lib/xulrunner-devel-1.9.1\ -DMOZILLA_PREFIX=\/usr\ -DGECKO_VERSION=\libxul-1.9.1.16\ -DG_LOG_DOMAIN=\Kazehakase-Gecko\ -DG_DISABLE_DEPRECATED=1 -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libdrm -DDEBIAN_VERSION=\0.5.8-4\ -Wall -g -O2 -Wall -Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wcast-align -MT kz-gecko-embed-module.lo -MD -MP -MF .deps/kz-gecko-embed-module.Tpo -c -o kz-gecko-embed-module.lo kz-gecko-embed-module.c mv -f .deps/kz-gecko-embed-module.Tpo .deps/kz-gecko-embed-module.Plo
Bug#624687: marked as done (kazehakase: several bugs, reproduced using both html rendering engines)
Your message dated Wed, 25 Jan 2012 12:52:16 + with message-id e1rq2km-0004oy...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #624687, regarding kazehakase: several bugs, reproduced using both html rendering engines 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.) -- 624687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624687 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kazehakase Version: 0.5.8-4 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages kazehakase depends on: ii kazehakase-gecko 0.5.8-4 Gecko rendering engine for kazehak ii kazehakase-webkit 0.5.8-4 WebKit rendering engine for kazeha ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdbus-glib-1-2 0.88-2.1 simple interprocess messaging syst ii libestraier8 1.4.9-1.4 a full-text search system Librarie ii libgcrypt111.4.5-2 LGPL Crypto library - runtime libr ii libgettext-ruby1.8 2.1.0-2.1 Gettext for ruby1.8 ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnutls262.8.6-1 the GNU TLS library - runtime libr ii libgtk2-ruby 0.19.3-2 GTK+ bindings for the Ruby languag ii libgtk2.0-02.20.1-2 The GTK+ graphical user interface ii libice62:1.0.6-2 X11 Inter-Client Exchange library ii libpango1.0-0 1.28.3-1+squeeze2 Layout and rendering of internatio ii libqdbm14 1.8.77-4 QDBM Database Libraries [runtime] ii libruby1.8 1.8.7.302-2 Libraries necessary to run Ruby 1. ii libsm6 2:1.1.1-1 X11 Session Management library ii ruby1.81.8.7.302-2 Interpreter of object-oriented scr ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime kazehakase recommends no packages. Versions of packages kazehakase suggests: pn anthy none (no description available) pn mecab none (no description available) pn migemonone (no description available) -- no debconf information Bookmarks don't open their respective website when clicked. Downloads do not work, as far as I can tell. I was trying to download a torrent file, and clicking on the link did not produce any dialog box or any sign or notification that downloading was taking place. Also, going to Help-- Open Kazehakase Website results in kaz, or at least the browser window, immediately closing. I installed the webkit version first, and after these bugs occured, I purged and reinstalled the gecko version of kaz, thinking maybe the problem had to do with the fact that chromium is already installed on my pc, and maybe kaz-webkit was using some shared webkit config file intended for chromium or something. But after using the gecko version, all the same problems occured. Perhaps it's a gtk problem then? ---End Message--- ---BeginMessage--- Version: 0.5.8-4+rm Dear submitter, as the package kazehakase has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#631055: marked as done (kazehakase: FTBFS against iceweasel 4.0 or 5.0)
Your message dated Wed, 25 Jan 2012 12:52:16 + with message-id e1rq2km-0004oy...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #631055, regarding kazehakase: FTBFS against iceweasel 4.0 or 5.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.) -- 631055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kazehakase Version: 0.5.8-4 Severity: serious Tags: sid wheezy User: pkg-mozilla-maintain...@lists.alioth.debian.org Usertags: xulrunner-2.0 Hi, your package fails to build against iceweasel 4.0 (currently in experimental). iceweasel 5.0 will soon be uploaded to unstable, so your package needs to be updated to cope with the new version, or will have to be removed. Build logs are available at http://people.debian.org/~glandium/iceweasel4-transition.logs.tbz2 Cheers, Julien ---End Message--- ---BeginMessage--- Version: 0.5.8-4+rm Dear submitter, as the package kazehakase has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#648465: marked as done (kazehakase: Crashes trying to print)
Your message dated Wed, 25 Jan 2012 12:52:16 + with message-id e1rq2km-0004oy...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #648465, regarding kazehakase: Crashes trying to print 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.) -- 648465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kazehakase Version: 0.5.8-4 Severity: grave Justification: causes non-serious data loss If you try to print (e.g. a receipt for transaction, which is only available once), then kazhakase crashes and you lose your session (and therefore any data in it). This is more about too-buggy-for-release than data loss though (in terms of RC aspect). Printing is a rather important function of a web browser, though at least not presenting the apparent option to print doesn't give false expectation of what you can do. -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kazehakase depends on: ii kazehakase-gecko 0.5.8-4 Gecko rendering engine for kazehak ii kazehakase-webkit0.5.8-4 WebKit rendering engine for kazeha ii libc62.11.2-10 Embedded GNU C Library: Shared lib ii libdbus-glib-1-2 0.88-2.1simple interprocess messaging syst ii libestraier8 1.4.9-1.4 a full-text search system Librarie ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr ii libgettext-ruby1.8 2.1.0-2.1 Gettext for ruby1.8 ii libglib2.0-0 2.24.2-1The GLib library of C routines ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libgtk2-ruby 0.19.3-2GTK+ bindings for the Ruby languag ii libgtk2.0-0 2.20.1-2The GTK+ graphical user interface ii libice6 2:1.0.6-2 X11 Inter-Client Exchange library ii libpango1.0-01.28.3-1+squeeze2 Layout and rendering of internatio ii libqdbm141.8.77-4QDBM Database Libraries [runtime] ii libruby1.8 1.8.7.302-2squeeze1 Libraries necessary to run Ruby 1. ii libsm6 2:1.1.1-1 X11 Session Management library ii ruby1.8 1.8.7.302-2squeeze1 Interpreter of object-oriented scr ii zlib1g 1:1.2.3.4.dfsg-3compression library - runtime kazehakase recommends no packages. Versions of packages kazehakase suggests: pn anthy none (no description available) pn mecab none (no description available) pn migemonone (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Version: 0.5.8-4+rm Dear submitter, as the package kazehakase has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#650252: marked as done (kazehakase: FTBFS because it needs libxul-embedding-unstable)
Your message dated Wed, 25 Jan 2012 12:52:16 + with message-id e1rq2km-0004oy...@franck.debian.org and subject line Bug#656771: Removed package(s) from unstable has caused the Debian Bug report #650252, regarding kazehakase: FTBFS because it needs libxul-embedding-unstable 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.) -- 650252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kazehakase Version: 0.5.8-4 Severity: serious Hi, here is the problem: $ fakeroot apt-get -b source kazehakase [...] checking for MOZILLA_COMPONENT... no configure: error: Package requirements (libxul-embedding-unstable = 1.9) were not met: No package 'libxul-embedding-unstable' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables MOZILLA_COMPONENT_CFLAGS and MOZILLA_COMPONENT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Build command 'cd kazehakase-0.5.8 dpkg-buildpackage -b -uc' failed. E: Child process failed Looking for package libxul-embedding instead of libxul-embedding-unstable would work: $ pkg-config --list-all | grep libxul libxul-embeddinglibxul-embedding - Static library for version-independent embedding of the Mozilla runtime -- Laurent Bonnaud. http://www.gipsa-lab.inpg.fr/page_pro.php?vid=96 ---End Message--- ---BeginMessage--- Version: 0.5.8-4+rm Dear submitter, as the package kazehakase has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/656771 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ---End Message---
Bug#642736: already fixed
close 642736 2:2.20110726-1 thanks The Squeeze policy is never going to build in Wheezy. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: already fixed
Processing commands for cont...@bugs.debian.org: close 642736 2:2.20110726-1 Bug#642736: refpolicy: FTBFS: policy/modules/services/nx.te:16:ERROR 'unknown role nx_server_r' at token ';' on line 2950: 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 2:2.20110726-1, send any further explanations to Mònica RamÃrez Arceda mon...@probeta.net thanks Stopping processing here. Please contact me if you need assistance. -- 642736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642736 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#647231: marked as done (libvisual-plugins: FTBFS(!linux): error: possibly undefined macro: AM_PATH_ALSA)
Your message dated Wed, 25 Jan 2012 13:19:02 + with message-id e1rq2kg-00082u...@franck.debian.org and subject line Bug#647231: fixed in libvisual-plugins 0.4.0.dfsg.1-6 has caused the Debian Bug report #647231, regarding libvisual-plugins: FTBFS(!linux): error: possibly undefined macro: AM_PATH_ALSA 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.) -- 647231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libvisual-plugins Version: 0.4.0.dfsg.1-4 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the !linux buildds: libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' configure.ac:210: warning: macro `AM_PATH_ALSA' not found in library configure.ac:210: error: possibly undefined macro: AM_PATH_ALSA If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make: *** [build] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=libvisual-pluginsarch=kfreebsd-i386ver=0.4.0.dfsg.1-5stamp=1320089612 Regards Christoph If you have further questions please mail debian-...@lists.debian.org -- 9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731 Debian Developer | Lisp Hacker | CaCert Assurer ---End Message--- ---BeginMessage--- Source: libvisual-plugins Source-Version: 0.4.0.dfsg.1-6 We believe that the bug you reported is fixed in the latest version of libvisual-plugins, which is due to be installed in the Debian FTP archive: libvisual-0.4-plugins_0.4.0.dfsg.1-6_amd64.deb to main/libv/libvisual-plugins/libvisual-0.4-plugins_0.4.0.dfsg.1-6_amd64.deb libvisual-plugins_0.4.0.dfsg.1-6.debian.tar.gz to main/libv/libvisual-plugins/libvisual-plugins_0.4.0.dfsg.1-6.debian.tar.gz libvisual-plugins_0.4.0.dfsg.1-6.dsc to main/libv/libvisual-plugins/libvisual-plugins_0.4.0.dfsg.1-6.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 647...@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 libvisual-plugins 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, 25 Jan 2012 11:46:09 +0100 Source: libvisual-plugins Binary: libvisual-0.4-plugins Architecture: source amd64 Version: 0.4.0.dfsg.1-6 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Michael Biebl bi...@debian.org Description: libvisual-0.4-plugins - Audio visualization framework plugins Closes: 647231 Changes: libvisual-plugins (0.4.0.dfsg.1-6) unstable; urgency=low . * QA upload. * Ship the alsa.m4 macro in the package since libasound2-dev is linux-only and autoreconf will fail on non-linux plattforms otherwise. Closes: #647231 Checksums-Sha1: 5dd7d39297eeb52f39930fc5a7bc10941e88a48e 1998 libvisual-plugins_0.4.0.dfsg.1-6.dsc fcf7fc5c2b9b0051529c1f23869896605e888034 8930 libvisual-plugins_0.4.0.dfsg.1-6.debian.tar.gz 6162fd9d52b617952984a50536b225ab6171b473 147096 libvisual-0.4-plugins_0.4.0.dfsg.1-6_amd64.deb Checksums-Sha256: b52bf7097b0d5eb5ad0eb73b475848934526815df3424316913083605a5255bc 1998 libvisual-plugins_0.4.0.dfsg.1-6.dsc a212c00d891710f2758ff31d82d8e6450ead02a26153a7e927181277e1958e8d 8930 libvisual-plugins_0.4.0.dfsg.1-6.debian.tar.gz cc9de779105897ca19283ab5bbaafa62fec442e52f6049dcc67a582c1fffdb42 147096 libvisual-0.4-plugins_0.4.0.dfsg.1-6_amd64.deb Files: f82b9f535dea6409d6058714a43b582a 1998 sound optional libvisual-plugins_0.4.0.dfsg.1-6.dsc d9e9baea8ee312c1245ab16a65952b48 8930 sound optional libvisual-plugins_0.4.0.dfsg.1-6.debian.tar.gz c19594de385b8416960589e612e8f68e 147096 sound optional libvisual-0.4-plugins_0.4.0.dfsg.1-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG
Processed (with 17 errors): r4444 - in packages/fonts-arphic-uming: tags tags/0.2.20080216.2-3/debian trunk/debian
Processing commands for cont...@bugs.debian.org:
tags 655842 pending
Bug #655842 {Done: Hideki Yamane henr...@debian.org} [fonts-arphic-uming]
fonts-arphic-uming: fails to remove
Added tag(s) pending.
tags 649826 pending
Failed to alter tags of Bug 649826: Not altering archived bugs; see unarchive.
tags 442612 pending
Failed to alter tags of Bug 442612: Not altering archived bugs; see unarchive.
tags 423720 pending
Failed to alter tags of Bug 423720: Not altering archived bugs; see unarchive.
tags 436531 pending
Failed to alter tags of Bug 436531: Not altering archived bugs; see unarchive.
tags 425024 pending
Failed to alter tags of Bug 425024: Not altering archived bugs; see unarchive.
tags 417071 pending
Failed to alter tags of Bug 417071: Not altering archived bugs; see unarchive.
tags 414774 pending
Failed to alter tags of Bug 414774: Not altering archived bugs; see unarchive.
tags 401252 pending
Failed to alter tags of Bug 401252: Not altering archived bugs; see unarchive.
tags 412318 pending
Failed to alter tags of Bug 412318: Not altering archived bugs; see unarchive.
tags 412341 pending
Failed to alter tags of Bug 412341: Not altering archived bugs; see unarchive.
tags 412578 pending
Failed to alter tags of Bug 412578: Not altering archived bugs; see unarchive.
tags 331187 pending
Failed to alter tags of Bug 331187: Not altering archived bugs; see unarchive.
tags 332126 pending
Failed to alter tags of Bug 332126: Not altering archived bugs; see unarchive.
tags 308752 pending
Failed to alter tags of Bug 308752: Not altering archived bugs; see unarchive.
tags 322364 pending
Failed to alter tags of Bug 322364: Not altering archived bugs; see unarchive.
tags 305811 pending
Failed to alter tags of Bug 305811: Not altering archived bugs; see unarchive.
tags 297659 pending
Failed to alter tags of Bug 297659: Not altering archived bugs; see unarchive.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
297659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=297659
322364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322364
655842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655842
401252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401252
331187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=331187
414774: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414774
417071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417071
332126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332126
425024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425024
305811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305811
442612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442612
412318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412318
412578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412578
423720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423720
308752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308752
436531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436531
649826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649826
412341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412341
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#648304: marked as done (FTBFS: serve blackbox tests fails because of threading lock error (kfreebsd))
Your message dated Wed, 25 Jan 2012 14:18:57 +0100 with message-id 20120125131857.ga21...@vernstok.nl and subject line No longer occurring has caused the Debian Bug report #648304, regarding FTBFS: serve blackbox tests fails because of threading lock error (kfreebsd) 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.) -- 648304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bzr Version: 2.4.2-2 Severity: serious Tags: upstream Forwarded: https://bugs.launchpad.net/bzr/+bug/888517 Debian GNU/kFreeBSD is hitting an exception while building: https://buildd.debian.org/status/fetch.php?pkg=bzrarch=kfreebsd-amd64ver=2.4.2-2stamp=1320714938 ERROR: bzrlib.tests.blackbox.test_serve.TestBzrServe.test_server_exception_with_hook -- _StringException: Text attachment: log 2236.022 creating config directory: '/tmp/testbzr-4ihL7w.tmp/bzrlib.tests.blackbox.test_serve.TestBzrServe.test_server_exception_with_hook/home/.bazaar' 2236.256 run bzr: ['serve', '--port', 'localhost:0', '--quiet'] 2236.256 bazaar version: 2.4.2 2236.256 bzr arguments: [u'serve', u'--port', u'localhost:0', u'--quiet'] 2236.261 encoding stdout as sys.stdout encoding 'ANSI_X3.4-1968' 2236.264 interrupting... Text attachment: traceback Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/testtools/runtest.py, line 169, in _run_user return fn(*args, **kwargs) File /usr/lib/python2.7/dist-packages/testtools/testcase.py, line 540, in _run_test_method return self._get_test_method()() File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/blackbox/test_serve.py, line 121, in test_server_exception_with_hook out, err = self.run_bzr_serve_then_func(args, retcode=0) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/blackbox/test_serve.py, line 93, in run_bzr_serve_then_func retcode=retcode) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/__init__.py, line 2027, in run_bzr working_dir=working_dir, File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/__init__.py, line 1925, in _run_bzr_autosplit encoding=encoding, stdin=stdin, working_dir=working_dir, File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/__init__.py, line 1960, in _run_bzr_core args) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/tests/__init__.py, line 2302, in apply_redirected return a_callable(*args, **kwargs) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/commands.py, line 1257, in run_bzr_catch_user_errors return run_bzr(argv) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/commands.py, line 1150, in run_bzr ret = run(*run_argv) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/commands.py, line 699, in run_argv_aliases return self.run(**all_cmd_args) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/commands.py, line 721, in run return self._operation.run_simple(*args, **kwargs) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/cleanup.py, line 135, in run_simple self.cleanups, self.func, *args, **kwargs) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/cleanup.py, line 165, in _do_with_cleanups result = func(*args, **kwargs) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/builtins.py, line 5152, in run protocol(t, host, port, inet) File /build/buildd-bzr_2.4.2-2-kfreebsd-amd64-Abt9zF/bzr-2.4.2/build/lib.gnukfreebsd-8.1-1-amd64-x86_64-2.7/bzrlib/smart/server.py, line 391, in serve_bzr bzr_server.smart_server.serve() File
Bug#656755: marked as done (libhmsbeagle FTBFS on everything except amd64)
Your message dated Wed, 25 Jan 2012 13:33:30 + with message-id e1rq2yg-0002eo...@franck.debian.org and subject line Bug#656755: fixed in libhmsbeagle 1.0-4 has caused the Debian Bug report #656755, regarding libhmsbeagle FTBFS on everything except amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 656755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: libhmsbeagle version: 1.0-2 severity: serious Note: i'm not an expert on this package, just someone looking at build failures and filing bugs. It seems things are a little more complex than they first appeared. In particular it seems libhmsbeagle has a specific sse2 plugin which can only be built with sse2 enabled and that is built even if --enable-sse=no is passed (which seems like a bug in the upstream build system to me). Therefore disabling -msse2 has caused the package to FTBFS everywhere except amd64. For non pc architectures I would think the sse2 plugin should simply be disabled. For i386 the descision on what to do there requires knowlege of the internals of the software. If the software is capable of making sensible descisions about whether to use the sse2 plugin at runtime then the sse2 plugin (but NOT the rest of the package) should be built with -msse2 (this will probablly require adding an option to the buildscripts along the lines of --enable-sse=ssepluginonly). If the software is NOT capable of making sensible descisions about whether to use the sse2 plugin at runtime then either it should simply be disabled on i386 or the ability to make sensible descsions about whether to use it at runtime should be added to the code. ---End Message--- ---BeginMessage--- Source: libhmsbeagle Source-Version: 1.0-4 We believe that the bug you reported is fixed in the latest version of libhmsbeagle, which is due to be installed in the Debian FTP archive: libhmsbeagle-dev_1.0-4_amd64.deb to main/libh/libhmsbeagle/libhmsbeagle-dev_1.0-4_amd64.deb libhmsbeagle-java_1.0-4_all.deb to main/libh/libhmsbeagle/libhmsbeagle-java_1.0-4_all.deb libhmsbeagle1_1.0-4_amd64.deb to main/libh/libhmsbeagle/libhmsbeagle1_1.0-4_amd64.deb libhmsbeagle_1.0-4.debian.tar.gz to main/libh/libhmsbeagle/libhmsbeagle_1.0-4.debian.tar.gz libhmsbeagle_1.0-4.dsc to main/libh/libhmsbeagle/libhmsbeagle_1.0-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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated libhmsbeagle 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: Wed, 25 Jan 2012 13:54:59 +0100 Source: libhmsbeagle Binary: libhmsbeagle-dev libhmsbeagle1 libhmsbeagle-java Architecture: source amd64 all Version: 1.0-4 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: libhmsbeagle-dev - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle-java - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle1 - High-performance lib for Bayesian and Maximum Likelihood phylogen Closes: 656755 Changes: libhmsbeagle (1.0-4) unstable; urgency=low . * debian/patches/disable_cpu_sse_plugin.patch: Apply patch from Peter Green (thanks for your help, Peter) and debian/rules: Enable sse for amd64 (only) to profit from plugin library Closes: #656755 Checksums-Sha1: 5115ab27aa06a916afe0bacc2e03d4bca68dfebd 1580 libhmsbeagle_1.0-4.dsc 547d2c4786278eb15ff97a9f2d1349a828b18fd2 7154 libhmsbeagle_1.0-4.debian.tar.gz 80bb24b5b6f55f8a196ab1a92e261f928a241300 503782 libhmsbeagle-dev_1.0-4_amd64.deb bb2d74527f18594cdfc040789d6a2e58cfb67327 124054 libhmsbeagle1_1.0-4_amd64.deb 412e9a63af1874c382a2345aa110af598567cb47 20364 libhmsbeagle-java_1.0-4_all.deb Checksums-Sha256: 806b59d6a355243dcfcd8744c6599cc371a22e3de885ae74240c4c68237c9b99 1580 libhmsbeagle_1.0-4.dsc 56b6dbb3625d526a32d1ba4e088ac4e3064c57bbccca3dc479f473e9f5c12dd9 7154 libhmsbeagle_1.0-4.debian.tar.gz
Processed: tagging 651859
Processing commands for cont...@bugs.debian.org: tags 651859 + pending Bug #651859 [speakup-source] Fails to build against Linux 3.1; redundant with in-tree drivers Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 651859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651859 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#657311: needs update for 9.0 in experimental
Package: icedove-l10n Version: 1:8.0-2 Severity: serious Tag: experimental Hi, icedove-l10n is no longer installable in experimental since the upload of icedove 9.0 (thanks, much appreciated). Please also upload icedove-l10n 9.0 to experimental. Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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): tag 656263 as fix-in-experimental
Processing commands for cont...@bugs.debian.org: tag 656263 + fix-in-experimental Unknown tag/s: fix-in-experimental. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore. Bug #656263 [src:libwv-dev] libwv-dev: must depend on all needed -dev packages Warning: Unknown package 'src:libwv-dev' Requested to add no tags; doing nothing. Warning: Unknown package 'src:libwv-dev' -- Stopping processing here. Please contact me if you need assistance. -- 656263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656263 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#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)
Hi Peter, many thanks for the patch which was in fact helpful to solve the problem. On Wed, Jan 25, 2012 at 11:04:13AM +, peter green wrote: Ok I took pity on you and took a look at the Makefile.am in that directory, turns out it wasn't that hard to disable building of the CPU with SSE plugin. You should really be able to do this kind of build-system modification yourself though, it's not like the package is using an exotic build system it's bog standard autotools. I agree that this was not to hard. However, I did not understand your motivation to work behind a perfectly working clean target which was fully functional by using autotools-dev, dh-autoreconf. So I deleted your part of debian/rules changes. I have tested that the resulting package builds on i386, I have not tested whether it actually works. I noticed that now the plugin for amd64 is not builded and needed to tweak debian/rules a bit by detecting the build architecture. Hope this will work now for all archs. The attatched patch makes the aforementioned change and also makes debian/rules clean actually work. As I said, this was unnecessary. Thanks in any case for your help Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651859: marked as done (Fails to build against Linux 3.1; redundant with in-tree drivers)
Your message dated Wed, 25 Jan 2012 13:51:27 + with message-id e1rq3g3-0007de...@franck.debian.org and subject line Bug#651859: fixed in speakup 3.1.5.dfsg.1-2 has caused the Debian Bug report #651859, regarding Fails to build against Linux 3.1; redundant with in-tree drivers 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.) -- 651859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: speakup-source Version: 3.1.5.dfsg.1-1 Severity: grave Tags: wheezy sid These modules fail to build against Linux 3.1: make[3]: Entering directory `/usr/src/linux-headers-3.1.0-1-amd64' /usr/src/linux-headers-3.1.0-1-common/arch/x86/Makefile:81: stack protector enabled but no compiler support LD /usr/src/modules/speakup/built-in.o CC [M] /usr/src/modules/speakup/speakup_acntsa.o CC [M] /usr/src/modules/speakup/speakup_acntpc.o CC [M] /usr/src/modules/speakup/speakup_apollo.o CC [M] /usr/src/modules/speakup/speakup_audptr.o CC [M] /usr/src/modules/speakup/speakup_bns.o CC [M] /usr/src/modules/speakup/speakup_dectlk.o CC [M] /usr/src/modules/speakup/speakup_decext.o CC [M] /usr/src/modules/speakup/speakup_dtlk.o CC [M] /usr/src/modules/speakup/speakup_keypc.o CC [M] /usr/src/modules/speakup/speakup_ltlk.o CC [M] /usr/src/modules/speakup/speakup_soft.o CC [M] /usr/src/modules/speakup/speakup_spkout.o CC [M] /usr/src/modules/speakup/speakup_txprt.o CC [M] /usr/src/modules/speakup/speakup_dummy.o CC [M] /usr/src/modules/speakup/buffers.o /usr/src/modules/speakup/buffers.c:2:28: fatal error: linux/smp_lock.h: No such file or directory compilation terminated. make[6]: *** [/usr/src/modules/speakup/buffers.o] Error 1 make[5]: *** [_module_/usr/src/modules/speakup] Error 2 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-3.1.0-1-amd64' Since the speakup drivers were merged into mainline Linux, there should be no need for an additional copy, so please remove this binary package. Ben. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages speakup-source depends on: ii bzip2 1.0.6-1 ii debhelper 8.9.11 ii module-assistant 0.11.4 speakup-source recommends no packages. Versions of packages speakup-source suggests: ii kernel-package 12.036+nmu1 -- no debconf information ---End Message--- ---BeginMessage--- Source: speakup Source-Version: 3.1.5.dfsg.1-2 We believe that the bug you reported is fixed in the latest version of speakup, which is due to be installed in the Debian FTP archive: speakup-doc_3.1.5.dfsg.1-2_all.deb to main/s/speakup/speakup-doc_3.1.5.dfsg.1-2_all.deb speakup-tools_3.1.5.dfsg.1-2_all.deb to main/s/speakup/speakup-tools_3.1.5.dfsg.1-2_all.deb speakup_3.1.5.dfsg.1-2.diff.gz to main/s/speakup/speakup_3.1.5.dfsg.1-2.diff.gz speakup_3.1.5.dfsg.1-2.dsc to main/s/speakup/speakup_3.1.5.dfsg.1-2.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 651...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault sthiba...@debian.org (supplier of updated speakup 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: Wed, 25 Jan 2012 14:30:06 +0100 Source: speakup Binary: speakup-doc speakup-tools Architecture: source all Version: 3.1.5.dfsg.1-2 Distribution: unstable Urgency: low Maintainer: Debian Accessibility Team debian-accessibil...@lists.debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: speakup-doc - Documentation for speakup kernel modules speakup-tools - Tools to manage speakup configuration and synths Closes: 604643 651859 Changes: speakup (3.1.5.dfsg.1-2) unstable; urgency=low . * debian/speakup.postinst and debian/speakup.prerm: Drop duplicate #DEBHELPER#. * Bump Standards-Version to 3.9.2 (no change needed) * Remove speakup-source
Bug#652601: marked as done (espeakedit FTBFS with multiarch libwxgtk2.8-dev)
Your message dated Wed, 25 Jan 2012 13:51:05 + with message-id e1rq3fh-0007aj...@franck.debian.org and subject line Bug#652601: fixed in espeakedit 1.43.03-4 has caused the Debian Bug report #652601, regarding espeakedit FTBFS with multiarch libwxgtk2.8-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.) -- 652601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: espeakedit severity: serious tags: patch espeakedit FTBFS with libwxgtk2.8-dev 2.8.12.1-4 or later. This was first noticed on the armhf buildd but I have also reproduced it on i386. The cause is that /usr/lib/wx/include/gtk2-unicode-release-2.8/wx/setup.h has moved to /usr/lib/multiarch triplet/wx/include/gtk2-unicode-release-2.8/wx/setup.h The attatched patch fixes the paths and adds appropriate build-depends (the dpkg-dev dep is for dpkg-architecture -qDEB_HOST_MULTIARCH ). diff -ur espeakedit-1.43.03/debian/control espeakedit-1.43.03.new/debian/control --- espeakedit-1.43.03/debian/control 2011-10-12 08:51:22.0 +0100 +++ espeakedit-1.43.03.new/debian/control 2011-12-19 02:00:32.0 + @@ -6,7 +6,7 @@ Vcs-Browser: http://git.debian.org/?p=pkg-a11y/espeakedit.git;a=summary Vcs-Git: git://git.debian.org/git/pkg-a11y/espeakedit.git Homepage: http://espeak.sourceforge.net/ -Build-Depends: debhelper (= 7), libwxgtk2.8-dev, portaudio19-dev +Build-Depends: debhelper (= 7), libwxgtk2.8-dev (= 2.8.12.1-4), portaudio19-dev, dpkg-dev (= 1.16.0) Standards-Version: 3.9.2 Package: espeakedit diff -ur espeakedit-1.43.03/debian/patches/wx2.8.diff espeakedit-1.43.03.new/debian/patches/wx2.8.diff --- espeakedit-1.43.03/debian/patches/wx2.8.diff 2011-10-12 08:54:21.0 +0100 +++ espeakedit-1.43.03.new/debian/patches/wx2.8.diff 2011-12-19 02:02:56.0 + @@ -1,8 +1,8 @@ -diff --git a/src/Makefile b/src/Makefile -index d26273d..464fb0b 100644 a/src/Makefile -+++ b/src/Makefile -@@ -1,13 +1,13 @@ +Index: espeakedit-1.43.03/src/Makefile +=== +--- espeakedit-1.43.03.orig/src/Makefile 2007-05-05 11:25:42.0 +0100 espeakedit-1.43.03/src/Makefile 2011-12-19 02:02:29.0 + +@@ -1,13 +1,14 @@ SRCS=$(wildcard *.cpp) OBJS=$(patsubst %.cpp,%.o,$(SRCS)) @@ -12,10 +12,11 @@ LIBS=-lstdc++ -lportaudio -CPPFLAGS = -Wall -g -fexceptions -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT -+CPPFLAGS = -Wall -g -fexceptions -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT ++DEB_HOST_MULTIARCH ?=$(shell dpkg-architecture -qDEB_HOST_MULTIARCH) ++CPPFLAGS = -Wall -g -fexceptions -I/usr/lib/$(DEB_HOST_MULTIARCH)/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT -CXXFLAGS = -O2 -g0 -Wall -g -fexceptions -I/usr/lib/wx/include/gtk2-unicode-release-2.6 -I/usr/include/wx-2.6 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT -+CXXFLAGS = -O2 -g0 -Wall -g -fexceptions -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT ++CXXFLAGS = -O2 -g0 -Wall -g -fexceptions -I/usr/lib/$(DEB_HOST_MULTIARCH)/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -DNO_GCC_PRAGMA -D_ESPEAKEDIT all: espeakedit ---End Message--- ---BeginMessage--- Source: espeakedit Source-Version: 1.43.03-4 We believe that the bug you reported is fixed in the latest version of espeakedit, which is due to be installed in the Debian FTP archive: espeakedit_1.43.03-4.debian.tar.gz to main/e/espeakedit/espeakedit_1.43.03-4.debian.tar.gz espeakedit_1.43.03-4.dsc to main/e/espeakedit/espeakedit_1.43.03-4.dsc espeakedit_1.43.03-4_amd64.deb to main/e/espeakedit/espeakedit_1.43.03-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address
Processed: Re: Processed (with 1 errors): tag 656263 as fix-in-experimental
Processing commands for cont...@bugs.debian.org: tag 656263 + fixed-in-experimental Bug #656263 [src:libwv-dev] libwv-dev: must depend on all needed -dev packages Warning: Unknown package 'src:libwv-dev' Added tag(s) fixed-in-experimental. Warning: Unknown package 'src:libwv-dev' -- Stopping processing here. Please contact me if you need assistance. -- 656263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656263 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#654613: marked as done (pyxpcom: FTBFS on armhf, reproduced on sid amd64: No rule to make target `_xpidlgen/py_test_component.h', needed by `export'.)
Your message dated Wed, 25 Jan 2012 15:02:06 +0100 with message-id 20120125140206.ga5...@glandium.org and subject line Re: Bug#654613: pyxpcom: FTBFS on armhf, reproduced on sid amd64: No rule to make target `_xpidlgen/py_test_component.h', needed by `export'. has caused the Debian Bug report #654613, regarding pyxpcom: FTBFS on armhf, reproduced on sid amd64: No rule to make target `_xpidlgen/py_test_component.h', needed by `export'. 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.) -- 654613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pyxpcom Version: 1:8.0~hg20111006-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=pyxpcomarch=armhfver=1%3A8.0%7Ehg20111006-1stamp=1324610578 pyxpcom FTBFS on armhf, but I reproduced the exact failure on sid amd64, hence the severity set to serious. Excerpt from the build log: /usr/bin/python ../../../../config/nsinstall.py -D ../../../dist/idl make[6]: *** No rule to make target `_xpidlgen/py_test_component.h', needed by `export'. Stop. Please look into this. Thanks Konstantinos ---End Message--- ---BeginMessage--- Version: 9.0~hg20111212-1 On Wed, Jan 25, 2012 at 03:20:21AM +0100, Cyril Brulebois wrote: Konstantinos Margaritis mar...@genesi-usa.com (04/01/2012): Package: pyxpcom Version: 1:8.0~hg20111006-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=pyxpcomarch=armhfver=1%3A8.0%7Ehg20111006-1stamp=1324610578 pyxpcom FTBFS on armhf, but I reproduced the exact failure on sid amd64, hence the severity set to serious. Excerpt from the build log: /usr/bin/python ../../../../config/nsinstall.py -D ../../../dist/idl make[6]: *** No rule to make target `_xpidlgen/py_test_component.h', needed by `export'. Stop. There are other interesting parts during configure: | ../configure: 774: test: /build/buildd-pyxpcom_8.0~hg20111006-1-armhf-1vVrmO/pyxpcom-8.0~hg20111006: unexpected operator … | ../configure: 9917: ../configure: AM_LANGINFO_CODESET: not found … | ../configure: 10886: test: /usr/lib/xulrunner-devel-9.0: unexpected operator … Flakky build (configure) system? pyxpcom needed a few changes for xulrunner 9.0, and that's in the upload I just did. Mike ---End Message---
Bug#657312: keeps index files in /usr/share/man
Package: perlindex Version: 1.605-1 Severity: serious As it seems, perlindex maintains its index files under in /usr/share/man: $ ls -l /usr/share/man/index* -rw-r--r-- 1 root root 1257472 Jan 25 07:54 /usr/share/man/index_fn -rw-r--r-- 1 root root 5242880 Jan 25 07:54 /usr/share/man/index_idf -rw-r--r-- 1 root root 51593216 Jan 25 07:54 /usr/share/man/index_if -rw-r--r-- 1 root root 5230592 Jan 25 07:54 /usr/share/man/index_if.new -rw-r--r-- 1 root root 1290240 Jan 25 07:54 /usr/share/man/index_seen At some point in the past it seems to have used /var/cache/perlindex, as suggested by the debconf questions: $ ls -l /var/cache/perlindex# note the dates -rw-r--r-- 1 root root 1302528 Feb 11 2009 index_fn -rw-r--r-- 1 root root 2641920 Feb 11 2009 index_idf -rw-r--r-- 1 root root 8372224 Feb 11 2009 index_if -rw-r--r-- 1 root root 1294336 Feb 11 2009 index_seen The breaking commit is cf94623 (from yours truly), converting debian/rules to dh7 and omitting a critical INDEXDIR setting during $(MAKE) call. Ouch! Setting version accordingly. Will look dfor a fix. Fixing this bug will also fix a piuparts error :) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages perlindex depends on: ii debconf [debconf-2.0] 1.5.41 ii libterm-readkey-perl 2.30-4+b2 ii libtext-english-perl 1.605-3 ii perl 5.14.2-6 Versions of packages perlindex recommends: ii libio-stringy-perl 2.110-5 perlindex suggests no packages. -- debconf information: * perlindex/removeindexonpurge: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639636: [node-dev] Re: Bug#639636: nodejs: FTBFS/armel - testsuite fails
update : now building 0.6.8, test/simple/test-buffer is still failing on armel (armv4t), see https://buildd.debian.org/status/fetch.php?pkg=nodejsarch=armelver=0.6.8~dfsg1-1stamp=1327488576 Since the test used to succeed on armv7, i guess it needs an upstream v8 opinion. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610256: Fixed upstream
retitle 610256 gjs: Some tests fail on big endian architectures severity 610256 important tags 610256 fixed-upstream kthxbye As mentioned on the upstream bug report in https://bugzilla.gnome.org/show_bug.cgi?id=639505#c15 , cherry-picking upstream Git commits ca276a8281a045949fd3c2ad338260d808559a30 and dc69b12d5e44f9d3b209759082f721237a8c9a06 fixes the tests and related problems in gnome-shell. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Fixed upstream
Processing commands for cont...@bugs.debian.org: retitle 610256 gjs: Some tests fail on big endian architectures Bug #610256 [src:gjs] gjs: FTBFS: ./test/run-with-dbus: script gtester failed Changed Bug title to 'gjs: Some tests fail on big endian architectures' from 'gjs: FTBFS: ./test/run-with-dbus: script gtester failed' severity 610256 important Bug #610256 [src:gjs] gjs: Some tests fail on big endian architectures Severity set to 'important' from 'serious' tags 610256 fixed-upstream Bug #610256 [src:gjs] gjs: Some tests fail on big endian architectures Added tag(s) fixed-upstream. kthxbye Stopping processing here. Please contact me if you need assistance. -- 610256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610256 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#657258: marked as done (src:libindicate: Rebuild for Mono transition)
Your message dated Wed, 25 Jan 2012 14:52:40 + with message-id e1rq4di-0003zb...@franck.debian.org and subject line Bug#657258: fixed in libindicate 0.5.0-4 has caused the Debian Bug report #657258, regarding src:libindicate: Rebuild for Mono transition 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.) -- 657258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:libindicate Version: 0.5.0-3 Severity: serious User: debian-...@lists.debian.org Usertags: mono-2.10-transition Hi, A Mono transition is underway. Every source package needs to be rebuilt to compile against CLR 4.0 instead of CLR 2.0. Please upload libindicate for this change. You can check it worked if, after rebuilding, libindicate0.1-cil has a dependency on libmono-corlib4.0-cil instead of …corlib2.0-cil. http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775 Cheers, ---End Message--- ---BeginMessage--- Source: libindicate Source-Version: 0.5.0-4 We believe that the bug you reported is fixed in the latest version of libindicate, which is due to be installed in the Debian FTP archive: gir1.2-indicate-0.5_0.5.0-4_amd64.deb to main/libi/libindicate/gir1.2-indicate-0.5_0.5.0-4_amd64.deb libindicate-dev_0.5.0-4_amd64.deb to main/libi/libindicate/libindicate-dev_0.5.0-4_amd64.deb libindicate-doc_0.5.0-4_all.deb to main/libi/libindicate/libindicate-doc_0.5.0-4_all.deb libindicate-gtk-dev_0.5.0-4_amd64.deb to main/libi/libindicate/libindicate-gtk-dev_0.5.0-4_amd64.deb libindicate-gtk0.1-cil-dev_0.5.0-4_all.deb to main/libi/libindicate/libindicate-gtk0.1-cil-dev_0.5.0-4_all.deb libindicate-gtk0.1-cil_0.5.0-4_all.deb to main/libi/libindicate/libindicate-gtk0.1-cil_0.5.0-4_all.deb libindicate-gtk2_0.5.0-4_amd64.deb to main/libi/libindicate/libindicate-gtk2_0.5.0-4_amd64.deb libindicate0.1-cil-dev_0.5.0-4_all.deb to main/libi/libindicate/libindicate0.1-cil-dev_0.5.0-4_all.deb libindicate0.1-cil_0.5.0-4_all.deb to main/libi/libindicate/libindicate0.1-cil_0.5.0-4_all.deb libindicate5_0.5.0-4_amd64.deb to main/libi/libindicate/libindicate5_0.5.0-4_amd64.deb libindicate_0.5.0-4.diff.gz to main/libi/libindicate/libindicate_0.5.0-4.diff.gz libindicate_0.5.0-4.dsc to main/libi/libindicate/libindicate_0.5.0-4.dsc python-indicate_0.5.0-4_amd64.deb to main/libi/libindicate/python-indicate_0.5.0-4_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 657...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov evg...@debian.org (supplier of updated libindicate 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: Wed, 25 Jan 2012 12:11:05 +0100 Source: libindicate Binary: python-indicate libindicate5 libindicate-dev libindicate-gtk2 libindicate-gtk-dev libindicate-doc gir1.2-indicate-0.5 libindicate0.1-cil libindicate0.1-cil-dev libindicate-gtk0.1-cil libindicate-gtk0.1-cil-dev Architecture: source all amd64 Version: 0.5.0-4 Distribution: unstable Urgency: low Maintainer: The Ayatana Packagers pkg-ayatana-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: gir1.2-indicate-0.5 - Typelib file for libindicate5 libindicate-dev - library for raising indicators via DBus - development files libindicate-doc - library for raising indicators via DBus - documentation libindicate-gtk-dev - library for raising indicators via DBus - GTK+ bindings developme libindicate-gtk0.1-cil - CLI bindings for libindicate-gtk2 libindicate-gtk0.1-cil-dev - CLI bindings for libindicate-gtk4 - development files libindicate-gtk2 - library for raising indicators via DBus - GTK+ bindings libindicate0.1-cil - CLI bindings for libindicate5 libindicate0.1-cil-dev - CLI bindings for libindicate5 - development files libindicate5 - library for raising indicators via DBus python-indicate - Python bindings for libindicate Closes: 657258 Changes: libindicate (0.5.0-4) unstable; urgency=low . * Sourcefull rebuild for the Mono transition. Closes: #657258 Checksums-Sha1: 7c84e4abc1c56ee60c303b81f83396a54ffc3eb8 2402
Processed: Pending fixes for bugs in the perlindex package
Processing commands for cont...@bugs.debian.org: tag 657312 + pending Bug #657312 [perlindex] keeps index files in /usr/share/man Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 657312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657312 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#657312: Pending fixes for bugs in the perlindex package
tag 657312 + pending thanks Some bugs in the perlindex package are closed in revision fdd251ec223436ac53ef78c171631b6c61306329 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/perlindex.git;a=commitdiff;h=fdd251e Commit message: rules: invoke upstream build system with INDEXDIR in /var/cache otherwise the index files end up in /usr/share/man Closes: #657312 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures
Hi, We've got quite the same error with FreeBSD support. Attached patch should fix this issue. If it will still fail, would be helpful to have config.h generated by configure script of glog itself (which can be found here http://code.google.com/p/google-glog/). But if proposed patch will work fine, it can be commited to trunk. -- With best regards, Sergey Sharybin Index: extern/libmv/third_party/glog/src/config_linux.h === --- extern/libmv/third_party/glog/src/config_linux.h (revision 43691) +++ extern/libmv/third_party/glog/src/config_linux.h (working copy) @@ -133,6 +133,8 @@ /* How to access the PC from a struct ucontext */ #if defined(_M_X64) || defined(__amd64__) || defined(__x86_64__) #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_RIP] +#elif defined(IA64) + #undef PC_FROM_UCONTEXT #else #define PC_FROM_UCONTEXT uc_mcontext.gregs[REG_EIP] #endif
Bug#654468: removal
For what it's worth, this bug made gigolo appear on http://release.debian.org/~nthykier/rc-buggy-leaf-pkgs-dd-list-2012-01-25 I disagree about the RC-ness of that bug but I won't fight against ftpmasters on this, so that means gigolo won't be part of the next Debian release. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657275: libswe: FTBFS - unoconv expects writable home, loopback network(?)
Paul Elliott pelli...@blackpatchpanel.com writes:
I will begin looking at the problem immediately.
Thanks!
But as I am a beginning packager it may take me a while to completely
understand the situation.
No problem.
For instance, libswe just appeared in debian unstable, that means someone
must
have built it. How does the build environment of the autobuilder's differ
from
the one that built libswe on its path to unstable? Why is the autobuilder's
environment correct? In other words, why is this not a bug against the
autobuilder's software?
That's a fair question. As I recall, the setting historically came
about because autobuilders would reuse build environments from one
package to the next, and wanted to avoid having extra things to clean
up.
How can I duplicate the autobuilder's builds on my local machine to test this
problem?
Please try installing the sbuild package.
What is a full build and can I be sure that a full build will never occur
in
the autobuilder?
By a full build, I mean one that covers all binary packages (as
dpkg-buildpackage and wrappers such as debuild do by default) rather
than just the architecture-dependent ones. Autobuilders cover only the
latter, as rebuilding architecture-independent packages would be
redundant, and likewise disregard Build-Depends-Indep (making them
unlikely to have unoconv installed if you move it there from
Build-Depends).
That said, their environments are not technically guaranteed to be
minimal, so I'd still recommend building documentation only when
actually necessary. Also, there has been talk of discarding uploaded
binary packages, so you should still probably allow for that possibility
by adjusting debian/rules to establish and use a fake home directory.
Please try the following version, which incorporates both suggestions:
#!/usr/bin/make -f
# ... boilerplate comments snipped
FAKE_HOME=$(CURDIR)/debian/fake-home
export HOME=$(FAKE_HOME)
%:
dh $@
override_dh_auto_clean:
rm -rf $(FAKE_HOME)
override_dh_auto_configure:
mkdir $(FAKE_HOME)
if dh_listpackages | fgrep -qe -doc; then \
dh_auto_configure -- --docdir=\$${prefix}/share/doc/libswe-doc; \
else \
dh_auto_configure -- --disable-docs; \
fi
Thank You for considering this message.
Thanks for your contribution to Debian!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653887: libavformat53 breaks mplayer
clone 653887 -1 reassign -1 libavcodec-extra-53 severity -1 wishlist reopen -1 retitle -1 Please add breaks against mplayer found -1 4:0.8~beta2.2 thanks On Sun, Jan 01, 2012 at 02:56:29PM +0100, Reinhard Tartler wrote: On So, Jan 01, 2012 at 13:57:13 (CET), Julien Cristau wrote: On Sun, Jan 1, 2012 at 08:25:00 +0100, Reinhard Tartler wrote: [...] libavformat53 in experimental seems to have broken mplayer's ability to playback files. After upgrading to 4:0.8~beta1-1, mplayer reports the following whenever I attempt to play something: mplayer: relocation error: mplayer: symbol ff_codec_wav_tags, version LIBAVFORMAT_53 not defined in file libavformat.so.53 with link time reference I really think this is a bug in mplayer. ff_codec_wav_tags is and always was an internal symbol, that is no longer exported since this commit: http://git.libav.org/?p=libav.git;a=commitdiff;h=8d74bf17c6d6280195854f4dadb19ef37d054566 This issue a long-standing wart in mplayer that should really be fixed there. It should *also* be fixed in libavformat53 by adding Breaks against unfixed versions of mplayer. Yes, but only after we actually have a fixed version of mplayer in debian, or am I missing something? This is now the case. And also the corrected mplayer seems to have problems migrating to Testing, while libavformat53 has. Rebuilding of the new mplayer in testing does not work, either, because trying to install the build deps runs into: libavcodec-dev : Depends: libavcodec53 (= 4:0.7.3-99) but it is not going to be installed or libavcodec-extra-53 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed libavdevice-dev : Depends: libavdevice53 (= 4:0.7.3-99) but it is not going to be installed or libavdevice-extra-53 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed libavformat-dev : Depends: libavformat53 (= 4:0.7.3-99) but it is not going to be installed or libavformat-extra-53 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed libavutil-dev : Depends: libavutil51 (= 4:0.7.3-99) but it is not going to be installed or libavutil-extra-51 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed libpostproc-dev : Depends: libpostproc52 (= 4:0.7.3-99) but it is not going to be installed or libpostproc-extra-52 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed libswscale-dev : Depends: libswscale2 (= 4:0.7.3-99) but it is not going to be installed or libswscale-extra-2 (= 4:0.7.3.99) but 4:0.8~beta2.2 is to be installed So for now mplayer is broken in Testing. (And yes, there are other players, but mplayer *does* have its advantages) And also consider partial updates. 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#655930: gnome-mousetrap: broken by python-opencv 2.3
Hi there, You wrote: gnome-mousetrap is completely broken by the new opencv API. I have tried to patch, but came to a difficult issue, I have forwarded the issue upstream, without answer for now. I've been looking on the bug list[1] but I can't find anything similar to what you complain, can you please tell what the bug number you're referring to? [1] https://bugzilla.gnome.org/buglist.cgi?product=mousetrapbug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENED Best regards, -- Marcos Marado -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Forgot to CC control
Processing commands for cont...@bugs.debian.org:
clone 653887 -1
Bug#653887: libavformat53 breaks mplayer
Bug 653887 cloned as bug 657326.
reassign -1 libavcodec-extra-53
Bug #657326 {Done: Reinhard Tartler siret...@tauware.de} [mplayer]
libavformat53 breaks mplayer
Bug reassigned from package 'mplayer' to 'libavcodec-extra-53'.
Bug No longer marked as found in versions mplayer/2:1.0~rc4.dfsg1-1.
Bug No longer marked as fixed in versions mplayer/2:1.0~rc4.dfsg1+svn34492-1.
severity -1 wishlist
Bug #657326 {Done: Reinhard Tartler siret...@tauware.de}
[libavcodec-extra-53] libavformat53 breaks mplayer
Severity set to 'wishlist' from 'serious'
reopen -1
Bug #657326 {Done: Reinhard Tartler siret...@tauware.de}
[libavcodec-extra-53] libavformat53 breaks mplayer
retitle -1 Please add breaks against mplayer
Bug #657326 [libavcodec-extra-53] libavformat53 breaks mplayer
Changed Bug title to 'Please add breaks against mplayer' from 'libavformat53
breaks mplayer'
found -1 4:0.8~beta2.2
Bug #657326 [libavcodec-extra-53] Please add breaks against mplayer
Bug Marked as found in versions libav-extra/4:0.8~beta2.2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
657326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657326
653887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653887
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
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#653047: closed by Mike Hommey m...@glandium.org (Re: Bug#653047: jshashtable.h uses UINT32_MAX without including jsstdint.h)
severity 653047 important thanks Debian Bug Tracking System ow...@bugs.debian.org (23/12/2011): On Fri, Dec 23, 2011 at 03:53:44AM +0100, Michael Biebl wrote: Package: libmozjs-dev Version: 9.0.1-1 Severity: serious File: /usr/include/mozjs/jshashtable.h $ grep UINT32_MAX * jshashtable.h:JS_STATIC_ASSERT((sMaxCapacity * sInvMaxAlpha) = UINT32_MAX); jshashtable.h:JS_STATIC_ASSERT((sMaxCapacity * sizeof(Entry)) = UINT32_MAX); jsstdint.h:#define UINT32_MAX 4294967295U $ grep jsstdint.h jshashtable.h This breaks software using that header, thus RC severity That header goes away in version 10. I don't even think it was meant to be public. Downgrading severity accordingly, giving us an opportunity to migrate iceweasel 9 “soon”. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#653047 closed by Mike Hommey m...@glandium.org (Re: Bug#653047: jshashtable.h uses UINT32_MAX without including jsstdint.h)
Processing commands for cont...@bugs.debian.org:
severity 653047 important
Bug #653047 {Done: Mike Hommey m...@glandium.org} [libmozjs-dev]
jshashtable.h uses UINT32_MAX without including jsstdint.h
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
653047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653047
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#388141: Let's ask for a relicensing agreement
retitle 388141 Old content is not DFSG-free until all contributors agree for relicensing thanks Hi, Thanks to Stefano's help (see #238245), the new content of the website will now be DFSG free. In order to make the old content DFSG free, we need the agreement of every author of previous contributions. I propose to send them the following message, and will gladly accept your remarks before actually sending it: ——— Subject: Permission to relicense your Debian web site contributions Hi, As you may already be aware of (see #238245 for more information), the new material of the Debian web site is now compliant with our free software guidelines. In order to make the old content available with the same licenses, we need your agreement. Please send us back the following agreement, and, if you committed anything on behalf of someone else in the past (e.g. if you acted as a translation coordinator), please do ask them to also send it back to us: --8--8-- I hereby give permission to relicense all the material that I have provided to the Debian website under the terms of the MIT (Expat) License and of the GNU General Public License, version 2 and any later version. --8--8-- Thanks for the work you already did for the Debian web site, and thanks in advance for helping us to make it free. Regards someone on behalf of the Debian web team P.-S.: Please mention your real name and your Alioth (and pre-Alioth) account name(s) to help us track your commits. ——— As a first step of this relicensing task, I propose we contact: - current contributors (the 213 members of the Alioth webwml group); - members of security team who provided DSA (in security/year/); - members of publicity and release teams who provided News/ content. In the mean time, I hope translation coordinators could take care of contacting the previous translators of their language (who are not already among the current members of the Alioth webwml group). We'll also have to contact previous contributors who are not currently member of the Alioth webwml group (so we first need to identify them), and probably many more people in some corner cases I didn't yet think of right now. We could continue to discuss the specifics of the relicensing work flow only in the debian-www mailing list not to flood this bug report, and come back to this bug report when we have significant information to share. Regards David P.-S.: The relicensing agreement should be sent to webmas...@debian.org, in order not to spam our public mailing list or bug tracker, and to make it available to any Debian developer. signature.asc Description: OpenPGP digital signature
Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures
Hi Sergey, Le 25/01/2012 16:04, Sergey Sharybin a écrit : Hi, We've got quite the same error with FreeBSD support. Attached patch should fix this issue. If it will still fail, would be helpful to have config.h generated by configure script of glog itself (which can be found here http://code.google.com/p/google-glog/). But if proposed patch will work fine, it can be commited to trunk. I think the patch 0011-fix_FTBFS_with_libmv [1] in git will cover configs other than i386/amd64 but in doubt, could you look at it and tell me if yours is need to be added? Thanks [1] http://anonscm.debian.org/gitweb/?p=pkg-multimedia/blender.git;a=blob;f=debian/patches/0011-fix_FTBFS_with_libmv.patch;h=22356fef7cb9fcc6d63b02880a85506aeae0546b;hb=HEAD -- Kevin 'Kiniou' Roy http://blog.knokorpo.fr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646657: Fix available
Coin, Quoting Diego Elio Pettenò flamee...@flameeyes.eu: https://github.com/jimweirich/builder/pull/15 should fix the issue (and another unrelated one fwiw). -- Diego Elio Pettenò flamee...@flameeyes.eu Thanks a lot :-). -- Marc Dequènes (Duck) pgpA7hl1RSD0R.pgp Description: PGP Digital Signature
Bug#657336: ikiwiki-hosting-web: doesnt use invoke-rc.d
Package: ikiwiki-hosting-web Version: 0.20111005 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package starts processes where it shouldnt. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. This is seriously disturbing! ;-) See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well as /usr/share/doc/sysv-rc/README.policy-rc.d.gz From the attached log (scroll to the bottom...): Selecting previously unselected package ikiwiki-hosting-web. (Reading database ... 19255 files and directories currently installed.) Unpacking ikiwiki-hosting-web (from .../ikiwiki-hosting-web_0.20111005_amd64.deb) ... Setting up ikiwiki-hosting-web (0.20111005) ... invoke-rc.d: policy-rc.d denied execution of start. Enabling module suexec. To activate the new configuration, you need to run: service apache2 restart Enabling module userdir. To activate the new configuration, you need to run: service apache2 restart Restarting web server: apache2(98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed. The Apache error log may have more information. failed! dpkg: error processing ikiwiki-hosting-web (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: ikiwiki-hosting-web The installation is performed in a chroot and apache can't be started there because :80 is already in use on the host. But there is a policy-rc.d in the chroot that forbids starting any service, so this shouldn't even be attempted. cheers, Andreas ikiwiki-hosting-web_0.20111005.log.gz Description: GNU Zip compressed data
Bug#634400: morituri: diff for NMU version 0.1.2-1.1
tags 634400 + patch
tags 634400 + pending
thanks
Dear maintainer,
I've prepared an NMU for morituri (versioned as 0.1.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Rolling Stones
diff -Nru morituri-0.1.2/debian/changelog morituri-0.1.2/debian/changelog
--- morituri-0.1.2/debian/changelog 2011-06-05 19:28:39.0 +0200
+++ morituri-0.1.2/debian/changelog 2012-01-25 19:34:19.0 +0100
@@ -1,3 +1,13 @@
+morituri (0.1.2-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS: tests failed: add upstream patch, via Ubuntu / Daniel T Chen:
+- Add skip_flacparse.patch to fix FTBFS. (LP: #833896)
+Commit message: flacparse is busted in gst-plugins-good 0.10.30 too
+(Closes: #634400)
+
+ -- gregor herrmann gre...@debian.org Wed, 25 Jan 2012 19:32:34 +0100
+
morituri (0.1.2-1) unstable; urgency=low
* New upstream release.
diff -Nru morituri-0.1.2/debian/patches/series morituri-0.1.2/debian/patches/series
--- morituri-0.1.2/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ morituri-0.1.2/debian/patches/series 2012-01-25 19:32:20.0 +0100
@@ -0,0 +1 @@
+skip_flacparse.patch
diff -Nru morituri-0.1.2/debian/patches/skip_flacparse.patch morituri-0.1.2/debian/patches/skip_flacparse.patch
--- morituri-0.1.2/debian/patches/skip_flacparse.patch 1970-01-01 01:00:00.0 +0100
+++ morituri-0.1.2/debian/patches/skip_flacparse.patch 2012-01-25 19:33:45.0 +0100
@@ -0,0 +1,25 @@
+Description: Handle known-bad versions of gst-plugins-good, including 0.10.30
+Forwarded: not-needed
+Origin: upstream, https://thomas.apestaart.org/morituri/trac/changeset/535
+Author: Thomas Vander Stichele
+Reviewed-by: Daniel T Chen crim...@ubuntu.com
+Bug: https://thomas.apestaart.org/morituri/trac/ticket/78
+Bug-Debian: http://bugs.debian.org/634400
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/morituri/+bug/833896
+Last-Updated: 2011-09-15
+
+Index: morituri-0.1.2/morituri/common/gstreamer.py
+===
+--- morituri-0.1.2.orig/morituri/common/gstreamer.py 2011-09-15 00:33:23.0 -0400
morituri-0.1.2/morituri/common/gstreamer.py 2011-09-15 00:34:47.0 -0400
+@@ -190,8 +190,9 @@
+ log.debug('gstreamer', 'Found audioparsers plugin from %s %s',
+ plugin.get_source(), plugin.get_version())
+
++# was fixed after 0.10.30 and before 0.10.31
+ if plugin.get_source() == 'gst-plugins-good' \
+-and plugin.get_version() '0.10.29.1':
++and plugin.get_version() '0.10.30.1':
+ return
+
+ registry.remove_plugin(plugin)
signature.asc
Description: Digital signature
Processed: morituri: diff for NMU version 0.1.2-1.1
Processing commands for cont...@bugs.debian.org: tags 634400 + patch Bug #634400 [src:morituri] morituri: FTBFS: tests failed Added tag(s) patch. tags 634400 + pending Bug #634400 [src:morituri] morituri: FTBFS: tests failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 634400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634400 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#642754: marked as done (morfologik-stemming: FTBFS: You must specify a valid JAVA_HOME or JAVACMD)
Your message dated Wed, 25 Jan 2012 18:48:58 + with message-id e1rq7ty-0007re...@franck.debian.org and subject line Bug#642754: fixed in morfologik-stemming 1.2.2-1.1 has caused the Debian Bug report #642754, regarding morfologik-stemming: FTBFS: You must specify a valid JAVA_HOME or JAVACMD 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.) -- 642754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642754 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: morfologik-stemming Version: 1.2.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules clean test -x debian/rules dh_testroot You must specify a valid JAVA_HOME or JAVACMD! make: *** [testsanity] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/morfologik-stemming_1.2.2-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: morfologik-stemming Source-Version: 1.2.2-1.1 We believe that the bug you reported is fixed in the latest version of morfologik-stemming, which is due to be installed in the Debian FTP archive: libmorfologik-stemming-java_1.2.2-1.1_all.deb to main/m/morfologik-stemming/libmorfologik-stemming-java_1.2.2-1.1_all.deb morfologik-stemming_1.2.2-1.1.diff.gz to main/m/morfologik-stemming/morfologik-stemming_1.2.2-1.1.diff.gz morfologik-stemming_1.2.2-1.1.dsc to main/m/morfologik-stemming/morfologik-stemming_1.2.2-1.1.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 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane henr...@debian.org (supplier of updated morfologik-stemming 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: Tue, 24 Jan 2012 03:25:42 +0900 Source: morfologik-stemming Binary: libmorfologik-stemming-java Architecture: source all Version: 1.2.2-1.1 Distribution: unstable Urgency: low Maintainer: Rail Aliev r...@i-rs.ru Changed-By: Hideki Yamane henr...@debian.org Description: libmorfologik-stemming-java - Finite state automaton and stemming engine library Closes: 642754 Changes: morfologik-stemming (1.2.2-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/control - set Build-Depends: default-jdk * debian/rules - use /usr/lib/jvm/default-java as JAVA_HOME (Closes: #642754) Checksums-Sha1: 878bc46775d2c0b29028da12da2159bf103ffa7f 2039 morfologik-stemming_1.2.2-1.1.dsc 08b059dd0b2aa53c4402f6dcacb9abe0c627c663 4002 morfologik-stemming_1.2.2-1.1.diff.gz 746760783bde4fa6865581a9ee5b4f3ffa3c57d4 40638 libmorfologik-stemming-java_1.2.2-1.1_all.deb Checksums-Sha256: 9dcab2013f6dbaad32a9763423a307bb7e68ebb6112d5205f1f9bc2c6c3a65d8 2039 morfologik-stemming_1.2.2-1.1.dsc 16abc5dd1dd47b727159adf69a9cd3a664e9c3a805b97d159c50c078e844a209 4002 morfologik-stemming_1.2.2-1.1.diff.gz 586a6227b4cff58c1a79d2f9bbc950d0662418263f4c6e5d7dc6413b624ece01 40638 libmorfologik-stemming-java_1.2.2-1.1_all.deb Files: c09fbb45d1103df204b648f83d515385 2039 java optional morfologik-stemming_1.2.2-1.1.dsc cab6b53c59682fe80906c3fe5ac9d360 4002 java optional morfologik-stemming_1.2.2-1.1.diff.gz 1861e7fd8a3e8057b398c3da3b0b4a4b 40638 java optional libmorfologik-stemming-java_1.2.2-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJPHabsAAoJEF0yjQgqqrFAJKMP/0xN/Bdu3OS2vdXADey86OOp UITvTWPvPBeYBlRkjiZ1BpKePf9fK4Dx3R0yjk1q4nO5sVU5ZAAX31lbsMNrHx6D ZSWDIj7VHC1kHxodgwrcSFIMrd8w6mzdw0SekXGuqrwCywY93eG87kNYOB8JeB/2 Q5N7w4bezwXuEC+/nVtF9zT11r2qhZPPKjCwiIGw02utyGWNLjZt9sCHAJHUUokK KANqsEXDMuET3FSOHpuweS7GvAD5rFWE8l5It5d+yPAOzMxXC60gF3gm34eNKdFd UYZHWAK+pQpHaZWgdvY244t5/3cCR60E6vTdyzaqtzIMLoNWVqFN+YbAx8M7SgyF
Bug#642791: marked as done (jwordsplitter: FTBFS: You must specify a valid JAVA_HOME or JAVACMD)
Your message dated Wed, 25 Jan 2012 18:48:30 + with message-id e1rq7tw-0007p8...@franck.debian.org and subject line Bug#642791: fixed in jwordsplitter 3.0-1.1 has caused the Debian Bug report #642791, regarding jwordsplitter: FTBFS: You must specify a valid JAVA_HOME or JAVACMD 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.) -- 642791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jwordsplitter Version: 3.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules clean test -x debian/rules dh_testroot You must specify a valid JAVA_HOME or JAVACMD! make: *** [testsanity] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/jwordsplitter_3.0-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: jwordsplitter Source-Version: 3.0-1.1 We believe that the bug you reported is fixed in the latest version of jwordsplitter, which is due to be installed in the Debian FTP archive: jwordsplitter_3.0-1.1.diff.gz to main/j/jwordsplitter/jwordsplitter_3.0-1.1.diff.gz jwordsplitter_3.0-1.1.dsc to main/j/jwordsplitter/jwordsplitter_3.0-1.1.dsc libjwordsplitter-java_3.0-1.1_all.deb to main/j/jwordsplitter/libjwordsplitter-java_3.0-1.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 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane henr...@debian.org (supplier of updated jwordsplitter 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: Tue, 24 Jan 2012 03:19:59 +0900 Source: jwordsplitter Binary: libjwordsplitter-java Architecture: source all Version: 3.0-1.1 Distribution: unstable Urgency: low Maintainer: Rail Aliev r...@i-rs.ru Changed-By: Hideki Yamane henr...@debian.org Description: libjwordsplitter-java - Java library for splitting words into atoms Closes: 642791 Changes: jwordsplitter (3.0-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/control - set Build-Depends: default-jdk * debian/rules - use /usr/lib/jvm/default-java as JAVA_HOME (Closes: #642791) Checksums-Sha1: 1dd450cae029fd2f69f920571d4402b178f9503b 1954 jwordsplitter_3.0-1.1.dsc 858a21165ef18ce7ec50c6efc0cf72874a931e11 1946 jwordsplitter_3.0-1.1.diff.gz bcd8f15cdd275c9e4a8ba039d29f44896557e446 12196 libjwordsplitter-java_3.0-1.1_all.deb Checksums-Sha256: 5135f6a868e4f382e02e0c8fc6214e4363d7cb45aa9697418314425a4f46d935 1954 jwordsplitter_3.0-1.1.dsc 993b283df916c1ac0326749c29bd41e6e7b1a44c4b58b183eec1e6c3f7c6965a 1946 jwordsplitter_3.0-1.1.diff.gz 8b1419342e301e5a882a9fdc40560deca453322495bfa9230e9c26b856fa88f2 12196 libjwordsplitter-java_3.0-1.1_all.deb Files: d5f3835550eb47392cb2434b07e268a9 1954 java optional jwordsplitter_3.0-1.1.dsc 47d7057a4a596f3877201b93c4e9ca3b 1946 java optional jwordsplitter_3.0-1.1.diff.gz 474df533b5ec012578ce6bec318291b8 12196 java optional libjwordsplitter-java_3.0-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJPHaW2AAoJEF0yjQgqqrFAKWgP/jpONr3OFM9ebjOXOavtwL71 3xnYmbmvB0KDLH+gxdaniUqBGywPT0Z7WEnFn9Llo9TgP6LNQeM0GqmdlwsGzhqn +NKEQNashTekHG32YqV3Hvt6Fmx8v2XLXmHeatkoYpuUGDiCCEXDKRn1dC6YSzwU Qyjw77EfYIP9UIHjvLy6EilU9PyMzL0xe1vDAN8X++4J+fSfnePKMzOlADiACoIi yCeI9BxtmBvfrrpt4e7xPuo2o5Ko9g89n7zZyyfYx93OldUKG9YnN2yeH2hl8FFr OfzdORQaUjKGTNzS8Vz4pjuxDR63orSERxd7eG6kYDrt+W2gqZX3av5KGWwr7zx1 6WbfgzgSlN1pMgrWjINuInLIW0U4ozY3Hm9gpsyQovgrh8TPDlYy1y0zHxvdSHJU atb5W3C4mrz1QsnGwb3aFrR39Ewg68N/LrBuGsO+aBSfVJY0mWquYLvGRjS37m1K e1M/5wP9xsD1kZkSUstBkOqcO7QXgHqzHlpPZ2YcT0YjBs8whQdf0kIL0gs+G5FE
Bug#642792: marked as done (segment: FTBFS: You must specify a valid JAVA_HOME or JAVACMD)
Your message dated Wed, 25 Jan 2012 18:49:24 + with message-id e1rq7uo-0007vc...@franck.debian.org and subject line Bug#642792: fixed in segment 1.3.5~svn57+dfsg-1.1 has caused the Debian Bug report #642792, regarding segment: FTBFS: You must specify a valid JAVA_HOME or JAVACMD 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.) -- 642792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: segment Version: 1.3.5~svn57+dfsg-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110923 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules clean test -x debian/rules dh_testroot You must specify a valid JAVA_HOME or JAVACMD! make: *** [testsanity] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/segment_1.3.5~svn57+dfsg-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. ---End Message--- ---BeginMessage--- Source: segment Source-Version: 1.3.5~svn57+dfsg-1.1 We believe that the bug you reported is fixed in the latest version of segment, which is due to be installed in the Debian FTP archive: libsegment-java_1.3.5~svn57+dfsg-1.1_all.deb to main/s/segment/libsegment-java_1.3.5~svn57+dfsg-1.1_all.deb segment_1.3.5~svn57+dfsg-1.1.diff.gz to main/s/segment/segment_1.3.5~svn57+dfsg-1.1.diff.gz segment_1.3.5~svn57+dfsg-1.1.dsc to main/s/segment/segment_1.3.5~svn57+dfsg-1.1.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 642...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane henr...@debian.org (supplier of updated segment 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: Tue, 24 Jan 2012 03:33:44 +0900 Source: segment Binary: libsegment-java Architecture: source all Version: 1.3.5~svn57+dfsg-1.1 Distribution: unstable Urgency: low Maintainer: Rail Aliev r...@i-rs.ru Changed-By: Hideki Yamane henr...@debian.org Description: libsegment-java - Rule based text splitting library Closes: 642792 Changes: segment (1.3.5~svn57+dfsg-1.1) unstable; urgency=low . * Non-maintainer upload. * debian/rules,control - switch to default-jdk (Closes: #642792) Checksums-Sha1: 19f17937116e4c5b6c87f719b03e4a4e4f5e99da 1989 segment_1.3.5~svn57+dfsg-1.1.dsc 852e42d7500765a5d07011cb7d441104210708fe 3467 segment_1.3.5~svn57+dfsg-1.1.diff.gz 13043e4f832b7b7cb220590afbc2576aa3f19fcf 163114 libsegment-java_1.3.5~svn57+dfsg-1.1_all.deb Checksums-Sha256: 57912c72225b23f534304909dc619d7e9769ace07e71b9baa74d2b31319b28d1 1989 segment_1.3.5~svn57+dfsg-1.1.dsc 55e908c180b50aac50c9f65b7d69dda449b55ee54dacf436b3108e7ce63fb90e 3467 segment_1.3.5~svn57+dfsg-1.1.diff.gz 2ce0882d4afb226c86048a320ede4038527d5b596baada1ac92bf2bec1137ca0 163114 libsegment-java_1.3.5~svn57+dfsg-1.1_all.deb Files: 3c346c95cec409f74f4cfaf48bf8abdd 1989 java optional segment_1.3.5~svn57+dfsg-1.1.dsc 70b4f20e05fb15c668c0d01eb7b7e461 3467 java optional segment_1.3.5~svn57+dfsg-1.1.diff.gz a0d893b6110cf087955c2441081dbeab 163114 java optional libsegment-java_1.3.5~svn57+dfsg-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJPHahpAAoJEF0yjQgqqrFA/SIP/i8PWy32lFyfSugf5FgtlmIs Xp5SvXvPGCdZS9T7UTNdvCPZHCWgEvXWmR++95ttzVQ2lKSVLXrTM9c2fATeeHc0 SCh1iQrllvkbTfE+dmLNgn53O1/p9oJWYNAlof3WgCYobzwwo5yIFhvne9Vn6wWR xxXmPNjJC1dbqCAc+FjeOsA4+BotCerfA2rZ4+kx+u1kLSzpguoYwm9WZdxS4kCO /a20j6WF+tKXwSMs0/B4Wyhc2J9idtJXvQ1c5AyLjQgD4o8WQD0aUVptCPcIB1DW 5/1GflXYi/s51iMFQkAqcDCMMOs7EJmUGVbLU6XcV0xSID0tU3aB7QB+bKM0F1l5 6bFDX+SWDYJs532n31l5YCOqBUS1pu+Aq/XNHwYz/SSqCNnI8dKvgjdgiVhBSHDT r9zsNBmwSkoBCB3L4ZecPpyy8tjpdU5aF+F5r+lseQa4nh9/ps8jj69qIsQL6ib7 t61wtJL7AB6T875Imx3WpkW49muZ6isPf1ZpAJyqsZAt3mhQniDrcb8FKYbE+QCt
Bug#657256: NMU uploaded to DELAYED/7
Dear maintainer, A non-maintainer upload has been uploaded to the Delayed queue to fix this release-critical bug, as per policy. To cancel the NMU, please ask, or upload your own revision with a higher version number. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649408: marked as done (gnome-keyring: no socket to connect to)
Your message dated Wed, 25 Jan 2012 19:17:54 + with message-id e1rq8ly-0002ki...@franck.debian.org and subject line Bug#649408: fixed in gnome-keyring 3.2.2-2 has caused the Debian Bug report #649408, regarding gnome-keyring: no socket to connect to 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.) -- 649408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-keyring Version: 3.2.2-1 Severity: normal After updating, gnome-keyring [3.0.3-2 - 3.2.2-1]. Package gnome-keyring causing errors in the work cupt. When you upgrade the archive index shows: WARNING: gnome-keyring:: no socket to connect to. example: #cupt update Get:1 http://ftp.pl.debian.org/debian sid Release Get:2 http://ftp.pl.debian.org/debian testing Release WARNING: gnome-keyring:: no socket to connect to| 0B/s | ETA: 16m38s WARNING: gnome-keyring:: no socket to connect to Get:3 http://ftp.pl.debian.org/debian testing Release.gpg WARNING: gnome-keyring:: no socket to connect to Release.gp| 10,7KiB/s | ETA: 3s Get:4 http://ftp.pl.debian.org/debian testing/main Packages.diff/Index [2038B] WARNING: gnome-keyring:: no socket to connect tomain Packag| 18,3KiB/s | ETA: 0s Get:5 http://ftp.pl.debian.org/debian sid Release.gpg WARNING: gnome-keyring:: no socket to connect to 0%][5 sid | 18,8KiB/s | ETA: 0s Get:6 http://ftp.pl.debian.org/debian sid/contrib Packages.diff/Index [2023B] WARNING: gnome-keyring:: no socket to connect to0%]| 19,0KiB/s | ETA: 0s Get:7 http://ftp.pl.debian.org/debian sid/non-free i18n/Translation-pl_PL.bz2 WARNING: gnome-keyring:: no socket to connect to0B]| 19,1KiB/s | ETA: 0s . . --- System information. --- Architecture: i386 Kernel: Linux 3.1.0-1-686-pae Debian Release: wheezy/sid 500 unstableftp.pl.debian.org 500 testing ftp.pl.debian.org --- Package information. --- Depends (Version) | Installed ===-+- dconf-gsettings-backend | 0.7.5-3 OR gsettings-backend | libc6 (= 2.4) | 2.13-21 libcap-ng0 | 0.6.6-1 libdbus-1-3 (= 1.1.1) | 1.4.16-1 libgck-1-0 (= 2.91.1) | 3.2.2-1 libgcr-3-1 (= 3.2.2) | 3.2.2-1 libgcrypt11 (= 1.4.5) | 1.5.0-3 libglib2.0-0(= 2.26.0) | 2.30.2-4 libgtk-3-0 (= 3.0.0) | 3.2.2-2 dbus-x11| 1.4.16-1 libcap2-bin | 1:2.22-1 Recommends(Version) | Installed ===-+-=== libpam-gnome-keyring| 3.2.2-1 Package's Suggests field is empty. ---End Message--- ---BeginMessage--- Source: gnome-keyring Source-Version: 3.2.2-2 We believe that the bug you reported is fixed in the latest version of gnome-keyring, which is due to be installed in the Debian FTP archive: gnome-keyring_3.2.2-2.debian.tar.gz to main/g/gnome-keyring/gnome-keyring_3.2.2-2.debian.tar.gz gnome-keyring_3.2.2-2.dsc to main/g/gnome-keyring/gnome-keyring_3.2.2-2.dsc gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/gnome-keyring_3.2.2-2_amd64.deb libgck-1-0_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-0_3.2.2-2_amd64.deb libgck-1-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-dev_3.2.2-2_amd64.deb libgck-1-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgck-1-doc_3.2.2-2_all.deb libgcr-3-1_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-1_3.2.2-2_amd64.deb libgcr-3-common_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-common_3.2.2-2_all.deb libgcr-3-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-dev_3.2.2-2_amd64.deb libgcr-3-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-doc_3.2.2-2_all.deb libpam-gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/libpam-gnome-keyring_3.2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@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-keyring package) (This message was generated automatically at their
Bug#651414: marked as done (gnome-keyring: fails to connect to socket when running updates)
Your message dated Wed, 25 Jan 2012 19:17:54 + with message-id e1rq8ly-0002ki...@franck.debian.org and subject line Bug#649408: fixed in gnome-keyring 3.2.2-2 has caused the Debian Bug report #649408, regarding gnome-keyring: fails to connect to socket when running updates 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.) -- 649408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gnome-keyring Version: 3.2.2-1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? i have had the can't connect to socket sense i installed nothing was done special. * What exactly did you do (or not do) that was effective (or ineffective)? I tried apt-get --purge remove and reinstalling to no avail * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-keyring depends on: ii dbus-x11 1.5.8-1 ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii libc62.13-21 ii libcap-ng0 0.6.6-1 ii libcap2-bin 1:2.22-1 ii libdbus-1-3 1.5.8-1 ii libgck-1-0 3.2.2-1 ii libgcr-3-1 3.2.2-1 ii libgcrypt11 1.5.0-3 ii libglib2.0-0 2.30.2-4 ii libgtk-3-0 3.2.2-3 Versions of packages gnome-keyring recommends: ii libpam-gnome-keyring 3.2.2-1 gnome-keyring suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gnome-keyring Source-Version: 3.2.2-2 We believe that the bug you reported is fixed in the latest version of gnome-keyring, which is due to be installed in the Debian FTP archive: gnome-keyring_3.2.2-2.debian.tar.gz to main/g/gnome-keyring/gnome-keyring_3.2.2-2.debian.tar.gz gnome-keyring_3.2.2-2.dsc to main/g/gnome-keyring/gnome-keyring_3.2.2-2.dsc gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/gnome-keyring_3.2.2-2_amd64.deb libgck-1-0_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-0_3.2.2-2_amd64.deb libgck-1-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-dev_3.2.2-2_amd64.deb libgck-1-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgck-1-doc_3.2.2-2_all.deb libgcr-3-1_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-1_3.2.2-2_amd64.deb libgcr-3-common_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-common_3.2.2-2_all.deb libgcr-3-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-dev_3.2.2-2_amd64.deb libgcr-3-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-doc_3.2.2-2_all.deb libpam-gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/libpam-gnome-keyring_3.2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@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-keyring 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, 25 Jan 2012 20:02:03 +0100 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring libgck-1-dev libgck-1-doc libgck-1-0 libgcr-3-dev libgcr-3-doc libgcr-3-1 libgcr-3-common Architecture: source all amd64 Version: 3.2.2-2 Distribution: unstable Urgency: low Maintainer: Josselin Mouette j...@debian.org Changed-By: Michael Biebl bi...@debian.org Description: gnome-keyring - GNOME keyring services (daemon and tools) libgck-1-0 - Glib wrapper library for PKCS#11 - runtime libgck-1-dev - GLib wrapper library for PKCS#11 - development libgck-1-doc - GLib wrapper library for PKCS#11 -
Bug#654583: marked as done (WARNING: gnome-keyring:: no socket to connect to)
Your message dated Wed, 25 Jan 2012 19:17:54 + with message-id e1rq8ly-0002ki...@franck.debian.org and subject line Bug#649408: fixed in gnome-keyring 3.2.2-2 has caused the Debian Bug report #649408, regarding WARNING: gnome-keyring:: no socket to connect to 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.) -- 649408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: rkhunter Version: 1.3.8-10 Severity: normal Hi, For some time (last months?) I get an email from the daily cron job: | Subject: Anacron job 'cron.daily' on frost.DOMAIN | [..] | /etc/cron.daily/rkhunter: | WARNING: gnome-keyring:: no socket to connect to When I execute the script from an X session I don't get this warning. This is somehow important due to the spam-like daily email from rkhunter. Thanks -- root@frost:~# sh -x /etc/cron.daily/rkhunter + RKHUNTER=/usr/bin/rkhunter + test -x /usr/bin/rkhunter + . /etc/default/rkhunter + CRON_DAILY_RUN=yes + CRON_DB_UPDATE=yes + DB_UPDATE_EMAIL=false + REPORT_EMAIL=root + APT_AUTOGEN= + NICE=0 + RUN_CHECK_ON_BATTERY=false + [ -z 0 ] + [ -z false ] + [ -x /usr/bin/on_ac_power ] + on_ac_power + [ 255 -eq 1 -a false != true ] + mktemp + OUTFILE=/tmp/tmp.C3b0R6QvdW + /usr/bin/nice -n 0 /usr/bin/rkhunter --cronjob --report-warnings-only --appendlog + [ -s /tmp/tmp.C3b0R6QvdW -a -n root ] + rm -f /tmp/tmp.C3b0R6QvdW -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rkhunter depends on: ii binutils 2.22-3 ii debconf [debconf-2.0] 1.5.41 ii file 5.09-2 ii net-tools 1.60-24.1 ii perl 5.14.2-6 ii ucf3.0025+nmu2 Versions of packages rkhunter recommends: ii curl 7.23.1-3 ii iproute 2017-1 ii lsof 4.81.dfsg.1-1 ii ssmtp [mail-transport-agent] 2.64-5 ii unhide20110113-3 ii wget 1.13.4-1 Versions of packages rkhunter suggests: pn bsd-mailx [mailx] 8.1.2-0.2006cvs-1 pn libdigest-whirlpool-perl none pn liburi-perl 1.59-1 pn libwww-perl 6.03-1 pn powermgmt-base1.31 pn tripwire none -- Configuration Files: /etc/default/rkhunter changed: CRON_DAILY_RUN=yes CRON_DB_UPDATE=yes DB_UPDATE_EMAIL=false REPORT_EMAIL=root APT_AUTOGEN= NICE=0 RUN_CHECK_ON_BATTERY=false -- debconf information: rkhunter/apt_autogen: rkhunter/cron_db_update: yes rkhunter/cron_daily_run: yes ---End Message--- ---BeginMessage--- Source: gnome-keyring Source-Version: 3.2.2-2 We believe that the bug you reported is fixed in the latest version of gnome-keyring, which is due to be installed in the Debian FTP archive: gnome-keyring_3.2.2-2.debian.tar.gz to main/g/gnome-keyring/gnome-keyring_3.2.2-2.debian.tar.gz gnome-keyring_3.2.2-2.dsc to main/g/gnome-keyring/gnome-keyring_3.2.2-2.dsc gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/gnome-keyring_3.2.2-2_amd64.deb libgck-1-0_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-0_3.2.2-2_amd64.deb libgck-1-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-dev_3.2.2-2_amd64.deb libgck-1-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgck-1-doc_3.2.2-2_all.deb libgcr-3-1_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-1_3.2.2-2_amd64.deb libgcr-3-common_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-common_3.2.2-2_all.deb libgcr-3-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-dev_3.2.2-2_amd64.deb libgcr-3-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-doc_3.2.2-2_all.deb libpam-gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/libpam-gnome-keyring_3.2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@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-keyring package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the
Bug#652104: marked as done (WARNING: gnome-keyring:: no socket to connect to breaks gnus)
Your message dated Wed, 25 Jan 2012 19:17:54 + with message-id e1rq8ly-0002ki...@franck.debian.org and subject line Bug#649408: fixed in gnome-keyring 3.2.2-2 has caused the Debian Bug report #649408, regarding WARNING: gnome-keyring:: no socket to connect to breaks gnus 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.) -- 649408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: msmtp-mta Version: 1.4.26-1 Severity: important The new message WARNING: gnome-keyring:: no socket to connect to confuses sendmail using programs (like gnus) and makes them fail to send email. Regards Christoph -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/6 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 msmtp depends on: ii debconf [debconf-2.0] 1.5.41 ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libc6 2.13-21 ii libgnutls262.12.14-3 ii libgsasl7 1.6.1-1 ii libidn11 1.23-1 ii ucf3.0025+nmu2 Versions of packages msmtp recommends: ii ca-certificates 20111025 Versions of packages msmtp suggests: ii msmtp-mta 1.4.26-1 -- debconf information: msmtp/host: msmtp/tls: false msmtp/maildomain: msmtp/sysconfig: false msmtp/auto_from: true msmtp/port: 25 ---End Message--- ---BeginMessage--- Source: gnome-keyring Source-Version: 3.2.2-2 We believe that the bug you reported is fixed in the latest version of gnome-keyring, which is due to be installed in the Debian FTP archive: gnome-keyring_3.2.2-2.debian.tar.gz to main/g/gnome-keyring/gnome-keyring_3.2.2-2.debian.tar.gz gnome-keyring_3.2.2-2.dsc to main/g/gnome-keyring/gnome-keyring_3.2.2-2.dsc gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/gnome-keyring_3.2.2-2_amd64.deb libgck-1-0_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-0_3.2.2-2_amd64.deb libgck-1-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgck-1-dev_3.2.2-2_amd64.deb libgck-1-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgck-1-doc_3.2.2-2_all.deb libgcr-3-1_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-1_3.2.2-2_amd64.deb libgcr-3-common_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-common_3.2.2-2_all.deb libgcr-3-dev_3.2.2-2_amd64.deb to main/g/gnome-keyring/libgcr-3-dev_3.2.2-2_amd64.deb libgcr-3-doc_3.2.2-2_all.deb to main/g/gnome-keyring/libgcr-3-doc_3.2.2-2_all.deb libpam-gnome-keyring_3.2.2-2_amd64.deb to main/g/gnome-keyring/libpam-gnome-keyring_3.2.2-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 649...@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-keyring 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, 25 Jan 2012 20:02:03 +0100 Source: gnome-keyring Binary: gnome-keyring libpam-gnome-keyring libgck-1-dev libgck-1-doc libgck-1-0 libgcr-3-dev libgcr-3-doc libgcr-3-1 libgcr-3-common Architecture: source all amd64 Version: 3.2.2-2 Distribution: unstable Urgency: low Maintainer: Josselin Mouette j...@debian.org Changed-By: Michael Biebl bi...@debian.org Description: gnome-keyring - GNOME keyring services (daemon and tools) libgck-1-0 - Glib wrapper library for PKCS#11 - runtime libgck-1-dev - GLib wrapper library for PKCS#11 - development libgck-1-doc - GLib wrapper library for PKCS#11 - documentation libgcr-3-1 - Library for Crypto UI related task - runtime libgcr-3-common - Library for Crypto UI related task - common files libgcr-3-dev - Library for Crypto UI related task - development libgcr-3-doc - Library for Crypto UI related task - documentation libpam-gnome-keyring - PAM module to unlock the GNOME keyring upon login Closes: 649408 Changes: gnome-keyring (3.2.2-2) unstable; urgency=low . [ Martin Pitt ] * Add
Bug#657340: src:dlr-languages: FTBFS with Mono 2.10; updated version required
Package: src:dlr-languages Version: 20090805+git.e6b28d27+dfsg-4 Severity: serious User: debian-...@lists.debian.org Usertags: mono-2.10-transition This package no longer builds, due to the Mono 2.10 transition. An updated upstream release is needed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657336: marked as done (ikiwiki-hosting-web: doesnt use invoke-rc.d)
Your message dated Wed, 25 Jan 2012 19:33:31 + with message-id e1rq8b5-0005zs...@franck.debian.org and subject line Bug#657336: fixed in ikiwiki-hosting 0.20120125 has caused the Debian Bug report #657336, regarding ikiwiki-hosting-web: doesnt use invoke-rc.d 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.) -- 657336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657336 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ikiwiki-hosting-web Version: 0.20111005 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package starts processes where it shouldnt. This is very probably due to not using invoke-rc.d as mandated by policy 9.3.3.2. This is seriously disturbing! ;-) See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well as /usr/share/doc/sysv-rc/README.policy-rc.d.gz From the attached log (scroll to the bottom...): Selecting previously unselected package ikiwiki-hosting-web. (Reading database ... 19255 files and directories currently installed.) Unpacking ikiwiki-hosting-web (from .../ikiwiki-hosting-web_0.20111005_amd64.deb) ... Setting up ikiwiki-hosting-web (0.20111005) ... invoke-rc.d: policy-rc.d denied execution of start. Enabling module suexec. To activate the new configuration, you need to run: service apache2 restart Enabling module userdir. To activate the new configuration, you need to run: service apache2 restart Restarting web server: apache2(98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed. The Apache error log may have more information. failed! dpkg: error processing ikiwiki-hosting-web (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: ikiwiki-hosting-web The installation is performed in a chroot and apache can't be started there because :80 is already in use on the host. But there is a policy-rc.d in the chroot that forbids starting any service, so this shouldn't even be attempted. cheers, Andreas ikiwiki-hosting-web_0.20111005.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: ikiwiki-hosting Source-Version: 0.20120125 We believe that the bug you reported is fixed in the latest version of ikiwiki-hosting, which is due to be installed in the Debian FTP archive: ikiwiki-hosting-common_0.20120125_all.deb to main/i/ikiwiki-hosting/ikiwiki-hosting-common_0.20120125_all.deb ikiwiki-hosting-dns_0.20120125_all.deb to main/i/ikiwiki-hosting/ikiwiki-hosting-dns_0.20120125_all.deb ikiwiki-hosting-web_0.20120125_i386.deb to main/i/ikiwiki-hosting/ikiwiki-hosting-web_0.20120125_i386.deb ikiwiki-hosting_0.20120125.dsc to main/i/ikiwiki-hosting/ikiwiki-hosting_0.20120125.dsc ikiwiki-hosting_0.20120125.tar.gz to main/i/ikiwiki-hosting/ikiwiki-hosting_0.20120125.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 657...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess jo...@debian.org (supplier of updated ikiwiki-hosting 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, 25 Jan 2012 15:00:37 -0400 Source: ikiwiki-hosting Binary: ikiwiki-hosting-common ikiwiki-hosting-web ikiwiki-hosting-dns Architecture: source all i386 Version: 0.20120125 Distribution: unstable Urgency: low Maintainer: Joey Hess jo...@debian.org Changed-By: Joey Hess jo...@debian.org Description: ikiwiki-hosting-common - ikiwiki hosting: common files ikiwiki-hosting-dns - ikiwiki hosting: dns server ikiwiki-hosting-web - ikiwiki hosting: web server Closes: 657336 Changes: ikiwiki-hosting (0.20120125) unstable; urgency=low . * Add the adduser_basedir configuration file setting, which can be used to create sites someplace other than /home. Thanks, Philip Hands. * Don't use savelog -C, it spews an ls
Bug#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures
Hi, Good patch, don't think mine is needed to be added (the same changes are already made). Don't have access to non-i386/amd64 machines, but 0011-fix_FTBFS_with_libmv.patch looks fine and if it's indeed resolves build issues i would be happy to commit it to blender's trunk. On Wed, Jan 25, 2012 at 11:40 PM, Kevin Roy kin...@gmail.com wrote: I think the patch 0011-fix_FTBFS_with_libmv [1] in git will cover configs other than i386/amd64 but in doubt, could you look at it and tell me if yours is need to be added? -- With best regards, Sergey Sharybin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646657: marked as done (ruby-builder: FTBFS: ERROR: Test ruby1.9.1 failed. Exiting)
Your message dated Wed, 25 Jan 2012 19:48:14 + with message-id e1rq8pk-0007ae...@franck.debian.org and subject line Bug#646657: fixed in ruby-builder 3.0.0-2 has caused the Debian Bug report #646657, regarding ruby-builder: FTBFS: ERROR: Test ruby1.9.1 failed. Exiting 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.) -- 646657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: ruby-builder Version: 3.0.0-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111022 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules binary dh binary --buildsystem=ruby --with ruby dh_testroot -O--buildsystem=ruby dh_prep -O--buildsystem=ruby dh_installdirs -O--buildsystem=ruby dh_auto_install -O--buildsystem=ruby Entering dh_ruby --install install -d /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby install -D -m644 lib/builder/xmlmarkup.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder/xmlmarkup.rb install -D -m644 lib/builder/xmlevents.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder/xmlevents.rb install -D -m644 lib/builder/xmlbase.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder/xmlbase.rb install -D -m644 lib/builder/xchar.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder/xchar.rb install -D -m644 lib/builder/blankslate.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder/blankslate.rb install -D -m644 lib/builder.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/builder.rb install -D -m644 lib/blankslate.rb /build/ruby-builder-EphMNt/ruby-builder-3.0.0/debian/ruby-builder/usr/lib/ruby/vendor_ruby/blankslate.rb /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb Loaded suite -e Started ... Finished in 0.010933 seconds. 99 tests, 178 assertions, 0 failures, 0 errors /usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb Run options: # Running tests: ..SS..E Finished tests in 0.017215s, 5750.7336 tests/s, 8829.4091 assertions/s. 1) Skipped: test_global_includes_still_work(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 2) Skipped: test_late_included_module_in_kernel_is_ok(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 3) Skipped: test_late_included_module_in_object_is_ok(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 4) Skipped: test_method_defined_late_multiple_times_remain_undefined(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 5) Skipped: test_methods_added_late_to_global_remain_undefined(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 6) Skipped: test_methods_added_late_to_kernel_remain_undefined(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 7) Skipped: test_methods_added_late_to_object_remain_undefined(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 8) Skipped: test_preload_method_added(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 9) Skipped: test_private_methods_are_undefined(TestBlankSlate) [/build/ruby-builder-EphMNt/ruby-builder-3.0.0/test/test_blankslate.rb:93]: BlankSlate is not used in this environment 10) Skipped:
Processed: tagging 620264
Processing commands for cont...@bugs.debian.org:
# doesnt fail in squeeze
tags 620264 + wheezy sid
Bug #620264 {Done: Andreas Rottmann ro...@debian.org}
[src:guile-gnome-platform] guile-gnome-platform: FTBFS: make[5]: ***
[gobject.doc] Error 1
Added tag(s) sid and wheezy.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
620264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620264
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#654428: blender: FTBFS: uses i386/amd64 specific register definitions on all architectures
Le 25/01/2012 20:50, Sergey Sharybin a écrit : Hi, Good patch, don't think mine is needed to be added (the same changes are already made). Don't have access to non-i386/amd64 machines, but 0011-fix_FTBFS_with_libmv.patch looks fine and if it's indeed resolves build issues i would be happy to commit it to blender's trunk. As far as I and others have tested the patch, builds are now ok on ARM and KFreeBSD. I'm not sure on others but debian buildd servers will tell us :) . -- Kevin 'Kiniou' Roy http://blog.knokorpo.fr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641542: Reducing the severity of the bug
I'm going to reduce the severity of the bug to the Wishlist. Rewriting the software is not the task of packaging. The RC-bug will probably remove Paraview from Wheezy [1], [2]. Comments are welcome. [1] http://lists.debian.org/debian-devel/2012/01/msg00653.html [2] http://release.debian.org/~nthykier/rc-buggy-leaf-pkgs-dd-list-2012-01-25 Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627300: Fwd: [mytop] can't use Config:IniFiles for my.cnf
On Thu, 2011-05-19 at 13:48 +0200, Andreas Ulm wrote: Package: mytop Version: 1.6-6 Severity: grave (snip) Hi, because of the usage of Config::IniFiles you can't use all parameters which can be set in my.cnf. If you e.g. use skip-external-locking the CPAN Config::IniFiles can't open the file because it is a mal-formed ini-file because ini-files use the format parameter = value. You can reproduce it by setting this parameter which is default in /etc/mysql/my.cnf. Then call mytop. Hello Andreas, I am unable to reproduce this bug. It seems that libconfig-inifiles-perl is able to read the my.cnf file even if some variables are not set in a parameter = value fashion: ~$ grep -vE (^#|=|\[|^$) /etc/mysql/my.cnf skip-external-locking quick quote-names !includedir /etc/mysql/conf.d/ ~$ sudo mytop -b MySQL on localhost (5.1.58-1) up 0+00:15:18 [19:14:59] Queries: 3.0 qps:0 Slow: 0.0 Se/In/Up/De(%): 00/00/00/00 Key Efficiency: 100.0% Bps in/out: 0.1/ 8.7 Id User Host/IP DB TimeCmd Query or State -- --- -- --- -- 47 root localhost0 Query show full proce 44 root localhost2 Sleep Do you still have the exact error or scenario for me to reproduce it? The package has been flagged to be removed from testing because of this pending RC bug [1]; it would be nice if we could prevent this from happening. ;) Thanks in advance. Cheers, Ignace M [1] http://lists.debian.org/debian-devel/2012/01/msg00660.html -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (99, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mytop depends on: ii libconfig-inifiles-perl 2.68-1 ii libdbd-mysql-perl4.020-1+b1 ii libdbi-perl 1.616-1+b2 ii libterm-readkey-perl 2.30-4+b2 ii perl 5.14.2-6 mytop recommends no packages. Versions of packages mytop suggests: ii perl [libtime-hires-perl] 5.14.2-6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657244: batik bundles a non free colour profile in pdf-transcoder.jar
On Wed, 25 Jan 2012 08:57:24 +0100 Vincent Fourmond fourm...@debian.org wrote: On Tue, Jan 24, 2012 at 11:54 PM, Karl Goetz k...@kgoetz.id.au wrote: From [1], it seems the pdf-transcoder.jar in batik contains a colour profile with a crazy licence. ...permission to use, copy and distribute this file for any purpose is hereby granted without fee, provided that the file is not changed including the HP copyright notice tag, ... The file will need to be removed from the jar, or the jar (and pdf support) removed from batik :/ Actually, it's more annoying than this. As far as I can tell, batik doesn't use this binary jar (and it should have been stripped from the debian source ages ago). Unfortunately, the jar comes from fop, and the incriminated file is present in fop source, which makes it unsuitable for main... Thanks for tracking down the real source of the problem! kk -- Karl Goetz, (Kamping_Kaiser / VK7FOSS) http://www.kgoetz.id.au No, I won't join your social networking group signature.asc Description: PGP signature
Bug#656762: Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random
On 24.01.2012 05:45, Norbert Preining wrote: at the same time packagekit was updated from 0.7.1-2 - 0.7.2-1 which brought eg - glib: Convert libpackagekit-glib2 from dbus-glib to GDBus I've been seeing more frequent crashes of g-s-d too in the last couple of days. The core dump I got also points into the direction of PackageKit. Could you disable the updates plugin for now (re-login, to be sure the change is picked up). For that, run (as the regular user) # gsettings set org.gnome.settings-daemon.plugins.updates active false -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#656688: usb_modeswitch fix 1.2.2-1
The fixed version of usb_modeswitch supplied by Josua Dietze : http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-1.2.2-1.tar.bz2 Fixes this issue for me as well. Up to date Sid (as at 2012-01-25) Thanks Josua! -- Alastair Sherringham http://www.sherringham.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656184: marked as done (libav: FTBFS on armel)
Your message dated Wed, 25 Jan 2012 21:18:28 + with message-id e1rqaee-0005r9...@franck.debian.org and subject line Bug#656184: fixed in libav-extra 4:0.8.0.1 has caused the Debian Bug report #656184, regarding libav: FTBFS on armel 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.) -- 656184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libav Version: 4:0.8~beta2-2 Severity: Serious On Fri, Jan 13, 2012 at 5:08 PM, fabian-gu...@users.alioth.debian.org wrote: The following commit has been merged in the master branch: commit 7415b3bd0fdb7188c7c5cc8802f92aeb7890a0d3 Author: Fabian Greffrath fabian+deb...@greffrath.com Date: Fri Jan 13 17:07:53 2012 +0100 Properly set the library paths for multiarch and shared libs in debian/*.install instead of using brace expansion and asterisks. The debian/*.install files for the shared library packages get dynamically generated at build time with the proper multipath library paths set. On archs that support optimized shared libraries, the special path to these libraries for the dynamic linker is also set. NOTE: This currently only works for *one* additional optimized shared library per arch! It seems that this patch broke compilation on armel, see this buildlog: https://buildd.debian.org/status/fetch.php?pkg=libavarch=armelver=4%3A0.8~beta2-2stamp=1326762191 Interestingly, it still works on armhf. Fabian, do you think you can fix this somehow soon. Alternatively, we can also revert that commit and re-introduce it later. What would you prefer? Cheers, Reinhard -- regards, Reinhard ---End Message--- ---BeginMessage--- Source: libav-extra Source-Version: 4:0.8.0.1 We believe that the bug you reported is fixed in the latest version of libav-extra, which is due to be installed in the Debian FTP archive: libav-extra_0.8.0.1.dsc to main/liba/libav-extra/libav-extra_0.8.0.1.dsc libav-extra_0.8.0.1.tar.gz to main/liba/libav-extra/libav-extra_0.8.0.1.tar.gz libavcodec-extra-53_0.8.0.1_amd64.deb to main/liba/libav-extra/libavcodec-extra-53_0.8.0.1_amd64.deb libavdevice-extra-53_0.8.0.1_amd64.deb to main/liba/libav-extra/libavdevice-extra-53_0.8.0.1_amd64.deb libavfilter-extra-2_0.8.0.1_amd64.deb to main/liba/libav-extra/libavfilter-extra-2_0.8.0.1_amd64.deb libavformat-extra-53_0.8.0.1_amd64.deb to main/liba/libav-extra/libavformat-extra-53_0.8.0.1_amd64.deb libavutil-extra-51_0.8.0.1_amd64.deb to main/liba/libav-extra/libavutil-extra-51_0.8.0.1_amd64.deb libpostproc-extra-52_0.8.0.1_amd64.deb to main/liba/libav-extra/libpostproc-extra-52_0.8.0.1_amd64.deb libswscale-extra-2_0.8.0.1_amd64.deb to main/liba/libav-extra/libswscale-extra-2_0.8.0.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 656...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler siret...@tauware.de (supplier of updated libav-extra package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 24 Jan 2012 08:02:29 +0100 Source: libav-extra Binary: libavutil-extra-51 libavcodec-extra-53 libavdevice-extra-53 libavfilter-extra-2 libpostproc-extra-52 libavformat-extra-53 libswscale-extra-2 Architecture: source amd64 Version: 4:0.8.0.1 Distribution: unstable Urgency: medium Maintainer: Reinhard Tartler siret...@debian.org Changed-By: Reinhard Tartler siret...@tauware.de Description: libavcodec-extra-53 - Libav codec library libavdevice-extra-53 - Libav device handling library libavfilter-extra-2 - Libav filter library libavformat-extra-53 - Libav video postprocessing library libavutil-extra-51 - Libav utility library libpostproc-extra-52 - Libav video postprocessing library libswscale-extra-2 - Libav video software scaling library Closes: 656184 657326 Changes: libav-extra (4:0.8.0.1) unstable; urgency=medium . [ Fabian Greffrath ] * Properly set the library paths for multiarch and shared libs in debian/*.install instead of using brace expansion and asterisks. * Fix debian/*.install file generation on archs (e.g. armel) that build more than only one optimized shared library (Closes: #656184).
Bug#657261: marked as done (src:gmime2.4: Rebuild for Mono transition)
Your message dated Wed, 25 Jan 2012 21:48:02 + with message-id e1rqahg-0002yo...@franck.debian.org and subject line Bug#657261: fixed in gmime2.4 2.4.31-1 has caused the Debian Bug report #657261, regarding src:gmime2.4: Rebuild for Mono transition 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.) -- 657261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:gmime2.4 Version: 2.4.25-1 Severity: serious User: debian-...@lists.debian.org Usertags: mono-2.10-transition Hi, A Mono transition is underway. Every source package needs to be rebuilt to compile against CLR 4.0 instead of CLR 2.0. Please upload gmime2.4 for this change. You can check it worked if, after rebuilding, libgmime2.4-cil has a dependency on libmono-corlib4.0-cil instead of …corlib2.0-cil. http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775 Cheers, ---End Message--- ---BeginMessage--- Source: gmime2.4 Source-Version: 2.4.31-1 We believe that the bug you reported is fixed in the latest version of gmime2.4, which is due to be installed in the Debian FTP archive: gmime2.4_2.4.31-1.diff.gz to main/g/gmime2.4/gmime2.4_2.4.31-1.diff.gz gmime2.4_2.4.31-1.dsc to main/g/gmime2.4/gmime2.4_2.4.31-1.dsc gmime2.4_2.4.31.orig.tar.gz to main/g/gmime2.4/gmime2.4_2.4.31.orig.tar.gz libgmime-2.4-2_2.4.31-1_amd64.deb to main/g/gmime2.4/libgmime-2.4-2_2.4.31-1_amd64.deb libgmime-2.4-dev_2.4.31-1_amd64.deb to main/g/gmime2.4/libgmime-2.4-dev_2.4.31-1_amd64.deb libgmime-2.4-doc_2.4.31-1_all.deb to main/g/gmime2.4/libgmime-2.4-doc_2.4.31-1_all.deb libgmime2.4-cil-dev_2.4.31-1_all.deb to main/g/gmime2.4/libgmime2.4-cil-dev_2.4.31-1_all.deb libgmime2.4-cil_2.4.31-1_all.deb to main/g/gmime2.4/libgmime2.4-cil_2.4.31-1_all.deb monodoc-gmime2.4-manual_2.4.31-1_all.deb to main/g/gmime2.4/monodoc-gmime2.4-manual_2.4.31-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 657...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mirco Bauer mee...@debian.org (supplier of updated gmime2.4 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: Wed, 25 Jan 2012 21:31:17 +0100 Source: gmime2.4 Binary: libgmime-2.4-dev libgmime-2.4-doc libgmime-2.4-2 libgmime2.4-cil libgmime2.4-cil-dev monodoc-gmime2.4-manual Architecture: source amd64 all Version: 2.4.31-1 Distribution: unstable Urgency: low Maintainer: Mirco Bauer mee...@debian.org Changed-By: Mirco Bauer mee...@debian.org Description: libgmime-2.4-2 - MIME message parser and creator library - runtime libgmime-2.4-dev - MIME message parser and creator library - development files libgmime-2.4-doc - MIME message parser and creator library - documentation libgmime2.4-cil - CLI binding for the GMime library libgmime2.4-cil-dev - CLI binding for the GMime library monodoc-gmime2.4-manual - compiled XML documentation for GMime Closes: 657261 Changes: gmime2.4 (2.4.31-1) unstable; urgency=low . * New upstream (bugfix) release + No new API interfaces + Build against Mono 2.10 (closes: #657261) * Ship symbols file for libgmime-2.4-2 starting with 2.4.6 * Lowered shlibs to = 2.6.7 as that was the last version with added symbols Checksums-Sha1: fdd1eeb7c54c347a0425f64cd940cad6927fdc80 2016 gmime2.4_2.4.31-1.dsc 073d9d151280b39374d1593c7954be4ea6ea0a21 1044528 gmime2.4_2.4.31.orig.tar.gz fbb2b68f62ffca19d7902a9e522e3041a4c202e0 8073 gmime2.4_2.4.31-1.diff.gz 12b02ce24bd4a113c31c421a6e24b18b5bda248d 303022 libgmime-2.4-dev_2.4.31-1_amd64.deb b0a7456ae5a505a0013985e2805c9967c7c9fffa 211392 libgmime-2.4-doc_2.4.31-1_all.deb ebc4a7f3b51a9a087529ec6446298ed05e019160 237532 libgmime-2.4-2_2.4.31-1_amd64.deb 9364871abcb22f34304c2aab10321f099f8f6216 113316 libgmime2.4-cil_2.4.31-1_all.deb 81ea02c5568e94b440873f745edfba1afbfaa553 77918 libgmime2.4-cil-dev_2.4.31-1_all.deb 3026a05fe76ad46a89122a7d636f99c6874ad056 146194 monodoc-gmime2.4-manual_2.4.31-1_all.deb Checksums-Sha256: 42a498c040bce9671bb8fef5a970042950d1a5cc660bba9efea1f83ff939d1bd 2016 gmime2.4_2.4.31-1.dsc
Processed: tagging 653884
Processing commands for cont...@bugs.debian.org: tags 653884 - fixed Bug #653884 [xul-ext-useragentswitcher] xul-ext-useragentswitcher: incompatible with iceweasel 4.1 and later Removed tag(s) fixed. thanks Stopping processing here. Please contact me if you need assistance. -- 653884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653884 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#656688: usb_modeswitch throws general protection errors to syslog
Am 24.01.2012 21:21, schrieb Kein Kommentar: this version works for me. Thank you. usb-modeswitch-1.2.2-1.tar.bz2 Thanks for the confirmation, everyone. I will do an upstream bugfix release which Odyx can just package as usual. Josua Dietze -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657276: pcf2bdf crashes on unifont.pcf.gz
clone 657276 -1 retitle -1 pcf2bdf crashes on unifont.pcf.gz severity -1 normal reassign -1 pcf2bdf found -1 1.04-2 clone -1 -2 retitle -2 pcf2bdf should have distinct exit status for corrupted font severity -2 wishlist clone 657276 -3 retitle -3 update-xfonts-traditional should ignore all corrupted pcfs severity -3 wishlist block -3 by -2 retitle 657276 xfonts-traditional trigger dies if pcf2bdf crashes on any font thanks This report reveals (at least) three things wrong which will require four changes to be made to the various bits of software: 1. pcf2bdf crashes on unifont.pcf.gz. To reproduce: - Install pcf2bdf 1.04-2 - Install xfonts-unifont 1:5.1.20080914-1 - Run zcat zcat /usr/share/fonts/X11/misc/unifont.pcf.gz | pcf2bdf t - Observe the output: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted - Note that the output file is empty. The Aborted line is the shell reporting SIGABRT If the font is in fact corrupted somehow then of course it is OK for pcf2bdf to fail, but it should not crash. This is the new bug -1 pcf2bdf crashes on unifont.pcf.gz 2. update-xfonts-traditional cannot cope with the existence of any font for which pcf2bdf crashes. It needs to have a special case for this pending a fix to (1). #657276 will be this bug. 3. It would be very good if update-xfonts-traditional could ignore corrupted pcfs. But it should not ignore other errors (such as disk io problems, programs dying due to lack of memory or disk space, etc.) Currently xfonts-traditional cannot do this because pcf2bdf does not have a distinct exit status for corrupted fonts. I would therefore like to request that bdf2pcf be modified to produce a distinct exit status for corrupted or invalid pcfs. I suggest the value 2 should be used for this, since 1 has already been used by older versions of pcf2bdf to mean any kind of failure and thus cannot safely be ignored by callers. This change request to pcf2bdf is the new bug -2 pcf2bdf should have distinct exit status for corrupted font. When this is done, or at least an interface defined, update-xfonts-traditional needs to be changed to handle that exit status appropriately. This is the new bug -3 update-xfonts-traditional should ignore all corrupted pcfs Additionally, it would be nice of xfonts-traditional had rewriting rules for xfonts-unifont. However, I don't propose to keep wishlist items of the form xfonts-traditional should have rewriting rules for font X in the BTS. And of course this depends on pcf2bdf being fixed not to crash on this font and also on someone doing the necessary glyph investigation (or perhaps editing). Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654456: marked as done (gdebi-kde isn't working (possibly passing a wrong command).)
Your message dated Wed, 25 Jan 2012 23:02:13 + with message-id e1rqbr3-000353...@franck.debian.org and subject line Bug#654456: fixed in gdebi 0.8.4 has caused the Debian Bug report #654456, regarding gdebi-kde isn't working (possibly passing a wrong command). 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.) -- 654456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gdebi-kde Version: 0.8.3 Severity: grave Justification: renders package unusable Dear Maintainer, gdebi-kde simply can't install anything probably because it passes a wrong command. For example the picture at http://en.zimagez.com/zimage/snapshot517.php shows the command [kdesu] '/usr/bin/gdebi-kde -n ' /home/pessoa/Downloads/meta-backup-2.1-cli.deb and that doesn't work. It pops the error window http://en.zimagez.com/zimage/snapshot614.php If I run the command from the run window (Alt+F2) /usr/bin/gdebi-kde -n /home/pessoa/Downloads/meta-backup-2.1-cli.deb then it works. So those single quotes ' are probably out of place. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.1.0-1-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdebi-kde depends on: ii gdebi-core 0.8.3 ii kde-runtime 4:4.7.4-1 ii kdesudo 3.4.2.4-1 ii python 2.7.2-9 ii python-kde4 4:4.7.4-1 Versions of packages gdebi-kde recommends: ii shared-mime-info 0.90-1 gdebi-kde suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: gdebi Source-Version: 0.8.4 We believe that the bug you reported is fixed in the latest version of gdebi, which is due to be installed in the Debian FTP archive: gdebi-core_0.8.4_all.deb to main/g/gdebi/gdebi-core_0.8.4_all.deb gdebi-kde_0.8.4_all.deb to main/g/gdebi/gdebi-kde_0.8.4_all.deb gdebi_0.8.4.dsc to main/g/gdebi/gdebi_0.8.4.dsc gdebi_0.8.4.tar.gz to main/g/gdebi/gdebi_0.8.4.tar.gz gdebi_0.8.4_all.deb to main/g/gdebi/gdebi_0.8.4_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 654...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Falavigna dktrkr...@debian.org (supplier of updated gdebi 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, 25 Jan 2012 23:37:55 +0100 Source: gdebi Binary: gdebi-core gdebi gdebi-kde Architecture: source all Version: 0.8.4 Distribution: unstable Urgency: low Maintainer: Ubuntu Developers ubuntu-dev-t...@lists.alioth.debian.org Changed-By: Luca Falavigna dktrkr...@debian.org Description: gdebi - simple tool to install deb files - GNOME GUI gdebi-core - simple tool to install deb files gdebi-kde - simple tool to install deb files - KDE GUI Closes: 654456 Changes: gdebi (0.8.4) unstable; urgency=low . * GDebi/GDebiKDE.py: - Fix execl invocation (Closes: #654456). * debian/control: - Add kdebase-runtime as optional dependency for gdebi-kde. Checksums-Sha1: 7ffc6fc49480809d08863cfb4a052e714ea0d894 1664 gdebi_0.8.4.dsc 90515ed717cd5b520db56a66b893934b38300753 222197 gdebi_0.8.4.tar.gz b7275ee98d1ff5357dbbc74dab30be90a775f25f 175152 gdebi-core_0.8.4_all.deb 3a42a02dd6e33aa174b0112156c6ccc0c698fee9 40318 gdebi_0.8.4_all.deb 37791badc602fb1be0e1b20a432a0a3e37182dd5 29062 gdebi-kde_0.8.4_all.deb Checksums-Sha256: 6700b6d7e216a58fabee17a4cffe5025f66ff41af5b23b71bcb115b13672024b 1664 gdebi_0.8.4.dsc 9fc09cd1d893c5df81b7d2af12b01466f4310118af671fed0fd76a919e255399 222197 gdebi_0.8.4.tar.gz 54f4a270a440fd36ae254f9e743c3b2c8296a1f9628a42390213074be6e3a532 175152 gdebi-core_0.8.4_all.deb 16245ebd4fb5d4f9561ee5cdba372256ace4628927dc134f36ced35c5600917d 40318 gdebi_0.8.4_all.deb ce0afd39b8da010cdfdc113bf409729ca4668ddd33ecc9a1f86c4e3b801f2bf8 29062 gdebi-kde_0.8.4_all.deb Files: 934fa3a4509baef350c198442d934be7 1664 admin optional gdebi_0.8.4.dsc d7338369e473c0d418a2c29ddfe9bd82 222197 admin optional gdebi_0.8.4.tar.gz 5b7fe5e43770c45fcc1a363fe56d 175152 admin optional
Processed (with 4 errors): pcf2bdf crashes on unifont.pcf.gz
Processing commands for cont...@bugs.debian.org:
clone 657276 -1
Bug#657276: xfonts-traditional: can't cope with xfonts-unifont
Bug 657276 cloned as bug 657396.
retitle -1 pcf2bdf crashes on unifont.pcf.gz
Bug #657396 [xfonts-traditional] xfonts-traditional: can't cope with
xfonts-unifont
Changed Bug title to 'pcf2bdf crashes on unifont.pcf.gz' from
'xfonts-traditional: can't cope with xfonts-unifont'
severity -1 normal
Bug #657396 [xfonts-traditional] pcf2bdf crashes on unifont.pcf.gz
Severity set to 'normal' from 'serious'
reassign -1 pcf2bdf
Bug #657396 [xfonts-traditional] pcf2bdf crashes on unifont.pcf.gz
Bug reassigned from package 'xfonts-traditional' to 'pcf2bdf'.
Bug No longer marked as found in versions xfonts-traditional/1.2.
found -1 1.04-2
Bug #657396 [pcf2bdf] pcf2bdf crashes on unifont.pcf.gz
Bug Marked as found in versions pcf2bdf/1.04-2.
clone -1 -2
Unknown command or malformed arguments to command.
retitle -2 pcf2bdf should have distinct exit status for corrupted font
Failed to set the title of -2: The 'bug' parameter (-2) to
Debbugs::Control::set_title did not pass regex check
Debbugs::Control::set_title('transcript', 'IO::Scalar=GLOB(0x182a4d0)',
'requester', 'Ian Jackson ijack...@chiark.greenend.org.uk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'20256.35262.86238.69...@chiark.greenend.org.uk', 'request_subject', ...)
called at /usr/lib/debbugs/service line 879
eval {...} called at /usr/lib/debbugs/service line 878
severity -2 wishlist
Failed to set severity of Bug -2 to wishlist: The 'bug' parameter (-2) to
Debbugs::Control::set_severity did not pass regex check
Debbugs::Control::set_severity('transcript',
'IO::Scalar=GLOB(0x182a4d0)', 'requester', 'Ian Jackson
ijack...@chiark.greenend.org.uk', 'request_addr', 'cont...@bugs.debian.org',
'request_msgid', '20256.35262.86238.69...@chiark.greenend.org.uk',
'request_subject', ...) called at /usr/lib/debbugs/service line 778
eval {...} called at /usr/lib/debbugs/service line 777
clone 657276 -3
Bug#657276: xfonts-traditional: can't cope with xfonts-unifont
Bug 657276 cloned as bug 657397.
retitle -3 update-xfonts-traditional should ignore all corrupted pcfs
Bug #657397 [xfonts-traditional] xfonts-traditional: can't cope with
xfonts-unifont
Changed Bug title to 'update-xfonts-traditional should ignore all corrupted
pcfs' from 'xfonts-traditional: can't cope with xfonts-unifont'
severity -3 wishlist
Bug #657397 [xfonts-traditional] update-xfonts-traditional should ignore all
corrupted pcfs
Severity set to 'wishlist' from 'serious'
block -3 by -2
Failed to set blocking bugs of 657397: Invalid blocking bug(s):-2
retitle 657276 xfonts-traditional trigger dies if pcf2bdf crashes on any font
Bug #657276 [xfonts-traditional] xfonts-traditional: can't cope with
xfonts-unifont
Changed Bug title to 'xfonts-traditional trigger dies if pcf2bdf crashes on any
font' from 'xfonts-traditional: can't cope with xfonts-unifont'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
657276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657276
657396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657396
657397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657397
-2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-2
-3: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-3
-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1
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: do this again without nested clone
Processing commands for cont...@bugs.debian.org: clone 657396 -2 Bug#657396: pcf2bdf crashes on unifont.pcf.gz Bug 657396 cloned as bug 657398. retitle -2 pcf2bdf should have distinct exit status for corrupted font Bug #657398 [pcf2bdf] pcf2bdf crashes on unifont.pcf.gz Changed Bug title to 'pcf2bdf should have distinct exit status for corrupted font' from 'pcf2bdf crashes on unifont.pcf.gz' severity -2 wishlist Bug #657398 [pcf2bdf] pcf2bdf should have distinct exit status for corrupted font Severity set to 'wishlist' from 'normal' block 657397 by -2 Bug #657397 [xfonts-traditional] update-xfonts-traditional should ignore all corrupted pcfs Was not blocked by any bugs. Added blocking bug(s) of 657397: 657398 retitle 657276 xfonts-traditional trigger dies if pcf2bdf crashes on any font Bug #657276 [xfonts-traditional] xfonts-traditional trigger dies if pcf2bdf crashes on any font Ignoring request to change the title of bug#657276 to the same title thanks Stopping processing here. Please contact me if you need assistance. -- 657276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657276 657398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657398 657396: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657396 657397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657397 -2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-2 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#657276: marked as done (xfonts-traditional trigger dies if pcf2bdf crashes on any font)
Your message dated Wed, 25 Jan 2012 23:51:00 + with message-id 20256.38244.954355.296...@chiark.greenend.org.uk and subject line xfonts-traditional 1.3 fixed #657276 not #657397 has caused the Debian Bug report #657276, regarding xfonts-traditional trigger dies if pcf2bdf crashes on any font 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.) -- 657276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xfonts-traditional Version: 1.2 Severity: normal xfonts-traditional blows up when trying to process unifont.pcf.gz from xfonts-unifont: processing /usr/share/fonts/X11/misc... terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc BDF Error on line 0: bad 'STARTFONT' bdftopcf: bdf input, stdin, corrupt gunzip [20054] 0 13 at /usr/bin/update-xfonts-traditional line 228. dpkg: error processing xfonts-traditional (--unpack): subprocess installed post-installation script returned error exit status 255 Could you please take a look? Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfonts-traditional depends on: ii debconf [debconf-2.0] 1.5.41 ii pcf2bdf1.04-2 ii perl 5.14.2-6 ii xfonts-utils 1:7.6+1 xfonts-traditional recommends no packages. xfonts-traditional suggests no packages. -- debconf information excluded ---End Message--- ---BeginMessage--- reopen 657397 thanks The upload of 1.3 had the wrong bug# in the changelog. I have fixed this in my git repo so future changelogs will be right but we also need to sort out the BTS. Sorry! Ian. ---End Message---
Bug#652417: Does this issue need a CVE #?
Does this issue need a CVE #? -- -- Kurt Seifried / Red Hat Security Response Team kseifr...@redhat.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: do proper fixed mark
Processing commands for cont...@bugs.debian.org:
fixed 657276 xfonts-traditional/1.3
Bug #657276 {Done: Ian Jackson ijack...@chiark.greenend.org.uk}
[xfonts-traditional] xfonts-traditional trigger dies if pcf2bdf crashes on any
font
Bug Marked as fixed in versions xfonts-traditional/1.3.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
657276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657276
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: bug 655930 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=668698
Processing commands for cont...@bugs.debian.org: forwarded 655930 https://bugzilla.gnome.org/show_bug.cgi?id=668698 Bug #655930 [gnome-mousetrap] gnome-mousetrap: broken by python-opencv 2.3 Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=668698'. thanks Stopping processing here. Please contact me if you need assistance. -- 655930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655930 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#655930: gnome-mousetrap: broken by python-opencv 2.3
Marcos Marado, le Wed 25 Jan 2012 16:52:32 +, a écrit : You wrote: gnome-mousetrap is completely broken by the new opencv API. I have tried to patch, but came to a difficult issue, I have forwarded the issue upstream, without answer for now. I've been looking on the bug list[1] but I can't find anything similar to what you complain, I had forwarded on mousetrap-l...@gnome.org, not as a bugreport. Subject: mousetrap and python-opencv 2.3 Date: Tue, 20 Dec 2011 21:40:23 +0100 can you please tell what the bug number you're referring to? [1] https://bugzilla.gnome.org/buglist.cgi?product=mousetrapbug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENED I have now opened https://bugzilla.gnome.org/show_bug.cgi?id=668698 Samuel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657404: sg3-utils: FTBFS on hurd-i386
Package: sg3-utils Version: 1.31-1 Severity: serious Justification: fails to build from source sg3-utils fails to build from source on hurd-i386[1] due to missing files in /usr/bin/. [1] https://buildd.debian.org/status/fetch.php?pkg=sg3-utilsarch=hurd-i386ver=1.32-1stamp=1312890554 -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric'), (400, 'oneiric-proposed'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-hyper2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_SG.utf8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sg3-utils depends on: ii libc6 2.13-20ubuntu5 Embedded GNU C Library: Shared lib ii libsgutils2-2 1.31-1 utilities for devices using the SC sg3-utils recommends no packages. sg3-utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656762: Bug#656564: libglib2.0-0: since upgrade to 2.30.2-5 programs start segfaulting at random
On Mi, 25 Jan 2012, Michael Biebl wrote:
I've been seeing more frequent crashes of g-s-d too in the last couple
Ahh, at least it is getting reproducible ;-)
of days. The core dump I got also points into the direction of
PackageKit. Could you disable the updates plugin for now (re-login, to
be sure the change is picked up).
For that, run (as the regular user)
# gsettings set org.gnome.settings-daemon.plugins.updates active false
I have done this now and will see what happens.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
CORFE (n.)
An object which is almost totally indistinguishable from a newspaper,
the one crucial difference being tat it belongs to somebody else and
is unaccountably much more interesting that your own - which may
otherwise appear to be in all respects identical. Though it is a rule
of life that a train or other public place may contain any number of
corfes but only one newspaper, it is quite possible to transform your
own perfectly ordinary newspaper into a corfe by the simple expedient
of letting somebody else read it.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656600: [broadcom-sta-source] doesn't compile on latest kernel
Package: broadcom-sta-source Version: 5.100.82.112-4 Followup-For: Bug #656600 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? when I try to compile the broadcom module in Debian Sid: # cat /proc/version Linux version 3.2.0-1-amd64 (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 09:46:46 UTC 2012 after upgrade to the kernel 3.2. I followed the debina wiki and using m-a a-i broadcom-sta, I have the following error: # cat /var/cache/modass/broadcom-sta-source*buildlog*(part of the output of cat) # Build the module cd /usr/src/modules/broadcom-sta \ make -C /lib/modules/3.2.0-1-amd64/build M=/usr/src/modules/broadcom- sta make[2]: se ingresa al directorio `/usr/src/linux-headers-3.2.0-1-amd64' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API Kernel architecture is X86_64 CC [M] /usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.o /usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.c:390:2: error: unknown field ândo_set_multicast_listâ specified in initializer /usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.c:390:2: warning: initialization from incompatible pointer type [enabled by default] /usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.c:390:2: warning: (near initialization for âwl_netdev_ops.ndo_validate_addrâ) [enabled by default] make[5]: *** [/usr/src/modules/broadcom-sta/src/wl/sys/wl_linux.o] Error 1 make[4]: *** [_module_/usr/src/modules/broadcom-sta] Error 2 make[3]: *** [sub-make] Error 2 make[2]: *** [all] Error 2 make[2]: se sale del directorio `/usr/src/linux-headers-3.2.0-1-amd64' make[1]: *** [binary-modules] Error 2 make[1]: se sale del directorio `/usr/src/modules/broadcom-sta' make: *** [kdist_build] Error 2 * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_CL.utf8, LC_CTYPE=es_CL.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-source depends on: ii bzip2 1.0.6-1 ii debhelper 9.20120115 ii make 3.81-8.1 ii quilt 0.50-2 Versions of packages broadcom-sta-source recommends: ii module-assistant 0.11.4 Versions of packages broadcom-sta-source suggests: ii wireless-tools 30~pre9-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638379: marked as done (xine-ui: fatal error: curl/types.h: No such file or directory)
Your message dated Thu, 26 Jan 2012 01:33:14 + with message-id e1rqedc-0003ur...@franck.debian.org and subject line Bug#638379: fixed in xine-ui 0.99.7~hg20120125-1 has caused the Debian Bug report #638379, regarding xine-ui: fatal error: curl/types.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.) -- 638379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xine-ui Version: 0.99.6-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, xine-ui currently FTBFS on sid, as it tries to include curl/types.h which has been removed (see bug#636457): | mv -f .deps/control.Tpo .deps/control.Po | gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -I../../src -I../../src -I../../src/common -I../../src/common -I../../src/xitk/xine-toolkit -I../../src/xitk/xine-toolkit -I/usr/include-I/usr/include/readline -I../../src/xitk/xine-toolkit -Wall -D_FILE_OFFSET_BITS=64 -Wpointer-arith -Wnested-externs -Wcast-align -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -g -O2 -DNDEBUG -Wformat=2 -Wno-format-zero-length -Wmissing-format-attribute -Wstrict-aliasing=2 -MT download.o -MD -MP -MF .deps/download.Tpo -c -o download.o download.c | download.c:31:24: fatal error: curl/types.h: No such file or directory | compilation terminated. | make[5]: *** [download.o] Error 1 | make[5]: Leaving directory `/build/buildd-xine-ui_0.99.6-1-s390x-vRMVeW/xine-ui-0.99.6/src/xitk' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/build/buildd-xine-ui_0.99.6-1-s390x-vRMVeW/xine-ui-0.99.6/src/xitk' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/build/buildd-xine-ui_0.99.6-1-s390x-vRMVeW/xine-ui-0.99.6/src' | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory `/build/buildd-xine-ui_0.99.6-1-s390x-vRMVeW/xine-ui-0.99.6' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/build/buildd-xine-ui_0.99.6-1-s390x-vRMVeW/xine-ui-0.99.6' | make: *** [build-stamp] Error 2 Full build log (s390x, but also affects other architectures) at: http://buildd.debian-ports.org/status/fetch.php?pkg=xine-uiarch=s390xver=0.99.6-1stamp=1313611241 Regards, Aurelien -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (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/bash ---End Message--- ---BeginMessage--- Source: xine-ui Source-Version: 0.99.7~hg20120125-1 We believe that the bug you reported is fixed in the latest version of xine-ui, which is due to be installed in the Debian FTP archive: xine-console_0.99.7~hg20120125-1_amd64.deb to main/x/xine-ui/xine-console_0.99.7~hg20120125-1_amd64.deb xine-dbg_0.99.7~hg20120125-1_amd64.deb to main/x/xine-ui/xine-dbg_0.99.7~hg20120125-1_amd64.deb xine-ui_0.99.7~hg20120125-1.debian.tar.gz to main/x/xine-ui/xine-ui_0.99.7~hg20120125-1.debian.tar.gz xine-ui_0.99.7~hg20120125-1.dsc to main/x/xine-ui/xine-ui_0.99.7~hg20120125-1.dsc xine-ui_0.99.7~hg20120125-1_amd64.deb to main/x/xine-ui/xine-ui_0.99.7~hg20120125-1_amd64.deb xine-ui_0.99.7~hg20120125.orig.tar.xz to main/x/xine-ui/xine-ui_0.99.7~hg20120125.orig.tar.xz 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 638...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. li...@youmustbejoking.demon.co.uk (supplier of updated xine-ui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 26 Jan 2012 00:23:24 + Source: xine-ui Binary: xine-ui xine-console xine-dbg Architecture: source amd64 Version: 0.99.7~hg20120125-1 Distribution: unstable Urgency: low Maintainer: Darren Salt li...@youmustbejoking.demon.co.uk Changed-By: li...@youmustbejoking.demon.co.uk Description: xine-console - the xine video player, user interface xine-dbg - the xine video player, debug symbols xine-ui- the xine video player, user interface Closes: 600534 634334 638379 Changes: xine-ui (0.99.7~hg20120125-1) unstable; urgency=low .
Bug#651717: pulseaudio-utils - Unversioned lib in public directory
found 651717 0.9.10-3+lenny2 found 651717 0.9.21-3+squeeze1 found 651717 1.0-4 thanks Looks like this bug affects oldstable, stable and testing as well as unstable :/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: re: pulseaudio-utils - Unversioned lib in public directory
Processing commands for cont...@bugs.debian.org: found 651717 0.9.10-3+lenny2 Bug #651717 [pulseaudio-utils] pulseaudio-utils - Unversioned lib in public directory Bug Marked as found in versions pulseaudio/0.9.10-3+lenny2. found 651717 0.9.21-3+squeeze1 Bug #651717 [pulseaudio-utils] pulseaudio-utils - Unversioned lib in public directory Bug Marked as found in versions pulseaudio/0.9.21-3+squeeze1. found 651717 1.0-4 Bug #651717 [pulseaudio-utils] pulseaudio-utils - Unversioned lib in public directory Bug Marked as found in versions pulseaudio/1.0-4. thanks Stopping processing here. Please contact me if you need assistance. -- 651717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651717 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#634403: marked as done (bzr-hg: FTBFS: *** Bazaar has encountered an internal error.)
Your message dated Thu, 26 Jan 2012 02:47:50 + with message-id e1rqfno-p7...@franck.debian.org and subject line Bug#634403: fixed in bzr-hg 0.2.0~bzr544-1 has caused the Debian Bug report #634403, regarding bzr-hg: FTBFS: *** Bazaar has encountered an internal error. 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.) -- 634403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bzr-hg Version: 0.2.0~bzr409-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 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/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409' BZR_CONCURRENCY=10 BZR_PLUGINS_AT=hg@/build/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409 /usr/bin/bzr selftest --parallel=fork \ -v -s bp.hg bzr: ERROR: exceptions.AttributeError: 'module' object has no attribute '_LockWarner' Traceback (most recent call last): File /usr/lib/python2.6/dist-packages/bzrlib/commands.py, line 946, in exception_to_return_code return the_callable(*args, **kwargs) File /usr/lib/python2.6/dist-packages/bzrlib/commands.py, line 1150, in run_bzr ret = run(*run_argv) File /usr/lib/python2.6/dist-packages/bzrlib/commands.py, line 699, in run_argv_aliases return self.run(**all_cmd_args) File /usr/lib/python2.6/dist-packages/bzrlib/commands.py, line 721, in run return self._operation.run_simple(*args, **kwargs) File /usr/lib/python2.6/dist-packages/bzrlib/cleanup.py, line 135, in run_simple self.cleanups, self.func, *args, **kwargs) File /usr/lib/python2.6/dist-packages/bzrlib/cleanup.py, line 165, in _do_with_cleanups result = func(*args, **kwargs) File /usr/lib/python2.6/dist-packages/bzrlib/builtins.py, line 3810, in run result = tests.selftest(**selftest_kwargs) File /usr/lib/python2.6/dist-packages/bzrlib/tests/__init__.py, line 3627, in selftest suite = test_suite(keep_only, starting_with) File /usr/lib/python2.6/dist-packages/bzrlib/tests/__init__.py, line 4112, in test_suite plugin_suite = plugin.test_suite() File /usr/lib/python2.6/dist-packages/bzrlib/plugin.py, line 562, in test_suite return self.module.test_suite() File /build/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409/__init__.py, line 250, in test_suite suite.addTest(tests.test_suite()) File /build/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409/tests/__init__.py, line 36, in test_suite suite.addTest(loader.loadTestsFromModuleNames([%s.%s % (__name__, i) for i in testmod_names])) File /usr/lib/python2.6/dist-packages/bzrlib/tests/TestUtil.py, line 109, in loadTestsFromModuleNames result.addTests(self.loadTestsFromModuleName(name)) File /usr/lib/python2.6/dist-packages/bzrlib/tests/TestUtil.py, line 114, in loadTestsFromModuleName module = pyutils.get_named_object(name) File /usr/lib/python2.6/dist-packages/bzrlib/pyutils.py, line 57, in get_named_object __import__(module_name, globals(), locals(), []) File /build/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409/tests/test_branch.py, line 21, in module from bzrlib.plugins.hg.dir import ( File /build/bzr-hg-Ca8Mfv/bzr-hg-0.2.0~bzr409/dir.py, line 192, in module LockWarner = bzrlib.lockable_files._LockWarner AttributeError: 'module' object has no attribute '_LockWarner' bzr 2.4b5 on python 2.6.7 (Linux-2.6.32-5-amd64-x86_64-with-debian-wheezy-sid) arguments: ['/usr/bin/bzr', 'selftest', '--parallel=fork', '-v', '-s', 'bp.hg'] plugins: bash_completion[2.4b5], changelog_merge[2.4b5], hg[0.2.0dev], launchpad[2.4b5], netrc_credential_store[2.4b5], news_merge[2.4b5], weave_fmt[2.4b5] encoding: 'ANSI_X3.4-1968', fsenc: 'ANSI_X3.4-1968', lang: None *** Bazaar has encountered an internal error. This probably indicates a bug in Bazaar. You can help us fix it by filing a bug report at https://bugs.launchpad.net/bzr/+filebug including this traceback and a description of the problem. make[1]: *** [override_dh_auto_test] Error 4 The full build log is available from: http://people.debian.org/~lucas/logs/2011/07/18/bzr-hg_0.2.0~bzr409-1.1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a
Bug#657408: libjavascriptcoregtk-1.0-dev: fails to upgrade from squeeze - trying to overwrite ...
Package: libjavascriptcoregtk-1.0-dev Version: 1.6.1-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'squeeze'. It installed fine in 'squeeze', then the upgrade to 'wheezy' fails because it tries to overwrite other packages files without declaring a replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package libjavascriptcoregtk-1.0-dev. Unpacking libjavascriptcoregtk-1.0-dev (from .../libjavascriptcoregtk-1.0-dev_1.6.1-5+b1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libjavascriptcoregtk-1.0-dev_1.6.1-5+b1_amd64.deb (--unpack): trying to overwrite '/usr/share/gir-1.0/JSCore-1.0.gir', which is also in package libwebkit-dev 1.2.7-0+squeeze1 This bug affects the piuparts tests of several other packages. I'll set affects ... otherpackage and found ... otherpackage/version on this bug when they are discovered. With this tagging piuparts-analyze can detect them and move the failed logs to the bugged category. cheers, Andreas libwebkit-dev_1.6.1-5+b1.log.gz Description: GNU Zip compressed data
Bug#652245: marked as done (tomoe: FTBFS: dpkg-buildpackage: error: dpkg-source --after-build tomoe-0.6.0 gave error exit status 1)
Your message dated Thu, 26 Jan 2012 03:18:09 + with message-id e1rqfqj-0003is...@franck.debian.org and subject line Bug#652245: fixed in tomoe 0.6.0-1.3 has caused the Debian Bug report #652245, regarding tomoe: FTBFS: dpkg-buildpackage: error: dpkg-source --after-build tomoe-0.6.0 gave error exit status 1 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.) -- 652245: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: tomoe Version: 0.6.0-1.2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20111210 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[3]: Entering directory `/build/tomoe-PoQn0t/tomoe-0.6.0' make[3]: Nothing to be done for `install-exec-am'. test -z /usr/lib/pkgconfig || /bin/mkdir -p /build/tomoe-PoQn0t/tomoe-0.6.0/debian/tmp/usr/lib/pkgconfig /usr/bin/install -c -m 644 'tomoe.pc' '/build/tomoe-PoQn0t/tomoe-0.6.0/debian/tmp/usr/lib/pkgconfig/tomoe.pc' make[3]: Leaving directory `/build/tomoe-PoQn0t/tomoe-0.6.0' make[2]: Leaving directory `/build/tomoe-PoQn0t/tomoe-0.6.0' make[1]: Leaving directory `/build/tomoe-PoQn0t/tomoe-0.6.0' dh_install dh_installdocs dh_installchangelogs dh_installexamples dh_installman dh_installcatalogs dh_installcron dh_installdebconf dh_installemacsen dh_installifupdown dh_installinfo dh_pysupport dh_pysupport: This program is deprecated, you should use dh_python2 instead. Migration guide: http://deb.li/dhs2p dh_installinit dh_installmenu dh_installmime dh_installmodules dh_installlogcheck dh_installlogrotate dh_installpam dh_installppp dh_installudev dh_installwm dh_installxfonts dh_installgsettings dh_bugfiles dh_ucf dh_lintian dh_gconf dh_icons dh_perl dh_usrlocal dh_link dh_compress dh_fixperms dh_strip dh_makeshlibs dh_shlibdeps dpkg-shlibdeps: warning: debian/libtomoe0/usr/lib/tomoe/module/recognizer/simple.so contains an unresolvable reference to symbol tomoe_dict_get_type: it's probably a plugin. dpkg-shlibdeps: warning: 23 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if debian/libtomoe0/usr/lib/tomoe/module/dict/unihan.so debian/libtomoe0/usr/lib/libtomoe.so.0.1.0 debian/libtomoe0/usr/lib/tomoe/module/recognizer/simple.so debian/libtomoe0/usr/lib/tomoe/module/dict/xml.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if debian/libtomoe0/usr/lib/tomoe/module/dict/unihan.so debian/libtomoe0/usr/lib/libtomoe.so.0.1.0 debian/libtomoe0/usr/lib/tomoe/module/recognizer/simple.so debian/libtomoe0/usr/lib/tomoe/module/dict/xml.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgmodule-2.0.so.0 could be avoided if debian/python-tomoe/usr/lib/pyshared/python2.7/tomoe.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if debian/python-tomoe/usr/lib/pyshared/python2.7/tomoe.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on librt.so.1 could be avoided if debian/python-tomoe/usr/lib/pyshared/python2.7/tomoe.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libpthread.so.0 could be avoided if debian/python-tomoe/usr/lib/pyshared/python2.7/tomoe.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: debian/ruby-tomoe/usr/lib/ruby/1.8/x86_64-linux/tomoe.so contains an unresolvable reference to symbol rbgutil_def_setters: it's probably a plugin. dpkg-shlibdeps: warning: 15 other similar warnings have been skipped (use -v to see them all). dpkg-shlibdeps: warning: dependency on libgmodule-2.0.so.0 could be avoided if debian/ruby-tomoe/usr/lib/ruby/1.8/x86_64-linux/tomoe.so were not uselessly linked against it (they use none of its symbols). dpkg-shlibdeps: warning: dependency on libgthread-2.0.so.0 could be avoided if debian/ruby-tomoe/usr/lib/ruby/1.8/x86_64-linux/tomoe.so were not uselessly linked against it (they use none of its symbols).
