=== fta_ is now known as fta === gnomefre4k is now known as gnomefreak === santiago-ve is now known as santiago-ve-muri === santiago-ve-muri is now known as santiago-ve-hung === santiago-ve-hung is now known as santiago-ve === gnomefre2k is now known as gnomefreak [01:43] what's the preferred method of upgrading to the latest release? [01:43] someone was mentioning to be using the update agent with the -d flag or some such thing [01:43] I myself have always use apt-get [01:44] chillywilly: update-manager -d [01:44] chillywilly: Don't use dist-upgrade. [01:44] why not? [01:44] I did upgrade changing sources.list and then # aptitude update && aptitude full-upgrade [01:44] just like in debian [01:44] * chillywilly doesn't really like any of the apt front ends [01:44] other than good ol' apt-get === santiago-php is now known as santiago-ve [01:45] is apt-get dist-upgrade broken? [01:46] chillywilly: then use apt-get, but aptitude handles dependencies in a smarter way, say people [01:46] chillywilly: No, but it isn't guaranteed to work, and definitely won't work from Dapper. [01:46] this is gutsy [01:46] chillywilly, dist-upgrade can do some funky things. I'd recommend using update manager. [01:46] aptitude should work ok [01:46] We have do-release-upgrade and update-manager for a reason - their are quirks between Ubuntu releases that need to be handled by special rules. [01:47] +1 wgrant [01:47] ok then [01:47] ok, I'm a debian guy, so don't know those apps [01:47] rockstar_: You're a new LP guy, aren't you? [01:47] chillywilly, I was in the same boat. I come from the Debian world, and though a dist-upgrade would do. I learned the hard way it doesn't [01:47] neither did I [01:48] wgrant, yeah, bzr-lp [01:48] I've never had it "fail" on me... [01:48] chillywilly: It can do some funny things. And upgrading from Dapper it will definitely cause mass chaos with upstart and Python. [01:49] any documentation for do-release-upgrade? [01:49] well I was not aware of the "new" tools [01:49] it doesn't have a man [01:49] are they both GUI tools? [01:50] x1250: do-release-upgrade is all you need to know. [01:50] chillywilly: do-release-upgrade is the CLI version. [01:50] wgrant: no its not [01:50] I want to know more [01:50] Anyway, this isn't the place. [01:51] oh, probably #ubuntu-devel? [01:51] That's even worse. [01:51] You want #ubuntu. [01:51] hi, there [01:52] I just wanted to take a look at that special rules that can't be done by apt [01:52] or aptitude [01:52] i'd like to know the first steps to become a Ubuntu's developer [01:52] x1250: look at the source then [01:53] x1250: They're handled by the release upgrader tarball which is on archive.ubuntu.com and downloaded by do-release-upgrade, not do-release-upgrade itself. [01:53] ok, thanks wgrant [01:53] LeandroMattioli: https://wiki.ubuntu.com/UbuntuDevelopment, https://wiki.ubuntu.com/MOTU/Contributing [01:54] thanks crimsun [02:03] guys, anywhere i look, there will be: [02:03] before you start, read this... [02:04] where is the absolute start? [02:05] LeandroMattioli: what do seek? [02:05] do you* seek, rather [02:06] i want to understand the ubuntu development system [02:06] i'm not an experient programmer [02:06] LeandroMattioli: ok, and what do you mean by "ubuntu development system"? [02:07] i've studied a bit of C, Python and GTK, and I use linux as my O.S. since 2004, but i've never got envolved [02:07] i'm brazilian [02:08] LeandroMattioli: did you read the first URL? [02:08] its a lot of information, isn't there a page like that in Portuguese? [02:09] LeandroMattioli: did you try System> About Ubuntu ? [02:09] in the top panel of the GNOME menu if you use GNOME [02:09] let me see [02:10] no no, there isnt any information on contributing === gnomefre1k is now known as gnomefreak [02:11] LeandroMattioli: I think it will be best to start with https://wiki.ubuntu.com/MOTU/GettingStarted, then. Sorry, I don't think there are translations. [02:12] i have an account on launchpad, that is a good start, isn't it? [02:12] LeandroMattioli: yes, it's a good start. Please see https://wiki.ubuntu.com/MOTU/GettingStarted next. [02:12] ok [02:12] ill check [02:13] thanks for your patience [02:14] what about mentoring? [02:15] it seems its better to start with a mentor, right? [02:15] Heya gang [02:15] LeandroMattioli: I recommend the mentoring process, yes. [02:15] hi barry [02:15] Hi crimsun [02:16] LeandroMattioli: next week in irc we're having packaging sessions and how to get involved sessions [02:16] LeandroMattioli: https://wiki.ubuntu.com/UbuntuOpenWeek/ [02:17] hmm that's fine [02:17] LeandroMattioli: packaging 101 would probably interest you [02:18] of course, that's very important [02:18] i dont know C++ and OOP yet, is this a big problem? [02:33] evening [02:36] Hey LaserJock. [02:38] hi TheMuso [02:38] how's it going? [02:39] Very well thanks, got a public holiday in Australia today so am around, but not doing anything Ubuntu related. [02:40] nice [02:45] Heya LaserJock, TheMuso [02:45] hi Barry [02:46] Hey bddebian. [02:47] guys [02:47] hello [02:47] listen to this one alright.. [02:48] i have a tough choice to make i wanted to ask for opinion i have this htc touch right for me its an expensive device.. i was wondering do you think i could take the risk messing with it, in order to try linux or at least having it sync some way with the new ubuntu release.. or do you think i should leave it alone? do u think i would damage the device or not? bare in mind i dont want to buy a new one/afford a new one, the htc touch is a [02:48] what would you do? would you leave it alone or give it a shot? [02:52] grhluna: This is not a support channel. [02:53] im just looking for someone familiar with the ubuntu code thats all to help me to make the choice im not asking for support [02:53] That isn't a development question, so isn't relevant here. It is a support question. [02:54] if u know just drop me a message ok [03:15] The more this support stuff in here and -devel happens, the more I think #ubuntu is getting too busy for people to feel like they can get help and will get help. === santiago-php is now known as santiago-ve === boomer` is now known as boomer [04:02] Good evening everyone. [04:02] I'm still waiting for the flood of bugmail and not getting it. [04:02] ;-) [04:02] Hey ScottK. [04:02] There are many fewer bugs than I expected. [04:03] A lot of them being Kubuntu- or x86_64-specific. [04:04] So far I've seen exactly one new kde-guidance but since the RC and that turned out to be hal. [04:04] Heh. Good to see. [04:04] Greetings ScottK. [04:05] Considering displayconfig was substantially broken with the current Xorg, I think it's terrific. [04:05] Hey there TheMuso. [04:05] A remote fraction of the upgrade failures we had for Gutsy. [04:06] But I hate to think what'll happen once 8.04.1 is released and all Dapper folks upgrade. [04:06] Yeah. [04:06] So what's with the new nick? Get banned and have to hide? [04:32] ScottK: no, he must be working for canonical now, of course [04:32] TheMuso: it is. it's been like that for a while [04:33] Hobbsee: ?? [04:33] TheMuso: #ubuntu being too busy [04:33] ah [04:34] That's one theory. [04:35] or he's trying to get away from the painful guy last night, who has a similar nick. [04:35] Ah. [04:36] Hmm [04:36] Where do I find the list of packages blacklisted from being synced? [04:36] I'm trying to figure out why we don't have python-ldap-doc. [04:36] check p.u.c/~ubuntu-archiv [04:36] check p.u.c/~ubuntu-archive [04:37] ScottK: Decided it was time for a change, I guess. [04:38] That'd work too. [04:38] wgrant: pathetic [04:42] * wgrant rechristens Hobbsee. [04:47] wgrant: no. [04:47] Bah. [04:47] * Hobbsee also ditched her real name in multiple places last night [05:40] Good morning! [06:16] good morning [06:22] good morning [06:32] Guten Morgen dholbach [06:33] hi geser === boomer` is now known as boomer === asac_ is now known as asac [07:48] <\sh> moins [07:49] Hi \sh [07:50] Hey \sh. [07:51] <\sh> wgrant, nick change? how comes? :) [07:52] \sh: I'd been planning to do it for ages, and decided that at release was as good a time as any. [07:53] <\sh> hehe [08:42] reporting bugreports to debian is a pain in the a.. :( [08:48] <\sh> elmargol, claws-mail has a nice feature named templates ;) it helps /me never uses reportbug for debian actually [10:01] <_ruben> bah ... DKMS is scary stuff :p === _Czessi is now known as Czessi [10:11] <_ruben> hmm .. whats wrong with this changelog entry? megaraid_sas-dkms (v00.00.03.16) stable; urgency=low [10:11] \sh, can I have your template? [10:11] _ruben: stable? [10:12] <_ruben> jpatrick: its an auto-created entry by DKMS [10:12] <\sh> elmargol, sure...just send me an email pls, so I can reply this evening when I'm at home [10:13] <_ruben> bad syntax for version or so ? dont really have a clue myself :( [10:13] \sh, blaxhall.com? [10:14] Are versions starting with non-numerics valid? [10:14] I don't think they are. [10:14] <\sh> elmargol, write to sh@sourcecode.de :) [10:14] <_ruben> wgrant: that's what i was thinking .. lets see if i can fix that easily [10:15] mail is out [10:15] <\sh> elmargol, thx...I'll send it out this evening...when I'm home [10:16] _ruben: you can't have an underscore in package names [10:16] <_ruben> james_w: ah! [10:16] <_ruben> will change that as well then [10:32] can someone please test http://launchpadlibrarian.net/13886491/shell-fm_0.5-0%7Eppa0_i386.deb [10:32] seems to work for me [10:46] <_ruben> ok .. dkms is just too nasty .. time to move on, might try again later [10:53] _ruben: What makes you think there's something wrong with it? [10:54] _ruben: I'm not saying there's not, but I'm just wondering. [10:55] _ruben: I'm assuming the answer will be something like "Because foo tells the bar when I try baz". [10:55] _ruben: What are foo, bar, and baz? [10:56] <_ruben> soren: well, there's either something wrong with dkms and/or megaraid_sas, or im just too stupid to figure it out under my current workload [10:57] <_ruben> these servers need to be up and running asap, if i could sneak in the latest megaraid_sas driver it would've been nice, but it isnt a showstopper atm [10:57] _ruben: You're not really answering my question. [10:57] :) [10:58] <_ruben> soren: most likely because i dont fully understand your question :) [11:00] What makes you think it doesn't work? [11:00] I'm not saying it *does* work. It just helps if you answer that question (as stupid as it may sound). [11:01] _ruben: what did you try? what worked? what didn't work? where are you stuck? [11:04] _ruben: Usually, answers to that question have the general form: "Oh, because the X says Y when I do Z". X, Y, and Z happen to be very, very helpful pieces of information, hence the question. [11:11] <_ruben> soren: dkms fails to build a .deb file for various reasons .. some things i have worked around (specifying kernel source dir, etc), but working around the invalid changelog entry wasnt successful thusfar .. the megaraid_sas package probably has some hardcoded references to megaraid_sas, since even tho i renamed a fair amount of things to megaraid-sas, it still shows mention of megaraid_sas [11:12] <_ruben> soren: once i finished up configuring these 2 machines i'll give it a try in a clean environment to see if i can pinpoint some more [11:13] <_ruben> and the fact that dkms is originally aimed at RPM aint helping either :) .. you need to alien a driver downloaded from dell .. and using the resulting .deb you can get dkms to build another .deb which holds the actual driver :P [13:44] hi [13:45] How to merge using MoM and upload it onto my PPA? [13:45] !merge [13:45] Sorry, I don't know anything about merge - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi [13:45] bah [13:46] coolbhavi: https://wiki.ubuntu.com/UbuntuDevelopment/Merging [13:46] * persia doesn't understand merging to a PPA [13:47] * coolbhavi is a newbie in packaging so requires help badly [13:47] maybe explain what you're trying to achieve [13:49] or maybe allow us to have a break, seeing as the release was yesterday. [13:49] persia: trying hte merged package in a ppa, probably [13:49] Nah. Good to ask questions. Given that the release was yesterday, people may not answer. [13:50] Hobbsee: Maybe: I just don't see the point, given the possibility of a local build. [13:50] !merge is https://wiki.ubuntu.com/UbuntuDevelopment/Merging [13:50] I'll remember that, Amaranth [13:50] persia: that requires setting up a build environment. but yes [13:54] Ok was it wrong to ask questions? Then I'm sorry [13:55] coolbhavi: No. Good to ask questions: just realise that many people aren't likely to answer much, especially without further information about your ultimate goals. [13:55] hi [13:55] https://bugs.edge.launchpad.net/ubuntu/+source/ocsinventory-agent/+bug/217257 [13:55] Launchpad bug 217257 in ocsinventory-agent "package ocsinventory-agent 1:0.0.8-1 failed to install/upgrade: subprocess post-installation script killed by signal (Interrupt)" [Undecided,New] [13:55] what happens to packages which break the packaging system, ie, are uninstallable? [13:56] are those candidates for change in stable? [13:56] jordi: Very much so [13:56] !SRU [13:56] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [13:56] this is universe [13:56] jordi: that will be fixed in the auto-sync for the development release. [13:56] My aim is there is a new version of John the ripper in debian which has to merged into ubuntu so I m asking [13:56] jordi: Right. Same process, excepting subscribing motu-sru rather than ubuntu-sru. [13:56] jordi: It's certainly a candidate for an SRU [13:57] nod [13:57] good, because this one is annoying me :) [13:57] it's a pitty because I knew about this well before the release [13:57] but I'm swamped [13:58] jordi: yeah, that's a shame === __Czessi is now known as Czessi [13:59] It should have been in one our lists that is "RC bugs fixed in Debian but not in Ubuntu", but that list wasn't empty at release [13:59] it seems the diff from -1 to -2 should be ok for the SRU, perhaps with the debconf templates stripped, I'm not sure. [14:00] * persia notes that SRU submissions from that list are likely very welcome, and the SRU archives are the only ones accepting uploads right now. [14:00] persia: good point. [14:00] I can't remember what was in -3, but I would use that one [14:00] persia: is it possible to sync for an SRU? [14:00] james_w: ok, yes [14:00] james_w: the fix for this bug is in -3 [14:01] james_w: I suppose it might be, but manual upload to -proposed is likely better, given the preference for reversioning and reducing the changes to the minimal set to fix the bug. [14:01] jordi: ok, I'm pulling up the PTS now to investigate. [14:01] persia: ok, thanks. [14:01] james_w: http://snapshot.debian.net/archive/2008/04/13/debian/pool/main/o/ocsinventory-agent/ [14:02] jordi: thanks [14:02] it looks like we want the combined -2 and -3 diffs. [14:02] yes [14:02] I'm extracting a diff now [14:02] jordi: ah, you're on it, great. I'll go and have lunch instead :-) [14:03] cheers ;) [14:03] jordi: target hardy-proposed with an NMU version number if you didn't know already. [14:03] coolbhavi: Probably best to wait for intrepid to open to merge it. [14:07] james_w: hmm, I leave those details to yo [14:07] I need to go now, I hope I provided enough info [14:07] I thought a pull from Debian was possible here too [14:07] bye [14:07] jordi: sure, I'll subscribe, then I can tweak it. [14:44] hi folks [14:44] Hi sistpoty|work [14:44] hi geser [14:53] ScottK: btw.: imho we should get the audacious-crossfade plugin fixed ASAP. whom did you talk to to get permission for libitpp? [14:54] I talked to slangasek as it was pre-release. Now that we've released, I think it's up to motu-sru to decide. [14:54] ah, I see... [14:55] Hardy belongs to a different batch of bureacrats now. [14:56] Is the motu-release team staying on for intrepid, with new elections mid-cycle, or planning a shuffle early-cycle? [14:56] It should be discussed. [14:57] * ScottK has been pondering sending a mail to MOTU ML saying, "I'll be at UDS, is there anything for motu-release to do there?" [14:57] * ScottK had been thinking the team should have some role all the way through and not vaporise/re-appear. [14:58] imbrandon, jdong, TheMuso: can you give me an ACK to upload a rebuild only xmms-crossfade for bug #208666 to hardy-proposed? (mere rebuild is known to fix the problem) [14:58] Launchpad bug 208666 in xmms-crossfade "audacious crashed with SIGSEGV in g_type_check_instance_cast()" [Medium,Confirmed] https://launchpad.net/bugs/208666 [14:58] I'd like to see motu-release help triage some of the blueprints and outline some early targets for work to be done pre DIF, although I'm not sure any of the members will have time. [14:59] I'd be up for some of that, but I'd like for MOTU (at a meeting) to say we have that role. [15:00] let's put it on the agenda for tonights meeting, shall we? (at least to start the discussion there= [15:00] I don't see how motu-release identifying targets is restrictive of anyone else doing anything, or why that activity should be restricted to motu-release. [15:00] As a result, I don't think it needs a determination by MOTU. [15:00] ScottK: then i have to decide quickly if i want to be a part. hmmm. [15:00] On the other hand, I'd think the members of motu-release would be the natural interested party. [15:02] Hobbsee: I'd put it the other way. You are a part until you decide you don't want to be. You can always deactivate yourself when you want to. [15:02] ScottK: i meant MOTU generallly, but poitn taken. [15:02] More generally, I don't see the point of waiting until there is an "authorised" team in place before doing whatever, especially if it is unlikely to break someone else's workflow. If it's contentious, then yes, it needs discussion and agreement at a meeting. [15:02] persia: I don't think Universe has had release goals. [15:03] ScottK: I set some for hardy: didn't meet too many of them, but I think more of hardy builds than did for gutsy, as an example. [15:03] I had some for myself too. [15:03] Ah. Mine were for other people :) [15:03] heh, geser implemented on of mine (ghc6 transition) *g* [15:03] one even [15:04] Sure, I got help with mine too. [15:04] At a minimum we should have a mirror to a Main release goal that says "Get X out of Main" that says "Get X out of the archive" usually about one release later. [15:06] Someone might look at http://ftbfs.wordpress.com/2008/04/25/pyslide-story/ and see if we need an SRU. [15:06] ScottK: That sounds perfectly reasonable. I'd think that if you, or motu-release, or some random MOTU wanted to track those somewhere for people to push, it ought not require any specific authoirsation. If someone wants to preserve something, it's worth discussion, but in the absence of opposition, it ought just be done. [15:07] persia: Agreed. As I did for the python-xml transition in Hardy. But if I want "Because I'm in motu-release" to have any special meaning in the discussion, it needs to be agreed. [15:07] (deprecating python-xml made me sad.) [15:08] laga: It was needed. It's been largely duplicate to what was in python since 2.4. I'm not sure what the best answer for the not duplicate parts are. [15:09] I can see that point of view. Personally, I'd rather see self-organised teams (e.g. motu-release) take on responsibility organically, and avoid discussion until there is contention. As an example, I think both organisers of School have done well, and others have respected their opinions about School, without there ever being any formalisation beyond self-selection. [15:09] I just wish we'd decided on doing that one last October than in March. [15:09] persia: For something that's a separate project, that's perfectly fine. [15:09] motu-release affects all of universe. [15:10] It's a bit different. [15:10] Let's have a Release-planning session at UDS, run by someone in motu-release and identify things like python-xml that would be good targets, and submit for discussion. Unless there is objection by someone about one of the transitions, we oughtn't need to formalise anything. [15:11] Essentially, my feeling is that unless someone cares enough to ask about it, it's not worth having a rule that motu-release always wins, and if someone cares enough to object, the specific issue ought be discussed, rather than just a reference to motu-release planning. [15:14] sistpoty|work: if you wanted to meet your release goal on your own you should have told me :) [15:14] heh [15:14] geser: I wouldn't have been able to do that actually ;) [15:17] persia: Sounds generally reasonable. [15:19] ScottK: Note that if it doesn't work organically, I'm happy to support having a special blessing for motu-release identified release goals, but want to try it without as much process first, as I'd like to generally see more self-initiated things happening in MOTU. [15:19] Agreed. [15:21] persia: please make sure it's at a reasonable time for aussies. [15:21] if you can [15:21] * Hobbsee would like to see yada out of the archive. [15:21] hm... we really should start with SRUs for hardy now (even though these cannot be fixed for intrepid yet)... [15:22] Hobbsee: You're motu-release, and I'm not: you're in a better position to set the schedule for my suggested session to be run by motu-release :p [15:22] sistpoty|work: There's a bunch already processed: no reason not to push more :) [15:23] persia: is there? [15:23] persia: sure, but i won't be at UDS [15:23] persia: None in Universe since release. [15:23] ScottK: all the uploads to -proposed were for main? [15:24] persia: all but libitpp [15:24] persia: I've suggested to motu-sru that they relax the "Must be fixed in the development version first rule", but no word. [15:24] sistpoty|work: And one mythbuntu one. [15:24] Both uploaded before the release. [15:24] oh, must have missed that one [15:24] Ah. Right. I guess it needs the SRU team to jump up and do. [15:25] have a great weekend everybody - enjoy the celebrations [15:25] Yes. I've pointed a couple of them at it, but that's all I can do. [15:25] cya dholbach === cpro1 is now known as cprov [15:30] Hobbsee: I'm not sure the chair can't be from VoIP, but understood. Maybe someone else will volunteer, but I'll mention that morning is better, if asked. [15:31] persia: it's mroe the fact that if it's at 4am local, i won't be there. [15:32] Hobbsee: Right. Has to be before lunch, if I remember Sevilla correctly. [15:32] for a SRU, i should subscribe motu-sru, right? [15:32] laga: If the package is in universe, yes. [15:33] persia: something like that [15:34] done, thanks. [15:51] * sistpoty|work gets impatient and sent a mail to -motu about SRUs :) [15:52] huhu sistpoty|work [15:52] hi sebner === gnomefre1k is now known as gnomefreak [16:09] superm1: Bug #218649 looks mythtv related, so would you please take a look at it. [16:09] Launchpad bug 218649 in fusion-icon "fusion-icon crashed with SIGSEGV in XChangeProperty()" [Undecided,New] https://launchpad.net/bugs/218649 [16:09] sistpoty|work: you got your ACK [16:09] thanks jdong [16:09] what was the outcome of that large discussion yesterday on SRU policy? [16:10] jdong: It awaits a decision from internal discussion amoung motu-sru [16:11] ah [16:11] * jdong looks at his mailbox [16:11] ScottK, not to me. it looks like they have a disk with an invalid partition table that is causing areas of concern [16:11] * persia hopes for a repeat of the early SRU policy with all updates going into intrepid the day the archive opens [16:12] superm1: THanks. [16:12] I just saw myth stuff in the log and am to tired to think much further. [16:13] superm1: Would you be up for marking that in the bug (if you haven't already)? [16:13] oh already did :) [16:13] just letting you know since you probably weren't subscribed [16:13] Thanks. [16:13] I am actually (I get bugmail for most all Python packages). Thanks. [16:13] superm1: i filed an sru for mcc [16:13] yup [16:14] okay good laga [16:16] persia: I already wrote a mail to -motu, but it's currently in the moderation queue (maybe some list admin might want to whitelist my work address? *g*) [16:16] * persia thinks that would be a good idea, and wonders if one of the listadmins is about [16:32] I found a bug in smstools.... /var/run/smstools folder isn't recreated after reboot... How are those things usualy handled? [16:32] CrippledCanary: via a bug report. [16:32] made it already... thought I'd make a patch as well :) [16:32] https://bugs.edge.launchpad.net/ubuntu/+source/smstools/+bug/221973 [16:32] And by having the program check for the existence of the file before writing to it, and generating the necessary directory if it is not present at runtime. [16:32] Launchpad bug 221973 in smstools "smstools folder under /var/run isn't recreated after reboot" [Undecided,New] [16:33] thats my bug [16:33] is there a best practise on where to put those thinds... i'd guess somewhere in the init.d/smstools script [16:33] https://bugs.edge.launchpad.net/ubuntu/+source/smstools/+bug/135033 should be checked and fixed at the same time I guess [16:33] Launchpad bug 135033 in smstools "wrong ownership of /var/run/smstools" [Undecided,New] [16:34] CrippledCanary: yep, that's exactly where it should go. [16:34] if you can provide a patch that would be fantastic. [16:35] will start working on it right away [16:35] thanks [16:35] CrippledCanary: do you know how to make a debdiff? [16:35] yes I know [16:35] even better :-) [16:35] i know how to make packages to (if not to complex) [16:36] so a attached debdiff is the prefered way to do it then [16:37] how should I handle 135033... it will get fixed at the same time... mark as duplicate or ? [16:37] CrippledCanary: An attached debdiff with all the changes that would make for a new revision. Right now, only SRUs are being considered, so the target ought be hardy, and it needs to go through the SRU process. [16:37] Once intrepid opens, a new revision closing all the outstanding bugs in LP would be great :) [16:38] i don't think i have the time to do more then a patch right now... but how should i mark the other bug that will get fixed at the same time? [16:38] persia: "target ought to be hardy", is it not hardy-proposed, or did you mean target in a looser sense? [16:39] Err, Actually reading the bug, I suspect both are SRU worth on the basis of "completely fails to work". [16:39] persia: yeah, I agree [16:39] true [16:39] hardy-proposed [16:39] james_w: debian/changelog target is hardy. dput target is hardy-proposed. [16:39] ScottK: in debian/changelog? [16:39] persia: I usually just put hardy-proposed in the changelog [16:39] ok [16:40] Ah. I thought we weren't supposed to do that anymore (but I haven't done an SRU in quite a while) [16:40] * ScottK defers to the documenation [16:40] !SRU [16:40] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [16:40] It's the version numbering for proposed we weren't supposed to do anymore. [16:41] The documentation seems to indicate to use release-security, but I'm sure that's unintentional. [16:43] ok... creating a patch will have to wait until tomorow for me.... don't have time right now [16:46] can someone go over https://answers.edge.launchpad.net/ubuntu/+question/30700 please I was told to come here if I had further questions [16:47] z1o: you could always be helpful and put the patch up there yourself. [16:48] Hobbsee: I dont have a patch the current patch should be pushed upto the upstream provider. [16:48] z1o: then...push it? [16:48] z1o: Ubuntu hasn't modified that package, so no-one will have touched it to push it upstream. [16:49] well that packaged does not build without out the patch.. do I have to to throught the patch to figure out what bug it fixes ? [16:49] * Hobbsee wonders if coolbhavi has alwasy been that unhelpful on questions [16:52] z1o: this package is directly import from debian/unstable w.o. changes (i.e. with only a new entry in debian/changelog). You might want to ask there. [16:52] z1o: do you have a build log that shows the problem? [16:53] james_w: my point is that its a diservice to not talk to the jade maintainer and fix the actual bugs [16:53] z1o: yes, and I agree. [16:53] z1o: Sure, but that package has not been inspected or modified by anyone in Ubuntu, so it oughtn't be very surprising that the patch wasn't sent upstream by anyone in Ubuntu. [16:54] I'm not sure how debian to ubuntu packages work. [16:55] z1o: also, if the Debian revision is -47 it suggests that the upstream doesn't release very often [16:55] z1o: In most cases, Ubuntu builds the Debian source package automatically. [16:55] Heya gang [16:55] hi bddebian [16:55] Hi sistpoty|work [16:56] persia: great but someone must be responsible for maintaining it? [16:56] Hobbsee: yeah I'm also concerned by coolbhavi's response to that answer tracker ticket [16:56] z1o: Neil Roeth [16:57] z1o: that's the Debian maintainer. [16:57] z1o: Not specifically. As a team, the developers are responsible for all the packages, but we've about 200 developers and about 12,000 packages, so some don't get any attention. [16:57] jdong: well, the reason he got membership, apparently, because the guys didn't think they could veto it, form the loco [16:57] In most cases, we rely on the Debian maintainers, and only make changes where there is a bug that we fix, or there is some difference between Debian and Ubuntu that needs working around. [16:58] Hobbsee: I seem to recall that his membership is primarily from his work on the answer tracker... perhaps in his quest for karma points he's gotten rushed at responding [16:58] personally I've already put alot of time into this. it looks like I'll find what the patch fixes and post a bug to http://www.jclark.com/jade/ [16:58] Hobbsee: looking through his replies on the tracker it seems like a lot of the responses are "canned" or otherwise contextless [16:58] jdong: probably.... [16:59] jdong: i doubt they have a membership revoker. i wonder if they have a catalyser for the tracker, even. [16:59] z1o: thankyou [16:59] are you talking about the same question here? [17:00] Hobbsee: "and please close this question before doing so" [17:00] Hobbsee: it's those kinds of responses that concern me :-/ [17:00] yes.... [17:00] Hobbsee: https://answers.edge.launchpad.net/ubuntu/+source/gcalctool/+question/30347 the filer was markedly unhappy at the remark [17:01] anyways... thanks for the help [17:06] jdong: i guess you'd have to take it up with the CC or something === sistpoty|work changed the topic of #ubuntu-motu to: https://wiki.ubuntu.com/MOTU | Want to get involved with the MOTUs? https://wiki.ubuntu.com/MOTU/Contributing | MOTU Meeting tonight at 20.00 UTC in #ubuntu-meeting [17:09] hm... I guess "tonight" is not the best word for a global community *g* === gnomefre1k is now known as gnomefreak [17:15] sistpoty|work: ähm. Stupid question. what does 20 utc is in our time? xD [17:15] 19:00 [17:15] Err. 18:00 (Stupid clock changing laws) [17:16] persia: that would mean it's *now* [17:16] sebner: use your date command :) [17:16] Oh. Then you're not in the timezone I thought you were in :) [17:16] for example, date -d 20:00UTC [17:17] jdong: coooooooll [17:17] persia: np [17:17] grml. utc+2 :\ [17:19] sebner: hence I wrote "tonight" :P [17:19]