=== danielm_ is now known as danielm [01:57] Heya gang [01:57] Yo! bddebian ! [01:58] Hi RAOF [01:59] :) [01:59] Hello emgent === danielm_ is now known as danielm [03:35] is the maintainer of the ubuntu sugar packages here? [03:37] Jani? No. [03:37] He doesn't usually hang out on IRC [03:38] mm ok. === Allan_ is now known as Hit3k [03:38] i was hoping to talk to him about making my install work ;) [03:41] :) [03:41] jani@ubuntu.com [03:43] i'll let him get to the bug when hes ready. just thought i might be able to pin him about it === danielm_ is now known as danielm [06:05] ScottK: bug 209012 has an inappropriate status set, correct? [06:05] Launchpad bug 209012 in monodevelop "[FFe] Merge monodevelop_1.0+dfsg-1 from Debian(Unstable)" [Undecided,Confirmed] https://launchpad.net/bugs/209012 === cody-somerville_ is now known as cody-somerville === never|mobi is now known as neversfelde|mobi [06:53] Good morning [07:05] good morning [07:07] good morning dholbach [07:08] hi warp10 === fabo_ is now known as fabo === \sh_away is now known as \sh [08:59] siretart, you there? [09:12] <\sh> moins [09:40] heya [09:43] k [09:43] k === Allan_ is now known as Hit3k === sdh_ is now known as sdh [09:57] elmargol: at work, what's up? [09:57] elmargol: email is the safest way [09:57] siretart, did you notice that xine is atm broken on hardy? [09:58] elmargol: oh, sorry, is there a bug nr yet? [09:58] https://bugs.launchpad.net/ubuntu/+source/xine-lib/+bug/210510 [09:58] Launchpad bug 210510 in xine-lib "[Hardy Heron] Some formats including quicktime (.mov) and m4v stop playing with xine after upgrade" [Undecided,New] [09:59] ah, that one, I'm aware of it [09:59] I'll update the bugreport, thanks [10:02] elmargol: I frightened me. xine is not broken, a demuxer of xine is [10:02] heya siretart :) [10:03] hey emgent [10:07] congratulations mok0 [10:07] dholbach: It's a bit premature to congratulate, I think [10:08] dholbach: unless you know something that I don't :-) [10:08] mok0: I don't think so :) [10:10] Congrats mok0! :-D [10:10] warp10: :-) [10:11] * mok0 is somewhat puzzled [10:11] mok0: Yeah, congrats. [10:12] soren: ... and thanks for the +1 :-P [10:12] Ah, now I see my email :-D [10:13] Yay [10:15] elmargol: fix uploaded [10:18] congratulations mok0 [10:18] Thanks james_w! I just saw the email a few moments ago! [10:18] Definitely cool [10:18] mok0: congrats :) [10:19] Thanks pochu! I can take care of xtide myself now :-D [10:19] :-) [10:23] who's next then? [10:28] <\sh> mok0: congrats :) [10:28] Thanks \sh! [10:30] siretart, thx === Seveaz is now known as Seveas === dholbach_ is now known as dholbach [10:50] Is gcalctool a calendar??? https://bugs.edge.launchpad.net/gcalctool [10:50] I would say calculator === ianc_ is now known as ianc === asac_ is now known as asac [11:02] <\sh> mok0: hmmm [11:02] <\sh> mok0: lol [11:03] \sh that package is so buggy it should be removed from hardy [11:03] We can't make a release with a buggy calculator!! [11:05] ... and there are plenty of others available === kitterma is now known as ScottK2 [11:18] mok0: Congratulations. [11:19] ScottK2: Thanks! Wouldn't have happened without you! [11:20] ScottK2: Now I have to learn how to use my new powers ;-) [11:20] ScottK2: I'll likely be asking a lot [11:20] mok0: Have you used a ppa before? [11:20] s/learn/abuse/ :-) [11:20] Yes, I have a ppa [11:20] mok0: Then you'll feel right at home :) [11:21] You just upload to upload.ubuntu.com/ instead of ppa.launchpad.net/~username/ubuntu [11:21] soren: and then the packages appear in the queue, I assume? [11:22] mok0: Yeah, and get built and all that. [11:22] soren: ... while completely new packages still need an ack from the archive-admin, right? [11:22] mok0: Right. [11:23] Both binary and source packages. [11:23] Which means: [11:23] a) if an existing source package starts building an extra binary package, that new binary package needs to be accepted by an admin. [11:23] and [11:24] b) if you upload a new source package, first the source package needs to be accepted, then it gets built and then the resulting binaries need to be accepted. [11:24] soren: very reasonable [11:25] ... but noone actually checks to see if the application (say) in fact runs on a given platform? I do not have access to all supported platforms [11:27] soren: ^ [11:27] mok0: No, we rely on users for that. [11:27] Well, people testing the development version will and any testsuites run during the package build will have been run. [11:28] mok0: Most arch-specific problems turn up at build time, though. [11:28] I think. [11:28] :) [11:28] soren: I've seen that happen :-) [11:29] Oh, sure, I'm just not entirely sure that *most* arch-specific problems will reveal themselves at build time. I think so, though. [11:30] soren: you are probably right. If it builds, it runs, unless the application does something arch-specific that does not trigger a compile error or something [11:30] Right. I just don't have any statistics to back me up, so I should probably be careful with words like "most" :) [11:30] heh [11:30] yes [11:36] A lot of arch-specific problems that don't stop the build will at least generate warnings during build. [12:10] Seveaz: hey, falcon 2.0.5 is not in hardy :) === Seveaz is now known as Seveas [12:11] tjaalton, there are some issues [12:11] Seveas: really? 2.0.4 is broken for me, but .5 works [12:19] boo [12:19] Hey [12:25] Hi [12:25] has anyone seen tepsipakki latey? [12:25] mok0: that was fast, gratz! :) [12:26] Thanks RainCT! Yeah it was fast! I was taken by surprise :-) [12:26] * RainCT hadn't even time to answer :) [12:31] siretart: good response, btw [12:31] to what? [12:31] wait. wrong one. [12:31] * Hobbsee meant sistpoty. === elkbuntu_ is now known as elkbuntu [12:31] i always get confused with your two name <--> irc nick conversions. [12:32] the stpoty == Stefan Potyra. my name is 'REinhard TARTler' :) [12:47] siretart: tepsipakki == tjaalton [12:47] ah [12:48] siretart: Just like shawarma == soren. Things change :) [12:48] * Hobbsee mumbles about canonical naming [12:49] It was (almost) unrelated to my joining Canonical. [12:49] It certainly wasn't mandated in any way. [12:49] just the others all seem to do it [12:50] At the first sprint I overheard someone say that if a nick wasn't used, you could hijack it. (on freenode) [12:50] ....no? [12:50] you can link to it, etc, though [12:50] i fyou have it registered, you can ghost people off it [12:50] I guess if I hadn't joined Canonical, I wouldn't have been at that sprint, and I wouldn't have known, and hence wouldn't have changed, so in a *very* îndirect way, it's because I joined Canonical :) [12:51] Hobbsee: If a nick hasn't been used for more than 6 months, you can ask to take it over. [12:51] oh, true [12:51] That's what I meant. [12:51] although i would expect that if the master nick was active, they'd say no [12:51] It's not like it automatically frees up so that you can just take it over somehow. [12:52] Hobbsee: Nope. [12:52] Hobbsee: I'm *almost* sure the previous master nick of "soren" was active (not much, though), but "soren" itself hadn't been used for almost two years. It was waay easy taking it over. [12:53] oh, strange [12:53] then again, freenode rules seem to change on who you get, at times [12:53] Lots easier than taking over #ubuntu-virt, for instance. [12:54] yeah, well. erk, channels. [13:32] * Hobbsee ponders what to say about till's core dev app [13:37] <\sh> Hobbsee: I'm biased [13:39] <\sh> Hobbsee: one the one hand, it would be good to have someone who has a lot of clue about printing to work in main...on the other hand, when you want to be a core-dev you need to be more careful even when you need packages in before FF badly [13:40] well...yeah... [13:40] so, i'm allowed to write that kind of thing? [13:40] <\sh> Hobbsee: if this is your opinion, too why not :) [13:41] \sh: i can't help wondering if these packages would still have been shoved through, in broken state, if till had *not* been working for canonical though. [13:42] presumably the community devs would have been looking at the work done, and would have rejected it due to the errors it contained, had it been from a community member. [13:43] <\sh> Hobbsee: well, motus can push packages without reviewing into ubuntus archive...I did that once, because I was really sure that I fixed all warnings, errors etc. from lintian and friends...but normally I go via revu...especially then when I need more then one pair of eyes to look at the package [13:43] \sh: that's different, isn't it? they've done enough packaging to know how it all works? [13:43] oh wait, till was a MOTU [13:44] <\sh> Hobbsee: TBH, everyone makes mistakes...e.g. sometimes the copyright stuff is really a problem [13:44] oh, indeed. [13:44] i'd forgotten he was a MOTU for a second there [13:45] \sh: oh, rats. MC makes the recommendation, then TB acts on their recommendation, right? [13:45] Hobbsee: Allowed to write what kind of thing? [13:46] soren: objections in general? [13:46] Hobbsee: Why shouldn't you be allowed when Stefan clearly is? [13:46] soren: because i'm hated by various people? [13:47] soren: i don't feel like being told i'm overreacting, when respectfully stating objections again. [13:47] hence, i'm fairly careful in what i write, when it comes to people, and them making questionable judgements. [13:48] Well, if you think you're right, go ahead. If people disagree, that's their right, too, surely? [13:48] you don't have to be correct the first time, if it promotes a discussion [13:49] huh. I thought Till was already core. === \sh is now known as \sh_away [13:49] meh.. === \sh_away is now known as \sh [13:50] sladen: no, they just grill me if they didn't like what i said. [13:50] <\sh> grmpf [13:50] <\sh> Hobbsee: sry..I didn't get your last statements..because totem thinks about letting my desktop die when I use strace on it with an .flv file === jono is now known as serveredfifth === serveredfifth is now known as severedfifth [13:53] \sh: http://pastebin.ca/967443 === severedfifth is now known as jono [13:55] <\sh> Hobbsee: I think when we are not allowed to write or say our valid objections anymore, then the community model of ubuntu in general failed [13:56] Noone's barring anyone from saying anything. [13:56] <\sh> Hobbsee: actually...tbh...we shouldn't make any diff between someone who is doing voluntary work or someone who is freelancing for the company which sponsors the project... [13:56] \sh: we shouldn't, yes. I'm just wondering if we are... [13:57] as in, we collectively [13:59] <\sh> Hobbsee: in 2006 it was my call that till went to UDS Paris and talked to pitti because of printing..(while he was still working for mandriva) so, I know he knows a lot of printing stuff and also packaging...(during our dinner he gave me a personal shock that till knew still the line numbers of special stuff inside cups' source, he scared me ;)) [13:59] It's only natural to consider that fact that we know that these people work on Ubuntu all day long. [14:01] argh. an envy-ng uvfe. [14:01] <\sh> soren: regarding his status, he is working for the linuxprintingfoundation...or what the name is [14:01] \sh: Right. [14:02] Hobbsee: What exactly would you expect people to do if they disagreed with you? [14:04] soren: dunno. disagree politely, and not flame me to hell about it? not discuss it in an office block, and then get multiple emails complaining about it, even from people who weren't even there? Also, i'd appreciate people actually looking at the idea i'd put forth, rather than my actual manner of saying it, if they found that unpallatable. [14:04] the latter part, in particular. [14:05] Hobbsee: Er... So you want other people to disregard your tone, because you don't like *their* tone when they don't? [14:06] soren: is it a problem to drop all tone from all mails, and feel that people are trying to do the best they can, and may well have credible ideas, on both sides? [14:06] as in, pick the best possible interpretation, from all sides? [14:06] Do you think so? [14:07] i don't, no. [14:07] So what's the problem? [14:07] if i'm rude to people, then yes, call me on it. if i've not done the mail with my rose coloured glasses firmly enough on, then look at what i mean, and don't flame me to hell. [14:08] that's what i'd *like* [14:09] * soren is on the phone [14:09] TBH, just about all of us are rude at some point. (e.g., I'm a PITA) [14:09] i find it crazy that if i say something with a glass-half-empty approach, people flame me for tone, and not being positive. yet someone who says *exactly* the same thing, with their rose-coloured glasses on, glass half full, doesn't receive any censure at all, and people actually read the intent of their male. [14:10] now, obviously, i should ensure that i do it with the rose-coloured glasses on, but in the case that i don't, is it *really* productive to ignore the entire mail, and not take anything from it? [14:10] Not at all. [14:11] so, why does it happen? [14:11] and why do you think that i now don't speak much, because of that? [14:11] Yet, I've certainly seen e-mails that were written in a tone that so thoroughly and consistently invited me to ignore it or act on that instead. [14:11] all of them? [14:12] Huh? [14:12] No, I've seen e-mail that didn't. I get a *lot* of e-mail. [14:13] At some point, if someone consistently sends e-mail in such a tone, I (bloody human as I am) get annoyed as soon as I see that person's name on an e-mail. [14:13] * \sh is an asshole from time to time, too...but it's just because you need to be one at certain times...even a CoC doesn't change that [14:14] soren: which is exactly why i don't bother sending mails now, a lot of the time. [14:14] what's done is done. [14:14] i can't change it now, when people have gone into ignore mode. [14:14] While being human, I also find myself to be rather reasonable. [14:15] If one of those people started to be not quite as testy, I might very well start to reconsider. [14:15] sometimes i wonder why i put effort into ubuntu at all, if everything gets ignored. [14:15] It doesn't happen overnight (just like getting to this point didn't) [14:16] no, but it appears to be a one way street, apparently. [14:17] I don't know what you're basing that on. [14:17] ..but I disagree. [14:18] if you ignore mail, then of course you don't see any good stuff. [14:19] OTOH, you also avoid a lot of flaming. [14:20] Hobbsee, some people have a personal orientation in being more noisy blocking/opposing other people participation, that is usually labeled as negative, IMHO you are such kind of person, regardless of the great things you do [14:21] crimsun: this is true. i'm actually trying to stop that. and wondering if it's worth it. [14:22] Hobbsee: well, trying is worth it. I wouldn't worry about drama much; anytime you put people together, you get it. [14:22] crimsun: just that i don't get taken seriously at all anymore. [14:23] although i'm greatful to see that stefan agreed with my mail, so people should take what i said into consideration, through him. [14:24] Hobbsee: their seeming failures to accomodate your perspective should not drive you off, though [14:24] crimsun: why? [14:25] if i'm being unproductive, for various reasons, and can't seem to fix that, then what's the point in wasting everyone's time? [14:25] it doesn't matter what i think, if people don't agree with it - it gets discounted. [14:25] and if peopel do agree with it, they say it themselves. [14:25] None. (Please note that I don't believe the conditions to be true) [14:26] so unless i'm making uploads, i'ts pretty much worthless to be here, as it's proven that i'm not doing anything usfeul for the team. [14:26] allow me to play devil's advocate. If you're a whistle-blower and everyone else turns a blind eye, does it mean you're incorrect? Does it mean you should stop saing things? [14:26] saying * [14:27] crimsun: doesn't say anything about correctness, but does say that i should shut up, yes, for the general good of the team. [14:27] ther'es no point consistently fighting, no matter whehtehr you're fighting for something that is right, if the rest of the team has no intention of changing their mind. [14:27] no matter what [14:27] Hobbsee: If someone is unproductive beyond repair it's a waste of (everyone's) time (by definition). I'm not saying that you are indeed unproductive beyond repair, though. I'm merely confirming your hypothetical logical implication. [14:28] soren: i'm failing to see, how if someone's contributions get put on an ignore list, how anyone might know if their contributions have turned useful or not, as they don't see it. [14:28] am i missing something? [14:28] or is it not a true ignore list? [14:28] Hobbsee: Yes, you are. [14:28] then please tell me what i'm missing [14:29] That we're all humans? [14:29] For instance: While I tend to try to ignore certain people, I sometimes fail to do so. [14:29] Other times I give them a second chance to see if they've changed. [14:30] Other times again, someone else tells me something to make me see things from a different perspective. [14:30] We work with computers, yes, but we are not computers ourselves. Deal. [14:30] Hobbsee, There seems to be a lot of parallels between a situation I was in with another ubuntu team about a year ago and yours. [14:32] cody-somerville: oh? [14:34] Hobbsee: I don't believe, by the way, that I ever mentioned any sort of filter. Every time I ignore someone, it's a conscious decision. [14:35] soren: out of curiousity, hypothetically, how would you go about putting your thoughts about something that clearly doesn't work, into a mail, which would be accepted due to it's rose-coloured glasses. if something's not working, then the world is *not* all fine and rosy, so trying to pretend it is isn't a great idea. [14:35] right [14:38] this is my great problem, you see. [14:43] it's not an easy one to solve [14:49] soren: there's my attempt at a productive mail. Take it as you will. [14:55] protonchris: I just released another glom. 2.6.12. It has another fix for a postgres 8.3 change, so it would be great if it can get in to Hardy. [15:01] <\sh> soren: we work with humans...the computer is just a tool like a hammer or screwdriver...if I'm shouting at my computer...he won't be pissed and works like expected...people don't [15:01] Hobbsee: I try do deal with things constructively. Good or bad. [15:02] \sh: Precisely. [15:02] hi RainCT, what do you think about Debian bug #455482? do you think we should keep it, remove it, or wait until someone (you?) writes it in PyGTK? [15:02] Debian bug 455482 in pyzenity "Please motivate inclusion in Debian" [Serious,Open] http://bugs.debian.org/455482 [15:03] <\sh> the problem here is this: till made a mistake for the first time...the first time he judged by himself the good or bad of this upload..his solution (imho): I need to get the package in, without fixing the bugs, but I still have time to fix them.. [15:05] <\sh> the decision to be made is upon us motus/cores....if till thinks it's allright, then ok...he needs to deal with the questions at some point...which is good...and should go into the decision if he's becoming a core dev or not...if he made a wrong decision in universe/multiverse it's likely to happen that a similiar decision is going to be made for main. But the latter is not Till...Till learns quickly...and if he's not going to become a core dev now, h [15:06] \sh: you got cut off [15:07] At "if he's not going to become a core dev now," [15:07] <\sh> he will become one in the near future [15:08] <\sh> soren: the MOTU team is now more then 3 years old...most of the policies we developed in the last year [15:08] \sh: My point exactly. [15:09] <\sh> regarding other projects...yes, we are young...regarding ubuntu, we are just as old as ubuntu itself ;) [15:10] Pretty much, yes. My statements hold true for most of Ubuntu. [15:20] hello [15:23] i have an dilemma about an bug that is fixed in LP but is still present when you install the package [15:24] In a watch file, how do I deal with a version that is present in both the directory and the tar file? E.g http://...../foo-1.2/foo-1.2.tar.gz [15:24] mariuz: what's the bug number? [15:25] hmm, where did my theme go? [15:25] 135695 [15:25] is there a known hardy bug where the theme disappears? [15:25] bug 135695 [15:25] Launchpad bug 135695 in php-interbase "FTBFS: depends on php4-dev, which has been removed" [Medium,Fix released] https://launchpad.net/bugs/135695 [15:25] thanks ubotu [15:26] the problem is fixed in hardy but in gutsy is still there i mean the php5-interbase package is not installable [15:26] it depends on the php4 api , yes i know is horrible [15:27] mariuz: ok, you will need to apply for a stable release update, a.k.a. an SRU. [15:27] ah removal of murrine. [15:28] mariuz: https://wiki.ubuntu.com/StableReleaseUpdates [15:28] ok thanks [15:28] hi [15:29] mok0: congratulations ;) a bit ealier than the 23th ^^ [15:29] sebner: yes :-) I am surprised it went so fast! [15:29] I just uploaded OpenTTD's new major release to Debian, and I wonder if/how hard would it be to sneak it in hardy at this point. It'd be good to have compatible network games with the current version during while ubuntu 8.10 gets developed. [15:31] jordi: does it fix major bugs? [15:34] mok0: congratilations! [15:34] mok0: *shrug*, the main changes are new features, it's not a bugfix release. [15:34] congratulations* [15:34] but I'm having a look at the changelog [15:34] nxvl: Thanks! :-) [15:35] jordi: then it's a no-go [15:35] <\sh> jcastro: mail send...I can't because linuxtag :) [15:35] mok0: see any gnome package, their watch file have versioned directories [15:35] \sh: I appreciate the timely response, thanks! [15:35] pochu: thanks! [15:35] mok0: my biggest concern is people using the current version won't be able to play online with the servers, as they'll have outdated clients [15:35] <\sh> jcastro: postpone the invitation for octobre ;) [15:36] jordi: the package might go in hardy-backports [15:37] jordi: although I don't know what the policy is for that to happen [15:37] jordi: you mean the servers have changed, so the current version doesn't run anymore? [15:38] mok0: aha, anyway, I just wondered if it'd be not too hard to get in [15:38] if it's a problem, I'm not going to push for it too hard [15:38] mok0: if the public servers at openttd.org run 0.6.0, which they will, 0.5.3 clients won't connect [15:38] .... and when is this upgrade going to happen? [15:39] jordi: ^ [15:41] mok0: 0.6.0 was released yesterday, I assume it'll happen in the following weeks [15:41] mok0: this happens all the time with online games: frozen bubble, freeciv, etc. [15:41] Hmm. I'd say that is a bug [15:41] the timing for this release isn't too fortunate then [15:41] mok0: no, it's like trying to install a package compiled for glibc 2.7 on a glibc 2.3 system [15:42] do people really play f-b online? [15:42] the client lacks features the server wants to use in the game [15:42] jordi: you can try to file a bug at Launchpad, with all the facts you've given here, and subscribe the motu-release team. They will decide [15:42] jdong: is there any point playing solo? :) [15:42] jdong: I only play online [15:42] mok0: I think in the case of incompatible network games, a FFe should be attempted [15:42] jordi: thanks for making me feel antisocial ;-) [15:42] jdong: yeah [15:42] jdong: haha [15:43] jdong: jordi first said it was a new feature release [15:43] mok0: yeah, this is the biggest reason for my request; I mean, I come from Debian, there's a pretty tough culture to not allow freeze breaks :P [15:43] mok0: and the new features are a problem to old client users [15:44] jordi: but you need to present it as a bug that the older version will not work shortly [15:44] Well, the thing is: You can't just file a sync request and expect it to be done. You need to file a feature freeze exception. [15:44] I think this is a case of "if nothing horribly breaks it's better than freezing the way it is" [15:44] but yeah without a doubt a FFe needs to be filed for this to happen [15:44] jdong: exactly [15:45] jordi: you know what to do? [15:45] I had a look at th wiki [15:45] ugh, changelog diffs [15:46] jordi: how long might it be until they release another incompatible version? [15:46] jordi: just cut'n paste upstream changelog from 0.5.3 to now [15:47] james_w: openttd's release schedule is long [15:47] let me check when 0.5.x was released [15:48] that's another reason I'm trying this [15:48] if they were going to release 0.7 in May it'd be pointless [15:48] openttd (0.5.3-1) unstable; urgency=low [15:48] -- Jordi Mallach Tue, 18 Sep 2007 12:05:28 +0200 [15:48] jordi: yeah, that's what I was wondering. [15:48] er [15:48] that was 0.5.3 [15:48] -- Jordi Mallach Thu, 8 Mar 2007 15:34:54 +0100 [15:49] james_w: but that's not saying they change the protocol at every release [15:49] true [15:49] I think it's probably worthwhile, and the chance of breaking something else is low. [15:50] yes, and the application will apparently be partly broken anyway [15:50] jordi: will it work now? Or only after the upgrade of the servers [15:51] jesus [15:51] http://www.openttd.org/servers.php [15:51] everyone is running 0.6.0 already [15:51] and it was released yesterday [15:51] mok0: I guess it doesn't work anymore *today* [15:52] jordi: go ahead and make your case in a bug report. The release team will likely ask the same questions that we've done here on IRC, so put all that info there [15:52] should I report the bug against openttd, or what? [15:52] jordi: yes [15:52] jordi: Ubuntu -> openttd [15:54] jordi: openttd has ubuntu changes, so you need to ask for a merge [15:56] wtf [15:56] I had no idea [15:56] + * Merge from Debian unstable (LP: #181738). Remaining Ubuntu changes: [15:56] + - Add .desktop file. [15:56] jordi: it may just be dependencies or something [15:57] can be discarded, 0.6.0 includes one [15:58] jordi: if you can argue that a straight sync will work on Ubuntu, just do that in the bug comment [15:58] jordi: we want to get rid of as many ubuntu'isms as possible [15:59] jordi: why wtf? [16:00] james_w: I had no idea [16:00] but the added change made sense [16:00] I'm not sure if our desktop file came from the same person [16:00] it's not the same though [16:00] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460073 [16:00] Debian bug 460073 in openttd "Add .desktop file" [Minor,Fixed] [16:01] the person who made the change in Ubuntu reported that [16:01] ah, great [16:01] there's a couple of updates in the bug, so that may explain the difference. [16:01] jordi: do you know about the "derivatives" keyword in the PTS? [16:02] no, I don't know how it works [16:02] I regularly look for ubuntu diffs in the pts for some of my packages though [16:03] if you subsribe to that keyword on the PTS then you get a mail when an upload is made in Ubuntu for the package, with the diff attached. [16:03] mm, that's really interesting [16:03] I'll do that [16:03] because the ALSA diff is getting way too big [16:04] yeah, I was just about to say that we could probably use some help reducing that [16:06] I'd want the Ubuntu ALSA people to join the Debian ALSA team, which is suffering from lack of time [16:07] that would be good [16:07] I don't think there is an Ubuntu ALSA team though [16:08] crimsun: you appear to be the Ubuntu ALSA team, is that right? [16:09] jordi: I'd be happy to go through the patches with you some time to sort them out if you would like. [16:13] james_w: that'd be great [16:14] jordi: it's obviously not the best time right now, but after release when we look to merge with Debian again I'll get in touch, does that suit you? [16:15] james_w: totally [16:15] not the best time for me either :) [16:15] where would be the best place to find you? [16:15] I'll always be online in feenode and oftc, but pkg-alsa-devel@lists.alioth.debian.org should be the best place, so Elimar is also in the loop [16:15] he's doing most of the work lately [16:16] ah, ok. I'll note it down so I don't forget [16:17] it's the Maintianer for all the ALSA packages [16:17] hard to miss [16:18] yep, I meant more the fact that I have said I'll do it :-) [16:21] oh [16:21] :) [16:21] ok, so bug was filed [16:22] we'll see [16:25] jordi: thanks for taking an interest [16:25] james_w: no, you really [16:25] I see there are interesting ALSA fixes there [16:25] and minimising diffs is always good [16:26] yeah, I see there are a couple of things you may not want to take as they are pretty Ubuntu specific, and there are some things plucked from upstream, but yes, minimising them would be great. === pgquiles_ is now known as pgquiles === lmr__ is now known as lmr[lunch] [17:31] james_w: yeah, I was aware some things will stay as diff [17:31] but much of it can be merged [17:32] I'm sure it can. It would be great if we could also come up with a strategy to keep the ubuntu diff easier to manage as well. [17:32] but that's our problem, not yours really. [17:32] yep [17:32] we can help you by discussing new patches though. [17:33] yeah [17:33] I need to go now [17:33] let's talk after hardy [17:33] yep, I'll be in touch. [17:33] good luck, and thanks for the earlier advice! [17:33] thanks :-) [17:33] Could someone remind me how to check out a svn without the .svn folders? [17:35] jussi01: is it export? [17:44] james_w: thats sounds right... [17:48] james_w: thanks :) [17:50] jussi01: no problem === fta_ is now known as fta === \sh is now known as \sh_away === danielm_ is now known as danielm [18:55] I've got a package from old debian that hasn't been maintained in a few years. I've taken over maintenance of the project, and am trying to build an initial package for Ubuntu (as an experiment). Are there any differences in the debian/ files I need to worry about? [18:56] Looks like there is a new beta of firefox out. [18:56] Can I update the package on my hardy machine? [18:56] another beta of firefox? [18:56] wait patiently for an update? [18:56]