Re: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Goswin von Brederlow
Eric Cranley <[EMAIL PROTECTED]> writes:

> You are my savior. Thank you. Now before I continue with the upgrade I
> should have done two months ago, are there any other major package conflicts
> I should be aware of? I installed the system as sid in the first week of
> December. I pinned the system to testing last week, and this morning's
> problem was the first upgrade I tried. Here's what apt-get upgrade wants to
> do:
>
> The following packages will be upgraded:
>   apache apache-common apache-utils apt-utils console-common console-data
>   console-tools cpio dash dialog discover1 discover1-data dselect exim4
>   exim4-base exim4-config exim4-daemon-light gettext-base grub initrd-tools
>   initscripts libconsole libcupsys2-gnutls10 libdb3 libdb4.2 libdbi-perl
>   libdiscover1 libgc1 libgcc1 libkrb53 libltdl3 libmysqlclient12
>   libsigc++-1.2-5c102 login mailx mdadm module-init-tools modutils
>   mysql-client mysql-common mysql-server netbase passwd perl perl-base
>   perl-modules php4 rdate samba samba-common sysv-rc sysvinit webmin
>   webmin-inetd webmin-samba
> The following packages will be DOWNGRADED:
>   e2fslibs e2fsprogs libacl1 libattr1 libblkid1 libbz2-1.0 libcomerr2
>   libgcrypt11 libgnutls11 liblzo1 libreadline4 libss2 libtasn1-2 libuuid1
>   mount procps util-linux zlib1g
> 55 upgraded, 0 newly installed, 18 downgraded, 0 to remove and 1 not
> upgraded.
>
> Is there anything I should really becareful of or install in a specific
> order?
> Thanks again for your help.

Nothing I'm aware of or as catastrophic as the libc6/base-files
problem that basically kills the system. Please note that I'm running
sid on my main system with sarge chroots for tests and buildd though.

If something doesn't work you can always go back to the sid versions
(lower the pin below 1000 then).

MfG
Goswin

PS: Sarge needs users to find any remaining problems. The more the
better. So thanks for doing it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



RE: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Eric Cranley
You are my savior. Thank you. Now before I continue with the upgrade I
should have done two months ago, are there any other major package conflicts
I should be aware of? I installed the system as sid in the first week of
December. I pinned the system to testing last week, and this morning's
problem was the first upgrade I tried. Here's what apt-get upgrade wants to
do:

The following packages will be upgraded:
  apache apache-common apache-utils apt-utils console-common console-data
  console-tools cpio dash dialog discover1 discover1-data dselect exim4
  exim4-base exim4-config exim4-daemon-light gettext-base grub initrd-tools
  initscripts libconsole libcupsys2-gnutls10 libdb3 libdb4.2 libdbi-perl
  libdiscover1 libgc1 libgcc1 libkrb53 libltdl3 libmysqlclient12
  libsigc++-1.2-5c102 login mailx mdadm module-init-tools modutils
  mysql-client mysql-common mysql-server netbase passwd perl perl-base
  perl-modules php4 rdate samba samba-common sysv-rc sysvinit webmin
  webmin-inetd webmin-samba
The following packages will be DOWNGRADED:
  e2fslibs e2fsprogs libacl1 libattr1 libblkid1 libbz2-1.0 libcomerr2
  libgcrypt11 libgnutls11 liblzo1 libreadline4 libss2 libtasn1-2 libuuid1
  mount procps util-linux zlib1g
55 upgraded, 0 newly installed, 18 downgraded, 0 to remove and 1 not
upgraded.

Is there anything I should really becareful of or install in a specific
order?
Thanks again for your help.

