So let's experiment with this... :) announcing: https://gentoo.osuosl.org/experimental/amd64/binpkg/default/linux/17.1/x86-64/
More information can be found in a blog post, which will also be on planet.g.o
soon: https://dilfridge.blogspot.com/2021/09/experimental-binary-gentoo-package.html
Cheers -A
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
Andreas,
How is USE=bindist treated?
Its on for stage building and off in profiles.
Andreas,
How is USE=bindist treated?
Its on for stage building and off in profiles.
USE=bindist is switched on, and in addition we have
ACCEPT_RESTRICT="* -bindist"
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
I have repos configs placed into /etc/portage/repos.conf with
"rsync-type = git" fo all repos
so I created binhost.cond file here instead of /etc/portage/ as
mentioned in blog post.
Then I tried to sync and got warnings:
...
!!! Section 'binhost' in repos.conf is missing location attribute
!!! Repository 'binhost' has sync-uri attribute, but is missing
sync-type attribute
...
So it seems it's dosn't sync with binhost index without location attribute. After setup location attribute to specific directory I got warning on
sync trying:
!!! Repository 'binhost' has sync-uri attribute, but is missing
sync-type attribute
!!! Repository 'binhost' is missing masters attribute in '/usr/local/portage/binhost/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
I tried to set up "rsync-type = rsync" or "webrsync" with "amsters =
gentoo" but then I got error:
!!! Repository 'binhost' is missing masters attribute in '/usr/local/portage/binhost/metadata/layout.conf'
!!! Set 'masters = gentoo' in this file for future compatibility
So I created /usr/local/portage/binhost/metadata/layout.conf :
masters = gentoo
auto-sync = false
thin-manifests = true
So then on sync I got:
  The current sync-type attribute of repository 'gentoo' is not set to 'rsync' or 'webrsync':
  sync-type=git
----
Is it currently git sync available for binhost?
Sorry for previous html message. I tried to recend it as plaintext.
I have repos configs placed into /etc/portage/repos.conf with
"rsync-type = git" fo all repos so I created binhost.cond file here
instead of /etc/portage/ as mentioned in blog post.
binhost.conf should be in binrepos.conf instead of repos.conf. See also: https://wiki.gentoo.org/wiki/Binary_package_guide#Pulling_packages_from_a_binary_package_host
A binhost is different from an ebuild repository, it is just a
collection of .xpak files so there is no git sync involved.
Finally it happened!
I already planned to try to ask infra/council about sponsoring few
servers for build farm for "official gentoo binhosts" when I had
enough time, but fortunately, you've already did that.
It's very good news.
Btw, do you need any help with that?
I'd be very happy to help with that project.
3. an easy way to figure out if a binary package repo is suitable for
a profile / arch / ... or not, and a standard for path names
This is not so important right now, and partially also already present
Hi Vadim,
Finally it happened!
I already planned to try to ask infra/council about sponsoring few
servers for build farm for "official gentoo binhosts" when I had
enough time, but fortunately, you've already did that.
It's very good news.
Thanks! Nice to see that this is appreciated :)
So far I'm only using "spare time" on the machine that builds the
releng stages (amd64, x86, m68k, riscv). So no need for a big server
farm.
Btw, do you need any help with that?
I'd be very happy to help with that project.
Sure! Feel free to add yourself to the Project:Binhost wiki page. I'll
ask for an alias and a channel soon.
The most useful steps now are only half related to actual building. I
barely know any python and am not very familiar with portage
internals... this is what in my opinion we'd need next:
1) a tool to manage and manipulate a binpkg/ directory tree
The main functions that I see needed are
* delete packages/versions that are not in the gentoo repository
anymore (xpak and in index file), maybe with some grace time
* merge xpak files built elsewhere into the directory (also in the
index file)
On Thu, Sep 23, 2021 at 7:12 AM Andreas K. Huettel <dilfridge@gentoo.org> wrote:
Hi Vadim,
Finally it happened!
I already planned to try to ask infra/council about sponsoring few servers for build farm for "official gentoo binhosts" when I had
enough time, but fortunately, you've already did that.
It's very good news.
Thanks! Nice to see that this is appreciated :)
So far I'm only using "spare time" on the machine that builds the
releng stages (amd64, x86, m68k, riscv). So no need for a big server
farm.
Btw, do you need any help with that?
I'd be very happy to help with that project.
Sure! Feel free to add yourself to the Project:Binhost wiki page. I'll
ask for an alias and a channel soon.
The most useful steps now are only half related to actual building. I barely know any python and am not very familiar with portage
internals... this is what in my opinion we'd need next:
1) a tool to manage and manipulate a binpkg/ directory tree
The main functions that I see needed are
* delete packages/versions that are not in the gentoo repository
anymore (xpak and in index file), maybe with some grace time
* merge xpak files built elsewhere into the directory (also in the
index file)
eclean packages from gentoolkit does this exactly.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 51:52:06 |
Calls: | 6,650 |
Calls today: | 2 |
Files: | 12,200 |
Messages: | 5,330,383 |