All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: "printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Options in /etc/cups/printers.conf
Date: Wed, 10 Jul 2013 20:44:58 +0200	[thread overview]
Message-ID: <51DDABAA.90100@gmail.com> (raw)
In-Reply-To: <10E1A012-2576-49D5-ABE1-ED036D5E0531@apple.com>

Sorry, on both machines where I observed the bug I was already on CUPS
1.7.x. I have downgraded to the official Ubuntu package (1.6.2) on my
Saucy (13.10) machine and there the bug indeed did not show. So the
problem got introduced in 1.7.x and I will apply your patch to my 1.7.x
packages on my PPA.

Thank you for the patch anyway, as now the bug will not appear when
distros switch over to 1.7.x.

   Till

On 07/10/2013 07:30 PM, Michael Sweet wrote:
> Till,
> 
> I don't know if you saw my followup message or not - I was unable to reproduce on TOT 1.6.  You can test TOT 1.6 from the GIT repository with:
> 
>     git clone -b branch-1.6 http://www.cups.org/cups.git cups-1.6
> 
> 
> On Jul 10, 2013, at 1:11 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
> 
>> Unfortunately, this patch applies to a completely new concept of CUPS
>> 1.7.x which did not exist in 1.6.x. Can you also supply a fix for CUPS
>> 1.6.x, so that I can do a patch release of CUPS for Ubuntu 13.04? Thanks.
>>
>>   Till
>>
>> On 07/10/2013 04:44 PM, Michael Sweet wrote:
>>> Till,
>>>
>>> Here is the patch for 1.7 (1.7rc1 to be released soon):
>>>
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> 


      reply	other threads:[~2013-07-10 18:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 21:40 [Printing-architecture] Options in /etc/cups/printers.conf Till Kamppeter
2013-07-10 14:17 ` Michael Sweet
2013-07-10 14:44   ` Michael Sweet
2013-07-10 15:28     ` Till Kamppeter
2013-07-10 15:47       ` Michael Sweet
2013-07-10 15:55         ` Till Kamppeter
2013-07-11  8:48         ` Tim Waugh
2013-07-11 13:11           ` Michael Sweet
2013-07-16 14:33             ` Tim Waugh
2013-07-16 14:48               ` Michael Sweet
2013-07-16 16:27                 ` Tim Waugh
2013-07-16 16:34                   ` Michael Sweet
2014-02-25 23:00             ` James Cloos
2014-02-26  1:12               ` Michael Sweet
2013-07-10 17:11     ` Till Kamppeter
2013-07-10 17:30       ` Michael Sweet
2013-07-10 18:44         ` Till Kamppeter [this message]

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=51DDABAA.90100@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=msweet@apple.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.