need help moving from layman to eselect-repository

[Tony0945]

It seems like layman is heading for the graveyard. The wiki page seems to assume a lot.
I could use some (a lot) of help here. The first step is to emerge eselect-repository.

On the wiki page it looks like the repos sync every two hours. Doesn't this violate the once a day rule? I'd rather sync on demand.

I have two local LAN repos. How do I migrate them? Must they use git?

Code: Select all

$ cat /etc/portage/repos.conf/layman.conf
[oldgentoo]
priority = 50
location = /var/lib/layman/oldgentoo
layman-type = rsync
sync-type = laymansync
sync-uri = rsync://192.168.0.102/oldgentoo
auto-sync = Yes

[mybuilds]
priority = 70
location = /var/lib/layman/mybuilds
layman-type = rsync
sync-type = laymansync
sync-uri = rsync://192.168.0.102/mybuilds
auto-sync = Yes

What are the replacements for "layman -S" and "layman -s <reponame>" ?

[fedeliallalinea]

On the wiki page it looks like the repos sync every two hours. Doesn't this violate the once a day rule? I'd rather sync on demand.

I think this rule is for official gentoo rsync.

I have two local LAN repos. How do I migrate them? Must they use git?

Never tried but I think you can add these with

Code: Select all

eselect repository add oldgentoo rsync rsync://192.168.0.102/oldgentoo
eselect repository add mybuilds rsync rsync://192.168.0.102/mybuilds

This command create an entry in /etc/portage/repos.conf/eselect-repo.conf with

Code: Select all

# created by eselect-repo

[oldgentoo]
location = /var/db/repos/oldgentoo
sync-type = rsync
sync-uri = rsync://192.168.0.102/oldgentoo

(pay attention that location is different that from layman)

What are the replacements for "layman -S" and "layman -s <reponame>" ?

For this you can use emaint sync -A and emaint sync -r <reponame>

[Tony0945]

so far so good. I just emerged eselect-repository. When I tried to add an existing repo

Code: Select all

# eselect repository add oldgentoo rsync rsync://192.168.0.102/oldgentoo
!!! Error: error: oldgentoo: repository already enabled, in /var/lib/layman/oldgentoo
exiting

But when I tried to update it

Code: Select all

 # emaint sync -r mybuilds
!!! Repository 'freegentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'oldgentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'mybuilds' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /usr/portage (cache: metadata-md5-or-flat)
     Reading category 181|181 (100) Finished             
