A couple of patches have been submitted moving ghostscript from 9.20 to 9.21. Should I submit a new one fixing the CUPSCONFIG issue, or is the one from Fan Xin being considered instead?
Joe From: Slater, Joseph Sent: Thursday, May 25, 2017 2:54 PM To: Slater, Joseph; BURTON, ROSS Cc: OE-core Subject: RE: [OE-core] [oe-core][PATCH 1/1] ghostscript: move to version 9.21 Setting CUPSCONFIG as an argument to configure works. I’ve filed a bug with ghostscript to See if they confirm the issue. I could modify my 9.21 patch to set CUPSCONFIG for target builds and Things should be back to where they were. Joe From: openembedded-core-boun...@lists.openembedded.org<mailto:openembedded-core-boun...@lists.openembedded.org> [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Slater, Joseph Sent: Thursday, May 25, 2017 12:44 PM To: BURTON, ROSS Cc: OE-core Subject: Re: [OE-core] [oe-core][PATCH 1/1] ghostscript: move to version 9.21 I don’t know if it’s intentional, but it does seem to be a feature of 9.21 that cups support Is never built even though configure finds cups.h and cups-config. In trying to compare build logs, I see a new variable called BUILD_CUPSCONFIG which is Set to what the old CUPSCONFIG variable was. In the new log, CUPSCONFIG is null. Joe From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, May 25, 2017 5:50 AM To: Slater, Joseph Cc: OE-core Subject: Re: [OE-core] [oe-core][PATCH 1/1] ghostscript: move to version 9.21 On 24 May 2017 at 18:39, Joe Slater <jsla...@windriver.com<mailto:jsla...@windriver.com>> wrote: Eliminate CVE patches that are now in source. Add CVE-2017-7975 patch. packages/corei7-64-poky-linux/ghostscript/ghostscript: RDEPENDS: removed all items "cups-libimage (['>= 2.2.2']) cups-lib (['>= 2.2.2'])" Is that intentional? Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
