From: Till Kamppeter <till.kamppeter@gmail.com>
To: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] CUPS 1.7.x packaged for Ubuntu!
Date: Tue, 11 Jun 2013 18:47:56 +0200 [thread overview]
Message-ID: <51B754BC.3040302@gmail.com> (raw)
Hi,
I have packaged CUPS 1.7b1, a first beta version of the 1.7.x series of
CUPS and uploaded it to my Ubuntu PPA [1] for both Raring and Saucy,
both based on the current Debian 1.6.2-8 package of CUPS (source
packages of Raring and Saucy version are identical).
There are only a few new features, mainly API enhancements [2]:
- Improved support for paid, PIN, and release printing
- Expanded support for IPP Everywhere
- Automatic support for data compression
- Improved CUPS APIs
Note that most of the upstream web site is down currently, so I do not
have much more info about the new release.
Please try it out and report your experiences here.
Till
[1]https://launchpad.net/~till-kamppeter/+archive/ppa
[2]http://www.cups.org/index.php
next reply other threads:[~2013-06-11 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 16:47 Till Kamppeter [this message]
2013-06-12 8:25 ` [Printing-architecture] CUPS 1.7.x packaged for Ubuntu! Jiri Popelka
2013-06-12 12:58 ` Michael Sweet
2013-06-12 14:38 ` Jiri Popelka
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=51B754BC.3040302@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@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.