Re: debian/upstream/metadata: next steps

2020-08-16 Thread Jelmer Vernooij
On Sun, Aug 16, 2020 at 02:17:13PM +0200, Mattia Rizzolo wrote: > On Sat, Aug 15, 2020 at 01:04:35AM +, Paul Wise wrote: > > I wonder if storing metadata (including Homepage, debian/watch, > > debian/upstream/*) about the upstream project in the Debian source > > package is the wrong approach.

Re: debian/upstream/metadata: next steps

2020-08-16 Thread Mattia Rizzolo
On Sat, Aug 15, 2020 at 01:04:35AM +, Paul Wise wrote: > I wonder if storing metadata (including Homepage, debian/watch, > debian/upstream/*) about the upstream project in the Debian source > package is the wrong approach. Upstream metadata can change without > any need for the Debian source

Re: debian/upstream/metadata: next steps

2020-08-14 Thread Charles Plessy
> On Fri, Aug 14, 2020 at 4:37 PM Jelmer Vernooij wrote: > > > Would it make sense to standardize the current proposal as DEP-12, perhaps > > with > > a limited set of uncontroversial and widely used fields? Le Sat, Aug 15, 2020 at 01:04:35AM +, Paul Wise a écrit : > > I wonder if storing

Re: debian/upstream/metadata: next steps

2020-08-14 Thread Paul Wise
On Fri, Aug 14, 2020 at 4:37 PM Jelmer Vernooij wrote: > Would it make sense to standardize the current proposal as DEP-12, perhaps > with > a limited set of uncontroversial and widely used fields? I wonder if storing metadata (including Homepage, debian/watch, debian/upstream/*) about the

debian/upstream/metadata: next steps

2020-08-14 Thread Jelmer Vernooij
uot; lives in debian/control and rather than DEP-12. * as discussed previously, Contact and Name live in debian/copyright rather than debian/upstream/metadata Next Steps == Would it make sense to standardize the current proposal as DEP-12, perhaps with a limited set of uncontroversial