[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Slink upgrade problems



Got a mixed slink/potatoe system.
Bought the CheapBytes 2.1 disks.

apt-cdrom add outputs;

Using CD-ROM mount point /cdrom/
Unmounting CD-ROM
Please insert a Disc in the drive and press any key Mounting CD-ROM
Identifying.. apt-cdrom: error in loading shared libraries
/usr/local/lib/libpthread.so.0: undefined symbol: __libc_opendir


  (/usr/local/lib/libpthreads.so.0 is a link to /lib/libpthreads.so.0
   to allow ./configure to run in /usr/local/src/gnome-xxx)




apt-get update outputs;

0% [Working] Err file:/cdrom/debian/dists/slink/ main/contrib Packages
  File not found
0% [Working] Ign file:/cdrom/debian/dists/slink/ main/contrib Release
33% [Working]apt-get: error in loading shared libraries
/usr/local/lib/libpthread.so.0: undefined symbol: __libc_opendir



Upgrading misc. packages give install-info errors;

(Reading database ... 40823 files and directories currently installed.)
Preparing to replace bison 1:1.25-11 (using bison_1.25-13.deb) ...
Unpacking replacement bison ...
install-info: No dir file specified; try --help for more information.
dpkg: warning - old post-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
install-info: No dir file specified; try --help for more information.
dpkg: error processing bison_1.25-13.deb (--install):
 subprocess new post-removal script returned error exit status 1
install-info: No dir file specified; try --help for more information.
dpkg: error while cleaning up:
 subprocess post-removal script returned error exit status 1
dpkg: error processing 2 (--install):
 cannot access archive: No such file or directory
Errors were encountered while processing:
 bison_1.25-13.deb
 2

Can anybody tell me what I've missed in the setups???

Thanks!
Mike

+--------------------------------------------------+
| Mike Nachlinger  (408) 446-9914  mnach@apres.org |
| Apres Ski Club   1-888-APRESGO   www.apres.org   |
+--------------------------------------------------+



Reply to: