Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 493844 - x11-libs/libfm-1.1.4 should not block lxde-base/lxshortcut
Summary: x11-libs/libfm-1.1.4 should not block lxde-base/lxshortcut
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Markos Chandras (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-10 16:33 UTC by jospezial
Modified: 2013-12-10 19:07 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jospezial 2013-12-10 16:33:49 UTC 
libfm-1.1.4.ebuild blocks lxshortcut .
lxde-meta-0.5.5-r3.ebuild depends on lxshortcut .
libfm-1.1.4 does not install lxshortcut .



I unmerged lxshortcut, installed libfm-1.1.4.ebuild and installed lxshortcut-0.1.2 --nodeps and there were no file collisions in log.


>>> Installing (1 of 1) lxde-base/lxshortcut-0.1.2
 * checking 6 files for package collisions
>>> Merging lxde-base/lxshortcut-0.1.2 to /
--- /usr/
--- /usr/share/
>>> /usr/share/lxshortcut/
>>> /usr/share/lxshortcut/lxshortcut.ui
>>> /usr/share/lxshortcut/choose-icon.ui
--- /usr/share/locale/
--- /usr/share/locale/de/
--- /usr/share/locale/de/LC_MESSAGES/
>>> /usr/share/locale/de/LC_MESSAGES/lxshortcut.mo
--- /usr/share/doc/
>>> /usr/share/doc/lxshortcut-0.1.2/
>>> /usr/share/doc/lxshortcut-0.1.2/README.bz2
>>> /usr/share/doc/lxshortcut-0.1.2/ChangeLog.bz2
--- /usr/bin/
>>> /usr/bin/lxshortcut
>>> lxde-base/lxshortcut-0.1.2 merged.
>>> Regenerating /etc/ld.so.cache...
>>> Auto-cleaning packages...
Comment 1 Markos Chandras (RETIRED) gentoo-dev 2013-12-10 19:07:38 UTC 
Sorry my fault.

Fixed

+  10 Dec 2013; Markos Chandras <hwoarang@gentoo.org> libfm-1.1.4.ebuild,
+  libfm-9999.ebuild:
+  Do not block lxde-base/lxshortcut. Bug #493844