Re: [gentoo-user] OT: github (and gitlab, etc etc): track down a particular commit

[Vadim A. Misbakh-Soloviov]

> Which official released released versions V1.0, V2.0 etc contain a
> particular commit C1ABCDE?

> Unfortunately I know of no direct way of answering either question with
> the web UI of github

Talking about github - you can open the commit page (say, https://github.com/
torvalds/linux/commit/fa41b900c30b45fab03783724932dc30cd46a6be )
And look at the bottom of long description field. There will be a label that 
shows which tag(s) contains this commit.

Re: [gentoo-user] Re: Would unmerging xorg-server certainly help it?

[Akater]

Ian Zimmerman  writes:

> On 2018-03-25 17:49, Martin Vaeth wrote:
>
>> It should be scrnsaverproto-1.2.2-r2 which is pulled in.
>> Maybe you sync'ed at an unfortunate moment. Try emerge --sync again.
>
> In my case at least, the root cause was this: in the nightly webrsync
> snapshot (which I prefer to use instead of rsync),
> scrnsaverproto-1.2.2-r2 is keyworded and not stable.  Adding it to
> portage/package.use magically unblocks everything.

Yep. webrsync here too. Adding

> =x11-proto/scrnsaverproto-1.2.2-r2 ~amd64

to package.accept_keywords unblocked everything for me. Thank you.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: Would unmerging xorg-server certainly help it?

[gevisz]

2018-03-25 22:25 GMT+03:00 Ian Zimmerman :
> On 2018-03-25 17:49, Martin Vaeth wrote:
>
>> It should be scrnsaverproto-1.2.2-r2 which is pulled in.
>> Maybe you sync'ed at an unfortunate moment. Try emerge --sync again.
>
> In my case at least, the root cause was this: in the nightly webrsync
> snapshot (which I prefer to use instead of rsync),
> scrnsaverproto-1.2.2-r2 is keyworded and not stable.  Adding it to
> portage/package.use magically unblocks everything.

The same here:
$ eix scrnsaverproto
* x11-proto/scrnsaverproto
 Available versions:  1.2.2-r1 ~1.2.2-r2 {doc ABI_MIPS="n32 n64
o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"}
 Homepage:https://www.x.org/wiki/
 Description: X.Org ScrnSaver protocol headers

And I also use webrsync.

Re: [gentoo-user] New xorg-proto package blocks everything else.

[gevisz]

2018-03-25 22:02 GMT+03:00 Dale :
> gevisz wrote:
>> 2018-03-25 21:40 GMT+03:00 Franz Fellner :
>>> Just a stupid question: Did you add =scrnsaverproto-1.2.2-r1 to
>>> package.mask?
>> No. Actually, I do not need screensaver at all.
>>
>>> Because the -r2 is stable and nothing should prevent it from being merged...
>> But something does prevent it from being merged.
>>
>>> I am running partly testing and the time xorg-proto was added I had to deal
>>> with hard blocks which I circumvented by un-keywording (remove from
>>> package.accept-keywords) and selectively masking.
>> I have not understood the above comment.
>> But I prefer to stick with stable versions of all packages.
>>
>
> I would try the -t option to see what is pulling it in.  That may shed
> some light on the problem.  Won't hurt anything if it doesn't work either.

$ equery d scrnsaverproto
 * These packages depend on scrnsaverproto:
x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1)

So, it is xorg-server package that pulls scrnsaverproto in.

But I see no way how to switch it off:
$ equery uses xorg-server
[ Legend : U - final flag setting for installation]
[: I - package is installed with flag ]
[ Colors : set, unset ]
 * Found these USE flags for x11-base/xorg-server-1.19.5-r1:
 U I
 - - debug   : Enable extra debug codepaths, like asserts and
extra output. If you want to get meaningful backtraces see

https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
 - - dmx : Build the Distributed Multiheaded X server
 - - doc : Add extra documentation (API, Javadoc, etc). It is
recommended to enable per package instead of globally
 + + glamor  : Enable Glamor OpenGL 2D acceleration
 - - ipv6: Add support for IP version 6
 - - kdrive  : Build the kdrive X servers
 - - libressl: Use dev-libs/libressl instead of dev-libs/openssl
as SSL/TLS provider (ineffective with USE=-ssl), packages should not
depend on this USE flag
 - - minimal : Install a very minimal build (disables, for
example, plugins, fonts, most drivers, non-critical features)
 - - static-libs : Build static versions of dynamic libraries as well
 + + suid: Enable setuid root program, with potential security risks
 - - systemd : Enable use of systemd-specific libraries and
