Red Hat Bugzilla – Bug 192811
Yumex queue dissappears after repository initialization
Last modified: 2007-11-30 17:11:33 EST
Description of problem:
While running Yumex and adding packages to the Que, selecting
other repositories and refreshing the definitions removes all
already allocated queues chosen.
Version-Release number of selected component (if applicable):
Open Yumex, refresh the repository data definitions.
Select a few packages to update using a testing or development source.
Refresh the repository definitions again and the queue has dissappeared.
Steps to Reproduce:
1. Open Yumex.
2. Select packages for update
3. Refresh repository definition data.
Selected packages put in Que dissappear.
Selected packages should stay allocated even after new repository information
if an only if the packages are new packages.
In this case the selected packages
were from updates-testing, and the new repository added was Fedora development.
I can see how all packages probably had a package in development.
In any case if I do not want the newest set of packages from development alone
but wanted one or two, I would be left in the dirt re-selecting all packages
previously selected. I am unsure how yum.conf pkgpolicy tag set at newest
comes into play in this situation.
The actual situation here is with Core, Extras, and Updates read in, packages
selected, libqtparted.so is a missing dependency, which I assume is in
development and development was added to the current repository data.
The que dissappeared. I think maybe subtrees of packages from each repository
could perhaps be listed, say I need development's Parted, but only want GCC
updates from updates, or updates testing and development is shown also.
The default behavior is the clear everything, when doing a refresh.
I dont think it is posible the keep older packages when adding a repo with newer
versions of the same packages, like development, i think it will mess up the
Ok. It makes sense in that regard of course to only show the newest packages.
I am also thinking that disregarding newer packages altogether which are already
checked into the queue may also be of benefit to some, but certainly a hassle in
the way of deciding what is or isn't known to the user.
e.g. If you already have packages selected in que, adding another repository
will only show packages selectable outside of the current qued selections packages.
Interesting. Ok. I guess that's about it as far as suggestions from me.