[07:30] ok re-uploaded mesa [11:30] I want to do a hardware enablement SRU in Trusty, letting Trusty fully support IPP Everywhere printing as Utopic does. So I backported all appropriate changes from Utopic's cups-filters to Trusty's including ippusbxd (the IPP-over-USB support), only problem is that ippusbxd introduced the new cups-filters-ippusbxd binary package and if I put ippusbxd into the cups-filters binary package in the SRU I would also need a Utop [11:30] ic SRU for assuring correct Trusty->Utopic update. What should I do? [11:32] tkamppeter: best to introduce the new package in trusty, as packaged in later releases. [11:32] tkamppeter: we add new packages all the time for hardware support, see all the -lts- packages [11:34] xnox, OK, thanks. As the whole SRU has also a part in system-config-printer (for auto setup of IPP-over-USB printers) I will let system-config-printer-udev depend on cups-filters-ippusbxd and so the IPP-over-USB support will get into Trusty. [11:45] tkamppeter: i'm no SRU team member though, so your miledge may vary =) but, in general, hw-enablement is attempted to be closer to parity with future release. === txspud` is now known as txspud === kirkland` is now known as kirkland [16:08] xnox, thanks, SRU bug 1386241. [16:08] bug 1386241 in system-config-printer (Ubuntu Trusty) "Add the full IPP Everywhere support from Utopic to Trusty" [High,In progress] https://launchpad.net/bugs/1386241 [16:26] cjwatson: any new news on dailies? i've seen posts about vivid being available for download out on the internets… [16:32] wxl: FYI: cjwatson's in vacation mode :) [16:32] aw shoot [16:32] teward: you know who's taking care of making sure our dailies get up there? [16:33] or do we only care about upgrades and netboot now? XD [16:33] wxl: no idea, i'm not on the release team, I just lurk everywhere :) (I'm not sure who manages what, either). Just thought i'd give you that FYI :) [16:33] wxl: it'll get sorted :) [16:33] elfy: thank you :) [16:35] elfy: ping me if you need any help and/or if you get it all figured out thx :) [16:35] I'm not doing it ... I'm just sure that it'll not get forgotten and I'm not too worried about a few days at the beginning of a cycle [16:36] I'd be less laid back last fortnight of April ;) [16:41] elfy: in theory, couldn't a Utopic build just have `vivid` substituted for `utopic` in the sources.list to set up a vivid environment...? That is, if we're not testing dailies, of course. [16:42] teward: oh you can do all sorts of things to actually run vivid [16:43] this isn't that - there are no images at the image tracker yet :) [16:43] elfy: may as well clone my Utopic VM so I have a vivid environment to beat with a stick :P [16:43] elfy: and true. [16:43] * elfy changed over to vivid on Friday [16:43] kind of necessary with this hat on [16:43] elfy: my systems stay on LTSes, I don't have any testing hardware unfortunately [16:43] so VMs are useful [16:43] at least, for what I test and do :0 [16:43] yep [21:27] those two builds on fischer look very unhappy [21:29] Indeed. Cancelled them both. === wgrant_ is now known as Guest43514 [22:53] is it normal for me to receive a bunch of rejects (things related to libav9) and a bunch of accepts (toolchain / cross compilers) from the time of archive opening? [22:55] xnox: You may have received a few binary rejects (looking like "The following files are already published in Primary Archive for Ubuntu: suchandsuch_blah_all.deb") for packages that were in utopic-proposed at release, due to a Soyuz bug triggered by the nominatedarchindep change. === Guest43514 is now known as wgrant