=== eeejay is now known as eeejay_is_afk === eeejay_is_afk is now known as eeejay [06:14] Good morning [07:23] good morning everyone [07:24] hi chrisccoulson :) [07:24] hi micahg, how are you? [07:24] chrisccoulson: well, but tired, thanks [07:25] how are you this morning [07:25] pretty bad. i've been getting more and more ill all week, and i can hardly breathe today :( [07:25] i#'m meant to be flying to berlin this afternoon, and i'm not sure what to do now [07:26] chrisccoulson: I'm sorry to hear that [07:30] pitti, hi [07:36] hello tkamppeter [07:37] pitti, about the new CUPS filter Blueprint. There is no intention to switch to CUPS 1.6. What changes in Precise is only the structure of the packaging of CUPS. [07:38] tkamppeter: but 1.5 still ships all those filters? [07:38] pitti, as CUPS upstream/Apple made a decision how to handle the filters, which implies not integrating the PDF filters, I have worked out a new way how the PDF filters will be provided upstream. [07:41] pitti, I want to drop the add-on source package (which we currently ship inside our CUPS package) and provide a real upstream package with BZR and bug tracking and all on OpenPrinting. It is already prepared for CUPS 1.6, but I will add CUPS 1.5 support (=do not install filters which CUPS 1.5 already ships) to its build system. [07:42] tkamppeter: ah, ok; so that doesn't change the cups package at all, it's just an "upstream" spec for now? [07:42] tkamppeter: ah, I see [07:42] tkamppeter: yes, that'll make things a lot easier indeed [07:44] pitti, in Ubuntu, to reduce the distro patches (the PDF filters add-on is more or less a distro patch) I will introduce one new package to Ubuntu/Debian which contains the PDF filters. CUPS will pull it in by Depends and so the printing environment stays the same, only coming from two source Debian packages as there are two upstream source packages. [07:46] tkamppeter: ok, great [08:07] morning === eeejay is now known as eeejay_is_afk [08:22] hey rodrigo_, how are you? [08:22] hi pitti, I'm fine and you? [08:23] I'm fine, thanks [08:41] pitti, about https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-color-management-next-steps, should RAOF be the assignee or me? [08:59] tkamppeter: doesn't matter, as all the WIs have explicit assignees [09:00] tkamppeter: btw, I'm removing the lcm1 work item, as it's already a linked bug (they count as work item, too) [09:00] tkamppeter: spec accepted and updated, thanks! [11:02] pitti, it is about the cloud print integration, we agreed on adding a switch to the Online accounts, I have reported bug 888981. [11:02] Launchpad bug 888981 in gnome-online-accounts "Google account in Online Accounts section of GNOME Control Center needs support for Google Cloud Print" [Medium,New] https://launchpad.net/bugs/888981 [11:02] pitti, should I reporta GNOME upstream bug and wait for the feature simply coming in from upstream? [11:03] tkamppeter: not necessarily wait for them to implement it, but at least discuss whether they'd accept it [11:04] pitti, how to do with the security aspect, should I report a bug on cloud print, assign it to the security people, and ask them to do a security review, security test, stress testy, or whatever on cloud print? [11:04] tkamppeter: I already assigned the MIR to ubuntu-security [11:05] it's not about stress testing, they should review the architecture [11:05] pitti, so we make the Blueprint dependent on whether GNOME upstream accepts it? [11:05] tkamppeter: that's a strong word, but let's please discuss such things with upstream first [11:06] they might have similar plans, or might want us to implement it in a better/different way, etc. [11:08] rodrigo_, hi [11:08] hi tkamppeter [11:09] rodrigo_, it is about https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-google-cloud-print-integration [11:09] rodrigo_, we have discussed an idea of integrating Google Cloud Print, at least sharing out the local printers into the cloud, in Ubuntu. [11:10] oh, and how would that be done? [11:10] rodrigo_, our ideas are written down in the Blueprint, using "cloudprint" as user daemon and adding a switch to the Online Accounts of g-c-c. [11:11] ok, reading the bp :) [11:12] rodrigo_, now I want to ask you whether there are any efforts at GNOME upstream to integrate Google Cloud Print or whether our suggested way to integrate it has a chance to get accepted by GNOME upstream. [11:12] I don't know of any effort in gnome land [11:12] and yes, the suggested way might get accepted [11:13] rodrigo_, perhaps "cloudprint" should only be taken as sample code to know how the Google Cloud Print interface works but the user daemon implementation should be done in gnome-settings-daemon? [11:13] yes, probably [11:14] also, we should add a cups queue for this, right? so that it shows up on the print dialog? [11:14] rodrigo_, how should we proceed with this Blueprint? Would you move it forward? [11:15] or is that only supposed to accept print jobs from the outside? [11:15] that is, what does cloudprint do exactly? [11:15] rodrigo_, for sharing out printers we do not need a CUPS queue. The existing queues are forwarded to Google. [11:16] rodrigo_, yes, this is intended so that the user can print on the printers at home or in the office from his cell phone or tablet from any place on the world. [11:17] ok [11:17] rodrigo_, a CUPS queue for Google Cloud Print would only be needed if we want to support the scenario of Ubuntu on a mobile device (netbook, laptop) and printing to the printers at home, but this is more implementation effort and so more for Q. [11:17] ok, understood [11:18] rodrigo_, sharing out printers is rather easy to implement. [11:18] this is not for printing to the cloud, but to allow printing to your local printers through the cloud [11:18] Yes. [11:18] so yes, sounds quite good, I'll have a thought about it [11:19] rodrigo_, will you contact GNOME upstreamfor that? [11:19] tkamppeter, I am upstream for g-c-c [11:19] but yes, will discuss with marek, the guy doing the print stuff [11:19] rodrigo_: it also requires changing g-o-a [11:20] pitti, yes [11:20] rodrigo_, great. [11:21] tkamppeter, I added a w-i for you in the bp, as per pitti's comment [11:28] rodrigo_, this WI is not needed, as pitti has done this already in the MIR for cloudprint. [11:28] tkamppeter, but I don't think we would need cloudprint as a separate package, right? [11:28] we can probably have that functionality in g-s-d [11:30] rodrigo_, we will let the Ubuntu security team review cloudprint and if they approve it, we implement it the same way in g-s-d. [11:30] ok [11:31] also see https://bugs.launchpad.net/ubuntu/+source/cloudprint/+bug/889018/comments/3 [11:31] Launchpad bug 889018 in cloudprint "[MIR] cloudprint" [Medium,New] [11:31] * pitti vetos yet another python daemon, we are trying to get rid of them [11:33] pitti, yes, +100 :) [11:33] pitt, WI for integrating cloudprint in g-s-d added. [11:33] pitti, ^^ [11:34] seen, thanks [11:38] pitti, rodrigo_, updated bug 888981. [11:38] Launchpad bug 888981 in gnome-settings-daemon "Google account in Online Accounts section of GNOME Control Center needs support for Google Cloud Print" [Medium,New] https://launchpad.net/bugs/888981 [11:39] pitti, rodrigo_, is this OK for the Blueprint? [11:39] for now, seems so :) [11:43] seems fine; doing the ubuntu-security review of cloudprint is still good, though, as presumably the architecture and security properties will be the same in a g-c-c/g-s-d implementation [11:44] http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html [11:44] 303 WIs already [11:44] we'll definitively need to cut quite many [11:45] we have a limit of 160 === zyga_ is now known as zyga [12:03] pitti, for bug 882553 I have already started to work on. What I need first is to have https added to the server and I have already asked the admins at the LF and they wanted to do it for me quickly. [12:04] pitti, as soon as it is done we need to do a security update of cupshelpers which adds the access through https and the check of the certificate of OP's https. [12:05] tkamppeter: see privmsg [12:05] pitti, the modeswitch blueprint should be ready for approval now. [12:06] hello everyone! [12:08] tkamppeter: already done [12:08] hey nessita, how are you? [12:08] pretty good! [12:08] pitti: trying to learn a bit more about packaging [12:08] * pitti lunch, bbl [13:29] rodrigo not around [13:29] ? [13:34] seif: he was two hours ago [13:35] what happened ? [13:36] I don't know [13:40] pitti, it seems that now all my BPs are approved, thanks for that, how about the Blueprint about the CPD? As it is a Q Blueprint it probably does not need to get approved now? [13:45] tkamppeter: right, as by that time it might have changes anyway [13:45] so we can review it in 6 months [13:50] pitti, OK, until then there will also be an OpenPrinting Summit and another UDS and a lot of time for larsu, mpt, and others to work on the design. [13:53] pitti, and the U1 cloud print BP I think I do not need to move to approval as its assignee is Stuart Langridge. Am I right? [13:53] right, that's U1 land === m_conley_away is now known as m_conley [14:39] pitti, can you upload CUPS into Debian and Ubuntu? Once it contains changes for the new printing package scheme and second it contains some USB printer bug fixes. [14:39] pitti, the ones I asked you for testing, but now I have test results from the original reporters of the bugs. [14:40] ah, nice, thanks! [14:52] pitti [14:52] hey Sweetshark [14:52] heya [14:53] pitti: Im just building a 3.4.4-0ubuntu1 for oneiric-proposed. If it succeeds are you ready for upload? [14:55] Sweetshark: in the next hour or so, yes; otherwise on Monday [14:56] yes, it should have finished the test build by then [14:57] I can sign and upload to chinstrap already, I guess [14:57] sure [15:01] tkamppeter: done [15:02] pitti, thanks. [16:08] pitti, can you approve the CUPS SRU for bug 887094? [16:08] Launchpad bug 887094 in cups "usb printer backend crashes" [Undecided,Fix released] https://launchpad.net/bugs/887094 [16:53] pitti: uploaded === eeejay_is_afk is now known as eeejay === Zdra is now known as xclaesse === Shadows` is now known as SoulShadow === eeejay is now known as eeejay_is_afk === eeejay_is_afk is now known as eeejay === m_conley is now known as m_conley_away === eeejay is now known as eeejay_is_afk