Troubles using new ports-2017 + xorg-kit

Sandro · March 31, 2017

Hi.

I've a new installation in chroot using:

ci74771ht xorg-kit # cat /etc/portage/repos.conf/gentoo  
[DEFAULT]
main-repo = gentoo

[gentoo]
location = /usr/portage
sync-type = git
sync-uri = git://github.com/funtoo/ports-2017.git
auto-sync = yes

and

ci74771ht xorg-kit # cat /etc/portage/repos.conf/xorg-kit  
[xorg-kit]
location = /root/xorg-kit
sync-type = git
sync-uri = git://github.com/funtoo/xorg-kit.git
auto-sync = yes

but i obtain errors; and dunno how to do abou "prime or 1.17" ????? dunno forgive my ignorance

ci74771ht xorg-kit # emerge boot-update 
setlocale: unsupported locale setting
setlocale: unsupported locale setting

* IMPORTANT: 3 news items need reading for repository 'gentoo'. 
* Use eselect news read to view new items. 

Calculating dependencies \/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/m
edia-libs/freetype/freetype-9999.ebuild: Permission denied
* ERROR: media-libs/freetype-9999::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=media-libs/freetype-9999::xorg
-kit'`,
* the complete build log and the output of `emerge -pqv '=media-libs/freetype-9999::xorg-
kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/media-libs/freetype-9999/work/freetype-9999' 
//usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/media-libs/freetype/freet
ype-2.7.1-r2.ebuild: Permission denied
* ERROR: media-libs/freetype-2.7.1-r2::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=media-libs/freetype-2.7.1-r2::
xorg-kit'`,
* the complete build log and the output of `emerge -pqv '=media-libs/freetype-2.7.1-r2::x
org-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/media-libs/freetype-2.7.1-r2/work/freetype-2.7.1' 
/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/media-libs/freetype/freetyp
e-2.7.1-r1.ebuild: Permission denied
* ERROR: media-libs/freetype-2.7.1-r1::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=media-libs/freetype-2.7.1-r1::
xorg-kit'`,
* the complete build log and the output of `emerge -pqv '=media-libs/freetype-2.7.1-r1::x
org-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/media-libs/freetype-2.7.1-r1/work/freetype-2.7.1' 
\/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/media-libs/freetype/freet
ype-2.6.5.ebuild: Permission denied
* ERROR: media-libs/freetype-2.6.5::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=media-libs/freetype-2.6.5::xor
g-kit'`,
* the complete build log and the output of `emerge -pqv '=media-libs/freetype-2.6.5::xorg
-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/media-libs/freetype-2.6.5/work/freetype-2.6.5' 
/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/media-libs/freetype/freetyp
e-2.6.3-r1.ebuild: Permission denied
* ERROR: media-libs/freetype-2.6.3-r1::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=media-libs/freetype-2.6.3-r1::
xorg-kit'`,
* the complete build log and the output of `emerge -pqv '=media-libs/freetype-2.6.3-r1::x
org-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/media-libs/freetype-2.6.3-r1/work/freetype-2.6.3' 
... done!

!!! All ebuilds that could satisfy "media-libs/freetype:2" have been masked. 
!!! One of the following masked packages is required to complete your request:
- media-libs/freetype-9999::xorg-kit (masked by: corruption)
- media-libs/freetype-2.7.1-r2::xorg-kit (masked by: corruption)
- media-libs/freetype-2.7.1-r1::xorg-kit (masked by: corruption)
- media-libs/freetype-2.6.5::xorg-kit (masked by: corruption)
- media-libs/freetype-2.6.3-r1::xorg-kit (masked by: corruption)

(dependency required by "sys-boot/grub-2.02_beta3-r2::gentoo[themes,fonts]" [ebuild]) 
(dependency required by "sys-boot/boot-update-1.7.7::gentoo" [ebuild]) 
(dependency required by "boot-update" [argument]) 
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

dunno how to adjust the xorg-kit .... :| Sorry :|

cafaia · April 7, 2017

Hello, Sandro!

That good that I helped!

It may not be possible to have master and prime in same folder. You tried to put each one in one folder? So:

#mkdir /usr/portage-kits

#cd /usr/portage-kits/

#git clone -b master git://github.com/funtoo/xorg-kit.git

#mv xorg-kit xorg-kit-master

#mkdir /usr/portage-kits/xorg-kit-prime

And to have this in folder /etc/portage/repos.conf:

- file gentoo:

[DEFAULT]

main-repo = gentoo

[gentoo]

location = /usr/portage

sync-type = git

sync-uri = git://github.com/funtoo/ports-2017.git

auto-sync = yes

- file xorg-kit-master:

[xorg-kit-master]

location = /usr/portage-kits/xorg-kit-master

sync-type = git

sync-uri = git://github.com/funtoo/master/xorg-kit.git

auto-sync = yes

- file xorg-kit-prime:

[xorg-kit-prime]

location = /usr/portage-kits/xorg-kit-prime

sync-type = git

sync-uri = git://github.com/funtoo/master/xorg-kit.git

auto-sync = yes

Then you do: eix-sync

Maybe this is the solution final!

Sandro · March 31, 2017

The situation has been put back in place thanks to "brhenc" he told me to change directory using /var/overlays instead of /root/ (where portage not allowed to write on it).

Now I can continue the compilation of the system

Unfortunately I did not understand what to do to operate properly xorg-kit or how to activate one or the other branch, and which one to choose. 17.1-prime, the master and / or others possibilities.

Forgive my ignorance :(

Oleg Vinichenko · April 1, 2017

its not able to run from root, because root is not in portage group by default

to fix this you need to add root into portage group by:

gpasswd -a root portage

and it will work

cardinal · April 1, 2017

On 3/31/2017 at 9:12 PM, Sandro said:

Unfortunately I did not understand what to do to operate properly xorg-kit or how to activate one or the other branch, and which one to choose. 17.1-prime, the master and / or others possibilities.

Forgive my ignorance :(

cd xorg-kit

List all available branches :

rj@funtoo ~/xorg-kit $ git branch -a
* master
  remotes/origin/1.17-prime
  remotes/origin/HEAD -> origin/master
  remotes/origin/gentoo-1.17-snap
  remotes/origin/gentoo-1.19-snap

New Ports-2017 tree and Kits

For xorg-kit, you will want to check out the 1.17-prime branch. You can keep ports-2017 on the master branch.

1.17-prime is a branch that contains a curated snapshot of xorg 1.17. We have grabbed a snapshot of xorg from Gentoo that we have found particularly stable, and will be adding security backports, bug fixes and feature enhancements -- but without bumping versions of ebuilds. This is equivalent to an 'enterprise grade' version of xorg. If you need to run xorg and just have it work, all the time, and not have it break, you can know that sticking with the 1.17-prime branch will greatly increase your likelihood of this happening. It is what 1.17-prime is designed for. Note the "-prime" extension, which is our way of saying "this is the good stuff" -- the prime cuts of Larry the Cow ;) 1.17-prime's functionality and hardware support should continue to remain constant -- so that if it works well on your laptop, you can have very good confidence that you can reload your laptop using 1.17-prime and it will continue to work well into the future.

rj@funtoo ~/xorg-kit $ git checkout 1.17-prime
Branch 1.17-prime set up to track remote branch 1.17-prime from origin.
Switched to a new branch '1.17-prime'

rj@funtoo ~/xorg-kit $ git branch
* 1.17-prime
master

Bleeding-edge users will want to use the master branch to get access to all the latest Gentoo goodies:

rj@funtoo ~/xorg-kit $ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.

rj@funtoo ~/xorg-kit $ git branch
1.17-prime
* master

Sandro · April 1, 2017

ci74771ht ~ # cd /root/xorg-kit/ 
ci74771ht xorg-kit # git branch -a 
* master 
 remotes/origin/HEAD -> origin/master 
 remotes/origin/master 
ci74771ht xorg-kit #

Ok ... i don't see the "1.17-prime" .... why this ?

Thanx and excuse me :|

Sandro · April 1, 2017

Damn ... because I can not run this new technology? Damn ... I think I become a noob :'(

AdiosKid · April 2, 2017

I create a new folder to xorg-kit

I put on "/usr/portage-kits/xorg" and add the path on file

Sandro · April 2, 2017

Ok ... the trouble was the "Funtoo Stable".

Now i've made anexperiment in a dedicated new partition with the current ....

I've addedd root to Portage ...

now xorg is in 1.17.prime but isn't possible to switch to "master" :|

ci74771ht ~ # cd /root/xorg-kit/ 
ci74771ht xorg-kit # git branch -a 
* 1.17-prime 
 remotes/origin/1.17-prime 
 remotes/origin/HEAD -> origin/1.17-prime 
ci74771ht xorg-kit # gpasswd -a root portage 
Adding user root to group portage
ci74771ht xorg-kit # git branch -a           
* 1.17-prime 
 remotes/origin/1.17-prime 
 remotes/origin/HEAD -> origin/1.17-prime 
ci74771ht xorg-kit #

ci74771ht xorg-kit # eix-sync 
* Running emerge --sync 
>>> Syncing repository 'gentoo' into '/usr/portage'...
/usr/bin/git pull
Already up-to-date.
=== Sync completed for gentoo
q: Updating ebuild cache in /usr/portage ...  
q: Finished 39070 entries in 0.099431 seconds 
>>> Syncing repository 'xorg-kit' into '/root/xorg-kit'...
/usr/bin/git pull
Already up-to-date.
=== Sync completed for xorg-kit
q: Updating ebuild cache in /root/xorg-kit ...  
q: Finished 583 entries in 0.001593 seconds 

* IMPORTANT: 3 news items need reading for repository 'gentoo'. 
* Use eselect news read to view new items. 

* Copying old database to /var/cache/eix/previous.eix 
* Running eix-update 
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /usr/portage/ (cache: metadata-md5-or-flat)
    Reading category 165|165 (100) Finished              
[1] "" /root/xorg-kit (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
    Reading category 165|165 (100) EMPTY!
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 19409 packages in 165 categories
* Calling eix-diff 
* Time statistics: 
    3 seconds for syncing
    3 seconds for eix-update
    1 seconds for eix-diff
    7 seconds total
ci74771ht xorg-kit # eix xorg-x11 
No matches found 
ci74771ht xorg-kit # emerge xorg-server 

* IMPORTANT: 3 news items need reading for repository 'gentoo'. 
* Use eselect news read to view new items. 

Calculating dependencies |/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/x
11-base/xorg-server/xorg-server-1.17.4-r1.ebuild: Permission denied
* ERROR: x11-base/xorg-server-1.17.4-r1::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.17.4-r1
::xorg-kit'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.17.4-r1:
:xorg-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/x11-base/xorg-server-1.17.4-r1/work/xorg-server-1.17.4' 
|/usr/lib/portage/python2.7/ebuild.sh: line 611: /root/xorg-kit/x11-base/xorg-server/xorg
-server-1.17.4.ebuild: Permission denied
* ERROR: x11-base/xorg-server-1.17.4::xorg-kit failed (depend phase): 
*   error sourcing ebuild 
*  
* Call stack: 
*   ebuild.sh, line 611:  Called die 
* The specific snippet of code: 
*                      source "$EBUILD" || die "error sourcing ebuild" 
*  
* If you need support, post the output of `emerge --info '=x11-base/xorg-server-1.17.4::x
org-kit'`,
* the complete build log and the output of `emerge -pqv '=x11-base/xorg-server-1.17.4::xo
rg-kit'`.
* Working directory: '/usr/lib64/python2.7/site-packages' 
* S: '/var/tmp/portage/x11-base/xorg-server-1.17.4/work/xorg-server-1.17.4' 
... done!

