[00:51] <RoAkSoAx> nixternal, around?
[01:02] <pochu> Jazzva: regarding autoreconf patches: yes, they tend to be huge, but you can make them smaller by running the same autoconf/automake/intltoolize... versions as upstream did
[01:02] <pochu> Jazzva: but that's ok, thanks for the debdiff!
[01:03] <Jazzva> pochu: No problem... I noticed I missed one change - to add to lintian-overrides that it depends on quilt 0.40-1, lintian produces one warning for depending on -1.
[01:04] <Jazzva> pochu: So, I'll just add that and upload new patches... to reduce the upload, do you need diffs with or without .po files :)?
[01:04] <pochu> Jazzva: can't you depend on 0.40?
[01:04] <pochu> without the -1
[01:04] <pochu> Jazzva: and regarding the po changes from MoM... always remove them
[01:05] <Jazzva> pochu: It's introduced in debian, I know I saw a log why it has to depend on -1
[01:06] <pochu> Jazzva: ok, live it anyway, that's just a warning and we don't want to add more useless diff
[01:06] <Jazzva> pochu: Ok...
[01:08] <Jazzva> pochu: Tracker merge seems to be a lot easier ... just to remove some Debian deps we don't use (qdbm), and to check if we still need patches from debian/patches...
[01:08] <pochu> yup
[01:09] <pochu> Jazzva: you will likely need all of them, as Debian has 0.6.6 too
[01:12] <Jazzva> pochu: Yep... Just checked. I'll do a testbuild and upload the diffs...
[01:14] <pochu> Jazzva: wait, I'm reviewing it
[01:21] <pochu> Jazzva: looks fine, just make the changelog entry a bit more verbose (mention what files you have removed, that we don't build a liferea-webkit package...)
[01:21] <pochu> Jazzva: feel free to copy&paste from older changelog entries for the remaining changes if you want ;)
[01:21] <pochu> Jazzva: but other than that the merge looks perfect, I'd sponsor it if I could :-)
[01:23] <Jazzva> pochu: Thanks :)... I'll prepare a new patch and subscribe sponsors.
[02:34] <Jazzva> pochu: Uploading new debdiffs. I'll be off when it finishes, too tired.
[05:48] <LaserJock> anybody familiar with python conditionals about?
[05:54] <persia> LaserJock: I'm not familar, but suspect that if you described your test problem, one of you, I, or some lurker might have the answer :)
[05:56] <LaserJock> sure
[05:57] <LaserJock> I'm wanting to do a pretty extended if statement
[05:57] <LaserJock> basically something like:
[05:57] <LaserJock> if x == y && z == (q|r|s)
[06:00] <x1250> does that even work?
[06:00] <persia> OK.  I think that's if(x==y){if(z=(q|r|s){...
[06:00] <LaserJock> x1250: no, that's why I'm asking
[06:00] <LaserJock> :-)
[06:01] <LaserJock> ok, so x == y and z = ( q or r or s ) it seems to be ok with
[06:01] <persia> Ah.  Maybe you wanted || instead of | ?
[06:01] <Amaranth> if x == y and z in (q, r, s)
[06:01] <x1250> LaserJock: try #python, they answer fast ;-)
[06:01] <LaserJock> no, it doesn't like || or &&
[06:02]  * persia retreats from python again, wishing it were slightly less prevalent
[06:02] <LaserJock> persia: why?
[06:03] <LaserJock> Amaranth: actually, I want to do x == y and z != (q or r or s)
[06:03] <x1250> then use -> not in
[06:03] <LaserJock> Amaranth:  so you if x==y and z notin (q,r,s) work?
[06:03] <persia> LaserJock: The syntax is un-C like.  Also, whitespace treatment may require bit-analysis, rather than visual analysis.
[06:04] <LaserJock> persia: C-like syntax is a good thing?
[06:04] <Amaranth> LaserJock: if x == y and not z in (q, r, s)
[06:04] <Amaranth> i think that'll work
[06:04] <x1250> LaserJock: (q or r or s) will return true if anyone of them is true, or whatever value != false and != 0 any of the members would have
[06:04] <x1250> is that what you want?
[06:05] <persia> LaserJock: I think so, but I've been reading C since around the first flight of the Space Shuttle Discovery
[06:05] <LaserJock> x1250: yeah
[06:06] <LaserJock> I want it to work if x == y and z != any of q,r,s
[06:07] <x1250> ("text" or false or true") will be == "text"
[06:07] <x1250> (0 or false or True) will be == True
[06:07] <LaserJock> these conditionals are one thing I just can't get the hang of in Python
[06:07] <x1250> the only case the result is false is when every member is false
[06:08] <LaserJock> sweet, Amaranth's recipe worked
[06:08] <Amaranth> :)
[06:14] <LaserJock> persia: I'm getting somewhere http://laserjock.us/files/ubuntu/buglist.html
[06:15] <persia> LaserJock: That's looking great!  Is it that just approved tasks, or nominations as well?  Also, is it possible to pull the descriptions?
[06:15] <LaserJock> persia: I can pull pretty much anything now that I've hooked into python-launchpad-bugs
[06:16] <LaserJock> persia: those are bugs that are subscribed to by MOTU SRU
[06:16] <LaserJock> I'm working now on how to get a list of tasks that haven't been targeted yet
[06:17] <persia> Interesting.  That list would be the list of things that need review/action by the approval team, and there'd be another list of things that need review / approval by the wider stable developers team?
[06:18] <LaserJock> persia: items that are "Fix Commited" have been accepted into  -proposed and need testing
[06:18] <LaserJock> items that are "Confirmed" are ack'd by the SRU team
[06:19] <LaserJock> maybe I should seperate out those lists
[06:21] <persia> Might be nice to have a few lists: things that need testing, things that need review/approval of the proposed solution, and things that need someone to either prepare a proposed solution, or determine that it doesn't qualify for SRU.
[06:21] <LaserJock> yeah
[06:22] <LaserJock> actually, those are better categorizations than release
[06:22] <LaserJock> I'll put the release as a column
[06:24] <persia> Just out of curiosity, what is the workflow to handle approvals?  To me there seem to be two approval stages: firstly whether a given issue meets the criteria for SRU, and secondly whether a given solution is acceptable for upload, (regression analysis, etc.).  Are both stages handled by the SRU team?
[06:25] <jdong> *cry* car shopping sucks....
[06:25] <persia> The reason I ask is that I wonder if it is possible to generate a list of pending updates that would benefit from someone preparing a patch.
[06:28] <LaserJock> persia: well, first SRU approves the "worthyness" of it and makes sure things are following policy, then it gets uploaded to -proposed (verification-needed tag is added)
[06:28] <LaserJock> then once it's been tested it gets a verification-done tag and gets moved to -updates
[06:29] <persia> Ah, so currently the SRU team determines both whether the bug is suitable for SRU and whether the patch is good at the same time?
[06:29] <LaserJock> basically
[06:29] <LaserJock> we don't do testing per se
[06:29] <LaserJock> but make sure things are being done sanely
[06:29] <persia> Oh, sure, I wouldn't expect testing.
[06:29] <LaserJock> we might say "that's too invasive", etc.
[06:30] <LaserJock> but we expect the contributors and their sponsors to test before upload
[06:31] <persia> So the contributors end up responsible for determining what gets development attention for SRUs?  I'm just thinking it might be awkward for someone to determine that something should be updated, do all the work, and only at the end be advised that they ought have selected a different bug.
[06:31] <LaserJock> well, we like people sub'ing SRU if they thing something should be an SRU
[06:32] <LaserJock> and work with us early on
[06:32] <persia> OK.  So there are two cycles: first an approval for the class of bug, and then for the proposed patch?
[06:32] <LaserJock> sometimes
[06:32] <LaserJock> depends on if the patch is already there
[06:33] <LaserJock> but informally yes
[06:33] <persia> Let's assume it's not.  If there is a patch, it falls back to the case where someone didn't get pre-approval, and may be advised they've wasted their time.
[06:33] <LaserJock> I'll say "looks good, work up the SRU", then once it's ready actually ack it
[06:35] <LaserJock> I think mostly we get to bugs and comment before people get all that far
[06:35] <LaserJock> I can't think of any cases where somebody got all the way to having a ready debdiff and I rejected it
[06:36] <persia> Hmm.  Well then, if it's not broke, no point fixing it :)  I think it still might be nice to have a supplementary list of all tasks nominated or approved for stable releases, but maybe only as a source for contributors to review when selecting candidates to bring to the SRU team.
[06:37] <LaserJock> hmm, yeah. I agree
[06:38] <persia> Might get a little confused with security vs. SRU, but I'd think that would be obvious from the bug description, etc.
[06:43] <LaserJock> perhaps yeah
[06:43] <Amaranth> LaserJock: so was your question so you could do something like   not status in ("Incomplete", "Invalid", "Won't Fix") ?
[06:43] <LaserJock> I wouldn't mind having to go through some false positives
[06:43] <LaserJock> Amaranth: Invalid, Won't Fix, and Fix Released
[06:43] <Amaranth> ah
[06:43] <Amaranth> close enough :)
[06:45] <LucidFox> Does the ALSA device "default" in Hardy correspond to PulseAudio by default?
[06:46] <TheMuso> LucidFox: No.
[06:46] <LucidFox> Is "pulse" present by default, then?
[06:51] <TheMuso> LucidFox: If you install Ubuntu/GNOME, yes.
[06:51] <TheMuso> LucidFox: But it can be disabled.
[06:51] <LucidFox> ah
[06:51] <TheMuso> LucidFox: However when pulse is playing audio, it accesses the audio hardware directly, so alsa apps won't work while pulse plays audio.
[06:51] <LucidFox> yes, I know that
[06:52] <LaserJock> persia: ok, so maybe I'll do two pages. One for potential SRUs and one for the tasks we're actively tracking
[06:52] <LucidFox> I was patching an app that used "plughw:0,0" as the default audio device, and wondered whether to set the default to "default" or "pulse"
[06:52] <persia> LaserJock: That seems sensible to me.  Perhaps for the former, it might make sense to coordinate with SWAT as a common list towards which to point people who want to work on the stable environments.
[06:53] <LaserJock> persia: agreed
[07:10] <TheMuso> LucidFox: default.
[07:47] <geser> good morning
[08:49] <Iulian> G'morning
[09:53] <LucidFox> If I'm going to upload a NEW package from debian-multimedia.org that requires Ubuntu changes, do I need to submit it to REVU?
[09:54] <LucidFox> I can't find mpeg4ip on REVU, for one...
[10:37] <wgrant> LucidFox: Quite old == latest release? Tracking SVN is foolish.
[10:39] <wgrant> We have 1.0rc2 in Hardy, IIRC.
[10:39] <LucidFox> yes
[10:39] <wgrant> They say 1.0rc1 is old.
[10:44] <LucidFox> Well, smplayer uses some features that aren't even in rc2 - I'll ask upstream which exactly
[10:45] <wgrant> If mplayer actually made any vaguely useful releases..
[10:49] <LucidFox> also, how about shipping mplayer in Ubuntu with the compiz xv patch?
[10:50] <LucidFox> the one that enables use of the compiz video output plugin
[10:50] <wgrant> LucidFox: Wasn't that patch rejected violently by upstream?
[10:50] <wgrant> Or is there another one which is blessed?
[10:52] <LucidFox> hmm, this was proposed as bug #121476
[10:54] <LucidFox> there was a new version of the patch posted after it was closed as Won't Fix, though
[10:55] <wgrant> Doesn't Xv work in Compiz on most cards these days?
[10:55] <wgrant> Even textured video should work on Intel soon, at list.
[10:55] <wgrant> *at least
[10:55] <LucidFox> hmm
[10:55] <LucidFox> "There is an unofficial patch for mplayer/compiz (it'll never be official, it's more like a temporary and dirty hack)"
[10:55] <LucidFox> looks like that answers it
[10:55] <wgrant> Yes.
[10:58] <Laney> Is there a fix/workaround for the pbuilder libc6 issue yet?
[11:18] <RAOF> LucidFox: The compiz 'video' plugin is in some sort of perpetual limbo.  Davidr consistently threatens to do it again, correctly.  So nothing supports it, because it's kinda temporary.
[11:19] <RAOF> Also, debhelper 7 is whack.
[11:19] <persia> RAOF: Please define "whack"
[11:20] <RAOF> Two line debian/rules kinda whack.
[11:20] <RAOF> Like CDBS, but it seems that doing advanced stuff doesn't require sacrifices to the four dark gods of chaos.
[11:21] <persia> Simple.  Concise.  Readable.  Says "Nothing to see here.  Please move on." to people, and they look at the useful files.  Fewer irregular debian/rules hacks.
[11:21] <RAOF> Yeah.  Whack is not necessarily indicative of disapproval.
[11:23] <RAOF> I'm just packaging Do for debian, and playing with dh and cli-common-dev 0.5.7.
[11:35]  * Hobbsee waves
[11:42] <geser> Hi Hobbsee
[12:27] <bardyr> what benefits does packaging programs as perl5.8, perl5.10 and making other packages depend on them instead of a meta package for perl and depends on the perl5.8 like the linux-image packages
[12:28] <mok0> bardyr: I am not a perl programmer, but I assume that new features were introduced in 5.10
[12:29] <mok0> another package making use of those features needs to depend on 5.10
[12:30] <bardyr> mok0, but then special packages can depend on certain version of perl
[12:30] <mok0> bardyr: yes
[12:30] <bardyr> mok0, im on intrepid and trying to install some perl depended programs but they all depend on 5.8 but its gone
[12:31] <bardyr> now i need to manually change dependencies to 5.10 :/
[12:31] <Hobbsee> which means they need to be updated, which may well require code changes
[12:31] <Hobbsee> or removed.
[12:31] <mok0> bardyr: or just >= 5.8
[12:32] <bardyr> mok0, it has that, but it points to perl5.8 and it has been replaced with perl5.10
[12:34] <mok0> bardyr: there may be a virtual package perl, that depends on the "current" perl version for any given distribution
[13:24] <pochu> Do FTBFS bugs have a whitelist from motu-sru?
[13:26] <sistpoty> hi folks
[13:26] <geser> Hi sistpoty
[13:26] <sistpoty> hi geser
[13:27]  * sistpoty merges ghc6... just trying to rebuild itself with the merged version
[13:29] <LucidFox> Anyone want any REVU packages reviewed?
[13:58] <slicer> Hm. Is there a way to get PPA to build the same source package for both hardy and gutsy?
[13:59] <rexbron> slicer: Look at the copy package option
[14:01] <slicer> rexbron: Ah, I must be blind :) Thank you.
[14:06] <rexbron> slicer: np
[14:08] <sebner> is there a difference between debhelper (>> 5) and debhelper (>> 5.0.0) ?
[14:09] <rexbron> sebner: I would guess that >>5.0.0 would be satisfied by 5.0.1 while >>5 would not
[14:09] <Hobbsee> sarah@saturn:~% dpkg --compare-versions 5 lt 5.0.0 && echo true         11:09PM
[14:09] <Hobbsee> true
[14:09] <Hobbsee> interesting
[14:10] <Hobbsee> sarah@saturn:~% dpkg --compare-versions 5 lt 5.0.1 && echo true         11:09PM
[14:10] <Hobbsee> true
[14:10] <Hobbsee> rexbron: both should be satisfied.
[14:10] <Hobbsee> sebner: i don't really think so - there's no number in between 5 and 5.0.0 except for 5.0
[14:10] <Hobbsee> which all equates to the same thing, in real version #'s, anyway
[14:10] <sebner> Hobbsee: cool. thanks :)
[14:13] <Mez> wow. the debian NM process is complex
[14:21] <bddebian> Heya gang
[14:23] <sistpoty> hi bddebian
[14:23] <emgent> heya :D
[14:24] <bddebian> Hi sistpoty, emgent
[14:31] <LucidFox> Hmm
[14:31] <LucidFox> In the orig.tar.gz for cairo-dock on REVU, various automake files in the root are symlinks to files in /usr/share/automake-1.10
[14:32] <LucidFox> is this allowed?
[14:34] <sistpoty> LucidFox: hm... looks like a mistake from upstream to me, though (if it b-d on automake 1.10 it imho is ok *packaging* wise)
[14:34] <sistpoty> LucidFox: if it's gpl (or lgpl) however, the license file must not be a symlink though
[14:35] <LucidFox> it isn't - only config.guess, depcomp, install-sh, all that stuff
[14:36] <sistpoty> ok... packaging wise I guess it's ok, but the packager should really ask upstream to fix that (as it defeats the purpose of autoconf/automake actually)
[14:38] <sistpoty> anyone know if intrepid is currently safe? or are there any big issues?
[14:38] <sistpoty> (as I'm pondering dist-upgrading)
[14:42] <wgrant> sistpoty: libxfonts1 is broken.
[14:42] <wgrant> But downgrading that gets things working again, I believe.
[14:43] <geser> sistpoty: I've only a intrepid chroot for working on packages and a intrepid pbuilder. Both doesn't seem to be broken right now.
[14:52] <sistpoty> hm... apt tries to remove quite a bunch of important packages from me... (e.g. dia, exim4-daemon-heavy, svn-buildpackage)...
[14:52] <sistpoty> and kvirc! *g*
[14:53] <sistpoty> oh... apt changes the behaviour when puring old packages... strange
[14:53] <sistpoty> purging even
[14:54] <geser> my intrepid chroot is only minimal (enough to work on packages). I'll upgrade my main system to intrepid around the first or second alpha.
[14:55] <geser> what did change during purging=
[14:55] <geser> ?
[14:55] <sistpoty> geser: I'm entirely unsure actuallly... I've thought the packages I purged were entirely unrelated
[14:55] <sistpoty> geser: it changed from removing many packages to hold back a bunch of others
[14:56] <sistpoty> however I don't see a pattern yet for apt doing so
[14:57] <sistpoty> and now it upgraded some packages while purging only other ones... *strange*
[15:02] <geser> may it be related to recommends?
[15:04] <sistpoty> do we have recommends by default now?
[15:05] <sistpoty> hm... there's at least nothing in apt-cache -i unmet for e.g. kvirc or exim *shrug*
[15:10] <geser> sistpoty: "* enable installation of recommends by default" [from the changelog entry for apt (0.7.14ubuntu1)]
[15:12] <sebner> sistpoty: don't hestiate to upgrade. it's never false to get rid of this kde stuff ^^ ;P
[15:14] <sistpoty> geser: ah, thanks
[15:14] <sistpoty> sebner: :P
[15:16] <geser> sebner: luckily kernel-image got renamed to linux-image so you can do now: "apt-get --purge remove k*" :)
[15:17] <sebner> geser: hrhr :)
[15:22]  * sistpoty is bold and dist-upgrades *g*
[15:30] <sistpoty> bug #228997 reported
[15:35] <sebner> sistpoty: nice comments xD
[15:36] <sistpoty> hm... I'm still puzzled. maybe the difference is that apt-get install will do an apt-get upgrade (vs. apt-get dist-upgrade) under the hood?
[15:59] <geser> as sistpoty isn't swearing, either the upgrade went fine, or is still in progress or sistpoty is fighting to bring his box back to life :)
[15:59]  * sistpoty is still upgrading (replacing packages right now)
[16:06] <penper> hi! I have a python app that depends on python-pygame. My app just contains python files with nothing to compile. Can anyone point me to the easiest way to make a .deb with my python files and the pygame dependency? Thanks :)
[16:07] <pochu> penper: https://wiki.ubuntu.com/PackagingGuide/Python
[16:07] <pochu> penper: that should guide you into making a deb package for a Python application
[16:08] <penper> pochu: perfect! Thanks
[16:30] <sebner> pochu: wow. really great work by Michael Gliwinski for putting your session on the wiki page.
[16:33] <pochu> yeah he did a nice work
[16:34] <LucidFox> Holy...!
[16:34] <LucidFox> dh_make was updated just yesterday!
[16:35] <sebner> LucidFox: that means?
[16:35] <LucidFox> well... it's been long time since the last update
[16:37] <sebner> ah. k
[16:37] <RainCT_> lol
[16:46] <LucidFox> It's somewhat ironic that dh_make only updated to debhelper 6 after debhelper 7 was released
[16:52]  * sistpoty is off again... cya
[16:56] <stgraber> btw, if some of you have some spare time can they have a look at : http://revu.tauware.de/details.py?package=emu8051
[16:57] <stgraber> Pierre Ferrari is one of my teachers, trying to learn packaging. It looks good to me but as I only do some packaging updates nowadays I probably missed a lot of things :)
[16:59] <geser> stgraber: I've only looked at the diff.gz yet, and at first I only see a very minor issue: move the Homepage field to the source stanza in debian/control
[17:02] <geser> stgraber: and the link to the GPL in debian/copyright should point to GPL-2 as GPL is a symlink to GPL-3
[17:05] <stgraber> geser: ah, right code is not GPL2 and higher. Thanks
[17:12] <LucidFox> stgraber, geser> I also have doubts about Section: x11
[17:13] <LucidFox> to be fair, the Debian section conventions are far from clear
[17:16] <geser> LucidFox: as I can't find a better section and it has a gui, it could stay in x11
[17:16] <LucidFox> makes sense to me
[17:17] <LucidFox> Holy cow... someone submitted a 9.1 MB debdiff for a new upstream release, including upstream changes
[17:17] <LucidFox> uncompressed to boot
[17:18] <LucidFox> actually... two people did it
[17:25] <LucidFox> sebner, congratulations!
[17:25] <sebner> LucidFox: ah.. thanks ^^
[17:26] <geser> sebner: congrats
[17:26] <sebner> geser: thanks. :) ehm yes, you made it possible ^^
[17:30] <LucidFox> I feel a little lost here, to be frank
[17:31] <LucidFox> universe-contributors is a recently created team, how is it different from MOTU?
[17:31] <sebner> LucidFox: I have no upload right ;)
[17:32] <geser> LucidFox: universe-contributors is like ubuntu-members but you don't have to go the CC but to the MC
[17:33] <geser> LucidFox: it grants ubuntu membership and is a step towards MOTU
[17:33]  * persia notes that it's possible to be MOTU without being a universe-contributor, but most people will likely reach the threshold for universe-contributor before reaching the threshold for MOTU (lower technical requirements, same community requirements)
[17:34] <LucidFox> ah
[17:36] <LucidFox> oh, hello blueyed_
[17:39] <no0tic> I reported a bug on kid3 debian package to add dh_icons on debian/rules and the mantainer forcibly merged this bug to an unsolved previous one (156 days old). Is this a sign she won't fix it again? Can we proceed with the merge?
[17:40] <no0tic> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480246
[17:40] <no0tic> merged to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454526
[17:42] <coppro> there's a typo on a REVU page
[17:43] <coppro> "Please consider  submitting your package to Debian as well. The Utnubu team would be more than happy to help you to get started. "
[17:43] <coppro> or is that intentional?
[17:43] <jdavies> coppro: Utnubu is a team
[17:43] <coppro> ok
[17:44] <jdavies> coppro: it's focused on getting Ubuntu packages into Debian
[17:44] <LucidFox> coppro> A largely defunct one, really
[17:45] <pochu> sebner: congrats :)
[17:45] <LucidFox> If you can't find a sponsor otherwise, I suggest pitching packages to the Debian team that's involved in similar packages
[17:46] <sebner> pochu: also thanks to you :)
[17:46] <jdavies> sebner: congrats!
[17:46]  * RoAkSoAx hi all
[17:46] <sebner> jdavies: thanks ^^
[17:47] <RoAkSoAx> sebner, congrats too (what for? hehexD :P)
[17:47] <sebner> RoAkSoAx: xD. You remind me of me when I started contributing ^^
[17:48] <RoAkSoAx> sebner, looool
[17:48] <warp10> hey sebner, congrats! ;)
[17:49] <sebner> warp10: thanks. But I'm now contributing member and not president of the USA ^
[17:49] <slytherin> geser: Do you have time to take a look at merge for lucene2?
[17:49] <LucidFox> Where can I find debhelper 7 documentation? Other than "man dh" :)
[17:49] <warp10> sebner: How knows, maybe a day you will be the first MOTU-president...! :P
[17:49] <sebner> warp10: hrhr
[17:50] <LucidFox> also... why do I see so many debdiffs uploaded as text/html? (including yours, slytherin)
[17:50] <slytherin> LucidFox: I am filing a bug report about it right now. :-)
[17:51] <LucidFox> heh
[17:52]  * LucidFox can't wait for openjdk-6 to get into Debian finally
[17:52] <geser> slytherin: sure
[17:54] <slytherin> geser: As LucidFox has already mentioned, debdiff is shown in html format.:-( You will need to wget it.
[17:54] <slytherin> LucidFox: https://bugs.edge.launchpad.net/launchpad/+bug/229040
[17:54] <geser> sebner: if you would told me two years ago, I will be a part of the MC I wouldn't believe you. Let's recheck in two years again.
[17:55] <geser> slytherin: I've changed the filetype of your debdiff from text/html to text/plain so I can review it in firefox
[17:55] <slytherin> geser: where did you find that option?
[17:56] <slytherin> ahh, in edit attachment
[17:56] <geser> exactly
[17:56] <Laney> I'm doing a merge, some of the previous Ubuntu patches just modified the source directly. Is it worth me refactoring these to use cdbs or similar, or should I just leave them?
[17:57] <geser> Laney: does the package use a patch management system (dpatch, quilt, etc)?
[17:57] <Laney> geser: No, there is no debian/patches or anything
[17:58] <Laney> Actually, the Debian patches do it too. I guess it's not worth it, eh?
[17:59] <geser> then leave them as they are as adding a patch system would increase the Ubuntu delta even more (unless there a many and/or big patches)
[17:59] <Laney> geser: Right then, cheers
[18:00] <slytherin> what does this error mean - debian/rules:16: *** target file `build-indep' has both : and :: entries.  Stop.
[18:01] <pochu> slytherin: I think that's because you added a 'clean:' target and included a CDBS include which has 'clean::', so if that's the case, change your 'clean:' to 'clean::'
[18:01] <geser> slytherin: re lucene2: why got the patches 80 and 81 removed from 00list?
[18:02] <pochu> slytherin: err, the same but 's/clean/build-indep/g'
[18:02] <slytherin> geser: they were removed on debian side.
[18:02] <slytherin> pochu: thanks. There is a debhelper include which is not needed.
[18:07] <sebner> geser: hmmm?
[18:12] <geser> slytherin: debian/patches/00list from the unmodified Debian package lists 80_prevent-downloading-data-files.dpatch and 81_prevent-network-access.dpatch
[18:13] <slytherin> geser: let me take a look
[18:13] <geser> slytherin: but these are different patches as the patches from the old Debian package with the number 80 and 81
[18:15] <slytherin> geser: Oh, Wait. These patches were included in Debian as fix for FTBFS. Remember 'no-internet-access-on-buildd' problem? We fixed it in different way.
[18:15] <geser> ah, ok then
[18:17] <NorthernLights> Hello all
[18:18] <geser> slytherin: does the DTD fix replace also patch 80 (prevent downloading data files) or only patch 81?
[18:18] <NorthernLights> Would someone have a look at my package "gtkvncviewer" on REVU? Its Debian version has been accepted by Debian mentors, so I believe it's not bad.
[18:18] <slytherin> geser: both. we patch the unit test to use local DTD.
[18:21] <geser> slytherin: please document it better the next time you merge this package, that the ubuntu patch replaces the other two patches
[18:22] <slytherin> geser: Can you please wait. Looks like patch 80 should not be dropped. My bad. :-(
[18:25] <geser> slytherin: so I should readd patch 80 again?
[18:26] <geser> slytherin: no need to create a new debdiff just for that
[18:26] <slytherin> geser: Yes, if that is not much trouble to you. Otherwise I will add it and document things properly
[18:27] <geser> slytherin: no problem. it's probably easier than to start from fresh
[18:30] <NorthernLights> Bye all
[18:37] <ScottK> sebner: Congratulations.
[18:37] <slytherin> geser: I have reverted that changed and documented why patch 81 was removed. Should I delete old debdiff and upload new one or simply upload new one?
[18:37] <sebner> ScottK: oh. thanks :) Just hoping that I won't be thrown out of the team after the courier merge ^^
[18:38] <RoAkSoAx> sebner, lol... now i know.. you've been the first accepted as a u-u-c member
[18:39] <sebner> RoAkSoAx: exactly :)
[18:39] <no0tic> ScottK, did you follow the kid3 merging adventure two days ago?
[18:39] <ScottK> no0tic: No.  I've been offline the last few days.
[18:39] <RoAkSoAx> sebner, congrats then ;)
[18:39] <sebner> RoAkSoAx: thanks thanks ^^
[18:40] <no0tic> ScottK, may I bother you anyway? :)
[18:40] <ember> is there a simple way with debhelper to install a debian/desktop and debian/desktop.png or i have to link in install?
[18:40] <ScottK> no0tic: You can ask.  Not sure I'll have time to answer.
[18:40] <ember> congrats sebner !
[18:40] <sebner> ember: also thanks to you
[18:41] <ScottK> ember: Isn't there a dh_desktop for that.
[18:41] <no0tic> ScottK, I reported a bug on kid3 debian package to add dh_icons on debian/rules and the mantainer forcibly merged this bug to an unsolved previous one (156 days old) reported by DarkSun88 during hardy merging. Is this a sign she won't fix it again? Can we proceed with the merge?
[18:41] <slytherin> Can someone point me to some page that explains you-you-c?
[18:41] <ember> ScottK yeah that registers the .desktop file
[18:41] <ember> and the png i link it on .install right?
[18:42] <ScottK> no0tic: What bug?
[18:42] <sebner> slytherin: https://wiki.ubuntu.com/UbuntuDevelopers
[18:42] <RoAkSoAx> slytherin, https://launchpad.net/~universe-contributors
[18:42] <ScottK> Note that dh_icons is still somewhat controversial in Debian.  Some DDs favor the idea and some don't.
[18:42] <no0tic> ScottK, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480246 was merged to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454526
[18:43] <ScottK> no0tic:
[18:43] <ScottK> no0tic: Looking
[18:43] <slytherin> sebner: RoAkSoAx: thanks
[18:44] <ScottK> no0tic: Yes.  I'd say go ahead.
[18:44] <geser> slytherin: like you want
[18:44] <ScottK> no0tic: I don't think you needed to file your bug as it appears essentially the same as the existing bug.
[18:45] <slytherin> geser: I will simply upload the new one so you can compare it with old one if you want.
[18:46] <no0tic> ScottK, ok, I'll file the merge wishlist bug on LP, thanks a lot
[18:47] <ScottK> no0tic: No problem.  Thanks for contributing and working to get Debian and Ubuntu in better sync.
[18:50] <sebner> ScottK: already looked at courier?
[18:51] <ScottK> sebner: I have not.  I just got back from being out of town.  I'll probably look at it tonight (I'm at -0400).
[18:52] <sebner> ScottK: ah ok. sry
[18:52] <ScottK> sebner: No problem.
[19:19] <no0tic> since kid3 turned out to be a merge and not a sync I set this bug https://bugs.launchpad.net/bugs/227405 to invalid, is it ok?
[19:22] <slytherin> geser: Done. Uploaded new debdiff.
[19:30] <geser> slytherin: Uploaded.
[19:32] <ScottK> no0tic: Just edit that bug to be a merge bug.  No need to start a new one.
[19:33] <no0tic> ScottK, I hope not to miss another merge, but if it will happen I'll do that way
[19:33] <ScottK> no0tic: OK.
[19:37] <nxvl> is there something like an upload count?
[19:47] <slytherin> geser: Thanks. And since you have ack'ed my previous sync bugs, I would be glad if you also did it fro tomcat5.5 :-D
[20:39] <sommer> geser: I was looking at merging bioperl and noticed you were the merge-o-matic, just wondering if it's cool if I take a crack at merging it?
[20:56] <sebner> huhu no0tic
[20:56] <sebner> huhu norsetto
[20:56] <norsetto> err, yes, huhu 2u2 sebner
[20:56] <sebner> ^^
[20:58] <norsetto> sebner: so you made it eh? Bribing the MC with home-made sauchertorte proved to be a worthy tactic after all
[20:59] <sebner> norsetto: hrhr. psst! don't reveal my top secret success plan ;)
[20:59]  * norsetto didn't realise he wasn't quering :-O
[21:00] <sebner> norsetto: xD xD xD
[21:01] <sebner> norsetto: btw, filed the flightgear bug and reported the changes to debian. We'll see what happenes :)
[21:02] <norsetto> sebner: I'm eagerly awaiting
[21:03] <sebner> norsetto: ^^, why?
[21:03] <norsetto> sebner: "We'll see what happenes :)"
[21:04] <sebner> norsetto: well, if they accept our changes or not
[21:04] <norsetto> sebner: yes, thats why I said that I'm curious to see it too
[21:05] <sebner> norsetto: I thought that was just a joke because you are working on a lot of other packages ^^
[21:05] <norsetto> sebner: do you think this guy (bug 228976) is upset?
[21:06] <sebner> norsetto: STILL, maybe a little bit =)
[21:06] <norsetto> sebner: but we are very nice guys, so we will ask debian to update it to 0.60 (supposing the DM is still alive)
[21:07] <sebner> norsetto: 0.6 fixes it? Not worth a SRU or? We are very nice guys, indeed ^^
[21:08] <norsetto> sebner: there are very high chances it will, the version right now in hardy is from beg. 2006
[21:08] <sebner> norsetto: I see. bug 206862
[21:09] <norsetto> sebner: if it works in intrepid, we could backport it, but first we need to check
[21:09] <crimsun> hmm, unstable still has 0.50-1
[21:09] <sebner> norsetto: yep. do you want me to file a bug in debian BTS?
[21:10] <norsetto> sebner: why not, check if there isn't one already, and if you really feel nice you can try to upgrade it yourself in the meantime, it will be a good exercise for you
[21:11] <sebner> norsetto: well then I have to be pretty quickly. Today is the last the I will work for ubuntu for at least for one week. You know. final exams :)
[21:11] <norsetto> sebner: there is a bug alreday btw: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446530
[21:11] <norsetto> alreday !?
[21:12] <sebner> norsetto: pretty old :\ what already?
[21:13] <sebner> sistpoty: thanks for the nice comment ^^
[21:14] <norsetto> sebner: if this is true (bug 225362) this could be easily solved
[21:15] <sebner> norsetto: sry. doesn't understand what you mean now
[21:15] <norsetto> sebner: check last comment of bug 225362
[21:15] <geser> sommer: afaik nobody claimed it already, so you can have it
[21:16] <sebner> norsetto: launcher = .desktop file?
[21:17] <sommer> geser: cool thanks, do I need to file a merge bug as mentioned here: https://wiki.ubuntu.com/UbuntuDevelopment/Merging ?
[21:17] <norsetto> sebner: yes, but I wonder if this could not be solved via configure/rules
[21:18] <sebner> norsetto: good question
[21:18] <sommer> geser: nm, since I'm not the previous maintainer I do :)
[21:21] <norsetto> sebner: looks like this is hardcoded as /etc/sensors.conf
[21:22] <sebner> norsetto: possible solution? just curious because I'm just doing a merge and then bye bye ubuntu for one week :)
[21:22]  * sistpoty ponders if haskell-utils is safe to merge... as it will be quite rigid in regards to version numbers
[21:23]  * sistpoty decides to at least wait for ghc6 being built :)
[21:27] <norsetto> sebner: that last comment seems to be an hoax ....
[21:28] <sebner> norsetto: -.- If you can wait for one week I'll try to update it
[21:34] <sebner> sistpoty: intrepid up and running?
[21:36] <sistpoty> sebner: partly... bug #229079 and bug #229016 still prevent me from a full upgrade
[21:37] <sebner> sistpoty: what about upgrading excluding these two?
[21:37]  * norsetto still has not updated to hardy even
[21:37] <sebner> norsetto: good. it's not that stable ^^
[21:37] <sistpoty> sebner: might be an idea
[21:37] <sebner> sistpoty: at least this is my plan ^^
[21:38] <sistpoty> (though I'm partially at new versions already *g*)
[21:38] <sistpoty> sebner: also check, what apt will remove (the bug with the funny comments) ;)
[21:39] <sebner> sistpoty: yeah I know ^^. I also upgraded partly. It took me 10 minutes to realize that debuild is complaining that dh_clean can't be done because it need debhelper 7 whats only in intrepid -.-
[21:48] <norsetto> RainCT_: are you working on bug 225362 too? (meaning, is it the same as bug 206280)
[21:54]  * norsetto is now entering maintenance-mode
[21:54] <gnomefreak> norsetto: its the weekend monday == maintainance-mode :)
[21:55] <norsetto> gnomefreak: I'm synced with LP unfortunately
[21:55] <laga> it's saturday night, some geeks are trying to get something done ;)
[21:55] <gnomefreak> norsetto: sorry to hear that
[21:55] <sistpoty> laga: :P
[21:56] <norsetto> gnomefreak: not as much as I'm ;-)
[21:57] <gnomefreak> norsetto: i forgot LP was going down :(
[21:58] <tbielawa> you all ever get the error where pdebuild will fail at: debsign: Can't find or can't read changes file /var/cache/pbuilder/result//bibus_1.4.2-1ubuntu1_amd64.changes!
[21:58] <tbielawa> except, insert your package name there.
[21:59] <gnomefreak> are PPA repos affected by LP gown down?
[22:00] <LaserJock> gnomefreak: I would think the actual repos would be still up
[22:00] <LaserJock> but you won't be able to do soyuz bits
[22:00] <gnomefreak> LaserJock: thanks i was thinking that too but its db update
[22:00] <LaserJock> sure, but the archive is the archive
[22:01] <LaserJock> it should be technically independent of LP
[22:01] <sistpoty> LaserJock: so I'll be able to attach a debdiff? *g*
[22:01] <gnomefreak> thanks LaserJock :)
[22:01] <LaserJock> gnomefreak: I don't know for sure, we can try it :-)
[22:02] <gnomefreak> LaserJock: ill test as soon as i know for sure its down
[22:02] <gnomefreak> as of this moment they are working
[22:02] <LaserJock> LP is down right now for me
[22:02] <gnomefreak> ok PPA are working than
[22:03] <gnomefreak> yay libc6 updates
[22:03] <gnomefreak> maybe i will be going down with LP ;)
[22:03] <sebner> LaserJock: yeah, they are updating it. And I was currently filing a bug -.-
[22:05] <LaserJock> darn, that'll mean I can't work on my SRU script :(
[22:05] <sebner> LaserJock: btw, gnustep maintainers answered and it's a sync now ;) But they also told me that they maybe remove edemapp because of troubles with gnustep upgrades
[22:07] <LaserJock> sebner: awesome, good work
[22:07] <sebner> LaserJock: yeah fine that's a sync now but not that good if they remove it ^^
[22:10] <LaserJock> either way really
[22:10] <LaserJock> I doubt much of anybody uses it
[22:10] <LaserJock> so if it's time to get rid of it then it's better overall for us
[22:11] <sebner> LaserJock: ok :)
[22:11] <RainCT_> norsetto: I got a fix ready for Hardy but nobody uploaded it
[22:12] <RainCT_> norsetto: (lm-sensors is in main)
[22:12] <norsetto> RainCT_: yes, main is ... main
[22:12] <norsetto> RainCT_: so the new libsensors doesn't replace the old one
[22:13] <norsetto> RainCT_: I have bot sensor.conf and sensor3.conf in my hardy chroot, I guess thats because I upgraded
[22:15] <RainCT_> yes, I think the config file name changed
[22:15] <tbielawa> LaserJock: i got a version of bibus up on revu. looks like I fixed it making a native package this time
[22:15] <RainCT_> (I don't know the program, thought; actually I don't even remember what it is for :P)
[22:15] <LaserJock> tbielawa: ah excellent
[22:16] <tbielawa> LaserJock: it's summer break, time for the ubuntu hackery to begin
[22:16] <geser> tbielawa: good to hear that you managed to build a non-native package
[22:17] <tbielawa> i guess changing a - to an _ changes a lot with debuild
[22:17]  * gnomefreak is missing something :( LP going down made wiki go down?
[22:18] <gnomefreak> damn
[22:18] <gnomefreak> i cant paste it
[22:18] <LaserJock> tbielawa: with Launchpad down I know what I can do with my time ;-)
[22:18] <tbielawa> LaserJock: w00t
[22:19] <gnomefreak> it says The authentication database is temporarily unavailable. Anonymous access only.
[22:19] <LaserJock> gnomefreak: yeah, wiki is authenticated via Launchpad
[22:19] <gnomefreak> LaserJock: thanks
[22:20] <sistpoty> hm... anyone with upload rights for main around, who'd like to sponsor me two packages?
[22:21] <sistpoty> (I can post debdiffs on a site that will work :P)
[22:21] <LaserJock> sistpoty: you're not Cre Dev?
[22:21] <LaserJock> *Core
[22:22] <sistpoty> LaserJock: no, I'm interested mainly in universe... so no reason for me to go for core-dev
[22:22] <sistpoty> (unless a package in main is fubar)
[22:23] <LaserJock> huh, I thought you'd been a core dev forever
[22:23] <LaserJock> sistpoty: what packages?
[22:23] <sistpoty> LaserJock: I also didn't go for core-dev when being on MC, since I was the only motu back then (and I think MC back then should have been mainly for motus)
[22:24] <sistpoty> LaserJock: system-config-printer and system-config-printer-kde
[22:24] <LaserJock> sistpoty: make sense
[22:25] <LaserJock> I'm both MOTU and Core-Dev, I don't feel like it has to be one or the other
[22:25] <norsetto> hmmmm, can you be a core-dev and not a MOTU?
[22:25] <LaserJock> norsetto: not technically, but socially very much so
[22:26] <norsetto> LaserJock: we love you even if you are a core-dev ;-)
[22:26] <LaserJock> hah
[22:26] <tbielawa> *hug to LaserJock*
[22:26] <sistpoty> hm... I at least couldn't describe *why* I'd be a core-dev... fixing up the bad things in main that are left behind doesn't make a good impression for an application imho :P
[22:26] <norsetto> sistpoty: lol
[22:27] <LaserJock> sistpoty: oh, I don't know
[22:27] <LaserJock> sistpoty: well, get me debdiffs and I'll have a look
[22:27] <LaserJock> I'm upgrading my intrepid chroot now
[22:29] <geser> it depends if you count the indirect membership of ~ubuntu-core-dev in ~motu as being MOTU or not
[22:30] <sistpoty> LaserJock: thanks... first one is http://www.potyra.de/s-c-p-kde.debdiff
[22:30] <LaserJock> geser: isn't the relationship via ~ubuntu-dev ?
[22:31] <sistpoty> LaserJock: second one is http://www.potyra.de/s-c-p.debdiff
[22:33] <sistpoty> (I didn't report the remaining lintian warnings about system-config-printer yet, before lp went down)
[22:35] <geser> LaserJock: I don't remember exactly and can't currently look it up but you could be right
[22:36] <sistpoty> geser, LaserJock: afair it's core-dev -> ubuntu-dev and motu -> ubuntu-dev
[22:36] <LaserJock> yeah, I think that's how it is
[22:37] <LaserJock> so core-dev can upload to Main and ubuntu-dev to Universe
[22:37] <sistpoty> yes
[22:38] <norsetto> oh $DEITY, I don't believe this
[22:38] <geser> so it's even technically possible to be core-dev but not MOTU (if MOTU == member of ~motu)
[22:38] <sistpoty> geser: fwiw, yes
[22:39] <sistpoty> (and iirc not only technically)
[22:39] <norsetto> anyone that can spot whats wrong with the output of "apt-cache show gtkgo" wins a hug
[22:40] <geser> norsetto: don't forget to "export DEITY=bddebian" :)
[22:40] <sistpoty> heh
[22:40] <norsetto> geser: thx for reminding me!
[22:40] <sebner> norsetto: package doesn't exist ;)
[22:40] <norsetto> sebner: nope
[22:41] <sebner> norsetto: I want my hug! ^^
[22:41] <geser> norsetto: the maintainer address
[22:41]  * norsetto hugs geser
[22:41] <LaserJock> hah
[22:41] <LaserJock> funny
[22:41] <sebner> wth?
[22:41] <norsetto> geser: the fastest eyes in #ubuntu-motu :-)
[22:41] <sebner> can somebody explain that to me?
[22:42] <LaserJock> I'm surprised we don't have more of those
[22:42] <LaserJock> sebner: explain what?
[22:42] <norsetto> sebner: check the maintainer line
[22:42] <sebner> norsetto: ?? http://pastebin.com/m429b63d
[22:43] <LaserJock> odd
[22:43] <norsetto> sebner: yes, its amd64 only
[22:43] <sebner> grml
[22:43] <sebner> norsetto: unfair. Not possible for me to win a hug -.-
[22:43]  * norsetto hugs sebner
[22:44] <sebner> hihi
[22:44]  * sebner hugs norsetto back =)
[22:44] <sistpoty> oh, norsetto: do we need to revisit gfortran dependant packages for intrepid, or will everything work fine with gfortran 4.2 -> 4.3?
[22:44] <norsetto> I owed you one anyhow to congratulate you on your membership :-)
[22:44] <geser> gtkgo | 0.0.10-15ubuntu3 | hardy/universe | source, amd64, i386
[22:45] <sebner> norsetto: hehe. true :)
[22:45] <LaserJock> I saw it and I'm on i386
[22:45] <sebner> geser: hmm. so wth?
[22:45] <norsetto> ah ....
[22:45] <geser> sebner: did you forget to enable universe?
[22:45] <LaserJock> sebner: you're special :-)
[22:45] <sistpoty> (austrian mirros are behind at least one release :P)
[22:46] <sebner> geser: I'm a universe-contributor xD
[22:46] <sebner> LaserJock: I use them main servers ;)
[22:46] <norsetto> sistpoty: it should be ok, my only concern was with R but we only had two packages to merge and I made sure they were built after R was built
[22:46] <sebner> And I br0ke my sources.list ^^
[22:46] <sebner> no
[22:46] <sebner> everything enabled
[22:46] <sebner> :\
[22:46] <sistpoty> norsetto: cool, thanks! :)
[22:47] <sistpoty> norsetto: you also took care of the package I still couldn't verify from hardy-proposed?
[22:47] <norsetto> sistpoty: to be sure, I have anyhow some syncs I'm waiting to request so that they are built with the new blas/lapack
[22:47] <norsetto> sistpoty: libittp?
[22:48] <norsetto> sistpoty: or libitpp, can never remember
[22:48] <sistpoty> norsetto: yes
[22:48] <sistpoty> norsetto: neither can I ;)
[22:48] <norsetto> sistpoty: AFAIK, its still in proposed
[22:48] <sebner> norsetto:  <ubunto-motu@lists.ubuntu.com>
[22:48] <sebner>   <.---- lol
[22:48] <sistpoty> norsetto: but what about intrepid?
[22:49] <norsetto> sistpoty: that should be autosynced
[22:49]  * norsetto checks
[22:49] <sistpoty> norsetto: ah, excellent! :)
[22:49] <norsetto> sistpoty: yes, its autosynced
[22:49] <sistpoty> :)
[22:50] <norsetto> sistpoty: btw, we should really push that to hardy, its a rebuild, and all the tests run during build are fine
[22:51] <sistpoty> norsetto: hm... I think it's definitely worthwhile, but I cannot figure what is broken with the old version :/....
[22:52] <sistpoty> norsetto: maybe compile some fortran packages against it? (which I guess is out of my scope, since I just can't figure fortran)
[22:52] <sistpoty> (linked against it even)
[22:52] <norsetto> sistpoty: tried that, but short of looking at the API and do some stupid program which is anyhow much simpler than any of the test which are run during build seems hopeless
[22:53] <sebner> LP is running again. wuhu
[22:53] <geser> LP is back
[22:53] <sebner> geser: faster :P
[22:53] <sistpoty> norsetto: it would prove the point that the old version needs to be replaced afair (since iirc you cannot link to libgfortran2 and s.th. else at the same time)
[22:54] <sistpoty> norsetto: if you can attach s.th. like this to the bug, I'd be very happy to pick it up and check what's going on (or try to modify it so that the hardy package breaks)
[22:57] <LaserJock> grr, sbuild isn't likingn me
[22:58] <LaserJock> hmm, maybe it's the problem pitti was talking about
[22:58] <LaserJock> it complains that it can't find fakeroot
[22:59] <norsetto> sistpoty: you have a point actually, why should the current libitpp in hardy not work!?
[23:02] <sistpoty> norsetto: my believe is that it won't work, if you compile a fortran program against it... maybe. maybe it does work, that's what I'd like to find out
[23:02] <norsetto> sistpoty: I don't see why it shouldn't work
[23:03] <sistpoty> norsetto: oh, then I guess we can leave hardy as is? or what do you think?
[23:03] <norsetto> sistpoty: well, the idea was to complete the transitionm, its just not clean but I think it should be perfectly workable
[23:04] <sistpoty> :)
[23:06] <norsetto> sistpoty: its just funny to leave the bug thats started it all as the only one that was not fixed :-\
[23:06] <RainCT_> good night
[23:06] <sistpoty> heh
[23:06] <sistpoty> gn8 RainCT_
[23:06] <sebner> RainCT_: gn8 =)
[23:11] <sistpoty> LaserJock: any news about sponsoring for main?
[23:11] <sebner> is anybody here member of the Debian Scientific Computing Team?
[23:13] <sistpoty> sebner: not too sure, but I guess norsetto is and LaserJock as well
[23:13] <sebner> sistpoty: that would be great
[23:13] <norsetto> sistpoty: I'm not actually
[23:13] <sistpoty> ah
[23:13] <sebner> LaserJock: still around?
[23:15] <emgent> sebner: try in #debian-devel
[23:15] <sebner> emgent: I know. It's just that I would need a MOTU who is part in this team ;)
[23:15] <emgent> oh ok :)
[23:17] <LaserJock> sebner: yeah
[23:17] <LaserJock> sistpoty: trying to get my sbuild working
[23:17] <sistpoty> ok :)
[23:17] <sebner> LaserJock: are you member of the Debian Scientific Computing Team?
[23:18] <LaserJock> no
[23:18] <sebner> damn
[23:18] <sebner> sistpoty: damn you ^^
[23:18] <LaserJock> I hang out with Debian Science and Debichem
[23:18] <sebner> LaserJock: sorry then
[23:18] <sebner> LaserJock: do you know a MOTU who is in this team?
[23:18] <LaserJock> are you looking at pkg-compsci ?
[23:18] <LaserJock> no
[23:18] <sebner> LaserJock: ok, np. And no
[23:18] <LaserJock> is there even really a team for it?
[23:19] <LaserJock> I thought it was just a couple people
[23:20] <sebner> LaserJock: it's pkg-scicomp
[23:20] <LaserJock> yeah, that's the one
[23:20] <LaserJock> I don't think there's all that many people in it
[23:20] <LaserJock> and none that are connected to Ubuntu that I'm aware of
[23:20] <LaserJock> sebner: what do you need?
[23:20] <sebner> LaserJock: ok. thanks
[23:22] <sebner> LaserJock: somebody that needs to push our changes back since persia filed a bug there but a debian-dev didn't trust him. persia told me to ask directly a member. So I have to file a bug now and hope the best
[23:22] <LaserJock> if all else fails you might be able to email debian-science for discussion
[23:23] <sebner> LaserJock: yeah. We'll see
[23:25] <LaserJock> anybody have problems with fakechroot in an intrepid sbuild?
[23:27] <norsetto> sebner: what package was that?
[23:27] <sebner> norsetto: gmsh
[23:29] <tholdar> why. Czessi?
[23:37] <sistpoty> heh, so I just sent a very short application for core-dev to mc... let's see what will happen :)
[23:37] <tholdar> why
[23:38] <sistpoty> tholdar: you could aks that on a follow-up mail (in case you are responding to my comment)
[23:38] <sistpoty> ask even
[23:38] <LaserJock> sistpoty: heh, good luck!
[23:38] <sistpoty> LaserJock:  thanks!
[23:38] <sebner> sistpoty: now I'm universe-contributor. I'll comment ^^ Maybe then the think you application is a  joke ^^
[23:39] <sistpoty> :O
[23:39] <sebner> hmm. It's pretty late and I can't write -.-
[23:40] <sebner> sistpoty: just a joke ^^, good luck :)
[23:40] <sistpoty> :)
[23:41] <sebner> norsetto: special interest in gmsh?
[23:41] <norsetto> sebner: no
[23:42] <sebner> norsetto: ok :)
[23:43] <sebner> so. gn8 folks :)
[23:43] <norsetto> sistpoty: nighty sistpoty
[23:43] <sistpoty> gn8 sebner
[23:43] <sistpoty> gn8 norsetto (or did you mean sebner there?)
[23:44]  * norsetto has a fried brain
[23:44] <sistpoty> heh
[23:48] <sistpoty> geser, persia, dholbach, nixternal, soren: you've got mail :)
[23:48] <LaserJock> sistpoty: I'm having to rebuild my intrepid chroot, but I'm still working on your packages
[23:48] <sistpoty> LaserJock: no problem... ;)
[23:49] <sistpoty> LaserJock: thanks for looking actually :)
[23:49] <LaserJock> sistpoty: lol, that is such a typically sistpoty application :-)
[23:51] <sistpoty> heh
[23:52] <LaserJock> I don't think sistpoty even has a -v switch
[23:56] <sistpoty> LaserJock: I do have... just give me lots of beer ;)
[23:59] <LaserJock> heh
[23:59] <LaserJock> alright, intrepid chroot rebuilt