| 2015-02-07 12:21:40 |
Alex Valavanis |
bug |
|
|
added bug |
| 2015-02-07 12:22:17 |
Alex Valavanis |
tags |
|
build pdf |
|
| 2015-02-07 12:24:43 |
Alex Valavanis |
inkscape: importance |
Undecided |
Medium |
|
| 2015-02-07 12:24:45 |
Alex Valavanis |
inkscape: status |
New |
Triaged |
|
| 2015-02-07 12:25:43 |
Alex Valavanis |
inkscape: assignee |
|
Alex Valavanis (valavanisalex) |
|
| 2015-02-07 14:31:01 |
Alex Valavanis |
bug task added |
|
inkscape-devlibs |
|
| 2015-02-07 14:31:14 |
Alex Valavanis |
inkscape-devlibs: importance |
Undecided |
Wishlist |
|
| 2015-02-07 14:31:21 |
Alex Valavanis |
inkscape-devlibs: status |
New |
Triaged |
|
| 2015-02-12 12:12:35 |
Alex Valavanis |
description |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3
3. Get rid of the POPPLER_NEW_GFXFONT test
4. Upgrade Devlibs Poppler version to something >= 0.18.4
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
|
| 2016-01-06 10:01:54 |
jazzynico |
inkscape-devlibs: status |
Triaged |
In Progress |
|
| 2016-01-06 10:01:54 |
jazzynico |
inkscape-devlibs: assignee |
|
jazzynico (jazzynico) |
|
| 2016-01-08 08:55:42 |
jazzynico |
inkscape-devlibs: status |
In Progress |
Fix Released |
|
| 2016-01-11 13:54:47 |
Alex Valavanis |
description |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
|
| 2016-01-11 14:20:35 |
Alex Valavanis |
description |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* <s>POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3</s>
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
|
| 2016-01-11 14:21:09 |
Alex Valavanis |
description |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* <s>POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3</s>
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* [DONE] POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* [DONE] POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
|
| 2016-01-11 14:29:48 |
Alex Valavanis |
description |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* [DONE] POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* [DONE] POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
TL;DR: I'd like to bump our Poppler dependency to > 18.4 and tidy up a lot of code. I'll go ahead in the next couple of days, if no objections.
We currently have over 100 lines in configure.ac dedicated just to checking for libpoppler. This creates a maintenance burden, and results in fairly messy conditional builds.
The first problem is that we don't check for the libpoppler private headers (We shouldn't be using these, but that's a separate issue!). This means that the configure script will happily let the user build Inkscape even though failure is inevitable. Instead, the script should output an error message and exit.
Second, we have a lot of output #define variable. Some of these can probably go away:
* HAVE_POPPLER: Use libpoppler for direct PDF import
* HAVE_POPPLER_CAIRO: Use libpoppler-cairo for rendering PDF preview
* HAVE_POPPLER_GLIB: Use libpoppler-glib and Cairo-SVG for PDF import
* [DONE] POPPLER_NEW_GFXFONT: Use GfxFont from Poppler >= 0.8.3
* POPPLER_NEW_ERRORAPI: Use new error API from Poppler >= 0.20.0
* [DONE] POPPLER_NEW_COLOR_SPACE_API: Use color space API from Poppler >= 0.12.2
* POPPLER_EVEN_NEWER_COLOR_SPACE_API: Use even newer color space API from Poppler >= 0.26.0
* POPPLER_EVEN_NEWER_NEW_COLOR_SPACE_API: Use even newer new color space API from Poppler >= 0.29.0
* [DONE] POPPLER_NEW_GFXPATCH: GfxPatch no longer uses GfxColor in >= 0.15.1
Our Tracking Dependencies page [1] shows that even the oldest of our supported build environments can cope without some of these (Devlibs = poppler-0.12.1, Debian Wheezy = poppler-0.18.4).
Can I suggest the following:
1. Add a check for the necessary Poppler private headers
2. Bump our dependency level to Poppler >= 0.8.3 [done: lp:inkscape r13917]
3. Get rid of the POPPLER_NEW_GFXFONT test [done: lp:inkscape r13917]
4. Upgrade Devlibs Poppler version to something >= 0.18.4 [done: lp:inkscape-devlibs r56, lp:inkscape r14566, lp:inkscape/0.91.x r13853]
5. Bump our dependency level to Poppler >= 0.18.4
6. Kill the POPPLER_NEW_COLOR_SPACE_API and and POPPLER_NEW_GFXPATCH tests
[1] http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies |
|
| 2016-01-11 14:40:41 |
Launchpad Janitor |
branch linked |
|
lp:inkscape |
|
| 2016-01-11 14:40:44 |
Alex Valavanis |
inkscape: status |
Triaged |
Fix Committed |
|
| 2016-01-11 14:40:49 |
Alex Valavanis |
inkscape: milestone |
|
0.92 |
|
| 2017-01-10 19:08:58 |
Bryce Harrington |
inkscape: status |
Fix Committed |
Fix Released |
|
