On Sun, 3 May 1998, Bob Nielsen wrote:
On 3 May 1998, Torsten Hilbrich wrote:
Bob Nielsen [EMAIL PROTECTED] writes:
midnight commander now requires e2fsligsg, but when I tried installing
that, it won't install because of a conflict with e2fsprogs. The packages
file says it
-BEGIN PGP SIGNED MESSAGE-
On 3 May 1998, Torsten Hilbrich wrote:
The latter First force the removal of e2fsprogs (IIRC
--force-remove-essential) and then install e2fslibsg. You need a
package named comerr2g too.
No. comerr2g and e2fslibsg are obsolete and should be removed from the
Bob Nielsen [EMAIL PROTECTED] writes:
midnight commander now requires e2fsligsg, but when I tried installing
that, it won't install because of a conflict with e2fsprogs. The packages
file says it conflicts with e2fsprogs = 1.10-7. but I have 1.10-15
installed. e2fsprogs says it conflicts
On 3 May 1998, Torsten Hilbrich wrote:
Bob Nielsen [EMAIL PROTECTED] writes:
midnight commander now requires e2fsligsg, but when I tried installing
that, it won't install because of a conflict with e2fsprogs. The packages
file says it conflicts with e2fsprogs = 1.10-7. but I have
midnight commander now requires e2fsligsg, but when I tried installing
that, it won't install because of a conflict with e2fsprogs. The packages
file says it conflicts with e2fsprogs = 1.10-7. but I have 1.10-15
installed. e2fsprogs says it conflicts with e2fslibsg (no version
listed). mc still
5 matches
Mail list logo
