Bug#345168: Sarge version of nscd is completely broken (Fails to cache any entry)

2005-12-31 Thread Phil Blundell
On Thu, 2005-12-29 at 15:08 +0100, Laurent Caron wrote:
> I'm using nscd (sarge version) with LDAP, and it is  not working.
> 
> Attaching to it with strace -p $PID shows no activity while doing a
> simple ls -al /home with a few directories in /home, making constant
> LDAP lookups.
> 
> Upgrading nscd to the one in sid solves the problem..

It is hard to believe that the version of nscd in sarge could have
remained completely broken for this length of time without someone
noticing.  So I'm guessing that there must be some local problem on your
system that is preventing it from working.

Could you please send us the complete strace output from nscd (i.e. from
program startup onwards), and also the complete output from "strace ls
-l /home" or something similiar?

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#214898: Bug#133578: gdm: default locale setting

2005-12-29 Thread Phil Blundell
On Fri, Apr 16, 2004 at 09:13:42PM -0700, Ryan Murray wrote:
> > Just to make it clear to everyone involved -- #133578 is waiting for #214898
> > to be fixed in glibc.  I'm not going to parse/use a tool to read the PAM
> > configuration file /etc/environment.  That config file is for setting up
> > the _login_ environment, not the system boot environment.

I see that #133578 has been closed now.  Does this mean that the
requirement for #214898 has gone away, and this bug can also be closed?

p.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#264887: GLOB_APPEND ignored by glob() in at least one place

2005-12-29 Thread Phil Blundell
On Tue, 2004-08-10 at 14:41 -0500, Jeff Licquia wrote:
> When the GLOB_APPEND flag is passed to glob(), the call is supposed to
> tack new results on to the ones already represented in the glob_t passed
> in.  If there is an error, partial results may be added, but the
> original glob_t should definitely be left alone.
> 
> This is not respected in at least one part of glibc's glob
> implementation.  In this particular place, globfree() is called on the
> glob_t regardless of the flags passed.  Since glob() is implemented
> recursively with GLOB_APPEND added to the flags, this can affect the
> results returned even from a call where GLOB_APPEND is not set.
> 
> The following patch fixes the one instance of this behavior I found.

Thanks for the patch.  Do you have a testcase that demonstrates the
effect of the bug?

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#326791: install of libc6 wants to remove all kernels

2005-12-29 Thread Phil Blundell
On Mon, 2005-09-05 at 21:10 +0200, Wolfgang Leister wrote:
> As you can see from the example the install tries to uninstall
> initrd-tools and all installed kernels. This makes that I cannot upgrade
> some other packages that depend on a newer version of libc6.

This is caused by libc6's Conflict with older versions of initrd-tools.
If you upgrade initrd-tools before libc6 then the problem should go
away.

I'm not sure if there is anything we can do in libc6 to make this
situation work better (for example, by encouraging apt to upgrade
initrd-tools rather than removing it).  Any suggestions would be
welcome.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#298913: locales: option to locale-gen to avoid regenerating existing locales?

2005-12-29 Thread Phil Blundell
tags 298913 + pending
thanks

On Thu, 2005-03-10 at 17:16 +, Colin Watson wrote:
> Attached is a patch that implements a --keep-existing flag, with
> documentation. It relies on perl-base to figure out whether the locale
> exists, but perl-base is Essential so that should be OK. Run 'make' in
> debian/local/manpages/ after applying it.

Looks good to me.  I've checked this in.  Thanks.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: r1075 - in glibc-package/trunk/debian/local/manpages: . es fr id pl

2005-12-28 Thread Phil Blundell
On Wed, 2005-12-28 at 22:34 +0100, Denis Barbier wrote:
> thanks for taking care of translated manual pages, but the po/
> directory needs to be checked in too.  OTOH you may remove
> xx/validlocale.xx.8 files (they are generated during the build)
> and fr/termwrap.add (it was needed for the termwrap program,
> which does no more exist).

Whoops.  Thanks for the correction.  I've checked in the missing po/*
files now, and I'll remove the extraneous validlocale.xx.8 ones shortly.

p.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#329126: please add conflict with sarge gawk to post-sarge libc6

2005-12-28 Thread Phil Blundell
On Mon, 2005-09-19 at 23:07 +0400, Nikita V. Youshchenko wrote:
> [EMAIL PROTECTED]:~> echo -n | fakeroot awk '{print}'
> awk: relocation error: awk: symbol _dl_catch_error, version GLIBC_PRIVATE not 
> defined in file ld-linux.so.2 with link time reference
> 
> This is fixed in post-sarge gawk 3.1.4-2.0.1.
> 
> This may affect large number of people, who upgrade to post-sarge libc6 to
> be able to install other post-sarge packages. So it seems reasonable to
> add a conflict with sarge version of gawk to current libc6 packages.

