Bug#943735: resolvconf maintenance

Hi there Andrej, Good to hear that you'd like to maintain resolvconf which has been suffering badly from my neglect. You have my best wishes. If you have any questions or need any help then I am happy to oblige. My TODO list for resolvconf, which is now a couple of years old, is in debian/NOTES

Bug#847440: [Resolvconf-devel] Bug#847440: pending

I will orphan the package if I can't meet my self-imposed deadline. I'll also RFA it again, although that didn't attract any interest on previous occasions. Please feel free to do a QA NMU. Regards, Thomas Op vr 22 feb. 2019 08:58 schreef Bernhard Schmidt : > Hi Thomas, > > having no time

Bug#847440: [Resolvconf-devel] Bug#847440: pending

a deadline should help. I hereby set a deadline for myself of the end of March 2019. I realize that is too late for Buster. Cheers, Thomas Hood Op do 21 feb. 2019 13:09 schreef Michael Prokop : > * Bernhard Schmidt [Sun May 07, 2017 at 10:57:24PM +0200]: > > On Thu, Dec 15, 2016 at 11:18:4

Bug#887176: [Resolvconf-devel] Bug#887176: resolvconf should depend on e2fsprogs explicitly

Hi there, Is there any special reason not to add e2fsprogs as a dependency? Cheers, Thomas On Sat, 20 Jan 2018 at 01:45 Andreas Henriksson wrote: > Hello, > > On Sun, Jan 14, 2018 at 08:10:44PM +0100, Helmut Grohne wrote: > > Package: resolvconf > [...] > >

Bug#729665: [Resolvconf-devel] Bug#729665: Please implement an option that causes resolvconf to list VPN nameservers exclusively

Thanks for the suggestion. I'm going to read up on this. Cheers, Thomas Hood On Tue, Apr 18, 2017 at 7:57 PM Jason A. Donenfeld <ja...@zx2c4.com> wrote: > This would be accomplished by the recommendation in #860564. > > ___ > Resolv

Bug#856015: [Resolvconf-devel] Bug#856015: may be dnsmasq issue

package resolvconf severity 856015 normal retitle 856015 Fails in networks with non-equivalent nameservers reassign 856015 dnsmasq merge 856015 675319 stop Hi. This is a known behavior of dnsmasq. -- Thomas On Mon, Feb 27, 2017 at 11:45 AM Daniel Pocock wrote: > > > I ran

Bug#783596: resolvconf /e/n/i dns-* option only works in last of homonymous iface def'ns

Hi there, The change you suggested is at best only a partial solution: second and later records non-overwrite the first record only if they are completely empty. Furthermore an empty record is valid and possibly wanted in the corner case where there is a stale file in the database. As things

Bug#847440: [Resolvconf-devel] Bug#847440: resolvconf: run resolvconf service before any networking service

Hi and thanks for the patch. Did you test it in Debian? -- Thomas

Bug#776778: Still to do

Remaining to do to eliminate the incompatibility between dnssec-trigger and resolvconf * Change dnssec-trigger such that it does not touch /etc/resolv.conf directly when /sbin/resolvconf is present on the filesystem * Replace "Breaks: resolvconf" with "Breaks: resolvconf (<< 1.79)" and "Suggests:

Bug#776778: #777228 done

> I wrote: >> We can file a new bug report requesting that unbound include the file in question. > > I have filed bug report #777228. As of version 1.5.7-2 the unbound package includes the file in question; #777228 has been closed. -- Thomas

Bug#819498: [Resolvconf-devel] Bug#819498: /etc/resolvconf/update.d/resolvconf-update-bind called without CAP_CHOWN from n-m

30, 2016 at 09:35:32AM +0200, Thomas Hood wrote: > > I am happy to remove the chown from the (example) script. But are you > sure > > that bind processes the file if the owner is not root:bind? > > Mine takes it happily with root:staff. I guess it won't if it can't > read th

Bug#819498: [Resolvconf-devel] Bug#819498: /etc/resolvconf/update.d/resolvconf-update-bind called without CAP_CHOWN from n-m

