[pkg-go] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?
foka at debian.org
Wed Sep 9 00:05:45 UTC 2015
Thank you for your reply!
On Tue, Sep 8, 2015 at 1:00 AM, Michael Stapelberg
<stapelberg at debian.org> wrote:
> On Tue, Sep 8, 2015 at 8:53 AM, Anthony Fok <foka at debian.org> wrote:
>> 3. Or should I create new packages like golang-github-russross-blackfriday
>> for the cutting-edge version, and leave golang-blackfriday
>> as the stable 1.2 version?
> No, but you should rename the existing packages to the proper name.
> See other recently uploaded packages for examples on how to do that
> with regards to Breaks/Replaces if you’re unsure about that.
Thank you for this very important note. I took some time to examine existing
packages (basically git cloned 237 Go packages and grep'd for ^Replaces: etc.)
and noticed slight discrepancies. Now, regarding the renaming:
1. Rename the binary -dev package
2. Rename the source package in debian/control (and hence orig.tar.xx too)
3. Rename the git repository too, i.e. "ssh git.debian.org",
"cd /git/pkg-go/packages", then "mv old-name.git new-name.git"
Should I just do #1? (e.g. golang-gocolorize, a new package)
Or just #1 and #2? (e.g. golang-golang-x-net-dev)
Or all three? (e.g. golang-github-gorilla-mux)
And, should I use Breaks/Replaces/Provides with transitional package
(e.g. golang-golang-x-net-dev) instead of Conflicts/Replaces/Provides
without transitional package (e.g. golang-github-gorilla-mux)?
Sorry for sounding pedantic, but as I am still pretty new to this
and will be upgrading/migrating at least a handful of Go packages,
I would like to know the best way before I dive all in.
More information about the Pkg-go-maintainers