Tr : [Yum] Can yum be used to remove a single package?
Littoz
ajlittoz at users.sourceforge.net
Tue Jan 1 09:25:11 UTC 2008
De : seth vidal <skvidal at fedoraproject.org>
À : "Yellowdog Updater, Modified" <yum at lists.dulug.duke.edu>
Envoyé le : Lundi, 31 Décembre 2007, 16h00mn 43s
Objet : Re: [Yum] Can yum be used to remove a single package?
> On Mon, 2007-12-31 at 15:52 +0100, Littoz wrote:
> > Experiencing a mis-hap in an update, I wanted to back up one step by
> > removing the suspected package. I then selected this package with YumEx
> > (graphical front-end for yum) in the "installed list" and asked it
> to be
> > removed. To my surprise, the dependency "transitive closure
> computation"
> > concluded that nearly all packages should be removed, even ones not
> > clearly related to my purpose (Explanation by the example: cups to be
> > removed; after dependency, open-office, kde, gnome, ..., maybe even
> > kernel to be removed also).
> >
> > If the dependency computation used for package removal is the same as
> > for inclusion, it seems to me this is a design flaw. For inclusion, it
> > is perfectly right to compute a transitive closure and to add all
> > packages needed. For deletion, the dependency computation should only
> > decrement the "in-use" counter of the referenced package. Only when
> this
> > in-use counter goes to zero should the referenced package be put on the
> > removal list. Think of the way the i-nodes are deleted by Unix-like OS
> > in presence of hard links.
> >
> > I admit that in some circumstances this approach can't be totally
> > fail-safe. For instance, you included an "independant" package A (not
> > referenced nor referencing). You then install package B referencing A.
> > If you remove B, you also remove A. But this situation can be quite
> > manageable compared to the present flooding strategy capable of
> > dramatically damaging a working system.
> >
> > Configuration:
> > yum 3.0.6 (not the most up-to-date but coming from packages FC6)
> > yumex 2.0.1
> > i686 box running linux 2.6.22
> >
What package were you trying to remove when you encountered the above
problem?
-sv
CUPS
Fearing a misuse from my part, I carefully reattempted the removal this
morning by selecting only one package of the suite, namely cups. I took
a screen snapshot of the result of computing the dependencies. The
result is not as bad as first mentioned in my original message, but why
does this try to remove e.g. gnome-session or planner or xfig? I might
well use these without the intent of printing anything. Worse, if it
removes gnome-session, how do I again log in?
Anyway, I suspect something went wrong during a previous update because
yumex (or yum underneath) consistently now reports that my computer does
not need any update. And this situation has already lasted for two
weeks. Statistically, with the number of packages installed on my
computer (>1800), even during this holiday period, I should find some by
my previous experience. Is there a way to regenerate the rpm data base?
(Note: I counter checked the present state of the dependencies with
smart, it says OK but, well, only for the "closure" of the dependencies).
Best season's wishes
ajl
> ______________________________________________
> Yum mailing list
> Yum at lists.dulug.duke.edu <mailto:Yum at lists.dulug.duke.edu>
> https://lists.dulug.duke.edu/mailman/listinfo/yum
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.baseurl.org/pipermail/yum/attachments/20080101/2d04e40d/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cps-del-1.png
Type: image/png
Size: 101668 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum/attachments/20080101/2d04e40d/attachment-0002.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cps-del-2.png
Type: image/png
Size: 104979 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum/attachments/20080101/2d04e40d/attachment-0003.png
More information about the Yum
mailing list