!!! All ebuilds that could satisfy "xorg-server" have been masked. 
!!! One of the following masked packages is required to complete your request:
- x11-base/xorg-server-1.17.4-r1::xorg-kit (masked by: corruption)
- x11-base/xorg-server-1.17.4::xorg-kit (masked by: corruption)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

I obtain only errors ... very sorry; excuse me.

cafaia · April 3, 2017

Hello, Sandro!

I made it:

#mkdir /usr/portage-kits/

#cd /usr/portage-kits/

#git clone -b master git://github.com/funtoo/xorg-kit.git

And I have this in my folder /etc/portage/repos.conf:

- file gentoo:

[DEFAULT]

main-repo = gentoo

[gentoo]

location = /usr/portage-tree

sync-type = git

sync-uri = git://github.com/funtoo/ports-2017.git

auto-sync = yes

- file xorg-kit:

[xorg-kit]

location = /usr/portage-kits/xorg-kit

sync-type = git

sync-uri = git://github.com/funtoo/master/xorg-kit.git

auto-sync = yes

And I did several times "emerge --sync" and "eix-sync" without any error! It's OK for me!

Sandro · April 3, 2017

Oh ... Funtoo-astic = Fantastic :)

With Your configuration xorg is viewed also with eix and now i'm compiling xorg.

