On Sat, Jun 27, 2015 at 1:09 AM, Potter, Tim (Cloud Services) < [email protected]> wrote:
> On 23 Jun 2015, at 5:34 pm, Michael Stapelberg <[email protected]> > wrote: > > > > Sorry for the late reply. In the meantime, we’ve changed the library > naming conventions in http://pkg-go.alioth.debian.org/packaging.html, so > could you please adjust the package names? > > > > Let me know when you want me to take another look. > > OK I’m all done with renaming for packages that have not been uploaded > yet. Could you take a look? I’ve found some non-determinism in one of the > tests for goini so that and it’s antecedent globalconf can’t be uploaded > yet. > > golang-goini -> golang-github-glacjay-goini > Uploaded. > golang-globalconf -> golang-github-rakyll-globalconf > Depends on goini, so I can’t upload it yet. > golang-go-uuid -> golang-github-pborman-uuid > This one still has export DH_GOPKG := code.google.com/p/go-uuid/uuid in its debian/rules. Is that an oversight? In debian/{control,copyright}, you use https://github.com/pborman/uuid > > Should I rename golang-go-semver and golang-clockwork? They’re in testing > but aren’t dependencies of any other packages yet so now would be a good > time to re-upload them with new names I think. > I’ll deal with them later, ideally in an automated fashion. Currently, the first renamed package is still in NEW, but once it’s through and hence has validated our strategy, we can come up with a concrete plan. Are there any other not-yet-uploaded Go packages you want me to take a look at? -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
