From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,221c61113210e0ef
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.66.82.2 with SMTP id e2mr3454083pay.40.1343789444707;
        Tue, 31 Jul 2012 19:50:44 -0700 (PDT)
Path: 
 g9ni9635140pbo.0!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nrc-news.nrc.ca!goblin1!goblin.stu.neva.ru!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Newsgroups: comp.lang.ada
Subject: Re: astyle/cindent for Ada?
Date: Sat, 28 Jul 2012 00:46:21 +0200
Organization: A noiseless patient Spider
Message-ID: <87pq7gq0ua.fsf@ludovic-brenta.org>
References: <2df5566c-c219-4226-b41e-78ed47190bc4@googlegroups.com>
	<87txwtp074.fsf@ludovic-brenta.org>
	<b7f87eac-d4c2-4d6b-8cc0-623869e697e3@googlegroups.com>
	<9393e18c-212b-4dba-b2bc-4970800a8f25@googlegroups.com>
Mime-Version: 1.0
Injection-Info: mx04.eternal-september.org;
 posting-host="f640624b15764fd99855b8fb610f0ac2";
	logging-data="25358"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX1+qBxtJKffdA8Dt+Z2xhbVo"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Cancel-Lock: sha1:QMbJzwdnObAIp397zr2G7IbUrSE=
	sha1:oSJKxBTeraiEdYxW+MjSBNVfEwY=
Content-Type: text/plain; charset=us-ascii
Date: 2012-07-28T00:46:21+02:00
List-Id: <comp.lang.ada>

Patrick writes on comp.lang.ada:
> Hi Ludovic
>
> I would be the one to post the bug report only I have switch distros
> so many times I can't be sure what the set up was when I observed
> this.

A critical piece of information in any bug report is the *exact* version
of the gnatpp (i.e. of the package asis-programs, which contains gnatpp)
that produced the unexpected output.  So, please try to reproduce the
problem and use the Debian bug-reporting tools (i.e. reportbug) so it
gathers the critical information automatically and exactly.  Without
exact and complete information I cannot do anything.

The symptoms you describe remind me of http://bugs.debian.org/676338
(which BTW is an example of how properly to report a bug) but I cannot
be sure.

This bug is, of course, corrected in Debian.

-- 
Ludovic Brenta.