[12:10] <bddebian> welshbyte: ping?
[12:10] <welshbyte> pong
[12:10] <welshbyte> hey bddebian
[12:10] <bddebian> Hi
[12:10] <bddebian> Hey, are you sure adonthell needed merging, and not just syncing?
[12:11] <welshbyte> um, it was on http://merges.ubuntu.com/universe.html
[12:11] <welshbyte> but maybe there's a newer upstream upstream version?
[12:11] <bddebian> Was my python move the only change?
[12:12] <welshbyte> bddebian: the python move was sorted out in debian, i believe
[12:12] <welshbyte> but yes, from the last version your python move was the only change, it seems
[12:12] <bddebian> That's my question.  Can it be synced straight from Debian than, without needing a merge?
[12:13] <welshbyte> ah i see what you mean
[12:13] <welshbyte> now you mention it, it probably could be :)
[12:14] <welshbyte> there were some changes in config scripts but i couldn't really tell how important they were
[12:14] <ryanakca> Can someone please look at http://revu.tauware.de/details.py?upid=3004 when they get a chance? Only thing left is figure out if the image is GPL or not (from what I see).
[12:20] <kristog>  fix-released != closed ?
[12:21] <somerville32> No.
[12:22] <somerville32> Depends on the package
[12:23] <geser> For which packages isn't fix-released == closed?
[12:24] <kristog> this bug is closed https://launchpad.net/distros/ubuntu/+source/libgalago/+bug/26714
[12:24] <Ubugtu> Malone bug 26714 in libgalago "beagle dies with libgalago error" [Medium,Needs info] 
[12:24] <kristog> edgy ships a newer version and dapper is no more afflicted
[12:26] <geser> then you can set it to fix-released and add a comment
[12:29] <somerville32> Geser: I know of one example
[12:31] <geser> do you remember it?
[12:32] <somerville32> Yup
[12:32] <somerville32> I'd show you too but you probably don't have access to it.
[12:32] <somerville32> (or maybe you do *shrugs*)
[12:33] <somerville32> But, anyhow
[12:33] <somerville32> But the package was Pike
[12:33] <somerville32> There was a security vulnerability in the current version
[12:33] <somerville32> But they had already fixed it upstream and made a release
[12:36] <geser> ok, security bugs may be special
[12:36] <geser> but for normal bugs setting status to fix-releases closes a bug on LP
[12:37] <somerville32> Well, I'd think that any bug fixed upstream and released but not synced would be that special case.
[12:37] <crimsun> the semantics are identical
[12:37] <crimsun> fix released -> closed
[12:37] <crimsun> a bug should not be marked f.r. unless it in fact is available in the archive
[12:38] <somerville32> f.r.?
[12:38] <crimsun> "fix released"
[12:38] <somerville32> Ah, yeah - I got that.
[12:38] <somerville32> I guess I'll change it to f.c. then
[12:38] <crimsun> where it -> fixed package(s)
[12:43] <geser> crimsun: do you know if the universe sponsors team is still working?
[12:44] <ryanakca> since -bug is sleeping... could bug 15178 be closed? The user has reported a fix to the bug.
[12:44] <Ubugtu> Malone bug 15178 in linux-restricted-modules-2.6.15 "fglrx hangs/crashes" [Medium,Needs info]  http://launchpad.net/bugs/15178
[12:45] <crimsun> geser: yes, it is (as is the one for main). We're just incredibly busy atm.
[12:45] <geser> ok
[12:45] <crimsun> I probably have a few thousand unread Ubuntu e-mails that I'll attempt to process tonight
[12:45] <ryanakca> lol
[12:45] <ryanakca> fun
[12:47] <geser> I'm just wondering because my first debdiffs got uploaded very quickly (on the next day) and the recent ones are waiting
[12:47] <crimsun> geser: right, it's called "I was less busy then and am extremely busy now"
[01:25] <wolki_> hi motus! i'm the upstream german translator for comix, and there is an embarrasing bug in the translation for 3.1 (edgy). it doesn't use rosetta (yet?), so i can't fix it myself. what should i do? file a bug with a patch?
[01:31] <Burgwork> wolki_, you can login to rosetta and make teh suggestion yourself
[01:33] <wolki_> Burgwork: the problem is that comix translations are not in rosetta
[01:34] <Burgwork> right
[01:34] <Burgwork> is this a bug in the german translation?
[01:37] <wolki_> yes
[01:37] <wolki_> i confused left and right ^^;;
[01:41] <Burgwork> did you make the mistake yourself, or did an Ubuntu translator make it?
[01:45] <wolki_> nah, I made it... english is clockwise/counterclockwise, i made it turn left/right to fit into the translations for eog and to make it shorter, and used the wrong ones... thinko. and didn't use the feature and only realized it recently.
[01:46] <Burgwork> then yes, file a bug
[01:46] <wolki_> ok, thanks
[01:46] <Burgwork> better would be to get another upstream release
[01:47] <tseng> Burgwork: gnome is in string freeze
[01:47] <Burgwork> tseng, comix isn't gnome
[01:48] <tseng> oh i read eog
[01:48] <tseng> my mistake
[01:49] <Burgwork> no worries
[01:52] <wolki_> Burgwork: I'e already fixed it for upstream's new versionbut that one's not in edgy (at least not yet)
[01:53] <Burgwork> wolki_, if upstream has a new version, reuest that somebody package the new version, rather than carrying a patch
[01:56] <wolki_> iirc there is already a request, but it's an old one for dapper (where the new package didn't happen). should i file a new one for edgy?
[01:56] <Adri2000> hello :)
[01:56] <Burgwork> wolki_, just change the description and reup the bug
[01:57] <Burgwork> wolki_, another way todo it would be to ask the debian maintainer to upload the new version and ask for a sync
[01:57] <wolki_> reup?
[01:57] <Burgwork> mention the new version
[01:58] <Burgwork> anyway, I have to run
[02:04] <Adri2000> i need some help with dpatch : i want to create a few patches (with multiple patched files in each patch) for a new package (initial release). i tried dpatch-edit-patch test in the source directory, i get that : "make: *** No rule to make target `unpatch'.  Stop."
[02:12] <crimsun> Adri2000: did you modify debian/rules as appropriate?
[02:12] <Adri2000> no, don't se anything about that on the wiki
[02:14] <Adri2000> i'm reading http://netz.smurf.noris.de/logs/freenode/2006/07/25/%23ubuntu-motu-school.log i think i'll find the answer there :)
[02:26] <Adri2000> hm, i didn't find anything :(
[02:26] <Adri2000> crimsun: how should i edit debian/rules ?
[02:27] <crimsun> Adri2000: see dpatch(1)
[02:29] <Adri2000> ok
[02:31] <ryanakca> Can someone please look at http://revu.tauware.de/details.py?upid=3004 when they get a chance? Only thing left is figure out if the image is GPL or not (from what I see).
[02:32] <bluefoxicy> it appears to be pervert day .... was another Edgy milestone released?
[02:33] <bddebian> pervert day?
[02:35] <bluefoxicy> bddebian:  there's a lot of off-color jokes about the naming convention for Edgy's milestones going about in some of the channels I'm in; so whenever a new one gets released there's a large influx of perverted comedy.
[02:35] <bddebian> What milestones?
[02:35] <tseng> you're in weirdo channels
[02:36] <bluefoxicy> (okay so about 50 people commented for Knot 1 and only one or two for Knot 2)
[02:36] <bluefoxicy> tseng:  I know
[02:36] <tseng> i don't even see how you could make 'knot' sexual
[02:36] <bluefoxicy> tseng:  I am sure you don't want to know.
[02:36] <tseng> not that I need an example
[02:37] <bluefoxicy> heh, a couple months ago someone in #-offtopic mentioned the possible revival of ubuntu-calendar
[02:37] <bluefoxicy> was that a joke or did someone actually consider it?
[02:38] <Adri2000> crimsun: ok ! i made a patch :) just a question : is there a rule about how naming patches ?
[02:39] <micahcowan> what's the deal with ubuntu-calendar, anyway? Did it only go for a handful of months? I'm surprised it was ever around, considering how controversial it might be for some.
[02:39] <crimsun> Adri2000: name it sensibly.
[02:39] <bluefoxicy> micahcowan:  yeah, the controversy was over whether there was too much nudity or not enough :P
[02:39] <Adri2000> but with 01_foo, 02_bar, .. ?
[02:39] <micahcowan> lol
[02:40] <crimsun> Adri2000: lexical ordering, yes, but make the names sensible
[02:40] <micahcowan> iirc, there weren't even any boobs in the shots... just a butt, right?
[02:40] <Adri2000> yep, ok, thank you
[02:41] <crimsun> ah, the controversy from the old days.
[02:41] <bddebian> heh
[02:41] <bddebian> As opposed to "why the hell is mono default" of today? ;-P
[02:42] <crimsun> back then we didn't even have -motu ;)
[02:42] <micahcowan> if they were gonna decide it was okay to have in universe, they should've at least carried it through a full year. As there is, there ain't enough shots to make a calendar.
[02:42] <tseng> crimsun: eh
[02:42] <micahcowan> crimsun, where did discussion take place, then, -devel?
[02:42] <tseng> micahcowan: yes
[02:42] <tseng> but i talked dholbach into coming here pretty early on
[02:42] <tseng> < 10 members
[02:42] <tseng> or something
[02:43] <bddebian> And what do we have now? 12? :-)
[02:43] <tseng> uh, lots
[02:43] <micahcowan> are all of the shots of ubuntu members? Or are the first few of professional models? (or both?)
[02:43] <tseng> not everyone has stuck around
[02:43] <tseng> micahcowan: 'shots'?
[02:43] <tseng> oh jeez
[02:43] <micahcowan> desktop backgrouns.
[02:43] <tseng> the racy ones are all models
[02:43] <micahcowan> backgrounds.
[02:43] <tseng> the only one with developers was an april fools joke
[02:43] <micahcowan> gotcha.
[02:44] <bluefoxicy> lol
[02:44] <bluefoxicy> nude models mind you.
[02:44] <micahcowan> there wasn't much variety in models, though, right? I seem to remember exactly two different models.
[02:44] <micahcowan> bluefoxicy, but again, just the butt, right? :-)
[02:44] <tseng> there were 3 models
[02:44] <bluefoxicy> micahcowan: I wouldn't have minded being photographed nude but I am not hot enough to be a model.
[02:44] <micahcowan> lol.
[02:44] <tseng> in the original artwork
[02:45] <micahcowan> i c
[02:51] <bluefoxicy> wow
[02:51] <bluefoxicy> whoever wrote this is one hell of an architect
[02:52] <bluefoxicy> the memory tracer I'm toying with replaces sbrk(), calloc(), malloc(), free(), realloc(), vmalloc(), and memalign() to track all growth of the heap and all allocations and frees
[02:52] <bluefoxicy> everything is output to a profile file which is then read by a simulator
[02:53] <bluefoxicy> the simulator uses tuning variables to simulate the behavior of glibc (for example, the MMAP threshold-- when an allocation is bigger than that, it gets its own mmap() segment) and profile the memory usage of the allocator versus the memory requested by the program and show how much memory is wasted (among other stats)
[02:54] <bluefoxicy> you can do all kinds of neat stuff like graph memory use, allocation rate, or wasted memory over the entire course of the program; I'm looking at the average memory waste myself
[02:54] <bluefoxicy> problem is it doesn't seem to be thread safe
[02:54] <bluefoxicy> I'll have to rewrite it to be thread safe; it's going to slow the fuck out of everything I profile but at least I should be able to make it stop corrupting the output.
[02:57] <bluefoxicy> Wolfram Gloger, and it appears to be MIT licensed.
[03:05] <bddebian> welshbyte: Is pybackpack on REVU yours?
[03:06] <welshbyte> bddebian: oh yeah... don't worry about it, i want it taken off REVU (but forgot to request it.. oops)
[03:07] <bddebian> welshbyte: Oh, OK, I'll archive it, thx
[03:07] <welshbyte> bddebian: cheers :)
[03:08] <welshbyte> i'm too proud to put it into universe in its current state of bugginess ;)
[03:32] <Adri2000> crimsun: still here ?
[03:33] <Adri2000> i get "make: dpatch: Command not found" from pbuilder. dpatch must be in the build-depends ?
[03:33] <crimsun> yes.
[03:34] <Adri2000> ok
[03:38] <Adri2000> applying patch 01_qtdir to ./ ... ok.
[03:38] <Adri2000> applying patch 02_bitmapbutton to ./ ... ok.
[03:38] <Adri2000> applying patch 03_bitmapslider to ./ ... failed.
[03:38] <Adri2000> :-|
[03:42] <Adri2000> crimsun: is there a verbose mode for that ? i really don't understand why it fails and 02_bitmapbutton works :/
[03:42] <crimsun> probably because when you created 03_bitmapslider.dpatch you didn't account for the fact that it would be applied _after_ 02_bitmapbutton.dpatch
[03:42] <crimsun> s/dpatch//
[03:43] <bluefoxicy> oh hell yes!  I fixed mtrace!  I think.
[03:43] <Adri2000> ah yes, some files are patched twice : by patch 02 and patch 03
[03:43] <bluefoxicy> nope
[03:45] <Adri2000> crimsun: so i could make only one patch, but it's not really a good solution...
[03:45] <crimsun> or you could create the dpatches incrementally
[03:48] <Adri2000> ok, i'm reading the man, it's explained
[03:51] <bluefoxicy> oh wow, libpthread.so.0 is an elf binary
[03:51] <bluefoxicy> the last time I looked at it it was 2 lines of text
[03:52] <bluefoxicy> oh, it's like 5 lines of text.
[04:15] <Hobbsee> how odd.
[04:15] <bddebian> Heya Hobbsee
[04:15] <Hobbsee> hey bddebian
[04:18] <TheMuso> hey Hobbsee. Sounds like fun.
[04:18] <Hobbsee> TheMuso: heya..  indeed.
[04:19] <Hobbsee> actually, that's the day after it died, so i certainly wasnt driving it.  only way that could have happened was if it was on the back of a tow truck.
[04:20] <TheMuso> haha
[04:27] <Adri2000> crimsun: another problem :)
[04:27] <Adri2000> patches are applied correctly
[04:28] <Adri2000> but then :
[04:28] <Adri2000> dpatch call-all -a=pkg-info >patch-stamp
[04:28] <Adri2000> 01_qtdir.dpatch: script expects -patch|-unpatch as argument
[04:28] <Adri2000> make: *** [patch-stamp]  Error 1
[04:28] <bddebian> Why are you using call-all instead of apply-all?
[04:28] <tritium> hey bddebian
[04:29] <bddebian> Hi tritium
[04:29] <tritium> bddebian: still no sync?
[04:29] <bddebian> Nope :-(
[04:29] <tritium> okay, no worries
[04:30] <Adri2000> bddebian: there is dpatch apply-all before : apply-all, appliying... ok, call-all and error
[04:30] <Adri2000> -i
[04:31] <bddebian> You are doing call-all in rules or apply-all performs a call-all?
[04:31] <Adri2000> i put in debian/rules exactly what is specified in the man :
[04:31] <Adri2000> patch-stamp:
[04:31] <Adri2000>   dpatch apply-all
[04:31] <Adri2000>   dpatch call-all -a=pkg-info >patch-stamp
[04:32] <bddebian> Hmm, I don't think I've ever seen call-all used
[04:32] <Adri2000> can i remove the call-all line ?
[04:34] <bddebian> I think so
[04:35] <Adri2000> ok, i try that
[04:35] <TheMuso> I use the include file. SOmething like /usr/share/dpatch/dpatch.make
[04:35] <TheMuso> include /usr/share/dpatch/dpatch.make
[04:36] <TheMuso> I put that in debian/rules
[04:37] <Adri2000> just include and nothing else to change ?
[04:37] <TheMuso> You still have to put the relevant bits in to make sure the patch steps are performed. All that include line does is include the snippets like what you posted above. I am pretty sure the man page talks about the include file.
[04:42] <Adri2000> ok, anyway my patches now work :) tanks
[04:42] <Adri2000> thanks
[04:42] <Adri2000> thanks
[04:42] <Adri2000> oops...
[04:43] <Adri2000> no 'tanks', just one 'thanks' TheMuso ;)
[04:43] <bddebian> :-)
[04:49] <welshbyte> brings a new meaning to getting tanked :)
[04:53] <bddebian> heh
[04:54] <welshbyte> bddebian: will you be attending the CC meeting on tuesday?
[04:55] <bddebian> welshbyte: If you are gonna be there, I will try :-)
[04:55] <welshbyte> oh i'll be there :)
[04:55] <welshbyte> guess i should buy myself some other fans
[05:01] <bddebian> buy?  I don't remember getting any money :-)
[05:03] <welshbyte> sorry did i say "buy"? i meant brown nose :)
[05:04] <theCore> is still there a need for a MOTU logo?
[05:08] <bddebian> welshbyte: :-)
[05:12] <theCore> here an attempt of logo: http://peadrop.com/files/motu-logo-attempt.png
[05:13] <bddebian> What, no he-man? :-)
[05:15] <welshbyte> if i had to draw a MOTU logo i'd do three small ubuntu symbols swirling in the distance like galaxies
[05:15] <welshbyte> but i have no skill
[05:15] <theCore> it basically a "sun", for universe, and a sergeant wings for master
[05:17] <theCore> I also thought about doing some sort of spiral that could vaguely resemble the Ubuntu logo
[05:24] <theCore> another attempt, http://peadrop.com/files/motu2.png
[05:26] <theCore> It isn't easy to design a logo that represent MOTUs well
[05:27] <crimsun> isn't the current LP logo a hammer?
[05:28] <theCore> crimsun: https://wiki.ubuntu.com/MOTU/Logo should be updated then
[05:29] <crimsun> ah, no, mistaken for core-dev
[05:43] <theCore> that one doesn't look bad, http://peadrop.com/files/motu3.png
[05:44] <theCore> it likes a mix between Ubuntu logo and a galaxy shape
[05:51] <theCore> maybe I'm just losing my time, and MOTUs aren't "brandable"
[05:52] <theCore> anyway
[05:52] <theCore> 'night all
[08:35] <Arbiter> 'morning
[09:47] <Arbiter> hey Gloubiboulga
[09:47] <Arbiter> :)
[09:50] <Gloubiboulga> hello Arbiter
[10:38] <phanatic> morning
[11:24] <Arbiter> hey Hobbsee
[11:24] <Hobbsee> hey Arbiter
[12:08] <Sp4rKy> \o
[12:47] <heno> I'd like to plead for some help with reviewing and uploading some universe packages!
[12:47] <heno> http://revu.tauware.de/details.py?upid=2993
[12:48] <heno> and http://revu.tauware.de/details.py?upid=2994
[12:48] <heno> The plan is to move them through universe and into main before feature freeze :)
[12:49] <heno> It's a a11y SoC project. Chris, the student, has packaged it but is not a MOTU yet
[12:49] <ajmitch> good luck, they look like they need some work :)
[12:49] <heno> ajmitch: really, in what sense?
[12:50] <ajmitch> not using python policy, etc
[12:50] <ajmitch> I'll try & write up some stuff on revu
[12:51] <heno> ajmitch: ok, thanks
[12:52] <tortoise_> ajmitch where is this python policy?
[12:52] <ajmitch> http://wiki.debian.org/DebianPython/NewPolicy
[12:52] <tortoise_> this one http://www.debian.org/doc/packaging-manuals/python-policy/
[12:53] <ajmitch> yes
[12:53] <ajmitch> plus you should use ${shlibs:Depends}, target edgy, use an orig.tar.gz (non-native versioning), and remove unnecessary cruft from debian/rules
[12:54] <ajmitch> I doubt you'd want to make a new upstream release for every minor packaging change
[02:49] <tortoise_>  ajmitch: Did you write some stuff on REVU.  Do I have to log in to see it, I can't for some reason.
[02:51] <Hawkwind> Yes you have to be logged in
[02:55] <tortoise_> When I click recover password it asks me to paste the text below into gpg
[02:55] <tortoise_> there is however, no text
[03:11] <xerxas> Hi, I would like to backport edgy's mldonkey, I want to use pbuilder
[03:12] <xerxas> pbuilder create doesn't work as non root
[03:12] <xerxas> is it normal ?
[03:12] <kristog> yes.
[03:12] <kristog> sudo pbuilder create sid --mirror ....
[03:12] <kristog> sudo pbuilder build $pkg.dsc
[03:12] <xerxas> ok
[03:12] <Hobbsee> ... why sid?
[03:12] <xerxas> thanks
[03:13] <Goshawk> how can i obtain my REVU password?
[03:13] <Goshawk> lostpw-py is broken
[03:13] <kristog> Hobbsee: *habi*
[03:13] <kristog> Hobbsee: *habit*
[03:13] <Goshawk> s/-/.
[03:13] <xerxas> I have read the packing guide, how can I contribute now M
[03:13] <xerxas> ?
[03:14] <Hobbsee> kristog: well, not a good habit if you've building for edgy.
[03:14] <xerxas> I have a gpg key, not signed thought
[03:15] <kristog> Hobbsee: uhm afaik edgy == unstle, it isn't?
[03:15] <Hobbsee> kristog: no.
[03:16] <Hobbsee> xerxas: you dont need a signed key, you're nto uploading it yourself
[03:16] <Hobbsee> kristog: we take a snapshot of debian unstable, and merge it
[03:16] <xerxas> Hobbsee:  so how can I contribute M
[03:16] <xerxas> ?
[03:16] <xerxas> is there a todo list ?
[03:17] <xerxas> should I try to fix bugs ?
[03:17] <xerxas> do some bug triage ?
[03:17] <Hobbsee> gah.  where's dholbach when you need him
[03:17] <Hobbsee> that's useful too
[03:17] <kristog> Hobbsee: yes, ok, what i mean is that edgy is the last ubuntu version avaible
[03:17] <Hobbsee> see the /topic
[03:17] <Hobbsee> kristog: true.  unstable usually refers to debian unstable
[03:18] <xerxas> Hobbsee:  where you advise me to start in the topic ?
[03:18] <xerxas> UNMETDEPS?
[03:19] <Hobbsee> xerxas: first link, on how to participate
[03:22] <xerxas> Hobbsee:  you mean http://wiki.ubuntu.com/MOTU ?
[03:22] <Hobbsee> xerxas: yep
[03:22] <xerxas>  ok
[03:22] <xerxas> thanks
[03:27] <Lathiat> anyone remember th ename of the program that prints word documents out in text
[03:27] <Hobbsee> Lathiat: only that there are two versions of it.  tseng knows, iirc.
[03:27] <Hobbsee> Lathiat: he asked me about it
[03:27] <Lathiat> i used to use it way back
[03:27] <Lathiat> cant rmemmember the name and apt-cache is failing me
[03:28] <StevenK> catdoc is one
[03:28] <Lathiat> ah, antiword
[03:28] <geser> and there is also wv
[03:28] <StevenK> My boss makes great use of catdoc.
[03:29] <tseng> Hobbsee: thats wv
[03:30] <tseng> Hobbsee: but that isnt what he asked for
[03:30] <Lathiat> ah turns out i have some whack permissiosn on my package lists
[03:30] <Lathiat> which is why apt-cache was turning a blank
[03:30] <Hobbsee> tseng: ahhhhh.....
[03:41] <tortoise_> is there a way to fetch my revu password?  I think the password recover program is nackered
[06:00] <trappist> if a very minor bug is known to exist upstream, is it best to submit the fix upstream and wait for it to come back down the pike?  if so, what to do with the launchpad bug?
[06:01] <trappist> bddebian
[06:02] <bddebian> Hi trappist
[06:02] <bddebian> Heya gang
[06:02] <AnAnt> bddebian: hide
[06:03] <bddebian> Uh oh :-)
[06:04] <bddebian> AnAnt: Have more work for me? :-)
[06:05] <AnAnt> bddebian: nope, not more than yesterday's stuff
[06:05] <AnAnt> bddebian: nothing new I mean
[06:05] <welshbyte> trappist: yeah if it doesn't affect things in ubuntu then it's probably best to wait for upstream to fix it and get on with some more important stuff ;)
[06:05] <welshbyte> bddebian: howdy
[06:05] <AnAnt> bddebian: you remember them ?
[06:05] <bddebian> Heya welshbyte
[06:05] <trappist> welshbyte: all the ones I'm talking about are very similar to bug 58589
[06:05] <Ubugtu> Malone bug 58589 in kdebase "Grammatical error in kcmkonq string" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/58589
[06:05] <bddebian> AnAnt: I don't remember which one I said I would advocate.  I was looking last night
[06:06] <trappist> welshbyte: (and submitted by the same guy)
[06:06] <AnAnt> bddebian: archmage
[06:06] <AnAnt> bddebian: but I also uploaded kchmviewer & acon yesterday as I fixed the issues you & demon@poleboy.de mentioned
[06:06] <AnAnt> demon doesn't seem to have come online since 2 days
[06:07] <AnAnt> his nick starts with an s
[06:07] <AnAnt> but not one of the s* here now
[06:07] <tseng> i see several s's
[06:07] <trappist> welshbyte: also, this submitter and I agree that importance is relative - they're string fixes, and he and I are both on something of a campaign to improve polish by fixing these things
[06:08] <AnAnt> bddebian: but if you want more stuff to review tell me
[06:08] <bddebian> Oh there is plenty on REVU and I'm trying to dig through MOTUREviewer bugs too
[06:08] <AnAnt> k
[06:08] <welshbyte> trappist: one of my old bugs (bug #3960 ) was similar and bddebian fixed that one
[06:08] <Ubugtu> Malone bug 3960 in gtodo "Typos in Misc Preferences tab" [Medium,Fix released]  http://launchpad.net/bugs/3960
[06:09] <AnAnt> sorry if I am bugging you
[06:18] <bddebian> Oh man, was I mean to AnAnt?
[06:19] <welshbyte> nah
[06:49] <Goshawk> is there a pbuilder guru here?
[06:55] <geser> I'm not a guru but perhaps I can help you nonetheless (or someone else)
[07:07] <Goshawk> thanks... my problem is taht i wanna to preserve the buildplace because i'm making a package and i should veryfy where teh compiled files are
[07:07] <Goshawk> geser: i tried the --preserver-buildplace
[07:07] <Goshawk> but didn't work
[07:07] <Goshawk> also --debug does not do this
[07:11] <geser> have to tried pbuilder login an then to build the package from within?
[07:13] <Goshawk> geser: no
[07:13] <Goshawk> how to do it?
[07:13] <Goshawk> pbuilder login to login
[07:14] <Goshawk> but how to put the folder to build in it?
[07:14] <Goshawk> (the source tree)
[07:15] <geser> you could copy into the dir where pbuilder is currently running your session
[07:15] <Goshawk> but when i do pbuilder login i'm chrooted in it
[07:16] <Goshawk> i'm logging in
[07:16] <geser> yes but you can still copy from outside
[07:16] <Goshawk> in another shell you mean
[07:16] <geser> yes
[07:19] <Goshawk> ok it's here
[07:19] <Goshawk> now i should run debuild
[07:19] <Goshawk> now found
[07:19] <Goshawk> not
[07:20] <geser> install devscripts inside pbuilder
[07:20] <Goshawk> done
[07:21] <Goshawk> unmet dependecies.. trying to find a way to solve it without typing the whole package list
[07:23] <geser> if the package is known to apt  you can apt-get build-dep packagename
[07:23] <Goshawk> no it's a new version of gcc
[07:23] <Goshawk> it's modificated
[07:24] <Goshawk> i've only the source tree
[07:25] <Goshawk> ehehhe
[07:25] <Goshawk> solved
[07:25] <Goshawk> yep it's a brute hack
[07:25] <Goshawk> but it works
[07:26] <Goshawk> strange that --preserve-buildplace does not work
[07:27] <Goshawk> thanks for your help geser
[07:32] <Goshawk> another little thing: in man pbuilder i read  --debug
[07:32] <Goshawk>               Turn on Debug mode of pbuilder, to be verbose about errors,  and
[07:32] <Goshawk>               try to avoid cleanup processing when error happens in update
[07:32] <Goshawk>                and create targets.
[07:32] <Goshawk>  i did pdebuild -- --debug it failed and the cleanup procedure was done. should i fill a bug against pbuilder?
[07:37] <tortoise_> ls
[07:38] <tortoise_> ^^whoops
[08:49] <love>  
[08:49] <love> 
[08:50] <RichiH> did love just spam the channel?
[08:50] <love>  
[08:50] <love> 
[08:50] <love>  
[08:50] <RichiH> love: i need you to stop with that, please
[08:51] <love>     
[08:51] <love> 
[08:51] <love> 
[08:51] <love> 
[08:51] <love> 
[08:51] <love> 
[08:51] <love> 
[08:52] <RichiH> *sigh*
[08:52] <RichiH> anyway, have fun, guys :)
[09:01] <sladen> love: if you're going to spam the channel, could you please at least use UTF-8 :)
[09:46] <kristog> do you know  where i can put diff and dsc from a merged /but not uploaded package?
[09:47] <bddebian> File a bug on malone, attach the diff and subscribe MOTU Reviewers
[09:47] <kristog> motu reviewer is a ml?
[09:48] <kristog> s*
[09:49] <bddebian> No a LaunchPad group
[09:49] <bddebian> I think it's actually motureviewers
[09:56] <woodstoc1> Hello?
[10:08] <woodstoc1> Hi all! I have made a package (my first one) for bkchem (bkchem.zirael.org) but I have trouble to understand which files exactly I should upload to the REVU service. I already read the wiki-page but it seems that I am to stupid to understand it. I already put some effort (a huge amount in fact) into that package and it would be a shame if it would fail at this stage.
[10:10] <tortoise_> woodstoc1 just dput revu your-package.changes and dput should do the rest
[10:11] <woodstoc1> that one?
[10:11] <woodstoc1> bkchem_0.11.5-0ubuntu1_i386.changes
[10:11] <kristog> yes
[10:12] <bddebian> bkchem is already on revu
[10:12] <woodstoc1> I asked because I wondered if there is a special one if I would run "dpkg-buildpackage -S -sa ...
[10:15] <woodstoc1> Well, it worked. Thank you.
[10:23] <tortoise_> ajmitch: ping
[11:37] <vil> doko: hi, do you have few minutes for chit-chat?
[12:03] <BHSPitMonkey> hi all