On 2016-01-28 21:16, Bjarne Saltbæk wrote:
Hi Gordan.

If you ignore the original date on the mail I respond on now :D - do
your offer still stand?

I could probably put something together next weekend. No promises on
what it might be at the moment. I comprehensively failed to do the
server maintenance I was hoping to do this weekend, but I'll see
what I can do. Poke me a reminder toward the end of the week,

I have now (I think) a working Koji setup. Took me almost a year (of
spare time) to understand how Koji work and now I badly need build
power :-D

And now you understand why I instead chose to write 50 lines of
bash to provide the required functionality. The one killer feature
Koji would have had to bring with it is dependency resolution that
ensures that packages are build in order that ensures no FTBFS-es
due to missing dependencies. It doesn't provide this feature, so
apart from a pretty web front end and being "very enterprisey" I
am struggling to see why it is useful.

Please - do tell.

Compile time on a RPI 2B is sooo slow and it will take more than a
week to compile the whole EPEL6 repo.

Welcome to our world. :)
I can highly recommend the Samsumg Chromebook 2. Easily the
most cost effective ARM machine at the moment, and the convenience
of the laptop form factor is also very helpful.

I plan to move my esx host to my scullery so it can run 24/7 this
weekend. Then I can provide public access to the koji hub and the git
server.

Are concise docs on how to reproducibly set it up and getting it
working on RSEL7 available?

The builders can then pull code from git and transfer packages to/from
the hub. I also need to grant the builders access to the Sigul bridge
(just a port) for RPM signing.
I have made a "RedSleeve Test" gpg key that I sign the packages with.
I can rename the key if it is not appropriate.

On a side note: Speaking of the performance of the RPI - I have looked
at the specs on the Banana PI. It looks rather good. More RAM, a SATA
connetion.
Is it any good or will I get the same low performance as the RPI?


SATA (with a decent disk) helps during the initial setup (e.g. extract
src.rpm) stage. Once things start to compile, things are mostly CPU
limited.

Gordan
_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

Reply via email to