Bug#776778: Please play nicely with resolvconf

2015-02-06 Thread Thomas Hood
On 5 February 2015 at 21:28, Thomas Hood wrote: > Second, it might be simpler just for resolvconf to detect that > dnssec-triggerd is running and, in that case, to override the > immutability attribute when installing the symlink at > /etc/resolv.conf. I have committed the change to resolvconf so

Bug#776778: Please play nicely with resolvconf

2015-02-05 Thread Thomas Hood
On 5 February 2015 at 16:35, Axel Beckert wrote: > Ondřej Surý wrote: >> There's already a unblock bug filled as well. Great! >> Then we need to come up with solution that doesn't break resolvconf when >> installing it after dnssec-trigger is already installed. > > Just an idea, but what about

Bug#776778: Please play nicely with resolvconf

2015-02-05 Thread Axel Beckert
Hi, Ondřej Surý wrote: > Then we need to come up with solution that doesn't break resolvconf when > installing it after dnssec-trigger is already installed. Just an idea, but what about resolvconf checking in its postinst if dnssec-triggerd is available and if so restarting it first? Then dnssec-

Bug#776778: Please play nicely with resolvconf

2015-02-05 Thread Ondřej Surý
On Thu, Feb 5, 2015, at 15:12, Axel Beckert wrote: > Hi Thomas, > > Thomas Hood wrote: > > >> > a) add Breaks: resolvconf > > >> > > >> That's ok-ish. It would be the short-hack temporary solution and > > >> likely suitable for Jessie. > > > > > > okay, this is fairly easy > > > > Please do this

Bug#776778: Please play nicely with resolvconf

2015-02-05 Thread Axel Beckert
Hi Thomas, Thomas Hood wrote: > >> > a) add Breaks: resolvconf > >> > >> That's ok-ish. It would be the short-hack temporary solution and > >> likely suitable for Jessie. > > > > okay, this is fairly easy > > Please do this quickly, closing #776776, and push to Jessie. He already closed that bug

Bug#776778: Please play nicely with resolvconf

2015-02-05 Thread Thomas Hood
On 4 February 2015 at 12:00, Ondřej Surý wrote: > On Wed, Feb 4, 2015, at 11:14, Axel Beckert wrote: >> Ondřej Surý wrote: >> > do you think that we can push the resolvconf compatibility to jessie? >> > >> > I see two possible paths here: >> > >> > a) add Breaks: resolvconf >> >> That's ok-ish. It

Bug#776778: Please play nicely with resolvconf

2015-02-04 Thread Ondřej Surý
On Wed, Feb 4, 2015, at 11:14, Axel Beckert wrote: > Hi Ondřej, > > Ondřej Surý wrote: > > do you think that we can push the resolvconf compatibility to jessie? > > > > I see two possible paths here: > > > > a) add Breaks: resolvconf > > That's ok-ish. It would be the short-hack temporary solut

Bug#776778: Please play nicely with resolvconf

2015-02-04 Thread Axel Beckert
Hi Ondřej, Ondřej Surý wrote: > do you think that we can push the resolvconf compatibility to jessie? > > I see two possible paths here: > > a) add Breaks: resolvconf That's ok-ish. It would be the short-hack temporary solution and likely suitable for Jessie. > b) add (Pre-)Depends: resolvconf

Bug#776778: Please play nicely with resolvconf

2015-02-04 Thread Ondřej Surý
Hi Thomas, do you think that we can push the resolvconf compatibility to jessie? I see two possible paths here: a) add Breaks: resolvconf b) add (Pre-)Depends: resolvconf and force resolvconf usage BTW does resolvconf play nicely with NetworkManager? Cheers, Ondrej On Tue, Feb 3, 2015, at 21:

Bug#776778: Please play nicely with resolvconf

2015-02-03 Thread Thomas Hood
Currently dnssec-trigger is not resolvconf-compatible. For one thing, dnssec-triggerd writes /etc/resolv.conf directly and sets the immutability attribute on the file, causing resolvconf installation to fail and resolvconf to fail to function as designed. Let this report track the request that dns