ewald.tienkamp.nl » blocks

Gentoo blocker: AdobeFlash-10.1 license

Ewald — Mon, 21 Jun 2010 10:32:53 +0000

Lately, my Adobe Flash on Gentoo amd64 complained about being blocked by the Adobe Flash 10.0 license and since yesterday the 10.1 one. Blocked by a license? Had never seen that before…

As of yesterday, emerge -uDN world spits out the following for me:
!!! The following updates are masked by LICENSE changes: - www-plugins/adobe-flash-10.1.53.64 (masked by: AdobeFlash-10.1 license(s)) A copy of the 'AdobeFlash-10.1' license is located at '/usr/portage/licenses/AdobeFlash-10.1'.
!!! The following installed packages are masked: - www-plugins/adobe-flash-10.0.45.2 (masked by: AdobeFlash-10 license(s)) A copy of the 'AdobeFlash-10' license is located at '/usr/portage/licenses/AdobeFlash-10'.
Now I could have looked into the 10.0 error, but hey, it was already installed, so who cares. I could have also paid attention to the notice below the block telling me to look into “the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook“. I just couldn’t be bothered. But, since 10.1 popped up, I resorted to searching the web in hopes of finding a quick and easy way to solve this blocker.

Turns out that just yesterday, the Spanish GFO presented the correct way to fix this. You can simply create the file /etc/portage/package.license and add a line that accepts the AdobeFlash-10.1 license for the Adobe Flash package in portage:
echo "www-plugins/adobe-flash AdobeFlash-10.1" >> /etc/portage/package.license

Just add the line with the command above and rerun emerge -uDN world to upgrade Adobe Flash.

Update Jun 21, 2010 @ 14:00: You will, however, need the nspluginwrapper package to use Adobe Flash in a 64-bit browser. Also note this bugreport in special and the other bugreports in general.

This week’s blockers: perl-core/Compress-Zlib and perl-core/IO-Compress-Zlib

Ewald — Sun, 21 Jun 2009 13:11:57 +0000

Less than a week after my previous post on blockers caused by poppler, perl-core/Compress-Zlib and perl-core/IO-Compress-Zlib pop up as blockers in my emerge -uDN world.

This week’s update greeted me with the following message:

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

(‘installed’, ‘/’, ‘perl-core/IO-Compress-Zlib-2.015′, ‘nomerge’) pulled in by
perl-core/IO-Compress-Zlib required by world

(‘ebuild’, ‘/’, ‘perl-core/IO-Compress-2.020′, ‘merge’) pulled in by
~perl-core/IO-Compress-2.020 required by (‘installed’, ‘/’, ‘perl-core/IO-Zlib-1.09′, ‘nomerge’)
~perl-core/IO-Compress-2.020 required by (‘ebuild’, ‘/’, ‘virtual/perl-Compress-Zlib-2.020′, ‘merge’)
~perl-core/IO-Compress-2.020 required by (‘ebuild’, ‘/’, ‘virtual/perl-IO-Compress-Base-2.020′, ‘merge’)
(and 5 more)

(‘installed’, ‘/’, ‘perl-core/Compress-Zlib-2.015′, ‘nomerge’) pulled in by
perl-core/Compress-Zlib required by world

Fortunately, after seeing this and having seen poppler doing the exact same, I knew the solution. Clearly perl-core/Compress-Zlib and perl-core/IO-Compress-Zlib were somehow present in world, while they should be mere dependencies.

The fix was just like last week’s fix:
emerge -C perl-core/Compress-Zlib perl-core/IO-Compress-Zlib

Easy does it! For more details, see the previous post.

emerge -u world causes poppler blocks

Ewald — Mon, 15 Jun 2009 12:59:32 +0000

When updating world, as we should all do every now and then, yesterday I was confronted with a number of different blocks relating to poppler. Usually I find it easiest to unmerge a blocking package by hand and see if the dependency conflict resolves itself. This time that wasn’t quite what I needed.

During my initial emerge -uDN world I was confronted with the following list of blocks:

Conflict: 7 blocks (6 unsatisfied)

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

(‘ebuild’, ‘/’, ‘dev-libs/poppler-glib-0.10.7′, ‘merge’) pulled in by
~dev-libs/poppler-glib-0.10.7[cairo] required by (‘installed’, ‘/’, ‘media-gfx/gimp-2.6.4′, ‘nomerge’)
~dev-libs/poppler-glib-0.10.7[cairo] required by (‘ebuild’, ‘/’, ‘virtual/poppler-glib-0.10.7′, ‘merge’)

(‘ebuild’, ‘/’, ‘dev-libs/poppler-qt3-0.10.7′, ‘merge’) pulled in by
~dev-libs/poppler-qt3-0.10.7 required by (‘installed’, ‘/’, ‘kde-base/kpdf-3.5.10-r1′, ‘nomerge’)
~dev-libs/poppler-qt3-0.10.7 required by (‘ebuild’, ‘/’, ‘virtual/poppler-qt3-0.10.7′, ‘merge’)

(‘installed’, ‘/’, ‘app-text/poppler-bindings-0.10.5-r1′, ‘nomerge’) pulled in by
app-text/poppler-bindings required by world

(‘ebuild’, ‘/’, ‘app-text/poppler-utils-0.10.7′, ‘merge’) pulled in by
~app-text/poppler-utils-0.10.7[abiword] required by (‘ebuild’, ‘/’, ‘virtual/poppler-utils-0.10.7′, ‘merge’)
~app-text/poppler-utils-0.10.7[abiword] required by (‘installed’, ‘/’, ‘net-print/cups-1.3.10-r1′, ‘nomerge’)

(‘ebuild’, ‘/’, ‘dev-libs/poppler-0.10.7′, ‘merge’) pulled in by
~dev-libs/poppler-0.10.7 required by (‘ebuild’, ‘/’, ‘dev-libs/poppler-glib-0.10.7′, ‘merge’)
~dev-libs/poppler-0.10.7 required by (‘ebuild’, ‘/’, ‘virtual/poppler-0.10.7′, ‘merge’)
~dev-libs/poppler-0.10.7 required by (‘installed’, ‘/’, ‘app-office/openoffice-3.0.0′, ‘nomerge’)
(and 2 more)

For more information about Blocked Packages, please refer to [snip]

Now if I read through this list carefully I might have spotted the culprit before resorting to a websearch, but unfortunately I didn’t. Both poppler*-0.10.7 and poppler*-0.10.5-r1 were required and I didn’t realize why.

Turns out the solution was my sloppy Gentoo-past haunting me: poppler does not belong in world. In the past I may have emerged software that did not belong in world without -1, as I just didn’t see the issue with that. Well, here it was.

To remove poppler (and others) from world, use:
emerge -C app-text/poppler app-text/poppler-bindings
Followed by
emerge -uDN world
(assuming you have set –ask (and –verbose) as EMERGE_DEFAULT_OPTS)

For anyone who, after reading this, is still somewhat puzzled as to the how and why of world, try the Gentoo documentation on Portage or browse through man emerge.

In my own (probably not quite correct) words: whenever you install a major piece of software, use emerge without -1, to ensure it is recorded in the so called world file. Whenever you update your world file using emerge -u world, the packages in the world file will be updated. In case a package is a dependency, Portage will automatically upgrade it once something in the world file requests it. As poppler was recorded in the world file, while it should have been a dependency, a conflict arose when other package in world were requesting an update. So whenever you have the need to manually install a dependency, use emerge -1 [packagename].

TL;DR: no dependencies in world please.