On 27.07.2017 15:05, Michael Stapelberg wrote:
> It does break the API, as evinced by one build failure.
> I’m not aware of situations in the past where we created a new binary. How 
> would we name them? Is it worth the trouble?
> Personally, I would just update the new version + the fixed affected packages 
> in one go, to reduce the breakage to a minimum.

... and generally, vendoring certain older revisions if needed to build always 
is at hand.


4096R/DF5182C8 (sten...@debian.org)

Pkg-go-maintainers mailing list

Reply via email to