On Sat, Jun 29, 2019 at 10:15 AM Nicolas Mailhot via devel
<devel(a)lists.fedoraproject.org> wrote:
Hi,
> What should I do at this moment as a packager that maintaining some
> Go packages?
> Should I fix my packages and build against f31-go in Koji?
Yes, sure, if you can that would be appreciated. The vast majority of
packages is easy to clean up (just adapt the templates in go-rpm-
templates or use go2rpm), it's just there is an awful lot of them, so
Robert-André Mauchin (eclipseo) can not do all of them in a single
pass.
It's great to see that all this stuff is finally coming together.
I've tried to fix some of my broken packages locally, but I had
trouble getting go2rpm to run from the sources -
because AFAICT, go2rpm isn't packaged for fedora yet. Is there
anything blocking a package or has just nobody worked on it yet?
Fabio
> If you hit one of the cases where a project needs weird stuff, or if
> you do not understand something, there is help available here and in
> the #fedora-golang channel.
>
> Please just state here (or tell eclispeo directly) what you will
> convert, so you do not end up doing the same work in parallel.
>
> Quite often, eclipseo will have prepared things in his copr, just not
> built them in koji yet.
>
https://copr.fedorainfracloud.org/coprs/eclipseo/golang-ng/
>
> So taking up from where he prepared, and checking the result builds in
> koji and works for you, will accelerate things.
>
> @eclipseo: please correct if I wrote something that does not make
> things easier your side
>
> Regards,
>
> --
> Nicolas Mailhot
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org