Your message dated Fri, 26 Oct 2018 19:52:03 +0200 with message-id <20181026175159.GA4810@mapreri.org> and subject line Re: Bug#892339: inkscape: Please use 'pkg-config' to find FreeType 2 has caused the Debian Bug report #892339, regarding inkscape: Please use 'pkg-config' to find FreeType 2 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.) -- 892339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892339 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: inkscape: Please use 'pkg-config' to find FreeType 2
- From: hugh.mcmaster@outlook.com
- Date: Thu, 08 Mar 2018 22:52:28 +1100
- Message-id: <E1etu60-0003sW-CO@sid.telstra.com.au>
Source: inkscape Severity: important Dear Maintainer, The next release of libfreetype6-dev will *not* ship `freetype-config', as the script has now been deprecated in favour of `pkg-config'. This is an upstream change: "Use of the `freetype-config' script to get compilation and linking options is deprecated since it doesn't support cross-compiling, among other deficiencies. Instead, you should use the `pkg-config' interface." [1] Please use `pkg-config' to detect the FreeType 2 headers and libraries in inkscape. If this bug is not resolved prior to the release of FreeType 2.9.1, your package may FTBFS. Thank you [1] http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0 a93839b52818abbfe9b4c8755b4aa0f5232063
--- End Message ---
--- Begin Message ---
- To: 892339-close@bugs.debian.org
- Subject: Re: Bug#892339: inkscape: Please use 'pkg-config' to find FreeType 2
- From: Mattia Rizzolo <mattia@debian.org>
- Date: Fri, 26 Oct 2018 19:52:03 +0200
- Message-id: <20181026175159.GA4810@mapreri.org>
- In-reply-to: <SLXP216MB035152B7F1682500445E8B84F2D30@SLXP216MB0351.KORP216.PROD.OUTLOOK.COM>
- References: <E1etu60-0003sW-CO@sid.telstra.com.au> <20180308160004.GC22618@mapreri.org> <E1etu60-0003sW-CO@sid.telstra.com.au> <SLXP216MB035152B7F1682500445E8B84F2D30@SLXP216MB0351.KORP216.PROD.OUTLOOK.COM>
On Mon, Mar 12, 2018 at 10:04:56AM +0000, Hugh McMaster wrote: > > I haven't looked deep, but I believe the inkscape is not affected: > > the version currently in debian contains a double build system > > autoconf+cmake: the autoconf one seems to be alling `freetype-config`, > > whereas cmake seems be doing something else (possibly pkg-config, or > > not); and we're using the cmake build system. > > FTR, the next major upstream release (0.93) will have only cmake. > > Thanks for the explanation. I confirm what I said. I've now tested building inkscape with the experimental version of freetype, and cmake found it. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-Attachment: signature.asc
Description: PGP signature
--- End Message ---