-Original Message-
From: Goswin von Brederlow [mailto:[EMAIL PROTECTED] 
Sent: Sunday, February 20, 2005 3:12 PM
To: Eric Cranley
Cc: debian-amd64@lists.debian.org
Subject: Re: FW: anybody help me? dependency problem: no way back???

Eric Cranley <[EMAIL PROTECTED]> writes:

> I thought I had already upgraded base-files and libc6 after the move. I'll
> give your suggestion a try. I need to reinstall base-files as well (I
> removed it in a spectacular display of stupidity.) I can't even login at
the
> console right now, hence the part about using a live cd. I'll definitely
> write up a report on how I fixed it if I'm successful.

Removing the old base-files removed the /lib64 -> /lib link. That
means all dynamically linked binaries fail to find the ld.

/lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64

of from a live CD just "ln -s /lib /mountpoint/lib64".

After that the system should work again and reinstalling libc6 will
get the /lib64 link owned by libc6 correctly.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Goswin von Brederlow
Erik Norman <[EMAIL PROTECTED]> writes:

> The system has been running for about 48 hours now, I did not think of
> upgrading now, since I was still installing and configuring all the
> programs I need/want.
>
> Since I am newbie to Debian (I have used Fedora before) there is still
> much I must learn.

Then how did you get the libc6 and libc6-dev versions mixed up?
Apt-get should never have let you do this to your system without
sufficient force options (and you would know if you used them) so I'm
quite baffeled.

There probably is some plausible explaination I'm just not
seeing. This is one of those "This should never happen" bugs that do
happen non the less sometimes.

Anyway, I hope you got it fixed now.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Goswin von Brederlow
Eric Cranley <[EMAIL PROTECTED]> writes:

> I thought I had already upgraded base-files and libc6 after the move. I'll
> give your suggestion a try. I need to reinstall base-files as well (I
> removed it in a spectacular display of stupidity.) I can't even login at the
> console right now, hence the part about using a live cd. I'll definitely
> write up a report on how I fixed it if I'm successful.

Removing the old base-files removed the /lib64 -> /lib link. That
means all dynamically linked binaries fail to find the ld.

/lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64

of from a live CD just "ln -s /lib /mountpoint/lib64".

After that the system should work again and reinstalling libc6 will
get the /lib64 link owned by libc6 correctly.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



RE: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Eric Cranley
I thought I had already upgraded base-files and libc6 after the move. I'll
give your suggestion a try. I need to reinstall base-files as well (I
removed it in a spectacular display of stupidity.) I can't even login at the
console right now, hence the part about using a live cd. I'll definitely
write up a report on how I fixed it if I'm successful.

-Original Message-
From: Goswin von Brederlow [mailto:[EMAIL PROTECTED] 
Sent: Sunday, February 20, 2005 1:27 PM
To: debian-amd64@lists.debian.org
Subject: Re: FW: anybody help me? dependency problem: no way back???

Eric Cranley <[EMAIL PROTECTED]> writes:

> Forgot to CC this to the list.
>
> -Original Message-
> From: Eric Cranley 
> Sent: Sunday, February 20, 2005 11:54 AM
> To: 'Erik Norman'
> Subject: RE: anybody help me? dependency problem: no way back???
>
> Looks like a conflict over /usr/lib64. I'm having the same problem right
> now, but between libc6 and base-files, and I've hosed my system. (I'm sure
I
> just made a large majority of the list groan and/or laugh at me.) My
> understanding is that you can force the install with dpkg, using the
> following:

Then you either didn't upgrade in a long time (and we warned about
this) or you used force-overwrite on base-files during the short time
libc6 and base-files where out of sync the same long time ago or
downgraded or something.

I knew moving the link would create problems. There just isn't a way
to make it foolproof with dpkg. Lets hope you are the last stragler.

MfG
Goswin

PS: I recommend you reinstall libc6 and then dist-upgrade to be on the
save side.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Erik Norman
The system has been running for about 48 hours now, I did not think of
upgrading now, since I was still installing and configuring all the
programs I need/want.

Since I am newbie to Debian (I have used Fedora before) there is still
much I must learn.

Thanks

Erik