features like socket activation or session tracking
 - - tslib   : Build with tslib support for touchscreen devices
 + + udev: Enable virtual/udev integration (device discovery,
power and storage device support, etc)
 - - unwind  : Enable libunwind usage for backtraces
 - - wayland : Enable dev-libs/wayland backend
 - - xcsecurity  : Build Security extension
 - - xephyr  : Build the Xephyr server
 - - xnest   : Build the Xnest server
 + + xorg: Build the Xorg X server (HIGHLY RECOMMENDED)
 - - xvfb: Build the Xvfb server

[gentoo-user] Re: Would unmerging xorg-server certainly help it?

[Ian Zimmerman]

On 2018-03-25 17:49, Martin Vaeth wrote:

> It should be scrnsaverproto-1.2.2-r2 which is pulled in.
> Maybe you sync'ed at an unfortunate moment. Try emerge --sync again.

In my case at least, the root cause was this: in the nightly webrsync
snapshot (which I prefer to use instead of rsync),
scrnsaverproto-1.2.2-r2 is keyworded and not stable.  Adding it to
portage/package.use magically unblocks everything.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: [gentoo-user] New xorg-proto package blocks everything else.

[Dale]

gevisz wrote:
> 2018-03-25 21:40 GMT+03:00 Franz Fellner :
>> Just a stupid question: Did you add =scrnsaverproto-1.2.2-r1 to
>> package.mask?
> No. Actually, I do not need screensaver at all.
>
>> Because the -r2 is stable and nothing should prevent it from being merged...
> But something does prevent it from being merged.
>
>> I am running partly testing and the time xorg-proto was added I had to deal
>> with hard blocks which I circumvented by un-keywording (remove from
>> package.accept-keywords) and selectively masking.
> I have not understood the above comment.
> But I prefer to stick with stable versions of all packages.
>

I would try the -t option to see what is pulling it in.  That may shed
some light on the problem.  Won't hurt anything if it doesn't work either. 

Dale

:-)  :-) 

Re: [gentoo-user] New xorg-proto package blocks everything else.

[gevisz]

2018-03-25 21:40 GMT+03:00 Franz Fellner :
> Just a stupid question: Did you add =scrnsaverproto-1.2.2-r1 to
> package.mask?

No. Actually, I do not need screensaver at all.

> Because the -r2 is stable and nothing should prevent it from being merged...

But something does prevent it from being merged.

> I am running partly testing and the time xorg-proto was added I had to deal
> with hard blocks which I circumvented by un-keywording (remove from
> package.accept-keywords) and selectively masking.

I have not understood the above comment.
But I prefer to stick with stable versions of all packages.

> 2018-03-25 20:58 GMT+03:00 gevisz :
>>
>> 2018-03-25 20:38 GMT+03:00 gevisz :
>> > 2018-03-25 15:50 GMT+03:00 Neil Bothwick :
>> >> 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-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-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)
>> > 

Re: [gentoo-user] New xorg-proto package blocks everything else.

[Franz Fellner]

Just a stupid question: Did you add =scrnsaverproto-1.2.2-r1 to
package.mask? Because the -r2 is stable and nothing should prevent it from
being merged...
I am running partly testing and the time xorg-proto was added I had to deal
with hard blocks which I circumvented by un-keywording (remove from
package.accept-keywords) and selectively masking.

2018-03-25 20:58 GMT+03:00 gevisz :

> 2018-03-25 20:38 GMT+03:00 gevisz :
> > 2018-03-25 15:50 GMT+03:00 Neil Bothwick :
> >> 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-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-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)
> >
> >   

Re: [gentoo-user] New xorg-proto package blocks everything else.

[gevisz]

2018-03-25 20:38 GMT+03:00 gevisz :
> 2018-03-25 15:50 GMT+03:00 Neil Bothwick :
>> 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-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-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 

[gentoo-user] Re: Would unmerging xorg-server certainly help it?

[Martin Vaeth]

Akater  wrote:
> I just tried
>
>> emerge --ask --verbose --update --oneshot x11-base/xorg-proto x11-proto/s=
> crnsaverproto
>
> >  (x11-proto/scrnsaverproto-1.2.2-r1:0/0::gentoo, installed) pulled in by
> >x11-proto/scrnsaverproto

It should be scrnsaverproto-1.2.2-r2 which is pulled in.
Maybe you sync'ed at an unfortunate moment. Try emerge --sync again.

Re: [gentoo-user] New xorg-proto package blocks everything else.

