[01:09] How long till http://qa.ubuntuwire.com/bugs/rcbugs supports vivid? [01:13] wgrant, ^ [01:13] ajmitch: ^^ [01:17] Is there a vcs where i can try and make a patch? [01:36] i'm only getting an ftbfs on a powerpc build of nginx, 1.6.2-5ubuntu1 seems otherwise to be working - do I need to panic about the powerpc build failing, or no? https://launchpadlibrarian.net/193675980/buildlog_ubuntu-vivid-powerpc.nginx_1.6.2-5ubuntu1_FAILEDTOBUILD.txt.gz is the build log, looks like it doesn't relate to a code ftbfs issue, maybe [01:36] s/a powerpc build/the powerpc build/ [10:23] teward: I wouldn't counsel "panic", but somebody needs to figure it out as this package has previously built on powerpc so the new version isn't going to reach vivid until this is fixed. [12:08] guys .... http://wstaw.org/m/2014/12/30/plasma-desktopyq1947.png [13:18] cjwatson: the question then becomes, why are the ddebs unable to be parsed [13:19] teward: Don't know, you'll have to investigate that ... [13:20] That usually means that some of the .debs that you might expect to be generated actually weren't generated [13:20] IIRC [13:21] hmm [13:21] You may well be able to work some of this out by reading pkg-create-dbgsym code and matching it up against the error output [13:21] cjwatson: out of pure curiosity - are the repository builders for powerpc virtualized? [13:21] No [13:21] (Not yet, anyway) [13:21] * teward grumbles. [13:21] None of the builders used for Ubuntu itself are currently virtualised [13:22] But also, powerpc is not yet available in PPAs, which I suspect is your actual question [13:22] makes it difficult to run build tests here if there's no reliable way to replicate the environment... but whatever, guess i'll start digging, on top of work adding 5 days of work into 2 days work [13:23] We'll hopefully improve the virtualisation situation next year [14:06] cjwatson: is there any way to replicate a powerpc environment locally? Because I can find no sane reason for the package to not build - the binary hasn't actually changed and apparently the exact same one builds fine upstream, so it's either in our Ubuntu delta... or something else [14:07] (upstream in Debian) [14:07] if the changes break because of the delta, then why didn't they break -4ubuntu1... hence my confusion [14:07] and my seeking of a way to replicate the build environment local [14:07] teward: you can try with qemu-system-ppc, though it probably won't be quick [14:08] you can also retry the build to see if it's a non-deterministic failure, I suppose [14:09] cjwatson: i'm thinking it might be a temporary derp, if it ftbfs again then maybe i'll dig into it, but it makes no logical sense that the changes incorporated in the merge would break the automated debug symbols process [14:09] especially when the actual delta hasn't changed and doesn't affect the light packaging [14:09] and there didn't appear to be any actual build failures either... [14:09] did you check for failures earlier in the build that might not have stopped the build? [14:10] o...kay this is interesting [14:10] https://launchpad.net/ubuntu/+source/nginx/1.6.2-5ubuntu1/+build/6678397 [14:10] looks like it reran its own build? [14:10] either that or someone poked it - looks like it built the second time round o.o [14:10] oh yeah, I did a mass retry of all failures (unrelatedly) [14:10] so there, you can stop agonising about it ;) [14:10] heheh [14:10] cjwatson: possible non-deterministic temporary failure perhaps? [14:10] (thanks for that btw) [14:10] *shrug* dunno [14:11] cjwatson: i think i saw other powerpc failures upstream once before but a rerun fixed it there *shrugs* [14:11] i'd have to sift throug hmy debian notices [14:11] maybe it was on a different builder, I didn't check [14:12] yeah, denneed02 vs. sagari, suppose the different host might make a difference, but not hugely motivated to dig into it [18:41] hi ubuntu developers! [18:41] have a nice new year! [18:48] LocutusOfBorg1: I think you might be a day or two early :) [18:51] sladen, maybe ;) but I won't be there tomorrow :D [18:53] maybe somewhere it is already tomorrow ;) === Guest60657 is now known as mfisch [20:55] hi all, what's the position of ubuntu regarding packages that link to other packages that were built with openssl? [20:56] for example if cyrus sasl has been built with openssl support, that means a given gpl package cannot link against cyrus sasl, or what?