[05:09] cyphermox: hm, do you have an actual .crash file report with a backtrace? [05:50] sorry about all the last-minute uploads/syncs, trying to fix a lot of those rebuild FTBFSes :P [06:31] Laney: rejecting one of your duplicate stsci.distutils syncs, don't get confused [06:40] Laney: sorry, not you [06:41] Logan: rejecting one of your duplicate stsci.distutils syncs, don't get confused [06:41] oh yeah, my bad for requesting twice [06:41] I thought it didn't go through the first time [06:41] (Launchpad email notifications still leave something to be desired) [07:17] cyphermox, infinity: in case you pung about bug 1508075, I just followed up [07:17] bug 1508075 in policykit-1 "crash during network setup in ubiquity wily" [Critical,Confirmed] https://launchpad.net/bugs/1508075 [07:57] infinity: can you test core arm64 and powerpc? I tested the others, but I don't have root access to these arches [07:58] * pitti goes to test ubuntu desktop i386 [08:14] hm, can someone confirm that ubuntu i386 desktop live session is stuck? I see the background pic and nothing else [08:14] both with default qemu vga driver and -vga vmware [08:15] everything is okay on amd64 [08:15] pitti, in a VM? [08:15] yes [08:15] pitti, use kvm64 cpu type [08:15] that has never been necessary -- is that some kind of mesa regression or so? [08:16] smb: "64" for 32 bit ubuntu? [08:16] default is qemu64 which is an odd enough type to break llvm-pipe [08:16] ah [08:16] pitti, and yes theat is "known" to people since dunno Trusty? [08:16] pitti, at least when you ask them [08:17] * pitti searches for an existing bug [08:17] pitti, give me a sec and I could tell you [08:17] smb: thanks [08:18] pitti, one at least is bug 1448985 [08:18] bug 1448985 in qemu "llvmpipe i386 crashes when running on qemu64 cpu" [Medium,Confirmed] https://launchpad.net/bugs/1448985 [08:19] smb: cheers, I'll add that to the tracker [08:19] * pitti links that in the tracker result, so that it appears in the future [08:20] pitti, np. Spent hours to understand that one and then Adam came and told me "oh yeah we know that" :-P [08:20] smb: I remember that I had to change -cpu in autopkgtest to get around that [08:21] cyphermox, We've found the the Deja Dup plugin for Caja has a namespace collision, so doesn't work anymore. [08:22] cyphermox, I've spoken with the developer (who is on the Ubuntu MATE team). [08:22] He is not available until much later today. [08:22] But is happy for me to provide and updated debdiff and tarball. [08:22] pitti, ah right. Yeah either core2duo or kvm64 is ok. Only qemu64 is modeling some weird athlon with virt-extensions that never existed as real hw. And my guess is llvm-pipe assumes some things either from cpuid or id name which does not hold true when running the assembly code for it. Unfortunately the llvm-pipe error message is rather useless. At least to me [08:23] cyphermox, Does that sound like a good way to proceed? [08:23] smb: right, that rings a bell; I just used -cpu host for now [08:23] pitti, yup, that should work as well. [09:22] pitti, ok, fwiw I also did a quick install on an old netbook, so i386 desktop iso via life session and then install. Not sure the final reboot really got stuck with a black screen there as well or I am just getting too impatient in my old days. three finger salute did finish things... [09:51] flexiondotorg: sorry, what does that mean? you'd need a respin? [09:52] flexiondotorg: I think it probably should be a SRU at this point [09:53] flexiondotorg: I'll go back to my "I'm not in the release team so my opinion doesn't matter much, you could argue with them" cop out, but I think it's better to SRU the fix at this point, especially when it's "just" for dejadup. [09:58] ^ FWIW, sounds sensible [09:59] aside from that, it sounds we need a respin for Kubuntu for the kwallet-kf5 thing, right? [10:02] cyphermox, No respin required. [10:02] cyphermox, Just an upload. [10:02] cyphermox, OK, SRU it is. [10:02] flexiondotorg: oh, it's a package which isn't on teh images? which package is that? [10:02] infinity, Are the images getting spun again? [10:03] bug #1502821 [10:03] bug 1502821 in usb-creator "usb-creator-* fails with message cannot install bootloader" [Undecided,New] https://launchpad.net/bugs/1502821 [10:03] flexiondotorg: likely, yes [10:03] pitti, It is seeded, in Ubuntu mATE only. [10:03] states [10:03] "it looks for files into directory /usr/lib/syslinux/ but (in ubuntu Wily) the correct path is [10:03] /usr/lib/SYSLINUX/" [10:03] flexiondotorg: then it needs a respin [10:03] ^ that might be something to fix for release? [10:03] seb128, OK, I'll prepare a debdiff. [10:03] we'll need a respin for bug 1508075 and for the "ubiquity decorations are wrong" thing that seb128 was looking into [10:03] bug 1508075 in udisks2 "ubiquity and others time out on polkit (killed by udisks2-inhibit)" [Critical,Incomplete] https://launchpad.net/bugs/1508075 [10:03] flexiondotorg, for usb-creator? [10:05] smb: I get the shutdown screen with "remove install media and press enter" all the time, hmm [10:05] smb: we fought with that during the vivid release sprint [10:06] Laney, ^ you said you would be interested to fix usb-creator issues? ;-) [10:07] * pitti claims the "first mandatory green 9/9" flag for desktop i386 [10:07] flexiondotorg: As pitti says, we have a couple of bugs we'll probably respin for, assuming fixes happen. [10:07] The only one I consider RC is the polkit thing. [10:08] pitti: If there's any help you can lend on the polkit bug, more brains are better. Even German ones. [10:08] infinity, Thanks. I'll not burn another PowerPC DVD just yet then ;-) [10:08] infinity: was just talking to cyphermox; I asked him to test an idea which has a pretty good chance to succeed [10:08] pitti: \o/ [10:08] infinity: but I can't reproduce the hang on any of my three platforms, so I need some testing help [10:08] anyone who knows about syslinux and want to comment on the usb-creator issue just mentioned? [10:09] like did the path change and on purpose? [10:09] seb128: If you can hunt down mdeslaur, he touched usb-creator in funny ways this cycle. [10:09] seb128: As for paths changing, check the Debian maintainer field. :P [10:09] infinity, he's probably still sleeping [10:10] infinity: I'd like to sync https://tracker.debian.org/news/720214 once it's imported into LP, to mop up some small fixes (most importantly, fix backportability to trusty) [10:11] pitti: It's not seeded, I'm fine with that. [10:11] infinity: and fixing the "prepare VM" scripts to give a working minimal VM again (lxc/lxd was added very late) [10:11] infinity: ok, what I thought [10:12] * pitti sighs at cloud images carrying more and more unnecessary stuff [10:14] it's ever so slightly less worse, but still tends to be racy [10:14] seb128: /usr/lib/syslinux is in syslinux-common, BTW, not syslinux. [10:14] cyphermox: still getting timeouts? [10:16] yes [10:16] seb128: usb-creator was correct, and working fine this cycle unless something changed recently [10:16] aside from issues if there's an architecture mismatch [10:17] cyphermox, it fails to create the bootloader for me and I found that but with the details I just copied [10:17] testing if changing syslinux to SYSLINUX fixes it [10:17] well, it might if you have that path, but I think it would be good to know why it didn't find the other path [10:18] which one? [10:18] cyphermox: ok, thanks for testing; it was worth a try, although I still don't quite understand this [10:18] infinity, I need a respin. Allegedly. [10:19] https://bugs.launchpad.net/ubuntu-mate/+bug/1505505 [10:19] Launchpad bug 1505505 in ubuntu-mate "ubuntu-mate-desktop does depend on vlc-plugin-pulse but that got removed" [Undecided,New] [10:19] infinity, I'll update the seeds in a sec. [10:19] seb128: syslinux-common [10:22] cyphermox, infinity, Laney, in fact the path seems correct on disk, maybe that user has a local problem. My bug was because I picked an amd64 iso on a 32 bits machine I think, sorry about the noise :-/ [10:25] seb128: It's just a missing dep. We'll fix it here. [10:25] seb128: Just needs to depend on syslinux-common. [10:26] infinity, thanks [10:26] infinity, Can you update ubuntu-mate-meta please? [10:26] Can someone please sponsor this update please? https://bugs.launchpad.net/ubuntu-mate/+bug/1508353 [10:26] Launchpad bug 1508353 in deja-dup-caja "deja-dup-caja plugin has a namespace collision in Ubuntu MATE 15.10 [debdiff]" [Undecided,In progress] [10:29] cyphermox, infinity: ok, give me some time for this; at this point we need an unintrusive and small fix, teaching polkitd about SIGHUP doesn't sound like that. I'll try some other things first [10:30] no, it's not unobtrusive enough [10:31] but I think your systemctl try-restart is the best we have right now [10:31] cyphermox: I thought that still leads to timeouts, and thus is useless? [10:31] I'm going to try it some more, see if it's good enough to get us something that looks good [10:31] it does sometimes lead to timeouts, but it's better than it was [10:31] and my testing method isn't exactly what people usually do - starting and stopping and restarting ubiquity repeatedly [10:32] unfortunately polkit doesn't support /run/polkit-1/localauthority/ [10:32] on the live system we don't actually need the bind mount though, but I would be surprised if inotify worked on aufs [10:32] anwyay, that's part of "I'll try some things" [10:40] Riddell: You around? [10:41] Riddell: If so, can you try pitti's workaround for this bug, since you reproduce it better than anyone? [10:41] not that important really, as it'll just a bit less bad, but still not "good" [10:41] I have about three ideas which I'm currently testing [10:41] pitti: If "less bad" is the best we can do, it's still better. :/ [10:42] pitti: But, yeah. Goodest would be more gooder. [10:43] pitti: The live system is overlay, not aufs, and inotify definitely doesn't work. :P [10:43] infinity: I'm currently testing that, but that's what I was afraid of [10:43] pitti: In fact, it's actively broken, which is even worse than not working (as in, the FS claims to support it, then does nothing useful when you hook into it). [10:43] I have a solution which works on my installed sytesm [10:44] hm, it actually does trigger, curious [10:45] sudo G_MESSAGES_DEBUG=all /usr/lib/policykit-1/polkitd -r [10:45] sudo touch /var/lib/polkit-1/localauthority/90-mandatory.d/foo.pkla [10:45] -> polkit reacts (that's on a live system) [10:45] not expected (but would be nice indeed) [10:45] pkcheck -a org.freedesktop.udisks2.filesystem-mount -p $$; echo $? [10:46] that should be 0 for normal mode, and 1 for inhibited mode [10:46] anyway, I still have another idea, let me test/prod more [10:47] cyphermox: can you reproduce that with ubiqutiy under the live system? i. e. where it's non-agonizing to downlaod/update a file? [10:47] Riddell: ^ [10:49] pitti: Is that path an overlay, or a tmpfs? [10:50] pitti: of course [10:50] infinity: it's on teh normal overlayfs [10:50] pitti: Huh. Then something's polling manually, cause inotify definitely doesn't work on overlay. :P [10:50] cyphermox: ack, I should have a new udisks2-inhibit for testing then [10:50] pitti: what what? [10:50] pkcheck I didn't try [10:50] cyphermox: I mean, in 5 mins, sorry [10:50] I just rebooted [10:51] your systemctl try-restart fix looks sufficient [10:52] it helps if one changes both kills, for sure. [10:52] infinity: it does use inotify,confirmed in strace [10:53] now, to run all this in a vm so I can actually complete the install and make sure things work correctly [10:53] cyphermox: the second kill is only when ubiquity finishes, though [10:53] sure [10:53] but that's *why* I said it wasn't quite there [10:53] cyphermox: oh, you only got hangs on the second restart? [10:53] ah [10:53] if it gets killed, it hangs on second starts or NM might not have a polkit ready [10:54] right, *if* the restart helps, then it needs to go to both places [10:55] looks good so far [10:55] pitti: Then I question that it's on overlay, unless someone fixed that in the last 6 months, but... Kay. [10:56] pitti: (I could have sworn I saw a weird polkit related mount in my last live session) [10:56] infinity: yes, you did [10:56] infinity: it *currently* doesn't rely on inotify, but it seems it actually works now [10:57] infinity: perhaps since the new version that landed in the upstream kernel (remember we had to change casper and everything for the new syntax) [10:57] pitti: Oh, actually. It might be that it works for new files, but not changed files or something. [10:57] overlayfs and inotify, i'd be epically supprised if it works reliably [10:57] infinity: right, but that'd be sufficient [10:57] pitti: Yeah. [10:57] new file and rm seem to work [10:58] (repeatedly) [10:58] i. e. it seems to work for dirs, but not files [10:58] (changing files does *not* work, I tested) [10:58] New files are new inodes, changed files don't change the inode with the watch on, but instead give you a new inode and the world explodes. [10:58] pitti, right because directories are a thing at the overlayfs level, files arn't, they exist in the real filesystems but your watches are not in the right world [10:59] apw: I still think the fix for that is just to copy-up when a watch is added, and attach the watch to the copy. [10:59] apw: Bit of a waste of space, but would be reliable. [11:00] new udisks2-inhibit works locally; /me tests it on live system [11:01] infinity, except it is more complex in that there are are three places and you are in the thrid one, i have patches which [11:02] make overlayfs a consumer of inotify on the files it uses from the lower layers, and propogate them to the real upper watches [11:02] \o/ works fine [11:02] apw: Three? Doesn't the inode on the combined filesystem either match the underlay (before a copy-up) or the overlay (after a copy-up), so there's really only two options? [11:02] pitti: how new is it? [11:02] cyphermox: sorry, how new is what? [11:02] apw: Oh. I guess I'm nothing thinking of multiple layer cases. [11:02] * cyphermox has been testing systemctl try-restart in an install now [11:02] but they are invasive, and they don't fix the issue that there is no way to represent copy up itself [11:02] how new is your udisks2-inhibit? [11:03] infinity, the third place is the overlayfs inode, which doesn't exist per-see but does from a notify point of view [11:03] infinity, Can you update ubuntu-mate-meta please? [11:04] flexiondotorg: do you have your caja fix too? [11:04] cyphermox, https://bugs.launchpad.net/ubuntu-mate/+bug/1508353 [11:04] Launchpad bug 1508353 in deja-dup-caja "deja-dup-caja plugin has a namespace collision in Ubuntu MATE 15.10 [debdiff]" [Undecided,In progress] [11:05] infinity, cyphermox: attached the kill-less inotify scrip to the bug [11:05] flexiondotorg: I can do your meta update. [11:06] infinity, Thank you! [11:06] flexiondotorg: I wouldn't recommend a rebuild until we sort this ubiquity thing, since I have to rebuild everyone for that anyway. [11:06] infinity, Understood. [11:11] cyphermox, infinity, Riddell: I attached both variants to the bug now [11:11] flexiondotorg: Is there a bug number for this meta update? [11:12] flexiondotorg: Ahh, found it. [11:13] it's a "pick your poison" decision: the inotify one relies on overlayfs and might leave dangling symlinks behind if you actually use that in a real system, and the restart one might break pending calls to polkit (but not existing connections any more, which is the bug here) [11:13] I actually have a better solution in mind using temporary udev rules (which have neither problem), but that's more intrusive [11:14] if the restart one works, then my recommendation is to use that for wily as that's the least intrusive [11:14] if it doesn't work, then let's use the inotify one [11:17] Or both! [11:17] Two hammers are better than one hammer. [11:17] That's what my hammer salesman told me. [11:18] infinity: sorry, it's just one shaft with a hammer head on either end [11:18] pitti: It's PHP? [11:18] Oh, that was two claws. [11:18] https://www.flickr.com/photos/raindrift/sets/72157629492908038/ [11:18] there; I was going to work on the udev rule one and now I need to chuckle [11:19] as long as it's not like this: http://vignette4.wikia.nocookie.net/starwars/images/1/1a/Darth_Maul_lightsaber_reveal.png/revision/latest?cb=20140421143551 [11:21] infinity, cyphermox: remind me, why do we have this inhibit thing in the first place? for installations to USB drives, right? (as internal drives aren't being automounted anyway) [11:24] or, I guess it was for preventing the user from clicking on the internal drive icons and thus manually mounting them [11:25] automounting hasn't always been inhibited consistently on internal drives, and yes, external ones matter too [11:25] ubiquity needs complete control muahahahaha etc. [11:26] just tested on current live system, manual mounting is all too easy too [11:26] cf. http://www.chiark.greenend.org.uk/~cjwatson/blog/desktop-automount-pain.html :-) [11:26] so just setting UDISKS_AUTO=0 won't suffice [11:27] cjwatson: heh, right; but most of them won't prevent manual mounts, which AFAICS is the bigger problem? [11:27] the original motivation was things randomly capturing temporary mount points [11:27] that was the idea behind temporarily changing the polkit policy -- then you both disable auto- and manual mounts, and it works for all desktsop [11:27] but suppressing manual mounts would be good too [11:37] infinity, Thanks. [11:37] pitti: upload whichever one you prefer, both your fixes seem to work correctly here. [11:37] unless Riddell says otherwise [11:37] cyphermox: cool, thanks for testing [11:37] I can only test it so much, it's hard to reproduce [11:38] cyphermox: I'll flip a coin :) but indeed I'm leaning towards the restart thingy as that's the least intrusive [11:38] ok [11:38] well, the inhibit one seemed to be quite nice [11:38] not restarting means it's even less intrusive to other things on the session [11:38] I'm testing the temp udev rules one right now, which is kind of "best of both worlds" [11:39] but I wouldn't do that a day before release [11:39] right [11:39] but after release I'd just teach polkit to do USR1 or HUP. [11:39] seems like a fairly useful trick [11:40] * cyphermox takes a backup to be able to run at least one install test on real hardware [11:40] yay, we have an X-series bug target in LP now [11:41] cyphermox: oh, don't you guys have infinity's craptop as a victim in the office? [11:41] I didn't bring my spare laptop this time, no. Didn't want the weight when I'm on the road for three weeks. [11:41] I considered bringing craptops, but didn't want to take more shit out at airport securities [11:43] I'd have thought in the office there sohuld be a spare or three [11:43] There might be. [11:44] ^ kthxbye lunch o'clock [11:45] pitti: thanks [11:45] infinity: if you review/accept it seems a a perfect lunch time for you as well, for LP/britney to do their things :) [11:46] ^ u-s-d, that's for bug #1508327 [11:46] bug 1436861 in unity-settings-daemon "duplicate for #1508327 unity-settings-daemon crashed with SIGSEGV in engine_update_composite_device()" [High,In progress] https://launchpad.net/bugs/1436861 [11:46] would be nice to get in as well [11:46] both didrocks and I got it while testing ubiquity install-mode [11:46] https://launchpadlibrarian.net/221863227/unity-settings-daemon_15.04.1%2B15.10.20151012-0ubuntu1_15.04.1%2B15.10.20151021-0ubuntu1.diff.gz [11:46] it leads to having wm decorations on the right and probably some other issues [11:46] ^ debdiff for that, as it's non trivial to find [11:47] This bug is confirmed not present in Ubuntu MATE but still present in Unity - https://bugs.launchpad.net/ubuntu-mate/+bug/1437764 [11:47] Launchpad bug 1437764 in msttcorefonts "ttf-mscorefonts-installer doesn't work from Ubuntu Software Center because of EULA, breaks APT" [Undecided,Confirmed] [11:47] I didn't do anything to fix it. [11:47] could be a missing frontend? [11:48] seb128: is the "devices = " just for not having to write manager->priv->devices_array several times in the loop, or is there some funky refcounting thing going on? [11:48] seb128: i. e. the gist of the change is to disconnect signal handlers before freeing, right? [11:48] pitti, it's just to improve readability [11:49] yes [11:49] seb128: I thought one would use g_ptr_array_new_with_free_func() for such things, and disconnect handlers there [11:49] pitti, same reasoning than https://bugzilla.gnome.org/show_bug.cgi?id=673007#c17 [11:49] but anyway, LGTM [11:49] Gnome bug 673007 in general "[power]: gnome-settings-daemon crashed with SIGSEGV in engine_update_composite_device()" [Normal,Resolved: fixed] [11:49] pitti: Are you reviewing u-s-d? [11:50] pitti, feel free to comment on #ubuntu-desktop for larsu about that [11:50] we can improve that with another commit after wily [11:50] infinity: I was reviewing, seems Laney is currently pushing the button for it [11:50] seb128: yeah, nevermind [11:50] thanks for the review! [11:50] pitti: I didn't [11:50] lunch now, I'm starving [11:50] bbiab [11:50] I saw you were reviewing :) [11:50] just saying that we will take this change [11:51] ack; accepting then [11:51] "The Unapproved queue is empty." [11:51] and so is my stomach [11:51] * pitti bbl [11:51] thanks [12:03] ^ oooh! [12:03] we have an adjective? [12:03] shh [12:03] sssshhhhhh [12:05] (also, if we're fired, I blame infinity) [12:15] promoted the slimit binary, only the source was promoted [12:15] Huh, I thought I got that in the queue yesterday. Thanks. [12:18] pitti, really it might be just me being too quick... I am not used to a puny netbook with an old Atom CPU. [12:55] Laney: vim/amd64 WTH? [13:00] pitti: ? [13:00] did it fail? [13:00] Laney: yes, in a really weird way; I retried it [13:00] Laney: https://launchpadlibrarian.net/221870097/buildlog_ubuntu-wily-amd64.vim_2%3A7.4.712-2ubuntu4_BUILDING.txt.gz [13:00] * Laney blinks [13:01] Laney: seems the new build is past that point already [13:02] worrying [13:02] but thanks for retrying :) [13:03] the new build was just a better build, that's it :p (hem… ;)) [13:13] pitti: Can you hunt down why the kio/i386 autopkgtest isn't autopkgtesting? [13:14] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-wily/wily/i386/k/kio/20151021_095959@/log.gz [13:14] argh that again [13:14] * pitti radiates hate towards lcy01 [13:14] infinity: yep, on it [13:14] http://autopkgtest.ubuntu.com/status/alerts/ - eww [13:14] pitti: I retried it. But I'm not convinced it's retrying. [13:17] infinity: next britney run will re-trigger them [13:18] * pitti disabled lcy01 again, next runs will use lgw01 and clean up the mess [13:18] infinity: http://autopkgtest.ubuntu.com/running.html -> kio/i386 is actually running [13:21] pitti: I always forget the URL to that page. [13:21] infinity: "Running" in the menu on a.u.c. [13:21] ... which is linked from the top level. [13:21] infinity: http://autopkgtest.ubuntu.com/status/alerts/ shows all the tmpfails, FYI; i. e. problems with the testbeds [13:26] are uploads for wily-proposed already accepted? [14:17] cyphermox, Will you have time for the Deja Dup extension fix for Caja? [14:18] can you point me to the bug again? I was on something else [14:18] cyphermox, Sure. [14:18] cyphermox, https://bugs.launchpad.net/ubuntu-mate/+bug/1508353 [14:18] Launchpad bug 1508353 in deja-dup-caja "deja-dup-caja plugin has a namespace collision in Ubuntu MATE 15.10 [debdiff]" [Undecided,In progress] [14:25] flexiondotorg: are you sure this is good? the commented out part in setup.py? [14:40] pitti: infinity: still need testng? [14:41] flexiondotorg, Yep. [14:41] cyphermox, Thanks. [14:42] Did you change debian/install to executable? [14:43] Riddell: I'm going to respin you shortly, you can just test the ISO instead. :) [14:43] lovely [14:50] Riddell: if you want, you can replace udisks2-inhibit with what's attached to the bug, to get it early [14:50] also, the fixed udisks2 is just being published [14:52] ^ lolz [14:53] flexiondotorg: deja-dup-caja is atrocious [14:57] cyphermox, In what sense? [14:58] in the sense that the packaging was broken, and that your patch means the upstream tarball should get fixed [14:58] (and we rejected twice before getting it right) [14:58] cyphermox, I'm working with the upstream author to fix the tarball either tonight or tomorrow. [14:58] ok [14:59] Is there anything else you want me to improve. [14:59] Because I'v not ben involved with the development or packaging until tody. [15:03] cyphermox, ^^^^^^^^^^^^^^^^^^^^^^ === fginther` is now known as fginther [15:14] flexiondotorg: nothing critical now; if you can just make sure that the upstream developer fixes the filename in their tarball, then we'll be pretty good [15:14] oh, and the README too; there's a small diff [15:14] basically, what's in deja-dup-caja.patch [15:15] once that is done, there's nothing special to do but to drop the patch with the upload, the rest is not an issue [15:21] infinity, i've done a quick spin through the release notes, dropped the bugs which appear fixed etc. we are missing updated release notes for most of the flavours at the moment (many are /beta2 still) [15:22] infinity, we are also missing server [15:24] apw - ours are done - just not changed that page yet [15:27] flocculant, cool thanks [15:28] apw - though if I'd have waited I could have said I'd done the main page ... [15:29] must be install testing fever [15:41] flexiondotorg: Will rebuild MATE once that deja-dup thing publishes in the next 30m. [15:41] **** WARNING: REBUILDING THE WORLD **** [15:43] * ogra_ searches for cover [15:43] infinity: \o/ imagesssss the precccciiiouussssss [15:45] infinity, Thanks. [15:45] I'll get my DVD burner at the ready for PowerPC ;-) [15:46] cyphermox, Noted regarding the tarball. [15:47] flexiondotorg: oh, that's right. getting a ppc machine next week means I'll really need to do my netboot setup. [15:53] cyphermox, What PPC machine you getting? [15:54] flexiondotorg: some random G5 I might be able to aquire. [15:54] flexiondotorg: I've been meaning to setup a proper netboot environment regardless. [15:57] pitti: How long after something disappears from running.html until is shows up in the test results? [15:57] s/is/it/ [16:00] pitti: The juju-core tests went away from running.html minutes ago, but I don't see results. Weird. [16:00] pitti: Bah. And now they both show up. Finally. As failures. [16:06] cyphermox, Look on ebay, they G5 powermacs are really cheap now. [16:06] yeah [16:07] it shouldn't be too hard to find, I just need to email someone actually [16:07] I just postponed until next week since I'm not in Canada [16:08] cyphermox, There is also the Amiga ONE X500 and X1000 too. [16:08] Which are new. [16:18] flexiondotorg: which are probably quite expensive then [17:06] infinity: up to 5 minutes [17:07] infinity: I retried them, in case it helps; but if it's urgent, feel free to hint away [17:07] pitti: You're way behind. [17:07] pitti: I already hinted them, and the bug has been diagnosed and is being fixed. [17:07] panic: osVersion reported an error: Could not determine series ? [17:08] behind> heh, indeed I am, just returned quickly to laptop before basketball [17:08] infinity: is that the old "no current development series in Launchpad" thing agaain? [17:09] ah, autopkgtest finally imported; /me pushes sync button === robru is now known as robru|sick [17:10] pitti: No, it's a bug in the test. [17:11] * pitti will be back in some 3 hours after basketball; anything I should be looking out for then? [17:11] (I assume/hope you'll be out by then) [17:11] 19:11:25 rbasak | Juju fix uploaded. [17:11] \o/ [17:12] pitti: Just ISO testing. This spin should be "final" unless something horrible happens. [17:12] infinity: ack; I guess I'll give them an initial spin tonight then, and do the finer-grained install cases tomorrow [17:12] already went through all of them today after all, and we didn't change that much [17:12] (famous last words, I know) [17:13] infinity: assuming that nothing particularly horrid has been seen - these new images just need a quick check? [17:14] infinity: this spin> the ones that just landed 45 mins ago, or is another one going on? [17:14] i. e. 20151021 or an upcoming 20151021.1? [17:16] pitti, final build should be 20151021 [17:16] flocculant: Pretty much, yeah. [17:17] pitti: What jibel said. [17:17] hmm, and still bug 1471476 and bug 1508000 [17:17] bug 1471476 in libimage-exiftool-perl "[MIR] libimage-exiftool-perl" [High,New] https://launchpad.net/bugs/1471476 [17:17] bug 1508000 in cmake-extras "[MIR] cmake-extras" [Undecided,New] https://launchpad.net/bugs/1508000 [17:17] pitti: Yeah, neither of those affect images, so we just need them sorted by tomorrow afternoon. [17:17] the latter could be promoted now, after doko's review and latest comments [17:18] infinity: thanks - that was exactly what I needed to read :p [17:18] pitti: Would perhaps be nice if those mythical bugfixes were actually in wily instead of a PPA, but meh. [17:21] infinity: will there be 20151021 server ISOs, or did only the desktop need a respin? [17:21] jderose: Server's building right now. [17:21] infinity: gotcha, thanks! [17:37] infinity: so what are we trying to fix with today's global respin, sigh? [17:38] …bug numbers might be helpful [17:38] wxl, bug 1436861 and bug 1508075 [17:38] bug 1436861 in unity-settings-daemon "unity-settings-daemon crashed with SIGSEGV in engine_update_composite_device()" [High,Fix released] https://launchpad.net/bugs/1436861 [17:38] bug 1508075 in udisks2 "ubiquity and others time out on polkit (killed by udisks2-inhibit)" [Medium,Fix committed] https://launchpad.net/bugs/1508075 [17:38] jibel: 1436861 required a global respin? [17:39] wxl: No, the other bug did. [17:39]