So I go to remove the Google "stuff" from my machine and I get this:
$ yum remove google-gadgets-qt google-gadgets google-desktop-linux Loaded plugins: fastestmirror, fedorakmod, protectbase, refresh-packagekit, refresh-updatesd Setting up Remove Process Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. --> Running transaction check ---> Package google-desktop-linux.i386 0:1.2.0-0088 set to be erased ---> Package google-gadgets.i386 0:0.10.5-3.fc10 set to be erased --> Processing Dependency: libggadget-1.0.so.0 for package: kdebase-workspace ---> Package google-gadgets-qt.i386 0:0.10.5-3.fc10 set to be erased --> Running transaction check ---> Package kdebase-workspace.i386 0:4.2.0-8.fc10 set to be erased --> Processing Dependency: kdebase-kdm for package: fedorainfinity-kdm-theme --> Processing Dependency: kdebase-workspace = 4.2.0-8.fc10 for package: kdebase-workspace-libs --> Running transaction check ---> Package fedorainfinity-kdm-theme.noarch 0:1.0.4-1.fc8 set to be erased ---> Package kdebase-workspace-libs.i386 0:4.2.0-8.fc10 set to be erased --> Finished Dependency Resolution
Dependencies Resolved
==================================================================================================================================== Package Arch Version Repository Size ==================================================================================================================================== Removing: google-desktop-linux i386 1.2.0-0088 installed 19 M google-gadgets i386 0.10.5-3.fc10 installed 5.8 M google-gadgets-qt i386 0.10.5-3.fc10 installed 654 k Removing for dependencies: fedorainfinity-kdm-theme noarch 1.0.4-1.fc8 installed 1.1 M kdebase-workspace i386 4.2.0-8.fc10 installed 27 M kdebase-workspace-libs i386 4.2.0-8.fc10 installed 1.9 M
Transaction Summary ==================================================================================================================================== Install 0 Package(s) Update 0 Package(s) Remove 6 Package(s)
HUH? What possible reason could there be for anything related to KDE to have with the google garbage?
Thanks.
Kevin
Kevin Martin wrote:
HUH? What possible reason could there be for anything related to KDE to have with the google garbage?
Plasma supports showing Google Gadgets as applets/widgets.
But we have split this out into a kdebase-workspace-googlegadgets subpackage in our KDE 4.2.1 update, so you'll be able to remove the google-gadgets crap when 4.2.1 hits the stable updates.
Kevin Kofler
Kevin Kofler wrote:
Kevin Martin wrote:
HUH? What possible reason could there be for anything related to KDE to have with the google garbage?
Plasma supports showing Google Gadgets as applets/widgets.
But we have split this out into a kdebase-workspace-googlegadgets subpackage in our KDE 4.2.1 update, so you'll be able to remove the google-gadgets crap when 4.2.1 hits the stable updates.
Kevin Kofler
Kevin,
Thanks for that info. Makes more sense now.
Kevin
Kevin Martin wrote:
So I go to remove the Google "stuff" from my machine and I get this:
$ yum remove google-gadgets-qt google-gadgets google-desktop-linux Loaded plugins: fastestmirror, fedorakmod, protectbase, refresh-packagekit, refresh-updatesd Setting up Remove Process Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. --> Running transaction check ---> Package google-desktop-linux.i386 0:1.2.0-0088 set to be erased ---> Package google-gadgets.i386 0:0.10.5-3.fc10 set to be erased --> Processing Dependency: libggadget-1.0.so.0 for package: kdebase-workspace ---> Package google-gadgets-qt.i386 0:0.10.5-3.fc10 set to be erased --> Running transaction check ---> Package kdebase-workspace.i386 0:4.2.0-8.fc10 set to be erased --> Processing Dependency: kdebase-kdm for package: fedorainfinity-kdm-theme --> Processing Dependency: kdebase-workspace = 4.2.0-8.fc10 for package: kdebase-workspace-libs --> Running transaction check ---> Package fedorainfinity-kdm-theme.noarch 0:1.0.4-1.fc8 set to be erased ---> Package kdebase-workspace-libs.i386 0:4.2.0-8.fc10 set to be erased --> Finished Dependency Resolution
Dependencies Resolved
==================================================================================================================================== Package Arch Version Repository Size ==================================================================================================================================== Removing: google-desktop-linux i386 1.2.0-0088 installed 19 M google-gadgets i386 0.10.5-3.fc10 installed 5.8 M google-gadgets-qt i386 0.10.5-3.fc10 installed 654 k Removing for dependencies: fedorainfinity-kdm-theme noarch 1.0.4-1.fc8 installed 1.1 M kdebase-workspace i386 4.2.0-8.fc10 installed 27 M kdebase-workspace-libs i386 4.2.0-8.fc10 installed 1.9 M
Transaction Summary
Install 0 Package(s) Update 0 Package(s) Remove 6 Package(s)
HUH? What possible reason could there be for anything related to KDE to have with the google garbage?
Thanks.
Kevin
Kevin I run across this all the time, it is frustrating, but I just use the command;
rpm -e --nodeps google-gadgets-qt google-gadgets google-desktop-linux
What the --nodeps is , it removes only those packages and no Dependencies.
Hopefully, someday, they will fix that problem in Yum
LOL
Jim wrote:
Kevin I run across this all the time, it is frustrating, but I just use the command;
rpm -e --nodeps google-gadgets-qt google-gadgets google-desktop-linux
What the --nodeps is , it removes only those packages and no Dependencies.
Hopefully, someday, they will fix that problem in Yum
LOL
It is *not* a problem in yum. Yum is merely doing it's job. The dependencies are in the software itself in most cases and package maintainers control it to some extend. Kevin Kofler has already explained what has happened in this thread. Read it.
Rahul
<snip>
HUH? What possible reason could there be for anything related to KDE to have with the google garbage?
Thanks.
Kevin
Kevin I run across this all the time, it is frustrating, but I just use the command;
rpm -e --nodeps google-gadgets-qt google-gadgets google-desktop-linux
What the --nodeps is , it removes only those packages and no Dependencies.
Hopefully, someday, they will fix that problem in Yum
LOL
Yes, that's what I ultimately did; it's just that one shouldn't have to force a --nodeps on a remove for something like google* (or anything else for that matter). The dependencies for google "stuff" will be removed, apparently, with the release of KDE 4.2.1 so I guess it'll happen then.
Kevin
Rahul Sundaram wrote:
Jim wrote:
Kevin I run across this all the time, it is frustrating, but I just use the command;
rpm -e --nodeps google-gadgets-qt google-gadgets google-desktop-linux
What the --nodeps is , it removes only those packages and no Dependencies.
Hopefully, someday, they will fix that problem in Yum
LOL
It is *not* a problem in yum. Yum is merely doing it's job. The dependencies are in the software itself in most cases and package maintainers control it to some extend. Kevin Kofler has already explained what has happened in this thread. Read it.
Rahul
Easy there Rahul. I suspect that Jim read my question from a Digest that had maybe come out before Kevin's response (or just replied prior to getting that far in the Digest). No need to jump down his throat; honey vs. vinegar and all that.
Kevin
Kevin Martin wrote:
Easy there Rahul. I suspect that Jim read my question from a Digest that had maybe come out before Kevin's response (or just replied prior to getting that far in the Digest). No need to jump down his throat; honey vs. vinegar and all that.
I was merely explaining it to him. Nothing more.
Rahul
Kevin Martin wrote:
Rahul Sundaram wrote:
Jim wrote:
Kevin I run across this all the time, it is frustrating, but I just use the command;
rpm -e --nodeps google-gadgets-qt google-gadgets google-desktop-linux
What the --nodeps is , it removes only those packages and no Dependencies.
Hopefully, someday, they will fix that problem in Yum
LOL
It is *not* a problem in yum. Yum is merely doing it's job. The dependencies are in the software itself in most cases and package maintainers control it to some extend. Kevin Kofler has already explained what has happened in this thread. Read it.
Rahul
Easy there Rahul. I suspect that Jim read my question from a Digest that had maybe come out before Kevin's response (or just replied prior to getting that far in the Digest). No need to jump down his throat; honey vs. vinegar and all that.
Kevin
No problem, I do feel his pain, I have experienced it many times. What I had suggested was a short term fix. I also have one of those irritating little problems that has been in KDE for many past releases.
When your in Konqueror as SU and try to edit with Kedit or Kwrite you get a "cant launch Kedit or Kwrite" You then have to restart KDE to get Kedit or Kwrite to launch.
Jim
-
Jim -
Kevin Kofler -
Kevin Martin -
Rahul Sundaram