[06:11] * Quex01 np: Johnny Rebel jr. - Ship those Niggers back [02:00] [06:11] BATH IN NIGGER'S BLOOD [06:11] !ops [06:11] Help! Hobbsee, Riddell, sladen, fbond, mneptok, gnomefreak, Seveas, dholbach, elkbuntu, PriceChild, or jpds! [06:12] AFRICA IS FOR APES, EUROPE IS FOR WHITE! [06:13] GARBAGE JUICE! SALMANELLY! [06:13] * Quex01 np: Public Enemy - Anti-Nigger Machine [03:17] [06:14] hinnger i hate your face [06:14] NIGGERS ARE LIKE SALMANELLI !!! GARBAGE JOUCE! [06:15] * Quex01 np: JEWTHANASIA (DEN) - 13. White Pride – JEWTHANASIA (DEN) [02:48] [06:18] * Quex01 np: German Military Marches - Eger [02:40] [06:21] thanks elky ;) [07:54] So... A package went from nginx to nginx-light, nginx-full, and nginx-extras; the three new packages replace each other; nginx became a dummy package to select nginx-full; I'm having some troubles though. Any help with getting it to work right? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609254 [07:54] I know it's a debian question- but they seem to all be sleeping over there [07:56] the best I can come up with is adding to nginx-* s/Conflicts/Replaces:/ and to nginx Replaces: nginx (<< 0.8.54-1) Breaks: nginx (<< 0.8.54-1) === hanska is now known as dapal [08:54] <\sh> happy new year :) [08:54] <\sh> siretart: can you approve me for ubuntu fai team again? I'm expired ;) === vish is now known as evilvish [11:15] <\sh> siretart: merci :) [11:55] Hi, what happen with LP? LP send me a lot of bug emails that linked to debian bug [11:55] a lot of status changes === hannesw_ is now known as hannesw [14:03] i have a main package that needs sponsoring ... [14:03] currently building here : https://launchpad.net/~rohangarg/+archive/experimental/+builds?build_state=building [14:04] oh crap ... forgot something === yofel_ is now known as yofel [14:51] tumbleweed: T&S sent. this is the longest section, so feel free to send me part of it if you can't do it all in one sitting :) [14:51] * Laney accidently destroyed ~90% complete T&S replies [14:51] twice [14:52] heh [14:52] lfaraone: thanks [14:52] Isn't NM fun! [14:52] Laney: barrels. at least he's got a responsove AM. [14:52] ;) [14:53] I've actually done T&S (yesterday), but he doesn't seem to have updated the website [14:53] * tumbleweed gets a cup of coffe and sits down to it (not like I was going to get any more work done today, anyway) [14:55] tumbleweed: what's your day job, anyway? [14:55] good morning [14:55] away [14:55] dholbach: hi. I see you don't own the ubuntu-sponsoring branch any more. Can we just land merges in it, or do you need to bzr pull on the other side? Also, can it be upgraded to 2.0? [14:55] tumbleweed, pull on the other side, but that could be automated, I guess [14:55] lfaraone: student (who really needs to work on my thesis more...) [14:55] tumbleweed, still I think we should be still using merge proposals [14:56] tumbleweed, hum... upgraded - let me see [14:56] dholbach: good afternoon :) [14:56] hi geser [14:56] geser, in Dallas this week :) [14:56] dholbach: great, as long as you are still reviewing & landing merges on it, that's really what matters. [14:57] figured it out by now, wondered why IRC is so quiet today [14:57] tumbleweed, I think if somebody in ~ubuntu-dev reviews and merges it, that's totally cool with me - that's why I moved the branch [14:57] ok, but until there's automatition, you'd probably be involved [14:58] hello all [14:58] tumbleweed, I'll try to have a look at the open merge proposal later on, but it'll be a busy day [15:01] tumbleweed, branch should be updated now [15:05] tumbleweed: heh. I myself have midterms this week :P [15:07] hello ari-tczew [15:08] dholbach, hello [15:08] hi coolbhavi [15:08] hi [15:20] dholbach: thanks, no rush [15:21] tumbleweed, bdrung is on it [15:21] indeed [15:26] dholbach: merged. you can pull it. [15:26] done [15:27] thanks === Lutin is now known as Guest92216 === RoAk is now known as andreserl [18:02] hello there, if I want to start a python using dh_make should I specify "single binary" or "indep binary"? [18:03] s/python/python package/ [18:04] al-maisan: indep for pure Python, single binary for python extensions (C, C++, pyx, etc.) [18:04] thanks tumbleweed ! [18:31] ttx, i like the sound of your fosdem talk. which day is that on? [18:48] I am trying to package a python extension with a cpp file that needs to be compiled; when I build the new package in pbuilder I get the following error: [18:48] dev [18:49] sorry: [18:49] src/geohash.cpp:72: fatal error: Python.h: No such file or directory [18:49] I guess I need to require python-dev [18:50] yes, perhaps even python-all-dev if you want to compile for all supported python versions [18:51] geser: thanks, will try that. [18:51] geser: that would be a "Build-Depends:" entry. Right? [18:51] yes [18:52] great, thanks! === al-maisan is now known as almaisan-away === Lutin_ is now known as Lutin [19:25] directhex: saturday, 3:30pm I think [19:26] directhex: http://wiki.debian.org/Java/DevJam/2011/Fosdem/TalkSchedule [19:26] It's actually a trilogy. [19:28] oh dear, i hope it doesn't clash [19:29] i've got my talk "Mono packaging in Debian and Ubuntu - why we're always right" on saturday [19:29] you might enjoy it [19:29] haha [19:29] directhex: Good one. :-) [19:30] * iulian cannot go to fosdem unfortunately. :( [20:09] now that's irritating - I can't create a pbuilder maverick chroot under natty [20:09] my pbuilderrc: http://pastebin.com/H43MKA2B [20:09] I run sudo DIST=maverick pbuilder --create [20:10] kklimonda: sudo -E DIST=maverick pbuilder --create :) [20:10] let see if pbuilder-dist works better [20:10] tumbleweed: no, I use sudo without -E for a reason [20:10] it should work - it did in the past [20:11] (I've had CC=clang for some time, and it did propagate to pbuilder chroot breaking builds ;) ) [20:11] kklimonda: sudo's configuration file changed in natty to include env_reset, which means sudo pbuilder will use HOME=/root [20:11] tumbleweed: oh.. [20:12] (no wonder my hooks didn't work) [20:12] * kklimonda feels tired [20:12] heh === almaisan-away is now known as al-maisan [20:42] geser: could you rerun FTBFS script? a lot of packages are deprecated [20:44] ari-tczew: Last update 2011-01-10 20:14:22 +0000 [20:44] micahg: so there is another problem [20:44] ari-tczew: which one? and I don't have access to the machine where the scripts run [20:46] geser, micahg: nevermind, my bad [20:56] geser: another question: is it possible to rebuild all packages in universe which are on FTBFS page? buildlogs are deprecated [20:57] mass give back IIRC [20:59] ari-tczew: what you mean with "deprecated"? just old? [20:59] do you have a reason why you think they'll build now? [20:59] geser: I mean that now there is new FTBFS message [21:00] new FTBFS message? I seem to lack some context [21:01] geser: well, e.g. builder on LP has got buildlog from 01.11.2010 and it shows that there is problem with DSO linking. now if I build this package, I see another FTBFS message [21:02] I guess it's not hard to gotcha [21:02] ari-tczew: lucas just did a rebuild a couple of days ago. Not recent enough? [21:02] ah [21:04] tumbleweed: we discuss about FTBFS geser's script [21:05] ari-tczew: only buildd admins can do mass-give backs as far as I know [21:05] you can only click on the retry buttons of every package (or use the ubuntu-build script) [21:06] ari-tczew: just look at lucas's rebuild result if you want to know what's more current [21:07] micahg: you don't understand. I mean that if someone looks on FTBFS geser's script, buildlogs show deprecated output. [21:07] it's not good. [21:07] ari-tczew: doing a mass give back just to get new buildlogs seems a bit crazy. If they aren't going to build, why rebuild them. The same issues are presumably present. [21:07] ari-tczew: you are misusing the word "deprecated" [21:07] ari-tczew: that's standard fare for that page though [21:07] tumbleweed: the reason is working on correct FTBFS issue [21:08] now I have to build locally current existing package in archive [21:08] ari-tczew: I don't know about you, but I test build locally before I start working on an FTBFS [21:08] before any patching [21:08] no sense [21:08] it's not efficient [21:09] mass giving back just for fresh build logs isn't efficient either [21:09] sure, there is, it might have been fixed, also sometimes it's easier to fix when you can see what's happening where it fails [21:09] (plus, you can play around in pbuilder, if you have a shell hookscript, and try a few fixes) [21:10] the FTBFS page only displays the current state of the archive, if the last build-attempt is from Nov 2010 than the page displays it, it can't do retries on it's on now and then to keep the logs "current" [21:10] ok you like wasting a time on pbuilder before patching, I don't want still discuss in no sense [21:10] you prefer to waste the buildd time? [21:10] it's machine [21:10] I'm human [21:12] ari-tczew: yes, but those resources are shared by everyone [21:12] I only see that contributors are for machines, not machines for us to make work easier [21:12] ari-tczew: plus, as I said earlier, there are newer build logs available (lucas' rebuild) [21:13] I agree with ari-tczew. contributor time is infinitely more valuable than cpu time [21:13] is there room in the /topic for the new rebuild results? [21:13] ari-tczew: talk to the buildd admins if you want regulary mass-givebacks, they are in a better position to implement it (if they think that's a good idea) [21:13] tumbleweed: so this way I have to spend more minutes on looking also on lucas page udd [21:15] geser: who is admin of buildd? [21:15] where can I find them admins? [21:15] ari-tczew: I don't think it would take you *that* long. Personally I have no issue with stale logs, and I tend to test that a package can be built locally before giving it back. [21:16] tumbleweed: look from another hand [21:16] ok, you will notice that there is new FTBFS message [21:16] this information will stay only on your mind [21:17] ari-tczew: https://launchpad.net/~launchpad-buildd-admins [21:17] another day, another contributor will have a look on geser's FTBFS page [21:17] I seem to remember someone suggesting not sending FTBFS messages to uploaders from failed give-backs, but rather to the requster - that'd help [21:17] and he will be confused, because there is another FTBFS message! [21:17] what's going? - he thinks [21:17] ari-tczew: as I said, that's standard fare for any buildd log failure [21:18] tumbleweed: That was me. Someone should file a bug on LP about it. [21:18] they should be taken with a grain of salt since new uploads could've changed the failure [21:19] micahg: I don't understand your words. [21:19] what's your point, quo vadis.. [21:19] ari-tczew: you'd have to constantly rebuild to have up to date logs [21:20] because they should be updated [21:20] flow of information [21:20] masacre, developers couldn't understand this thing [21:21] * Rhonda suspects that ari-tczew is discussing now way longer (and using the resources of the others involved in the discussion) than the test build would had taken. [21:23] Rhonda: this is not a case of one package [21:24] and there is another point of discussion - who is more important - server or contributor's time? [21:24] and I see that a lot of people here prefer to wasting contributors time [21:24] maybe servers will take merges and FTBFS' fixes? [21:28] No, that's not what lot of people her prefer nor did actually state. It would be nice if you'd not put words in other people's mouths. [21:31] It would be nice if you'd take off slippers from your eyes. [21:41] Don't have any there, sorry to disappoint you. === al-maisan is now known as almaisan-away