Hi,
On Thu, Mar 07, 2024 at 07:20:11PM +0100, Volker Schlecht wrote:
> Updates print/ghostscript/gnu to latest release 10.03.0
>
> This is marked as a security release, but the only documented vulnerability
> affects builds with tesseract enabled. In our port we disable it, so we seem
> to be
Updates print/ghostscript/gnu to latest release 10.03.0
This is marked as a security release, but the only documented vulnerability
affects builds with tesseract enabled. In our port we disable it, so we seem
to be unaffected.
https://ghostscript.readthedocs.io/en/gs10.03.0/News.html
Built and
Not intended as a ping, but updating the diff to use SITES rather than
MASTER_SITES.
On 9/14/23 19:54, Volker Schlecht wrote:
Ghostscript just released version 10.02.0
The major change is the removal of the old PDF interpreter.
The new one has been the default since 10.0.0 and the possibility
Ghostscript just released version 10.02.0
The major change is the removal of the old PDF interpreter.
The new one has been the default since 10.0.0 and the possibility to
fall back to the old PDF interpreter is gone since 10.01.0.
I'm not aware that this caused any trouble, so I don't expect
ghostscript was just released as 10.01.2
No named security content (yet), but this commit is pretty explicit:
https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=9af4197bdccd4b65ed35a8ad2be075c3de2f0555
Overall, the diff is small and seems to be centered around getting the
fix mentioned
Pinging again, since I just got aware of this CVE:
https://nvd.nist.gov/vuln/detail/CVE-2023-28879
The patch should apply to -stable and work there just
as well.
On 4/8/23 11:24, Volker Schlecht wrote:
Ping
On 3/31/23 19:37, Volker Schlecht wrote:
Update ghostscript to the latest release
Ping
On 3/31/23 19:37, Volker Schlecht wrote:
Update ghostscript to the latest release 10.01.1
Lots of changes, most of which are considered bugfixes.
This release deprecates the old PDF interpreter (the new
one was already default in 10.0.0).
Other changes:
* Remove workaround to handle
Update ghostscript to the latest release 10.01.1
Lots of changes, most of which are considered bugfixes.
This release deprecates the old PDF interpreter (the new
one was already default in 10.0.0).
Other changes:
* Remove workaround to handle different version string
formats - not needed
bowser pointed out (thanks!) that I forgot to update MASTER_SITES
when working around the version confusion (10.00.0 and 10.0.0 are used
inconsistently). Fix attached.
On 10/4/22 16:16, Volker Schlecht wrote:
Here's the update to ghostscript 10.0 with the version bump to the
shared
Here's the update to ghostscript 10.0 with the version bump to the
shared lib.Index: Makefile
===
RCS file: /cvs/ports/print/ghostscript/gnu/Makefile,v
retrieving revision 1.124
diff -u -p -r1.124 Makefile
--- Makefile 3 Jul 2022
Since there's no documented security content, there's probably no harm
in waiting until after 7.2 with that one if the update is deemed too
risky.
It looks to me like a lot of dynamic exports have been removed. I think
we should bump the major shared lib version.
Post 7.2 please
Fair
On 2022/09/23 12:06, Rafael Sadowski wrote:
> On Thu Sep 22, 2022 at 08:32:46PM +0200, Volker Schlecht wrote:
> > And now also with update-patches ...
> >
> > On 9/22/22 20:26, Volker Schlecht wrote:
> > > Here's an update to ghostscript 10.0.0
> > > Unfortunately there seems to be a bit of
On Thu Sep 22, 2022 at 08:32:46PM +0200, Volker Schlecht wrote:
> And now also with update-patches ...
>
> On 9/22/22 20:26, Volker Schlecht wrote:
> > Here's an update to ghostscript 10.0.0
> > Unfortunately there seems to be a bit of confusion whether the version
> > is 10.0.0 or 10.00.0, so we
And now also with update-patches ...
On 9/22/22 20:26, Volker Schlecht wrote:
Here's an update to ghostscript 10.0.0
Unfortunately there seems to be a bit of confusion whether the version
is 10.0.0 or 10.00.0, so we need some gymnastics to not break PLIST
substitution.
Since there's no
Here's an update to ghostscript 10.0.0
Unfortunately there seems to be a bit of confusion whether the version
is 10.0.0 or 10.00.0, so we need some gymnastics to not break PLIST
substitution.
Since there's no documented security content, there's probably no harm
in waiting until after 7.2
On 2022/04/13 12:57, Volker Schlecht wrote:
>
>
> On 4/13/22 12:30, Stuart Henderson wrote:
> > That said, I don't think it is necessary to include a pkg-readme for
> > this at all.
>
> Fair enough, here's the patch without pkg/README for completeness' sake.
Thanks, builds went OK so I've
On 2022/04/13 12:05, Volker Schlecht wrote:
> This updates ghostscript to 9.56.1
There is a standard format which should be used for pkg-readme files.
That said, I don't think it is necessary to include a pkg-readme for
this at all.
The change is clearly mentioned in upstream's release notes and
Hi,
On 1/25/22 20:09, Matthias Kilian wrote:
Everything looked ok for me. Thanks for working on the update. If
there are no complaints from other people, I'll commit it later
this week.
Ok, cool!
Do you still want to take maintainership? Then I'll
adjust MAINTAINER accordingly.
Sure,
Hi,
On Mon, Jan 24, 2022 at 07:19:42PM +0100, Matthias Kilian wrote:
> On Mon, Jan 24, 2022 at 05:56:21PM +0100, Volker Schlecht wrote:
> > Sorry to bother you about it, but did you get around to having a look at the
> > patch?
>
> Looks good so far, I also ran dpb -uR to rebuild any packages
Hi, and sorry for the delay,
On Mon, Jan 24, 2022 at 05:56:21PM +0100, Volker Schlecht wrote:
> Sorry to bother you about it, but did you get around to having a look at the
> patch?
Looks good so far, I also ran dpb -uR to rebuild any packages depending
on it, without any problems.
I'll do some
Sorry to bother you about it, but did you get around to having a look at
the patch?
On 1/17/22 20:51, Matthias Kilian wrote:
Hi,
On Sun, Jan 16, 2022 at 05:12:25PM +0100, Volker Schlecht wrote:
Update with Makefile in the same order as the current port, I hope this
makes reviewing easier.
Hi,
On Sun, Jan 16, 2022 at 05:12:25PM +0100, Volker Schlecht wrote:
> Update with Makefile in the same order as the current port, I hope this
> makes reviewing easier.
Thanks! I'll have a look and do some tests during this week.
Ciao,
Kili
> Index: Makefile
>
On Mon, Jan 17, 2022 at 05:55:23PM +0100, Marc Espie wrote:
> On Fri, Jan 14, 2022 at 08:16:14PM +0100, Volker Schlecht wrote:
> > Hi,
> >
> > ok, so here's my first attempt. I did manage to use system and ports
> > libraries, except for jbig2dec. Here the version in ports is too old.
> >
> > I
On Fri, Jan 14, 2022 at 08:16:14PM +0100, Volker Schlecht wrote:
> Hi,
>
> ok, so here's my first attempt. I did manage to use system and ports
> libraries, except for jbig2dec. Here the version in ports is too old.
>
> I bumped the shared object version from 15.0 to 16.0 - not sure if that's
>
Update with Makefile in the same order as the current port, I hope this
makes reviewing easier.
Index: Makefile
===
RCS file: /cvs/ports/print/ghostscript/gnu/Makefile,v
retrieving revision 1.117
diff -u -p -u -p -r1.117 Makefile
---
And now without the gtk flavour as default ... :(
On 1/14/22 22:56, Volker Schlecht wrote:
... and here's ghostscript using it.
On 1/14/22 22:35, Brad Smith wrote:
On 1/14/2022 2:16 PM, Volker Schlecht wrote:
Hi,
ok, so here's my first attempt. I did manage to use system and ports
... and here's ghostscript using it.
On 1/14/22 22:35, Brad Smith wrote:
On 1/14/2022 2:16 PM, Volker Schlecht wrote:
Hi,
ok, so here's my first attempt. I did manage to use system and ports
libraries, except for jbig2dec. Here the version in ports is too old.
jbig2dec has been
On 1/14/22 21:20, Stuart Henderson wrote:
reformatting the whole makefile in an update (especially for a complex
port) makes it really hard to see what's changed, making review more
difficult and take longer
Yes, sorry about that. But I did follow kili@'s advice and started to
build the
On Fri, Jan 14, 2022 at 08:26:28PM +, Stuart Henderson wrote:
> On 2022/01/14 17:05, Crystal Kolipe wrote:
> > As this new version is no longer 'gnu ghostscript', shouldn't the path
> > change
> > to just print/ghostscript?
>
> No because there is another subdirectory under print/ghostscript
On 2022/01/14 17:05, Crystal Kolipe wrote:
> As this new version is no longer 'gnu ghostscript', shouldn't the path change
> to just print/ghostscript?
No because there is another subdirectory under print/ghostscript
Maybe it could change to something else, but should be decoupled from the
On 2022/01/14 20:20, Stuart Henderson wrote:
> : +FLAVOR?= no_x11
>
> not sure but having this as default might well cause issues with other ports
scrub the "not sure"; libspectre requires a not no_x11 build
and that's depended on by various other ports, we can't have a
some quick comments (some of them apply to your lang/node update too),
reformatting the whole makefile in an update (especially for a complex
port) makes it really hard to see what's changed, making review more
difficult and take longer
also re formatting, you add quite a lot of horizontal
On Fri, Jan 14, 2022 at 08:16:14PM +0100, Volker Schlecht wrote:
> ok, so here's my first attempt. I did manage to use system and ports
> libraries, except for jbig2dec. Here the version in ports is too old.
>
> I bumped the shared object version from 15.0 to 16.0 - not sure if that's
> advisable
Hi,
ok, so here's my first attempt. I did manage to use system and ports
libraries, except for jbig2dec. Here the version in ports is too old.
I bumped the shared object version from 15.0 to 16.0 - not sure if
that's advisable and/or necessary, but I think for a first shot it's
pretty good
Intermediate update to ghostscript-9.07. Yes, I know gs-9.10 is
already out, but I'd like to do this in smaller steps.
Please note that this version lacks JPX support (because the patched
jasper had been removed and I didn't yet manage to get gs built
with openjpeg).
Ciao,
Kili
Index:
Update ghostscript to 9.05.
THe following devices had been added (+) or deleted (-):
+cdnj500
+eplcolor
+eplmono
+inkcov
+pamcmyk4
+plan
+planc
+plang
+plank
+planm
+tiff48nc
+tiff64nc
Update to ghostscript-9.94, ugly as usual. This also enables
jbig2dec support.
There are probably some new devices supported by ghostscript-9.04,
but I didn't yet update the supported devices. This can be done
later in a separate commit.
Ciao,
Kili
Index: Makefile
Update to ghostscript-9.00.
Better than what I had during p2k10, and shoulnd't be worse than
the old 8.63 we've in the tree.
Please test and/or comment. If I don't get any negative feedback
within the next two weeks, I'll just commit it.
Installs and works fine on amd64. No problems,
On Thu, Jan 15, 2009 at 03:41:30PM +0100, Antoine Jacoutot wrote:
Why can't evince depend on -gtk flavor directly if it is needed to operate?
This fallout is being worked on.
Eventually libgs may end up in ghostscript proper and the issue will
disappear. Give us a couple more days.
Here
On Sun, Jan 18, 2009 at 07:34:52PM +0100, Antoine Jacoutot wrote:
This fallout is being worked on.
Eventually libgs may end up in ghostscript proper and the issue will
disappear. Give us a couple more days.
Thank kili@, very good news !
I will have an intensive look at this tomorrow.
This removes the cups flavor from ghostscript and instead enables
the cups driver for all flavors, using dlopen(3) to load the cups
libraries.
ajacoutot@ already tested the modified cups driver with a previous
version of the diff; this new one just adds the necessary changes
to actually get rid
Apart from the pstoraster discussion, did anyone even TEST this?
That's: build it, install it, use it, look whether it breaks
something. If not: fine, i'll commit it and wait for people crying.
Here's a new update for THE THING[tm]:
Note that the pam device has been renamed to pamcmyk32.
Meuser wrote:
Date: Sun, 23 Mar 2008 12:44:35 +
From: Jacob Meuser [EMAIL PROTECTED]
To: ports@openbsd.org
Subject: Re: update: print/ghostscript/gnu
Message-ID: [EMAIL PROTECTED]
X-CRM114-Status: Good ( pR: 53.6595 )
On Sun, Mar 23, 2008 at 12:32:13PM +0100, Antoine Jacoutot wrote
+
From: Jacob Meuser [EMAIL PROTECTED]
To: ports@openbsd.org
Subject: Re: update: print/ghostscript/gnu
Message-ID: [EMAIL PROTECTED]
X-CRM114-Status: Good ( pR: 53.6595 )
On Sun, Mar 23, 2008 at 12:32:13PM +0100, Antoine Jacoutot wrote:
On Sun, 23 Mar 2008, Jacob Meuser wrote
On Sun, 23 Mar 2008, Jacob Meuser wrote:
i'm 99% sure the cups flavor isn't really necessary. pstoraster is
used by some of the PPD files shipped with cups, but the printers they
support are better supported by foomatic.
If we go this way, then gutenprint cups flavor should be removed too.
On Sun, Mar 23, 2008 at 09:21:56AM +0100, Antoine Jacoutot wrote:
On Sun, 23 Mar 2008, Jacob Meuser wrote:
i'm 99% sure the cups flavor isn't really necessary. pstoraster is
used by some of the PPD files shipped with cups, but the printers they
support are better supported by foomatic.
If
On Sun, 23 Mar 2008, Jacob Meuser wrote:
yep. I've never used that stuff to print with gutenprint drivers
under cups.
I did... and still do on several boxen.
But it is no issue to use foomatic instead of course.
the only references to 'gimp-print', 'gutenprint' or 'stp' in the hplip
sources
On Sun, Mar 23, 2008 at 12:32:13PM +0100, Antoine Jacoutot wrote:
On Sun, 23 Mar 2008, Jacob Meuser wrote:
yep. I've never used that stuff to print with gutenprint drivers
under cups.
I did... and still do on several boxen.
But it is no issue to use foomatic instead of course.
just to be
On Sun, 23 Mar 2008, Jacob Meuser wrote:
just to be clear, you can still use cups. just use the foomatic
generated PPD files instead of the ones that come with cups. and
be sure to use the gimp-print-ijs drivers instead of the gimp-print
drivers.
Of course, this is what I meant :-)
--
Here's a new update for THE THING[tm]:
Note that the pam device has been renamed to pamcmyk32. However,
it's still available as pam. I'll stick with upstream here, so at
one day in the far future, pam may just disappear.
Another note (which also applies to ghostscript-8.60): the -cups
flavor has
On Sun, Mar 23, 2008 at 12:26:48AM +0100, Matthias Kilian wrote:
Here's a new update for THE THING[tm]:
Note that the pam device has been renamed to pamcmyk32. However,
it's still available as pam. I'll stick with upstream here, so at
one day in the far future, pam may just disappear.
Update to ghostscript-8.61 (mostly bug fix release). This also fixes
some linking problem for the gtk-cups flavor.
Please comment and test.
Ciao,
Kili
Index: Makefile
===
RCS file:
On Sun, Oct 28, 2007 at 12:33:27AM +0200, Matthias Kilian wrote:
this needs some testing. For now, pdfwrite seems to be broken at
least on powerpc and arm (but it works on amd64). If you need some
test files for it, see http://openbsd.dead-parrot.de/testgs (run
the testgs.sh script on the .ps
On Sun, Nov 04, 2007 at 07:41:59PM +0100, Matthias Kilian wrote:
On Sun, Oct 28, 2007 at 12:33:27AM +0200, Matthias Kilian wrote:
this needs some testing. For now, pdfwrite seems to be broken at
least on powerpc and arm (but it works on amd64). If you need some
test files for it, see
Hi,
this needs some testing. For now, pdfwrite seems to be broken at
least on powerpc and arm (but it works on amd64). If you need some
test files for it, see http://openbsd.dead-parrot.de/testgs (run
the testgs.sh script on the .ps files). However, I'll debug this
soon, so other tests and bug
55 matches
Mail list logo
