All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "printing-foomatic@lists.linux-foundation.org"
	<printing-foomatic@lists.linux-foundation.org>,
	Open Printing <printing-architecture@lists.linux-foundation.org>,
	Printing-japan <printing-japan@lists.linux-foundation.org>
Subject: [Printing-architecture] ANNOUNCE: Foomatic 4.0.5 released!
Date: Tue, 17 Aug 2010 08:35:05 +0200	[thread overview]
Message-ID: <4C6A2D99.8020703@gmail.com> (raw)

Foomatic 4.0.5 is released and now available for download [1].

This release fixes several bugs which got reported to us in the past 6 
months.

foomatic-rip now errors out on any problem instead of continuing or 
silently exiting, fixed-size string buffers are enlarged and causes for 
segmentation faults eliminated, '0' as a placeholder for the custom 
value in the prototype for a custom option actually works now, custom 
option settings embedded in PostScript input work now also without the 
initial comment containing the value, and remainders of the libgs time 
are removed from the documentation.

foomatic-db-engine got updated to fit to the newest changes and 
requirements of the OpenPrinting database on our web server, especially 
links to signature keys of downloadable packages are now supported, XMLs 
generated from PPDs do not reference to the removed driver entry 
"lj5mono" any more, and fixes on the build system and the man pages got 
done.

Thanks to everyone who reported bugs to us (or to their distributions) 
or sent feature requests.

Have a lot of fun with the new Foomatic release!

    Till


[1]https://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/foomatic


                 reply	other threads:[~2010-08-17  6:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C6A2D99.8020703@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-foomatic@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.