=== almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === apachelogger_ is now known as apachelogger === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [06:51] good morning [07:26] *sigh* [07:26] Why does the software center have to be so strange … and has *no* icon now for wesnoth in oneiric?! [07:27] Who can I bark at for getting that fixed, and potentially not run into the same issue for the wesnoth 1.10 release that might hit precise? [07:28] I seem to remember that we had the same issue when we switched from 1.6 to 1.8 in the first place, but that puzzles me now. :/ [07:28] That it seems to got disfunctional again, in between. [07:30] Rhonda: try talking to mvo === ara is now known as Guest79243 [07:40] geser: thanks === almaisan-away is now known as al-maisan === dholbach_ is now known as dholbach === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan [12:10] hi, when mass-sync from debian started? [12:10] many 'new' packages from debian not sync in precise [12:12] udienz, https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule does say it's not defined yet. [12:14] udienz: I started it on Monday [12:15] udienz: I've been processing new packages, but haven't worked my way through all of them yet [12:15] udienz: If there are specific ones you care about, tell me [12:15] (it's awkward to automate because we have to be careful about ones that were previously removed from Ubuntu for some reason) [12:17] I've been getting through, er, rough estimate maybe 50 a day [12:19] * udienz chose to wating 'till monday [12:19] udienz: huh? [12:19] udienz: I started it Monday as in three days ago [12:19] udienz: if there are specific new packages you care about, tell me [12:22] cjwatson, owh i think nexy monday [12:22] i;ll looking my packages first [12:30] cjwatson, bug 878809 glfw package [12:30] Launchpad bug 878809 in glfw (Ubuntu) "Please sync glfw 2.7.2-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/878809 === al-maisan is now known as almaisan-away [12:35] udienz: you can just tell me the package names, I don't need bugs [12:35] er, actually, maybe that's a bad precedent. but I do not want to be told about the same thing by a bug *and* on IRC, in any case [12:35] udienz: also, that isn't a new package! [12:36] udienz: that's a new version of an existing package. perhaps you're unaware that we're syncing from testing by default this cycle, unless explicitly requested otherwise [12:37] udienz: once that bug has been acked by a sponsor, it will appear on the list of manual syncs we need to do [12:37] which is a "run a tool once a day or so" kind of thing [16:33] grr, this bug bot is a pain [17:12] is there a "yes" option for mk-build-deps so it does not ask whether I really want to install the dependencies [17:14] c_korn: untested, but I think -t 'apt-get -y' [17:15] ok, I test it ;) [17:15] or MKBUILDDEPS_TOOL='apt-get -y' in ~/.devscripts.conf [17:15] sorry, ~/.devscripts [17:16] I try the command line option first. I have mk-build-deps in a alias anyway [19:34] hum, a pkgconfig file in an arch-indep library -dev package contains this line "Cflags: -I${includedir}/c++-gtk-utils-2-2.0 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include " does this mean it has to be arch dependent now? === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === yofel_ is now known as yofel [21:19] good evening [21:43] anyone wanna help me sort out the fact that boinc-client is broken? [21:43] :D [21:51] bug 878571 for those that don't follow #ubuntu-bugs [21:51] Launchpad bug 878571 in boinc (Ubuntu) "boinc-client bad signature for URL" [Undecided,Confirmed] https://launchpad.net/bugs/878571 [21:52] yofel: thanks :) [22:01] what was the name of that script that could tell you what ubuntu releases there were, which was the development release etc? [22:03] distro-info [22:07] thanks [22:36] anyone familiar with git-buildpackage? I'm having an issue where the orig.tar.gz is not being extracted from the git repo .. resulting in a "failed .. no orig.tar file found" [22:44] Kiall: is it finding the upstream branch ok? [22:44] it seems to... [22:45] when i `rm debian/source/format` (native package) it works .. [22:45] but with a 3.0 (quilt) package, it fails [22:46] arand: I end up with this error: http://pastie.org/2732409 [22:47] It doesnt seem to even try and extract the tar.. [22:48] any ideas what might be causing it? :) [22:50] Kiall: Do you have a pristine-tar branch? Is the gbp.conf set up right to build from pristine-tar? [22:51] RAOF: yea branch is there .. and I think I have it setup right: http://pastie.org/2732432 [22:52] Kiall: Yeah, that looks right. What's the full output of git-buildpackage? [22:52] Full output is here: http://pastie.org/2732409 [22:52] no mention of pristine-tar in it though [22:56] Hmm, what happens if you omit the export dir? [22:56] the ../build-area option? [22:56] Yeah.. [22:57] same thing, no mention of pristine-tar [22:58] If you just run it with --pristine-tar option? [22:58] you mean --git-pristine-tar ? [22:58] Ah, yeah [22:58] I'll try again, just in case! [22:58] Humm.. [22:59] Oh .. dooh .. tried it in a copy without quilt ;0 [22:59] Oh .. dooh .. tried it in a copy without quilt ;) [23:00] same thing again, no mention of pristine-tar [23:00] Do you know of a public repo that uses GPB and pristine-tar? Maybe I can test that [23:02] Humm .. Okay, testing with a repo I found and its working [23:02] http://anonscm.debian.org/gitweb/?p=pkg-xorg/app/apitrace.git;a=summary does. [23:02] Hah, too slow. [23:04] The only obvious difference is one has an pristine-tar and origin/pristine-tar, while my only has pristine-tar [23:05] nope .. thats not it :( [23:05] Mind taking a look? https://github.com/kiall/test/tree/pristine-tar [23:06] I've obv got something wrong with the repo [23:10] aha! [23:10] https://github.com/kiall/test/blob/master/debian/changelog#L1 .. [23:10] needed to add a -1 to the end of the version [23:11] Oh. To make it non-native. Right. [23:12] yea, makes sense (now) [23:12] thanks RAOF / arand [23:19] since you guys would probably know, since the upstream package is also managed in git, is it possible for me to clone that repo, and use gpb + quilt without git-import-orig? [23:22] Kiall: Absolutely; the apitrace repository I linked to above does exactly that. [23:22] ah .. tried that first and didnt get it working :) [23:23] how does the pristine-tar branch get managed so? [23:24] I just manage it manually - ?pristine-tar commit ../path-to-tarball upstream-branch? [23:25] so you create actually create a .tar.gz based on the upstream branch? [23:26] Well, that depends. If there *is* no upstream tarball then you need to create one, but if you're packaging a release you start with their tarball. [23:27] and pristine-tar picks up on being inside a git repo and does the rest? [23:37] Yeah. pristine-tar commits to the pristine-tar branch :) [23:40] cool :) should be easy to switch over then [23:41] RAOF: So when you import-orig you only touch the pristine branch, and the debian branch? [23:44] arand: I don't import-orig. [23:45] arand: I merge the upstream release tag the tarball is based on into the ?upstream? branch, merge ?upstream? into debian, and pristine-tar commit the tarball.