[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#921449: marked as done (lintian: stop saying that GTK is misspelled)

Your message dated Fri, 6 Dec 2019 21:37:55 -0800
with message-id <CAFHYt5409KM7aZPeoX3DoOrXzEPt_O9HnijnAeBtdEFgAevdmQ@mail.gmail.com>
and subject line Re: Bug#921449: lintian: stop saying that GTK is misspelled
has caused the Debian Bug report #921449,
regarding lintian: stop saying that GTK is misspelled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
921449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921449
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: lintian
Version: 2.5.124
Severity: minor

GTK+ is now GTK so I suggest dropping these 2 lines:
https://salsa.debian.org/lintian/lintian/blob/master/data/spelling/corrections-case#L54-55

I don't really think it's worth complaining about GTK+ since I believe
GTK3 needs to still identify itself as GTK+.

References
----------------
https://gitlab.gnome.org/GNOME/gtk/issues/1439

Thanks,
Jeremy Bicha

--- End Message ---
--- Begin Message --- 
Hi Jeremy,

On Tue, Feb 5, 2019 at 9:03 AM Jeremy Bicha <jbicha@debian.org> wrote:
>
> GTK+ is now GTK so I suggest dropping these 2 lines:
> https://salsa.debian.org/lintian/lintian/blob/master/data/spelling/corrections-case#L54-55

This was fixed on the day you reported it, but the bug number was
bungled. Thus, the resolution was never recorded here. (The other bug
was an RFS.) The relevant commit was:

   https://salsa.debian.org/lintian/lintian/commit/c6108a6bd5c4d0b75188b99dd8ce188d07e24e0f

The commit removed only one line, and not both. Please re-open this
bug if that is an issue.

Kind regards,
Felix Lechner

--- End Message ---
Reply to: