[MacPorts] #35321: kdelibs4 needs to depend no longer on liblzma
MacPorts
noreply at macports.org
Thu Jul 26 05:13:16 PDT 2012
#35321: kdelibs4 needs to depend no longer on liblzma
--------------------------------+-------------------------------------------
Reporter: william@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.1
Keywords: | Port: kdelibs4
--------------------------------+-------------------------------------------
Comment(by ryandesign@…):
Replying to [ticket:35321 william@…]:
> When liblzma tries to uninstall itself, it is prevented from doing so in
the following way:
>
{{{
---> Unable to uninstall liblzma @5.0.3_0, the following ports depend on
it:
---> kdelibs4 @4.8.3_2
Error: org.macports.uninstall for port liblzma returned: Please uninstall
the ports that depend on liblzma first.
Please see the log file for port liblzma for details:
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_liblzma_5.0.3_0/liblzma/main.log
Warning: Failed to execute portfile from registry for liblzma @5.0.3_0
---> Unable to uninstall liblzma @5.0.3_0, the following ports depend on
it:
---> kdelibs4 @4.8.3_2
Error: port uninstall failed: Please uninstall the ports that depend on
liblzma first.
}}}
You can force the uninstallation of liblzma since it is no longer needed
since xz now takes its place:
{{{
sudo port -f uninstall liblzma
}}}
> I'm aware that liblzma has been superseded by xz. Is the correct
solution simply to make kdelibs4 depend on xz instead of liblzma?
Yes, and that has already happened in r94904. The reason this upgrade did
not go smoothly is that the revision of kdelibs4 (and other ports that
depended on liblzma) was not also increased at the same time. The problem
will go away the next time kdelibs4's version or revision is increased for
any other reason. Or you could also force kdelibs4 to rebuild now, if it
bothers you:
{{{
sudo port -n upgrade --force kdelibs4
}}}
> Incidentally, Macports is at version 2.1.2, and this bug is still
present, but that has not yet appeared in trac, so I set it to 2.1.1
(where I first saw the problem)!
Thanks, I have added 2.1.2 to the list of versions.
--
Ticket URL: <https://trac.macports.org/ticket/35321#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list