[1] "oldgentoo" /var/lib/layman/oldgentoo (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
     Reading category 163|181 ( 90): sys-process...!!! Repository 'freegentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'mybuilds' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'oldgentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'freegentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'mybuilds' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'oldgentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
     Reading category 181|181 (100) Finished       
[2] "freegentoo" /var/lib/layman/freegentoo (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
     Reading category 181|181 (100) Finished        
[3] "mybuilds" /var/lib/layman/mybuilds (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
     Reading category 181|181 (100) Finished         
Applying masks...
Calculating hash tables...
Writing database file /var/cache/eix/portage.eix...
Database contains 17476 packages in 181 categories
!!! Repository 'freegentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'oldgentoo' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'
!!! Repository 'mybuilds' has sync-type attribute set to unsupported value: 'laymansync'
!!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']'


ERROR: Sync module 'laymansync' is not an installed/known type'

Action: sync for repo: mybuilds, returned code = 1

[Phoenix591]

Remove the layman added entries for it, or edit them to match the format used in the example (mostly just change sync type to rsync). Once you do that you may also use emerge --sync and it will sync both portage and overlays, or emerge --sync <repo> . I believe it uses emaint under the hood, but I haven't bothered to look.

[Anon-E-moose]

It doesn't sound like layman is going anywhere at least from the gentoo wikis.

While Eselect/Repository supersedes layman for listing, configuring, and handling synchronization of ebuild repositories, app-portage/layman users can manage their ebuild repositories (overlays) in a simple, centralized manner. The layman provides an overview of available remote repositories and allows the user to select one or more for the system. Once selected, the user can update (similar to emerge --sync), add, remove, display and information about the overlays.

Sounds like a choice to me.

https://wiki.gentoo.org/wiki/Layman

[Tony0945]

Additional steps needed

Code: Select all

mkdir -p /var/db/repos/oldgentoo/metadata/
 cp /var/lib/layman/oldgentoo/metadata/layout.conf /var/db/repos/oldgentoo/metadata/layout.conf

repeat for each layman repo

Full procedure:

Code: Select all

emerge -av eselect-repository
cd /etc/portage/repos.conf
# move layman.conf somewhere handy like /root
cp /etc/portage/repos.conf/layman.conf  /root/
#for each repo in layman.conf 
mkdir -p mkdir -p /var/db/repos/oldgentoo/metadata/ # replace oldgentoo with repo name
cp /var/lib/layman/oldgentoo/metadata/layout.conf /var/db/repos/oldgentoo/metadata/layout.conf #replace oldgentoo with repo name
eselect repository add oldgentoo rsync rsync://192.168.0.102/oldgentoo # ditto for ip address and name
#end of loop
## now test the emaint commands, unmerge layman and erase /root/layman.conf as cleanup

Priority got lost along the way. manually restore priority lines to eselect-repo.conf

[Tony0945]

Something still wrong here. appeared to work until I unmerged layman

Code: Select all

 # eix-update
Reading Portage settings...
Building database (/var/cache/eix/portage.eix)...
[0] "gentoo" /usr/portage (cache: metadata-md5-or-flat)
     Reading category 180|180 (100) Finished             
[1] "" /var/db/repos/oldgentoo (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
     Reading category 180|180 (100) EMPTY!
[2] "" /var/db/repos/mybuilds (cache: parse|ebuild*#metadata-md5#metadata-flat#assign)
     Reading category 180|180 (100) EMPTY!

[Tony0945]

Something wrong with my rsyncd.conf ?

Code: Select all

[documents]
path = /home/tony/Documents
comment = My Documents from XP

[gentoo-portage]
path=/usr/portage
comment=Gentoo Portage
exclude=distfiles/ packages/

[oldgentoo]
path=/usr/local/oldgentoo
comment=oldgentoo Overlay
exclude=distfiles/ packages/

[mybuilds]
path=/usr/local/mybuilds
comment=mybuilds Overlay
exclude=distfiles/ packages/

The paths are the paths on the server. Isn't that correct?

You see it is NOT as simple as the wiki says. Only if you are using an accredited overlay.

[Phoenix591]

There's no magic that makes it different for official repositories and overlays aside from the fact it pulls in the sync type and uri when generating the entry from repositories.xml.
if your rsync configuration was working before there's no reason it shouldn't still work.

All you'd need for each rsync repository is a section in repos.conf/somefile

Code: Select all

[gentoo]
location = /var/db/repos/gentoo
sync-type = rsync
sync-uri = rsync://rsync.gentoo.org/gentoo-portage

changing the repository name and sync-uri is all you need.

metadata/layout.conf is part of the repository, it should be moved and synced with the rest of the repository (eg, move the whole repository folder out of /var/lib/layman into /var/db/repos)

The only other configuration real portage entry for the main repository has is related to pgp verification which isn't necessary.

[papu]

error!

[Tony0945]

All the examples are for repos on the internet, not on the computer or on the LAN

[NeddySeagoon]

Tony0945,


My cross compiler overlay is

Code: Select all

[DEFAULT]
main-repo = gentoo

[gentoo_cross]
location = /usr/local/gentoo-cross
priority = 100

The overlay is actually populated by crossdev, when you add a new cross toolchain. At that time, crossdev uses portage to do the building.

[Tony0945]

Neddy, do you have an example for a repo on another lan machine? I suppose I could mount with samba but that is cumbersome on multiple machines.
Or I could rsync the repo by hand, I suppose.

Layman uses:

Code: Select all

sync-uri = rsync://192.168.0.102/mybuilds

The actual location on 192.168.0.102 is /usr/local/mybuilds, with for example www-client/palemoon under it.

[Hu]

Code: Select all

[mybuilds]
path=/usr/local/mybuilds
comment=mybuilds Overlay
exclude=distfiles/ packages/

The paths are the paths on the server. Isn't that correct?

The argument given to path= is a filesystem path on the machine running rsyncd. The name in brackets is the pseudo-path used by the rsync client. That is why your sync-uri in the post right above this one works as it does.

[Tony0945]

The argument given to path= is a filesystem path on the machine running rsyncd. The name in brackets is the pseudo-path used by the rsync client. That is why your sync-uri in the post right above this one works as it does.

But it works with layman and finds no packages on eselect repository