[solved] Slim themes conflict with e2fsprogs

I tried installing a couple of slim themes, and got a message saying...
util-Linux-ng conflicts with e2fsprogs. Remove e2fsprogs?
I am currently on my desktop trying to install arch on a old laptop.
Last edited by Jboxer (2010-02-08 01:24:46)

I have discovered e2fsprogs has to deal with Ext2 Filesystem Utilities, i have installed Ext4, therefore I might try to remove the programs that are dependent of e2fsprogs. I would like to receive some more suggestions before I do anything.
Edit: It also is used for Ext4, so scratch that idea.
Last edited by Jboxer (2010-02-07 22:43:20)

Similar Messages

[solved]util-linux-ng conflicts with e2fsprogs

i encount this error msg when i am installing apache server in my archlinux,at first i think that is a apache dependencies problem,but later,when i install other program pacman shows the same error msg.so i remove the e2fsprogs,but more programs need e2fsprogs.
what should i do then?
Last edited by yisohoo (2009-09-26 04:58:17)

I had the same problem at install hal, ( pacman -S extra/hal )
CONFLICT util-linux-ng conflicts with e2fsprogs .. remove y/n ? -->> fail by dependences...
pacman -Syu --->>> SOLVED !!
Thx.

Cannot install xorg Get error about a conflict with e2fsprogs?

