On Tue, Sep 08, 2015 at 09:00:34AM +0200, Michael Stapelberg wrote: > > 1. ... just go ahead and update them? :-) > > Yes.
Yesish. Yes, you should absolutely update them, but you should also check all their reverse build dependencies to ensure that we don't cause FTBFSs. Yo, sECuRE - is RATT ready for team use? > > 2. Or should I first ask for permissions from the previous uploaders? > > You should at least let them know, but team policy is that we don’t > have such strict ownership. The packages are team-maintained for a > reason. Absolutely true. Just be careful of an upload before we know what might trigger FTBFSs -- upstreams in Goland seem to break API all the time, so we should be a bit careful in leau of versioning. > > 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 your advice! > > Thank you for your contributions :). +1! Cheers, Paul
signature.asc
Description: Digital signature
_______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
