/srv/irclogs.ubuntu.com/2014/02/17/#ubuntu-devel.txt

=== mwhudson is now known as zz_mwhudson
edwinq03:08
=== zz_mwhudson is now known as mwhudson
=== mwhudson is now known as zz_mwhudson
dholbachgood morning07:20
Unit193seb128: Hello.  Sorry to bother you again, but is there a chance you can take a look at https://bugs.launchpad.net/bugs/1060543 ?08:46
ubottuLaunchpad bug 1060543 in software-properties (Ubuntu) "Additional Drivers is not discoverable in Quantal" [Critical,In progress]08:46
seb128Unit193, hey, I'm not working on software-properties, maybe try mvo when he's around?08:46
Unit193Ah, sorry.  Saw your name on last uploader.  He's been quite busy and normally is on the wrong timezone for me. :P08:47
seb128if you have a patch just subscribe ubuntus-sponsors to the bug08:50
=== psivaa-afk is now known as psivaa
Unit193seb128: Just a "mockup" of a desktop file.09:04
=== Ursinha is now known as Ursinha-afk
mlankhorstok so all upgrade bugs from lts to lts are fixed \o/09:33
brendanddoes anyone know of any good information on the file POTFILES.in? what is it used for , and information on the format09:49
seb128brendand, did you try man intltool-update?09:54
brendandseb128, that's the tool i was looking for, thanks09:56
seb128brendand, yw!09:57
=== Ursinha-afk is now known as Ursinha
brendandseb128, sorry - what about the format? does it support globs?10:00
brendandseb128, and also types. some of the files i want to translate are qt/qml10:02
seb128brendand, not sure about those, I guess so10:06
seb128brendand, you should maybe look at some project using similar techs to yours as an example.10:06
seb128?10:06
seb128hum10:09
seb128the ppc64el seem all on "manual", is that normal?10:09
infinityseb128: Yeah, it's temporary.10:10
infinityseb128: We're rebootstrapping the entire archive.  Nothing to see here.10:10
seb128infinity, does it mean things are sutcked in trusty-proposed until that's resolved?10:10
brendandseb128, hmm seems qml apps avoid using POTFILES.in10:10
infinity(Should be back to autobuilding in an hour or so)10:10
brendandseb128, i guess intltool-update only supports gettext10:11
infinityseb128: For a little bit, but not long (see above).10:11
seb128brendand, could be, I'm not the best person to ask about that10:11
seb128infinity, thanks10:11
brendanddpm ? ^10:12
dpmbrendand, could you give me more context on your question about POTFILES.in?10:42
brendanddpm, i'm trying to figure out the best way to set up translations for my c++/qml package10:43
brendanddpm, i guessed intltool-update would be best to use, but it seems to not support qml10:44
brendanddpm, are there ubuntu touch core apps that have a c++ component?10:45
Laneybrendand: take a look at ubuntu-system-settings10:45
dpmbrendand, yes, that or lp:reminders-app or lp:ubuntu-weather-app (the latter has an up-to-date README.translations file that provides more context)10:48
seb128Laney, dpm: just for the record I didn't point him to e.g u-s-s because it would be handy to have intltool working, our current setup is inferior in several ways (including the fact that we can't simply update the template by running intltool-update, we need to generate a build tree to run the make command and copy manual back)10:49
brendandseb128, i'm not the guy to make that happen though :)10:50
seb128well, you were looking at it, who knows, maybe you would have found a way10:50
brendandseb128, we're trying to get this package into main so we need translations set up10:50
dpmbrendand, can you point me to the lp project? I can try to help, but this week is rather full, so unfortunately I can't make any promises10:51
brendanddpm: it's in lp:checkbox but in the checkbox-gui directory10:52
dpmseb128, yeah, I see it that way too. But I couldn't figure out a way to replicate intltool-update with cmake without calling cmake and make, either :/10:53
dpmwith qmake it was a bit easier, but still not optimal10:53
infinityseb128: compiz and bamf built, were those the ones you were worrying about?10:54
seb128infinity, I'm watching the builds, nux and unity still10:54
seb128infinity, but yeah, those 2 were part of the unity update10:54
Laneyseb128: yeah, but I think the problem is that intltool just doesn't support qml at all, let alone ubuntu sdk qml10:55
Laneythe xgettext call we have encodes 'tr' as a thing to look for10:55
seb128Laney, right, I need to look at making our "make pot" at least not output the fullpath in the template, that makes the whole template change every time we run the command10:56
seb128dholbach, the cordova binaries are a bit weird, they install their .so in /usr/share ... is that wanted?10:56
infinityIt's never wanted.10:57
infinityUnless those are magical arch-indep libraries.10:57
seb128that package is quite hackish, I don't like much10:57
seb128but I'm not wanting to fight over details since I don't have a better suggestion/I'm not interested enough into the topic to spend efforts on it10:57
infinityIf they're not following FHS, that's absolutely a reason to reject.10:58
seb128infinity, they are not, but that package is weird, it's basically a "provide files for clicks to copy/embed"10:58
infinityAhh, binaries in /usr/share make sense in that context.  But they still shouldn't overlap between arches, if they currently do.10:59
seb128/usr/share/cordova-ubuntu-3.4/www/libcoreplugins.so10:59
seb128so yeah, they do10:59
infinityYeah, so no indication of what arch that .so is for...11:00
seb128dholbach, can we get that fixed?11:00
infinityIt's not multi-arch:same, of course, so there's allowed to be overlap.  It just seems like a bit of a messy design.11:01
seb128infinity, feel free to accept the binaries from the queue if you are fine with them ;-)11:01
* seb128 has no strong opinion, as said that package is a bit hackish11:01
seb128but if it does the job/unblock people...11:02
infinityI'd probably want to talk to the people behind it to get more context before I accepted them.  Which I'm unlikely to do at 4am after working all weekend.11:03
seb128infinity, yeah, you should get some sleep!11:05
seb128infinity, have a good night11:05
infinityseb128: I'll try. :)11:05
dholbachseb128, AFAIK (I'm just trying to help the team get things landed): the SDK will download <package>:<arch> from the archive and bundle that the runtime in the click package11:15
seb128dholbach, what if you try to dev for e.g i386 and armhf on the same machine?11:16
seb128those conflict atm11:16
dholbachseb128, AFAIK they're not necessarily required to be installed on the developers machine, but I might be wrong11:16
seb128well, they are in the archive, so nothing prevent you to apt-get install them11:17
dholbachdbarth and team would be the people to answer this - maybe we should discuss it on https://launchpad.net/bugs/1279814?11:17
ubottuLaunchpad bug 1279814 in Cordova Ubuntu "[needs-packaging] Get cordova-ubuntu-3.4 into trusty release" [Critical,Fix committed]11:17
seb128well, as said before, I'm busy enough with other things and I don't know much about the cordova thing11:18
dholbachok11:18
seb128so I'm going to letting infinity a chance to comment on that later on, and if he doesn't I think I'm just going to wave the binaries in11:18
seb128they are a bit hackish/wrong but that's not the end of the world imho11:18
dholbachthanks seb128, infinity11:20
seb128yw11:21
seb128do we have any buildd admin around to bump the score of https://launchpad.net/ubuntu/+source/unity/7.1.2+14.04.20131106.1-0ubuntu5/+build/5606463 ?11:22
cjwatsondone11:22
seb128cjwatson, thanks11:22
cjwatson(not really here, just going again)11:23
seb128(good timing for not being here, thanks again ;-)11:23
infinityThat really wasn't necessary...11:24
infinityseb128: Everything in the release pocket is being rebuilt, there's no particular reason to score any of it up, as we still have all the old binaries.11:24
cjwatsonoh, that was a release pocket build?11:25
cjwatsonright, matters not11:25
cjwatson*shrug* it'll all churn through anyway11:25
cjwatsonI expect seb128 actually identified the wrong build from proposed-migration11:26
seb128shrug, indeed11:26
seb128I wanted https://launchpad.net/ubuntu/+source/unity/7.1.2+14.04.20140214.1-0ubuntu1/+build/560790411:26
infinityThe proposed one is dep-waiting for a publisher cycle.11:26
cjwatsonwhich is needs-build now and about to start11:26
infinityOr, was.11:26
seb128I got confused by the lp table lines order and clicked on the wrong version11:26
cjwatsoneverything in -proposed will build before anything in the release pocket11:26
seb128cjwatson, infinity: thanks11:26
seb128oh, nice11:26
cjwatsonso actually your request slowed more important things down11:26
cjwatsonoh well, not by much11:26
seb128:-(11:26
seb128sorry about that11:27
infinityS'ok.  I'm still banking on main being done in just over a day.11:27
seb128I cancelled the build of the other version11:27
cjwatsonyou still planning to commandeer more hardware?11:27
cjwatsonseb128: just leave it please11:27
infinitycjwatson: Yeah, but not until Tuesday, when I can get pinky to twiddle some cables.11:27
infinityAnd main will probably be done by then.11:27
seb128too late, sorry again :-(11:28
cjwatsonseb128: rule of thumb for today: don't try to micromanage ppc64el :)11:28
seb128yeah, I just learnt that I think11:28
cjwatsonI've retried that cancelled build for consistency's sake11:28
* seb128 justs wants that unity in trusty :p11:28
seb128anyway, we should be good once the proposed build finish11:29
seb128so I'm staying away from builders now11:29
seb128thanks again ;-)11:29
cjwatsoninfinity: I'd certainly expect the whole thing to be quicker than the predicted five days11:40
infinitycjwatson: I gave myself a lot of padding in my estimates.11:45
infinitycjwatson: Years of "5-minute-fix" engineering estimates have taught me some valuable lessons.11:45
infinitycjwatson: Of course, it's also feature freeze week, which means everyone and their dog will be vomiting their last two months of pending local changes to every package ever, so that churn will slow us down a tiny bit.11:46
wgrantcjwatson, infinity: There's were ~700 buildd-hours of successful builds in the release pocket at the time of the purge, from what I can see.11:53
infinitywgrant: So, 3 days on the current setup.  Add a couple for proposed churn, subtract for extra hardware on Tuesday, carry the 1...11:54
wgrantPlus the failures, which I'll work out in a moment.11:54
infinityRight, well.  I'll set up the other two machines tomorrow "just in case", so they can be lit up as soon as they have a network.11:54
wgrantYep11:54
infinityAnd if we don't need 'em, whatever.  But handy to have them.11:55
wgrantLooks like about 950 if we include failures.11:58
wgrantStill, not very many days.11:58
infinity4 days, plus an extra for proposed churn, I'd say...11:59
infinityHits my 5 day mark almost on the head.  But 8 more VMs will win the day.11:59
ogra_doko_, infinity .... why does libgcc nowadays depend on gcc-4.9 ?12:01
ogra_seems a recent change pulled the compiler into the touch image12:01
infinityogra_: It doesn't.12:01
infinityogra_: gcc-4.9-base isn't a compiler.12:01
infinityogra_: You already had gcc-4.8-base12:01
ogra_http://people.canonical.com/~ogra/touch-image-stats/20140214.3.changes12:01
ogra_ah12:02
ogra_why isnt 4.8 not dropped then ?12:02
ogra_-not12:02
infinityogra_: libgcc1 is 4.9, but you still have other libs from 4.8 (probably libstdc++6, at least)12:02
ogra_hmm, k12:02
xnoxogra_: because 4.8 is default for C/C++, whilst 4.9 is default for Go on armhf/arm64/ppc64el12:02
infinityogra_: So, you need both -base packages.  They're tiny, no big deal.12:02
ogra_ok12:02
=== doko_ is now known as doko
dokoneither pitti nor jibel online ... and python2.7, python3.3, python3.4 autopkg tests are failing. did the test env change?12:07
ogra_they are on oakland iirc12:07
ogra_should come online in a while12:08
seb128right, QA is in Oakland this week12:08
=== MacSlow is now known as MacSlow|lunch
infinityOh, one more rebuild-related thing: archive admins, please ignore the heck out of component-mismatches for the next few days, it'll be full of lies.12:29
infinitycjwatson, doko, seb128 ^12:30
seb128infinity, noted, thanks12:30
=== tkamppeter_ is now known as tkamppeter
=== Pici` is now known as Pici
brendanddpm, hello again13:45
brendanddpm, all the packages you pointed to seem to involve cmake at some stage13:45
brendanddpm, can we avoid introducing cmake into the chain?13:45
dpmbrendand, you can try with qmake, which for translations was pretty lightweight. Have a look at the weather app, 3 or 4 revisions back from trunk13:46
dpmthat was before the cmake switch13:47
jamespagedoko, any ideas? https://launchpadlibrarian.net/166508215/buildlog_ubuntu-trusty-ppc64el.gccgo-go_1.2-0ubuntu5_FAILEDTOBUILD.txt.gz14:07
jamespagethat upload failed with the same error on armhf, powerpc and ppc64el14:07
dokoyes, known14:07
jamespagedoko, ok14:07
pittiGood morning14:13
dokoneither pitti nor jibel online ... and python2.7, python3.3, python3.4 autopkg tests are failing. did the test env change?14:14
pittiI just saw14:14
pittiI added proxy vars so that tests can talk to the network14:14
pittibut apparently that's confusing some things14:15
seb128pitti, when did you add them?14:15
pittiI wanted to revert that for now, but now I can't build any fresh VMs any more14:15
shadeslayerpitti: morning :)14:15
pittiit seems the latest cloud-image upload from Feb 14 broke VM building entirely, looking at that now14:15
pittiseb128: Feb 11 or so14:15
seb128k14:15
shadeslayerpitti: so regarding the upgrade tests for Kubuntu + Backports PPA , we have http://bazaar.launchpad.net/~kubuntu-dev/auto-upgrade-testing/auto-upgrade-testing/files/head:/share/profiles/kubuntu-full-backports/14:16
seb128I guess the software-properties tests started failing for another reason14:16
shadeslayerpitti: which apparently requires a script to be added, wouldn't that be needed in main auto-upgrade-testing?14:17
pittismoser: so since Feb 14 (new cloud-init), ssh connections to the cloud images keep timing out; did you hear any report about this already and already have an idea why?14:18
=== MacSlow|lunch is now known as MacSlow
shadeslayerpitti: so, any thoughts?14:23
pittishadeslayer: sorry, stack overflow14:23
shadeslayerhah :D14:24
pittitons of IRC scrollback, and I mostly wanted to see whether I can catch smoser before Europe goes EOD14:24
shadeslayerpitti: tl;dr http://bazaar.launchpad.net/~kubuntu-dev/auto-upgrade-testing/auto-upgrade-testing/files/head:/share/profiles/ < has some kubuntu profiles, thoughts on getting that merged into auto-upgrade-testing since we have some scripts in there too that can't be added to jibel's branch14:25
pittiyes, if we want to run them, we'll merge that; jibel wanted to merge his +junk branch into lp:a-u-t, too14:26
pittidoko: so in short, it's on my radar, I'll fix it today14:27
dokocool, tanks14:27
pittias soon as I find out what changed in cloud-init and I get working VMs again, I'll fix or revert the proxy settings and retry all failing tests14:27
pittismoser: do the current cloud images (with latest cloud-init) work for you at all? they just hang eternally in qemu for me, with no useful output or possibility of logging in14:30
shadeslayerpitti: ack, I'll try and update the branch14:32
pittismoser: last known working image is from Freb 1414:33
pittiFeb14:33
spineaudoko: hello, we've uploaded checkbox 0.17.4 but surprisingly, that didn't trigger any component mismatches, two mir'ed dep are still not in main (bug 1278822 and bug 1277408)14:36
ubottubug 1278822 in plainbox-provider-checkbox (Ubuntu) "[MIR] plainbox-provider-checkbox" [Undecided,Fix committed] https://launchpad.net/bugs/127882214:36
ubottubug 1277408 in checkbox-ng (Ubuntu) "[MIR] checkbox-ng" [Undecided,Fix committed] https://launchpad.net/bugs/127740814:36
spineaudoko: Ideally we'd like to see both of them in main before Thursday14:37
pittismoser: http://paste.ubuntu.com/6949086/ is the output from ttyS0; this still worked with the very same cloud-init iso until Feb 14; any idea?14:42
ogra_pitti, check your serial cable14:43
* ogra_ grins14:43
Laneydid anyone notice that gpg-agent has stopped saying which key it's prompting you for?14:50
xnoxLaney: is it the result of using ssh-agent, instead of gnome-keyring secrets agent?14:51
Laneydoubt it, this is inside a container14:51
mapreriGodd afternoon! I'm wondering why 4.5.0-2 is stuck in proposed https://launchpad.net/ubuntu/+source/insighttoolkit4 ....14:52
mapreri(Architecture field in the control file state only "amd64 i386", so builds are ok http://sources.debian.net/src/insighttoolkit4/4.5.0-2/debian/control )14:54
cjwatsonmapreri: stale library left around in -proposed, looking14:54
maprericjwatson: great, thank you!14:55
cjwatsonplastimatch will need to be rebuilt against the new version14:55
cjwatsonlet me quickly do that now14:56
maprericjwatson: can I know how do you find it? (just to learn something new...)14:56
cjwatsonhttp://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#insighttoolkit414:56
cjwatsonplus experience14:56
cjwatsonand checkrdepends against an archive mirror to find the reverse-deps of that library in -propsoed14:58
cjwatson*-proposed14:58
mapreriuh14:59
* mapreri takes note....14:59
cjwatsonmapreri: ok, I've uploaded a no-change rebuild of plastimatch and removed the stale libinsighttoolkit4.4/i386 binary from -proposed, so that should clear it up shortly assuming plastimatch builds14:59
maprericjwatson: I'll check in a few hours, thanks again15:01
=== freeflying is now known as freeflying_away
seb128does anyone know what is missing to make indicator-datetime/unity-control-center migrates?15:14
seb128indicator-datetime stopped building unity-control-center-datetime15:14
seb128 unity-control-center C,R,P it15:14
seb128 so the binary should be NBS and provided by u-c-c15:14
seb128 that should be enough no?15:14
pittidoko: I re-ran python2.7, that failed many tests, but they don't sound network/proxy related; I'll have a look later after breakfast15:35
pittiseb128: so it seems gjs is due to the new version? Error: Requiring GjsPrivate, version none: Typelib file for namespace 'Gtk', version '3.0' not found15:37
pittiseb128: sounds like it now grew a missing gir1.2-gtk-3.0 test dep?15:37
pitti(or perhaps binary dep, not sure)15:37
seb128pitti, looks like15:37
seb128darkxst, ^ can you look at that/get it sorted out (since you did that update)15:37
=== vibhav is now known as Guest49842
seb128is britney supposed to resolve provides?15:56
* seb128 wonders why it doesn't consider the unity-control-center providing unity-control-center-datetime as valid/enough15:56
geserdoes britney consider those two packages together or each for it's own if it can transition?16:01
dokorbasak, could you have a look at the php5 merge?16:01
seb128geser, each one it seems16:07
seb128Laney, can you hint britney to consider both together?16:07
Laneyworth a try16:09
seb128Laney, thanks16:10
rbasakdoko: ack.16:16
Laneyseb128: if it doesn't work I guess you can remove the package and fix the seeds to not pull it in16:18
seb128Laney, right, the seed need fixing anyway, but robert_ancell and pitti stacked work, and robert_ancell wants to transition to unity-settings-daemon as well, so I was sort of letting one of them deal with an upload16:19
Laneyjus' saying, that'll probably help with the migration16:19
seb128right16:20
seb128let's see at the next run with the hint16:20
apwcjwatson, just updated an old clunker, and am getting "diskfilter writes are not supported" with a press any key to continue, from grub2, expected ?16:22
rbasakdoko: you mean 5.5.9, right? 5.6 is in experimental, but I'm not sure that's a good idea.16:27
hakermaniaCan anyone remind me the process of updating a package from the repos? I want to update Wallch to the version 4.0. I remember that I have to post a bug report somewhere and link to the ppa but I don't clearly remember the process...16:31
seb128geser, Laney: britney hint worked ;-)16:50
Laneyneat16:50
brendanddpm, do you have any more detail on how translations work with sdk apps? are the qml files installed with the translations merged in, or does it work some other way?16:52
dpmbrendand, it's quite similar to e.g. python apps on the desktop. We're using gettext: the qml files load the translations at runtime, and translations are shipped as .mo files in the .click packages, using the same gettext paths as in the desktops, with the difference that they are installed within the click package's installation folders16:53
dpmand not in the system16:53
=== FliesLik1ABrick is now known as FliesLikeABrick
seb128pitti, huuuummm16:59
seb128pitti, why did gtk migrate to the release pocket while gjs tests are still red?16:59
seb128pitti, not that complain about gtk migrating, but that seems buggy16:59
Laneyadt migration bugs are usually jibel17:00
pittiseb128: we had the same problem last week with the libgcc bug17:00
Laneyhe was looking into it iirc17:00
apwcjwatson, seems to only affect my 32bit box ... amd64 seems happy17:00
=== jasoncwarner__ is now known as jasoncwarner
seb128jibel, ^17:04
dokorbasak, yes, 5.5.9, please not an alpha ;)17:10
pittistgraber: can you leave in the lxc proxy hack? I'm going to revert it from the VMs for now17:18
pittistgraber: it breaks too many things, and e. g. glib and python have different ideas about how these variables work17:18
stgraberpitti: ok17:21
stgraberpitti: oh and I was just about to ping you about logind, any chance you can get me a PPA build or something of the systemd version we'd like to have for Trusty?17:22
dokodoko, any hint about https://launchpad.net/ubuntu/+archive/test-rebuild-20140127/+build/5518972 ?  there are about 100 build failures like this one17:22
pittistgraber: I don't currently have any plan of changing what we have in a major way17:22
dokorbasak, ^^^17:22
pittistgraber: unless you plan on landing the cgroupmanager and compat API? But even then, upgrading to systemd 208 would be quite a bold step at this point IMHO17:23
stgraberpitti: right, I was asking specifically because of that. We have cgmanager working fine now and I'm looking at the next steps.17:24
pittioh, nice17:24
stgraberpitti: if you don't plan on updating systemd at this point, then that's fine, I'll just patch logind directly to talk to cgmanager, if you plan on updating systemd, then I should be working on the shim instead.17:24
pittistgraber: yes, agreed17:24
pittistgraber: but TBH I'd leave that to 14.1017:25
stgraberwell, I can't, we need logind to do the right thing for unprivileged containers in 14.04... so I guess I'll just patch our current logind to talk to cgmanager and look at systemd-shim for 14.10 instead.17:25
pittidoko: hm, I get all kinds of failures even locally now ("cannot allocate memory" and other  strange stuff); could that be related to the new glibc?17:26
stgraberpitti: I'll try and get the logind patching done this week and will send you a patch or branch so you can sanity check it17:32
pittistgraber: thanks; we are on a sprint this week, so I probably won't have too much bandwidth for large patches; but I guess if that's only against 204 it should not be too big17:33
=== jono is now known as Guest43181
stgraberpitti: right, it should really just be some code to detect cgmanager and do 3 dbus calls (per controller) instead of the matching cgroupfs writes17:50
cjwatsonapw: won't have much to do with 32-bit, I expect that's because it's trying to write to a /boot/grub/grubenv on RAID or LVM17:51
cjwatsonstgraber: we still want the shim to work properly for Debian, though, right?17:52
stgrabercjwatson: right and for 14.10 (probably) but I'm not going to rush into doing that for 14.04 if our logind doesn't use that API anyway17:53
apwcjwatson, ahhh yes this is the machine i got rid of the separate /boot from because it was far toooo small18:00
cjwatsonapw: it's a relatively harmless error - main side-effect is that the logic to display the boot menu if the previous boot failed won't work18:08
cjwatson(also some other side-effects of similar kinds, but that's the one you're most likely to notice)18:08
apwcjwatson, yeah and it makes teh boot ugly suddenly, i assume it is something new with the beta?  anyhow this setup is a very odd one i am sure18:09
cjwatsondunno about that18:09
tseliotstgraber: hi, can you approve bug #1279229 please? I've verified the fix18:11
ubottubug 1279229 in jockey (Ubuntu Precise) "Jockey is unable to check Saucy's xserver ABI" [High,Fix committed] https://launchpad.net/bugs/127922918:11
pittistgraber: I'm writing a little script which is supposed to run every day to create a fresh container and (almost) atomically replacing the previous one with the new one: http://paste.ubuntu.com/6950426/19:02
pittistgraber: but of course that rips out the underlying FS for any running containers19:02
pittistgraber: are you aware of an existing solution how to provide daily updated containers when they also might be running?19:03
=== TheLordOfTime is now known as teward
stgraberpitti: as in, you have containers using that one as a base with overlayfs or aufs?19:05
pittiright, with ephemeral19:05
pittistgraber: I want to use that on the machines that run autopkgtests (arm/ppc64el)19:05
stgraberhmm, best guess would be to create your .new, then rsync the rootfs19:05
pittistgraber: I can of coure add some lock file mechanism so that the update job always runs alone19:06
stgraberso you'll never end up with an empty underlay, and it should update pretty quickly19:06
pittistgraber: but if I rsync the new rootfs into the old container, doesn't that also create inconsistent file systems?19:07
stgraber(rsync -A --numeric-ids --sparse --hard-links --delete trusty.new/rootfs/ trusty/rootfs/)19:07
stgraberyeah, it'd be inconsistent for a tiny bit of time19:07
stgraberit's a tradeoff, either you have an update script as yours which will only apply to new containers19:08
pittistgraber: ah, and I would never actually move/rename the .new container to the old one, but just always keep the one existing "trusty" container?19:08
stgraberor you have something using rsync which will also apply to running containers19:08
stgraberright, no reason to copy a new config, fstab, ... those don't change, you only really care about the rootfs19:09
pittistgraber: ack19:09
pittistgraber: many thanks!19:09
stgraberjdstrand, doko, infinity: any of you (probably security) has time to review bug 1279048? I'm going to release LXC 1.0 this week and I'd very much like it to use cgmanager by the time I upload it...19:20
ubottubug 1279048 in cgmanager (Ubuntu) "[MIR] cgmanager" [Undecided,New] https://launchpad.net/bugs/127904819:20
stgraberthis is also very soon going to become a blocker for landing of logind, libvirt, libcgroup and upstart features, so would be nice if we could have this processed soonish19:20
dokopitti, glibc didn't change yet. (I mean glibc-2.19 wasn't yet uploaded)19:29
pittidoko: ah, so what triggered the run was only the two ppc64 patches in https://launchpad.net/ubuntu/+source/eglibc/2.18-0ubuntu719:30
ogra_robru, hmm, seems since the last update the G+ webapp on the desktop uses the QML browser ... which just tells me that the browser is unsupported after login19:48
robruogra_, hmmm? my understanding is that all the webapps are supposed to be using the qml container on the desktop. that was a transition that we tried to get in last cycle, but it wasn't ready before feature freeze, so it got delayed until this cycle...19:59
ogra_robru, yes, thats why i ping you, because i know you were involved19:59
ogra_robru, G+ does definitely not work with that19:59
robruoh...20:00
ogra_(most likely needs a hacked user agent)20:00
robruogra_, is there a bug filed?20:00
ogra_not by me, i just noticed it before i pinged you20:00
robruogra_, ok, please file a bug and assign it to justinmcp20:01
nvrpunkanyone know why I am getting:  can't build with source format '3.0 (quilt)'20:03
ogra_robru, against what, webapp-contsainer ?20:04
ogra_*container20:04
robruogra_, nah, unity-webapps-googleplus20:04
ogra_ok20:05
nvrpunknvm, got it20:05
sergiusensrobru, ogra_ g+ app is owned by xnox20:19
sergiusensrobru, ogra_ nvm, wrong channel :-) just the click one ;-)20:19
xnoxsergiusens: well, i've submitted g+ app update, but it got rejected20:19
* sergiusens checks20:20
sergiusensxnox, just add --webappUrlPatterns20:23
nvrpunkI dput a new build in my ppa for tahr and it isn't showing up, what should I check?21:29
nvrpunkif I try to reupload it says package exists21:29
nvrpunkI don't see it in my build queue etc21:29
infinitynvrpunk: Which PPA?21:33
nvrpunktim.l.nelson/ppa21:33
nvrpunkerr21:33
nvrpunktim-l-nelson/ppa21:34
nvrpunknvm21:34
nvrpunki think i got it21:34
infinityMmkay.21:35
nvrpunki think i need to create a new ppa, my first one was for Saucy21:36
Unit193You can use the same PPA for trusty, saucy, precise, etc.21:37
teward^ that21:38
infinitynvrpunk: What matters is what distribution is in the .changes file.21:39
infinitynvrpunk: (Or, alternately, the magic path you dput to, but that's a bit sketchier)21:39
nvrpunkVersion: 8.6.1-4ubuntu1ppa121:41
nvrpunkDistribution: trusty21:41
nvrpunklooks like my versioning and distribution are correct, I just don't see it queued to build etc21:41
nvrpunkI dput it an hour ago or so21:41
nvrpunkit should show in my "recent activities" correct?21:42
Ampelbeinnvrpunk: did you upload the same version before and then delete the packages from your ppa?21:43
nvrpunkno21:43
nvrpunkunless I uploaded 8.6 months ago and forgot, but I don't recall doing that21:43
nvrpunkand if I did it was most likely rejected because I had no clue what I was doing months ago21:44
nvrpunkyeah, I am at a loss21:54
nvrpunknever had this happen21:54
semi have installed gnome-shell package in my kubuntu box ==> unable to login21:54
semthis is not nice21:55
wgrantnvrpunk: You signed the .changes file with an OpenPGP key that isn't associated with your Launchpad account.22:03
wgrantnvrpunk: If you get no email from Launchpad at all, that usually means that there was no signature, or the signature was unable to be verified.22:03
tewardwgrant: are the PPA uploaders lagged at the moment?22:04
tewardoops i meant to point to #launchpad but I hate laptop touchpads, they clicked me to here22:04
teward>.>22:04
wgrantteward: No, no issues.22:04
wgrantteward: Are you seeing delays?22:07
tewardwgrant: yeah, 5 - 10 minute upload gap between amd64 and i38622:07
tewardwas causing bug triage problems for an upstream project, hence why i meant this to go to #launchpad22:07
tewardit *just* resolved itself22:07
wgrantteward: Oh, binary uploads?22:07
tewardmhm22:07
tewardwgrant: yeah, the upload of the built binaries22:08
tewardnot the upload of the source package22:08
* teward was imprecise in his explanation of the issue22:08
nvrpunkwgrant: well I imported my keys from my old install ~/.gnupg22:08
wgrantA couple of minutes of lag there is normal at high-traffic times. Are you sure it wasn't rather different build times?22:08
nvrpunkwgrant: then set my DEBFULLNAME and DEBEMAIL and I assume that should be my old key?22:09
nvrpunkif I no longer have my key how do I update that?22:09
tewardwgrant: since Launchpad doesn't report the actual timestamp of when the build started, both i386 and amd64 show the same build start time22:09
tewardbut you're right the completion was a different issue22:09
wgrantnvrpunk: debuild will have told you which key it used. Compare that to the one at https://launchpad.net/~/+editpgpkeys22:10
wgrantteward: You can hover over an "X minutes ago" timestamp to get the precise time.22:10
tewardwgrant: still, it took a while even *after* building to upload, and it seemed uncharacteristically slow22:10
=== sem is now known as Peace-
wgrantNothing's been delayed by more than two minutes in several hours.22:10
* teward shrugs22:11
tewardwgrant: maybe i'm impatient because the bug is a High priority bug that prevents installation of the nginx PPAs but meh22:11
* teward yawns22:11
tewardi shouldn't be doing packaging stuffs while tired >.<22:11
wgrantHeh22:13
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
nvrpunkwgrant, thanks I updated my key22:27
nvrpunkwill that cause them to build now?22:27
nvrpunkor will i have to wait on some form of rejection?22:27
wgrantnvrpunk: No, you'll need to upload the package again22:28
nvrpunkok lol22:28
wgrantAll your existing uploads were rejected.22:28
wgrantBecause the key was unverifiable.22:28
nvrpunkPackage has already been uploaded to ppa on ppa.launchpad.net22:29
wgrantdput -f22:29
nvrpunkdoes that matter?>22:29
nvrpunkok22:29
nvrpunkit's like you read my mind :D22:29
nvrpunkor saw my failure22:30
wgrantThe latter, I'm not that good.22:30
cjwatsoninfinity: Holy crap, the rebuild finished main already.22:37
cjwatson(Modulo builds in progress.)22:38
wgrantYeah22:39
wgrantI didn't believe it, but I can't see that anything went wrong.22:39
wgrantI've given back various plausible retries, and they've mostly worked now that the deps are rebuilt.22:40
wgrantStill several -O3 failures, though22:41
cjwatsonImagine my surprise :-/22:42
wgrantAll the errors have been the same, but who knows how many miscompilations have gone unwarned :)22:42
nvrpunkwgrant: does debuild create binaries?22:43
wgrantnvrpunk: It does by default, but you can tell it to build only the source package with -S22:43
nvrpunkok22:44
wgrantYou must use -S for a Launchpad upload.22:44
nvrpunkyes22:44
nvrpunkhence why I asked, thanks :)22:44
=== zz_mwhudson is now known as mwhudson
cjwatsonwgrant: The firefox and thunderbird failures are a bit suspicious.  I guess some dependency isn't really rebuilt yet23:02
stgraberhmm, so who screwed up tha indicator-datetime upload? it wants to pull half of the archive on my machine including unity823:02
stgraberah, looks like it's failing to find unity-control-center 14.04.3 and so fallbacks to ubuntu-system-settings which in turns pulls all of the touch stuff on my machine23:05
wgrantcjwatson: Oh, I didn't look at them since they never worked.23:05
stgraberrobert_ancell: ping23:05
wgranthttp://people.canonical.com/~wgrant/ppc64el-prepurge-logs/primary-trusty-ppc64el.html is the pre-purge page, for reference.23:06
robert_ancellstgraber, hello23:06
stgraberrobert_ancell: hey, that last indicator-datetime is trying to pull half of ubuntu touch on my machine, can you please fix ASAP?23:07
=== freeflying_away is now known as freeflying
robert_ancellstgraber, do you have gnome-control-center-datetime installed? Do you normally?23:07
stgraberrobert_ancell: you put a recommend on unity-control-center >= 14.04.3 but only 14.04.2 exists in the archive, so apt then fallsback to ubuntu-system-settings which in turns pull all of touch on my system23:07
infinitycjwatson: That firefox failure is the same one we always had.23:08
robert_ancellstgraber, this is edubuntu right?23:08
stgraberrobert_ancell: I appear to have this package installed, yes, though I certainly didn't install it manually23:08
wgrantcjwatson: The firefox failure looks the same as http://people.canonical.com/~wgrant/ppc64el-prepurge-logs/primary-failure-logs/buildlog_ubuntu-trusty-ppc64el.firefox_25.0+build3-0ubuntu0.13.10.1_FAILEDTOBUILD.txt.gz23:08
cjwatsonoh right, ok23:08
cjwatsonI didn't check prepurge :)23:08
stgraberrobert_ancell: nope, that's my laptop, so standard Ubuntu desktop23:08
robert_ancellstgraber, ok23:08
infinitycjwatson: IBM has patches for it, we're trying to talk them into upstreaming it, so we don't have to maintain it.23:08
cjwatsonk23:09
stgraberrobert_ancell: so I guess the question is, are we supposed to have indicator-datetime on our desktops?23:09
robert_ancellstgraber, ok, will fix it. Yeah, we're off by one for the version23:09
robert_ancellstgraber, yes23:09
stgraberok, good, so yeah, get that down to 14.04.2 and we should be fine23:09
infinitycjwatson, wgrant: http://paste.ubuntu.com/6951641/23:16
infinityProbably easier than hunting for "failures that matter".23:16
infinitybinutils is intentionally scored down, and the cross toolchain will need fixing later anyway.23:17
wgrantA couple of them are pretty weird23:17
infinitymodemmanager is fairly obviously -O3 fallout.23:18
infinitydbus-test-runner is a mystery to me.23:18
wgrantsquid3 is -O3 too23:18
wgrantAnd a few others that I forget23:18
wgrantI don't see how libecap ever worked.23:19
infinityOh, erm.  It's just symbols out of whack?  Yeah, that's weird.  Have an old log handy?23:22
=== mwhudson is now known as zz_mwhudson
wgranthttp://people.canonical.com/~wgrant/ppc64el-prepurge-logs/primary-all-logs/23:22
wgrantBeware, the listing is large23:22
wgranthttp://people.canonical.com/~wgrant/ppc64el-prepurge-logs/primary-all-logs/buildlog_ubuntu-trusty-ppc64el.libecap_0.2.0-1ubuntu3_UPLOADING.txt.gz23:23
wgrantOh23:23
wgrantWarnings are there, but non-fatal23:23
infinityOkay, so it's just that one symbol that went byebye.23:23
wgrantCould be -O3, I suppose23:24
infinityI wonder if it disappeared on all arches due to a dep changing.23:24
infinityOr possibly -O3...23:24
wgrantGiven what it is.23:24
infinityiterator?  Yeah, maybe.23:24
infinityLooks like something that should be ignored anyway.23:24
infinityC++ symbols, for the loss.23:24
infinityLemme have a poke at it.23:25
infinitySo, handily, the only thing that links to it is squid3, which is FTBFS.23:25
infinitySo, dropping the symbol is pretty much a non-issue even if it was referenced before.23:26
infinityBut, for kicks, let's see if squid3 uses that symbol on x86...23:27
wgrantaptitude's link failure is somewhat disturbing, and not reproducible on amd6423:28
infinity  2567: 0000000000175e10   179 FUNC    WEAK   DEFAULT   13 _ZNSs12_S_constructIPcEES23:29
infinityLooks optional to me.23:30
infinitywgrant: aptitude is probably -O3, but unwinding why makes my head hurt.23:33
wgrantIndeed, I can't see what else it could be.23:33
wgrantBut it's still pretty weird that it breaks like that.23:33
pittiinfinity: hm, no binutils on ppc64el?23:38
infinitypitti: There will be.23:38
pittidpkg-dev is uninstallable on ppc64el apparently23:38
infinitywgrant: Testing aptitude now.23:38
infinitypitti: I'll get it built in a sec.23:38
infinityActually, I guess it can happen now.23:39
pittiinfinity: ah, I wondered how I ran those autopkgtests on ppc64 yesterday; I re-bootstrapped the containers today, and it now magically got broken23:39
pittibut from what you say it has never existed yet23:39
infinitypitti: It existed in the previous incarnation of the archive. :P23:40
pittiinfinity: ah, so I'm not going mad :)23:40
infinitypitti: You might also be doing that.23:40
pittiinfinity: well, I'm going mad for a lot of other reasons, yes :)23:40
pitti(not to the least about killing two of my four ppc64el nodes already..)23:41
infinitypitti: Right.  So, I may not have warned everyone.  By the way, I broke ppc64el last night.23:41
infinity(Blame RedHat)23:41
pittiinfinity: with the eglibc upload?23:42
pittiinfinity: oh, perhaps that's the reason what killed wolfe04..23:42
infinitypitti: Yeah.  Dropped all the symbol versions from @2.18 to @2.17, dumped the contents of the archive, and rebuilt the world.23:42
pittihah23:42
pittiinfinity: so that explains the binutils lobotomy, thanks23:43
wgrantSo the ppc64el linker is currently a complete hack.23:43
infinityCOMPLETE HACK.23:43
infinityMORE UPPER CASE NEEDED.23:43
wgrantIt remaps @GLIBC_2.18 to @GLIBC_2.1723:43
pittiah, I've seen a complaint about that symbol earlier on23:44
wgrantSo we don't have to do a full cross rebootstrap, just rebuild everything with the new eglibc23:44
infinity(And a hacked binutils)23:44
wgrantSome builds will explode until their build-deps are sane23:44
wgrantBut it's been reasoanbly well behaved so far.23:44
infinityIt's all working remarkably well, to be fair.  Not just reasonably well.23:44
infinityI'm waiting for the other shoe to drop.23:45
wgrantIndeed23:45
infinitypitti: Check the diff for 2.18-0ubuntu7 if you want to lose a small portion of your remaining sanity.23:45
infinitywgrant: aptitude happy with -O2, uploading hack^Wfix.23:49
infinityWell, it passed that link failure anyway.  Watch it fail later, now that I've uploaded.23:50
wgrantHeh23:50
infinityI need a way to tell soyuz "don't accept the binaries for this upload until I've looked at the build log because the maintainer doesn't believe in failing on testsuite breakages".23:51
* infinity stares at binutils.23:51
wgrant:(23:54
infinityKay, looks good.  Yay.23:54
infinitySo, binutils in the archive should work fine for linking against any NEW binaries.23:55
infinityBut will have an incredible sad trying to link against old stuff.23:55
wgrantYou have a greater version in bootstrap, right?23:56
infinitywgrant: Yeahp.23:56
infinitywgrant: 3.1 instead of 323:56
infinitywgrant: And doko's agreed not to upload binutils until I say it's cool (or will warn me first so I can reapply my hack)23:56
infinityBut the way we're going, we probably only have a couple of days left, at most.23:57
infinityAssuming I get those other 8 VMs online tomorrow morning.23:57
infinitywgrant: And yeah, per our previous discussion, this seems to be the only "clean" way to change optimisation in a dh(1) package:23:57
infinityhttp://launchpadlibrarian.net/166583882/aptitude_0.6.8.2-1ubuntu3_0.6.8.2-1ubuntu4.diff.gz23:58
wgrantew23:58
wgrantBut yeah, another 8 VMs will have us done by Thursday.23:58
wgrantEasily.23:58
infinitywgrant: Which is just so many forms of icky.  Must see if we can do something less gross in debhelper or dpkg.23:58

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