** My first ever mail! :) **
I have tried to update my system to rawhide today by adding the following to my /etc/yum.conf file.
[fedora-core-devel] name=Fedora Core (development: Rawhide) baseurl=ftp://ftp.heanet.ie/mirrors/download.fedora.redhat.com/pub/fedora/linux/core/development/i386 gpgcheck=0 failovermethod=priority
When I run 'yum update' it downloads all the new rpm headers, and then I get the following output:
Resolving dependencies .package redhat-config-mouse needs /usr/bin/python2.2 (not provided) package redhat-config-network-tui needs /usr/bin/python2.2 (not provided) package redhat-config-securitylevel needs /usr/bin/python2.2 (not provided) package redhat-config-date needs /usr/bin/python2.2 (not provided) package redhat-config-keyboard needs /usr/bin/python2.2 (not provided) package redhat-config-kickstart needs /usr/bin/python2.2 (not provided) package redhat-config-language needs /usr/bin/python2.2 (not provided) package redhat-config-rootpassword needs /usr/bin/python2.2 (not provided) package redhat-config-soundcard needs /usr/bin/python2.2 (not provided) package redhat-config-users needs /usr/bin/python2.2 (not provided) package redhat-config-xfree86 needs /usr/bin/python2.2 (not provided)
And it dumps be back at the shell prompt. I have the latest python rpm installed, and /usr/bin/python2.2 is on my machine. Can someone please tell me what I am doing wrong?
Thanks,
Marc O'Morain
(I assume this is the place to ask about rawhide, rather than fedora-list?)
On Wed, 7 Jan 2004, Marc O'Morain wrote:
Resolving dependencies .package redhat-config-mouse needs /usr/bin/python2.2 (not provided) package redhat-config-network-tui needs /usr/bin/python2.2 (not provided) package redhat-config-securitylevel needs /usr/bin/python2.2 (not provided) package redhat-config-date needs /usr/bin/python2.2 (not provided) package redhat-config-keyboard needs /usr/bin/python2.2 (not provided) package redhat-config-kickstart needs /usr/bin/python2.2 (not provided) package redhat-config-language needs /usr/bin/python2.2 (not provided) package redhat-config-rootpassword needs /usr/bin/python2.2 (not provided) package redhat-config-soundcard needs /usr/bin/python2.2 (not provided) package redhat-config-users needs /usr/bin/python2.2 (not provided) package redhat-config-xfree86 needs /usr/bin/python2.2 (not provided)
And it dumps be back at the shell prompt. I have the latest python rpm installed, and /usr/bin/python2.2 is on my machine. Can someone please tell me what I am doing wrong?
You need to remove your redhat-config-* packages (rpm -e) and install system-config-* clones instead.
behdad
Thanks,
Marc O'Morain
(I assume this is the place to ask about rawhide, rather than fedora-list?)
On Wed, 2004-01-07 at 12:48, Behdad Esfahbod wrote:
On Wed, 7 Jan 2004, Marc O'Morain wrote:
Resolving dependencies .package redhat-config-mouse needs /usr/bin/python2.2 (not provided) package redhat-config-network-tui needs /usr/bin/python2.2 (not provided) package redhat-config-securitylevel needs /usr/bin/python2.2 (not provided) package redhat-config-date needs /usr/bin/python2.2 (not provided) package redhat-config-keyboard needs /usr/bin/python2.2 (not provided) package redhat-config-kickstart needs /usr/bin/python2.2 (not provided) package redhat-config-language needs /usr/bin/python2.2 (not provided) package redhat-config-rootpassword needs /usr/bin/python2.2 (not provided) package redhat-config-soundcard needs /usr/bin/python2.2 (not provided) package redhat-config-users needs /usr/bin/python2.2 (not provided) package redhat-config-xfree86 needs /usr/bin/python2.2 (not provided)
And it dumps be back at the shell prompt. I have the latest python rpm installed, and /usr/bin/python2.2 is on my machine. Can someone please tell me what I am doing wrong?
You need to remove your redhat-config-* packages (rpm -e) and install system-config-* clones instead.
I think they obsolete each other.
Try yum upgrade instead.
-sv
On Wed, 7 Jan 2004, seth vidal wrote:
Try yum upgrade instead.
I thought 'upgrade' was a deprecated option. What does it buy that 'update' doesn't?
-- Paul Heinlein heinlein@madboa.com
On Wed, 7 Jan 2004, seth vidal wrote:
On Wed, 2004-01-07 at 13:03, Paul Heinlein wrote:
On Wed, 7 Jan 2004, seth vidal wrote:
Try yum upgrade instead.
I thought 'upgrade' was a deprecated option. What does it buy that 'update' doesn't?
it is deprecated - upgrade includes obsoletes processing.
update doesn't.
Well, that's really complecated. I remember in the days that there was a rawhide-release package, yum upgrade used to install fedora-release and remove rawhide-release, and yum update the other way... Would be nice that when yum shows what it's gonna do and asks for yes/no, also show what it's going to remove.
And my experiences show that sometimes it needs manual handling. And in this case of upgrade/update, poor users would appreciate it if you mention in the manual the difference AND that upgrade can save lifes sometimes...
behdad
-sv
Well, that's really complecated.
I agree, that's why it's been deprecated. For the future it should be:
yum --obsoletes update
That way people can enable obsolete processing at will.
And my experiences show that sometimes it needs manual handling. And in this case of upgrade/update, poor users would appreciate it if you mention in the manual the difference AND that upgrade can save lifes sometimes...
save lives? umm. maybe just a TOUCH dramatic there? :)
-sv
On Wed, Jan 07, 2004 at 01:19:54PM -0500, seth vidal wrote:
Well, that's really complecated.
I agree, that's why it's been deprecated. For the future it should be:
yum --obsoletes update
That way people can enable obsolete processing at will.
Apart from "release-foo*" (which could be put into a exclude-list;-), is there any other reason obsolete processing should not be done? I'd hope to have that enabled all the time to get newer rpms that obsolete old stuff.
greetings,
Florian La Roche
On Wed, 2004-01-07 at 14:10, Florian La Roche wrote:
On Wed, Jan 07, 2004 at 01:19:54PM -0500, seth vidal wrote:
Well, that's really complecated.
I agree, that's why it's been deprecated. For the future it should be:
yum --obsoletes update
That way people can enable obsolete processing at will.
Apart from "release-foo*" (which could be put into a exclude-list;-), is there any other reason obsolete processing should not be done? I'd hope to have that enabled all the time to get newer rpms that obsolete old stuff.
obsolete loops
foo obsoletes bar bar obsoletes foo
so the packages perpetually oscillate.
Or longer loops
foo obsoletes bar baz obsoletes foo bar obsoletes baz
-sv