[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#720507: .dsc field for dgit

user debian-policy@packages.debian.org
severity 720507 wishlist
usertags 720507 normative issue

Le Thu, Aug 22, 2013 at 06:48:02PM +0100, Ian Jackson a écrit :
> I have been working on a new tool for integration between the Debian
> archive and git.  The best available description is probably its
> manpage:
>   http://www.chiark.greenend.org.uk/~ijackson/2013/dgit.html
> dgit uses a new field in .dsc files, which I have called
> Vcs-Dgit-Master.  Here is my proposed policy amendment to describe it.

Dear Ian,

thank you for your patch and for your work on dgit.  In light of the discussion
about how our infrastructure handles this field, I would like to wait for
further testing and adoption before adding it to the Policy.  Please do not
hesitate to ping us when you think it is time.

About the name, what does "Master" mean ?  Isn't that misleading if the
referenced commit is not on the master branch ?

About the specification of the commit hash: why is it not needed for a package
uploaded to a given suite, that the commit is reachable in refs/dgit/suite ?
Also, what kind of commits in dgit repository are not reachable in refs/dgit/* ?
I am asking because I wonder if the description is going too much in details.

Lastly, in case of the dgit repositories would move from the Alioth project
'dgit-repos' to somewhere else, could you propose a wording that is more
generic, and that is more explicit on what a 'dgit-repos' is ?

Have a nice day,

PS: off-topic question: do you have comments to make about the documentation
of Dpkg's triggers to the Policy ?

Charles Plessy
Tsurumi, Kanagawa, Japan

Reply to: