Bug#743605: [Pkg-gtkpod-devel] Bug#743605: usbmuxd and libusbmuxd-tools: error when trying to install together
On Fri, Apr 4, 2014 at 14:28:17 +0800, Chow Loong Jin wrote: On Fri, Apr 04, 2014 at 08:20:04AM +0200, Ralf Treinen wrote: Package: libusbmuxd-tools,usbmuxd Version: libusbmuxd-tools/1.0.9-1 Version: usbmuxd/1.0.8-3+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-04-04 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: That's a known issue. The libusbmuxd stuff was recently split into a different source package and I was waiting for that go pass through NEW before removing it from usbmuxd itself. You still might want to version libusbmuxd-tools' Replaces as usbmuxd ( 1.0.8-4) instead of usbmuxd ( 1.0.8-3+) to account for the binNMU. Cheers, Julien signature.asc Description: Digital signature
Bug#743833: gnat-4.6: no longer buildable on buildds
package: gnat-4.6 version: 4.6.4-2 severity: serious Hi, It seems gnat-4.6 is no longer buildable on buildds: https://buildd.debian.org/status/package.php?p=gnat-4.6 This is probably caused by the change (in 4.6.4-2) of gnat-4.6-base from arch any to arch all. The strict versioned dependency of gnat-4.6 on gnat-4.6-base makes gnat-4.6 uninstallable on every arch that's no longer in sync with the arch any package, so it's no longer possible to build gnat-4.6 with (an older version of) gnat-4.6 on those archs. Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742423: /usr/bin/winecfg is now a broken link
Oops, now /usr/bin/wine* are mostly broken symbolic links. compy /usr/bin ls -l wine* -rwxr-xr-x 1 root root 41 Mar 23 11:04 wine lrwxrwxrwx 1 root root 34 Apr 5 22:57 wineboot - ../lib/wine-unstable/wineapploader lrwxrwxrwx 1 root root 34 Apr 5 22:57 winecfg - ../lib/wine-unstable/wineapploader lrwxrwxrwx 1 root root 34 Apr 5 22:57 winedbg - ../lib/wine-unstable/wineapploader lrwxrwxrwx 1 root root 34 Apr 5 22:57 winefile - ../lib/wine-unstable/wineapploader lrwxrwxrwx 1 root root 34 Apr 5 22:57 winepath - ../lib/wine-unstable/wineapploader -rwxr-xr-x 1 root root 671 Apr 5 22:57 wine-unstable ls -l ../lib/wine-unstable total 28 -rwxr-xr-x 1 root root 7396 Apr 5 22:57 wine -rwxr-xr-x 1 root root 12860 Apr 5 22:57 wine-preloader -rwxr-xr-x 1 root root 1649 Apr 5 22:57 wine-wrapper Those links supposed to go to wine-preloader, wine-wrapper, or is there supposed to be a wineapploader in there? -- Jason -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 743600
Processing commands for cont...@bugs.debian.org: close 743600 0.9.8.1-3 Bug #743600 [src:libnm-qt] FTBFS on sparc Marked as fixed in versions libnm-qt/0.9.8.1-3. Bug #743600 [src:libnm-qt] FTBFS on sparc Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 743600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743600: closing 743600
close 743600 0.9.8.1-3 thanks Closing bug fixed in latest upload. -- Saludos, Maxy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740491: Similar problem
On Fri, Apr 04, 2014 at 02:31:27PM +0200, Benedict Verhegghe wrote: After upgrading a system from wheezy to jessie, nfs-common failed to (re)start. Version: 1:1.2.8-6. Reinstalling rpcbind, nfs-common, nfs-kernel-server, libnfsidmap2 did not help. Startup message: [FAIL] Starting NFS common utilities: statd idmapd failed! In syslog I noticed: rpc.idmapd[6984]: main: open(/var/lib/nfs/rpc_pipefs/nfs): No such file or directory I manually created a directory /var/lib/nfs/rpc_pipefs/nfs and the problem was solved. That's an unrelated issue. Note that as of version 1:1.2.8-5, by default nfs-common looks for rpc_pipefs under /run, not in /var/lib. You may need to update your locally-modified /etc/idmapd.conf, to pick up this new default, since /etc/init.d/nfs-common will no longer mount /var/lib/nfs/rpc_pipefs for you. (And manually creating the directory may let the package upgrade, but will not give the correct behavior since this must be a mountpoint, not a directory.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: reopening 743376
Processing commands for cont...@bugs.debian.org:
reopen 743376
Bug #743376 {Done: Nicolas Boulenguez nico...@debian.org}
[gnat-4.6-base,gnat-4.9-base] gnat-4.9-base and gnat-4.6-base: error when
trying to install together
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnat-4.6/4.6.4-3.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
743376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743376: gnat-4.9-base and gnat-4.6-base: error when trying to install together
This isn't fixed : ... Preparing to unpack .../gnat-4.9-base_4.9-20140330-1_all.deb ... Unpacking gnat-4.9-base (4.9-20140330-1) ... dpkg: error processing archive /var/cache/apt/archives/gnat-4.9-base_4.9-20140330-1_all.deb (--unpack): trying to overwrite '/usr/share/ada/debian_packaging.mk', which is also in package gnat-4.6 4.6.4-3 Didn't you test this before uploading the package ? -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 743376 in gnat-4.6/4.6.4-3
Processing commands for cont...@bugs.debian.org: found 743376 gnat-4.6/4.6.4-3 Bug #743376 [gnat-4.6,gnat-4.9-base] gnat-4.9-base and gnat-4.6-base: error when trying to install together Marked as found in versions gnat-4.6/4.6.4-3. thanks Stopping processing here. Please contact me if you need assistance. -- 743376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 743376 to gnat-4.6,gnat-4.9-base
Processing commands for cont...@bugs.debian.org: reassign 743376 gnat-4.6,gnat-4.9-base Bug #743376 [gnat-4.6-base,gnat-4.9-base] gnat-4.9-base and gnat-4.6-base: error when trying to install together Bug reassigned from package 'gnat-4.6-base,gnat-4.9-base' to 'gnat-4.6,gnat-4.9-base'. No longer marked as found in versions gnat-4.6-base/4.6.4-2, gnat-4.9-base/4.9-20140330-1, and gnat-4.6-base/4.6.4-1. Ignoring request to alter fixed versions of bug #743376 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 743376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743376 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 626718 +patch Bug #626718 [src:xmail] xmail: FTBFS: missing -ldl Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 626718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642570: python-pyhyphen: FTBFS: Permission denied: '/usr/lib/python2.7/dist-packages/hyphen/config.pyc'
control: tags -1 +pending Hi, henrich@debian:~/tmp$ grep-dctrl -F Depends python2.7-pyhyphen -s Source -s Package /var/lib/apt/lists/*_Packages | sort | uniq henrich@debian:~/tmp$ grep-dctrl -F Depends python-pyhyphen -s Source -s Package /var/lib/apt/lists/*_Packages | sort | uniq It seems that no packages depend on python-pyhyphen, so update it would not break any dependency packages. I'll do NMU for it to close this FTBFS. -- Hideki Yamane
Processed: Re: python-pyhyphen: FTBFS: Permission denied: '/usr/lib/python2.7/dist-packages/hyphen/config.pyc'
Processing control commands: tags -1 +pending Bug #642570 [src:python-pyhyphen] python-pyhyphen: FTBFS: Permission denied: '/usr/lib/python2.7/dist-packages/hyphen/config.pyc' Added tag(s) pending. -- 642570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648801: lib, commandline client and gui in one package
Hi, Why including lib, commandline client and gui in one package There are several reasons: - The upstream sources are under heavy development and changes to the lib likely - Upgrading is a pain, if no so-names are managed upstream - No other software is using the lib There will be a RC-bug filed against this package as long as this situation remains. This bug will prevent cutechess to go into testing. As upstream commit log in https://github.com/cutechess/cutechess/commits/master , now they are calm so it's time to separate packages. -- Hideki Yamane
Bug#742149: marked as done (mapnik: FTBFS on mipsen (virtual memory exhausted))
Your message dated Mon, 07 Apr 2014 09:47:31 +0200 with message-id 1396856851.8982.3.camel@imac.chaumes and subject line Re: mapnik: FTBFS on mipsen (virtual memory exhausted) has caused the Debian Bug report #742149, regarding mapnik: FTBFS on mipsen (virtual memory exhausted) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 742149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: mapnik Version: 2.2.0+ds1-6 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: block 731403 with -1 Hi, your package FTBFS on the mips and mipsel buildds: g++ -o bindings/python/mapnik_geometry.os -c -g -O2 -Wformat -Werror=format-security -ansi -Wall -pthread -O2 -fno-strict-aliasing -finline-functions -Wno-inline -Wno-parentheses -Wno-char-subscripts -rdynamic -fPIC -D_FORTIFY_SOURCE=2 -DHAVE_JPEG -DMAPNIK_USE_PROJ4 -DHAVE_PNG -DHAVE_TIFF -DBIGINT -DBOOST_REGEX_HAS_ICU -DLINUX -DMAPNIK_THREADSAFE -DNDEBUG -DHAVE_CAIRO -DHAVE_PYCAIRO -Ideps -Ideps/clipper/include -Ideps/agg/include -I. -Iinclude -I/usr/include -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/gdal -I/usr/include/postgresql -I/usr/include/python2.7 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/mips-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/libpng12 -I/usr/include/libdrm -I/usr/include/pycairo bindings/python/mapnik_geometry.cpp virtual memory exhausted: Cannot allocate memory scons: *** [bindings/python/mapnik_geometry.os] Error 1 See https://buildd.debian.org/status/package.php?p=mapnik Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- I believe this bug is closed by mapnik 2.2.0+ds1-7: * Add 1002 upstream patch to reduce memory usage during compilation using BOOST_SPIRIT_NO_PREDEFINED_TERMINALS * Disable debugging symbols to save memory during compilation. This and the previous change should be enough to close: #742149. (Virtual) memory usage stays below 2GB during compilation. Jérémy.---End Message---
Processed: Re: telepathy-ring: uninstallable on kfreebsd-*
Processing control commands: tags -1 +patch Bug #620544 [telepathy-ring] telepathy-ring: uninstallable on kfreebsd-* Added tag(s) patch. -- 620544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Debian Bug 737613
Processing commands for cont...@bugs.debian.org: submitter 737613 houndean+deb...@gmail.com Bug #737613 [xen-hypervisor-4.3-amd64] xen-hypervisor-4.3-amd: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen Changed Bug submitter to 'houndean+deb...@gmail.com' from 'Steve Hnizdur hounden+deb...@gmail.com' thanks Stopping processing here. Please contact me if you need assistance. -- 737613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620544: telepathy-ring: uninstallable on kfreebsd-*
control: tags -1 +patch
Hi,
As Steven suggested, set linux-any for Architecture.
--
Hideki Yamane
diff -u telepathy-ring-2.1.0/debian/control telepathy-ring-2.1.0/debian/control
--- telepathy-ring-2.1.0/debian/control
+++ telepathy-ring-2.1.0/debian/control
@@ -19,7 +19,7 @@
Homepage: http://telepathy.freedesktop.org/wiki/
Package: telepathy-ring
-Architecture: any
+Architecture: linux-any
Depends: ${shlibs:Depends}, ${misc:Depends}, ofono (= 0.33)
Provides: telepathy-connection-manager
Description: GSM and 3G UMTS Telepathy connection manager
@@ -30,7 +30,7 @@
Package: telepathy-ring-dbg
Priority: extra
Section: debug
-Architecture: any
+Architecture: linux-any
Depends: telepathy-ring (= ${binary:Version}), ${misc:Depends}
Description: GSM and 3G UMTS Telepathy connection manager (debug symbols)
Telepathy-Ring a 3GPP (GSM and 3G UMTS) connection manager for
diff -u telepathy-ring-2.1.0/debian/changelog
telepathy-ring-2.1.0/debian/changelog
--- telepathy-ring-2.1.0/debian/changelog
+++ telepathy-ring-2.1.0/debian/changelog
@@ -1,3 +1,12 @@
+telepathy-ring (2.1.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control
+- set it as Architecture: linux-any since ofono requires udev and the
+ BlueZ stack (Closes: #620544)
+
+ -- Hideki Yamane henr...@debian.org Mon, 07 Apr 2014 16:51:28 +0900
+
telepathy-ring (2.1.0-1) unstable; urgency=low
* Initial packaging.
Bug#743605: [Pkg-gtkpod-devel] Bug#743605: usbmuxd and libusbmuxd-tools: error when trying to install together
On Mon, Apr 07, 2014 at 08:18:53AM +0200, Julien Cristau wrote: On Fri, Apr 4, 2014 at 14:28:17 +0800, Chow Loong Jin wrote: On Fri, Apr 04, 2014 at 08:20:04AM +0200, Ralf Treinen wrote: Package: libusbmuxd-tools,usbmuxd Version: libusbmuxd-tools/1.0.9-1 Version: usbmuxd/1.0.8-3+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-04-04 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: That's a known issue. The libusbmuxd stuff was recently split into a different source package and I was waiting for that go pass through NEW before removing it from usbmuxd itself. You still might want to version libusbmuxd-tools' Replaces as usbmuxd ( 1.0.8-4) instead of usbmuxd ( 1.0.8-3+) to account for the binNMU. True that. Committed as 298321594071a6701238c57eb02b7dc667533774, thanks. -- Kind regards, Loong Jin signature.asc Description: Digital signature
Bug#734238: Patch for CVE-2013-6045
Here is the dpatch version (thanks to http://matrixhasu.altervista.org/?view=use_dpatch). Raphaël do you have the time to produce a 1.3+dfsg-4.8 ? Thanks, segfault1.dpatch Description: Binary data
Processed: retitle 683744 to gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME
Processing commands for cont...@bugs.debian.org: retitle 683744 gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME Bug #683744 [gnome-terminal] gnome-terminal: startup broken - the terminal is not usable afterwards (in awesome) Bug #721489 [gnome-terminal] gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME Bug #723721 [gnome-terminal] gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME Bug #731392 [gnome-terminal] gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME Changed Bug title to 'gnome-terminal: black-on-black text with Use colors from system theme under non-GNOME' from 'gnome-terminal: startup broken - the terminal is not usable afterwards (in awesome)' Ignoring request to change the title of bug#721489 to the same title Ignoring request to change the title of bug#723721 to the same title Ignoring request to change the title of bug#731392 to the same title thanks Stopping processing here. Please contact me if you need assistance. -- 683744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683744 721489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721489 723721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723721 731392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725685: code-aster-gui: Depends on tk8.5 and calls /usr/bin/wish
tags 725685 +patch quit I've added a patch for this in the Git repository (converted from SVN in passing): http://anonscm.debian.org/gitweb/?p=debian-science/packages/astk.git -- Denis Laxalde Logilab http://www.logilab.fr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#725685: code-aster-gui: Depends on tk8.5 and calls /usr/bin/wish
Processing commands for cont...@bugs.debian.org: tags 725685 +patch Bug #725685 [code-aster-gui] code-aster-gui: Depends on tk8.5 and calls /usr/bin/wish Added tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 725685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed:
Processing control commands: severity -1 grave Bug #698456 [libpoppler19] libpoppler19: renders parts of PDF with large black squares and reports parse error Severity set to 'grave' from 'important' found -1 0.18.4-6 Bug #698456 [libpoppler19] libpoppler19: renders parts of PDF with large black squares and reports parse error Marked as found in versions poppler/0.18.4-6. -- 698456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743177: gmsh
Hi Anton, could you please add the attached patch (from gmsh-tetgen) to gmsh package. It is very helpfull to use mesh adaptation from API. Best C Description: Adds missing headers Author: Christophe Trophime christophe.troph...@lncmi.cnrs.fr Reviewed-by: Anton Gladky gladky.an...@gmail.com Last-Update: 2012-06-24 Index: gmsh-tetgen-2.8.3~svn17531/CMakeLists.txt === --- gmsh-tetgen-2.8.3~svn17531.orig/CMakeLists.txt 2014-01-27 17:29:47.449822326 +0100 +++ gmsh-tetgen-2.8.3~svn17531/CMakeLists.txt 2014-01-27 17:29:47.449822326 +0100 @@ -103,6 +103,7 @@ Common/VertexArray.h Common/Octree.h Common/OctreeInternals.h Common/OS.h Common/StringUtils.h Common/OpenFile.h Common/onelab.h Common/GmshSocket.h Common/onelabUtils.h +Common/Options.h Numeric/Numeric.h Numeric/GaussIntegration.h Numeric/polynomialBasis.h Numeric/JacobianBasis.h Numeric/bezierBasis.h Numeric/fullMatrix.h Numeric/simpleFunction.h Numeric/cartesian.h Numeric/ElementType.h @@ -122,6 +123,7 @@ Mesh/meshGFaceElliptic.h Mesh/meshPartition.h Mesh/meshGFaceDelaunayInsertion.h Mesh/simple3D.h Mesh/meshPartitionOptions.h Mesh/directions3D.h Mesh/yamakawa.h Mesh/Voronoi3D.h Mesh/Levy3D.h Mesh/periodical.h Mesh/meshMetric.h +Mesh/Field.h Numeric/mathEvaluator.h Solver/dofManager.h Solver/femTerm.h Solver/laplaceTerm.h Solver/elasticityTerm.h Solver/crossConfTerm.h Solver/orthogonalTerm.h @@ -132,6 +134,7 @@ Post/PViewDataList.h Post/PViewDataGModel.h Post/PViewOptions.h Post/ColorTable.h Numeric/nodalBasis.h Graphics/drawContext.h + Graphics/Camera.h Graphics/Trackball.h contrib/kbipack/gmp_normal_form.h contrib/kbipack/gmp_matrix.h contrib/kbipack/gmp_blas.h contrib/kbipack/mpz.h contrib/DiscreteIntegration/Integration3D.h
Bug#743749: marked as done (sylpheed: mails lost when mailbox not accessible)
Your message dated Mon, 07 Apr 2014 09:21:31 + with message-id e1wx5kb-0001h1...@franck.debian.org and subject line Bug#743749: fixed in sylpheed 3.4.1-1 has caused the Debian Bug report #743749, regarding sylpheed: mails lost when mailbox not accessible to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 743749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sylpheed Version: 3.4.0-1 Severity: grave Tags: upstream Justification: causes data loss This is for preventing migration of current unstable version to testing because of bug http://sylpheed.sraoss.jp/redmine/issues/193 Upstream already released 3.4.1 to address this, which will be packaged ASAP. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) ---End Message--- ---BeginMessage--- Source: sylpheed Source-Version: 3.4.1-1 We believe that the bug you reported is fixed in the latest version of sylpheed, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ricardo Mones mo...@debian.org (supplier of updated sylpheed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Apr 2014 10:06:56 +0200 Source: sylpheed Binary: sylpheed sylpheed-dbg sylpheed-i18n sylpheed-plugins Architecture: source amd64 all Version: 3.4.1-1 Distribution: unstable Urgency: high Maintainer: Ricardo Mones mo...@debian.org Changed-By: Ricardo Mones mo...@debian.org Description: sylpheed - Light weight e-mail client with GTK+ sylpheed-dbg - Debugging symbols for sylpheed, a GTK+ e-mail client sylpheed-i18n - Locale data for Sylpheed (i18n support) sylpheed-plugins - Loadable modules for extending Sylpheed features Closes: 743749 Changes: sylpheed (3.4.1-1) unstable; urgency=high . * New upstream release - Fixes bug causing mail to be lost with POP3 (Closes: #743749) * debian/sylpheed.symbols - Add symbols file for shared libraries within sylpheed package Checksums-Sha1: 8ee782f25c669c2e1099755c38f0aed72f72f30c 1597 sylpheed_3.4.1-1.dsc 000f7c8b0aee188004b63b446792af04a2b71f12 3473101 sylpheed_3.4.1.orig.tar.bz2 82870aeaa4ac6e469f62308a7ed1f2d7c3f33c29 27840 sylpheed_3.4.1-1.debian.tar.xz ef57f2df483b6dd528920b70ce24826409c11388 800250 sylpheed_3.4.1-1_amd64.deb ab737ee513977d81babc11f5b01729f25edfd6cd 3411996 sylpheed-dbg_3.4.1-1_amd64.deb 1d0148fbe711c3d1f82194228653b745847c56e5 777266 sylpheed-i18n_3.4.1-1_all.deb 9e694aadf1d17bbe5ed2cc8f372d130daf34c866 89268 sylpheed-plugins_3.4.1-1_amd64.deb Checksums-Sha256: 87ea1ecd2f2209b349f2b13a4bcd250754c0b887fee9b2dde05bbbe7ff74c8a8 1597 sylpheed_3.4.1-1.dsc 7ded48cff0761332d829008e2b6536f54d5c6330f9c45d7123172864b78b9787 3473101 sylpheed_3.4.1.orig.tar.bz2 25abdb3c8ad999c755ee50f24039421f4d955d67ad269b326ac77d2d9abb4fa0 27840 sylpheed_3.4.1-1.debian.tar.xz 71c360248bd2eb19f08dc0eaf98375718c87088ecdd591445f54ac4e0a954a79 800250 sylpheed_3.4.1-1_amd64.deb 0e32fa071e7bc412e1950294a0dc757f1fae60cd66b85e9c3f8fec2902b1e464 3411996 sylpheed-dbg_3.4.1-1_amd64.deb 0b4a4f0ed2ab39d595b7683c1408b85d18538cb91adef9444d09464dbb4ac22a 777266 sylpheed-i18n_3.4.1-1_all.deb 3f60846a81b30f25fb2eb5c0cbadec9c87f7b69c37cefec776a0f463e8d29a67 89268 sylpheed-plugins_3.4.1-1_amd64.deb Files: 7d0ab4e48e12a0a868eaeb022dbc6a0b 1597 mail optional sylpheed_3.4.1-1.dsc 9071bb341a6d96244fe7cd5ff013c70d 3473101 mail optional sylpheed_3.4.1.orig.tar.bz2 3d889961c9d0f9d92524dca5c18021e8 27840 mail optional sylpheed_3.4.1-1.debian.tar.xz 7acb9d378ed5a7f94252f3d2734a7acd 800250 mail optional sylpheed_3.4.1-1_amd64.deb 3a4a282e2a3d77b1beaf42578840a156 3411996 debug extra sylpheed-dbg_3.4.1-1_amd64.deb d29cdcab96a22a269add63d01f2db197 777266 localization optional sylpheed-i18n_3.4.1-1_all.deb ebe83df5968517e00f8eea034a1c8ce6 89268 mail optional sylpheed-plugins_3.4.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNCZe4ACgkQLARVQsm1XazTvgCgldw1xrzWLrpD8LYMrnG2sbUa
Bug#743177: gmsh
Hi Christophe! Sure,I will. Actually, I will be in Grenoble again on July, so if you have time/wish we could meet and try another sort of Belgian bier. https://yade-dem.org/wiki/1st_Yade_Workshop Anton 2014-04-07 11:12 GMT+02:00 trophime christophe.troph...@lncmi.cnrs.fr: Hi Anton, could you please add the attached patch (from gmsh-tetgen) to gmsh package. It is very helpfull to use mesh adaptation from API. Best C
Bug#743177: gmsh
Sorry for the previous mail. I forgot to drop @bugs.debian.org Anton
Bug#743842: php5: uninstallable due to dependency loops
Source: php5 Version: 5.5.11+dfsg-1 Severity: serious https://buildd.debian.org/status/package.php?p=php-json Dependency installability problem for [43]php-json on armel, hurd-i386, i386, kfreebsd-i386, mipsel, powerpc and sparc: php-json build-depends on: - php5-cli (= 5.5.0~rc1+dfsg-1~) php5-cli depends on: - php5-common (= 5.5.11+dfsg-1) php5-common depends on: - php5-json php5-json depends on missing: - phpapi-20121212 The new php5 upload changed the phpapi, which means it’s now uninstallable because it Depends php5-json which cannot be recompiled against the new php, due to that loop. Please remove the Depends: php5-json from php itself. PHP should not depend on any of its extensions; people can rather do that themselves. (Actually, this is an issue in every version that had this Depends.) bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: moreinfo
Processing commands for cont...@bugs.debian.org: # thanks to everyone trying to reproduce the issue! tags 737374 moreinfo unreproducible Bug #737374 [pulseaudio-module-x11] pulseaudio-module-x11: pulseaudio crash upon loading flac file in totem Added tag(s) unreproducible and moreinfo. # since is not reproducible and affects only one use-case it should not be RC severity 737374 important Bug #737374 [pulseaudio-module-x11] pulseaudio-module-x11: pulseaudio crash upon loading flac file in totem Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 737374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737374 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743605: marked as done (usbmuxd and libusbmuxd-tools: error when trying to install together)
Your message dated Mon, 07 Apr 2014 10:00:06 + with message-id e1wx6lw-0003vn...@franck.debian.org and subject line Bug#743605: fixed in usbmuxd 1.0.8-4 has caused the Debian Bug report #743605, regarding usbmuxd and libusbmuxd-tools: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 743605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libusbmuxd-tools,usbmuxd Version: libusbmuxd-tools/1.0.9-1 Version: usbmuxd/1.0.8-3+b1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-04-04 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package libxml2:amd64. (Reading database ... 10937 files and directories currently installed.) Preparing to unpack .../libxml2_2.9.1+dfsg1-3_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-3) ... Selecting previously unselected package libplist2:amd64. Preparing to unpack .../libplist2_1.11-3_amd64.deb ... Unpacking libplist2:amd64 (1.11-3) ... Selecting previously unselected package libusb-1.0-0:amd64. Preparing to unpack .../libusb-1.0-0_2%3a1.0.17-1+b1_amd64.deb ... Unpacking libusb-1.0-0:amd64 (2:1.0.17-1+b1) ... Selecting previously unselected package libusbmuxd2:amd64. Preparing to unpack .../libusbmuxd2_1.0.9-1_amd64.deb ... Unpacking libusbmuxd2:amd64 (1.0.9-1) ... Selecting previously unselected package libusbmuxd-tools. Preparing to unpack .../libusbmuxd-tools_1.0.9-1_amd64.deb ... Unpacking libusbmuxd-tools (1.0.9-1) ... Selecting previously unselected package usbmuxd. Preparing to unpack .../usbmuxd_1.0.8-3+b1_amd64.deb ... Unpacking usbmuxd (1.0.8-3+b1) ... dpkg: error processing archive /var/cache/apt/archives/usbmuxd_1.0.8-3+b1_amd64.deb (--unpack): trying to overwrite '/usr/bin/iproxy', which is also in package libusbmuxd-tools 1.0.9-1 Processing triggers for man-db (2.6.6-1) ... Errors were encountered while processing: /var/cache/apt/archives/usbmuxd_1.0.8-3+b1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/iproxy /usr/share/man/man1/iproxy.1.gz This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. ---End Message--- ---BeginMessage--- Source: usbmuxd Source-Version: 1.0.8-4 We believe that the bug you reported is fixed in the latest version of usbmuxd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chow Loong Jin hyper...@debian.org (supplier of updated usbmuxd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Apr 2014 15:53:36 +0800 Source: usbmuxd Binary: usbmuxd usbmuxd-dbg Architecture: source amd64 Version: 1.0.8-4 Distribution: unstable Urgency: medium Maintainer: gtkpod
Bug#743456: marked as done (startpar uninstallable makes !linux uninstallable)
Your message dated Mon, 07 Apr 2014 10:03:58 + with message-id e1wx6pg-0005ng...@franck.debian.org and subject line Bug#743456: fixed in startpar 0.58-5 has caused the Debian Bug report #743456, regarding startpar uninstallable makes !linux uninstallable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 743456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: startpar Version: 0.58-3 Severity: serious Justification: Makes system uninstallable Tags: patch Hello, The !linux ports currently can't be installed because the startpar package conflicts with the sysvinit-utils package. The renaming done on Linux has to be done on !linux too, see attached patch. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash --- debian/rules.orig 2014-04-03 00:32:15.682600612 +0200 +++ debian/rules2014-04-03 00:32:16.634573452 +0200 @@ -22,8 +22,8 @@ ifeq ($(DEB_HOST_ARCH_OS),linux) dh_install startpar-upstart-injector lib/startpar/ dh_installman startpar-upstart-injector.8 - mv debian/startpar/usr/share/man/man8/startpar.8 debian/startpar/usr/share/man/man8/startpar.8init endif + mv debian/startpar/usr/share/man/man8/startpar.8 debian/startpar/usr/share/man/man8/startpar.8init override_dh_installinit-arch: dh_installinit --name startpar-bridge -n ---End Message--- ---BeginMessage--- Source: startpar Source-Version: 0.58-5 We believe that the bug you reported is fixed in the latest version of startpar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Petter Reinholdtsen p...@debian.org (supplier of updated startpar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Apr 2014 11:49:38 +0200 Source: startpar Binary: startpar Architecture: source amd64 Version: 0.58-5 Distribution: unstable Urgency: low Maintainer: Debian sysvinit maintainers pkg-sysvinit-de...@lists.alioth.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: startpar - run processes in parallel and multiplex their output Closes: 743456 Changes: startpar (0.58-5) unstable; urgency=low . * Upload final startpar split from sysvinit-utils to unstable. * Fix build problem on !linux systems (Closes: #743456). * Correct Vcs-Browser URL in control file, add missing .git ending. Checksums-Sha1: c40a787dc9d6eef74fe9d7aed04ddf266c1c854e 1469 startpar_0.58-5.dsc c979117a63222c96b6d8272b2db12c9ec4fd26b9 11024 startpar_0.58-5.debian.tar.xz 85d8bd8615c8eacb24ec0c024e8e0df940778a52 21330 startpar_0.58-5_amd64.deb Checksums-Sha256: 45c6715dac823b878bd3522fda7fa40c39ad4586ccd400c9b0b358bccc43a2ad 1469 startpar_0.58-5.dsc 06e2e68a28085c9dd7181fa36f2c0329ebcb9589e7e1827a7c250a89d9324caa 11024 startpar_0.58-5.debian.tar.xz 848f8f835e7bbf286dba1a50b236ace9f144a67692a7990f76eddab0382da342 21330 startpar_0.58-5_amd64.deb Files: 765babb759832d3637bfe78c8c487643 1469 admin required startpar_0.58-5.dsc 4351896279935d7b72ed799fbd789ade 11024 admin required startpar_0.58-5.debian.tar.xz 82e245bca19c25372946ae96c887d4a2 21330 admin required startpar_0.58-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iD8DBQFTQnXJ20zMSyow1ykRAkQGAJwPCkGnQ9txdLNFvKKamzcCUOCoNwCgwCL+ a5tT/yPEjUpiQh0eReFyBog= =h0r4 -END PGP SIGNATUREEnd Message---
Bug#718624: Bug#742626: transmission-daemon: SEGFAULT on first run, breaks installation
On Sb, 05 apr 14, 21:26:39, Markus Koschany wrote: thanks for testing. I will try to write a patch which implements these changes. Writing the patch is probably not the difficult part but rather to ensure that the upgrade path works and the changes won't cause any breakage. I won't find the time for tests this weekend but will start to work on it next week. If someone is faster, please go ahead. If you build a package with your patch applied I'll try to do some testing. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#741821: marked as done (xcircuit: FTBFS: menucalls.c:1278:27: error: 'fontnumbers' undeclared (first use in this function))
Your message dated Mon, 07 Apr 2014 10:20:52 + with message-id e1wx6fd-0001ad...@franck.debian.org and subject line Bug#741821: fixed in xcircuit 3.7.56.dfsg-1 has caused the Debian Bug report #741821, regarding xcircuit: FTBFS: menucalls.c:1278:27: error: 'fontnumbers' undeclared (first use in this function) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 741821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: xcircuit Version: 3.7.55.dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140315 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): gcc -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE_URL=\\ -DPACKAGE=\xcircuit\ -DVERSION=\3.7\ -DPROTOTYPES=1 -D__PROTOTYPES=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STRING_H=1 -DHAVE_LIBM=1 -DSIZEOF_VOID_P=8 -DSIZEOF_UNSIGNED_INT=4 -DSIZEOF_UNSIGNED_LONG=8 -DSIZEOF_UNSIGNED_LONG_LONG=8 -DHAVE_LIBXT=1 -DSTDC_HEADERS=1 -DHAVE_SETENV=1 -DHAVE_PUTENV=1 -DHAVE_DIRENT_H=1 -DHAVE_LIBZ=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAVE_U_CHAR=1 -DDOUBLEBUFFER=1 -DHAVE_X11_XPM_H=1 -DHAVE_XPM=1 -DLGF=1 -DINPUT_FOCUS=1 -DGS_EXEC=\gs\ -DSPICE_EXEC=\ngspice\ -DPROG_VERSION=3.7 -DPROG_REVISION=55 -DCAD_DIR=\/usr/lib/x86_64-linux-gnu\ -DTEMP_DIR=\/tmp\ -DRESOURCES_DIR=\/usr/lib/x86_64-linux-gnu/xcircuit-3.7/app-defaults\ -DSCRIPTS_DIR=\/usr/share/xcircuit\ -DBUILTINS_DIR=\/usr/share/xcircuit\ -DBUILTINS_FILE=\\ -DUSER_RC_FILE=\.xcircuitrc\ -DPROLOGUE_DIR=\/usr/share/xcircuit\ -DPROLOGUE_FILE=\xcircps2.pro\ -DSTARTUP_FILE=\startup.script\ -DLGF_LIB=\lgf.lps\ -DASG_SPICE_LIB=\asg_spice.lps\ -I. -IXw -D_FORTIFY_SOURCE=2 -I/usr -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wno-pointer-sign -c menucalls.c menucalls.c: In function 'findbestfont': menucalls.c:1278:27: error: 'fontnumbers' undeclared (first use in this function) while (strcmp(fonts[fontnumbers[newfont]].family, fonts[curfont].family)) ^ menucalls.c:1278:27: note: each undeclared identifier is reported only once for each function it appears in make[3]: *** [menucalls.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/03/15/xcircuit_3.7.55.dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: xcircuit Source-Version: 3.7.56.dfsg-1 We believe that the bug you reported is fixed in the latest version of xcircuit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Roland Stigge sti...@antcom.de (supplier of updated xcircuit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Apr 2014 11:46:15 +0200 Source: xcircuit Binary: xcircuit Architecture: source amd64 Version: 3.7.56.dfsg-1 Distribution: unstable Urgency: medium Maintainer: Margarita Manterola ma...@debian.org Changed-By: Roland Stigge sti...@antcom.de Description: xcircuit - Draw circuit schematics or almost anything Closes: 724826 741821 742495 Changes: xcircuit (3.7.56.dfsg-1) unstable; urgency=medium . * New upstream release - API adjustment (Closes: #741821) - Dependencies fixed (Closes: #742495) * Applied Tcl 8.6 fix by Sergei Golovan (Closes: #724826) * Use chrpath to strip RPATH from /usr/lib/xcircuit/xcircexec
Bug#743729: way out
* Christian Hofstaedtler z...@debian.org [140406 23:33]: I /think/ we should add this to all interpreter preinsts: update-alternatives --remove-all ruby On second thought, there are probably some corner cases; for one this needs to be done in src:ruby-defaults, and we must ensure that 1.8 never gets configured again after the preinst runs. I don't see how to guarantee that whatever workaround we come up with won't break in a random way. I'd be much more comfortable with readding the Conflicts on ruby1.8. -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- pgpwSPzE4KYXP.pgp Description: PGP signature
Bug#738735: marked as done (linop: FTBFS: dh_sphinxdoc: Sphinx documentation not found)
Your message dated Mon, 07 Apr 2014 10:33:50 + with message-id e1wx6sa-0005lo...@franck.debian.org and subject line Bug#738735: fixed in linop 0.8.2-1 has caused the Debian Bug report #738735, regarding linop: FTBFS: dh_sphinxdoc: Sphinx documentation not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 738735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linop Version: 0.8-1 Severity: serious Justification: fails to build from source Builds of linop covering only its architecture-dependent binary packages and skipping its architecture-independent -doc package (as on the autobuilders) have been faiing: dh_sphinxdoc -a -O--buildsystem=pybuild dh_sphinxdoc: Sphinx documentation not found make: *** [binary-arch] Error 2 Please arrange to invoke dh --with sphinxdoc only when it would have something to do. Thanks! ---End Message--- ---BeginMessage--- Source: linop Source-Version: 0.8.2-1 We believe that the bug you reported is fixed in the latest version of linop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ghislain Vaillant ghisv...@gmail.com (supplier of updated linop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 07 Apr 2014 09:14:01 +0100 Source: linop Binary: python-linop python3-linop python-linop-doc Architecture: source amd64 all Version: 0.8.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Ghislain Vaillant ghisv...@gmail.com Description: python-linop - Linear mathematical operators in Python (Python 2) python-linop-doc - Linear mathematical operators in Python (documentation) python3-linop - Linear mathematical operators in Python (Python 3) Closes: 738735 Changes: linop (0.8.2-1) unstable; urgency=medium . * New upstream release * Fix FTBFS (Closes: #738735) + move sphinxdoc build to override_dh_auto_install-indep Checksums-Sha1: ae5bfc1d0d95078355a0158bba2544de66cc0816 2248 linop_0.8.2-1.dsc cf981bd7e37f19fbb5516c93143b5ba9327b951a 17157 linop_0.8.2.orig.tar.gz 447d3de65ba444bd80cc253bd814d82b6d969fb7 2804 linop_0.8.2-1.debian.tar.xz c0e8d2366c1c96baa99f3691127a91339082547d 11390 python-linop_0.8.2-1_amd64.deb d02311694aaf1c37f97e6656a61776a081417ac4 11454 python3-linop_0.8.2-1_amd64.deb b372aa5b7f28aa47760d51d07c27ef55e340c7a2 32422 python-linop-doc_0.8.2-1_all.deb Checksums-Sha256: 0838e8baa3c12dd26797f1908784f2d9d73c1b3ed699af8dadfe2b0c8c00014c 2248 linop_0.8.2-1.dsc 7b8464e712a04a3225b047be5aa93f5e8c01c461633dedfac85470e6d96087f0 17157 linop_0.8.2.orig.tar.gz 18b1e06d9139a8c002914bb6a36491800699f9df3593b7996ca34caaceff4efd 2804 linop_0.8.2-1.debian.tar.xz bd63120c10d1d524336f6056d8e424f7a056094507b89166ae8521d82fe7717d 11390 python-linop_0.8.2-1_amd64.deb c7df3e74ef9889a3bf280983bb6b0a77df36ad6ac5949d97c43df5e1e49e1678 11454 python3-linop_0.8.2-1_amd64.deb e34b4fac2276bb47cf34ea30aa4881e78daf37249562ad04cc466505c5b4e12e 32422 python-linop-doc_0.8.2-1_all.deb Files: 9a2dc4d91b9f96150bf6041595e73f58 2248 python optional linop_0.8.2-1.dsc ead0d19694d2dbe5f5b9cca37a09ad38 17157 python optional linop_0.8.2.orig.tar.gz b7b6ef0ab2f05cc7a9e00e88c2b34cb5 2804 python optional linop_0.8.2-1.debian.tar.xz f208d7d900470453ca6b390d8172129c 11390 python optional python-linop_0.8.2-1_amd64.deb 226274a0eae2d85509ff83b2ec25e988 11454 python optional python3-linop_0.8.2-1_amd64.deb a690638a499aecd93d12911be498d5b4 32422 doc optional python-linop-doc_0.8.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTQnvhAAoJEFeKBJTRxkbREeEP/0ynv3DTd9Tb8/QrQzmxz7ab dFQDYPjhLgqQ+0y5P7fVDF/bPFkgbXa1GHLW1/sje1fIb4OxOwGtSPQX0tapDRGU Z0RMZiQLvix6LCLPO0r/bGsqgtGzp4zFKRwb24Hxhldhf0cHGr2Uc9nLnWdv/oSs SLQ3JEUDBA7uRyrl/r3E9Vkufsv9x2pyp60yNg1Yn0p6ilY7su3SI6L/ytW/jxpy CKWdD53kA5U4PFr8YGPAuQILbExMByRdtbAgDSR5qd7Z6NXric/pmwRmR/hxCUqe 2A+MHTYRomGcHcVA1ddOiRR7/G8XpOdbiteyn8f7aZ+XYhab54whmQmDfLnyLeNO
Bug#700758: bcrypt: Bcrypt exposes patterns in data, it is broken
On Mon, Feb 24, 2014 at 04:55:50PM +0100, Ulrik wrote: Hi, Fixing the flaw is not a good idea. A debian-developed new encrypted file format just to salvage this package? Not a good idea. Alternatives: 1) Remove it 2) Document the flaw directly in the package description, recommend a better solution (gpg) directly in the package description. Alternative (2) would allow users (if any) to decrypt/migrate their data. Hi, If something Debian-only is to be done with this package to keep it available, it could be disabling encryption, together with a descriptive error message. This would be a minimal intervention and have the advantages of (1) and (2). This should be documented in the package description and would allow users to decrypt already encrypted data (you never know where that may appear), but not to encrypt. What maintainer thinks about this? Note that this package has been proposed for removal (See cc'ed http://bugs.debian.org/740748), so if any action is intended to keep this package in the archive it should happen soon. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743842: [php-maint] Bug#743842: php5: uninstallable due to dependency loops
On Mon, April 7, 2014 11:49, Thorsten Glaser wrote: Please remove the Depends: php5-json from php itself. PHP should not depend on any of its extensions; people can rather do that themselves. (Actually, this is an issue in every version that had this Depends.) The dependency exists for transitional reasons: the functionality in the extension used to be in core, so the dependency guarantees that upgrades will not regress in functionality and applications will suddenly break. It can be weakened after one release cycle. Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743489: marked as done (license issues)
Your message dated Mon, 07 Apr 2014 11:20:16 + with message-id e1wx7b6-0002gj...@franck.debian.org and subject line Bug#743489: fixed in postgis 2.1.2+dfsg-1 has caused the Debian Bug report #743489, regarding license issues to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 743489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgis Version: 2.1.2-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: postgis-2.1.2\doc\xsl\* postgis-2.1.2\java\* (LGPL, BSD) postgis-2.1.2\liblwgeom\stringbuffer.* postgis-2.1.2\loader\* to debian/copyright. The link in the license of postgis-2.1.2\extras\ogc_test_suite\* does not work anymore. Please also add the license that your organization has signed to debian/copyright. Thanks! Thorsten ---End Message--- ---BeginMessage--- Source: postgis Source-Version: 2.1.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of postgis, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 743...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg sebas...@xs4all.nl (supplier of updated postgis package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 04 Apr 2014 20:16:30 +0200 Source: postgis Binary: postgis postgis-doc libpostgis-java liblwgeom-2.1.2 liblwgeom-dev postgresql-9.3-postgis-2.1 postgresql-9.3-postgis-scripts postgresql-9.3-postgis-2.1-scripts Architecture: source amd64 all Version: 2.1.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Bas Couwenberg sebas...@xs4all.nl Description: liblwgeom-2.1.2 - PostGIS Lightweight Geometry library liblwgeom-dev - PostGIS Lightweight Geometry library - Development files libpostgis-java - Geographic objects support for PostgreSQL -- JDBC support postgis- Geographic objects support for PostgreSQL postgis-doc - Geographic objects support for PostgreSQL -- documentation postgresql-9.3-postgis-2.1 - Geographic objects support for PostgreSQL 9.3 postgresql-9.3-postgis-2.1-scripts - PostGIS for PostgreSQL 9.3 -- scripts -- dummy package postgresql-9.3-postgis-scripts - Geographic objects support for PostgreSQL 9.3 -- scripts Closes: 717307 729284 743489 Changes: postgis (2.1.2+dfsg-1) unstable; urgency=medium . * Add myself to Uploaders. * Update copyright file using copyright-format 1.0. * Repack upstream tarball, remove OGC test cases with unclear license. (closes: #743489) * Add gbp.conf to use pristine-tar by default. * Add man page for raster2pgsql. (closes: #717307) * Bump Debhelper compatibility to 9. * Add partial German translation for documentation. Thanks to Chris Leick for the patch. (closes: #729284) Checksums-Sha1: 5aeafb305db3d553c6d91649e467eb94f9f75552 3817 postgis_2.1.2+dfsg-1.dsc b4450b397c7e2b33eb297482d3af427c41961989 6744593 postgis_2.1.2+dfsg.orig.tar.gz f6988832a0eb4d302b2a4859db786f4429b800c5 47096 postgis_2.1.2+dfsg-1.debian.tar.xz e991b9dcb209b0ec258ad75fff6f95e607510ab9 495724 postgis_2.1.2+dfsg-1_amd64.deb 04e8e4c17b9548f11abbbea5214635da700b742a 492210 liblwgeom-2.1.2_2.1.2+dfsg-1_amd64.deb ba4cf55aaca5ffe9fdfb3bdeec142adcca6c408f 513036 liblwgeom-dev_2.1.2+dfsg-1_amd64.deb 399d6e616fff3cc0627c3f734c7bf17e5c5630f2 580012 postgresql-9.3-postgis-2.1_2.1.2+dfsg-1_amd64.deb af7ffe260d934ae32844bdc8eb73cc58200239f0 2978976 postgis-doc_2.1.2+dfsg-1_all.deb 5d2845fea9f14e6d727740ad531d09fe1f14f88a 418420 libpostgis-java_2.1.2+dfsg-1_all.deb ece6280eae11e83baf43fd83fe2b7c9b6dabd104 714158 postgresql-9.3-postgis-scripts_2.1.2+dfsg-1_all.deb 7a58dc6e809efe02bf5c165f206af6a0194c33e6 346202 postgresql-9.3-postgis-2.1-scripts_2.1.2+dfsg-1_all.deb Checksums-Sha256: d8cd19964533ed605bad042d147c9c42641c2f16f1ab14cca23a0cb2efc62636 3817 postgis_2.1.2+dfsg-1.dsc dae0edf9aa2b211365d132e7a478d06e666464b4c095fb1c48decfd9bd7ce39a 6744593
Bug#743842: [php-maint] Bug#743842: php5: uninstallable due to dependency loops
On Mon, Apr 7, 2014 at 12:49 PM, Thorsten Glaser t.gla...@tarent.de wrote: Dependency installability problem for [43]php-json on armel, hurd-i386, i386, kfreebsd-i386, mipsel, powerpc and sparc: php-json build-depends on: - php5-cli (= 5.5.0~rc1+dfsg-1~) php5-cli depends on: - php5-common (= 5.5.11+dfsg-1) php5-common depends on: - php5-json php5-json depends on missing: - phpapi-20121212 The new php5 upload changed the phpapi, which means it’s now uninstallable because it Depends php5-json which cannot be recompiled against the new php, due to that loop. The phpapi number wasn't changed, but we've reenabled LFS ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738984), which means that for 32bits it has lfs in the name: Version: 5.5.10+dfsg-1 Provides: php5-mhash, phpapi-20121212 Version: 5.5.11+dfsg-1 Provides: php5-mhash, phpapi-20121212+lfs Kaplan
Bug#743854: wrong license in debian/coypright
Package: testrepository Version: 0.0.14-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, according to the file header and COPYING this software is licensed under a dual license. According to debian/copyright the software is just licensed under Apache and the dual license is only valid for debian/*. This does not match ... Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743842: [php-maint] Bug#743842: php5: uninstallable due to dependency loops
On Mon, 7 Apr 2014, Lior Kaplan wrote: The phpapi number wasn't changed, but we've reenabled LFS ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738984), which means that for 32bits it has lfs in the name: Yes, that precisely means that it changes. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743855: projectl ftbfs after the gdc update in 4.8.2-19
Package: projectl Version: 1.001.dfsg1-6 Severity: serious Tags sid jessie [...] cc1d: warning: command line option '-Wformat=1' is valid for C/C++/ObjC/ObjC++ but not for D src/util/parts.d:635: error: multiple field maxParts initialization make[2]: *** [projectl] Error 1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743758: procps: FTBFS on mips and powerpc
On Sun, Apr 06, 2014 at 04:04:52PM +0200, Cyril Brulebois wrote: Maybe I missed it, but I don't see any mails from you on debian-wb-team@. It would probably be a good entry point (along with $a...@buildd.debian.org) to get answers to buildd-related questions, don't you think? There have been multiple emails to the various arches with the replies being: * Oh, it compiled on some buildd so its all good now * It complied on my XYZ arch * Silence The problems stem from either: *the buildds putting the kernel into an odd situation so the sched_setscheduler() function fails, or works and doesn't show up or perhaps the kernel tables are weird. * the buildds mangling the shell is so it simultaneously says kill exists and kill doesn't exist. * the buildds messing up some /proc files, such as /proc/partitions in a way that cannot really exist in a real system. I suspect that the two references you sent are #1 and #3. Generally if you login to the relevant arches and compile the programs they will compile and test ok, it is something the buildd process itself that makes these problems occur. I don't have access to these systems, I don't really understand them and I know they are inconsistent (the last being the i386 set that failed and then.. was ok with no change of the code) FTBFS just basically blocks fixes which is probably not what anyone wants with impossible to isolate let alone fix, phantom bugs. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint:5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734238: Patch for CVE-2013-6045
Salut Mathieu, On 7 April 2014 10:16, Mathieu Malaterre ma...@debian.org wrote: Here is the dpatch version (thanks to http://matrixhasu.altervista.org/?view=use_dpatch). Raphaël do you have the time to produce a 1.3+dfsg-4.8 ? I can find some time to do it and release a revision to the DSA to fix the regression. I assume that the patch also works as-is in squeeze. If you have a few minutes and you can prepare the packages yourself it'd be of great help. Just make sure you target squeeze-security, wheezy-security, you follow the versioning schema, set urgency=high, make no other change and upload to security-master.d.o. Can you do that? Thanks. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): merge python-setuptools issues
Processing commands for cont...@bugs.debian.org:
severity 743704 grave
Bug #743704 [python-setuptools] python-setuptools fails to install
Severity set to 'grave' from 'important'
severity 743655 grave
Bug #743655 [src:python-setuptools] Conflicts with python-pyaudio
Severity set to 'grave' from 'serious'
forcemerge 743655 743704
Bug #743655 [src:python-setuptools] Conflicts with python-pyaudio
Unable to merge bugs because:
package of #743704 is 'python-setuptools' not 'src:python-setuptools'
Failed to forcibly merge 743655: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2adddf8)',
'requester', 'Matthias Klose d...@debian.org', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid', '5342acb6.6060...@debian.org',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', 'forcemerge 743655
743704', 'clonebugs', 'HASH(0x2a242a0)', 'limit', 'HASH(0x2a1a810)',
'common_control_options', 'ARRAY(0x2a1a858)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
thanks
Stopping processing here.
Please contact me if you need assistance.
--
743655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743655
743704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: merge setuptools issues
Processing commands for cont...@bugs.debian.org: severity 743704 grave Bug #743704 [python-setuptools] python-setuptools fails to install Ignoring request to change severity of Bug 743704 to the same value. severity 743655 grave Bug #743655 [src:python-setuptools] Conflicts with python-pyaudio Ignoring request to change severity of Bug 743655 to the same value. severity 743644 grave Bug #743644 [python-setuptools] python-setuptools fails to upgrade to 3.4.1-1 Severity set to 'grave' from 'normal' reassign 743644 src:python-setuptools Bug #743644 [python-setuptools] python-setuptools fails to upgrade to 3.4.1-1 Bug reassigned from package 'python-setuptools' to 'src:python-setuptools'. No longer marked as found in versions python-setuptools/3.3-1. Ignoring request to alter fixed versions of bug #743644 to the same values previously set reassign 743655 src:python-setuptools Bug #743655 [src:python-setuptools] Conflicts with python-pyaudio Ignoring request to reassign bug #743655 to the same package reassign 743704 src:python-setuptools Bug #743704 [python-setuptools] python-setuptools fails to install Bug reassigned from package 'python-setuptools' to 'src:python-setuptools'. No longer marked as found in versions python-setuptools/3.3-1. Ignoring request to alter fixed versions of bug #743704 to the same values previously set forcemerge 743655 743704 743644 Bug #743655 [src:python-setuptools] Conflicts with python-pyaudio Bug #743644 [src:python-setuptools] python-setuptools fails to upgrade to 3.4.1-1 Marked as found in versions python-setuptools/3.4.1-1. Bug #743704 [src:python-setuptools] python-setuptools fails to install Marked as found in versions python-setuptools/3.4.1-1. Merged 743644 743655 743704 thanks Stopping processing here. Please contact me if you need assistance. -- 743644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743644 743655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743655 743704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738735: linop: FTBFS: dh_sphinxdoc: Sphinx documentation not found
found 738735 0.8.2-1 thanks It looks like you never committed an actual fix; could you please do so? You can test the change by running gbp buildpackage -B. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#738735: linop: FTBFS: dh_sphinxdoc: Sphinx documentation not found
Processing commands for cont...@bugs.debian.org:
found 738735 0.8.2-1
Bug #738735 {Done: Ghislain Vaillant ghisv...@gmail.com} [src:linop] linop:
FTBFS: dh_sphinxdoc: Sphinx documentation not found
Marked as found in versions linop/0.8.2-1; no longer marked as fixed in
versions linop/0.8.2-1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
738735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743862: keep tiff3 out of testing
Package: tiff3 Severity: critical This is to keep tiff3 from getting back into testing -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743864: Does not allow to log in [kfreebsd]
Package: slim Version: 1.3.6-2 Severity: serious Hi! Seems I can no longer log into my notebook -- after I enter my password in slim it imediately retyursn to asking for an username. I don't see anything in auth.log and a foreground slim doesn't seem to output anything interesting. CHristoph -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 11.0-0-amd64 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 slim depends on: ii consolekit 0.4.6-4 ii dbus 1.8.0-3 ii debconf [debconf-2.0] 1.5.52 ii libc0.12.18-4 ii libck-connector0 0.4.6-4 ii libdbus-1-31.8.0-3 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.5.2-1 ii libgcc11:4.8.2-16 ii libjpeg8 8d-2 ii libpng12-0 1.2.50-1 ii libstdc++6 4.8.2-16 ii libx11-6 2:1.6.2-1 ii libxft22.3.1-2 ii libxmu62:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii libxrender11:0.9.8-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages slim recommends: ii xterm 303-1 Versions of packages slim suggests: ii scrot 0.8-13 ii xauth 1:1.0.7-1 -- debconf information: slim/daemon_name: /usr/bin/slim * shared/default-x-display-manager: slim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698456:
On 2014-04-07 11:09, Mathieu Malaterre wrote: Control: severity -1 grave Control: found -1 0.18.4-6 This found contraddicts what the reporter says in message #15, so either you are trying with a different document or the reporter is not providing correct information. Moving to grave, since I cannot even read the PDF (PDF are generated by a bank application, which makes those PDF pretty much useless with evince). I think grave as severity for I cannot read this particular PDF is slightly overinflated. Please downgrade back to important, thanks. -- Pino Toscano -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721547: libregexp-grammars-perl: Currently incompatible with Perl 5.18
Hi, Damian, CC'ing you only for information :) On Sun, Sep 01, 2013 at 10:32:31PM +0200, Salvatore Bonaccorso wrote: Package: libregexp-grammars-perl Version: 1.028-1 Severity: serious Tags: upstream Justification: maintainer decision, unfit for release with perl 5.18.1; incompatible This is a blocking bug to prevent further migration of libregexp-grammars-perl into testing until some incompatibility problems with Perl 5.18 are solved upstream: , [ lib/Regexp/Grammars.pm ] | Warning: Regexp::Grammars is currently unsupported under Perl 5.18. | | Perl 5.18 changed how 'qr' constant overloadings are parsed and the | scope in which they are subsequently compiled. This change currently | make it impossible to reliably create 'qr' overloadings that inject | code blocks into a regex, as it prevents the overloaded regexes from | compiling properly in many cases, even with an explicit 'use re | eval' in scope. | | These problems have been reported, and the brave volunteers of P5P are | currently working on fixes. However, these will not be available until | at least 5.18.2. | | Because Regexp::Grammars relies on 'qr' overloads to inject code blocks | into regexes, the module is curently not compatible with Perl 5.18. It | may continue to work in some limited cases, but is no longer reliable. | | At present, if you rely on Regexp::Grammars for your parsing needs, your | alternatives are either not to upgrade to Perl 5.18, to livce with the | problems until they are resolved (in Perl 5.18.2, we hope), or else to | consider switching to another parsing system, such as Marpa. | | We deeply regret that Regexp::Grammars cannot currently be maintained | completelt due to these backwards-incompatible changes and bugs in | Perl 5.18. ` I had the privilege to talk directly to Damian to aks about if it is worth keeping Regexp::Grammars. Basically I would suggest the following: As we have from the RT ticket, there is slowly progress, and possibly in some perl 5.18.x release it might be fixed the remaining problems, basically around say 95% of it should work already now again. I'm proposing the following: Keep Regexp::Grammars still in Debian unstable. The release-critical Bug prevents the package migrating to Debian Testing, so we will not ship libregexp-grammars-perl with a Debian release which has perl 5.18. The issues should be solved when working with Perl 5.20, which will be released next month. Once this happens, a new version of Regexp::Grammars will eventually be uploaded by Damian which changes the warning to mark explicitly only the broken 5.18 releases. Once we have Perl 5.20 in Debian libregexp-grammars-perl should be safe to distribute again together in Debian as packaged module. Thus in short: I'm in favour to keep the package for now with a RC bug open preventing the migration to testing. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698456:
Control: reassign -1 evince Control: found -1 3.4.0-3.1 Control: severity -1 important On Mon, Apr 7, 2014 at 5:37 PM, Pino Toscano p...@debian.org wrote: On 2014-04-07 11:09, Mathieu Malaterre wrote: Control: severity -1 grave Control: found -1 0.18.4-6 This found contraddicts what the reporter says in message #15, so either you are trying with a different document or the reporter is not providing correct information. OP is not very clear either. Apparently the bug would be fixed with '0.18.4-6' on 'jessie'. What I can tell, is that the bug is present on default wheezy installation (x86_64). I saw the corruption of my PDF generated bank account (OP is using the same bank online service) I do not believe the issue lie within the poppler code base since `pdftoppm` behave as expected. So the rendering issue should (must?) be within evince codebase. Thus re-assigning. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#698456:
Processing control commands: reassign -1 evince Bug #698456 [libpoppler19] libpoppler19: renders parts of PDF with large black squares and reports parse error Bug reassigned from package 'libpoppler19' to 'evince'. No longer marked as found in versions poppler/0.18.4-4 and poppler/0.18.4-6. Ignoring request to alter fixed versions of bug #698456 to the same values previously set found -1 3.4.0-3.1 Bug #698456 [evince] libpoppler19: renders parts of PDF with large black squares and reports parse error Marked as found in versions evince/3.4.0-3.1. severity -1 important Bug #698456 [evince] libpoppler19: renders parts of PDF with large black squares and reports parse error Severity set to 'important' from 'grave' -- 698456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698456 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742869: marked as done (lua-posix: fails to build with LDoc 1.4)
Your message dated Mon, 07 Apr 2014 15:58:22 +
with message-id e1wxbwe-0006hu...@franck.debian.org
and subject line Bug#742869: fixed in lua-posix 31-1
has caused the Debian Bug report #742869,
regarding lua-posix: fails to build with LDoc 1.4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
742869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lua-posix
Version: 29-7
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch trusty
lua-posix fails to build with LDoc 1.4:
ldoc .
/«PKGBUILDDIR»/lposix.c:2787: internal LDoc error
/usr/share/lua/5.1/ldoc/tools.lua:184: attempt to call method 'match' (a nil
value)
stack traceback:
/usr/share/lua/5.1/ldoc/tools.lua:184: in function
'extract_identifier'
/usr/share/lua/5.1/ldoc/parse.lua:376: in function
/usr/share/lua/5.1/ldoc/parse.lua:246
[C]: in function 'xpcall'
/usr/share/lua/5.1/ldoc/parse.lua:246: in function 'parse_file'
/usr/share/lua/5.1/ldoc/parse.lua:402: in function 'file'
/usr/bin/ldoc:403: in function 'process_file'
/usr/bin/ldoc:489: in main chunk
[C]: ?
reading configuration from config.ld
make[1]: *** [override_dh_auto_build] Error 255
Here's the upstream discussion:
https://github.com/stevedonovan/LDoc/issues/125
Looking through the git history at around the relevant time, two patches
seem clearly relevant. I backported these and lua-posix now builds
fine. Here you go:
* Backport a couple of ldoc fixes from upstream.
diff -Nru lua-posix-29/debian/patches/add-missing-ldoc-function-tag.patch
lua-posix-29/debian/patches/add-missing-ldoc-function-tag.patch
--- lua-posix-29/debian/patches/add-missing-ldoc-function-tag.patch
1970-01-01 01:00:00.0 +0100
+++ lua-posix-29/debian/patches/add-missing-ldoc-function-tag.patch
2014-03-28 11:06:37.0 +
@@ -0,0 +1,21 @@
+From: Gary V. Vaughan g...@gnu.org
+Date: Thu, 12 Dec 2013 09:17:09 +1300
+Subject: [PATCH] doc: add missing LDoc function tag.
+
+* ext/posix/posix.c (strptime): Add missing @function tag.
+
+Signed-off-by: Gary V. Vaughan g...@gnu.org
+Origin: backport,
https://github.com/luaposix/luaposix/commit/6640275b2e860521b8ae458b8f1c4ebaf53d7f27
+
+Index: b/lposix.c
+===
+--- a/lposix.c
b/lposix.c
+@@ -2901,6 +2901,7 @@
+
+ /***
+ Parse a date string.
++@function strptime
+ @see strptime(3)
+ @string s
+ @string format same as for `strftime`
diff -Nru lua-posix-29/debian/patches/fix-ldoc-custom-see-handler.patch
lua-posix-29/debian/patches/fix-ldoc-custom-see-handler.patch
--- lua-posix-29/debian/patches/fix-ldoc-custom-see-handler.patch
1970-01-01 01:00:00.0 +0100
+++ lua-posix-29/debian/patches/fix-ldoc-custom-see-handler.patch
2014-03-28 11:05:08.0 +
@@ -0,0 +1,29 @@
+From: Gary V. Vaughan g...@gnu.org
+Date: Thu, 12 Dec 2013 09:15:12 +1300
+Subject: [PATCH] doc: fix LDoc manual page custom_see_handler pattern.
+
+* ext/posix/config.ld (custom_see_handler): Add a missing closing
+`%)`.
+(upat): Pull the format string up per LDoc documentation.
+
+Signed-off-by: Gary V. Vaughan g...@gnu.org
+Origin: backport,
https://github.com/luaposix/luaposix/commit/1bcb12c59dcfb830ffb9b8db7305720c83cb17ac
+
+Index: b/config.ld
+===
+--- a/config.ld
b/config.ld
+@@ -7,9 +7,10 @@
+ tparam_alias 'int'
+ tparam_alias 'bool'
+
+-custom_see_handler('^([%w_]+)%((%d)$',function(name,section)
+-local url =
(http://www.kernel.org/doc/man-pages/online/pages/man%s/%s.%s.html;):format(section,name,section)
+-local name = name .. '(' ..section..')'
++local upat =
http://www.kernel.org/doc/man-pages/online/pages/man%s/%s.%s.html;
++custom_see_handler('^([%w_]+)%((%d)%)$',function(name,section)
++local url = upat:format(section,name,section)
++local name = name .. '(' .. section .. ')'
+ return name, url
+ end)
+
diff -Nru lua-posix-29/debian/patches/series lua-posix-29/debian/patches/series
--- lua-posix-29/debian/patches/series 2014-01-21 19:58:48.0 +
+++ lua-posix-29/debian/patches/series 2014-03-28 11:05:40.0 +
@@ -1,2 +1,4 @@
0001-Fix-build-on-hurd-i386.patch
0002-Fix-compilation-on-kfreebsd.patch
+fix-ldoc-custom-see-handler.patch
+add-missing-ldoc-function-tag.patch
Thanks,
--
Colin Watson
Processed: severity of 721118 is serious
Processing commands for cont...@bugs.debian.org: severity 721118 serious Bug #721118 [coreutils] coreutils: Missing mandatory build-arch and build-indep targets with Standards-Version 3.9.4 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 721118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741792: Bug#742734: [Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
Hi All, On Tue, 2014-04-01 at 21:34 +0200, Paul Gevers wrote: On 26-03-14 20:15, Paul Gevers wrote: Included *.lpk files in the binary packages and mark them as manually compiled to avoid recompiling them when used. Apparently that causes other side effects for build dependencies. I confirm that NOT marking these packages as manually compiled fixed the FTBFS for doublecmd. I need to analyse more the failure, but the fact that rebuilding a system build binary solves the issue does not mean that the issue is in that binary. It is more like if some program needs to rebuild libc in order to work in Debian, this is of course not a proof that there is a bug in libc Debian package. Abou, can you please comment if you know a way to have the manual trick work for both gtk2 and qt4? Please see my comments on my previous post. (Sorry this thread was badly filtered and I just discovered it) Otherwise, I think I will fix this real soon in Lazarus to prevent removal from jessie. Please don't remove the manual flag. Here, if I understood well, we are dealing about an alpha feature which is QT support in LCL. So it could not be a RC bug. Also upstream changed the way to handle LCL and the user programs should upgrade. Of course as a member of this team; I'll have a look at doublecmd sources and try to fix it, so the way to go now is probably to lower the severity of these bugs or to hope I can close them before the fatal deadline of April 14th. Cheers, signature.asc Description: This is a digitally signed message part
Bug#741792: [Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
On Wed, 2014-03-26 at 20:15 +0100, Paul Gevers wrote: Control: clone -1 -2 Control: reassign -2 lazarus Control: retitle -2 controls in lazarus/components should be marked auto On 26-03-14 07:41, Graham Inggs wrote: and the problem with gifanim.pas remains. Alexander then replied as follows: The real problem in lazarus package. Lazarus can not build any LCL-Qt application that uses controls from lazarus/components directory. It is because this components marked as manually build in lazarus debian package (lazarus debian rules file manually change it). In RPM distros (Fedora for example) they marked as automatically build (that is upstream default behavior) so there are no such problem. I make a workaround that worked in previous lazarus versions (forced build of some components from lazarus directory, that you can see in components/build.sh). But now it does not work because they depends on each other. I have confirmed this by simply commenting out the section that builds doublecmd-qt in debian/rules and the doublecmd-gtk package builds without problem. I must admit that I don't understand the details, but this really looks like a bug in lazarus then. Abou, what is your opinion here? The relevant change was made in commit 7c4585ed and the text accompanying it was Included *.lpk files in the binary packages and mark them as manually compiled to avoid recompiling them when used. Apparently that causes other side effects for build dependencies. Hi Paul Others, The decision to mark packages as Manually built was du to the fact that these are considered as provider binaries. So users need to work with them in their binary format. If you remove this, then Lazarus will build them in the user's home directory for each user. There are 2 points here: 1) It not relevant to package binary files if you know it will never be used 2) On multi-user system this is consuming a huge amount of memory useless. 3) It is working only because the source package is installed, while this one is optional. So I don't agree that we need to remove the manual build flag, and I don't agree that this is a critical bug as LC-QT is a alpha feature. I'd ask kindly to lower this bug severity or will do it myself in order to avoid a useless removal from testing scheduled for April 14th. Cheers, Abou Al Montacir, signature.asc Description: This is a digitally signed message part
Bug#741792: Bug#742734: [Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
Hi All, On Tue, 2014-04-01 at 21:34 +0200, Paul Gevers wrote: On 26-03-14 20:15, Paul Gevers wrote: Included *.lpk files in the binary packages and mark them as manually compiled to avoid recompiling them when used. Apparently that causes other side effects for build dependencies. I confirm that NOT marking these packages as manually compiled fixed the FTBFS for doublecmd. I need to analyse more the failure, but the fact that rebuilding a system build binary solves the issue does not mean that the issue is in that binary. It is more like if some program needs to rebuild libc in order to work in Debian, this is of course not a proof that there is a bug in libc Debian package. Abou, can you please comment if you know a way to have the manual trick work for both gtk2 and qt4? Please see my comments on my previous post. (Sorry this thread was badly filtered and I just discovered it) Otherwise, I think I will fix this real soon in Lazarus to prevent removal from jessie. Please don't remove the manual flag. Here, if I understood well, we are dealing about an alpha feature which is QT support in LCL. So it could not be a RC bug. Also upstream changed the way to handle LCL and the user programs should upgrade. Of course as a member of this team; I'll have a look at doublecmd sources and try to fix it, so the way to go now is probably to lower the severity of these bugs or to hope I can close them before the fatal deadline of April 14th. Cheers, -- It is as though Einstein's God had made sure that no one could ever know enough to predict the future. Leonard Susskind, 2008. signature.asc Description: This is a digitally signed message part
Bug#721547: libregexp-grammars-perl: Currently incompatible with Perl 5.18
Thanks for the CC, Salvatore. I've added a note to my ToDo list to revisit the module within the next month. BTW, only 4 of the module's 921 tests fail under 5.19.9, so we're very very close to okay for Perl 5.20. :-) Damian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718624: Bug#742626: transmission-daemon: SEGFAULT on first run, breaks installation
retitle 718624 transmission-daemon: segfaults with systemd due to erroneous maintainer scripts tags 718624 patch thanks On 07.04.2014 12:10, Andrei POPESCU wrote: [...] If you build a package with your patch applied I'll try to do some testing. Hello Andrei and Antoine, thanks for offering a helping hand with this bug. I have prepared a patch which I'm attaching to this bug report. I could also build a binary package but I recommend to apply the patch yourself and then to build everything from source. Here is the changelog: * transmission-daemon.postinst: - Change home directory of transmission-daemon to /var/lib/transmission-daemon from /home/debian-transmission. Thanks to Alex Peters for the report. (Closes: #734467) - Disable password authentication for debian-transmission user for improved security. Logins with e.g. SSH RSA keys are still possible. - Check existence of debian-transmission user with getent passwd debian-transmission instead of id. * Add transmission-daemon.preinst: - Fix permissions in /var/lib/transmission-daemon and use /var/lib/transmission-daemon as the new home directory. - Move old configuration files to appropriate config directory /var/lib/transmission-daemon/.config/transmission-daemon. All together this ensures that transmission-daemon will not segfault when systemd is the default init system. Thanks to Andrei Popescu and Antoine Legonidec for the report and additional tests. (Closes: #718624) * transmission-daemon.links: - Link settings.json from /etc/transmission-daemon/settings.json to /var/lib/transmission-daemon/.config/transmission-daemon. - Link /var/lib/transmission-daemon/.config/transmission-daemon to /var/lib/transmission-daemon/info due to compatibility reasons with the old sysv-rc init script settings. * transmission-daemon.dirs: - Do not create /var/lib/transmission-daemon/info anymore. * transmission-daemon.postrm: - Also delete debian-transmission user when purging the daemon. Regards, Markus From 6e5cf54fd27da04e71d7010a1621be3d3d8144f3 Mon Sep 17 00:00:00 2001 From: Markus Koschany a...@gambaru.de Date: Mon, 7 Apr 2014 16:34:04 +0200 Subject: [PATCH] fix 718624 and 734467 --- debian/changelog| 33 + debian/transmission-daemon.dirs | 1 - debian/transmission-daemon.links| 3 ++- debian/transmission-daemon.postinst | 9 ++--- debian/transmission-daemon.postrm | 4 debian/transmission-daemon.preinst | 23 +++ 6 files changed, 68 insertions(+), 5 deletions(-) create mode 100644 debian/transmission-daemon.preinst diff --git a/debian/changelog b/debian/changelog index 780b145..4ec85ff 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,36 @@ +transmission (2.82-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * transmission-daemon.postinst: +- Change home directory of transmission-daemon to + /var/lib/transmission-daemon from /home/debian-transmission. + Thanks to Alex Peters for the report. (Closes: #734467) +- Disable password authentication for debian-transmission user for improved + security. Logins with e.g. SSH RSA keys are still possible. +- Check existence of debian-transmission user with getent passwd + debian-transmission instead of id. + * Add transmission-daemon.preinst: +- Fix permissions in /var/lib/transmission-daemon and use + /var/lib/transmission-daemon as the new home directory. +- Move old configuration files to appropriate config directory + /var/lib/transmission-daemon/.config/transmission-daemon. + All together this ensures that transmission-daemon will not segfault when + systemd is the default init system. + Thanks to Andrei Popescu and Antoine Legonidec for the report and + additional tests. (Closes: #718624) + * transmission-daemon.links: +- Link settings.json from /etc/transmission-daemon/settings.json to + /var/lib/transmission-daemon/.config/transmission-daemon. +- Link /var/lib/transmission-daemon/.config/transmission-daemon to + /var/lib/transmission-daemon/info due to compatibility reasons with the + old sysv-rc init script settings. + * transmission-daemon.dirs: +- Do not create /var/lib/transmission-daemon/info anymore. + * transmission-daemon.postrm: +- Also delete debian-transmission user when purging the daemon. + + -- Markus Koschany a...@gambaru.de Mon, 07 Apr 2014 19:34:39 +0200 + transmission (2.82-1.1) unstable; urgency=medium * Non-maintainer upload. diff --git a/debian/transmission-daemon.dirs b/debian/transmission-daemon.dirs index 7d6fc68..0fe0558 100644 --- a/debian/transmission-daemon.dirs +++ b/debian/transmission-daemon.dirs @@ -1,2 +1 @@ -/var/lib/transmission-daemon/info /var/lib/transmission-daemon/downloads diff --git
Processed: Re: Bug#718624: Bug#742626: transmission-daemon: SEGFAULT on first run, breaks installation
Processing commands for cont...@bugs.debian.org: retitle 718624 transmission-daemon: segfaults with systemd due to erroneous maintainer scripts Bug #718624 [transmission-daemon] transmission-daemon: segfaults with systemd enabled due to erroneous service file Bug #742626 [transmission-daemon] transmission-daemon: segfaults with systemd enabled due to erroneous service file Changed Bug title to 'transmission-daemon: segfaults with systemd due to erroneous maintainer scripts' from 'transmission-daemon: segfaults with systemd enabled due to erroneous service file' Changed Bug title to 'transmission-daemon: segfaults with systemd due to erroneous maintainer scripts' from 'transmission-daemon: segfaults with systemd enabled due to erroneous service file' tags 718624 patch Bug #718624 [transmission-daemon] transmission-daemon: segfaults with systemd due to erroneous maintainer scripts Bug #742626 [transmission-daemon] transmission-daemon: segfaults with systemd due to erroneous maintainer scripts Added tag(s) patch. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 718624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718624 742626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707402: umview: FTBFS: um_select.c:177: undefined reference to `__FDELT'
Hi Gregor, On Sat, Nov 30, 2013 at 06:49:45PM +0100, gregor herrmann wrote: On Wed, 10 Jul 2013 21:00:11 +0200, gregor herrmann wrote: [...] Ubuntu seems to have a patch for this: https://patches.ubuntu.com/u/umview/umview_0.8.2-1ubuntu2.patch Attached are the Ubuntu changes as debdiff; with the changes the packages build in unstable, but not anymore in stable. Not sure if we care about this ... This bug block fuse-umfuse-iso9660 and furiusisomount migrate to testing. Is it any chance you upload an NMU for this bug? Regards, Prach -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741792: [Pkg-pascal-devel] Bug#741792: doublecmd FTBFS
Control: severity -1 normal On 07-04-14 08:06, Abou Al Montacir wrote: The decision to mark packages as Manually built was due to the fact that these are considered as provider binaries. Clear (an I thought so). Let's call these package library packages. So users need to work with them in their binary format. Indeed, but it is our task to make sure it actually works (similar to c where you have to state the right include foo.h things). I didn't update the package yet, as you (Abou) seem to have a much clearer picture of fpc and lazarus than I have, that is why I shared my observations. If you remove this, then Lazarus will build them in the user's home directory for each user. Ok, let's not do that then, if we can figure out what goes wrong with doublecmd There are 2 points here: I assume you added the third one later ;) 1) It not relevant to package binary files if you know it will never be used Ack 2) On multi-user system this is consuming a huge amount of memory useless. Ack (or disk space) 3) It is working only because the source package is installed, while this one is optional. Yeh, right. So I don't agree that we need to remove the manual build flag, and I don't agree that this is a critical bug as LC-QT is a alpha feature. Aha, now we are getting somewhere. If this QT thing is Alpha, why doesn't our package description say so. That would make things much clearer. I didn't know this for one thing, and I am building a qt version of my package winff, similar as Graham is doing with his package doublecmd. I'd ask kindly to lower this bug severity or will do it myself in order to avoid a useless removal from testing scheduled for April 14th. Done, but it doesn't solve the original problem for doublecmd as a qt package was build in the past. So the question remains, how should projects (or Debian packages) be handling this in a robust way? Apparently depending on the right package is not enough. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: [Pkg-pascal-devel] Bug#741792: doublecmd FTBFS
Processing control commands: severity -1 normal Bug #741792 [src:doublecmd] doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory Severity set to 'normal' from 'serious' -- 741792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Processed: Re: [Pkg-pascal-devel] Bug#741792: doublecmd FTBFS
Processing commands for cont...@bugs.debian.org: # OOPS # On 07-04-14 20:09, Debian Bug Tracking System wrote: # Processing control commands: # # severity -1 normal # Bug #741792 [src:doublecmd] doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory Unknown command or malformed arguments to command. # Severity set to 'normal' from 'serious' # What I meant was: severity 742734 normal Bug #742734 [lazarus] controls in lazarus/components should be marked auto Severity set to 'normal' from 'serious' # Reverting my mystake: severity 741792 serious Bug #741792 [src:doublecmd] doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory Severity set to 'serious' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. -- 741792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741792 742734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707402: umview: FTBFS: um_select.c:177: undefined reference to `__FDELT'
On Tue, 08 Apr 2014 01:07:42 +0700, Prach Pongpanich wrote: Attached are the Ubuntu changes as debdiff; with the changes the packages build in unstable, but not anymore in stable. Not sure if we care about this ... This bug block fuse-umfuse-iso9660 and furiusisomount migrate to testing. Is it any chance you upload an NMU for this bug? In theory yes; in practice it fails now with: gcc -DHAVE_CONFIG_H -I. -I.. -Wall -I../include -D_GNU_SOURCE -DLIBEXECDIR=\/usr/lib/umview\ -DMODULES_DIR=\/usr/lib/umview/modules\ -D_UM_MMAP -D_UM_EPOLL -D_VIEWOS_KM -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c -o kmview-um_select.o `test -f 'um_select.c' || echo './'`um_select.c um_select.c: In function 'wrap_in_epoll_create': um_select.c:468:28: error: 'EPOLL_NONBLOCK' undeclared (first use in this function) flags = (EPOLL_CLOEXEC | EPOLL_NONBLOCK); ^ Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Ostbahn-Kurti Die Chefpartie: Tequila Sunrise signature.asc Description: Digital Signature
Bug#718624: transmission-daemon: SEGFAULT on first run, breaks installation
On 04/07/2014 08:03 PM, Markus Koschany wrote: retitle 718624 transmission-daemon: segfaults with systemd due to erroneous maintainer scripts tags 718624 patch thanks On 07.04.2014 12:10, Andrei POPESCU wrote: [...] If you build a package with your patch applied I'll try to do some testing. Hello Andrei and Antoine, thanks for offering a helping hand with this bug. I have prepared a patch which I'm attaching to this bug report. I could also build a binary package but I recommend to apply the patch yourself and then to build everything from source. Here is the changelog: (…) Regards, Markus It just works, well done! signature.asc Description: OpenPGP digital signature
Bug#741801: marked as done (pp-popularity-contest: FTBFS: configure: error: Could not find a version of the library! (Boost multiarch issues))
Your message dated Mon, 07 Apr 2014 19:49:14 + with message-id e1wxfxe-00018u...@franck.debian.org and subject line Bug#741801: fixed in pp-popularity-contest 1.0.6-2 has caused the Debian Bug report #741801, regarding pp-popularity-contest: FTBFS: configure: error: Could not find a version of the library! (Boost multiarch issues) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 741801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pp-popularity-contest Version: 1.0.6-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140315 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): checking whether g++ accepts -g... yes checking dependency style of g++... none checking for ranlib... ranlib checking for boostlib = 1.20.0... yes checking whether the Boost::Program_Options library is available... yes configure: error: Could not find a version of the library! The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/03/15/pp-popularity-contest_1.0.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Source: pp-popularity-contest Source-Version: 1.0.6-2 We believe that the bug you reported is fixed in the latest version of pp-popularity-contest, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 741...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Kajan lka...@debian.org (supplier of updated pp-popularity-contest package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 07 Apr 2014 20:41:09 +0200 Source: pp-popularity-contest Binary: pp-popularity-contest pp-popularity-contest-dbg Architecture: source amd64 Version: 1.0.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Laszlo Kajan lka...@debian.org Description: pp-popularity-contest - PredictProtein popularity contest pp-popularity-contest-dbg - debug files for pp-popularity-contest Closes: 733230 741801 Changes: pp-popularity-contest (1.0.6-2) unstable; urgency=medium . * Fixes configure: error: Could not find a version of the library (Closes: #741801). * Fixes FTBFS: Automake 1.14.1 used, Automake 1.14 required (Closes: #733230). Checksums-Sha1: 52bb64eb7760e865865c1f31498c1d072a4c9e79 2246 pp-popularity-contest_1.0.6-2.dsc 3d92b6a7feef5952913d82e3577004adeee593f0 4128 pp-popularity-contest_1.0.6-2.debian.tar.xz 23638f8d496521b7f5bebfccc3b0f7fc1bf87684 35102 pp-popularity-contest_1.0.6-2_amd64.deb 61af0b971a752ad9f6906c0c80980288be372913 180844 pp-popularity-contest-dbg_1.0.6-2_amd64.deb Checksums-Sha256: 283a861dc5fa8831725e5a7e8166772fd59b8417c9ee4ab839a19ce33f4e327c 2246 pp-popularity-contest_1.0.6-2.dsc b4935a92a1e9b3d8a5edff383a18772d332a78d91fd156280aceac3d0cad8648 4128 pp-popularity-contest_1.0.6-2.debian.tar.xz 0664f935f8acfe16a108589df7ce0b2d63ee2ffa0d05dabeb837300779811038 35102 pp-popularity-contest_1.0.6-2_amd64.deb 2ff2690ad353fe70c7d87a422c609ecc7b45f92c32935c626b930689b4dfcd96 180844 pp-popularity-contest-dbg_1.0.6-2_amd64.deb Files: beac1178b4ea4a55401fc26a85deb524 2246 science extra pp-popularity-contest_1.0.6-2.dsc 5c2ad2f4e94464fb01944d44b3163e84 4128 science extra pp-popularity-contest_1.0.6-2.debian.tar.xz fd3b5e0b50c3d1936976c0a509d7b721 35102 science extra pp-popularity-contest_1.0.6-2_amd64.deb 77d845cf2b8108c18055f09bc32d48ed 180844 debug extra pp-popularity-contest-dbg_1.0.6-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux)
Bug#743880: maxima: Segmentation fault
Package: maxima Version: 5.33.0-1 Severity: grave Dear Maintainer, calling 'maxima' on my system leads to a segmentation fault: toto@catweazle:~$ maxima -v + '[' gcl = clisp ']' + '[' gcl = cmucl ']' + '[' gcl = scl ']' + '[' gcl = gcl ']' + exec /usr/lib/maxima/5.33.0/binary-gcl/maxima -eval '(cl-user::run)' -f -- -v '' '' '' '' '' '' '' '' Segmentation fault Downgrading the maxima packages down to 5.32.1-1 makes 'maxima' usable again. Toto -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages maxima depends on: ii gnuplot-x11 4.6.5-1 ii libc6 2.18-4 ii libgmp10 2:6.0.0+dfsg-2 ii libreadline6 6.3-6 ii libx11-6 2:1.6.2-1 Versions of packages maxima recommends: ii maxima-share 5.32.1-1 Versions of packages maxima suggests: ii maxima-doc5.32.1-1 ii maxima-emacs 5.32.1-1 pn texmacs none ii tk [wish] 8.6.0+8 ii xmaxima 5.32.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741792: [Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
Hi All, Control: severity -1 normal Great, On 07-04-14 08:06, Abou Al Montacir wrote: The decision to mark packages as Manually built was due to the fact that these are considered as provider binaries. Clear (an I thought so). Let's call these package library packages. Pascal units are a kind of libraries. If to be compared with C/C++ .ppu files are kind of precompiled headers and .o are pure object files. So users need to work with them in their binary format. Indeed, but it is our task to make sure it actually works (similar to c where you have to state the right include foo.h things). I didn't update the package yet, as you (Abou) seem to have a much clearer picture of fpc and lazarus than I have, that is why I shared my observations. Yes of course, we need to ensure Lazarus is clean and compiling correctly the projects using it. But it could happen that some evolutions break backward compatibility. Here, the main problem I can fond in the logs is: ERROR: package not found: /usr/lib/lazarus/default/ideintf/ideintf.lpk Looking at my laptop I can find: $find /usr/lib/lazarus/default/ -name ideintf.lpk /usr/lib/lazarus/default/components/ideintf/ideintf.lpk So this .lpk file migrated from a location to the other. This is not my decision but upstream's one. If you remove this, then Lazarus will build them in the user's home directory for each user. Ok, let's not do that then, if we can figure out what goes wrong with doublecmd I'll try to build this package, but currently I'm lacking time. There are 2 points here: I assume you added the third one later ;) 1) It not relevant to package binary files if you know it will never be used Ack 2) On multi-user system this is consuming a huge amount of memory useless. Ack (or disk space) 3) It is working only because the source package is installed, while this one is optional. Yeh, right. I can't image that some package build-depends on lazarus-src! Sorry but this is a complete nonsense. So The option of removing Manually is not one. So I don't agree that we need to remove the manual build flag, and I don't agree that this is a critical bug as LC-QT is a alpha feature. Aha, now we are getting somewhere. If this QT thing is Alpha, why doesn't our package description say so. That would make things much clearer. I didn't know this for one thing, and I am building a qt version of my package winff, similar as Graham is doing with his package doublecmd. Do you mean that you will package two versions of WinFF? Does this make sense? I know I was the first who open this door and packages the IDE twice, but now I'm realizing I did a big mistake probably. I really hate that LCL could not build as .so and that could choose that backend at run time. I'd ask kindly to lower this bug severity or will do it myself in order to avoid a useless removal from testing scheduled for April 14th. Done, but it doesn't solve the original problem for doublecmd as a qt package was build in the past. So the question remains, how should projects (or Debian packages) be handling this in a robust way? Apparently depending on the right package is not enough. I can't answer this one right now, but will probably do this in the next days. Paul Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#741792: [Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory
On Mon, 2014-04-07 at 22:39 +0200, Abou Al Montacir wrote: Apparently depending on the right package is not enough. I can't answer this one right now, but will probably do this in the next days. I just quickly downloaded .tar.gz and .debian.tar.gz and built it without any issue using latest Lazarus. The only thing is that I have a full installation. This looks like a dependency issue in doublecmd. I'll find out what package is missing if none is candidate to do this. Cheers, Abou Al Montacir, signature.asc Description: This is a digitally signed message part
Bug#743883: CVE-2014-0160 heartbeat read overrun (heartbleed)
Package: openssl Version: 1.0.1f-1 Severity: grave A serious flaw has been discovered in OpenSSL versions 1.0.1 through 1.0.1f. This bug can allow an attacker to read process memory on vulnerable systems leading to exposure of the private key. Please see: http://www.openssl.org/news/secadv_20140407.txt http://heartbleed.com/ Debian will need to patch OpenSSL in sid, jessie, and wheezy, and all keys used with vulnerable processes will need to be replaced both in Debian infrastructure and by all users of this package. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 743883 in 1.0.1e-2
Processing commands for cont...@bugs.debian.org: found 743883 1.0.1e-2 Bug #743883 [openssl] CVE-2014-0160 heartbeat read overrun (heartbleed) Marked as found in versions openssl/1.0.1e-2. thanks Stopping processing here. Please contact me if you need assistance. -- 743883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fixed 743883 in 1.0.1e-2+deb7u5
Processing commands for cont...@bugs.debian.org: fixed 743883 1.0.1e-2+deb7u5 Bug #743883 [openssl] CVE-2014-0160 heartbeat read overrun (heartbleed) There is no source info for the package 'openssl' at version '1.0.1e-2+deb7u5' with architecture '' Unable to make a source version for version '1.0.1e-2+deb7u5' Marked as fixed in versions 1.0.1e-2+deb7u5. thanks Stopping processing here. Please contact me if you need assistance. -- 743883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743883: [Pkg-openssl-devel] Bug#743883: CVE-2014-0160 heartbeat read overrun (heartbleed)
found 743883 1.0.1e-2 fixed 743883 + 1.0.1-g fixed 743883 + 1.0.1e-2+deb7u5 close 743883 thanks On Mon, Apr 07, 2014 at 09:11:09PM +, Travis Cross wrote: Package: openssl Version: 1.0.1f-1 Severity: grave A serious flaw has been discovered in OpenSSL versions 1.0.1 through 1.0.1f. This bug can allow an attacker to read process memory on vulnerable systems leading to exposure of the private key. Please see: http://www.openssl.org/news/secadv_20140407.txt http://heartbleed.com/ Debian will need to patch OpenSSL in sid, jessie, and wheezy, and all keys used with vulnerable processes will need to be replaced both in Debian infrastructure and by all users of this package. ___ Pkg-openssl-devel mailing list pkg-openssl-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-openssl-devel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): Re: [Pkg-openssl-devel] Bug#743883: CVE-2014-0160 heartbeat read overrun (heartbleed)
Processing commands for cont...@bugs.debian.org: found 743883 1.0.1e-2 Bug #743883 [openssl] CVE-2014-0160 heartbeat read overrun (heartbleed) Ignoring request to alter found versions of bug #743883 to the same values previously set fixed 743883 + 1.0.1-g Unknown command or malformed arguments to command. fixed 743883 + 1.0.1e-2+deb7u5 Unknown command or malformed arguments to command. close 743883 Bug #743883 [openssl] CVE-2014-0160 heartbeat read overrun (heartbleed) Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 743883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743889: libssl1.0.0: libssl update does not cause applications that use it to restart
Package: libssl1.0.0 Version: 1.0.1e-2+deb7u5 Severity: grave Tags: security Justification: user security hole Dear Maintainer, when I did apt-get updateapt-get upgrade today to get a fix for CVE-2014-0160, I got this from apt: Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u5) ... Setting up libssl-dev (1.0.1e-2+deb7u5) ... Setting up openssh-client (1:6.0p1-4+deb7u1) ... Setting up openssh-server (1:6.0p1-4+deb7u1) ... [ ok ] Restarting OpenBSD Secure Shell server: sshd. Setting up a2ps (1:4.14-1.1+deb7u1) ... Setting up libxalan2-java (2.7.1-7+deb7u1) ... Setting up openssl (1.0.1e-2+deb7u5) ... It restarted OpenSSH... and only OpenSSH. I then ran this command: root@thejh:/home/jann# for pid in $(grep -F '/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (deleted)' /proc/*/maps | cut -d/ -f3 | sort -u); do cat /proc/$pid/cmdline | tr '\0' ' '; echo; done /usr/lib/erlang/erts-5.9.1/bin/beam -Bd -K true -A 4 -- -root /usr/lib/erlang -progname erl -- -home /var/lib/couchdb -- -noshell -noinput -os_mon start_memsup false start_cpu_sup false disk_space_check_interval 1 disk_almost_full_threshold 1 -sasl errlog_type error -couch_ini /etc/couchdb/default.ini /etc/couchdb/local.ini /etc/couchdb/default.ini /etc/couchdb/local.ini -s couch -pidfile /var/run/couchdb/couchdb.pid -heart /usr/bin/couchjs /usr/share/couchdb/server/main.js /usr/bin/couchjs /usr/share/couchdb/server/main.js /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/stunnel4 /etc/stunnel/stunnel.conf /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf /usr/lib/postfix/master /usr/sbin/vsftpd /usr/bin/znc -d /etc/znc pickup -l -t fifo -u -c anvil -l -t unix -u -c smtpd -n smtp -t inet -u -c -o stress= -s 2 irssi /usr/sbin/openvpn --writepid /var/run/openvpn.tun0.pid --daemon ovpn-tun0 --cd /etc/openvpn --config /etc/openvpn/tun0.conf qmgr -l -t fifo -u tlsmgr -l -t unix -u -c So, uh, looks like although the fixed library is on my system, all the interesting and maybe-affected services (like couchdb, stunnel, lighttpd, postfix, ...) are still vulnerable until I reboot my server, which is not exactly standard procedure after installing updates? -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libssl1.0.0 depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u1 ii multiarch-support 2.13-38+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 libssl1.0.0 recommends no packages. libssl1.0.0 suggests no packages. -- debconf information: libssl1.0.0/restart-failed: libssl1.0.0/restart-services: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735940:
We've run into a snag: the file d3-2.4.6.time.min.js (or any more recent version of that file) does not appear to be packaged in the libjs-d3 package. Loading only d3.min.js is not sufficient, since it does not include the d3.time module. We cannot find any other Debian package that includes it. In addition, version 3.3.13-1 of libjs-d3 contains a d3.min.js file that is not binary-identical to the d3.min.js from the upstream d3 project (downloadable from https://github.com/mbostock/d3/releases/tag/v3.3.13). We are loath to proceed with using the Debian version without knowing what the differences from upstream are. (They could just be differences in minification, but that isn't clear.) -- Daira Hopwood ⚥ signature.asc Description: OpenPGP digital signature
Bug#743889: [Pkg-openssl-devel] Bug#743889: libssl1.0.0: libssl update does not cause applications that use it to restart
On Tue, Apr 08, 2014 at 01:12:34AM +0200, Jann Horn wrote: Package: libssl1.0.0 Version: 1.0.1e-2+deb7u5 Severity: grave Tags: security Justification: user security hole Dear Maintainer, when I did apt-get updateapt-get upgrade today to get a fix for CVE-2014-0160, I got this from apt: Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u5) ... Setting up libssl-dev (1.0.1e-2+deb7u5) ... Setting up openssh-client (1:6.0p1-4+deb7u1) ... Setting up openssh-server (1:6.0p1-4+deb7u1) ... [ ok ] Restarting OpenBSD Secure Shell server: sshd. Setting up a2ps (1:4.14-1.1+deb7u1) ... Setting up libxalan2-java (2.7.1-7+deb7u1) ... Setting up openssl (1.0.1e-2+deb7u5) ... It restarted OpenSSH... and only OpenSSH. I then ran this command: openssh actually isn't affected, you also just got an update for it that caused it to restart. The openssl update did not have anything to do with the update restarting of openssl. So, uh, looks like although the fixed library is on my system, all the interesting and maybe-affected services (like couchdb, stunnel, lighttpd, postfix, ...) are still vulnerable until I reboot my server, which is not exactly standard procedure after installing updates? We have code that checks some of the applications that need to be restarted, but it has a static list of packages to check and it's outdated. We're working on improving that list and providing an other update that will restart those services. In the mean that I suggest you reboot your system or use something like checkrestart (from debian-goodies). Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfixed 743883 in 1.0.1-g, fixed 743883 in 1.0.1g-1
Processing commands for cont...@bugs.debian.org:
notfixed 743883 1.0.1-g
Bug #743883 {Done: Kurt Roeckx k...@roeckx.be} [openssl] CVE-2014-0160
heartbeat read overrun (heartbleed)
There is no source info for the package 'openssl' at version '1.0.1-g' with
architecture ''
Unable to make a source version for version '1.0.1-g'
Ignoring request to alter fixed versions of bug #743883 to the same values
previously set
fixed 743883 1.0.1g-1
Bug #743883 {Done: Kurt Roeckx k...@roeckx.be} [openssl] CVE-2014-0160
heartbeat read overrun (heartbleed)
Marked as fixed in versions openssl/1.0.1g-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
743883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopening 696146
Processing commands for cont...@bugs.debian.org:
reopen 696146
Bug #696146 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[xemacs21-nomule,xemacs21-mule-canna-wnn] xemacs21-nomule,
xemacs21-mule-canna-wnn: prerm deletes files owned by xemacs21-support:
/usr/lib/xemacs-21.4.22/{etc, lisp}
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 21.4.22-4+rm.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
696146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: unarchiving 696146
Processing commands for cont...@bugs.debian.org:
unarchive 696146
Bug #696146 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org}
[xemacs21-nomule,xemacs21-mule-canna-wnn] xemacs21-nomule,
xemacs21-mule-canna-wnn: prerm deletes files owned by xemacs21-support:
/usr/lib/xemacs-21.4.22/{etc, lisp}
Unarchived Bug 696146
thanks
Stopping processing here.
Please contact me if you need assistance.
--
696146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696146: xemacs21-nomule, xemacs21-mule-canna-wnn: prerm deletes files owned by xemacs21-support: /usr/lib/xemacs-21.4.22/{etc, lisp}
This bug is still present in the current version of xemacs21 in the archives, therefore re-opening. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#743889: libssl1.0.0: libssl update does not cause applications that use it to restart
Processing control commands: found -1 openssl/1.0.1e-2+deb7u4 Bug #743889 [libssl1.0.0] libssl1.0.0: libssl update does not cause applications that use it to restart Marked as found in versions openssl/1.0.1e-2+deb7u4. -- 743889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743889: libssl1.0.0: libssl update does not cause applications that use it to restart
Control: found -1 openssl/1.0.1e-2+deb7u4 Hi, A helpful trick I found after upgrade is to: # lsof -nnP | grep libssl.so.1 Look for entries that mention an inode number - this means an unlinked, older version of the library rather than the one currently at that path: nginx 23947root mem REG 254,2 1452500 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (path dev=0,17, inode=1454629) After restarting the service, the process's pid changes obviously, but is now using the current version of libssl too: nginx 3791root mem REG 254,2 1454629 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (path dev=0,17) I discovered today that many services had not even restarted since the *last* openssl security upgrade. The DSA does mention it though. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743890: php-json: Build dependency loop
Source: php-json Version: 1.3.4-1 Severity: serious Justification: FTBFS Hello, There is a problem with building php-json on buildds, for instance the i386 status is: BD-Problem : php-json build-depends on: - php5-cli (= 5.5.0~rc1+dfsg-1~) php5-cli depends on: - php5-common (= 5.5.11+dfsg-1) php5-common depends on: - php5-json php5-json depends on missing: - phpapi-20121212 So to rebuild php-json against the new php api, one has to rebuild it against the new php api, so that php5-common becomes installable again, we have a chicken and egg issue here. Samuel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.0 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Samuel Q: How do you play religious roulette? A: You stand around in a circle and blaspheme and see who gets struck by lightning first. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741848: gst-plugins-ugly0.10: diff for NMU version 0.10.19-2.1
tags 741848 + pending thanks Dear maintainer, I've prepared an NMU for gst-plugins-ugly0.10 (versioned as 0.10.19-2.1) and uploaded it to unstable. I hope you don't mind me avoiding the DELAYED queue, but the patch has been sitting in the BTS over a week now, and this package is currently blocking the libx264-142 transition: https://release.debian.org/transitions/html/libx264-142.html Regarding the patch itself, the BTS contains two patches that workaround the same issue: AC_CHECK_A52DEC always returns HAVE_A52DEC=no. Matthias identified the reason why this recently broke: In a52dec_0.7.4-17, I have made the struct a52_state_t visible again, because the handbrake package currently makes use of that struct. Given the lack of development on the a52dec front, I asserted that this wouldn't break existing packages, but it seems that m4/a52.m4 of this package explicitly checks for the availabity of this struct, and asserts that a52dec was too old if this type is present. Ideally the test should be rewritten, but for the purposes of Debian/Ubuntu, disabling the check as done by Hideki seems just fine to me. Regards, Reinhard diff -Nru gst-plugins-ugly0.10-0.10.19/debian/changelog gst-plugins-ugly0.10-0.10.19/debian/changelog --- gst-plugins-ugly0.10-0.10.19/debian/changelog 2012-04-23 02:53:01.0 -0400 +++ gst-plugins-ugly0.10-0.10.19/debian/changelog 2014-04-07 20:26:02.0 -0400 @@ -1,3 +1,11 @@ +gst-plugins-ugly0.10 (0.10.19-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches +- add a52dec.patch to enable a52dec module and closes: #741848 + + -- Hideki Yamane henr...@debian.org Mon, 24 Mar 2014 23:56:56 +0900 + gst-plugins-ugly0.10 (0.10.19-2) unstable; urgency=low * debian/patches/01_opencore-amr-0.1.3.patch: diff -Nru gst-plugins-ugly0.10-0.10.19/debian/patches/a52dec.patch gst-plugins-ugly0.10-0.10.19/debian/patches/a52dec.patch --- gst-plugins-ugly0.10-0.10.19/debian/patches/a52dec.patch 1969-12-31 19:00:00.0 -0500 +++ gst-plugins-ugly0.10-0.10.19/debian/patches/a52dec.patch 2014-04-07 20:25:26.0 -0400 @@ -0,0 +1,23 @@ +Description: enable A52DEC module generation + + AC_CHECK_A52DEC always returns HAVE_A52DEC=no so module would not + be generated. This patch changes to do it. + +Author: Hideki Yamane henr...@debian.org +Bug-Debian: http://bugs.debian.org/741848 +Forwarded: no +Last-Update: 2014-03-26 + +Index: gst-plugins-ugly0.10-0.10.19/configure.ac +=== +--- gst-plugins-ugly0.10-0.10.19.orig/configure.ac gst-plugins-ugly0.10-0.10.19/configure.ac +@@ -242,7 +242,7 @@ echo + dnl *** a52dec *** + translit(dnm, m, l) AM_CONDITIONAL(USE_A52DEC, true) + AG_GST_CHECK_FEATURE(A52DEC, [a52dec], a52dec, [ +- AC_CHECK_A52DEC(HAVE_A52DEC=yes, HAVE_A52DEC=no) ++ AC_CHECK_A52DEC(,HAVE_A52DEC=yes) + ]) + + dnl *** amr-nb *** diff -Nru gst-plugins-ugly0.10-0.10.19/debian/patches/series gst-plugins-ugly0.10-0.10.19/debian/patches/series --- gst-plugins-ugly0.10-0.10.19/debian/patches/series 2012-04-23 02:52:15.0 -0400 +++ gst-plugins-ugly0.10-0.10.19/debian/patches/series 2014-04-07 20:22:13.0 -0400 @@ -1,2 +1,3 @@ 01_opencore-amr-0.1.3.patch 99_ltmain_as-needed.patch +a52dec.patch
Processed: gst-plugins-ugly0.10: diff for NMU version 0.10.19-2.1
Processing commands for cont...@bugs.debian.org: tags 741848 + pending Bug #741848 [src:gst-plugins-ugly0.10] gst-plugins-ugly0.10: FTBFS: dh_install: gstreamer0.10-plugins-ugly missing files (debian/tmp/usr/lib/*/gstreamer-0.10/libgsta52dec.so), aborting Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 741848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741848: marked as done (gst-plugins-ugly0.10: FTBFS: dh_install: gstreamer0.10-plugins-ugly missing files (debian/tmp/usr/lib/*/gstreamer-0.10/libgsta52dec.so), aborting)
Your message dated Tue, 08 Apr 2014 00:49:32 + with message-id e1wxkeg-00047t...@franck.debian.org and subject line Bug#741848: fixed in gst-plugins-ugly0.10 0.10.19-2.1 has caused the Debian Bug report #741848, regarding gst-plugins-ugly0.10: FTBFS: dh_install: gstreamer0.10-plugins-ugly missing files (debian/tmp/usr/lib/*/gstreamer-0.10/libgsta52dec.so), aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 741848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gst-plugins-ugly0.10 Version: 0.10.19-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140315 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[3]: Entering directory `/«PKGBUILDDIR»' make[3]: Nothing to be done for `install-exec-am'. make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/«PKGBUILDDIR»' make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: Leaving directory `/«PKGBUILDDIR»' touch debian/stamp-makefile-install Adding cdbs dependencies to debian/gstreamer0.10-plugins-ugly-doc.substvars dh_installdirs -pgstreamer0.10-plugins-ugly-doc dh_installdocs -pgstreamer0.10-plugins-ugly-doc ./README ./NEWS ./AUTHORS debian/README.Debian NEWS dh_installexamples -pgstreamer0.10-plugins-ugly-doc dh_installman -pgstreamer0.10-plugins-ugly-doc dh_installinfo -pgstreamer0.10-plugins-ugly-doc dh_installmenu -pgstreamer0.10-plugins-ugly-doc dh_installcron -pgstreamer0.10-plugins-ugly-doc dh_installinit -pgstreamer0.10-plugins-ugly-doc dh_installdebconf -pgstreamer0.10-plugins-ugly-doc dh_installemacsen -pgstreamer0.10-plugins-ugly-doc dh_installcatalogs -pgstreamer0.10-plugins-ugly-doc dh_installpam -pgstreamer0.10-plugins-ugly-doc dh_installlogrotate -pgstreamer0.10-plugins-ugly-doc dh_installlogcheck -pgstreamer0.10-plugins-ugly-doc dh_installchangelogs -pgstreamer0.10-plugins-ugly-doc dh_installudev -pgstreamer0.10-plugins-ugly-doc dh_lintian -pgstreamer0.10-plugins-ugly-doc dh_bugfiles -pgstreamer0.10-plugins-ugly-doc dh_install -pgstreamer0.10-plugins-ugly-doc dh_link -pgstreamer0.10-plugins-ugly-doc dh_installmime -pgstreamer0.10-plugins-ugly-doc dh_installgsettings -pgstreamer0.10-plugins-ugly-doc dh_gconf -pgstreamer0.10-plugins-ugly-doc dh_icons -pgstreamer0.10-plugins-ugly-doc dh_strip -pgstreamer0.10-plugins-ugly-doc --dbg-package=gstreamer0.10-plugins-ugly-dbg dh_compress -pgstreamer0.10-plugins-ugly-doc dh_fixperms -pgstreamer0.10-plugins-ugly-doc dh_makeshlibs -pgstreamer0.10-plugins-ugly-doc dh_installdeb -pgstreamer0.10-plugins-ugly-doc dh_perl -pgstreamer0.10-plugins-ugly-doc dh_shlibdeps -pgstreamer0.10-plugins-ugly-doc dh_gencontrol -pgstreamer0.10-plugins-ugly-doc dh_md5sums -pgstreamer0.10-plugins-ugly-doc dh_builddeb -pgstreamer0.10-plugins-ugly-doc -u-Zxz dpkg-deb: building package `gstreamer0.10-plugins-ugly-doc' in `../gstreamer0.10-plugins-ugly-doc_0.10.19-2_all.deb'. Adding cdbs dependencies to debian/gstreamer0.10-plugins-ugly.substvars dh_installdirs -pgstreamer0.10-plugins-ugly Adding cdbs dependencies to debian/gstreamer0.10-plugins-ugly-dbg.substvars dh_installdirs -pgstreamer0.10-plugins-ugly-dbg dh_installdocs -pgstreamer0.10-plugins-ugly ./README ./NEWS ./AUTHORS debian/README.Debian NEWS dh_installexamples -pgstreamer0.10-plugins-ugly dh_installman -pgstreamer0.10-plugins-ugly dh_installinfo -pgstreamer0.10-plugins-ugly dh_installmenu -pgstreamer0.10-plugins-ugly dh_installcron -pgstreamer0.10-plugins-ugly dh_installinit -pgstreamer0.10-plugins-ugly dh_installdebconf -pgstreamer0.10-plugins-ugly dh_installemacsen -pgstreamer0.10-plugins-ugly dh_installcatalogs -pgstreamer0.10-plugins-ugly dh_installpam -pgstreamer0.10-plugins-ugly dh_installlogrotate -pgstreamer0.10-plugins-ugly dh_installlogcheck -pgstreamer0.10-plugins-ugly dh_installchangelogs -pgstreamer0.10-plugins-ugly dh_installudev -pgstreamer0.10-plugins-ugly dh_lintian -pgstreamer0.10-plugins-ugly dh_bugfiles -pgstreamer0.10-plugins-ugly dh_install -pgstreamer0.10-plugins-ugly dh_install: gstreamer0.10-plugins-ugly missing files (debian/tmp/usr/lib/*/gstreamer-0.10/libgsta52dec.so), aborting make: *** [binary-install/gstreamer0.10-plugins-ugly] Error 2 The full build log is available from:
Bug#743893: mediawiki: postinst uses php5enmod, but fails to depend on a php5-common that has it
Package: mediawiki Version: 1:1.19.15+dfsg-1 Severity: serious Justification: Policy 3.5 Setting up mediawiki (1:1.19.15+dfsg-1) ... /var/lib/dpkg/info/mediawiki.postinst: 78: php5enmod: not found dpkg: error processing mediawiki (--configure): subprocess installed post-installation script returned error exit status 127 $ dpkg -l php5-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++--- ii php5-common 5.3.3-7+squeeze19Common files for packages built from the php5 source Apparently, mediawiki needs a newer php5-common than that. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742940: since: Does not work on mips (includes test suite failures and FTBFS)
On Sat, 2014-03-29 07:17:33 +0100, Axel Beckert wrote: Package: since Version: 1.1-4 Severity: serious Tags: upstream Package version 1.1-4 added a build-time test-suite which revealed that since on mips does not work properly: $ echo foo foo $ since foo foo $ since foo since: considering foo to be truncated, displaying from start foo $ Expected behaviour would be: $ echo foo foo $ since foo foo $ since foo $ I'll contact upstream about this and #591386 and if we don't find a proper fix that soonish, I'll probably drop these two architectures from the package. At imgtec.com, we are testing a fix for this bug. A patch will be posted soon. Given the different symptoms, I suspect that this issue and #591386 (does not work on Hurd) are different issues. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Bug#669292: RFH: updating gitweb packaging for Apache 2.4
Hi, With Apache 2.2, the gitweb package worked out of the box. With Apache 2.4, it doesn't. http://bugs.debian.org/669292 tracks this problem. Last year, I tried to fix it --- patch at https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=23;filename=update-apache-packaging.patch;att=1;bug=669292 But I ran into several problems[*] around the upgrade path and uninstallation procedure. I think I understood how packaging for apache 2.2 worked, and I just don't understand how packaging for apache 2.4 works. [*] https://lists.debian.org/debian-webapps/2013/12/msg0.html In particular: * It's not clear when to run apache2_invoke enconf gitweb for a package like gitweb that does not have a Depends against apache 2.4. If I run it conditionally based on the Apache version, then gitweb will still be broken when the user upgrades apache, unless gitweb happens to be upgraded later in the same upgrade run. * It's not clear when to run apache2_invoke disconf gitweb. At remove and purge time doesn't seem to be enough. Until this is fixed, installing the gitweb package does not give the user a usable installation of gitweb, meaning I've been sitting with an RC bug for a long time. Help? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: php5-suhosin: With PHP 5.4, Suhosin doesn't actually load.
Processing control commands: tags -1 +fixed-upstream Bug #680145 [php5-suhosin] php5-suhosin: With PHP 5.4, Suhosin doesn't actually load. Added tag(s) fixed-upstream. -- 680145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680145: php5-suhosin: With PHP 5.4, Suhosin doesn't actually load.
control: tags -1 +fixed-upstream Not it's officially supported php5.4 in Version 0.9.35 see http://www.hardened-php.net/suhosin/changelog.html -- Hideki Yamane
Processed: Re: RFH: updating gitweb packaging for Apache 2.4
Processing commands for cont...@bugs.debian.org: found 669292 git/1:1.9.1-1 Bug #669292 [gitweb] gitweb: automatic configuration breaks with apache2 2.4 Bug #669798 [gitweb] gitweb: transition towards Apache 2.4 Marked as found in versions git/1:1.9.1-1. Marked as found in versions git/1:1.9.1-1. tags 669292 + help Bug #669292 [gitweb] gitweb: automatic configuration breaks with apache2 2.4 Bug #669798 [gitweb] gitweb: transition towards Apache 2.4 Added tag(s) help. Added tag(s) help. End of message, stopping processing here. Please contact me if you need assistance. -- 669292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669292 669798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743729: way out
Control: tag -1 pending
On Mon, Apr 07, 2014 at 12:22:20PM +0200, Christian Hofstaedtler wrote:
* Christian Hofstaedtler z...@debian.org [140406 23:33]:
I /think/ we should add this to all interpreter preinsts:
update-alternatives --remove-all ruby
On second thought, there are probably some corner cases; for one
this needs to be done in src:ruby-defaults, and we must ensure that
1.8 never gets configured again after the preinst runs.
I don't see how to guarantee that whatever workaround we come up
with won't break in a random way. I'd be much more comfortable with
readding the Conflicts on ruby1.8.
I think I achieved a solution:
http://anonscm.debian.org/gitweb/?p=collab-maint/ruby-defaults.git;a=commitdiff;h=8d8239020464f18e96c816b87cc6c7ca834a562f
I tested several different cases and it always succeeds in keeping the
symlinks pointing to default ruby, even if you reconfigure or reinstall
ruby1.8 and ruby1.9.1.
I admit that hacking /var/lib/dpkg/info/ruby{1.8,1.9.1}.postinst from
ruby.postinst is not very pretty, but the situation as a whole is
already not pretty. ;-)
--
Antonio Terceiro terce...@debian.org
signature.asc
Description: Digital signature
Processed: Re: Bug#743729: way out
Processing control commands: tag -1 pending Bug #743729 [ruby] ruby: badly handles transition away from alternatives, breaks dependant packages Added tag(s) pending. -- 743729: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 743096
Processing commands for cont...@bugs.debian.org: tags 743096 + pending fixed-upstream Bug #743096 [src:bzr] bzr: FTBFS: ValueError: invalid literal for int() with base 10: '1post0' Added tag(s) fixed-upstream and pending. thanks Stopping processing here. Please contact me if you need assistance. -- 743096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
