[Bug 61310] Re: patch to close 33362 not applied to edgy release

2006-09-27 Thread Kai Kasurinen
** Bug 62700 has been marked a duplicate of this bug -- patch to close 33362 not applied to edgy release https://launchpad.net/bugs/61310 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 61310] Re: patch to close 33362 not applied to edgy release

2006-09-20 Thread William Grant
** Changed in: resolvconf (Ubuntu) Status: Fix Committed => Fix Released -- patch to close 33362 not applied to edgy release https://launchpad.net/bugs/61310 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 61310] Re: patch to close 33362 not applied to edgy release

2006-09-20 Thread Daniel T Chen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Sep 2006 03:12:20 -0400 Source: resolvconf Binary: resolvconf Architecture: source Version: 1.36ubuntu1 Distribution: edgy Urgency: low Maintainer: resolvconf maintainers <[EMAIL PROTECTED]> Changed-By: Daniel T Chen <[EMAIL P

[Bug 61310] Re: patch to close 33362 not applied to edgy release

2006-09-19 Thread William Grant
Here I've attached a debdiff for a new version which readds those changes. I am wondering why the sync of 1.36 was performed in the first place, as the package had Ubuntu changes. ** Changed in: resolvconf (Ubuntu) Assignee: (unassigned) => William Grant ** Attachment added: "debdiff to fix