Bug#726602: mpfr4: sh4: Please change optimize from O3 to O0
Package: mpfr4 Version: 3.1.1-2 Severity: wishlist Tags: patch Dear Maintainer, I am a porter of Renesas sh4. mpfr4 ftbfs on unstable of sh4, because this fails to build in O3. http://buildd.debian-ports.org/status/fetch.php?pkg=mpfr4arch=sh4ver=3.1.1-1stamp=1375195194 - /bin/bash ../libtool --tag=CC --mode=compile gcc -DTIME_WITH_SYS_TIME=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_STDINT_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 -DMPFR_HAVE_INTMAX_MAX=1 -DMPFR_HAVE_FESETROUND=1 -DHAVE_DENORMS=1 -DHAVE_ROUND=1 -DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 -DMPFR_USE_THREAD_SAFE=1 -DLT_OBJDIR=\.libs/\ -DHAVE_ATTRIBUTE_MODE=1 -DHAVE___GMPN_ROOTREM=1 -DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -I. -I../../src -g -O3 -mieee -MT exp3.lo -MD -MP -MF .deps/exp3.Tpo -c -o exp3.lo ../../src/exp3.c libtool: compile: gcc -DTIME_WITH_SYS_TIME=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_STDINT_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 -DMPFR_HAVE_INTMAX_MAX=1 -DMPFR_HAVE_FESETROUND=1 -DHAVE_DENORMS=1 -DHAVE_ROUND=1 -DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 -DMPFR_USE_THREAD_SAFE=1 -DLT_OBJDIR=\.libs/\ -DHAVE_ATTRIBUTE_MODE=1 -DHAVE___GMPN_ROOTREM=1 -DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -I. -I../../src -g -O3 -mieee -MT exp3.lo -MD -MP -MF .deps/exp3.Tpo -c ../../src/exp3.c -fPIC -DPIC -o .libs/exp3.o libtool: compile: gcc -DTIME_WITH_SYS_TIME=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 -DHAVE_ALLOCA_H=1 -DHAVE_STDINT_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 -DMPFR_HAVE_INTMAX_MAX=1 -DMPFR_HAVE_FESETROUND=1 -DHAVE_DENORMS=1 -DHAVE_ROUND=1 -DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 -DMPFR_USE_THREAD_SAFE=1 -DLT_OBJDIR=\.libs/\ -DHAVE_ATTRIBUTE_MODE=1 -DHAVE___GMPN_ROOTREM=1 -DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -I. -I../../src -g -O3 -mieee -MT exp3.lo -MD -MP -MF .deps/exp3.Tpo -c ../../src/exp3.c -o exp3.o /dev/null 21 make[3]: *** [exp3.lo] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/build/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/«PKGBUILDDIR»/build/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»/build' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 - I confirmed that this can be built with O1. when target architecture is sh4, could you set to O1? Best regards, Nobuhiro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libmpfr4:amd64 depends on: ii libc6 2.17-93 ii libgmp10 2:5.1.2+dfsg-3 ii multiarch-support 2.17-93 libmpfr4:amd64 recommends no packages. libmpfr4:amd64 suggests no packages. -- no debconf information diff --git a/debian/rules b/debian/rules index 39bd55d..1aa070d 100755 --- a/debian/rules +++ b/debian/rules @@ -38,13 +38,15 @@ export CFLAGS = -g export LDFLAGS = -Wl,-z,defs ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS))) -CFLAGS += -O0 + CFLAGS += -O0 else -ifeq (m68k,$(DEB_HOST_ARCH)) - CFLAGS += -O0 -else - CFLAGS += -O3 -endif + ifeq (m68k,$(DEB_HOST_ARCH)) +CFLAGS += -O0 + else ifeq (sh4,$(DEB_HOST_ARCH)) +CFLAGS += -O1 + else +CFLAGS += -O3 + endif endif ifeq (sh4,$(DEB_HOST_ARCH))
Bug#722531: groundcontrol: diff for NMU version 1.6.6-1.1
tags 722531 + patch
tags 722531 + pending
thanks
Dear maintainer,
I've prepared an NMU for groundcontrol (versioned as 1.6.6-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru groundcontrol-1.6.6/debian/changelog groundcontrol-1.6.6/debian/changelog
--- groundcontrol-1.6.6/debian/changelog 2010-08-02 10:26:40.0 -0700
+++ groundcontrol-1.6.6/debian/changelog 2013-10-16 23:14:25.0 -0700
@@ -1,3 +1,11 @@
+groundcontrol (1.6.6-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add 01_no_bzr_gtk: comments out dependencies on bzr-gtk, which is
+due to be removed from the archive. Closes: #722531
+
+ -- Jelmer Vernooij jel...@debian.org Wed, 16 Oct 2013 23:14:19 -0700
+
groundcontrol (1.6.6-1) unstable; urgency=low
* New upstream release
diff -Nru groundcontrol-1.6.6/debian/control groundcontrol-1.6.6/debian/control
--- groundcontrol-1.6.6/debian/control 2010-05-29 09:12:36.0 -0700
+++ groundcontrol-1.6.6/debian/control 2013-10-16 23:13:49.0 -0700
@@ -15,7 +15,7 @@
Architecture: all
Depends: ${python:Depends}, ${misc:Depends},
python-gtk2, python-gobject, python-launchpadlib,
- bzr, bzr-gtk, bzrtools,
+ bzr, bzrtools,
python-httplib2, python-nautilus, python-yaml,
python-lazr.restfulclient | python-lazr-restfulclient,
python-lazr.uri | python-lazr-uri,
diff -Nru groundcontrol-1.6.6/debian/patches/01_no_bzr_gtk groundcontrol-1.6.6/debian/patches/01_no_bzr_gtk
--- groundcontrol-1.6.6/debian/patches/01_no_bzr_gtk 1969-12-31 16:00:00.0 -0800
+++ groundcontrol-1.6.6/debian/patches/01_no_bzr_gtk 2013-10-16 23:13:19.0 -0700
@@ -0,0 +1,49 @@
+Description: Comment out single dependency on bzr-gtk (which no longer in the archive)
+Author: Jelmer Vernooij jel...@debian.org
+Status: Not upstream, but trunk has similar code
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722531
+
+diff -ur groundcontrol-1.6.6/GroundControl/commiter.py groundcontrol-1.6.6-no-bzr-gtk/GroundControl/commiter.py
+--- groundcontrol-1.6.6/GroundControl/commiter.py 2010-07-25 01:25:09.0 -0700
groundcontrol-1.6.6-no-bzr-gtk/GroundControl/commiter.py 2013-10-16 23:10:56.030191231 -0700
+@@ -28,7 +28,7 @@
+ IconManager, GtkApp
+ )
+ from GroundControl.bugs import BugSelection
+-from bzrlib.plugins.gtk.diff import DiffView
++#from bzrlib.plugins.gtk.diff import DiffView
+
+ change_types = (
+ 'added', # (path, id, kind)
+@@ -70,10 +70,10 @@
+ self.dirs= {}
+ self.fixes = []
+ super(CommitWindow, self).load(*args, **kwargs)
+-self.diffview = DiffView()
++#self.diffview = DiffView()
+ #self.diffview.set_trees(self.prevt, self.wtr)
+-self.diffview.set_trees(self.wtr, self.prevt)
+-self.widget('viewchanges').add(self.diffview)
++#self.diffview.set_trees(self.wtr, self.prevt)
++#self.widget('viewchanges').add(self.diffview)
+ self.slist = ChangesView(self.widget('changes'),
+ selected=self.selected)
+ all_changes = self.branch.get_changes()
+@@ -178,12 +178,12 @@
+ Show in the diff any items which we want
+ if not item.isdir and item.type == 'modified':
+ logging.debug(Showing diff for %s % item.stem)
+-self.diffview.show_diff([item.stem])
++#self.diffview.show_diff([item.stem])
+ self.widget(viewchanges).set_position(300)
+ self.window.resize(800, 600)
+-self.diffview.show()
+-else:
+-self.diffview.hide()
++#self.diffview.show()
++#else:
++#self.diffview.hide()
+
+ def remove_bug(self, widget):
+ It doesn't fix this bug at all!
+Only in groundcontrol-1.6.6-no-bzr-gtk/GroundControl: commiter.py~
diff -Nru groundcontrol-1.6.6/debian/patches/series groundcontrol-1.6.6/debian/patches/series
--- groundcontrol-1.6.6/debian/patches/series 1969-12-31 16:00:00.0 -0800
+++ groundcontrol-1.6.6/debian/patches/series 2013-10-16 23:13:27.0 -0700
@@ -0,0 +1 @@
+01_no_bzr_gtk
signature.asc
Description: Digital signature
Bug#726603: RM: mpich old binaries -- ROM; new version
Package: ftp.debian.org Severity: normal Please, remove old mpich-binaries from unstable. New version does not provide them any more: libmpich-mpd1.0-dev, libmpich-mpd1.0gf, libmpich-shmem1.0-dev, libmpich-shmem1.0gf, libmpich1.0-dev, libmpich1.0gf, mpe-source, mpi-doc, mpich-bin, mpich-mpd-bin, mpich-shmem-bin Thanks, Anton -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726604: isc-dhcp-relay: please add status parameter to init script
Package: isc-dhcp-relay Version: 4.1.1-P1-15+squeeze8 We're using isc-dhcp-relay in a cluster environment and need to call the init script with status to get a return code if running or not. Our quick hack is to add in /etc/init.d/isc-dhcp-relay: status) ps aux | grep dhc | grep -q -v grep || exit 1 ;; Please include something similar to the next release. Regards Stefan
Bug#726605: open-font-design-toolkit: Please drop dependency on unused bzr-dbus
Package: open-font-design-toolkit Severity: normal Dear Maintainer, Please consider dropping the dependency on bzr-dbus. bzr-dbus is a helper plugin that is not directly used by the user but rather by other tools that use it overon dbus; open-font-design-toolkit doesn't appear to do so. Background: there are no tools left in Debian that rely on bzr-dbus now that bzr-gtk has been removed, so I would like to request its removal. Thanks! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726002: xserver-xorg-video-mga: Dualheading using 1.6.2 segfaults
On Thu, Oct 17, 2013 at 5:34 AM, Robert Jacobs wrote: The right solution is for someone to modernize the 1.9.100 branch from six years ago, and give the MGA driver EXA support. But IIRC Brice Goglin had a number of problems that showed up in that branch. (e.g. debian 457502, 452223, 488762, 443936, 444739, c c c) Yes, I guess we cannot expect this to happen. When I tracked down this bug, I put in conditional execution that simply checked whether each function pointer was null and if so refused to dereference it. I feel like your conditional compilation patch is better, because then whenever upstream finishes ripping out XAA bits, the conditional compilation will be removed along with all the rest. And ideally Cyril's 02-* dualhead patch should go upstream, so review of that would be welcome too. I'm not certain what meets upstream's standards? It's sitting ineffectively at https://bugs.freedesktop.org/show_bug.cgi?id=18472 ; I assume the problem is there no real maintainer there to accept it. I know it's been getting plenty of in-the-field testing though. Getting this segfault fixed upstream probably requires getting 18472 commited first. Yes, I think the problem is the lack of a maintainer or someone who cares. There is no real upstream since no X.org people use this driver, can test it, or can justify spending time on it. IMO as long as it doesn't introduce regressions the patch should be applied. Personally I am not so inclined to apply it and to some degree implicitly accept the support burden and maintainership since I don't have the hardware the test, and not enough technical insight to be deal with it without testing. However if I can collect some Reviewed-by's and Tested-by's and someone stays around for testing I could do it. Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726606: RM: bzr-dbus -- ROM; Packages that relied on it have been removed from the archive
Package: ftp.debian.org Severity: normal Please remove bzr-dbus from the archive. It was previously only used by bzr-gtk, for which removal has also been removed from the archive and is not maintained upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705420: libsoup2.4-1: Problem with Eclipse and java
Despite my previous comment, this is not a libsoup2.4 bug, but a eclipse bug. The bug is solved in Eclipse 4.3 Kepler See: https://bugzilla.gnome.org/show_bug.cgi?id=710242#c5 https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726607: python-dev: dh_python2 incorrectly identifies a trigrams/so file as a python extension
Package: python-dev Version: 2.7.5-5 Severity: normal Take this package: http://archive.kali.org/kali/pool/main/p/python-guess-language/ And see how it must add --no-guessing-versions to its dh_python2 invocation just to work around the fact that dh_python2 incorrectly identifies /usr/lib/python2.7/dist-packages/guess_language/trigrams/so as a a Python extension. Even though readelf fails with: readelf: Error: Unable to read in 0xa35 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start And even though I tried to tell dh_python2 to ignore that file. And the file still ends up in /usr/lib/python2.7/ intead of /usr/lib/pyshared/ so the work-around is not really satisfactory, it only avoids the build failure on wheezy: E: dh_python2:145: extension for python2.6 is missing. Build extensions for all supported Python versions (`pyversions -vr`) or adjust X-Python-Version field or pass --no-guessing-versions to dh_python2 Please be a bit more strict in identifying Python extensions. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-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/dash Versions of packages python-dev depends on: ii libpython-dev 2.7.5-5 ii python 2.7.5-5 ii python2.7-dev 2.7.5-8 python-dev recommends no packages. python-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725143: unbuildable on some archs
Control: reopen -1
Looks like upstream forgot that OGRE_GCC_VERSION (the CMake variable) is
just the version, not multiplied by 100 like OGRE_COMP_VER (the C
macro), so libatomic never gets enabled. Fix attached.
Fix version check for enabling libatomic: OGRE_COMP_VER (C macro) is multiplied by 100, OGRE_GCC_VERSION (CMake variable) isn't.
$ diff -up OgreMain/CMakeLists.txt_orig OgreMain/CMakeLists.txt
--- OgreMain/CMakeLists.txt_orig 2013-10-16 15:32:31.0 +0100
+++ OgreMain/CMakeLists.txt 2013-10-17 08:05:37.285790478 +0100
@@ -289,7 +289,7 @@ else()
set_target_properties(OgreMain PROPERTIES VERSION ${OGRE_SOVERSION} SOVERSION ${OGRE_SOVERSION})
endif()
-if(OGRE_GCC_VERSION GREATER 470)
+if(OGRE_GCC_VERSION VERSION_GREATER 4.7)#-dumpversion doesn't include the patch level, so this requires = 4.8
list(APPEND LIBRARIES -latomic)
endif()
Bug#726069: libhpdf-2.2.1: fails to support large fonts
Alan, I will add the patch and create a new package. Note that I sent the patch to libharu upstream and they included it. So the next version will no longer require the patch. https://github.com/libharu/libharu/commit/e6fae213911c28bc00bb788f3d5a42913e37fbbe Johan On Thu, Oct 17, 2013 at 7:31 AM, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote: On 2013-10-11 16:16-0700 Alan W. Irwin wrote: I did try the obvious step of building the Debian packages for libhpdf using apt-src build libhpdf. All seemed well with that build, but when I installed the corresponding debs, none of the critical symbols for the library as revealed by objdump --dynamic-syms /usr/lib/libhpdf.so were available, and as a result all PLplot tests with the corresponding plot device failed. Is there something special I have to do to get apt-src build to work for this package? For this reason, I was unable to test the attached patch for the Debian source of version 2.2.1 of this library, but I am virtually positive this patch will work because it is only a two-line patch that does apply cleanly to 2.2.1. I have now figured out the source of these unexpected objdump results. Those were an artifact of having CFLAGS=-O3 -fvisibility=hidden defined as an environment variable for the PLplot build I was doing at the same time. Sorry this issue obscured the simple issue which I now repeat for clarity. The patch I attached to the original report applies cleanly to the Debian version of the libharu (a.k.a., libhpdf) source code, the apt-src build of that patched result proceeds cleanly, and when the resulting debs are installed, they produce -rw-r--r-- 1 root root 747408 Oct 16 21:23 /usr/lib/libhpdf-2.2.1.so lrwxrwxrwx 1 root root 16 Oct 16 21:23 /usr/lib/libhpdf.so - libhpdf-2.2.1.so The PLplot build of our pdf device against the above patched library proceeds without issues as does all our tests of that device (which is linked with the above device). In particular the segfault that appeared for our example 24 in the unpatched case is now gone, and valgrind shows no memory management errors for that example now. Therefore, please apply this patch when you create debs for libhpdf from now on. Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717777: pushed 1.3.3 to my personal git repo
Hi, just a quick update, I pushed my changes to http://anonscm.debian.org/gitweb/?p=users/mvo/ansible.git;a=summary for review, would be great to get feedback. Cheers, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726002: xserver-xorg-video-mga: Dualheading using 1.6.2 segfaults
Tormod Volden writes: And ideally Cyril's 02-* dualhead patch should go upstream, so review of that would be welcome too. I'm not certain what meets upstream's standards? It's sitting ineffectively at https://bugs.freedesktop.org/show_bug.cgi?id=18472 ; I assume the problem is there no real maintainer there to accept it. I know it's been getting plenty of in-the-field testing though. Getting this segfault fixed upstream probably requires getting 18472 commited first. Yes, I think the problem is the lack of a maintainer or someone who cares. There is no real upstream since no X.org people use this driver, can test it, or can justify spending time on it. IMO as long as it doesn't introduce regressions the patch should be applied. Personally I am not so inclined to apply it and to some degree implicitly accept the support burden and maintainership since I don't have the hardware the test, and not enough technical insight to be deal with it without testing. However if I can collect some Reviewed-by's and Tested-by's and someone stays around for testing I could do it. I'm happy to count as a Tested-by, and as far as I can tell the patch 02_tentatively_unbreak_dual_head.diff looks sane to me. I'm unfortunately not very familiar with the Xorg low-level internals to do any kind of comparison to any other (if any) more-nearly maintained legacy driver. What kind of testing is needed? Just simple HEAD doesn't have obvious regressions on my hardware? If so, I did test a very close variant to the patch that's in LP 1180986, and it mostly worked, but as I said, I got droppings on the second head. - Robert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726587: vpb-driver: config.guess/config.sub out of date for arm64
Hi Colin, On Wed, Oct 16, 2013 at 11:49:08PM +0100, Colin Watson wrote: Package: vpb-driver Version: 4.2.55-1 Severity: important Tags: patch User: debian-...@lists.debian.org Usertags: arm64 vpb-driver's config.guess/config.sub are out of date for the forthcoming arm64 port. The attached patch sets things up so that you don't have to be bothered by this type of bug for future ports. Thanks for the patch, but you realise this shouldn't actually be a problem in the version that's actually shipping in _Debian_, right? Unless I'm missing something, aarch64 support was added to autotools-dev in Feb 2012, and vpb-driver already has new enough versions for that. If that's not true, then please do let me know what other version of them you do need for this. This patch just hides the problem for Debian, but I'd much rather fix it for all users with a new upstream release whenever this sort of thing is needed. Since then I'll only be bothered by people reporting bugs against old versions they haven't updated, not people using the latest version on systems other than Debian ;) Thanks for the heads up, but please check the current version and let me know if there's still actually a problem. I can get a new package out quickly if there is, but afaics, we're already fine. Cheers, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726608: sleepd suspends on AC even when running with --ac-unused=0
Package: sleepd Version: 2.04 Severity: normal Hello, I don't know when it started (my notebook is mostly in use, hence sleepd has little to do ;), but recently I found that sleepd sends my system into S3 even when on AC. From the log: $ grep sleepd /var/log/syslog Oct 16 19:12:57 t420s sleepd[2889]: 12 sec sleep; resetting timer Oct 16 19:32:07 t420s sleepd[2889]: system inactive for 600s; forcing sleep The running process: $ ps ax | grep sleep[d] 2889 ?Ssl0:00 /usr/sbin/sleepd --ac-unused=0 --unused=600 --battery=5 --sleep-command=/root/bin/suspend2ram sysfs tells me: $ cat /sys/class/power_supply/AC/online 1 Unfortunately running with -v doesn't show anything of interest in the log either. Cheers Wolfgang -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-3-686-pae (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/bash Versions of packages sleepd depends on: ii libapm1 3.2.2-14 ii libc62.17-93 ii libdbus-1-3 1.6.16-1 ii libhal1 0.5.14-8 ii lsb-base 4.1+Debian12 Versions of packages sleepd recommends: ii hal 0.5.14-8 ii pm-utils 1.4.1-12 sleepd suggests no packages. -- Configuration Files: /etc/default/sleepd changed: PARAMS=--ac-unused=0 --unused=600 --battery=5 --sleep-command=/root/bin/suspend2ram -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567210:
tags 567210 patch severity 567210 grave thanks Instead of: $ cat /usr/bin/saxon-xslt #!/bin/sh exec java -classpath /usr/share/java/saxon.jar com.icl.saxon.StyleSheet $@ it should read: #!/bin/sh java -cp /etc/xml/resolver:/usr/share/java/xslthl.jar:/usr/share/java/xml-resolver.jar:/usr/share/java/saxonb.jar net.sf.saxon.Transform -x org.apache.xml.resolver.tools.ResolvingXMLReader -y org.apache.xml.resolver.tools.ResolvingXMLReader -r org.apache.xml.resolver.tools.CatalogResolver $@ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726610: libjts-java: New version 1.13 is available upstream.
Package: libjts-java Version: 1.11-1 Severity: wishlist Package could use a newer upstream version. http://sourceforge.net/p/jts-topo-suite/code/HEAD/tree/tags/Version_1.13/ Thx! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (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 libjts-java depends on: ii default-jre 1:1.7-49 ii default-jre-headless 1:1.7-49 ii libjdom1-java 1.1.3-1 ii libxerces2-java 2.11.0-7 libjts-java recommends no packages. Versions of packages libjts-java suggests: pn libjts-java-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726609: maven-debian-helper: Using wrong path to mvnDebug when checking if apt-file
Package: maven-debian-helper Version: 1.6.5 Severity: normal Tags: patch mh_make checks if apt-file is configured. For that purpose it searches for /usr/bin/mvnDebug using apt-file. However, mvnDebug can never be found that way as it is nowadays available at /usr/share/maven/bin/mvnDebug. As such, mh_make always issues an update just to recognize that its 'Index is up-to-date.' The following patch resolves the issue. --- /usr/bin/mh_make 2013-08-17 20:26:36.0 +0200 +++ /tmp/mh_make 2013-10-17 09:15:56.0 +0200 @@ -132,7 +132,7 @@ exit 1 else res=ok -apt-file search /usr/bin/mvnDebug | grep maven /dev/null || res=failed +apt-file search /usr/share/maven/bin/mvnDebug | grep maven /dev/null || res=failed if [ $? != 0 ] || [ $res == failed ]; then echo Warning: apt-file doesn't seem to be configured apt-file update -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (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 maven-debian-helper depends on: ii default-jdk 1:1.7-49 ii libmaven-clean-plugin-java 2.5-1 ii libmaven-compiler-plugin-java 2.0.2-6 ii libmaven-jar-plugin-java2.2-6 ii libmaven-resources-plugin-java 2.3-7 ii libmaven-site-plugin-java 2.1-2 ii libplexus-velocity-java 1.1.8-1 ii libsurefire-java2.10-4 ii maven-repo-helper 1.8.4 ii maven2 2.2.1-14 ii velocity1.7-4 maven-debian-helper recommends no packages. Versions of packages maven-debian-helper suggests: ii apt-file 2.5.2 ii devscripts2.13.4 ii libmaven-javadoc-plugin-java 2.6.1-2 ii subversion1.7.9-1+nmu6 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726611: /usr/bin/mh_make: NPE while resolving dependencies
Package: maven-debian-helper
Version: 1.6.5
Severity: important
File: /usr/bin/mh_make
Oct 17, 2013 9:38:48 AM
org.debian.maven.packager.DependenciesSolver$ToResolve resolve
SEVERE: Cannot resolve dependencies in ./basex-api/pom.xml: Not a valid
package name: null
java.lang.IllegalArgumentException: Not a valid package name: null
at
org.debian.maven.packager.DebianDependency.checkPackageName(DebianDependency.java:44)
at org.debian.maven.packager.DebianDependency.init(DebianDependency.java:15)
at org.debian.maven.packager.DebianDependency.init(DebianDependency.java:20)
at
org.debian.maven.packager.util.PackageScanner.searchPkg(PackageScanner.java:124)
at
org.debian.maven.packager.util.PackageScanner.searchPkgContainingJar(PackageScanner.java:87)
at
org.debian.maven.packager.DependenciesSolver.resolveDependency(DependenciesSolver.java:657)
at
org.debian.maven.packager.DependenciesSolver.access$100(DependenciesSolver.java:56)
at
org.debian.maven.packager.DependenciesSolver$ToResolve.resolve(DependenciesSolver.java:176)
at
org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:268)
at
org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:900)
$ cat ./basex-api/pom.xml
?xml version=1.0?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0http://maven.apache.org/xsd/maven-4.0.0.xsd;
modelVersion4.0.0/modelVersion
artifactIdbasex-api/artifactId
parent
groupIdorg.basex/groupId
artifactIdbasex-parent/artifactId
version7.7.2/version
relativePath../relativePath
/parent
nameBaseX API/name
dependencies
dependency
groupIdorg.basex/groupId
artifactIdbasex/artifactId
version${project.version}/version
/dependency
dependency
groupIdnet.xqj/groupId
artifactIdbasex-xqj/artifactId
/dependency
dependency
groupIdorg.xmldb/groupId
artifactIdxmldb-api/artifactId
/dependency
dependency
groupIdorg.eclipse.jetty/groupId
artifactIdjetty-server/artifactId
/dependency
dependency
groupIdorg.eclipse.jetty/groupId
artifactIdjetty-servlet/artifactId
/dependency
dependency
groupIdorg.eclipse.jetty/groupId
artifactIdjetty-webapp/artifactId
/dependency
dependency
groupIdcom.ettrema/groupId
artifactIdmilton-api/artifactId
/dependency
dependency
groupIdcommons-fileupload/groupId
artifactIdcommons-fileupload/artifactId
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-nop/artifactId
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
/dependency
dependency
groupIdcom.vividsolutions/groupId
artifactIdjts/artifactId
/dependency
/dependencies
build
finalName${project.artifactId}-${project.version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
useIncrementalCompilationfalse/useIncrementalCompilation
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
configuration
jettyXml${basedir}/src/main/webapp/WEB-INF/jetty.xml/jettyXml
!-- Key and port for stopping Jetty
stopKeykeyToStopJetty/stopKey
stopPort8985/stopPort --
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
/plugin
!--plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin--
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
includeScopecompile/includeScope
excludeArtifactIdsxstream/excludeArtifactIds
/configuration
/plugin
!-- Temporarily removed (takes some time)
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
/plugin--
/plugins
/build
/project
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (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 maven-debian-helper depends on:
ii default-jdk 1:1.7-49
ii
Bug#706639: btsync
Hi, I am willing to 'adopt' this package though I am not sure how it all works. Kind regards, Dennis Ruhe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726578: pwgen: Multiple vulnerabilities in passwords generation
Hi, On 16 October 2013 22:03, Yves-Alexis Perez cor...@debian.org wrote: I'm not too sure how to handle that, especially for stable releases, since it seems major refactoring might be needed to get rid of the weaknesses and bias. I think it's best to write a script that uses makepasswd and is command-line and output-compatible with pwgen. Basically changing everything under the hood without letting others know. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726612: ITP: cpl-plugin-kmos -- ESO data reduction pipeline for KMOS
Package: wnpp Severity: wishlist Owner: Ole Streicher deb...@liska.ath.cx X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org * Package name: cpl-plugin-kmos Version : 1.2.4 Upstream Author : MPG * URL : http://www.eso.org/sci/software/pipelines/kmos/kmos-pipe-recipes.html * License : GPL Programming Lang: C Description : ESO data reduction pipeline for KMOS This is the data reduction pipeline for the KMOS instrument of the Very Large Telescope (VLT) from the European Southern Observatory (ESO). . The K-band Multi Object Spectrograph (KMOS) is a second-generation instrument designed for operation on the VLT. The key feature of KMOS is its ability to perform Integral Field Spectroscopy in the near-infrared bands for 24 targets simultaneously. Further information about KMOS can be found under http://www.eso.org/sci/facilities/paranal/instruments/kmos/ A git repository is created at http://anonscm.debian.org/gitweb/?p=debian-science/packages/cpl-plugin-kmos.git The recipe will be based on the same template as the other plugins created so far (cpl_plugin_amber, cpl_plugin_fors, cpl_plugin_giraf, cpl_plugin_hawki, cpl_plugin_sinfo). Best regards Ole -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726549: ITA: iftop -- displays bandwidth usage information on an network interface
retitle 726549 ITA: iftop -- displays bandwidth usage information on an network interface owner 726549 ! thanks I intend to adopt iftop. Markus signature.asc Description: OpenPGP digital signature
Bug#726553: ITA: tofrodos -- Converts DOS - Unix text files, alias tofromdos
retitle 726553 ITA: tofrodos -- Converts DOS - Unix text files, alias tofromdos owner 726553 ! thanks I intend to adopt tofrodos. Markus signature.asc Description: OpenPGP digital signature
Bug#726492: debian-edu: Task files are specifying a lot of not existing / renamed packages
Hi, On Wed, Oct 16, 2013 at 04:55:20PM +0200, Holger Levsen wrote: On Mittwoch, 16. Oktober 2013, Andreas Tille wrote: Yes, there is a way. Inspecting the log I've posted. Could you please have a real look at the list? Could you provide examples from that list, please? You already parsed it it seems. task common: Package gcc-4.0-base not found task common: Package expect-tcl8.3 is provided in Ubuntu task common: Package tk8.3 is provided in Ubuntu task common: Package gobjc-4.2 is provided in Ubuntu task common: Package gobjc++-4.2 is provided in Ubuntu task common: Package gfortran-4.2 is provided in Ubuntu task common: Package sun-java5-bin is provided in Ubuntu task common: Package sun-java5-jre is provided in Ubuntu task common: Package sun-java5-plugin is provided in Ubuntu task main-server: Package php4-cli not found task main-server: Package php4 not found task desktop-other: Package gij-4.1 is provided in Ubuntu task desktop-other: Package ibm-jdk1.1-installer not found task desktop-other: Package jdk1.1 not found task desktop-other: Package kaffe is provided in Ubuntu ... Here are some tricky ones you most probably want to replace with valid packages: task lang-no-desktop: Package openoffice.org-help-nb not found task lang-no-desktop: Package openoffice.org-help-nn not found task lang-no-desktop: Package icedove-l10n-nb not found task lang-no-desktop: Package icedove-l10n-nn not found task desktop-other: Package openoffice.org-help-en not found task desktop-other: Package openoffice.org-l10n-common is provided in Ubuntu task desktop-other: Package openoffice.org-l10n-en-us not found task desktop-other: Package openoffice.org-l10n-fr is mentioned more than once. There is no point in adding an extra entry with strength 'ignore'. task desktop-other: The warning about duplicated package openoffice.org-l10n-fr should have just happended'. task desktop-other: Package openoffice.org-l10n-hi not found task desktop-other: Package openoffice.org-l10n-lo is provided in Ubuntu task desktop-other: Package openoffice.org-l10n-sr-cs not found task desktop-other: Package iceweasel-l10n-cy-gb not found task desktop-other: Package iceweasel-l10n-et-ee not found task desktop-other: Package iceweasel-l10n-roa-es-val not found task desktop-other: Package iceweasel-l10n-uk-ua not found task desktop-other: Package kde-l10n-af not found task desktop-other: Package kde-l10n-az not found task desktop-other: Package kde-l10n-bn not found task desktop-other: Package kde-l10n-br not found task desktop-other: Package kde-l10n-cy not found task desktop-other: Package kde-l10n-mn not found task desktop-other: Package kde-l10n-ms not found task desktop-other: Package kde-l10n-rw not found task desktop-other: Package kde-l10n-se is provided in Ubuntu task desktop-other: Package kde-l10n-srlatin not found task desktop-other: Package kde-l10n-ss not found task desktop-other: Package kde-l10n-ta not found task desktop-other: Package kde-l10n-uz not found ... Moreover: Future packages should get some additional information inside the tasks file - you might really want to reread the docs[2]. Frankly: if debian-blends only gives me work more work regularily, Ups, please prove your point: In how far does the Blends framework gives you more work? I would say it just opens your eyes for work you missed to do. why should I use it at all? As I see it we want to maintain a few metapackages with it, keeping up with some meta framework just to achieve this, seems a bit cumbersome... Please be more verbose how you want to maintain a few metapackages just without checking whether * they are valid * they contain things that should not be in The framework was initially invented by Petter for Debian Edu exclusively and I took the freedom to enhance it for everybody. Your question why you should use what you invented before becomes a bit unexpected, really. And you should know that I spended a lot of time on creating tools that go way beyond just metapackages you could perfectly use for advertising of Debian Edu and doing QA work. Its not my fault if you reduce the framework only onto a few metapackages. (eg also that the debian-edu package requires a special buld procedure is not nice for new Debian Edu developers.) I admit this is an issue and I'm working with my GSoC student to try to fix this. However, the exact wording for your sentence above would be ... the debian-edu *source* package requires ... I really wonder in how far a make dist is so complex to create a source package. In the GSoC project we even injected automatic debian/changelog creation what package was added / removed and added support for different architectures (I'm keen on learning how you want to cope with this with your a few metapackages editing approach). Unfortunately the source package creation process is *now* a bit more advanced than a simple make dist and thus we
Bug#726587: vpb-driver: config.guess/config.sub out of date for arm64
On Thu, Oct 17, 2013 at 06:10:51PM +1030, Ron wrote: On Wed, Oct 16, 2013 at 11:49:08PM +0100, Colin Watson wrote: Package: vpb-driver Version: 4.2.55-1 Severity: important Tags: patch User: debian-...@lists.debian.org Usertags: arm64 vpb-driver's config.guess/config.sub are out of date for the forthcoming arm64 port. The attached patch sets things up so that you don't have to be bothered by this type of bug for future ports. Thanks for the patch, but you realise this shouldn't actually be a problem in the version that's actually shipping in _Debian_, right? Unless I'm missing something, aarch64 support was added to autotools-dev in Feb 2012, and vpb-driver already has new enough versions for that. If that's not true, then please do let me know what other version of them you do need for this. This patch just hides the problem for Debian, but I'd much rather fix it for all users with a new upstream release whenever this sort of thing is needed. Since then I'll only be bothered by people reporting bugs against old versions they haven't updated, not people using the latest version on systems other than Debian ;) I was one version back from the latest version in Debian, indeed, and the latest version does have new enough files. However: We port to new architectures an average of once a year or so. Every time we do this, we have to fix a whole bunch (hundreds, at the very least) of packages shipping old config.guess and config.sub files; it's by far the most common porting problem by package count. It is very tedious work and means that the porters end up wasting time doing this rather than dealing with more interesting porting bugs. In quite a number of those cases, the maintainers of those packages have previously said that they'll just release new versions for this kind of thing. However, life happens: sometimes they've gone MIA for a while, or sometimes they have some external constraint that means they don't want to upload new versions just now. None of this ought to hold up the porting work. Every package that updates its config.guess/config.sub automatically at build time is one fewer package with a non-zero probability of being a hassle for *any* future port. I used to think the same way you do: hey, I'm a conscientious maintainer, *of course* I'll update config.guess/config.sub when I get bugs about it. Then I started doing ports to new architectures and saw things from the other side of the fence, and now I see why the autotools-dev maintainer has been banging on about this in README.Debian for all these years. There's an enormous time lag on getting config.* updates into packages by way of source uploads. We're in a situation where lots of otherwise-portable packages routinely fail to build during architecture bring-ups just because they don't recognise the architecture name yet and have to be manually re-educated, and this doesn't really seem a sensible situation to be in. Thanks for the heads up, but please check the current version and let me know if there's still actually a problem. I can get a new package out quickly if there is, but afaics, we're already fine. Sorry if this bug isn't quite right as stated. However, statistically, I just filed this bug too early. :-) Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726613: mercurial wheezy backport has incorrect libc6 dependency
Package: mercurial Version: 2.7.2-1~bpo70+1 Severity: normal Currently, I see the mercurial wheezy backport is 2.7.2-1~bpo70+1 0 100 http://debian.lcs.mit.edu/debian/ wheezy-backports/main amd64 Packages and `apt-cache show` gives Package: mercurial Version: 2.7.2-1~bpo70+1 Installed-Size: 236 Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Architecture: amd64 Depends: libc6 (= 2.14), python (= 2.7), python ( 2.8), ucf (= 2.0020), mercurial-common (= 2.7.2-1~bpo70+1) But the version of libc6 in wheezy is *** 2.13-38 0 500 http://debian.lcs.mit.edu/debian/ wheezy/main amd64 Packages 100 /var/lib/dpkg/status and indeed this version does not install on my wheezy system. It looks to me like this was somehow compiled against the wrong version of libc6. Regards, Faheem -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'), (50, 'unstable'), (50, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689858: Bug#715555: gnome package has icedove and xul-ext-adblock-plus incompatibility
tags 689858 +patch
thanks
On Thu, Sep 05, 2013 at 03:01:21AM +0200, John Paul Adrian Glaubitz wrote:
For the sake of sanity, please do that. This dependency is constantly
creating headaches as installations or dist-upgrades constantly
fail when either Iceweasel or Icedove are out of sync version-wise
when xul-ext-adblock-plus is updated.
Patch attached. GNOME folks, feedback greatly appreciated.
Index: debian/control
===
--- debian/control (revision 39941)
+++ debian/control (working copy)
@@ -158,15 +158,15 @@
telepathy-rakia,
telepathy-salut,
totem-plugins,
-# To match functionality that used to be in epiphany
- xul-ext-adblock-plus,
# For debconf
libgtk2-perl (= 1:1.130),
${misc:Depends}
Recommends: browser-plugin-gnash,
gdebi,
nautilus-sendto-empathy,
-telepathy-idle
+telepathy-idle,
+# To match functionality that used to be in epiphany
+xul-ext-adblock-plus
Suggests: dia-gnome,
gnome-boxes [amd64 i386],
gnucash,
Index: debian/changelog
===
--- debian/changelog (revision 39941)
+++ debian/changelog (working copy)
@@ -1,3 +1,12 @@
+meta-gnome3 (1:3.8+4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Move xul-* dependencies to Recommends:, since they cause
+inter-operation problems with users wishing to co-install/
+upgrade Icedove, etc. Closes: #689858.
+
+ -- Jonathan Dowland j...@debian.org Wed, 16 Oct 2013 23:50:31 +0100
+
meta-gnome3 (1:3.8+4) unstable; urgency=low
[ Michael Biebl ]
Bug#689858: gnome depends on adblock-plus
On Sat, Oct 12, 2013 at 03:03:19AM +0200, berenger.mo...@neutralite.org wrote: gnome depends on xul-ext-adblock-plus. … So, I would like to know if someone knows why this dependency exists, instead of a recommendation or suggestion. I was curious so I investigated. The dependency was added in this commit¹ with the message Require firefox extensions that match epiphany functionality: keyring, adblock. Looking at the commit log, an earlier commit sheds some more light²: Install iceweasel instead of epiphany :( See bug#682481. So, GNOME proper includes the Epiphany browser, but Debian's GNOME metapackage omits it due to the lack of security support. Iceweasel is used in its place, and the XUL* extensions are also depended upon so that users have the same level of functionality as Epiphany has. That's the logic, but the consequence is lots of problems as #689858 indicates. It seems to me that attempting to get feature parity with Epiphany is a nice goal, but perhaps not mission critical: would the GNOME maintainers not consider moving the xul-* dependencies to Recommends? The last consensual message to #682481 seemed to suggest that depending on chromium made more sense than Iceweasel, so I don't know why that wasn't done, but perhaps it could. I haven't seen any comment from the GNOME maintainers regarding this suggestion. ¹ http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/meta-gnome3/debian/control?revision=35790view=markup ² http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/meta-gnome3/debian/control?revision=35758view=markup -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724287: rt4-extension-jsgantt, trac-jsgantt: embeds jsgantt - should depend on libjs-jsgantt separately packaged
Quoting Satoru KURASHIKI (2013-10-17 03:18:53) On Tue, Oct 8, 2013 at 10:15 PM, Jonas Smedegaard d...@jones.dk wrote: Ah, right - here are the diffs: https://github.com/bestpractical/rt-extension-jsgantt/tree/master/etc The libjs-jsgantt package could include wiht its source the above diffs and apply them at build time, to also offer in the binary package the patched variant usable for RT. I believe that is much better than status quo. I'm unsure which that is better or not, but anyway, nearly dead upstream, few references, and so on... Indeed not actively maintained - but evidently in active use, so arguably _more_ important to streamline for eventual bugfixing. Package libjs-jsgantt does not yet exist. �Just now I filed bug#725794, and intend to do the packaging unless (preferred) someone else in the Javascript team picks it up. if libjs-jsgantt is packaged and provides patched variant for rt, I will update rt-extension-jsgantt to fit. Thanks! - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#726615: comixcursors: New upstream version available, 0.8
Package: comixcursors Version: 0.7.2-3 Severity: wishlist The Comixcursors project has released a new version, 0.8 URL:https://opendesktop.org/content/download.php?content=32627id=9tan=97479777PHPSESSID=54c69c9d6522e539893a01d56eb29e52. -- \ “The surest way to corrupt a youth is to instruct him to hold | `\ in higher esteem those who think alike than those who think | _o__) differently.” —Friedrich Nietzsche, _The Dawn_, 1881 | Ben Finney b...@benfinney.id.au signature.asc Description: Digital signature
Bug#726607: python-dev: dh_python2 incorrectly identifies a trigrams/so file as a python extension
Control: clone 726607 -1 Control: reassign -1 dh-python 1.20131003-1 Control: tag -1 +pending I will upload fixed dh-python today or tomorrow, please add dh-python to your Build-Depends to use dh-python's dh_python2 (I will fix it in python package as well, but don't plan to upload it soon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712475: RM: libfsobasics -- ROM; since version 0.12 libfsoXYZ is built from one source package (libfsoframework)
Hi, Should be ready for removal now: $ ssh coccia.debian.org dak rm -Rn libfsobasics Will remove the following packages from unstable: libfsobasics | 0.11.0-1.1 | source libfsobasics-dbg | 0.11.0-1.1 | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc libfsobasics-dev | 0.11.0-1.1 | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc libfsobasics0 | 0.11.0-1.1 | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc Maintainer: Debian FreeSmartphone.Org Team pkg-fso-ma...@lists.alioth.debian.org --- Reason --- -- Checking reverse dependencies... # Broken Depends: fso-gsmd: fso-gsmd-ezx [amd64 armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] fso-gsmd-gta04 [amd64 i386 ia64 mips mipsel powerpc s390 s390x sparc] fso-gsmd-htc [amd64 i386 ia64 mips mipsel powerpc s390 s390x sparc] fso-gsmd-openmoko [amd64 armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] Dependency problem found. Each of the broken depends are no longer built by fso-gsmd. (Arch: any has been changed to Arch: arm*, since the packages are not useful on architectures not supported by the platform) -- Sebastian signature.asc Description: Digital signature
Bug#726617: O: cminpack -- Nonlinear equations and nonlinear least squares problems
Package: wnpp Severity: normal I intend to orphan cminpack. My initial intention was to package cminpack as dependency of PCL (The Point Cloud Library). Since I gave up on PCL (not using it really), see #624178. I'd like to orphan cminpack. Description is: Minpack includes software for solving nonlinear equations and nonlinear least squares problems. Five algorithmic paths each include a core subroutine and an easy-to-use driver. The algorithms proceed either from an analytic specification of the Jacobian matrix or directly from the problem functions. The paths include facilities for systems of equations with a banded Jacobian matrix, for least squares problems with a large amount of data, and for checking the consistency of the Jacobian matrix with the functions. . This is the C re-write of the original fortran minpack implementation. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726091: Processed: Re: Bug#726091: liferea: Does not connect through proxy anymore.
notforwarded 726091 retitle 726091 libsoup: Cannot connect to proxy on localhost. reassign 726091 libsoup2.4-1 thanks. On 10/13/2013 01:33 AM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: forwarded 726091 https://sourceforge.net/p/liferea/bugs/1120/ Bug #726091 [liferea] liferea: Does not connect through proxy anymore. Set Bug forwarded-to-address to 'https://sourceforge.net/p/liferea/bugs/1120/'. Upstream has closed this bug out as being due to the library libsoup. I'm reassigning this bug report to the libsoup package. -David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726501: mysql-workbench: Crash on adding new table to empty EER diagram
Package: mysql-workbench Version: 6.0.7+dfsg1-1 Followup-For: Bug #726501 What i did was: * upgrade to latest version of mysql-workbench * create a new model (.mwb file) * deleted the created default database mydb * add a new diagram * click on the table icon - Crash. So I guess the problem is that I removed the database, and the EER diagram view somehow depends on it. Nevertheless I guess it is not supposed to crash. With an existing database, everything works fine. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-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 mysql-workbench depends on: ii libatkmm-1.6-1 2.22.7-2 ii libc62.17-93 ii libcairo21.12.16-2 ii libctemplate22.2-3 ii libgcc1 1:4.8.1-10 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgl1-mesa-glx [libgl1] 9.1.6-2+b1 ii libglib2.0-0 2.36.4-1 ii libglibmm-2.4-1c2a 2.36.2-1 ii libgnome-keyring03.4.1-1 ii libgtk2.0-0 2.24.21-1 ii libgtkmm-2.4-1c2a1:2.24.4-1 ii liblua5.1-0 5.1.5-5 ii libmysqlclient18 5.5.33+dfsg-1 ii libmysqlcppconn7 1.1.3-5 ii libodbc1 2.2.14p2-5 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpangomm-1.4-1 2.34.0-1 ii libpcre3 1:8.31-2 ii libpcrecpp0 1:8.31-2 ii libpython2.7 2.7.5-8 ii libsigc++-2.0-0c2a 2.2.10-0.2 ii libstdc++6 4.8.1-10 ii libtinyxml2.6.2 2.6.2-2 ii libuuid1 2.20.1-5.5 ii libvsqlitepp30.3.12-1 ii libx11-6 2:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 ii libzip2 0.10.1-1.1 ii mysql-client 5.5.33+dfsg-1 ii mysql-client-5.5 [mysql-client] 5.5.33+dfsg-1 ii mysql-workbench-data 6.0.7+dfsg1-1 ii python-mysql.connector 0.3.2-1 ii python-paramiko 1.10.1-1 ii python-pexpect 2.4-1 ii python-pyodbc3.0.6-2 ii python-pysqlite2 2.6.3-3 ii python2.72.7.5-8 pn python:any none Versions of packages mysql-workbench recommends: ii mysql-utilities 1.3.5-1 ii ttf-bitstream-vera 1.10-8 Versions of packages mysql-workbench suggests: ii gnome-keyring 3.8.2-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726618: slepc3.4.2-doc: Dangling links in example HTML files
Package: slepc3.4.2-doc Version: 3.4.2.dfsg-1 Severity: normal The links in the HTML example files such as /usr/share/doc/slepc3.4.2-doc/src/eps/examples/ex1.c.html don't work. At the top they have a link to raw source code, which doesn't work because the *.c files don't seem to be included. In addition, the links within the code, to the SLEPC manual pages, are incorrect. Their targets begin with /usr/share/doc/docs but I think that should be /usr/share/doc/slepc3.4.2-doc/docs Best regards Torquil Sørensen -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.11.5 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash slepc3.4.2-doc depends on no packages. slepc3.4.2-doc recommends no packages. Versions of packages slepc3.4.2-doc suggests: ii libslepc3.4.2-dev 3.4.2.dfsg-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726619: Debian cloud image built with openstack-debian-images shows no output in the log tab of Horizon
Package: openstack-debian-images Version: 0.4 I've built a Debian Wheezy cloud image using openstack-debian-images. When I instanciate it, it works as expected. But the log tab in OpenStack Dashboard shows no output. I'd like to have the output of the console/tty also displayed in this tab. The ubuntu cloud archive image can be used as an example. Thanks, Jordan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555199: liferea: 'localhost' doesn't work as proxy host
retitle 555199 libsoup: 'localhost' doesn't work as proxy host reassign 555199 libsoup2.4-1 thanks. When I enter 'localhost' as the proxy host, Lifera fails with the message: HTTP error code 0: Unable to connect to proxy Liferea Upstream has determined that this is an issue with libsoup. Reference: http://sourceforge.net/p/liferea/bugs/1120/ -David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726559: exaile: Segmentation fault after a second of playing
Toto == Thorsten Bonow thorsten.bo...@withouthat.org writes: Toto Package: exaile Version: 3.3.1-1 Severity: grave [...] Hi, the crash appears to be related to the Wikipedia-plugin. If I disable the plugin, exaile works again. It occured to me to disable the plugin after checking my syslog (sry, must have had a nail in my had): Oct 17 10:42:33 gepetto kernel: [91597.061624] exaile[29414]: segfault at 2c ip b2bc0df5 sp bf9cd580 error 4 in libwebkitgtk-1.0.so.0.19.8[b26eb000+1bd8000] Although libwebkitgtk and related packages were updated in the last few days, downgrading to libjavascriptcoregtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-0_2.1.90.1-1_i386.deb libwebkitgtk-1.0-common_2.1.90.1-1_all.deb doesn't fix the problem; only disabling the plugin helps. Toto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726578: pwgen: Multiple vulnerabilities in passwords generation
Hi, I don't see that any major refactoring is needed, but rather the default assumed flags are unsafe, although changing them might be incompatible with some scripts/applications using pwgen. CVE-2013-4440 non-tty passwords are trivially weak by default should ideally stop using -0A by default in non-tty mode, but could maybe warn/fail if the caller doesn't override with -nc, which has been recommended in the man page until now. CVE-2013-4441 Phonemes mode has heavy bias and is enabled by default assume -s by default? I think it uses the same character set but with more entropy, so only a human user should notice any difference at all. As long as the -s flag is set *before* parsing command line flags, it does not conflict with -0 -A -B or -v. CVE-2013-4442 Silent fallback to insecure entropy consider using /dev/random instead of /dev/urandom? (Debian bug #672241) and in any case fail if it cannot be read CVE-2013-4443 Secure mode has bias towards numbers and uppercase letters probably the least serious issue; -n guarantees at least one numeral, -c guarantees at least one capital, instead of being a completely random selection. Sometimes necessary if the password consumer enforces such a rule. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726620: geoclue: misses Depends: adduser
Package: geoclue Version: 2.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package geoclue. (Reading database ... 7103 files and directories currently installed.) Unpacking geoclue (from .../geoclue_2.0.0-1_amd64.deb) ... Setting up geoclue (2.0.0-1) ... /var/lib/dpkg/info/geoclue.postinst: 12: /var/lib/dpkg/info/geoclue.postinst: addgroup: not found dpkg: error processing geoclue (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: geoclue E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Andreas geoclue_2.0.0-1.log.gz Description: GNU Zip compressed data
Bug#726621: python{,3}-babel: leaves alternatives after purge: /usr/bin/pybabel
Package: python-babel,python3-babel Version: 1.3-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see http://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove name path'. Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 0m39.2s ERROR: WARN: Broken symlinks: /usr/bin/pybabel - /etc/alternatives/pybabel /etc/alternatives/pybabel - /usr/bin/pybabel-python2 0m40.7s ERROR: FAIL: Package purging left files on system: /etc/alternatives/pybabel - /usr/bin/pybabel-python2 not owned /usr/bin/pybabel - /etc/alternatives/pybabel not owned 0m41.1s ERROR: WARN: Broken symlinks: /usr/bin/pybabel - /etc/alternatives/pybabel /etc/alternatives/pybabel - /usr/bin/pybabel-python3 0m42.7s ERROR: FAIL: Package purging left files on system: /etc/alternatives/pybabel - /usr/bin/pybabel-python3 not owned /usr/bin/pybabel - /etc/alternatives/pybabel not owned cheers, Andreas python-babel_1.3-1.log.gz Description: GNU Zip compressed data
Bug#726089: Processed: Re: Bug#726089: liferea: Crashes on font decrease.
tag 726089 fixed-upstream thanks. Thank you for reporting this bug report. Upstream has fixed this bug in their git repository. The fix will be included in the next release. -David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726587: vpb-driver: config.guess/config.sub out of date for arm64
On Thu, Oct 17, 2013 at 08:46:27PM +1030, Ron wrote: And sometimes, updating autoconf at random actually breaks things, sometimes subtly (to be fair this seems to happen less often over the last few years now - but I have the scars of being burned by that too, and _always_ review the diffs when it is updated before trusting them). I'm not talking about updating autoconf output, though. I'm talking about updating config.guess and config.sub, which have some of the best compatibility records of anything in the archive. I've never heard of any bug caused by updating those, ever. I'm not unsympathetic to the work and pain of porters bootstrapping a new arch, but any 'solution' that is Debian-specific, isn't really a solution at all, it's just an SEP field. There are other distributions who update config.guess/config.sub in their packaging too. I would say that *both* upstream and distributions need to handle this, realistically; but I don't think the lack of upstream handling it should hold back distributions. If you really want to fix this for new ports, maybe we need a tool to scan the archives and report these things before they become the bottleneck for porting work. That just moves the manual work earlier (filing bugs, discussing them with maintainers, and NMUing when they ignore them is still quite a bit of manual work when you compare it with having all the packages just update themselves automatically); it isn't a fix. Lintian does already have a too old check -- but it doesn't actually bark about what would _really_ break (which 90% of the time is something utterly obscure that Debian won't run on anyway). Um, well. As a point of information: Tag: outdated-autotools-helper-file Severity: normal Certainty: possible Info: The referenced file has a time stamp older than April of 2012 and the package does not build-depend on autotools-dev or automake and therefore apparently does not update it. This usually means that the source package will not build correctly on ARM64, for which a Debian port is currently in progress, and may not support other newer architectures. . For packages using debhelper, the tools from the dh-autoreconf package should handle this issue. cdbs will automatically update these files if autotools-dev is installed during build, but the build dependency on autotools-dev is still necessary. . Otherwise, read /usr/share/doc/autotools-dev/README.Debian.gz (from the autotools-dev package) for information on how to fix this problem. Lintian's threshold is generally only updated when there's a specific relevant new port. It helps, but it's not good enough since many of the problematic packages simply aren't uploaded at all often enough so their maintainers tend not to notice; and I fundamentally disagree that let's source-upload half the archive is a sensible way to handle new ports, even if those uploads are spread out. Not enough people garden their pages on lintian.debian.org routinely enough for this not to be a horrendous pain for porters, and we still have the problem of MIA maintainers. Yes, it's true that some packages require manual porting, but those are statistically rare and often have other indicators (e.g. a specific limitation in their Architecture field). Anyhow, I'll close this one if you've confirmed the current package is ok, but I don't want you to think I don't care about your pain. On the contrary, I think we need a _better_ solution than what this patch does to lay the groundwork for common problems seen when porting new arches, and I'm pretty sure that for this specific problem, lintian already implements 99% of what you'd need. I'm a Lintian committer, albeit a somewhat dormant one; I respectfully disagree that it can ever deal with this problem adequately. Still, at least some other maintainers are switching to autotools-dev in response to my patches, so that's reducing the pain for the next time round. I wasn't expecting to be able to persuade everyone. Cheers, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726622: clang-3.3: failed unittests after building
Package: clang-3.3 Severity: important Dear Maintainer, I use Debian Wheezy but I needed clang-3.3 so I tried to backport it myself. I tried to backport it from jessie repos. What I did for that: First I tried to sudo apt-get build-dep clang-3.3 but it said that the needed version of libisl-dev couldn't be resolved So I installed it from jessie deb-src repos too: apt-get source -b libisl-dev sudo dpkg -i libisl10_0.11.2-1_amd64.deb sudo dpkg -i libisl-dev_0.11.2-1_amd64.deb It was built and installed ok. Then I did sudo apt-get build-dep clang-3.3 apt-get source -b clang-3.3 It decided that all dependencies are ok and started to build the package. It took a lot of time but in the end unit testing reported errors. I'll include the log of that and some log file generated by sphinx in next emails. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726623: nmu: libprelude_1.0.0-9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libprelude_1.0.0-9 . ALL . jessie . -m Rebuild against perl 5.18 libprelude-perl in testing is currently uninstallable due to a perl 5.14 dependency. Due to a FTBFS on kfreebsd the current sid version cannot migrate to testing, so lets try to rebuild the testing version ... possible alternatives: * remove libprelude from testing * give-back libprelude in sid since the FTBFS seems spurious Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658896: Bug status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm running several machines with Debian 7 (Wheezy) and have experience the problem described in bug #658896. I'd like to know whether are there some updates about this or an estimate of when will it be fixed on Wheezy. I'd be glad to help if you require it. Best Regards. - -- Joel Rosental R. Systems Administrator GPG Key Fingerprint = A9BF 3386 4371 2D14 C05D 7B91 2652 661F 7DB7 5B58 Tel: +34 91 481 69 87 Web: http://www.networks.imdea.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSX8SQAAoJECZSZh99t1tYYAYH/jkHTsJVi6hcLJPreS3ONvBq ZifDlX1rGotOfANYCBxm2+EhUcZ3H2dp+PrHtgizIDvoDpoREsnXtnS1JScL47Jf TxtVvDolqfugIjKe3yH39HcPHEg04MDQFFzCJslxie5FGO/ngML3fnYrHm8vsnde ZMWCXt/3cOq/KYf5zKe9U2M8eCD6Bmx/6U8KJ0MQcAuGnBXP9UOGKCpzARQjeeIJ 6asmayE3y/J+exuZE7E7uwP9LJ3zF5rx/A/g0JyVTos9udoXWQ7dXLNSYzJ4XQ1C j/h7K7uzSpBW1EThqASBKoU2108PeVB/lYRe/xX4nk479Umn/HLOuJLUSmNgcho= =8/qm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726575: RequiredComponents=[...]; nautilus-classic; in gnome-flashback.session.desktop
retitle 726575 gnome-session-flashback needs a versioned depdendency on nautilus = 3.8 severity 726575 important thanks Am 17.10.2013 06:25, schrieb Fabian Greffrath: Am Mittwoch, den 16.10.2013, 22:12 +0200 schrieb Michael Biebl: /usr/share/applications/nautilus-classic.desktop I see, I didn't have my nautilus upgraded to version 3.8 yet. However, it is nowhere reflected in the package relations that gnome-session-flashback depends on nautilus (= 3.8). Fair enough. Retitling the bug report and bumping severity. Might even be bumped to serious. -- 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#709641: gtkiostream will close these bugs
On Thursday, 26. September 2013 10:30:14 Matt Flax wrote: I can't upload because my key isn't in the ring. If someone else could upload for me - that would be great ... You should upload the package to mentors.debian.net and look for a sponsor - see the documentation on http://mentors.debian.net/ Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689858: Bug#715555: gnome package has icedove and xul-ext-adblock-plus incompatibility
Am 17.10.2013 10:56, schrieb Jonathan Dowland: tags 689858 +patch thanks On Thu, Sep 05, 2013 at 03:01:21AM +0200, John Paul Adrian Glaubitz wrote: For the sake of sanity, please do that. This dependency is constantly creating headaches as installations or dist-upgrades constantly fail when either Iceweasel or Icedove are out of sync version-wise when xul-ext-adblock-plus is updated. Patch attached. GNOME folks, feedback greatly appreciated. meta-gnome3 (1:3.4+7+deb7u1) stable; urgency=low * Demote xul-ext-adblock-plus to Suggests. Icedove and Iceweasel receive major updates via stable-security causing them to get out of sync and making xul-ext-adblock-plus and thus the gnome metapackage uninstallable. Closes: #71 -- Michael Biebl bi...@debian.org Thu, 26 Sep 2013 11:54:31 +0200 This was already addressed in a stable upload. We just need to merge the change for the unstable branch at some time. -- 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#726624: gnome-shell: notifications not working
Package: gnome-shell Version: 3.8.4-4 Severity: important Dear Maintainer, Notifications seem not to be working, and testing them with notify-send (from libnotify-bin) causes the following JS error in .xsession-errors: - JS ERROR: !!! Exception was: Error: Wrong type object; string expected JS ERROR: !!! message = 'Wrong type object; string expected' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/messageTray.js' JS ERROR: !!! lineNumber = '1348' JS ERROR: !!! stack = '([object Object])@/usr/share/gnome-shell/js/ui/messageTray.js:1348 wrapper([object Object])@/usr/share/gjs-1.0/lang.js:213 ([object Object])@/usr/share/gjs-1.0/lang.js:154 ([object Object])@/usr/share/gjs-1.0/lang.js:248 ([object Object])@/usr/share/gnome-shell/js/ui/messageTray.js:1886 wrapper([object Object])@/usr/share/gjs-1.0/lang.js:213 ([object Object],[object Object])@/usr/share/gnome-shell/js/ui/messageTray.js:1983 wrapper([object Object],[object Object])@/usr/share/gjs-1.0/lang.js:213 ([object Object])@/usr/share/gnome-shell/js/ui/messageTray.js:1880 wrapper([object Object])@/usr/share/gjs-1.0/lang.js:213 ([object Array],17582,[object Object],:1.55,null)@/usr/share/gnome-shell/js/ui/notificationDaemon.js:349 wrapper([object Array],17582,[object Object],:1.55,null)@/usr/share/gjs-1.0/lang.js:213 ([object Array],null)@/usr/share/gnome-shell/js/ui/notificationDaemon.js:451 ([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:91 ' - This also affects other programms sending notifications, like rhythmbox, which locks up when trying to notify. Cheers -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1 ii evolution-data-server3.8.5-2 ii gdm3 3.8.4-2 ii gir1.2-accountsservice-1.0 0.6.34-2 ii gir1.2-caribou-1.0 0.4.12-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-freedesktop 1.36.0-2+b1 ii gir1.2-gcr-3 3.8.2-4 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.03.8.1-2 ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-gtk-3.0 3.8.5-1 ii gir1.2-ibus-1.0 1.5.3-7 ii gir1.2-mutter-3.03.8.4-2 ii gir1.2-networkmanager-1.00.9.8.0-5 ii gir1.2-nmgtk-1.0 0.9.8.4-1 ii gir1.2-pango-1.0 1.32.5-5+b1 ii gir1.2-polkit-1.00.105-4 ii gir1.2-soup-2.4 2.42.2-6 ii gir1.2-telepathyglib-0.120.22.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-2 ii gir1.2-upowerglib-1.00.9.22-1 ii gjs 1.36.1-2 ii gnome-bluetooth 3.8.1-2 ii gnome-icon-theme-symbolic3.8.2.2-2 ii gnome-settings-daemon3.8.5-2 ii gnome-shell-common 3.8.4-4 ii gnome-themes-standard3.8.4-1 ii gsettings-desktop-schemas3.8.2-2 ii libatk-bridge2.0-0 2.10.0-1 ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcamel-1.2-43 3.8.5-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.14.4-3 ii libcogl-pango12 1.14.0-3 ii libcogl121.14.0-3 ii libcroco30.6.8-2 ii libdbus-1-3 1.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libecal-1.2-15 3.8.5-2 ii libedataserver-1.2-173.8.5-2 ii libegl1-mesa [libegl1-x11] 9.1.7-1 ii libgck-1-0 3.8.2-4 ii libgcr-base-3-1 3.8.2-4 ii libgdk-pixbuf2.0-0 2.28.2-1 ii
Bug#726625: gnome-shell: media-keys plugin not working; JS ERROR
Package: gnome-shell Version: 3.8.4-4 Severity: important Dear Maintainer, None of the keybindings associated with the media-keys plugin are working and the plugin itself seems to be crashing with the following error: JS ERROR: !!! Exception was: Error: Expected type utf8 for Argument 'accelerator' but got type 'object' 0x7f97bc3565d8 JS ERROR: !!! message = 'Expected type utf8 for Argument 'accelerator' but got type 'object' 0x7f97bc3565d8' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/shellDBus.js' JS ERROR: !!! lineNumber = '184' JS ERROR: !!! stack = '([object Array],4294967295,:1.11)@/usr/share/gnome-shell/js/ui/shellDBus.js:184 wrapper([objectArray],4294967295,:1.11)@/usr/share/gjs-1.0/lang.js:213 ([object Array],[objectGObject_Object])@/usr/share/gnome-shell/js/ui/shellDBus.js:152 wrapper([object Array],[objectGObject_Object])@/usr/share/gjs-1.0/lang.js:213 _handleMethodCall([object GObject_Boxed],[object GObject_Object],GrabAccelerators,[object GObject_Boxed],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:315 ([object GObject_Object],GrabAccelerators,[object GObject_Boxed],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:346 ' Shortly after this error another one further indicates an issue: (gnome-settings-daemon:16637): media-keys-plugin-WARNING **: 24: Timeout was reached This may be related to #726624, since both seem to be related to API issues (wrong argument types), but this is of course a very superficial interpretation Cheers PS.: severity:important because I consider not being able to use many of my keybindings a major usability effect for a desktop environment. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1 ii evolution-data-server3.8.5-2 ii gdm3 3.8.4-2 ii gir1.2-accountsservice-1.0 0.6.34-2 ii gir1.2-caribou-1.0 0.4.12-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-freedesktop 1.36.0-2+b1 ii gir1.2-gcr-3 3.8.2-4 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.03.8.1-2 ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-gtk-3.0 3.8.5-1 ii gir1.2-ibus-1.0 1.5.3-7 ii gir1.2-mutter-3.03.8.4-2 ii gir1.2-networkmanager-1.00.9.8.0-5 ii gir1.2-nmgtk-1.0 0.9.8.4-1 ii gir1.2-pango-1.0 1.32.5-5+b1 ii gir1.2-polkit-1.00.105-4 ii gir1.2-soup-2.4 2.42.2-6 ii gir1.2-telepathyglib-0.120.22.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-2 ii gir1.2-upowerglib-1.00.9.22-1 ii gjs 1.36.1-2 ii gnome-bluetooth 3.8.1-2 ii gnome-icon-theme-symbolic3.8.2.2-2 ii gnome-settings-daemon3.8.5-2 ii gnome-shell-common 3.8.4-4 ii gnome-themes-standard3.8.4-1 ii gsettings-desktop-schemas3.8.2-2 ii libatk-bridge2.0-0 2.10.0-1 ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcamel-1.2-43 3.8.5-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.14.4-3 ii libcogl-pango12 1.14.0-3 ii libcogl121.14.0-3 ii libcroco30.6.8-2 ii libdbus-1-3 1.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libecal-1.2-15 3.8.5-2 ii libedataserver-1.2-173.8.5-2 ii libegl1-mesa [libegl1-x11] 9.1.7-1 ii libgck-1-0 3.8.2-4 ii libgcr-base-3-1 3.8.2-4 ii
Bug#726587: vpb-driver: config.guess/config.sub out of date for arm64
On Thu, Oct 17, 2013 at 11:48:46AM +0100, Colin Watson wrote: On Thu, Oct 17, 2013 at 08:46:27PM +1030, Ron wrote: I'm not unsympathetic to the work and pain of porters bootstrapping a new arch, but any 'solution' that is Debian-specific, isn't really a solution at all, it's just an SEP field. There are other distributions who update config.guess/config.sub in their packaging too. I would say that *both* upstream and distributions need to handle this, realistically; but I don't think the lack of upstream handling it should hold back distributions. Sure, but there was no lack of upstream handling it here. I can only speak of what is optimal for _this_ particular package, and knowing about this sooner rather than later is definitely the global optimum in this case, regardless of who spots it first. There is no one-size-fits-all answer here that doesn't just push the very same problem onto somebody else. I don't really want to trot out the old we will not hide problems chestnut, but reporting upstream issues to upstream is one of the clear hallmarks of being a good and effective downstream user. If you really want to fix this for new ports, maybe we need a tool to scan the archives and report these things before they become the bottleneck for porting work. That just moves the manual work earlier (filing bugs, discussing them with maintainers, and NMUing when they ignore them is still quite a bit of manual work when you compare it with having all the packages just update themselves automatically); it isn't a fix. If there was no manual work needed for porting, then we wouldn't need porters. This isn't much different from other toolchain updates. If nobody reports the problem it will never get noticed to be fixed. Which means someone else will hit it and still have to do the same work. The distro is a perfect place for automated scanning of this sort of thing, and automated filing of reports if the check is sufficiently certain, and the need for a fix is sufficiently necessary. In this case, you haven't been ignored, you got a response within a few hours, and would have had a fix just as fast if it wasn't actually a false positive related to the way you 'manually' did this check. Lintian does already have a too old check -- but it doesn't actually bark about what would _really_ break (which 90% of the time is something utterly obscure that Debian won't run on anyway). Um, well. As a point of information: Tag: outdated-autotools-helper-file Severity: normal Certainty: possible Info: The referenced file has a time stamp older than April of 2012 and the package does not build-depend on autotools-dev or automake and therefore apparently does not update it. This usually means that the source package will not build correctly on ARM64, for which a Debian port is currently in progress, and may not support other newer architectures. Ah, I stand (happily) corrected :) I'd have sworn the previous time I looked at these they mostly turned out to be false positives. But this is one of those cases where I'm quite glad if I'm mistaken. Of course I wouldn't have seen this warning on the last upload, because this package didn't have that problem. Lintian's threshold is generally only updated when there's a specific relevant new port. It helps, but it's not good enough since many of the problematic packages simply aren't uploaded at all often enough so their maintainers tend not to notice; and I fundamentally disagree that let's source-upload half the archive is a sensible way to handle new ports, even if those uploads are spread out. Not enough people garden their pages on lintian.debian.org routinely enough for this not to be a horrendous pain for porters, and we still have the problem of MIA maintainers. Yes, it's true that some packages require manual porting, but those are statistically rare and often have other indicators (e.g. a specific limitation in their Architecture field). Which is why I suggested maybe it could be used to actually file bug reports, well before they become 'important' blockers for porting work. Just like other toolchain updates do. In this case, a properly automated check would _not_ have had a false positive on this package, and would have saved us both time. And you could have known about it much more easily than attempting a build and waiting for it to fail. Anyhow, I'll close this one if you've confirmed the current package is ok, but I don't want you to think I don't care about your pain. On the contrary, I think we need a _better_ solution than what this patch does to lay the groundwork for common problems seen when porting new arches, and I'm pretty sure that for this specific problem, lintian already implements 99% of what you'd need. I'm a Lintian committer, albeit a somewhat dormant one; I respectfully disagree that it can ever deal with this problem adequately. Still, at least some
Bug#726625: gnome-shell: media-keys plugin not working; JS ERROR
Am 17.10.2013 14:01, schrieb Leo Antunes: Package: gnome-shell Version: 3.8.4-4 Severity: important Dear Maintainer, None of the keybindings associated with the media-keys plugin are working and the plugin itself seems to be crashing with the following error: JS ERROR: !!! Exception was: Error: Expected type utf8 for Argument 'accelerator' but got type 'object' 0x7f97bc3565d8 JS ERROR: !!! message = 'Expected type utf8 for Argument 'accelerator' but got type 'object' 0x7f97bc3565d8' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/shellDBus.js' JS ERROR: !!! lineNumber = '184' JS ERROR: !!! stack = '([object Array],4294967295,:1.11)@/usr/share/gnome-shell/js/ui/shellDBus.js:184 wrapper([objectArray],4294967295,:1.11)@/usr/share/gjs-1.0/lang.js:213 ([object Array],[objectGObject_Object])@/usr/share/gnome-shell/js/ui/shellDBus.js:152 wrapper([object Array],[objectGObject_Object])@/usr/share/gjs-1.0/lang.js:213 _handleMethodCall([object GObject_Boxed],[object GObject_Object],GrabAccelerators,[object GObject_Boxed],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:315 ([object GObject_Object],GrabAccelerators,[object GObject_Boxed],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:346 ' Shortly after this error another one further indicates an issue: (gnome-settings-daemon:16637): media-keys-plugin-WARNING **: 24: Timeout was reached This may be related to #726624, since both seem to be related to API issues (wrong argument types), but this is of course a very superficial interpretation Not reproducible here. Does the problem persist if you reboot your system or if you use a fresh user account? -- 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#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Hi
I have a very similar problem, adding it here as it seems to have the same
origin. As mentioned by Petter, 1.86 introduced the follwoing change:
grub-installer (1.86) unstable; urgency=low
[ Vincent McIntyre ]
* Support menu selection of GRUB boot disk. Closes: #706112
-- Cyril Brulebois k...@debian.org Mon, 29 Apr 2013 13:53:27 +0200
I used to have a small preseed file and a virt-install invocation
like, described by Guido here, doing a net install:
http://honk.sigxcpu.org/con/Preseeding_Debian_virtual_machines_with_virt_install.html
virt-install --connect=qemu:///system \
--location=http://ftp.us.debian.org/debian/dists/unstable/main/installer\-amd64
\
--initrd-inject=${HOME}/virt/d-i/preseed.cfg \
--extra-args=auto keymap=us hostname=${NAME}
netcfg/get_ipaddress=${IP} suite=${SUITE} -- console=tty0
console=ttyS0,115200n8 \
--name $NAME \
--ram=$RAM \
--disk=pool=default,size=${DISKSIZE},format=qcow2,bus=virtio,cache=writeback
beeing able to quickly do tests in newly created vms, the preeseed.cfg
look like:
cut-cut-cut-cut-cut-cut-
d-i debian-installer/language string en
d-i debian-installer/country string US
d-i debian-installer/locale string en_US.UTF-8
d-i keymapselect us
d-i netcfg/choose_interface select auto
d-i netcfg/disable_autoconfig boolean true
d-i netcfg/get_netmask string 255.255.255.0
d-i netcfg/get_gateway string 192.168.122.1
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/get_nameservers string 192.168.122.1
d-i netcfg/confirm_static boolean true
d-i mirror/countrystring manual
d-i mirror/http/hostname string cdn.debian.net
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string
d-i passwd/make-user boolean false
d-i passwd/root-password password r00tme
d-i passwd/root-password-again password r00tme
d-i time/zone string US/Eastern
d-i clock-setup/utc boolean true
d-i clock-setup/ntp boolean true
d-i partman-auto/method string regular
#d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
tasksel tasksel/first multiselect
d-i pkgsel/include string openssh-server
d-i pkgsel/upgrade select full-upgrade
popularity-contest popularity-contest/participate boolean false
d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean true
d-i finish-install/reboot_in_progress note
cut-cut-cut-cut-cut-cut-
It happens with both
d-i partman-auto/method string lvm
or
d-i partman-auto/method string regular
The installer stops at the new question: [!] Install the GRUB boot
loader on a hard disk.
Interestingly it stoppend only to work for me some days ago, IIRC it
was one of the days after the wheezy point release (some installer
components where updated then, IIRC). So I don't know (yet) if one
other part of the installer updated is involved causing this.
Regards,
Salvatore
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726626: python-setuptools: Please update setuptools to version 1.x
Package: python-setuptools Version: 0.6.49-2 Severity: important Dear Maintainer, Note: I am new to asking such things in debian, so I may to doing it wrong. That said : setuptools has recently reached a 1.0 version by merging with distribute. One interesting feature, among many, is a better namespace support that is more compatible with what the latest versions of pip do. Can a version upgrade be done ? Thanks, Christophe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-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/dash Versions of packages python-setuptools depends on: ii python2.7.5-5 ii python-pkg-resources 0.6.49-2 python-setuptools recommends no packages. python-setuptools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726627: php5: segfault while loading extension
Package: php5 Version: 5.4.4-14+deb7u5 Severity: normal Tags: patch We are getting segfaults while loading extensions in the case if you have extensions deps not meet. I found the upstream commit http://git.php.net/?p=php-src.git;a=commit;h=4c6678d6058fd740a9e186b49f9daa72d09ed300 which seems to fix the issue. Seems useful to merge the fix in wheezy version. Thanks, -- William -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen p...@hungry.com (2013-06-20): Package: grub-installer Version: 1.86 Severity: important User: debian-...@lists.debian.org Usertags: debian-edu We discovered this in Debian Edu based on testing using d-i udebs from unstable. See URL: http://jenkins.debian.net/view/edu/job/g-i-installation_debian-edu_jessie_standalone/ for a automatic test of such installation. The change introduced in version 1.86 added a new question in Debian Installer, causing the installation to hang at the end asking where to install grub. This used to work automatically, but now require people to fill in a value, and [enter] do not work. Not in every case, that's why the question was added in the first place! I haven't looked whether one can preseed it like other questions. If it isn't possible, that should be fixed. (Why you're using unstable udebs for a wheezy-based debian-edu isn't obvious to me, by the way.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#726628: autopostgresqlbackup: Please source OPT from defaults
Package: autopostgresqlbackup Version: 1.0-3 Severity: normal Tags: patch Hi, controlling the restore functionality from the backup files I encountered several databases, that couldn't be restored correctly from the sql files. I have to use the custom format of pg_dump to be able to backup and restore those files. When I wanted to configure this it turned out that the OPT-variable in the script is created after sourcing the default configuration file. Attached patches move the source entry to the correct place and add the option to defaults. Please consider to add those patches to the package. Thanks, Mathias -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/bash --- autopostgresqlbackup.old 2013-09-24 19:25:00.0 +0200 +++ autopostgresqlbackup 2013-10-17 02:28:17.0 +0200 @@ -99,14 +99,6 @@ # Command run after backups (uncomment to use) #POSTBACKUP=/etc/postgresql-backup-post -# === -# === Debian specific options === -# - -if [ -f /etc/default/autopostgresqlbackup ]; then - . /etc/default/autopostgresqlbackup -fi - #= # Options documentation #= @@ -269,6 +261,14 @@ BACKUPFILES= OPT= # OPT string for use with pg_dump ( see man pg_dump ) +# === +# === Debian specific options === +# + +if [ -f /etc/default/autopostgresqlbackup ]; then + . /etc/default/autopostgresqlbackup +fi + # Add --compress pg_dump option to $OPT if [ $COMMCOMP -gt 0 ]; then --- autopostgresqlbackup.old 2013-09-23 22:24:00.0 +0200 +++ autopostgresqlbackup.default 2013-10-17 14:16:21.027339521 +0200 @@ -86,3 +86,5 @@ # Command run after backups (uncomment to use) #POSTBACKUP=/etc/postgresql-backup-post +# OPT string for use with pg_dump ( see man pg_dump ) +OPT=
Bug#726629: qemu-utils: please support qemu-img option preallocation=full for qcow2
Package: qemu-utils Version: 1.6.0+dfsg-2 Severity: wishlist Hi, some other distros have preallocation=full option for qemu-img qcow2 format, somehow Debian (even sid) doesn’t. Please add it, because this is needed in order to not overcommit the available VM backing store space when one is unable to directly use LVs for storage. Thanks! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (100, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Versions of packages qemu-utils depends on: ii libaio1 0.3.109-4 ii libc62.17-93 ii libcurl3-gnutls 7.33.0-1 ii libglib2.0-0 2.36.4-1 ii libiscsi11.4.0-3 ii libssh2-11.4.3-1 ii libuuid1 2.20.1-5.5 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages qemu-utils recommends: ii sharutils 1:4.13.5-1 Versions of packages qemu-utils suggests: ii debootstrap 1.0.53 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726630: autopostgresqlbackup: Please make file extension of backup files configurable
Package: autopostgresqlbackup Version: 1.0-3 Severity: wishlist Tags: upstream Hi, when using a backup format different from sql, the file extension of the backup files are somewhat misleading. It would be nice to be able to configure this extension (e.g. dump instead of sql). Thanks for considering, Mathias -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587187: Any progress on thsi one?
Hi. I just noticed the missing MIME entry. Is there any progress on thsi simple bug? Its rather old. -- Regards, Mario Lang Graz University of Technologymailto:ml...@tugraz.at Department Computing http://www.ZID.TUGraz.at/lang/ Phone: +43 (0) 316 / 873 - 6897 // /_Apparently a teacher has been arrested in the UK in possession_/ /of a compass, protractor, and straight edge. It is claimed he is a/ /member of the Al Gebra movement, bearing weapons of math instruction/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726631: vinagre: Please add spice support
Package: vinagre Version: 3.8.3-1 Severity: wishlist The package 'libspice-client-gtk-3.0-dev' should be added to Build-Depends. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-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/bash Versions of packages vinagre depends on: ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1 ii libavahi-common3 0.6.31-2 ii libavahi-gobject00.6.31-2 ii libavahi-ui-gtk3-0 0.6.31-2 ii libc62.17-93 ii libcairo21.12.16-2 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.38.0-1 ii libgtk-3-0 3.10.1-1 ii libgtk-vnc-2.0-0 0.5.2-2 ii libsecret-1-00.15-2 ii libtelepathy-glib0 0.22.0-1 ii libvte-2.90-91:0.34.8-1 ii libxml2 2.9.1+dfsg1-3 Versions of packages vinagre recommends: ii gnome-icon-theme 3.8.3-1 ii rdesktop 1.7.1-1 vinagre suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706746: vm-bonus-el: fails to install: ERROR: install script from vm-bonus-el package failed
Followup-For: Bug #706746 The problem was not fixed in the most recent upload: Selecting previously unselected package vm-bonus-el. (Reading database ... 14281 files and directories currently installed.) Unpacking vm-bonus-el (from .../vm-bonus-el_35.6_all.deb) ... Setting up vm-bonus-el (35.6) ... given is experimental at /usr/lib/emacsen-common/emacs-package-install line 43. when is experimental at /usr/lib/emacsen-common/emacs-package-install line 45. when is experimental at /usr/lib/emacsen-common/emacs-package-install line 46. Install vm for emacs install/vm: Ignoring emacsen flavor emacs. Install vm for emacs24 install/vm: Byte-compiling for emacs24...vm files already compiled in /usr/share/emacs24/site-lisp/vm. Install vm-bonus-el for emacs Install vm-bonus-el for emacs24 install/vm-bonus-el: Handling emacs24, logged in /tmp/elc_Sh2uJt.log ERROR: install script from vm-bonus-el package failed dpkg: error processing vm-bonus-el (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: vm-bonus-el The logfile in /tmp contains: emacs24 -q -no-site-file --no-site-file -batch -l path.el -f batch-byte-compile vm-bogofilter.el In toplevel form: vm-bogofilter.el:189:30:Error: Symbol's function definition is void: eval-when Andreas vm-bonus-el_35.6.log.gz Description: GNU Zip compressed data
Bug#726632: RFS: tintii/2.8.0-1 [Updated package]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package tintii * Package name: tintii * Version : 2.8.0-1 * Upstream Author : Lawrence Murray * URL : http://www.indii.org/software/tintii/ * License : GPL-2.0 Section : graphics It builds those binary packages: tintii - Turns colour photos into b/w and highlights regions in colour To access further information about this package, please visit the following URL: http://mentors.debian.net/package/tintii Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/t/tintii/tintii_2.8.0-1.dsc More information about hello can be obtained from http://www.indii.org/software/tintii/. Changes since the last upload: * New upstream release. * debian/control + Adjust B-D according boost transitions. Regards, Daniel Echeverry -- Daniel Echeverry http://wiki.debian.org/DanielEcheverry Linux user: #477840 Debian user Software libre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726625: gnome-shell: media-keys plugin not working; JS ERROR
Hi, [since the package is team-maintained, should I cc you in replies?] On 17/10/13 14:11, Michael Biebl wrote: Not reproducible here. Does the problem persist if you reboot your system or if you use a fresh user account? Also happens in a freshly created account. I've attached the .xsession-errors from this new account, maybe there's more context to it and I'm not seeing it. You'll notice I only logged in, opened dconf-editor to make sure the keybindings where set, tried a Ctrl-Alt-Del (seemed like an appropriate one to test) and nothing happened. The logout was performed via menu item. Is there any more debugging info I could send? Cheers -- Leo costela Antunes [insert a witty retort here] Xsession: X session started for test at Thu 17 Oct 14:27:14 CEST 2013 localuser:test being added to access control list Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. ** (gnome-session-check-accelerated:21047): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** (gnome-session:20973): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** (gnome-settings-daemon:21054): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. W: [pulseaudio] authkey.c: Failed to open cookie file '/home/test/.config/pulse/cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to load authorization key '/home/test/.config/pulse/cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to open cookie file '/home/test/.pulse-cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to load authorization key '/home/test/.pulse-cookie': No such file or directory GNOME_KEYRING_CONTROL=/run/user/1003/keyring-97Qwee GNOME_KEYRING_CONTROL=/run/user/1003/keyring-97Qwee GPG_AGENT_INFO=/run/user/1003/keyring-97Qwee/gpg:0:1 GNOME_KEYRING_CONTROL=/run/user/1003/keyring-97Qwee GPG_AGENT_INFO=/run/user/1003/keyring-97Qwee/gpg:0:1 SSH_AUTH_SOCK=/run/user/1003/keyring-97Qwee/ssh GNOME_KEYRING_CONTROL=/run/user/1003/keyring-97Qwee GPG_AGENT_INFO=/run/user/1003/keyring-97Qwee/gpg:0:1 ** (gnome-shell:21158): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. JS LOG: GNOME Shell started at Thu Oct 17 2013 14:27:16 GMT+0200 (CEST) Creating config directory:'/home/test/.config/tracker' Tracker-Message: Importing config file to GSettings Tracker-Message: Importing config file to GSettings ** (smart-notifier:21218): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. JS ERROR: !!! Exception was: TypeError: arguments[0] is null JS ERROR: !!! message = 'arguments[0] is null' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/components/autorunManager.js' JS ERROR: !!! lineNumber = '131' JS ERROR: !!! stack = '(null,[object GLib_Error])@/usr/share/gnome-shell/js/ui/components/autorunManager.js:131 ([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:87 ' JS ERROR: !!! Exception was: Error: Expected type utf8 for Argument 'str' but got type 'object' 0x7fad5318a2c0 JS ERROR: !!! message = 'Expected type utf8 for Argument 'str' but got type 'object' 0x7fad5318a2c0' JS ERROR: !!! fileName = '/usr/share/gnome-shell/js/ui/status/power.js' JS ERROR: !!! lineNumber = '157' JS ERROR: !!! stack = '()@/usr/share/gnome-shell/js/ui/status/power.js:157 wrapper()@/usr/share/gjs-1.0/lang.js:213 ()@/usr/share/gnome-shell/js/ui/status/power.js:166 wrapper()@/usr/share/gjs-1.0/lang.js:213 ([object GObject_Object],null)@/usr/share/gnome-shell/js/ui/status/power.js:65 ([object GObject_Object],[object GObject_Object])@/usr/share/gjs-1.0/overrides/Gio.js:203 ' Window manager warning: Log level 16: invalid cast from `NMRemoteConnection' to `NMObject' Window manager warning: Log level
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
[Cyril Brulebois] Not in every case, that's why the question was added in the first place! How often was the old default wrong? If it was rare, perhaps the question should only show up in expert installs (ie use priority low)? (Why you're using unstable udebs for a wheezy-based debian-edu isn't obvious to me, by the way.) I was tested using Jessie/testing when I discovered this. I did not experience it with Wheezy when I tested it a while back. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726629: qemu-utils: please support qemu-img option preallocation=full for qcow2
Control: tag -1 + wontfix 17.10.2013 16:31, Thorsten Glaser wrote: Package: qemu-utils Version: 1.6.0+dfsg-2 Severity: wishlist Hi, some other distros have preallocation=full option for qemu-img Which other distros? qcow2 format, somehow Debian (even sid) doesn’t. Please add it, because this is needed in order to not overcommit the available VM backing store space when one is unable to directly use LVs for storage. I don't plan to apply feature patches to upstream qemu. Only fixes please. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726633: php5: (un)serialize() leaves dangling pointers, causes crashes
Package: php5 Version: 5.4.4-14+deb7u5 Severity: normal Tags: patch We are impacted by the upstream bug https://bugs.php.net/63369 (un)serialize() leaves dangling pointers, causes crashes upstream fix: http://git.php.net/?p=php-src.git;a=commit;h=f2bffdc2e48174e38a059d425953e8b1c08dd4bf more than useful to merge it in wheezy version since that the common use in PHP to use serialize/unserialize functions. Thanks, -- William -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726619: [Openstack-devel] Bug#726619: Debian cloud image built with openstack-debian-images shows no output in the log tab of Horizon
On 10/17/2013 06:02 PM, Jordan Pittier wrote: Package: openstack-debian-images Version: 0.4 I've built a Debian Wheezy cloud image using openstack-debian-images. When I instanciate it, it works as expected. But the log tab in OpenStack Dashboard shows no output. I'd like to have the output of the console/tty also displayed in this tab. The ubuntu cloud archive image can be used as an example. Thanks, Jordan Hi, As much as I know, it does work. I had the console working (using spice-html5). Though nova console-log doesn't. In fact, the problem is that you can't have both of them (eg: the tty1 in the dashboard, and the console log). Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726634: O: portalocker
Package: wnpp Severity: normal Hi, due to the lack of time and interest, I orphan portalocker. Package's description follows: Description: portalocker - easy API to file locking (Python 2) Portalocker is a cross-platform library to provide an easy API to file locking. . This is the Python 2 version of the package. Cheers, -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen p...@hungry.com (2013-10-17): [Cyril Brulebois] Not in every case, that's why the question was added in the first place! How often was the old default wrong? If it was rare, perhaps the question should only show up in expert installs (ie use priority low)? More or less everytime the install medium was a USB stick. Mraw, KiBi. signature.asc Description: Digital signature
Bug#726631: vinagre: Please add spice support
Am 17.10.2013 14:34, schrieb Dani Chaves: Package: vinagre Version: 3.8.3-1 Severity: wishlist The package 'libspice-client-gtk-3.0-dev' should be added to Build-Depends. That package is only available on i386 and amd64. So if we enable spice support, this b-dep needs to be arch-qualified. Michael -- 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#726636: [l10n:eu] strongswan 5.1.0-1: updated Basque translation
Package: strongswan Version: 5.1.0-1 X-Debbugs-CC: debian-l10n-bas...@lists.debian.org Severity: wishlist Tags: l10n patch Attached Basque translation. Please, could you add it for us? Thanks and best regards, Dooteo # translation of strongswan_4.4.1-5.1_eu.po to Basque # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # # Piarres Beobide p...@beobide.net, 2009. # Iñaki Larrañaga Murgoitio doo...@zundan.com, 2010, 2013. msgid msgstr Project-Id-Version: strongswan_4.4.1-5.1_eu\n Report-Msgid-Bugs-To: strongs...@packages.debian.org\n POT-Creation-Date: 2013-02-07 13:28+0100\n PO-Revision-Date: 2013-10-15 21:41+0200\n Last-Translator: Iñaki Larrañaga Murgoitio doo...@zundan.com\n Language-Team: Basque librez...@librezale.org\n Language: eu\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=2; plural=(n != 1);\n X-Generator: Lokalize 1.4\n #. Type: note #. Description #: ../strongswan-starter.templates:2001 msgid Old runlevel management superseded msgstr Exekuzio-mailaren kudeaketa zaharra ordeztuta #. Type: note #. Description #: ../strongswan-starter.templates:2001 msgid Previous versions of the strongSwan package gave a choice between three different Start/Stop-Levels. Due to changes in the standard system startup procedure, this is no longer necessary or useful. For all new installations as well as old ones running in any of the predefined modes, sane default levels will now be set. If you are upgrading from a previous version and changed your strongSwan startup parameters, then please take a look at NEWS. Debian for instructions on how to modify your setup accordingly. msgstr strongSwan paketearen aurreko bertsioak hiru Abiarazte-/Gelditzen-maila desberdinen arteko aukera eskaintzen zuen. Sistemaren abioaren prozedura arruntean aldaketak gertatu direnez, ez dira beharrezkoak edo erabilgarriak. Instalazio berri guztientzako, aurredefinitutako moduetako batean exekutatzen diren zaharretan ere, zentzuzko maila lehenetsiak ezarriko dira orain. Aurreko bertsiotik eguneratzen ari bazara, eta strongSwan-en abioko parametroak aldatu bazenituen, irakur ezazu NEWS.Debian fitxategia. konfigurazioa modu egokian nola aldatzen den jakiteko. #. Type: boolean #. Description #: ../strongswan-starter.templates:3001 msgid Restart strongSwan now? msgstr Berrabiarazi StrongSwan orain? #. Type: boolean #. Description #: ../strongswan-starter.templates:3001 msgid Restarting strongSwan is recommended, since if there is a security fix, it will not be applied until the daemon restarts. Most people expect the daemon to restart, so this is generally a good idea. However, this might take down existing connections and then bring them back up, so if you are using such a strongSwan tunnel to connect for this update, restarting is not recommended. msgstr StrongSwan berrabiaraztea gomendatzen da segurtasunezko konponketa bat badago ez baita ezarriko daemona berrabiarazi artea. Erabiltzaile gehienek daemona berrabiaraztea espero dutenez, burutazio ona da hori. Hala ere, honek martxan dauden konexioak itxi eta gero berriz abiaraziko ditu. Hori dela eta, eguneraketa honetan strongSwan tunela erabiltzen ari bazara, ez da gomendatzen berrabiaraztea. #. Type: boolean #. Description #: ../strongswan-starter.templates:4001 #| msgid Start strongSwan's IKEv1 daemon? msgid Start strongSwan's charon daemon? msgstr Abiarazi StrongSwan-ren 'charon' daemona abiarazi? #. Type: boolean #. Description #: ../strongswan-starter.templates:4001 #| msgid #| The charon daemon must be running to support version 2 of the Internet #| Key Exchange protocol. msgid The charon daemon must be running to support the Internet Key Exchange protocol. msgstr 'charon' daemona exekutatzen egon behar da Interneteko Gakoen Trukaketa (IKE) protokoloa onartzeko. #. Type: boolean #. Description #: ../strongswan-starter.templates:5001 msgid Use an X.509 certificate for this host? msgstr X.509 ziurtagiria erabili ostalari honentzako? #. Type: boolean #. Description #: ../strongswan-starter.templates:5001 msgid An X.509 certificate for this host can be automatically created or imported. It can be used to authenticate IPsec connections to other hosts and is the preferred way of building up secure IPsec connections. The other possibility would be to use shared secrets (passwords that are the same on both sides of the tunnel) for authenticating a connection, but for a larger number of connections, key based authentication is easier to administer and more secure. msgstr Ostalari honentzako X.509 ziurtagiri bat automatikoki sor edo inportatu daiteke. Beste ostalariekin IPsec bidez konektatzean autentifikatzeko erabili daiteke, eta hobetsitako bidea da IPsec konexio seguruak eraikitzeko. Beste aukera bat ezkutukoak (tunelaren bi aldeetan berdinak diren pasahitzak) partekatzea litzateke
Bug#725461: batik: FTBFS: Unable to find a javac compiler
Hi, [currently at a congress, hence not very on top of Debian things] On Wed, Oct 16, 2013 at 8:28 PM, Markus Koschany a...@gambaru.de wrote: The current svn revision still recommends default-jre because of the included wrapper scripts squiggle, rasterizer, ttf2svg and svgpp. The recommendation for default-jre is the only thing that bothers me. The current dependencies on jre-headless go against the current java policy but the current package also needs a working JRE to run the aforementioned wrapper scripts. I think recommending default-jre is a kind of compromise here. Excatly... I agree with Emmanuel Bourg's comment from the list that it is more reasonable to split the package in libbatik-java and batik. I have done this locally and all reverse dependencies (except osmosis that FTBFS because of another bug) still build fine. Though I'm not 100% sure if one of those r-deps expects one of the wrapper scripts to be included in libbatik-java, otherwise it would be simple. This is the sensible thing to do, and one I should have done ages ago, but evaluating the impact on rdeps/build-rdeps is far from trivial, so this is not a change to be acted too lightly -- and one of the reasons why I refrained from doing so, mostly because I didn't have the time to look. Hence I think uploading the current changes would be a good idea and I will attach a patch for #566901 soon. I don't have the time to review the patch right now. I can have a look this week-end, if you want more eyes, but if you feel confident about the current state, I don't mind an upload as-is. Cheers, and sorry for the lack of timely feedback. Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726613: mercurial wheezy backport has incorrect libc6 dependency
Control: reopen -1 2013/10/17 Javi Merino vi...@debian.org: 2013/10/17 Faheem Mitha fah...@faheem.info: Package: mercurial Version: 2.7.2-1~bpo70+1 Severity: normal Currently, I see the mercurial wheezy backport is 2.7.2-1~bpo70+1 0 100 http://debian.lcs.mit.edu/debian/ wheezy-backports/main amd64 Packages and `apt-cache show` gives Package: mercurial Version: 2.7.2-1~bpo70+1 Installed-Size: 236 Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Architecture: amd64 Depends: libc6 (= 2.14), python (= 2.7), python ( 2.8), ucf (= 2.0020), mercurial-common (= 2.7.2-1~bpo70+1) The version in the archive depends on libc6 (= 2.4) except for armhf, ia64, kfreebsd-amd64, kfreebsd-i386, s390x and sparc: http://packages.debian.org/wheezy-backports/mercurial Your mirror is tampering with the package: $ wget -q http://http.us.debian.org/debian/pool/main/m/mercurial/mercurial_2.7.1-2~bpo70+1_i386.deb -O - | sha1sum b93368a34adf0852520c31e2778dd07b4f43460d - $ wget -q http://ftp.es.debian.org/debian/pool/main/m/mercurial/mercurial_2.7.1-2~bpo70+1_i386.deb -O - | sha1sum b93368a34adf0852520c31e2778dd07b4f43460d - $ wget -q http://debian.lcs.mit.edu/debian/pool/main/m/mercurial/mercurial_2.7.1-2~bpo70+1_amd64.deb -O - | sha1sum 58035bc1d33f36a3742ca50ae835e7a9404434b2 - $ Erm this is wrong, I downloaded the i386 version from the official mirrors which obviously has a different sha1sum. You're right, looks like I didn't build it in a wheezy chroot and that's why it got the wrong dependencies. I'll request a binnmu. Sorry for that, Javi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726637: conky: please enable ALSA support
Package: conky Version: 1.9.0-3 Severity: wishlist Please build conky with ALSA support. It's the only package on my system that still requires OSS compatibility. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages conky depends on: ii conky-std 1.9.0-3 conky recommends no packages. conky suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725546: numptyphysics: FTBFS: configure.in:6: error: required file './compile' not found
Control: tags -1 +patch
Hi,
Attached patch would fix this FTBFS, could you consider to apply it,
please?
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru numptyphysics-0.2+svn156/debian/changelog numptyphysics-0.2+svn156/debian/changelog
--- numptyphysics-0.2+svn156/debian/changelog 2012-05-11 07:18:16.0 +0900
+++ numptyphysics-0.2+svn156/debian/changelog 2013-10-17 12:11:42.0 +0900
@@ -1,3 +1,11 @@
+numptyphysics (0.2+svn156-1.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/rules
+- add -fi option to autoreconf (Closes: #725546)
+
+ -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 12:09:55 +0900
+
numptyphysics (0.2+svn156-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru numptyphysics-0.2+svn156/debian/rules numptyphysics-0.2+svn156/debian/rules
--- numptyphysics-0.2+svn156/debian/rules 2010-01-24 05:37:59.0 +0900
+++ numptyphysics-0.2+svn156/debian/rules 2013-10-17 11:51:18.0 +0900
@@ -14,7 +14,7 @@
dh $@
override_dh_auto_configure:
- autoreconf
+ autoreconf -fi
dh_auto_configure -- --bindir=\$${prefix}/games
#override_dh_installchangelogs:
Bug#725569: libpam-unix2: FTBFS: configure.in:36: error: required file './compile' not found
Control: tags -1 +patch
Hi,
Attached patch would fix this FTBFS, could you consider to apply it,
please?
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru libpam-unix2-2.6/debian/changelog libpam-unix2-2.6/debian/changelog
--- libpam-unix2-2.6/debian/changelog 2013-07-03 03:18:17.0 +0900
+++ libpam-unix2-2.6/debian/changelog 2013-10-17 10:58:58.0 +0900
@@ -1,3 +1,15 @@
+libpam-unix2 (1:2.6-2) unstable; urgency=low
+
+ * QA upload.
+ * debian/rules
+- add -i option to autoreconf (Closes: #725569)
+ * debian/control
+- add Build-Depends: autopoint as above change
+ * debian/patches
+- add specify-gettext-version.patch
+
+ -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 10:55:57 +0900
+
libpam-unix2 (1:2.6-1) unstable; urgency=low
* QA upload.
diff -Nru libpam-unix2-2.6/debian/control libpam-unix2-2.6/debian/control
--- libpam-unix2-2.6/debian/control 2013-07-01 17:17:58.0 +0900
+++ libpam-unix2-2.6/debian/control 2013-10-17 10:47:31.0 +0900
@@ -4,7 +4,7 @@
Maintainer: Debian QA Group packa...@qa.debian.org
Build-Depends: debhelper (= 7), dpkg-dev (= 1.15.7),
libpam0g-dev (= 0.81),
- autoconf, automake,
+ autoconf, automake, autopoint,
libxcrypt-dev (= 1:2.4), libxcrypt-dev ( 1:3.0)
Build-Conflicts: libxcrypt2
Standards-Version: 3.9.3
diff -Nru libpam-unix2-2.6/debian/patches/series libpam-unix2-2.6/debian/patches/series
--- libpam-unix2-2.6/debian/patches/series 2013-07-03 02:55:20.0 +0900
+++ libpam-unix2-2.6/debian/patches/series 2013-10-17 10:51:47.0 +0900
@@ -4,3 +4,4 @@
04_typos.diff
05_glibc216.diff
06_format_security.diff
+specify-gettext-version.patch
diff -Nru libpam-unix2-2.6/debian/patches/specify-gettext-version.patch libpam-unix2-2.6/debian/patches/specify-gettext-version.patch
--- libpam-unix2-2.6/debian/patches/specify-gettext-version.patch 1970-01-01 09:00:00.0 +0900
+++ libpam-unix2-2.6/debian/patches/specify-gettext-version.patch 2013-10-17 10:52:21.0 +0900
@@ -0,0 +1,19 @@
+Description: necessary to specify gettext version
+ autopoint needs to specify gettext version in configure.in
+Author: Hideki Yamane henr...@debian.org
+
+---
+Bug-Debian: http://bugs.debian.org/bugnumber
+Last-Update: 2013-10-17
+
+--- libpam-unix2-2.6.orig/configure.in
libpam-unix2-2.6/configure.in
+@@ -93,7 +93,7 @@ else
+ LDFLAGS=${LDFLAGS} -G
+ fi
+
+-AM_GNU_GETTEXT_VERSION
++AM_GNU_GETTEXT_VERSION(0.18)
+ AM_GNU_GETTEXT([external])
+
+ AC_SUBST(LIBPAM)
diff -Nru libpam-unix2-2.6/debian/rules libpam-unix2-2.6/debian/rules
--- libpam-unix2-2.6/debian/rules 2013-07-01 17:17:58.0 +0900
+++ libpam-unix2-2.6/debian/rules 2013-10-17 10:42:57.0 +0900
@@ -16,7 +16,7 @@
config.status: configure
dh_testdir
- autoreconf -vf
+ autoreconf -vif
cp -f /usr/share/misc/config.sub config.sub
cp -f /usr/share/misc/config.guess config.guess
./configure $(confflags)
Bug#725568: mtr: FTBFS: configure.ac:13: error: required file './compile' not found
Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -u mtr-0.85/debian/changelog mtr-0.85/debian/changelog --- mtr-0.85/debian/changelog +++ mtr-0.85/debian/changelog @@ -1,3 +1,11 @@ +mtr (0.85-1.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/rules +- use autoreconf to fix FTBFS (Closes: #725568) + + -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 11:43:32 +0900 + mtr (0.85-1) unstable; urgency=low * New upstream version, closes: #706816, #717727 diff -u mtr-0.85/debian/rules mtr-0.85/debian/rules --- mtr-0.85/debian/rules +++ mtr-0.85/debian/rules @@ -26,9 +26,7 @@ touch aclocal.m4 \ touch configure - aclocal \ - automake --foreign --include-deps Makefile \ - autoconf + autoreconf -fi mkdir mtr cd mtr CFLAGS=-I.. ../configure $(shell dpkg-buildflags --export=configure /dev/null 21 dpkg-buildflags --export=configure) $(confflags) --prefix=`pwd`/debian/tmp/usr --mandir=`pwd`/debian/tmp/usr/share/man --sbindir=`pwd`/debian/tmp/usr/bin make -C mtr
Bug#725580: mecab: FTBFS: configure.in:23: error: required file './compile' not found
Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -u mecab-0.996/debian/changelog mecab-0.996/debian/changelog --- mecab-0.996/debian/changelog +++ mecab-0.996/debian/changelog @@ -1,3 +1,14 @@ +mecab (0.996-1.1) unstable; urgency=low + + [ Hideki ] + * Non-maintainer upload. + * debian/rules +- use dh-autoreconf (Closes: #725580) + * debian/control +- add Build-Depends: dh-autoreconf as above + + -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 10:35:20 +0900 + mecab (0.996-1) unstable; urgency=low * New upstream release. diff -u mecab-0.996/debian/control mecab-0.996/debian/control --- mecab-0.996/debian/control +++ mecab-0.996/debian/control @@ -2,7 +2,7 @@ Section: misc Priority: optional Maintainer: TSUCHIYA Masatoshi tsuch...@namazu.org -Build-Depends: debhelper (= 7.0.0), cdbs, libtool, automake, autoconf, quilt +Build-Depends: debhelper (= 7.0.0), cdbs, libtool, automake, autoconf, quilt, dh-autoreconf Uploaders: Taku YASUI t...@debian.org Vcs-Git: git://git.debian.org/collab-maint/mecab.git Vcs-Browser: http://git.debian.org/?p=collab-maint/mecab.git;a=summary diff -u mecab-0.996/debian/rules mecab-0.996/debian/rules --- mecab-0.996/debian/rules +++ mecab-0.996/debian/rules @@ -4,6 +4,7 @@ include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk include /usr/share/cdbs/1/rules/patchsys-quilt.mk +include /usr/share/cdbs/1/rules/autoreconf.mk LIBPACKAGE = $(shell dh_listpackages|egrep 'lib.*[0-9]') LIBFILES = debian/$(LIBPACKAGE).install
Bug#724467: revelation: FTBFS: configure.ac:14: error: required file './compile' not found
Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -Nru revelation-0.4.13/debian/changelog revelation-0.4.13/debian/changelog --- revelation-0.4.13/debian/changelog 2012-10-18 18:36:47.0 +0900 +++ revelation-0.4.13/debian/changelog 2013-10-17 13:14:44.0 +0900 @@ -1,3 +1,11 @@ +revelation (0.4.13-1.3) unstable; urgency=low + + * Non-maintainer upload. + * debian/rules +- add -fi option to autoreconf to fix FTBFS (Closes: #724467) + + -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 13:14:31 +0900 + revelation (0.4.13-1.2) unstable; urgency=high * Non-maintainer upload. diff -Nru revelation-0.4.13/debian/rules revelation-0.4.13/debian/rules --- revelation-0.4.13/debian/rules 2012-06-08 18:31:25.0 +0900 +++ revelation-0.4.13/debian/rules 2013-10-17 13:01:01.0 +0900 @@ -47,7 +47,7 @@ build-stamp: patch-stamp dh_testdir dh_clean -k - autoreconf + autoreconf -fi for py in $(PYVERS); do \ $(MAKE) -f debian/rules build-python$$py-stamp; \ done
Bug#724913: gmysqlcc: FTBFS: required file './compile' not found
Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -u gmysqlcc-0.3.0/debian/rules gmysqlcc-0.3.0/debian/rules --- gmysqlcc-0.3.0/debian/rules +++ gmysqlcc-0.3.0/debian/rules @@ -32,7 +32,7 @@ build-stamp: config.status $(QUILT_STAMPFN) dh_testdir - autoreconf + autoreconf -fi $(MAKE) touch $@ diff -u gmysqlcc-0.3.0/debian/changelog gmysqlcc-0.3.0/debian/changelog --- gmysqlcc-0.3.0/debian/changelog +++ gmysqlcc-0.3.0/debian/changelog @@ -1,3 +1,11 @@ +gmysqlcc (0.3.0-2.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/rules +- add -fi option to autoreconf (Closes: #724913) + + -- Hideki Yamane henr...@debian.org Thu, 17 Oct 2013 12:51:32 +0900 + gmysqlcc (0.3.0-2) unstable; urgency=low * Set standards-version to 3.8.0
Bug#726571: RlwrapFilter.pm should be /usr/share/perl5/App/Rlwrap/Filter.pm
On Wed, Oct 16, 2013 at 18:56:33 +, Ivan Shmakov wrote: The conventional namespace for application-specific Perl modules is App::⟨package name⟩::⟨module name…⟩. Can you give some examples or references? I see a few but not enough that I'd call it a convention. As opposed to simply $PACKAGE::$MODULE... Moreover, the conventional directory for Perl modules is /usr/share/perl5, and indeed, – it’s already in @INC, while /usr/share/rlwrap isn’t. This is indeed required for packages that primarily provide perl libraries. However there are also many packages in Debian that install perl modules in application-specific directories when those modules are primarily for that application's use only. Therefore, my suggestion would be to move RlwrapFilter.pm from /usr/share/rlwrap to /usr/share/perl5/App/Rlwrap/Filter.pm, and edit its ‘package’ line (as well as the filters’ ‘use’ lines) respectively. (In order to preserve compatibility, a “redirecting” .pm may be installed at the former location.) This will bring the module in line with the other Perl modules in Debian, and will allow for a Perl filter to be started with simple ‘use App::Rlwrap::Filter;’ instead of the current form, which explicitly the Perl module search path (as shown below.) Do you have any other reasons for wanting to make this change, some added functionality or benefit that would come from doing this reorganization? -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725537: photoprint: FTBFS: configure.ac:12: error: required file 'scripts/compile' not found
Control: tags -1 +patch Hi, Attached patch would fix this FTBFS, could you consider to apply it, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -Nru photoprint-0.4.2~pre2/debian/changelog photoprint-0.4.2~pre2/debian/changelog --- photoprint-0.4.2~pre2/debian/changelog 2013-06-23 22:41:31.0 +0900 +++ photoprint-0.4.2~pre2/debian/changelog 2013-10-16 08:41:05.0 +0900 @@ -1,3 +1,15 @@ +photoprint (0.4.2~pre2-2.2) unstable; urgency=low + + * Non-maintainer upload. + * debian/rules +- add -fi option to autoreconf (Closes: #725537) + * debian/control +- add Build-Depends: autopoint with above change + * debian/patches +- add define_macro-dir.patch + + -- Hideki Yamane henr...@debian.org Wed, 16 Oct 2013 08:41:03 +0900 + photoprint (0.4.2~pre2-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru photoprint-0.4.2~pre2/debian/control photoprint-0.4.2~pre2/debian/control --- photoprint-0.4.2~pre2/debian/control 2011-11-13 17:40:54.0 +0900 +++ photoprint-0.4.2~pre2/debian/control 2013-10-16 08:27:28.0 +0900 @@ -2,7 +2,7 @@ Section: graphics Priority: optional Maintainer: David Stone da...@nnucomputerwhiz.com -Build-Depends: debhelper (= 7), libgtk2.0-dev, liblcms1-dev, libpng12-dev, libtiff4-dev, libnetpbm10-dev, libgutenprint-dev, chrpath, automake, libtool +Build-Depends: debhelper (= 7), libgtk2.0-dev, liblcms1-dev, libpng12-dev, libtiff4-dev, libnetpbm10-dev, libgutenprint-dev, chrpath, automake, libtool, autopoint Standards-Version: 3.9.2 Homepage: http://blackfiveimaging.co.uk/index.php?article=02Software%2F01PhotoPrint diff -Nru photoprint-0.4.2~pre2/debian/patches/define_macro-dir.patch photoprint-0.4.2~pre2/debian/patches/define_macro-dir.patch --- photoprint-0.4.2~pre2/debian/patches/define_macro-dir.patch 1970-01-01 09:00:00.0 +0900 +++ photoprint-0.4.2~pre2/debian/patches/define_macro-dir.patch 2013-10-17 22:26:12.0 +0900 @@ -0,0 +1,19 @@ +Description: necessary to define macro directory + + If we don't specify it, it causes FTBFS. + +Author: Hideki Yamane henr...@debian.org +Bug-Debian: http://bugs.debian.org/725537 +Forwarded: no +Last-Update: 2013-10-16 + +--- photoprint-0.4.2~pre2.orig/configure.ac photoprint-0.4.2~pre2/configure.ac +@@ -7,6 +7,7 @@ AC_CONFIG_AUX_DIR([scripts]) + AC_CONFIG_SRCDIR([photoprint.cpp]) + AM_CONFIG_HEADER([config.h]) + AM_INIT_AUTOMAKE([1.9 foreign]) ++AC_CONFIG_MACRO_DIR([m4]) + + AM_GNU_GETTEXT_VERSION([0.17]) + AM_GNU_GETTEXT([external]) diff -Nru photoprint-0.4.2~pre2/debian/patches/series photoprint-0.4.2~pre2/debian/patches/series --- photoprint-0.4.2~pre2/debian/patches/series 2013-06-23 22:31:39.0 +0900 +++ photoprint-0.4.2~pre2/debian/patches/series 2013-10-16 08:34:44.0 +0900 @@ -4,3 +4,4 @@ fix-spelling.patch fix-man-page-minux.patch glib-single-include.patch +define_macro-dir.patch diff -Nru photoprint-0.4.2~pre2/debian/rules photoprint-0.4.2~pre2/debian/rules --- photoprint-0.4.2~pre2/debian/rules 2011-11-13 17:40:54.0 +0900 +++ photoprint-0.4.2~pre2/debian/rules 2013-10-16 08:25:57.0 +0900 @@ -40,7 +40,7 @@ configure-stamp: dh_testdir libtoolize --copy --force - autoreconf + autoreconf -fi ./configure --prefix=/usr --disable-rpath $(confflags) touch configure-stamp
Bug#726638: xapers' curses interface fails to open file with a space in their name
Package: xapers
Version: 0.5.2-1
Severity: normal
Dear Maintainer,
I added pdf files to my xapers database that contain space (namely
.xapers/docs/000110/Di 99.pdf). Using 'xapers show id:110' then
Return to open said file gives 'ERROR: id:110: file not found'
I trace the problem to line 174 of file
/usr/lib/python2.7/dist-packages/xapers/nci/search.py which protects
spaces with '\' before passing this path to os.path.exists which fails
as ~/.xapers/docs/000110/Di\ 99.pdf does not exist... This action
should be done after that conditional but before the subprocess.call
line.
This patch solves the problem for me:
@@ -171,10 +171,11 @@
if not path:
self.ui.set_status('No file for document id:%s.' % entry.docid)
return
-path = path[0].replace(' ','\ ')
+path = path[0]
if not os.path.exists(path):
self.ui.set_status('ERROR: id:%s: file not found.' % entry.docid)
return
+path = path.replace(' ','\ ')
self.ui.set_status('opening file: %s...' % path)
subprocess.call(' '.join(['nohup', 'xdg-open', path, '']),
shell=True,
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (700, 'unstable'), (650, 'testing'), (600, 'experimental'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages xapers depends on:
ii poppler-utils 0.18.4-8
ii pybtex0.15-1
ii python2.7.5-5
ii python-pkg-resources 0.6.49-2
ii python-pycurl 7.19.0-7
ii python-xapian 1.2.15-4
Versions of packages xapers recommends:
ii python-urwid 1.1.1-1+b1
ii xclip 0.12+svn84-2
ii xdg-utils 1.1.0~rc1+git20111210-7
xapers suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668442: tucnak2: leaves alternatives after purge
Followup-For: Bug #668442 Hi, to finally get rid of the incorrect alternative handling, I've prepared a NMU and uploaded it to DELAYED/10, see the attached patch. Andreas diff -u tucnak2-2.48/debian/changelog tucnak2-2.48/debian/changelog --- tucnak2-2.48/debian/changelog +++ tucnak2-2.48/debian/changelog @@ -1,3 +1,11 @@ +tucnak2 (2.48-2.2) unstable; urgency=low + + * Non-maintainer upload. + * Merge changes from 2.47-2+deb7u1: +- Remove the correct alternative upon package removal. (Closes: #668442) + + -- Andreas Beckmann a...@debian.org Thu, 17 Oct 2013 15:27:36 +0200 + tucnak2 (2.48-2.1) unstable; urgency=low * Non-maintainer upload. @@ -23,6 +31,13 @@ -- Jaime Robles ja...@debian.org Thu, 05 Apr 2012 10:16:00 + +tucnak2 (2.47-2+deb7u1) testing; urgency=low + + * Non-maintainer upload. + * Remove the correct alternative upon package removal. (Closes: #668442) + + -- Andreas Beckmann a...@debian.org Wed, 10 Apr 2013 01:27:28 +0200 + tucnak2 (2.47-2) unstable; urgency=low * Fixed the update-alternatives. diff -u tucnak2-2.48/debian/postrm tucnak2-2.48/debian/postrm --- tucnak2-2.48/debian/postrm +++ tucnak2-2.48/debian/postrm @@ -6,9 +6,6 @@ if getent group davac4 /dev/null; then groupdel davac4 || true fi - - update-alternatives --remove tucnak /usr/bin/tucnak2 - fi [ -L /etc/udev/rules.d/025_davac4.rules ] rm /etc/udev/rules.d/025_davac4.rules diff -u tucnak2-2.48/debian/prerm tucnak2-2.48/debian/prerm --- tucnak2-2.48/debian/prerm +++ tucnak2-2.48/debian/prerm @@ -2,11 +2,7 @@ - set -e - if [ $1 = remove ] ; then - update-alternatives --remove tucnak /usr/bin/tucnak2 + update-alternatives --remove tucnak /usr/bin/tucnak fi - -#DEBHELPER# -exit 0 +#DEBHELPER#
Bug#722537: ,wordpress: CVE-2013-4338 CVE-2013-4339 CVE-2013-4340
CVE-2013-4338[0]: Unsafe PHP unserialization https://core.trac.wordpress.org/changeset/25325 It is very vague how that was a security bug. The code change doesn't actually make the default mode of is_serialized() any stricter, that is unchanged. Rather, it implements a new, more-relaxed check that can be used to prevent something being stored in MySQL which, after being truncated due to another bug, something else might be able to wrongly deserialise later... it's a very poor way to fix what is really unsafe coding all over the place. It mitigates this specific exploit though. The original researcher explains the original vulnerability here: http://vagosec.org/2013/09/wordpress-php-object-injection/ Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726403: Proxy support solution proposed for how-can-i-help
Hi, As I'm using how-can-i-help on a computer that is behind a poxy, I've made modifications that correct this bug (that is more and enhancement than a real bug). Now you can define a proxy on how-can-i-help using: - either the http_proxy (or HTTP_PROXY) environment variable - or using a --http-proxy http://myuser:mypassword@myproxy:port; switch The second one overwrites the environment variable. Note: environment variable do not have to be exported. You can also do: http_proxy=http://myuser:mypassword@myproxy:port how-can-i-help Tested with a non authenticated proxy environment. I have some friends that will test it in an authenticated one. I'm currently following the process described at https://wiki.debian.org/BSP/BeginnersHOWTO and will propose the diff upload as soon as I've finished. Regards, Joseph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724826: xcircuit: FTBFS with upcoming multiarchified Tcl/Tk
Hi! Thanks for the patch! Will apply and upload when tcl8.6 is in unstable. Roland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726538: partman-md: Should rescan for encrypted volumes on top of raid after assembling it
reassign 726538 rescue-mode retitle 726538 rescue-mode: Should scan for encrypted volumes on top of raid after assembling it found726538 rescue-mode/1.41 forcemerge 484263 726538 thanks On Wed, Oct 16, 2013 at 04:41:08PM +0200, Agustin Martin wrote: Package: partman-md Version: 67 Severity: normal Hi, maintainers, Want to share a minor inconsistency when using crypto on top of RAID, mostly related to rescue mode. First, what works and should be expected, a normal crypto volume, no RAID: * Rescue mode * After selecting time zone d-i notices there is an encrypted volume I am prompted to enter a passphrase for it if I want to have it available for rescue operations. That is the expected behavior. However things work differently when the encrypted volume is on top of a RAID (RAID1 in this case). * Rescue mode * Get the Device to use as root file system dialog, known partitions shown, no RAID is still assembled and of course nothing inside it is shown, just plain /dev/sd* stuff. * I choose Assemble RAID array, tick Automatic and proceed. * However, although a crypto volume is on top of that RAID, that seems not detected and I am not prompted for a passphrase to enable it for rescue. Of course I can open a shell, enable luks volume and the lvm logical volumes it contains, go back and continue, now with all really available choices including those inside the crypto volume. I'd expect the same check that is automaticaly done when the encrypted volume is not on top of a RAID be run right after assembling the RAID so the contents of the encrypted volume (single partion or lvm stuff) become available for the rescue session in a simpler way if the passphrase is provided. Some extra details I forgot to add. In the second case both components of the RAID are detected separately as encrypted volumes and I am asked for their (common) passphrase. If I provide it, volume contents are properly scanned (not sure which lvm stuff is shown, it is replicated in both devices, but only one is shown), but since the RAID is not assembled I'd rather not use them separately. Did not try to mount it. It is the encrypted volume on top of RAID using both devices what is not detected as crypto and so no passphrase is asked for it and not further processed. Anyway, just noticed that this has already been reported as #484263 against rescue-mode. Thus reassigning and merging, sorry for the noise. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726600: otrs2: Internal server error when replying to email ticket
Hi Patrick, On Thu, Oct 17, 2013 at 03:20:55PM +0200, Patrick Matthäi wrote: reassign #726600 libmime-tools-perl thanks Hello, could you please update libmime-tools-perl to version 5.504, it should fix this issue. We have the package ready in the Debian Perl Group repository, and will upload after a review. Did you had a chance to test that 5.504 fix this issue? Do you have a hint on how to reproduce this? I'm asking since this second bugreport #724972 was closed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719957: cloog: fix FTBFS when DSO linking
Am 17.08.2013 09:57, schrieb Eleanor Chen: Package: src:cloog Version: 0.18.0-2 Tags: patch Attached patch fixed the FTBFS issue when DSO linking is enabled. why would that be needed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726600: otrs2: Internal server error when replying to email ticket
Hi Patrick, On Thu, Oct 17, 2013 at 04:14:13PM +0200, Patrick Matthäi wrote: Am 17.10.2013 16:06, schrieb Salvatore Bonaccorso: Hi Patrick, On Thu, Oct 17, 2013 at 03:20:55PM +0200, Patrick Matthäi wrote: reassign #726600 libmime-tools-perl thanks Hello, could you please update libmime-tools-perl to version 5.504, it should fix this issue. We have the package ready in the Debian Perl Group repository, and will upload after a review. Did you had a chance to test that 5.504 fix this issue? Do you have a hint on how to reproduce this? I'm asking since this second bugreport #724972 was closed. Both are to me currently unreproduceable. This and the fact that his e-mail address was bouncing, see [0], intend me to close the older report. But I have found a thread with some more people with the same problems since they have upgraded Perl in testing to 5.18.1-4. Upstream said that the combination of Perl 5.18.1 and libmime-tools-perl 5.503 should be the source of the problem. Feedback from the bug submitter would be welcome after he is using libmime-tools-perl = 5.504. Ok, and thanks for the quick reply. I just uploaded libmime-tools-perl/5.504-1 to unstable. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726483:
I can confirm this bug; seems console-tools version 2:0.2.3-71 is incompatible with systemd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726453: ibus: Deactivating show icon on system tray does not hide the icon
Hi, On Thu, Oct 17, 2013 at 12:17:32AM +0200, Deb wrote: Package: ibus Version: 1.5.3-7 Followup-For: Bug #726453 Dear Maintainer, Thanks for looking into this. I'll try to explain better. The LXDE panel has a notification area (tray) like GNOME 2. Ibus adds an icon where the current keyboard layout is shown (in most cases a keyboard with a small globe), and where I could click to use the mouse to switch keyboard layouts. In the ibus preferences (under General) there is an option Show icon on system tray. It doesn't matter whether I tick this box or not, the icon is always visible on the system tray. (otherwise ibus works fine) Well, I don't *know* whether this is an ibus bug or a bug in lxde-panel (or elsewhere), but it appeared with the most recent updated of ibus. There was no update for the LXDE panel. Now I am clear what is your problem. We may be hitting GNOME 2 to GNOME 3 difference... Since GNOME3 do not use ibus-setup to set up configuration, I did not notice. But this transition timing of GNOME 3.8 seems to coinside with the problem for ibus-setup. I do not know is this is related or not. Let me investigate more. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694881: small update
I'm currently waiting on upstream, there are some big changes in the pipe. Still active and being worked on. Sorry, interested folks. I'll re-ping upstream. Cheers, Paul -- .''`. Paul Tagliamonte paul...@debian.org : :' : Proud Debian Developer `. `'` 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `- http://people.debian.org/~paultag signature.asc Description: Digital signature
Bug#726483: console-tools fails to install
Control: reassign -1 src:sysvinit 2.88dsf-43
Control: retitle -1 service incorrectly handles console-screen.service
Control: affects console-tools -1
On Wed, Oct 16, 2013 at 09:50:15AM +0200, David Weinehall wrote:
When upgrading to the latest version of console-tools, I received the
following error message:
Setting up console-tools (2:0.2.3-71) ...
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
Failed to issue method call: Unit console-screen.sh.service failed to
load: No such file or directory. See system logs and 'systemctl status
console-screen.sh.service' for details.
“/etc/init.d/console-screen.sh start” works fine but neither “service
console-screen.sh start” nor the equivalent invoke-rc.d does.
The difference is that /lib/lsb/init-functions.d/40-systemd correctly
trims the .sh off the service name while service does not. The attached
patch addresses the issue in both service and invoke-rc.d
James
diff -Nru sysvinit-2.88dsf/debian/changelog sysvinit-2.88dsf/debian/changelog
--- sysvinit-2.88dsf/debian/changelog 2013-07-16 16:10:10.0 -0400
+++ sysvinit-2.88dsf/debian/changelog 2013-10-17 09:47:20.0 -0400
@@ -1,3 +1,12 @@
+sysvinit (2.88dsf-43.1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * sysv-rc:
+- Update invoke-rc.d and service to trim .sh from service names when
+ calling systemctl.
+
+ -- James McCoy james...@debian.org Thu, 17 Oct 2013 09:42:55 -0400
+
sysvinit (2.88dsf-43) unstable; urgency=low
[ Roger Leigh ]
diff -Nru sysvinit-2.88dsf/debian/service/service sysvinit-2.88dsf/debian/service/service
--- sysvinit-2.88dsf/debian/service/service 2013-07-14 16:57:26.0 -0400
+++ sysvinit-2.88dsf/debian/service/service 2013-10-17 09:40:50.0 -0400
@@ -163,9 +163,10 @@
# systemctl calls.
if [ -n $is_systemd ]
then
+ UNIT=${SERVICE%.sh}.service
case ${ACTION} in
restart|status)
- exec systemctl ${ACTION} ${SERVICE}.service
+ exec systemctl ${ACTION} ${UNIT}
;;
start|stop)
# Follow the principle of least surprise for SysV people:
@@ -173,32 +174,32 @@
# has one or more .socket files, we also stop the .socket units.
# Users who need more control will use systemctl directly.
for unit in $(systemctl list-unit-files --full --type=socket 2/dev/null | sed -ne 's/\.socket\s*[a-z]*\s*$/.socket/p'); do
- if [ $(systemctl -p Triggers show $unit) = Triggers=${SERVICE}.service ]; then
+ if [ $(systemctl -p Triggers show $unit) = Triggers=${UNIT} ]; then
systemctl ${ACTION} $unit
fi
done
- exec systemctl ${ACTION} ${SERVICE}.service
+ exec systemctl ${ACTION} ${UNIT}
;;
reload)
- _canreload=$(systemctl -p CanReload show ${SERVICE}.service 2/dev/null)
+ _canreload=$(systemctl -p CanReload show ${UNIT} 2/dev/null)
if [ $_canreload = CanReload=no ]; then
# The reload action falls back to the sysv init script just in case
# the systemd service file does not (yet) support reload for a
# specific service.
run_via_sysvinit
else
-exec systemctl reload ${SERVICE}.service
+exec systemctl reload ${UNIT}
fi
;;
force-stop)
- exec systemctl --signal=KILL kill ${SERVICE}.service
+ exec systemctl --signal=KILL kill ${UNIT}
;;
force-reload)
- _canreload=$(systemctl -p CanReload show ${SERVICE}.service 2/dev/null)
+ _canreload=$(systemctl -p CanReload show ${UNIT} 2/dev/null)
if [ $_canreload = CanReload=no ]; then
-exec systemctl restart ${SERVICE}.service
+exec systemctl restart ${UNIT}
else
-exec systemctl reload ${SERVICE}.service
+exec systemctl reload ${UNIT}
fi
;;
*)
diff -Nru sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d
--- sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d 2013-07-14 16:57:26.0 -0400
+++ sysvinit-2.88dsf/debian/src/sysv-rc/sbin/invoke-rc.d 2013-10-17 09:42:46.0 -0400
@@ -276,6 +276,7 @@
is_upstart=1
elif test -d /run/systemd/system ; then
is_systemd=1
+UNIT=${INITSCRIPTID%.sh}.service
elif test ! -f ${INITDPREFIX}${INITSCRIPTID} ; then
## Verifies if the given initscript ID is known
## For sysvinit, this error is critical
@@ -390,7 +391,7 @@
if [ -n $is_upstart ]; then
_executable=1
elif [ -n $is_systemd ]; then
-_state=$(systemctl -p LoadState show ${INITSCRIPTID}.service 2/dev/null)
+_state=$(systemctl -p LoadState show ${UNIT} 2/dev/null)
if [ $_state != LoadState=masked ]; then
_executable=1
fi
@@ -519,25 +520,25 @@
fi
case $saction in
Bug#726467: [ibus] ibus-setup shortcut setting does not work
Hi, My short response is: Can you install gir1.2-gtk-3.0 and try again? (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725134 ) Here is my response as below. On Wed, Oct 16, 2013 at 11:31:30PM +0900, ISHIKAWA Mutsumi wrote: In 20131016133632.GA7716@goofy.localdomain Can yopu tell me what and where I can see ibus-setup's shortcut setting? Ah... I'm mistaken, it is keybord short cut (setting) on top of generic tab. I guess you are under en_US.UTF-8 when you see this. ... return model[path.get_indices()[0]][0] TypeError: 'int' object has no attribute '__getitem__' Can you describe a bit more in detail what you did to reach this. 1) I started ibus-setup from console (I use konsole of KDE for X terminal console) with LANG=ja_JP.UTF-8 This is another case, I guess. 2) a window of ibus-setup window is shown. window screen shot: https://docs.google.com/file/d/0B5a7kImy47K_RDlndFR6b2doUDQ/edit?usp=sharing ... OK, I see. You mean to click elipse ... to get subwindow. Also why the following list does not look like normal list? Why installed version are missing? They are generated by reportbug-ng automaticaly. I don't know why... I see. Please file bug to reportbug-ng citing the difference. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