On Sun, 2005-02-20 at 19:24 +0100, Goswin von Brederlow wrote:
> Eric Cranley <[EMAIL PROTECTED]> writes:
> 
> > Forgot to CC this to the list.
> >
> > -Original Message-
> > From: Eric Cranley 
> > Sent: Sunday, February 20, 2005 11:54 AM
> > To: 'Erik Norman'
> > Subject: RE: anybody help me? dependency problem: no way back???
> >
> > Looks like a conflict over /usr/lib64. I'm having the same problem right
> > now, but between libc6 and base-files, and I've hosed my system. (I'm sure I
> > just made a large majority of the list groan and/or laugh at me.) My
> > understanding is that you can force the install with dpkg, using the
> > following:
> 
> Then you either didn't upgrade in a long time (and we warned about
> this) or you used force-overwrite on base-files during the short time
> libc6 and base-files where out of sync the same long time ago or
> downgraded or something.
> 
> I knew moving the link would create problems. There just isn't a way
> to make it foolproof with dpkg. Lets hope you are the last stragler.
> 
> MfG
> Goswin
> 
> PS: I recommend you reinstall libc6 and then dist-upgrade to be on the
> save side.
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: FW: anybody help me? dependency problem: no way back??? SOLVED

2005-02-20 Thread Erik Norman
I have resolved the problem

I used the Synaptic Package Manager to remove the package with the
broken dependency, then I removed xmms-kde and xmms.
Upgrade (without problems)
Install xmms-kde and xmms and all other packages which were removed at
the same time (kde kdeaddons kdenetwork kicker-applets kopete
mplayer-amd64 xmp-xmms) -> no problems.

apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Problem solved.


Thanx for any help!




On Sun, 2005-02-20 at 12:40 -0500, Eric Cranley wrote:
> Forgot to CC this to the list.
> 
> -Original Message-
> From: Eric Cranley 
> Sent: Sunday, February 20, 2005 11:54 AM
> To: 'Erik Norman'
> Subject: RE: anybody help me? dependency problem: no way back???
> 
> Looks like a conflict over /usr/lib64. I'm having the same problem right
> now, but between libc6 and base-files, and I've hosed my system. (I'm sure I
> just made a large majority of the list groan and/or laugh at me.) My
> understanding is that you can force the install with dpkg, using the
> following:
> 
> dpkg - dpkg --force-overwrite -i
> /var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb
> 
> I would check elsewhere before doing this though, because my intranet server
> will tell you that I've hosed this before.
> 
> For anyone on the list that's dealt with this, it this suggested solution
> correct? Also, I have a system where some idiot (me) temporarily uninstalled
> base-files in order to upgrade libc6. If I did this same command from an
> ubuntu AMD64 live cd for libc6 and base-files, but with the -root= option,
> fix the problem for me? Thanks.
> 
> -Original Message-
> From: Erik Norman [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, February 20, 2005 11:29 AM
> To: debian-amd64
> Subject: anybody help me? dependency problem: no way back???
> 
> I made an upgrade with atp-get after having installed some packages.
> I got some dependency problems, so I tried
> 
> fzr:/# apt-get check
> Reading Package Lists... Done
> Building Dependency Tree... Done
> You might want to run `apt-get -f install' to correct these.
> The following packages have unmet dependencies:
>   libc6-dev: Depends: libc6 (= 2.3.2.ds1-20.0.0.1.pure64) but
> 2.3.2.ds1-20 is installed
> E: Unmet dependencies. Try using -f.
> 
> fzr:/# apt-get install -f
> Reading Package Lists... Done
> Building Dependency Tree... Done
> Correcting dependencies... Done
> The following extra packages will be installed:
>   libc6
> Suggested packages:
>   glibc-doc
> The following packages will be upgraded:
>   libc6
> 1 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
> 1 not fully installed or removed.
> Need to get 0B/4318kB of archives.
> After unpacking 0B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> (Reading database ... 87507 files and directories currently installed.)
> Preparing to replace libc6 2.3.2.ds1-20
> (using .../libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb) ...
> Unpacking replacement libc6 ...
> dpkg: error
> processing /var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb
> (--unpack):
>  trying to overwrite `/usr/lib64', which is also in package xmms-kde
> Errors were encountered while processing:
>  /var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> 
> The problem is that I can't remove xmms-kd3, but I can't force any
> installation.
> HELP!
> 
> Erik
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Goswin von Brederlow
Eric Cranley <[EMAIL PROTECTED]> writes:

> Forgot to CC this to the list.
>
> -Original Message-
> From: Eric Cranley 
> Sent: Sunday, February 20, 2005 11:54 AM
> To: 'Erik Norman'
> Subject: RE: anybody help me? dependency problem: no way back???
>
> Looks like a conflict over /usr/lib64. I'm having the same problem right
> now, but between libc6 and base-files, and I've hosed my system. (I'm sure I
> just made a large majority of the list groan and/or laugh at me.) My
> understanding is that you can force the install with dpkg, using the
> following:

