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

aeorilHello! I am interested in becoming an Ubuntu developer - not apps, but Ubuntu itself02:02
aeorilI have bought the book "Tanenbaum, Andrew S.; Bos, Herbert (2014-04-02). Modern Operating Systems (4th Edition). Prentice Hall. Kindle Edition." to start learning OS theory02:03
aeorilbut it has lots of typos and I am not sure of how accurate it is.  I am interested in low-level stuff, like kernel, module, vm, etc.02:04
aeorilWhat are good resources to get a background in theory to work my way into this type of development?  I have a background in C programming in embedded real time systems and simulation systems, as well as dabbling in Unix/Linux drivers, modules, etc.02:06
aeorilkernel, module, drivers, vms, etc*02:07
aeorilNote that I am currently reading the Ubuntu documentation on development (based on the link in the topic of this channel).  My question above is more geared toward theory, architecture and design of operating systems such as one might get in a computer science curriculum02:24
hyperairwhat's the equivalent for udisksctl power-off -b /dev/sdb on a machine without udisks?03:24
hyperairnone of the /sbin/eject modes seem to do the right thing03:25
=== freeflyi_ is now known as freeflying
pittiGood morning05:16
pittihyperair: correct, ther is no equivalent; eject is the closest thing to it05:17
RAOFpitti: Is a vivid machine booted with systemd expected to be able to shutdown at the moment?05:50
pittiRAOF: yes, of course05:58
RAOFIn a related query, what are the interesting logs when it doesn't? :)05:59
pittiRAOF: /usr/share/doc/systemd/README.Debian has a section "Debugging boot/shutdown problems"06:00
RAOFAlso, systemd dramatically regresses boot speed for me, because it seems to want to write 0s to my 8GB swapfile in /var/cache/swapfile each boot. But that's a simple bug report.06:00
RAOFpitti: Ta.06:00
pittiRAOF: i. e. enable the debugging shell, shut down, then switch to it, and see which job is hanging06:00
hyperairpitti: ugh really06:10
pittihyperair: why "ugh"?06:10
hyperairpitti: because there's no proper eject tool aside from udisks?06:11
hyperairsomeone was asking on ##linux about usb_modeswitch06:11
pittieject works fine06:11
hyperairand i was trying to get him to manually eject it, but there wasn't udisks so...06:11
pittithe "power down the host controller" of udisks does even more, but it's more like a goodie than a required thing06:11
hyperairhmm06:11
pittie. g. for ipods and stuff which still warn if you merely eject06:11
hyperairkinda odd that we don't have an actual mass-storage eject tool though06:12
hyperairyou'd think that eject would get that functionality06:12
hyperairinstead of just doing a cdrom eject06:12
pittiwhat's missing in eject?06:12
pittiit doesn't just cd-rom eject06:12
pittiit also disconnects USB sticks, SD cards and the like, but just the medium06:12
hyperairoh yeah it does a scsi eject, which for some reason isn't the right kind of eject either06:12
pittinot the usb host controller06:12
hyperairit doesn't actually do a usb disconnect, does it?06:13
pittiusb-modeswitch is a special case for 3G sticks and the like06:13
hyperairyeah it is06:13
hyperairexcept sometimes it doesn't work, and all that's needed is a simple udisksctl power-off06:13
pittieject doesn't do an USB disconnect, no (as I said); it merely ejects the medium06:13
hyperairthat's the thing. i was kinda hoping for the usb disconnect stuff06:13
hyperairseems to be the kind of eject that usb devices actually expect06:14
pittimost of them don't06:14
pittiipods are pretty much the only one I know06:15
pitti(bbl)06:15
hyperairhmm okay06:15
darkxstapw, what is the status of bug 1410480? this completely breaks installing via ubiquity  on Ubuntu GNOME and probably most other flavours07:01
ubottubug 1410480 in linux (Ubuntu) "overlayfs v1: renaming existing file uses chardev whiteout (should be symlink)" [High,In progress] https://launchpad.net/bugs/141048007:01
darkxstand its alpha2 this week as well07:01
pittiyes, it's not flavor specific, happens for ubuntu as well07:02
darkxstpitti, how did it get though the automated tests then?07:03
darkxsthmm ubiquity autopilot tests havent run in 6weeks?07:04
pittiapparently yes, then07:05
=== seb128_ is now known as seb128
=== kickinz1|afk is now known as kickinz1
dholbachgood morning07:49
maclinHi,  Ubuntu Installer Team,  could someone help to review the merge request: https://code.launchpad.net/~maclin.jun/ubiquity/fix_1304410/+merge/24606408:03
ngaiois it reasonable to assume Ubuntu vivid will feature QT 5.4?08:11
LocutusOfBorg1hi people!08:20
Unit193Howdy.08:23
LocutusOfBorg1hi folks, quick question: I'm trying to fix 141150708:54
LocutusOfBorg1the problem: now the version in trusty is 4.3.10-108:54
LocutusOfBorg1since I'm the maintainer I'm preparing the debdiff with 4.3.10-1ubuntu1 rather than ubuntu0.1 as suffix08:55
LocutusOfBorg1is that ok?08:55
=== mthaddon` is now known as mthaddon
dholbach@pilot in09:17
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
ochosidholbach: in case you'll be reviewing xdg-utils MRs and you have any questions just lemme know!09:29
dholbachochosi, there is nothing for xdg-utils on http://reqorts.qa.ubuntu.com/reports/sponsoring/?09:30
ochosioh, i guess i need to subscribe ubuntu-sponsors on https://code.launchpad.net/~ubuntu-branches/ubuntu/vivid/xdg-utils/vivid/+activereviews09:30
dholbachno, that shouldn't be necessary - that's just for bug reports09:31
dholbachlet me see09:31
pittiit's already approved, maybe that's why?09:31
dholbachyes, but it wasn't landed09:32
dholbachseb128,  can you comment on https://code.launchpad.net/~ochosi/ubuntu/vivid/xdg-utils/drop_xserver_patch/+merge/246101?09:32
dholbachhttps://code.launchpad.net/~thad-fisch/ubuntu/vivid/xdg-utils/lp1363540/+merge/246820 was approved by ochosi (who doesn't have upload rights)09:32
seb128dholbach, I already did?09:32
dholbachseb128, it wasn't landed AFAICS09:32
seb128dholbach, no, just approved09:32
dholbachright09:32
dholbachthat got it off the sponsoring list09:33
seb128feel free to upload it09:33
seb128I just didn't get to it yet09:33
seb128what, approving?09:33
dholbachI wasn't complaining09:33
dholbachyes09:33
seb128why?09:33
seb128the intend was to say "it's ready to be sponsored"09:33
dholbachI tried to point out a workflow issue09:33
seb128to "it has been uploaded"09:33
seb128thanks for that09:33
seb128I though that only "merged" would get it out of the list09:33
dholbachright09:34
dholbachI'll take a look at the sponsoring script and see what the result would look like if we had "approved" MPs on there too09:34
seb128thanks09:35
* ochosi apologizes if he has caused any sort of inconvenience here09:35
seb128sorry for the mistake, and thanks for pointing it out09:35
seb128ochosi, no, not at all09:35
dholbachno worries09:35
seb128I just assumed that if I reviewed without having the slot for actual upload it would still be useful09:35
seb128I didn't get that it would get it out of the list09:35
ochosiactually that's good to know09:38
ochosii'll keep that in mind too09:38
ochosii obviously made a similar mistake (even without having upload rights, i thought reviewing/commenting the code/MR would be useful)09:38
dholbachI'll play around with the sponsoring script now and let you know if the world breaks, if we add 'Approved' MPs as well.09:39
dholbachochosi, no, I think it's great that you added your support for it09:39
ochosioh ok, so just to get the most out of this: was it ok (procedure-wise) to come here and ask the current pilot? or what could i have done differently not to disrupt your workflow09:40
dholbachochosi, yes, that was perfectly fine :)09:45
dholbachochosi, I didn't expect the MP to fall off the radar when seb and you set it to 'Approved'09:46
dholbachso I'm just checking if there's a good way to fix the sponsoring overview :)09:46
ochosisounds good :)09:46
LaneyThere's probably loads of approved-not-merged UDD branches09:46
dholbachLaney, yes, probably09:47
dholbachseb128, Laney, http://paste.ubuntu.com/9783833/ changed our list from 57 to 69 requests, with no xdg-utils MPs among them.......10:14
dholbachhum10:14
apwdarkxst, still broken at the moment, working on it10:15
seb128dholbach, seems like a managable difference, do you know why xdg is missing still?10:16
dholbachno, no idea10:16
dholbachLaney, seb128, could it be that "review requested from <ubuntu-branches or something>" is missing on both xdg-utils MPs?10:17
dholbachlike on https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/246772 for example10:18
seb128could be10:18
seb128shouldn't that be added by default though?10:18
dholbachyeah10:18
LaneyI think that a person takes over a team's review when they perform it10:18
seb128or is that because ochosi added me specifically for review?10:18
Laneymaybe10:19
Laney?10:19
seb128oh?10:19
dholbachochosi, do you remember if you changed something in the "reviewer" settings or requested a particular review from somebody?10:19
dholbachLaney, I always thought that it was added10:19
ochosidholbach: yes, because i had worked with seb128 on xdg-utils merges before, i specifically requested his review10:19
dholbachlet me see what happens if I can add jodh to xnox' MP10:20
ochosiand it's possible that brainwash (aka thaddäus tintentfisch) directly requested my review10:20
seb128ochosi, but did you remove the team from reviewers?10:20
ochosiseb128: no, not actively/willingly10:20
seb128k10:20
Laneyfor example https://code.launchpad.net/~laney/ubuntu-system-settings/as-activation/+merge/22595310:20
dholbachLaney, seb128: looks like it's added and not replacing ubuntu-branches: https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/24677210:20
Laneythere's no team review10:20
Laneybut I wouldn't have requested seb128 explicitly there10:21
dholbachLaney, maybe because it's not source package branch?10:21
dholbachs/not/no10:21
Laneydoubt it10:21
Laneyone sec10:21
seb128dholbach, I think what Laney is saying is that if a member of the team does a review and set approve, launchpad considers the review done and replace the team by the reviewer10:21
seb128Laney, something like that?10:22
dholbachahh ok10:22
Laneyya10:22
dholbachwhich.... for https://code.launchpad.net/~thad-fisch/ubuntu/vivid/xdg-utils/lp1363540/+merge/246820 wouldn't quite explain it10:22
dholbachit's even still in "Needs review"10:22
Laneyif you're looking for all MPs which ubuntu-branches has a requested review on then that won't be returned10:22
Laneyis that what the queue is doing?10:22
dholbachLaney, yes - I think that's the only way how we can get a list of MPs10:23
seb128dholbach, Laney, one other possibility is that when you file a mp and directly put the reviewer on the filing page, then it leads to not have the default reviewers added10:23
seb128rather than filing and adding a reviewer then10:23
dholbachmight be, yes10:24
Laneyhttps://code.launchpad.net/~laney/ubuntu/vivid/0ad/test/+merge/24687310:24
Laneyreview that please10:24
* seb128 tries10:25
seb128ja10:25
seb128that replaced the team10:25
seb128Laney, also, https://code.launchpad.net/~seb128/gallery-app/some-translations-tweaks/+merge/24687410:25
seb128that's buggy but I picked one of my vcs and mp it selecting you as reviewer in the optional entry on the mp filing page10:26
seb128the team is not there, only you10:26
Laneythat replaces the default10:26
Laneyit's probably by design there10:26
Guest67718That's correct.10:26
=== Guest67718 is now known as wgrant
seb128right10:27
xnoxdholbach: ubuntu-branches is default, at proposal time one can choose someone else to review (in that case ubuntu-branches is removed)10:27
wgrantIt's rather odd, but that's the way it is.10:27
seb128which I guess is what happened on those xdg-utils reviews10:27
xnoxdholbach: i typically keep ubuntu-branches and add extra people, that I would like to notify10:27
ochosiso, i should have not requested a reviewer when filing the MR but instead added one on top of the default?10:27
=== wgrant is now known as Guest24387
seb128ochosi, correct10:27
xnoxdholbach: however, i have the benefit of knowing plenty of relevant people to notify.10:27
ochosiok, good to know10:27
Guest24387The field on the MP form replaces the default reviewer, and once a team member reviews it the team request is replaced with a review from that person.10:27
dholbachhum, so we don't have a good way of finding MPs which have had ubuntu-branches removed :)10:27
seb128ochosi, yeah, some of us learnt something today ;-)10:27
=== Guest24387 is now known as wgrant_
xnoxdholbach: apart from iterating across all open MPs..... not really10:28
ochosiseb128: hehe, indeed. i'll see that knowledge gets passed on in the xubuntu team10:28
LaneyIs there an API way to find all ubuntu-branches MPs which are 'Needs Review'?10:28
seb128ochosi, thanks10:28
dholbachLaney, yes, that's what we're using10:28
wgrant_Laney: ubuntu-branches in which sense?10:28
LaneyAs target10:28
wgrant_As branch owner, or as reviewer?10:28
Laneythat's what lp:ubuntu/... is an alias too, right?10:28
Laneyto10:28
xnoxpitti: i'm failing to create or start ubuntu-emulator on vivid, with a vivid image.10:29
xnoxam I missing something obvious?10:29
xnoxhttps://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/141226110:29
ubottuLaunchpad bug 1412261 in goget-ubuntu-touch (Ubuntu) "can't create emulator instance on vivid" [Undecided,New]10:29
xnox"Can't create tempfile to create emulator instance"10:29
xnox$ sudo ubuntu-emulator create --arch armhf --channel ubuntu-touch/devel-proposed --revision 68 vivid210:29
pittixnox: oh, it's been ages since I tried armhf; it's utterly slow, I only use i386 (the defualt)10:30
xnoxpitti: i386 also fails10:31
* xnox ponders if i need to create a magic directory somewhere for it to work.10:31
pittixnox: creating one again10:36
pittiit was working just fine until Friday, for months anyway; but maybe something broke over the weekend10:36
pittixnox: do you have a full /tmp/ or anything like thatZ?10:37
=== wgrant_ is now known as wgrant
LocutusOfBorg1dholbach, pitti do you have time for a virtualbox/trusty review?10:50
LocutusOfBorg1https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/141150710:50
ubottuLaunchpad bug 1411507 in virtualbox (Ubuntu) "virtualbox-guest-dkms 4.3.10-dfsg-1: virtualbox-guest kernel module failed to build [error: 'generic_file_aio_read' undeclared here (not in a function)]" [Undecided,New]10:50
LocutusOfBorg1I fixed the bug ;)10:50
dholbachI'll check it out in a bit10:51
LocutusOfBorg1oh and BTW I added some packages here https://bugs.launchpad.net/ubuntu/+source/poedit/+bug/140828510:51
ubottuLaunchpad bug 1408285 in kbuild (Ubuntu) "Please sync kbuild, virtualbox and virtualbox-guest-additions-iso from debian/experimental" [Undecided,Incomplete]10:51
LocutusOfBorg1(kbuild is still being worked in debian by me)10:52
dholbachhum... ok10:52
dholbachubuntu-sponsors is not subscribed, let me re-add it10:52
LocutusOfBorg1thanks! :)11:06
=== _salem is now known as salem_
=== jpds_ is now known as jpds
=== kickinz1 is now known as kickinz1|afk
LocutusOfBorg1dholbach, did you test virtualbox? :)11:54
dholbachLocutusOfBorg1, it's taking a bit longer to set up everything with trusty11:54
dholbachare you in a hurry?11:54
LocutusOfBorg1nope, just wonderinf if you were taking a look or not, sorry but I'm currently working on other 10 packages, and I forgot really soon things :)11:56
dholbachsure, take your time11:56
LocutusOfBorg1so can I forget about that bug, right? (until I get some mails)11:56
dholbachyes11:57
LocutusOfBorg1wonderful thanks11:58
LocutusOfBorg1do you think 3.18 will be backported to trusty too? just to cherry-pick something more, to step ahead the next build failure :)11:59
apwLocutusOfBorg1, v3.18 likely will not be backported to trusty, there will be an lts-vivid with whatever vivid has at release12:05
apw(which is looking currently like it would be v3.19)12:06
LocutusOfBorg1so apw the answer was "yes", but the question was "wrong" :)12:06
LocutusOfBorg1I mean, somebody will have that kernel and the build failure with virtualbox then12:07
apwLocutusOfBorg1, heh, very likely yes in the future, cirtainly i do already :)12:07
LocutusOfBorg1do you have any ppa for it? this way I can proactively fix also that build failure :)12:08
dholbachLocutusOfBorg1, so I created a trusty chroot, updated to the latest, installed virtualbox and linux-generic-lts-utopic (which has 3.16), but I don't see the issue happening......12:09
dholbachdid you try this too?12:10
LocutusOfBorg1dholbach, nope I have a real machine and a virtualbox machine12:11
LocutusOfBorg1I tried and it failed12:11
LocutusOfBorg1chroot might not be enough ( pitti has something to say about the topic :p )12:11
=== MacSlow is now known as MacSlow|lunch
dholbachok... how do you reproduce the issue?12:11
LocutusOfBorg1try uname -a in the chroot, you will likely have the "host" kernel12:11
pittiof course, chroots don't have their own kernel; but you can install various linux-headers-* packages to build against12:12
LocutusOfBorg1I install trusty in a VM, update the kernel, reboot with the new one and install12:12
LocutusOfBorg1I found that having a VM, was easiest for testing and reproducing the issue ;)12:12
LocutusOfBorg1pitti, I tried also this solution, but for some reasons I didn't investigate virtualbox-dkms was picking the wrong kernel12:13
LocutusOfBorg1maybe because it does an "uname -a" to know the version to build modules against?12:13
dholbachah ok12:13
pittiyeah, probably12:13
LocutusOfBorg1I think you can force the version somewhere, but again, I didn't investigate since setting up a VM takes less time :)12:14
pittiit might only build against the current kernel, not all instlaled linux-header-* ones12:14
LocutusOfBorg1and I think makes me more confident about the issue12:14
apwLocutusOfBorg1, dkms should build against the kernel version of the headers/image you are installing, not the runnnig kernel12:18
apwLocutusOfBorg1, that is passed into the dkms incantation, and dkms packages themsleves should not be using uname to work out the version to use12:18
apwLocutusOfBorg1, or is this on upgrade of the dkms package itself12:20
LocutusOfBorg1apw, yes, but "uname -a" was just a guess, I don't know what are they actually using, so your solution might be perfectly correct12:20
apwdholbach, you do need to install the dkms package before the headers to get the right version build12:21
LocutusOfBorg1nope apw I'm talking about virtualbox-guest-dkms12:21
LocutusOfBorg1not dkms itself12:21
apwin a chroot context12:21
LocutusOfBorg1wonderful apw :)12:21
tseliotapw, LocutusOfBorg1: if dkms packages call the right DKMS template (/usr/lib/dkms/common.postinst), they will pick up the correct kernel version12:21
tselioteven in a chroot12:22
tseliot(nvidia and fglrx do this in their postinst scripts)12:22
apwtseliot, so they would, that is a postinst and 3/412:23
tseliotapw: I'm not sure I follow you12:24
apw(oh i was just agreeing and saying, "man that is a long postinst fragment"12:24
tseliotapw: hah, thanks, I worked on it myself :)12:25
apwtseliot, i noticed :)12:25
apwdarkxst, ok ... i've just uploaded a casper change to move to proper overlay, which should avoid the overlayfs issue which is breaking live boot12:28
apwdarkxst, i am still working the original issue in the kernel12:29
sittercyphermox: upstream plasma-networkmanager dev asks when we are going to land networkmanager 1.0. will it be 15.04 or 15.10?12:38
=== Malsasa_ is now known as Malsasa
mlankhorstdo I need a MIR for clang? because the llvm source package is already in main..12:54
seb128mlankhorst, if it's a binary from a source already in main, no12:58
mlankhorstok12:59
=== kickinz1|afk is now known as kickinz1
rsalvetipitti: I'm getting a race when starting whoopsie on latest ubuntu-touch image (vivid)13:04
rsalvetipitti: seems it's not started by the upstart job13:04
rsalvetiremoved the start line from the upstart job and it still got started, which would explain the race13:04
pittirsalveti: so there's something else that runs "start whoopsie"?13:05
pittior service whoopsie start or whatever13:05
rsalvetipitti: from ps it's not running with -f, just get /usr/bin/whoopsie13:05
rsalvetiwonder if https://launchpadlibrarian.net/195012178/whoopsie_0.2.43_0.2.44.diff.gz made any difference13:05
rsalvetiright13:05
pittirsalveti: oh, it could actually do13:05
ogra_pitti, seb128 suggested there would perhaps be some dbus activation13:06
pittirsalveti: I uploaded that as I started the emulator and saw the error message from init-d-script13:06
seb128ogra_, in fact not likely, just checked13:06
ogra_ah, k13:06
pittirsalveti: no, whoopsie doesn't listen on dbus13:06
ogra_just wanted to carry the info along13:06
pittirsalveti: so something indeed starts the init.d script13:06
rsalvetipitti: hm, what was the emulator error?13:06
seb128whoopsie-preference is the one which has a dbus service13:06
rsalvetipitti: yeah13:06
pittirsalveti: I just saw init-d-script complaining about a malformed $DAEMON13:07
rsalvetioh, ok13:07
pittibut not what tried to start it13:07
rsalvetiso you fixed the script and that caused the race13:07
pittirsalveti: so, we've had the broken init.d script for ages, and indeed it's not supposed to be started in the first place13:07
rsalvetiright13:07
pittithe phone does have the LSB hook to divert calling /etc/init.d/whoopsie to upstart, which makes this thing even weirder13:08
pitti/lib/lsb/init-functions.d/01-upstart-lsb13:08
pittiso, we can certainly "break" the init.d script again, or even drop it, but this might happen to other init.d scripts too13:09
rsalvetiyeah13:09
pittirsalveti: initially I thought this was just a side effect of running with systemd (which I did on Friday), I wasn't aware it also happens under upstart13:09
rsalvetimaybe something is broken with that LSB hook13:12
rsalvetibut guess that would cause some other bad side effects13:12
pittiyeah, it would mean that other init.d scripts woudl run too13:12
pittiI can't imagine something specifically calling the whoopsie init.d hook outside the boot process itself13:13
pittii. e. /etc/rc2.d/*13:13
pittis/hook/script/13:13
xnoxand whoopsie-preferences does not start whoopsie?13:13
shadeslayermvo: pitti could one of you approve https://code.launchpad.net/~rohangarg/synaptic/bug1375786/+merge/24400513:23
shadeslayerbeen over a month13:23
rsalvetipitti: added a debug line in /lib/lsb/init-functions.d/01-upstart-lsb and it didn't check for the whoopsie job (it did for quite a few others)13:24
mvoshadeslayer: ups, sorry, let me merge/upload13:25
shadeslayermvo: thanks alot, can we also get a SRU fix for Utopic?13:26
shadeslayerwould be supremely awesome13:26
shadeslayermvo: tbh I'm not entirely sure if we need 2 desktop files13:27
shadeslayerhttp://paste.ubuntu.com/9785018/ < diff between the 2 desktop files13:27
shadeslayernot sure what X-KDE-SubstituteUID is13:27
mvoshadeslayer: I think that had the effect to start it with sudo, but I have little knowledge of kde, so if kde can use the normal file, that would rock13:28
shadeslayermvo: we do have a pkexec helper13:28
shadeslayermvo: just a sec, just let me use the normal file and see what happens13:29
mvoshadeslayer: ok13:30
dholbachLocutusOfBorg1, I'll change the version number to 4.3.10-dfsg-1ubuntu1, ok?13:31
dholbachapart from that it looks good to me13:31
shadeslayermvo: yeah , I'd just nuke the kde desktop file, the regular one works in Plasma 5 on vivid13:32
mvocool, I will push that to vivid13:35
shadeslayermvo: thoughts about what to do for utopic ? just use the synaptic-pkexec patch?13:36
shadeslayer( Also, just throwing it out there, you probably want to remove the NotShownIn line in the regular desktop file )13:38
mvoshadeslayer: if someone could test if dropping the synaptic-kde.desktop file (and removing the "not-show-in=kde" works for utopic as well I would prefer to also drop the file there13:38
mvoshadeslayer: http://bazaar.launchpad.net/~synaptic-developers/synaptic/trunk/revision/2167 :)13:38
shadeslayermvo: I can do that13:39
mvoshadeslayer: great, please let me know and I can do the SRU13:40
shadeslayerawesome, give me 20 mins13:40
Riddellarmhf builders all broken?13:43
shadeslayerRiddell: seems to be working fine https://launchpad.net/ubuntu/+source/kio-extras/4:5.1.95-0ubuntu3/+build/673101513:44
Riddellooh they just caught up, good good13:45
cjwatsonRiddell: There was a power issue earlier that took them all out, but they've been back for most of an hour now.13:45
shadeslayercjwatson: did someone trip over a power strip :P13:45
cjwatsonshadeslayer: Not as far as I know :-P13:45
rbasakI think they're all in one chassis, aren't they?13:46
rbasakNo need for a power strip :-)13:46
cjwatsonThere was some scheduled power maintenance but then some systems weren't quite as dual-power as one might hope.13:46
=== Malsasa_ is now known as Malsasa
cjwatsonAnd yes, the LP non-virt ARM builders are all in one chassis.13:47
shadeslayercurious, does anyone know how to pass a env var to the schroot setup scripts? I have a script that needs to read a env var that Jenkins sets13:48
svenxshadeslayer: schroot(1) explains it in its ENVIRONMENT section (bottom)13:51
svenxref environment-filter13:51
shadeslayersvenx: isn't that explcitly to filter out env variables13:51
shadeslayerI want to whitelist something13:51
svenxhm, true13:52
svenxthe text is ambiguous13:52
shadeslayerquite :)13:52
svenxrelated: https://bugs.debian.org/66627413:54
ubottuDebian bug 666274 in schroot "schroot complains about unknow source-root-groups config entry" [Minor,Fixed]13:54
svenx"Arbitrary options may now be set in a chroot definition in schroot.conf.  These options are also set in the environment when running setup scripts, making this a simple means by which setup scripts may be customised without writing code."13:54
=== MacSlow|lunch is now known as MacSlow
xnoxcjwatson: i'm not going into the datacentre this time around.... i did leave a note that most things are single-power.13:58
shadeslayersvenx: aha figured it out14:01
shadeslayerthx14:01
shadeslayerthis is awesome :314:01
ngaiohi everyone! Is it safe to assume that Qt 5.4 is a certainty for inclusion in Vivid?14:04
pittirsalveti: ok, that indicates that something was calling it as /etc/init.d/whoopsie instead of /etc/rc2.d/S??whoopsie14:08
dholbach@pilot out14:12
=== udevbot changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
shadeslayermvo:  seems to work in utopic as well14:39
shadeslayerplz go ahead and nuke it14:39
cyphermoxsitter: I am landing 0.9.10 today; will get started on 1.0 right after that's done14:41
sittercyphermox: awesome. do you think 1.0 is going to make it into 15.04?14:44
sturmflut-workIf anybody has ideas about https://sturmflut.github.io/linux/ubuntu/2015/01/17/unprivileged-icmp-sockets-on-linux/ or https://sturmflut.github.io/linux/wireless/2015/01/19/designing-a-wifi-analyzer-app-for-ubuntu-touch/, please do let me hear them14:47
sturmflut-workWould be nice to know that I am completely wrong and there are other solutions14:47
cyphermoxsitter: yes14:48
sittercyphermox: groovy, thanks for the info :)14:48
* xnox ponders to switch to CIRC irc client15:06
didrocksxnox: hey! so, on your email about systemd local bridge… I guess you will have to create virtual units for value then. (that's what I told you on the hangout on Friday, that I doubted * would work)15:08
xnoxdidrocks: correct, if there are virtual values in fact. cause in other places it seems like a forward-looking glob rather than a required one.15:09
xnoxdidrocks: but that means someone needs data/values for those, and then in the hw-override tarball or the android config do15:10
didrocksxnox: yeah, it doesn't reevaluate15:10
xnoxpostinst15:10
xnoxsystemctl enable android-container@foo.bar=val1.target15:10
xnoxsystemctl enable android-container@foo.bar=val2.target15:10
xnoxsystemctl enable android-container@foo.bar=val3.target15:10
xnoxas needed.15:10
didrocksyeah :/15:10
xnox.... adn then template the job as well....15:10
didrocks(btw, I would prefer android-property, as the property is accessible outside the container… but it's just a matter of taste ;))15:11
didrocksyeah, quite tricky…15:11
xnoxi guess one only needs systemctl enable adb@val1.target, which should have wanted by = android-container@foo.bar=%i.target15:11
xnoxdidrocks: "android-container" is a configurable string. In the upstart job it was "upstart-local-bridge --event android-container"15:12
didrocksah ok, it's the parameter :)15:12
xnoxdidrocks: we can totally change the systemd unit to do "--event android-property"15:12
didrockswell, just a suggestion, but great it's easy to change15:12
xnoxwhich in systemd world means "the name of the template target"15:12
didrocksyeah15:12
xnoxdidrocks: however ogra_ didn't get back to me with names of targets. And i don't have all the phones to check / test these.15:13
xnoxdidrocks: unless come CI thing has a dump of all the "getprops"15:13
xnoxs/come/some/15:13
didrocksxnox: actually, we can go the other way around, units knows what property they expect15:13
didrocksand so, you scan the .service with WantedBy=15:14
didrocksand only expose/enable them dynamically?15:14
didrocksthat would avoid creating tons of unwanted unit properties…15:14
* didrocks tries to create a WantedBy= on unexisting target15:15
xnoxdidrocks: if the wanted by has the full name of the target, that one gets enabled, yes.15:15
xnoxdidrocks: that's how it currently works, it's just one cannot have a glob in it.15:15
xnoxlike what's currently used in upstart: maybe with, maybe without reason.15:15
xnoxadbd.service should list all the wantedby's it wants to trigger on. If we need globbing, then I guess the upstart-local-bridge can15:16
xnoxinstead of activating: a-c@a.b.c.d=foo1.target15:16
xnoxactivate:15:16
xnoxa-c@a.b.c.d=foo1.target a-c@a.b.c.d=foo.target a-c@a.b.c.d=.target a-c@a.b.c.target a-c@a.b.target a-c@a=foo1.target15:17
xnoxbut imho that's ugly.15:17
didrocksyeah, it is :/15:17
xnoxi think it would be ok for, e.g. adbd.service if it needs "a-c@propery=adb[0-9]*.target" to make itself adbd@.service "WantedBy = a-c@property=adb%i.target" and do systemctl enable adbd@`seq 0 100`.service15:19
xnoxtemplated instance .service <- 1 to 1 -> templated property instances15:20
didrocksxnox: I don't get why you don't rather do that:15:20
xnox?15:21
didrocksadb.service -> WantedBy=a-c@adb.target15:21
didrocksthen, the bridge look at the target in systemd memory15:21
didrockssorry WantedBy=a-c@property=adb.target15:21
xnoxand do the globbing on the bridge?15:21
didrocksget that it needs to fetch and monitor "property"15:21
didrocksyeah15:21
didrocksand so, create that target/start/stop it as needed15:22
didrocksthat way, you only create the targets that are needed on the system15:22
xnoxi'm ok to implement that, however i would adb.service then list:15:22
* xnox has no systemd-escape on this machine15:22
didrocksdon't worry ;)15:22
didrocksI know about it15:22
xnoxWantedBy=a-c@property=adb*.target15:23
xnoxwhere * is the systemd-escaped code.15:23
didrocksand you escape the *15:23
didrocksyeah15:23
xnoxthen the bridge can tell appart what should and shouldn't be globbed15:23
didrocksright15:23
xnoxand it will start a-c@property=adb*.target & a-c@property=adb75.target15:23
didrocksand create and start the target15:23
xnox.... stars escaped.15:24
didrockswhich will then bring the unit15:24
didrocks(sure)15:24
xnoxyeah, the whole thing.15:24
didrocksnot sure if the API is good to list WantedBy targets15:24
* didrocks looks at what status says15:24
didrocks   Loaded: not-found (Reason: No such file or directory)15:24
didrocks   Active: inactive (dead)15:24
LocutusOfBorg1thanks dholbach15:25
LocutusOfBorg1:)15:25
=== roadmr is now known as roadmr_afk
didrocksnot sure, status doesn't know about it even if I enabled a unit which WantedBy= against it15:25
dholbachanytime15:25
xnoxdidrocks: correct.15:25
xnoxdidrocks: that's fine.15:25
xnoxdidrocks: as it's not loaded, start & stop the .target, then status will know about it.15:25
didrocksxnox: right, but how would you detect those patterns then?15:26
xnoxdidrocks: wantedby installs a file on disk, it's static and evaluated on the the instance start.15:26
didrocksxnox: you don't want to scan /etc/systemd/system/*target.d? :)15:26
xnoxdidrocks: i would have hoped systemd dbus api exposes wantedby's of the units themself.15:26
xnoxdidrocks: a-c@property=adb*.target15:27
didrocksxnox: yeah, I hope as well. I can just tell you status (which is talking through the dbus api to systemd) doesn't know :/15:27
xnoxdidrocks: readonly as WantedBy = ['multi-user.target'];15:27
xnoxdidrocks: so with d-feet  / gdbus one can query iterate all units (e.g. adbd.service) and check theirs wantedby=a-c@15:28
xnoxwe do parsing of all jobs a lot in bridges.15:28
didrocksxnox: oh, we have the WantedBy fields over dbus for each units?15:28
xnoxe.g. upstart-systemd-bridge & upstart-file-bridge iterates through all units and caches their start on / stop on.15:28
didrocksyeah, sounds good :)15:28
xnoxto do things with file & socket events.15:28
xnoxsimilar thing will be here.15:28
didrocksyeah15:28
xnoxalso will subscribe to NewUnit signal.15:29
didrocksand I guess on the android side, you have an event in the container when a property changes?15:29
xnoxdidrocks: there is no events  inside the android container.15:29
didrockshow do you track changes then?15:30
didrockslike I'm enabling developer mode15:30
xnoxsetprop -> changes shared bionic memory, we have a property-watcher daemon (bionic binary) running under android-init, that thing writes key=value pairs into the socket.15:30
xnoxthe socket is the one created by the upstart-local-bridge, and bind-mounted into the lxc container by lxc-android-config15:31
xnoxand that's how propery changes arrive at upstart-local-bridge.15:31
didrocksahah, tricky ;)15:31
xnoxdidrocks: upstart-local-bridge only listens to the container.15:31
xnoxdidrocks: as it's entirely android thing.15:31
xnoxdidrocks: ideally, we'd make systemd bionic aware and memory map android properities and expose them as native conditions.....15:32
xnoxbut my left half of the brain says that's crazy15:32
didrocksxnox: I guess for the transition period, reusing the local bridge is what makes more sense15:32
didrocksxnox: so, I guess we are mostly set on the solution in the least intrusive way? do you need any help on this?15:32
didrocksno hurry anyway, as Touch on systemd isn't for this cycle anyway (activation of it, we can have it nicely running in advance though :p)15:33
xnoxdidrocks: non-globbing bridge is in silo 0001, however i need it tested on the phone/emulator "does not explode under upstart, may do nothing under systemd"15:33
xnoxdidrocks: before i land it.15:33
xnoxand emulator is not giving me any joy at the moment15:34
didrocksxnox: yeah, I saw that, works nicely (amd64) here, freshly created on Friday15:34
xnoxdidrocks: do you mind dist-upgrade with silo 1, and boot with upstart / boot with android? and verify that it generally works?15:35
xnoxand e.g. you can see event with upstart-monitor when you do setprop under upstart15:36
xnoxand target under systemd?15:36
didrocksxnox: can do in ~20 minutes, finishing up some plymouth stuff first15:36
=== kickinz1 is now known as kickinz1|afk
didrockswill get back to you then :)15:36
=== mardy_ is now known as mardy
=== roadmr_afk is now known as roadmr
sturmflut-workI'm on 15.04 and at random times a day a popup will appear, requesting me to enter my password to change my user data. The "Details" section states "Action: org.freedesktop.accounts.change-own-user-data" and "Vendor:". I have now idea where this comes from, and if I just cancel it nothing happens. Any ideas?16:18
sturmflut-workCouldn't find a matching bug report, but it seems to be the same issue as mentioned in http://askubuntu.com/questions/562355/seemingly-random-authentication-is-required-to-change-your-own-user-data16:19
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr
didrocksxnox: after a "sudo setprop persist.sys.usb.config mtp", I see no new target with systemctl16:22
xnoxdidrocks: can you do that from inside android container?16:29
xnoxdidrocks: or for example boot emulator with upstart and "--debug" on the kernel command line and check that android events are generated with upstart16:30
xnoxdidrocks: are there any targets generated at all? systemctl status android-container@*.target ?16:30
xnoxdidrocks: possibly property watcher only works from container....16:30
xnoxdidrocks: i know that you can do $ socat - UNIX-CONNECT:/dev/socket/* persist.sys.usb.config=mtp16:31
xnoxdidrocks: maybe things explicitely echo stuff into the socket inside the android container.16:31
mvoshadeslayer: thanks,  I am very busy right now, would you mind reminding me again tomorrow if I haven't acted on this by then? sorry, work is very busy right now16:34
shadeslayermvo: sure, I understand, it'd just be nice to have it fixed soonish, one of our downstreams has a release soon and would be nice to get it in16:34
didrocksxnox: actually, the bridge isn't started… what is supposed to start it? I don't see any upstart job doing that16:36
pittiapw: oh, "overlay" != "overlayfs" :) thanks for the casper fix/workaround!16:36
pittiapw: that avoids the weird char dev issue on renaming?16:36
mvoshadeslayer: yeah, if someone could prepare the sru diff (should be really) easy that would make it much simpler for me, a review/dput is quick for me16:36
shadeslayermvo: sure, I can do that16:37
apwpitti, yes it should avoid it for new overlays such as those which the installer makes16:37
apwpitti, i am working on, actually testing the heck out of, a fix for the V1 support separatly from that16:38
pittiapw, the rescuer of alpha-2!16:38
apwpitti, the breaker of perhaps :)16:39
apwpitti, dunno if someone can respin something to test it sooner than tonight16:39
mvoshadeslayer: \o/16:39
pittiapw: heh -- I hope that overlay isn't an entirely new thing, but just the evolution of overlayfs?16:39
xnoxdidrocks: there are systemd unit and upstart job in lxc-android-config package16:39
pittiapw: the release team should be able to16:39
didrocksxnox: hum, I didn't see the upstart job, looking16:40
xnoxdidrocks: there is no stock upstart-job, as the user configures their own job with the required socket path & event name.16:40
didrocksxnox: I did the systemd unit in lxc-android-config, and I only started the container, (to mirror the upstart one)16:40
xnox /etc/init/upstart-local-bridge.conf16:41
xnoxand i don't see unit one sec.16:41
apwpitti, ack, have asked on #u-release ... it seems prudent to get ahead16:41
pittiapw: yes, absolutely16:41
pittiapw: it could in theory be hacked into break=casper-top, but that quickly gets tiresome16:42
xnoxdidrocks: and i did not upload lxc-android-config 0.215 well that's a fail.16:42
didrocksxnox: :)16:42
xnoxdidrocks: no idea where that upload is at now though.16:42
xnoxdidrocks: cause e.g. one needs upstart-bin to have local-bridge binary16:42
pittistgraber: you are TIL for ifupdown; do you plan to merge it?16:43
pittistgraber: if not, I'll upload it soon to provide the static-network-up counterpart for systemd16:43
didrocksxnox: works with the daemon started manually16:43
pittistgraber: (i. e. I'll add those as a network-online.target dependency)16:44
xnoxdidrocks: systemd or upstart or both?16:44
stgraberpitti: merging it is on my todo but not extremely high on it at the moment16:44
didrocksxnox: systemd only for now16:44
xnoxdidrocks: that's cool.16:44
didrocksxnox: how do I try the upstart ones? I'm not as upstart-savy than systemd :)16:44
didrocksas you create an event16:44
xnoxdidrocks: sudo upstart-monitor; trigger the same way you triggered for systemd -> should see things from upstart-monitor stdou16:45
xnoxdidrocks: sudo upstart-monitor; trigger the same way you triggered for systemd -> should see things from upstart-monitor stdout16:45
didrocksok :) uno memento!16:45
xnoxhowever i think it's fine to let upstart in, and then i'll upload fixed up lxc-android-config16:46
xnoxi don't have it locally anymore, so i'll have recreate16:46
didrocksxnox: hum, upstart-monitor is a gtk app?16:47
didrocksah, it's telling it's fallbacking to cli16:48
didrocksbut traceback :p16:48
didrocks    class UpstartEventsGui(Gtk.Window):16:48
didrocksNameError: name 'Gtk' is not defined16:48
* didrocks edits to avoid the traceback16:48
xnoxdidrocks: sudo upstart-monitor -n16:48
xnoxfor the non-gui version16:48
xnoxsorry forgot.16:49
didrocksxnox: yeah, it's puzzling that it's telling that it's fallbacking though :)16:49
didrockseven with -n, traceback16:49
didrocksso really an issue with the app/16:49
* didrocks fires vi16:49
xnoxdidrocks: yeah..... =/16:50
shadeslayermvo: https://launchpadlibrarian.net/195323505/patch16:51
didrocksxnox: hum, interesting, can't import Glib, despite having gir1.2-glib-2.0 installed on the phone16:54
xnoxdidrocks: apt-get install python -gi16:55
xnoxdidrocks: apt-get install python-gi16:55
xnoxno?16:55
didrocksxnox: not that, you are trying to import Gtk first16:56
didrocksthen, it bails out16:56
didrocksand so don't import the rest :p16:56
* didrocks will do some patches to upstart-monitor :)16:56
xnoxdidrocks: option easier = boot emulator with "--debug" on the kernel command line16:56
didrocksxnox: too late, running ;)16:56
xnoxdidrocks: that your emulator console will be full of upstart events.16:56
xnoxdidrocks: than your emulator console will be full of upstart events.16:56
didrocksxnox: 2015-01-19 16:59:14.398513android-container SOCKET_TYPE='unix' SOCKET_VARIANT='named' CLIENT_UID='0' CLIENT_GID='0' CLIENT_PID='17531' SOCKET_PATH='/dev/socket/upstart-text-bridge' persist.sys.usb.config='mtp'16:59
didrocks\o/16:59
xnoxcool.16:59
didrocks(needed to use socat, for some reason, couldn't lxc-attach to the container)16:59
didrocksxnox: so, seems to be good from my limited testing17:00
xnoxdidrocks: lxc-attach does not quite work on the android container - it's rootfs is unpacked into private tmpfs, which one cannot get into.17:00
xnoxdidrocks: so now i need to figure out which buttons to push for release.17:00
didrocksxnox: yeah, when I saw the "couldn't access to <mount point>", I reckoned that was the case :)17:00
didrocksxnox: ahah, I guess the publish one ;)17:00
didrocksor ask on #ubuntu-ci-eng17:00
didrocksxnox: so, filtering and globbing for the longer term solution, but seems like a nice step forward!17:01
xnoxdidrocks: well if https://ci-train.ubuntu.com/job/ubuntu-landing-001-2-publish/75/ fails then i'll ask stuff17:01
xnoxFinished: SUCCESS17:02
didrockssweet17:02
xnoxlooking good http://people.canonical.com/~platform/citrain_dashboard//#?distro=ubuntu&q=landing-00117:02
* didrocks waves good evening17:04
xnoxslangasek: looks like you are admin of ~ci-train-ppa-service can I get added to that team, such that I can dput packages into silos that are assigned to me?17:10
LocutusOfBorg1mdeslaur, hi, do you plan to merge openssl?17:25
LocutusOfBorg1I think we can almost drop all, since debian merged some ubuntu stuff17:25
mdeslaurLocutusOfBorg1: no, I'm waiting for when W opens17:38
mdeslaurLocutusOfBorg1: there are regressions and big changes in the current debian versions that I don't want for V17:39
LocutusOfBorg1ack, thanks for the reply! so I won't touch anything17:39
LocutusOfBorg1wonderful :)17:39
apwpitti, ok, a respin looks good, booted and installed ok here, so i think we are good should there be a milestone17:59
=== robbiew1 is now known as robbiew
Laneycjwatson / someone else: could you moderate my mail to u-d-a please? The one with the correct subject line spelling, not the other one. :)18:41
LaneyOh right, I can cancel it can't I18:41
rsalvetixnox: hey, mind updating lp:ubuntu/upstart with the content from the latest version that got uploaded?19:09
rsalvetiseem to be https://code.launchpad.net/~xnox/upstart/systemd-local-bridge/+merge/246772, but there is a conflict in there19:09
asaccjwatson: do you know if its normal that sshd doesnt start if one of the host keys referenced in /etc/ssh/sshd+_config is not avail?19:34
asacwonder because seems we gen these ed2... keys in openssh serer19:34
asacbut seems that cloud-init doesnt generate them :/19:34
asace.g. in code they only generate three19:34
asacso wonder how noone coudl have noticed and suspect there is a flag i am missing that will make sshd start ignoring that missing key19:35
asacseems you landed that key in trusty a year ago :)19:35
asacanyone else? :)19:35
asackirkland: you around?19:36
=== doko_ is now known as doko
=== roadmr is now known as roadmr_afk
cjwatsonasac: not at a proper computer right now, but from what I can make out from browsing sshd.c on my phone, that should result in an error being logged but the server otherwise continuing to start up fine, as long as you have *some* protocol-2-suitable host key available.  this is not behaviour governed by any flag as far as I can see.  I would need to see logs to tell you any more.20:46
cjwatsonLaney: done20:47
=== xerf_ is now known as dxerf
=== dxerf is now known as _xerf
=== roadmr_afk is now known as roadmr
=== salem_ is now known as _salem

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