Hi and thanks for the bug report. I am happy to remove the chown from the (example) script. But are you sure that bind processes the file if the owner is not root:bind? -- Thomas

Bug#802845: /etc/resolvconf/update.d/dnsmasq

The offending script is in the dnsmasq package. I agree that RUN_DIR should be /run and not /var/run. -- Thomas Hood

Bug#797652: wontfix

package resolvconf tags 797652 wontfix stop Dear bug report submitter, First of all, thanks for the suggestion. In general services shouldn't implement their own enable/disable mechanisms; that's what init systems are for. Resolvconf isn't a typical service, however. It's really a bit of

Bug#791978: #181: Re: Bug#791978: interfaces-order is being ignored

On Jul 10, 2015 11:04 PM, Stephen Crowley c...@canaccord.com wrote: I think I might know what the problem is... the proprietary f5 client has some thread that sits in the background and monitors for changes to resolv.conf and routing tables and fixes them. Ugh. Is there any way to switch off

Bug#791978: More info, pls

Hi and thanks for the report. Please run this command /usr/share/resolvconf/dump-debug-info when you are experiencing the problem and post the output here. -- Thomas Hood

Bug#791978: interfaces-order is being ignored

resolvconf is not putting the tun0 resolvers below that of eth* even though tun* is supposed to take precedence I don't understand this. If tun* is supposed to take precedence over eth* then resolvconf *shouldn't* put the tun0 resolver addresses *below* those of eth* in resolv.conf; resolvconf

Bug#787457: Cannot reproduce

package resolvconf severity 787457 minor stop Experiment reveals that running update-rc.d test defaults on wheezy does not result in a traditional default field of symlinks when the initscript has LSB headers that specify otherwise; update-rc.d obeys the LSB header spec. So the aforementioned

Bug#787457: Needs fixing

Experiment. I create a bogus rc symlink for resolvconf. ln -s ../init.d/resolvconf /etc/rc2.d/S01resolvconf Then I run update-rc.d with an unrelated initscript. update-rc.d alsa-utils defaults After this, the resolvconf symlink in rc2.d is still present but has been renumbered to

Bug#787457: Resolvconf in Jessie missing dependency on sysv-rc

2.88dsf-41+deb7u1 which allows for a scenario where resolvconf gets upgraded first and its postinst runs the old update-rc.d. Whether or not this results in the Wrong Thing being done requires investigation. -- Thomas Hood

Bug#783596: Not a bug

