In article <[EMAIL PROTECTED]> you write:
>
> The only thing the libreadlineg2 postinst does is ldconfig. I
>suggest you run ldconfig and see what error it complains about. This
>is most likely a dangling symlink. Removing the dangling symlink
>often cures the problem. If the ldconfig error
Ben Pfaff <[EMAIL PROTECTED]> said:
>Actually, the best way to install 2.0, AFAICT and IMHO, is to use the
>brand-new 2.0 install disks. You can find them in the usual archives
>in the disks-i386 distribution.
Would that be:
ftp://ftp.debian.org/pub/debian/hamm/hamm/disks-i386/current/
And t
Ben Pfaff <[EMAIL PROTECTED]> write:
> Actually, the best way to install 2.0, AFAICT and IMHO, is to use the
> brand-new 2.0 install disks. You can find them in the usual archives
> in the disks-i386 distribution.
That is unquestionably the best way, if the disks work on your
machine, howeve
I got A LOT of problems when trying to upgrade, my lack of
response the past few days is because I was fixing my box. :) Well, this
is the 'best' way to upgrade to glibc2, unfortunately, it is a very
undesirable solution.
Install 1.3.R6 fresh, THEN as dselect come
I got A LOT of problems when trying to upgrade, my lack of
response the past few days is because I was fixing my box. :) Well, this
is the 'best' way to upgrade to glibc2, unfortunately, it is a very
undesirable solution.
Install 1.3.R6 fresh, THEN as dselect comes up, cancel, a
Don Erickson <[EMAIL PROTECTED]> writes:
> I've been having a heck of a time upgrading a 1.3.1 bo (originally 1.2)
> system to hamm using autoup. Everything is installed up to libreadlineg2
> in the autoup script, then libreadlineg2's post install script bombs out
> and leaves the system in an es
Hello,
I've been having a heck of a time upgrading a 1.3.1 bo (originally 1.2)
system to hamm using autoup. Everything is installed up to libreadlineg2
in the autoup script, then libreadlineg2's post install script bombs out
and leaves the system in an essentially unusable state (nearly everythi
7 matches
Mail list logo
