Nicolas François wrote:
On Mon, Aug 21, 2006 at 03:12:56PM -0400, Jamin W. Collins wrote:
I also appear to be bitten by this one. My user accounts are also stored
in LDAP.
Does anybody know why we use LOGNAME (in /usr/lib/dpkg/controllib.pl)?
I could find this in the ChangeLog:
dpkg (1.4.0.9) unstable; urgency=low
[...]
* Changed controllib.pl to use $ENV{LOGNAME}, getlogin(), and $<
(in that order) to determine the intended ownership of
debian/{files,substvars}, (fixes #7324, #6823, #5659, #5965, #5929,
#9239, #5366).
[...]
-- Klee Dienes <[EMAIL PROTECTED]> Mon, 17 Mar 1997 16:11:24 -0500
(And I can't find these bug reports; BTW does anybody have an archive of them)
If we could remove the usage of LOGNAME (and getlogin), and only keep $< and
$(, I think it would be fine (in that case, there is no need to call getpwnam).
A patch is attached, but it assumes these bugs do not apply anymore ;(
It might also be worth noting that this same configuration was not a
problem under sarge. The problem did not occur until I upgraded my
system from sarge to etch on Sunday. Then the boot process broke due to
the libnss-ldap changes (ldap then compat no longer worked in
/etc/nsswitch.conf, but that's a different bug report). Once
/etc/nsswitch.conf was changed to files then ldap the boot process at
least continued. Then I found this problem.
It seems that some change with libnss-ldap between sarge and etch is
wreaking havoc on configurations that have thus far been working fine.
I know of breakage within at least three different locations related to
the changes (boot, dbus/hal, and now this).
--
Jamin W. Collins
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