I have a feeling that adding this conflict is likely to result in gawk
just being uninstalled, and potentially taking a lot of other packages
with it, during upgrades.  If that's the case, it seems that the cure
would be rather worse than the original disease.  That said, I agree
with you that just leaving gawk in a broken state is not exactly
satisfactory either.

I've copied this note to debian-release in case the fine folks on that
list can provide any guidance.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#344954: validlocale needs a new home

2005-12-28 Thread Phil Blundell
tags 344954 + pending
thanks

On Tue, 2005-12-27 at 17:39 -0500, Joey Hess wrote:
> The validlocale program is currently part of base-config, but
> base-config is going away. validlocale needs a new home ASAP and locales
> seems like the best place.

Seems reasonable to me.  I've checked this into SVN; it'll be in the
next upload.

Thanks

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#314616: doesn't re-read resolv.conf

2005-12-26 Thread Phil Blundell
reassign 314616 no-ip
thanks

Glibc's standard behaviour is to cache the contents of /etc/resolv.conf
across multiple calls to gethostbyname().  I doubt this will change any
time soon.

The solution to this bug is probably for no-ip to call res_init() prior
to attempting resolution, if it suspects that the nameservers are likely
to have changed.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#324795: libc6 in stable broken on arm4vl

2005-12-25 Thread Phil Blundell
The "llseek" problem is caused by a kernel bug.  I thought that the
2.2.19 netwinder kernels in Debian had been patched to fix this, but I
guess I was mistaken about that.  Anyway, there isn't a great deal that
we can do in glibc to fix the underlying problem.

I guess we could add a check to glibc's preinst to catch this case and
prevent the new library being installed under a kernel where it won't
work.  The easiest thing would just be to disallow anything older than
2.4.0.  Writing a directed test to detect the presence of the actual bug
would also be possible, but that'd be a bit harder.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#222536: libc6: [ARM] ldd returns error on shlibs

2004-01-01 Thread Phil Blundell
tags 222536 unreproducible
thanks

On Tue, 2003-12-30 at 18:24, Adam C Powell IV wrote:
> Can you try to build illuminator, and see if the problem occurs?

I ran a build of illuminator in the unstable chroot on smackdown (the
user chroot, not the buildd one) and it worked fine.  So, I don't really
know what's going on here.

p.






Bug#222536: libc6: [ARM] ldd returns error on shlibs

2004-01-01 Thread Phil Blundell
tags 222536 unreproducible
thanks

On Tue, 2003-12-30 at 18:24, Adam C Powell IV wrote:
> Can you try to build illuminator, and see if the problem occurs?

I ran a build of illuminator in the unstable chroot on smackdown (the
user chroot, not the buildd one) and it worked fine.  So, I don't really
know what's going on here.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#219769: libc6-2.3.2.ds1-10 on ARM breaks modutils

2003-11-12 Thread Phil Blundell
on Sat, Nov 08, 2003 at 08:43:07PM -0800, Jeff Bailey wrote:
> I was hoping to wait until BenC (or another Sparc porter) came up with
> the solution for the sparc64 borkage.

Okay.  I've uploaded 2.3.2.ds1-10.0.1 as a binary NMU.  It seems to fix
the modutils problem.

p.





Bug#219769: libc6-2.3.2.ds1-10 on ARM breaks modutils

2003-11-12 Thread Phil Blundell
on Sat, Nov 08, 2003 at 08:43:07PM -0800, Jeff Bailey wrote:
> I was hoping to wait until BenC (or another Sparc porter) came up with
> the solution for the sparc64 borkage.

Okay.  I've uploaded 2.3.2.ds1-10.0.1 as a binary NMU.  It seems to fix
the modutils problem.

p.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#204930: libc6: similar error when using library mix

2003-09-02 Thread Phil Blundell
on Mon, Sep 01, 2003 at 01:07:57PM +0200, Josselin Mouette wrote:
> Interesting point.
> I'm still experiencing the same issues with regxpcom and gcc -ldl, but
> I'm afraid there is no such explanation on my system. LD_LIBRARY_PATH is
> unset, and I have no other copies of glibc lying around.

Thanks.  It sounds like you are suffering from a different problem
anyway.  I'll open a separate bug for this issue.

p.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]