Sean Whitton writes ("Bug#904608: Support specifying upstream VCS location in
debian/control"):
> No-one needs to do that extra work anytime soon. Policy lags best
> practices. The fact that debian/upstream/metadata is already being used
> to store a URI to the upstream rep
Hi!
On Wed, 2018-07-25 at 18:20:52 -0700, Jonathan Nieder wrote:
> Sean Whitton wrote:
> > On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote:
> >> Some tools, like git-buildpackage, can support merging an upstream's
> >> version history into Debian packaging repositories. This enables more
>
control: retitle -1 Include upstream metadata spec in Policy
control: tag -1 +moreinfo
Hello,
On Thu 26 Jul 2018 at 09:21AM +0100, Iain Lane wrote:
> However, I'm not very keen on the extra work that would be required to
> transfer that wiki page into policy as opposed to specifying an extra
>
On Wed, 25 Jul 2018 18:20:52 -0700, Jonathan Nieder wrote:
> > In fact, there is: the Repository field in debian/upstream/metadata.[1]
>
> Neat!
>
> I would have expected to find this information in debian/copyright. The
> Source field there sometimes names an upstream VCS but isn't required
On Thu, Jul 26, 2018 at 09:05:33AM +0800, Sean Whitton wrote:
> control: tag -1 +moreinfo
> Even if we did want to add this to d/control files, we would want to see
> it already used in d/control files in the archive before documenting
> that in Policy.
Thanks Sean. This is an interesting
Control: retitle -1 Specify a canonical location for upstream's VCS to be
declared
On Wed, Jul 25, 2018 at 06:20:52PM -0700, Jonathan Nieder wrote:
> My feeling is that it doesn't belong in debian/control.
>
> The debian/control file is the source for control fields that appear
> in the binary
Hello,
On Wed 25 Jul 2018 at 06:20PM -0700, Jonathan Nieder wrote:
> I would have expected to find this information in debian/copyright. The
> Source field there sometimes names an upstream VCS but isn't required to
> do so; I'd be in favor of some tightening of the requirements in
>
Hi,
Sean Whitton wrote:
> On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote:
>> Some tools, like git-buildpackage, can support merging an upstream's
>> version history into Debian packaging repositories. This enables more
>> rich usage of (D)VCS when packaging - for example `git blame' works
control: tag -1 +moreinfo
Hello Iain,
On Wed 25 Jul 2018 at 05:14PM +0100, Iain Lane wrote:
> Some tools, like git-buildpackage, can support merging an upstream's
> version history into Debian packaging repositories. This enables more
> rich usage of (D)VCS when packaging - for example `git
Package: debian-policy
Version: 4.1.5.0
Severity: normal
Hi,
Some tools, like git-buildpackage, can support merging an upstream's
version history into Debian packaging repositories. This enables more
rich usage of (D)VCS when packaging - for example `git blame' works
properly.
Currently there's
10 matches
Mail list logo
