On 08/26/2009 06:10 AM, [email protected] wrote:
Sorry, I'm not following what you're trying to say :P
jpeg-7 is masked
It is not, actually. Unless you mean it's keyworded ~arch. But it's
not masked.
Without it any update process stops with this
failure. jpeg-7 needs itsself to update jpeg-7 (according the output
I posted).
Your output tells that something depends on it or that you're explicitly
trying to emerge it.
If I install it, many packaged needs to rebuild, for which I
have not the time.
Which is why I recommended installing media-libs/jpeg-compat :P
When I want to prevent that, I am urged to install another masked
package.
That one is also not masked. Just keyworded ~arch.
Why needs a "non masked" system a masked packed and build against
it (incorporate its masked character) OR needs a compatibility
package which also is masked to not to build (directly) against
the other masked package?
Or in more peotic words:
To live on, take this poison. If you dont want to get poisoned
take the other poison.
Sorry, english is not my native code page...
Since jpeg-7 is not masked, you can mask it yourself. Try this:
=media-libs/jpeg-7
in /etc/portage/packages.mask and see if it helps.
Also, at this point, I would be interested in seeing the output of:
equery depends media-libs/jpeg
to see what is pulling-in jpeg-7.
