* Lucas Nussbaum (lu...@debian.org) wrote:
> (This might be related to the fact that I use a "user" login on my build
> machine)
Yes, it is.
We could possibly remove those tests, but I'm not really thrilled with
that idea. I'm not sure if it'd be at all sensible to try and write
something to che
Greetings,
It looks like the referenced bug in python-central (#424906) was
closed out over a month ago. If that's been fixed can we get a
rebuild of player/stage on affected platforms? Looks like at least
amd64, mips, m68k, powerpc, s390.
Thanks,
Stephen
sign
* Giuseppe Sacco ([EMAIL PROTECTED]) wrote:
> Now I understood the problem and will prepare a fix in a few days. At
> the same time I wrote to the maintainer asking if he would like to
> orphan this package; I would gladly adopt it.
Erm, I don't recall seeing that message. libnss-ldap and libpam-
severity 400448 wishlist
reassign 400448 gnutls
thanks
* Mitar ([EMAIL PROTECTED]) wrote:
> Package: libnss-ldap
[...]
> When I configure CA directory with "tls_cacertdir" configuration option
> in /etc/libnss.conf file NSS querying (for example "finger mitar") takes
> very long (about 20 seconds
* Scott Anderson ([EMAIL PROTECTED]) wrote:
> Setting up nfs-common (1.0.7-12) ...
> Adding system user `statd' with uid 107...
> Adding new user `statd' (107) with group `nogroup'.
> useradd: /home/devel/openldap/openldap2-2.1.30/libraries/liblber/io.c:161:
> ber_free_buf: Assertion
> `((ber)->be
* Jan Evert van Grootheest ([EMAIL PROTECTED]) wrote:
> Using these settings, udevd still reports about the ldap server being
> unreachable.
Right, that's expected, and perfectly reasonable.
> But the timeouts are now such that bootup is basically a snap. Each
> search takes about 1 second.
Go
* Stephen Frost ([EMAIL PROTECTED]) wrote:
> Right, with the defaults... The idea was to reduce those. I've played
> with this some in preparation of 251-6. Try:
> reconn_maxconntries = 2
> reconn_tries = 1
> reconn_sleeptime = 1
> reconn_maxsleeptime = 8
I guess I cou
* Jan Evert van Grootheest ([EMAIL PROTECTED]) wrote:
> I've tried it.
I'm not sure you have...
> During boot udevd attempts to resolve a few groups (group scanner, group
> scanner, group scanner, group nvram, user tss, group tss, group fuse,
> group rdma, group rdma), as far as I understand th
* Steinar H. Gunderson ([EMAIL PROTECTED]) wrote:
> On Tue, Oct 03, 2006 at 11:28:34PM -0700, Steve Langasek wrote:
> > Can we just fix libnss-ldap already to use a sensible default bind policy,
> > please?
>
> Sure, I could do that (removing the boot-time workarounds), assuming the
> maintainer d
* Julien Danjou ([EMAIL PROTECTED]) wrote:
> Severity: grave
Not every bug in libnss-ldap is 'grave', not even ones which make NSS
start having problems.
> I tried to upgrade to libnss-ldap 251-5 and the upgrade failed with a
> beautiful error:
>
> Setting up libnss-ldap (251-5) ...
> Can't loca
* Vedran Fura? ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > What do your configs look like,
What are the permissions on your libnss-ldap.conf?
> But the problem is not in login(1), if I log in with nscd and then disable
> it *every* started app will crash immediately wit
* Sjoerd Simons ([EMAIL PROTECTED]) wrote:
> I've rebooted one of the systems with the ipv6 module blacklisted. After that
> it still shows exactly the same behaviour (identicaly trace, just the ipv6
> addresses replaced by ipv4 addresses)...
Hmm, ok.
> > Can you check if there's a file in /var/l
* Sjoerd Simons ([EMAIL PROTECTED]) wrote:
> On Sun, Jul 02, 2006 at 08:00:22PM -0400, Stephen Frost wrote:
> > * Vedran Fura?? ([EMAIL PROTECTED]) wrote:
> > > After upgrade to version 251 I can't login as a user in ldap and even as
> > > root which is a loc
severity 376426 serious
tags +moreinfo
thanks
* Vedran Fura?? ([EMAIL PROTECTED]) wrote:
> After upgrade to version 251 I can't login as a user in ldap and even as
> root which is a local user. Login process dies with SIGPIPE.
> It only happens without nscd.
What do your configs look like, what v
* Michael Biebl ([EMAIL PROTECTED]) wrote:
> > case here? Also, have you tried waiting it out? Each request would end
> > up taking about 2 minutes, but technically it *should* give up
> > eventually..
>
> I waited for something like 10min without success. But honestly this
> wouldn't be a prope
* Gasper Zejn ([EMAIL PROTECTED]) wrote:
> It does not want to time out. After each timeout, it just tries again and
> again.
Please try 251-5 and see if it helps.
Thanks,
Stephen
signature.asc
Description: Digital signature
* Gasper Zejn ([EMAIL PROTECTED]) wrote:
> [pid 5186] connect(7, {sa_family=AF_INET,
> sin_port=htons(389), sin_addr=inet_addr("10.10.7.99")}, 16)
> = -1 ENETUNREACH (Network is unreachable)
>
> clearly means network is not setup properly to be able to
> reach LDAP server, since there's no mat
* Gasper Zejn ([EMAIL PROTECTED]) wrote:
> Dne sobota 24 junij 2006 17:04 ste napisali:
> > Do you have a reasonably complete /etc/passwd and
> > /etc/shadow files for the local accounts?
>
> Yes, I am actually using local account for daily work.
>
> > Also, have you actually waited it out? Even
* Michael Biebl ([EMAIL PROTECTED]) wrote:
> Marco d'Itri wrote:
> > On Jun 24, Stephen Frost <[EMAIL PROTECTED]> wrote:
> >
> >> It's simply not possible for libnss-ldap to provide a correct answer
> >> before networking or the slapd daemon has
* Gasper Zejn ([EMAIL PROTECTED]) wrote:
> My nsswitch.conf:
>
> passwd: compat ldap
> group: compat ldap
> shadow: compat ldap
>
> Other lines don't have ldap.
>
> I have no custom udev rules.
Do you have a reasonably complete /etc/passwd and /etc/shadow files for
the
* Gasper Zejn ([EMAIL PROTECTED]) wrote:
> After I installed libnss-ldap, udevd stalled at startup,
> waiting for libnss-ldap, which can't connect to a remote LDAP
> server, since networking is not yet set up at that time.
This is being discussed in #375077. libnss-ldap can be configured to
giv
* Marco d'Itri ([EMAIL PROTECTED]) wrote:
> On Jun 24, maximilian attems <[EMAIL PROTECTED]> wrote:
>
> > > udev does not even know about LDAP, it just uses the libc interface.
> > > What do you think it should do?
> > > Possibly without horrible layering violations.
> > the errors happen when the
* Luk Claes ([EMAIL PROTECTED]) wrote:
> Attached the patch for the version I intend to upload. Please respond if
> you don't want this NMU to happen, if you are working yourself on a
> patch or if you think that the attached patch won't work.
Geez, seems like we just did this. Oh well, looks alr
* Luk Claes ([EMAIL PROTECTED]) wrote:
> Yes, I did test it. Well, I think they are needed as they are used all
> over in the autotools.mk, the only way to get rid of them is to delete
> all DEB_AUTO_UPDATE lines, though I'm not sure if it would behave
> correctly...
We don't want to get rid of th
* Luk Claes ([EMAIL PROTECTED]) wrote:
> Attached the patch for the version I intend to upload. Please respond if
> you don't want this NMU to happen, if you are working yourself on a
> patch or if you think that the attached patch won't work.
I don't see any obvious reason why it won't work. I t
severity 327562 normal
done
hahahahhahaha
Enjoy,
Stephen
signature.asc
Description: Digital signature
* Frank Lichtenheld ([EMAIL PROTECTED]) wrote:
> On Mon, Apr 25, 2005 at 10:00:33AM -0400, Stephen Frost wrote:
> > Just following up for those playing along at home. libnss-ldap and
> > libpam-ldap need to be linked against the same ldap (either 'ldap' or
> >
reassign 306258 libpam-ldap
retitle 306258 libpam-ldap needs to be linked against ldap_r
thanks
Greetings,
Just following up for those playing along at home. libnss-ldap and
libpam-ldap need to be linked against the same ldap (either 'ldap' or
'ldap_r'). I thought I had done this for both
* Martin Zobel-Helas ([EMAIL PROTECTED]) wrote:
> i am not sure if i overlooked your answer to my last mail. Is there anything
> we
> can help on #232810? As we are going to freeze realy soon now (looks like both
> ends of the toolchain are fixed by now), i fear that openmosix will be
> dropped
* Otavio Salvador ([EMAIL PROTECTED]) wrote:
> Sure. I know it. But the problem doesn't look be there.
>
> Looks like curl links about .so file and not .so.
Sounds like it's build system is busted then.
Stephen
signature.asc
Description: Digital signature
* Otavio Salvador ([EMAIL PROTECTED]) wrote:
> || On Wed, 9 Feb 2005 14:58:39 -0500
> || Stephen Frost <[EMAIL PROTECTED]> wrote:
>
> sf> * Otavio Salvador ([EMAIL PROTECTED]) wrote:
> >> Then you should contact curl maintainer. He included libldap2-dev as
> >
* Otavio Salvador ([EMAIL PROTECTED]) wrote:
> Then you should contact curl maintainer. He included libldap2-dev as
> suggestion to have support to ldap on it. Take a look.
>
> He argued about .so file missed on libldap2 package and there we
> really don't have one. I though you need to provide th
* Domenico Andreoli ([EMAIL PROTECTED]) wrote:
> doh!
Uhhh, the .so's are supposted to be symlinks in the -dev package to the
real .so.x files, which in fact is what they look like on *my* system
anyway, so I've really got no idea what the issue is...
Stephen
> - Forwarded message fr
* Matthijs Mohlmann ([EMAIL PROTECTED]) wrote:
> We are running debian sarge on some of our servers now and are getting
> data and index corruption (every few weeks). On different servers
> (configured the same) we experience those problems. I think it is
> openldap that causes this problem because
* Pietro Abate ([EMAIL PROTECTED]) wrote:
> I'm using ldap together with kerberos (that works ok). After installing
> the following packages libnss-ldap libdb3-util libsasl7 I get
Something about that doesn't add up- why are you installing libsasl7?
Everything should be using libsasl2. Can you pl
35 matches
Mail list logo
