My Hugo package continues to gobble up more dependencies. The following
are available for review, and they are required before I can package
Hugo 0.121.1:

golang-github-tj-spin: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256316
golang-github-tj-kinesis: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256315
golang-github-tj-elastic: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256314
golang-github-tj-buffer: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256313
golang-github-tj-assert: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256312
golang-github-mgutz-ansi: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256311
golang-github-bep-mclib: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256310
golang-github-bep-logg: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256309
golang-github-bep-godartsass-2: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256308
golang-github-aybabtme-rgbterm: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256307
golang-github-aphistic-sweet: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256306
golang-github-aphistic-golf: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256305
golang-github-apex-logs: 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2256304
golang-github-apex-log: https://bugzilla.redhat.com/show_bug.cgi?id=2256303

I generated each of these using go2rpm, and I have started to build them
in COPR at:

https://copr.fedorainfracloud.org/coprs/mikep/golang/builds/

-- 
Mike

:wq
--
_______________________________________________
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-le...@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/golang@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to