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.

On Mon, 2005-07-18 at 20:45 -0800, Kam Leo wrote: > On 7/18/05, Amadeus W. M. <amadeus84(a)cablespeed.com&gt; 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.... (that's all one long line) Paul. -- Paul Howarth <paul(a)city-fan.org&gt;

Let's try to fix this first. You have multiple repository definitions for the extras, updates-released, and base repositories, which probably means that your existing FC3 repo definitions are still active. I'd guess that you have them in /etc/yum.conf, whereas they are specified in separate files in directory /etc/yum.repos.d in FC4. Try editing /etc/yum.conf and removing the entries for these three repositories from there.