/srv/irclogs.ubuntu.com/2016/02/22/#ubuntu-release.txt

=== sil2100_ is now known as sil2100
jamespageanyone else noticed that the SRU report is not updating?  http://people.canonical.com/~ubuntu-archive/pending-sru.html11:09
flocculantOdd_Bloke: thanks :)12:21
flocculantyofel superm1 stgraber - any of you doing xenial beta 112:21
flocculantinfinity: so - any idea of who's doing the release-team bit yet?12:22
knomeinfinity, also, what's the status of the "base" merges? :X12:22
Odd_Blokeflocculant: :)13:03
cyphermoxflocculant: you should still see both, low disk should show a screen that is titled "Sorry" and has just how much space you have and how much is needed, and no connection should have the updates checkbox disabled and a caption under it that says why13:57
lotuspsychjecan some check if a package hits xenial for enyc?14:02
lotuspsychjemythtv 0.2814:03
ginggslotuspsychje: mythtv FTBFS on some archs https://launchpad.net/ubuntu/+source/mythtv/2:0.28.0+fixes.20160217.44fd8a6-0ubuntu114:06
lotuspsychjeginggs: thank you! enyc ^14:06
apwqmake for Qt5.2 or newer not found.14:08
flocculantcyphermox: ok - cool, not seen the no internet one - assumed there'd be something in that case :)15:35
cyphermoxyou did see the space one though?15:36
* davmor2 shakes his fist at cyphermox dude why you make ubiquity crash?15:36
cyphermoxdoes it crash now?15:36
flocculantcyphermox: yep - 8Gb not enough for Ubuntu :)15:37
cyphermoxerr, that's probably wrong15:37
flocculantseems to want 8.6Gb iirc - not often booting ubuntu image15:38
cyphermoxok.. well I'm going to have to try a few images and flavors to see15:38
davmor2cyphermox: on current with the check sum of 09bc9cec32f7cd49270f165b81390d7a  iso/daily-live/current/xenial-desktop-amd64.iso on macbook pro15:38
cyphermoxok15:38
davmor2all intel mac that is15:38
cyphermoxdavmor2: would need to know what the crash is. you'll file a bug?15:39
davmor2cyphermox: about to if I can get the wifi to connect15:39
xnoxflocculant, if your RAM >> disk space then yes partioner does things weridly. Are you testing in a VM with a weirdly sized config?15:45
xnoxdavmor2, ^ ?15:45
davmor226869915:45
xnoxbug 26869915:46
ubot5bug 268699 in Empathy "empathy crashed with SIGSEGV in tp_connection_run_until_ready()" [Critical,Fix released] https://launchpad.net/bugs/26869915:46
xnoxdavmor2, is that your phone number? or sudo password?15:46
davmor2xnox: no15:46
davmor2xnox: otp in the wrong window :)15:47
flocculantcyphermox xnox: possibly - vm with 2Gb ram in a 8Gb drive - anyway - my ping was really just about the change - not how much space something needs - I'd actually only have concerns if it was xubuntu :)15:48
davmor2xnox, cyphermox: bug 154836215:48
ubot5Error: Launchpad bug 1548362 could not be found15:48
davmor2xnox, cyphermox: subscribed you both so you should have access15:50
xnoxflocculant, is this a real machine or a VM? i believe swap is generated to be 1x or 2x of RAM, i can't remember, and then there is not much disk space left. we have the weird swap calculation, so do use "normal" machines, were disk drive is >> RAM.15:50
xnoxdavmor2, strange. upower doesn't exist anymore....15:50
utlemmingcould I bother a core-dev for a merge of https://code.launchpad.net/~utlemming/livecd-rootfs/v380/+merge/286806 ?15:50
xnoxdoes it?15:50
davmor2xnox: mine is a macbook pro 2011 all intel iirc15:50
flocculantxnox: vm - so if it did 1x with the ram I give then - then leaves 6.something Gb for install15:50
davmor2might 2013 it's been a while anyway :)15:51
xnoxflocculant, and the argument is that with 6GB of disk space, there is not enough space to a) ever install any additional apps b) store any documents/photos/music/files15:52
xnoxflocculant, do thin provisioning/non-preallocated 20GB drive or some such, if you are testing in a VM.15:52
flocculantxnox: yea - I'm not complaining at all - this is JUST about me wanting to double check that things were supposed to be missing from ubiquity now :)15:52
flocculantI didn't want a discussion about disk sizes :)15:53
xnoxflocculant, ubiquity fails to install whenever disk ~= RAM size. and it's not a bug =)15:54
xnoxit has always been the case.15:54
flocculantdude - I know - you're reading too much into my comments :p15:55
flocculantI have NO idea at all - how much space ubuntu would want - I don't use it - I only ever install it to check if a bug I see is global or just xubuntu15:56
davmor2xnox, jibel, cyphermox: http://paste.ubuntu.com/15171252/16:00
cyphermoxdavmor2: so, clearly upower got broke16:09
davmor2cyphermox, jibel: oddly works on vm with the same image16:10
cyphermoxdavmor2: oh, I think I know what this is16:10
cyphermoxor have an idea, anyway16:10
Odd_Blokeslangasek: Your switch to a plain rootfs broke some of our outside-of-buildds code, so I've opened https://code.launchpad.net/~daniel-thewatkins/livecd-rootfs/ext4/+merge/286809 to (partially) revert it; I've retained the hard-coding because (as you identified) building with an alternative type of rootfs doesn't make sense.16:47
xnoxOdd_Bloke, slangasek is on 4 week holiday =)17:12
superm1flocculant: it's not looking good to me for mythbuntu.  mythtv 0.28 didn't make it out of proposed still, mythtv isn't building on non-x86 stuff properly, we're not really sure why but that will blcok the proposed migration17:12
Odd_Blokexnox: Yeah, I know; I'm going to bug someone else soon. :p17:14
tgm4883superm1: isn't it specifically just arm64?17:15
superm1tgm4883: and s390x, ppc64el, powerpc17:15
tgm4883ah17:15
superm1i mean i personally don't think anyone is going to be running mythtv on anything but x86 and arm, but anyway..17:15
cjwatson    CHECK_QMAKE="qmake-qt5 /usr/lib64/qt5/bin/qmake /usr/lib/x86_64-linux-gnu/qt5/bin/qmake /usr/lib/i386-linux-gnu/qt5/bin/qmake /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake /usr/local/lib/qt5/bin/qmake $qmake"17:18
cjwatsonnone of those look very clever17:18
cjwatsonmaybe pass --qmake=/usr/bin/qmake to mythtv's configure as well as to mythplugins?17:19
flocculantsuperm1: thanks :)17:20
superm1cjwatson: we did some test builds on a PPA to look more into it and i want to say it tried /usr/bin/qmake and wasn't working still.  tgm4883 where is that test build?17:21
superm1tgm4883: i thought it was on ~mythbuntu/master-building but maybe teh logs got destroyed when you copied the x86 builds17:25
xnoxsuperm1, however arm64 should kind of work. i'm poking darkness with a stick in a ppa.17:25
tgm4883looking17:26
superm1yeah the test build was trying to give some more verbosity to that error17:26
cjwatsonhttps://launchpad.net/~mythbuntu/+archive/ubuntu/master-building/+build/9028662 exists and is a little different17:27
cjwatsonfound qmake at /usr/bin/qmake but version failed17:27
tgm4883https://launchpadlibrarian.net/240280457/buildlog_ubuntu-trusty-arm64.mythtv_2%3A0.29.0~master.20160218.e4fface-0ubuntu0mythbuntu3_BUILDING.txt.gz17:27
tgm4883cjwatson: yea that's the error17:27
tgm4883found qmake at /usr/bin/qmake but version failed17:28
tgm4883qmake: could not find a Qt installation of ''17:28
superm1which makes me wonder if qmake is misconfigured in the chroot?17:28
cjwatsonperhaps this is a QT_DEFAULT=5 thing or whatever the syntax is17:29
cjwatsonQT_SELECT=5, sorry17:29
superm1that's for when you have 4 and 5 side by side though right?  shouldn't be needed when only 5 is around?17:30
cjwatsonyeah17:31
* xnox is downloading all the build-deps in an s390x chroot....17:31
cjwatsonlooks like you're just missing some Qt-related build-dep, anyway, question is which17:32
xnoxlibqtmirclient1-not-ported-dev </joking>17:32
xnox(xenial-s390x)root@DEVAC02:~# QT_SELECT=5 qmake -version17:33
xnoxQMake version 3.017:33
xnoxUsing Qt version 5.5.1 in /usr/lib/s390x-linux-gnu17:33
xnox(xenial-s390x)root@DEVAC02:~# qmake -version17:33
xnoxqmake: could not find a Qt installation of ''17:33
Odd_Blokexnox: Speaking of bugging people, I notice that you could merge https://code.launchpad.net/~daniel-thewatkins/livecd-rootfs/ext4/+merge/286809 ^_^17:33
xnoxsounds like export QT_SELECT=5 is the thing.... /me ponders what makes it work on  [x86 + armhf]17:34
Odd_Blokexnox: (For context, we're pinned on an old version of livecd-rootfs until this happens <coercion>which will make fixing any s390x problem tricky</coercion>)17:34
cjwatsonQT_SELECT=5 does indeed make a difference here17:35
cjwatsonsuperm1: ^- I'd suggest exporting that and trying17:35
tgm4883superm1: so how do we add that to our packaging?17:35
cjwatsonexport QT_SELECT = 5 in debian/rules17:36
* xnox ponders if our qt5 is borked somehow17:36
tgm4883that's what I figured17:36
xnoxMirv, qmake is weird. On armhf,i386,x86_64 there are two of them built "armhf" and "native", and on those arches, installing qt5-qmake "qmake -version" just works.17:41
xnoxMirv, but on all other architectures requires an export of QT_SELECT=5 to "find" the qt installation.17:42
jderoseinfinity: could you point me to the tools you use to build the daily/release ISOs? I'd like to build up-to-date 15.10 ISOs (desktop and server) to master System76 images from, so i can avoid any chance of USN-2900-1/CVE-2015-7547 compromising the VM during the initial update17:49
infinityjderose: Surely, you install/update on an isolated network?17:51
jderoseinfinity: yes, but the VM still makes network requests that get sent to the outside world. short of disabling networking, i'm not sure there's a reasonable way to work around this.17:52
jderoseplus, i've always wanted to know how the ISOs are built anyway :)17:52
infinityjderose: I can point you at livecd-rootfs, live-build, cdimage, and debian-cd, but you won't like what you find (and certainly won't like it for a one-off respin) :P17:53
jderoseinfinity: hmm, i always hope there was just a magic button you pushed :P17:54
infinityjderose: If you ask really nicely when I'm not on VAC, though, I could be pursuaded to do a one-off daily of wily for you.17:54
davmor2jibel, cyphermox: so played with live desktop mode on hardware and vm both look okay so just that upower issue so far oh and the fact that the new store is missing from the launcher.17:54
jderoseinfinity: ah, didn't realize you were on vacation ATM. sorry about that, ignore me and enjoy your time off17:54
infinityjderose: That said, I'd suggest your network should just be more isolated.  Authoritative nameserver with limited outside resolution, local mirrors, etc.17:54
xnoxcjwatson, superm1 - build-dependency resolution is somehow off, so on some architectures one ends up pulling in libqtcore4 which has default preset to qt4, on other architectures only qt5 is pulled in which doesn't have such a default.17:56
xnoxunless i'm doing something wrong, let me try again.17:58
xnoxactually i'm wrong.17:59
xnoxsuperm1, on both amd64 and s390x qmake doesn't find any installations. It's just i guess x86/armhf configure options result in qmake not being needed at all during mythtv mythtv portion of the build.18:00
xnoxcjwatson, superm1 - ok found it. Mythtv plugins are funky and did tricks behind our back with iterating:18:36
xnoxif [ x"$qmake" = "xqmake" ]; then18:36
xnox    CHECK_QMAKE="qmake-qt5 /usr/lib64/qt5/bin/qmake /usr/lib/x86_64-linux-gnu/qt5/bin/qmake /usr/lib/i386-linux-gnu/qt5/bin/qmake /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake /usr/local/lib/qt5/bin/qmake $\18:36
xnoxqmake qmake-qt4"18:36
xnoxin case of "qmake" default qmake specified.18:36
xnoxand thus it "worked" on x86_64, i386, armhf only =)18:37
xnoxexporting QT_SELECT=5 would have been a better trick.18:37
xnoxor like querying the triplet from gcc.18:37
xnoxMirv, our qt is fine, it's mythtv which is funny.18:38
superm1xnox: thanks so much for digging in and that analysis, we'll yell at upstream.18:54
xnoxsuperm1, qt-chooser is an "upstream" thing as far as I understand. and all they should do is like QT_CHOOSER=5 qmake, QT_CHOOSER=4 qmake, and then give up, and that's it.18:57
Mirvxnox: fun hacks there. arguably though qtchooser is a bit of a hack itself and not universally liked either (Fedora chose to rename all binaries instead)19:53
xnox=(19:54
xnoxi see19:54
xnoxmeh19:54
xnoxMirv, time to switch "default" to qt5 and forget this ever happened?19:54
flocculantinfinity: didn't realise you're on vacation - who else is likely to do the beta stuff for the flavours?19:54
stgraberFFe request for LXD. We'll be tagging our next beta tomorrow so it'd be great if we could have this reviewed before then!19:55
stgraberhttps://bugs.launchpad.net/ubuntu/+source/lxd/+bug/154848919:55
ubot5Launchpad bug 1548489 in lxd (Ubuntu) "[FFe] Let's get LXD 2.0 final in Xenial" [Undecided,New]19:55
infinityflocculant: It's only one day of VAC, though if you can talk someone else into doing this one (hi, stgraber!), I've done my fair share of milestones already. :P19:58
flocculantinfinity: yea I know you have :)19:59
stgrabersure, I'm around this week, so I can take care of the machinery, so long as someone else takes care of tracking, paperwork, announcement, ...19:59
flocculantstgraber: I'm doing that stuff20:00
stgrabercool, who's participating?20:00
stgrabercreating the milestone now, then do a one-off build and switch all of those off in cron20:00
flocculantstgraber: lubuntu/kylin/mate/cloud/gnome/studio and xubuntu20:01
flocculanthttps://wiki.ubuntu.com/XenialXerus/Beta1 is up to date20:01
flocculantI pinged yofel earlier today re kubuntu20:01
flocculantand you didn't reply about Edubuntu - but I kind of assumed you'd not be anyway :p20:02
stgraberwe won't20:03
stgrabernot even sure we'll be releasing 16.04 at all in fact20:03
stgraberhighvoltage and I have been rather busy with !Edubuntu stuff and we've said that if we'd make a 16.04, it would be the last release we'd be involved in, though even that seems unlikely now20:03
flocculantright20:03
stgraberflocculant: http://iso.qa.ubuntu.com/qatracker/series/56/manifest does that look good?20:04
* stgraber fires up VPN20:04
stgraberdailies disabled for those20:05
flocculantstgraber: if all of those EC2 things are cloud - then yep that looks like the right things :)20:05
stgraberyeah, they're the cloudy stuff20:05
flocculantcool20:06
stgraberoh, though I'm not sure if they still matter since they have their own tracker20:06
flocculantthanks stgraber :)20:06
stgraberutlemming, rcj, Odd_Bloke: do you guys still need the products in the manifest on iso.qa.ubuntu.com or is that only tracked through the cloud tracker nowadays?20:06
stgraberif they don't need it, I'll remove those entirely from the manifest so they don't keep popping up20:06
flocculantstgraber: I'll let people taking part know things are building *soon*20:07
flocculantand yea - if they use something else20:07
stgraberI "think" they don't need those anymore20:08
flocculantI have no clue for sure :)20:09
stgraberrebuilds requested for all the participating products, the bot will announce as they show up20:10
flocculantstgraber: thanks :)20:11
Odd_Blokestgraber: We don't.20:23
wxlwe have a rebuild going on for some reason?20:44
flocculantstgraber: looks like bug 1547518 is going to be an issue21:03
ubot5bug 1547518 in ubiquity (Ubuntu) "ubiquity crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.InvalidArgs: No such interface '/org/freedesktop/UPower'" [Critical,Confirmed] https://launchpad.net/bugs/154751821:03
flocculantstgraber: also - what timezone are you?21:03
stgraberUS/Canada eastern but usually working pacific hours21:04
utlemmingstgraber: correct, we do not need the products on iso.qa.ubuntu.com. We have cloud.qa.ubuntu.com for that stuff.21:05
stgraberutlemming: cool, removed from manifest21:05
stgraberflocculant: yeah, that sounds like a potential problem. Looks like it's been assigned to cyphermox so "just" need to wait for a fix and then ask everyone to respin their images21:05
flocculantstgraber: ok thanks - just so I know when to see you about if I need anything, I'm UK time21:05
flocculantstgraber: yup21:06
stgraberqatracker is temporarily down because of a security reboot taking longer than expected21:17
flocculantyep21:18
stgraberoh, this may actually trigger a second rebuild of some images when the server does come back online as the image builder wasn't able to mark things as built or published :(21:19
flocculantheh21:19
flocculantawesome timing :)21:20
stgraberyeah...21:20
flocculantstgraber: most people expect milestones to show up on Tuesday anyway so ...21:20
stgraberqatracker is back, lets see what's been lost in the process21:22
stgraberI confirmed that nusakan thinks that everything was processed so any product that's missing will be getting another build21:23
flocculantlubuntu missing desktops/gnome missing 32bit/ Mate missing completely21:24
stgraberconvenietly all the missing ones are marked as rebuilding :)21:25
stgrabertriggered those again now21:26
flocculantvery convenient - also seems that I can read and agree with that :)21:27
cyphermoxflocculant: that ubiquity crash, do you get it with the live session or with only ubiquity for installing?21:37
wxlcyphermox: both. bug report now says that21:38
cyphermoxhrm, sorry, I didn't notice21:38
wxlcyphermox: also it's i386 and amd64. i'm trying to get one of my ppc testers to check it out there, too, but it likely affects them as well21:38
wxlcyphermox: i just changed it21:38
cyphermoxI'm trying to figure out why21:38
wxlcyphermox: somehow it's related to the presence of the battery21:38
cyphermoxdon't bother checking every arch, it will fail eveywhere21:39
cyphermoxyeah21:39
flocculantcyphermox: I've not seen it21:39
wxlcyphermox: earliest report seems to be the 19th. i wonder if earlier images have something different in terms of the kernel or upower?21:39
cyphermoxwe only go ask dbus for upower if there is a battery21:39
cyphermoxthey might have, yes21:39
cyphermoxwe got 0.99.4-1 on the 18th21:39
cyphermox(but I also uploaded the last ubiquity on the 17th, so it's not a large different in timing)21:40
cyphermoxI think the new upower is broken somehow, haven't managed to find out how just yet but I also don't have a system with a battery to debug this today, I will later.21:41
cyphermoxbefore patching out the crashy bits I'd still like to know why it's crashing21:42
jibelcyphermox, if it's upower pitti could have a look tomorrow morning?21:43
cyphermoxyeah, I'll look too, just a bit later.21:45
wxlcyphermox: but did ubiquity have any changes that would affect its dealings with dbus?21:45
cyphermoxwxl: not directly, but I did move stuff tangentally relevant to upower, when I moved off the "connected to power" widget21:46
cyphermoxso it's probably just some timing issue where upower isn't starting fast enough or something21:46
cyphermoxnah, the widgets themselves don't reference that at all21:48
jibelcyphermox, actually on a laptop just run upower -d and upowerd crashes21:55
cyphermoxfigures21:56
cyphermoxoh, so it does, nifty21:56
cyphermoxI had looked in case there was something like this, but I saw it was just running the daemon seemingly happily on my laptop21:56
jibelcyphermox, the dbus call probably make it crash too21:57
cyphermoxyeah21:58
cyphermoxwell, I got the backtrace, going to look at the code to see21:58
jibelcyphermox, https://errors.ubuntu.com/bucket/?id=/usr/lib/upower/upowerd%3A11%3Ag_variant_is_trusted%3Ag_variant_builder_add_value%3Ag_variant_valist_new%3Ag_variant_new_va%3Ag_variant_new22:01
cyphermoxyeah22:05
flocculantstgraber: thanks for starting the ball rolling - I'm off now - back tomorrow :)22:11
cyphermoxjibel: I think I'll let pitti play with this22:11
jibelcyphermox, k, I'll ping him in the morning22:13
jibelit's a showstopper for beta1 IMHO22:14
wxljibel: well, server, netboot and lubuntu alternates will be fine :)22:14
cyphermoxjibel: I'm fixing up a patch to ubiquity to not crash22:14
flexiondotorg_infinity, You around?22:49
cyphermoxflexiondotorg_: infinity has a day off today, can I help?23:03
flexiondotorg_cyphermox, Hi :-)23:03
cyphermoxhey23:03
flexiondotorg_infinity, Asked me to annoy him about Xubuntu Base and Ubuntu MATE Base.23:03
flexiondotorg_Just here to do as instructed :-)23:04
cyphermoxok, then remind again tomorrow maybe ;)23:05
yofelflocculant: yes, kubuntu would like to do beta1 - not like we can test much, but it would be nice to at least get ubiquity etc. tested23:50
flexiondotorg_cyphermox, Wilco :-)23:58
flexiondotorg_cyphermox, Catch you tomorrow!23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!