=== Snova_ is now known as Snova
=== santiago-pgsql is now known as santiago-ve
=== lex79 is now known as lex79_
=== lex79_ is now known as lex79
=== rgreening_ is now known as rgreening
[06:56] <dholbach> good morning
[08:29] <directhex> morning dholbach
[08:42] <dholbach> hi directhex
[08:55]  * hyperair pokes dholbach 
[08:56] <hyperair> dholbach: remuco's in karmic? i don't see it =\
[08:59] <dholbach> hyperair: you're right - sorry, I was mistaken
[08:59] <hyperair> dholbach: do NEW packages get autosynced?
[08:59] <dholbach> yes
[08:59] <dholbach> until we're in DebianImportFreeze
[09:00] <dholbach> which isn't until June 25th
[09:04] <hyperair> ah i see
[09:04] <hyperair> dholbach: do main and universe packages get synced at different frequencies?
[09:04] <dholbach> no, I don't think
[09:04] <hyperair> dholbach: nautilus-share which i got uploaded to debian a short while ago was after remuco-server, but it's been synced already.
[09:05] <hyperair> 0.7.2-8.
[09:05] <dholbach> maybe it was an explicit sync request
[09:07] <hyperair> hmm
[09:07] <hyperair> maybe it was
[09:07] <hyperair> so how long does it take for a package to get synced usually?
[09:09] <dholbach> hyperair: I don't know - best to ask in #ubuntu-devel
[09:11] <hyperair> okay
=== proppy1 is now known as proppy
[09:27] <geser> hyperair: depends on when an archive-admin triggers the autosync
[09:27] <hyperair> ah so it's not auto? O_o
[09:35] <geser> no, only semi-automatic
[09:36] <hyperair> heh
[09:37] <hyperair> well i'll just continue waiting then
[09:39] <geser> I'm currently not sure if NEW package are included in the autosyncs or if importing them needs to get triggered seperately by an archive-admin
[09:43] <geser> according to https://wiki.ubuntu.com/ArchiveAdministration#Syncs this doesn't happen automatic
[09:45] <geser> hyperair: you could ask jdstrand to sync also NEW when he does the archive work today (it's his archive day today)
[09:46] <hyperair> ah okay
[09:46] <hyperair> nevermind, i'm in no hurry, as long as the package makes it in before debian import freeze =p
[09:46] <hyperair> and featurefreeze
=== ShadowChild is now known as lukjad007
[11:01] <maxb> Packages in Debian NEW *cannot* be synced, manually or otherwise
[11:02] <maxb> Only after they've been accepted out of Debian NEW
[11:03] <DktrKranz> there's no way to access them, OTOH
[11:04] <maxb> OTOH?
[11:04] <hyperair> maxb: er i meant just came out of NEW.
[11:04] <hyperair> DktrKranz: it's remuco-server, which had been ACCEPTED some days ago
[11:04] <maxb> Ah, "new" not "NEW" :-)
[11:04] <hyperair> =p
[11:04] <hyperair> right
[11:11] <DktrKranz> hyperair: heh
=== ember_ is now known as ember
=== ejat is now known as e-jat
=== asac_ is now known as asac
[12:48] <_ruben> heh .. "funny" version .. Unpacking mysql-client-5.0 (from .../mysql-client-5.0_5.1.30really5.0.75-0ubuntu10.2_i386.deb) ...
[12:53] <geser> this is used when a version needs to go backwards (which isn't possible) and one want to avoid adding an epoch (which will need to stay forever)
[12:55] <_ruben> so there was a "faulty" 5.1.30 upload at some time i guess? which does seem wrong for a 5.0 package indeed ;)
[13:02] <geser> looking a the changelog it seems it was done because the mysql 5.1 packages provided a package which was also build from mysql-5.0 which broke things (or so)
[13:05] <_ruben> nice :)
=== ogra_ is now known as ogra
=== korn_ is now known as c_korn
[14:24] <LarstiQ> Hi, what do I have to do to get someone to pay attention to bug 342782 ?
[14:24] <ubottu> Launchpad bug 342782 in pyqwt5 "python-qwt5-qt4 will not install on Jaunty" [Undecided,Confirmed] https://launchpad.net/bugs/342782
[14:28] <kklimonda> LarstiQ: if there is a patch attached subscribe motu-sru
[14:29] <LarstiQ> kklimonda: there are, though not really correct, due to python2.5 vs python2.6 site-packages/dist-packages differences. Still subscribe?
[14:30] <ScottK> LarstiQ: I think the 'hack' probably gives enough hints at the proper solution, so it's worth subscribing.
[14:30] <ScottK> LarstiQ: The odds go way up if you can get it to work for Qt3/Qt4 on both Python versions.
[14:31]  * ScottK worked on trying to figure that package out before release and didn't come up with a solution.
[14:31] <LarstiQ> ScottK: aye, I'll try that if I have some time to burn, will subscribe first
[14:32] <ScottK> LarstiQ: If you get it figured, ping me and I'll sponsor it.
[14:33] <LarstiQ> ScottK: cool, I will if I do :)
=== effie_jayx_ is now known as keffie_jayx
=== yofel_ is now known as yofel
[16:01] <gaspa> dholbach(or any MC member): is it too late to sign for the next MC meeting?
[16:02] <Laney> they say 7 days don't they?
[16:03] <gaspa> Laney: yep
[16:03] <Laney> doesn't it say when the next one is?
[16:04] <gaspa> 25th, the next Thursday...
[16:04] <gaspa> In fact I'm a bit late... that's why i'm asking.
[16:04] <dholbach> gaspa: I personally have no objections
[16:07] <gaspa> dholbach: ok, thanks.
[16:12] <slayton> the diff.gz that gets generated during build is that only for the debian dir or can it contain patched sources as well?
[16:12] <dholbach> slayton: the latter
[16:12] <dholbach> if the packages uses a patch system already, it's good if you use that patch system for changes to the actual changes
[16:14] <slayton> ok... but sources that are changed from upstream don't require patch files to be accepted?
[16:14] <slayton> in revu
[16:15] <dholbach> if you prefer working without a patch system that's fine
[16:16] <Laney> is it?
[16:17] <directhex> crap but permissible ;)
[16:17] <dholbach> Laney: sure - we have a bunch of those in the archive
[16:17] <dholbach> ask cjwatson for his opinion on patch systems :)
[16:17] <Laney> we do, but I wonder if w...
[16:17]  * Laney runs
[16:17] <directhex> dholbach, ISTR i did!
[16:17] <Laney> how did that end?
[16:17] <ScottK> It's also quite invitable for pacakges that use DVCS.
[16:18] <directhex> Laney, respectfully, of course!
[16:18] <Laney> I think that we should encourage best practices for our new contributors
[16:18] <Laney> what that means depends on who you talk to
[16:18] <Laney> and circumstances of course (DVCS being one)
[16:18] <dholbach> whenever I have to use quilt, I'd prefer straight patches to the source :)
[16:18] <directhex> straight patches to the source are easy.
[16:19] <directhex> until they stop applying, then they suck
[16:19] <Laney> having had to detangle a mess of diff.gz patches, they aren't fun
[16:19] <directhex> patch systems are useful because they have an "off" switch, more than anything else
[16:19] <dholbach> in any case I wouldn't want to overrule a package maintainer for no good reason
[16:20] <dholbach> if it makes your job easier, do whatever you like, but I don't see a lot of use in setting up a policy for it
[16:20] <directhex> no, of course, keep the maintainer's decisions
[16:20] <directhex> and if it's the first patch, check whether the package conforms to some kind of group policy - i.e. add a patch system if the package follows a policy which mandates one
[16:21] <Laney> so if you're sponsoring a new package, should you question it?
[16:55] <mok0> Laney: thank god for splitdiff
=== ejat is now known as e-jat
[17:52] <mok0> sebner: are u gonna merge flightgear?
[17:55] <sebner> mok0: wll, if you want to do it you are free to take it as I have 3 more weeks of military service todo with hardly any time
[17:56] <mok0> sebner: no time for flight simulator, huh?
[17:56] <mok0> sebner: ok, I'll take care of it
[17:57] <sebner> mok0: heh, you don't need if you don't want to. It's just that I'm not really sure if I have enough time for it this weekend or the next one
[17:58] <mok0> sebner: I doing at least one merge a day, so I was looking for one :-)
[17:58] <mok0> sebner: most are reserved
[17:59] <kb9vqf> ajmitch: Looks like I won't be able to deal with FDS after all....my main server cluster was just taken out by the severe storms this morning.
[17:59] <kb9vqf> ajmitch: Lightning struck within 30 feet and the EMP fried my systems. :-(
[17:59]  * kb9vqf is on his laptop for now
[17:59] <kb9vqf> Sorry! :-(
[17:59] <sebner> mok0: heh, fine then. I'm also happy to have a new version and when I have more time in future I'm going to play flightgear a lot :D
[17:59] <stefanlsd> mok0: i was looking at putting together a system where last contributors get notified of a new merge (sometimes you dont even know!) and then a way to say, feel free for someone else to take it...
[18:00] <mok0> stefanlsd: nice... in principle though, all merges are "free" since we have joint maintainership.
[18:01] <mok0> There have been complaints that the "last-merger-ping-required" policy has slowed down merging
[18:02] <stefanlsd> mok0: yeah, although we like to defer to the last uploader as they may have some specific knowledge.. also, I guess people trying to trying to show contributions dont enjoy other people doing there merges...
[18:03] <mok0> stefanlsd: at this point though, the merges have been sitting there since the archive opened a month and a half ago
[18:03] <stefanlsd> mok0: i think it has slowed merges alot! also some of the last mergers are not around anymore...
[18:04] <mok0> stefanlsd: right
[18:05] <stefanlsd> mok0: my thinking is that the last merger would get notified. if he doesnt do the merge or object to anyone doing it, or say its free - in a certain time period, it would move to a feel free to merge
[18:05] <mok0> stefanlsd: ... is that something you would implement of top of MoM?
[18:08] <stefanlsd> mok0: its just thoughts at the moment. not sure where exactly where its gonna go (ideas welcome!0
[18:09] <mok0> stefanlsd: kk... I think it would fit nicely there
[18:09] <stefanlsd> mok0: kk. thanks. i will look into it there...
[18:20] <carthik> Is there a guide somewhere on how to take a debian sid package, change a few dependencies and build a package for Ubuntu (jaunty)?
=== menesis1 is now known as menesis
=== andreas__ is now known as andreas
=== andreas is now known as ahasenack
[18:49] <slayton> is there a cdbs variable that can be used to determine which version of GCC is used?
[18:52] <azeem> slayton: "CC"
[18:52] <slayton> azeem, ty
[18:54] <c_korn> when will the next daily build be available?
[19:09] <RainCT> omg can't we just set up a filter on the ML which rejects any mail containing the word "mono"? :P
[19:13] <slayton> RainCT, what if there is an outbreak of disease?
[20:03] <directhex> RainCT_, a new flame war? yays :|
[20:04] <directhex> oh, someone trying to push the gnote suggestion on pure "zomg" grounds
[20:07] <RainCT_> directhex: Yeah, I'm starting to get annoyed of such mails.. A few more of them and I'll switch from "anti- but I don't really care" to "pro-mono" ;)
[20:08] <directhex> RainCT_, these folks don't seem to understand the harm they do to their argument by acting like f... in a tiresome manner.
[20:10] <CarlFK> somone in some #chan (I think here) pointed me to some site that would search PPAs... anyone know what I am talking about?
[20:10] <CarlFK> or... anyone know where I can find dia-trunk.deb
[20:11] <CarlFK> the version in jaunty has huge issues exporting svg, want to try trunk before I go wining about it
[20:12] <kb9vqf> CarlFK: This link should work: https://edge.launchpad.net/ubuntu/+ppas
[20:13] <kb9vqf> CarlFK: Or there's this (unofficial
[20:13] <kb9vqf> page: http://ppa-search.appspot.com/
[20:14] <CarlFK> bingo.  lets delicious it this time...
=== Quintasan_ is now known as Quintasan
=== kirkland` is now known as kirkland