On Tue, 2005-02-22 at 08:49 +0000, Paul Howarth wrote: > On Tue, 2005-02-22 at 12:58 +0900, Mark Sargent wrote: > > does it get any more fun than this..? 1st update after upgrading from 2 > > to 3 via CDs. As some of you may be aware, I had some trouble with the > > upgrade, which were never resolved. So, I went ahead with a yum update, > > just to see how it would go. Here are the results. Any Qs, please ask. > > > > [coolboarderguy@localhost ~]$ su - > > Password: > > [root@localhost ~]# yum update > > Repository updates-released already added, not adding again > > Repository base already added, not adding again > > Setting up Update Process > > Setting up Repo: dag > > repomd.xml 100% |=========================| 1.1 kB 00:00 > > Setting up Repo: base > > repomd.xml 100% |=========================| 1.1 kB 00:00 > > Setting up Repo: updates-released > > repomd.xml 100% |=========================| 951 B 00:00 > > Reading repository metadata in from local files > > primary.xml.gz 100% |=========================| 675 kB 00:09 > > MD Read : ################################################## 1807/1807 > > dag : ################################################## 1807/1807 > > base : ################################################## 2622/2622 > > primary.xml.gz 100% |=========================| 292 kB 00:03 > > MD Read : ################################################## 676/676 > > updates-re: ################################################## 676/676 > > Resolving Dependencies > > --> Populating transaction set with selected packages. Please wait. > > ---> Downloading header for gaim to pack into transaction set. > > (snip) > > > --> Finished Dependency Resolution > > Error: missing dep: openoffice.org for pkg openoffice.org-i18n > > Error: Missing Dependency: httpd is needed by package httpd-suexec > > Error: Missing Dependency: system-config-printer is needed by package > > system-config-printer-gui > > [root@localhost ~]# > > > > My yum.conf > > > > > > [main] > > cachedir=/var/cache/yum > > debuglevel=2 > > logfile=/var/log/yum.log > > pkgpolicy=newest > > distroverpkg=redhat-release > > tolerant=1 > > exactarch=1 > > retries=20 > > > > [base] > > name=Fedora Core $releasever - $basearch - Base > > baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/ > > > > [updates-released] > > name=Fedora Core $releasever - $basearch - Released Updates > > baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/ > > Remove the [base] and [updates-released] entries because they are > duplicates of the versions in /etc/yum.repos.d > > This will fix the "Repository updates-released already added, not adding > again" and "Repository base already added, not adding again" warning > messages you got above. > > > #[updates-testing] > > #name=Fedora Core $releasever - $basearch - Unreleased Updates > > #baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/$releasever/$basearch/ > > > > #[development] > > #name=Fedora Core $releasever - Development Tree > > #baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/ > > > > [dag] > > name=Dag RPM Repository for Fedora Core > > baseurl=http://apt.sw.be/fedora/$releasever/en/$basearch/dag > > > > I'm figuring that due to not being able to complete the upgrade b4(from > > 2 to 3, due to errors), that there are some mssing packages/dependecies. > > You could try doing the update in smaller batches of packages and then > addressing the issues that are left. > > e.g. > # yum update yum > # yum update xorg\* > # yum update gnome\* > > For the troublesome packages, which versions are available and which > versions do you currently have? > > # yum list openoffice.org\* > # rpm -q openoffice.org openoffice.org-libs openoffice.org-i18n > openoffice.org-kde > > Paul. > -- > Paul Howarth <paul@xxxxxxxxxxxx> > Hi All, Paul, after removing the entries you suggested, from yum.conf, and running yum update again, I got the following, [root@localhost ~]# yum update You have enabled checking of packages via GPG keys. This is a good thing. However, you do not have any GPG public keys installed. You need to download the keys for packages you wish to install and install them. You can do that by running the command: rpm --import public.gpg.key For more information contact your distribution or package provider. [root@localhost ~]# rpm --import public.gpg.key error: public.gpg.key: import read failed. I haven't enabled anything of the sort, that I recall and most certainly not since this problem started. What is this.? Cheers. Mark Sargent.