If the preload has been installed with the command:
[fedorax@localhost ~]$ su -c 'yum -y install preload'
and now if it is causing problems, how could it be uninstalled??
Am 20.07.2010 10:08, schrieb Parshwa Murdia:
If the preload has been installed with the command:
[fedorax@localhost ~]$ su -c 'yum -y install preload'
and now if it is causing problems, how could it be uninstalled??
The most convienient way would be su -c 'yum -y remove preload'
A simple
su -c "rpm -e preload"
will also work.
On Tuesday 20 July 2010 01:19 AM, Adalbert Prokop wrote:
A simple
su -c "rpm -e preload"
will also work.
However that is not recommended, at least that is what I know. This leaves yum in a state where it is unaware of the removed rpm. It is always recommended to use yum over rpm directly. :)
Adalbert Prokop wrote:
If the preload has been installed with the command:
[fedorax@localhost ~]$ su -c 'yum -y install preload'
and now if it is causing problems, how could it be uninstalled??
The most convienient way would be su -c 'yum -y remove preload'
I would imagine the "-y" would be rather dangerous, as "yum remove" often tries to remove many packages required by other applications.
2010/7/20 Suvayu Ali fatkasuvayu+linux@gmail.com:
On Tuesday 20 July 2010 01:19 AM, Adalbert Prokop wrote:
A simple
su -c "rpm -e preload"
will also work.
However that is not recommended, at least that is what I know. This leaves yum in a state where it is unaware of the removed rpm.
This is wrong. yum is just a frontend for rpm.
It is
always recommended to use yum over rpm directly. :)
Yum makes things easier. rpm itsself can handle more complex situations (system troubleshooting etc)
kind regards, Rudolf Kastl
On Tuesday 20 July 2010 04:39 AM, Rudolf Kastl wrote:
2010/7/20 Suvayu Alifatkasuvayu+linux@gmail.com:
On Tuesday 20 July 2010 01:19 AM, Adalbert Prokop wrote:
A simple
su -c "rpm -e preload"
will also work.
However that is not recommended, at least that is what I know. This leaves yum in a state where it is unaware of the removed rpm.
This is wrong. yum is just a frontend for rpm.
Yum also maintains a database of its own, that is how we get any of the newer features like yum history. Using rpm directly makes the 2 databases inconsistent with each other.
http://illiterat.livejournal.com/7834.html
On 07/20/2010 03:49 AM, Timothy Murphy wrote:
I would imagine the "-y" would be rather dangerous, as "yum remove" often tries to remove many packages required by other applications.
I don't think that's quite true. If you tell yum to remove a package, it'll remove that package and any package that requires it. It doesn't descend the dependency tree in the opposite direction (normally, I believe there's a plugin that'll do that), and in no case will it ever do something inconsistent like removing a package which is required by something that yum leaves installed.
On Tue, 2010-07-20 at 10:21 -0700, Gordon Messmer wrote:
On 07/20/2010 03:49 AM, Timothy Murphy wrote:
I would imagine the "-y" would be rather dangerous, as "yum remove" often tries to remove many packages required by other applications.
I don't think that's quite true. If you tell yum to remove a package, it'll remove that package and any package that requires it.
I believe what Timothy meant was something along the lines of what happens if you try to remove, say, xorg-x11-server-Xorg, which would probably result in the removal of every GUI application since they all depend on an X server. This is an obvious and therefore stupid example to illustrate the point, which is that it would be easy to attempt removing something that many other things depended on, and if you use the -y flag, many things you wanted to keep could be gone before you realized what was happening. That is why -y is dangerous.
--Greg
On 07/21/2010 12:05 AM, Greg Woods wrote:
I believe what Timothy meant was something along the lines of what happens if you try to remove, say, xorg-x11-server-Xorg, which would probably result in the removal of every GUI application since they all depend on an X server. This is an obvious and therefore stupid example to illustrate the point, which is that it would be easy to attempt removing something that many other things depended on, and if you use the -y flag, many things you wanted to keep could be gone before you realized what was happening. That is why -y is dangerous.
Yum in rawhide by default protects yum and everything that depends on it which atleast minimizes such accidental damage and it is user configurable. So you can add more packages to be protected. For previous releases, the protect-core plugin has similar functionality.
Rahul
Gordon Messmer wrote:
I would imagine the "-y" would be rather dangerous, as "yum remove" often tries to remove many packages required by other applications.
I don't think that's quite true. If you tell yum to remove a package, it'll remove that package and any package that requires it. It doesn't descend the dependency tree in the opposite direction (normally, I believe there's a plugin that'll do that), and in no case will it ever do something inconsistent like removing a package which is required by something that yum leaves installed.
I know that I have yum-installed X in the past, and it has installed X, together with Y and Z, Then I have yum-removed X, and it has listed X, Y and Z, and a large number of other packages to be uninstalled.
On 20Jul2010 13:39, Rudolf Kastl che666@gmail.com wrote: | 2010/7/20 Suvayu Ali fatkasuvayu+linux@gmail.com: | > On Tuesday 20 July 2010 01:19 AM, Adalbert Prokop wrote: | >> A simple | >> | >> su -c "rpm -e preload" | >> | >> will also work. | > | > However that is not recommended, at least that is what I know. This | > leaves yum in a state where it is unaware of the removed rpm. | | This is wrong. yum is just a frontend for rpm.
Indeed.
| > It is | > always recommended to use yum over rpm directly. :) | | Yum makes things easier. rpm itsself can handle more complex | situations (system troubleshooting etc)
In particular, if I want to remove _exactly_ one package, I will always use rpm and not yum.
Yum descends the packagae dependency tree and offers to also remove the package that require the package I asked to remove. Easy to do damage that way.
Rpm also descends the dependency tree, but will refuse the remove of if another package depends on the one I asked to remove. Safer!
So Adalbert's "rpm -e preload" advice is good advice.
It happens that nothing depends on preload (I know this because I routinely remove it from systems because it modifies binaries and that sets off annoying alerts in our integrity monitoring software).
So: yum is recommended because is makes a lot of common tasks much easier rpm is fine though, provided you are ok with its limitations; as described above - sometimes I want those limitations
The package state is kept entirely in the rpm database - it is safe, as far as the database integrity goes, to mix use of rpm and yum as suits your needs.
Cheers,
On 20 July 2010 15:21, Cameron Simpson cs@zip.com.au wrote:
So Adalbert's "rpm -e preload" advice is good advice.
It happens that nothing depends on preload (I know this because I routinely remove it from systems because it modifies binaries and that sets off annoying alerts in our integrity monitoring software).
So: yum is recommended because is makes a lot of common tasks much easier rpm is fine though, provided you are ok with its limitations; as described above - sometimes I want those limitations
The package state is kept entirely in the rpm database - it is safe, as far as the database integrity goes, to mix use of rpm and yum as suits your needs.
Please look at my response to Rudolf's post with reasons behind my statement.
On Tue, Jul 20, 2010 at 5:32 PM, suvayu ali <fatkasuvayu+linux@gmail.comfatkasuvayu%2Blinux@gmail.com
wrote:
On 20 July 2010 15:21, Cameron Simpson cs@zip.com.au wrote:
So Adalbert's "rpm -e preload" advice is good advice.
It's not wrong advice, but it's not "good" advice, either.
The package state is kept entirely in the rpm database - it is safe, as far as the database integrity goes, to mix use of rpm and yum as suits your needs.
Please look at my response to Rudolf's post with reasons behind my statement.
Suvayu is correct. Mixing use of yum and rpm is discouraged for a reason. If you want to use all the features of yum (at all) then you should be using yum for everything. The yum database needs to be aware of every package transaction in order to provide all the value-add it has to offer. If you're using rpm, you're cutting yum out of the loop and changing the state of the system outside of yum's ability to record what you're doing.
Yes, the package state is kept entirely in the rpm database, however, the rpm database does not contain records of transactions performed on that database.
To repeat: http://illiterat.livejournal.com/7834.html
Christofer C. Bell wrote:
Suvayu is correct. Mixing use of yum and rpm is discouraged for a reason. If you want to use all the features of yum (at all) then you should be using yum for everything. The yum database needs to be aware of every package transaction in order to provide all the value-add it has to offer. If you're using rpm, you're cutting yum out of the loop and changing the state of the system outside of yum's ability to record what you're doing.
I take that in. But I still have some doubt. Suppose I yum-install A, and it brings in A,B and C. If I yum-remove A, is it guaranteed that it will only remove A,B and C?
As I mentioned, at some point in the fairly recent past, I tried this, and yum wanted to remove more than A,B and C.
On Wed, Jul 21, 2010 at 13:34:16 +0100, Timothy Murphy gayleard@eircom.net wrote:
Suppose I yum-install A, and it brings in A,B and C. If I yum-remove A, is it guaranteed that it will only remove A,B and C?
If you haven't installed anything else in between and nothing was removed (as can be the case if something is obsoleted) only package A will be removed. B and C will remain installed.
As I mentioned, at some point in the fairly recent past, I tried this, and yum wanted to remove more than A,B and C.
If other stuff was installed, updated or removed in between then you need to take those other packages into account when trying to figure out what will get removed as dependencies.
On Wed, Jul 21, 2010 at 7:34 AM, Timothy Murphy gayleard@eircom.net wrote:
Christofer C. Bell wrote:
Suvayu is correct. Mixing use of yum and rpm is discouraged for a reason. If you want to use all the features of yum (at all) then you should be using yum for everything. The yum database needs to be aware of every package transaction in order to provide all the value-add it has to offer. If you're using rpm, you're cutting yum out of the loop and changing the state of the system outside of yum's ability to record what you're doing.
I take that in. But I still have some doubt. Suppose I yum-install A, and it brings in A,B and C. If I yum-remove A, is it guaranteed that it will only remove A,B and C?
As I mentioned, at some point in the fairly recent past, I tried this, and yum wanted to remove more than A,B and C.
Timothy,
You may find this information useful in learning more about yum's transaction history:
http://allaboutfedora.blogspot.com/2009/11/f12-yum-new-features.html
As indicated earlier, if you do this:
yum install A
And then yum pulls in B and C to satisfy dependencies, later running
yum remove A
Will simply remove A and leave B and C in place. With yum's transaction history log, you can ensure that when you remove A, you also remove B and C, leaving the rest of the system untouched.
In reading that blog post, you'll see Jef Spaleta asking how an *upgrade* is handled and everyone misunderstanding his question. To answer it here, yum will downgrade the packages if you undo an update transaction. I've provided an example of that below. In this case, the system is able to downgrade 5 of the 7 packages that were updated in that transaction:
[cbell@circe ~]$ sudo yum history list Loaded plugins: presto, refresh-packagekit ID | Login user | Date and time | Action(s) | Altered ------------------------------------------------------------------------------- 85 | Christofer ... <cbell> | 2010-07-21 15:52 | Erase | 1 84 | Christofer ... <cbell> | 2010-07-21 09:34 | Install | 2 83 | Christofer ... <cbell> | 2010-07-21 01:28 | Install | 1 82 | System <unset> | 2010-07-21 01:15 | I, U | 44 81 | Christofer ... <cbell> | 2010-07-19 22:37 | Install | 4 80 | Christofer ... <cbell> | 2010-07-19 22:28 | Install | 14 79 | Christofer ... <cbell> | 2010-07-17 01:24 | Erase | 9 78 | Christofer ... <cbell> | 2010-07-17 01:19 | Install | 9 77 | System <unset> | 2010-07-16 15:21 | Install | 1 76 | System <unset> | 2010-07-16 09:14 | Update | 7 75 | System <unset> | 2010-07-15 15:24 | Update | 19 74 | Christofer ... <cbell> | 2010-07-14 19:52 | Install | 1 73 | Christofer ... <cbell> | 2010-07-14 19:50 | Install | 6 72 | Christofer ... <cbell> | 2010-07-14 03:57 | Update | 2 71 | Christofer ... <cbell> | 2010-07-14 01:10 | Erase | 1 70 | Christofer ... <cbell> | 2010-07-14 01:08 | Install | 1 69 | Christofer ... <cbell> | 2010-07-14 00:49 | Erase | 1 68 | Christofer ... <cbell> | 2010-07-14 00:42 | Install | 1 67 | Christofer ... <cbell> | 2010-07-14 00:40 | Erase | 2 66 | Christofer ... <cbell> | 2010-07-14 00:39 | Install | 1 history list [cbell@circe ~]$ sudo yum history undo 76 Loaded plugins: presto, refresh-packagekit Undoing transaction 76, from Fri Jul 16 09:14:50 2010 Updated cairomm-1.8.4-1.fc13.i686 Update 1.8.4-2.fc13.i686 Updated glew-1.5.2-2.fc13.i686 Update 1.5.4-1.fc13.i686 Updated libdwarf-0.20090324-5.fc12.i686 Update 0.20100629-1.fc13.i686 Updated libgnomekbd-2.30.1-2.fc13.i686 Update 2.30.2-1.fc13.i686 Updated openldap-2.4.21-8.fc13.i686 Update 2.4.21-9.fc13.i686 Updated ppp-2.4.5-8.fc13.i686 Update 2.4.5-9.fc13.i686 Updated pptp-1.7.2-8.fc12.i686 Update 1.7.2-9.fc13.i686 Failed to downgrade: libgnomekbd-2.30.1-2.fc13.i686 Failed to downgrade: openldap-2.4.21-8.fc13.i686 Resolving Dependencies --> Running transaction check ---> Package cairomm.i686 0:1.8.4-1.fc13 set to be updated ---> Package cairomm.i686 0:1.8.4-2.fc13 set to be erased ---> Package glew.i686 0:1.5.2-2.fc13 set to be updated ---> Package glew.i686 0:1.5.4-1.fc13 set to be erased ---> Package libdwarf.i686 0:0.20090324-5.fc12 set to be updated ---> Package libdwarf.i686 0:0.20100629-1.fc13 set to be erased ---> Package ppp.i686 0:2.4.5-8.fc13 set to be updated ---> Package ppp.i686 0:2.4.5-9.fc13 set to be erased ---> Package pptp.i686 0:1.7.2-8.fc12 set to be updated ---> Package pptp.i686 0:1.7.2-9.fc13 set to be erased --> Finished Dependency Resolution
Dependencies Resolved
================================================================================ Package Arch Version Repository Size ================================================================================ Downgrading: cairomm i686 1.8.4-1.fc13 fedora 53 k glew i686 1.5.2-2.fc13 fedora 129 k libdwarf i686 0.20090324-5.fc12 fedora 88 k ppp i686 2.4.5-8.fc13 fedora 321 k pptp i686 1.7.2-8.fc12 fedora 58 k
Transaction Summary ================================================================================ Remove 0 Package(s) Reinstall 0 Package(s) Downgrade 5 Package(s)
Total download size: 650 k Is this ok [y/N]: n Exiting on user Command Complete! [cbell@circe ~]$
-
Adalbert Prokop -
Bruno Wolff III -
Cameron Simpson -
Christofer C. Bell -
Gordon Messmer -
Greg Woods -
Parshwa Murdia -
Rahul Sundaram -
Rudolf Kastl -
Suvayu Ali -
Timothy Murphy