On Fri, 12.01.07 12:59, Loïc Minier ([EMAIL PROTECTED]) wrote:
Hi!
Sorry for the late response. I have just come back from .au and still
am eating thhrough 800+ non-spam mails, which arrived since I left.
On Fri, Jan 12, 2007, Lennart Poettering wrote:
Short: If built with --enable-legacy
Hi,
(I'm Cc:ing the bug so that I can point people at the explanations you
gave.)
On Sun, Feb 04, 2007, Lennart Poettering wrote:
the moudle name suffix 4, 6, or specifies the family of the addresses
that
are resolved. i.e. specifies whether A, or both RRs should be
looked
Hi There,
On Sun, Dec 24, 2006 at 06:32:39PM +0100, Lo??c Minier wrote:
tag 393608 + confirmed
stop
On Wed, Oct 18, 2006, Sam Morris wrote:
I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the
same configuration (that I came to myself after consulting upstream's
On Tue, Dec 26, 2006, Trent Lloyd wrote:
I beleive it is worth noting that the recommended upstream string does
not do IPv6, and given that IPv6 is a goal of etch (last time I
checked?) it may be reasonable to enable that portion. Possibly at this
stage may not be reasonable to do but I still
Howdy,
On Fri, Jan 12, 2007 at 01:02:06PM +0100, Lo?c Minier wrote:
On Tue, Dec 26, 2006, Trent Lloyd wrote:
I beleive it is worth noting that the recommended upstream string does
not do IPv6, and given that IPv6 is a goal of etch (last time I
checked?) it may be reasonable to enable that
Hi,
On Sat, Jan 13, 2007, Trent Lloyd wrote:
- when built with --enable-legacy (as in the past), libnss-mdns will
support A and requests but only over IPv4
Yes however my point is to actually speak over IPv6 not just resolve
addresses.
Yes, but please note that this
tag 393608 + confirmed
stop
On Wed, Oct 18, 2006, Sam Morris wrote:
I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the
same configuration (that I came to myself after consulting upstream's
thoughts on the matter).
The maintainer added postinst snippets in version 0.8-6 to
severity 393608 important
thanks
This is a bug in the package and a policy violation, for discarding the
user's local configuration. It is not in and of itself release-critical,
because the bug only manifests when upgrading from particular unreleased
versions of the package.
--
Steve Langasek
Hi Sam,
On 10/17/06, Sam Morris [EMAIL PROTECTED] wrote:
Package: libnss-mdns
Version: 0.8-6
Severity: serious
Justification: Policy 10.7.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The package threw away my changes to /etc/nsswitch.conf:
[snip]
From what version of libnss-mdns did
The package threw away my changes to /etc/nsswitch.conf:
[snip]
From what version of libnss-mdns did you upgrade?
Was it either 0.8-4.2 or 0.8-5?
I previously had 0.8-5 installed. Before that I had 0.8-4.2 with the
same configuration (that I came to myself after consulting upstream's
Package: libnss-mdns
Version: 0.8-6
Severity: serious
Justification: Policy 10.7.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The package threw away my changes to /etc/nsswitch.conf:
- --- /etc/nsswitch.conf.pre-upgrade 2006-10-16 09:52:48.0 +0100
+++ /etc/nsswitch.conf
11 matches
Mail list logo
