Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

[solved] layman being replaced by eselect - questions

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
9 posts • Page 1 of 1
Author
Message
Bigun
Advocate
Advocate
User avatar
Posts: 2198
Joined: Sun Sep 21, 2003 3:45 am
Contact:
Contact Bigun
Website

[solved] layman being replaced by eselect - questions

  • Quote

Post by Bigun » Tue Jun 27, 2023 11:23 am

So this came across my latest update on one of my servers:

Code: Select all

!!! The following installed packages are masked:
- app-portage/layman-2.4.3::gentoo (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# David Seifert <soap@gentoo.org> (2023-05-19)
# Abandoned, replaced by 'eselect repository', tons of open bugs.
# Removal on 2023-08-17. Bug #761199.
So a few questions:

1) Running "eselect repository" yields an error. Will this functionality be available by 08-17?

2) Is there a conversion process to "move" any layman settings over to eselect? Or will things "just work"™️?

3) I thought these were called overlays, are we calling them repositories now? I'm so confused.
Last edited by Bigun on Mon Jul 03, 2023 7:07 pm, edited 1 time in total.
"It's ok, they might have guns but we have flowers." - Perpetual Victim
Top
ts-plus
n00b
n00b
User avatar
Posts: 26
Joined: Tue Dec 04, 2012 12:31 pm
Location: Germany

  • Quote

Post by ts-plus » Tue Jun 27, 2023 12:30 pm

1) Running "eselect repository" yields an error. Will this functionality be available by 08-17?
Which error? Is app-eselect/eselect-repository even installed?
2) Is there a conversion process to "move" any layman settings over to eselect? Or will things "just work"™️?
See this thread.
Top
ts-plus
n00b
n00b
User avatar
Posts: 26
Joined: Tue Dec 04, 2012 12:31 pm
Location: Germany

  • Quote

Post by ts-plus » Tue Jun 27, 2023 12:42 pm

As to your third question: to my understanding portage itself always called it repository. Every overlay is a repository, but not every repository is a overlay.
If a repository has a master (see metadata/layout.conf) this repository is layed on top of the master repository.

But I might also be totally wrong :lol:
Top
NeddySeagoon
Administrator
Administrator
User avatar
Posts: 56106
Joined: Sat Jul 05, 2003 9:37 am
Location: 56N 3W

  • Quote

Post by NeddySeagoon » Tue Jun 27, 2023 1:36 pm

Bigun,

The concept of overlays has changed a lot in the last 20 years :)
The used to be the portage tree and additions to it called overlays. Usually only one addition, your local overlay.

Layman made overlays easier to manage and made it easy to have several overlays.

When eselect repository was introduced, the concept was generalised, so we have the ::gentoo repo(sitory), which everyone has plus other repositories too.
All collection of ebuilds are repositories.

To migrate from layman to eselect repository, you rewrite the index to your repositories. Exactly how you do that depends on where your repositories are stored.
The default location is /var/db/repos/, I have

Code: Select all

$ ls /var/db/repos/
crossdev  gentoo  gentoo-static  librewolf  mva
They are covered by the indices in /etc/portage/repos.conf/

Code: Select all

$ ls /etc/portage/repos.conf/
eselect-repo.conf  gentoo.conf
If you do eselect repository add ... you may end up with a new copy, managed by eselect repository and an old abandoned unused copy that was managed by layman.

Make a note of the repos you have installed with layman. If they are all still available, remove them.
Add them again with eselect repository add ... now you only have a single copy of the overlays wherever eselect repository put them.

For overlays that are not available any longer. Can you do without them. The ebuilds will suffer bitrot, so its only a matter of time.
The migration is to tell eselect repository about it with the add command.

See

Code: Select all

eselect repository help
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Top
Bigun
Advocate
Advocate
User avatar
Posts: 2198
Joined: Sun Sep 21, 2003 3:45 am
Contact:
Contact Bigun
Website

  • Quote

Post by Bigun » Mon Jul 03, 2023 7:07 pm