ci74771ht xorg-kit # git branch -a 
* master 
 remotes/origin/1.17-prime 
 remotes/origin/HEAD -> origin/1.17-prime 
 remotes/origin/gentoo-1.17-snap 
 remotes/origin/gentoo-1.19-snap 
 remotes/origin/master

Now either master than 1.17-prime are present :D

You're very Great :)

Thank You :) :) :)

And now i can switch simply from master to 1.17-prime

:) :) :)

Sandro · April 3, 2017

Anyway ... I think it may be useful to find a standard procedure to get this .....

Your method on my system was decisive _'_

Sandro · April 3, 2017

No .. if i choice master portage wants to install the xorg-x11-1.17.4.

If i switch to branch 1.17-prime ... portage wants to install the same (1.17.4)

I don't know :|

cafaia · April 3, 2017

Hello, Sandro!

You should do this:

#rm -R /usr/portage-kits/xorg-kit/*

#rm -R /usr/portage-kits/xorg-kit/.git

#cd /usr/portage-kits/xorg-kit/

#git clone -b master git://github.com/funtoo/xorg-kit.git

#mkdir /usr/portage-tree

And you should have this in folder /etc/portage/repos.conf/:

- file gentoo:

[DEFAULT]

main-repo = gentoo

[gentoo]

