/srv/irclogs.ubuntu.com/2013/02/25/#ubuntu-devel.txt

ogra_haha, xnox uploaded the cj<tab> fix :)00:29
infinityogra_: Hahaha.  I should upload that same default change for irssi.  I set it locally, but never though to do it globally.02:03
ogra_:)02:04
ukiHello everyone. I'd like to perform two tasks using apt-get/aptitude. 1. Generate a list of all packages present in the Ubuntu repositories. 2. Given a package name, get a list of the packages it depends on(preferably without having to download the package source),02:58
ukiCould someone help me on how I could go about doing that? Thanks in advance02:59
infinityuki: See /var/lib/apt/lists and check out dctrl-tools03:01
ukiinfinity: will do, thanks!03:01
infinityuki: (And those sorts of questions probably belong in #ubuntu, not here)03:01
ukiah okay, sure :)03:01
ukiinfinity: Just to confirm, isnt /var/lib/apt/lists a list of packages that have been installed?03:02
infinityuki: No, that's all the Packages/Sources files from the archive, listing everything you *can* install.03:04
ukiinfinity: I see. Thank you!03:04
* infinity curses cmake.03:08
psusiohh, I feel as though I may have just had a brilliant stroke of insight...03:08
infinitypsusi: Does it involve why cmake's testsuite fails in raring?03:08
infinity*hopeful look*03:08
psusiok... so the importer storing quilt patches already applied in the bzr branch causes many problems03:08
psusibut not doing that makes bzr blame a problem03:09
psusiso how about have the importer replay the quilt patches one at a time into separate commits in a new branch based on the unpatched branch, then merge that branch back into the master03:09
infinityI didn't think bzr blame was the motivator at all, but just making a checkout the same as an unpacked source package.03:09
psusiwait, no... maybe I'm drunk03:10
psusiI just hate the packages already being applied03:10
psusipatches rather03:10
infinityI'm not a big fan of the udd workflow at all, so I'm not arguing for or against here. :P03:10
psusiI find it fantastic when the quilt patches aren't applied03:11
infinityjbicha: Well, I've transitioned everything for libarchive13 except cmake.  The cmake testsuite is sad in raring, and I'm not sure I want to spend any more of my Sunday trying to figure out why.03:15
jbichainfinity: thanks again04:08
infinityjbicha: Also, not to be picky, but actually fixing rdup correctly was easier than ignoring the deprecation warnings. :P04:10
infinityjbicha: (Uploading the proper fix now and forwarding to Debian)04:10
infinityjbicha: Was that the only package where you ignored the deprecation warnings?04:12
lifelessinfinity: rdup?04:15
infinitylifeless: Yes...?04:16
lifelessinfinity: was that a typo for rdep ?04:16
lifelessinfinity: or a package name ?04:16
infinitylifeless: It was a package name.04:16
infinityhttps://launchpad.net/ubuntu/+source/rdup/1.1.11-1ubuntu204:17
lifelessheh, its very specific04:17
jbichainfinity: I think so, I found the proper fix for pixz04:59
infinityxnox: I know how much you *love* cmake.  I'll give you a shiny nickel if you can figure out why it FTBFS in current raring, but the same source builds fine against quantal.05:08
=== cinerama_ is now known as cinerama
pittiGood morning05:40
Sarvattxnox: so many lols, thanks for fixing xchat that way as someone hit by sa<tab> too much :)05:54
dholbachgood morning07:12
wooohey guys I have a doubt about vnode. I think the inode for a specific file system is the vnode for virtual file system. Am I right?07:23
lifelesswooo: you might get a better answer in #ubuntu-kernel07:23
lifelesswooo: but - http://www.linuxquestions.org/questions/linux-kernel-70/difference-between-inode-and-vnode-657954/07:24
lifelessis what google tells me :>07:24
=== doko_ is now known as doko
=== Logan_ is now known as y
xnoxSarvatt: heh =) well there is no way to auto-migrate people, so existing users will need to change settings. I will be blogging about it ;-)09:13
=== negronjl` is now known as negronjl
=== henrix_ is now known as henrix
seb128hum09:52
seb128xnox, Laney, slangasek: is bug #1129157 the whoopsie/nm/ck one? did that got fixed/workedaround?09:53
ubottubug 1129157 in lightdm (Ubuntu) "lightdm pausing a long time at boot" [Undecided,Confirmed] https://launchpad.net/bugs/112915709:53
* xnox thought the whoopsie/nm/ck was bug 112433009:54
ubottubug 1124330 in whoopsie (Ubuntu) "[raring] Latest whoopsie 0.2.13 slows down boot process by 29 seconds!" [High,Confirmed] https://launchpad.net/bugs/112433009:54
seb128xnox, I'm asking if the one I pointed at is likely a duplicate or if you think it's a different issue ;-)09:55
xnoxah.09:55
Laneyhttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/112379809:55
ubottuUbuntu bug 1123798 in whoopsie (Ubuntu) "ubiquity-dm crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.ConsoleKit timed out" [High,Confirmed]09:55
LaneyI suppose it could be a dupe09:55
seb128I wonder how many different bugs we have for the issue :p09:55
LaneyI wonder if we should revert that libnm-glib stuff for now09:57
Laneyit was supposed to fix some leak but the problems it introduces seem to be worse09:58
seb128yeah09:58
seb128I'm still unsure how it does manage to screw ck though09:58
seb128it's weird that a buggy dbus service manages to break ck09:58
Laneyev: ↑09:59
evLaney: I'm worried that we're just kicking the can10:00
seb128ev, well, we can't keep raring broken for users, we either need somebody to focus on it and fix it soon or to revert until we can come with a fix10:01
seb128it seems like nobody has a good understanding of the issue and that it might take a while so maybe best to revert10:01
evfair point10:02
evadding it to my todo list for today10:02
jamespagedoko, re the zookeeper FTBFS with gcc-4.8 and glibc-2.17 - I think that is glibc as I've been hitting those same test failures in raring10:03
seb128ev, thanks10:04
dokojamespage, ok, could you change the user/usertag ?10:08
jamespagedoko, sure10:10
xnoxdoko: ... and you are expecting me to fix all the debian-med gcc4.8 failures?! =))))10:13
* xnox got spammed by doko10:13
Laneywhat changed to make my VMs reeeeeeeeallly sloooooooooooooooooooooowww?10:15
diwicif you'd like one FTBFS less, feel free to sponsor bug 107467310:16
ubottubug 1074673 in ubuntu-nexus7 "JACK server fails to start" [Medium,Triaged] https://launchpad.net/bugs/107467310:16
Laneyqemu-system-x86 is using all of one core10:16
tumbleweedno kvm?10:17
Laneythere should be10:17
seb128diwic, are those fixes including in jackd upstream? Debian has a new version, maybe we should sync that?10:17
diwicseb128, the FTBFS fix is is upstream. Also in Debian, but I tried the git version, but it has other FTBFSes instead10:19
seb128diwic, ok10:19
diwicseb128, the fix for arm is still under debate upstream, but I figure it would be better to have something with a theoretical issue, than not working at all10:20
seb128diwic, I was just asking in case, I saw that our version is older than the Debian one and was wondering if it would make sense to sync the new one10:20
seb128diwic, right10:20
diwicseb128, sure, that's a fair question, I tried that too, first, and it failed with FTBFS even earlier :-)10:20
Laneyyeah "kvm support: disabled"10:26
Laneypermissions on /dev/kvm seem ok10:26
Laneyhmm or maybe not10:27
Laneyah yes, reboot → correct now10:29
seb128Laney, :-(10:32
seb128starting sounding like old time win, stuff don't work, let's reboot10:32
Laneyit's a bug where after you upgrade qemu the permissions of /dev/kvm are set to root:root10:33
Laneyif you get the udev event to fire (e.g. by rebooting) then they are set correctly10:33
Laneyhallyn is trying to fix it10:33
seb128ok10:33
=== Sweetsha1k is now known as Sweetshark
evmpt: the quote on my desk comes from this book: http://www.amazon.com/Controlling-Software-Projects-Management-Measurement/dp/013171711110:53
evwas just reading a slide deck that referenced it and remembered that I never gave you a link to the book10:54
evI've never read it myself - I came by it via an article he wrote for the IEEE10:54
shakaranHi, there are some plan for fix nvidia drivers before to raring release? I am worry for don't get a working driver at time of 13.04 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/108392511:35
ubottuUbuntu bug 1083925 in nvidia-graphics-drivers-updates (Ubuntu) "nvidia kernel module failed to build on kernel >= 3.7 [error: #error remap_page_range() conftest failed!]" [Undecided,Confirmed]11:35
bdrungxnox: thanks for fixing bug #18922212:26
ubottubug 189222 in xchat (Ubuntu) "Xchat changes focus to new channels after automatic joins on connect and clears highlight" [Low,Fix released] https://launchpad.net/bugs/18922212:26
xnoxbdrung: thank you =)12:26
* xnox feels like a rock-star. This is second Kudos about a single upload on irc ;-)12:27
Laneynext stop LWN12:27
* bdrung looks at the bug again.12:27
xnoxLaney: I'm yet to be featured on LWN =)12:27
bdrungxnox: ah, you just enabled my workaround :)12:27
* xnox is quite happy with 3 appearances in "3Touch" magazine (the only UK volleyball magazine)12:28
Laneyget you12:28
Laney(hope you forwarded these changes to debian)12:28
xnoxbdrung: yeah, so no manual migration. But I was sick of that bug to the point of almost switching to *gasp* quassel (no libmessaging) or smuxi (mono/no channel tree view)12:29
xnoxLaney: well....12:29
* xnox has a backlog of stuff to forward.12:29
* Laney glares at (mono)12:29
xnoxMy library is in /lib should the dev .so be in /lib or can it stay in /usr/lib ?12:31
xnoxWhat's the best practice?12:31
xnox(or it doesn't really matter as long as pkg-config works correctly)12:31
=== _salem is now known as salem_
loolcjwatson: -proposed migration currently considers installability with Depends/Conflicts etc., but do we have a way to detect that a package misses conflicts/replaces?  I've got an upgrade error with latest gtk+2.0 and am thinking that we ought to have some kind of check to avoid this to users of the rolling release13:01
lool(this seems to involve :amd64 and :i386 packages on the same system, so might be trickier than just within one arch)13:01
seb128lool, if you can debug that one I would welcome that, it seems the file that ough to be the same between archs is different13:03
cjwatsonlool: No, there's no code to do that at the moment13:06
cjwatson(And it's pretty hard)13:06
cjwatsonMultiarch file differences are indeed not a matter of missing Replaces13:06
loolcjwatson: Yeah, it wasn't actually a conflict/replace issue but rather a difference between files wihch should be identical13:11
loolcjwatson: I wonder whether we ought to run a separate service generating hints to not allow promotion of broken updates tough13:11
lool*though13:11
seb128lool, before that upload in seems like the amd64 binary had a symlink for /usr/share/doc/gtk2-engines-pixbuf/README.gz13:12
seb128Laney, ^13:12
seb128-dh_compress -s -X.sgml -X.devhelp -XNEWS -Xchangelog.Debian -XREADME13:14
seb128+dh_compress -s -X.sgml -X.devhelp13:14
seb128in the update's diff13:14
seb128not sure why that would lead to that though13:14
lool-dh_compress -s -X.sgml -X.devhelp -XNEWS -Xchangelog.Debian -XREADME13:14
lool+dh_compress -s -X.sgml -X.devhelp13:14
loolYes13:14
loolseb128: clearly just a change to the arch dep packages rather the arch-indep ones for one13:14
seb128right13:14
loolseb128: Funny we've found it at the same time :)13:15
seb128lool, do you want to fix it or should I?13:15
loolseb128: I'm happy if you do13:15
seb128lool, ok13:16
seb128lool, hum, weird, the -i call is identic13:16
seb128dh_compress -i -X.sgml -X.devhelp13:16
loolseb128: got changed in r1578213:17
lool* Apply multiarch patch by Javier Serrano Polo, replacing all13:17
lool  occurrences of usr/lib by $(LIBDIR). Closes: #468100.13:17
lool* rules: don't compress .sgml and .devhelp files.13:17
loolseb128: Sorry, wrong branch13:17
seb128lool, we had13:18
seb128-    - Use -XNEWS -Xchangelog.Debian -XREADME to dh_compress calls to13:18
seb128-      workaround a gzip issue leading to different md5sum between builds13:18
loolseb128: It seems like a merge error13:18
seb128but I though that gzip issue got fixed in between13:19
loolseb128: Was it actually so that it was a gzip issue?13:19
seb128yes13:20
loolseb128: perhaps it was hiding this other issue with pkgbinarymangler interfering13:20
seb128the .gz were getting different md5 on i386 and amd64 for sure13:20
seb128but maybe it was hiding a second issue as well13:20
xnoxinteresting.13:20
loolseb128: I guess because of the difference of checksums we had -X for a while, but it wouldn't have worked with pkgbinarymangler also interfering and making files to symlinks only in some builds13:21
Laneyit's weird that the symlinke from e.g. libgtk2.0-0 works13:21
seb128yeah, and symlinks from previous built worked13:21
seb128builds13:22
Laneyah13:23
Laneythey're done manually13:23
Laneysee debian/*.links.in13:24
loolthat's even weirder, why wouldn't it have symlinks in one case?13:25
=== AbsintheSyringe2 is now known as AbsintheSyringe
loolah I guess they get generated the same, but then pkgbinarymangler outsmarts them13:26
seb128but why wasn't it doing that before then?13:27
loolif that's the issue, we could set NO_DOC_PKG_MANGLE to avoid this13:28
seb128or just drop the .links.in and let pkgbinarymangler does its job?13:28
seb128do*13:28
loolseb128: that might be more delta with Debian though13:29
seb128yeah13:30
seb128lool, I'm still not sure to understand what's happening exactly there though13:30
seb128Laney, are you working on it? (no need to be several debugging the issue, I'm happy to let you investigate if you are already doing that)13:31
seb128I'm over the "read the diff to spot a potential merge error"13:31
seb128that needs some debugging13:31
Laneysure I'll look at it13:32
loolseb128: clearly I see why pkgbinarymangler wouldn't work the same on amd6413:32
seb128lool, oh, why?13:32
seb128Laney, thanks13:33
loolit walks all deps, and skips the ones where test -d ../$dep/usr/share/doc fails13:33
xnoxmissing arch_all package build?! but how would that matter.13:33
loolso it wont go through the same candidates13:33
loolhmm actually it discards deps on arch: all entirely anyway13:34
seb128the easiest way seems to add back those files to the dh_compress13:34
seb128though I'm still unsure if that's this change who leads to the issue, and why we had a compressed file before if we were excluding them from dh_compress13:35
loolseb128: So one difference between libgtk2.0-0 and gtk-pixbuf is that both have a .links.in file, but dh_installdocs is only called on gtk-pixbuf13:40
lool*gdk13:40
lool(search for DH_INSTALLDOCS_FILES in rules)13:41
Laneybah, I got a symlink in my test build13:43
seb128Laney, did you build the arch all?13:43
Laneyno13:43
seb128:-(13:44
Laneyperhaps pkgbinarymangler didnt run though13:44
Laneyah, whoops I did build with -A (stupid muscle memory)13:48
Laneythat's better13:54
Riddelldoko: I've a probably fix for qtwebkit on powerpc13:55
Riddelldoko: qtwebkit-source_2.3-0ubuntu5.debdiff13:55
Riddelldoko: think I can just upload or does it need testing somehow?13:55
dokoRiddell, just upload13:55
Riddelldoko: can you eye it over for syntax sanity? http://paste.kde.org/680882/13:56
dokoRiddell, ok. just curious why build-webkit is called twice ...13:59
Riddelldoko: I don't even remember, I just know it broke on the first run :(14:01
dokoRiddell, could something similiar be done with qt5?14:02
Riddelldoko: similar to what?14:02
Riddelldoko: it's waiting on qtlocation5-dev14:03
dokoRiddell, yes, building qtlocation5-dev without the js dependency14:04
Riddellmm qtjsbackend broken14:04
dokoScottK, are you involved with boost in Debian?14:12
ScottKdoko: No.14:12
* xnox hides14:12
Riddelldoko: hmm syntax failed, it added the ENABLE_JIT=0 on i386 https://launchpadlibrarian.net/132300747/buildlog_ubuntu-raring-i386.qtwebkit-source_2.3-0ubuntu5_FAILEDTOBUILD.txt.gz14:13
dokoRiddell, you asked me to check syntax, not semantices ;-p14:14
Riddellifneq (,$(filter $(DEB_HOST_ARCH),powerpc))  that's true on i386?14:15
Riddellmake is scary foo14:15
=== wedgwood_away is now known as wedgwood
seb128diwic, was there any issue with syncing jackd2 from debian? I saw that bdrung did that rather than using your patch, but this morning you seemed to imply your patch was still needed?14:28
diwicseb128, argh14:29
seb128diwic, it built, not sure if it will work14:29
bdrungi checked the diff and saw that the proposed patches were included14:30
diwicbdrung, the ARM patch too?14:30
diwicbdrung, the one with PACKED something14:30
bdrungdiwic: yes, both14:32
diwicbdrung, ok, found it.14:35
diwicbdrung, seb128 thanks for looking it up. Let's try this version then and see if it works.14:35
seb128diwic, thanks14:35
=== kentb-afk is now known as kentb
=== salem_ is now known as _salem
=== _salem is now known as salem_
steven____hey all15:37
steven____is this the correct channel for questions about developing applications?15:37
xnoxsteven____: #ubuntu-app-devel is a better place =)15:39
steven____ok, then ill go there15:39
steven____thx :)15:39
xnoxsteven____: #ubuntu-packaging for creating a deb from a ready application15:39
xnoxsteven____: np.15:39
steven____nah, will take some time before its ready to be packed...15:41
=== kentb is now known as kentb-afk
psusismoser: I backported the online resize patches to our parted and pushed the branch if you are interested in testing it.  Not sure if it's a little late in the cycle to merge it or not.16:07
smoserpsusi, https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1096999 ?16:08
ubottuUbuntu bug 1096999 in util-linux (Ubuntu) "add new partx update and resize upstream features" [Low,Fix released]16:08
smoserthat shows fix-released. ie, i thought i uploaded that for you.16:09
smoseroh.  *parted*. gotcha.16:09
smoserpsusi, i dont think its too late in the cycle.16:10
smoserbut i'd ask someone else who has been active in parted package.16:10
mterry@pilot in16:26
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mterry
xnoxsmoser: psusi: sounds like we should find resources to port d-i then continuing to backport parted features.16:29
xnoxs/then/than/16:29
* dholbach hugs mterry16:30
psusixnox: that would be nice16:35
=== kentb-afk is now known as kentb
=== Elbrus_try_again is now known as Elbrus
=== deryck is now known as deryck[lunch]
=== fginther is now known as fginther|lunch
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
psusidoes anyone know if landscape-client release 13.02 is planned to make it into raring?18:09
xnoxpsusi: it should, why do you ask? anything interesting you are after?18:10
SpamapSUnpacking replacement gtk2-engines-pixbuf:amd64 ...18:11
SpamapSdpkg: error processing /var/cache/apt/archives/gtk2-engines-pixbuf_2.24.16-1ubuntu1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/gtk2-engines-pixbuf/README.gz', which is different from other instances of package gtk2-engines-pixbuf:amd6418:11
SpamapSknown bug?18:11
Laneyyes18:13
SpamapSOk, will just move on. :)18:15
psusixnox: yes, I patched it to report the *correct* memory usage.. it was merged upstream, just wondering if I can delete the merge request to ubuntu since upstream will have it next time it releases and is merged18:17
xnoxpsusi: if it landed in the upstream branch, there is no need for any other merge proposals / branches.18:18
jbichapitti: do you know of a way to enable apport for just specific PPAs? I was just using this basic code http://paste.ubuntu.com/5565457/18:32
=== deryck[lunch] is now known as deryck
=== wedgwood is now known as wedgwood_away
=== wedgwood_away is now known as wedgwood
=== henrix is now known as henrix_
dobeyxorg has SIGABRTed on me 3 times in the last 18 hours or so, so far. :( same crash as a bug report i filed a few weeks ago. who can i bribe to fix it?21:14
tumbleweedmterry: you can leave Logan_ to upload his own packages now - he just joined MOTU21:14
mterrytumbleweed, oh nice  :)21:14
mterryLogan_, congrats; I'll leave you to it21:15
Logan_Thanks! :)21:15
infinitydobey: You can bribe me.21:18
infinitydobey: I won't fix it, but I could use some spending money.21:18
dobeyhere's a nickel kid. :)21:18
infinitydobey: I wonder if that's the same nickel I was offering to get someone to fix cmake's testsuite on raring.  That thing gets around.21:19
mterry@pilot out21:19
=== udevbot changed the topic of #ubuntu-devel to: Ubuntu 12.10 released | Archive: Open | Dev' of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of hardy -> quantal | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
dobeycould be21:20
infinitykenvandine: Say, you're TIL on cmake.  Any urge to sort out WTF it doesn't pass its testsuite anymore?21:20
kenvandineinfinity, ugh... not really21:21
kenvandinei haven't done much with cmake21:21
infinitykenvandine: Probably more than I have.21:21
kenvandinejust re-applied a patch that someone had accidentally dropped21:21
kenvandinei can take a look21:21
kenvandinebut no promises :)21:21
infinityYeah.  I was doing the same "I'll look, but no promises" thing this week, but clearly someone needs to hunt it down.21:22
infinityI haven't dug far enough to determine if it's a cmake bug, a testsuite bug, or if something fundamentally broke in the toolchain or a dependency that broke it.21:22
infinityBut a simple rebuild fails now.21:22
infinity(And it needs a rebuild for the libarchive transition)21:23
* kenvandine grabs the source21:23
infinitykenvandine: For the record, it's not libarchive that breaks it, cause building against only the release pocket also breaks, no need for proposed to reproduce.21:24
infinity(Not that I'd expect libarchive to be the culprit, as the test that fails is some xmlrpc submission thing)21:24
infinityThere has been a new version of cURL, which seems a likely candidate.21:25
infinitymdeslaur: So maybe this is your problem. :P21:25
* infinity has a thought...21:29
xnoxinfinity: where do you see cmake not passing it's testsuite ?!21:29
infinityI wonder if it's double-linking two different libcurls or something.21:29
infinityxnox: On a rebuild.21:29
xnoxinfinity: ah.21:29
* infinity spins up another test build here to save the binaries.21:30
* xnox looks at his +1 maintainance availability and notices that has None =))))21:30
=== fginther|lunch is now known as fginther
infinitypitti: Around?21:41
mterryzul, I'm looking at the rtslib MIR.  Why the fb27 version suffix?21:56
barrytumbleweed: ping21:59
kenvandineinfinity, indeed i libcurl looks suspicious21:59
tumbleweedbarry: yeah?22:00
kenvandinethere is a crash in some xmlrpc test that says libcurl in the output22:00
kenvandine Submission problem: libcurl failed to execute the HTTP POST transaction, explaining:  <url> malformed (-504)22:00
barrytumbleweed: hi.  i just merged a fix to trunk and uploaded to pypi for bug 1132125.  i want to get this into ubuntu, but i am happy to update the debian package to wadllib 1.3.2 first.  you're the maintainer, is this cool with you?22:01
ubottubug 1132125 in python-wadllib (Ubuntu Raring) "python-wadllib ftbfs in raring" [High,Fix released] https://launchpad.net/bugs/113212522:01
tumbleweedbarry: please go ahead22:01
barrytumbleweed: if you want to review the svn changes first, that's also fine22:01
tumbleweedhappy to review & sponsor it22:02
barrytumbleweed: awesome, thanks.  i'll ping you after i test the rebuild and commit svn (should be soon-ish)22:02
kenvandineinfinity, although i can't make heads or tails of how to isolate that test right now...22:04
kenvandinei gotta head out22:04
kenvandineinfinity, make test succeeds in the /Build/Tests/CTestTestFailedSubmits/xmlrpc dir22:05
kenvandinewhich looks like where it blew up22:06
mdeslaurinfinity: hum, what now?22:06
mdeslaurinfinity: what'd I break?22:06
infinitymdeslaur: Shot in the dark, but it seems that the new cURL broke cmake's testsuite somehow.22:14
infinitymdeslaur: None of us being terribly familiar with cmake or its tests, it's a bit of a learning curve to hunt. :P22:14
mdeslaurinfinity: the cmake that's currently in raring, or a new one from debian?22:14
infinitykenvandine: Yeah, make test gives the same output as the build log, minus the next bit...22:14
infinitymdeslaur: The current one in raring.  Rebuilding it breaks.22:15
* mdeslaur tries now22:15
infinitymdeslaur: And it built fine less than a month ago, so that limits the options for what broke it.22:15
=== salem_ is now known as _salem
=== seb128_ is now known as seb128
jtaylorbarry: mind looking over the patch in https://bugreports.qt-project.org/browse/PYSIDE-145 if you happen to know details about the mechanism and change22:44
jtaylorbarry: a generated file looks like this: http://paste.ubuntu.com/5566184/   *_nonstatic is added22:45
barryjtaylor: sure.  i'm sitting on my thumbs anyway until svn.debian.org's fail2ban lockout expires ;)22:45
jtaylorbarry: related to bug 107077222:45
ubottubug 1070772 in shiboken (Ubuntu) "modelview_test.py segfaults python" [High,Confirmed] https://launchpad.net/bugs/107077222:45
jtaylorbarry: the context is shiboken adds some kind of wrapper which works for static and nonstatic overloads22:47
jtaylorbarry:  e.g. obj.exists() calls the nonstatic one, and class.exists('filename') the static one22:47
jtaylorapparently the nonstatic one is found over the getattro, so I added the new PyDef and used it there22:48
jtaylorPyMethodDe22:48
barryjtaylor: i see nothing in py33's Misc/NEWS file about the change (doesn't mean it didn't happen of course).  what exactly is the behavior change?22:53
jtaylorbarry: previously it used the same METH_STATIC function for both and it passed NULL for self in the first case nevertheless22:53
jtaylorbarry: now both calls get NULL22:53
jtaylorbarry: not sure why but its not surprising me, defining a function static is certainly not part up pythons api22:54
jtaylorso they can break it without documenting22:54
jtaylordefining static when its not22:54
barryjtaylor: interesting!22:56
barryjtaylor: i don't even see any mention of METH_STATIC in upstream `hg -v -b 3.3 log` output22:59
jtaylorhm22:59
jtaylorit might have been broken in older python323:00
jtaylorI think older versions did not run the testsuite23:00
barryjtaylor: but definitely a py2/py3 change?23:01
jtaylorhm no it worked in debian with 3.223:01
barryhmm, maybe the change didn't happen in Objects/methodobject.c23:02
* xnox was sure to be able to reproduce the shiboken fail with other pythons.23:05
* xnox quickly scans my local build logs23:05
jtaylorxnox: the segfaults happens with all23:05
jtaylorxnox: the static fail only with python323:05
xnoxah, ok.23:06
barryjtaylor: http://paste.ubuntu.com/5566184/23:06
barryjtaylor: i'm wondering if lines 355-356 should be out side of the if(self) test?23:06
jtaylorbarry: you mean if self is null it should return the static one?23:07
barryjtaylor: just guessing, but maybe the PyObject_GGA() will dtrt anyway23:08
barryjtaylor: nm23:08
barryjtaylor: i'm reading static/nonstatic backwards23:08
barry_exists is the class version _exists_nonstatic is the instance version23:09
jtaylorbarry:  my irc server seems to be down :/23:13
jtaylorbarry did you say something since line 355-... ?23:13
barry<barry> jtaylor: nm23:14
barry<barry> jtaylor: i'm reading static/nonstatic backwards23:14
barry<barry> _exists is the class version _exists_nonstatic is the instance version23:14
barry 23:14
barryjtaylor: so i think it looks sane23:14
barryjtaylor: the diff in qt-project.org is a bit hard to read due to lack of context and my unfamiliarity with the code, but the generated file doesn't look bad23:15
barrytumbleweed: r2359523:17
jtayloryey im back23:17
jtaylorthe ttests all succeed so the diff is probably ok, the segfault is more problematic23:18
barryjtaylor: it stops segfaulting after that patch though right?23:18
jtaylorone could add an intentional memleak or ignore the test, possibly having a broken py3 package23:18
jtaylordon't know whats better23:19
jtaylorbarry: no that patch fixes to other failures23:19
barryoh ;)23:19
barryi hate memleaks, but sometimes those things are really horribly painful to track down.  is it in a high traffic section?  (like, leak 1k every time you type the letter 'e'? ;)23:20
jtaylorgood question, no idea23:20
jtaylorI wanted to try it, but I fail since ages to install raring23:21
jtaylorthe test is named modelview so its probably a core component23:21
* xnox wants to hear the 1k leak on 'e' story, as it sounds so hilarious that it may have been actually true.23:21
jtaylorthe code is horrible, its full of races even without the crash line23:22
barryxnox: mostly fictional, but i do have another fun one that is kind of similar.  for another time perhaps :)23:22
barryjtaylor: that makes me sad23:22
jtaylorxnox: there is a bug on OS X if you type 8 characters almost every app will crash :) I think its fixed no though23:23
barryjtaylor: yeah, i think they released a fix for that.  it was like a file://// path typed somewhere23:23
=== jtaylor_ is now known as jtaylor
jtaylor< offline, lets hope upstream replies to one of the bugs soon :/23:25
jtaylorbarry, thx for the check23:26
xnoxbug 248619 was fun, especially it's consequences of not being able to print on tuesdays, see bug 255161 with "it works today" "it stopped working" "it works yet again!"23:27
ubottubug 248619 in file (Ubuntu Karmic) "file incorrectly labeled as Erlang JAM file (OOo does not print on Tuesdays)" [High,Fix released] https://launchpad.net/bugs/24861923:27
ubottubug 248619 in file (Ubuntu Karmic) "duplicate for #255161 file incorrectly labeled as Erlang JAM file (OOo does not print on Tuesdays)" [High,Fix released] https://launchpad.net/bugs/24861923:27
xnoxjtaylor: well upstream does mention that all patches should go via geritt code review instance, which has a few old pyside patches lingering.23:35
xnoxI wonder if we can find to poke some people about them.23:36
=== kentb is now known as kentb-out

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