https://bugzilla.redhat.com/show_bug.cgi?id=1430132 --- Comment #3 from Ed Marshall <esm@xxxxxxxxx> --- I'll run the next update through koji (or at least add all arches to the copr repo); I've been using copr for my workflow for this as I've been wading through dependencies and it makes working with a large group of packages easier, but at the level of individual reviews, koji is probably better on a few fronts. Re: the older version, I'm building this as a dependency for Hashicorp Vault, and the version I'm able to build against the dependencies in Fedora today (specifically, Consul is pretty far out of date, and updating it is a bit messy: #1348906) means back-dating this dependency before sweeping API change was made (contexts were added to most of the API). Do you see the older version as a sticking point? There's an argument to be made for just bringing the newest version in how, with the assumption that everything else will have caught up by the time I'm trying to package Vault, but I've learned to be conservative when estimating the rate of updates for golang dependencies in Fedora. ;) Tests/provides: good catch, and you're right; I'll clean that up. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx