Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > Thanks again for your help. I've applied all suggested changes. > Interdiff and updated patch attached. Thanks, this has been applied for the next release. -- Russ Allbery (r...@debian.org) -- To UNSUBSCRIBE, email to d

Bug#654958: debian-policy: Document VCS fields.

Russ Allbery writes: > Jonathan Nieder writes: > >> How about this? > >> diff --git i/policy.sgml w/policy.sgml >> index 7d514921..58bde0bb 100644 >> --- i/policy.sgml >> +++ w/policy.sgml >> @@ -3766,8 +3766,9 @@ Checksums-Sha256: >> >>The field name identifies the

Bug#654958: debian-policy: Document VCS fields.

Ben Pfaff writes: > Is a hyphen desirable there? > http://en.wikipedia.org/wiki/Hyphen#Compound_modifiers says: > In the 19th century, it was common to hyphenate > adverb–adjective modifiers with the adverb ending in -ly. > However, this has become rare. For example, wholly owned >

Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > How about this? > diff --git i/policy.sgml w/policy.sgml > index 7d514921..58bde0bb 100644 > --- i/policy.sgml > +++ w/policy.sgml > @@ -3766,8 +3766,9 @@ Checksums-Sha256: > > The field name identifies the VCS. The field's value uses the

Bug#654958: debian-policy: Document VCS fields.

Hi Bernhard, Bernhard R. Link wrote: >> + In the case of Git, the value consists of a URL, optionally >> + followed by the word -b and the name of a branch in >> + the indicated repository, following the syntax of the >> + git clone command. If

Bug#654958: debian-policy: Document VCS fields.

> + > + Vcs-Arch, Vcs-Bzr (Bazaar), Vcs-Cvs, > + Vcs-Darcs, Vcs-Git, Vcs-Hg > + (Mercurial), Vcs-Mtn (Monotone), Vcs-Svn > + (Subversion) > + > + > + > + The field name identifies the VCS. Th

Bug#654958: debian-policy: Document VCS fields.

Hi! On Thu, 2012-07-12 at 22:51:12 -0500, Jonathan Nieder wrote: > Thanks again for your help. I've applied all suggested changes. > Interdiff and updated patch attached. Seconded. thanks, guillem signature.asc Description: Digital signature

Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > Thanks again for your help. I've applied all suggested changes. > Interdiff and updated patch attached. Looks good to me -- seconded. -- Russ Allbery (r...@debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ.

Bug#654958: debian-policy: Document VCS fields.

Russ Allbery wrote: > Maybe we should instead say something like: > > ...and should be sufficient to locate the repository used for > packaging. Ideally, it also locates the branch used for development > of new Debian packages. With s/new Debian packages/new versions of the Debian pa

Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > diff --git a/policy.sgml b/policy.sgml > index 52dbb26a..371123e1 100644 > --- a/policy.sgml > +++ b/policy.sgml > @@ -2631,6 +2631,7 @@ Package: libc6 > Build-Depends et > al >id="f-Standards-Version">Standards-Version > (recommended) >

Bug#654958: debian-policy: Document VCS fields.

Le Sun, Jul 08, 2012 at 08:19:12PM -0500, Jonathan Nieder a écrit : > > My feedback got no replies, so I can only assume that everyone was so > awestruck by the suggestions that they were lost for words. ... or assume holidays :) Thanks a lot for the revised patch. From my point of view, it is

Bug#654958: debian-policy: Document VCS fields.

Charles Plessy wrote: > Would the following patch be acceptable now ? My feedback got no replies, so I can only assume that everyone was so awestruck by the suggestions that they were lost for words. Here's an updated patch. Improvements welcome. Looking forward to your thoughts, Jonathan From

Bug#654958: debian-policy: Document VCS fields.

Hi Charles, Charles Plessy wrote: > Would the following patch be acceptable now ? Getting a lot closer. Some questions: [...] > +++ b/policy.sgml [...] > @@ -3737,6 +3739,42 @@ Checksums-Sha256: > details. > > > + > + > + Version Control System (VCS) fields

Bug#654958: debian-policy: Document VCS fields.

Le Wed, May 09, 2012 at 08:32:26PM +0200, Bernhard R. Link a écrit : > * Bernhard R. Link [120108 14:03]: > > * Russ Allbery [120107 20:42]: > > > "Bernhard R. Link" writes: > > > > Something that was only added to git after that discussion was already > > > > running for a while is git-clone's

Bug#654958: debian-policy: Document VCS fields.

* Bernhard R. Link [120108 14:03]: > * Russ Allbery [120107 20:42]: > > "Bernhard R. Link" writes: > > > Something that was only added to git after that discussion was already > > > running for a while is git-clone's -b. Sadly > > > > > Vcs-Git: git://git.eyrie.org/kerberos/webauth.git -b squeez

