/srv/irclogs.ubuntu.com/2015/05/21/#ubuntu-devel.txt

=== shuduo_ is now known as shuduo
pittiGood morning05:02
tjaaltonUnknown release wily05:30
tjaaltonwth?05:30
tjaaltontrying to upload05:31
wgranttjaalton: What said that?05:31
tjaaltondput05:31
tjaalton-ng05:31
wgrantSounds like out of date distro-info-data or similar.05:32
tjaaltonyeah, upgrading05:32
=== oSoMoN_ is now known as oSoMoN
=== work_alkisg is now known as alkisg
=== shuduo is now known as shuduo_afk
pittiinfinity: hey! do you happen to remember historic reasons why "mount" is split from util-linux?08:14
pittiinfinity: just because of the any vs. linux-any arch:, or something else?08:14
infinitypitti: No idea.  You'd have to ask lamont.  Or maybe whoever maintained it before lamont.08:14
pittiinfinity: thanks08:15
infinitypitti: Given that they're both required/essential, it does seem a bit silly, but is it causing harm?08:15
pittiinfinity: ah was considering to merge them, as the split seems unnecessary, and it's making it easier to move stuff around like 'mountpoint' without having to NMU sysvinit again08:16
pittiinfinity: so it's more like a "can we clean this up?" question, not really harmful08:16
infinitypitti: That statement didn't make much sense to me.  Oh, as in, moving mountpoint from X to Y and having to update a Breaks or Depends in sysvinit?08:17
pittiright08:17
infinityYeah, mountpoint should be in util-linux, not mount.08:17
pittiinfinity: ah, don't get too confused by that; having to update the Breaks: was mostly just what triggered the question why they need to be split in the first place08:17
infinityIf I was actually participating in maintainership, I would have noticed that. :/08:18
pittiright, that's what we need to fix, to get back mountpoint for !linux08:18
pittiand while we're at it, he wondered if we shouldn't just move everythign, and make mount transitional (and then fix the ~ 5 rdepends over time)08:18
infinitypitti: The split may indeed just be about linux and non-linux.  Or maybe something more subtle.  But it also seems to do no harm to have the split, so I'm a bit "meh" about rocking that boat.08:19
infinitypitti: That said, while I have strong opinions about lots of things, I'm not sure it's worth listening to the opinion of someone who hasn't had time for util-linux in ages.08:20
zygahmm08:27
zygasone of the recent updates broke virtualenv -p python3 on wily08:27
zygahttp://pastebin.ubuntu.com/11260203/08:27
zygalooks like it's in pip-1.5.608:28
* mgedmin wonders when ubuntu will get a more modern pip version08:28
zygahmm08:34
zygadidrocks, barry: ^^ (virtualenv broken on wily, you are the last two uploaders of pip, any ideas?)08:35
didrockszyga: was it broken on vivid?08:37
zygadidrocks: nope08:37
zygadidrocks: broke yesterday08:37
zygadidrocks: or so08:37
zygadidrocks: I'm on wily since day one, I don't rebuild my virtualenvs every day but I do do it often, so this broke very recently08:38
didrockszyga: maybe python 3.5?08:38
zygaoh08:38
zygadid we get it now ^_^08:38
* zyga looks08:38
didrocksseems so, yesterday at midnight08:39
zygaah08:39
zygaI don't have python3.5 in apt yet at all08:39
zygaso probably not that08:39
zygaor maybe package uploads are out of alignment and it will fix itself with 3.508:39
zygadidrocks: do you know if we build the wheel binaries out of the debianinzed packages or from original upstream wheels?08:41
didrockszyga: that's a question for doko_ I guess08:41
zygadidrocks: thanks08:42
didrocksyw, let's see once he's around08:42
=== oSoMoN__ is now known as oSoMoN
lamontpitti: I want to say it's just because of any vs linux-any10:26
mvopitti: hi, just a quick (and maybe silly) question - could autopkgtest for snappy also drive real beagleboneblack with the ssh driver? I would love to have working reboot tests for this as well and wonder how realistic this is10:26
lamontwhich is much cleaner than the fugly mess it used to be10:26
pittimvo: yes, should work; I've seen people run tests on a real BB in Austin10:27
pittimvo: the one thing you need to do is to add the "--- ssh --reboot" parameter (or -r), to tell autopkgtest that it's safe to reboot the testbed (we can't assume this for everything)10:28
pittilamont: thanks10:28
mvopitti: nice, I will add that10:28
pittimvo: (details @ http://www.piware.de/2015/05/autopkgtest-3-14-now-twice-as-rebooty/)10:29
mvopitti: my other question is that I assume autopkgtest support "embeding", i.e. main autopkgtest builds the deb, runs the tests, installs the new debs into a snappy VM, then fires up a snappy VM using adt that contains the new debs and runs the selftest in the image with the new snappy)10:30
mvopitti: cool, thanks10:30
pittimvo: I don't understand that10:31
mvopitti: sorry10:31
pittimvo: how is that different from --dsc or --unbuilt-tree? that would build the debs,  install them on the testbed, and run the tests10:31
mvopitti: maybe its not and I'm thinking too complicated :)10:31
pittimvo: that's assuming --setup-commands 'mount -o remount,rw /' of course (IOW, cheating)10:31
pittimvo: but, consider that you likely can't build anything *on* snappy, you should do that outside in a proper sbuild or so10:32
mvopitti: yeah, thats the think, I build/test outside of the snappy image, then want to run the selftest in a snappy image that contains the newly build debs10:33
mvos/think/thing/10:33
pittimvo: so the usual approach would be sbuild -s newsnappy.dsc; adt-run newsnappy_amd64.changes --- ssh ...10:33
pittimvo: or, more explicitly, adt-run *.deb -B newsnappy.dsc --- ssh ...10:33
pittirunning a binary .changes is the same as running all debs in it plus the tests from the .dsc in it10:34
mvopitti: ok, thanks. I will see what I can do (after lunch :)10:34
ahlamont: thanks for the background info w.r.t mount vs util-linux.10:38
=== alkisg is now known as work_alkisg
=== rickspencer3_ is now known as rickspencer3
=== _salem is now known as salem_
cjwatsondoko: Can you have a look at what's up with gcc* on http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150521-wily.html (still in progress)?  That's a test rebuild of main in scalingstack with modern sbuild.13:39
pitticjwatson: wohoo!13:40
dokocjwatson, the gcc-4.9-* are replaced by gcc-4-9-cross, working on it13:40
cjwatsonIf this works out OK we should be able to move all x86 builds into scalingstack in the next week or two.13:41
dokothe other one is a mismatch between an alternate b-d and what is actually used for building13:43
cjwatsondoko: gcc-5?13:43
cjwatsondoko: can you expand on that?13:44
barryzyga, didrocks https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78578713:45
ubottuDebian bug 785787 in python-distlib "[REGRESSION] python-distlib == 0.2.0-1 breaks virtualenv and tox" [Normal,Open]13:45
didrockshere we go :)13:45
zygabarry: thanks!13:45
dokocjwatson, gnat-5 gets installed, but gcc is called. should be gnatgcc-5 or gcc-513:47
cjwatsondoko: old sbuild would have done the same thing though, right?13:48
cjwatsonsince that's the first in a list of alternates13:48
cjwatsonwgrant: shouldn't we be using --resolve-alternatives, though?  I had a mental note that we needed that for equivalence with old sbuild but missed it in review13:48
dokoyeah, wondering why it showed up now, because it built before. and there is only gnat-5 in main, not gnat-4.913:49
cjwatsonwgrant: I suspect we'll see some things that are main Build-Depends: package-in-universe | package-in-main that now fail to build, but we'll see13:49
cjwatsondoko: seems to be installing roughly the same build-deps, just different versions13:55
cjwatsondoko: and lower parallelism because we're making different trade-offs in scalingstack, but I shouldn't have thought that would matter here13:57
cjwatson-checking for x86_64-linux-gnu-gcc... gnatgcc13:57
cjwatson+checking for x86_64-linux-gnu-gcc... gcc13:57
cjwatsondoko: aha14:00
cjwatsoncjwatson@pepo:~$ dpkg -c gnat-5_5.1.1-5ubuntu4_amd64.deb | grep bin/gnatgcc14:00
cjwatsonlrwxrwxrwx root/root         0 2015-05-13 16:41 ./usr/bin/gnatgcc -> gcc-514:01
cjwatsoncjwatson@pepo:~$ dpkg -c gnat-5_5.1.1-6ubuntu1_amd64.deb | grep bin/gnatgcc14:01
cjwatsonlrwxrwxrwx root/root         0 2015-05-19 21:13 ./usr/bin/gnatgcc-5 -> gcc-514:01
cjwatsonlatter presumably more correct but do you perhaps need to take account of it in the build?14:01
dokoahh, I see. I shouldn't rename gnatgcc to gnatgcc-5 then. the gnat packages conflict anyway14:02
dokostill waiting for feedback from ludovic brenta, he's very quiet recently14:02
cjwatsonyou'll presumably need to handle the existing name in order to build a fix :-)14:02
dokoyep, or just using gcc-514:03
dokohmm, just loged out, and after re-login, the vpn is still active?14:12
xnoxyes... it's network manager14:13
dokointeresting14:13
xnoxdoko: so stgraber runs VPNS in their own network namespace as a user-namespace container.... then the vpn is a user process as a whole.14:16
cjwatsontedg: Does the dbus-test-runner failure on http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150521-wily.html mean anything to you?14:40
* tedg clicks14:40
cjwatsontedg: (this is a test rebuild of main in scalingstack with modern sbuild; the main purpose is just to shake out problems related specifically to those changes before we make all of Ubuntu x86 build that way)14:41
=== gammax90 is now known as gammax
tedgcjwatson, It looks like a timeout of shutting down dbus. Not sure why scalingstack or sbuild would effect that.14:42
tedgcjwatson, The test harness makes sure the dbus connection closes, or it times out and errors.14:43
cjwatsontedg: I can retry if you think that might help.  Is it possible that it just has an unnecessarily low timeout?14:43
tedgcjwatson, Oddly, it's failing on the easiest test case :-)14:43
tedgcjwatson, That would be my guess, but it would be kinda surprising.14:43
cjwatsontedg: The entire build only took 1.5 minutes, so the timeout can't be that long14:44
tedgIt is something like 10 seconds.14:44
cjwatson(and that's including build-dep installation and such)14:44
cjwatsonit's not running on dedicated hardware, so I suppose it could have been scheduled out if the nodes are overcommitted or something14:45
cjwatsonretrying, scored up a bit so we get a chance to recheck soon14:45
tedgcjwatson, Great, thanks!14:46
=== Elimin8r is now known as Elimin8er
=== work_alkisg is now known as alkisg
xnoxdoko: i'm toying with boost here.... a no change rebuild with c++11 abi took out source-highlight with undefined symbols throughout.15:25
xnoxi'll do more tests, but it seems like we will have pain with boot.15:26
=== Malsasa_ is now known as Malsasa
=== alkisg is now known as work_alkisg
=== oSoMoN__ is now known as oSoMoN
=== adrian is now known as alvesadrian
mrmcq2uhttps://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/145584518:12
ubottuUbuntu bug 1455845 in pulseaudio (Ubuntu) "Pulseaudio sinks nightmare to navigate" [Undecided,New]18:12
mrmcq2uany thoughts?18:13
jamespageplease could an archive admin bump python3-greenlet to main in wily - its a binary only movement and is needed for new eventlet18:19
=== alvesadrian is now known as adrian
=== dobey_ is now known as dobey
=== Malsasa is now known as Guest79487
=== Malsasa_ is now known as Malsasa
cjwatsonjamespage: done20:22
jamespagecjwatson, ta20:37
=== salem_ is now known as _salem
Dragonkeeperhey guys23:08
Dragonkeeperim interested in if there is a way to install ubuntu on no standard hardware lacking a standard bios23:09
Dragonkeeperin this case a chromebook cb3-11123:09
sarnoldDragonkeeper: the iso images should do 64-bit uefi alright; 32-bit uefi may take more work23:27
Dragonkeepersarnold: im attempting to use chrubuntu script to boot from usb + seemed my firmware wasnt in dev mode even though the OS was . so see how this goes23:29

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