/srv/irclogs.ubuntu.com/2015/01/29/#ubuntu-devel.txt

catbus1Does anyone know when 14.04.2 will be released?01:11
Sarvattcatbus1: https://wiki.ubuntu.com/DraftReleaseSchedule feb 5th01:13
Sarvattwhich is actually cutting it pretty close because the lts backport X stack *just* got in :D01:14
catbus1Sarvatt: thank you.01:15
ari-tczewcyphermox: around?01:45
cyphermoxari-tczew: yes02:03
ari-tczewcyphermox: hi. I saw the stuff is moved to -release. do you still need a help?02:03
cyphermoxno, that's covered I guess02:04
cyphermoxunless you want to merge the other vpn plugins, I'm not sure when I'll get around to those02:04
ari-tczewcyphermox: I can take those. The question is, should do I just merge from Debian, or additionally upgrade to new upstream release?02:05
=== doko_ is now known as doko
cyphermoxI think they're already at their newest release, but that's up to you02:06
cyphermoxI would merge + update if it's worth updating02:06
cyphermoxLogan_: hey, btw n-m-iodine migrated to -release if you didn't notice yet :)02:08
Logan_I saw :)02:08
cyphermoxgreat.02:09
cyphermoxI'm not sure if iodine is the plugin I never ever managed to make work properly ;)02:10
=== timrc is now known as timrc-zzz
pittiGood morning06:50
Unit193Howdy.06:53
dholbachgood morning07:49
LocutusOfBorg1hi dear developerz08:16
LocutusOfBorg1does anybody know which kernel will land on vivid?08:16
=== anthonyf is now known as Guest44978
alkisgmvo, stgraber: hi, could I ping you about LP #1415785 ? update-manager blacklists ltsp, and removes it on dist-upgrades (normal upgrades, not release upgrades), and that breaks ltsp installations. I'd like to help in fixing + SRU'ing this for 14.04 and 12.04...08:53
ubottuLaunchpad bug 1415785 in update-manager (Ubuntu) "Please remove all ltsp* blacklisting" [Undecided,New] https://launchpad.net/bugs/141578508:53
mvoalkisg: thanks, if you could prepare a diff and the sru test instruction I'm happy to sponsor it for you08:54
alkisgThank you mvo, will do08:55
=== dendroba` is now known as dendrobates
infinitymlankhorst: Does libevdev need a utopic->trusty backport too, or will my copying the trust/universe version to trusty-updates/main be enough to make xserver-xorg-input-evdev and xserver-xorg-input-synaptics happy?09:16
mlankhorstinfinity: I didn't update it at least09:21
mlankhorstand works locally09:21
infinitymlankhorst: Alright.  We'll see how that goes, then.  I think those are the only two not built now.09:22
mlankhorstah k09:22
Odd_BlokeI'm hitting "libgcc1 : Depends: gcc-5-base (= 5-20150128-0ubuntu1) but it is not installable" when building arm64/ppc64el images; is this (likely to be) a transient problem, or should I report a bug?09:27
mlankhorstdo you have -proposed enabled?09:30
Odd_Blokemlankhorst: Shouldn't do; Ctrl-F of the build log (https://launchpadlibrarian.net/196091740/buildlog_ubuntu_vivid_arm64_cpc_FAILEDTOBUILD.txt.gz) suggests proposed isn't mentioned anywhere.09:31
Odd_BlokeIt is in http://ports.ubuntu.com/dists/vivid/main/binary-ppc64el/Packages.bz2.09:33
cjwatsonOdd_Bloke: It's a component mismatch.  Fixing.09:34
mlankhorstah09:35
cjwatsonOdd_Bloke: Retry your build once "rmadison gcc-5-base" says "vivid" rather than "vivid/universe" (give it maybe half an hour or so)09:36
Odd_Blokecjwatson: Thanks, will do.09:36
Odd_BlokeFor my understanding, does this mean that someone uploaded gcc-5-base in to universe when it should have been uploaded to main?09:38
cjwatsonOdd_Bloke: Components are overridden centrally, not in general up to the uploader.  New packages tend to land in universe.09:38
cjwatsonSo if they're dependencies of stuff in main then we need to adjust the overrides to account for that.09:39
cjwatsonOften this requires an explicit signed-off main inclusion request, but in this case that wasn't necessary since gccgo-5 is obviously just a newer version of stuff already in main.09:39
cjwatson(that's the source package building gcc-5-base right now)09:39
Odd_BlokeRight, got it.09:40
Odd_Blokecjwatson: Not sure if what you've done will cover it, but "gcc-5-base | 5-20150128-0ubuntu1 | vivid-proposed/universe | armhf" just popped up in the rmadison output as well.10:08
cjwatsonOdd_Bloke: It'll be easier to check after an archive cycle or two when our reports update.10:09
Odd_BlokeCool.10:09
=== lilstevie is now known as lilstevie|Old
=== alkisg is now known as work_alkisg
mlankhorstdoko: are you there?11:36
mlankhorstI did some testing on 10.4.2 vs 10.4.2 with llvm-3.6, results look good. r600 with experimental llvm had no regressions compared to !llvm, swrast i386 and amd64 look good too..11:39
mitya57sil2100: hi, I am going to upload oxide-qt to landing-005, do you know if there should be any differences against the archive version?11:43
mitya57I see two patches in d/patches, but not sure if that's all or they are still needed11:44
sil2100mitya57: hah, hey, we just briefly talked about that with tsdgeos - not sure about that, but from Mirv's e-mail I somehow felt that some changes were needed, I think Timo added hack_qt540.patch to make it buildable11:45
sil2100And made some packaging changes11:45
sil2100So this might need rebasing on the newer oxide11:45
sil2100As I didn't hear anything about those being ported upstream11:46
=== _salem is now known as salem_
mitya57sil2100: I see that Timo had two patches but looks like the second one is no longer needed.11:49
mitya57I don't see any other packaging changes11:51
mitya57sil2100: Ok, I have something that I can upload and see if it builds11:53
sil2100mitya57: thanks :) oxide is really huge, we might need to bump the PPA size limit in case a re-upload is needed11:54
cjwatsonLet me check the current size limits11:54
cjwatsonubuntu/landing-005 already has a 20GiB limit.  It seems unlikely that you'll run into trouble.11:56
mitya57yes, should be no problem12:00
mitya57uploaded12:02
rbasakinfinity: around for the mysql chat?12:24
=== MacSlow is now known as MacSlow|lunch
mlankhorstdoko: I've uploaded mesa 10.4.2-2ubuntu212:43
dokomlankhorst, so from your point is it ok to make 3.6 the default?12:47
mlankhorstyeah looks like it12:50
=== pfsmorigo_ is now known as pfsmorigo
mlankhorstand pushed the changes for it :p12:53
mitya57sil2100: btw I just committed your qtbase change to bzr, so that it's again in sync with ppa12:54
jrwren~12:58
pitticyphermox: oh, now I understand what you meant by NM 0.9.10 having veth support -- when I start/stop LXC containers I get a ton of "you are now connected to vethDH32FO" notifications13:07
=== didrocks1 is now known as didrocks
shadeslayermvo: did you notice the synaptic upload got rejected13:34
=== MacSlow|lunch is now known as MacSlow
cyphermoxpitti: yeah. I'm considering patching that out of nm-applet or something14:09
sil2100mitya57: thanks! That was one thing I wasn't sure about, if we are using a bzr branch to keep track of the current ongoing work or not14:15
mitya57sil2100: the 5.4 packaging is in qtFOO-opensource-src branches, while 5.3.2 is in qtFOO-opensource-src_53214:24
sil2100ah, ok, saw the _532 but still wasn't sure if the trunk ones are supposed to have our 'experimental' bits in it14:25
pitticyphermox: should they even be considered connections that NM has to care about?14:31
cyphermoxpitti: they are already not managed, all you really do is connect/disconnect, and if you really want you could change settings (not that it wouldn't break things)14:32
pitti(brb)14:32
cyphermoxthat's why I'm thinking explicitly ignoring the virtual devices in nm-applet, since one probably shouldn't touch them, but NM isn't breaking them14:38
cyphermoxpitti: ^14:38
pitticyphermox: *nod*, thanks14:38
pittiah, and I see lxcbr0 now, too14:39
pittiwith an option to disconnect it14:39
cyphermoxyep14:39
cyphermoxthey all come up as virtual devices, and pretty clearly separated in nm-applet so hiding those should be trivial14:39
cyphermoxI'd do the same for VLANs, tunnels, bridges, bonds14:40
cyphermoxnot usually that common on desktop machines, or at least not in a case where you actually want to touch them14:40
=== timrc-zzz is now known as timrc
lefterishi there, i want to make an sru in update-manager15:35
lefterisi read the wiki for sru and says that firstly must branch and apply the fix to the development branch (vivid)15:36
lefterisi am using ubuntu 12.04; should i download ubuntu 15.04 for building the source and testing it15:38
infinitylefteris: Working on the branches isn't strictly required, you can just file a bug and attach patches.15:38
infinity(against the source from the archive)15:39
lefterisor i can to build the source to the presice15:39
lefterisinfinity: hello, firtsly; thanks for your help15:42
lefterismy actual question is: if i want to debuild the source code from vivid branch must have ubuntu 15.04 or i can to do this from precise; i am aksing because debuilding source code of vivid require python3-all 3.3.0-2 and in precise is available the python3-all 3.2.3-0ubuntu1.215:47
lefterissorry, my question may be stupid, but i am new to making sru's15:47
cjwatsonlefteris: For your test build, you should use a clean 15.04 build environment, but that doesn't involve upgrading your base system.  https://wiki.ubuntu.com/SimpleSbuild15:49
cjwatsonlefteris: If you set that up then you can also use an schroot environment for running "debuild -S" easily enough15:49
cjwatsonlefteris: Though in this particular case it probably doesn't actually matter just for building the source package; I'd be inclined to use "debuild -d -S" to ignore build-dependencies, and then compare the source packages with debdiff on the old and new .dsc files to make sure that didn't introduce anything unexpected15:51
cjwatsonlefteris: But for building the binary packages you should definitely use sbuild or similar, not try to get it to build on your 12.04 base system.15:51
LocutusOfBorg1dholbach, kbuild sync from debian/experimental? (bug 1408285) :D15:51
ubottubug 1408285 in kbuild (Ubuntu) "Please sync kbuild, virtualbox and virtualbox-guest-additions-iso from debian/experimental" [Undecided,Confirmed] https://launchpad.net/bugs/140828515:51
dholbachlet me take a look15:52
LocutusOfBorg1:)15:52
lefteriscjwatson, infinity: thank you very much for your help15:53
lefteriscjwatson: οκ, i got it; thank you15:54
LocutusOfBorg1thanks dholbach :)16:05
dholbachanytime16:05
pittidobey: look! "autopilot PASS" with --setup-commands ubuntu-touch-session :)16:16
pittidobey: thanks for the report16:17
balloonswoot!16:17
pittiseems vivid's upstart changed behaviour a bit16:18
pittithat was in qemu, testing in LXC now for completeness16:18
dobeypitti: nice :)16:19
pittiwow, that fails with http://paste.ubuntu.com/9939333/, but I'm not sure that's my fault16:20
pittiyep, python3 -c 'import psutil' reproduces it16:21
dobeyfun16:22
* pitti files a Debian bug16:25
=== work_alkisg is now known as alkisg
pittidobey: ok, bug sent, so running in LXC is broken for now; but qemu at least works fine now16:33
ovidiu_calbajoshello all, do you know if the libc6 has been patched already for the ubuntu 12.04 openvz image?16:37
infinityovidiu_calbajos: You might need to elaborate on what you mean.16:38
ovidiu_calbajoshi infinity, well one of my clients tries to update the libc6 library on his machine and doesn't get any update, also i couldn't find anything related to libc6 + openvz + ubuntu 12.04 + ghost vulnerability on the internet16:40
pittiI suppose the recent security fix?16:40
zygatseliot: hey16:40
pittiah yes, ghost16:40
infinityovidiu_calbajos: Oh.  openvz rolls their own libc.  We know nothing about that, here.16:40
zygatseliot: are you the right person to talk about graphics, drivers and such?16:40
infinityovidiu_calbajos: The libc6 that we provide for 12.04 has been updated.16:40
ovidiu_calbajosinfinity: indeed I saw the update on the 12.04 but I didn't see it on openvz16:41
ovidiu_calbajosthank you for your time16:41
infinityovidiu_calbajos: In other words, this is a question for openvz, not for Ubuntu.16:41
ovidiu_calbajosinfinity: thanks again, I will try to contact them :)16:42
zygatseliot: I want to ask you about a potential candidate for GPU stress tests16:47
zygatseliot: and if you have heard of the tool or others like it http://wili.cc/blog/gpu-burn.html16:47
tseliotzyga: I'll have a look and let you know17:05
zygatseliot: thanks17:08
tseliotzyga: I think that would be limited to the nvidia binary driver, as it involves using CUDA (I had a quick look)17:27
dobeypitti: awesome. i guess i'll need to grab the deb from vivid to install on the host, or it will just update when i run the tests and work?17:32
pittidobey: right, you need vivid's autopkgtest package (but you need that anyway if you want to do anything on the touch platform)17:33
zygatseliot: do you know of other tools that we could use for stress testing GPUs?17:33
pittidobey: note that ATM the fix is only in git, I didn't upload to Debian/Ubuntu yet17:33
pittidobey: you can of course check out git if you want and run /your/checkout/dir/run-from-checkout17:34
pittidobey: or just grab the fixed setup script and copy it to your machine :) (http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/plain/setup-commands/ubuntu-touch-session)17:34
dobeypitti: do i need it on the host or just in the vm though?17:34
pittidobey: it's unrelated to the VM; just on the system where you call adt-run17:35
pittidobey: i. e. --setup-commands <path to that script>17:35
dobeypitti: ok. i wasn't sure if it was using the one on the host or in the vm for that17:35
pittidobey: the VM doesn't have anything special (it can be any VM, or you can use a schroot, or a phone, or whatever)17:36
dobeyanyway, copied the new script onto my host and trying a run now :)17:36
tseliotzyga: that would be tests that involve using OpenGL. I think checkbox already uses the phoronix test suite, which, in turn, relies on some OpenGL tests.17:37
zygatseliot: I don't recall if we use any stress tests from pts17:44
zygatseliot: and we definitely don't have anything for opencl (or cuda)17:45
zygatseliot: so in general, the tool I've likned to is suitable for nvidia but not applicable for amd/intel, is that accurate?17:45
tseliotzyga: opencl would work with both fglrx and nvidia. I'm not sure we support opencl with open drivers. Cuda is nvidia only AFAIK17:46
tseliotmlankhorst, Sarvatt: ^17:46
dobeypitti: well, my tests still fail, but with a different error now :)17:46
tseliottjaalton: ^17:46
dobey** (run.py:17865): WARNING **: Unable to find keyfile for application 'com.canonical.payui_payui_15.01.last'17:46
dobeynot sure how to fix that though17:46
pittidobey: ok, that's not my bug then :) is that gsettings? missing schema?17:46
dobeypitti: i think it's ubuntu-app-launch complaining17:47
dobeyi guess it can't find the .desktop file for some reason17:47
pittidobey: ah, bug 133321517:47
ubottubug 1333215 in ubuntu-app-launch (Ubuntu) ""Unable to find keyfile for application": clicks installed in current session don't create UAL cache, and UAL does not look for .desktop files in click pkgdir" [High,Triaged] https://launchpad.net/bugs/133321517:47
zygatseliot: right about cuda, I don't know the current opencl story, I know all three vendors do their own drivers but they are not open IIRC17:49
pittidobey: you could work around it by "click install"ing it manually on the phone, restarting, and then running adt-run --click com.ubuntu.whatever (i. e. name instaed of a local .click file)17:50
dobeypitti: oh i guess so17:50
dobeypitti: well this is in qemu so phone won't help i guess :)17:50
pittidobey: I tried that with the calculator in qemu and it worked fine though17:50
pittidobey: hm, I wonder what I did differently then17:50
dobeyi wonder why the hooks aren't run when the package is installed in qemu?17:50
pittidobey: oh, which autopkgtest version do you have?17:51
pittidobey: it's not specific to qemu or lxc; it's a bug which affects all click packages17:51
dobeypitti: 3.0.117:51
pittidobey: eww old; try the current vivid one, I think I added a workaround for this some moons ago17:51
pittidobey: you can just download the deb and install it on anything >= precise17:52
dobeyoh i thought it was the latest. it was a month ago when i installed it anyway :)17:52
pittidobey: hm, trusty has 2.14, utopic has 3.6, vivid 3.9.3; so 3.0 isn't actually that easy to get :)17:54
dobeyi should set up a recipe for backports of it in my ppa17:54
dobeypitti: vivid only got 3.9.3 yesterday :)17:54
dobeyor well, tuesday17:54
dobeyoh, when did i install 3.0.117:55
dobeyweird17:55
dobeywhenever the last time you told me to install the latest version was, i guess :)17:56
dobeyi guess i should set up a backport recipe for it, to make life easier17:56
pittigit! git! git! :-)17:56
dobeyis there an upstream import of it into bzr? :)17:57
pittiDate:   Thu Jul 3 07:47:54 2014 +020017:57
pitti    Fix workaround for LP #133321517:57
ubottuLaunchpad bug 1333215 in ubuntu-app-launch (Ubuntu) ""Unable to find keyfile for application": clicks installed in current session don't create UAL cache, and UAL does not look for .desktop files in click pkgdir" [High,Triaged] https://launchpad.net/bugs/133321517:57
pittidobey: so the workaround for it was quite some time ago, but it landed in 3.117:58
pittiso 3.0.1 is only just a teensy bit too old17:58
dobeywell, whatever. SRU it or set up a backports PPA if you want people to always use the latest version :)17:58
pittivila has something like that17:58
pittigit import -> LP recipe17:59
vilagit clone <url> trunk17:59
vilabzr branch trunk feature18:00
pittivila: no, I mean your "crack of the day" autopkgtest PPA18:00
vilame too ;-)18:00
vilacd autopkgest ; git pull18:00
vilacd ../vila18:00
vilabzr pull18:00
vilatest18:00
vilabzr push18:00
vilatrigger recipe18:01
pittiah, ok; I thought you set up an automatic bzr import (these work rather well)18:01
vilabzr-git seems to work far better when dealing with a local repo than with a remote repo18:01
pittino, I mean LP does it all for you18:02
pittie. g. https://code.launchpad.net/~pitti/python-dbusmock/trunk is an automatic import of git18:02
vilaI don't do git push either (which is nice ;)18:03
dobeyand launchpad uses bzr-git18:03
dobeymanually pulling/pushing/etc seems like a pain in the ass for building a PPA package18:03
vilapitti: oh, for a backports PPA, sorry, missed that bit18:04
dobeypitti: lol. anyway, i updated and still get the keyfile error :-/18:04
* pitti uploads autopkgtest 3.9.4 to Debian sid, will auto-import into vivid tomorrow18:04
pittidobey: meh; I wonder if your click is slightly different than the calculator then18:04
pittidobey: feel free to open another bug and attach (or point to) click source and binary, then I can have a look on Monday?18:05
pitti(systemd hackfest tomorrow, and EOD today, sorry)18:05
dobeyoh18:05
dobeypitti: yes, payui isn't an actual app18:06
dobeypitti: so not your bug. i'll talk to ted about it18:06
tjaaltonzyga, tseliot: enabling opencl in mesa needs some packages moved to main first, and there is a plan to enable it once the MIR is done18:06
pittidobey: hm, still sounds related (or even identical) to #1333215?18:06
dobeypitti: nope18:06
dobeypitti: this doesn't have a "desktop" entry in the manifest, so there is no .desktop file in ~/.local/share/applications/ (and there isn't supposed to be)18:07
dobeypitti: so will have to figure out something special cased for this in our ap tests18:07
dobeypitti: so i'll talk to ted and leo about it18:07
pittiah, ok; cheers!18:08
=== alkisg is now known as work_alkisg
=== anthonyf is now known as Guest89771
=== work_alkisg is now known as alkisg
=== mwenning is now known as mwenning-rr5
=== alkisg is now known as work_alkisg
NoskcajLaney, Are you planning to package pinta 1.5 somewhere?19:39
=== neunon_ is now known as neunon
=== Bluefoxicy_ is now known as Bluefoxicy
=== danwest_ is now known as danwest
=== liam_ is now known as Guest91492
=== SpamapS_ is now known as SpamapS
=== salem_ is now known as _salem
=== work_alkisg is now known as alkisg
=== beisner- is now known as beisner
=== alkisg is now known as work_alkisg
=== jdstrand_ is now known as jdstrand
=== lionel_ is now known as lionel

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