On Thu, Jan 04, 2018 at 05:19:26PM +0100, Mattia Rizzolo wrote: > On Thu, Jan 04, 2018 at 04:01:18PM +0000, Holger Levsen wrote: > > > Personally, in this case I would say you need to change two things: > > > 1) edit the remote repository configuration so HEAD points to the debian > > > branch done this now. > > > 2) change Vcs-Git of the version in experimental by adding '-b debian-experimental' done this in git now, not yet uploaded… > > hm. how "personally" is that? will my simple suggestion also by > > sufficient? why do you suggest what you suggest? > Your suggestion is definitly enough for all automated tools (and for > users using debcheckout). Thanks for confirming. > > > (but it should be pointing to 'debian', really). > > why oh why? > > Because that way people running > git clone alioth:/git/collab-maint/munin.git > like me (I'm even more evil, I'd do `git clone cm:munin`) will then get > the packaging branch without further specifying flags for branches and > stuff. ah! & thanks, this made me point HEAD to debian! :) > Quoting from the Policy about Vcs-*: > | The field’s value uses the version control system’s conventional > | syntax for describing repository locations and should be sufficient to > | locate the repository used for packaging. Ideally, it also locates > | the branch used for development of new versions of the Debian package. > That means that the Vcs-* fields should ideally point to the packaging > branch. also thanks for pointing this out. > I like to take this one step further, as really what's in > alioth is all about debian packaging, the default branches IMHO should > be a packaging branch. agreed. > > to me its very simple: if there is a debian branch, this is the branch > > for debian packaging. if there isnt, the debian stuff is probably in the > > master branch… > > Right, probably everybody if what they look for is not in the default > branch, they have a look around at the available branches and can > easily figure it out. But really there ought to be no guesswork > involved at all... I like automated guesswork… not human guesswork. > But yes, specifying -b in Vcs-Git is really all that's expected (and it > will definitly make vcswatch happied :)) hm, so I will do this now in addition to having made HEAD point to debian. And then I'll wait two more days til 2.0.34-2 is in Buster and then upload -3 to see if everything is working as it shall :) -- cheers, Holger
Attachment:
signature.asc
Description: PGP signature