peter green wrote:
>> It looks like you forgot to really Cc them BTW?
> I did but I resent the mail seperately to them afterwards.
Ah, found it. Looks like I'm not CC'ed on that anymore though. I think
"it used to not work otherwise" seems like a very good reason for me to
use the static lib. :-)
It looks like you forgot to really Cc them BTW?
I did but I resent the mail seperately to them afterwards.
So yeah, we'd need a libresolv.so that exports these:
lib/lib.o: In function `srv_lookup':
/home/wilmer/src/bitlbee/devel/lib/misc.c:483: undefined reference to
`__res_query'
/home/wi
peter green wrote:
>>> Does anyone know if there is any particular reason that bitlbee uses
>>> libresolv.a rather than libresolv.so ?
>> Yes; the fact that Ulrich Drepper thought it'd be a good idea to declare
>> this API private and unsupported, claiming it's for internal use only,
>> even though
Does anyone know if there is any particular reason that bitlbee uses
libresolv.a rather than libresolv.so ?
Yes; the fact that Ulrich Drepper thought it'd be a good idea to declare
this API private and unsupported, claiming it's for internal use only,
even though it's documented in variou
Hi,
I'm a bitlbee user on the armel arch and have encountered this bug.
While the 1.2.4-1+b1 upload of bitlbee has fixed the libc6 dependencies
on some arches, the dependency is still incorrect on armel:
The following packages have unmet dependencies:
bitlbee: Depends: libc6 (< 2.10) but 2.
On Wed, 21 Oct 2009, Wilmer van der Gaast wrote:
> Alok G Singh wrote:
> > The libc6 version available in sid is 2.10.1-1, but bitlbee demands a
> > version
> > strictly less than 2.10.
> >
> Note that I did not add that dependency myself. I have absolutely no
> idea where it comes from and why i
Alok G. Singh wrote:
> Rebuilding the package on a buildhost with the latest libc6 (2.10.1-1)
> installed creates a package that does not conflict libc6. No changes are
> required except the rebuild.
>
So that's what confuses me. Are you seeing this problem on amd64 or some
different arch? Because
Rebuilding the package on a buildhost with the latest libc6 (2.10.1-1)
installed creates a package that does not conflict libc6. No changes are
required except the rebuild.
--
Alok
QOTD:
"I'm on a seafood diet -- I see food and I eat it."
--
To UNSUBSCRIBE, email to debian-bugs-rc-r
Alok G Singh wrote:
> The libc6 version available in sid is 2.10.1-1, but bitlbee demands a version
> strictly less than 2.10.
>
Note that I did not add that dependency myself. I have absolutely no
idea where it comes from and why it's not affecting any other package.
If you or anyone else who rea
It appears that this problem arises due to bitlbee being built with an
older version of libc6. Specifically, the
/var/lib/dpkg/info/libc6.symbols file is where dpkg-shlibdeps gets the
conflict for the latest libc6.
HTH.
--
Alok
Platonic Shadow:
A nonsexual friendship with a member of the
Package: bitlbee
Version: 1.2.4-1
Severity: grave
Justification: renders package unusable
The libc6 version available in sid is 2.10.1-1, but bitlbee demands a version
strictly less than 2.10.
The error is:
bitlbee: Depends: libc6 (< 2.10) but 2.10.1-1 is installed
-- System Information:
Debian
11 matches
Mail list logo