[gevisz]

2018-03-25 15:50 GMT+03:00 Neil Bothwick :
> 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-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-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 `.  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?

Re: [gentoo-user] Would unmerging xorg-server certainly help it?

[Akater]

The subject question of my message is stated in the last paragraph.

Helmut Jarausch  writes:

> Try to emerge x11-base/xorg-proto and x11-proto/scrnsaverproto  
> simultaneously.

I just tried

> emerge --ask --verbose --update --oneshot x11-base/xorg-proto 
> x11-proto/scrnsaverproto

and it didn't work:

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

 >  (x11-proto/scrnsaverproto-1.2.2-r1:0/0::gentoo, installed) pulled in by
 >x11-proto/scrnsaverproto

 >  (x11-base/xorg-proto-2018.4:0/0::gentoo, ebuild scheduled for merge) pulled 
 > in by
 >x11-base/xorg-proto

Note: I have a fairly nonstandard setup, and have not yet migrated from

> hardened/linux/amd64 (stable)

to

> default/linux/amd64/17.x/hardened (stable for x=0, exp for x=1)

but despite having a specific setup, I seem to have the same issues as
OP.

Can you (or anyone reading this) confirm from first-hand experience that
unmerging xorg-server would help? It won't be a problem for me as long
as it is certain that I'll have xorg-server back by tomorrow and would
not, say, find out that due to some interesting turn of events I'm going
to spend an indefinite amount of time in console. Note: I'd rather not
mess with binary packages, either.


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: New xorg-proto package blocks everything else.

[Neil Bothwick]

On Sun, 25 Mar 2018 08:10:29 -0700, Ian Zimmerman wrote:

> > 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.  
> 
> But ... I actually have packages that depend on scrnsaverproto:
> 
> matica!524 ~# equery d scrnsaverproto

equery d is unreliable, emerge -cav is a better check if deps.

>  * These packages depend on scrnsaverproto:
> x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1)
> x11-libs/libXScrnSaver-1.2.2-r1
> (>=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-misc/xautolock-2.2_p5_p1 (x11-proto/scrnsaverproto)
> x11-misc/xssstate-1.1 (x11-proto/scrnsaverproto)

When one package blocks another, it is often because both provide the
same files. It looks like xorg-proto is replacing a load f x11-proto
package. Remove the old one and let emerge work it out for you.

> 
> So I have to unmerge xautolock and xssstate too? 

Unlikely, because they will probably be satisfied by xorg-proto too, but
quickpkg anything you are going to remove, just in case.


-- 
Neil Bothwick

"You know how dumb the average person is? Well, statistically, half of
them are even dumber than that" - Lewton, P.I.


pgpVFwMYJT9C0.pgp
Description: OpenPGP digital signature

[gentoo-user] OT: github (and gitlab, etc etc): track down a particular commit

[Ian Zimmerman]

Very often, for a some large FLOSS project (often but not always
packaged by gentoo) I am interested in answering the question:

Which official released released versions V1.0, V2.0 etc contain a
particular commit C1ABCDE?

Using branches as an imperfect but mostly OK proxy for releases, the
question becomes:

Into which branches B_1_0_foo, B_2_0_bar etc has C1ABCDE been merged?

Unfortunately I know of no direct way of answering either question with
the web UI of github and its siblings, and this has bugged me for a long
time.  Of course I can clone the repository and answer the question with
command line git or gitk, but for really large projects this consumes
considerable resources on my computer, and worse, significant time for
the download.

So, am I missing some feature of github which would allow me to do this?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: [gentoo-user] Re: New xorg-proto package blocks everything else.

[Helmut Jarausch]

On 03/25/2018 05:10:29 PM, Ian Zimmerman wrote:

On 2018-03-25 13:50, Neil Bothwick wrote:

> 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.

But ... I actually have packages that depend on scrnsaverproto:

So I have to unmerge xautolock and xssstate too?  That will be painful
because they're baked deep into my X configuration.  I think it will
require a trip to the Linux console :-P



No,

I have x11-base/xorg-proto-2018.4  and x11-proto/scrnsaverproto-1.2.2-r2
install here.

Try to emerge x11-base/xorg-proto and x11-proto/scrnsaverproto  
simultaneously.

[gentoo-user] Re: New xorg-proto package blocks everything else.

[Ian Zimmerman]

On 2018-03-25 13:50, Neil Bothwick wrote:

> 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.

But ... I actually have packages that depend on scrnsaverproto:

matica!524 ~# equery d scrnsaverproto
 * These packages depend on scrnsaverproto:
x11-base/xorg-server-1.19.5-r1 (>=x11-proto/scrnsaverproto-1.1)
x11-libs/libXScrnSaver-1.2.2-r1 
(>=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-misc/xautolock-2.2_p5_p1 (x11-proto/scrnsaverproto)
x11-misc/xssstate-1.1 (x11-proto/scrnsaverproto)

So I have to unmerge xautolock and xssstate too?  That will be painful
because they're baked deep into my X configuration.  I think it will
require a trip to the Linux console :-P

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: [gentoo-user] Ubuntu with Gentoo somehow...

[Tom H]

On Sun, Mar 25, 2018 at 8:47 AM,  wrote:


> is there a way to download the archive (or how is it called in the
> world of Ubuntu ?) of a program, from which I only know the apt-get
> and apt-install commands?

A "deb" file, which you can expand with "ar" (no need to install "dpkg").


> And how can I do the same for a developer release of that program when
> I additionally know the ppa (whatever that is...?)

I'll use systemd because I used the Ubuntu maintainer's systemd ppa
two or three years ago and I still have that url bookmarked.

To get the regular systemd deb:

http://de.archive.ubuntu.com/ubuntu/pool/main/s/systemd/

[ I've chosen the "de" repository given your email address. ]

To get the ppa systemd deb (the ppa is called "pitti/systemd"):

http://ppa.launchpad.net/pitti/systemd/ubuntu/


> I onlu need the archives of the complete program. Like Blender the
> archive is "all inclusive" ... :

Make sure that the source package isn't split up into more than one
deb. If you look at the systemd example above, you'll find many
"lib..." debs as well as "systemd..." and "udev..." debs.




Rather than grabbing a "deb", unpacking it, and dropping its
components into "/usr/local/", you might want to look into using
Ubuntu's snap that allows you to install self-contained applications
in the same way that Android and iOS do.

[ I have no idea whether snap is available on Gentoo or whether your
app is packaged as a snap. ]

Re: [gentoo-user] New xorg-proto package blocks everything else.

[Neil Bothwick]

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
> [ebuild U  ] x11-proto/xproto-7.0.31-r1 [7.0.31]
> [blocks b  ]  (" [ebuild U  ] x11-proto/xextproto-7.3.0-r1 [7.3.0]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/inputproto-2.3.2-r1 [2.3.2]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/kbproto-1.0.7-r1 [1.0.7]
> [blocks b  ]  (" [ebuild U  ] x11-proto/renderproto-0.11.1-r2 [0.11.1-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/damageproto-1.2.1-r2 [1.2.1-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xf86vidmodeproto-2.3.1-r2 [2.3.1-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/fixesproto-5.0-r2 [5.0-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xf86bigfontproto-1.2.0-r2 [1.2.0-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/videoproto-2.3.3-r1 [2.3.3]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xf86driproto-2.1.1-r2 [2.1.1-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/dri2proto-2.8-r2 [2.8-r1]
> [blocks b  ]  (" [ebuild U  ] x11-proto/glproto-1.4.17-r2 [1.4.17-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/randrproto-1.5.0-r1 [1.5.0]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xineramaproto-1.2.1-r2 [1.2.1-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/fontsproto-2.1.3-r1 [2.1.3] ABI_X86="(64%*)
> -32% (-x32)"
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/dri3proto-1.0-r1 [1.0]
> [blocks b  ]  (" [ebuild U  ] x11-proto/presentproto-1.1-r1 [1.1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/recordproto-1.14.2-r2 [1.14.2-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/compositeproto-0.4.2-r2 [0.4.2-r1]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/resourceproto-1.2.0-r1 [1.2.0]
> ABI_X86="(64%*) -32% (-x32)"
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xcmiscproto-1.2.2-r1 [1.2.2]
> ABI_X86="(64%*) -32% (-x32)"
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/bigreqsproto-1.1.2-r1 [1.1.2]
> ABI_X86="(64%*) -32% (-x32)"
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/xf86dgaproto-2.1-r3 [2.1-r2]
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] x11-proto/trapproto-3.4.3-r1 [3.4.3] ABI_X86="(64%*)
> -32% (-x32)"
> [blocks b  ]  (" x11-base/xorg-proto-2018.4)
> [ebuild U  ] media-libs/gstreamer-1.12.4 [1.12.3]
> [ebuild U  ] dev-lang/orc-0.4.28-r1 [0.4.27]
> [ebuild U  ] media-libs/tiff-4.0.9-r3 [4.0.8]
> [ebuild U  ] net-misc/curl-7.59.0 [7.58.0]
> [ebuild U  ] x11-proto/xcb-proto-1.13 [1.12-r2]
> [ebuild U  ] media-libs/gd-2.2.5 [2.2.4]
> [ebuild U  ] media-libs/gst-plugins-base-1.12.4 [1.12.3]
> [ebuild U  ] virtual/package-manager-1 [0]
> [ebuild U  ] sys-libs/ncurses-6.1-r1 [6.0-r1]
> [ebuild  NS] dev-lang/python-3.6.3-r1 [2.7.14-r1, 3.5.4-r1]
> USE="gdbm ncurses readline ssl (threads) xml -build -examples
> -hardened -ipv6 -libressl -sqlite {-test} -tk -wininst"
> [ebuild U  ] sys-libs/slang-2.3.2 [2.3.0]
> [blocks b  ]  (" [ebuild U  ] dev-libs/double-conversion-3.0.0 [2.0.1] USE="{-test%}"
> [ebuild  N ] sys-libs/libomp-5.0.1  USE="-hwloc -ompt {-test}"
> ABI_X86="(64) -32 (-x32)"
> [ebuild U  ] virtual/w3m-0-r1 [0]
> [ebuild U  ] media-libs/jasper-2.0.14 [2.0.12] USE="{-test%}"
> [ebuild U  ] dev-qt/qtcore-5.9.4-r2 [5.7.1-r4]
> [ebuild U  ] dev-qt/qtnetwork-5.9.4 [5.7.1] USE="-libressl%"
> [ebuild U  ] dev-qt/qtxml-5.9.4 [5.7.1]
> [ebuild U  ] dev-qt/qtdbus-5.9.4 [5.7.1]
> [ebuild U  ] dev-qt/qttest-5.9.4 [5.7.1]
> [ebuild U  ] lxde-base/lxterminal-0.3.1 [0.1.11] USE="-gtk3%"
> [ebuild U  ] dev-qt/qtconcurrent-5.9.4 [5.7.1]
> [ebuild U  ] dev-qt/qtsql-5.9.4-r1 [5.7.1-r1]
> [ebuild U  ] dev-qt/qtgui-5.9.4-r3 [5.7.1-r1] USE="-vnc%"
> [ebuild U  ] 

[gentoo-user] Ubuntu with Gentoo somehow...

[tuxic]

Hi,

is there a way to download the archive (or how is it called in the
world of Ubuntu ?) of a program, from which I only know the 
apt-get and apt-install commands?
And how can I do the same for a developer release of that program
when I additionally know the ppa (whatever that is...?)

I onlu need the archives of the complete program. Like Blender
the archive is "all inclusive" ... :

Thanks a lot for any help!
Cheers
Meino

[gentoo-user] New xorg-proto package blocks everything else.

[gevisz]

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
[ebuild U  ] x11-proto/xproto-7.0.31-r1 [7.0.31]
[blocks b  ] =x11-proto/scrnsaverproto-1.1 required by
(x11-base/xorg-server-1.19.5-r1:0/1.19.5::gentoo, installed)

>=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-base/xorg-proto-2018.4:0/0::gentoo, ebuild scheduled for merge)
pulled in by
x11-base/xorg-proto required by
(x11-proto/presentproto-1.1-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/xproto-7.0.31-r1:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/dri3proto-1.0-r1:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/kbproto-1.0.7-r1:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/xf86dgaproto-2.1-r3:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/compositeproto-0.4.2-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/dri2proto-2.8-r2:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/xcmiscproto-1.2.2-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/xineramaproto-1.2.1-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/resourceproto-1.2.0-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/inputproto-2.3.2-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/damageproto-1.2.1-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/randrproto-1.5.0-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/videoproto-2.3.3-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/bigreqsproto-1.1.2-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/renderproto-0.11.1-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/fixesproto-5.0-r2:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/glproto-1.4.17-r2:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/xf86bigfontproto-1.2.0-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/xf86driproto-2.1.1-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/trapproto-3.4.3-r1:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/xf86vidmodeproto-2.3.1-r2:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/fontsproto-2.1.3-r1:0/0::gentoo, ebuild scheduled for
merge)
x11-base/xorg-proto required by
(x11-proto/xextproto-7.3.0-r1:0/0::gentoo, ebuild scheduled for merge)
x11-base/xorg-proto required by
(x11-proto/recordproto-1.14.2-r2:0/0::gentoo, ebuild scheduled for
merge)


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