On Wed, May 07, 2008 at 06:41:05PM +0200, Enrico Tröger wrote:
> On Wed, 7 May 2008 15:52:20 +0100, David <[EMAIL PROTECTED]>
> wrote:
> > On the other hand, I would suggest the upload of a new revision to
> > prevent the bug from affecting sid users that have not upgraded geany
> > yet, and before this version of geany migrates to testing.
With this grave (IMO overinflated severity) bug Geany won't migrate to
testing, so don't worry.
> Ok, this is up to Damián if he wants to add some patches or anything for
> the Debian package.
> But I don't think we will release anything new upstream because of this.
Ok, so the best I can think of is a note in NEWS.Debian that would be
displayed when the package is installing. This wouldn't fix the bug but
at least would document it. Besides, this should be sufficient to avoid
frustration at least in self admined environments.
> > > Unfortunately, I missed to note
> > > that in the release announcement, not sure if it would have changed
> > > anything.
> >
> > I am not sure about the effectiveness of this. Nobody reads the
> > release notes, because it is actually impossible because of the
> > limitation of 24 hours per day :-)
>
> Yes but if I had done so I simply could say: read the release notes,
> there were a warning ;-).
So, David, what do you think about this proposal? Also, now that we
know it only affect users with custom build commands, do you think the
bug should still be grave, and therefore avoid Geany shipping in Lenny
as is?
--
Damián Viano(Des) ¯ ¯ - _ _ - ¯ ¯
GPG: 0x6EB95A6F Debian ¯-_GNU_-¯ Linux
Web: http://damianv.com.ar/ ¯-¯
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
