Bug#777024: gmediarender segfaults on startup on armel, raspbian and possiblly other architectures if gstreamer1.0-plugins-bad is installed.
package: gstreamer1.0-plugins-bad version: 1.4.3-2 severity: grave tags: patch We received a report in raspbian, that gmediarender was segfaulting on startup. Further investigation by the original reporter showed that it only happened if gstreamer1.0-plugins-bad was installed. https://bugs.launchpad.net/raspbian/+bug/1392850 The reporter took it to upstream who tracked the problem down to an incorrect call to a variadic function. https://bugzilla.gnome.org/show_bug.cgi?id=740191 http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?id=3e1d7630187dd96b137553aec2c6edb60c213682 AIUI this has the potential to crash on most 32-bit architectures (on 64-bit architectures I belive alignment requirements will mask the problem), whether it actually crashes depends on what happens to be on the stack/in the registers at the time. My tests have shown that this does not appear to crash on debian armhf at the moment but it does appear to crash on debian armel. While working on this issue I also ran into an unrepresentable changes to source error caused by incomplete cleanup in your clean target. So I fixed that too. Debdiff attatched, no intent to nmu P.S. theres some noise in the debdiff, looks like your clean target needs further work. diff -Nru gst-plugins-bad1.0-1.4.4/debian/changelog gst-plugins-bad1.0-1.4.4/debian/changelog --- gst-plugins-bad1.0-1.4.4/debian/changelog 2014-11-11 12:40:17.0 + +++ gst-plugins-bad1.0-1.4.4/debian/changelog 2015-02-03 22:25:43.0 + @@ -1,3 +1,18 @@ +gst-plugins-bad1.0 (1.4.4-2+rpi2) jessie-staging; urgency=medium + + * Really apply the patch to fix gmediarender segfault. + * Remove win32/common/config.h-new in clean target to prevent +unrepresentable changes to source error when building a second time. + + -- Peter Michael Green plugw...@raspbian.org Tue, 03 Feb 2015 22:10:57 + + +gst-plugins-bad1.0 (1.4.4-2+rpi1) jessie-staging; urgency=medium + + * Apply upstream patch to fix gmediarendered segfault on startup +(LP: 1392850) + + -- Peter Michael Green plugw...@raspbian.org Fri, 26 Dec 2014 14:24:44 + + gst-plugins-bad1.0 (1.4.4-2) unstable; urgency=medium * Upload to unstable. diff -Nru gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install --- gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-0.install 2014-12-26 15:22:08.0 + @@ -0,0 +1,10 @@ +debian/tmp/usr/lib/*/libgstphotography-1.0.so.* +debian/tmp/usr/lib/*/libgstbadbase-1.0.so.* +debian/tmp/usr/lib/*/libgstbadvideo-1.0.so.* +debian/tmp/usr/lib/*/libgstbasecamerabinsrc-1.0.so.* +debian/tmp/usr/lib/*/libgstgl-1.0.so.* +debian/tmp/usr/lib/*/libgstinsertbin-1.0.so.* +debian/tmp/usr/lib/*/libgstcodecparsers-1.0.so.* +debian/tmp/usr/lib/*/libgstmpegts-1.0.so.* +debian/tmp/usr/lib/*/libgsturidownloader-1.0.so.* +debian/tmp/usr/lib/arm-linux-gnueabihf/libgstwayland-1.0.so.* diff -Nru gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install --- gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/libgstreamer-plugins-bad1.0-dev.install 2014-12-26 15:22:08.0 + @@ -0,0 +1,3 @@ +debian/tmp/usr/include +debian/tmp/usr/lib/*/pkgconfig +debian/tmp/usr/lib/*/*.so diff -Nru gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch --- gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch 1970-01-01 00:00:00.0 + +++ gst-plugins-bad1.0-1.4.4/debian/patches/fix-segfault-varargs.patch 2015-02-03 22:12:57.0 + @@ -0,0 +1,21 @@ +commit 3e1d7630187dd96b137553aec2c6edb60c213682 +Author: Tim-Philipp Müller t...@centricular.com +Date: Sat Nov 15 21:59:48 2014 + + +dvbbasebin: fix possible crash by passing 64 bits for 64-bit queue property + +https://bugzilla.gnome.org/show_bug.cgi?id=740191 + +Index: gst-plugins-bad1.0-1.4.4/sys/dvb/dvbbasebin.c +=== +--- gst-plugins-bad1.0-1.4.4.orig/sys/dvb/dvbbasebin.c gst-plugins-bad1.0-1.4.4/sys/dvb/dvbbasebin.c +@@ -417,7 +417,7 @@ dvb_base_bin_init (DvbBaseBin * dvbbaseb + dvbbasebin-tsparse = gst_element_factory_make (tsparse, NULL); + + g_object_set (dvbbasebin-buffer_queue, max-size-buffers, 0, +- max-size-bytes, 0, max-size-time, 0, NULL); ++ max-size-bytes, 0, max-size-time, (guint64) 0, NULL); + + gst_bin_add_many (GST_BIN (dvbbasebin), dvbbasebin-dvbsrc, + dvbbasebin-buffer_queue, dvbbasebin-tsparse, NULL); diff -Nru gst-plugins-bad1.0-1.4.4/debian/patches/series
Bug#777027: fpc: fp-compiler-2.6.0 prevents upgrade of binutils
Package: fpc
Version: 2.6.4+dfsg-4
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package prevents binutils
from being upgraded automatically.
It installed fine in 'wheezy', but during the upgrade to 'jessie'
apt prefers to keep the obsolete fp-compiler-2.6.0 installed and
holds back the wheezy version of binutils.
fp-compiler-2.6.0 has Breaks: binutils-gold, but in jessie binutils-gold
is a virtual package provided by binutils. fp-compiler-2.6.4 no longer
cares about binutils-gold.
From the attached log (scroll to the bottom...):
20 fp-units-rtl-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
20 fp-units-rtl-2.6.4 [ amd64 ] none - 2.6.4+dfsg-4 ( devel )
15 fp-compiler-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
15 fp-compiler-2.6.4 [ amd64 ] none - 2.6.4+dfsg-4 ( devel )
4 binutils [ amd64 ] 2.22-8 - 2.24.90.20141023-1 ( devel )
-1 fpc-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
Starting 2
Investigating (0) fp-compiler-2.6.0 [ amd64 ] 2.6.0-9 ( devel )
Broken fp-compiler-2.6.0:amd64 Conflicts on binutils-gold [ amd64 ] none
( none )
Considering binutils:amd64 4 as a solution to fp-compiler-2.6.0:amd64 15
Added binutils:amd64 to the remove list
Fixing fp-compiler-2.6.0:amd64 via keep of binutils:amd64
Try to Re-Instate (0) binutils:amd64
Done
The following NEW packages will be installed:
[...]
The following packages have been kept back:
binutils
The following packages will be upgraded:
[...]
239 upgraded, 108 newly installed, 0 to remove and 1 not upgraded.
Adding the Breaks to fp-units-rtl-2.6.4 is sufficient since it has
a higher score than fp-compiler-2.6.0 (20 vs. 15).
In all my piuparts upgrade tests with the changes from the attached
patch binutils was always upgraded.
cheers,
Andreas
diff -Nru fpc-2.6.4+dfsg/debian/changelog fpc-2.6.4+dfsg/debian/changelog
--- fpc-2.6.4+dfsg/debian/changelog 2014-10-13 21:19:22.0 +0200
+++ fpc-2.6.4+dfsg/debian/changelog 2015-02-04 05:35:57.0 +0100
@@ -1,3 +1,10 @@
+fpc (2.6.4+dfsg-5) UNRELEASED; urgency=medium
+
+ * fp-units-rtl-2.6.4: Add Breaks: fp-compiler-2.6.0 which otherwise would
+prevent upgrading binutils. (Closes: #xx)
+
+ -- Andreas Beckmann a...@debian.org Wed, 04 Feb 2015 05:35:25 +0100
+
fpc (2.6.4+dfsg-4) unstable; urgency=low
* Let Select manually be translatable in debconf questions and update
diff -Nru fpc-2.6.4+dfsg/debian/control fpc-2.6.4+dfsg/debian/control
--- fpc-2.6.4+dfsg/debian/control 2014-09-27 19:36:19.0 +0200
+++ fpc-2.6.4+dfsg/debian/control 2015-01-29 04:44:28.0 +0100
@@ -149,7 +149,7 @@
Depends: ${misc:Depends}
Recommends: fp-compiler-2.6.4 (= ${binary:Version})
Provides: fp-units-rtl, fpc-abi-2.6.4
-Breaks: fp-units-rtl (= 2.4.0-3)
+Breaks: fp-units-rtl (= 2.4.0-3), fp-compiler-2.6.0
Replaces: fp-units-rtl (= 2.4.0-3)
Description: Free Pascal - runtime libraries
The Free Pascal Compiler is an Object Pascal compiler supporting both Delphi
diff -Nru fpc-2.6.4+dfsg/debian/control.in fpc-2.6.4+dfsg/debian/control.in
--- fpc-2.6.4+dfsg/debian/control.in 2014-09-27 19:36:01.0 +0200
+++ fpc-2.6.4+dfsg/debian/control.in 2015-01-29 04:44:20.0 +0100
@@ -149,7 +149,7 @@
Depends: ${misc:Depends}
Recommends: fp-compiler${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-rtl, fpc-abi${PACKAGESUFFIX}
-Breaks: fp-units-rtl (= 2.4.0-3)
+Breaks: fp-units-rtl (= 2.4.0-3), fp-compiler-2.6.0
Replaces: fp-units-rtl (= 2.4.0-3)
Description: Free Pascal - runtime libraries
The Free Pascal Compiler is an Object Pascal compiler supporting both Delphi
fpc_2.6.4+dfsg-4.log.gz
Description: application/gzip
Processed: libxml2: #include unicode/ucnv.h not found (unicode/ucnv.h)
Processing control commands: affects -1 kde4libs Bug #777028 [src:libxml2] libxml2: #include unicode/ucnv.h not found (unicode/ucnv.h) Added indication that 777028 affects kde4libs -- 777028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777028 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#774794: Debian Bug#774794: Re: dpkg: Add breaks for new trigger cycles
[ CCing gconf maintainers. ] Hi! On Tue, 2015-02-03 at 10:19:29 +0100, Andreas Beckmann wrote: On 2015-02-03 07:12, Niels Thykier wrote: That said, I have no status on the cycles mentioned by Andreas Beckmann (CC'ed) in this bug report. If they are still relevant, we should have bugs for them. I can still reproduce these problems, not sure which package to be blamed for and whether its trigger cycles or something different. The debian-security-support and doc-base instances are just missing Breaks in dpkg, which I've added. The only remaining problem is the gconf2 one, which from a cursory check looks suspiciously like the dbus problem. (Sorry for not having checked that one before, it looked like something else, because it's not really a trigger cycle.) Andreas, if you have such system readily available, it would be nice to know if apt-get can get out of that state or if it gets stuck there. And to the gconf maintainers, does its trigger really need to be synchronous (i.e. do trigggering packages need to await the trigger processing)? Or in other words do those other triggering packages require the trigger to be processed to be able to consider themselves configured and able to satisfy dependencies? Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777028: libxml2: #include unicode/ucnv.h not found (unicode/ucnv.h)
Source: libxml2 Version: 2.9.2+dfsg1-3 Severity: serious Control: affects -1 kde4libs Hi, The kde4libs package FTBFS with the following error on mipsel[1]: make -f kjs/CMakeFiles/kjs.dir/build.make kjs/CMakeFiles/kjs.dir/build In file included from /usr/include/libxml2/libxml/parser.h:810:0, from ../../kdoctools/xslt.h:4, from ../../kdoctools/meinproc_simple.cpp:4: /usr/include/libxml2/libxml/encoding.h:31:26: fatal error: unicode/ucnv.h: No such file or directory #include unicode/ucnv.h ^ compilation terminated. This seems to becaused by a libxml2 header requiring a header that does not exist *OR* (more likely) it did not have a dependency for. This issue is currently blocking an RC bug in kde4libs from migrating to testing. Even if the patched version of libxml2 is not targeted for jessie, please consider prioritising this fix. Thanks, ~Niels [1] https://buildd.debian.org/status/fetch.php?pkg=kde4libsarch=mipselver=4%3A4.14.2-5stamp=1422755284 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
On Wednesday 04 February 2015 01:41:14, Michael Biebl wrote: Am 31.01.2015 um 10:19 schrieb Stefan Fritsch: severity 755722 serious retitle 755722 systemd must sync systemclock to RTC on shutdown thanks Systemd must make sure that the system clock does not go backwards, which causes all kinds of problems, with file systems and with other software. To achieve that, systemd has to sync the system time to RTC on shutdown. Upstream's argument that the system time may not be more accurate is completely unrelated to this issue. Upstream argues, that whoever changes the clock, should also make sure to sync that to the RTC if so desired. E.g. if you change the time using the builtin timedatectl command, it will make sure the RTC is synced. There is also natural drift between the system clock and the RTC. Who is supposed to account for that? On a system with an uptime of several months, the drift may be large enough to cause the time to go backwards at a reboot. NB: Upstream should try not to break existing software. The sysv init script compatibility is mostly moot if the init scripts need to be adjusted because of semantic changes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777026: openscenegraph: fails to upgrade from 'wheezy': apt prefers to hold the old package version
Package: openscenegraph
Version: 3.2.1-5
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because apt prefers to keep the old version instead of upgrading it.
From the attached log (scroll to the bottom...):
Starting 2
Investigating (0) libgdal1h [ amd64 ] none - 1.10.1+dfsg-8+b3 ( libs )
Broken libgdal1h:amd64 Breaks on libgdal1 [ amd64 ] 1.9.0-3.1 ( libs )
(= 1.10.0-0~)
Considering libgdal1:amd64 -1 as a solution to libgdal1h:amd64 -1
Holding Back libgdal1h:amd64 rather than change libgdal1:amd64
Investigating (1) libopenscenegraph100 [ amd64 ] none - 3.2.1-5 ( libs )
Broken libopenscenegraph100:amd64 Depends on libgdal1h [ amd64 ] none -
1.10.1+dfsg-8+b3 ( libs ) (= 1.8.0)
Considering libgdal1h:amd64 -1 as a solution to libopenscenegraph100:amd64 0
Holding Back libopenscenegraph100:amd64 rather than change libgdal1h:amd64
Investigating (2) openscenegraph [ amd64 ] 3.0.1-4 - 3.2.1-5 ( devel )
Broken openscenegraph:amd64 Depends on libopenscenegraph100 [ amd64 ] none
- 3.2.1-5 ( libs )
Considering libopenscenegraph100:amd64 0 as a solution to
openscenegraph:amd64 0
Holding Back openscenegraph:amd64 rather than change
libopenscenegraph100:amd64
Try to Re-Instate (3) openscenegraph:amd64
Done
The following NEW packages will be installed:
[...]
The following packages have been kept back:
openscenegraph
The following packages will be upgraded:
[...]
212 upgraded, 107 newly installed, 0 to remove and 1 not upgraded.
So we need to push apt a little bit to prefer libgdal1h over libgdal1,
this can be done by adding a Breaks: libgdal1 to libopenscenegraph100.
Patch attached, upgrade path verified in piuparts.
The similar problem exists in libopenscenegraph-dev, this will be fixed
by the patch, too.
cheers,
Andreas
diff -Nru openscenegraph-3.2.1/debian/changelog openscenegraph-3.2.1/debian/changelog
--- openscenegraph-3.2.1/debian/changelog 2014-10-31 12:14:46.0 +0100
+++ openscenegraph-3.2.1/debian/changelog 2015-01-28 23:33:12.0 +0100
@@ -1,3 +1,11 @@
+openscenegraph (3.2.1-6) UNRELEASED; urgency=medium
+
+ * libopenscenegraph100: Add Breaks: libgdal1 for smooth upgrades from
+wheezy. A little incentive that helps apt to take the right decision
+between libgdal1 and libgdal1h. (Closes: #xx)
+
+ -- Andreas Beckmann a...@debian.org Wed, 28 Jan 2015 17:45:57 +0100
+
openscenegraph (3.2.1-5) unstable; urgency=medium
* Update fix for correctly loading plugins on platforms other than amd64.
diff -Nru openscenegraph-3.2.1/debian/control openscenegraph-3.2.1/debian/control
--- openscenegraph-3.2.1/debian/control 2014-10-31 11:32:05.0 +0100
+++ openscenegraph-3.2.1/debian/control 2015-01-28 23:30:25.0 +0100
@@ -87,6 +87,7 @@
Multi-Arch: same
Depends: ${misc:Depends},
${shlibs:Depends}
+Breaks: libgdal1
Description: 3D scene graph, shared libs
A portable, high level graphics toolkit for the development of high performance
graphics applications such as flight simulators, games, virtual reality or
Bug#777027: fpc: fp-compiler-2.6.0 prevents upgrade of binutils
On 04/02/15 05:05, Andreas Beckmann wrote: Package: fpc Version: 2.6.4+dfsg-4 Severity: serious Please provide a justification for the severity. Adding the Breaks to fp-units-rtl-2.6.4 is sufficient It's also wrong. The conflict between the freepascal 2.6.0 packages in Debian wheezy and the binutils in Debian jessie has nothing to do with freepascal 2.6.4. I am strongly opposed to adding wrong information to package control fields simply because apt chooses to hold back a package without it. I'm not at all convinced this needs fixing but if it really does need fixing i'd much rather see it fixed by a stable update to make the freepascal 2.6.0 packages in wheezy compatible with jessie's binutils. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773764: network-manager-strongswan: bug in config file means strongswan unrecognised
Using Strongswan on Wheezy I created an common IPsec gateway for all kinds of road warrior setups in our company: Linux, Windows, MacOS, iphones and Android phones. It is surely not perfect (yet), but it works well. And now the Debian Laptops cannot be migrated to Jessie due to missing IPsec support in Jessie's network manager. This is embarrassing. Harri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 777010 is normal
Processing commands for cont...@bugs.debian.org: severity 777010 normal Bug #777010 [reportbug] reportbug crashes when trying to submit bug report Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 777010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777010 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#768269: appdata-tools and appstream-util: error when trying to install together
2015-02-03 12:38 GMT+01:00 Andreas Beckmann a...@debian.org: Followup-For: Bug #768269 Control: found -1 0.3.2-2 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. Oh crap, thanks for noticing this! I will upload a fixed version soon (maybe today, if I manage to do that) Cheers, Matthias -- Debian Developer | Freedesktop-Developer I welcome VSRE emails. See http://vsre.info/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774881: [Pkg-haskell-maintainers] Bug#774881: Bug#774881: package haskell-ieee754 is causing FTBFS of package haskell-hastache on big-endian
Hello, I am currently building haskell-hastache with this version of haskell-ieee754 on mips. I everything goes OK I will request unblock. Package haskell-hastache is built on hurd-i386 with latest upload version of haskell-ieee754. https://buildd.debian.org/status/fetch.php?pkg=haskell-hastachearch=hurd-i386ver=0.6.0-1%2Bb1stamp=1422967412 Thank you! Regards, Jurica -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776957: Panic at boot on arm64 systems
Package: src:linux Version: 3.16.7-ckt4-2 Severity: grave Tags: patch upstream The latest upstream stable kernel pull is broken on arm64. The system panics during early boot in arch_timer setup. The cause is simple. Commit 0b46b8a718c6e90910a1b1b0fe797be3c167e186 was pulled into stable, but a later fix d6ad36913083d683aad4e02e53580c995f1a6ede was missed and is necessary. Ian has already taken this patch; please upload a fixed linux ASAP. Cheers, Steve -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776007: CVE-2015-1430: buffer overrun in acknowledge.c(gi)
Hi, Moritz Mühlenhoff wrote: On Tue, Jan 27, 2015 at 12:34:09PM +0100, Axel Beckert wrote: I hadn't checked the status in jessie yet, but I just did and you're right: Wheezy/Squeeze is not affected. JFTR: This now has been confirmed on the upstream mailing list. The bug has been introduced upstream with release 4.3.4. For details see http://lists.xymon.com/archive/2015-February/040936.html and http://sourceforge.net/p/xymon/code/6691/tree//trunk/web/acknowledge.c?diff=516c17fd34309d2eb14bcb64:6690 Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: found 775640 in 6.0-13, found 775640 in 6.0-8+deb7u1
Processing commands for cont...@bugs.debian.org:
found 775640 6.0-13
Bug #775640 {Done: Santiago Vila sanv...@debian.org} [unzip]
libarchive-zip-perl: FTBFS: Test failure (unzip/CVE-2014-8139 regression?)
Marked as found in versions unzip/6.0-13.
found 775640 6.0-8+deb7u1
Bug #775640 {Done: Santiago Vila sanv...@debian.org} [unzip]
libarchive-zip-perl: FTBFS: Test failure (unzip/CVE-2014-8139 regression?)
Marked as found in versions unzip/6.0-8+deb7u1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
775640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775640
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: notfound 776726 1.8.3-1 Bug #776726 [rdesktop] rdesktop 1.8.2-3 fails to connect to Windows Server 2008 Ignoring request to alter found versions of bug #776726 to the same values previously set End of message, stopping processing here. Please contact me if you need assistance. -- 776726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776726 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#776926: openafs-modules-dkms: fails to build module for linux-headers-3.16.0-4-amd64: error: 'struct dentry' has no member named 'd_alias'
Package: openafs-modules-dkms Version: 1.6.10-3 Severity: serious Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts openafs-modules-dkms fails to build a module for the current kernel in sid: Selecting previously unselected package openafs-modules-dkms. (Reading database ... 45386 files and directories currently installed.) Preparing to unpack .../openafs-modules-dkms_1.6.10-3_all.deb ... Unpacking openafs-modules-dkms (1.6.10-3) ... Setting up openafs-modules-dkms (1.6.10-3) ... Loading new openafs-1.6.10 DKMS files... First Installation: checking all kernels... dpkg: warning: version '*-*' has bad syntax: version number does not start with digit It is likely that 3.16.0-4-amd64 belongs to a chroot's host Building initial module for 3.16.0-4-amd64 Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/openafs/1.6.10/build/make.log for more information. make.olg ends with CC [M] /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c: In function 'afs_CheckRootVolume': /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:403:24: error: 'struct dentry' has no member named 'd_alias' list_del_init(dp-d_alias); ^ /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:404:19: error: 'struct dentry' has no member named 'd_alias' list_add(dp-d_alias, (AFSTOV(vcp)-i_dentry)); ^ /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:404:7: warning: passing argument 2 of 'list_add' from incompatible pointer type [enabled by default] list_add(dp-d_alias, (AFSTOV(vcp)-i_dentry)); ^ In file included from /usr/src/linux-headers-3.16.0-4-common/include/linux/wait.h:6:0, from /var/lib/dkms/openafs/1.6.10/build/src/afs/sysincludes.h:124, from /var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.c:19: /usr/src/linux-headers-3.16.0-4-common/include/linux/list.h:60:20: note: expected 'struct list_head *' but argument is of type 'struct hlist_head *' static inline void list_add(struct list_head *new, struct list_head *head) ^ /usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:262: recipe for target '/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o' failed make[6]: *** [/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP/afs_daemons.o] Error 1 /usr/src/linux-headers-3.16.0-4-common/Makefile:1350: recipe for target '_module_/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP' failed make[5]: *** [_module_/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP] Error 2 Makefile:181: recipe for target 'sub-make' failed make[4]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-3.16.0-4-amd64' FAILURE: make exit code 2 Makefile.afs:241: recipe for target 'openafs.ko' failed make[2]: *** [openafs.ko] Error 1 make[2]: Leaving directory '/var/lib/dkms/openafs/1.6.10/build/src/libafs/MODLOAD-3.16.0-4-amd64-SP' Makefile:138: recipe for target 'linux_compdirs' failed make[1]: *** [linux_compdirs] Error 2 make[1]: Leaving directory '/var/lib/dkms/openafs/1.6.10/build/src/libafs' Makefile:13: recipe for target 'all' failed make: *** [all] Error 2 Andreas DKMS make.log for openafs-1.6.10 for kernel 3.16.0-4-amd64 (x86_64) Tue Feb 3 11:04:47 UTC 2015 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /var/lib/dkms/openafs/1.6.10/build/build-tools/missing: Unknown `--is-lightweight' option Try `/var/lib/dkms/openafs/1.6.10/build/build-tools/missing --help' for more information configure: WARNING: 'missing' script is too old or missing checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to run the C
Processed: Re: appdata-tools and appstream-util: error when trying to install together
Processing control commands:
found -1 0.3.2-2
Bug #768269 {Done: Matthias Klumpp m...@debian.org}
[appstream-util,appdata-tools] appdata-tools and appstream-util: error when
trying to install together
Marked as found in versions appstream-glib/0.3.2-2; no longer marked as fixed
in versions appstream-glib/0.3.2-2 and reopened.
--
768269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768269
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#768269: appdata-tools and appstream-util: error when trying to install together
Followup-For: Bug #768269 Control: found -1 0.3.2-2 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package appstream-util. Preparing to unpack .../appstream-util_0.3.2-2_amd64.deb ... Unpacking appstream-util (0.3.2-2) ... dpkg: error processing archive /var/cache/apt/archives/appstream-util_0.3.2-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/appdata-validate', which is also in package appdata-tools 0.1.7-3 Preparing to unpack .../appdata-tools_0.3.2-2_all.deb ... Unpacking appdata-tools (0.3.2-2) over (0.1.7-3) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.31.1-2+b1) ... Processing triggers for libglib2.0-0:amd64 (2.42.1-1) ... Errors were encountered while processing: /var/cache/apt/archives/appstream-util_0.3.2-2_amd64.deb cheers, Andreas appdata-tools_0.3.2-2.log.gz Description: application/gzip
Bug#776477: marked as done (tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades)
Your message dated Tue, 03 Feb 2015 17:37:30 +0100 with message-id 54d0f94a.4000...@debian.org and subject line Re: Bug#776477: tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades has caused the Debian Bug report #776477, regarding tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades 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.) -- 776477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tomcat7 Version: 7.0.56-1 Severity: serious Tags: patch User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + solr-tomcat Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. Even after the upgrade it is not possible to install solr-tomcat again (without removing tomcat6 manually). From the attached log (scroll to the bottom...): [ wheezy# apt-get distupgrade ] Starting 2 Investigating (0) libtomcat7-java [ amd64 ] none - 7.0.56-1 ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] 6.0.35-6+deb7u1 - 6.0.41-2 ( java ) Considering libtomcat6-java:amd64 2 as a solution to libtomcat7-java:amd64 0 Holding Back libtomcat7-java:amd64 rather than change libtomcat6-java:amd64 Investigating (0) tomcat7-common [ amd64 ] none - 7.0.56-1 ( java ) Broken tomcat7-common:amd64 Depends on libtomcat7-java [ amd64 ] none - 7.0.56-1 ( java ) (= 7.0.56-1) Considering libtomcat7-java:amd64 0 as a solution to tomcat7-common:amd64 0 Holding Back tomcat7-common:amd64 rather than change libtomcat7-java:amd64 Investigating (1) tomcat7 [ amd64 ] none - 7.0.56-1 ( java ) Broken tomcat7:amd64 Depends on tomcat7-common [ amd64 ] none - 7.0.56-1 ( java ) (= 7.0.56-1) Considering tomcat7-common:amd64 0 as a solution to tomcat7:amd64 1 Holding Back tomcat7:amd64 rather than change tomcat7-common:amd64 Investigating (2) solr-tomcat [ amd64 ] 3.6.0+dfsg-1+deb7u1 - 3.6.2+dfsg-5 ( java ) Broken solr-tomcat:amd64 Depends on tomcat7 [ amd64 ] none - 7.0.56-1 ( java ) Considering tomcat7:amd64 1 as a solution to solr-tomcat:amd64 2 Removing solr-tomcat:amd64 rather than change tomcat7:amd64 Done The following packages will be REMOVED: solr-tomcat Removing the package to be tested is not optimal, but sometimes unavoidable. So let's reinstall afterwards. [ jessie# apt-get install solr-tomcat ] Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) tomcat6-common [ amd64 ] 6.0.41-2 ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) (= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (0) libtomcat7-java [ amd64 ] none - 7.0.56-1 ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) Considering libtomcat6-java:amd64 -1 as a solution to libtomcat7-java:amd64 0 Added libtomcat6-java:amd64 to the remove list Fixing libtomcat7-java:amd64 via remove of libtomcat6-java:amd64 Investigating (1) tomcat6-common [ amd64 ] 6.0.41-2 ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) (= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (1) libtomcat7-java [ amd64 ] none - 7.0.56-1 ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) Considering libtomcat6-java:amd64 -1 as a solution to libtomcat7-java:amd64 0 Added libtomcat6-java:amd64 to the remove list Fixing libtomcat7-java:amd64 via remove of libtomcat6-java:amd64 Investigating (2) tomcat6-common [ amd64 ] 6.0.41-2 ( java ) Broken tomcat6-common:amd64 Depends on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) (= 6.0.41-2) Considering libtomcat6-java:amd64 -1 as a solution to tomcat6-common:amd64 1 Added libtomcat6-java:amd64 to the remove list Fixing tomcat6-common:amd64 via keep of libtomcat6-java:amd64 Investigating (2) libtomcat7-java [ amd64 ] none - 7.0.56-1 ( java ) Broken libtomcat7-java:amd64 Conflicts on libtomcat6-java [ amd64 ] 6.0.41-2 ( java ) Considering libtomcat6-java:amd64 1 as
Bug#769805: ming: FTBFS on current sid: swf4compiler.tab.c:3535:7: error: lvalue required as left operand of assignment
On Sun, Nov 16, 2014 at 04:52:01PM +0100, intrig...@debian.org wrote: I tried to test my fix for #752629, but couldn't build the package with pbuilder in a sid chroot: While trying to let the package use autoreconf (to really fix FTBFS on arm64, among others) and I noted I can build the current package without any issues, in a clean sid chroot. Might you retry? -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo signature.asc Description: Digital signature
Processed (with 1 errors): openafs needs update for new kernels
Processing commands for cont...@bugs.debian.org: severity 771298 serious Bug #771298 [openafs] openafs-modules-dkms: fails to build against v3.18 based kernels Severity set to 'serious' from 'important' forcemerge 771298 776926 Bug #771298 [openafs] openafs-modules-dkms: fails to build against v3.18 based kernels Unable to merge bugs because: package of #776926 is 'openafs-modules-dkms' not 'openafs' Failed to forcibly merge 771298: Did not alter merged bugs thanks Stopping processing here. Please contact me if you need assistance. -- 771298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771298 776926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776926 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#776477: tomcat7: fails to switch from tomcat6 to tomcat7 on upgrades
Le 03/02/2015 17:37, Andreas Beckmann a écrit : now that it migrated, tomcat6 removal has smoothened this upgrade path, thus closing. Great, thank you for confirming Andreas. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776910: apt: upgrade from wheezy to jessie breaks in the middle
W dniu 03.02.2015 o 15:17, David Kalnischkies pisze: Control: tag -1 - newcomer Hi Rafal, On Tue, Feb 03, 2015 at 10:20:26AM +0100, Rafal Pietrak wrote: My guess is that some limit on number of errors was taken into account unneceserly during an upgrade - upgrades are expected to rise trancient errors. Your report seems to error into the total opposite unfortunately by not mentioning a single error. Upgrading is a tricky business and basically OK. I can see it looks that way. different for everyone (as which packages you have installed can vary widely as you have ~3 to choose from). Your report is hence as actionable as a weather report saying: It is going to rain tomorrow somewhere on earth. That isn't really telling me much about if I should carry an umbrella around or not on my adventure around my little patch of dirt. For this, as well as here, we need details, details, details to actually do something about it. But my crystalball tells me that you might mean #776063 as dpkg shows in this context a too many errors message (litmus test: the word dbus was printed all over the place, right?). It might, but I don't think so. 1. in my case there was no such thing a long trail of lines with dbus word in them. 2. I do _vaguely_ remember last line above the shell prompt (after upgrade stopped) saying: too many errors (after quite long running upgrade). 3. to my surprise, apt-get -f install; apt-get dist-upgrade did help ... to some extend: the upgrade finished without next stop, but the system is not actually usable (I've filed two more bugreports regarding that). 4. the entire process/failure resembles what I've experiences while upgrading to wheezy some two years ago: at that time, I didn't have correct cpufreq-control and the upgrade did overheated the system, which rebooted during the process. After that I did numerous manual pushing of the upgrade, and (again _vaguely_ ) remember finding some apt-max-errors, which I've (remember) increasing then, which helped a lot. 5. I'm filing this bugreport, because this time there was no reboot-in-the middle, so I'd expect, the apt-max-errors (if it really exists - I cannot find it now) is truely too low for an average system I'd imagine, that upgrade from one major release to another should set it temporarly to infinity ;7, but may be not. If not we need at the very least the actual error message(s). The current system state (/var/lib/dpkg/status) as well as the state before the upgrade (the /var/backups/dpkg.status* file dated before the update) could also be helpful. The pervious dpkg.status is gone, sorry. But current dpkg.status is c.a. 4.5MB. Is it all right to upload it anyway? On a more general note: Try not to guess in bugreports. You are the eyewitness, you know the facts. I am the guy on jury duty who has to come up with a coherent story of what happened and why. I know its tempting to add evidence as a witness, but that can spoil the whole process. Yes, It is tempting :) In that case I should say, that I've only witnessed an unexpected and unprovoked single break during the upgrade. Which was fully mended by only running apt -f install followed by a single apt-get dist-upgrade. Yet, the system (although reported by apt-get as fully up to date) is not fully functional. Best regards David Kalnischkies P.S.: The 'newcomer' tag is for maintainers to indicate bitsized bugs which a newcomer to the project/package can try to tackle to get started. I wouldn't recommend these sort of upgrade bugs as a starting point… and we certainly don't need to label bugs from newcomers as such (which I guess is what you meant it to mean) as a bug is a bug, it isn't worse just because a longtime contributor reported it. Ups. (I thought it defines the reporting person). Sorry for misleading tag. -R -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776913: flightgear-data-all: new upstream version needed by flightgear/experimental
On 2015-02-03 14:14, Rebecca N. Palmer wrote: If you urgently want 3.2, dropping the 3.2 flightgear-data upstream into the 3.0.0-1 (not -2) packaging will probably work, but this has not been tested. The only thing I needed was this bug report, so that piuparts can mark the uninstallable flightgear package in experimental as that's a known bug. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 761179 is serious
Processing commands for cont...@bugs.debian.org: severity 761179 serious Bug #761179 [pgtune] pgtune: Update to a newer version Severity set to 'serious' from 'wishlist' thanks Stopping processing here. Please contact me if you need assistance. -- 761179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761179 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#776913: flightgear-data-all: new upstream version needed by flightgear/experimental
This is an intentionally abandoned transition: a serious bug delayed the (upstream) release of 3.2 past (Ubuntu and Debian) freezes, and 3.4 is due before the next Ubuntu freeze (LP#1414379). If you urgently want 3.2, dropping the 3.2 flightgear-data upstream into the 3.0.0-1 (not -2) packaging will probably work, but this has not been tested. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776910: apt: upgrade from wheezy to jessie breaks in the middle
Control: tag -1 - newcomer Hi Rafal, On Tue, Feb 03, 2015 at 10:20:26AM +0100, Rafal Pietrak wrote: My guess is that some limit on number of errors was taken into account unneceserly during an upgrade - upgrades are expected to rise trancient errors. Your report seems to error into the total opposite unfortunately by not mentioning a single error. Upgrading is a tricky business and basically different for everyone (as which packages you have installed can vary widely as you have ~3 to choose from). Your report is hence as actionable as a weather report saying: It is going to rain tomorrow somewhere on earth. That isn't really telling me much about if I should carry an umbrella around or not on my adventure around my little patch of dirt. For this, as well as here, we need details, details, details to actually do something about it. But my crystalball tells me that you might mean #776063 as dpkg shows in this context a too many errors message (litmus test: the word dbus was printed all over the place, right?). If not we need at the very least the actual error message(s). The current system state (/var/lib/dpkg/status) as well as the state before the upgrade (the /var/backups/dpkg.status* file dated before the update) could also be helpful. On a more general note: Try not to guess in bugreports. You are the eyewitness, you know the facts. I am the guy on jury duty who has to come up with a coherent story of what happened and why. I know its tempting to add evidence as a witness, but that can spoil the whole process. Best regards David Kalnischkies P.S.: The 'newcomer' tag is for maintainers to indicate bitsized bugs which a newcomer to the project/package can try to tackle to get started. I wouldn't recommend these sort of upgrade bugs as a starting point… and we certainly don't need to label bugs from newcomers as such (which I guess is what you meant it to mean) as a bug is a bug, it isn't worse just because a longtime contributor reported it. signature.asc Description: Digital signature
Processed: Re: Bug#776910: apt: upgrade from wheezy to jessie breaks in the middle
Processing control commands: tag -1 - newcomer Bug #776910 [apt] apt: upgrade from wheezy to jessie breaks in the middle Removed tag(s) newcomer. -- 776910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776910 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: openafs needs update for new kernels
Processing commands for cont...@bugs.debian.org: reassign 771298 openafs-modules-dkms Bug #771298 [openafs] openafs-modules-dkms: fails to build against v3.18 based kernels Bug reassigned from package 'openafs' to 'openafs-modules-dkms'. No longer marked as found in versions 1.6.10-3. Ignoring request to alter fixed versions of bug #771298 to the same values previously set forcemerge 771298 776926 Bug #771298 [openafs-modules-dkms] openafs-modules-dkms: fails to build against v3.18 based kernels Bug #776926 [openafs-modules-dkms] openafs-modules-dkms: fails to build module for linux-headers-3.16.0-4-amd64: error: 'struct dentry' has no member named 'd_alias' Added tag(s) experimental and patch. Bug #771298 [openafs-modules-dkms] openafs-modules-dkms: fails to build against v3.18 based kernels Marked as found in versions openafs/1.6.10-3. Merged 771298 776926 thanks Stopping processing here. Please contact me if you need assistance. -- 771298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771298 776926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776926 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#776881: closed by Charles Plessy ple...@debian.org (Bug#776881: fixed in bowtie 1.1.1-2)
Thanks! On Tue Feb 03 2015 at 4:21:08 AM Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the bowtie package: #776881: bowtie: '-debug' binaries break `bowtie-build` It has been closed by Charles Plessy ple...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Charles Plessy ple...@debian.org by replying to this email. -- 776881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Charles Plessy ple...@debian.org To: 776881-cl...@bugs.debian.org Cc: Date: Tue, 03 Feb 2015 03:19:00 + Subject: Bug#776881: fixed in bowtie 1.1.1-2 Source: bowtie Source-Version: 1.1.1-2 We believe that the bug you reported is fixed in the latest version of bowtie, 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 776...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Charles Plessy ple...@debian.org (supplier of updated bowtie 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: Tue, 03 Feb 2015 10:44:39 +0900 Source: bowtie Binary: bowtie bowtie-examples Architecture: source amd64 all Version: 1.1.1-2 Distribution: unstable Urgency: high Maintainer: Debian Med Packaging Team debian-med-packaging@lists. alioth.debian.org Changed-By: Charles Plessy ple...@debian.org Description: bowtie - Ultrafast memory-efficient short read aligner bowtie-examples - Examples for bowtie, the ultrafast memory-efficient short read al Closes: 776881 Changes: bowtie (1.1.1-2) unstable; urgency=high . * Team upload. * Install missing commands. Closes: #776881. Checksums-Sha1: 07a28a0af4b78bbdf722ad8cc22dfd44e30420cd 2195 bowtie_1.1.1-2.dsc 0e26e94bbc417620c580061503abd54397176224 13064 bowtie_1.1.1-2.debian.tar.xz 98a40fd8f05f9131be1e772558b0e3f08696fc46 1369362 bowtie_1.1.1-2_amd64.deb 2b586fc20f2f2c8654b7fc48624e5083a82ce241 6307360 bowtie-examples_1.1.1-2_all.deb Checksums-Sha256: 44f5af7bdedfc5330c004b37f3c014ecbefe5d290a593eb9b6e4be8d639897ed 2195 bowtie_1.1.1-2.dsc bc6ee5fa83667e6e042b750b88eedfa770276713892610df06f5a6cf79f81ea3 13064 bowtie_1.1.1-2.debian.tar.xz bd176deb2caea1b3a7088724e6c308cb6b7b13aa36951be97de98109514be253 1369362 bowtie_1.1.1-2_amd64.deb a77dd074cecef4dce1b1cb8aa021bafdeb7c90211c315f759a83ed4a8ccd255d 6307360 bowtie-examples_1.1.1-2_all.deb Files: 2210cbccf2207c970495ee228d0629ba 2195 science optional bowtie_1.1.1-2.dsc 2a35d285f03c48d7619f40c198551720 13064 science optional bowtie_1.1.1-2.debian.tar.xz 116b8244f07442931ce4aaff2f910f0c 1369362 science optional bowtie_1.1.1-2_amd64.deb 1067dde15b877c86092bbee12bebef3c 6307360 science optional bowtie-examples_1.1.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJU0DKhAAoJEMW9bI8ildUCbQ0QAJ147vfy4ZzeMyVFKkUpO2Kr 1CFNpMzun1J3qRokRwcB+bkdrK7PptsBF5iBlWO5p5cWL5E8CUE2lpkKlyPMudzU qUEQSJy0/f+v+HDDfsqVO38vp4OHa9byaOkOFrx02idsxhkxLJO2jUfaLGvlaT3k 1CtJOpWEcvE9FEIxXNWLcguBO/LKB4uRwijsIo15UT/r9XAl3lktWZxVcn3D/aOC dbNz773QDzzmucFgf9NHzaownqEz5SmwnFUZWPnIMbTR2sCGLpRUu9xl8vlz/i1/ 3Mt5O45xJbnGIi+FaXLJt6gjyap0eMHtFkG+arIynqkOg8KdkQWR3p0epx2QiZWz ynnljuDiTtINirqy2phOW3MSF3bDl9AvJonNk4x9OnbugyY5j2xW6Pm540lshLlr A3EUid+5bx+7HjWnRL8ghFTmtOj3JBeiQkzZ05NBU21PFJmBoVEIjX3qmhmkdZT+ sVOBvm5mGATdM8wAM4PUWHHbJhibuHGQD0lGc2OOdKvkLmfMA+63TFsyugYG1Nuf QDtO/Sb4/GR+U8E85yMT/viylrGckB2RbR+1Wo3fOT0CzyD46WUfCG8/F2pXq631 QwAuG6zggjxTmQryTxciKvJ+907UGDU4GKcrApG16ApRbw+dNQQLZB/TXyh5Ktii gnr5JgXiXaJjK8swvXvH =vGNd -END PGP SIGNATURE- -- Forwarded message -- From: Michael R. Crusoe michael.cru...@gmail.com To: Debian Bug Tracking System sub...@bugs.debian.org Cc: Date: Mon, 02 Feb 2015 20:14:46 + Subject: bowtie: '-debug' binaries break `bowtie-build` Package: bowtie Version: 1.1.1-1 Severity: grave Justification: renders package unusable Hello, Looks like the debug versions of 'bowtie-build-l' and 'bowtie-build-s' are present instead thus breaking the 'bowtie-build' wrapper making the package useless. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux
Processed: retitle
Processing commands for cont...@bugs.debian.org: retitle 776776 dnssec-trigger should declare Breaks: resolvconf Bug #776776 [dnssec-trigger] dnssec-trigger: dnssec-triggerd running causes resolvconf installation to fail Changed Bug title to 'dnssec-trigger should declare Breaks: resolvconf' from 'dnssec-trigger: dnssec-triggerd running causes resolvconf installation to fail' severity 776776 serious Bug #776776 [dnssec-trigger] dnssec-trigger should declare Breaks: resolvconf Severity set to 'serious' from 'important' retitle 776778 Please make dnssec-trigger work with resolvconf Bug #776778 [dnssec-trigger,resolvconf] dnssec-trigger+resolvconf: Don't play well together Changed Bug title to 'Please make dnssec-trigger work with resolvconf' from 'dnssec-trigger+resolvconf: Don't play well together' severity 776778 wishlist Bug #776778 [dnssec-trigger,resolvconf] Please make dnssec-trigger work with resolvconf Severity set to 'wishlist' from 'normal' stop Stopping processing here. Please contact me if you need assistance. -- 776776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776776 776778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776778 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#776776: Breaks resolvconf
Let this report (#776776) track the issue that dnssec-trigger breaks resolvconf and therefore must declare a Breaks: resolvconf. This can and should be fixed immediately, for jessie. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776999: broken 32-bit userland on 64-bit kernel
Package: efivar Version: 0.15-3 Severity: serious I'm afraid the patch 07-num_bits.patch breaks the case of 32-bit userland on a 64-bit kernel. As far as I know, this is how i386 would get installed on any non-ancient machine if d-i could get that far (it doesn't for me in qemu-kvm.x86-64, though). The bad assumption is that an 64-bit kernel would give the same data to any process. This seems to be obvious, but it's not the case: Here's a set of sample dumps of /sys/firmware/efi/vars/Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var -- all done on the same virtual machine, same kernel, same boot-up, all that differs is the ABI of the cat process: cat is amd64: 42 00 6f 00 6f 00 74 00 30 00 30 00 30 00 35 00 |B.o.o.t.0.0.0.5.| 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0400 61 df e4 8b ca 93 d2 11 aa 0d 00 e0 98 03 2b 8c |a.+.| 0410 76 00 00 00 00 00 00 00 01 00 00 00 62 00 64 00 |v...b.d.| ^^^ 0420 65 00 62 00 69 00 61 00 6e 00 00 00 04 01 2a 00 |e.b.i.a.n.*.| 0430 01 00 00 00 00 08 00 00 00 00 00 00 00 00 10 00 || 0440 00 00 00 00 14 ab c8 38 14 e4 68 40 89 28 2a 27 |...8..h@.(*'| 0450 8b 45 06 d2 02 02 04 04 34 00 5c 00 45 00 46 00 |.E..4.\.E.F.| 0460 49 00 5c 00 64 00 65 00 62 00 69 00 61 00 6e 00 |I.\.d.e.b.i.a.n.| 0470 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 |\.g.r.u.b.x.6.4.| 0480 2e 00 65 00 66 00 69 00 00 00 7f ff 04 00 00 00 |..e.f.i.| 0490 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0820 07 00 00 00 || 0824 cat is x32: 42 00 6f 00 6f 00 74 00 30 00 30 00 30 00 35 00 |B.o.o.t.0.0.0.5.| 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0400 61 df e4 8b ca 93 d2 11 aa 0d 00 e0 98 03 2b 8c |a.+.| 0410 76 00 00 00 01 00 00 00 62 00 64 00 65 00 62 00 |v...b.d.e.b.| ^^^ 0420 69 00 61 00 6e 00 00 00 04 01 2a 00 01 00 00 00 |i.a.n.*.| 0430 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 || 0440 14 ab c8 38 14 e4 68 40 89 28 2a 27 8b 45 06 d2 |...8..h@.(*'.E..| 0450 02 02 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 |4.\.E.F.I.\.| 0460 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 67 00 |d.e.b.i.a.n.\.g.| 0470 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 |r.u.b.x.6.4...e.| 0480 66 00 69 00 00 00 7f ff 04 00 00 00 00 00 00 00 |f.i.| 0490 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0810 00 00 00 00 00 00 00 00 07 00 00 00 || 081c cat is i386: 42 00 6f 00 6f 00 74 00 30 00 30 00 30 00 35 00 |B.o.o.t.0.0.0.5.| 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0400 61 df e4 8b ca 93 d2 11 aa 0d 00 e0 98 03 2b 8c |a.+.| 0410 76 00 00 00 01 00 00 00 62 00 64 00 65 00 62 00 |v...b.d.e.b.| ^^^ 0420 69 00 61 00 6e 00 00 00 04 01 2a 00 01 00 00 00 |i.a.n.*.| 0430 00 08 00 00 00 00 00 00 00 00 10 00 00 00 00 00 || 0440 14 ab c8 38 14 e4 68 40 89 28 2a 27 8b 45 06 d2 |...8..h@.(*'.E..| 0450 02 02 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 |4.\.E.F.I.\.| 0460 64 00 65 00 62 00 69 00 61 00 6e 00 5c 00 67 00 |d.e.b.i.a.n.\.g.| 0470 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 |r.u.b.x.6.4...e.| 0480 66 00 69 00 00 00 7f ff 04 00 00 00 00 00 00 00 |f.i.| 0490 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0810 00 00 00 00 00 00 00 00 07 00 00 00 || 081c Note that, surprisingly, the kernel detects the ABI of the running process and presents different contents of that file on the sys fs. This means, runtime detection is bad as any 32-bit process will get 32-bit fields (actually, just one, the rest is arch-independent). Thus, to fix the issue, it seems you can drop 07-num_bits.patch and install the patch I attached instead. I'm afraid I can't test it save for qemu and virtualbox at this time, though. And while we're here... could you please add x32 to the list of architectures in debian/control? This would fix a FTBFS on an unofficial arch. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777001: kdm: does not depend on X
Package: kdm Version: 4:4.11.13-2 Severity: grave Justification: renders package unusable Dear Maintainer, On a freshly installed machine, with suggests and recommends disabled kdm won't start because /usr/bin/X is not present. I guess it should be a dependency. Best regards and thanks! -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.2a (SMP w/4 CPU cores; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kdm depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii kde-runtime 4:4.14.2-2 ii kde-wallpapers-default4:4.14.0-1 ii kde-workspace-kgreet-plugins 4:4.11.13-2 ii libc6 2.19-14 ii libkdecore5 4:4.14.2-5 ii libkdeui5 4:4.14.2-5 ii libkio5 4:4.14.2-5 ii libknewstuff3-4 4:4.14.2-5 ii libkworkspace4abi24:4.11.13-2 ii libpam0g 1.1.8-3.1 ii libqimageblitz4 1:0.0.6-4 ii libqt4-svg4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++64.9.2-10 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxtst6 2:1.2.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 Versions of packages kdm recommends: ii kde-window-manager [x-window-manager] 4:4.11.13-2 ii konsole [x-terminal-emulator] 4:4.14.2-1 ii logrotate 3.8.7-1+b1 ii xserver-xorg [xserver] 1:7.7+7 ii xterm [x-terminal-emulator]312-1 Versions of packages kdm suggests: pn kde-wallpapers none ii kdepasswd 4:4.14.2-1 -- Configuration Files: /etc/kde4/kdm/kdmrc changed: [General] ConfigVersion=2.4 StaticServers=:0 ReserveServers=:1,:2,:3 ServerVTs=-7 ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 PidFile=/var/run/kdm.pid GreeterUID=kdm [Xdmcp] Enable=false Willing=/etc/kde4/kdm/Xwilling [Shutdown] [X-*-Core] Setup=/etc/kde4/kdm/Xsetup Startup=/etc/kde4/kdm/Xstartup Reset=/etc/kde4/kdm/Xreset Session=/etc/kde4/kdm/Xsession AllowRootLogin=false AllowNullPasswd=false AllowShutdown=Root ClientLogFile=.xsession-errors-%d [X-*-Greeter] LogoArea=Logo LogoPixmap=/usr/share/kde4/apps/kdm/pics/kdelogo.png MinShowUID=1000 MaxShowUID=2 Preloader=/usr/bin/preloadkde UseTheme=true Theme=@@@ToBeReplacedByDesktopBase@@@ [X-:*-Core] ServerCmd=/usr/bin/X ServerArgsLocal=-br -nolisten tcp AllowNullPasswd=true AllowShutdown=All [X-:*-Greeter] PreselectUser=Previous FocusPasswd=true LoginMode=DefaultLocal AllowClose=true [X-:0-Core] AutoLoginEnable=true AutoLoginUser=salvo AutoLoginLocked=true ClientLogFile=.xsession-errors [X-:0-Greeter] -- debconf information: kdm/daemon_name: /usr/bin/kdm kdm/stop_running_server_with_children: false * shared/default-x-display-manager: kdm -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776957: marked as done (Panic at boot on arm64 systems)
Your message dated Tue, 03 Feb 2015 23:05:58 + with message-id e1yimxe-00051v...@franck.debian.org and subject line Bug#776957: fixed in linux 3.16.7-ckt4-3 has caused the Debian Bug report #776957, regarding Panic at boot on arm64 systems 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.) -- 776957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.16.7-ckt4-2 Severity: grave Tags: patch upstream The latest upstream stable kernel pull is broken on arm64. The system panics during early boot in arch_timer setup. The cause is simple. Commit 0b46b8a718c6e90910a1b1b0fe797be3c167e186 was pulled into stable, but a later fix d6ad36913083d683aad4e02e53580c995f1a6ede was missed and is necessary. Ian has already taken this patch; please upload a fixed linux ASAP. Cheers, Steve ---End Message--- ---BeginMessage--- Source: linux Source-Version: 3.16.7-ckt4-3 We believe that the bug you reported is fixed in the latest version of linux, 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 776...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux 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: Tue, 03 Feb 2015 20:07:06 + Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all linux-headers-3.16.0-4-all-alpha linux-headers-3.16.0-4-common linux-image-3.16.0-4-alpha-generic linux-headers-3.16.0-4-alpha-generic linux-image-3.16.0-4-alpha-smp linux-headers-3.16.0-4-alpha-smp linux-image-3.16.0-4-alpha-legacy linux-headers-3.16.0-4-alpha-legacy linux-headers-3.16.0-4-all-amd64 kernel-image-3.16.0-4-amd64-di nic-modules-3.16.0-4-amd64-di nic-wireless-modules-3.16.0-4-amd64-di nic-shared-modules-3.16.0-4-amd64-di serial-modules-3.16.0-4-amd64-di usb-serial-modules-3.16.0-4-amd64-di ppp-modules-3.16.0-4-amd64-di pata-modules-3.16.0-4-amd64-di cdrom-core-modules-3.16.0-4-amd64-di firewire-core-modules-3.16.0-4-amd64-di scsi-core-modules-3.16.0-4-amd64-di scsi-modules-3.16.0-4-amd64-di scsi-common-modules-3.16.0-4-amd64-di scsi-extra-modules-3.16.0-4-amd64-di loop-modules-3.16.0-4-amd64-di btrfs-modules-3.16.0-4-amd64-di ext4-modules-3.16.0-4-amd64-di isofs-modules-3.16.0-4-amd64-di jfs-modules-3.16.0-4-amd64-di ntfs-modules-3.16.0-4-amd64-di xfs-modules-3.16.0-4-amd64-di fat-modules-3.16.0-4-amd64-di md-modules-3.16.0-4-amd64-di multipath-modules-3.16.0-4-amd64-di usb-modules-3.16.0-4-amd64-di usb-storage-modules-3.16.0-4-amd64-di pcmcia-storage-modules-3.16.0-4-amd64-di fb-modules-3.16.0-4-amd64-di input-modules-3.16.0-4-amd64-di event-modules-3.16.0-4-amd64-di mouse-modules-3.16.0-4-amd64-di nic-pcmcia-modules-3.16.0-4-amd64-di pcmcia-modules-3.16.0-4-amd64-di nic-usb-modules-3.16.0-4-amd64-di sata-modules-3.16.0-4-amd64-di core-modules-3.16.0-4-amd64-di acpi-modules-3.16.0-4-amd64-di i2c-modules-3.16.0-4-amd64-di crc-modules-3.16.0-4-amd64-di crypto-modules-3.16.0-4-amd64-di crypto-dm-modules-3.16.0-4-amd64-di efi-modules-3.16.0-4-amd64-di ata-modules-3.16.0-4-amd64-di mmc-core-modules-3.16.0-4-amd64-di mmc-modules-3.16.0-4-amd64-di nbd-modules-3.16.0-4-amd64-di squashfs-modules-3.16.0-4-amd64-di speakup-modules-3.16.0-4-amd64-di virtio-modules-3.16.0-4-amd64-di uinput-modules-3.16.0-4-amd64-di sound-modules-3.16.0-4-amd64-di hyperv-modules-3.16.0-4-amd64-di udf-modules-3.16.0-4-amd64-di fuse-modules-3.16.0-4-amd64-di linux-image-3.16.0-4-amd64 linux-headers-3.16.0-4-amd64 linux-image-3.16.0-4-amd64-dbg xen-linux-system-3.16.0-4-amd64 linux-headers-3.16.0-4-all-arm64 kernel-image-3.16.0-4-arm64-di nic-modules-3.16.0-4-arm64-di nic-wireless-modules-3.16.0-4-arm64-di nic-shared-modules-3.16.0-4-arm64-di ppp-modules-3.16.0-4-arm64-di cdrom-core-modules-3.16.0-4-arm64-di scsi-core-modules-3.16.0-4-arm64-di scsi-modules-3.16.0-4-arm64-di loop-modules-3.16.0-4-arm64-di btrfs-modules-3.16.0-4-arm64-di ext4-modules-3.16.0-4-arm64-di
Processed: found 692455 in 2.8.0-6, unarchiving 726801, affects 726801, found 774163 in 5.34.00-2 ...
Processing commands for cont...@bugs.debian.org:
found 692455 2.8.0-6
Bug #692455 [jspwiki] jspwiki: modifies conffiles (policy 10.7.3):
/etc/jspwiki/jspwiki.properties
Marked as found in versions jspwiki/2.8.0-6.
unarchive 726801
Bug #726801 {Done: olivier sallou olivier.sal...@gmail.com} [biomaj] biomaj:
fails to install with Recommends enabled
Unarchived Bug 726801
affects 726801 - biomaj-watcher
Bug #726801 {Done: olivier sallou olivier.sal...@gmail.com} [biomaj] biomaj:
fails to install with Recommends enabled
Removed indication that 726801 affects biomaj-watcher
found 774163 5.34.00-2
Bug #774163 {Done: Sebastian Ramacher sramac...@debian.org}
[ttf-root-installer] Unable to upgrade or install ttf-root-installer (dpkg:
error processing package) because of invalid certificate on root.cern.ch
Marked as found in versions root-system/5.34.00-2.
found 772598 1.0.0.49-2
Bug #772598 [steam] steam: install fails if debconf selections are already set
Marked as found in versions steam/1.0.0.49-2.
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
usertags 772598 piuparts
There were no usertags set.
Usertags are now: piuparts.
severity 770402 serious
Bug #770402 [nautilus-dropbox] nautilus-dropbox: hangs during installation with
100% cpu usage
Severity set to 'serious' from 'important'
fixed 770402 1.6.2-3
Bug #770402 [nautilus-dropbox] nautilus-dropbox: hangs during installation with
100% cpu usage
Marked as fixed in versions nautilus-dropbox/1.6.2-3.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
692455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692455
726801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726801
770402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770402
772598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772598
774163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774163
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: affects 776907, found 776330 in 2.3.1-1, affects 776330, tagging 771298
Processing commands for cont...@bugs.debian.org: affects 776907 + libsocksd0 Bug #776907 [src:dante] dante: FTBFS due to libtool movement Added indication that 776907 affects libsocksd0 found 776330 2.3.1-1 Bug #776330 [php-kdyby-console] php-kdyby-console: uninstallable in sid: php-symfony-console (= 2.5) is not available anywhere Marked as found in versions php-kdyby-console/2.3.1-1. affects 776330 + php-kdyby-events Bug #776330 [php-kdyby-console] php-kdyby-console: uninstallable in sid: php-symfony-console (= 2.5) is not available anywhere Added indication that 776330 affects php-kdyby-events tags 771298 + experimental Bug #771298 [openafs] openafs-modules-dkms: fails to build against v3.18 based kernels Added tag(s) experimental. thanks Stopping processing here. Please contact me if you need assistance. -- 771298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771298 776330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776330 776907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776907 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#776914: libavogadro-dev: unsatisfiable Depends: libeigen2-dev
Package: libavogadro-dev Version: 1.1.0-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts libavogadro-dev/experimental is not installable, since libeigen2-dev has moved on to libeigen3-dev. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776565: preparing nmu for di-netboot-assistant
Andreas B. Mundt a...@debian.org (2015-02-03): OK, I'll keep that in mind. (Perhaps I should/could take care of di-netboot-assistant ...). Having an active maintainer for it would be super nice, yes. I've taken the liberty of adding you to the alioth d-i group; that doesn't mean that you *have* to be the d-i-n-a maintainer of course, it should just make it easy for you to push your changes to the d-i repositories, be it for NMUs or MUs. (FWIW with that addition we reached 256 members. ;)) Mraw, KiBi. signature.asc Description: Digital signature
Bug#776920: blcr-dkms: fails to build kernel module for 3.16.0-4-amd64
Package: blcr-dkms Version: 0.8.6~b3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to build a kernel module for 3.16.0-4-amd64: Setting up blcr-dkms (0.8.6~b3-1) ... Creating symlink /var/lib/dkms/blcr/0.8.6~b3/source - /usr/src/blcr-0.8.6~b3 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area make KERNELRELEASE=3.16.0-4-amd64 -C /lib/modules/3.16.0-4-amd64/build M=/var/lib/dkms/blcr/0.8.6~b3/build.(bad exit status: 2) Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.6~b3/build/make.log for more information. make.log ends with checking for Linux kernel symbol table... failed configure: error: Failed to locate kernel symbol table. Try using --with-system-map or --with-vmlinux. /var/lib/dkms/blcr/0.8.6~b3/build/Kbuild:7: recipe for target '/var/lib/dkms/blcr/0.8.6~b3/build/config-stamp' failed make[3]: *** [/var/lib/dkms/blcr/0.8.6~b3/build/config-stamp] Error 1 /usr/src/linux-headers-3.16.0-4-common/Makefile:1350: recipe for target '_module_/var/lib/dkms/blcr/0.8.6~b3/build' failed make[2]: *** [_module_/var/lib/dkms/blcr/0.8.6~b3/build] Error 2 Makefile:181: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make: *** [all] Error 2 Andreas DKMS make.log for blcr-0.8.6~b3 for kernel 3.16.0-4-amd64 (x86_64) Tue Feb 3 10:32:40 UTC 2015 make: Entering directory '/usr/src/linux-headers-3.16.0-4-amd64' make[1]: Entering directory `/usr/src/linux-headers-3.16.0-4-amd64' /var/lib/dkms/blcr/0.8.6~b3/build/Kbuild:19: /var/lib/dkms/blcr/0.8.6~b3/build/module_files: No such file or directory cd /var/lib/dkms/blcr/0.8.6~b3/build env -i PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/lib/dkms ./configure --disable-maintainer-mode --with-linux=3.16.0-4-amd64 --with-installed-libcr --with-installed-util --with-components=modules --prefix=/usr touch /var/lib/dkms/blcr/0.8.6~b3/build/config-stamp checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for pwd... /bin/pwd checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for perl5... no checking for perl... /usr/bin/perl checking for gmake... no checking for make... /usr/bin/make checking if /usr/bin/make is GNU make... yes (4.0) checking for ranlib... ranlib checking whether ln -s works... yes checking for style of include used by /usr/bin/make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking size of void *... 8 checking whether CXX='g++' acts like a C++ compiler... yes checking whether CXX='g++' matches wordsize of CC... yes checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands +=... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to
Bug#771989: Bug#776063: dbus fails to upgrade rendering entire apt unusable
On Fri, 30 Jan 2015 at 17:56:16 +0100, Simon McVittie wrote: On 30/01/15 14:44, David Kalnischkies wrote: Its not helping the general case of course, but -noawait triggers can't run in to this problem as nothing can end up in 'iW' with them. OK, I'll queue that in git, and talk to the release team jmw kindly unblocked dbus/1.8.14-1, but it was still waiting for a d-i ack. I wanted to get this out of the way, so I've uploaded 1.8.14-2 with this additional change in the hope that that'll be OK. If the apt and dpkg maintainers think that dropping dbus' triggers down to interest-noawait (exact debdiff at https://lists.debian.org/debian-release/2015/02/msg00090.html) will be enough to avoid #776063 happening in practice, then I think it can be downgraded to non-RC. Regards, S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777016: linux-image-3.18.0-trunk-amd64: kernel panic in __intel_set_mode
Package: src:linux Version: 3.18.5-1~exp1 Severity: serious My system hangs when booting using kernel 3.18 sometime after unlocking the encrypted root disk. Kernel 3.17 works fine. * Using the default kernel command line, the problem occurs everytime. * Using the nomodeset parameter, the kernel works fine but I can't use X. * When using netconsole, the system sometimes hangs and sometimes works fine, though outputting a warning in the kernel (see first log below). When the kernel hangs, unfortunately only the first few lines of the BUG show up in the netconsole (see second log at the bottom). Let me know if I can be of any more assistance. -- Package-specific info: ** Version: Linux version 3.18.0-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 3.18.5-1~exp1 (2015-01-31) ** Command line: BOOT_IMAGE=/vmlinuz-3.18.0-trunk-amd64 root=UUID=452d1dc1-2c61-4bba-b64a-8137c122bf0b ro net.ifnames=1 netconsole=@130.89.172.53/eth0,@130.89.171.131/60:a4:4c:d6:77:4d ** Tainted: W (512) * Taint on warning. ** Kernel log (when system was booted with netconsole and didn't panic): [9.236016] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [9.236361] acpi device:60: registered as cooling_device10 [9.236420] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9 [9.236629] [drm] Initialized i915 1.6.0 20140905 for :00:02.0 on minor 0 [9.236710] ACPI Warning: SystemIO range 0xf040-0xf05f conflicts with OpRegion 0xf040-0xf04f (\_SB_.PCI0.SBUS.SMBI) (20140926/utaddress-258) [9.236728] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [9.236820] snd_hda_intel :00:03.0: enabling device ( - 0002) [9.236883] snd_hda_intel :00:1b.0: enabling device ( - 0002) [9.237298] snd_hda_intel :00:03.0: irq 31 for MSI/MSI-X [9.237400] snd_hda_intel :00:1b.0: irq 32 for MSI/MSI-X [9.247250] sound hdaudioC1D0: autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [9.247255] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.247257] sound hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [9.247259] sound hdaudioC1D0:mono: mono_out=0x0 [9.247261] sound hdaudioC1D0:dig-out=0x1e/0x0 [9.247262] sound hdaudioC1D0:inputs: [9.247264] sound hdaudioC1D0: Front Mic=0x19 [9.247266] sound hdaudioC1D0: Rear Mic=0x18 [9.247268] sound hdaudioC1D0: Line=0x1a [9.260930] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input18 [9.261589] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input19 [9.261619] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card1/input10 [9.261928] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input20 [9.262246] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card1/input11 [9.262699] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card1/input12 [9.262997] input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card1/input13 [9.263271] input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card1/input14 [9.263535] input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card1/input15 [9.263815] input: HDA Intel PCH Line Out Side as /devices/pci:00/:00:1b.0/sound/card1/input16 [9.264073] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card1/input17 [9.279344] [ cut here ] [9.279372] WARNING: CPU: 0 PID: 411 at /build/linux-xmCjRp/linux-3.18.5/drivers/gpu/drm/i915/intel_display.c:11417 intel_crtc_set_config+0xbe8/0xe60 [i915]() [9.279374] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_utf8 nls_cp437 vfat fat iTCO_wdt mxm_wmi ppdev iTCO_vendor_support joydev x86_pkg_temp_thermal evdev intel_powerclamp intel_rapl coretemp efi_pstore kvm_intel psmouse kvm snd_hda_intel snd_hda_controller serio_raw snd_hda_codec efivars snd_hwdep pcspkr i2c_i801 snd_pcm snd_timer snd i915 soundcore drm_kms_helper intel_smartconnect tpm_infineon 8250_fintek video drm parport_pc tpm_tis battery parport tpm i2c_algo_bit wmi i2c_core shpchp mei_me lpc_ich mei mfd_core button processor fuse autofs4 ext4 crc16 mbcache jbd2 algif_skcipher af_alg dm_crypt dm_mod hid_generic usbhid hid netconsole configfs sg sr_mod cdrom sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel xhci_pci [9.279628] ahci libahci aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd xhci_hcd libata ehci_pci ehci_hcd scsi_mod r8169 mii usbcore usb_common thermal fan
Bug#777010: reportbug crashes when trying to submit bug report
Package: reportbug Version: 6.6.3 Severity: grave Justification: renders package unusable I was trying to report a bug to the kernel, but after the report was shown for confirmation before sending the mail, it crashes: Submit this report on linux-image-3.18.0-trunk-amd64 (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]? Y Traceback (most recent call last): File /usr/bin/reportbug, line 2211, in module main() File /usr/bin/reportbug, line 1081, in main return iface.user_interface() File /usr/bin/reportbug, line 2203, in user_interface self.options.envelopefrom) File /usr/lib/python2.7/dist-packages/reportbug/submit.py, line 305, in send_report os.popen(pager, 'w').write(message) IOError: [Errno 32] Broken pipe -- Package-specific info: ** Environment settings: EDITOR=/home/oxan/shell/bin/edit -f DEBEMAIL=o...@oxanvanleeuwen.nl EMAIL=o...@oxanvanleeuwen.nl DEBFULLNAME=Oxan van Leeuwen NAME=Oxan van Leeuwen INTERFACE=text ** /home/oxan/.reportbugrc: mode advanced ui text paranoid editor nano -r 80 no-cc realname Oxan van Leeuwen email o...@oxanvanleeuwen.nl -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (920, 'testing'), (910, 'stable'), (900, 'testing-proposed-updates'), (525, 'unstable'), (515, 'experimental'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt 1.0.9.6 ii python2.7.8-2 ii python-reportbug 6.6.3 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utilsnone pn debsums none pn dlocate none pn emacs23-bin-common | emacs24-bin-common none ii file 1:5.20-2 ii gnupg1.4.18-6 ii msmtp-mta [mail-transport-agent] 1.4.32-2 pn python-gtk2 none pn python-gtkspell none pn python-urwid none pn python-vte none ii xdg-utils1.1.0~rc1+git20111210-7.3 Versions of packages python-reportbug depends on: ii apt 1.0.9.6 ii python-debian 0.1.25 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
Am 31.01.2015 um 10:19 schrieb Stefan Fritsch: severity 755722 serious retitle 755722 systemd must sync systemclock to RTC on shutdown thanks Systemd must make sure that the system clock does not go backwards, which causes all kinds of problems, with file systems and with other software. To achieve that, systemd has to sync the system time to RTC on shutdown. Upstream's argument that the system time may not be more accurate is completely unrelated to this issue. Upstream argues, that whoever changes the clock, should also make sure to sync that to the RTC if so desired. E.g. if you change the time using the builtin timedatectl command, it will make sure the RTC is synced. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#775065: dpkg --configure -a results in Hangup after first package
Processing control commands: severity -1 important Bug #775065 [systemd] dpkg --configure -a results in Hangup after first package Severity set to 'important' from 'serious' tags -1 moreinfo unreproducible Bug #775065 [systemd] dpkg --configure -a results in Hangup after first package Added tag(s) unreproducible and moreinfo. -- 775065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775065 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#775065: dpkg --configure -a results in Hangup after first package
control: severity -1 important control: tags -1 moreinfo unreproducible Am 11.01.2015 um 21:40 schrieb Chris Carr: On 11/01/2015 20:02, Michael Biebl wrote: Am 11.01.2015 um 20:54 schrieb Chris Carr: I still cannot start gdm3: chrisc@tony:~$ sudo invoke-rc.d gdm3 start [] Starting GNOME Display Manager: gdm3[ 1094.663256] systemd-logind[9907]: Failed to enable subscription: Launch helper exited with unknown return code 1 [ 1094.669994] systemd-logind[9907]: Failed to fully start up daemon: Input/output error Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 failed! That somehow sounds like something with your dbus installation is broken. What is the output of $ ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper Attached as dbus.txt invoke-rc.d: initscript gdm3, action start failed. chrisc@tony:~$ There seem to be two problems there: one is gdm3 not starting, and the other is logind complaining about not being fully started. Is the dbus package installed? What's the output of systemctl status dbus.socket dbus.service? Failed to get D-Bus connection: Unknown error -1 You might consider attaching the full output of the systemd state via systemd-analyze dump Failed issue method call: Launch helper exited with unknown return code 1 I will try booting using systemd tomorrow and address your other points. Thank you again for your time, Ok, the failing dbus/gdm3 service looks like a completely different issue from dpkg failing to run dpkg --configure -a. Let's stick to the latter issue in this bug report, to not mix up things. Please also provide steps, how we can reproduce the issue. I decided to downgrade the severity, due to lack of information which makes it hard to evaluate the real impact of this issue and it rather looks like a corner case to me. Michael Thank -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#774881: [Pkg-haskell-maintainers] Bug#774881: Bug#774881: package haskell-ieee754 is causing FTBFS of package haskell-hastache on big-endian
Dear Jurica, thanks. Patch applied and uploaded. If it works as expected, then you should now create a debdiff between the two versions and file an unblock request with release.debian.org, preferably using reportbug. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#776565: preparing nmu for di-netboot-assistant
Hi, On Mon, Feb 02, 2015 at 10:38:57PM +0100, Cyril Brulebois wrote: Andreas B. Mundt a...@debian.org (2015-02-02): I have prepared a nmu which I plan to upload tomorrow after having tested the modification once more. (1-day notice is a short timeframe.) Yes, sorry, I planned to upload to DELAYED (as Holger suggested), but wanted to have this first 'go for it' to be able to re-adjust if necessary. [...] If you see any problems with the planned nmu, please rise your hand. It'd be nice to have some description of the changes in the changelog (that's what it's for! ;)) instead of pointers to a bug report thread/discussion. Right, I added some more details to the changelog now. Whatever gets uploaded, please make sure to get that pushed into the repository, or point to a branch/tag somewhere if you can't find anyone to push your changes there. OK, I'll keep that in mind. (Perhaps I should/could take care of di-netboot-assistant ...). The package has been uploaded to DELAYED/2 now. Thanks to everybody involved, Andi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774794: Debian Bug#774794: Re: dpkg: Add breaks for new trigger cycles
On 2015-02-03 07:12, Niels Thykier wrote: That said, I have no status on the cycles mentioned by Andreas Beckmann (CC'ed) in this bug report. If they are still relevant, we should have bugs for them. I can still reproduce these problems, not sure which package to be blamed for and whether its trigger cycles or something different. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774881: marked as done (package haskell-ieee754 is causing FTBFS of package haskell-hastache on big-endian)
Your message dated Tue, 03 Feb 2015 09:34:32 +
with message-id e1yizso-0006wj...@franck.debian.org
and subject line Bug#774881: fixed in haskell-ieee754 0.7.3-5
has caused the Debian Bug report #774881,
regarding package haskell-ieee754 is causing FTBFS of package haskell-hastache
on big-endian
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.)
--
774881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: haskell-ieee754
Version:0.7.3-3
Severity: serious
Tags: sid + patch
User: debian-m...@lists.debian.org
Usertags: mips-patch
Hello,
Package haskell-ieee754 is reason why package haskell-hastache is FTBFS on
big-endian.
I have attached a patch for this issue.
With this patch applied to package haskell-ieee754 I was able to build package
haskell-hastache on mips big-endian successfully.
Upstream issue:
https://github.com/lymar/hastache/issues/36#
Thank you!
Regards,
Jurica
--- haskell-ieee754-0.7.3.orig/cbits/feqrel_source.c
+++ haskell-ieee754-0.7.3/cbits/feqrel_source.c
@@ -16,7 +16,7 @@
# define REAL_EXPBIAS((uint16_t) 0x3F00)
# define REAL_EXPBIAS_INT32 ((uint32_t) 0x7F80)
# define REAL_MANTISSAMASK_INT32 ((uint32_t) 0x007F)
-# if BIG_ENDIAN == 1
+# if BYTE_ORDER == BIG_ENDIAN
# define REAL_EXPPOS_INT16 0
# else
# define REAL_EXPPOS_INT16 1
@@ -28,7 +28,7 @@
# define REAL_EXPBIAS((uint16_t) 0x3FE0)
# define REAL_EXPBIAS_INT32 ((uint32_t) 0x7FF0)
# define REAL_MANTISSAMASK_INT32 ((uint32_t) 0x000F); /* for the MSB only */
-# if BIG_ENDIAN == 1
+# if BYTE_ORDER == BIG_ENDIAN
# define REAL_EXPPOS_INT16 0
# define REAL_SIGNPOS_BYTE 0
# else
---End Message---
---BeginMessage---
Source: haskell-ieee754
Source-Version: 0.7.3-5
We believe that the bug you reported is fixed in the latest version of
haskell-ieee754, 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 774...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joachim Breitner nome...@debian.org (supplier of updated haskell-ieee754
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: Tue, 03 Feb 2015 10:18:28 +0100
Source: haskell-ieee754
Binary: libghc-ieee754-dev libghc-ieee754-prof libghc-ieee754-doc
Architecture: source all amd64
Version: 0.7.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
pkg-haskell-maintain...@lists.alioth.debian.org
Changed-By: Joachim Breitner nome...@debian.org
Description:
libghc-ieee754-dev - Utilities for dealing with IEEE floating point
numbers${haskell:S
libghc-ieee754-doc - Utilities for dealing with IEEE floating point
numbers${haskell:S
libghc-ieee754-prof - Utilities for dealing with IEEE floating point
numbers${haskell:S
Closes: 774881
Changes:
haskell-ieee754 (0.7.3-5) unstable; urgency=medium
.
* Backport endianness detection fix from upstream (Closes: 774881)
Thanks to Jurica Stanojkovic for preparing the patch.
Checksums-Sha1:
18395453455ee978d3e9c61a794375f97747cd66 2217 haskell-ieee754_0.7.3-5.dsc
c6bbce1b012a2dd55c4620ddc033bcded9dd35f4 3528
haskell-ieee754_0.7.3-5.debian.tar.xz
151aca155bb85364f20907f977a26d42d93024be 39424
libghc-ieee754-doc_0.7.3-5_all.deb
c39772998f2872243abc8165221ea19816d7cc10 61826
libghc-ieee754-dev_0.7.3-5_amd64.deb
a523436e4adb50589c5f095c6663f0f09600c797 62088
libghc-ieee754-prof_0.7.3-5_amd64.deb
Checksums-Sha256:
8533f510435ed7bacf3533679d8fb78808f6f699e58ca8107f07f33ff3b1a192 2217
haskell-ieee754_0.7.3-5.dsc
e9fea524bfc14a10064a3ca34fdf3a01a9e7276fc7698b60bd07220017421903 3528
haskell-ieee754_0.7.3-5.debian.tar.xz
1220afb128b298f9b863cafd9e09aa2dbd35e543354a9ecfc6c2c94e2fd4eb06 39424
libghc-ieee754-doc_0.7.3-5_all.deb
1700a9602420152c8a6d1e88f492151028a1ce629ee04730dec676ace3f7add9 61826
libghc-ieee754-dev_0.7.3-5_amd64.deb
fc3b09dffaebcad2c05a1a8755a4c0feaca9ee79c9123653f3e80461738b08f8 62088
libghc-ieee754-prof_0.7.3-5_amd64.deb
Files:
6621417456831a1f17a3d9e46e8ba22b 2217 haskell extra haskell-ieee754_0.7.3-5.dsc
16f9e48efa4a0489a9ad0247745eb9d2 3528 haskell extra
Bug#776907: dante: FTBFS due to libtool movement
Source: dante Version: 1.2.2+dfsg-3 Severity: serious Justification: fails to build from source (but built successfully in the past) User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 dante-client Hi, dante/experimental needs a libtool dependency update, things have moved between packages some time ago already. dh_auto_build make[1]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg' Making all in include make[2]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/include' make all-am make[3]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/include' make[3]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/include' make[2]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/include' Making all in libscompat make[2]: Entering directory '/tmp/buildd/dante-1.2.2+dfsg/libscompat' /usr/bin/libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I. -D_FORTIFY_SOURCE=2 -DDEBUG=0 -DSOCKS_CLIENT=0 -DSOCKS_SERVER=0 -DSOCKSLIBRARY_DYNAMIC=0 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIE -fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security -pipe -c -o issetugid.lo issetugid.c /bin/bash: /usr/bin/libtool: No such file or directory Makefile:312: recipe for target 'issetugid.lo' failed make[2]: *** [issetugid.lo] Error 127 make[2]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg/libscompat' Makefile:271: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/buildd/dante-1.2.2+dfsg' dh_auto_build: make -j1 returned exit code 2 debian/rules:67: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: dante: FTBFS due to libtool movement
Processing control commands: affects -1 dante-client Bug #776907 [src:dante] dante: FTBFS due to libtool movement Added indication that 776907 affects dante-client -- 776907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776907 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#776910: apt: upgrade from wheezy to jessie breaks in the middle
Package: apt Version: 1.0.9.6 Severity: grave Tags: newcomer Justification: renders package unusable My guess is that some limit on number of errors was taken into account unneceserly during an upgrade - upgrades are expected to rise trancient errors. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture i386; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-headers-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-headers-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-image-extra-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-image-extra-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-signed-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-signed-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^kfreebsd-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^kfreebsd-headers-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^gnumach-image-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^gnumach-image-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^.*-modules-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^.*-modules-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^.*-kernel-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^.*-kernel-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-backports-modules-.*-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^linux-tools-3\.16\.0-4-586$; APT::NeverAutoRemove:: ^linux-tools-3\.2\.0-4-486$; APT::NeverAutoRemove:: ^postgresql-; APT::VersionedKernelPackages ; APT::VersionedKernelPackages:: linux-image; APT::VersionedKernelPackages:: linux-headers; APT::VersionedKernelPackages:: linux-image-extra; APT::VersionedKernelPackages:: linux-signed-image; APT::VersionedKernelPackages:: kfreebsd-image; APT::VersionedKernelPackages:: kfreebsd-headers; APT::VersionedKernelPackages:: gnumach-image; APT::VersionedKernelPackages:: .*-modules; APT::VersionedKernelPackages:: .*-kernel; APT::VersionedKernelPackages:: linux-backports-modules-.*; APT::VersionedKernelPackages:: linux-tools; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Update ; APT::Update::Post-Invoke-Success ; APT::Update::Post-Invoke-Success:: [ ! -f /var/run/dbus/system_bus_socket ] || /usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt org.debian.apt.CacheChanged || true; APT::Update::Post-Invoke-Success:: /usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service /usr/bin/test -S /var/run/dbus/system_bus_socket /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update /dev/null; /bin/echo /dev/null; APT::Immediate-Configure 1; APT::Default-Release jessie; APT::Architectures ; APT::Architectures:: i386; APT::Compressor ; APT::Compressor::. ; APT::Compressor::.::Name .; APT::Compressor::.::Extension ; APT::Compressor::.::Binary ; APT::Compressor::.::Cost 1; APT::Compressor::gzip ; APT::Compressor::gzip::Name gzip; APT::Compressor::gzip::Extension .gz; APT::Compressor::gzip::Binary gzip; APT::Compressor::gzip::Cost 2; APT::Compressor::gzip::CompressArg ; APT::Compressor::gzip::CompressArg:: -9n; APT::Compressor::gzip::UncompressArg ; APT::Compressor::gzip::UncompressArg:: -d; APT::Compressor::bzip2 ; APT::Compressor::bzip2::Name bzip2; APT::Compressor::bzip2::Extension .bz2; APT::Compressor::bzip2::Binary bzip2; APT::Compressor::bzip2::Cost 3; APT::Compressor::bzip2::CompressArg ; APT::Compressor::bzip2::CompressArg:: -9; APT::Compressor::bzip2::UncompressArg ; APT::Compressor::bzip2::UncompressArg:: -d; APT::Compressor::xz ; APT::Compressor::xz::Name xz; APT::Compressor::xz::Extension .xz; APT::Compressor::xz::Binary xz; APT::Compressor::xz::Cost 4; APT::Compressor::xz::CompressArg ; APT::Compressor::xz::CompressArg:: -6; APT::Compressor::xz::UncompressArg ; APT::Compressor::xz::UncompressArg:: -d; APT::Compressor::lzma ; APT::Compressor::lzma::Name lzma; APT::Compressor::lzma::Extension .lzma; APT::Compressor::lzma::Binary xz; APT::Compressor::lzma::Cost 5; APT::Compressor::lzma::CompressArg ; APT::Compressor::lzma::CompressArg:: --format=lzma; APT::Compressor::lzma::CompressArg:: -9;
Bug#774881: [Pkg-haskell-maintainers] Bug#774881: Bug#774881: package haskell-ieee754 is causing FTBFS of package haskell-hastache on big-endian
Hi again, Am Dienstag, den 03.02.2015, 10:20 +0100 schrieb Joachim Breitner: thanks. Patch applied and uploaded. If it works as expected, then you should now create a debdiff between the two versions and file an unblock request with release.debian.org, preferably using reportbug. I screwed up and accidentally uploaded 0.7.6 to unstable. Maybe you are lucky and can still get an unblock request granted for it; I really want to avoid things like 0.7.6.really.0.7.3 at this point (as it would also affect other packages). Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#776909: kernel-package: couple of modules fail to load after wheezy to jessie upgrade
Package: kernel-package Version: 13.014+nmu1 Severity: grave Tags: newcomer Justification: renders package unusable I've upgraded my LG notebook (X-note: LS50a) from wheezy to jessie and: 1. the upgrade have installed kernel version-i585 in addition to my earlier (automatically installed during an upgrade to wheezy) version-i486. 2. when booting i486, it fails to modprobe ext4-fs during the boot. It breaks boot sequence, but manual (from shell prompt) modprobe ext4 does not load the module into the kernel. 3. when booting i586, it fails to load kernel module responsible for notebook keyboard (touchpad is loaded OK). USB keyboard works fine. 4. DRM:i9xx fails to configure with *ERROR* pipe A underrun -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages kernel-package depends on: ii bc 1.06.95-9 ii binutils 2.24.90.20141023-1 ii build-essential 11.7 ii bzip21.0.6-7+b2 ii dpkg-dev 1.17.23 ii file 1:5.20-2 ii gettext 0.19.3-2 ii kmod 18-3 ii lzma 9.22-2 ii po-debconf 1.0.16+nmu3 ii xmlto0.0.25-2 ii xz-utils [lzma] 5.1.1alpha+20120614-2+b3 Versions of packages kernel-package recommends: ii cpio 2.11+dfsg-4 ii docbook-utils 0.6.14-3 ii kernel-common 13.014+nmu1 pn uboot-mkimage none Versions of packages kernel-package suggests: ii libncurses5-dev [libncurses-dev] 5.9+20140913-1+b1 pn linux-source none -- 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#776911: gnome-session: session fails to start with something went wrong message
Package: gnome-session Version: 3.14.0-2 Severity: grave Tags: newcomer Justification: renders package unusable right after upgrade from wheezy to jessie I'm not able to login with standard gdm3 login panel. It takes my username and password, and tries to start gnome session, but fails with Opps screen. The only hints I find in logs are drm:i9xx_set_fifo_underrun *ERROR* pipe A underrun. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gnome-session depends on: ii gnome-session-bin 3.14.0-2 ii gnome-session-common 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell3.14.2-3+b1 gnome-session recommends no packages. Versions of packages gnome-session suggests: ii desktop-base 8.0.2 ii gnome-keyring 3.14.0-1+b1 ii gnome-user-guide 3.14.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#776913: flightgear-data-all: new upstream version needed by flightgear/experimental
Package: flightgear-data-all Version: 3.2.0-1~exp1 Severity: serious Tags: experimental User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 flightgear Hi, flightgear/experimental is not installable: The following packages have unmet dependencies: flightgear : Depends: flightgear-data-all (= 3.2.0~) but it is not going to be installed Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: flightgear-data-all: new upstream version needed by flightgear/experimental
Processing control commands: affects -1 flightgear Bug #776913 [flightgear-data-all] flightgear-data-all: new upstream version needed by flightgear/experimental Added indication that 776913 affects flightgear -- 776913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776913 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#773354: please add breaks: live-tools ( 4.0.1-1)
Hello Gaudenz Steinlin! On Mon, Feb 02, 2015 at 10:25:07PM +0100, Gaudenz Steinlin wrote: Hi Andreas My NMU was in no way meant to critice your maintenance of util-linux or to attack you. It's just that in the current phase of the release process it's time to fix these bugs and my aim is to help with that. As you stated that you are not very motivated to work on this bug I thought you would appreciate this help. I absolutely appreciate that you're interested in working on this and I in no way see it as a critisism of my work. If my replies sound harsh and annoyed it's only because I'm busy and low on both motivation for Debian-work and low on energy. Please don't let that distract you. Please try to help dig through what I'm saying for the point that is technically adressable. I'm sorry I'm not better at english which is a limiting factor for me being able to express myself more clearly. Hopefully what I write gives you some clues to what issues I might have spotted. Andreas Henriksson andr...@fatal.se writes: Hello Gaudenz Steinlin. On Mon, Feb 02, 2015 at 11:25:55AM +0100, Gaudenz Steinlin wrote: Of course a fix in util-linux can't solve problems resulting from other packages. All packages that call update-initramfs and don't depend on initramfs-tools need the same Breaks relation to live-tools. I don't know how many other such packages exist beside util-linux. Easy to find out thanks to the awesome codesearch: http://codesearch.debian.net/perpackage-results/update-initramfs/2/page_0 (Adding regexps to the query for filtering out only relevant matches is left as an exercise to the reader.) In other words, many That is why adding breaks IMHO is not a viable solution at all anywhere. That does not really help much because we don't need a list of packages that mention update-initramfs in some file but a list of packages that call update-initramfs in their maintainerscript without depending on initramfs-tools. I don't think codesearch is able to produce that list, but to me this seems like a quite special case. I would expect most packages that modify the initramfs to actually depend on initramfs-tools. But I agree that probably more packages than just util-linux need fixing for this. But this is outside the scope of this bug and as long as no other bugs are filed, it's hard to track. I also don't see a viable solution to this bug which fixes all of these problems in one go. I guess we just have to agree to disagree. In my point of view sweeping symptoms under the carpet is not the way to go to call something solved. The problem is not in util-linux to start with and if we can't solve it in the actually buggy package then we should alter all the ways to trigger it, not just one. I also think it's better to just drop the update-initramfs call instead if we're going down that path anyway (as the reason it was added does not apply to jessie). I agree that fixing the problem with Breaks is a bit ugly and in theory adds the fix to the wrong package. But I currently don't see any viable other solution to this problem beside adding all these Breaks relations. An update to the stable version of live-tools does not seem practical to me. Do you see another way to fix this? Yes. Please read my previous mail to the bug report. So if I got you right, you would prefer to remove the update-initramfs call from util-linux's postinst. I'm fine with that. I can do another upload if you confirm that's your prefered solution. If initramfs-tools from current unstable really does not go into testing, then I agree that is probably the slightly better alternative. To me as an NMUer the Breaks seemd like the safer option as it's a no-op as long as live-tools is not installed on the same system. So there is less chance that the NMU breaks something. Right. I hope we, during the next development window, make sure initramfs-tools stops pulling in parts of util-linux into the initramfs. From what I've heard, the reason is that fsck does timestamp checking which other distributions has simply patched out to not have to deal with timezones in initramfs (or something like that -- don't remember exactly). This is just one example out of several problems I see with your NMU. Which other problem do you see? Well, for one: Your NMU is RC buggy, given that you incorporated the previous NMU with bugs and all. Thanks for taking responsibility for that. ;) Well for one it was not my upload that introduced this RC bug. The version of the previous NMU was already in *testing* when I did my upload. IMO we are all colectively responsible for getting the jessie RC bug count down. So it's as much my responsibility to fix this as yours. ;-) :P But if I do another upload I will also fix the typo in the 4.1 NMU. I missed the fact that the 4.1 NMU did not fix the bug it claimed to fix. Please, again, also read my
Bug#775350: marked as done (libblkid-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)
Your message dated Tue, 03 Feb 2015 21:42:16 +
with message-id e1yilee-0002yo...@franck.debian.org
and subject line Bug#775350: fixed in util-linux 2.25.2-5
has caused the Debian Bug report #775350,
regarding libblkid-dev: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
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.)
--
775350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libblkid-dev
Version: 2.25.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
lenny - squeeze - wheezy - jessie
The bug dates back to the lenny-squeeze upgrade cycle. The lenny version
of the package shipped
/usr/share/doc/libblkid-dev - libblkid1
while in squeeze this was replaced by a directory, but the symlink
got never transitioned, so the problem persists in long grown
installations until today.
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
5m26.4s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libblkid-dev/changelog.Debian.gz (libblkid-dev:amd64) !=
/usr/share/doc/libblkid1/changelog.Debian.gz (libblkid1:amd64)
/usr/share/doc/libblkid-dev - libblkid1
/usr/share/doc/libblkid-dev/changelog.gz (libblkid-dev:amd64) !=
/usr/share/doc/libblkid1/changelog.gz (libblkid1:amd64)
/usr/share/doc/libblkid-dev - libblkid1
/usr/share/doc/libblkid-dev/copyright (libblkid-dev:amd64) !=
/usr/share/doc/libblkid1/copyright (libblkid1:amd64)
/usr/share/doc/libblkid-dev - libblkid1
5m33.5s ERROR: FAIL: After purging files have disappeared:
/usr/share/doc/libblkid1/changelog.Debian.gz owned by: libblkid1:amd64
/usr/share/doc/libblkid1/changelog.gz owned by: libblkid1:amd64
/usr/share/doc/libblkid1/copyright owned by: libblkid1:amd64
It's sufficient to fix this in jessie, no need to backport the fix
to wheezy (which does not have dpkg-maintscript-helper symlink_to_dir).
cheers,
Andreas
libblkid-dev_2.25.2-4.log.gz
Description: application/gzip
---End Message---
---BeginMessage---
Source: util-linux
Source-Version: 2.25.2-5
We believe that the bug you reported is fixed in the latest version of
util-linux, 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 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Henriksson andr...@fatal.se (supplier of updated util-linux 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: Tue, 03 Feb 2015 20:55:38 +0100
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb cfdisk-udeb
libblkid1 libblkid1-udeb libblkid-dev libmount1
Processed: Re: rdesktop 1.8.2-3 fails to connect to Windows Server 2008
Processing control commands: severity -1 important Bug #776726 [rdesktop] rdesktop 1.8.2-3 fails to connect to Windows Server 2008 Severity set to 'important' from 'grave' -- 776726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776726 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#776726: rdesktop 1.8.2-3 fails to connect to Windows Server 2008
control: severity -1 important thanks Does the workaround in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763599 work? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775375: marked as done (python-django: CVE-2015-0219 CVE-2015-0220 CVE-2015-0221 CVE-2015-0222)
Your message dated Tue, 03 Feb 2015 21:32:18 + with message-id e1yil50-0008pl...@franck.debian.org and subject line Bug#775375: fixed in python-django 1.4.5-1+deb7u9 has caused the Debian Bug report #775375, regarding python-django: CVE-2015-0219 CVE-2015-0220 CVE-2015-0221 CVE-2015-0222 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.) -- 775375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775375 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: python-django Version: 1.7.1-1 Severity: grave Tags: security upstream fixed-upstream Hi, the following vulnerabilities were published for python-django. CVE-2015-0219[0]: WSGI header spoofing via underscore/dash conflation CVE-2015-0220[1]: Mitigated possible XSS attack via user-supplied redirect URLs CVE-2015-0221[2]: Denial-of-service attack against django.views.static.serve CVE-2015-0222[3]: Database denial-of-service with ModelMultipleChoiceField If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-0219 [1] https://security-tracker.debian.org/tracker/CVE-2015-0220 [2] https://security-tracker.debian.org/tracker/CVE-2015-0221 [3] https://security-tracker.debian.org/tracker/CVE-2015-0222 [4] https://www.djangoproject.com/weblog/2015/jan/13/security/ Please adjust the affected versions in the BTS as needed. Regards, Salvatore ---End Message--- ---BeginMessage--- Source: python-django Source-Version: 1.4.5-1+deb7u9 We believe that the bug you reported is fixed in the latest version of python-django, 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 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog hert...@debian.org (supplier of updated python-django 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: Wed, 28 Jan 2015 10:24:59 +0100 Source: python-django Binary: python-django python-django-doc Architecture: source all Version: 1.4.5-1+deb7u9 Distribution: wheezy-security Urgency: high Maintainer: Chris Lamb la...@debian.org Changed-By: Raphaël Hertzog hert...@debian.org Description: python-django - High-level Python web development framework python-django-doc - High-level Python web development framework (documentation) Closes: 775375 Changes: python-django (1.4.5-1+deb7u9) wheezy-security; urgency=high . * New upstream security release: https://www.djangoproject.com/weblog/2015/jan/13/security/ - WSGI header spoofing via underscore/dash conflation (CVE-2015-0219) - Possible XSS attack via user-supplied redirect URLs (CVE-2015-0220) - Denial-of-service attack against django.views.static.serve (CVE-2015-0221) Closes: #775375 * Also include a fix for a regression introduced by the patch for CVE-2015-0221: https://code.djangoproject.com/ticket/24158 Checksums-Sha1: c8c1760f38e043f5ad67871a8cf1d39086327026 1928 python-django_1.4.5-1+deb7u9.dsc 72e7794a049795d2a16bfa070336046276e17544 53052 python-django_1.4.5-1+deb7u9.debian.tar.gz a865f776c70540e8af70316299946d437473a134 5398024 python-django_1.4.5-1+deb7u9_all.deb 9cd42699ef94932983c537d3d2ae39cf59a44b03 2436772 python-django-doc_1.4.5-1+deb7u9_all.deb Checksums-Sha256: c5f3ac951c2ab826259684a57ea745b72aba073dc1002b2071e77641128ac9ac 1928 python-django_1.4.5-1+deb7u9.dsc bdd28da574424d333b7797e4bb8cb4f27a11e4c201decd8d10b189c0e35b9258 53052 python-django_1.4.5-1+deb7u9.debian.tar.gz 3734fe7cebccdf651098997ac8c9f76df49cc8d2585de232e3ed3ce232bf1565 5398024 python-django_1.4.5-1+deb7u9_all.deb ec7b1ed7b77932e54244a2e71463213a52587eff043114c5fe779258663d9b1c 2436772 python-django-doc_1.4.5-1+deb7u9_all.deb Files: 2a628d741213ad706a136698fc9f3334 1928 python optional python-django_1.4.5-1+deb7u9.dsc 5a169beef36a78db87c87e26fdc5df10 53052 python optional python-django_1.4.5-1+deb7u9.debian.tar.gz f56d65e6f8d01e06003ddbde3a8b82b3 5398024 python optional python-django_1.4.5-1+deb7u9_all.deb 16fcc053ace64ba0af18540d5de46af6 2436772 doc
Bug#768269: marked as done (appdata-tools and appstream-util: error when trying to install together)
Your message dated Tue, 03 Feb 2015 21:34:45 + with message-id e1yil7n-kd...@franck.debian.org and subject line Bug#768269: fixed in appstream-glib 0.3.4-1 has caused the Debian Bug report #768269, regarding appdata-tools and appstream-util: 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.) -- 768269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: appstream-util,appdata-tools Version: appstream-util/0.3.2-1 Version: appdata-tools/0.1.7-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-11-06 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: Extracting templates from packages: 30% Extracting templates from packages: 61% Extracting templates from packages: 91% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package libgmp10:amd64. (Reading database ... 10892 files and directories currently installed.) Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-3_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-3) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-3_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-2_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-2) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-3_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-3) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.9-5_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-5) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12.1+dfsg-11_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12.1+dfsg-11_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12.1+dfsg-11_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12.1+dfsg-11) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.2+dfsg1-1_amd64.deb ... Unpacking libxml2:amd64 (2.9.2+dfsg1-1) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../libglib2.0-0_2.42.0-2_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.42.0-2) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../libatk1.0-data_2.14.0-1_all.deb ... Unpacking libatk1.0-data (2.14.0-1) ... Selecting previously unselected package libatk1.0-0:amd64. Preparing to unpack .../libatk1.0-0_2.14.0-1_amd64.deb ... Unpacking libatk1.0-0:amd64 (2.14.0-1) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.1.0-6_amd64.deb ... Unpacking libexpat1:amd64 (2.1.0-6) ... Selecting previously unselected package libpng12-0:amd64. Preparing to unpack .../libpng12-0_1.2.50-2_amd64.deb ... Unpacking libpng12-0:amd64 (1.2.50-2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../libfreetype6_2.5.2-2_amd64.deb ... Unpacking libfreetype6:amd64 (2.5.2-2) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../fonts-dejavu-core_2.34-1_all.deb ... Unpacking fonts-dejavu-core (2.34-1) ... Selecting previously unselected package fontconfig-config.
Bug#771989: marked as done (dbus: Please (consider) switch(ing) to no-await triggers)
Your message dated Tue, 03 Feb 2015 21:35:23 + with message-id e1yil7z-in...@franck.debian.org and subject line Bug#771989: fixed in dbus 1.8.14-2 has caused the Debian Bug report #771989, regarding dbus: Please (consider) switch(ing) to no-await triggers 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.) -- 771989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dpkg Version: 1.17.22 Severity: grave Hello, today I tried to dist-upgrade my system (sid) starting from a package state of a couple of weeks ago. First apt reported a failed dpkg right in the middle of the upgrade process without displaying any visible error messages. Now when I run apt-get -f install or attempt to install some missing package explicitly, it ends up in a loop where dpkg runs maintainer scripts on dbus without end. Here is dpkg.log and some console output: 2014-11-29 11:23:24 startup archives unpack 2014-11-29 11:23:28 upgrade debianutils:amd64 4.4 4.4+b1 2014-11-29 11:23:28 status half-configured debianutils:amd64 4.4 2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4 2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4 2014-11-29 11:23:28 status triggers-pending man-db:amd64 2.7.0.2-2 2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4 2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1 2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1 2014-11-29 11:23:28 trigproc man-db:amd64 2.7.0.2-2 keine 2014-11-29 11:23:28 status half-configured man-db:amd64 2.7.0.2-2 2014-11-29 11:23:31 status installed man-db:amd64 2.7.0.2-2 2014-11-29 11:23:32 startup packages configure 2014-11-29 11:23:32 configure debianutils:amd64 4.4+b1 keine 2014-11-29 11:23:32 status unpacked debianutils:amd64 4.4+b1 2014-11-29 11:23:32 status half-configured debianutils:amd64 4.4+b1 2014-11-29 11:23:32 status installed debianutils:amd64 4.4+b1 2014-11-29 11:23:32 startup archives unpack 2014-11-29 11:23:33 upgrade bash:amd64 4.3-11 4.3-11+b1 2014-11-29 11:23:33 status half-configured bash:amd64 4.3-11 2014-11-29 11:23:33 status unpacked bash:amd64 4.3-11 2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11 2014-11-29 11:23:33 status triggers-pending menu:amd64 2.1.47 2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11 2014-11-29 11:23:33 status triggers-pending install-info:amd64 5.2.0.dfsg.1-5 2014-11-29 11:23:33 status triggers-pending man-db:amd64 2.7.0.2-2 2014-11-29 11:23:34 status half-installed bash:amd64 4.3-11 2014-11-29 11:23:34 status triggers-awaited menu:amd64 2.1.47 2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:34 trigproc menu:amd64 2.1.47 keine 2014-11-29 11:23:34 status half-configured menu:amd64 2.1.47 2014-11-29 11:23:36 status installed menu:amd64 2.1.47 2014-11-29 11:23:36 trigproc install-info:amd64 5.2.0.dfsg.1-5 keine 2014-11-29 11:23:36 status half-configured install-info:amd64 5.2.0.dfsg.1-5 2014-11-29 11:23:38 status installed install-info:amd64 5.2.0.dfsg.1-5 2014-11-29 11:23:38 trigproc man-db:amd64 2.7.0.2-2 keine 2014-11-29 11:23:38 status half-configured man-db:amd64 2.7.0.2-2 2014-11-29 11:23:39 status installed man-db:amd64 2.7.0.2-2 2014-11-29 11:23:40 startup packages configure 2014-11-29 11:23:40 configure bash:amd64 4.3-11+b1 keine 2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status half-configured bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status installed bash:amd64 4.3-11+b1 2014-11-29 11:23:40 status triggers-pending menu:amd64 2.1.47 2014-11-29 11:23:40 status triggers-awaited menu:amd64 2.1.47 2014-11-29 11:23:40 trigproc menu:amd64 2.1.47 keine 2014-11-29 11:23:40 status half-configured menu:amd64 2.1.47 2014-11-29 11:23:42 status installed menu:amd64 2.1.47 2014-11-29 11:23:43 startup archives unpack 2014-11-29 11:23:44 upgrade bsdutils:amd64 1:2.25.2-2 1:2.25.2-3 2014-11-29 11:23:44 status half-configured bsdutils:amd64 1:2.25.2-2 2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-2 2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2 2014-11-29 11:23:44 status triggers-pending man-db:amd64 2.7.0.2-2 2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2 2014-11-29 11:23:44 status unpacked
Bug#773354: marked as done (please add breaks: live-tools ( 4.0.1-1))
Your message dated Tue, 03 Feb 2015 21:42:16 + with message-id e1yilee-0002yi...@franck.debian.org and subject line Bug#773354: fixed in util-linux 2.25.2-5 has caused the Debian Bug report #773354, regarding please add breaks: live-tools ( 4.0.1-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 773354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: live-tools Version: 4.0.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. From the attached log (scroll to the bottom...): Preparing to unpack .../util-linux_2.25.1-5_amd64.deb ... Unpacking util-linux (2.25.1-5) over (2.20.1-5.3) ... Setting up util-linux (2.25.1-5) ... Installing new version of config file /etc/init.d/hwclock.sh ... E: /usr/sbin/update-initramfs.orig.initramfs-tools - command not found E: On Debian based systems, update-initramfs from initramfs-tools E: can be installed with: E: apt-get install initramfs-tools dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: util-linux cheers, Andreas live-tools_4.0.1-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: util-linux Source-Version: 2.25.2-5 We believe that the bug you reported is fixed in the latest version of util-linux, 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 773...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson andr...@fatal.se (supplier of updated util-linux 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: Tue, 03 Feb 2015 20:55:38 +0100 Source: util-linux Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb cfdisk-udeb libblkid1 libblkid1-udeb libblkid-dev libmount1 libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb Architecture: source amd64 all Version: 2.25.2-5 Distribution: unstable Urgency: medium Maintainer: Debian util-linux Maintainers ah-util-li...@debian.org Changed-By: Andreas Henriksson andr...@fatal.se Description: bsdutils - basic utilities from 4.4BSD-Lite cfdisk-udeb - Manually partition a hard drive (cfdisk) (udeb) fdisk-udeb - Manually partition a hard drive (fdisk) (udeb) libblkid-dev - block device id library - headers and static libraries libblkid1 - block device id library libblkid1-udeb - stripped down block device id library, for debian-installer (udeb) libmount-dev - device mounting library - headers and static libraries libmount1 - device mounting library libsmartcols-dev - smart column output alignment library - headers and static librar libsmartcols1 - smart column output alignment library libsmartcols1-udeb - stripped down smart column output aligment library, for debian-in (udeb) libuuid1 - Universally Unique ID library libuuid1-udeb - stripped down universally unique id library, for debian-installer (udeb) mount - Tools for mounting and manipulating filesystems util-linux - Miscellaneous system utilities util-linux-locales - Locales files for util-linux util-linux-udeb - stripped down miscellaneous system utilities, for debian-installe (udeb) uuid-dev - universally unique id library - headers and static libraries uuid-runtime - runtime components for the Universally Unique ID library Closes: 772846 773354 775350 Changes: util-linux (2.25.2-5) unstable; urgency=medium . * Revert Trigger update of initramfs on upgrades (Closes: #773354) * Revert Add Breaks: live-tools (4.0~alpha17-1) - No longer needed since dropping the update-initramfs call. * Fix typo in symlink_to_dir and bump prior-version - in other words, fix 2.25.2-4.1 upload. (Closes: #775350) * Add Breaks: grml-debootstrap ( 0.68) - previous versions does not work properly with
