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

Bug#680512: marked as done (unblock: isdnutils/1:3.25+dfsg1-1)

Your message dated Mon, 09 Jul 2012 23:40:34 +0200
with message-id <4FFB4FD2.9030709@dogguy.org>
and subject line Re: Bug#680512: unblock: isdnutils/1:3.25+dfsg1-1
has caused the Debian Bug report #680512,
regarding unblock: isdnutils/1:3.25+dfsg1-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 owner@bugs.debian.org
immediately.)


-- 
680512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680512
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: freeze-exception

Dear Release Team,

I'm requesting a freeze exception for 3.25+dfsg1-1 of isdnutils

Quoting the RC-bug 680503 I just filed:

'In the past few months I had been working with upstream to drop
dfsg-nonfree bits from their tarball and make my life easier.
"git diff $dfsgbranch $upstreambranch|lsdiff" recently led me
to believe that the difference between upstream and what we were
shipping as the dfsg-tarball had essentially dwindled down to
insignificant bits such as dotfiles, etc, leaving upstream
dfsg-free.  This assumption turns out to be mistaken and we need
to ship 3.25 as dfsg, too, just like previous versions.'

I'm sorry about the inconvenience my neglect has caused.  I've
already prepared a dfsg-tarball for upload where I drop the same
files as we did in Debian up to upstream 3.22.

A regression in the maintainer scripts was reported today in bug
#679651 that I'd like to fix alongside.  Please see the attached
simple patch.  I'm reintroducing a cd-command to make sure the
following commands are executed in the correct context. When I
dropped it I had considered it as part of the dropped code.

Please let me know if you have any objections to shipping
the patch alongside the dfsg-fix.

Regards

Rolf

>From 1bdd1ae0c2a8c210d0b1bbc5834109eb816f48a8 Mon Sep 17 00:00:00 2001
From: Rolf Leggewie <foss@rolf.leggewie.biz>
Date: Fri, 6 Jul 2012 14:53:31 +0800
Subject: [PATCH 1/2] debian/init.d.functions: reintroduce cd-command lost in 985a74cd63. Closes: #679651

The "cd"-command wasn't actually meant to be removed
---
 debian/init.d.functions |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/debian/init.d.functions b/debian/init.d.functions
index 0078d9c..1979cab 100644
--- a/debian/init.d.functions
+++ b/debian/init.d.functions
@@ -236,6 +236,7 @@ start_devices() {
     check_isdncards # side-effect: sets $isdncards
     what=' interfaces'
     olddir=`pwd`
+    cd /etc/isdn
     listdevices
     if [ -z "$DEVS" -a ! -f /etc/isdn/noconfig ]; then
         log_success_msg "  There is apparently no configuration created yet."
-- 
1.7.0.4

--- End Message ---
--- Begin Message --- 
On 07/09/2012 07:11 PM, Rolf Leggewie wrote:
> Hello,
> 
> I've had a fair bit of trouble to get the VERY brittle net
> connection here to successfully complete the upload of the sizeable
> isdnutils package.  I believe it's complete now but it took me a
> while.
> 
> I did not provide a debdiff here, I am not sure it makes much sense.
>  You've already seen the patch and ACK'd it.  On top of that is the 
> changelog patch which should be unspectacular.  The sizeable rest
> would have been a bunch of dropped files.  Instead, I now made the
> upload to unstable.  Feel free to grab it from there and inspect it.
> Thank you.
> 

Unblocked (and set required days for migration to 15... due to the diff
size).

Regards,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/

--- End Message ---
Reply to: