> 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".
Both SGTM; have .dscs ready or a package prepared? > 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. So on your game! > 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. Sounds fine here; I don't think we had to do transitional packages for other renames > Also I think I might need to ask the FTP masters to remove the > old binary packages once the changes have been uploaded. Yeah, I can take care of that on the backend too, just hit me up once it's fixed. > Tim. cheers, paul
signature.asc
Description: PGP signature
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
