Ensure that ebuilds use our sources in case of archived repositories

[krnowak]

Current situation

There are some ebuilds, like nova-agent-container or nova-agent-watcher, that are pulling sources from coreos github org. I think those should be forked over to kinvolk org.

Impact

If the organization ever goes away, the build will be broken and the sources may be hard to recover back. Also, if there's ever a need to fixing a bug, the fork will necessary anyway, since the projects are archived, thus read-only.

Ideal future situation

All ebuilds refer to either maintained projects or to kinvolk fork.

[tormath1]

we should create a list of this ebuild files to track them into the issue!

[aniruddha2000]

Hello! I would like to work on this issue. As the flatcar init ebuild is pointing to the kinvolk fork. Do I need to change the ebuild of nova-agent-container and nova-agent-watcher so that they point to kinvolk own fork. But as there is now such fork of the two packages in the kinvolk. In that case I need some direction what should be my approach.

[sayanchowdhury]

Solving this might not be straightforward and might need admin access, as we need to create a copy of all the required repos into the flatcar-linux org and then updating the references in the ebuild files.

to start off it would be good to create a list of repos that are still referring to github.com/coreos/

[aniruddha2000]

I searched in the coreos-overlay and got some packages that still referring to github.com/coreos/ List -

• sysroot-wrappers
• eselect-go
• nova-agent-container
• nova-agent-watcher
• fero-client
• kola-data
• go-tspi

Although I am not sure about coreos-au-key sysroot-wrappers repo already exist in kinvolk.