[00:05] <cjwatson> doko: Did libgcj-bc's dependencies intentionally get flipped from libgcj13 back to libgcj12?
[00:06] <cjwatson> doko: I can't see any sign of that in the diff, which is kind of odd
[00:06] <cjwatson> doko: But you can see the effects on http://people.canonical.com/~ubuntu-archive/testing/raring-proposed_probs.html
[01:26] <doko_> cjwatson, my bad. merge error. now fixed
[05:55] <simplew> anyone with packaging knowledge?
[06:42] <tumbleweed> simplew: no need to ask to ask, just ask a question. Also you probably want to ask it in #ubuntu-packaging, rather than here, if it's unrelated to development of Ubuntu
[06:43] <tumbleweed> oh, you already did, there
[09:36] <cjwatson> doko: great, thanks
[14:09] <jtaylor> infinity: was https://launchpad.net/ubuntu/+source/cython/0.16-1ubuntu1 forwarded somewhere?
[15:02] <sebasmagri> Hi!
[15:02] <sebasmagri> Any jockey/ubuntu-drivers-common developer in here?
[15:58] <ScottK> sebasmagri: Probably not on a weekend.
[15:59] <sebasmagri> ScottK: I see. Thanks anyway. I will be around.
[17:04] <infinity> jtaylor: No, I probably should push that one to Debian but, I think, at the time I was considering actually finding and fixing the real bug, rather than sticking with the workaround.
[17:05] <jtaylor> infinity: do you have a testcase?
[17:05] <infinity> jtaylor: Oh, also, it looks like 1.17 no longer has the problem (looking at experimental build logs)
[17:06] <infinity> jtaylor: So, I'll just sync current experimental and wash my hands of it.
[17:06] <jtaylor> infinity: k, the sync fixes 812511 too
[17:10] <infinity> jtaylor: Cheers, closed.  Annoying that MoM doesn't notice that we're tracking experimental and pop those on my radar, or I'd have updated a while ago.
[17:14] <jtaylor> so the issue was only seen in a buildlog?
[17:14] <infinity> jtaylor: Yes.  As in it failed to build on all arched with unsigned chars.
[17:15] <infinity> s/arched/arches/
[17:15] <jtaylor> why doesn't it fail in debian testing?
[17:15] <jtaylor> was it only 0.16?
[17:15] <infinity> jtaylor: It was 1.16 and the first 1.17 beta, 1.15 was fine.
[17:15] <infinity> jtaylor: See, eg: https://buildd.debian.org/status/logs.php?pkg=cython&arch=powerpc
[17:16] <jtaylor> k thx
[17:16] <infinity> (Replace "powerpc" with "armel" or "sparc" to see the pattern)
[17:23] <demosfere> Can someone help me? i'm having problems when building this recipe https://code.launchpad.net/~kedos-project/+recipe/bottomlauncher-daily , it gives me error No package 'dbusmenu-glib-0.4' found No package 'dbusmenu-gtk3-0.4' found , this is my buildlog : https://launchpadlibrarian.net/123265587/buildlog_ubuntu-raring-amd64.bottomlauncher_0.2.0-0-1~5~raring1_FAILEDTOBUILD.txt.gz
[17:26] <jtaylor> demosfere: you need to depend on libdbusmenu-gtk3-dev
[17:26] <demosfere> jtaylor: i've already did that
[17:27] <jtaylor> demosfere: you have libdbusmenu-gtk3-dev (>= 0.6.2) | libcairo2-dev
[17:28] <jtaylor> drop the or dependency
[17:32] <demosfere> jtaylor: what exactly should i do?
[17:33] <demosfere> jtaylor: can you pastebin control file after you fix it?
[17:33] <infinity> demosfere: He told you how to fix it...
[17:33] <infinity> demosfere: s/  | libcairo2-dev//
[17:34] <demosfere> infinity: the problem is that this package is used in the app
[17:36] <infinity> demosfere: Uhm.  What?
[17:36] <infinity> demosfere: You build-depend on libcairo2-dev, AND you build-depend on libdbusmenu-gtk3-dev|libcairo2-dev.
[17:36] <demosfere> infinity: the error is No package 'dbusmenu-glib-0.4' found No package 'dbusmenu-gtk3-0.4
[17:37] <infinity> demosfere: libdbusmenu-gtk3-dev gets (correctly) ignored because you're already installing libcairo2-dev, which you claimed was an adequate substitute.
[17:37] <jtaylor> demosfere: the error tells you the .pc file is missing
[17:37] <infinity> demosfere: Thus, libdbusmenu-gtk3-dev isn't being installed.
[17:37] <jtaylor> that .pc file is provided by libdbusmenu-gtk3-dev
[17:37] <infinity> demosfere: So, drop the " | libcairo2-dev"
[17:37] <jtaylor> see: apt-file list libdbusmenu-gtk3-dev | grep -E ".pc$"
[17:37] <demosfere> infinity: i'll try and see if it work
[17:40] <demosfere> infinity: jtaylor please stay here until i let you know if it works now :)
[17:40] <infinity> demosfere: Uhm.
[17:40] <infinity> demosfere: That was wrong. :P
[17:40] <infinity> -               libcairo2-dev,
[17:40] <infinity> -               libdbusmenu-gtk3-dev (>= 0.6.2) | libcairo2-dev,
[17:40] <infinity> +               libcairo2-dev | libcairo2-dev,
[17:40] <infinity> ^-- That won't fix anything...
[17:41] <infinity> That should read, simply:
[17:41] <infinity> libcairo2-dev,
[17:41] <infinity> libdbusmenu-gtk3-dev  (>= 0.6.2),
[17:41] <infinity> ---
[17:41] <infinity> Minus the extra space there.  My keyboard's repeating, apparently.
[17:42] <demosfere> infinity: i'm confused :P , what should i do now
[17:43] <infinity> demosfere: You want to build-depend on libcairo2-dev and libdbusmenu-gtk3-dev, right?  This isn't any different from any of your other build-deps.
[17:43] <infinity> demosfere: Having "foo | bar" means "either foo or bar is okay, we don't need both".
[17:44] <infinity> demosfere: And having "foo | foo", when you also want bar (which is what you did to "fix" it) is extra strange.
[17:44] <demosfere> infinity: now i'm totally confused :P
[17:45] <infinity> demosfere: The fix you committed at http://bazaar.launchpad.net/~kedos-project/bottomlauncher-pkg/trunk/revision/7
[17:45] <infinity> demosfere: You completely removed the build-dep on libdbusmenu-gtk3-dev
[17:45] <demosfere> infinity:and this will make it work?
[17:46] <infinity> Past tense.  You removED the build-dep.  You shouldn't have done that.
[17:46] <infinity> You need libdbusmenu-gtk3-dev
[17:47] <demosfere> infinity: so i should re-add libdbusmenu-gtk3-dev and then ?
[17:47] <infinity> demosfere: The line that says "libcairo2-dev | libcairo2-dev," should just say "libcairo2-dev," and then you also want a line that says "libdbusmenu-gtk3-dev (>= 0.6.2),"
[17:50] <demosfere> infinity: i think this is what you told me to do : http://pastiebin.com/?page=p&id=50a7ce358ac86
[17:50] <demosfere> infinity: is it right ^
[17:50] <demosfere> ?
[17:51] <jtaylor> looks good
[17:51] <infinity> I'd complain about the whitespace, but yeah.  That should do.
[17:52] <demosfere> infinity: i'm pushing and building ... i'll let you know if it wrks
[17:52] <infinity> Assuming nothing freaks out about the space between the ) and the comma, but probably not.
[17:53] <demosfere> infinity: ^ you mean it's wrong and causes failure in building ?
[17:53] <infinity> demosfere: For correctness, that space really shouldn't be there.  No idea if any of the tools parsing control will care, though.
[17:53] <infinity> demosfere: As in, "libdbusmenu-gtk3-dev (>= 0.6.2) ," should be "libdbusmenu-gtk3-dev (>= 0.6.2),"
[17:53] <demosfere> infinity: i'll remove after i make sure building works :)
[17:58] <demosfere> infinity: offtopic , do you want to join my team?
[17:58] <demosfere> infinity: failed to build https://launchpadlibrarian.net/123283341/buildlog_ubuntu-quantal-i386.bottomlauncher_0.2.0-0-1~5~quantal1_FAILEDTOBUILD.txt.gz
[18:01] <demosfere> infinity: any idea?
[18:01] <demosfere> jtaylor: ^^
[18:07] <jtaylor> demosfere: I don't see libdbusmenu-gtk3-dev being installed, what did you build there?
[18:08] <demosfere> Source: bottomlauncher Section: utils Priority: optional Maintainer: Drake Miller <dakemiller@gmail.com> Build-Depends: debhelper (>= 8.1.2ubuntu2),                gnome-common,                valac-0.18 (>= 0.18.0),                libbamf3-dev (>= 0.2.92),                libdbusmenu-gtk3-dev (>= 0.6.2) , 	       libcairo2-dev,                libgdk-pixbuf2.0-dev, 	       libdbusmenu-glib-dev, 	       libdbusmenu-glib4, 	    
[18:09] <demosfere> jtaylor: this is the control file of the current revision : http://pastiebin.com/?page=p&id=50a7d2a687731
[18:10] <infinity> The control file doesn't come close to matching the build-deps sbuild ends up looking for.  I'm inclined to blame whitespace here.
[18:11] <infinity> Perhaps wrap-and-sort(1) would unbreak your issues.  Or you could more carefully rewrite that line.
[18:12] <infinity> Though, not sure if it's smart enough to fix tabs/spaces and other things.
[18:13] <demosfere> infinity: spaces doesn't making an error
[18:13] <demosfere> infinity: i think the problem is by configure file in the source code
[18:14] <infinity> No...
[18:14] <infinity> The problem is that your build-deps aren't all being installed.
[18:14] <infinity> Compare this to your control file:
[18:14] <infinity> Build-Depends: debhelper (>= 8.1.2ubuntu2), gnome-common, valac-0.18 (>= 0.18.0), libbamf3-dev (>= 0.2.92), libcairo2-dev, libgdk-pixbuf2.0-dev, libgee-dev (>= 0.5.2), libglib2.0-dev (>= 2.28.0), libgtk-3-dev (>= 3.0.0), libwnck-3-dev, libx11-dev, libceleste-dev
[18:14] <infinity> Note that it doesn't list everything listed in your control.
[18:15] <jtaylor> infinity: cython failed :(
[18:15] <demosfere> why it's not installing them?
[18:16] <infinity> demosfere: Like I said, my guess is bad whitespace.  You might want to test locally.
[18:16] <infinity> jtaylor: Gah.
[18:16] <demosfere> i'll try
[18:17] <infinity> jtaylor: Oh, probably a missing build-dep on python3-all-dev
[18:17] <infinity> jtaylor: Err, no, it's there.
[18:17] <infinity> Hrm.
[18:17] <jtaylor> its strange
[18:17]  * infinity goes hunting for pyconfig.h
[18:19] <jtaylor> possibly multiarch issue
[18:19] <infinity> Is our python more multiarchy than Debian's?
[18:19] <infinity> doko: ^
[18:20] <jtaylor> I'm just guessing, let me check debian
[18:20] <infinity> doko: https://launchpadlibrarian.net/123283466/buildlog_ubuntu-raring-amd64.cython_0.17.1-1_FAILEDTOBUILD.txt.gz
[18:20] <infinity> doko: Ideas?
[18:20] <demosfere> infinity: dammit ! still doesn't work
[18:20] <infinity> jtaylor: It's not FTBFS in Debian, hence the curiosity.
[18:20] <doko> infinity, yes, use python-config --includes
[18:21] <doko> python3-config even
[18:21] <infinity> demosfere: Replace all those tabs with spaces and see how that goes.
[18:21] <infinity> doko: This is Ubuntu-specific at this point?
[18:21] <infinity> doko: (Same build is fine in experimental)
[18:22] <demosfere> infinity: i've removed empty spaces already and didn't work
[18:22] <doko> no, same versions
[18:22] <jtaylor> the pyconfig.h is in the same place in debian
[18:22] <jtaylor> weird
[18:22] <infinity> Oh, but this built in Debian in September.
[18:23] <infinity> Multiarch python probably happened after that?
[18:23] <jtaylor> I'm currently test building, I'll try to cook up a patch when I reproduced the failure
[18:23] <infinity> Heh.  I'm there too. :P
[18:24] <jtaylor> nice I got a different error ..
[18:24] <ricotz> demosfere, better to actually rebuild the source package with the recipe than just rebuilding the old source in ppa again
[18:24] <demosfere> Why dpkg is so complicated
[18:24] <demosfere> ?
[18:26] <demosfere> ricotz: i don't understand
[18:26] <infinity> jtaylor: Hrm, looks like the right -I/foo is in CFLAGS but not CPPFLAGS.
[18:27] <demosfere> ricotz: you built plank , i think you know in packaging it more than anyone else ..
[18:27] <ricotz> demosfere, your pastes indicate that you are not generating a new source package containing the new packaging
[18:29] <demosfere> ricotz: i just branched your deb-packaging and modified it to bottomlauncher .. and it won't work
[18:29] <demosfere> ricotz: but i think the problem is by configure
[18:29] <jtaylor> the configure is probably fine
[18:30] <ricotz> https://code.launchpad.net/~kedos-project/+recipe/bottomlauncher-daily
[18:30] <infinity> demosfere: The problem, as stated several times, is that your build-deps aren't being installed, which is due to a malformed debian/control.
[18:30] <ricotz> demosfere, hi the rebuild button in there
[18:31] <ricotz> infinity, the control file is fine, dpkg can handle those mix ups
[18:31] <infinity> ricotz: It *was* malformed before we started helping out.
[18:31] <infinity> ricotz: I'm not convinced that it isn't still, but we'll see after a rebuild. :P
[18:31] <demosfere> ricotz: i've tried to rebuild a lot of times .. why build-deps aren't being installed
[18:31] <ricotz> infinity, ok, but he is building the same source again
[18:31] <ricotz> infinity, which doesnt include the new packaging fixes
[18:33] <demosfere> ricotz: so the the deb-packaging doesn't match with the source?
[18:33] <ricotz> as i said "you are not generating a new source package containing the new packaging"
[18:34] <ricotz> you need to rebuild the recipe not just the already generated source package in the ppa
[18:35] <doko> infinity, heh, llvm-3.2 and clang ftbfs due to missing b-d on python
[18:36] <ricotz> doko, oh, hi, will this get sync asap to raring if done :)
[18:36] <infinity> doko: Well, that's easy enough to fix, at least.
[18:36] <ricotz> mesa git already depends on it
[18:37] <doko> you should *not* depend on an unreleased version yet
[18:38]  * infinity thinks that perhaps he should step away from the computer and enjoy the sunny Saturday outside for a bit.
[18:38] <ricotz> doko, it isnt me depend on it but a unreleased mesa (in xedgers)
[18:39] <ricotz> the mesa radeon dev introduced it, so just saying would be great to have 3.2rc1
[18:40] <ricotz> doko, https://launchpad.net/~ricotz/+archive/unstable/+sourcepub/2780997/+listing-archive-extra
[18:40] <ricotz> here is an earlier snapshot
[19:07] <jtaylor> doko: distutils.sysconfig.get_python_inc() doesn't return the multiarch path with python3.3
[19:07] <jtaylor> shouldn'T that return the same as python3.3-config?
[19:09] <tumbleweed> wiki.ubuntu.com seem sto have the wrong cert today
[19:24] <jtaylor> is the plat_specific flag in get_python_inc ubuntu specific?
[19:24] <jtaylor> or upstreamable?
[19:27] <jtaylor> can'T find anything in the patches, so I#m assuming upstream
[20:35] <jtaylor> a I hate reportbug ...
[20:35] <jtaylor> friggin think always crashes after I write my nice text ._.
[20:38] <jtaylor> infinity: I forwarded a cython patch to debian
[20:45] <jtaylor> 693555
[22:20] <infinity> jtaylor: Awesome, thanks.  I'll toss that same patch at Ubuntu in a second too, many thanks for hunting it down.
[22:32] <doko> jtaylor, you need to call it twice, the second time with plat_specific=1
[22:33] <jtaylor> doko: yes thanks I figured that out already
[23:54] <infinity> jtaylor: Do, in light of doko's comments, was there a followup patch?
[23:54] <jtaylor> infinity: no, dokos comment is how I implemented in the patch
[23:55] <infinity> jtaylor: Oh, check.  Kay.  I'll snag the patch from the bug and upload to Ubuntu then.
[23:55] <jtaylor> you may also want to wait a bit, I'm sure the debian maintainer will do a swift upload if we ask him
[23:55] <infinity> He may.  He may not.  No harm done in us uploading a fix and then syncing later.
[23:55] <jtaylor> its a very long building package
[23:55] <infinity> And all our buildds are idle and bored.
[23:55] <infinity> Weekend are like that.
[23:56] <infinity> s/Weekend/Weekends/