Re: upgrading base-files problem
Not sure if this is directly related to the other errors but libc6 and base-files are unhappy with each other. Here's the error: Preparing to replace libc6 2.3.2.ds1-19 (using .../libc6_2.3.2.ds1-19.0.0.1.pure64_amd64.deb) ... Unpacking replacement libc6 ... dpkg: error processing /afs/hackish.org/data/debian-amd64/pure64/pool/unstable/main/amd64/g/glibc/libc6_2.3.2.ds1-19.0.0.1.pure64_amd64.deb (--unpack): trying to overwrite `/usr/lib64', which is also in package base-files Errors were encountered while processing: /afs/hackish.org/data/debian-amd64/pure64/pool/unstable/main/amd64/g/glibc/libc6_2.3.2.ds1-19.0.0.1.pure64_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) When I did --force-overwrite it works, giving these warnings: Preparing to replace libc6 2.3.2.ds1-19 (using .../libc6_2.3.2.ds1-19.0.0.1.pure64_amd64.deb) ... Unpacking replacement libc6 ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/lib64', which is also in package base-files dpkg - warning, overriding problem because --force enabled: trying to overwrite `/lib64', which is also in package base-files Setting up libc6 (2.3.2.ds1-19.0.0.1.pure64) ... Thanks, -Peter
Re: upgrading base-files problem
Lorenzo Milesi <[EMAIL PROTECTED]> writes: >> That would be a bug of xfree86-driver-synaptics and nvu. If we even >> have a usr/X11R6/lib64 link then it belongs in the xfree86 >> package. The link in base-files is just a hack because it is easier to >> patch. > > should I open a bug for this on xfree86-driver-synaptics? > > I tried removing the package, the installation of base-files went fine. Yes please. MfG Goswin
Re: upgrading base-files problem
> That would be a bug of xfree86-driver-synaptics and nvu. If we even > have a usr/X11R6/lib64 link then it belongs in the xfree86 > package. The link in base-files is just a hack because it is easier to > patch. should I open a bug for this on xfree86-driver-synaptics? I tried removing the package, the installation of base-files went fine.
Re: upgrading base-files problem
Lorenzo Milesi <[EMAIL PROTECTED]> writes: >> I just uploaded a patched base-files_3.1.1.0.0.1.pure64_amd64.deb >> to alioth. > > yesterday evening I was trying to do a dist-upgrade but the base-files > package won't install. it says it's going to try to overwrite > /usr/X11R6/lib64 which is in xfree86-driver-synaptics package. > > it was previously giving me similar error due to nvu package. I tried > removing it, but as you can see the problem just moved. That would be a bug of xfree86-driver-synaptics and nvu. If we even have a usr/X11R6/lib64 link then it belongs in the xfree86 package. The link in base-files is just a hack because it is easier to patch. For anyone feeling lucky try: ~goswin-guest/done/glibc-sid/ and ~goswin-guest/done/base-files-sid/ MfG Goswin
Re: upgrading base-files problem
> I just uploaded a patched base-files_3.1.1.0.0.1.pure64_amd64.deb > to alioth. yesterday evening I was trying to do a dist-upgrade but the base-files package won't install. it says it's going to try to overwrite /usr/X11R6/lib64 which is in xfree86-driver-synaptics package. it was previously giving me similar error due to nvu package. I tried removing it, but as you can see the problem just moved.
Re: upgrading base-files problem
Frederik Schueler <[EMAIL PROTECTED]> writes: > Hi, > > you need to create the /lib64 -> /lib symlink. > > I just uploaded a patched base-files_3.1.1.0.0.1.pure64_amd64.deb > to alioth. > > Greetings > Frederik Schueler Args, that was supposed to happen only after/with the glibc changed to take over the link. MfG Goswin
Re: upgrading base-files problem
> > now I can no longer run simple commands! eg I can't ls > I'm in the same situation, can neither login, execute "su"... NOTHING! Today's base-files update removed the /lib64 symlink, which isn't too healthy because each binary has /lib64/ld-linux-x86-64.so.2 hardcoded as its interpreter. You can still run binaries using /lib/ld-linux-x86-64.so.2 /usr/bin/whatever A good one to try is /lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64 which cures the problem. Regards, Daniel.
Re: upgrading base-files problem
Hi, you need to create the /lib64 -> /lib symlink. I just uploaded a patched base-files_3.1.1.0.0.1.pure64_amd64.deb to alioth. Greetings Frederik Schueler On Wed, Dec 15, 2004 at 09:08:16AM +, rdocksey wrote: > I've just apt-get update/upgrade and upon processing base-files.. > > (Reading database ... 39651 files and directories currently installed.) > Preparing to replace base-files 3.1.0.0.1.pure64 (using > .../base-files_3.1.1_amd64.deb) ... > Unpacking replacement base-files ... > dpkg (subprocess): failed to exec rm for cleanup: No such file or > directory > dpkg: error while cleaning up: > subprocess rm cleanup returned error exit status 2 > Could not exec dpkg! > E: Sub-process /usr/bin/dpkg returned an error code (100) > > now I can no longer run simple commands! eg I can't ls > (echo * works) or ssh in to the box from another machine. some sample > error messages... > >koori:/usr/src/local# apt-get >-bash: /usr/bin/apt-get: No such file or directory > >koori:/bin# file ls >-bash: /usr/bin/file: No such file or directory > >[EMAIL PROTECTED]:~$ ssh koori >/bin/bash: No such file or directory >Connection to koori closed. > > I have one ssh session open to this box at the minute and am wondering > if there's any way I can repair things ... it's a headless machine > which I think means I'm soon to be lumping monitors and keyboards around > my flat... > > any help, greatly appreciated. > R. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- ENOSIG pgpKFF0e3gOv4.pgp Description: PGP signature
Re: upgrading base-files problem
> now I can no longer run simple commands! eg I can't ls I'm in the same situation, can neither login, execute "su"... NOTHING!
upgrading base-files problem
hi I've just apt-get update/upgrade and upon processing base-files.. (Reading database ... 39651 files and directories currently installed.) Preparing to replace base-files 3.1.0.0.1.pure64 (using .../base-files_3.1.1_amd64.deb) ... Unpacking replacement base-files ... dpkg (subprocess): failed to exec rm for cleanup: No such file or directory dpkg: error while cleaning up: subprocess rm cleanup returned error exit status 2 Could not exec dpkg! E: Sub-process /usr/bin/dpkg returned an error code (100) now I can no longer run simple commands! eg I can't ls (echo * works) or ssh in to the box from another machine. some sample error messages... koori:/usr/src/local# apt-get -bash: /usr/bin/apt-get: No such file or directory koori:/bin# file ls -bash: /usr/bin/file: No such file or directory [EMAIL PROTECTED]:~$ ssh koori /bin/bash: No such file or directory Connection to koori closed. I have one ssh session open to this box at the minute and am wondering if there's any way I can repair things ... it's a headless machine which I think means I'm soon to be lumping monitors and keyboards around my flat... any help, greatly appreciated. R.
