On Sun, Oct 22, 2017 at 06:19:10PM -0700, Ross Vandegrift wrote:
> On Wed, Oct 18, 2017 at 07:22:45PM -0700, Sean Whitton wrote:
> > On Tue, Oct 17 2017, Ross Vandegrift wrote:
> >
> > > Package: debian-policy Version: 4.1.1.1 Severity: normal
> > >
> > > Section 4.4 explains quite a bit about
control: reassign -1 developers-reference
control: retitle -1 State intended audience of debian/changelog
Hello Ross,
On Sun, Oct 22 2017, Ross Vandegrift wrote:
> I have, it does, and that's a reasonable reluctance. But I don't see
> anything there that would tell a new contributor about the
On Wed, Oct 18, 2017 at 07:22:45PM -0700, Sean Whitton wrote:
> On Tue, Oct 17 2017, Ross Vandegrift wrote:
>
> > Package: debian-policy Version: 4.1.1.1 Severity: normal
> >
> > Section 4.4 explains quite a bit about debian/changelog, but doesn't
> > really explain its purpose.
>
> Have you
On Wed, Oct 18, 2017 at 08:48:28PM -0700, Russ Allbery wrote:
> Separate than the point that Policy could probably stand to say something
> a little more concrete about the purpose of debian/changelog, I suspect
> this came out of the recurring discussion of whether to include unreleased
>
Hello,
On Thu, Oct 19 2017, Russ Allbery wrote:
> My impression of discussion on debian-mentors over the past few years
> is that most of the people active in sponsoring have as a requirement
> that all changelogs from versions of a package that weren't uploaded
> to Debian be consolidated and
Sean Whitton writes:
> On Wed, Oct 18 2017, Russ Allbery wrote:
>> It's probably worth noting here that while debian-mentors has
>> converged to a very strong consensus that unreleased versions of
>> packages should not appear in debian/changelog, the consensus about
>>
Bill Allombert writes:
> What actually matter is that the .changes file include the relevant
> extract from the changelog and do not miss packaging change because they
> where listed in unreleased versions and dpkg-genchanges -v was not used
> properly.
Yes, indeed, that's
Hello Russ,
On Wed, Oct 18 2017, Russ Allbery wrote:
> It's probably worth noting here that while debian-mentors has
> converged to a very strong consensus that unreleased versions of
> packages should not appear in debian/changelog, the consensus about
> that in the broader project is nowhere
On Wed, Oct 18, 2017 at 08:48:28PM -0700, Russ Allbery wrote:
>
> Some people in debian-mentors will make very absolute statements about
> never including unreleased versions in debian/changelog and always
> consolidating versions, and will give the impression that literally
> everyone in Debian
Ross Vandegrift writes:
> Section 4.4 explains quite a bit about debian/changelog, but doesn't
> really explain its purpose. I took its purpose to be recording history
> and driving automation - which led to some mistakes that might've been
> avoided. During a recent thread
control: tag -1 +moreinfo
Hello Ross,
On Tue, Oct 17 2017, Ross Vandegrift wrote:
> Package: debian-policy Version: 4.1.1.1 Severity: normal
>
> Section 4.4 explains quite a bit about debian/changelog, but doesn't
> really explain its purpose.
Have you seen Developer's Reference 5.2? That
On Tue, 17 Oct 2017 at 23:06:29 -0700, Ross Vandegrift wrote:
> During a
> recent thread on mentors [1], I learned that the purpose is to provide a human
> readable list of changes between released versions of Debian.
Between released versions of the package in Debian, rather than versions
of
Package: debian-policy
Version: 4.1.1.1
Severity: normal
Section 4.4 explains quite a bit about debian/changelog, but doesn't really
explain its purpose. I took its purpose to be recording history and driving
automation - which led to some mistakes that might've been avoided. During a
recent
13 matches
Mail list logo