Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 397691 - net-dns/openresolv-3.5.2 version bump
Summary: net-dns/openresolv-3.5.2 version bump
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Jim Ramsay (lack) (RETIRED)
URL: http://roy.marples.name/projects/open...
Whiteboard:
Keywords:
: 437148 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-01-04 20:00 UTC by teidakankan
Modified: 2012-12-02 09:09 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description teidakankan 2012-01-04 20:00:10 UTC
ftp://roy.marples.name/pub/openresolv/openresolv-3.4.5.tar.bz2

Reproducible: Always
Comment 1 Oleh 2012-03-24 14:13:50 UTC
openresolv-3.4.6 is out
Comment 3 Matthew Turnbull 2012-05-06 03:00:11 UTC
For the record, 3.5.2 does not appear to need any ebuild changes from 3.4.1, though I did include the change from Bug 383763 in my personal overlay.

I have been running 3.5.2 for about a month without any apparent issue (with dhcpcd-5.2.12 and wicd-1.7.2.1).
Comment 4 Guillaume Castagnino 2012-08-14 15:38:48 UTC
I support this. Moreover, I'm greatly interested by the feature "name_server_blacklist" present in the new version !

Does someone can bump it ? Thanks !
Comment 5 Oleh 2012-08-14 16:36:36 UTC
dhcpcd-5.5.x segfaults with openresolv-3.5.2, so there is something to fix.
Comment 6 Jeroen Roovers (RETIRED) gentoo-dev 2012-10-04 14:11:01 UTC
*** Bug 437148 has been marked as a duplicate of this bug. ***
Comment 7 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2012-11-26 11:12:47 UTC
+*openresolv-3.5.2 (26 Nov 2012)
+
+  26 Nov 2012; Lars Wendler <polynomial-c@gentoo.org> +openresolv-3.5.2.ebuild:
+  non-maintainer commit: Version bump (bug #397691).
+
Comment 8 Mihai Donțu 2012-11-29 01:50:04 UTC
Something went wrong after this update: on my system with NetworkManager enabled, I found myself with a fairly useless /etc/resolv.conf:

$ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 127.0.0.1

and that's it, which is useless because I don't have a local nameserver. I had to add the following line to /etc/resolvconf.conf

resolv_conf_passthrough=yes

which basically copies the contents of /var/run/resolvconf/interfaces/NetworkManager into that file.
Comment 9 Roy Marples 2012-11-30 09:50:10 UTC
(In reply to comment #8)
> Something went wrong after this update: on my system with NetworkManager
> enabled, I found myself with a fairly useless /etc/resolv.conf:
> 
> $ cat /etc/resolv.conf
> # Generated by resolvconf
> nameserver 127.0.0.1
> 
> and that's it, which is useless because I don't have a local nameserver. I
> had to add the following line to /etc/resolvconf.conf
> 
> resolv_conf_passthrough=yes
> 
> which basically copies the contents of
> /var/run/resolvconf/interfaces/NetworkManager into that file.

If you don't have a local nameserver, then remove the configuration for it.
You probably have 127.0.0.1 configured in /etc/resolvconf.conf
Comment 10 Mihai Donțu 2012-12-02 08:19:31 UTC
I don't have a local nameserver configured:

$ cat /etc/resolvconf.conf
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
resolv_conf_passthrough=yes
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1

NetworkManager seems to configure one, though. I don't know why yet.