/srv/irclogs.ubuntu.com/2010/11/16/#ubuntu-devel.txt

RoAkSoAxhi all... after the recent change to the linker (passing --as-needed by default) I have a package that is FTBFS with something like "./.libs/libpengine.so: undefined reference to `resource_location'." So I was wondering how can I find where are those symbols located (or in which library), so that I can add that to LDFLAGS?00:28
RoAkSoAxbefore the change, the message was "warning: symbol resource_location used by debian/libpengine3/usr/lib/libpengine.so.3.0.0 found in none of the libraries."  however it didn't FTBFS00:29
micahgRoAkSoAx: use apt-file to search for the library that provides that?00:31
james_wRoAkSoAx, that's rather a generic name for a symbol, so it might be supposed to come from the package itself. Might be worth grepping the package source first00:32
RoAkSoAxjames_w: i did that with this result: http://pastebin.ubuntu.com/532677/00:33
ebroderRoAkSoAx: It's in lib/pengine/utils.{h,c}00:34
james_wRoAkSoAx, ok, so depending on the buildsystem there is probably a missing dependency between parts of the project00:34
james_wRoAkSoAx, is it autotools?00:34
RoAkSoAxjames_w: yes it is00:35
RoAkSoAxebroder: right, but that's the thing, libpengine says those are missing symbols of itself?00:35
james_wRoAkSoAx, it probably doesn't link utils.o in to libpengine.so00:36
RoAkSoAxjames_w: so what could be the possible fix? patch the makefile somehow?00:37
RoAkSoAxjames_w: or telling it to use that utils.o by passing it through LDFLAGS?00:38
james_wRoAkSoAx, I'm just trying to remember how all this works00:38
RoAkSoAxjames_w: this is the makefile btw http://pastebin.ubuntu.com/532685/00:44
james_wRoAkSoAx, that doesn't seem to build libpengine00:47
james_wRoAkSoAx, can you grep for libpengine in all Makefile.am in the tree?00:47
achiangRoAkSoAx: what package are you actually building? libpengine?00:48
james_wachiang, pacemaker00:49
achiangis there a full build log available somewhere?00:50
RoAkSoAxjames_w: the only one that list libpengine i a makefile is this one: http://pastebin.ubuntu.com/532686/00:50
RoAkSoAxachiang: i'll get it for you :)00:51
james_wRoAkSoAx, line 59 has utils.c, which is what I would have suggested you add :-)00:52
RoAkSoAxachiang: http://launchpadlibrarian.net/59133765/buildlog_ubuntu-natty-amd64.pacemaker_1.0.9.1%2Bhg15626-2ubuntu1_FAILEDTOBUILD.txt.gz00:52
RoAkSoAxjames_w: indeed, and yet it still FTBFS00:52
james_wRoAkSoAx, ah, it's building the executable when it fails00:54
james_wRoAkSoAx, now I'm even more confused :-)00:57
james_wit seems to link pengine fine the line before, then fail when linking ptest00:58
RoAkSoAxjames_w: indeed it is confusing... I think I'll just opt for a ' -Wl,--no-as-needed' to disable the '--as-needed'01:00
ebroderRoAkSoAx: That seems almost certainly like obscuring the problem...01:01
RoAkSoAxebroder: indeed... but upstream doesn't even know why it may be failing and I can't seem to find a solution for the problem :(01:03
ebroderresource_location isn't declared static or something like that, is it?01:03
RoAkSoAxebroder:in  utils.h is extern void resource_location(resource_t *rsc, node_t *node, int score, const char *tag, pe_working_set_t *data_set);01:06
achiangthis looks like an optimizer problem to me01:06
ebroder...it's declared extern?01:06
RoAkSoAxebroder: and in utils.c is just a simple voide resource_location...01:06
achiangif object file foo.o requires symbols from object file (or library) bar.[s]o, then foo.o must come to the *right* of bar.[s]o in the linker invocation01:06
achiangotherwise, the optimizer strips out all unused symbols from foo.o01:07
achiangsorry, the optimizer strips out unused symbols from bar.[s]o01:08
RoAkSoAxachiang: could you provide an example cause I don't seem to follow :S01:08
achiangRoAkSoAx: let's say ptest.o needs a symbol from libpengine.so01:08
achiangthat means when you link it, you must say: bla bla bla -lpengine -o ptest.o01:09
achiangwhat happens is the linker looks at the symbols in ptest.o; it sees something called "resource_location", and it's undefined in ptest.o01:10
achiang"no problem" says the linker, i'll find it later somewhere up the line01:10
achiangif you do it the other way around, the linker looks at libpengine.so, and sees a symbol called "resource_location"01:11
achiangit says, "hm, no one is using this symbol yet, so i can just optimize it out"01:11
RoAkSoAxachiang: so this should be changed from: -o .libs/ptest ptest.o  ../lib/common/.libs/libcrmcommon.so ../lib/pengine/.libs/libpe_status.so ./.libs/libpengine.so -lncurses /usr/lib/libhbclient.so /usr/lib/libccmclient.so -lcoroipcc ../lib/cib/.libs/libcib.so ../lib/transition/.libs/libtransitioner.so /usr/lib/libgnutls.so /usr/lib/libplumb.so /usr/lib/libpils.so -lbz2 /usr/lib/libxslt.so /usr/lib/libxml2.so -lc -luuid -lpam -lrt -ldl /usr/lib/libgl01:11
achiangthen when you try and link ptest.o, you get the undefined reference01:11
achiangRoAkSoAx: that is my theory without actually looking at any code. it's a simple test to try for now01:12
achiangRoAkSoAx: in one sentence, the linker reads from right to left, not left to right. so you must arrange your objects that way01:12
ebroderachiang: AFAICT, pengine is using automake+libtool in the way that the docs recommend. If you're right, then all automake+libtool things should be breaking01:12
RoAkSoAxachiang: so how would I do that, fixing up the Makefile?01:14
achiangRoAkSoAx: let me try and find an example01:15
RoAkSoAxachiang: thanks :)01:15
achiangebroder: like i said, it's just a theory01:15
achiangRoAkSoAx: here's one that i fixed a while ago... https://bugs.launchpad.net/ubuntu/+source/alpine/+bug/66849901:17
achiangRoAkSoAx: hm, that is not very instructive, is it? :-/01:18
achiangfeh, my natty pbuilder seems busted. can't do a test build of pacemaker due to unmet dependencies01:20
RoAkSoAxachiang: more or less :/ I'd just need to find where to patch it :)01:21
achiangRoAkSoAx: as a quick test for my theory, i think you can try adding this:01:27
RoAkSoAxachiang: yes....?01:29
achiangptest_LDFLAGS = -l$(top_builddir)/lib/...01:29
achiangsorry, trying to figure out the relative path of libpengine.so01:29
RoAkSoAxachiang: cool I will. Thanks for the help :)01:30
achiangRoAkSoAx: sorry, that's not complete yet01:30
achiangstill trying to figure out the answer01:31
achiangah, ok. there it is01:31
achiangadd this to the proper makefile:01:31
achiangptest_LDFLAGS = libpengine.la01:31
achiangi *think* that should force the library *before* ptest.o01:31
achiangRoAkSoAx: if you try that, can you please show me the build output afterwards, whether it works or not?01:32
RoAkSoAxachiang: i will01:33
RoAkSoAxachiang: I added this, but shows same error: http://pastebin.ubuntu.com/532712/01:41
achiangRoAkSoAx: ok, i need to see the complete build log please01:41
RoAkSoAxhttp://pastebin.ubuntu.com/532713/01:41
RoAkSoAxachiang: oh ok, give me a sec01:41
achiangRoAkSoAx: nm, i see it didn't make it onto the linker line01:42
achiangRoAkSoAx: i don't know how to force libpengine.la before ptest.o to test my idea. perhaps whereever you were going to add "-Wl,--no-as-needed", you could instead add the reference to the library instead01:44
RoAkSoAxachiang: yest that's what I was thinking off01:44
RoAkSoAxachiang: something like  LDFLAGS += -Wl,--no-as-needed -libpengine.la -Wl,--as-needed ?01:46
achiangRoAkSoAx: well... i would not use -Wl,--no-as-needed because as mentioned earlier, that masks the real problem.01:47
achiangRoAkSoAx: try LDFLAGS += -llibpengine.la01:47
achiangRoAkSoAx: but i must admit, you might have to play around with that a little. sorry, i'm not giving very good advice right now, a little distracted and thinking about dinner (i'm GMT-7)01:48
RoAkSoAxachiang: haha that's fine :)... I'm in same situation (GMT-5)01:50
achiang:) speaking of which, time to go a-foraging01:50
RoAkSoAxachiang: i'll try that but im too tired and too hungry to keep on fighting with it. Thanks for your help :)01:52
RoAkSoAxebroder: james_w thank you to you too guys :)01:53
=== sanchaz is now known as sanchaz-away
ScottKdoko_: It looks like the Qt patch to add the missing IT instructions for Thumb2 support is ~working well enough to let it build.  The problem I thought was related to lack of implicit-it=thumb in the new gcc-4.5 is actually a different problem.  So Bug #675347 is blocking us now on getting qt4-x11 and the rest of the Qt/KDE stuff building on arm.03:22
ubottuLaunchpad bug 675347 in gcc-4.5 (Ubuntu Natty) "volatile int causes inline assembly build failure" [High,Confirmed] https://launchpad.net/bugs/67534703:22
ebroderScottK: In the interests of making backports bugs more machine-parseable, what would you think of adding tags to indicate the source release? i.e. from-natty, etc.03:45
ScottKebroder: I think without a script to file such bugs they will be too error prone to rely on the tags.03:46
ScottKIf we have proper tool support, then I think it's all good.03:46
ebroderScottK: Ok, fair enough. I guess I'll have my "backport-helper" script prompt for now03:47
ScottKOK.03:48
=== jelmer is now known as Guest86531
=== amitk is now known as amitk-afk
=== amitk-afk is now known as amitk
dholbachgood morning!08:04
pittiGood morning08:11
dholbachbarry, do you know what still needs to happen wrt bug 663343?08:20
ubottuLaunchpad bug 663343 in cheetah (Ubuntu) "Please merge cheetah 2.4.2.1-1 (main) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/66334308:20
dholbachyour merge proposal is marked as 'merged' - can we close the bug? what about Clint's merge proposal?08:20
wgrantmvo: Hi.08:30
mvohey wgrant08:33
wgrantmvo: I just saw your comment on bug #45129.08:34
ubottuLaunchpad bug 45129 in Soyuz "FFe: update-manager should have per-package changelog locations (was: uses changelogs.ubuntu.com for all packages)" [Low,Triaged] https://launchpad.net/bugs/4512908:34
=== smb` is now known as smb
wgrantmvo: In the IRC discussion you said you'd have to use the binary name and version in the changelog path. But the update-manager diff uses source name and version.08:35
wgrantThe latter is better for us, but just wanted to confirm that that's still the case.08:35
mvowgrant: let me double check, but iirc my concern was cases like "gcc-defaults" with src_ver != bin_ver. but because the Source: field contains the src-ver it should work just fine08:37
wgrantmvo: Yep, that's what I thought.08:37
mvowgrant: i.e. update-manager can construct the url without the need for a deb-src line08:38
mvowgrant: I just checked the code, the sourcepkg and sourcever should be enough08:38
mvowgrant: to make u-m work08:39
wgrantmvo: Perfect, thanks.08:39
* mvo goes and implements that in apt-get changelog too08:40
* wgrant goes and implements that in Soyuz.08:41
mvo!!!08:41
* mvo hugs wgrant08:41
wgrantdeathrow might be a bit of a challenge, but we'll see.08:41
mvothat is the orphan cleanup part of soyuz? or punishment if tests fail?08:42
wgrantIt's the bit that removes orphaned files from the pool.08:42
* mvo nods08:42
=== rraphink is now known as raphink
=== Guest86531 is now known as jelmer
=== MacSlow is now known as MacSlow|afk
=== jjohansen1 is now known as jj-afk
=== MacSlow|afk is now known as MacSlow
TLEpitti: Hallo, I'm presently working on the schedule for language packs updates for Maverick. I was wondering how long it takes to build them and distribute to the proposed update repositories10:32
pittiTLE: building and uploading the sources takes about 3 hours; getting them built about half a day10:33
pittia full base export takes a bit longer10:33
TLEpitti: more specifically, if the build starts on wednesdays at 1400 UTC at which time can I then plan on those packages being built, you copying them to proposed and finally them being distributed among the mirrors?10:33
pittiTLE: your first "the build" is for the LP export, or langpack-o-matic?10:34
TLElangpack-o-matic10:36
TLEthe exports seems to have a welldefined timeframe for them in this schedule: https://dev.launchpad.net/Translations/LanguagePackSchedule10:36
pittiTLE: it wildly depends on the load of the buildds, but I'd say 12 hours in good circumstances (by and large idle buildds), and 20 in peak times10:38
TLEok, then after they are built, how much time for you to upload to proposed and circulate between mirrors, roughly?10:39
TLEWhat'm really interested in is when we can tell users they can start testing them10:40
pittiTLE: those 12/20 hours include the total turnaround starting from langpack-o-matic cron job10:40
pittiuntil you can apt-get them on clients10:41
TLEahh ok, I thought that you would have to manually intervene to upload to proposed10:41
pittiTLE: I do, but that's part of the process10:42
pittiTLE: we never upload anything to -proposed automatically10:42
pittiwe do (or at least, want to, it's broken right now) upload to the daily PPA, and from there it's a manual process to copy to -proposed10:43
TLEI'm a little confused, so as it is right now, you start a process at the dates we agree on that builds the latest exported files from launchpad and puts them in proposed, and that takes <24 hours, correct?10:45
pittiright10:45
pittiTLE: more precisely, the cron jobs will build them automatically from Launchpad and upload into the test PPA10:46
pittiTLE: and from there I'll copy them to -proposed at the agreed dates10:46
TLEAll right, but you are in some way informed when the builds are done or something, so you don't need much time to do the uploads10:48
TLEI just don't want to set to tight deadlines for us10:49
TLEI mean to copy them from the ppa to -proposed10:50
TLEsorry if I'm a little dense today, I just want to get it right10:51
pittiTLE: the point where I need to do manual action is to issue the copy from PPA to -proposed; the rest happens automatically10:56
pittiI'm not notified when all the builds are finished, though10:56
pittione can find out by looking at https://launchpad.net/builders10:56
TLEpitti: ok, cool thanks10:59
pittitkamppeter: I am currently debugging why jockey takes so long to detect hardware11:00
pittitkamppeter: I shaved off 5 seconds, now I'm down to about 15.5 seconds on my system11:00
pittitkamppeter: of which 15 seconds is cupshelpers.getDevices(), all the rest is trivial11:00
pittitkamppeter: i. e. this takes 15 seconds here: python -c 'import cups, cupshelpers; print cupshelpers.getDevices(cups.Connection())'11:00
pittitkamppeter: do you know what takes it so long?11:01
=== MacSlow is now known as MacSlow|lunch
pittitkamppeter: should jockey perhaps not do that in the first place? s-c-p always calls it with a particular printer model already, right?11:01
=== diwic is now known as diwic_afk
didrocksdoko_: hey, around? I'm fighting with a gcc 4.5 build issue11:08
doko_didrocks: still firefox?11:09
didrocksdoko_: ? I'm not maintaining firefox :) no, it's about gnome-settings-daemon: http://launchpadlibrarian.net/59165700/buildlog_ubuntu-natty-i386.gnome-settings-daemon_2.32.1-0ubuntu1_FAILEDTOBUILD.txt.gz11:10
didrocksdoko_: as you can see we are building an additional file called debian/gnome-update-wallpaper-cache.c (http://paste.ubuntu.com/532905/) which simple options11:10
didrocksdoko_: we were already building the package for --as-needed for quite a long time. I tried even --no-as-needed without any success11:11
didrocksdoko_: I confirm it's still building fine with gcc 4.411:11
=== asac_ is now known as asac
doko_didrocks: would be nice to see how pkg-config expands ...11:12
didrocksdoko_: sure: http://paste.ubuntu.com/532927/ nothing to worry about it seems11:12
cjwatsonpitti: pkgstripfiles seems to still be removing changelog.Debian.gz in the odd case, e.g. https://launchpad.net/ubuntu/+source/biococoa/2.2.1-1/+build/204898511:14
cjwatsonsomething to do with symlinked changelogs between multi-binary sources maybe?11:15
cjwatsonpitti: I bet the symlink is broken so test -e fails.  perhaps:11:16
cjwatson-if [ ! -e "$dch" ]; then11:16
cjwatson+if [ ! -e "$dch" ] && [ ! -h "$dch" ]; then11:16
pitticjwatson: right, it shouldn't touch symlinks at all11:16
pitticjwatson: thanks for pointing out; I'll add a test case and fix it11:17
cjwatsonta, just noticed 'cos new-binary-debian-universe complained at me11:17
YokoZarpitti: ~branding-ubuntu -- do you think we can put pngcrush in there too?11:22
YokoZaralso kudos on the improvement ;)11:22
pittiYokoZar: do you think pngcrush does anything good on top of optipng and advancecomp? (which are already done in pkgbinarymangler)11:22
YokoZaractually maybe branding-ubuntu doesn't have any png, only svg...11:22
YokoZarpitti: actually, good question, I'm not sure if pngcrush -9 is better than optipng11:23
YokoZarmaybe binary mangler could just run both and compare11:23
YokoZarand shouldn't optipng be in main if it's done in pkgbinarymangler?11:25
pittiYokoZar: optipng is in main11:25
YokoZaroh, just not in maverick11:26
YokoZarerr nevermind11:26
joaopintomvo, hi, attempting to upgrade a package using a .deb,  using software center should work ?11:29
pittimvo: ^ I tried software-center yesterday to install a .deb from firefox, worked great; is that meant to make gdebi obsolete, or was it just an accident?11:44
pittiah, seems we already dropped it, nevermind11:44
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
bdrunghallyn: you dropped the capslock patch in qemu-kvm 0.12.4+noroms-0ubuntu1, which let bug #427612 reappear in maverick. i am using the NEO2 layout, where the caps lock key is a normal key.11:54
ubottuLaunchpad bug 427612 in qemu-kvm (Ubuntu) "does not pass pressed caps lock to client" [Low,Fix released] https://launchpad.net/bugs/42761211:54
=== MacSlow|lunch is now known as MacSlow
jmlcjwatson: just to be crystal clear, this week is not a week before an alpha is it?12:20
jmlcjwatson: nm12:20
mvojoaopinto: is that not working?12:21
cjwatsonjml: no12:22
=== diwic_afk is now known as diwic
joaopintomvo, nope, at least not on maverick, it just shows the installed button disabled12:43
joaopintothe install12:43
=== amitk is now known as amitk-afk
hallynbdrung: yes, that's what i said yesterday.  Someone needs to explain in the other bug: if we're going to carry a patch somewhere, why shouldn't it be in SDL to fix the root cause.13:20
stgraberogra_ac: Any change you can try to build https://launchpad.net/ubuntu/+source/lightspark on something faster than my Beagleboards/EfikaMX ?13:21
bdrunghallyn: is that really a bug in sdl?13:21
ogra_acstgraber, will tyr to13:22
stgraberogra_ac: cool, thanks13:22
DktrKranzstgraber: please consider it won't build other than i386 and amd64 (ppc port is still WIP)13:23
stgraberDktrKranz: ah, ok. Any plan for an ARM port ?13:26
hallynbdrung: yes, that's the explanation by upstream on why they won't take it13:29
DktrKranzstgraber: most of the code is portable (C++), but it also has a per-architecture portion of code written in assembly, which requires soneone to write it13:29
DktrKranzsomeone, even13:30
hallynbdrung: and we really don't want to have patches which were rejected by upstream.  we'd *like* to follow their guidance to pursue the proper fix.  Unfortunately I haven't had time yet to look into the SDL code for more background.13:30
hallynbdrung: if you have time, that'd be *awesome*.  In fact, if in the end you can explain why SDL must be so, and why there's no other way, then we can (grudgingly) take the patch back into qemu.13:31
bdrunghallyn: i have not enough time to dig into it, but i am offer testing. my testcase: set keyboard layout to NEO2 (in host and vm) and press caps+t (result should be "-")13:32
bdrunghallyn: in NEO2 the caps lock key is used as modifier (similar to shift and ctrl)13:33
hallynbdrung: now, as a workaround, using vnc should work correctly for you, right?13:47
bdrunghallyn: how do i use vnc with kvm?13:47
Keybukcjwatson: I was looking for a way for Launchpad to show me the merge preview in the review interface13:49
davmor2Keybuk: mad fool13:50
cjwatsonKeybuk: it would do if not for the Launchpad bug I linked to in my comment13:54
Keybukheh13:54
=== xfaf is now known as zul
hallynbdrung: if you're using kvm from cmline, you do 'kvm -vnc :1' (or :2, etc) then from the host 'vncviewer :1' to connect to it14:04
hallynbdrung: it's particularly useeful as it makes it easy to cross ssh tunnels14:04
jturek31014:09
bdrunghallyn: thanks. i tested vinagre and in vinagre the caps lock behave correct. what does this tell us?14:10
hallynbdrung: only that you have a workaround14:11
hallynbdrung: well, kirkland supports putting the patch back in, so maybe we'll end up doing that14:12
sorenhallyn: Don't use xvncviewer :)14:12
sorenhallyn: gvncviewer uses gtk-vnc which is What You Want To Use[tm]. I believe it supports "-via", too, just like xvncviewer.14:13
hallynsoren: think i use tightvncviewer14:13
hallynand actually i don't use -vio14:14
sorenhallyn: Same deal.14:14
hallynvia14:14
hallynhm, why?14:14
sorenhallyn: So you do the ssh forwarding manually? dude, you're missing out :)14:14
sorenhallyn: Lots of things are simply not supported properly in clients other than gtk-vnc.14:14
sorenraw key codes, for instance, which is a deal breaker for many use cases.14:15
hallynhm.  allright, i'll try it sometime.  but as for forwarding, doing it manually means i can just do it the same way on my n900, on my mom's windows machine, etc.14:15
hallynsoren: in the past, i had a lot of trouble with mix-matching vnc's, and back then i just settled on xtight as something that works everywhere14:16
hallyni wonder whether that's been mostly addressed by now14:16
hallynsoren: so package gtkvncviewer ?14:16
kirklandlool: did you push your changes for qemu-kvm (0.13.0+noroms-0ubuntu3) to lp:ubuntu/qemu-kvm ?14:16
sorenhallyn: There's an interesting intersection of people working on gtk-vnc and on various virt technology.14:16
kirklandlool: i just had an upload conflict14:16
sorenhallyn: Like danpb and aliguori.14:16
sorenhallyn: It's packaged.14:17
hallynyeah, but there are at least 2 that sound like it :)14:17
hallyngtkvncviewer and gvncviewer14:17
sorenhallyn: Both should be fine.14:17
sorenhallyn: They both use gtk-vnc.14:18
sorenhallyn: gvncviewer is just more familiar if you're used to xvncviewer.14:18
=== bregma_ is now known as bregma
hallynall right, installed, i'll give it a spin, thanks :)14:20
sorensure :)(14:20
soren:)14:21
bregmaI'm looking for some guidance on filing an SRU in maverick, is there anyone around to give me some advice?14:21
kirklandhallyn: okay, mouse fixes uploaded14:21
kirklandhallyn: i had to resolve a conflict with lool's last qemu-kvm upload14:21
hallynkirkland: oh?  i had just fetched the tree late last night14:22
kirklandhallyn: yup, you did the right thing14:22
hallyn<big sigh> i'm getting just about burned out on bugs for the week14:22
zulhggdh: ping14:23
kirklandhallyn: it's tuesday :-)14:23
zulhallyn: bugs are to be taken orally not rectally ;)14:23
hallyndoh!14:24
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
NoobFukaire1anyone know of a PPA or something with an ubuntu kernel and the new wonder UI patch applied?14:37
bdrungNoobFukaire1: you may ask in #ubuntu-kernel14:38
NoobFukaire1thx14:38
=== jam1 is now known as jam
pittikees, cjwatson, mdz: TB in 5 mins, right? or in an hour?14:54
cjwatsonmy belief is 5mins14:55
=== chrisccoulson_ is now known as chrisccoulson
ogra_acstgraber, omg ... 700M build deps ?14:59
highvoltageogra_ac: do you perhaps have a minute to shed some insight on a classmate issue in #edubuntu?15:01
stgraberogra_ac: I'm guessing it build-deps on gstreamer and a few similar stuff :) Though as mentioned by DktrKranz earlier, it'll fail anyway as the code needs to be "ported" to ARM (as in, add a bit of ARM assembly in the code).15:02
stgraberogra_ac: they support x86 32/64bit and seem to be working on a powerpc port, maybe we can find someone willing to do the work (or at least look at it) to make it compatible with ARM15:03
ogra_acstgraber, assembly ???15:03
stgraber14:29 < DktrKranz> stgraber: most of the code is portable (C++), but it also has a per-architecture portion of code written in assembly, which requires soneone to write it15:04
stgraberapparently, yes ...15:04
ogra_acbah15:04
ogra_acthere should really be no assembly15:05
stgraberI agree :) I'm guessing it's meant for performance optimization or whatever.15:06
ogra_acthats nonsense in times of gcc 4.5 ;)15:06
hggdhzul: consider yourself ponged15:07
zulhggdh: sorry i figured it out :)15:09
hggdhzul: heh15:09
kirklandhallyn: qemu-kvm FTBFS: http://launchpadlibrarian.net/59199370/buildlog_ubuntu-natty-i386.qemu-kvm_0.13.0%2Bnoroms-0ubuntu4_FAILEDTOBUILD.txt.gz15:11
ogra_acstgraber, so there isnt really any point in me doing a testbuild15:12
stgraberogra_ac: I'd guess it's simply going to fail on the ASM part. I haven't looked at the code but based on DktrKranz's comment earlier, I wouldn't think it's going to fallback to "less efficient" c++ code15:12
hallynkirkland: i think that has nothing to do with us...15:14
kirklandhallyn: interesting, alright ...15:15
hallyn'gcc: Internal error: Killed (program cc1)15:15
kirklandkees: toolchain issues in natty at the moment?15:15
kirklanddoko_: ?15:15
hallynkirkland: and too bad, bc i'm about to propose another little merge for the same tree15:15
=== diwic is now known as diwic_afk
keeskirkland: not sure; I just got back from holiday15:18
hallynkirkland: wonder whether the amd64 will pass15:20
kirklandhallyn: doubtful15:20
kirklandhallyn: did you try a pbuild local?15:20
hallynpessemist15:20
kirklandhallyn: heh15:20
hallynyeah, but against maverick15:20
kirklandhallyn: ah15:20
hallyn(so i could run it)15:21
kirklandhallyn: yeah15:21
ogra_acpfft, thats so unimportant, important is if armel will pass15:21
hallyna build is under way in a natty schroot15:21
ogra_ac:)15:21
kirklandogra: ;-)15:21
hallynogra_ac: so true15:21
hallynkirkland: if you're not on a call right now, interesting conversation on qemucall (about distro bugs)15:22
kirklandhallyn: hmm, no i didn't join today15:22
ScottKpitti: Would you please review the paragraph I added to https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy (at the end of the policy section) and make sure I captured it correctly.15:27
pittiScottK: that sounds fine to me, thank you15:31
ScottKpitti: Thanks for checking.15:31
hallynkirkland: ha!  https://launchpad.net/~serge-hallyn/+archive/virt?field.series_filter=natty15:32
=== sanchaz-away is now known as sanchaz
hallynkirkland: last night it compiled fine for natty15:32
pittiScottK: added to https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions15:32
ScottKCool.15:33
ScottKThat's only been on my TODO for a year and a half ....15:33
=== zyga is now known as zyga-afk
=== dholbach_ is now known as dholbach
ogra_acstgraber,15:39
ogra_acCMake Error at CMakeLists.txt:96 (MESSAGE):15:39
ogra_ac  Platform armv7l not supported15:39
kirklandhallyn: weird15:57
dholbachpitti, can we reset the burn down line of canonical-community?15:58
dholbachpitti, I tried to find a way, but there seems to be no natty.cfg15:58
=== tkamppeter_ is now known as tkamppeter
pittidholbach: there is, on lillypilly15:58
pittidholbach: sudo -u platform -i, then you can edit natty.cfg there15:59
pittidholbach: (sorry, in meeting)15:59
pittidholbach: lillypilly is people.c.c.15:59
dholbachaha, I was looking in ~pitti ;-)15:59
=== jj-afk is now known as jjohansen
tkamppeterpitti, hi16:00
tkamppeterpitti, sorry for not having followed IRC.16:01
tkamppeterpitti, cupshelpers.getDevices(16:01
pittihello tkamppeter, how are you? (no problem, it's not that urgent)16:01
dholbachthanks pitti16:01
pittitkamppeter: I disabled cupshelpers from normal jockey operation for now, since printer drivers are almost always installed via s-c-p16:01
tkamppeterpitti, cupshelpers.getDevices() takes 15 seconds like "lpinfo -v" does as CUPS waits 15 sec for answers of network and Bluetooth printers.16:02
pittitkamppeter: ah, that explains it16:02
tkamppeterpitti, Jockey does not actually need to look for printers. Local printers are handled via UDEV when plugged or via CUPS startup during boot.16:03
pittitkamppeter: that's what I thought16:03
pittitkamppeter: ok, thanks for confirming16:03
tkamppeterRemote printers printers should not be set up non-interactively. One usually sets them up on one or two boxes and then one activates CUPS browsing. Therefore these printers should only get set up on explicit request by the user (via s-c-p).16:05
tkamppeterSo for printers Jockey should only get called for the actual driver download for an already detected printer, not for finding the printers.16:06
pittiright16:06
doko_kirkland: preprocessed source?16:08
didrockspitti: cjwatson: FYI (just saw the meeting and the /opt discussion), I've implemented a tentative of getting prefix support for python-support and such. It's on my ppa now: https://launchpad.net/~didrocks/+archive/ppa/16:20
pittididrocks: oh, nice16:20
didrocksalso Quickly trunk now support installing in that prefix16:20
didrocks(and upgrade existing projects)16:21
=== You're now known as ubuntulog
smoserin a debian 3.0 quilt format, stored in bzr, should i store the bzr with the patches applied ?16:31
smoseri think the answer is yes16:32
cjwatsondidrocks: we should be moving to dh_python2/dh_python3, though, right?16:33
cjwatsonsmoser: yes (IMO)16:33
smosercjwatson, and store the .pc directory also ?16:33
cjwatsonI don't, normally, although the importer does16:34
cjwatsonit's an open question16:34
didrockscjwatson: I have a work item to prepare dh_python* to support prefix. But not sure with unity and such I'll have the time to support it this cycle. So, I've just keep with what exists16:34
smoseror were there fixes to that bug you had opened to have rules force-apply them.16:34
cjwatsonI find it easier not to16:34
cjwatsonand cope with the fact that other people working on the branch will have to do a little bit of fiddling after checkout/update16:34
cjwatsonbut that's just my opinion16:35
smoseri prefer no .pc, so i'll go with that. and add a rule to force fix .pc.16:35
smoserthanks.16:35
ogra_acstgraber, hmm, i get it to compile but on my ac100 it triggers compiler errors (which are more likely kernel errors with the tegra kernel), i will try it on a panda soon16:35
=== You're now known as ubuntulog_
=== You're now known as ubuntulog
=== yofel_ is now known as yofel
=== zyga-afk is now known as zyga
=== Claudinux_ is now known as Claudinux
RoAkSoAxkirkland: howdy!! For PowerNap I was thinking if it would be a good idea to turn off some services when on powersave mode... such as stopping logging or things that can still cause disk I/O or something... would that e something easily doable?17:47
kirklandRoAkSoAx: hmm, i'm not too sure about that18:05
kirklandRoAkSoAx: maybe in a future iteration18:05
kirklandRoAkSoAx: lets focus on hardware hacks for now18:05
RoAkSoAxkirkland: yeah the problem is that I've been trying to spin down the harddrive but it gets woken up. Maybe I'm not doing it right... Other thing I thought about is extend the time on which the data is actually written into disk18:08
RoAkSoAxfrom memory to disk18:08
RoAkSoAxkirkland: by reducing the dirty page writeback frequency18:11
seb128ev: could you review https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/661289 when you have time?18:53
=== dendrobates is now known as dendro-afk
=== Claudinux_ is now known as Claudinux
=== dendro-afk is now known as dendrobates
=== blueyed_ is now known as blueyed
=== hanska is now known as dapal
rsajdokhow to get access to send email to https://lists.ubuntu.com/archives/ubuntu-devel/ ?20:04
micahgrsajdok: anyone can send, but it's moderated for non-developers AFAIK20:05
=== dendrobates is now known as dendro-afk
rsajdokmicahg: I sent email yesterday. It is not yet approved20:10
=== dendro-afk is now known as dendrobates
* lamont has a question... https://bugs.launchpad.net/ubuntu/+source/apt/+bug/673446 is, in fact, not an apt bug, but was an archive issue. does that mean it should get closed as 'invalid', or would 'fix released' be more accurate?20:43
seb128lamont, invalid20:45
lamontseb128: thanks20:45
seb128the apt task was invalid at least, you can add a comment saying that20:45
highvoltagee/win 1920:45
lamontseb128: commented that it was actually an archive issue on old-releases, which I have now fixed.20:46
seb128lamont, ok, thanks20:47
lamontso amusingly,  while it's not a bug in ubuntu, it is my bug.20:47
lamontfor sad values of 'amusingly'20:47
smosercjwatson, is bug 581760 testable without a windows installation ?20:49
ubottuLaunchpad bug 581760 in grub2 (Ubuntu Lucid) "[Wubi] when updating it advices to install grub on all partitions" [High,Fix committed] https://launchpad.net/bugs/58176020:50
=== ximion is now known as ximion1
=== ximion1 is now known as ximion
geserkees: do you know what happened to the 'Dynamic "per package upload permissions" for Debian Developer' topic on the TB agenda? From a look at the wiki edits it looks like it simply got dropped without getting discussed. Sylvestre is asking about any information of the outcome.21:00
keesgeser: hmm... IIRC, it was supposed to go to the mailing list for further discussion?21:09
jdstrandwendar: fyi, I add PostReleaseApps/SecurityChecklist today21:09
wendarjdstrand: excellent, thanks! I'll read through it now21:10
geserkees: the TB mailing list?21:11
keesgeser: yeah21:12
geserkees: I don't see anything in the archives for Oct and Nov21:13
highvoltageddd/win 1321:13
highvoltage(bah)21:13
keesgeser: yeah, best to bring it up on the list then.21:15
wendarjdstrand: also sending the link on to the ARB list, for all members to review21:15
jdstrandwendar: cool, thanks21:15
geserkees: looks like it was discussed during the meeting on 2010-11-02. Will reply to Sylvestre with the link to the meeting log.21:16
keesokay21:17
ajmitchjdstrand: some of the social items in there will need more discussion, like the developer contract & $21:17
jdstrandajmitch: oh absolutely21:17
jdstrandajmitch: I imagine that document to be refined after further discussion, but based on our team's current understanding, etc, etc that is what we came up with21:18
ajmitchjdstrand: thanks for putting it together21:18
jdstrandajmitch: sure np. I wrote it up, but everyone on the ubuntu-security contributed21:19
jdstrandthe ubuntu-security *team* that is21:20
wendarjdstrand: the comments on socially encouraging good security behavior by preventing anonymous contributions are an important addition too, thanks!21:45
wendarjdstrand: at the moment we require a PPA, which is a certain level of "verification" of a real human. and in the future it looks like we'll be integrating ARB with our commercial signup process, which is another level of verification21:46
wendarjdstrand: we may not charge a dollar for submitting an application, but we may very well take financial information from some developers, if they want to accept donations for their free software21:47
jdstrandwendar: regarding 'anonymous contributions'-- thank mdeslaur (but we all agree :)21:47
jdstrandwendar: it doesn't have to be a dollar-- it could be $.01. the idea is that it makes it harder to be anonymous (unless you are being seriously criminal)21:48
jdstrandwendar: but all the PPA business was that we don't want their software changing the upgrade system, etc21:49
jdstrandwell, you probably ment that the PPA is one deterrent21:49
jdstrandwendar: anyhoo, yes it is, but it is easy to miss intentionally malicious software without a very thorough and time-consuming review. with social deterrents, you tend to get for free21:50
jdstrand/get/keep malicous software out/21:51
jdstrandmind you, *tend* :)21:51
jdstranda really bad guy will find a way21:51
wendarjdstrand: aye, there's always a way, but we can prevent/discourage as much as possible21:51
jdstrandabsolutely! (hence the checklist ;)21:52
cjwatsonrsajdok: then it's in the queue - I'll look at it next time I'm at my laptop21:52
cjwatsonsmoser: no21:52
wendarjdstrand: and, on PPAs, yes, meant the fact that they have to set up account with valid email and sign the code of conduct, etc, etc, is a beginning of social pressure for good behavior21:53
jdstrandwendar: we discussed that and recognize it is the beginning, but that alone is a pretty low barrier in our opinion21:54
wendarwendar: agreed, it's possible to complete with entirely fake identity21:55
jdstrandwendar: anyhoo, it seems we are on the same page for that. certainly worht more discussion for more social pressure21:55
wendarjdstrand: very much so. will loop back with you once ARB has had a chance to discuss. thanks for putting it together!21:56
jdstrandsure! :)21:56
=== lucas__ is now known as lucas
=== Auv5 is now known as Auv5_
lifelesskees: ping22:21
lifelesspitti: ping22:22
keeslifeless: sup?22:22
lifelessplease try your private files thing22:22
lifelesson launchpad production22:22
keesoh, is it live?22:23
lifelessjust now22:23
lifelessevaluating whether we broke anything22:23
keesone moment...22:23
kees*drum roll*22:24
keesno 503!22:25
kees\o/22:25
lifelesskees: faster ?22:25
keeslifeless: looks great for the one smaller package we've got in a secppa22:25
lifeless\o/22:26
keeslifeless: dunno about actual transfer through-put, but yeah, when 5 out of every 6 downloads don't have to retry 3 times with a 10 second pause between each attempt, it's much faster ;)22:26
lifelesskees: awesome. Feel free to blog about lp awesomeness :)22:26
lifelesskees: though we may have to roll it back - dunno yet :)22:27
keesheh, d'oh22:27
keeslifeless: well, FWIW, this is the first time in maybe a year (or more?) where there have been no 503 retries. well done! :)22:29
lifelessrolling it back22:29
lifelesswould break apport right now22:29
lifelessactually22:29
lifelessI think we can avoid this.22:29
keesoh? bummer.22:30
lifelesskees: keeping it live22:34
lifelessplease let me know how it goes22:34
ScottKwendar: Having a PPA is not related to not being anonymous.22:35
ScottKThe fact that there is a valid email address doesn't help that at all.22:36
=== Auv5_ is now known as Auv5
kirklandkees: fyi, your dmesg change will break kvm-ok, at least until you get the changes checked in to check kvm in bios outside of dmesg ;-)22:46
SpamapSis anyone else overjoyed that we actually have v3 of mdadm in natty?23:07
keeskirkland: yeah, I've been making a list. I intend to replace kvm-ok and the nx test with proper MSR calls anyway.23:18
ebroderkees: Does that mean that I'll be able to detect if the BIOS disabled HW virt without loading the kvm modules? Because that would be awesome23:19
keesebroder: yes, I think so. As I understand it, the kvm modules are just checking a specific MSR.23:19
keesebroder: it'll look something like this: http://bazaar.launchpad.net/~cpu-checker-dev/cpu-checker/trunk/annotate/head%3A/check-nx23:20
keesexcept I'll be adjusting it to not do all that crazy stuff at the start and just expects to run as root with msr-tools installed.23:20
ebroderkees: Oh, I can do this now? Even better23:20
keesebroder: yup, if you can find the MSR you need to read, it should be trivial. It just hasn't bubbled to the top of my TODO yet.23:21
keesebroder: but if you do get it written, please share. I want to get it in there. :)23:21
kees(I also need to write an MIR for msr-tools)23:21
ebroderkees: Will do. Shouldn't be too hard - last time I looked at this I gave up when I found that the instruction the kernel used was privileged only. Hooking the bits together should be easy, though23:22
keesebroder: well, that part isn't much different, only root can read the msr device.23:23
ebroderkees: That's fine. I can arrange to be root for my use case. I didn't want to arrange to be the kernel23:24
keeshaha yeah23:24
keeswell, while I'm waiting, now I want to go look23:24
ebroderrdmsrl(MSR_VM_CR, vm_cr); is one of the manufacturers23:24
ebroderThat's AMD23:24
ebroderis_disabled in arch/x86/kvm/svm.c23:25
ebroderAnd vmx_disabled_by_bios in arch/x86/kvm/vmx.c23:25
RoAkSoAxkirkland: btw.. just saw you gonna work on cobbler. You might wanna take a look at: http://www.threedrunkensysadsonthe.net/2010/07/installing-cobbler-on-ubuntu23:26
keesMSR_IA32_FEATURE_CONTROL23:30
ebroderkees: I think rdmsr --bitfield 4:4 0xc0010114 will work for AMD23:30
ebroderStill working on understanding the logic for Intel, but it's various bits of 0x3a23:30
RoAkSoAxkirkland: seems unaccessible for now, but that guy branched cobbler and made changes that supposedly enabled it to work in Ubuntu23:33
kirklandRoAkSoAx: where at?23:34
RoAkSoAxkirkland: http://www.threedrunkensysadsonthe.net/2010/07/installing-cobbler-on-ubuntu (Seems unaccessible for me, for now)23:34
RoAkSoAxkirkland: I read it like couple weeks ago or so23:36
keesebroder: when svm is disabled in the BIOS, does it still show up in /proc/cpuinfo?23:38
ebroderkees: Not sure23:39
keeskirkland: ?23:39
ebroderkees: vmx definitely does23:39
kirklandkees: huh?23:39
kirklandkees: oh, yes, it does23:39
keesah, yeah, looking at kvm-ok, it does. okay23:39
kirklandkees: see the current logic in kvm-ok23:40
kirklandkees: that logic is correct23:40
ebroderkees: I take it you're writing the code at this point so I shouldn't?23:40
keesebroder: I think I'm close. I just need hw to test with23:48
keesebroder: I'll continue in a bit23:48
ebroderkees: I have Intel hw I can reboot repeatedly if that helps, although I don't think I can test any of the trusted boot stuff23:49

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