up2date wrong version after updating to fc4.

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

 



I've got a problem with up2date after upgrading an FC3 server to FC4.

I installed the new rpms spoken of at the bottom of this email. 

I've edited the sourcesConfig.py file, changing releasever from "3" to
"4".

I ran up2date --upgrade-to-release=4

I also ran up2date --register

When I run up2date from the command line, I get:

Repository extras already added, not adding again
Repository updates-released already added, not adding again
Repository base already added, not adding again

When it starts it goes:

Baseurl(s) for repo:
['ftp://ftp.uci.edu/mirrors/fedora/linux/core/updates/3/i386/'

Notice it says 3 instead of 4.

Where and how do I change up2date to look for version 4 files instead of
version 3 files ?

This is killing me !







On Tue, 2005-07-19 at 08:08 +0100, Paul Howarth wrote:
> On Mon, 2005-07-18 at 20:45 -0800, Kam Leo wrote:
> > On 7/18/05, Amadeus W. M. <amadeus84@xxxxxxxxxxxxxx> wrote:
> > > Running FC4.
> > > 
> > > I have livna.repo in /etc/yum.repos.d/ with the following contents:
> > > 
> > > [livna]
> > > name=Livna.org Fedora Compatible Packages
> > > baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.lvn
> > > enabled=1
> > > gpgcheck=1
> > > gpgkey=http://rpm.livna.org/RPM-LIVNA-GPG-KEY
> > > 
> > > 
> > > When I try to upgrade the system with up2date, the livna repository shows
> > > up, and when highlighted the channel information says
> > > 
> > > repomd channel livna from  http://rpm.livna.org/fedora/3/i386/RPMS.lvn
> > > 
> > > Why is it looking for FC3 rpms? I suspect the 3 is given by the releasver
> > > variable from livna.repo, but where is that set, and why is that set to 3?
> > > 
> > > Thanks!
> > > 
> > > P.S. I did update the system with yum update, but it's nice to see when
> > > new updates are available, that's why I still want to fix up2date.
> > > 
> > 
> > It's an up2date bug.  I have already entered a bug report in Bugzilla:
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=163209 .
> 
> Looks like a duplicate of:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161071
> 
> There's a workaround in that bug report, or you could install my updated up2date package that includes that workaround:
> # rpm -Uvh
> http://www.city-fan.org/ftp/contrib/yum-repo/up2date-4.4.23-4a.fc4.i386.rpm 
> http://www.city-fan.org/ftp/contrib/yum-repo/up2date-gnome-4.4.23-4a.fc4.i386.rpm
> 
> (that's all one long line)
> 
> Paul.
> -- 
> Paul Howarth <paul@xxxxxxxxxxxx>
> 
-- 
Kim Lux,  Diesel Research Inc.



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux