On 12/08/2013 20:05, Paul Klos wrote: > Op dinsdag 13 augustus 2013 01:54:00 schreef Andrew Lowe: >> On 08/11/13 01:16, Daniel Frey wrote: >>> On 08/10/2013 09:27 AM, Andrew Lowe wrote: >>>> Hi all, >>>> As per usual an update of Libre Office is failing and causing all >>>> sorts of build troubles. I have an install, the previous version, of >>>> Libre Office working so how do I stop portage from trying to update to >>>> the latest. >>>> >>>> >>>> [ebuild UD ] app-office/libreoffice-4.0.4.2 [4.1.0.1] >>>> >>>> What do I have to fiddle so that portage won't want to upgrade >>>> libreoffice? This is stopping my "-NuD world" from completing so I need >>>> to suppress libreoffice for the time being and come back to it later. >>>> >>>> Any thoughts, greatly appreciated, >>>> >>>> Andrew >>>> >>> >>> You can use the --exclude parameter (I think?) and it will ignore it for >>> the one command, then after everything is updated you can solve it >>> further. Try: >>> >>> emerge --exclude app-office/libreoffice -NuD world >>> >>> This is not a permanent change but it will allow you to complete your >>> update, then you can set the masking afterwards. >>> >>> Dan >>> >>> >> It worked. Thanks. Now to get this all sorted out and Libre Office to >> build at leisure. >> >> Andrew >> > FWIW, I had initially unmasked a bunch of stuff (suggested by portage) to get > the first 4.x version of LO to compile. Upgrading to 4.0.4.2 only worked > after I had upgraded boost and boost-build from 1.52 to 1.53. Portage had > nothing to say about it, the build just failed with some weird boost errors.
You should log that as a bug, chances are good the devs are not aware of it. They can't test every combination and so rely on us users to report combinations shown to not work. -- Alan McKinnon Systems Engineer^W Technician Infrastructure Services Internet Solutions +27 11 575 7585 -- Alan McKinnon alan.mckin...@gmail.com
