description: A personal overlay with no specific focus (mainly to test ebuilds). Highly experimental. It is meant as a playground for me, but others might be interested. homepage (optional): . admin access to: Myself write access to: Myself public SSH key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEEUv+Fug+DQj3Mgpkj97ne9tko6IM5c5RgD8KW/knzJ ci3nt@gump ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIOFOnKq8r3840Ii5DMXZMT8ArapZwrMtfadQJRaHSW+N gerion@falbala ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCis4xj15zD+BvNM/wrhivxdz5iNrp3aOgl3QDidacE5aDk5XbmMc4JeoOhV9iTU0UY/DVLjg0LCXc6O9YbMAnC4fMFyKDV+FTm8Kc9Bo3PPTPmpZhJUZgCqc3G0N4PkzP5FkCfvgArPbCFPFuembqfqQDVWJBU4WdomeauBOvgaRJ4R9aMLyXFEvzqwbu/nWeqkE7ae4UHSKZVHJXER/C73vkXQcPZg2HXuON0BmnD7966LDPzQPA9OvFErIAzkwKQYW0W2OhQrCYJFI/9qtOJvT0Udo2MZUo4W00OkhyZzLVo5ocvO/LXOUOHTopBHpQQN89V/TgSINPcYrFQ9+dr ci3nt@lappi (Can I somehow modify my keys without interacting with you?)
Your user overlay "gerislay" is almost ready. Please read (all of) this guide to get it to work. If you have any question we'll be here to help. In this Guide ============= - Terms of Service - The Initial Push - After That - Online Browsing - Getting into Layman - Keeping your overlay healthy Terms of Service ================ The infra team has worked out the terms of service for us. To make us host your user overlay you need to accept these terms, which I don't expect to be a problem. By pushing to the remote repository you are accepting these terms: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Use of this service is limited to overlays containing ebuilds and supporting files (e.g. init.d scripts, configuration files, patches, but not distfiles) and must follow the same guidelines as apply to the gentoo-x86 tree of Gentoo. Any or all uses of this service and all files on this service may be intercepted, monitored, recorded, copied, audited, inspected, and disclosed to authorized site personnel, as well as authorized officials of federal law enforcement agencies, both domestic and foreign. By using this service, the user consents to such interception, monitoring, recording, copying, auditing, inspection, and disclosure at the discretion of authorized site personnel. Use of this service constitutes consent to security monitoring and testing. All activity is logged with your host name and IP address. Unauthorized or improper use of this service may result in civil and criminal penalties. By continuing to use this service you indicate your awareness of and consent to these terms and conditions of use. -- Gentoo Linux Infrastructure Admins CEASE USE IMMEDIATELY, if you do not agree to the conditions stated in this warning. ******************* -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- The Initial Push ================ First, before anybody can clone from your overlay an initial push is needed. 0) If you start with an empty repository be sure to setup your identity: # git init # git config user.name 'first last' # git config user.email foo@example.org [..] 1) Once you have ebuilds in there please set profiles/repo_name to '${USER}' in order to make it a valid overlay. Unless your ebuilds do not require any eclasses or licenses, and do not depend on any packages from Gentoo, set masters=gentoo in metadata/layout.conf as well. # mkdir metadata profiles # echo "masters = gentoo" > metadata/layout.conf # echo "gerislay" > profiles/repo_name # git add metadata/layout.conf profiles/repo_name # git commit 2) Now you are ready to push. Proposed way of doing is this: # git remote add overlays-gentoo-org \ git+ssh://git@git.gentoo.org/repo/user/gerislay.git # git push overlays-gentoo-org master After That ========== Online Browsing --------------- After the initial push you can browse your overlay online at: https://gitweb.gentoo.org/repo/user/gerislay.git/ Getting into Layman ------------------- We have scripts to get hosted overlay into Layman easily: no need to write XML on your end. Just let us know that you did complete the procedure from "The Initial Push" to get added. Once it's in the Layman registry its content will be indexed at http://gpo.zugaina.org/ and two dedicated views of your overlay will appear at http://gentoo-overlays.zugaina.org/gerislay/ and http://gpo.zugaina.org/Overlays/gerislay/, too. Keeping your overlay healthy ---------------------------- A few rules of thumb help to keep your overlay most useful to you and others: - If you package newer versions of software that is packaged in Gentoo already, try to get the version in Gentoo updated, too. (If there is no bump request on https://bugs.gentoo.org/ please file one and share patches you may have produced.) - If you apply custom patches make sure that you never use the very same revision that is used in Gentoo, e.g. if you use the ebuild of app-arch/bzip2-1.0.6-r3 do not call it app-arch/bzip2-1.0.6-r3 in your overlay to avoid confusion. A tool called "overlint" can support you with that process: # sudo emerge -av app-portage/overlint For a quick introduction to overlint see http://blog.hartwork.org/?p=1667 . To answer your question regarding SSH key management, unfortunately self-service is not available. Please file a bug for the overlays team with any changes you require. Michael, for the Gentoo Overlays Team
Initial push done. Would be great, if you add it to layman. Thank you for adding the repo.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/data/api.git/commit/?id=c10a9dcb11da23cfcfa1c906c1c1f43ac73a5b66 commit c10a9dcb11da23cfcfa1c906c1c1f43ac73a5b66 Author: Michael Palimaka <kensington@gentoo.org> AuthorDate: 2018-07-17 13:34:26 +0000 Commit: Michael Palimaka <kensington@gentoo.org> CommitDate: 2018-07-17 13:34:31 +0000 repositories: add gerislay Closes: https://bugs.gentoo.org/658724 files/overlays/repositories.xml | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
For the record, I've banned it from repo-mirror-ci since it used some fancy mistake of EAPI that crashed the whole system.
Do you mean my repository? Sorry, if this is the case. How can I trigger the error?
You need to install pkgcore, and run 'pmaint regen'.
pmaint regen should work without errors now.
profiles/eapi still specifies 5-progress which means pkgcore can't use that repository at all. If it works for you, you're probably using an older buggy version that doesn't parse EAPI in that file.
Thank you for the clarification. I have removed the file (as far as I can remember, it was neccessary for some feature, when EAPI 4 was in use). However, pmaint does not complain about anything. I have pkgcore-0.9.7 (all commands are executed with the profiles/eapi file): # pmaint regen WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/crossdev' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/riscv-gentoo' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/crossdev' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/riscv-gentoo' skipping repo vdb: location /var/db/pkg: cache disabled skipping repo ('/usr/overlays/pzskc383', '/usr/overlays/crossdev', '/usr/overlays/kde', '/usr/overlays/audio-overlay', '/usr/overlays/matrix', '/usr/overlays/pentoo', '/usr/overlays/dotnet', '/usr/local/portage', '/usr/overlays/riscv-gentoo', '/usr/overlays/qt', '/usr/portage'): cache disabled # pmaint regen --force WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/crossdev' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/riscv-gentoo' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/riscv-gentoo' WARNING:pkgcore:repo lacks a defined name: '/usr/overlays/crossdev' (The second command takes a long time.) I have searched several places to find out how to enable my cache, especially since `emerge --regen` seems to work, but did not found anything.
Put into metadata/layout.conf: cache-formats = md5-dict
