[arch-general] kde-unstable install - Round 2 - There is a BUG here...
DR, List Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install). So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type: error: could not prepare transaction error: failed to commit transaction (conflicting files) /usr/share/apps/color-schemes/Zion.colors exists in both 'kdeaccessibility- colorschemes' and 'kdeaccessibility' /usr/share/apps/color-schemes/ZionReversed.colors exists in both 'kdeaccessibility-colorschemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' <snip 20000 lines> Literally, thousands and thousands of conflicting files. For full details (100k) see: http://nirvana.3111skyline.com/download/Archlinux/bugs/kde4-conflicts- i686.txt.bz2 So on good advise, I set about to remove the conflicts by removing kde4 before trying to install kde4 from kde-unstable -- no joy, same conflicts: [17:40 supersff:/home/david] # pacman -Rs kde kde not found, searching for group... :: group kde: kdebase-runtime kdelibs kdemultimedia Remove whole content? [Y/n] checking dependencies... error: failed to prepare transaction (could not satisfy dependencies) :: k3b: requires kdelibs :: k3b: requires kdemultimedia :: k9copy: requires kdebase-runtime :: kdiff3: requires kdelibs [18:02 supersff:/home/david] # pacman -Rs kde k3b k9copy kdiff3 kde not found, searching for group... :: group kde: kdebase-runtime kdelibs kdemultimedia Remove whole content? [Y/n] checking dependencies... Remove (16): kdiff3-0.9.95-1 k9copy-2.3.2-1 k3b-1.66.0alpha2-1 polkit- qt-0.9.2-1 normalize-0.7.7-3 vorbis-tools-1.2.0-3 mpg123-1.7.3-1 cdrdao-1.2.2-2 kdemultimedia-4.2.4-1 kdebase- runtime-4.2.4-1 kdelibs-4.2.4-2 strigi-0.6.4-2 exiv2-0.18-1 soprano-2.2.3-1 clucene-0.9.21b-1 phonon-4.3.1-2 Total Removed Size: 213.03 MB Do you want to remove these packages? [Y/n] ( 1/16) removing kdiff3 [#################################################################################] 100% ( 2/16) removing k9copy [#################################################################################] 100% ( 3/16) removing k3b [#################################################################################] 100% ( 4/16) removing polkit-qt [#################################################################################] 100% ( 5/16) removing normalize [#################################################################################] 100% ( 6/16) removing vorbis-tools [#################################################################################] 100% ( 7/16) removing mpg123 [#################################################################################] 100% ( 8/16) removing cdrdao [#################################################################################] 100% ( 9/16) removing kdemultimedia [#################################################################################] 100% (10/16) removing kdebase-runtime [#################################################################################] 100% (11/16) removing kdelibs [#################################################################################] 100% (12/16) removing strigi [#################################################################################] 100% (13/16) removing exiv2 [#################################################################################] 100% (14/16) removing soprano [#################################################################################] 100% (15/16) removing clucene [#################################################################################] 100% (16/16) removing phonon [#################################################################################] 100% [18:03 supersff:/home/david] # pms kde kde-extragear :: Synchronizing package databases... kdemod-legacy is up to date kde-unstable is up to date core is up to date extra is up to date community is up to date archlinuxfr is up to date kde package not found, searching for group... :: group kde (including ignored packages): kdeaccessibility-colorschemes kdeaccessibility-iconthemes kdeaccessibility-kmag kdeaccessibility-kmousetool kdeaccessibility-kmouth kdeaccessibility-kttsd kdeadmin-kcron kdeadmin- ksystemlog kdeadmin-kuser <snip packages to be installed> Total Download Size: 0.00 MB Total Installed Size: 1470.55 MB Proceed with installation? [Y/n] checking package integrity... (272/272) checking for file conflicts [#################################################################################] 100% error: could not prepare transaction error: failed to commit transaction (conflicting files) /usr/share/apps/color-schemes/Zion.colors exists in both 'kdeaccessibility- colorschemes' and 'kdeaccessibility' /usr/share/apps/color-schemes/ZionReversed.colors exists in both 'kdeaccessibility-colorschemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/48x48/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/48x48/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/64x64/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' Grrrrr. Same conflicts, what in the world is going on? The nearly identical gory details (99k): http://nirvana.3111skyline.com/download/Archlinux/bugs/kde4-conflicts-i686- again.txt.bz2 [18:21 supersff:/home/david] # pacman -Q | grep kde | grep -v kdemod3 <nothing> OK, what is 'accessibility' and where is the conflict? [18:26 supersff:/home/david] # pmq -s | grep accessibility A library providing a set of interfaces for accessibility local/kdemod3-kdeaccessibility 3.5.10-1 (kdemod3-complete kdemod3-vanilla) Huh?? kdemod3 is this issue??? Damn! Why can't I have kdemod3 and kde4 installed side-by-side and why can't I install kde-unstable if kdemod3 is installed. kde3 & kde4 can exist side-by-side just fine. What gives?? OK, fine, I'll blow kdemod3 away and try again (Note: I really did not want to have to do this...) pacman -Rs kdemod3-complete basket compizconfig-backend-kconfig filelight ksensors qcad OK, now both kde and everything related to kdemod has been torpedoed. Proceed with installation? [Y/n] checking package integrity... :: File pilot-link-0.12.3-4-i686.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package) pilot-link-0.12.3-4-i686.pkg.tar.gz is invalid or corrupted Errors occurred, no packages were upgraded. Oh for goodness sake! [18:39 supersff:/home/david] # pms kde kde-extragear :: Synchronizing package databases... kdemod-legacy is up to date kde-unstable is up to date core is up to date extra is up to date community is up to date archlinuxfr is up to date kde package not found, searching for group... :: group kde (including ignored packages): kdeaccessibility-colorschemes kdeaccessibility-iconthemes kdeaccessibility-kmag kdeaccessibility-kmousetool <snip> Total Download Size: 0.47 MB Total Installed Size: 1550.16 MB Proceed with installation? [Y/n] :: Retrieving packages from extra... pilot-link-0.12.3-4... 477.9K 126.3K/s 00:00:04 [#################################################################################] 100% checking package integrity... (299/299) checking for file conflicts [#################################################################################] 100% error: could not prepare transaction error: failed to commit transaction (conflicting files) /usr/share/apps/color-schemes/Zion.colors exists in both 'kdeaccessibility- colorschemes' and 'kdeaccessibility' /usr/share/apps/color-schemes/ZionReversed.colors exists in both 'kdeaccessibility-colorschemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/128x128/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/16x16/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/22x22/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/32x32/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/48x48/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/48x48/animations/process-working.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' /usr/share/icons/mono/64x64/animations/process-idle.png exists in both 'kdeaccessibility-iconthemes' and 'kdeaccessibility' / WTF???? This is a BUG, there isn't a damn thing installed and still I get 20000 lines of conflicts.... The same conflicts..... OK, let's disable kdemod- legacy in pacman and try once again. [18:46 supersff:/home/david] # vi /etc/pacman.conf [18:46 supersff:/home/david] # pms kde kde-extragear <snip SAME damn conflicts> Errors occurred, no packages were upgraded. [18:46 supersff:/home/david] # I give up ;-( I'm pulling out the Nuclear option. I have uninstalled everything related to kde and kde-unstable still will not install. This has to be some type of bug. I'll report back after I get my system installed and running.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, Jun 17, 2009 at 6:49 PM, David C. Rankin<drankinatty@suddenlinkmail.com> wrote:
DR, List
Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install).
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type:
<snip>
I give up ;-( I'm pulling out the Nuclear option. I have uninstalled everything related to kde and kde-unstable still will not install. This has to be some type of bug. I'll report back after I get my system installed and running....
So you are right on a few counts. You *don't* have KDE installed, but you told it to get installed when you did the -Syu operation. See how pacman prompts twice for "group kde"? The first time is for the [kde-unstable] repository; the second time is for [extra]. I'm not familiar with the whole KDE setup, so I can't speak for kde-extragear, but this is almost certainly what is going on. Notice your conflict messages- they aren't saying anything about conflicts with the filesystem, but conflicts between packages that are to be installed: usr/lib/libsuperkaramba.so exists in both 'kdeutils-superkaramba' and 'kdeutils' The short-term fix is to do exactly as you did, but only answer "Y" to the first kde group prompt, and "N" to the following one. -Dan
On Wednesday 17 June 2009 19:04:42 Dan McGee wrote:
On Wed, Jun 17, 2009 at 6:49 PM, David C.
Rankin<drankinatty@suddenlinkmail.com> wrote:
DR, List
Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install).
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type:
<snip>
I give up ;-( I'm pulling out the Nuclear option. I have uninstalled everything related to kde and kde-unstable still will not install. This has to be some type of bug. I'll report back after I get my system installed and running....
So you are right on a few counts. You *don't* have KDE installed, but you told it to get installed when you did the -Syu operation.
See how pacman prompts twice for "group kde"? The first time is for the [kde-unstable] repository; the second time is for [extra]. I'm not familiar with the whole KDE setup, so I can't speak for kde-extragear, but this is almost certainly what is going on.
Notice your conflict messages- they aren't saying anything about conflicts with the filesystem, but conflicts between packages that are to be installed: usr/lib/libsuperkaramba.so exists in both 'kdeutils-superkaramba' and 'kdeutils'
The short-term fix is to do exactly as you did, but only answer "Y" to the first kde group prompt, and "N" to the following one.
-Dan
I thought about that too Dan, but that isn't the case. I got the same blow up of conflicts with a simple: pacman -S kde Dunno, something is rotten somewhere... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 18 June 2009 02:49, David C. Rankin wrote:
DR, List
I give up ;-( I'm pulling out the Nuclear option. I have uninstalled everything related to kde and kde-unstable still will not install. This has to be some type of bug. I'll report back after I get my system installed and running....
i think, (tho i haven't checked) that the problem is the "kde" group. it pulls packages from extra too... as said earlier, i had the same issue on a fresh VM. i solved it with the "nuclear" option, but now that i think of it, i didn't try abs. also, as someone suggested, pacman -S kde kde-extragear works if you press "n" the second time it asks you for the group. (i tested the latter and it has no problem at all) -- - We have such sites to show you... - Oh shit....
On Wednesday 17 June 2009 19:08:27 Ed Jobs wrote:
On Thursday 18 June 2009 02:49, David C. Rankin wrote:
DR, List
I give up ;-( I'm pulling out the Nuclear option. I have uninstalled everything related to kde and kde-unstable still will not install. This
has
to be some type of bug. I'll report back after I get my system
installed
and running....
i think, (tho i haven't checked) that the problem is the "kde" group. it pulls packages from extra too...
as said earlier, i had the same issue on a fresh VM. i solved it with the "nuclear" option, but now that i think of it, i didn't try abs.
also, as someone suggested, pacman -S kde kde-extragear works if you press "n" the second time it asks you for the group. (i tested the latter and it has no problem at all)
I'll test as well, I have yet a 3rd spare box with Arch running on it configured with kdemod3. So I can go through this same wonderful process all over again. (but on the bright side, I have kde-unstable packages for both x86_64 and i686 on the local server, so I could do this over-and-over again all night and not have to worry about a download;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, June 17, 2009 7:49 pm, David C. Rankin wrote:
DR, List
Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install).
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type:
Egads! How many times do I have to say it?!?!? 1) First UNINSTALL any existing KDE packages. i.e., repeat: pacman -Rs kde-<whatever> 2) Then, install KDE from unstable. i.e., pacman -S kde Sheesh! :-) DR
On Wednesday 17 June 2009 19:13:54 David Rosenstrauch wrote:
On Wed, June 17, 2009 7:49 pm, David C. Rankin wrote:
DR, List
Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install).
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type:
Egads! How many times do I have to say it?!?!?
1) First UNINSTALL any existing KDE packages. i.e., repeat: pacman -Rs kde-<whatever>
2) Then, install KDE from unstable. i.e., pacman -S kde
Sheesh! :-)
DR
Err umm, DR, umm: Did you miss this part, or are we somehow not communicating? [18:02 supersff:/home/david] # pacman -Rs kde k3b k9copy kdiff3 kde not found, searching for group... :: group kde: kdebase-runtime kdelibs kdemultimedia Remove whole content? [Y/n] then [18:21 supersff:/home/david] # pacman -Q | grep kde | grep -v kdemod3 <nothing> pacman -Rs kdemod3-complete basket compizconfig-backend-kconfig filelight ksensors qcad then I even confirmed with: pacman -Q -s | grep kde <nothing> Then and only then did I pacman -S kde and it still blew up with 20000+ conflicts What else could I have done?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
look at package directory, and try to see if there is any leftover after have removed kde. There should be none, be there should be no bug too. 2009/6/18, David C. Rankin <drankinatty@suddenlinkmail.com>:
On Wednesday 17 June 2009 19:13:54 David Rosenstrauch wrote:
On Wed, June 17, 2009 7:49 pm, David C. Rankin wrote:
DR, List
Here is the situation after the difficulty I had installing kde-unstable on the x86_64 box where I finally just installed with '-f', I have the exact setup on an i686 box where I am trying to install kde-unstable, but this time finding a way to do it without resorting to the '-f' option. On the box, I have kdemod3 installed and configured and I have never specifically installed kde4 from anywhere (I guess I got it by default with the Arch install).
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type:
Egads! How many times do I have to say it?!?!?
1) First UNINSTALL any existing KDE packages. i.e., repeat: pacman -Rs kde-<whatever>
2) Then, install KDE from unstable. i.e., pacman -S kde
Sheesh! :-)
DR
Err umm, DR, umm:
Did you miss this part, or are we somehow not communicating?
[18:02 supersff:/home/david] # pacman -Rs kde k3b k9copy kdiff3 kde not found, searching for group... :: group kde: kdebase-runtime kdelibs kdemultimedia Remove whole content? [Y/n]
then
[18:21 supersff:/home/david] # pacman -Q | grep kde | grep -v kdemod3 <nothing>
pacman -Rs kdemod3-complete basket compizconfig-backend-kconfig filelight ksensors qcad
then I even confirmed with:
pacman -Q -s | grep kde <nothing>
Then and only then did I
pacman -S kde
and it still blew up with 20000+ conflicts
What else could I have done??
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 18 June 2009 01:48:50 ludovic coues wrote:
look at package directory, and try to see if there is any leftover after have removed kde. There should be none, be there should be no bug too.
I still think there may be a bug here. I had to iteratively remove packages even after the first pacman -Rs that should have gotten all the left-overs. It took about 3 go-rounds. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
David C. Rankin wrote:
On Wednesday 17 June 2009 19:13:54 David Rosenstrauch wrote:
On Wed, June 17, 2009 7:49 pm, David C. Rankin wrote:
So far, all packages for kde-unstable have been downloaded to the i686 box when I tried to install kde-unstable with 'pacman -Sy kde kde-extragear'. There were 20000+ lines of conflicts of the following type: Egads! How many times do I have to say it?!?!?
1) First UNINSTALL any existing KDE packages. i.e., repeat: pacman -Rs kde-<whatever>
2) Then, install KDE from unstable. i.e., pacman -S kde
Sheesh! :-)
DR
Err umm, DR, umm:
Did you miss this part, or are we somehow not communicating?
Oops - my bad. I did miss that part. Just read the beginning of the post where you show "pacman -Sy" and I assumed that you skipped all the uninstalls. Of course, we all know what happens when we assume .... :-) Judging from the rest of your post (and some subsequent posts) it sounds like this is some sort of weird conflict between the stock KDE packages and the unstable ones. Apologies for the bad advice (and the pissy tone!) DR
David Rosenstrauch wrote:
Judging from the rest of your post (and some subsequent posts) it sounds like this is some sort of weird conflict between the stock KDE packages and the unstable ones.
I guess you just have to know going in about the potential for this kind of aggravation when you're living in the bleeding-edge world of unstable. :-) DR
On Thursday 18 June 2009 09:39:27 am David Rosenstrauch wrote:
David Rosenstrauch wrote:
Judging from the rest of your post (and some subsequent posts) it sounds like this is some sort of weird conflict between the stock KDE packages and the unstable ones.
I guess you just have to know going in about the potential for this kind of aggravation when you're living in the bleeding-edge world of unstable. :-)
DR
I have no complaints. Linux wouldn't be any fun if it just worked all the time. Life in a world with nothing to bitch about -- boring.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 18 June 2009 01:49:30 David C. Rankin wrote:
WTF???? This is a BUG, there isn't a damn thing installed and still I get 20000 lines of conflicts.... The same conflicts..... OK, let's disable kdemod- legacy in pacman and try once again.
If you would have read my last mail you would now what the problem is and how easy it is to fix... -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
participants (6)
-
Dan McGee
-
David C. Rankin
-
David Rosenstrauch
-
Ed Jobs
-
ludovic coues
-
Pierre Schmitz