IIRC, I got this error message:
:: util-linux-ng conflicts with e2fsprogs. Remove e2fsprogs? [Y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
And this message, too:
cryptsetup: requires e2fsprogs
I'm stuck.
Looks like I'm gonna reformat again!
Last edited by RJARRRPCGP (2010-02-09 00:05:24)

wonder wrote:
RJARRRPCGP wrote:
IIRC, I got this error message:
:: util-linux-ng conflicts with e2fsprogs. Remove e2fsprogs? [Y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
Looks like I'm gonna reformat again!
not really, just do pacman -Syu
Fixed it, for some reason, pacman didn't do a full update. Was wondering why I didn't see much being updated.
Syu did the trick.

[SOLVED] kdebase-workspace: conflicts with kdemod-kde-common

Hi! My pacman -Syu failed today: Here there is the output (of a retrial):
:: Synchronizing package databases...
kdemod-core is up to date
kdemod-extragear is up to date
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
:: Replace qtmod with kdemod-core/kdemod-kde-common? [Y/n] Y
:: Replace guidance-power-manager with extra/kdebase-workspace? [Y/n] Y
resolving dependencies...
looking for inter-conflicts...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kdebase-workspace: conflicts with kdemod-kde-common
Any suggestions on how to get this update right?
Last edited by joan (2009-02-23 02:18:30)

joan wrote:Hi! My pacman -Syu failed today: Here there is the output (of a retrial):
:: Replace qtmod with kdemod-core/kdemod-kde-common? [Y/n] Y
:: Replace guidance-power-manager with extra/kdebase-workspace? [Y/n] Y
Any suggestions on how to get this update right?
Try:
pacman -Rd gtmod
pacman -S qt
#Qtmod not needed anymore
pacman -R guidance-power-manager /or pacman -Rcsn ....
pacman -Syu kdemod /or pacman -Syu kdemod-complete
also backup/ remove ~/.kde4 to start with clean config, especially if you have your own plasmoids.
#powerdevil is included in kde now, so other inferior powermanagers might conflict with it.

[SOLVED]gnumeric-goffice conflicts with abiword-goffice0.8

Gnumeric updated today and apparently is preventing abiword from launching. The goffice versions conflict. I assume abiword will update soon and all will be fixed.
[chris@N281G ~]$ abiword
abiword: error while loading shared libraries: libgoffice-0.8.so.8: cannot open shared object file: No such file or directory
[chris@N281G ~]$ sudo pacman -S goffice
warning: downgrading package goffice (0.10.0-1 => 0.8.17-1)
resolving dependencies...
looking for inter-conflicts...
:: goffice and goffice0.8 are in conflict. Remove goffice0.8? [y/N] n
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: goffice and goffice0.8 are in conflict (goffice<0.10)
edit: just had to install goffice0.8
Last edited by czubek (2012-12-24 17:25:50)

rightwingrb wrote:Also...I have no idea what "code" tags are but hopefully the above is acceptable ;-)
When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.
Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309
Last edited by karol (2014-02-18 22:23:24)

[SOLVED]"fontconfig conflicts with fontconfig-ubuntu" and other issues

Almost every program I have has stopped working. If I run a program from a terminal (one of the virtual terminals, gnome-terminal wont work either), they either complain about not being able to find libpng or libjpeg. I read the news posting about these and some forum posts, but none of them mentioned people having problems. What I understood from reading is that I just need to update my system.
This is where the problem lies. I cannot run "pacman -Syu" as usual. When I do, I get the following error:
fontconfig conflicts with fontconfig-ubuntu. Remove fontconfig-ubuntu?
If I answer yes, I get:
error: failed to prepare transaction (could not satisfy dependencies)
:: kdelibs: requires phonon
:: cairo-ubuntu: requires fontconfig-ubuntu>=2.6.0
:: libxft-ubuntu: requires fontconfig-ubuntu
If I answer no, I get:
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: fontconfig: conflicts with fontconfig-ubuntu
Either way, nothing is upgraded. How can I resolve this, as well as the libpng/libjpeg issue? I cleaned my cache and tried re-installing them, but it didn't help.
Last edited by DWilliams (2010-02-11 00:35:07)

DWilliams wrote:
Surgat_ wrote:
Or you can check AUR, get the latest pkgbuilds and rebuild your -ubuntu (or -lcd) packages. After installing them, the update should go flawlessly.
Also, if you have KDE installed you should check the news frontpage to see the KDE 4.4 announcement
Alright I installed fontconfig-ubuntu from the AUR and that resolved my initial conflict. It started complaining about gtk-qt-engine and kdelibs and they weren't depended on by anything so I just removed them (I assume I can re-install them later) and now my system upgrade is underway. Hopefully things will be fixed when it finishes.
Does anyone know what caused this and whether I can avoid similar issues in the future?
It happens because you are using a modified version of fontconfig (the ubuntu one). When a new version of fontconfig reaches [extra], pacman tries to update fontconfig (because fontconfig-ubuntu provides fontconfig, and fontconfig from [extra] is newer than the version you have installed) and finds that it conflicts with fontconfig-ubuntu.
The way to go is the one that you have followed: when there is an update in fontconfig, update your fontconfig-ubuntu package to the latest in AUR (hopefully the same version as the new one in [extra], else you'll have to wait or modify the PKGBUILD) and then update the rest of the system.

Unable to open Aperture 2 because it is apparently in conflict with an old trial version 3. Any tips how to solve this?

I am unable to open my Aperture2.
The following warning message shows on top of the ususl opening window:
Quote
The libraryin "users/pedro/pictures/Aperture 3 Trial Library2.aplibrary" cannot be loaded because it is from newer version of Aperture.
Unquote
It looks like some kind of conflict with an old trial version 3, to which I never upgraded.
Any tips to help me solving the issue?

Do you need to run Aperture 2, or do you need to open the "Aperture 3 Trial Library2.aplibrary"?
If you only want to run Aperture 2, then launch Aperture by double-clicking your regular Aperture 2 library; this should open Aperture on the correct library. In Aperture 3 you also simply could hold down the options-key while double-clicking the Aperture Applications icon in the Dock - probably this works in Aperture 2 as well,
But if you need to open your Aperture 3 trial library with Aperture 2, because you converted your Aperture 2 library to Aperture 3 format; there is no easy way to do it. The best would be to find a backup of your library from the time before you converted it. If you do not have such a backup, then the easiest way would be to upgrade to Aperture 3 at this point.
I do not know enough about the Aperture 2 library format to be able to tell you how to manually downgrade an Aperture 3 library to Aperture 2 format.
Regards
Léonie

Custom visual styles conflicting with Firefox theme

I've installed a custom visual style on my Windows 7 machine. The thing is, it seems to conflict with Firefox's layout. It doesn't affect Google Chrome at all. But it changes Firefox's layout - and when I try to install a theme into Firefox, it really messes it up. Anyway I can tell firefox to ignore the visual style applied in the computer? Maybe in the userChrome.css file?

Ok,
Finally found a way to get this working. First you need to add the class from a related COM/XP styling Microsoft KB article (http://support.microsoft.com/kb/830033) into your .NET forms project. The class EnableThemingInScope will selectively apply XP styling. In my Form Main method I have removed the call to EnableVisualStyles , and instead invoke the EnableThemingInScope constructor around the call to Application.Run. Now I can have XP styling for my forms app and retain the default look and feel of the TestStand UI controls. Hope this helps someone else.
static void Main()
// doesn't work with TestStand 3.5 UI controls -- Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.DoEvents();
using (new EnableThemingInScope(true))
Application.Run(new MainForm());

[SOLVED] SLiM background no longer persists with Openbox

Hello,
I've been using SLiM and Openbox in conjunction for a while now, and one of the features I really liked was how, after logging in, the slim theme would become the Openbox desktop background.
(I didn't set up any configuration file to do this. It happens by default, and as far as I know it might be a bug.)
Recently, I decided to try out some other login managers. Eventually, I decided to return to using SLiM.
Now, however, after logging in, Openbox blanks the screen, replacing the SLiM theme with the default grey background.
I don't know if one of the other login managers modified some configuration files, or if something completely different is happening.
In short, I have two questions:
Has anyone else experienced this behaviour between SLiM and Openbox? If so, can anyone confirm whether or not the persistent background is a bug or intentional?
What files cause Openbox to blank the screen on startup? How could I disable this?
Thanks in advance for your help/input, everyone.
Last edited by Dekusola (2014-08-05 20:49:08)

I'm pretty sure this behavior is a bug. I use SLIM and if you don't set the background after you log in, the SLIM background will persist including any prompts that might pop up (try pressing F1 to bring up the WM selection prompt and then log in to see what I mean).
I use hsetroot from the AUR with Openbox to set the background at start up by putting it in ~/.config/openbox/autostart.
There are also other similiar programs you can use to set the background with openbox like nitrogen, feh, to name a few. Take your pick.
Here is the relevant section from the openbox wiki page https://wiki.archlinux.org/index.php/Op … d_programs

[Solved] phonon conflicts with qt

pyther@tux: sudo pacman -Su ~
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: kdelibs: requires phonon
pyther@tux: sudo pacman -S phonon ~
resolving dependencies...
warning: provider package was selected (phonon-gstreamer provides phonon-backend)
looking for inter-conflicts...
:: phonon conflicts with qt. Remove qt? [Y/n]
error: failed to prepare transaction (could not satisfy dependencies)
:: phonon-gstreamer: requires qt
:: phonon: requires qt
:: kdelibs: requires qt>=4.5.3-4
:: mythtv-fixes-vdpau: requires qt
:: phonon-xine: requires qt>=4.5.2-3
:: polkit-qt: requires qt
:: soprano: requires qt
:: strigi: requires qt
:: vlc: requires qt
I'm not sure what to do here, phonon says it depends on qt (pacman -Si phonon), but apparently I'm getting an error.
Last edited by pyther (2010-02-01 17:09:26)

pyther wrote:Sorry for the noise!
Don't be sorry. I wouldn't have found Pierre's email without your post. I just upgraded to testing, and I had forgotten about reading the dev mailing list.
So, uh, actually ... thank you for posting!

How do I solve my FONT conflict issue with the system Helvetica Neue

Everytime I start up in Leopard I get the error message "There is a conflict with the "HelveticaNeue" font file". How do I resolve this issue? I require the Postscript versions of Helvetica Neue for my design programs. I use Linotype FontExplorer to manage the fonts. Is there a way to rename these postscript versions so they don't conflict?

Currently, the only way is to remove Apple's supplied versions of Helvetica. They have exactly the same internal names as the PostScript versions. Follow the instructions in section 4 of my article, Font Management in OS X, to see how to do that.
The link, or one of the links above directs you to my personal web site. While the information is free, it does ask for a contribution. As such, I am required by Apple's rules for these discussions to include the following disclaimer.
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Avahi conflicts with nss-mdns. [solved]

I'm confused. Went to update today, and got this message:
:: avahi conflicts with nss-mdns. Remove nss-mdns? [Y/n]
I thought 'Fair enough...' but I always check packages like this with -Si to know what's actually happening in my system. Soo, I run:
$ pacman -Si avahi
Repository : extra
Name : avahi
Version : 0.6.6-2
Groups : None
Provides : howl mdnsresponder
Depends On : dbus libcap libdaemon nss-mdns
Conflicts With : howl mdnsresponder
Replaces : None
Size (compressed) : 557952
Description : A multicast/unicast DNS-SD framework
MD5 Sum : 52ec5424dde107d8099637feb3076925
Now, this is why I'm confused. -Si tells me avahi depends on nss-mdns. When I try to install, it tells me they conflict.
So.... which is right?
-=edit=-
Okay, I've found something else out that may be pertinent. Currently, the packages I have for avahi and nss-mdns depend on each other. That is:
$pacman -Si nss-mdns avahi
Name : nss-mdns
Version : 0.7-3
Depends On : avahi
Required By : avahi kdelibs
Name : avahi
Version : 0.6.5-1
Depends On : dbus libcap libdaemon nss-mdns
Required By : nss-mdns
However there are new packages for both avahi and nss-mdns available in the repos. (0.7-4 and 6.6-2 respectively)
The thing is, pacman isn't picking up the new nss-mdns package with a -Syu operation, and gives me that conflicts line... I'm going to try updating nss-mdns first then see if that fixes it.
-=edit again=-
Geez, I hate it when I post something and moments later figure it out myself. The newest versions of nss-mdns and avahi break the dependancy cycle I noted above; that is, nss-mdns no longer depends on avahi. If I manually updated nss-mdns first, pacman now installs avahi with no problem.
I'm wondering, is this worth a bug report? I'm not surprised a cyclic dependancy like that would cause wierd behaviour...

murkus wrote:snip
$ pacman -Si avahi
Repository : extra
Name : avahi
Version : 0.6.6-2
Provides : howl mdnsresponder
Depends On : dbus libcap libdaemon nss-mdns
Conflicts With : howl mdnsresponder
You get that error because they DO conflict. Do you have mdnsresponder installed?
If so, and you want avahi, then you'll have to remove mdnsresponder and install avahi.

Gtk-gir conflicts with atk and gtk2 updates [SOLVED]

When upgrading with pacman -Syu I get the following error:
error: failed to commit transaction (conflicting files)
atk: /usr/share/gir-1.0/Atk-1.0.gir exists in filesystem
gtk2: /usr/share/gir-1.0/Gdk-2.0.gir exists in filesystem
gtk2: /usr/share/gir-1.0/GdkPixbuf-2.0.gir exists in filesystem
gtk2: /usr/share/gir-1.0/Gtk-2.0.gir exists in filesystem
Errors occurred, no packages were upgraded.
Checking with pacman -Qo /usr/share/gir-1.0/Atk-1.0.gir gives:
/usr/share/gir-1.0/Atk-1.0.gir is owned by gtk-gir 0.6.5-1
And pacman -Qi gtk-gir gives:
Name : gtk-gir
Version : 0.6.5-1
URL : http://live.gnome.org/GObjectInstrospection
Licenses : GPL
Groups : None
Provides : None
Depends On : gobject-introspection>=0.6.5 gtk2
Optional Deps : None
Required By : libdesktop-agnostic-gnome-bzr
Conflicts With : None
Replaces : None
Installed Size : 3676.00 K
Packager : Unknown Packager
Architecture : x86_64
Build Date : Tue 23 Mar 2010 05:17:59 PM CET
Install Date : Tue 23 Mar 2010 05:18:07 PM CET
Install Reason : Installed as a dependency for another package
Install Script : No
Description : GIR interface description files for GTK+
The dependencies can be tracked up to my installation of aur/avant-window-navigator-0.4-bzr 20100211-1
I'm stumped. Can you help me get around this problem?
Thanks!
Last edited by mattmurdock (2010-04-05 22:59:04)

@wonder
Thanks for the tip! It makes sense.
However, the current PKGBUILD for libdesktop-agnostic-gnome-bzr speaks about dependencies like so:
depends=('glib2' 'gtk2>=2.20.0' 'gconf' 'gnome-vfs' 'gnome-desktop')
makedepends=('bzr' 'python' 'pygobject' 'pygtk' 'vala' 'gobject-introspection')
optdepends=('python')
conflicts=('libdesktop-agnostic')
And I still get the build error. I suspect the workaround is to force a removal of gtk-gir but I'm hesitating because I really don't want to break my AWN installation.
Am I being too cautios - or is there a better way of doing this?
Thanks!

[SOLVED] systemd-arch-units conflicts with mdadm and xinetd packages

Trying to upgrade my testing box today to latest/greatest and running into a file conflict between systemd-arch-linux providing systemd profiles for xinetd and mdadm which also think they control the same files:
error: failed to commit transaction (conflicting files)
/usr/lib/systemd/system/mdadm.service exists in both 'mdadm' and 'systemd-arch-units'
/usr/lib/systemd/system/xinetd.service exists in both 'systemd-arch-units' and 'xinetd'
Errors occurred, no packages were upgraded.
Should I just do a force? I am not relying on systemd yet. Or should I just remove systemd?
Chester
Last edited by chetwisniewski (2012-05-15 18:17:45)

silent wrote:So now the new version of mdadm and xinetd moved to [core] and I have the same conflict with systemd-arch-units in [community].
Try -Syu again?

Error: exo-devel conflicts with exo [SOLVED]

I am trying to install xfce4-goodies and I receive an error about exo-devel conflicting with exo when trying to install. Any suggestions?
error: exo-devel conflicts with exo

Snowman wrote:Perhaps you have a custom/unofficial repo in your pacman.conf. However, this should work:
# pacman -S exo
# pacman -S xfce4-goodies
No custom or unoffical repos in pacman.conf.
I tried your suggestion above, and am seeing this...
# pacman -S exo
Targets: exo-0.3.0-3
Total Package Size: 0.2 MB
Proceed with upgrade? [Y/n]
:: Retrieving packages from extra...
exo-0.3.0-3 [################] 100% 212K 276.0K/s 00:00:00
checking package integrity... done.
loading package data... done.
checking for file conflicts... done.
installing exo... done.
After that I attempted to install xfce4-goodies and receive the following...
# pacman -S xfce4-goodies
:: group xfce4-goodies:
exo terminal xfce4-artwork xfce4-battery-plugin xfce4-clipman-plugin
xfce4-cpugraph-plugin xfce4-datetime-plugin xfce4-diskperf-plugin
xfce4-fsguard-plugin xfce4-minicmd-plugin xfce4-netload-plugin
xfce4-notes-plugin xfce4-sensors-plugin xfce4-showdesktop-plugin
xfce4-systemload-plugin xfce4-taskbar-plugin xfce4-wavelan-plugin
xfce4-weather-plugin xfce4-windowlist-plugin xfce4-xkb-plugin
xfce4-xmms-plugin exo-devel
Install whole content? [Y/n]
:: exo-0.3.0-3: is up to date. Upgrade anyway? [Y/n]
Remove: exo
Targets: exo-0.3.0-3 vte-0.12.2-1 terminal-0.2.4-4 xfce4-artwork-0.0.4-2
xfce4-battery-plugin-0.3.0-2 xfce4-clipman-plugin-0.4.1-3
xfce4-cpugraph-plugin-0.2.2-3 xfce4-datetime-plugin-0.3.1-3
xfce4-diskperf-plugin-1.5-3 xfce4-fsguard-plugin-0.2.0-3
xfce4-minicmd-plugin-0.3.0-2 xfce4-netload-plugin-0.3.3-1
xfce4-notes-plugin-0.11.0-1 xfce4-sensors-plugin-0.7.0-1
xfce4-showdesktop-plugin-0.4.0-2 xfce4-systemload-plugin-0.3.6-2
xfce4-taskbar-plugin-0.2.2-2 xfce4-wavelan-plugin-0.4.1-2
xfce4-weather-plugin-0.4.9-2 xfce4-windowlist-plugin-0.1.0-3
xfce4-xkb-plugin-0.3.5-1 glib-1.2.10-6 gtk-1.2.10-7 xmms-1.2.10-7
xfce4-xmms-plugin-0.3.1-2 perl-uri-1.35-1 exo-devel-0.3.1.8beta2-1
Total Package Size: 8.7 MB
Proceed with upgrade? [Y/n]
:: Retrieving packages from extra...
vte-0.12.2-1 [################] 100% 1065K 419.9K/s 00:00:02
terminal-0.2.4-4 [################] 100% 695K 391.9K/s 00:00:01
xfce4-artwork-0.0.4-2 [################] 100% 1728K 438.8K/s 00:00:03
xfce4-battery-plugin-0.3 [################] 100% 21K 62.8K/s 00:00:00
xfce4-clipman-plugin-0.4 [################] 100% 6K 22.7K/s 00:00:00
xfce4-cpugraph-plugin-0. [################] 100% 13K 41.4K/s 00:00:00
xfce4-datetime-plugin-0. [################] 100% 13K 31.4K/s 00:00:00
xfce4-diskperf-plugin-1. [################] 100% 16K 47.4K/s 00:00:00
xfce4-fsguard-plugin-0.2 [################] 100% 12K 31.3K/s 00:00:00
xfce4-minicmd-plugin-0.3 [################] 100% 6K 20.5K/s 00:00:00
xfce4-netload-plugin-0.3 [################] 100% 19K 52.2K/s 00:00:00
xfce4-notes-plugin-0.11. [################] 100% 16K 49.0K/s 00:00:00
xfce4-sensors-plugin-0.7 [################] 100% 23K 58.9K/s 00:00:00
xfce4-showdesktop-plugin [################] 100% 9K 31.3K/s 00:00:00
xfce4-systemload-plugin- [################] 100% 15K 46.4K/s 00:00:00
xfce4-taskbar-plugin-0.2 [################] 100% 6K 23.4K/s 00:00:00
xfce4-wavelan-plugin-0.4 [################] 100% 139K 229.5K/s 00:00:00
xfce4-weather-plugin-0.4 [################] 100% 332K 319.8K/s 00:00:01
xfce4-windowlist-plugin- [################] 100% 9K 31.6K/s 00:00:00
xfce4-xkb-plugin-0.3.5-1 [################] 100% 42K 100.4K/s 00:00:00
xfce4-xmms-plugin-0.3.1- [################] 100% 18K 53.6K/s 00:00:00
perl-uri-1.35-1 [################] 100% 75K 164.3K/s 00:00:00
:: Retrieving packages from current...
xmms-1.2.10-7 [################] 100% 1886K 406.0K/s 00:00:04
:: Retrieving packages from community...
exo-devel-0.3.1.8beta2-1 [################] 100% 592K 301.6K/s 00:00:01
checking package integrity... done.
removing exo... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
opt/xfce4/include/exo-0.3/exo/exo-binding.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-cell-renderer-ellipsized-text.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-config.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-ellipsized-label.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-enum-types.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-gdk-pixbuf-extensions.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-gobject-extensions.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-gtk-extensions.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-icon-bar.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-icon-view.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-md5.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-pango-extensions.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-string.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-toolbars-editor-dialog.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-toolbars-editor.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-toolbars-model.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-toolbars-view.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo-xsession-client.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/include/exo-0.3/exo/exo.h: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/libexo-0.3.a: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/libexo-0.3.so: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/libexo-0.3.so.0: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/pkgconfig/exo-0.3.pc: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/exo-0.3/_exo.a: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/exo-0.3/_exo.so: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/exo-0.3/exo/__init__.py: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/exo-0.3/exo/__init__.pyc: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/exo-0.3/exo/__init__.pyo: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/pyexo.py: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/pyexo.pyc: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/lib/python2.4/site-packages/pyexo.pyo: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/share/locale/de/LC_MESSAGES/libexo-0.3.mo: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/share/locale/en_GB/LC_MESSAGES/libexo-0.3.mo: exists in "exo" (target) and "exo-devel" (target)
opt/xfce4/share/pygtk/2.0/defs/exo-0.3/exo.defs: exists in "exo" (target) and "exo-devel" (target)
errors occurred, no packages were upgraded.

[solved] Slim themes conflict with e2fsprogs

Similar Messages

Maybe you are looking for