location = /usr/portage-tree

sync-type = git

sync-uri = git://github.com/funtoo/ports-2017.git

auto-sync = yes

- file xorg-kit:

[xorg-kit]

location = /usr/portage-kits/xorg-kit

sync-type = git

sync-uri = git://github.com/funtoo/master/xorg-kit.git

auto-sync = yes

Then you do: eix-sync

If I do 'ls /usr/portage-tree/x11-base/' I only have 'metadata.xml'. What does this command have for you? If have only 'metadata.xml' you are using only ports-2017, otherwise have ports-2012.

cafaia · April 3, 2017

Correcting:

#rm -R /usr/portage-kits/xorg-kit

#cd /usr/portage-kits/

#git clone -b master git://github.com/funtoo/xorg-kit.git

cafaia · April 3, 2017

If I do 'eix xorg-server' I have:

x11-base/xorg-server [1]

Available versions: 1.12.4-r7(0/1.12.4) 1.15.2-r4(0/1.15.2) 1.18.4(0/1.18.4) 1.19.2(0/1.19.2) (~)1.19.3(0/1.19.3) **9999(0/9999) {debug dmx doc glamor ipv6 kdrive libressl minimal nptl selinux static-libs +suid systemd tslib +udev unwind wayland xephyr xnest xorg xvfb}

Installed versions: 1.19.3(0/1.19.3)(14:31:00 03-04-2017)(dmx ipv6 kdrive suid udev xorg -debug -doc -glamor -libressl -minimal -selinux -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb)

Homepage: https://www.x.org/wiki/

Description: X.Org X servers

[1] "xorg-kit" /usr/portage-kits/xorg-kit

Sandro · April 4, 2017

Nothing to do ...

Now i can see "xorgt-server" but i've not the capability to switch from 1.17-prime to master and viceversa.

Thanks for You aid :)

Sandro · April 4, 2017

Ok ... now seems solved.

Thx :)

Sandro · April 7, 2017

Thanx 100000 :)

You're Great :)

cafaia · April 9, 2017

Hello, Sandro!

That good that I helped!

Thank you very much for the words of thanks!

Sandro · April 10, 2017

cafaia .... Thanks To You Very much Dear "master" :) :) :)

Sandro · April 11, 2017

However also the Great Cardinal got reason:

[cdoe]

sandro@ci74771ht ~/xorg-kit $ git branch -a
* 1.17-prime
remotes/origin/1.17-prime
remotes/origin/HEAD -> origin/1.17-prime
remotes/origin/gentoo-1.17-snap
remotes/origin/gentoo-1.19-snap
remotes/origin/master
sandro@ci74771ht ~/xorg-kit $ git checkout master
Branch master set up to track remote branch master from origin.
Switched to a new branch 'master'
sandro@ci74771ht ~/xorg-kit $ git branch -a
1.17-prime
* master
remotes/origin/1.17-prime
remotes/origin/HEAD -> origin/1.17-prime
remotes/origin/gentoo-1.17-snap
remotes/origin/gentoo-1.19-snap
remotes/origin/master
sandro@ci74771ht ~/xorg-kit $ git checkout 1.17-prime
Si ? passati al branch '1.17-prime'
Your branch is up-to-date with 'origin/1.17-prime'.
sandro@ci74771ht ~/xorg-kit $ git branch -a
* 1.17-prime
master
remotes/origin/1.17-prime
remotes/origin/HEAD -> origin/1.17-prime
remotes/origin/gentoo-1.17-snap
remotes/origin/gentoo-1.19-snap
remotes/origin/master
sandro@ci74771ht ~/xorg-kit $
[/code]

Good Funtoo to All :) :) :)

Troubles using new ports-2017 + xorg-kit

Question

Link to comment

Share on other sites

21 answers to this question

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites