/srv/irclogs.ubuntu.com/2014/06/05/#ubuntu-devel.txt

cjwatsonxnox: Almost anything is more straightforward than that00:58
wgrantxnox: Oh, nice, WSGIProxy is exactly what I thought we'd have to implement.01:22
pittiGood morning03:40
Unit193Howdy, pitti.03:41
RAOFpitti: Aloha!03:41
pittiRAOF: ah, I forgot to check again yesterday03:42
pittiRAOF: so, it built fine03:42
pittiRAOF: it took over 2 hours, and at some point it just dropped off my brain03:42
pittiRAOF: do you want the debs/log/etc., or is "it builds" enough?03:42
RAOFIt builds is good for me.03:42
RAOFLet me push a tag for you to upload.03:43
RAOFpitti: debian/1.2.1-1 should be good to go to unstable. Let's get this transition on the road!03:54
pittiRAOF: ah, soname bump?03:54
pittiRAOF: hm, gbp-pull gives me nothing new03:55
RAOFTo git+ssh://git.debian.org/git/collab-maint/colord03:55
RAOF   3045b6b..3719f1b  master -> master03:55
RAOF * [new tag]         debian/1.2.1-1 -> debian/1.2.1-103:55
pittiok, so I was just blind, or gbp-pull didn't show me the new tag03:56
RAOFpitti: Yeah, a bunch of deprecated symbols got dropped in the 1.2 series, making it libcolord2 et al.03:56
pittiRAOF: quite impressive that on my box creating a profile takes ~ 20 seconds where on mips it takes about half an hour; I wasn't aware that these mips boxes were *that* slow..04:02
RAOFIt turns out that you can do a lot of computation with billions of transistors!04:04
infinitypitti: Which mips box is that?04:08
pittiinfinity: gabrielli.debian.org (the porter box)04:08
infinitypitti: The Cavium machine is pretty peppy, except for crappy I/O.04:08
pittiah, I stopped at the first "mips porterbox" on the db.d.o. page04:08
infinitypitti: And gabrielli is the machine I was thinking of.04:08
infinitypitti: Maybe I only think it's peppy, cause I build with -j1604:08
pittiinfinity: I built with -j8, but doesn't help much with colord as it doesn't parallelize the calculation04:09
infinityThe individual cores certainly aren't screamers (they're not meant to be, it's essentially a switch in a desktop case)04:09
pittiit has 16 cores04:09
RAOFinfinity: Yeah, profile generation is explicitly serial, as each profile takes over a GiB of memory to compute.04:09
pittiinfinity: yeah, I used to have one of these d-link linux routers, they were quite nice to hack on04:09
infinityRAOF: Ow.04:09
pittiRAOF: uploaded04:10
RAOFSo the relevant performance indicator is IPC :)04:10
RAOFTimes clockspeed, obviously.04:10
RAOFpitti: Much ta.04:10
infinitypitti: I'd love someone to talk me into doing an Ubuntu MIPS port some day, but we'd need a whole lot of gabrielli-sized machines to make it go, I suspect.04:11
infinityAt least, to provide the same SLA people are currently used to in LP and whine about when it degrades. :P04:11
RAOFVirtualise it on prodstack! :P04:11
pittithe internet of ubuntus!04:12
* RAOF loves how his copyright line doesn't fit in 80 characters04:13
infinityRAOF: Get a shorter name.04:20
=== plars is now known as plars-away
NoskcajCan someone please review https://code.launchpad.net/~noskcaj/libgweather/3.12.204:49
Noskcajcjwatson, Mind if i take the unzip merge?05:00
dpmhi wgrant, pitti is currently working on generating utopic langpacks for the phone, but as per the schedule we set up in LP, the next export is not due until Wednesday next week. In order not to have to wait until then, would it be possible to run a one-off export of translations for utopic today?06:12
dpmWe've done this in the past, e.g. when we needed exports outside of the crontab for a release, but I don't know the procedure for requesting these nowadays06:13
pittihey dpm06:15
dpmmorning pitti :)06:16
pittidpm: I refined the script to calculate source packages shipped on touch now, just committed to langpack-o-matic; now I'll work on generating langpacks based on that06:16
dpmexcellent!06:16
pittidpm: I think we don't do the -base/update split for touch06:16
pittiit makes little sense with image based updates06:17
dpmyes, I agree06:17
dpmpitti, do we have to change all universe packages in the list to be imported to LP? Can we determine beforehand which ones we need to import translations for?06:17
pittidpm: not necessary for building langpacks; they'll just contain the bits from main and with X-Use-Ubuntu-Langpacks (or whatever that magic key was)06:18
pittidpm: I suppose we could download all binaries from that pastebin, check if they have anything in /usr/share/locale; all which have mo files are candiates for importing06:19
dpmpitti, yes, but ultimately to have meaningful langpacks, well need the X-Use-Ubuntu-Langpacks (can't remember the exact name, either :) for their .mo files to be in the export to be fed to langpack-o-matic. So at some point, we'll either have to mark all the universe ones with X-Use-Ubuntu-Langpacks or do an initial filtering (e.g. with your latest suggestion) and only mark those that make sense to be imported06:22
pittiright06:23
pittidpm: but then we should also strip them06:23
pittiotherwise langpacks wouldn't have much effect06:23
pitti(only for new languages)06:24
dpmpitti, yes, but that's what X-Use-Ubuntu-Langpacks does already, IIRC - it strips them, imports the translations and then LP exports those06:24
dpmor were you suggesting something else?06:25
pittidpm: ah right, just checked; I thought we also had something like "export translation tarballs, but don't strip"06:25
pittibut I think we export tarballs for all builds06:26
dpmpitti, ah, no, I don't think we have a "don't strip" option06:26
dpmpitti, what do you mean by "all builds" in this context?06:27
pittidpm: I mean, I think we export _translations.tar.gz for all universe packages, we just don't strip them or export them from LP06:28
dpmpitti, ah, I didn't know that. Where are these universe translations tarballs exported to?06:29
pittidpm: to LP translations, as usual06:30
dpmoh, you mean they're generated as part of the package build, right? So you're saying you could use that to feed to langpack-o-matic instead of the big weekly Launchpad export?06:32
pittidpm: no, not at all; I'm saying we merely need to mark these packages as X-Use-Ubuntu-Langpacks:, and it should be all good then06:33
dpmok, gotcha06:33
pittidpm: so your web app shows that we have some 20 languages with coverage >= 70%; that might be a good set to start with?06:34
dpmpitti, yeah, once we get this up and running, I think I'd like to set the percentage to 80 or even 90%, but right now, 70% should be good to initially get some more languages in. Can langpack-o-matic do this calculation and filtering based on coverage %?06:35
pittidpm: not at the moment, but I'll teach it06:36
dpm:)06:36
pittidpm: not that simple to get the absolute number of translatable strings though, so it might need some handholding06:36
pittidpm: i. e. if I just look at a set of .po files, then I don't see the ones which don't have any translations at all06:37
pittidpm: I suppose your web app compares with the .pots ?06:37
dpmpitti, yes, I use the .pots to get the total, but currently all apps in that list are checked out to a local branch to calculate the stats, so I have access to the .pot files. However, langpack-o-matic could have some other options if it cannot access the .pot files directly06:39
pittidpm: I need to check whether the LP exports contain the pots06:40
dpm- Read the template stats from the daily LP translations data dump in JSON at http://people.canonical.com/~dpm/data/ubuntu-l10n/06:40
dpm- Use the LP Translations API - It's not complete, but the templates part is available. I can't recall if it does more than just listing template names per source package, though06:41
pittidpm: ah, nice06:41
pittidpm: i. e. in http://people.canonical.com/~dpm/data/ubuntu-l10n/trusty-potemplate-stats.json06:41
dpmpitti, exactly06:41
pittidpm: that would mean that accounts-service has 10 translatable strings?06:41
dpmI've got an RT open to get the utopic stats06:42
pittiand apt 62406:42
dpmpitti, indeed06:42
pittiok06:42
pittidpm: so the stats will be skewed a bit as we ship e. g. apt and gdb on the phone although they aren't "visible"06:42
pittidpm: implementing that will take some time, perhaps we start with a fixed list of language codes06:43
pittibased on your web app06:43
pittiit won't change every other week anyway06:43
dpm+106:43
wgrantdpm, pitti: Export is running.06:44
pittiwgrant: cheers06:44
dpmawesome, thanks wgrant06:45
debfxScottK, Laney: do we still need to enforce that trusty->precise backports end up in saucy too? is precise->saucy a supported upgrade path?06:45
dpmpitti, I'd use only the totals for the packages that we're considering as part of the UI. I've ran my stats webapp for source packages to calculate the distro translation coverage in the past, and I use the "priority" field to determine if it's a template whose translations are visible. E.g. anything with a priority <= 100 I'm not counting towards the total number of strings06:46
dpmand those priorities are set in LP, generally I go through the templates when we open translations and set them all up and tweak them afterwards if needed06:47
dpmpitti, a third option would be for me to add an API to my web stats to return the language coverage for each language06:48
dpms/language/translation/ coverage06:48
pittidpm: downloading a single .json file sounds fine to me06:56
dholbachgood morning06:58
dpmpitti, yes, whatever works best for you. I've also checked that you can get the string count from the LP API, so just to confirm, this is also an option you could use. https://launchpad.net/+apidoc/devel.html#translation_template06:58
dpm"message_count"06:58
=== evfool is now known as evfool-nr
=== evfool-nr is now known as evfool
mitya57Mirv: Good to know that!08:16
Laneydebfx: nope, indeed not08:16
cjwatsonNoskcaj: Would prefer to do it myself, thanks.09:00
=== doko_ is now known as doko
Noskcajok. I'll cancel my merge proposal then09:00
cjwatsonIn general I don't need help with my merges unless explicitly requested09:01
Noskcajok09:02
infinitydoko: Did you see my binutils ping?  You dropped my delta from http://launchpadlibrarian.net/173790298/binutils_2.24.51.20140425-0ubuntu1_2.24.51.20140425-0ubuntu2.diff.gz09:03
infinitydoko: Which is why the lintian testsuite is failing again.09:04
infinitydoko: You may also have dropped it from Debian, I didn't check.09:04
dokoinfinity, ouch. will reapply it09:05
infinitydoko: Ta.09:06
infinitydoko: Should probably add an autopkgtest that does the same thing as the lintian test (attempt to link -lm to a simple test program using ld directly) to make sure it doesn't regress.09:07
ogra_xnox, seeing your mail exchange with janimo ... didnt we say the non RTM devices will keep loop mounting ? so for these a proper image name definitely makes sense09:10
=== MacSlow is now known as MacSlow|lunch
pittiinfinity, cjwatson: do you know, do we still need pre-depends: for packages using xz compression? (it's the default now, but I'm also wondering about precise)11:19
pitti${misc:Pre-Depends} ought to take care of that?11:19
cjwatsonI think it was lucid-to-precise updates that needed that11:20
pittiok, thanks; these days dpkg doesn't generate any misc:Pre-Depends, but I guess it can't hurt to add it anyways11:21
pitticontext: langpack builds (so far they've been using bzip2, but that's now marked as deprecated)11:21
cjwatsondpkg wouldn't anyway, it was debhelper11:21
cjwatsonI think it dropped them a little while back11:22
cjwatsonBut yeah, for anything at all recent there's no need to keep them now11:22
pittiack, thanks11:22
cjwatsonMaybe for precise it's simplest to leave them as bz211:22
pittiI just tested it under precise, seems to work just fine11:24
pittibuild/install/lintian/etc.11:24
infinitylucid didn't support xz.11:24
infinitySo the pre-depends is needed on packages in precise.11:24
infinityIt's not needed in trusty.11:24
infinitypitti: ^11:25
pittiinfinity: thanks11:25
cjwatsonRight, even for packages in -updates, because otherwise we break lucid-to-precise upgrades which will likely have -updates enabled during the upgrade.11:28
cjwatsonIf dh_installdeb or whatever it was DTRT in precise then ${misc:Pre-Depends} would be simple enough.11:28
pittino, it doesn't seem to do that, it just sets it to empty11:29
pittiso I bumped the existing manual pre-dep now11:30
cjwatsonI guess it can't know since the compression method is set in options to dh_builddeb, which is too late to do anything to the control file.11:30
dpm_pitti, it seems that the langpack export was pretty quick this time. We've now got the first full langpack available at: https://translations.launchpad.net/ubuntu/utopic/+language-packs :)11:35
pittidpm_: oh, wow! that's just the *perfect* timing11:35
dpm_:)11:35
pittidpm_: I just started downloading the latest trusty langpack for testing my recent langpack-o-matic stuff on real data :)11:35
dpm_aha!11:36
pitti(so far I've just written test cases with the mini-tarballs in tests/)11:36
pittidpm_: cool, so utopic langpack time, too :)11:36
dpm_\o/11:36
pittiwgrant: and yes, that was mighty fast -- whatever you did, rock!11:37
pittiouch -- the whole unpack and import of the full translation tarball takes ~ 15 s on my machine, ~ 2 h on germanium; yay tmpfs..11:42
pittidpm_: http://paste.ubuntu.com/7594256/11:44
pittiogra_: ^ FYI: first iteration of -touch langpack is ~ 800 kB for German (which should have fairly good coverage), whereas the regular langpack is 3.6 (not including -gnome)11:45
pitti3.6 MB, I mean11:45
ogra_wheee !!!!11:45
* ogra_ hugs pitti 11:45
pittiogra_: and dpm determined we'll need some 20 or so (all languages with >= 70% coverage)11:46
ogra_well, as many as we can ship ...11:46
ogra_but that will reduce our size massively ... awesome news11:47
pittiogra_: there's still room for optimization here -- e. g. this ships translations for gdb, apt, etc. (see http://paste.ubuntu.com/7594256/)11:49
pittiand OTOH it does'n yet have many apps (we need to mark those in universe which we want to get included in langpacks and stripped)11:49
pittibut it's a first ballpark figure11:49
pittianyway, time for lunch :)11:49
dpm_pitti, that's awesome, thanks! I think that's good for the initial ones, but do you think we could do some further filtering in the next iteration? I see things such as colord, gdebi, libgweather-locations and others that we could probably drop.11:49
ogra_ah, well, we want to get the devices in the hands of developers ...11:49
ogra_i think it makes sense to keep that stuff in for now11:49
ogra_(gdb, apt etc)11:50
pittidpm_: yes, absolutely11:50
mlankhorstchrisccoulson: I've added a hack to the bug report in case you want to use nouveau, but I think it's too ugly to even propose it as a sru :P11:50
dpm_cool. pitti, also, could you add 'ca' to the list of langpacks generated? It's the locale I'm testing on (apart from zh_CN), but I'll make sure it gets to 70% before the stats are updated tomorrow :)11:52
pittidpm_: I currently built all, I still need to add a --languages feature11:52
dpm_ah, perfect11:52
pittior implement --min-coverage etc.11:52
chrisccoulsonmlankhorst, oh, it doesn't support gl from more than one thread. that kinda sucks :/11:55
mlankhorstchrisccoulson: the hack I wrote probably works though :P11:56
mlankhorstbut yeah I'd have to make things thread-safe in a cleaner way11:57
chrisccoulsonmlankhorst, I also need to implement the missing bits to make chromium's GPU blacklist work in oxide, so that we could disable the GL compositor and webgl12:04
chrisccoulsonthat would mean the only thread accessing gl would be the rendering thread for the qml scenegraph12:05
mlankhorstchrisccoulson: the hack makes nouveau thread safe enough not to crash12:05
chrisccoulsonbut that's a fair bit of work and I was hoping not to do it yet :/12:05
chrisccoulsonyeah, the issue is that it's not me with the crash (I don't have nvidia hardware)12:05
mlankhorstLaney: can you test?12:06
Laneytest what?12:06
mlankhorstLaney: hack from https://bugs.launchpad.net/nouveau/+bug/130904412:06
ubottuUbuntu bug 1309044 in xserver-xorg-video-nouveau (Ubuntu) "Unity webapps crash Ubuntu 14.04 LTS on my computer" [Undecided,Triaged]12:06
mlankhorstbut it requires libdrm 2.4.54 first, just grab it from debian or utopic12:09
Laneyi'm on utopic already12:09
Laneydo you have a package?12:09
mlankhorstno, just the diff, let me build one..12:09
Laneyit's okay12:09
Laneyassuming it applies12:09
Laneyi thought you could reproduce this yourself though12:10
mlankhorstyeah :p12:10
mlankhorstbut no idea if this breaks other things or not12:10
Laneymlankhorst: erm what is this a patch to? :(12:12
=== _salem is now known as salem_
mlankhorstmesa12:13
mlankhorstbut I'm upgrading my chroot, just give me a bit12:13
Laneyit's okay, building now12:14
pete-woodssil2100: hi, I've done the testing for the HUD stuff in silo #9, I don't think and landing folks want to hit the publish button, though, because the status still makes it look like the build failed12:18
Laneymlankhorst: trying ...12:22
=== MacSlow|lunch is now known as MacSlow
chrisccoulsonmlankhorst, is there an easy, reliable way to detect that nouveau is being used?12:24
mlankhorstyes, but I would rather not add blacklists12:24
sil2100pete-woods: hey! Let me take a look at that, maybe it needs a small push from our side12:25
chrisccoulsonmlankhorst, as a stop-gap, making the webbrowser-app abort is probably better than the whole machine locking up :)12:26
mlankhorstchrisccoulson: though in that case I would prefer only adding certain nouveau versions, not blacklist newer nouveau entirely12:26
Laneymlankhorst: I had some weird flickering when I logged in12:27
LaneyWHAT HAVE YOU DONE12:27
mlankhorstno idea12:28
Laneyactually I have it all the time12:28
mlankhorstyeah I've noticed, no idea about it yet :/12:28
Laneyhaha12:28
Laneywhy did you get me to run it if you knew?12:28
mlankhorstmight be that flush I removed on swapbuffers, but hey i told you it was hacky :P12:28
Laneyoh god12:28
* Laney babbles12:28
pete-woodssil2100: thanks :)12:40
=== pete-woods is now known as pete-woods-lunch
=== salem_ is now known as _salem
=== _salem is now known as salem_
jdstrandjamesh: hey, for bug #1303962, does this policy look reasonable:13:05
ubottubug 1303962 in apparmor-easyprof-ubuntu (Ubuntu) "please integrate mediascanner2 and media-hub with apparmor" [High,In progress] https://launchpad.net/bugs/130396213:05
jdstrand# Allow communications with mediascanner213:05
jdstranddbus (send)13:05
jdstrand     bus=session13:05
jdstrand     path=/com/canonical/MediaScanner2{,/**},13:05
ScottKdebfx: I'd say no.13:05
jdstrandthe {,/**} specifies an alternation such that both path=/com/canonical/MediaScanner2 and path=/com/canonical/MediaScanner2/<something else> matches13:06
pittiogra_: TBH, repeating where things changed in the changelog seems pretty obsolete to me; after all, that's all in the individual commits?13:12
pittiogra_: of course, the commit logs need to be useful; i. e. explain *why* something was done, not just *how*13:12
ogra_pitti, i just want somethig descriptive so that one of the landers can understand the change13:13
pittiogra_: yeah, summaries still help to find affected packages, of course; but I think having all the details in debian/changelog is too noisy13:13
ogra_ist fine to have a caption referring to the feature across the ten packages it spans13:13
pittiogra_: or did you actually mean bzr changelogs?13:13
pittiif these suck, then yes, big fail13:14
ogra_pitti, i mean debian changelogs ...13:14
pitti(but they always implicitly have the "where")13:14
ogra_well, bzr changelogs are usually not much better13:14
ogra_the debian changelog is assembled from them in CI13:14
pittiogra_: ah right, with CI train debian changelog == MP "commit changelog", meh13:15
ogra_pitti, my mail is more towards the upstream devs that arent familiar with packaging ... i havent seen malformed changelogs from experienced packagers yet13:15
ogra_if your MP commit mesage only says "hey, new feature added !!!! i rock" ... thats not helpful13:16
pittiogra_: heh, I don't think it's inherently related to packaging; more like "did that developer ever have to go through the pain of researching commits from some years ago" :)13:16
pittiyes13:16
pittiso in git terms, the one-line summary should be in the debian/changelog, the detailled 20-line description shouldn't13:16
pittibut right, we don't have the detailled 20-line description with our approach (at most in the individual commits of each merge)13:17
ogra_well, even a *proper* one liner would help13:19
ogra_most of the time its not even that13:20
jameshjdstrand: currently everything is hanging off a single object path, so the /** bit isn't strictly necessary.  You could also lock it down by the interface name too if you want.13:25
jameshjdstrand: it looks like that policy would work though.13:26
jdstrandjamesh: I'll lock it down more like you said. if we need to refine, it is easy enough to do13:32
jdstrandjamesh: thanks!13:32
shadeslayerpitti: wut https://jenkins.qa.ubuntu.com/job/utopic-adt-kapptemplate/3/console13:35
mlankhorstLaney: so no crashes then?13:36
Laneymlankhorst: it didn't crash13:36
mlankhorst:D13:36
Laneybut13:36
LaneyI couldn't really interact with it13:36
mlankhorstwhy?13:36
Laneybecause it was flickering so much13:36
mlankhorstai13:37
mlankhorstok so needs more thought then13:37
pittishadeslayer: yep, will restart; we had to reboot the ppc64el boxes, and jenkins as the pain that it is vomits on that for the x86 boxes too13:50
shadeslayerheh13:50
pittithis affected some 5 other tests too, all restarted now13:51
Laneyis that why I got a failure for a test which actually passed?13:51
pittile sigh, *want jenkins go away*13:51
pittiLaney: yes13:51
Laneynod13:52
=== pete-woods-lunch is now known as pete-woods
=== oSoMoN_ is now known as oSoMoN
xnoxpitti: not only i get shutdown-hang, a basic lxc container fails to boot as well *sigh*14:14
pittixnox: darn; the code looks rather correct to me, so I guess it's hanging someplace else now? :-(14:15
xnoxpitti: let me go the traditional route and upload remaining fixes for tasks & try concurrent boot without changing sysv-init at all.14:16
xnoxcause that suppose to work (or at least did in limited sense)14:16
xnoxand the fact that startpar is not producing any logs anywhere is annoying. (and even it's stdout/stderr is slurrped up by the rc script)14:17
pittidpm_: actually, with http://people.canonical.com/~dpm/data/ubuntu-l10n/utopic-potemplate-stats.log the percentage cutoff is not that hard to do; how reliable/up to date are these json files in general?14:23
pittidpm_: with that file I'll add the numbers of all templates that we have in the package list, and with msgfmt --statistics I can add the number of translated strings, the rest is simple division and comparison14:24
dpm_pitti, they're pretty good, and they are updated once a day. As an alternative, you can use the LP API to get instant stats if we need it to be more frequent.14:25
pittidpm_: nah, that's totally fine14:25
pittithanks14:25
dpm_pitti, that sounds good to me. If you're looking for a pure python solution, you might want to use polib instead of the cli gettext tools14:26
bdmurraymvo: bug 1309447 failed the verification for the SRU. I posted the traceback I received.14:26
ubottubug 1309447 in apt-clone (Ubuntu Trusty) "Unicode decode error during upgrade to 14.04 if sources.list contains non-ascii characters and locale is non-US" [High,In progress] https://launchpad.net/bugs/130944714:26
pittidpm_: not installed on macquarie, I guess I'll just keep the existing msgfmt call (it's already calling that anyway for normalization)14:27
dpm_ok, sounds fine, then14:27
mvobdmurray: thanks, let me have a look14:28
mlankhorstpmcgowan: oh btw, i checked and bug https://bugs.launchpad.net/checkbox-gui/+bug/1318584 is not a regression from trusty14:44
ubottuUbuntu bug 1318584 in Next Generation Checkbox (GUI) "checkbox-gui crashed when switching video out mode to external only mode" [Medium,Confirmed]14:44
shadeslayerpitti: https://jenkins.qa.ubuntu.com/job/utopic-adt-kate/ < doesn't seem to have actually run the tests?14:45
shadeslayerhttps://jenkins.qa.ubuntu.com/job/utopic-adt-kate/ARCH=i386,label=adt/2/console14:45
pmcgowanmlankhorst, hmm? meaning its busted on earlier stuff?14:45
pittishadeslayer: it could certainly do with some more verbosity..14:46
shadeslayerkbuildsycoca4 running... < kdeinit starts, but then nothing14:46
mlankhorstpmcgowan: yeah, trusty crashes in the same way, and I diffed the qplatformscreen.cpp file against 5.2.1, didn't find any changes14:46
shadeslayerklauncher: Exiting on signal 1 < that's from shutdown I kdeinit4_shutdown think14:46
=== timrc-afk is now known as timrc
shadeslayerpitti: btw locally my hook seems to run them14:47
pittishadeslayer: perhaps this is missing some xvfb-run etc. magic?14:47
shadeslayerhttp://paste.ubuntu.com/7595244/14:47
pmcgowanmlankhorst, I assume the concern is trusty since thats what is used for preinstalls14:47
mlankhorstit looked to me like the concern was it being a regression that prevented 5.3.0 from landing..14:49
pittimkdir failed: : No such file or directory14:51
pittitrying to create local folder /home/shadeslayer: Permission denied14:51
pittishadeslayer: ^ something seems wrong in your hook?14:51
mlankhorstpmcgowan: from the qplatformscreen.cpp documentation14:52
mlankhorst    Reimplement in subclass to return the pixel geometry of the screen14:52
mlankhorst\fn QRect QPlatformScreen::geometry() const = 014:52
shadeslayerpitti: http://paste.ubuntu.com/7595266/ < afaict that comes from kdeinit14:52
pmcgowanmlankhorst, no the concern aiui is validating trusty images with the test tool14:53
pittishadeslayer: ah, this probably still keeps your $HOME although it runs as user pbuilder14:54
shadeslayermost likely14:54
pittishadeslayer: btw, adt-run has a -s/--shell-on-fail option which you might want to use14:54
pittishadeslayer: ah no, it's currently broken with --output-dir, so not yet :/ (and --tmp-dir is obsolete)14:55
shadeslayerpitti: the hook gives me a shell on fail :)14:55
shadeslayersee lines 31-3314:55
pittishadeslayer: anyway, I suppose this needs to be checked in schroot or qemu to see what's going on14:55
pittishadeslayer: right, that's what I was looking at14:55
mlankhorstpmcgowan: hm might be found with valgrind..14:56
mlankhorstif object was already destroyed14:57
shadeslayeruf :P14:57
shadeslayerseems like so much work14:57
pittishadeslayer: well, what is this test supposed to do?14:59
pittishadeslayer: the essence is that it calls dh_auto_test14:59
shadeslayeryep14:59
pittishadeslayer: you really want to do that during build instead14:59
pittithat doesn't test the installed pacakges at all15:00
pittiand also explains why nothign is being tested in CI as there is no built tree15:00
pittishadeslayer: (it doesn't have build-needed); but you really shouldn't run tests against the built tree in an autopkgtest anyway :)15:01
pittishadeslayer: so that same appraoach in debian/rules override_dh_auto_test seems just fine15:01
pitti(and dropping the autopkgtest, or replacing it with something that actually tests the installed package)15:01
shadeslayerso I wonder why debian does it this way15:01
pittishadeslayer: I know, it's a rampant error which apparently keeps spreading via copy & paste :(15:02
pittishadeslayer: may I point to https://lists.debian.org/debian-devel-announce/2014/05/msg00004.html ?15:02
=== timrc is now known as timrc-afk
* shadeslayer looks15:03
shadeslayerpitti: cheers, I'll collaborate with debian15:05
pittishadeslayer: many thanks!15:05
=== timrc-afk is now known as timrc
xnoxstgraber: https://launchpadlibrarian.net/177016056/buildlog.txt.gz this looks odd (during recipe build now)15:29
stgraberxnox: hmm, yeah, that's weird... I did put a breaks + replace in there didn't I?15:30
xnoxstgraber: you did, but it's unpacking a weird upstart at the same time.15:30
stgraberxnox: ah, yeah, I guess that may break if using the upstart from the PPA maybe, if it has a version higher than the break but still has 01-upstart-lsb15:31
xnoxstgraber: right, let me fix that. However, that shouldn't have happened as we use latest packaging.... which has the right commit dropping the hook.15:32
cjwatsonYeah, it'll always dist-upgrade from the archive in question first15:32
xnoxright, last build of upstart into ppa for utopic used packaging revision 1562 and thus still has the hook, which now prevents building new upstart into ppa via recipe.15:34
xnoxwill delete upstart from PPA, check the recipe and re-trigger the build.15:35
pittidpm_: so I implemented the "count number of translated strings" in langpack-o-matic now; turns out that we ought to remove quite a number of really poor langpacks for regular Ubuntu, too: http://paste.ubuntu.com/7595543/15:37
pittidpm_: even with a really low cutoff like 5% we can get rid of a lot of noise (where there are only 5 strings translated in the whole Ubuntu..)15:37
xnoxstgraber: cjwatson: ha, recipe uses trusty packaging instead of utopic.15:38
xnoxwhich i think happens on each distro-series branch. lp:ubuntu/upstart recipe branches become lp:ubuntu/(devel-1)/upstart15:39
dpmpitti, that'd work for me if that helps managing language packs. I'm not too worried about it, as for me the priority would be to get more languages in the CD rather than reducing the number of langpacks in the archive. But if it helps removing cruft, wfm, yes15:39
pittidpm: yeah, I implemented it for the 70% threshold for the touch packs, but it has that nice side effect :)15:40
pittiif we reduce the buildd load and archive overhead from 800 to 600 packages that's already something15:40
dpm:)15:41
cjwatsonpitti: it's much more manageable with cross-architecture builder pooling now, anyway15:42
pitticjwatson: right, but it's also Packages.gz size etc.15:42
cjwatsonso we can build 16 language packs at a time in parallel and *blam*15:42
cjwatsonYeah15:43
pitticertainly not a huge saving, but we'll get that for free15:43
pittiand with that, good bye everyone! see you on Tuesday (swap day tomorrow, Pentecost on Monday)15:44
bdmurraymvo: do you have any plans to upload aptdaemon? bug 132483315:51
ubottubug 1324833 in aptdaemon (Ubuntu) "crash handler does not include package version" [High,In progress] https://launchpad.net/bugs/132483315:51
mvobdmurray: I had no plans, but I can do it tomorrow15:53
=== timrc is now known as timrc-afk
hallynBenC: sorry on bug 1321365, i'll be testing a 1.2.5 candidate with that fix today16:18
ubottubug 1321365 in libvirt (Ubuntu) " virsh (ppc) fails with "missing /proc/device-tree/cpu "" [Critical,Triaged] https://launchpad.net/bugs/132136516:18
BenChallyn: Thanks. I’m working on testing libvirt fully. Tryign 1.2.5 right now (if you have wip src package, please let me try it too)16:19
BenChallyn: I’ll let you know if I run into any other issues16:19
BenChallyn: But please backport that fix to trusty too16:19
hallynBenC: zul will push it to ppa:zulcss/libvirt-testing momentarily16:19
hallynBenC: yes, will do.  i was going to wait for 1.2.5 but at this point forget that.  lemme check check other pending srus,16:20
hallynyeah that's the only one i have listed for trusty16:20
hallynsay is saucy eol yet?16:20
zulBenC:  just doing a local test build first16:25
hallynstgraber: hey, if you're around, would you midn looking at the libvirt pkg i pushed to trusty-proposed?  it's urgent for ben, a 2-line fix;  it's not in utopic yet only bc we're still testing the huge and painful 1.2.5 merge there.16:43
hallynstgraber: and BenC is blocked without it16:44
* hallyn shoulda just pushed the two-line fix originally, instead of trying to save the build farm some effort :)16:44
stgraberhallyn: ok, I'll take a look16:45
stgraberhallyn: minor nitpicking, why did you use ubuntu13.1.1 instead of ubuntu13.2? :)16:46
hallynstgraber: bc ubuntu13.1 is still in utopic for a day <shrug>  i bikeshedded for 2 mins then figured this seemed safest16:47
hallynhappy to change it back :)16:47
hallynwill look neater in the end16:47
stgraberhallyn: nah, I'll accept it as is, the version is not wrong, it's just unusual ;)16:48
stgraberhallyn: accepted16:49
hallynstgraber: thanks16:50
BenCerror: Failed to create domain from vir1.xml17:24
BenCerror: internal error: cannot load AppArmor profile 'libvirt-ffcc0d49-cf2d-48f7-bb59-fb60731b3c59'17:24
BenChallyn: Any ideas on that?17:24
=== dpm is now known as dpm-afk
BenCThis is using the 1.2.5 in zul’s  ppa17:24
BenCzul: ^^17:24
zulBenC:  no thats new to me17:26
BenCzul: This references an lp bug http://stackoverflow.com/questions/12069297/create-virtual-machine-using-libvirt-error-related-to-apparmor17:28
BenCzul: The workaround doesn’t apply to my xml though. It’s already raw17:29
zulBenC:  that version didnt have the device-tree fix since I havent uploaded it to my ppa yet hallyn is uploading a new fix17:29
BenCzul: I have that fixed locally, so that’s not the issue17:30
zulBenC:  then its another issue17:30
hallynBenC: i've pushed the fix against 1.2.2 to both utopic and trusty-proposed.  you can grab the binaries from trusty-proposed17:33
BenChallyn: Thanks17:33
=== rickspencer3_ is now known as rickspencer3
BenChallyn: Thanks17:46
BenCzul: No messages from apparmor in syslog when this happens17:46
BenCI even disabled apparmor and it still errors the same17:46
hallynBenC: you get this with the 1.2.2 version as well?17:47
BenChallyn: I can’t use 1.2.2 because it doesn’t configure the pci correctly, but no, I didn’t see this error there17:47
BenCIt showed that it successfully loaded/removed the apparmor profiles for the guest too17:48
hallynwhat patch do you need to configure teh pci correctly17:53
bdmurraypitti: have you seen the updated comments in bug 1259829 regarding some other models?18:01
ubottubug 1259829 in linux (Ubuntu) " htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39" [Low,Triaged] https://launchpad.net/bugs/125982918:01
=== timrc-afk is now known as timrc
BenCzul: If I set security_driver = "none" in libvirt/qemu.conf, and teardown apparmor, I can start vms with no issue18:07
jamespagegaughen, btw firefly is in -updates now18:07
BenCzul: When that error happens, virt-aa-helper isn’t even being called, so it fails even before that point in the code18:08
zulhallyn: ^^^18:08
BenCzul, hallyn: Something in virDomainDefFormatInternal() is erroring out (and it isn’t printing an error to syslog, so that limits the possibilities)18:14
gaughenjamespage, excellent18:22
BenCzul, hallyn: Here’s a FAQ: Not having a <uuid></uuid> in the xml causes that error18:23
* hallyn mumbles something about xml18:26
=== roadmr is now known as roadmr_afk
Unit193henrix: Hello, are you alive there?19:25
=== roadmr_afk is now known as roadmr
=== shenk is now known as shenkz
=== shenk is now known as shenkz
=== salem_ is now known as _salem

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