View previous topic :: View next topic |
Author |
Message |
djand n00b
Joined: 09 Jul 2002 Posts: 13
|
Posted: Thu May 01, 2003 8:40 pm Post subject: Can't emerge tclx |
|
|
Gentoo noobie here so be gentle. Long time linux/Unix though.
emerge -u tclx
>>> emerge (1 of 1) dev-tcltk/tclx-8.3-r1 to /
>>> md5 ;-) tclx8.3.tar.gz
>>> md5 ;-) tcl8.4.2-src.tar.gz
>>> md5 ;-) tk8.4.2-src.tar.gz
....
This eventually fails with an error about version problems:
Error: version conflict for package "Tcl": have 8.4, need 8.3
(while initializing TclX)
When I look at the online package database this is listed:
tcl 8.3.4
tk 8.3.4r1
Any solutions to suggest? I deleted the tcl and tk 8.4* packages and did
emerge portage
emerge sync
The 8.4* packages come back. I can't finish my 'emerge -e world' because of this error. Is this a problem with the package dependency structure? If so then how would one go about telling emerge to ignore tclx and finish my world update? |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Fri May 02, 2003 3:33 am Post subject: |
|
|
Perhaps it is related to this. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
djand n00b
Joined: 09 Jul 2002 Posts: 13
|
Posted: Fri May 02, 2003 2:17 pm Post subject: |
|
|
Yes, it is related. For now I am updating packages manually, thanks for the pointer. |
|
Back to top |
|
|
enek n00b
Joined: 17 Jan 2003 Posts: 15 Location: Edmonton
|
Posted: Fri Nov 14, 2003 9:04 am Post subject: or this? |
|
|
Possibly a result of this:
Code: | * Your compile WILL fail if you are upgrading from
* a previous version of tclx.
*
* emerge unmerge tclx
* BEFORE upgrading to a newer version
*
* You have been warned :)
|
_________________ Tied up in Knots |
|
Back to top |
|
|
djand n00b
Joined: 09 Jul 2002 Posts: 13
|
Posted: Mon Nov 24, 2003 4:35 am Post subject: Re: or this? |
|
|
enek wrote: | Possibly a result of this:
Code: | * Your compile WILL fail if you are upgrading from
* a previous version of tclx.
*
* emerge unmerge tclx
* BEFORE upgrading to a newer version
*
* You have been warned :)
|
|
No, the problem back in May was of a different nature. Check the link in the second article for the cause. |
|
Back to top |
|
|
|