Then you either didn't upgrade in a long time (and we warned about
this) or you used force-overwrite on base-files during the short time
libc6 and base-files where out of sync the same long time ago or
downgraded or something.

I knew moving the link would create problems. There just isn't a way
to make it foolproof with dpkg. Lets hope you are the last stragler.

MfG
Goswin

PS: I recommend you reinstall libc6 and then dist-upgrade to be on the
save side.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



FW: anybody help me? dependency problem: no way back???

2005-02-20 Thread Eric Cranley
Forgot to CC this to the list.

-Original Message-
From: Eric Cranley 
Sent: Sunday, February 20, 2005 11:54 AM
To: 'Erik Norman'
Subject: RE: anybody help me? dependency problem: no way back???

Looks like a conflict over /usr/lib64. I'm having the same problem right
now, but between libc6 and base-files, and I've hosed my system. (I'm sure I
just made a large majority of the list groan and/or laugh at me.) My
understanding is that you can force the install with dpkg, using the
following:

dpkg - dpkg --force-overwrite -i
/var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb

I would check elsewhere before doing this though, because my intranet server
will tell you that I've hosed this before.

For anyone on the list that's dealt with this, it this suggested solution
correct? Also, I have a system where some idiot (me) temporarily uninstalled
base-files in order to upgrade libc6. If I did this same command from an
ubuntu AMD64 live cd for libc6 and base-files, but with the -root= option,
fix the problem for me? Thanks.

-Original Message-
From: Erik Norman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, February 20, 2005 11:29 AM
To: debian-amd64
Subject: anybody help me? dependency problem: no way back???

I made an upgrade with atp-get after having installed some packages.
I got some dependency problems, so I tried

fzr:/# apt-get check
Reading Package Lists... Done
Building Dependency Tree... Done
You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:
  libc6-dev: Depends: libc6 (= 2.3.2.ds1-20.0.0.1.pure64) but
2.3.2.ds1-20 is installed
E: Unmet dependencies. Try using -f.

fzr:/# apt-get install -f
Reading Package Lists... Done
Building Dependency Tree... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libc6
Suggested packages:
  glibc-doc
The following packages will be upgraded:
  libc6
1 upgraded, 0 newly installed, 0 to remove and 59 not upgraded.
1 not fully installed or removed.
Need to get 0B/4318kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 87507 files and directories currently installed.)
Preparing to replace libc6 2.3.2.ds1-20
(using .../libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb) ...
Unpacking replacement libc6 ...
dpkg: error
processing /var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb
(--unpack):
 trying to overwrite `/usr/lib64', which is also in package xmms-kde
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.3.2.ds1-20.0.0.1.pure64_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


The problem is that I can't remove xmms-kd3, but I can't force any
installation.
HELP!

Erik


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]