On 28 April 2015 at 16:28, Andrew Shadura and...@shadura.me wrote: That isn't true: ifupdown calls all hook scripts for every entry that many times as is the number of entries. Ah, sorry, I didn't know that. (I thought that ifupdown would combine the information and call the hook scripts only

Bug#783596: Not a bug

as the other one is called legacy Where did you read this? -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783596: Not a bug

reassign 783596 ifupdown retitle 783596 ifupdown elides info from all but last homonymous iface def'n stop OK, thanks for the reference. I didn't know that ifupdown had been enhanced in that way. ifupdown (0.7~alpha4) experimental; urgency=low [...] * Allow multiple

Bug#777228: Bug report with paths corrected

Package: unbound Version: 1.4.22-3 Severity: wishlist Please add the hook script /usr/lib/resolvconf/dpkg-event.d/unbound. The purpose of this script is to cause unbound to take notice of the installation or removal of the resolvconf package. If resolvconf has been installed then unbound should

Bug#777228: Please add resolvconf packaging-event hook script

Aak, the correct path is /usr/lib/resolvconf/dpkg-event.d/. The other path beginning with /etc is obsolete and only got mentioned because I copypasted text from another message. My apologies! -- Thomas Op 21 feb. 2015 23:31 schreef Robert Edmonds edmo...@debian.org: Thomas Hood wrote: Please

Bug#776778: TODO

Am I correct in tentatively concluding that the only thing that has to be done in order to make dnssec-trigger work correctly with resolvconf and thus grant this wish (#776778) is to stop dnssec-trigger from touching /etc/resolv.conf directly when /sbin/resolvconf is present on the filesystem? So

Bug#776778: Report filed

I wrote: We can file a new bug report requesting that unbound include the file in question. I have filed bug report #777228. http://bugs.debian.org/777228 -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#700850: Hangs?

incorrectly. That should be investigated, also because it could be a problem quite independently of this report. Cheers, -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#777228: Please add resolvconf packaging-event hook script

Package: unbound Version: 1.4.22-3 Severity: wishlist Please add the hook script /etc/resolvconf/packaging-event.d/unbound. The purpose of this script is to cause unbound to take notice of the installation or removal of the resolvconf package. If resolvconf has been installed then unbound should

Bug#776778: Please play nicely with resolvconf

On 5 February 2015 at 21:28, Thomas Hood jdth...@gmail.com 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

Bug#776778: Please play nicely with resolvconf

On 4 February 2015 at 12:00, Ondřej Surý ond...@sury.org 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 would

Bug#776778: Please play nicely with resolvconf

On 5 February 2015 at 16:35, Axel Beckert a...@debian.org 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

Bug#776776: Bug in resolvconf?

The dnssec-trigger daemon sets the immutability attribute on a file /etc/resolv.conf which it writes out. Evidently, dnssec-trigger is not resolvconf-compatible. The immediate, straightforward solution is for the dnssec-trigger package to Conflict with the resolvconf package. At least this should

Bug#776776: Breaks resolvconf

Let this report (#776776) track the issue that dnssec-trigger breaks resolvconf and therefore must declare a Breaks: resolvconf. This can and should be fixed immediately, for jessie. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#776778: Please play nicely with resolvconf

itself to futz with /etc/resolv.conf. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776776: Bug in resolvconf?

Hi and thanks for the report. Do you think that this failure means that there is a bug in the resolvconf package? -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776778: Don't play well together

Is dnssec-trigger meant to work with resolvconf or does it conflict (functionally) with resolvconf, so that it should declare a Conflicts: resolvconf? -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#775356: New patch

@@ -1,3 +1,10 @@ +resolvconf (1.77) unstable; urgency=medium + + * [eb81ca0] Eliminate bashisms. +Thanks to Michael Gilbert (Closes: #775356) + + -- Thomas Hood jdth...@gmail.com Fri, 23 Jan 2015 21:46:34 +0100 + resolvconf (1.76) unstable; urgency=low * resolvconf.service: Install

Bug#775356: Evolved patch

Here's a cosmetically evolved patch which I'll commit and release shortly. Thanks! -- Thomas diff --git a/etc/dhcp/dhclient-enter-hooks.d/resolvconf b/etc/dhcp/dhclient-enter-hooks.d/resolvconf index 529504b..cf61615 100644 --- a/etc/dhcp/dhclient-enter-hooks.d/resolvconf +++

Bug#773749: Resolvconf vs wicd

On 14 January 2015 at 16:18, Axel Beckert a...@debian.org wrote: It's up to the admin to change things in /etc/. Programs that play around with things in /etc/ at runtime are not well behaved by Debian standards. Depends. I agree for anything in the maintainer scripts, but I disagree for

Bug#773749: Resolvconf vs wicd

On 14 January 2015 at 15:08, Vincent Lefevre vinc...@vinc17.net wrote: On 2015-01-14 14:14:22 +0100, Thomas Hood wrote: This is an allowed configuration (which is sometimes even useful). [...] OK, but this is a very atypical usage for users of wicd, whose goal is to make things work without

Bug#773749: Resolvconf vs wicd

I just read bug report #514597 entitled wicd does not work properly with resolvconf which was closed in version 1.5.9-2 with the message that 07-add_resolvconf_support.patch added. Although I don't see this patch in the current source tree, I do see references to the resolvconf program which

Bug#754084: More info please

Hi there. Can you please provide more information for Debian bug report #754084? I don't see what the problem is. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#754084: [Resolvconf-devel] Bug#754084: stateless DHCPv6 info request doesn't set /etc/resolv.conf

On 30 July 2014 13:37, Harald Dunkel harald.dun...@aixigo.de wrote: Any news on this? Hi there. How 'bout sending us a patch? We'll include it in the upcoming release. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#749405: [Resolvconf-devel] Bug#749405: Bug#749405: Current Status + Moving Forward?

(1.76) unstable; urgency=medium + + * resolvconf.service: Install into sysinit.target, not into +network.target (Closes: #749405) + + -- Thomas Hood jdth...@gmail.com Tue, 24 Jun 2014 11:50:33 +0200 + resolvconf (1.75) unstable; urgency=low * [49dedb8] Update man page re: dns-nameserver

Bug#752521: Misleading man page statements and command names

Package: dh-systemd Version: 1.18 Severity: minor It is conventional to choose command names that express what the command does. Accordingly, it is conventional for debhelper command names to express what they do. For example, the dh_installinit command installs init files into package build

Bug#749405: [Resolvconf-devel] Bug#749405: Current Status + Moving Forward?

On 23 June 2014 05:45, Nick Daly nick.m.d...@gmail.com wrote: What still needs to be done on this bug to resolve it? I think it just needs to be tested. Have you tested the proposed fix at all? -- Thomas

Bug#749405: [Resolvconf-devel] Bug#749405: resolvconf: /etc/resolvconf/run/interface either does not exist or is not a directory

Hi all, First of all I must apologize for the inconvenience caused by this bug. Martin, can you please comment? -- Thomas

Bug#746941: Proposed solution

-is-installed ] || exit 0 The file /usr/lib/dnsmasq/package-is-installed could include a comment explaining the purpose of the file. -- Thomas Hood

Bug#700846: Service file

Martin, Cameron, Is resolvconf.service releasable? Should I now copy the file /lib/systemd/system/resolvconf.service from Martin Pitt's package to the Debian resolvconf package? Anything else you want to remind me to do when I include this file? -- Thomas

Bug#746940: Cruft in initscript

Package: dnsmasq Version: 2.70-1 Severity: minor In the initscript the following three lines of code at the end of the stop function are superfluous. RETVAL=$? [ $RETVAL = 2 ] return 2 return $RETVAL They can be deleted without changing the behavior of the script.

Bug#746941: Initscript fails to disable itself when the dnsmasq package is removed

Package: dnsmasq Version: 2.70-1 Severity: serious By means of test -x $DAEMON || exit 0 the initscript disables itself if /usr/sbin/dnsmasq is not installed. But this binary belongs to another package, dnsmasq-base. So the initscript disables itself if and only if that other package,

Bug#700846: service file

Thanks for the service file, Cameron. Readers are invited to test and (if necessary) to improve it. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#483098: Resolvconf - bind9 integration

agree to include the requested hook script then I am prepared to write and submit it here. That offer still stands, but I have never heard a peep from the bind9 maintainers, so I have not submitted a modified script. Please see my earlier comment for other details. -- Thomas Hood

Bug#729665: Please implement an option that causes resolvconf to list VPN nameservers exclusively

Package: resolvconf Version: 1.74 Severity: wishlist A user wishes that when a VPN is established and registers a VPN nameserver address with resolvconf then only the VPN nameserver is used, not other nameservers. What is wished for is in effect an option

Bug#629100: winexe build

4.0.10 packages from unstable. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#721082: The patch (take 2)

Attached is a second version of the patch with a bug removed that was noticed by Nathan Stratton Treadway. The bug was that I had used 'echo' instead of 'exit' in two instances at the top of the script. Thanks to Nathan and my apologies for the bug. -- Thomas

Bug#721082: The patch

/update-resolv-conf # down /etc/openvpn/update-resolv-conf # -# Used snippets of resolvconf script by Thomas Hood jdth...@yahoo.co.uk -# and Chris Hanson +# Used snippets of resolvconf script by Thomas Hood and Chris Hanson. Thomas Hood's e-mail address has changed

Bug#721082: Please better document the update-resolv-conf script and/or explain why it conflicts with ifup

overwriting ifup's resolvconf record. So I decided to ask about that first. Especially in light of your answer, I think that the aforementioned oddities are just a result of the user copying the hook script from ifup and not changing identifiers. So I will submit the patch. :) -- Thomas Hood

Bug#344233: Bug still exists

In Debian 7 the host.conf(5) man page still describes the order option which has been inoperative for years and still refers to resolv+(8) which doesn't exist. And it still fails to mention nsswitch.conf. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#270368: Fwd: Bug still exists

In Debian 7 the host.conf(5) man page still describes the order option which has been inoperative for years and still refers to resolv+(8) which doesn't exist. And it still fails to mention nsswitch.conf. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#721082: Please better document the update-resolv-conf script and/or explain why it conflicts with ifup

. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#663006: Retitle to RFP?

Given that this ITP was filed over a year ago, should it be retitled to RFP? -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#720732: Please apply yet another patch to resolvconf update script

reasons. Thanks! -- Thomas Hood etc-resolvconf-update-dnsmasq_20130824th1.patch Description: Binary data

Bug#716908: New version of patch for latest version of the update script

I just realized that I based the submitted patch on a version of the update script that isn't the latest in Debian. I based it on the latest version of the script in Ubuntu, which is out of date in comparison with Debian. Sorry about that! For the latest script in Debian the patch has to look

Bug#718021: [Resolvconf-devel] Bug#718021: dns-nameservers vs dns-nameserver

On Tue, Jul 30, 2013 at 12:16 AM, Christoph Anton Mitterer cales...@scientia.net wrote: it's just that we're probably better off with suggesting people only one variant... so we can phase out the other on the long term scale... I'll make dns-nameserver the canonical one and dns-nameservers

Bug#718232: update-rc.d: warning: start and stop actions are no longer supported

Thanks for the report. I wasn't aware of this issue. It seems the start and stop arguments are now deprecated. Roger Leigh announced this debian-devel. http://lists.debian.org/debian-devel/2013/05/msg01109.html We should go with the flow and stop using start and stop. Here's the postinst

Bug#716908: Resolvconf 1.74 released

Hi Simon, Resolvconf 1.74 has been released with the --after feature which dnsmasq-resolvconf-hook-script_20130718th1.patch makes use of. BTW, the back story for this change can be read at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1163147 Cheers, -- Thomas

Bug#717438: Recall latest pdnsd version

Also tell me if there are any hot alternatives to pdnsd, Most people use dnsmasq for DNS caching. It is very well maintained. -- Thomas

Bug#716908: New patch

One curious thing about my proposal is that I called the new list-records option --omit-up-to instead of simply --after. Some thinking did precede that. I thought: If the option is called 'after' then that will suggest that if there is no record named like the argument then nothing will be

Bug#716908: Please apply patch to dnsmasq's resolvconf hook script

Package: dnsmasq Version: 2.65 Severity: wishlist Please apply the attached patch to dnsmasq's resolvconf hook script /etc/resolvconf/update.d/dnsmasq. With the patch the script calls the list-records program with a new option --omit-up-to lo.dnsmasq. This causes a new version of list-records

Bug#582916: Testing eglibc 2.17-7

Jens, I ran your program (updated test) on a Debian 7.0 system with libc6 et al upgraded to 2.17-7. Output: y.c:44: error: r=-2 Name or service not known Output after replacing karme.de. with www.google.com: none; the program completed successfully. Output after doing iptables -I OUTPUT -p

Bug#683061: getaddrinfo() return value chaos

It looked to me as if #582916 and roughly duplicate #671789 could have been fixed in libc6 2.17-7 which it includes two commits http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=cfde9b463d63092ff0908d4c2748ace648e2ead8

Bug#582916: Testing eglibc 2.17-7

On Mon, Jul 8, 2013 at 9:16 AM, Jens Thiele ka...@karme.de wrote: Output: y.c:44: error: r=-2 Name or service not known Output after replacing karme.de. with www.google.com: none; the program completed successfully. Output after doing iptables -I OUTPUT -p udp -m udp --dport

Bug#582916: Testing eglibc 2.17-7

On Mon, Jul 8, 2013 at 9:35 AM, Jens Thiele ka...@karme.de wrote: from the test: to easily reproduce, fake packet loss/overloaded dns server on linux do something like: # iptables -I OUTPUT -p udp -m udp --dport 53 -j DROP # iptables -I OUTPUT -p udp -m udp --dport 53 -j LOG --log-prefix

Bug#683061: getaddrinfo() return value chaos

Continuing on from the boot ordering and resolvconf thread; cc:ed to Helmut in case this gets filtered again; bcc:ed to 683...@bugs.debian.org since this is relevant for how that issue is addressed... Executive summary: The getaddrinfo() returns different values depending on the OS and on

Bug#582916: Is #582916 still a bug?

Hi there Jens, I have been looking into bug #683061 and Kurt Roeckx pointed me to #582916 which you investigated last November. I have trouble understanding exactly what the current behavior is and what you expect. Does getaddinfo() do what you expect on Ubuntu 13.04 which has version

Bug#582916: Is #582916 still a bug?

On Sun, Jul 7, 2013 at 3:00 PM, I jdth...@gmail.com wrote: Does getaddinfo() do what you expect on Ubuntu 13.04 which has version 2.17-0ubuntu5 of eglibc? Do you think that the bug has been properly fixed upstream? http://sourceware.org/bugzilla/show_bug.cgi?id=14719

Bug#683061: [pkg-ntp-maintainers] Bug#683061: bug report #683061

On Tue, Jul 2, 2013 at 1:59 PM, Kurt Roeckx k...@roeckx.be wrote: Do you know NXDOMAIN returns? I think it returns just the same? I don't immediately see how getaddrinfo() alone can be used to tell whether or not an actual NXDOMAIN was received. A test with a small C program reveals that

Bug#275487: willfix?

package resolvconf tags 275487 - wontfix stop This feature would be useful for debugging purposes.

Bug#683061: [pkg-ntp-maintainers] Bug#683061: Bug#683061: bug report #683061

On Tue, Jul 2, 2013 at 3:57 PM, Kurt Roeckx k...@roeckx.be wrote: Do you expect the DHCP server on the LAN then to set that ntp server? Currently this would now result in ntpd getting restarted by dhcp and should get you a working ntp server. I think it is a good idea to furnish time

Bug#683061: bug report #683061

. That a domain name does not now exist does not entail that it never will exist. And then there is no need to distinguish the two cases. -- Thomas Hood P.S. I got to this bug report from here: http://lists.debian.org/debian-devel/2013/06/msg00316.html

Bug#629100: Status update

The Samba team has been very busy preparing a unified, solid, and policy-compliant package based on release 4.0.6. Those guys deserve some serious respect. Their package will soon appear in experimental and then unstable and in Ubuntu. Once this package appears and has stabilized for a few weeks,

Bug#710960: Please support domain name lookup routing with resolvconf

Package: dnsmasq Version: 2.66-3 Severity: wishlist When NetworkManager controls dnsmasq it configures dnsmasq to route VPN domain name lookups to the VPN nameserver. It should be possible to implement this for dnsmasq server too. Suppose the VPN client has registered the following record

Bug#709179: Here's the patch

package dnsmasq tags 709179 patch stop Attached is the patch to implement this. dnsmasq.gz - The patched /etc/resolvconf/update.d/dnsmasq dnsmasq_2.65-1ubuntu1_bug709179.patch - Patch against 2.65-1ubuntu1 -- Thomas dnsmasq.gz Description: GNU Zip compressed data

Bug#709179: Here's the patch

Oops, forgot this part of the patch which fixes a spelling mistake. ;) @@ -27,7 +27,7 @@ report_err() { echo $0: Error: $* 2 ; } # Stores arguments (minus duplicates) in RSLT, separated by spaces -# Doesn't work properly if an argument itself contain whitespace +# Doesn't work properly if an

Bug#709179: Please automagically forward to dnscrypt-proxy if available

Package: dnsmasq Version: 2.66-2 Severity: wishlist OpenDNS's DNSCrypt client for Linux (called 'dnscrypt-proxy')[0] is not yet packaged for Debian but some people are already installing it from source and it is of course possible that it will eventually be packaged. This is a request that the

Bug#709258: Please automagically handle dnscrypt-proxy correctly

Package: resolvconf Version: 1.71 Severity: wishlist OpenDNS's DNSCrypt client for Linux (called 'dnscrypt-proxy')[0] is not yet packaged for Debian but some people are already installing it from source and it is of course possible that it will eventually be packaged. (It is free software and

Bug#705745: Please add resolvconf dpkg-event hook script

Package: dhcpcd Severity: wishlist Please add the hook script /usr/lib/resolvconf/dpkg-event.d/dhcpcd The purpose this script is to cause dhcpcd to take notice of the installation (or removal) of the resolvconf package. If resolvconf has been installed then dhcpcd should register with resolvconf

Bug#705759: Please support and Recommend resolvconf as well as openresolv

Package: dhcpcd5 Version: 5.5.6-1 Severity: wishlist The dhcpcd5 package currently Recommends openresolv. As openresolv is resolvconf-compatible (it Provides: resolvconf), it should be possible to extend the recommendation to resolvconf as follows. Recommends: openresolv | resolvconf If

Bug#705582: Please add option PREFER_IPV6

Package: resolvconf Version: 1.71 Severity: wishlist -- Forwarded message -- From: Pali Rohár pali.ro...@gmail.com Date: Sun, Apr 14, 2013 at 8:31 PM Subject: [Resolvconf-devel] [PATCH] Add option PREFER_IPV6 To: resolvconf-de...@lists.alioth.debian.org Hello, I created small

Bug#629100: Status update

Winexe in the winexe-waf repository now builds nicely against the Samba 4 public API and shared libraries as represented by Debian Samba 4 packages and I am hoping, therefore, that there will soon be a new Winexe release based on this winexe-waf code. Once Winexe has been released it would be

Bug#704528: Please include new resolvconf hook script which handles multiple postfix instances

Package: postfix Version: 2.9.6-2 Severity: wishlist Tags: patch Attached is a new resolvconf update hook script (/etc/resolvconf/update-libc.d/postfix) which handles multiple postfix instances. Please include it instead of the existing script. Thanks to Patrik Båt for writing this. -- Thomas

Bug#700385: Improved update script

I wrote: Then include a file named /etc/resolvconf/update-libc.d/000nscd in the nscd package with the following content. #!/bin/sh [ -x /etc/init.d/nscd ] /etc/init.d/nscd invalidate-hosts There's a bug in this one-line script. :) The script with accompanying amendment to

Bug#700846: Please add systemd support

it if someone would give advice or submit patches. -- Thomas Hood

Bug#700385: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache

the hosts cache enabled. -- Thomas Hood

Bug#699425: Fetchmail's resolvconf update script can be simplified

(as it once did have to be). -- Thomas Hood --- fetchmail_ORIG 2013-01-31 11:11:39.926431750 +0100 +++ fetchmail 2013-01-31 11:11:57.522479569 +0100 @@ -1,12 +1,5 @@ #!/bin/sh -while [ $1 ]; do - if [ $1 = --nscd ]; then - exit 0 - fi - shift -done - if [ -x /etc/init.d/fetchmail ] [ -n $(pidof

Bug#699061: Please ignore leading whitespace on lines in resolv.conf

-dns-using-host-but-cant-ping-ssh-ntp/247542 I request that leading whitespace on lines in resolv.conf be ignored. -- Thomas Hood

Bug#697435: Warn users about removal of old update.d/bind

Package: resolvconf Version: 1.69 Severity: minor Tags: confirmed Resolvconf 1.69 (and thus Wheezy+1) moves the old /etc/resolvconf/update.d/bind script out of the way. (See bug report #687507.) (The file has not been included in resolvconf since 1.53 and thus has not been included in a Debian

Bug#695121: kppp not resolvconf-aware; appears to clobber /etc/resolvconf

Package: kppp Version: 4.8.4-1 Severity: important Looking at the kdenetwork 4.8.4-1 source code I see the following code snippets in kppp/connect.cpp starting at line 1419: // Replace the DNS domain entry in the /etc/resolv.conf file and // disable the nameserver entries if option is

  1   2   3   4   5   6   7   >