trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] Commit c926c513 (amarok) caused a conflict between packages

From: Slávek Banko <slavek.banko@...>
Date: Fri, 14 Feb 2014 09:01:43 +0100
On Friday 14 of February 2014 06:15:30 Michele Calgaro wrote:
> > Why?  What was wrong with share/apps/amarok/icons?  I know with arch, if
> > there is a single naming conflict, the package WILL NOT INSTALL. If the
> > icons were happy in share/apps/amarok/icons -- why not leave them there?
>
> The problem is that the same file (with exactly the same path) is built in
> two different Debian/Ubuntu packages, which then causes a conflict at
> installation time.
>
> Slavek,
> below is the list of errors I get when I update TDE. I don't have *ALL* TDE
> packages installed on my system, but I have a good majority of them (major
> exception is koffice and tde-i18n). So there may be some more conflicts.
> Conflicts are in:
> 1) amarok-common-trinity and konq-plugins-trinity on babelfish.png'
> 2) kopete-trinity and kcmsambaconf.png on kcmsambaconf.png
> Other affected packages are:
> 1) amarok-trinity
> 2) amarok-trinity-dbg
> 3) tdenetwork-trinity
> 4) tdenetwork-trinity-dev
>
> Cheers
>   Michele
>
> --------------------------------------------------------------
> ERROR LIST
> Unpacking amarok-common-trinity (4:14.0.0-b020+20140208) over
> (4:14.0.0-b018+20140126) ... dpkg: error processing archive
> ./applications/amarok/amarok-common-trinity_14.0.0-b020+20140208_all.deb
> (--unpack): trying to overwrite
> '/opt/trinity/share/icons/crystalsvg/22x22/actions/babelfish.png', which is
> also in package konq-plugins-trinity 4:14.0.0-b020+20140208
>
> Unpacking kopete-trinity (4:14.0.0-b020+20140208) over
> (4:14.0.0-b018+20140125) ... dpkg: error processing archive
> ./tdenetwork/kopete-trinity_14.0.0-b020+20140208_amd64.deb (--unpack):
> trying to overwrite
> '/opt/trinity/share/icons/hicolor/16x16/apps/kcmsambaconf.png', which is
> also in package tdenetwork-filesharing-trinity 4:14.0.0-b020+20140208
>
> dpkg: dependency problems prevent configuration of tdenetwork-trinity-dev:
>  tdenetwork-trinity-dev depends on kopete-trinity (=
> 4:14.0.0-b020+20140208); however: Version of kopete-trinity on system is
> 4:14.0.0-b018+20140125.
>
> dpkg: dependency problems prevent configuration of amarok-trinity:
>  amarok-trinity depends on amarok-common-trinity (>=
> 4:14.0.0-b020+20140208); however: Version of amarok-common-trinity on
> system is 4:14.0.0-b018+20140126.
>
> dpkg: dependency problems prevent configuration of tdenetwork-trinity:
>  tdenetwork-trinity depends on kopete-trinity (>= 4:14.0.0-b020+20140208);
> however: Version of kopete-trinity on system is 4:14.0.0-b018+20140125.
>
> dpkg: dependency problems prevent configuration of amarok-trinity-dbg:
>  amarok-trinity-dbg depends on amarok-trinity (= 4:14.0.0-b020+20140208);
> however: Package amarok-trinity is not configured yet.
>
> Errors were encountered while processing:
>  tdenetwork-trinity-dev
>  amarok-trinity
>  tdenetwork-trinity
>  amarok-trinity-dbg
> --------------------------------------------------------------
>

Aha - it seems that kopete / tdenetwork it really is the packaging problem. 
However, the Amarok is definitely a problem in the source code.

Michele, thank you for checking packages. You have installed all packages? 
Respectively, you can check duplicates using extracts of packages content?

Slavek
--