On Mon, Feb 13, 2017 at 01:55:24PM +0200, Kyle Robbertze wrote:
> * Package name: fonts-sansation
> Version : 1.31
> Upstream Author : Berd Montag
> * URL : http://www.dafont.com/sansation.font
> * License : OFL-1.1
I don't see any mention of the OFL-1.1 for t
Simon McVittie writes ("Re: changelog practice, unfinalised vs UNRELEASED vs
~version"):
> If I'm understanding correctly, your motivation to do so is that you
> have a strong belief that building a Debian source package with `debuild`
> or similar, directly from a VCS checkout, should always work
Simon McVittie writes ("Re: changelog practice, unfinalised vs UNRELEASED vs
~version"):
> On Mon, 13 Feb 2017 at 09:42:32 +1100, Ben Finney wrote:
> > I don't see how this complaint is any different from the need to merge,
> > for example, changes to API documentation and test cases that accompan
Sean Whitton writes ("Re: changelog practice, unfinalised vs UNRELEASED vs
~version"):
> On Sun, Feb 12, 2017 at 12:48:35PM +, Ian Jackson wrote:
> > Q1. Should the suite in the changelog entry be UNRELEASED,
> > or the suite at which the vcs branch is targeted ?
> > [...]
> > Q1: Replacin
Wookey writes ("Re: changelog practice, unfinalised vs UNRELEASED vs ~version"):
> I'd be happier if I didn't have to deal with 'UNRELEASED' at all
> unless I actually wanted to, so I'm not at all keen on your suggestion
> of making it mandatory.
Well, tools can be configured, too. If my UNRELEAS
5 matches
Mail list logo
