Processed: user debian...@lists.debian.org, tagging 717457, tagging 687086
Processing commands for cont...@bugs.debian.org:
user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
tags 717457 + wheezy
Bug #717457 [release.debian.org] pu: package oss4/4.2-build2006-2+deb7u2
Added tag(s) wheezy.
tags 687086 + patch
Bug #687086 {Done: Sebastien NOEL sebast...@twolife.org} [oss4-dkms]
oss4-dkms: missing dependency on dpkg-dev
Added tag(s) patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
687086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687086
717457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137439923731166.transcr...@bugs.debian.org
Bug#717489: RM: xfm/1.5.4-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove xfm from testing. I plan to drop it (RFA #717486 filed in the unlikely case anyone wants to take it over instead) and have filed #717487 to stop it from migrating back to testing. (I currently plan to request removal from unstable once jessie released (preferable without xfm)). Bernhard R. Link -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130721115102.ga4...@client.brlink.eu
Bug#707018: Status of KDE 4.10 transition
Hi, yet another update on the status of the KDE 4.10 transition: Alle venerdì 19 luglio 2013, Pino Toscano ha scritto: * thanks to the latest givebacks [1], now basically all the uploaded sources are built. There are still a couple of failures on mipsel, but they are in leaf sources which do not affect this transitions (I will ask for further gb). There is only rocs left in such state. * regarding the rest of the sources: apper -- binNMU bespin -- binNMU calligra -- binNMU digikam -- (A) kamoso -- (A) kde-style-qtcurve -- binNMU kdevelop -- binNMU knights -- binNMU kphotoalbum -- binNMU kshutdown -- binNMU ktorrent -- binNMU kwin-style-crystal -- (A) kwin-style-dekorator -- binNMU plasma-widget-fastuserwitch -- binNMU tagua -- binNMU (A) the version in sid/testing is not compatible with newer libs, we either are going to upload the version in experimental or a proper fix I missed the status of knights and tagua, that FTBFSed (#717414 and #717415); calligra did it too (#717413). knights and calligra had both MUs which fixed the build issues, and tagua has a patch for fixing it (it is a leaf package, so if unfixed could be hinted out of testing). That said, we are tackling few issues/regressions (mostly in the new pim stack), so could it be possible to hold the kde4libs migration with a block for now? (It should avoid all the rest to migrate too.) Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
Bug #681374 cherry picked upstream patch
Dear release team,
with the patch from the upstream commit it is possible to fix this Bug.
I've attached a debdiff of the package with the patch applied.
I hope you can make use of this and possibly add it to proposed updates.
Regards,
Marcel Meißner
diff -Nru rhythmbox-2.97/debian/changelog rhythmbox-2.97/debian/changelog
--- rhythmbox-2.97/debian/changelog 2012-07-28 03:42:01.0 +0200
+++ rhythmbox-2.97/debian/changelog 2013-07-21 14:13:17.0 +0200
@@ -1,3 +1,11 @@
+rhythmbox (2.97-2.2) UNRELEASED; urgency=normal
+
+ * Non-maintainer upload.
+ * fix rhythmbox not resuming from pause on audio-cd playback
+(Closes: #681374)
+
+ -- Marcel Meißner mm-meiss...@gmx.de Sun, 21 Jul 2013 12:43:21 +0200
+
rhythmbox (2.97-2.1) unstable; urgency=high
* Non-maintainer upload.
diff -Nru rhythmbox-2.97/debian/patches/series rhythmbox-2.97/debian/patches/series
--- rhythmbox-2.97/debian/patches/series 2012-07-27 22:40:37.0 +0200
+++ rhythmbox-2.97/debian/patches/series 2013-07-21 13:12:24.0 +0200
@@ -1,2 +1,3 @@
rb-mb5.patch
CVE-2012-3355.patch
+shell-player-clear-playlist.patch
diff -Nru rhythmbox-2.97/debian/patches/shell-player-clear-playlist.patch rhythmbox-2.97/debian/patches/shell-player-clear-playlist.patch
--- rhythmbox-2.97/debian/patches/shell-player-clear-playlist.patch 1970-01-01 01:00:00.0 +0100
+++ rhythmbox-2.97/debian/patches/shell-player-clear-playlist.patch 2013-07-21 13:16:14.0 +0200
@@ -0,0 +1,20 @@
+From: Jonathan Matthew jonat...@d14n.org
+Subject: shell-player: clear playlist parser cancellable when pausing
+Origin: upstream, https://git.gnome.org/browse/rhythmbox;a=commitdiff;h=98e5a25b3c32c9915357968a78783c1ac21c7130
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=663440
+Debian-Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681374
+Index: rhythmbox-2.97/shell/rb-shell-player.c
+===
+--- rhythmbox-2.97.orig/shell/rb-shell-player.c 2012-06-03 10:03:15.0 +0200
rhythmbox-2.97/shell/rb-shell-player.c 2013-07-21 13:12:53.588599603 +0200
+@@ -2378,6 +2378,10 @@
+ rb_debug (playing source is already NULL);
+ } else if (rb_source_can_pause (player-priv-source)) {
+ rb_debug (pausing mm player);
++ if (player-priv-parser_cancellable != NULL) {
++g_object_unref (player-priv-parser_cancellable);
++player-priv-parser_cancellable = NULL;
++ }
+ rb_player_pause (player-priv-mmplayer);
+ songs = rb_source_get_entry_view (player-priv-current_playing_source);
+ if (songs)
signature.asc
Description: This is a digitally signed message part
Bug#717445: pu: package ndiswrapper/1.57-1+deb7u1
On Sun, Jul 21, 2013 at 12:26:00AM +0200, Andreas Beckmann wrote:
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu
Hi,
there are two bugs affecting ndiswrapper-dkms that should be fixed in
wheezy:
* the module fails to build for a kernel that is not running (#693638)
* dkms throws up during kernel upgrades (#690747)
The second does not make sense. It would only add support for 3.4-3.7,
as ndiswrapper 1.57 does not compile against 3.8. The only supported
of those is 3.4. Backports is already at 3.9, so it seems unlikely
that someone wants to run a 3.4 kernel with ndiswrapper. It works
with 3.2 AFAICT, and that's the reason I did not workaroud this
bug in stable.
For supporting kernels newer than 3.2, the best way seems to be
a backport of 1.58-1 (or -2, once I added a patch for 3.10
kernels).
But it might make sense to include the patch:
* Patch userland for 3.X kernels
While there is no bug report for that, it fixes the ndiswrapper
tool to use modprobe.d and modprobe.conf on 3.X kernels, instead of
modutils/ and modules.conf.
The changes are cherry-picked from 1.58-1 and adjusted for 1.57.
I can do a NMU, but I'd prefer a maintainer upload fixing this.
@jak (Cc:ed): Shall I push my wheezy branch to the git repo?
In general, I prefer git patches against tag/1.57-1 over branches, so I can
review the individual commits. In this case, I'd like some further changes
as mentioned above, so I came up with the attached patch (committed in a
*local* branch).
Please comment.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
diff --git a/debian/changelog b/debian/changelog
index 5654ab5..acdab74 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ndiswrapper (1.57-1+deb7u1) stable; urgency=low
+
+ * Use $KERNELRELEASE as target kernel version (Closes: #693638)
+ * Patch userland for 3.X kernels
+
+ -- Julian Andres Klode j...@debian.org Sun, 21 Jul 2013 14:42:49 +0200
+
ndiswrapper (1.57-1) unstable; urgency=low
* Imported Upstream version 1.57
diff --git a/debian/patches/Add-support-for-3.x-kernel-versions.patch b/debian/patches/Add-support-for-3.x-kernel-versions.patch
new file mode 100644
index 000..1fea628
--- /dev/null
+++ b/debian/patches/Add-support-for-3.x-kernel-versions.patch
@@ -0,0 +1,28 @@
+From 71ec9e8a80b74652d660232b560bbe1dfa7915ba Mon Sep 17 00:00:00 2001
+From: Tim Gardner tim.gard...@canonical.com
+Date: Mon, 13 Feb 2012 14:19:58 -0700
+Subject: [PATCH] Add support for 3.x kernel versions
+
+As suggested by Kano on Freenode #ubuntu-kernel
+
+Signed-off-by: Tim Gardner tim.gard...@canonical.com
+---
+ utils/ndiswrapper | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/utils/ndiswrapper b/utils/ndiswrapper
+index 4bb91f2..ba082a3 100755
+--- a/utils/ndiswrapper
b/utils/ndiswrapper
+@@ -55,7 +55,7 @@ if (@ARGV 1) {
+
+ my $modconf;
+ if (`uname -r` =~ /(\d+)\.(\d+)\.(\d+)/) {
+-if ($2 4) {
++if (($2 4) || ($1 2)) {
+ if (-d /etc/modprobe.d) {
+ $modconf = /etc/modprobe.d/ndiswrapper.conf;
+ } else {
+--
+1.8.3.2
+
diff --git a/debian/patches/ndiswrapper-use-KERNELRELEASE.patch b/debian/patches/ndiswrapper-use-KERNELRELEASE.patch
new file mode 100644
index 000..f1cb786
--- /dev/null
+++ b/debian/patches/ndiswrapper-use-KERNELRELEASE.patch
@@ -0,0 +1,22 @@
+From: Ben Hutchings b...@decadent.org.uk
+Subject: Use $KERNELRELEASE as target kernel version
+Bug-Debian: http://bugs.debian.org/693638
+
+We must not assume that the running kernel version is the target
+version! DKMS and later Kbuild set $KERNELRELEASE to be the target
+kernel version.
+
+--- a/driver/Makefile
b/driver/Makefile
+@@ -12,7 +12,11 @@ DISTFILES = \
+ # By default, we try to compile the modules for the currently running
+ # kernel. But it's the first approximation, as we will re-read the
+ # version from the kernel sources.
++ifeq (,$(KERNELRELEASE))
+ KVERS ?= $(shell uname -r)
++else
++KVERS ?= $(KERNELRELEASE)
++endif
+
+ # KBUILD is the path to the Linux kernel build tree. It is usually the
+ # same as the kernel source tree, except when the kernel was compiled in
diff --git a/debian/patches/series b/debian/patches/series
index 2335794..99ec0d6 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,3 @@
ndiswrapper-harden.patch
+ndiswrapper-use-KERNELRELEASE.patch
+Add-support-for-3.x-kernel-versions.patch
pgp6UkJo1Y96_.pgp
Description: PGP signature
Bug#707018: Status of KDE 4.10 transition
On Sun, 2013-07-21 at 14:10 +0200, Pino Toscano wrote: That said, we are tackling few issues/regressions (mostly in the new pim stack), so could it be possible to hold the kde4libs migration with a block for now? (It should avoid all the rest to migrate too.) Block hint for kde4libs added. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374411265.5881.8.ca...@jacala.jungle.funky-badger.org
Bug#717489: marked as done (RM: xfm/1.5.4-3)
Your message dated Sun, 21 Jul 2013 13:55:52 +0100 with message-id 1374411352.5881.9.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#717489: RM: xfm/1.5.4-3 has caused the Debian Bug report #717489, regarding RM: xfm/1.5.4-3 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.) -- 717489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Please remove xfm from testing. I plan to drop it (RFA #717486 filed in the unlikely case anyone wants to take it over instead) and have filed #717487 to stop it from migrating back to testing. (I currently plan to request removal from unstable once jessie released (preferable without xfm)). Bernhard R. Link ---End Message--- ---BeginMessage--- Control: tags -1 + jessie On Sun, 2013-07-21 at 13:51 +0200, Bernhard R. Link wrote: Please remove xfm from testing. I plan to drop it (RFA #717486 filed in the unlikely case anyone wants to take it over instead) and have filed #717487 to stop it from migrating back to testing. (I currently plan to request removal from unstable once jessie released (preferable without xfm)). Removal hint added. Regards, Adam---End Message---
Re: Bug #681374 cherry picked upstream patch
On Sun, 2013-07-21 at 14:31 +0200, Marcel, Meißner wrote: with the patch from the upstream commit it is possible to fix this Bug. I've attached a debdiff of the package with the patch applied. I hope you can make use of this and possibly add it to proposed updates. Thanks for the patch. However, the release team don't upload patches ourselves for fixes in stable; that step is performed by the maintainers or others interested in fixing the bug, after discussion. In any case, this bug would need to be fixed in unstable before we could look at considering it for a stable update; according to the version information on #681374, the package in unstable is still affected. As an additional note: +rhythmbox (2.97-2.2) UNRELEASED; urgency=normal normal is not a valid urgency value. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374411792.5881.13.ca...@jacala.jungle.funky-badger.org
Bug#717426: marked as done (nmu: ben_0.6.4)
Your message dated Sun, 21 Jul 2013 14:08:46 +0100 with message-id 1374412126.5881.16.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#717426: nmu: ben_0.6.4 has caused the Debian Bug report #717426, regarding nmu: ben_0.6.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 717426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu ben_0.6.4 . ALL . -m Rebuild against updated libtyxml-ocaml and libpcre-ocaml. libben-ocaml depends on the no longer available libpcre-ocaml-xu8a5 libtyxml-ocaml-esbp7 so rebuild to pick up the new ones. Andreas ---End Message--- ---BeginMessage--- On Sat, 2013-07-20 at 21:30 +0200, Andreas Beckmann wrote: nmu ben_0.6.4 . ALL . -m Rebuild against updated libtyxml-ocaml and libpcre-ocaml. That's missing the . experimental. libben-ocaml depends on the no longer available libpcre-ocaml-xu8a5 libtyxml-ocaml-esbp7 so rebuild to pick up the new ones. Scheduled. Regards, Adam---End Message---
Bug#717493: pu: package sympa/6.1.11~dfsg-5.1~deb7u1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu
Sympa fails to install if the ca-certificates trigger has never been
run, yet. #717435
One solution is to add a Pre-Depends: ca-certificates to sympa
(suggested patch attached).
The other solution would be to fix this in ca-certificates and force a
trigger run during postinst (not sure if that is really feasible due to
the interaction needed with ca-certificates-java). Fixing this in
ca-certificates would prevent similar bugs to happen in other packages,
although I haven't seen any more in my piuparts tests.
Andreas
diff -Nru sympa-6.1.11~dfsg/debian/changelog sympa-6.1.11~dfsg/debian/changelog
--- sympa-6.1.11~dfsg/debian/changelog 2012-11-30 20:01:18.0 +0100
+++ sympa-6.1.11~dfsg/debian/changelog 2013-07-21 14:41:49.0 +0200
@@ -1,3 +1,17 @@
+sympa (6.1.11~dfsg-5.1~deb7u1) wheezy; urgency=low
+
+ * Non-maintainer upload.
+ * Rebuild for wheezy.
+
+ -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 14:41:08 +0200
+
+sympa (6.1.11~dfsg-5.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add Pre-Depends: ca-certificates. (Closes: #717435)
+
+ -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 14:37:04 +0200
+
sympa (6.1.11~dfsg-5) unstable; urgency=low
* Fix SQLite patch to avoid crash during installation from scratch and
diff -Nru sympa-6.1.11~dfsg/debian/control sympa-6.1.11~dfsg/debian/control
--- sympa-6.1.11~dfsg/debian/control 2012-05-21 14:23:32.0 +0200
+++ sympa-6.1.11~dfsg/debian/control 2013-07-21 13:59:24.0 +0200
@@ -36,7 +36,7 @@
Package: sympa
Architecture: any
-Pre-Depends: dpkg (= 1.15.7.2~)
+Pre-Depends: dpkg (= 1.15.7.2~), ca-certificates
Depends: ${perl:Depends}, ${shlibs:Depends}, ${misc:Depends}, ${cdbs:Depends}
Replaces: wwsympa
Provides: wwsympa
Bug#717432: marked as done (nmu: libuuid-perl_0.02-5+exp1)
Your message dated Sun, 21 Jul 2013 14:06:18 +0100 with message-id 1374411978.5881.14.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#717432: nmu: libuuid-perl_0.02-5+exp1 has caused the Debian Bug report #717432, regarding nmu: libuuid-perl_0.02-5+exp1 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.) -- 717432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libuuid-perl_0.02-5+exp1 . ALL . experimental . -m Rebuild against perl 5.18 dw libuuid-perl_0.02-5+exp1 . ALL . experimental . -m perl (= 5.18) perlapi-5.16.2 does no longer exist on most architectures ... Andreas ---End Message--- ---BeginMessage--- On Sat, 2013-07-20 at 22:09 +0200, Andreas Beckmann wrote: nmu libuuid-perl_0.02-5+exp1 . ALL . experimental . -m Rebuild against perl 5.18 dw libuuid-perl_0.02-5+exp1 . ALL . experimental . -m perl (= 5.18) perlapi-5.16.2 does no longer exist on most architectures ... Scheduled. Regards, Adam---End Message---
Bug#717425: marked as done (nmu: avogadro_1.1.0-4)
Your message dated Sun, 21 Jul 2013 14:09:29 +0100 with message-id 1374412169.5881.17.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#717425: nmu: avogadro_1.1.0-4 has caused the Debian Bug report #717425, regarding nmu: avogadro_1.1.0-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 717425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu avogadro_1.1.0-4 . ALL . experimental . -m Rebuild for new sip4 ABI. python-avogadro/experimental depends o the no longer available sip-api-9.2, so rebuild to pick up sip-api-10.0 instead. Andreas ---End Message--- ---BeginMessage--- On Sat, 2013-07-20 at 21:21 +0200, Andreas Beckmann wrote: nmu avogadro_1.1.0-4 . ALL . experimental . -m Rebuild for new sip4 ABI. python-avogadro/experimental depends o the no longer available sip-api-9.2, so rebuild to pick up sip-api-10.0 instead. Scheduled. Regards, Adam---End Message---
Bug#717421: marked as done (nmu: libxslt_1.1.28-1)
Your message dated Sun, 21 Jul 2013 14:10:12 +0100 with message-id 1374412212.5881.18.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#717421: nmu: libxslt_1.1.28-1 has caused the Debian Bug report #717421, regarding nmu: libxslt_1.1.28-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.) -- 717421: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu libxslt_1.1.28-1 . ALL . experimental . -m Rebuild to drop libpython2.6 dependency. Hi, python-libxslt1/experimental depends on the no longer available libpython2.6. A rebuild gets rid of this dependency. The version in experimental is also not affected by the FTBFS bug #713471. Andreas ---End Message--- ---BeginMessage--- On Sat, 2013-07-20 at 20:31 +0200, Andreas Beckmann wrote: python-libxslt1/experimental depends on the no longer available libpython2.6. A rebuild gets rid of this dependency. The version in experimental is also not affected by the FTBFS bug #713471. Scheduled. Regards, Adam---End Message---
Bug#717493: pu: package sympa/6.1.11~dfsg-5.1~deb7u1
Control: tags -1 + wheezy moreinfo On Sun, 2013-07-21 at 15:07 +0200, Andreas Beckmann wrote: Sympa fails to install if the ca-certificates trigger has never been run, yet. #717435 One solution is to add a Pre-Depends: ca-certificates to sympa (suggested patch attached). The other solution would be to fix this in ca-certificates and force a trigger run during postinst (not sure if that is really feasible due to the interaction needed with ca-certificates-java). Fixing this in ca-certificates would prevent similar bugs to happen in other packages, although I haven't seen any more in my piuparts tests. Whichever solution was chosen, it looks like this bug is not fixed in unstable yet? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374412420.5881.20.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#717493: pu: package sympa/6.1.11~dfsg-5.1~deb7u1
Processing control commands: tags -1 + wheezy moreinfo Bug #717493 [release.debian.org] pu: package sympa/6.1.11~dfsg-5.1~deb7u1 Added tag(s) wheezy and moreinfo. -- 717493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b717493.137441242814301.transcr...@bugs.debian.org
Bug#717445: pu: package ndiswrapper/1.57-1+deb7u1
On 2013-07-21 14:47, Julian Andres Klode wrote: On Sun, Jul 21, 2013 at 12:26:00AM +0200, Andreas Beckmann wrote: * dkms throws up during kernel upgrades (#690747) The second does not make sense. It would only add support for 3.4-3.7, [...] It works with 3.2 AFAICT, and that's the reason I did not workaroud this bug in stable. Good. I was afraid it would explode on kernel updates in stable, too. In general, I prefer git patches against tag/1.57-1 over branches, so I can review the individual commits. In this case, I'd like some further changes as mentioned above, so I came up with the attached patch (committed in a *local* branch). That's fine. But since everything is already integrated in your patch, there is no probably no need to resend my individual commits. This pu request is yours now :-) Thanks. Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ebe010.7050...@debian.org
Bug#717436: pu: shutdown-at-night - avoid daily email from cron when enabled
On Sat, 2013-07-20 at 23:07 +0200, Petter Reinholdtsen wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please stop filing stable update requests as unblocks; they're not requests to move a package to testing. Here is a request to approve an upload of shutdown-at-night to wheezy, to fix a bug Debian Edu would like to have fixed in our Debian Edu Wheezy release. The same fix was uploaded as version 0.11 to unstable with this changelog entry: [...] This is the change I want to include: [...] Please let us know if this is OK before we upload, and tell us which version number to use for this upload. In general, we'd prefer to see a complete debdiff of the proposed package, including changelog stanza, rather than simply isolated patches. (reportbug would have prompted for that, along with setting the tags correctly.) However, if the diff is purely the addition of the patch, with a changelog entry similar to the unstable upload, then I guess you could go ahead; please use 0.10+deb7u1 (predictably) as the version number and wheezy as the changelog distribution. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374413193.5881.25.ca...@jacala.jungle.funky-badger.org
Bug#717493: pu: package sympa/6.1.11~dfsg-5.1~deb7u1
On 2013-07-21 15:13, Adam D. Barratt wrote: Whichever solution was chosen, it looks like this bug is not fixed in unstable yet? Yes, I wanted to write a sentence about this as well ... If the release team considers adding a pre-depends in stable as acceptable, I would first upload a NMU to sid (same patch, just omitting the wheezy changelog entry) and later on to wheezy. Instead of doing NMUs, maintainer uploads would be welcome of course! Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ebe1b5.7060...@debian.org
Bug#717436: pu: shutdown-at-night - avoid daily email from cron when enabled
[Adam D. Barratt]
Please stop filing stable update requests as unblocks; they're not
requests to move a package to testing.
Sorry, my mistake copying from the wrong bug. :)
Hope to do better if I have to do it again.
However, if the diff is purely the addition of the patch, with a
changelog entry similar to the unstable upload, then I guess you
could go ahead; please use 0.10+deb7u1 (predictably) as the version
number and wheezy as the changelog distribution.
Thank you. I have uploaded it. This is the complete debdiff.
diff -Nru shutdown-at-night-0.10/debian/changelog
shutdown-at-night-0.10+deb7u1/debian/changelog
--- shutdown-at-night-0.10/debian/changelog 2012-02-13 23:42:49.0
+0100
+++ shutdown-at-night-0.10+deb7u1/debian/changelog 2013-07-21
15:37:21.0 +0200
@@ -1,3 +1,10 @@
+shutdown-at-night (0.10+deb7u1) wheezy; urgency=low
+
+ * Quiet down cron job to wake up client to not complain when fping
+notice they are unavailable.
+
+ -- Petter Reinholdtsen p...@debian.org Sun, 21 Jul 2013 15:36:19 +0200
+
shutdown-at-night (0.10) unstable; urgency=low
* Do not shut down if uptime is less then an hour. Based on patch and
diff -Nru shutdown-at-night-0.10/wakeupclients
shutdown-at-night-0.10+deb7u1/wakeupclients
--- shutdown-at-night-0.10/wakeupclients2008-06-13 10:55:04.0
+0200
+++ shutdown-at-night-0.10+deb7u1/wakeupclients 2013-07-21 15:39:21.0
+0200
@@ -63,7 +63,7 @@
sub get_alive_list {
my @addresses = @_;
-return split(/\s+/, `fping -a @addresses`);
+return split(/\s+/, `fping -a @addresses 2/dev/null`);
}
sub logmsg {
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130721134240.ga17...@ulrik.uio.no
Bug#717457: pu: package oss4/4.2-build2006-2+deb7u2
Andreas Beckmann (2013-07-21): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hi, oss4-dkms and oss4-source have insufficient dependencies and fail to build kernel modules in a minimal system. Since the module fails to build for the current kernel in sid, I cannot verify whether some of these dpendencies are missing is sid, too. Sigh @ out-of-tree kernel modules… + * Non-maintainer upload. + * oss4-dkms: Add missing Depends: dpkg-dev, libc6-dev. (Closes: #687086) At least ia64 has a non-libc6-dev package, libc6.1-dev instead. I guess the Provides is sufficient at the moment, but if that's turned into a versioned dependency at some point, that won't fly. + * oss4-source: Add missing Depends: gcc, libc6-dev. I'm not sure whether it might make sense to just pull build-essential, which would do the job on all architectures, without risking getting unsatisfiable dependencies. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130721142155.ga30...@mraw.org
Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hi, the change I suggested for sysvinit (#694252) and got applied in sysvinit/2.88dsf-41+deb7u1 does not fix the bootchart upgrade path lenny-squeeze-wheezy, but instead renders bootchart uninstallable in stable (and sid as well): #717495. I'm attaching a suggested patch to fix this upgrade path along with the uninstallability. This will work by renaming /etc/init.d/bootchart to /etc/init.d/stop-bootchart. As a side effect, the buggy initscript will have been renamed to bootchart.dpkg-remove so that it is not considered by sysv-rc even if the new one is not yet installed. Or is there another possibility to force the new bootchart being configured before sysv-rc (without adding a Pre-Depends)? The fix has not been applied in sid, yet. If the release team considers this rename as a possible solution for wheezy, I'll first get this applied in sid. I can confirm that this patch fixes the lenny-squeeze-wheezy upgrade path if it gets applied to wheezy. The bootchart versioning is bumped in a way that requires no further changes to sysvinit to restore installability. Andreas diff -u bootchart-0.10~svn407/debian/control bootchart-0.10~svn407/debian/control --- bootchart-0.10~svn407/debian/control +++ bootchart-0.10~svn407/debian/control @@ -12,6 +12,7 @@ Package: bootchart Architecture: all +Pre-Depends: dpkg (= 1.15.7.2) Depends: psmisc, lsb-base (= 3.0-6) Recommends: bootchart-view, acct Description: Boot process performance analyser diff -u bootchart-0.10~svn407/debian/rules bootchart-0.10~svn407/debian/rules --- bootchart-0.10~svn407/debian/rules +++ bootchart-0.10~svn407/debian/rules @@ -50,6 +50,7 @@ dh_installexamples dh_installman dh_installinit --no-restart-on-upgrade --no-start \ + --init-script=stop-bootchart \ --update-rcd-params=start 99 1 2 3 4 5 . dh_link dh_compress diff -u bootchart-0.10~svn407/debian/changelog bootchart-0.10~svn407/debian/changelog --- bootchart-0.10~svn407/debian/changelog +++ bootchart-0.10~svn407/debian/changelog @@ -1,3 +1,29 @@ +bootchart (0.10~svn407-4.1~deb7u1) wheezy; urgency=low + + * Build for wheezy. + + -- Andreas Beckmann a...@debian.org Sat, 20 Jul 2013 20:21:17 +0200 + +bootchart (0.10~svn407-4.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix the upgrade path lenny (bootchart 0.10~svn407-3) = squeeze (bootchart +0.10~svn407-3 from lenny because bootchart was not included in squeeze) = +wheezy. The initscript from 0.10~svn407-3 prevents migration to dependency +based boot sequencing causing a sysv-rc upgrade failure. Since it is not +possible to express a dependency/conflict like either bootchart is purged +or fully configured, it is possible for an updated bootchart being +unpacked but unconfigured, leaving the broken initscript still in place at +the time sysv-rc tries to switch to dependency-based sequencing. +Therefore rename the initscript from bootchart to stop-bootchart which +will move the buggy script out of the way early enough to make sysv-rc +succeed. Use Pre-Depends: dpkg (= 1.15.7.2) and dpkg-maintscript-helper +for the renaming. (Closes: #717495) + * Bump Debian revision to -4.1 to restore installability after recent +initscripts having Breaks: bootchart ( 0.10~svn407-4). + + -- Andreas Beckmann a...@debian.org Sat, 20 Jul 2013 20:21:12 +0200 + bootchart (0.10~svn407-3.3) unstable; urgency=low * Non-maintainer upload. diff -u bootchart-0.10~svn407/debian/bootchart.init bootchart-0.10~svn407/debian/bootchart.init --- bootchart-0.10~svn407/debian/bootchart.init +++ bootchart-0.10~svn407/debian/bootchart.init @@ -17,7 +17,7 @@ PATH=/sbin:/usr/sbin:/bin:/usr/bin NAME=bootchartd DAEMON=/sbin/$NAME -SCRIPTNAME=/etc/init.d/bootchart +SCRIPTNAME=/etc/init.d/stop-bootchart # Exit if the package is not installed [ -x $DAEMON ] || exit 0 diff -u bootchart-0.10~svn407/debian/bootchart.postrm bootchart-0.10~svn407/debian/bootchart.postrm --- bootchart-0.10~svn407/debian/bootchart.postrm +++ bootchart-0.10~svn407/debian/bootchart.postrm @@ -5,6 +5,8 @@ set -e +dpkg-maintscript-helper mv_conffile /etc/init.d/bootchart /etc/init.d/stop-bootchart 0.10~svn407-4~ bootchart -- $@ + case $1 in purge) rm -f /var/log/bootchart.tgz only in patch2: unchanged: --- bootchart-0.10~svn407.orig/debian/bootchart.preinst +++ bootchart-0.10~svn407/debian/bootchart.preinst @@ -0,0 +1,6 @@ +#!/bin/sh +set -e + +dpkg-maintscript-helper mv_conffile /etc/init.d/bootchart /etc/init.d/stop-bootchart 0.10~svn407-4~ bootchart -- $@ + +#DEBHELPER# only in patch2: unchanged: --- bootchart-0.10~svn407.orig/debian/bootchart.postinst +++ bootchart-0.10~svn407/debian/bootchart.postinst @@ -0,0 +1,6 @@ +#!/bin/sh +set -e + +dpkg-maintscript-helper mv_conffile /etc/init.d/bootchart /etc/init.d/stop-bootchart 0.10~svn407-4~ bootchart -- $@ + +#DEBHELPER#
Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1
Andreas Beckmann (2013-07-21): the change I suggested for sysvinit (#694252) and got applied in sysvinit/2.88dsf-41+deb7u1 does not fix the bootchart upgrade path lenny-squeeze-wheezy, but instead renders bootchart uninstallable in stable (and sid as well): #717495. I'm attaching a suggested patch to fix this upgrade path along with the uninstallability. This will work by renaming /etc/init.d/bootchart to /etc/init.d/stop-bootchart. As a side effect, the buggy initscript will have been renamed to bootchart.dpkg-remove so that it is not considered by sysv-rc even if the new one is not yet installed. Or is there another possibility to force the new bootchart being configured before sysv-rc (without adding a Pre-Depends)? Needless to say, I'm not impressed by the amount of changes and the whole lot of possible side effects. The fix has not been applied in sid, yet. If the release team considers this rename as a possible solution for wheezy, I'll first get this applied in sid. I can confirm that this patch fixes the lenny-squeeze-wheezy upgrade path if it gets applied to wheezy. Please stop filing pu requests for bugs that aren't even fixed in unstable; that's not amusing and wasting everyone's time. KiBi. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130721153507.gb30...@mraw.org
Bug#708536: transition: python3-defaults (add python3.3 to supported python3)
Followup-For: Bug #708536 A few NMUs for python3 packages are needed in experimental: nmu pygame_1.9.2~pre~r3189-2 . ALL . experimental . -m Rebuild to add support for python3.3 nmu matplotlib_1.2.0-1 . ALL . experimental . -m Rebuild to add support for python3.3 nmu pyopenssl_0.13-3 . ALL . experimental . -m Rebuild to add support for python3.3 nmu python-psutil_0.7.0-1 . ALL . experimental . -m Rebuild to add support for python3.3 nmu python-pyaudio_0.2.7-1 . ALL . experimental . -m Rebuild to add support for python3.3 Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130721160421.32157.62877.report...@cake.ae.cs.uni-frankfurt.de
Processed: Re: Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1
Processing control commands: tags -1 + moreinfo wheezy Bug #717498 [release.debian.org] pu: package bootchart/0.10~svn407-4.1~deb7u1 Added tag(s) wheezy and moreinfo. -- 717498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b717498.13744231179511.transcr...@bugs.debian.org
Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1
Control: tags -1 + moreinfo wheezy On Sun, 2013-07-21 at 16:51 +0200, Andreas Beckmann wrote: the change I suggested for sysvinit (#694252) and got applied in sysvinit/2.88dsf-41+deb7u1 does not fix the bootchart upgrade path lenny-squeeze-wheezy, but instead renders bootchart uninstallable in stable (and sid as well): #717495. Hmmm, I'd rather assumed that was the point, given that the Breaks matches the only version of bootchart in the archive. Is keeping bootchart around still useful? The last upload of any kind was in 2009, with the last maintainer upload in early 2008. Going back through the history of the sysvinit bug, I have to admit to being rather confused. You state that 0.10~svn407-3.3 was the last existing and therefore broken version in lenny (and on snapshots.d.o). However, the lenny packages files (as on archive.d.o) indicates that lenny contained -3; the fix for #491391 in bootchart was included in -3.1. Please clarify... :-| Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374423106.5881.34.ca...@jacala.jungle.funky-badger.org
Bug#707018: Status of KDE 4.10 transition
On Sun, Jul 21, 2013 at 14:10:18 +0200, Pino Toscano wrote: That said, we are tackling few issues/regressions (mostly in the new pim stack), so could it be possible to hold the kde4libs migration with a block for now? (It should avoid all the rest to migrate too.) FWIW you could just keep a serious bug open against the sid version until you're ready for it to migrate. Cheers, Julien signature.asc Description: Digital signature
Bug#717493: pu: package sympa/6.1.11~dfsg-5.1~deb7u1
On Sun, Jul 21, 2013 at 15:27:17 +0200, Andreas Beckmann wrote: On 2013-07-21 15:13, Adam D. Barratt wrote: Whichever solution was chosen, it looks like this bug is not fixed in unstable yet? Yes, I wanted to write a sentence about this as well ... If the release team considers adding a pre-depends in stable as acceptable, I would first upload a NMU to sid (same patch, just omitting the wheezy changelog entry) and later on to wheezy. Instead of doing NMUs, maintainer uploads would be welcome of course! I think adding a pre-depends in stable would be worse than this bug. Cheers, Julien signature.asc Description: Digital signature
Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1
On 2013-07-21 18:11, Adam D. Barratt wrote: On Sun, 2013-07-21 at 16:51 +0200, Andreas Beckmann wrote: the change I suggested for sysvinit (#694252) and got applied in sysvinit/2.88dsf-41+deb7u1 does not fix the bootchart upgrade path lenny-squeeze-wheezy, but instead renders bootchart uninstallable in stable (and sid as well): #717495. Hmmm, I'd rather assumed that was the point, given that the Breaks matches the only version of bootchart in the archive. but it makes a package in stable uninstallable without planning to remove it from stable ... and that does not fix the upgrade issue in sysv-rc Is keeping bootchart around still useful? The last upload of any kind was in 2009, with the last maintainer upload in early 2008. If the package were removed entirely (or at least version -3.3+1 would be forced to rename the initscript), we could have sysv-rc use dpkg-maintscript-helper rm_conffile to get rid of that script ... that would even cover the case where bootchart lenny was installed, removed, the initscript remained and the system would be upgraded to squeeze and wheezy later on. Going back through the history of the sysvinit bug, I have to admit to being rather confused. You state that 0.10~svn407-3.3 was the last existing and therefore broken version in lenny (and on snapshots.d.o). However, the lenny packages files (as on archive.d.o) indicates that lenny contained -3; the fix for #491391 in bootchart was included in -3.1. Please clarify... :-| I think I have mixed up the versions -3 vs. -3.3 at some point, therefore suggesting to add the wrong Breaks against -4, after seeing that a Breaks against -3 was not sufficient to fix that upgrade path. That Breaks actually worked, but it was not sufficient to ensure -3.3 gets configured before sysv-rc, leaving the bad initscript still around. At the time I initially filed the bug I didn't have piuparts ready to easily do upgrade tests with the new --testdebs-repo option, otherwise I might have tried the Breaks approach myself (and seen that it does not work as planned). Entirely new approach to fix this much less intrusively: bootchart.preinst: on upgrade from -4 sed -i 's/rmnologin/$all/' /etc/init.d/bootchart # makes the initscript identical to the new shipped one, so no conffile prompts (unless there were other user modifications) bump version to -4.1 / -4.1~deb7u1 to satisfy initscripts Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ec1243.7000...@debian.org
Bug#712204: marked as done (transition: libitpp)
Your message dated Sun, 21 Jul 2013 18:56:15 +0200 with message-id 20130721165615.gn28...@betterave.cristau.org and subject line Re: Bug#712204: transition: libitpp has caused the Debian Bug report #712204, regarding transition: libitpp 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.) -- 712204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, I have inadvertently started a transition with the latest upload of libitpp to unstable. I'd like to apologise for this. I had not noticed that a couple of packages have started using libitpp as a dependency. To make things easier, I have verified that the two reverse dependencies, viz. aghermann and mia, will build. There are issues, however: 1. aghermann needs the pkg-config file for IT++ to be installed. Unfortunately, a change in the upstream build system no longer installs this file. A bug report has been filed upstream, and I can upload a patched version to unstable to fix this issue. 2. mia has an RC bug (#705385) that is blocked by (#705495). A fix for the latter seems to be available, though, so a resolution can be expected shortly. Please let me know the best way ahead. Thanks, and sorry for the trouble. Kumar Ben file: title = libitpp; is_affected = .depends ~ libitpp7 | .depends ~ libitpp8; is_good = .depends ~ libitpp8; is_bad = .depends ~ libitpp7; -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Kumar Appaiah ---End Message--- ---BeginMessage--- On Fri, Jun 14, 2013 at 01:11:31 -0400, Kumar Appaiah wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear Release Team, I have inadvertently started a transition with the latest upload of libitpp to unstable. I'd like to apologise for this. I had not noticed that a couple of packages have started using libitpp as a dependency. libitpp7 is no longer in testing, closing. Cheers, Julien signature.asc Description: Digital signature ---End Message---
Bug#717498: pu: package bootchart/0.10~svn407-4.1~deb7u1 - PATCH v2
Followup-For: Bug #717498 New patch, much less intrusive, use preinst to fix up the old initscript. Andreas diff -u bootchart-0.10~svn407/debian/changelog bootchart-0.10~svn407/debian/changelog --- bootchart-0.10~svn407/debian/changelog +++ bootchart-0.10~svn407/debian/changelog @@ -1,3 +1,25 @@ +bootchart (0.10~svn407-4.1~deb7u1) wheezy; urgency=low + + * Rebuild for wheezy. + + -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 19:17:44 +0200 + +bootchart (0.10~svn407-4.1) unstable; urgency=low + + * Non-maintainer upload. + * Fix the upgrade path lenny (bootchart 0.10~svn407-3) = squeeze (bootchart +0.10~svn407-3 from lenny because bootchart was not included in squeeze) = +wheezy. The initscript from 0.10~svn407-3 prevents migration to dependency +based boot sequencing causing a sysv-rc upgrade failure. +Add bootchart.preinst to replace the problematic rmnologin use in the +ancient /etc/init.d/bootchart because it is impossible to ensure the new +bootchart is already configured (which would replace the old initscript) +at the time sysv-rc gets configured. (Closes: #717495) + * Bump Debian revision to -4.1 to restore installability after recent +initscripts having Breaks: bootchart ( 0.10~svn407-4). + + -- Andreas Beckmann a...@debian.org Sun, 21 Jul 2013 19:16:49 +0200 + bootchart (0.10~svn407-3.3) unstable; urgency=low * Non-maintainer upload. only in patch2: unchanged: --- bootchart-0.10~svn407.orig/debian/bootchart.preinst +++ bootchart-0.10~svn407/debian/bootchart.preinst @@ -0,0 +1,13 @@ +#!/bin/sh +set -e + +if [ $1 = install ] || [ $1 = upgrade ]; then + if dpkg --compare-versions $2 lt-nl 0.10~svn407-4 ; then + if [ -f /etc/init.d/bootchart ] grep -q rmnologin /etc/init.d/bootchart ; then + echo Fixing up old /etc/init.d/bootchart... + sed -i 's/rmnologin/$all/' /etc/init.d/bootchart + fi + fi +fi + +#DEBHELPER#
Processed: user release.debian....@packages.debian.org, usertagging 717420, tagging 717420 ...
Processing commands for cont...@bugs.debian.org: user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was jcris...@debian.org). usertags 717420 pu There were no usertags set. Usertags are now: pu. tags 717420 + wheezy Bug #717420 [release.debian.org] update reSIProcate in stable from 1.8.5 - 1.8.12 Added tag(s) wheezy. severity 717420 wishlist Bug #717420 [release.debian.org] update reSIProcate in stable from 1.8.5 - 1.8.12 Severity set to 'wishlist' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 717420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137442918711316.transcr...@bugs.debian.org
Bug#717420: update reSIProcate in stable from 1.8.5 - 1.8.12
On Sat, 2013-07-20 at 20:26 +0200, Daniel Pocock wrote: Package: release.debian.org Severity: important Nope. Bugs in packages may have all kinds of severities, requests to update packages in stable are normal at best. (It would also be helpful if you used reportbug or otherwise normalised the usertags and titles when making such requests.) For the record, I had to dig the mail to which I'm replying out of a BTS mbox; it never reached the debian-release list, presumably due to the size of the diff. We've found that versions of reSIProcate 1.8.11-4 are not reliable on non-Intel platforms. Does anyone actually use the package on such architectures? In particular, essential code such as the MD5 implementation was not being compiled the right way for big endian systems. The code may appear to compile and run but as soon as a user tries to engage in a DIGEST authentication they will find that it fails to operate correctly. [...] A long list of other bug fixes is also included, several of them eliminate bugs that can cause a crash The cumulative effect of all bug fixes on the 1.8.x release branch brings a significant improvement in quality and convenience for end users. The _filtered_ diffstat is 189 files changed, 5819 insertions(+), 2235 deletions(-) and adds two new packages. We'd need a lot of convincing that the latter is worth doing, rather than just proving updates via backports (fwiw, I'm only aware of one occasion where a new package was introduced to a release once it was stable, and that was openssh-blacklist via security.d.o, which is a somewhat different situation). Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1374430544.5881.42.ca...@jacala.jungle.funky-badger.org
Re: DSA concerns for jessie architectures
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/22/2013 07:26 PM, Martin Zobel-Helas wrote: * sparc: no working nflog (mild concern); no stable kernels in stable (compiling clisp for instance crashes the kernel reliably on smetana). We need to run sparc with oldstable kernels to provide stable machines. That's not an option for long. I think all machines except stadler and sompek are US IIIi machines. The problem with US IIIi is, that sun never published the cpu specs - they would have done it if somebody would have paid for the lawyers to look trough them before publishing. US IIi support was implemented by a student working at SUN under NDA and US IV and later was published. So I think if dropping (official) support for US IIIi CPUs would keep the port alive, we should do that. Running Debian on the more recent machines makes more sense anyway imho. The older ones are nice, but they consume a lt of power. - -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJR7DExAAoJEOs2Fxpv+UNffpcP/2Rs12KtUr1R8Fj/SUFsGTGi Qq4IyIsq6T9+0be/Q2NT+8vKhqy9eAfLIGPYfEfMP/gQUXHxqURF7452FCum5pCe PPbhpGMFL67rX9I9tdNbYGEcD6KnHksHc64PaV4FkCd5W/dvQzaVHxfP5I7TjFL2 JQVrfqYTi546kPN7kqo6YhNNC+jFRBJOxB+2RhdEddg12xU9/08/YIy865qJqXSP 0X+xBfiGu040AKUC+Ml4ZjFGKDnCOKhuuAKDYnyZLjLSFjTkE00WowKDS8JmJRLC ls89Xha2K4Sk01io+f4iermCjRsHD/GvS4mNIG5HsEQYHROdWoCFNRl4hAdGI0zZ CvFnxaJLwQ+cd0dsoFO/OkuRLTYOrjHKTniOjrWcgaOl0L6C6K4Jhyh+jpl2GmO/ sUs/K3jtUBos5Q1ojetmm/rAXjEFe3giOokosUP1DOB8fWUnYqRDYf5ODOeEucot nzl6lfvp+g2nQVQAAOqpSqxCYYhue23Mg8ZYfW1L/I8mNIvClrcSVfHAAP3URQeY eDGoyPNX6AIYiFX8J121ynfMa/TujGURfoPcQWWGFb3NyJ4/RM/FrTAAseldcIlW 2nfpRUX118LEYLQ6Jj4JQn7Ci6lL+SUgI2HfSRu/5a1aoBrEVhVF5ItUbMU6B0Vx YTnzPB7WteSULAbu90Iz =H+fH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51ec3137.1020...@bzed.de
Bug#706973: transition: audit
Hi, Is anything blocking this transition? The tracker shows no conflict. libvirt is currently FTBFS but the version in testing has no dependency against libaudit. Tell me if I could help with something. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130721220431.3b888...@fornost.bigon.be
Bug#710143: marked as done (transition: libraw)
Your message dated Sun, 21 Jul 2013 23:20:10 +0100 with message-id 1374445210.5881.44.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#710143: transition: libraw has caused the Debian Bug report #710143, regarding transition: libraw 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.) -- 710143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Control: block -1 by 710133 710141 I'd like to request a slot for taking care of the libraw transition. The new upstream release (in experimental) has bumped soname. Reverse dependencies * entangle * freeimage * luminance-hdr * shotwell freeimage FTBFS (#710133), but upstream already has a patch to fix it. Also shotwell FTBFS (#710141), issue has been forwarded upstream. Ben file: title = libraw; is_affected = .build-depends ~ /libraw-dev/; is_good = .depends ~ libraw9; is_bad = .depends ~ libraw5; Cheers, Luca ---End Message--- ---BeginMessage--- On Thu, 2013-07-11 at 12:20 +0200, Julien Cristau wrote: On Thu, Jul 11, 2013 at 11:41:29 +0200, Luca Falavigna wrote: libraw 0.15.3-1 built everywhere, and I just uploaded fixed packages for shotwell and freeimage. Could you please schedule binNMUs for the other two packages? nmu entangle_0.5.1-1 . ALL . -m 'Rebuild against libraw9' nmu luminance-hdr_2.3.0-3 . ALL . -m 'Rebuild against libraw9' On their way. libraw5 is no longer in testing; closing. Regards, Adam---End Message---
Bug#710720: marked as done (transition: libechonest)
Your message dated Sun, 21 Jul 2013 23:19:08 +0100 with message-id 1374445148.5881.43.ca...@jacala.jungle.funky-badger.org and subject line Re: Bug#710720: transition: libechonest has caused the Debian Bug report #710720, regarding transition: libechonest 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.) -- 710720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hi! A new upstream release of libechonest is sitting in experimental and I would like to push it to unstable. The only reverse dependency I know of is clementine. I'm sure a binNMU will surely work in this case, as clementine in experimental was linked against this new version. Kinds regards, Lisandro. Ben file: title = libechonest; is_affected = .depends ~ libechonest1.2 | .depends ~ libechonest2.0; is_good = .depends ~ libechonest2.0; is_bad = .depends ~ libechonest1.2; -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.21+edid (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Wed, 2013-07-17 at 18:34 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: On Wednesday 17 July 2013 21:34:11 Adam D. Barratt wrote: [snip] In sid, yes (I've just asked for the old binary package to be decrufted). There's still a few days before it hits testing though. My bad, I didn't know that it's marked until it hits testing. It did now. :-) Therefore closing. Regards, Adam---End Message---
