[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#780038: marked as done (unblock: ulogd2/2.0.4-2)

Your message dated Sun, 08 Mar 2015 17:50:15 +0100
with message-id <54FC7DC7.40401@thykier.net>
and subject line Re: Bug#780038: unblock: ulogd2/2.0.4-2
has caused the Debian Bug report #780038,
regarding unblock: ulogd2/2.0.4-2
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 owner@bugs.debian.org
immediately.)


-- 
780038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780038
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package ulogd2.

The updated package fixes an RC bug (#779865). This is done by adding
some maintscript entries to remove more obsolete conffiles from the
previous ulogd package.

Here is the full debdiff from 2.0.4-1 (version in testing) to 2.0.4-2
(version freshly uploaded to sid):

diff -Nru ulogd2-2.0.4/debian/changelog ulogd2-2.0.4/debian/changelog
--- ulogd2-2.0.4/debian/changelog	2014-04-13 14:49:13.000000000 +0100
+++ ulogd2-2.0.4/debian/changelog	2015-03-08 15:22:46.000000000 +0000
@@ -1,3 +1,15 @@
+ulogd2 (2.0.4-2) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Fix removal of old ulogd initscript upon initial installation of ulogd2.
+  * Remove more obsolete conffiles.
+
+  [ Chris Boot ]
+  * Apply patches from Andreas Beckmann correct the transition from ulogd to
+    ulogd2. (Closes: #779865, LP: #1354720)
+
+ -- Chris Boot <debian@bootc.net>  Sun, 08 Mar 2015 15:22:44 +0000
+
 ulogd2 (2.0.4-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru ulogd2-2.0.4/debian/ulogd2.maintscript ulogd2-2.0.4/debian/ulogd2.maintscript
--- ulogd2-2.0.4/debian/ulogd2.maintscript	2014-04-13 11:42:32.000000000 +0100
+++ ulogd2-2.0.4/debian/ulogd2.maintscript	2015-03-08 15:22:10.000000000 +0000
@@ -1,4 +1,6 @@
 
 # Remove the old ulogd 1.x init script, as it can cause problems/confusion
-rm_conffile /etc/init.d/ulogd 2.0.2-4~ ulogd
+# Provide a fall-back old-version ("0") as a hack to ensure this is performed
+# by dpkg-maintscript-helper on the initial install of ulogd2, too.
+rm_conffile /etc/init.d/ulogd 2.0.4-2~ ulogd -- "$@" 0
 
diff -Nru ulogd2-2.0.4/debian/ulogd.maintscript ulogd2-2.0.4/debian/ulogd.maintscript
--- ulogd2-2.0.4/debian/ulogd.maintscript	1970-01-01 01:00:00.000000000 +0100
+++ ulogd2-2.0.4/debian/ulogd.maintscript	2015-03-08 15:22:10.000000000 +0000
@@ -0,0 +1,2 @@
+rm_conffile /etc/init.d/ulogd 2.0.4-2~
+rm_conffile /etc/logrotate.d/ulogd 2.0.4-2~


unblock ulogd2/2.0.4-2

Thanks for your consideration.

Regards,
Chris

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On 2015-03-08 17:04, Chris Boot wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package ulogd2.
> 
> The updated package fixes an RC bug (#779865). This is done by adding
> some maintscript entries to remove more obsolete conffiles from the
> previous ulogd package.
> 
> Here is the full debdiff from 2.0.4-1 (version in testing) to 2.0.4-2
> (version freshly uploaded to sid):
> 
> [...]
> 
> 
> unblock ulogd2/2.0.4-2
> 
> Thanks for your consideration.
> 
> Regards,
> Chris
> 
> [...]

Unblocked, thanks.

~Niels

--- End Message ---
Reply to: