unmerge 614804 notfound 614804 0.6.6-2 notfound 614804 0.6.6-3 found 614804 0.8.1-6 severity 614804 important block 614804 by 606268 thanks
Hi Michael!
On Wed, 23 Feb 2011 16:18:14 +0100, Michael Biebl wrote:
> forcemerge 500998 614804
Reverted, for the reasons explained below. And please wait for my email
to #500998 before any action.
> Am 23.02.2011 16:09, schrieb Luca Capello:
>> Package: network-manager
>> Version: 0.8.1-6
>> Severity: important
>> Blocked-by: 606268
>
>>
>> While investigating bugs #412989 [1] and #500998 [2], I found out that
>> enabling LDAP lookup for all the primary four entries in
>> /etc/nsswitch.conf [3] causes a system lookup:
>
> Looks like a duplicate of 500998.
No, it is a different one:
1) what triggers them is different
#500998 is triggered by "group ldap"
#614804 is triggered by "passwd+group+shadow+hosts ldap"
2) the distributions they happen in is different
#500998 is only in lenny
#614804 is only in squeeze, it manifests in lenny because of the
users/groups referenced by udev not present by default, which is
now fixed, see #412989
FYI, I was closing #500998, given that I found the solution (in the end
it is a network-manager problem), but I waited until this bug got its
number to reference it there. Now I will wait until the two bugs are
unmerged to finally send the solution for #500998, which closes it.
> Ultimately I think this is a bug in libnss-ldap (and you might want to try
> libnss-ldapd and libpam-ldapd).
Have you read the *full* report I submitted?
First, I already know about libnss-ldapd and libpam-ldapd:
>> On lenny, surprisingly enough, this bug does not happen if the "unknown"
>> groups have been replaced by nobody/nogroup (because of #412989 [1]).
>> On squeeze, however, these "unknown" groups are no more unknown [4], but
>> this bug (or some incarnation of it) is still there. Squeeze users can
>> simply install libpam-ldapd and libnss-ldapd, given that even the
>> squeeze Release Notes [5] suggests that for other reasons [6][7].
Second, I found even a more important bug than this one, for which I
left any future action to the network-manager maintainers:
>> Trying to debug dbus-daemon in single-user mode, I discovered that there
>> is no more network. Because of #530024 [10], my /etc/network/interfaces
>> (generated by d-i for a wired interface, so #606268 is no more only
>> related to wireless [11]) is:
[...]
>> This is a serious bug (feel free to clone it), since according to the
>> Debian Reference [11][12]:
>>
>> 3.5.7. Network interface initialization
>>
>> Network interfaces are initialized in runlevel S by the init script
>> symlinked to "/etc/init.d/ifupdown-clean" and "/etc/init.d/ifupdown".
>> See Chapter 5, Network setup for how to configure them.
>>
>> [11]
>> <http://www.debian.org/doc/manuals/debian-reference/ch03.en.html#_network_interface_initialization>
>> [12] I am sorry, but I was not able to find any other documentation or
>> package where this is actually defined, corrections welcomed!
>>
>> FWIW, the squeeze Release Notes contains a text about that [13], but
>> this does not say anything about boot or single-user mode:
>>
>> 5.6.3. network-manager and ifupdown interaction
[...]
>> [13]
>> <http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#id333260>
Thx, bye,
Gismo / Luca
pgpWhzCCVQhub.pgp
Description: PGP signature
