If anyone is going through this problem, hopefully my resolution
might help them - it looks like in the upgrade of libc-dev, something
got hosed. The interim solution to the problem while I fixed the
install was to set the LD_LIBRARY_PATH=/lib, as it seemed that the
problem was arising fro
after further digging, I've found this thread on the debian glibc list:
http://lists.debian.org/debian-glibc/2005/03/msg00145.html
I'll be looking into how I can fix the problem - their suggested fix
does not work.
-lev
On Aug 17, 2007, at 2:51 PM, Lev Lvovsky wrote:
Ron,
On Aug 17, 2007
Ron,
On Aug 17, 2007, at 2:42 PM, Ron Johnson wrote:
If I indeed am running a mixed system, how can I switch entirely
to the
etch release?
Eliminate all Sarge references from sources.list.
my sources.list is as follows:
deb http://security.debian.org etch/updates main contrib non-free
deb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/07 16:27, Lev Lvovsky wrote:
> [sorry for the multiple replies]
>
> On Aug 17, 2007, at 2:21 PM, Ron Johnson wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/17/07 16:16, Lev Lvovsky wrote:
>>> replying to my initial
[sorry for the multiple replies]
On Aug 17, 2007, at 2:21 PM, Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/07 16:16, Lev Lvovsky wrote:
replying to my initial post -
I just subbed for the purposes of finding out about this issue - I'm
assuming that if this was wi
replying to myself -
I just subbed for the purposes of finding out about this issue - I'm
assuming that if this was widespread, I would've heard a "yeah, it's
being worked on" sort of reply.
Given that - can anyone recommend even a place to start from as far
as this problem goes? It seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/07 16:16, Lev Lvovsky wrote:
> replying to my initial post -
>
> I just subbed for the purposes of finding out about this issue - I'm
> assuming that if this was widespread, I would've heard a "yeah, it's
> being worked on" sort of reply.
>
replying to my initial post -
I just subbed for the purposes of finding out about this issue - I'm
assuming that if this was widespread, I would've heard a "yeah, it's
being worked on" sort of reply.
Given that - can anyone recommend even a place to start from as far
as this problem goes?
Hello, it looks like after running apt-get upgrade on my box, my
glibc environment has been broken:
Updated the following:
Get:1 http://http.us.debian.org stable/main libc6-dev
2.3.6.ds1-13etch2 [2717kB]
Get:2 http://http.us.debian.org stable/main libc6 2.3.6.ds1-13etch2
[4699kB]
Get:3 http
9 matches
Mail list logo