Red Hat Bugzilla – Bug 195407
Exception when trying to upgrade few packages several times
Last modified: 2007-11-30 17:11:35 EST
Description of problem:
When trying to select the remaining packages that I excluded earlier, pup dumped
an exception. The exception was saved to a file that will be attached.
Version-Release number of selected component (if applicable):
Check and uncheck remaining updates according to report of dep conflicts. Try
other choices. Observe crash.
Steps to Reproduce:
1. try to update with all choices
2. read error report
3. toggle off selection according to error report
4. try updating again
5. deselect packages according to error report
6. try again
7. note and save exception to file
Crashed pup and yum needed some information for sqlite on next run so I could
get available update information.
Expected conflicts since I read the rawhide report prior to the large update.
These packages were tried since I was not sure of the conflict still being there
or if it was resolved.
The available packages were:
ImageMagick.i386 220.127.116.11-1 development
eclipse-bugzilla.i386 1:0.2.2-6 development
eclipse-cdt.i386 1:3.1.0-0jpp_0fc.3.1.0 development
eclipse-changelog.i386 1:2.0.4_fc-3 development
eclipse-ecj.i386 1:3.2.0-0jpp_0fc.3.2RC development
eclipse-jdt.i386 1:3.2.0-0jpp_0fc.3.2RC development
eclipse-platform.i386 1:3.2.0-0jpp_0fc.3.2RC development
eclipse-rcp.i386 1:3.2.0-0jpp_0fc.3.2RC development
libswt3-gtk2.i386 1:3.2.0-0jpp_0fc.3.2RC development
nautilus-cd-burner.i386 2.15.3-1 development
Created attachment 130947 [details]
Exception saved to file
After the slight delay when trying to run yum, the available packages were
listed as none. I take it that the cache fouled and got older mirror information
where the packages were not available.
Can pup stay at the mirror that I found with the available updates? Did pup pull
in information from mirrors with outdated information on later runs?
It makes more sense for pup to stay on the same repositories unless it was
closed. It is less likely to die on retries for dep resolution and selection
Created attachment 131021 [details]
The problem with pup repeated an exception
I only tried to deselect packages once before this exception occurred.
1. Start pup
2. find deps needed
3. deselect packages
4. try again
5. Get exception
I'm not sure there's really a way for me to currently stick with a specific
entry when dealing with mirror lists. And doing so has downsides in that the
mirror you first get may not be fully synced and yet have the metadata.
.. not quite sure what the good answer here is other than the general "improve
our currently crappy mirror infrastructure" :-/
I have not tried pup since the incident reported above. The out of sync mirrors
is a problem even when using yum in a terminal. I frequently need to run yum
clean all in order to update because of the availability and out of sync
My main suggestion was to have pup stick with the same mirror when you need to
deselect packages because of dep issues. Switching mirrors with each package
selection adjustment will not work reliably with different mirrors being used
that are not listed on the package selection GUI.
If there is no practical way to cache the mirror information to ensure that the
mirror contains the package revisions intended, the random mirror selection will
remain a problem until the mirror infrastructure is improved.
There have been some improvements to the mirror infrastructure that should make
this a non-issue
Thanks! Currenlty I am using one dependable mirror instead of the random mirrors
because of the previous problem. The better infrastructure should help.