Thank you, very clear and moved off of layman.
"It's ok, they might have guns but we have flowers." - Perpetual Victim
Top
Brumi-2021
n00b
n00b
Posts: 8
Joined: Sun Oct 17, 2021 8:34 am

layman being replaced by eselect - questions

  • Quote

Post by Brumi-2021 » Tue Jul 18, 2023 11:19 am

User: Bigun
Topic: [solved] layman being replaced by eselect - questions
Post: [post]8794320[/post]
Reason:


Hello thanks for opening and sharing that issue .

I have similar problem with app-portage/layman-243
Recently , no updating , getting that error,

Code: Select all

emerge: there are no ebuilds built with USE flags to satisfy ">=sys-apps/portage-2.2.16[python_targets_pypy3(-)?,python_targets_python3_10(-)?,python_targets_python3_11(-)?]".
!!! One of the following packages is required to complete your request:
- sys-apps/portage-3.0.49-r1::gentoo (Change USE: +python_targets_python3_10)
- app-portage/layman-2.4.3::gentoo (Change USE: -python_targets_python3_10)
(dependency required by "app-portage/layman-2.4.3::gentoo" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

I already emerged the app-eselect/eselect-repository

Can you please give me some more details about how to migrate the layman to eselect-repository .
Do I need to unemerge first the layman, which commands ?
, and which files do I need to edit to migrate it .

This is my , $ ls /etc/portage/repos.conf/
layman.conf my-overlay.conf pentoo.conf


This is my , ls /var/db/repos/
gentoo pentoo


thanks in advance ,

The poster cliched Report rather than Reply, so the post went to the wrong topic.
Added code tags too -- NeddySeagoon
Top
NeddySeagoon
Administrator
Administrator
User avatar
Posts: 56106
Joined: Sat Jul 05, 2003 9:37 am
Location: 56N 3W

  • Quote

Post by NeddySeagoon » Tue Jul 18, 2023 11:41 am

Brumi-2021,

layman and eselect repository do the same thing in different ways and keep their .conf files in different locations too.
I think that they use different default locations for overlays too.

There are two or three approaches.

Migrate your layman.conf to eselect repository.
Remove your existing overlays, then readd them with eselect repository.
The worst of both ... move the overlays to the new location, then tell eselect repository about them.
Abandon the layman repos where they are, that's just disk clutter and add the repos again with eselect repository.
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Top
Fitzcarraldo
Advocate
Advocate
User avatar
Posts: 2057
Joined: Sat Aug 30, 2008 9:49 pm
Location: United Kingdom
Contact:
Contact Fitzcarraldo
Website

  • Quote

Post by Fitzcarraldo » Tue Jul 18, 2023 12:15 pm

Brumi-2021,

In case it is of help, below is how I migrated from Layman to the eselect respository module:

First I checked which third-party Portage overlays were being managed by Layman in my installations:

Code: Select all

# layman -l

 * guru                      [Git       ] (https://anongit.gentoo.org/git/repo/proj/guru.git                                             )
 * seden                     [Git       ] (https://anongit.gentoo.org/git/user/seden.git                                                 )

The repos.conf directory on my machines each had three configuration files (one for the main Portage repository; one for the Layman-managed third-party overlays; one for my local overlay on the machine):

Code: Select all

# ls /etc/portage/repos.conf
gentoo.conf  layman.conf  local_overlay.conf
The layman.conf file contained the information on the third-party overlays:

Code: Select all

# cat /etc/portage/repos.conf/layman.conf 
[guru]
priority = 50
location = /var/lib/layman/guru
layman-type = git
sync-type = laymansync
sync-uri = https://anongit.gentoo.org/git/repo/proj/guru.git
auto-sync = Yes

[seden]
priority = 50
location = /var/lib/layman/seden
layman-type = git
sync-type = laymansync
sync-uri = https://anongit.gentoo.org/git/user/seden.git
auto-sync = Yes
The first thing I did was to use Layman to delete the two third-party overlays:

Code: Select all

# layman -d guru

 * Deleting selected overlay(s)...
 * Deleting directory "/var/lib/layman/guru"
 * Successfully deleted overlay(s) guru.

# layman -d seden

 * Deleting selected overlay(s)...
 * Deleting directory "/var/lib/layman/seden"
 * Successfully deleted overlay(s) seden.
Then I installed the eselect-repository package:

Code: Select all

# emerge eselect-repository
Calculating dependencies... done!
Dependency resolution took 36.59 s.


!!! The following installed packages are masked:
- app-portage/layman-2.4.3::gentoo (masked by: package.mask)
/usr/portage/profiles/package.mask:
# David Seifert  (2023-05-19)
# Abandoned, replaced by 'eselect repository', tons of open bugs.
# Removal on 2023-08-17. Bug #761199.

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

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-eselect/eselect-repository-13::gentoo
>>> Installing (1 of 1) app-eselect/eselect-repository-13::gentoo
>>> Completed (1 of 1) app-eselect/eselect-repository-13::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 1.17, 0.62, 0.34

 * GNU info directory index is up-to-date.
Then I used the ‘eselect repository‘ command to re-add the two overlays:

Code: Select all

# eselect repository add guru git https://anongit.gentoo.org/git/repo/proj/guru.git
--2023-06-25 14:09:31--  https://qa-reports.gentoo.org/output/repos/repositories.xml
Resolving qa-reports.gentoo.org... 151.101.61.91, 2a04:4e42:82::347
Connecting to qa-reports.gentoo.org|151.101.61.91|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 253999 (248K) [text/xml]
Saving to: ‘/root/.cache/eselect-repo/repositories.xml’

repositories.xml                               100%[====================================================================================================>] 248.05K  --.-KB/s    in 0.06s   

2023-06-25 14:09:32 (4.19 MB/s) - ‘/root/.cache/eselect-repo/repositories.xml’ saved [253999/253999]

Adding guru to /etc/portage/repos.conf/eselect-repo.conf ...
Repository guru added
# eselect repository add seden git https://anongit.gentoo.org/git/user/seden.git
Adding seden to /etc/portage/repos.conf/eselect-repo.conf ...
Repository seden added
Then I synchronised the two overlays with their respective repository:

Code: Select all

# emaint sync -r guru
>>> Syncing repository 'guru' into '/var/db/repos/guru'...
/usr/bin/git clone --depth 1 https://anongit.gentoo.org/git/repo/proj/guru.git .
Cloning into '.'...
remote: Enumerating objects: 9267, done.
remote: Counting objects: 100% (9267/9267), done.
remote: Compressing objects: 100% (8162/8162), done.
remote: Total 9267 (delta 1303), reused 7128 (delta 1010), pack-reused 0
Receiving objects: 100% (9267/9267), 6.53 MiB | 3.11 MiB/s, done.
Resolving deltas: 100% (1303/1303), done.
Updating files: 100% (7445/7445), done.
=== Sync completed for guru
!!! Section 'seden' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/seden'

Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  #='/var/db update'  @='/var/db move'
  s='/var/db SLOT move'  %='binary move'  S='binary SLOT move'
  p='update /etc/portage/package.*'
/var/db/repos/guru/profiles/updates/3Q-2020.
/var/db/repos/guru/profiles/updates/1Q-2020.
/var/db/repos/guru/profiles/updates/1Q-2021......
/var/db/repos/guru/profiles/updates/2Q-2022.........
/var/db/repos/guru/profiles/updates/4Q-2020...
/var/db/repos/guru/profiles/updates/1Q-2022....
/var/db/repos/guru/profiles/updates/2Q-2020..
/var/db/repos/guru/profiles/updates/3Q-2022.....
/var/db/repos/guru/profiles/updates/1Q-2023......
/var/db/repos/guru/profiles/updates/2Q-2021............
/var/db/repos/guru/profiles/updates/2Q-2023.........
/var/db/repos/guru/profiles/updates/4Q-2021...........
/var/db/repos/guru/profiles/updates/4Q-2022..


!!! Section 'seden' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/seden'

Action: sync for repo: guru, returned code = 0

# emaint sync -r seden
>>> Syncing repository 'seden' into '/var/db/repos/seden'...
/usr/bin/git clone --depth 1 https://anongit.gentoo.org/git/user/seden.git .
Cloning into '.'...
remote: Enumerating objects: 160, done.
remote: Counting objects: 100% (160/160), done.
remote: Compressing objects: 100% (143/143), done.
remote: Total 160 (delta 16), reused 29 (delta 4), pack-reused 0
Receiving objects: 100% (160/160), 78.45 KiB | 1.40 MiB/s, done.
Resolving deltas: 100% (16/16), done.
=== Sync completed for seden

Action: sync for repo: seden, returned code = 0
I checked that the repositories are listed correctly (the main Gentoo Linux repository and the third-party overlays have a hash symbol after the name, and a local overlay on the machine has the ‘@‘ symbol after the name):

Code: Select all

# eselect repository list
Available repositories:
  [1]   4nykey (https://github.com/4nykey/4nykey)
  [2]   AlexandreFournier (https://github.com/AlexandreFournier/gentoo-overlay)
  [3]   ArchFeh (https://github.com/ArchFeh/ArchFeh-overlay)
  [4]   AstroFloyd (https://cgit.gentoo.org/user/AstroFloyd.git/)
  [5]   CachyOS-kernels (https://github.com/Szowisz/CachyOS-kernels)
  [6]   Case_Of (https://codeberg.org/Case_Of/gentoo-overlay)
  [7]   Drauthius (https://cgit.gentoo.org/repo/user/Drauthius.git/)
  [8]   EmilienMottet (https://github.com/EmilienMottet/overlay)
  [9]   FireBurn (https://github.com/FireBurn/Overlay)
  [10]  HomeAssistantRepository (https://git.edevau.net/onkelbeh/HomeAssistantRepository)
[...]
  [370] x0rzavi (https://github.com/x0rzavi/x0rzavi-overlay)
  [371] x11 (https://cgit.gentoo.org/proj/x11.git)
  [372] xarblu-overlay (https://github.com/xarblu/xarblu-overlay)
  [373] xdch47 (https://github.com/xdch47/gpo-xdch47)
  [374] xelnor (http://overlay.xelnor.net)
  [375] xoreos (https://github.com/xoreos/gentoo-overlay)
  [376] xwing (https://gentoo.xwing.info)
  [377] yandex (https://github.com/yandex-gentoo/overlay)
  [378] yurij-overlay (https://github.com/yurijmikhalevich/yurij-overlay)
  [379] zGentoo (https://lab.retarded.farm/zappel/zGentoo)
  [380] zeldu (https://github.com/3elDU/gentoo-repository)
  [381] zerodaysfordays (https://git.sr.ht/~jakob/zerodaysfordays)
  [382] zozx-overlay (https://github.com/zozx/zozx-overlay)
  [383] zugaina (http://gpo.zugaina.org/Overlays/zugaina/)
  [384] zyrenth (https://github.com/kabili207/zyrenth-overlay)
These are easier to see by listing only the installed repositories:

Code: Select all

# eselect repository list -i
Available repositories:
  [136] gentoo # (https://gentoo.org/)
  [153] guru # (https://wiki.gentoo.org/wiki/Project:GURU)
  [196] local_overlay @
  [290] seden # (https://cgit.gentoo.org/user/seden.git/)
So, as everything looked correct, I then removed Layman from the installations:

Code: Select all

# emerge --ask --depclean layman

Calculating dependencies... done!
>>> Calculating removal order...

>>> These are the packages that would be unmerged:

 app-portage/layman
    selected: 2.4.3 
   protected: none 
     omitted: none 

All selected packages: =app-portage/layman-2.4.3

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Would you like to unmerge these packages? [Yes/No] Yes
>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging (1 of 1) app-portage/layman-2.4.3...
Packages installed:   1826
Packages in world:    254
Packages in system:   48
Required packages:    1826
Number removed:       1

 * GNU info directory index is up-to-date.
I also deleted all Layman directories and the Layman configuration file in the repos.conf directory:

Code: Select all

# rm -rf /var/lib/layman
# rm /etc/portage/repos.conf/layman.conf
# rm -rf /etc/layman
For good measure I synced the main Portage tree and the two overlays again:

Code: Select all

# emaint sync -a
[...]
x11-misc/compose-tables/compose-tables-1.8.6.ebuild
x11-themes/Manifest.gz
x11-themes/QGnomePlatform/Manifest
x11-themes/QGnomePlatform/QGnomePlatform-0.9.1-r1.ebuild
x11-themes/QGnomePlatform/metadata.xml
x11-themes/numix-icon-theme-circle/Manifest
x11-themes/numix-icon-theme-circle/numix-icon-theme-circle-23.04.28.ebuild
x11-themes/numix-icon-theme/Manifest
x11-themes/numix-icon-theme/numix-icon-theme-23.04.26.ebuild
x11-wm/Manifest.gz
x11-wm/xpra/Manifest
x11-wm/xpra/xpra-4.4.6.ebuild

Number of files: 145,549 (reg: 118,735, dir: 26,814)
Number of created files: 600 (reg: 578, dir: 22)
Number of deleted files: 622 (reg: 600, dir: 22)
Number of regular files transferred: 5,382
Total file size: 190.75M bytes
Total transferred file size: 20.90M bytes
Literal data: 20.90M bytes
Matched data: 0 bytes
File list size: 3.70M
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 131.96K
Total bytes received: 16.87M

sent 131.96K bytes  received 16.87M bytes  400.04K bytes/sec
total size is 190.75M  speedup is 11.22
 * Manifest timestamp: 2023-06-25 12:39:45 UTC
 * Valid OpenPGP signature found:
 * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D
 * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
 * - timestamp: 2023-06-25 12:39:45 UTC
 * Verifying /usr/portage/.tmp-unverified-download-quarantine ...                                                                                                                    [ ok ]
=== Sync completed for gentoo
>>> Syncing repository 'seden' into '/var/db/repos/seden'...
>>> Syncing repository 'guru' into '/var/db/repos/guru'...
/usr/bin/git fetch origin --depth 1
/usr/bin/git fetch origin --depth 1
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
/usr/bin/git reset --merge refs/remotes/origin/master
=== Sync completed for seden
remote: Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
/usr/bin/git reset --merge refs/remotes/origin/master
=== Sync completed for guru

Action: sync for repo: gentoo, returned code = 0
Action: sync for repo: seden, returned code = 0
Action: sync for repo: guru, returned code = 0
As one of the overlays was causing a problem in my case, below is how I disabled that overlay using the 'eselect repository' command.

My installations have the elogind package installed but it turned out that the package could not be re-merged due to an error in the manifest of one of the packages in the seden overlay:

Code: Select all

# emerge -1v elogind

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 38.39 s.

[ebuild     U  ] sys-auth/elogind-252.9::seden [246.10-r3::gentoo] USE="acl doc pam (policykit) -audit -debug (-selinux) -test (-cgroup-hybrid%*)" 0 KiB

Total: 1 package (1 upgrade), Size of downloads: 0 KiB

>>> Verifying ebuild manifests

!!! A file listed in the Manifest could not be found: /var/db/repos/seden/sys-auth/elogind/elogind-239.9999.ebuild
Therefore I disabled the seden overlay:

Code: Select all

# eselect repository disable seden
Updating repos.conf ...
1 repositories disabled
I was then able to install the latest version of elogind available in the main Portage repository:

Code: Select all

# emerge -1v elogind

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 14.27 s.

[ebuild   R    ] sys-auth/elogind-246.10-r3::gentoo  USE="acl cgroup-hybrid doc pam (policykit) -audit -debug (-selinux) -test" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-auth/elogind-246.10-r3::gentoo
>>> Installing (1 of 1) sys-auth/elogind-246.10-r3::gentoo
>>> Completed (1 of 1) sys-auth/elogind-246.10-r3::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 3.12, 2.63, 2.01

 * GNU info directory index is up-to-date.
Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC systemd-utils[udev] elogind KDE on both.

My blog
Top
Brumi-2021
n00b
n00b
Posts: 8
Joined: Sun Oct 17, 2021 8:34 am

layman being replaced by eselect - questions

  • Quote

Post by Brumi-2021 » Tue Jul 18, 2023 2:35 pm

[quote="Fitzcarraldo"]Brumi-2021,

In case it is of help, below is how I migrated from Layman to the eselect respository module:.....
--------------------

Hello , @Fitzcarraldo, thanks a lot for your detailed steps explanations . That is what i needed !!!!!!

I could follow all your steps and move the 3 layman repos to the new methode with eselect-repository tool.

I only had one problem at the end , that even having deleted all related directories , when trying to re-sync the 3 repos ,
I got this kind of error , (similar in the 3 external repo sync)

Code: Select all

 pentoo@pentoo / $ sudo emaint sync -r hamari
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/portage/util/__init__.py", line 735, in sourcehook
    return shlex.shlex.sourcehook(self, newfile)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 286, in sourcehook
    return (newfile, open(newfile, "r"))
                     ^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/layman/make.conf'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.11/emaint", line 57, in <module>
    emaint_main(sys.argv[1:])
  File "/usr/lib/python3.11/site-packages/portage/emaint/main.py", line 245, in emaint_main
    returncodes = taskmaster.run_tasks(tasks, func, status, options=task_opts)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/emaint/main.py", line 122, in run_tasks
    inst = task()
           ^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/emaint/modules/sync/sync.py", line 51, in __init__
    emerge_config = load_emerge_config(action="sync", args=_files, opts=opts)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/proxy/objectproxy.py", line 31, in __call__
    return result(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/_emerge/actions.py", line 2908, in load_emerge_config
    emerge_config.trees = portage.create_trees(trees=emerge_config.trees, **kwargs)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/__init__.py", line 650, in create_trees
    settings = config(
               ^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/package/ebuild/config.py", line 441, in __init__
    mygcfg = getconfig(
             ^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/util/__init__.py", line 779, in getconfig
    getconfig(
  File "/usr/lib/python3.11/site-packages/portage/util/__init__.py", line 854, in getconfig
    key = _unicode_decode(lex.get_token())
                          ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/shlex.py", line 113, in get_token
    spec = self.sourcehook(self.read_token())
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/portage/util/__init__.py", line 752, in sourcehook
    raise ParseError(msg)
portage.exception.ParseError: "/etc/portage/make.conf", line 40: /var/lib/layman/make.conf: No such file or directory
I could solve it , by editing my file
sudo nano /etc/portage/make.conf

And i need to do two things ,

(1) comment or delete that second line related to layman,
# overlays de Layman:
==> # source /var/lib/layman/make.conf

And after saving that make.conf without that line, now my system is doing a correct sync + correct system update .
Now after several weeks without any update due to layman conflict ,

(2) I should go to edit eselect-repo.conf, adding priority parameter,
sudo nano /etc/portage/repos.conf/eselect-repo.conf
And add to those external repo, higher priority (priority = 50) , than the base pentoo (priority = 49)

Code: Select all

 Example , 
[hamari]
priority = 50
location = /var/db/repos/hamari
sync-type = git
sync-uri = https://github.com/hamarituc/gentoo-overlay.git

With those following two changes , now finally my system is emerging from pentoo correctly again , 870 packages and also linux kernel update !
and I can emerge external packages.

Thanks a lot for your big and usefull help !!!!
Top
Post Reply

9 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic