Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wow, something is really screwed up....
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
Wallsandfences
Guru
Guru


Joined: 29 Mar 2010
Posts: 359

PostPosted: Sun Mar 04, 2018 5:10 pm    Post subject: Wow, something is really screwed up.... Reply with quote

Latest xorg-server update is going havoc. Will this be sorted in a next --sync or what is going on there?

The error message is similar on all my gentoo boxes (which are otherwise quite differnent hardware- and wordfilewise

Code:
[blocks B      ] <x11-proto/dri3proto-1.0-r1 ("<x11-proto/dri3proto-1.0-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/glproto-1.4.17-r2 ("<x11-proto/glproto-1.4.17-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xproto-7.0.31-r1 ("<x11-proto/xproto-7.0.31-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/fontsproto-2.1.3-r1 ("<x11-proto/fontsproto-2.1.3-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/randrproto-1.5.0-r1 ("<x11-proto/randrproto-1.5.0-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/recordproto-1.14.2-r2 ("<x11-proto/recordproto-1.14.2-r2" is blocking 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)
[blocks B      ] <x11-proto/xf86driproto-2.1.1-r2 ("<x11-proto/xf86driproto-2.1.1-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/bigreqsproto-1.1.2-r1 ("<x11-proto/bigreqsproto-1.1.2-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/trapproto-3.4.3-r1 ("<x11-proto/trapproto-3.4.3-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/damageproto-1.2.1-r2 ("<x11-proto/damageproto-1.2.1-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xf86dgaproto-2.1-r3 ("<x11-proto/xf86dgaproto-2.1-r3" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/videoproto-2.3.3-r1 ("<x11-proto/videoproto-2.3.3-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/compositeproto-0.4.2-r2 ("<x11-proto/compositeproto-0.4.2-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/presentproto-1.1-r1 ("<x11-proto/presentproto-1.1-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xf86vidmodeproto-2.3.1-r2 ("<x11-proto/xf86vidmodeproto-2.3.1-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xf86miscproto-0.9.3-r1 ("<x11-proto/xf86miscproto-0.9.3-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/renderproto-0.11.1-r2 ("<x11-proto/renderproto-0.11.1-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xextproto-7.3.0-r1 ("<x11-proto/xextproto-7.3.0-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/inputproto-2.3.2-r1 ("<x11-proto/inputproto-2.3.2-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xineramaproto-1.2.1-r2 ("<x11-proto/xineramaproto-1.2.1-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xf86bigfontproto-1.2.0-r2 ("<x11-proto/xf86bigfontproto-1.2.0-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/dri2proto-2.8-r2 ("<x11-proto/dri2proto-2.8-r2" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/kbproto-1.0.7-r1 ("<x11-proto/kbproto-1.0.7-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/resourceproto-1.2.0-r1 ("<x11-proto/resourceproto-1.2.0-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/xcmiscproto-1.2.2-r1 ("<x11-proto/xcmiscproto-1.2.2-r1" is blocking x11-base/xorg-proto-2018.4)
[blocks B      ] <x11-proto/fixesproto-5.0-r2 ("<x11-proto/fixesproto-5.0-r2" is blocking x11-base/xorg-proto-2018.4)

Total: 12 packages (11 upgrades, 1 new), Size of downloads: 38.306 KiB
Conflict: 27 blocks (27 unsatisfied)

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-base/xorg-server:0

  (x11-base/xorg-server-1.19.99.901:0/1.19.99.901::gentoo, ebuild scheduled for merge) pulled in by
    (no parents that aren't satisfied by other packages in this slot)

  (x11-base/xorg-server-1.19.6-r1:0/1.19.6::gentoo, installed) pulled in by
    x11-base/xorg-server:0/1.19.6= required by (x11-drivers/xf86-video-nouveau-1.0.15:0/0::gentoo, installed)
                        ^^^^^^^^^^                                                                                                               
    <x11-base/xorg-server-1.19.99:0/1.19.6= required by (x11-drivers/nvidia-drivers-390.25:0/390::gentoo, installed)
    ^                     ^^^^^^^^^^^^^^^^^                                                                                                                                                   
    (and 3 more with the same problems)
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21782
Location: here

PostPosted: Sun Mar 04, 2018 5:25 pm    Post subject: Reply with quote

x11-drivers/nvidia-drivers require a version <x11-base/xorg-server-1.19.99.
You should wait that nvidia release new drivers that support xorg-1.19.99
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6996
Location: Austria

PostPosted: Sun Mar 04, 2018 5:38 pm    Post subject: Reply with quote

Why do you have nouveau and nvidia-drivers installed at the same time? Not that it is a problem, but in case you don't use nvidia-drivers then your blocker is completely unnecessary.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 866
Location: The Village, Portmeirion

PostPosted: Sun Mar 04, 2018 5:43 pm    Post subject: Reply with quote

Wallsandfences wrote:
Latest xorg-server update is going havoc.

LoL, you think you have problems now? Wait till you get it installed. :) Don't do it it's a trap!

Welcome to "~".
Back to top
View user's profile Send private message
Wallsandfences
Guru
Guru


Joined: 29 Mar 2010
Posts: 359

PostPosted: Sun Mar 04, 2018 5:49 pm    Post subject: Reply with quote

Yeah, i won‘t install it for now. I‘m doing the dual thingie for nvidia/noveau as per wiki. But on my intel box its similar...
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 866
Location: The Village, Portmeirion

PostPosted: Sun Mar 04, 2018 5:53 pm    Post subject: Reply with quote

They are trying to make a transition so X dosn't run as "root", there will be plenty of permissions problems to hash out with that. I'd just wait a bit. :)
Back to top
View user's profile Send private message
Eriya
n00b
n00b


Joined: 16 Aug 2017
Posts: 12
Location: Minnesota, USA

PostPosted: Sun Mar 11, 2018 1:40 am    Post subject: Reply with quote

skellr wrote:
They are trying to make a transition so X dosn't run as "root", there will be plenty of permissions problems to hash out with that. I'd just wait a bit. :)


What should we do in the mean-time to update the rest of our packages? mask >=x11-base/xorg-server-1.19.99?
Back to top
View user's profile Send private message
skellr
l33t
l33t


Joined: 18 Jun 2005
Posts: 866
Location: The Village, Portmeirion

PostPosted: Sun Mar 11, 2018 2:02 am    Post subject: Reply with quote

Eriya wrote:
skellr wrote:
They are trying to make a transition so X dosn't run as "root", there will be plenty of permissions problems to hash out with that. I'd just wait a bit. :)


What should we do in the mean-time to update the rest of our packages? mask >=x11-base/xorg-server-1.19.99?

That works.
Back to top
View user's profile Send private message
yngwin
Retired Dev
Retired Dev


Joined: 19 Dec 2002
Posts: 4572
Location: Suzhou, China

PostPosted: Sun Mar 11, 2018 2:44 am    Post subject: Reply with quote

Eriya wrote:
skellr wrote:
They are trying to make a transition so X dosn't run as "root", there will be plenty of permissions problems to hash out with that. I'd just wait a bit. :)


What should we do in the mean-time to update the rest of our packages? mask >=x11-base/xorg-server-1.19.99?


That seems to be the sensible thing to do.
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
tuggbuss
Apprentice
Apprentice


Joined: 20 Mar 2017
Posts: 214

PostPosted: Sun Mar 25, 2018 1:43 am    Post subject: Reply with quote

As usual, Gentoo forums provides an useful answer. My xorg during reinstall today got exactly this error. Will mask, and install. Thanks again.

E: Nah, i masked xorg server version and did emerge update --deep --with-bdeps=y @world and it downgraded around 20 packages, but trying to install google-chrome it still shows
Code:
 [blocks B ] ("<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.


It's a brand new install, trying to fire up X
Back to top
View user's profile Send private message
tuggbuss
Apprentice
Apprentice


Joined: 20 Mar 2017
Posts: 214

PostPosted: Sun Mar 25, 2018 6:07 pm    Post subject: Reply with quote

Getting info on gentoo-user mailing list that some are affected of this. Seems that there is no current solution right now, so I'll wait a couple of days for upstream fix.

E: link to mailing list

https://archives.gentoo.org/gentoo-user/message/5749eb4ddeb864389fcfbfef90672a1d
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Sun Mar 25, 2018 7:58 pm    Post subject: Reply with quote

you need xorg-proto, but to install xorg-proto you need to upgrade them.
you have the easy solve to tell portage to install xorg-proto, next portage will not have to look on "howto install" xorg-proto, because it is already there.
Code:
emerge --nodeps --upgrade xorg-proto
Back to top
View user's profile Send private message
tuggbuss
Apprentice
Apprentice


Joined: 20 Mar 2017
Posts: 214

PostPosted: Sun Mar 25, 2018 8:30 pm    Post subject: Reply with quote

krinn wrote:
you need xorg-proto, but to install xorg-proto you need to upgrade them.
you have the easy solve to tell portage to install xorg-proto, next portage will not have to look on "howto install" xorg-proto, because it is already there.
Code:
emerge --nodeps --upgrade xorg-proto


Thanks, there was no packages to update thou.

When trying to install xfce4 or google chrome Gentoo still displaying the same error message.
If im not missing something trivial

Solved: i did a emerge-webrsync, rebooted and everything is fine now.
Back to top
View user's profile Send private message
globus
n00b
n00b


Joined: 24 Dec 2014
Posts: 39
Location: Newsiberianstadt, Rus

PostPosted: Thu Mar 29, 2018 2:20 pm    Post subject: Reply with quote

Hello, sorry my bad English.
When I do
Code:
emerge --nodeps --upgrade xorg-proto

me in the answer
Code:
# emerge --nodeps --upgrade xorg-proto
!!! '--upgrade' is not a valid package atom.
!!! Please check ebuild(5) for full details.

There is no "upgrade" key in man emerge. Sorry about the truth. :-)

Code:
# emerge --nodeps --update xorg-proto
gives rise to such a conclusion:
Code:
# emerge --nodeps --update xorg-proto
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) x11-base/xorg-proto-2018.4::gentoo
>>> Installing (1 of 1) x11-base/xorg-proto-2018.4::gentoo
>>> Failed to install x11-base/xorg-proto-2018.4, Log file:
>>>  '/var/tmp/portage/x11-base/xorg-proto-2018.4/temp/build.log'
>>> Jobs: 0 of 1 complete, 1 failed                 Load avg: 1.29, 0.70, 0.51
 * Package:    x11-base/xorg-proto-2018.4
 
 * Detected file collision(s):
  *
 * Searching all installed packages for file collisions...
 *
  *
 * Package 'x11-base/xorg-proto-2018.4' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.


Please tell me what to do.


Last edited by globus on Thu Mar 29, 2018 4:54 pm; edited 3 times in total
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7092
Location: Saint Amant, Acadiana

PostPosted: Thu Mar 29, 2018 3:38 pm    Post subject: Reply with quote

Quote:
Please tell me what to do.

You look at the error you are getting.
You read Gentoo Wiki.
You read portage and emerge man pages.
You search internet and this site for solutions.
When everything fails you post here, telling exactly what error you are getting and what you did to solve the problem.

IMHO, posting a screenful of garbage and asking others to sort out the error for you is plain rude and does not go well with nature of these or any other technical forums where support is provided by volunteers.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
globus
n00b
n00b


Joined: 24 Dec 2014
Posts: 39
Location: Newsiberianstadt, Rus

PostPosted: Thu Mar 29, 2018 4:51 pm    Post subject: Reply with quote

Sorry, tag "spoiler" does not work. The error is the same as in the first message, otherwise why would I be here to write. Made, as said in this topic.
Back to top
View user's profile Send private message
tuggbuss
Apprentice
Apprentice


Joined: 20 Mar 2017
Posts: 214

PostPosted: Thu Mar 29, 2018 5:03 pm    Post subject: Reply with quote

globus wrote:
Sorry, tag "spoiler" does not work. The error is the same as in the first message, otherwise why would I be here to write. Made, as said in this topic.


Have you done a # emerge-webrsync

and then an update?
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7071

PostPosted: Thu Mar 29, 2018 5:11 pm    Post subject: Reply with quote

globus wrote:
There is no "upgrade" key in man emerge. Sorry about the truth. :-)

I'm human :)

globus wrote:

* Detected file collision(s):

I'm not sure if you are seeking answer to that, but it's just because a file own by another package will be crush by another package.
Well, you are forcing the package to be install without looking at its need, you should make sure of the result, will the package will get runtime trouble or build trouble if you don't provide a needed build dep while doing that, will it crush other own files... As usual with --nodeps and such kind of options, it's always upto user to know what he is doing, or taking care of what he is doing (quickpkg is your friend)
I sometimes forget such kind of issue, because i'm not using these kinds of feature, collision-protect, preserved-libs, i just have all them disable, i know what i'm doing, and i'm preventing myself from any mistake when i'm doing such things, so when i want do something, i just prefer portage doing what i'm asking and these features are naggers for me...
That's something i should try to keep in mind, but cannot.

But that's for the story, because you should had use the proper fix, already given upper.
tuggbuss wrote:
Solved: i did a emerge-webrsync, rebooted and everything is fine now.
Back to top
View user's profile Send private message
globus
n00b
n00b


Joined: 24 Dec 2014
Posts: 39
Location: Newsiberianstadt, Rus

PostPosted: Fri Mar 30, 2018 7:17 am    Post subject: Reply with quote

I do "eix-sync", is it not the same? But not yet rebooted.
Back to top
View user's profile Send private message
tuggbuss
Apprentice
Apprentice


Joined: 20 Mar 2017
Posts: 214

PostPosted: Fri Mar 30, 2018 8:29 am    Post subject: Reply with quote

globus wrote:
I do "eix-sync", is it not the same? But not yet rebooted.


eix-sync does:

emerge --sync
cp -a /var/cache/eix/portage.eix /var/cache/eix/previous.eix
eix-update
eix-diff


Unless you don't have sync-type set to webrsync in your repos.conf.
Back to top
View user's profile Send private message
globus
n00b
n00b


Joined: 24 Dec 2014
Posts: 39
Location: Newsiberianstadt, Rus

PostPosted: Fri Mar 30, 2018 5:57 pm    Post subject: Reply with quote

Code:
# emerge-webrsync
Fetching most recent snapshot ...
 * Latest snapshot date: 20180329
 *
 * Approximate snapshot timestamp: 1522370700
 *        Current local timestamp: 1522427701
 *
 * The current local timestamp is newer than the timestamp of the latest
 * snapshot. In order to force sync, use the --revert option or remove
 * the timestamp file located at '/usr/portage/metadata/timestamp.x'


Reboot did not help
Back to top
View user's profile Send private message
globus
n00b
n00b


Joined: 24 Dec 2014
Posts: 39
Location: Newsiberianstadt, Rus

PostPosted: Mon Apr 02, 2018 6:11 am    Post subject: Reply with quote

I solved the problem by removing all conflict x11-proto/*.
Back to top
View user's profile Send private message
wim-x
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2004
Posts: 109
Location: Netherlands

PostPosted: Wed Apr 04, 2018 5:12 am    Post subject: Reply with quote

Solved by doing a
Code:
emerge -av1uD xorg-proto $(eix -IC# x11-proto)


Thx to EoD's post in this topic.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum