/srv/irclogs.ubuntu.com/2013/07/18/#ubuntu-devel.txt

=== thomi is now known as thomi|lunch
=== thomi|lunch is now known as thomi
pittiGood morning03:30
pittibdmurray: I am now; I got your mail03:30
=== _ffio_ is now known as ffio
=== Guest81623 is now known as Zic
rbasakcjwatson: thanks! I'll retry.06:58
=== smb` is now known as smb
dholbachgood morning07:17
cjwatsonrbasak: OK - better do it quick because otherwise I might manage to land this whole stack in saucy first :)07:25
rbasakcjwatson: done. It's building now :)07:25
cjwatsoncool07:28
=== tkamppeter_ is now known as tkamppeter
=== iahmad is now known as iahmad|afk
doko_SpamapS, online?09:04
=== doko_ is now known as doko
=== iahmad|afk is now known as iahmad
tvoss_xnox, ping09:10
yolandahi, what steps do i need to follow to test lua 5.2 and ruby 1.9 ? i checked package rubyluabridge but it defaults to ruby 1.809:14
xnoxtvoss_: heya09:16
yolandaxnox, do you know about that? how to test lua 5.2 bindings for ruby 1.9?09:26
xnoxyolanda: nope =) no idea.09:26
yolandafound that rubyluabridge package but it forces ruby 1.8, so no clue09:27
Ph0busruby is a wore09:29
cjwatsonPh0bus: That's hardly appropriate here09:31
yolandacjwatson, do you know about how to test that bindings?09:31
yolandai'm a bit lost on it09:31
cjwatsonyolanda: Sorry, haven't the foggiest.  Perhaps contact the Debian maintainers, or the appropriate language development communities09:32
yolandaScottK seems to be the latest uploader09:34
yolandai'll try09:34
rbasakinfinity: have you upstreamed your golang header patch? Or does someone need to do this?09:46
cjwatsonPh0bus> charming chap09:47
cjwatsonyolanda: Note that rubyluabridge was just auto-synced from Debian, so you might want to update your working tree if you're working on it09:52
cjwatson(0.7.0-2)09:52
cjwatsonOr, well, would just have been auto-synced if bits of LP weren't disabled in preparation for a deployment09:54
yolandacjwatson, lp still shows 0.7.0-1 version09:54
cjwatsonSee my previous comment :)09:54
yolandawas typing at same moment :)09:55
cjwatsonBut you can grab it from https://launchpad.net/debian/+source/rubyluabridge/0.7.0-2 in the meantime09:55
yolandaok09:55
yolandajust working on other issue now and i'll grab later, great09:56
jamespagedoko, we where going to talk about go policies this week - when suits you?10:12
tvoss_ogra_, ping10:13
ogra_tvyup10:16
ogra_eh10:16
ogra_tvoss_, yup ?10:18
dokojamespage, today is fine, after lunch? 2pm?10:18
jamespagedoko, yeah - thats good with me10:19
infinityrbasak: I can push it to Debian, but I'd rather someone bypass them and upstream it directly for me, if we have a decent working relationship with them.10:23
cjwatsonyolanda: it's synced and (mostly) built now10:23
yolandagreat10:24
sil2100mardy: hello!10:31
sil2100mardy: I'm looking at lp:webaccounts-browser-extension right now10:31
sil2100mardy: it's not daily-released right now, and I see there are no integration tests there - only unit tests10:32
sil2100mardy: do you think it's possible to do integration testing with those branches?10:32
rbasakinfinity: OK, I'll ask.10:35
rbasakinfinity, jamespage: bug 1187722 is fixed now then, right, both for dpkg and golang?10:39
ubottubug 1187722 in golang (Ubuntu) "dpkg-shlibdeps fails on armhf ELF binaries that do not define architecture specific information" [High,Confirmed] https://launchpad.net/bugs/118772210:39
infinityrbasak: Oh, I didn't know there was a bug for it.10:44
infinityrbasak: Closed.10:45
dokoinfinity, eglibc ping10:47
mardysil2100: I doubt it, it's something very difficult to test10:50
mardysil2100: unless it's possible to programmatically login into facebook10:50
infinitydoko: See /msg10:50
dokothanks10:51
sil2100mardy: ACK10:54
rbasakinfinity: no problem. I just wanted to check that there aren't any tasks remaining, apart from upstreaming.10:55
infinityrbasak: Nah, my simple 3-line patch should DTRT and be upstreamable.10:56
rbasakack11:00
rbasakI've asked Dave to look into it.11:00
=== MacSlow is now known as MacSlow|lunch
=== greyback is now known as greyback|lunch
yolandacjwatson, i checked rubyluabridge package, but it still forces ruby 1.811:19
cjwatsonyolanda: Sure, I don't actually know about it, I was just letting you know that there was an update since you said you were working on it11:27
yolandai messaged ScottK to talk about it11:28
Davieyyolanda: Do you have a partially done branch or dsc you can throw somewhere?11:34
yolandaDaviey, for the ruby issue?11:35
yolandai just grabbed rubyluabridge but it has a patch forcing to ruby 1.8, i was told to test with 1.9 so not sure about how to act11:36
=== greyback|lunch is now known as greyback
Davieyyolanda: Right, ScottK did an NMU in Debian, perhaps he has more info.  Looking at the upstream project, certainly no fix there.12:03
yolandaDaviey, i pushed a MP for rrdtool, that one is working12:04
Davieyyolanda: super12:09
=== MacSlow|lunch is now known as MacSlow
evany archive admins around who want to NEW something for me? https://launchpad.net/ubuntu/saucy/+queue?queue_state=0&queue_text=whoopsie-preferences13:02
dobeyLaney: sigh. i wonder how these tests ever passed in autopkgtest…13:18
pittisoftware-center? they never did13:21
dobeypitti: really? the entire time that software-center has had autopkgtest setup, it's never actually passed?13:27
pittiyes, despite several pings they've never been fixed13:27
pittiFWIW, if nobody has the time or cares, and there is an upstream test suite that at least succeeds locally, it could just be dropped13:28
dobeyi don't know if the tests work locally13:29
dobeythe tests are doing a lot of nasty broken things13:30
SpamapSdoko: online now. Wassup?13:31
dokoSpamapS, did you try to cross-build mysql in the past?13:35
=== jtechidna is now known as JontheEchidna
dobeypitti: ok, since they've never actually worked, i just uploaded a software-center that just removes debian/tests and the X-Testsuite:, please do what you need to do to the jenkins job/britney as a result of that :)13:55
pittidobey: ack13:55
pittijibel: ^ on that note, I'll remove the job from the actual jenkins; does britney look at that, or at the public mirror?13:56
=== jono is now known as Guest30113
jibelpitti, none of them the status is kept on lillypilly. it must be removed from there.13:57
pittijibel: hm,  where do I find that?13:59
pittijibel: proposed-migration/autopkgtest/data/adt/saucy-proposed/amd64/saucy-proposed_amd64_software-center ?14:02
pittijibel: just wipe that?14:02
sergiusenscjwatson: seems I made a mistake with the click hook by using people.canonical.com (external name), what's the host or fqdn that the builders see? lillypilly.canonical.com, just lillypilly or another internal domain?14:18
=== balloons_ is now known as balloons
stgrabersergiusens: archive-team.internal but that's a view of people.canonical.com/~ubuntu-archive14:20
dobeydholbach: hi! can you take another peak at bug #1199017 please? i've updated the dsc/debian.tar for it. thanks14:22
ubottubug 1199017 in Ubuntu "[needs-packaging] ubuntuone-credentials" [Wishlist,New] https://launchpad.net/bugs/119901714:22
sergiusensstgraber: ah, so I need one more step14:23
dholbachdobey, will do14:24
sergiusensogra_: ideas? ^^14:24
ogra_sergiusens, oh, i totally forgot14:24
dobeypitti: so i'm not sure what to do about the u1-client autopkgtest issue. will you add the feature flag to ignore stderr? hacking up the tests to work around autopkgtest behaving differently than everything else seems wrong to me :)14:25
stgrabersergiusens: where are those files on lillypilly?14:25
sergiusensstgraber: http://people.canonical.com/~sergiusens/click_packages/ but they can be anywhere14:25
sergiusensstgraber: you can copy them ... this is what I do  ~sergiusens/click_ready/click_copy.py https://jenkins.qa.ubuntu.com ~/public_html/click_packages14:26
ogra_sergiusens, i tallked to cjwatson already ... but wanted to wait for you :) ... the machine is reachable under a different name ond only ~/ubuntu-rachive can be seen ... i think running your copy script from an ubuntu-arechive cronjob and have it dump into ~/ubuntu-archive/public_html/click-packages would be best14:26
ogra_stgraber, ^^^14:26
stgraberI just put a symlink, looks like it's working: http://people.canonical.com/~ubuntu-archive/click_packages/14:26
sergiusensstgraber: awesome14:26
stgraberon disk, that's a symlink to /home/sergiusens/public_html/click_packages14:26
ogra_stgraber, well, i'm not sure the access from cadejo works that way14:27
stgraberogra_: let me check that14:27
stgraberogra_: it does14:27
ogra_sergiusens, so now we need to change the url to http://archive-team.internal/ in livecd-rootfs14:28
ogra_(with the proper path indeed)14:28
stgraberogra_: I just tried with wget http://archive-team.internal/click_packages/com.ubuntu.calendar-app_0.4_all.click -O /dev/null from nusakan and that worked fine14:28
ogra_stgraber, you have a login on cadejo ?14:28
sergiusensogra_: do you feel jealous? :-P14:28
stgraberogra_: no, but nusakan has access to that vhost/proxy server14:28
ogra_nusakan doesnt help :)14:28
ogra_the buildd needs to be able to see it14:28
ogra_i can see it pulls the seeds from http://archive-team.internal/seeds/14:29
ogra_http://archive-team.internal/ being lilliypilly14:29
ogra_(see live-build/auto/config)14:29
stgraberogra_: archive-team.internal == 91.189.89.174 which is a separate IP from the main lillypilly IP, so if cadejo can access it, then it has the same view as I'm getting from nusakan which works when access archive-team.internal/click_packages, so I'm 99% sure it'll work fine from cadejo14:30
ogra_ok14:30
ogra_let me change livecd-rootfs and upload14:31
stgraber(the remaining 1% would be IS sending that traffic to squid and having some ACLs restricting to sub-directories of archive-team.internal, but I very much doubt they'd do that)14:31
ogra_sergiusens, stgraber, livecd-rootfs change and uploaded14:34
ogra_lets see how the next build goes14:35
pittidobey: we can add the feature flag (bug appreciated, so that I don't forget and we can coordinate who will do it); hacking autopkgtest is always a lot of "fun", might take a bit14:35
dobeypitti: ok, i'll get a bug filed14:35
cjwatsonsergiusens: So, I'd prefer for the ubuntu-archive user to be fetching the click packages itself rather than symlinking into your home directory14:36
cjwatsonsergiusens: Not least because archive-team.internal will soon be a separate *machine*, not just a separate IP address14:36
cjwatsonsergiusens: Is it possible to run click_copy.py on lillypilly?  I couldn't figure out which Jenkins base URL to use14:36
sergiusenscjwatson: this is what I do  ~sergiusens/click_ready/click_copy.py https://jenkins.qa.ubuntu.com ~/public_html/click_packages14:37
SpamapSdoko: no, I have noly ever built it for x8614:38
SpamapSonly14:38
SpamapSdoko: well and arm ... it has some signed char issues IIRC14:38
cjwatsonsergiusens: Huh, could've sworn I'd tried that, thanks14:39
cjwatsonsergiusens: I'll cron that in a bit then14:39
ogra_yay14:39
sergiusensthanks14:40
cjwatsonsergiusens: do you have it cronned at the moment?  what's the frequency?14:41
sergiusenscjwatson: I don't, wanted to get an intial build before stressing anything, the click packages are built once a day, so once a day is good enough14:42
sergiusensa good time would be before the actual touch build but not really as important14:42
ogra_cjwatson, something like 6 or 7am UTC should be fine14:45
pittijibel: did you notice my question about removing the britney software-center check?14:48
pittipitti | jibel: proposed-migration/autopkgtest/data/adt/saucy-proposed/amd64/saucy-proposed_amd64_software-center ← just wipe that?14:48
jibelpitti, yes that's the file, but if the source with a XS-TEstsuite header is still available in the release pocket it will recreate it.14:49
pittijibel: ah, chicken-egg problem14:50
jibelpitti, yes. the copy must be forced, in any case that won't hurt since the tests have been removed.14:53
sil2100Wellark: hi!14:55
sil2100Wellark: could you tell me what's up with lp:~unity-team/unity-action-api/nohud ? Is it supposed to be daily-released as well? Should this land to distro?14:56
jodhjibel/pitti: hi - can I pester you about bug 1158391? I need to get DEP-8 integration tests working for upstart in the next few weeks so really need the ability for an autopkgtest env to spin up a nested kvm instance say and prod it in various ways.15:17
ubottubug 1158391 in Auto Package Testing "ability to have a DEP-8 test run a test in a separate full system environment" [High,Confirmed] https://launchpad.net/bugs/115839115:17
rbasakPerhaps I should write an adt-virt-libvirt at some point15:22
rbasakOr just a direct adt-virt-kvm15:23
rbasakxnox: I'm having some trouble reproducing your apache 2.4 upgrade problem. I tried installing libapache2-mod-wsgi first, but the upgrade didn't fail.15:25
xnoxrbasak: i'll try to recreate my setup and i'll let you know.15:26
rbasakTHanks15:26
rbasakLooks like apt chose in my case to configure libapache2-mod-wsgi before apache2.2-bin but after all unpacks.15:28
rbasakI'm not quite clear on the ordering required to reproduce it.15:28
pittijibel: ah, thanks15:32
pittiLaney: can you do the magic to let software-center in despite failing tests? (-proposed removes the tests deliberately)15:32
Laneypitti: how are there failing tests then?15:33
cjwatsonLaney: Apparently something in the stack is not good at handling removed tests and considers them a failure15:36
pittiLaney: it never succeeded, but jibel says our britney integration requires forcing this once15:36
cjwatsonThat is, adt-britney incorrectly requests a test run when there are no tests in that case15:36
LaneyYeah, seems like a bug15:36
Laneyas long as jibel knows about it :-)15:36
cjwatsonShould be sufficient to force-badtest it15:37
Laneyindeed, but I didn't want to without making people at least aware15:37
pittiwell, that saved us from accidentally losing tests yesterday15:37
pittiand it's the first time we actually remove a test (and I hope that won't happen too often)15:37
mdeslaurrbasak: are you planning on merging php5 5.5.0+dfsg-15 ?15:42
rbasakmdeslaur: wow. Struggling to keep up!15:45
* rbasak looks15:45
rbasakmdeslaur: I understand why you asked now. If I do, I won't get around to it until tomorrow afternoon at the earliest I think. Do you need it sooner?15:46
mdeslaurrbasak: I can do it now if you don't mind15:46
rbasakmdeslaur: sure, go ahead. Or just a cherry-pick if that's appropriate. At the pace they're going I expect to do at least another merge before release.15:47
mdeslaurrbasak: ok, I'll handle it...just wanted to make sure you didn't start something already. Thanks!15:47
stgrabercjwatson: hey, so I'm looking at those ubiquity and grub2 changes to always install and use the shim on EFI. My current plan is to simply remove the sb check in ubiquity so we always install shim-signed, grub2-signed and linux-signed, then change grub-install to always set the shim as the boot entry if it exists and grub2-signed is installed. Did I miss anything?15:48
rbasakmdeslaur: OK. Thanks for checking!15:48
sil2100Wellark: if you're around, could you backlog to the question I posted earlier?15:52
sil2100Wellark: thanks15:52
cjwatsonstgraber: You need to change grub-installer as well, before ubiquity15:53
cjwatson(i.e. both grub-install and grub-installer)15:53
Laneyev: Hey, I'm just looking at your system-settings MP... is it supposed to work on desktop?15:54
Laneyyour first isValid() call returns false here for me15:54
evLaney: it needs activity-log-manager installed at the same time. I'm working on splitting out the dbus service into the whoopsie-preferences package15:54
Laneyev: I already had that15:55
LaneyI can see it in d-feet (but get polkit errors when I try to query the methods)15:55
evoh right, sorry15:55
evthe other part is you need to abuse /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla15:56
smoserpitti, i'm looking at ./debian/extra/initramfs.top in lp:ubuntu/systemd15:56
smoserhttp://paste.ubuntu.com/5887973/15:56
evChange crash reporting settings]15:56
evIdentity=unix-group:admin15:56
evAction=com.ubuntu.whoopsiepreferences.change15:56
evResultActive=yes15:56
evLaney: ^15:56
smoserthe ROOTDELAY lines blame to you. i dont think that you authored them, but i'm wondering if you could provide some insigth there.15:57
stgrabercjwatson: ah right, forgot that one, thanks15:57
pittismoser: no idea, I'm afraid; I mostly took what we had in the old udev scripts, and I was afraid to remove it15:57
pittismoser: but it is certainly a gross hack15:57
pittismoser: as with wait-for-root it should just work15:58
smoserpitti, i've never seen it before15:58
smoserit is not in raring15:58
pittismoser: ah, then maybe it came in through debian15:59
smoserthey dont have that file in their systmed package15:59
pittismoser: right, not in version 44, it's from the 182 packages15:59
pittismoser: anyway, is that creating a problem?15:59
pittismoser: we can certainly take it out, but it seems like a no-op15:59
smoserfor context, on azure, we had been booting with the 'rootdelay=' which is a similarly crappy hack to deal with the fact that their scsi disks are terribly underperformant.16:00
smoserand now we're seeing bug 1202700 because of this sleep.16:00
ubottubug 1202700 in linux (Ubuntu Saucy) "saucy kernel 300 second hang before root mounted rw on azure" [Medium,Confirmed] https://launchpad.net/bugs/120270016:00
smoserits not a no-op for sure.16:00
smoserif you boot with rootdelay= it most definitely causes a sleep of that long.16:00
pittismoser: yes, but I meant if that didn't exist in raring, why would this parameter exist?16:01
smoserthe parameter in raring goes to wait-for-root16:01
smoserit increases its default timeout16:01
smoser(and it still doe sgo there in saucy, it just also gets used here :)16:02
utlemmingrootdelay for the kernel means wait up to X for the root to appear, but doesn't have to wait that long16:02
smoserutlemming, it doesn't mean anything to the kernel.16:02
pittismoser: aah, ok; so we shared the parameter, but now got a second implementation16:02
smoserjust to 'wait-for-root'16:02
smoserand initramfs.16:02
smoserwell, it seems it came and went in debian.16:03
smoserhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=41484216:03
ubottuDebian bug 414842 in udev "udev: Add support for the ROOTDELAY parameter" [Serious,Fixed]16:03
smoseri suspect somehow we merged bad or something...16:03
pittino, they just implemented it differently16:03
smoserhm..16:03
pittithe wait-for-root program is an ubuntuism, it's not in debian16:03
smoserwell, wait-for-root is better.  :)16:03
pittiso the sleep shoudl certainly go away from the initramfs script then16:03
utlemmingsmoser: https://www.kernel.org/doc/Documentation/kernel-parameters.txt16:03
pittismoser: wait-for-root is better> for sure :)16:04
smoserutlemming, it must do nothing if there is an initramfs.16:04
pittismoser: the part that I don't understand is why that parameter is needed at all; it still smells like a bad hack16:04
pittisleep is never the right answer for those kinds of problems16:04
smoserpitti, it is.16:05
smoserwell, right.16:05
utlemmingpitti: for Azure, it was requested by MS16:05
smoseron azure its necessary16:05
smoserbecause their devices suck16:05
smoserthe disks might just not wake up for 300 seconds16:05
smoserand you should pretned that is not a bug16:05
* smoser ends rant16:05
smoseranyway.16:05
smoserpitti, so you support me just dropping those lines in our systemd ?16:06
pittismoser: ah, so is that mostly to just extend the timeout of wait-for-root? (that defaults to 60 seconds, I think)16:06
utlemmingthe actual reason, given by MS is that on earlier version of Azure, the network backed devices might have the full the disk presented during the time of boot.....but smoser summed it up nicely16:06
pittismoser: yes, sure16:06
smoserpitti, thanks for your help.16:06
pittiso for ubuntu, that command line argument should mostly change the 60 seconds wait-for-root timeout, not actually sleep for that time16:06
smoserpitti, it does16:06
pittiwith that semantics it would make sense, WDYT?16:06
pittiah, good16:06
pittismoser: thanks!16:07
smoseror at least it used to :)16:07
smoserbut i'll make sure.16:07
pittismoser: committed to my local packaging git16:10
smoserah.16:10
pittismoser: I plan some other systemd debugging/fixes tomorrow, is that enough? or do you want it uploaded now?16:10
smoserwell then.16:10
smoserthank you.16:10
smoseri was going to do it16:10
smoserbut good enough16:10
smoserin looking, i find that cryptsetup also reads ROOTDELAY16:10
smoserbut it does a 'while sleep .1' for 10 x ROOTDELAY.16:11
smoserso thats much better than 'sleep ROOTDELAY'16:11
smoserbut it should probably still use wait-for-root16:11
cjwatsonjbicha: Um, when you synced https://launchpad.net/ubuntu/+source/packagekit-qt, you did realise that that would break future attempts to upload 0.7-series packagekit, right?16:21
xnoxjodh: looks like pre compiled headers work fine with gcc4.8. So must be something with abi-compliance-checker!16:24
jodhxnox: interesting - I'll take a look tomorrow.16:25
stokachuis there a way to tell bzr to use-existing-dir within the conf file?16:27
jbichacjwatson: I only synced it after packagekit 0.8 had been in saucy-proposed for ~6 weeks16:37
jbichaanyway, the pk8-compatible aptdaemon should be nearly ready for saucy https://code.launchpad.net/~aptdaemon-developers/aptdaemon/main16:38
jbichaI was surprised that pk-qt didn't get stuck in -proposed like the rest of the pk8 stack, and no I didn't realize that would prevent uploading "newer" pk7 updates16:42
dobeyanyone know why i would get a symbols change error immediately after generating the symbols file, building a source package with the new file, and then trying to build the binaries in pbuilder? it makes no sense to me, and i can't figure out how to make it not happen17:05
cjwatsonjbicha: ah, right, packagekit got deleted from -proposed ...17:07
cjwatsonjbicha: indeed, I saw about aptdaemon, I just have packagekit changes to land in advance of that.  I'll work around it17:08
dobeyshould i just pull the .symbols file for now and not worry about it?17:12
cjwatsonwg 2817:13
cjwatsondoh17:13
jdstrandcjwatson, mdeslaur, sbeattie: I just responded to the ubuntu-appstore-developers list asking for confirmation that we agree on the new json structure. can you guys respond (so everyone can be unblocked)?17:24
jdstrandit sounds like we are, but wanted to be sure17:24
sbeattiejdstrand: responded17:27
mdeslaurjdstrand: yep17:28
jdstrandsbeattie: I'll ditch the unconfined profile too17:29
mdeslaurjdstrand: hum? unconfined profile?17:29
jdstrandsorry,unconfined template17:30
mdeslaurwhat do you mean by "ditching it"?17:30
jdstrandmdeslaur: well, sbeattie mentioned we could remove it, but now that I think about it, I think we may still want it17:31
mdeslaurwe can't remove it, the upstart job still needs to switch to it17:31
cjwatsonreplied17:31
cjwatsonThere's no rush to ditch unconfined17:32
jdstrandmdeslaur: right17:32
jdstrandcjwatson: thanks17:32
dobeyanyone?17:32
=== sabdfl_ is now known as sabdfl
sbeattiemdeslaur: ah, right.17:34
cjwatsonjdstrand: It turns out that 30C heat in a country without pervasive aircon is not the optimal weather for doing complex rearrangements of hook execution code, but I'm trying ;-)17:36
cjwatson(Not that I expect complaints about heat to get much sympathy from your neck of the woods)17:36
mdeslaurhehe :)17:36
jdstrandcjwatson: haha :)17:37
jdstrandactually, we've had unseasonably cool and rainy weather here this week :)17:37
slangasek(if you can't stand the heat, stay out of Texas?)17:39
ScottKPlus Texas is the land of pervasive air conditioning.17:39
jdstrandand fans. don't forget the fans17:40
mdeslaurstepping back from the BBQ is kind of like air conditioning17:40
=== dpm_ is now known as dpm
* jdstrand is getting hungry17:41
=== bfiller is now known as bfiller_afk
xnoxdobey: well, please provide logs of the local build and pbuilder. cause e.g. symbols of libraries used can link into your symbols, especially if local build is on raring and pbuilder on saucy-proposed.18:02
dobeyxnox: that seems like a complete failure of the system if so. the symbols provided by a library shouldn't change between raring and saucy18:04
xnoxdobey: depends what you code. if you include a boost template, boot transition from 1.49 to 1.53 between raring and saucy suddently the same API compatible template changes functions, boom you can new/changed symbols in a saucy rebuild.18:06
dobeydoes that only happen with c++ or something crazy?18:06
xnoxdobey: that's not the only case.18:06
xnoxdobey: e.g. gcc-4.8 change symbol visibility / export rules slightly, enough to break bionic and loading binary drivers on android.18:06
xnoxdobey: and that's pure c18:06
xnox(with with assembly)18:07
dobeyso yes, "something crazy" :(18:07
xnoxdobey: so nobody can tell what's going on between your local build and pbuilder, without seeing the logs.18:07
xnoxdobey: i'm sure, our toolchain is deterministic producer of symbols in same or compatible environments.18:07
xnox=)))))18:07
dobey:(18:08
xnoxdobey: better give the URL to the source package in question and the logs of local build vs saucy build.18:08
stgrabercjwatson: is bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/saucy/grub2/saucy/ the right branch for grub2? the status of the patches in this one appears to be a bit weird (they're applied but .pc is empty, so quilt refuses to push/pop patches)18:08
xnoxstgraber: lp:~ubuntu-core-dev/grub/ubuntu ?18:09
xnoxnah, that one looks old.18:10
xnoxstgraber: does http://people.canonical.com/~cjwatson/dpkg-quilt-setup help at all?18:10
stgraberxnox: ah I think it'd yes, that also explains what I'm seeing in the branch I think18:11
dobeyxnox: well, if gcc changed things, then that must be it18:11
xnoxstgraber: i remember using that for some of patches-applied-pc-dir-vcs-ignored packaging styles18:11
stgraber(well, except that .pc exists in my case but is empty ;))18:11
xnoxdobey: don't assume, can you not like pastebin the diff of symbols that pbuilder generated for you?18:12
jdstrandsbeattie: if we have this in the click manifest:18:12
jdstrand"hooks": {18:12
jdstrand  "myapp": {18:12
xnoxstgraber: =)))))) patches-applied-.pc/*-vcs-ignored packaging styles18:12
jdstrand  "apparmor": "apparmor/myapp.json",18:12
dobeyxnox: well, i did gensymbols on raring (local), and pbuilder on saucy, so yeah. it explains it. plus pbuilder didn't fail when building on raring.18:12
dobeyxnox: and the symbols are all low level red-black tree things in qt or something :(18:13
jdstrandsbeattie: I understand the a symlink will be created that is of the form $name_myapp_$version18:13
jdstrandsbeattie: what is creating that symlink?18:13
dobeythat should not be exported anyway, but yay c++ is crazy18:13
jdstrandoh, you know, let me reread the spec18:13
xnoxdobey: c++filt makes those symbols not look crazy. but is it still compatible?! =/18:14
jdstrand"On install, the package manager creates the target path as a symlink to a path provided by the Click package"18:14
jdstrandsbeattie: nm18:14
dobeyxnox: http://pastebin.ubuntu.com/5888378/18:18
=== synaptix is now known as caboose85S
xnoxdobey: looks to me like abi got broken http://paste.ubuntu.com/5888384/18:22
xnoxdobey: and it's not in the Qt* symbols anything. Are you using C++11?18:22
dobeyxnox: no: -std=c++0x is what is passed to g++18:23
stgraberslangasek, cjwatson: So, I've got: http://paste.ubuntu.com/5888394/ http://paste.ubuntu.com/5888396/ http://paste.ubuntu.com/5888397/18:24
stgraberI "think" that's all that needs changing but I can't very easily test it as the real test is spinning a new media with all of those landed18:25
dobeywould be nice if the symbols stuff could avoid things that aren't directly from the library.18:25
stgraberso my plan is to push that to the archive today, spin a new desktop image as soon as I can, test that in an OVMF VM without SB, confirm I boot through shim, and if that's the case, then push the same change to precise tomorrow18:26
dobeybut yes, definitely a change in stl there18:26
xnoxdobey: well, if it's a change in templates, it does get included in your library, it also means at the moment that ABI is broken and you need to recompile all reverse-dependencies as raring packages will fail with this saucy build lib.18:27
dobeyxnox: is there really no way to make this work correctly on both saucy and raring with the same symbols file?18:27
xnoxdobey: the problem here is not about "getting symbols to work", but that abi is broken and incompatible library is getting built.18:28
xnoxthe solution here is to either: bump the soname or fix the abi to stay the same.18:28
dobeythere is no change in abi in the code. this is a problem of g++ breaking things18:28
dobeyall i want to do is have a package that can be built on both saucy and on raring, without changes18:29
dobeywhy is that so hard to do?18:29
xnoxwell a crashing application doesn't care where the problem is, apart from that libfoo.so.2.0.0 is missing symbols.18:29
xnoxdobey: it is most likely in your code. By the say specifying -std=c++0x is unstable abi as that's what c++11 was known as before releasing.18:30
dobey"they say" ? who is they? and where do they say that?18:31
=== caboose85S is now known as synaptix
dobey(and it's not my code, i didn't write libsdtd++)18:31
xnoxdobey: Gnu GCC upstream -- enable experimental features to support c++11 standard.18:31
xnoxdobey: the package specified to build with that standard enabled one way or the other, thus it's in the package's code. as c++0x is not the default.18:32
xnox(packaging or upstream)18:33
xnoxSET (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++0x -O2 -g -Wall -Werror -fPIC") in https://bazaar.launchpad.net/~ubuntuone-control-tower/ubuntuone-credentials/trunk/view/head:/CMakeLists.txt18:34
xnoxdobey: try compile on raring without specifying "-std=c++0x" and compile on saucy, and compare the symbols between the two.18:34
xnox"Important: GCC's support for C++11 is still experimental. Some features were implemented based on early proposals, and no attempt will be made to maintain backward compatibility when they are updated to match the final C++11 standard."18:35
xnoxhttp://gcc.gnu.org/projects/cxx0x.html18:35
dokodobey, why do you include symbols of libstdc++ at all in the symbols files?18:35
dobeydoko: i didn't make a choice to do so18:35
dokodobey, but you do have the choice to fix it18:35
dobeyi'm trying to understand why those symbols are there, and how to fix it18:36
dobeybut telling me my library broke ABI just because it was built on a different version of ubuntu doesn't help me18:36
xnoxdoko: how? mark them as (optional)? but isn't the abi broken?18:36
dokoxnox, how would it? it's not part of the API of this library18:37
dobey error: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [-Werror]18:38
dobeybah18:38
xnox(yeah, c++0x is now aliased to c++11, due to standard rename after final publication)18:38
xnoxdobey: (c++|regex|optional)"std::.*@Base 13.07" in the symbols file, should make any removals/changes ignored under std::* namespace.18:44
dobeyxnox: where is that documented? http://wiki.debian.org/UsingSymbolsFiles is not especially helpful here :-/18:50
xnoxdobey: man dpkg-gensymbols and https://wiki.ubuntu.com/DailyRelease/FAQ#I.27m_exposing_a_new_C.2BAC8-C.2B-.2B-_symbols_in_my_library.2C_it_seems_that_some_packaging_changes_are_needed.2BICY-18:51
xnoxdobey: the later shows how to use "c++" filter/tag, but not the others "optional, arch, ignore-blakclist, symver, regex"18:53
dobeyxnox: what should be in the .symbols file though? the mangled symbols, or the filtered ones?18:54
dobeyit's not exactly clear what the preference is for that18:55
xnoxdobey: so by default one uses symbols as they are _Zloadsofgibberish@Base 1.0, but that's not very nice for C++ since some of mangled names are architecture specific due to different sizes of things.18:55
dobeyxnox: so it would also likely fail building on i386 or arm, even if it didn't fail on amd64, with the mangled symbols?18:57
xnoxdobey: thus ideally for most symbols one would use full symbols (those that stay the same across all arches), and for arch specific ones use (c++)"myclass::foo()" name, to avoid commiting symbols.i386 symbols.armhf etc...18:57
xnoxdobey: correct.18:57
xnoxdobey: because c++ is crazy, i preffer to use (c++) for all c++ symbols, to have demangled names across the board. That does hide some changes, where mangled name changes to indicate some abi change, yet demangled name is staying the same.18:58
xnoxbut that's the price one pays for it.18:58
dobeyit would be nice if gensymbols just did the right thing…18:58
xnoxdobey: to catch remaining changes, I'm working on making dh-acc which takes complete dump of symbols & headers for each arch and generates and checks both ABI and API compatibility.18:59
xnoxby using abi-compliance-checker18:59
xnoxbut that's still work in progress.18:59
xnoxdobey: i think, it would be all ok in your case and "done the right thing..." if c++0x/c++11 was not used =/19:00
dobeyxnox: well, no. it wouldn't have the (c++)Foo::bar()@Base for all the symbols, they'd still be mangled19:01
dobeyand it would still probably include things that aren't really part of the library itself, i presume19:02
xnoxdobey: yeah, true, since the std::* is for some reason exported in your example.19:03
xnoxlet me find another example i did.19:03
xnoxdobey: https://code.launchpad.net/~didrocks/qtubuntu-sensors/symbols/+merge/17060319:04
xnoxin that one there are actually all symbols part of the api, and no other stuff from std::*19:04
xnoxdobey: i'm not that good with c++ but it is strange that std::* symbols are getting exported.19:05
dobeyand QByteArray::* is also being exported19:05
slangasekstgraber: testing the whole thing might require an image, but surely the grub2 package itself could be tested locally?  since the grub2 package should fix this up on upgrade as well19:05
dobeywhy is all this stuff being exported here i wonder :(19:06
dobey (c++)"QString::QString(char const*)@Base" 13.0719:06
dobeyfor example19:06
slangasekstgraber: although, does the installer not install grub2-efi-amd64-signed for us in that case? hrm19:06
dobeythat doesn't belong there. we don't provide the QString object19:06
xnoxdobey: i never had formal C++ education, so it's all even more fuzzy to me =)19:06
infinityxnox: Make the upstart testsuite stop sucking.  Thanks.19:07
slangasek(grub-efi-amd64-signed, I mean)19:07
xnoxinfinity: yeah, that would be good..... managed to reproduce it outside of launchpad?19:08
xnoxinfinity: i could disable it on powerpc/buildds, but it does seem wrong, w.r.t. how and why it's hanging.19:09
infinityxnox: Erm, I probably can, except the thing that triggered the memory was mir, not upstart.  It's one of those days.19:09
slangasekstgraber: so actually, that's a point... what does http://paste.ubuntu.com/5888394/ wind up doing on upgrade, if grub-efi-amd64-signed (or shim-signed) is not installed?  seems like it'll fail?19:09
infinityxnox: Can I blame you for the Mir testsuite too? :)19:09
xnoxinfinity: sure! =) if that helps you work, why not.... =)19:09
infinityAwesome.  Done.  Big jerk.19:10
slangasekstgraber: ahhh nope, I see -     if [ "$uefi_secure_boot" = yes ] && [ -e "$efi_signed" ]; then19:10
stgraberslangasek: right, it won't fail but won't install the missing package either. So upgrades won't magically fix systems, they'd still have to install the packages or reinstall.19:11
stgraberslangasek: though by the nature of the bugs reported so far, I doubt it's a big problem as people aren't likely to be able to boot the system in the first place19:12
xnoxa quirk could be added to do-release-upgrade?!19:12
stgraberxnox: well, any system that booted isn't likely to be affected by the bug so I don't see what that'd gain us19:14
slangasekstgraber: right, there is that :-)19:14
slangasekstgraber: anyway, that does mean a useful test of grub post-install would be to install grub-efi-amd64-signed + shim-signed, rerun grub-install on a non-SB system, and see what happens19:15
stgraberslangasek: yep, doing that now19:15
xnoxstgraber: is there a bug description? i'd like to be able to have efi machine install, upgrade bios, toggle secureboot on, reboot and it boots/works.19:15
slangasekstgraber: it gains us future-proofing against firmware changes down the line, fwiw19:15
stgraberslangasek: confirmed that a non-SB system becomes SB-ready once shim-signed and grub-efi-amd64-signed is installed (and not before those two are)19:18
stgraberxnox: the bug I'm trying to address here is https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/118429719:18
ubottuUbuntu bug 1184297 in ubiquity (Ubuntu Precise) "Secure boot failed, claiming boot is against security policy" [High,Triaged]19:18
slangasekstgraber: ok, cool19:18
stgraberxnox: so I'm mostly interested by new installs of 13.10 and 12.04.319:18
stgraberslangasek: so I'll upload the new grub2 and grub-installer, wait for those two to publish in the release pocket, then push ubiquity and test a new daily, if all looks good, I'll push the same to precise-proposed tomorrow19:19
slangasekstgraber: LGTM19:19
stgraberif we really wanted all existing users to get the shim by default, the easiest way would be for grub-efi-amd64 to depend on grub-efi-amd64-signed and shim-signed (or recommend them)19:20
stgrabernot sure it's something we want to do just yet though19:20
xnoxstgraber: i see. so i guess i can simply install *-signed here to be like everyone else ;-)19:21
stgraberxnox: yep, install all the -signed then the grub I'll upload in a minute and it'll just work19:22
slangasekmaking grub-efi-amd64 depend on grub-efi-amd64-signed would present bootstrapping problems19:23
=== bfiller_afk is now known as bfiller
stgrabergood point19:26
dobeyxnox, doko: ok, i got a version building, but it has some +symbols mentioned in the build log, for a bunch of Qt stuff, which also shouldn't be exported. would prefer to just make it so this stuff isn't getting exported if you have any ideas, but if i have to add the optional/regex flag for them, i guess i can do that too.19:41
xnoxdobey: .symbols file is merely a dpkg check. nm -C -D *.so still shows all of those symbols exported.19:44
xnoxdobey: if compiled like so:19:45
xnoxg++ -fvisibility=hidden -Wl,-z,relro -Wl,-Bsymbolic-functions -std=gnu++11 -fPIC -I. -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I/usr/include/qt5/QtNetwork -I/usr/include/libsecret-1 -I/usr/include/glib-2.0/ -I/usr/lib/x86_64-linux-gnu/glib-2.0/include/ -DPROJECT_VERSION='"foo"' -shared -Wl,-soname,1.0 -o libfoo.so *.cpp19:45
xnoxdobey: i get a reduction from 736 -> 467 symbols exported, but it still shows a lot of stuff exported.19:45
xnoxdobey: there is some indication that when a derived class is exported, its parents class' symbols also get exported19:46
dobeyxnox: i don't think we're deriving from QString or QByteArray anywhere. only QObject or maybe something higher level19:47
slangasekthe surest way to control what symbols are exported is to use a version script19:49
xnoxslangasek: do you have an example for c++ code though?19:51
xnox-fvisibility-inlines-hidden brings me down to 393 exported symbols.19:51
dobeyi wonder if it's moc that's causing the problem19:51
slangasekno, I expect the version script for C++ might not be very pretty :)19:52
slangasekbut would support globbing19:52
slangasekon symbol names, not on C++ function names19:52
xnoxbut like even things like "oauth_free_array" are still exported, which is C functions, from a linked library19:53
cjwatsonstgraber: Those all look basically right to me.  Thanks.19:54
cjwatson(Belatedly)19:54
xnoxslangasek: dobey: even with version script matching against public* results in 189 symbols exported with many unneeded ones20:01
xnoxhttp://paste.ubuntu.com/5888666/20:01
xnoxwhich is better than current 736 symbols.20:02
xnox(down to 189 at the moment)20:02
dobeyxnox: not sure where you got the 736 from20:03
xnoxwell nm -C -D *.so | wc20:03
xnoxor is that not the same as exported symbols?20:03
dobeyxnox: add --defined-only do that nm?20:04
xnoxdobey: down to 1 symbol, I guess I overdid it now =)20:06
xnoxgreat, now I only have std::* symbols exported and none of the UbuntuOne::* =(20:07
dobeyi have 170 with -fvisibility-inlines-hidden and -Wl,--as-needed20:07
xnoxdobey: yeah, that looks good. all the C stuff is gone, but there is till a bit of std::* left and Q* stuff.20:09
dobeyyeah, i'd love to know how to get rid of the stl and qt stuff20:09
xnoxdobey: http://accu.org/index.php/journals/1372 seems like a proper description of versioned script for C++20:10
xnoxdobey: win!20:14
xnoxdobey: http://paste.ubuntu.com/5888713/20:14
xnoxdobey: -Wl,--version-script=exports.version   , where exports.version has20:14
xnoxdobey:20:15
xnoxhttp://paste.ubuntu.com/5888715/20:15
xnoxslangasek: ^^^ just like dpkg-gensymbols has (c++) filter for names, so does GNU linker.20:15
dobeywonder if i should bother with the --as-needed then20:17
xnoxdobey: i don't think you should. at the moment this is a catch all script. but you can wrap it with UBUNTU_ONE_13.07 { }; for example to version your symbols, and then you can change the abi, by exporting updated symbol under new version.20:19
xnoxdobey: as done later on in the article from http://accu.org/index.php/journals/137220:19
xnoxdobey: so, now my question, is why doesn't "the toolchain do the right thing by default", it's not that hard to syntactically see what's getting exported / public.20:21
dobeyyeah, i don't know :)20:22
xnoxdobey: thanks for bringing this issue up, this was fun =)20:23
dobeyxnox: well, i suppose using globs together with symbol versioning, is not a great plan20:23
dobeywould need to be explicit for that20:24
=== Soupermanito is now known as GridCube
xnoxdobey: there is -export-symbols-regex that can be used instead of writting it out in a file for simple regexp.20:30
=== Soupermanito is now known as GridCube
dobeyxnox: it would be easier if c++ didn't require #include of private headers, to satisfy usage of things from them in the private section of a class20:41
dobeybecause i really don't want to export *all* the symbols, only some of them. but since we're forced to install extra headers, it's a bit of a pain20:42
dobeyhopefully i can figure out a way to fix that soon though, and only export the things we want/need to export20:43
xnoxnow, you are just getting picky =)20:44
dobeywell, i just don't want people to use API that is almost certainly going to break :)20:44
xnox=)))))))20:44
dobeyoops20:57
dobey/home/dobey/Projects/canonical/ubuntuone-credentials/authlib-export-map/libubuntuoneauth/requests.h:44: undefined reference to `vtable for UbuntuOne::OAuthTokenRequest'20:58
dobeyplenty of those when it tries to build the test program that links20:58
dobeythat's with UbuntuOne::*; in the version script20:58
dobeythe 'vtable for FOo*' are definitely not in the nm output now :-/21:06
dobeyso this sucks :(21:07
dobeyoh, wtf; cmake is being stupid. it's trying to add the -Wl,--version-script= to the test target as well. even though i only added to the lib target.21:26
Noskcajroaksoax, kirkland: I've made wiki page for the testdrive hackfest. wiki.ubuntu.com/QATeam/Testdrive/Hackfest If either of you could be online through part of it that would be great. I'm still looking for someone to run it from 1600-2000UTC21:53
sarnoldpitti: hello :) I think the retracer service may be sick; https://bugs.launchpad.net/bugs/1201254 was filed three or four days ago, but still has the 'need-i386-retrace' tag and coredump file attached22:06
ubottuError: ubuntu bug 1201254 not found22:06
=== _salem` is now known as _salem

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