> AFAICT, this leads to "put whatever you want within a changelog entry,
> so long as it doesn't cause significant annoyance, because no program
> can expect to read it".
Don't forget the existence of package libparse-debianchangelog-perl (and
of dpkg-parsechangelog) which do seem to read and inte
James Westby <[EMAIL PROTECTED]> writes:
> As the ability to provide non-standard changelog parsers doesn't
> seem to be used much, would it be a good idea to make it mandatory
> to use the standard format, and at the same time retire any
> pre-standard entries to debian/changelog.old or similar?
On Tue, 2008-05-13 at 16:58 +0200, Sandro Tosi wrote:
> python-debian states that can parse "debian/changelog": maybe you can
> explore how it works, and if it parses names too.
No, it doesn't, it just uses the two space rule and lumps all the
changes up as just a group of lines without trying t
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> Nearly all of the changelog is currently not machine-parsable, with
> notable exclusion of the first and last line (-- author), and the
> closes: statements. Everything else, like descriptions of files
> changed, bugs fixed, translations updated, rele
Thijs, Goswin: Please follow the Debian mailing list code of conduct
http://www.debian.org/MailingLists#codeofconduct>, in particular
please don't send me copies of messages also sent to the list.
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> Nearly all of the changelog is currently not machine-p
Ben Finney <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>
>> I don't know if it's worth being more formal here in Policy or not.
>> It might be more of a devref thing.
>
> I'm less interested in strictness in Policy than I am in finding out
> how this is *specified* for a
On Tue, May 13, 2008 at 4:35 PM, Thijs Kinkhorst <[EMAIL PROTECTED]> wrote:
> Ok, so to answer your question: the information was until now only ever
> intended to be human-readable.
python-debian states that can parse "debian/changelog": maybe you can
explore how it works, and if it parses name
On Tuesday 13 May 2008 16:28, Ben Finney wrote:
> All the answers I've had so far indicate that there *is* no
> specification for developer names within a changelog entry, and that
> any format at all is allowed so long as the loose definition in Policy
> is followed.
>
> My issue with that is that
Ben Finney <[EMAIL PROTECTED]> writes:
> Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
>
> > Maybe you can specify what problem you are trying to solve.
>
> That's a fair question.
And I didn't really answer it directly. Here's another try:
I'm trying to know that what I put into the changelog i
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> Maybe you can specify what problem you are trying to solve.
That's a fair question.
Thibaut Paumard <[EMAIL PROTECTED]> writes:
> Le 13 mai 08 à 13:24, Ben Finney a écrit :
> > I'm less interested in strictness in Policy than I am in finding
> > ou
On Tuesday 13 May 2008 13:24, Ben Finney wrote:
> I'm less interested in strictness in Policy than I am in finding out
> how this is *specified* for all consumers, rather than merely
> *implemented* in specific programs.
Maybe you can specify what problem you are trying to solve.
Thijs
--
To
Hi,
Le 13 mai 08 à 13:24, Ben Finney a écrit :
Russ Allbery <[EMAIL PROTECTED]> writes:
I don't know if it's worth being more formal here in Policy or not.
It might be more of a devref thing.
I'm less interested in strictness in Policy than I am in finding out
how this is *specified* for al
Russ Allbery <[EMAIL PROTECTED]> writes:
> I don't know if it's worth being more formal here in Policy or not.
> It might be more of a devref thing.
I'm less interested in strictness in Policy than I am in finding out
how this is *specified* for all consumers, rather than merely
*implemented* in
Ben Finney <[EMAIL PROTECTED]> writes:
> Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
>> I know of no special meaning that dpkg assigns to those names, as far
>> as I know it just treats them like any other changelog line.
> Yet they don't conform to the policy specification, so I'm wondering
> wh
Thijs Kinkhorst <[EMAIL PROTECTED]> writes:
> On Monday 12 May 2008 06:17, Ben Finney wrote:
> > The Policy section above is silent on this extension to the
> > format, though I've seen Joey Hess discussing it in the past. I
> > also know that 'debchange' can produce it, and 'dpkg' can consume
> >
On Monday 12 May 2008 06:17, Ben Finney wrote:
> In recent years I've seen entries in 'debian/changelog' that are
> broken up into "sections" by developer name. I'm referring to entries
> like this:
> The Policy section above is silent on this extension to the format,
> though I've seen Joey Hess
Howdy all,
Policy §4.4, "Debian changelog", details the expected changelog format
http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog>.
It defines entries in the following form:
=
package (version) distribution(s); urgency=urgency
[optional blank line(s), stripp
17 matches
Mail list logo
