Description of problem: SEE TITLE Version-Release number of selected component (if applicable): ALL UPGRADES How reproducible: VERY - TRY UPGRADING ! Steps to Reproduce: 1. UPGRADE ALL 2. 3. Actual results: FILES UNFINDABLE CAUSE UPGRADE TO ABORT - THUS NO UPGRADE OCCURS. Expected results: UPGRADE PROGRESSES UNHALTED Additional info:
I believe that this bug is assigned to the wrong component (unless you are upgrading your 389 Directory Server). I'm assuming that you are trying to upgrade to a newer Fedora distribution, so I'm assigning this to the anaconda (installer) component. Much more information needs to be provided to troubleshoot this issue. What version of Fedora are you upgrading from/to? What files are unfindable? What errors do you receive?
Yeah, all the questions in comment #1 need to be answered before we have a hope of fixing this bug.
Hi Nathan and Chris Greetings ! I had successfully installed Fedora 12 newly and it was running fine on an x86 machine (AMD 3000+ single core processor with 1 Gig of Ram). When I went to upgrade the running system online (as one normally does, regularly) I found that there were 57 "Security Updates". These which all went through OK and the system ran better. The other two upgrade categories, however, fell over in a big way. The 43 Enhancement upgrades and the 239 Bugfixes upgrades both would not complete because certain files were "missing " from the server Repositories. It was something to do with "Yum" and "2.6.2" files - - - I tried removing anything to do with Yum & 2.6.2 from teh upgrade list. Fedora 12 still would Halt the upgrades based on "Missing Repository Files" error, no matter what I tried. So this is an external file / version / security management issue in the upgrade servers. It's also an inability for Fedora 12 to handle / report on upgrade errors and to be clever enough to sidestep them if they arise. Let me know if you need more info. Regards Ken Gibbs * * *
Thanks for attaching the extra info. When you say "upgrade the running system online", do you mean that you used yum to do an upgrade while the system was running, or was anaconda involved somehow (either by just rebooting into anaconda or using the preupgrade program)?
Hi Folks - No Probs. The upgrader is the one in Fedora as called from the Desktop menus (often called "Synaptic Manager" in Linux distros). Yum was the files that it couldn't find - I wasn't using Yum at all - I don't even know what that is. At install, there is a message that comes at the end of the install process, on the white screen headed "Fedora Installer", it states : "Please reboot - - > Note that Updates maybe be available, please install these after Reboot". That's what I did - so its the upgrader in Fedora that's gone weird. (Commonly it's called "Synaptic Manager" in Linux distros). I am re-installing Fedora 12 KDE and KFCE on the same machine to really understand this bug, so I will have more data Tomorrow/Saturday. The bug seems straightforward to comprehend- either : 1) The repositories are corrupted, incomplete or misindexed, 2) There's a bug in Fedora 12 that messes up / loses the updates "index list" or the files themselves during upgrade, 3) The servers and Fedora 12 are speaking a different language/protocol, 4) Other types of bug exist, 5) Hardware issues exist in my machine (unlikely as it runs and updates "Ubuntu Studio" perfectly). 6) Combos of the above. Linux Mint had this issue about a month back and they have fixed that. Now Mint 8 has a recovery mode which will check what's there and get upgrades at boot, if its called. I call it every day at boot and get the latest packages and a current-package check, all at the same time :) On another line of thought, PCBSD-8 is a cool system because it circumvents such an unwieldy update system as found in the Linux community by having only certain combo's of file allowed to construct each Application - very clever. When a PCBSD-8 App is downloaded (see www.pbidir.com) is comes complete and therefore has no dependencies on a mix of various files from different places arranged by different people. Thanks ! Ken Gibbs * * *
Hi Folks I got the error dump screen copied below, for you to see. I had reinstalled Fedora-12 KDE on another machine entirely, for the experiment - same results. This attempted system upgrade process was the only job that this new install has done. It was carried out using the KDE Software Manager App. This graphical command is gotten to by pushing : " Fedora Icon > Applications > System > Software Manager > Software Updates > Refresh > etc, etc " " All my previous notes apply. I will try a fresh install of Fedora12-XFCE next, in search of the same bug - - - Good luck ! * Error Type: Error Value: Error getting repository data for installed, repository not found File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in main() File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main backend.dispatcher(sys.argv[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 699, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command self.update_packages(only_trusted, package_ids) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages signed = self._is_package_repo_signed(pkg) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed repo = self.yumbase.repos.getRepo(pkg.repoid) File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo 'Error getting repository data for $s, repository not found' $ (repoid) * * *
Hi - I just installed the Fedora 12 XFCE spin. It does exactly the same as described in my last post for the KDE variant. Same leadup and resulting errors, exactly. Good bugthumping - - - Best Ken * * *
Thanks for attaching the traceback you are getting. I'm going to reassign to the correct component that involves that traceback, as they'll have a better idea of what needs to be done to fix this issue.
(In reply to comment #6) > File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo > 'Error getting repository data for $s, repository not found' $ (repoid) Do "yum update -y yum rpm PackageKit" and then reboot.
Hi Richard That worked - the upgrades came down and went in AOK. I noted that the download App looked different and worked great (important or not). Since using F-12 I have some observations which seem to be along the similar line of "things not being connected to things" properly. I chose F-12 due to its webcam streaming and editing abilities. Of the many packages I downloaded in this area, none work properly, for example :" 1) XAWTV won;'t record properly as it keeps getting "init error"upon the request to record. It shows what the webcam sees very well. 2) Toitem and fscam would not appear on the desktop - I had to make a link to the desktop. Now only Totem works - the other webcam/player app links wont. 3) The F-12 "system" cannot find the CDROM on my e-mahcines AMD 3000+ with 1 gig of RAM, so I cannot play CD's etc etc. * In summary, the system seems to have many useful packages but they either conflict or won't sync up with the system or the Desktop menu's. I am using the XFCE Desktop spin. I suggest making : a) A cleanup pack which deletes any Gnome packages and allows only XFCE packages so there's no conflicts (or vice versa if Gnome/KDE is used etc etc). b) Having an App which shows graphically whats connected to what and for the user to know how the machine is set up. This app would also allow for troubleshooting as the system can be described to Bugzilla properly, by the user when he/she gets in trouble. c) An app which searches out system disconnects or conflicts, given the Desktop in use, be it XFCE or KDE or Gnome etc. * Any suggestions to get me going again are VERY welcome !! Thanks Ken Gibbs Engineer * * *
The original problem looks like what was reported in bug 541645, so I'm marking this report as a duplicate. I added some information to the project wiki to help Gnome users figure out which command a given menu item runs: https://fedoraproject.org/wiki/BugZappers/CorrectComponent If it's too dissimilar in KDE or Xfce to figure out, let me know and I can boot up a Live version and get step-by-step instructions for those as well. To keep things trackable in Bugzilla as they are diagnosed and fixed, we need to have only one issue per report. If you are still experiencing problems with xawtv, totem, fscam, and accessing CDs, could you report each one in a new bug, please? They might represent problems in different programs, so the bugs would need to be assigned to different people. It sounds like for some of those you might be having trouble with desktop icons/shortcuts. You can see what command any desktop icon is running by right-clicking, selecting Properties, and noting what's in the Command field. It would be helpful to include in any bug reports whether or not that command works from the command line, and if any output results when you try that. I believe it is possible to use yum to sync your installed RPMs with the default RPMs in e.g. the Gnome or KDE spin, but as you suggest it might be interesting to make that easier through a graphical application. (You might file that as a separate bug/enhancement request.) If you do have any problems when applications are cross-installed, though, I would think of that as a bug which needs to be solved for that particular application, and we should not rely on users like yourself to avoid doing that. We have assembled some general advice which may assist you in documenting any remaining bugs: http://fedoraproject.org/wiki/Bugs_and_feature_requests Thanks, and good luck! --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 541645 ***