2018-03-25 15:50 GMT+03:00 Neil Bothwick <[email protected]>:
> On Sun, 25 Mar 2018 15:19:33 +0300, gevisz wrote:
>
>> It seems that newly introduced x11-base/xorg-proto-2018.4 package
>> blocks everything else. What to do?
>> Is there better option in this case than unmerging xorg-server?
>> Thank you.
>>
>> # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating dependencies... done!
>> [ebuild U ] sys-apps/rename-1.3-r2 [1.3]
>> [ebuild U ] sys-devel/autoconf-archive-2017.09.28 [2017.03.21]
>> [ebuild U ] app-misc/pax-utils-1.2.3 [1.2.2-r2]
>> [ebuild U ] sys-apps/sandbox-2.13 [2.12]
>> [ebuild N ] x11-base/xorg-proto-2018.4
...
>> [blocks B ] <x11-proto/scrnsaverproto-1.2.2-r2
>> ("<x11-proto/scrnsaverproto-1.2.2-r2" is blocking
>> x11-base/xorg-proto-2018.4)
>>
>> * Error: The above package list contains packages which cannot be
>> * installed at the same time on the same system.
>
> The only hard block here appears to be xscrnsaverproto, unmerge that and
> the rest should take care of themselves. I had all the soft blocks today
> but not that one, and everything worked fine.
Unmerging the scrnsaverproto package did not changed the message from
portage. However, adding --exclude scrnsaverproto --exclude chromium
to the command above helped a bit. So, now, I have the following:
# emerge --update --deep --with-bdeps=y --newuse --backtrack=100 --ask
world --exclude chromium
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] x11-proto/scrnsaverproto-1.2.2-r1 USE="-doc"
ABI_X86="(64) -32 (-x32)"
[blocks B ] <x11-proto/scrnsaverproto-1.2.2-r2
("<x11-proto/scrnsaverproto-1.2.2-r2" is blocking
x11-base/xorg-proto-2018.4)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
(x11-base/xorg-proto-2018.4:0/0::gentoo, installed) pulled in by
x11-base/xorg-proto required by
(x11-proto/renderproto-0.11.1-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xf86bigfontproto-1.2.0-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/glproto-1.4.17-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/fixesproto-5.0-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xproto-7.0.31-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/dri2proto-2.8-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/compositeproto-0.4.2-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/randrproto-1.5.0-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/inputproto-2.3.2-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/resourceproto-1.2.0-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/videoproto-2.3.3-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/kbproto-1.0.7-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/fontsproto-2.1.3-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xf86vidmodeproto-2.3.1-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/trapproto-3.4.3-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xf86driproto-2.1.1-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/damageproto-1.2.1-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/recordproto-1.14.2-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xineramaproto-1.2.1-r2:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/presentproto-1.1-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xcmiscproto-1.2.2-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xf86dgaproto-2.1-r3:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/xextproto-7.3.0-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/bigreqsproto-1.1.2-r1:0/0::gentoo, installed)
x11-base/xorg-proto required by
(x11-proto/dri3proto-1.0-r1:0/0::gentoo, installed)
(x11-proto/scrnsaverproto-1.2.2-r1:0/0::gentoo, ebuild scheduled for
merge) pulled in by
>=x11-proto/scrnsaverproto-1.2.2-r1[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
(>=x11-proto/scrnsaverproto-1.2.2-r1[abi_x86_64(-)]) required by
(x11-libs/libXScrnSaver-1.2.2-r1:0/0::gentoo, installed)
>=x11-proto/scrnsaverproto-1.1 required by
(x11-base/xorg-server-1.19.5-r1:0/1.19.5::gentoo, installed)
For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):
https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages
# revdep-rebuild
* This is the new python coded version
* Please report any bugs found using it.
* The original revdep-rebuild script is installed as revdep-rebuild.sh
* Please file bugs at: https://bugs.gentoo.org/
* Collecting system binaries and libraries
* Checking dynamic linking consistency
Your system is consistent
# emerge --depclean --backtrack=120 --ask
* Always study the list of packages to be cleaned for any obvious
* mistakes. Packages that are part of the world set will always
* be kept. They can be manually added to this set with
* `emerge --noreplace <atom>`. Packages that are listed in
* package.provided (see portage(5)) will be removed by
* depclean, even if they are part of the world set.
*
* As a safety measure, depclean will not remove any packages
* unless *all* required dependencies have been resolved. As a
* consequence of this, it often becomes necessary to run
* `emerge --update --newuse --deep @world` prior to depclean.
Calculating dependencies... done!
* Dependencies could not be completely resolved due to
* the following required packages not being installed:
*
* >=x11-proto/scrnsaverproto-1.2.2-r1[abi_x86_64(-)] pulled in by:
* x11-libs/libXScrnSaver-1.2.2-r1
*
* Have you forgotten to do a complete update prior to depclean? The
* most comprehensive command for this purpose is as follows:
*
* emerge --update --newuse --deep --with-bdeps=y @world
*
* Note that the --with-bdeps=y option is not required in many
* situations. Refer to the emerge manual page (run `man emerge`)
* for more information about --with-bdeps.
*
* Also, note that it may be necessary to manually uninstall
* packages that no longer exist in the portage tree, since it may
* not be possible to satisfy their dependencies.
I don't think that old chromium package is a culprit here but will try
to unmerge it as well.
Any more ideas?
