[pkg-go] Package renames for clockwork and go-semver packages
Potter, Tim (HPE Linux Support)
timothy.potter at hpe.com
Tue May 10 01:27:40 UTC 2016
Hi everyone. I found a couple of dependency-related problems last week when attempting to
rebuild both Docker and Kubernetes in a Jessie environment.
The problems stem from both the golang-clockwork and golang-go-semver packages being
packaged in between the previous two packaging naming standards. The result is both
binary package names are non-standard and it's easy to mistype them. There were no transitional
packages were not made (by me BTW) way back in 2015 which further messes things up.
I'm proposing to rename the binary packages thusly:
golang-github-coreos-semver-dev -> golang-github-coreos-go-semver-dev as the package name
is "go-semver" and not just "semver".
golang-jonboulle-clockwork-dev -> golang-github-jonboulle-clockwork-dev as we are missing
the vendor name "github".
Luckily now is a good time to make this change as existing uploaded packages depend on the
old package name via a conditional dependency (oldname | newname) and so don't need changing.
There are a few cases where the RHS new name needs to be updated and I've checked in fixes for this
already.
I *think* this is all do-able without having to create any transitional packages but it would be
nice to get some feedback on this. Also I think I might need to ask the FTP masters to remove
the old binary packages once the changes have been uploaded.
Tim.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160510/98d95808/attachment.sig>
More information about the Pkg-go-maintainers
mailing list