Bug#600745: Bug#654958: debian-policy: Document VCS fields.

On Sun, Jan 08, 2012 at 09:50:32AM -0800, Russ Allbery wrote: > Steve Langasek writes: > > > I object to policy specifying any Vcs-* fields in a way that does not > > uniquely identify a Debian packaging branch. Running debcheckout for a > > package only to then have to guess at random which of

Bug#654958: debian-policy: Document VCS fields.

Steve Langasek wrote: > Yes. By the nature of svn, the Vcs-Svn URI always unambiguously refers to a > single branch ("trunk" is a branch). FWIW, I would be happy to see at least that documented. (It would provide a reason to propose this change in the eglibc package. :)) -- To UNSUBSCRIBE,

Bug#600745: Bug#654958: debian-policy: Document VCS fields.

Steve Langasek writes: > I object to policy specifying any Vcs-* fields in a way that does not > uniquely identify a Debian packaging branch. Running debcheckout for a > package only to then have to guess at random which of 20 branches is the > one containing the packaging I care about[1] is non

Bug#654958: debian-policy: Document VCS fields.

Charles Plessy wrote: > For Git, as discussed in this thread, it is not possible to specify the branch > in the URL. I hope that it will be possible one day Git URLs deliberately represent a repository, not a branch. That is because branches and repositories for a package are simply different n

Bug#654958: debian-policy: Document VCS fields.

* Russ Allbery [120107 20:42]: > "Bernhard R. Link" writes: > > Something that was only added to git after that discussion was already > > running for a while is git-clone's -b. Sadly > > > Vcs-Git: git://git.eyrie.org/kerberos/webauth.git -b squeeze > > > does not work as debcheckout is not word

Bug#654958: debian-policy: Document VCS fields.

On Sun, Jan 08, 2012 at 09:55:48PM +0900, Charles Plessy wrote: > From what I see in Sid, only 37 Subversion URLs contain the string ‘branch’. > This matches well with the practice I know in the Debian Med and Debian > Science teams, where we indicate the trunk. Yes. By the nature of svn, the Vc

Bug#654958: debian-policy: Document VCS fields.

Hi all, this is a grouped answer for Jonathan, Russ and Steve. >From what I see in Sid, only 37 Subversion URLs contain the string ‘branch’. This matches well with the practice I know in the Debian Med and Debian Science teams, where we indicate the trunk. For Git, as discussed in this thread, i

Bug#600745: Bug#654958: debian-policy: Document VCS fields.

On Sat, Jan 07, 2012 at 08:46:47AM -0800, Russ Allbery wrote: > > I wonder if something like > > Vcs-Git: git://git.eyrie.org/kerberos/webauth.git squeeze > > could be made to work. > My understanding was that the debcheckout developers were not enthused > about adding a syntax that Git upst

Bug#654958: debian-policy: Document VCS fields.

Russ Allbery wrote: > Maybe we should just > document them as they are and be explicit about the limitations, saying > things like: > > The information in the Vcs-* header should be sufficient to locate the > repository used for packaging and

Bug#654958: debian-policy: Document VCS fields.

"Bernhard R. Link" writes: > Something that was only added to git after that discussion was already > running for a while is git-clone's -b. Sadly > Vcs-Git: git://git.eyrie.org/kerberos/webauth.git -b squeeze > does not work as debcheckout is not word splitting the argument, but the > error me

Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > Russ Allbery wrote: >> Also, for a Git repository, what do you do if the Debian packaging isn't >> on the master branch? For example, for packages for which I'm also >> upstream, I do upstream development on the master branch and Debian >> packaging on a separate debian

Bug#654958: debian-policy: Document VCS fields.

Jonathan Nieder writes: > If I keep my sources in svn, should I give a URL to the toplevel of the > repository (which is what one passes to "git svn clone -s" and allows > access to all branches) or one particular branch? For debcheckout to work properly, you want to specify a branch. > If a br

Bug#654958: debian-policy: Document VCS fields.

Hi Charles, Charles Plessy wrote: > + > + Vcs-arch, Vcs-bzr (Bazaar), Vcs-cvs, > + Vcs-darcs, Vcs-git, Vcs-hg > + (Mercurial), Vcs-mtn (Monotone), Vcs-svn > + (Subversion) > + > + > + > + S

Bug#654958: debian-policy: Document VCS fields.

Package: debian-policy Version: 3.9.2.0 Severity: normal Dear all, now that thousands of pakcages use the VCS fields, I think that it is time to document them in the Policy. Please see the attached patch as a starting point. The Developers Reference already documents the VCS fields, and discuss