[00:01] <fernando2> _16aR_: into upstream author
[00:03] <_16aR_> argh, someone just told me the inverse
[00:04] <_16aR_> and to put the original maintainer of the project into upstream author
[00:06] <fernando2> in Copyright: you need to put all copyright licenses of the source code
[00:14] <Megaqwerty> Quick question: Does anyone know how I would get dput to work through a proxy?
[00:15] <fernando2> Megaqwerty: export http_proxy and ftp_proxy vars
[00:15] <Megaqwerty> fernando2: could you give me an example of the ftp_proxy var? (I know the http_proxy one is already set by Sys>Prefs>Network Proxy)
[00:16] <Megaqwerty> fernando2: nvm, found an example on Google
[00:16] <fernando2> Megaqwerty: export http_proxy='http:/user:pass@<IP_ADDRESS>:3128"
[00:17] <fernando2> =)
[00:17] <fernando2> ftp_proxy follow same syntax
[00:19] <fernando2> gn
[00:24] <lamego> _16aR_, by providing a patch the persons does not get copy rights over the entire source, unless the patch itself includes contents using a different copyright owner, on that case, yes you should list it on the copyright section also
[00:25] <lamego> but I guess, a 1 line patch will not be copyrighted :)
[00:27] <RAOF> Or is probably not copyrightable.
[01:02] <nixternal> umm, I have just brainfarted, who do I subscribe again for a sync request? :)
[01:03] <soren> You're motu?
[01:03] <soren> Sorry, I forget.
[01:03] <nixternal> ya
[01:03] <soren> ubuntu-archive
[01:03] <nixternal> ahh, I was right..thanks
[01:03] <soren> np
[01:27] <bmk789> hey persia: i got your email on the MOTU list and i was wondering if there was anything i could do (without programming or packaging experience) to contribute to hardy development
[01:27] <bmk789> i do have a powerful server with some bandwidth to spare
[01:28] <persia> bmk789: In terms of contributing to development, the best way is really to work on code or packaging.  In terms of supporting the development effort, there's a fair bit that would be helpful.
[01:29] <persia> One thing that needs doing is to run the piuparts installation checker after the freezes.  Dktrkranz is currently estimating time requirements, and might be a good person to ask about how more servers / bandwidth could help.
[01:30] <persia> There's also some documentation things that would be helpful.  One is looking at the list of software not in Sid from http://people.ubuntu.org.au/~fujitsu/motuscience/versions/universe.html, and discovering if there is a new upstream version available.
[01:32] <persia> Another would be looking for software in the repository for which there are multiple versions (e.g. autoconf, python, wxwidgets, GTK, etc.).  Lists of software that needs to be adjusted, along with pointers to migration guides could be useful.
[01:32] <Fujitsu> Hm, I wonder if it might be a good idea to turn MDT's notes feature on (displays comments per-package from a wiki page).
[01:32] <persia> Fujitsu: That might be useful.  We'll need documentation on the comment format on the wiki page :)
[01:32] <Fujitsu> I think the old wiki page is still there, even.
[01:33]  * Fujitsu looks.
[01:33] <Fujitsu> It would be nice to have an mdt page in the style of ajmitch's RC bugs list, with a dynamic comment function.
[01:33] <bmk789> thanks persia, ill look into those
[01:33] <ajmitch> yes, I was looking at doing that when I revamped the bug list
[01:34] <ajmitch> since the code for the bug list is partially shared with something ti did along the same lines of mdt
[01:34] <Fujitsu> I guess it would be, yeah.
[01:34] <ajmitch> I'm also moving hosting of it off my home system :)
[01:34] <persia> bmk789: And just because it's often forgotten: one of the best ways to support the developers is to look over the bug lists, and try to consolidate the various reports into only those for which we can prepare a solution.
[01:34] <persia> ajmitch: Do you have a hosting site already organised?
[01:34] <bmk789> i see
[01:34] <ajmitch> persia: I think so
[01:35] <persia> ajmitch: Excellent.  I look forward to not feeling guilty about polling :)
[01:36] <nixternal> hrmm, I don't remember piuparts running so slow in the past
[01:36] <ajmitch> persia: yeah, it's a large page, and a slow DSL line
[01:37] <persia> nixternal: How long do you think it should take to install/uninstall 20,000 packages?
[01:37] <nixternal> I am not install/uninstall 20,000 packages, I am just doing 1
[01:37] <Fujitsu> Will piuparts use sbuild if it's available? That should speed things up significantly.
[01:38] <Fujitsu> s/sbuild/schroot/
[01:39] <ajmitch> nixternal: buy some 15K RPM hard drives & use them with a decent hardware RAID controller
[01:39] <nixternal> it will use pbuilder if you tell it
[01:39] <ajmitch> then piuparts should be faster
[01:39] <nixternal> sure, I will go do that right now
[01:39] <Fujitsu> 15k SAS drives are nice and fast. Particularly in RAID10.
[01:46] <LaserJock> we replace iceweasel references with firefox right?
[01:47] <Fujitsu> LaserJock: And hope it works, yeah.
[01:47] <persia> LaserJock: Generally, but you might want to check with the #ubuntu-mozillateam folks, given that we also like gobuntu these days
[01:47] <Fujitsu> We've only got a couple of packages broken because of that, IIRC.
[01:47] <LaserJock> hmm, I wonder if an | would work
[01:48] <LaserJock> right now I've got Depends: ${shlibs:Depends}, iceweasel | iceape-browser | xulrunner
[01:48]  * persia thought that should work unmodified, given xulrunner in hardy
[01:48] <LaserJock> but will that work for Firefox?
[01:49] <persia> Isn't the plan for firefox to either provides: or depends: xulrunner?  I forget.
[01:49] <Fujitsu> Firefox 3 will be using xulrunner, but it won't work for current Firefox
[01:49] <Fujitsu> persia: The latter.
[01:49] <persia> Fujitsu: Hardy will have Firefox 3 by default, no?
[01:49] <Fujitsu> persia: Presuming it will be released in time.
[01:49] <Fujitsu> So we will soon be able to remove firefox without the world exploding :D
[01:50] <persia> Hrm.  Someone should get an official opinion from the mozilla team
[01:50] <Fujitsu> Yeah.
[01:50] <Fujitsu> Probably asac, really.
[01:50] <persia> Fujitsu: It may be that there is already an official opinion, and we just don't know, so others could also share.
[01:52] <RAOF> You probably want xulrunner-1.9 for the depend, don't you?
[01:52] <Fujitsu> True, that's what Gran Paradiso uses.
[01:53] <persia> RAOF: Why?  Are there currently two versions of xulrunner shipping?
[01:53] <RAOF> persia: Yes; xulrunner (which is 1.8 or 1.7) and xulrunner-1.9
[01:53] <Fujitsu> xulrunner is 1.8, xulrunner-1.9 is 1.9.
[01:54] <persia> Right.  Goal for next release (hardy+1): transition everything and watch it break :)
[01:54]  * ajmitch cheers
[01:54] <RAOF> I thought that was a _Hardy_ goal
[01:54] <ajmitch> Fujitsu: do you want me to spend time on something for replacing mdt?
[01:54] <RAOF> Since nothing currently depends on xulrunner, 'cause it does'nt work.
[01:54] <Fujitsu> persia: Transition what? Only a Java plugin depends on 1.8.
[01:55] <persia> RAOF: I doubt main will make it, and I'm certain universe won't.  We'll transition a lot, but hardy is more about things working than pushing the newest, shiniest code.
[01:55] <Fujitsu> ajmitch: If you want to, or I could try to post-exams.
[01:55] <LaserJock> the plan for Edubuntu was to ship Epiphany for hardy
[01:55] <LaserJock> no Firefox
[01:55] <ajmitch> well I've already got a steaming pile of code here to revive if it's needed
[01:55] <Fujitsu> persia: A goal for Hardy is moving things off firefox and onto xulrunner-1.9.
[01:55] <persia> Fujitsu: If it's just one package, why is there versioning for a transition plan?  That's just silly.
[01:55]  * RAOF doesn't know, either.
[01:56] <Fujitsu> persia: I guess to avoid messing with the package from Debian.
[01:56] <persia> Fujitsu: Right.  I meant *everything*, as in finish all the transitions in progress, and then spend four months trying to fix the resulting mess.
[01:56] <Fujitsu> Ah.
[01:56] <LaserJock> but I need to figure out what to do with Gutsy so xulrunner is no help ;-)
[01:56] <persia> (definitely a hardy+1 goal - hardy shouldn't be that broken)
[01:56] <Fujitsu> LaserJock: What are you doing to Gutsy?
[01:56] <persia> LaserJock: ping asac: he should have an answer you can trust.
[01:57] <LaserJock> Fujitsu: lots of things ... mwuahahahaha
[01:57] <persia> LaserJock: Ah, for gutsy, yes.  Firefox is the answer.
[01:57] <LaserJock> Fujitsu: gnome-chemistry-utils/gchempaint
[01:57] <Fujitsu> LaserJock: Ah, messy.
[01:58] <LaserJock> tell me about it :-)
[01:58] <LaserJock> I spent the morning trying to figure out how to build stuff with static libs and misc other things
[01:58] <TheMuso_Boston> Heya folks.
[01:58] <Fujitsu> ajmitch: A dynamically-generated, commentable, not-so-ridiculously-slow, likely more flexible mdt-like thing would be very useful. Particularly the commenting bit.
[01:59] <Fujitsu> Hi TheMuso_Boston.
[01:59]  * persia seconds the call to ressurect ajmitch's super-mdt
[01:59] <Fujitsu> versions2html is soooo slooow.
[01:59] <LaserJock> Fujitsu: and in ruby
[01:59] <LaserJock> which wasn't helping me
[01:59] <ajmitch> Fujitsu: ok
[01:59] <Fujitsu> LaserJock: I'm fairly sure those things are interdependent.
[02:00] <ajmitch> not so sure about the 'dynamically-generated' bits though :)
[02:00]  * Fujitsu hacked it up a bit, even without any ruby experience... didn't break it tooo badly.
[02:00] <ajmitch> it could be expensive to do the version comparisons each time the page is displayed
[02:00] <Fujitsu> ajmitch: What do you mean?
[02:00] <persia> ajmitch: dynamically-generated commenting, etc.? perhaps.  The raw data process might only refresh less often.
[02:00] <Fujitsu> ajmitch: Oh, I didn't mean like that.
[02:01] <ajmitch> the rc bug list is a combination of processing a text file generated by a separate script, and comments stored in the DB
[02:01] <Fujitsu> Just something better than the current comments system which scrapes from a wiki page hourly and gets caught in the next versions2html.
[02:01] <ajmitch> I'd probably do the same
[02:01] <ajmitch> ouch :)
[02:01] <ajmitch> yes, that's easy to fix
[02:01] <persia> ajmitch: The same as rcbugs would be a vast improvement over the current.
[02:01] <ajmitch> I'm just trying to get mysql to cooperate on this system
[02:02] <ajmitch> it'll have to sit in the queue behind a plone site that I have to get done ASAP
[02:02] <ajmitch> hopefully not too far away
[02:02] <Fujitsu> ajmitch: Thanks.
[02:06] <bddebian> Hmm, I assume pitti is asleep at this time of day?
[02:06] <Fujitsu> bddebian: He'd be in Boston, so probably not quite.
[02:07] <Fujitsu> Gr, lintian is really annoying if the process gets interrupted mid-run. It doesn't bother to check what it has done when you restart it, so you need to manually mangle its status files to get it to redo the bits it missed.
[02:14] <ajmitch> persia: does http://motu.ajmitch.net.nz/rcbugs/ load any faster for you?
[02:15] <Fujitsu> ajmitch: Fairly high latency still, but a lot faster.
[02:16] <persia> ajmitch: Not noticeably, but I suspect that's a combination of Safari having a slow renderer and my not having loaded the previous page recently enough to be sure of my memory.
[02:16] <ScottK> ajmitch: Seems faster to me than I remember before the Gutsy release.
[02:16] <ajmitch> it's in the US
[02:16] <ajmitch> it'd be hard to be slower, I think
[02:16] <ScottK> That would likely help me...
[02:16] <Fujitsu> wget says 3 times quicker.
[02:17] <ajmitch> the DB has just been copied, and this will probably be just for testing for now
[02:17] <ajmitch> so don't rely on stuff to stay around
[02:17] <persia> ajmitch: Is that still targeting Gutsy?
[02:17] <ajmitch> yes
[02:17] <ajmitch> I just copied stuff for now
[02:18] <ajmitch> nothing more
[02:18] <persia> Ah.  Good.  I was worried that the syncs somehow weren't including the bugs.
[02:19] <ajmitch> a minor rework of the code & I'll have lists for whatever distro
[02:25] <persia> ajmitch: That would be extra cool for the SRU team.
[02:25]  * persia wonders who is a good contact for the SRU team
[02:26] <Fujitsu> persia: There isn't such a team any more, is there?
[02:26] <persia> Fujitsu: Well, there should be :)
[02:27] <persia> e.g. someone should claim responsibility for trying to keep the current release working
[02:29] <ajmitch> so a team of people to do stuff, rather than just approve
[02:29] <Fujitsu> Like we're meant to have for security, but motu-swat is sorta dead.
[02:29] <ajmitch> but being revived a bit
[02:29] <persia> ajmitch: Well, maybe do stuff, but more 1) maintain a current release system to test things, 2) watch an RC bug list against the release system, 3) oversee and coordinate SRU efforts.
[02:30] <Fujitsu> Hopefully, particularly with testing-security.
[02:30] <tonyyarusso> Is it?  I subscribed motu-swat to a bug recently, and I'm pretty sure it got taken care of.
[02:30]  * tonyyarusso checks
[02:30] <persia> Fujitsu: Is that what motu-swat was?
[02:30] <Fujitsu> persia: motu-swat was for universe security updates.
[02:30] <Fujitsu> Now that Debian tracks and handles security issues in unstable/testing, it makes that sort of thing easier.
[02:31] <persia> Fujitsu: Ah.  security only.  I was thinking security + "cannot install", "segfault on start", "breaks on upgrade", etc.
[02:31] <ajmitch> "munches my system"
[02:32]  * Fujitsu takes a bite out of ajmitch's system(s).
[02:32] <bddebian> hehe
[02:32] <tonyyarusso> yeah, bug #155990 - someone caught it
[02:32] <ubotu> Launchpad bug 155990 in drupal5 "Several security updates and bugfixes in Drupal 5.3" [Undecided,Fix released] https://launchpad.net/bugs/155990
[02:32] <nosrednaekim> is there a compiz team?
[02:33]  * persia thinks it's called something like desktop-effects
[02:33] <ajmitch> crack-fiends
[02:33] <bddebian> hehe
[02:34] <nosrednaekim> becase THIS so called "addict" wants some more compiz packages
[02:34] <ajmitch> great
[02:34] <persia> nosrednaekim: Best way to get them in is to package them
[02:34] <nosrednaekim> yeah, wellI have dial-up and so I can't do packaging very well
[02:36] <tonyyarusso> Hey guys, lamalex and Zelut are interesting in getting their feet wet in packaging-land, so you'll probably see them around a bit, and if you have time to offer some instruction/guidance give 'em a nudge.  :)
[02:36] <lamalex> indeed I am
[02:36] <persia> lamalex , Zelut: welcome.
[02:37] <Zelut> I've been lurking here a few days since UDS started.. just need to find some time
[02:37] <persia> For people interested in starting, I'd recommend looking at https://launchpad.net/ubuntu/+bugs?field.tag=packaging.  It's a nice list of how not to do things, and finding the solutions allows one to learn one thing at a time.
[02:38] <tonyyarusso> hehe, persia's making you learn and fix bugs at the same time!
[02:38] <tonyyarusso> crafty
[02:38] <tonyyarusso> Seriously though, it's a good point.
[02:39] <persia> tonyyarusso: Not "making".  Also, I think it's easier to fix a package that mostly works instead of trying to start from scratch.
[02:39] <tonyyarusso> persia: true
[02:39] <Fujitsu> It's also of larger benefit to fix existing ones.
[02:40] <Fujitsu> Because they're likely to be used, and don't cause a large maintenance burden afterwards.
[02:40] <bmk789> night everyone, thanks for the help persia
[02:40]  * Fujitsu cringes at 639 Ubuntu-specific packages.
[02:40] <ajmitch> Zelut: good, you can take over the selinux stuff then
[02:41]  * ajmitch can give up on it for good
[02:41] <Fujitsu> Hi Hobbsee.
[02:41] <persia> Fujitsu: I was thinking, do they all have watch files?  If so, perhaps they're not so bad...
[02:41] <Jazzva> TheMuso, TheMuso_Boston: I was looking at merges and I noticed that you are the uploader of axel. Is it ok if I submit this merge?
[02:41] <Fujitsu> persia: Do any of them have watch files?
[02:41] <Hobbsee> hiya
[02:42] <Fujitsu> I wonder if I can pipe that list into DEHS...
[02:42]  * persia thinks requiring watch files should be a REVU approval requirement
[02:42] <Zelut> ajmitch: heh, I'll do docs and testing but that might be a bit greedy yet
[02:42] <Fujitsu> persia: That's a good idea.
[02:42]  * persia goes to find the wiki page to make it official
[02:42] <ScottK> persia: Why?
[02:42] <ajmitch> Zelut: nah, you've been soloing selinux so far, go for it
[02:42]  * Hobbsee curses disappearing irssi and screen sessions.
[02:42]  * ScottK is gonna disagree.
[02:42] <nosrednaekim> Zelut: are you not the guy who does ubuntu-tutorials?
[02:43] <ajmitch> hey Hobbsee :)
[02:43] <persia> ScottK: So that we have some chance of identifying packages that need a refresh early in the cycle when we're not synchronising from Debian
[02:43] <Hobbsee> hi ajmitch!
[02:43] <Zelut> nosrednaekim: I am
[02:43] <ScottK> persia: OK.  Got it.
[02:43] <TheMuso_Boston> Jazzva: I didn't touch it.
[02:43] <TheMuso_Boston> I only uploaded it.
[02:43] <nosrednaekim> Zelut: loved your latest article, but thats a bit off-topic :)
[02:43] <ScottK> persia: I missed the distinction between requiring it for packages and requiring it for new packages we weren't getting from Debian.
[02:44] <Zelut> ajmitch: hopefully the ubuntu-hardened list keeps picking up and we can get the policy working.. then I'll think about it.
[02:44] <ScottK> persia: I do think that a process change must be agreed at a MOTU meeting though.
[02:44] <Zelut> ajmitch: selinux has a way to go before its functional.. we had a sprint at UDS about it this week.
[02:44] <ajmitch> yes, I know you did
[02:44] <persia> ScottK: Ah.  Sorry about that.  I'm just thinking the REVU guidelines: the other 13,000 packages should have one, but it's not as important.
[02:44] <Zelut> nosrednaekim: thanks, glad to hear people still read the blog :)
[02:44] <persia> ScottK: You're right.  I'll add it to the agenda.  Thanks for the reminder.
[02:44] <TheMuso_Boston> Jazzva: As in, I only sponsored the upload for someone else.
[02:44] <Fujitsu> Debian is getting watch files progressively - a lot do have them.
[02:45] <ScottK> persia: For REVU, I agree.  Good.
[02:45] <ScottK> persia: One of my goals for involvment in this cycle is to be a hardass about unagreed process change.
[02:46] <ajmitch> joy
[02:46] <persia> ScottK: I appreciate that.  Having someone watch the process change and make noise helps my goal of ensuring there is sane and progressive process change.
[02:47] <Jazzva> TheMuso_Boston: I see... I'll ask the person last mentioned in the changelog then :). Thanks.
[02:47] <TheMuso_Boston> Jazzva: No problem.
[02:47] <ScottK> For those interested in watch files (persia and maybe Fujitsu) you might enjoy reading lamont's rationale for won't fixing the please add this watch file for postfix.
[02:48] <persia> ScottK: reference pointer?
[02:48]  * ScottK looks
[02:48] <Fujitsu> persia: What is your opinion on packages like bkp?
[02:48] <Fujitsu> (note last upload, and popcon)
[02:48] <Fujitsu> (and not being in Debian)
[02:49]  * persia is bothered by the lack of an Ubuntu platform, and hunts
[02:49] <ScottK> https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/129316/comments/7
[02:49] <ubotu> Launchpad bug 129316 in postfix "New watch file" [Undecided,Won't fix]
[02:49] <ScottK> persia and Fujitsu ^^^
[02:49] <Fujitsu> persia: Ubuntu platform?
[02:49] <Fujitsu> ScottK: Thanks, looking.
[02:50] <Fujitsu> ScottK: That reason isn't valid for most of our Ubuntu-specific packages, which don't have a maintainer (or anybody at all) watching over them.
[02:50] <ScottK> Fujitsu: Agreed.  I just thought it was an amusing counterpart to the watch file parade.
[02:50] <persia> Fujitsu: My current client is an Apple shop, and requests onsite presence.  As a result, I am limited.
[02:51] <Fujitsu> ScottK: Yeah.
[02:51] <Fujitsu> persia: Oh, lovely.
[02:55] <persia> Fujitsu: That's why we need watch files.  Compare with http://opensource.polytechnique.org/debian/bkp_0.6.3-2.dsc
[02:56] <Fujitsu> persia: Yeah, i saw that yesterday, but do we even want to keep it? Nobody uses it, and nobody has complained that it's three years out of date.
[02:57] <Fujitsu> We can maintain the extra packages, or remove them if nobody uses them and there's little benefit. The latter is more efficient.
[02:57] <persia> ScottK: Actually, when a maintainer is as active as postfix's, I don't mind that attitude.  This is especially true for packages well maintained in Debian.  On the other hand, for leaf packages in universe with maintainer as MOTU, I demand watch files as otherwise we forget.
[02:57] <ScottK> persia: I think that makes complete sense.
[02:57] <persia> Fujitsu: I agree, but I don't trust popcon.
[02:59] <persia> Fujitsu: I think the policy for when to dispose of Ubuntu-only stuff likely needs some definition.  It might be nice to also apply those criteria when accepting new random stuff.  Personally, I'd like to see a very small amount of REVU activity that wasn't linked to some active external community.
[02:59] <Fujitsu> persia: Right, same with me.
[02:59] <Fujitsu> We do need a policy, or we accumulate enormous amounts of unmaintained... crap.
[03:00] <persia> Fujitsu: If you have some ideas for such a policy, raising them for the 9th November meeing might be a good time: we'll only have had one REVU day, so people shouldn't be too in practice :)
[03:00] <ajmitch> what time is the meeting on the 9th?
[03:01] <persia> ajmitch: 20:00 UTC
[03:01]  * TheMuso_Boston should send out a reminder...
[03:01] <ajmitch> ah, 9am on the saturday morning
[03:01] <ajmitch> I may be awake if I'm lucky
[03:01] <persia> TheMuso: So soon?  I'd wasn't expecting one until this weekend.
[03:01] <Fujitsu> 7am on Saturday, should be doable.
[03:01] <persia> It's 5am here, which is annoying
[03:01] <bddebian> yikes
[03:02]  * persia tends to go to bed early before such meetings
[03:03] <TheMuso_Boston> persia: Well, yes, and I'll do one mid next week.
[03:04]  * persia thanks TheMuso_Boston for dedication to the MOTU Meeting process
[03:05] <TheMuso_Boston> persia: As much as I don't always enjoy doing it, I do it because it ensures that it gets done, and announcements are sent out, etc.
[03:05] <ajmitch> uh oh
[03:05]  * ajmitch hides from the LongPointyStick
[03:05] <persia> TheMuso_Boston: That's why you got a "Thank you".  If you enjoyed it, we'd all just think you were a bit odd.
[03:05] <TheMuso_Boston> persia: ah ok.
[03:06]  * persia suspects there is painful prodding happening somewhere else
[03:06] <TheMuso_Boston> persia: yet at the same time, I don't want people to start assuming I'll do it.
[03:07] <persia> TheMuso_Boston: You keep volunteering first :)
[03:07] <bddebian> heh
[03:07] <TheMuso_Boston> Yeah I know, but I don't want people to start thinking "Luke will do it, I need not worry"
[03:08] <TheMuso_Boston> persia: If you have noticed, I have been saying lately that I'll do it if nobody else wants to.
[03:08] <LongPointyStick> persia: no, there probably will be in future.
[03:08] <persia> TheMuso_Boston: I don't think you need worry.  At least I'll do it if I'm attending and you don't.  Further, there are usually other volunteers when you don't make it.
[03:08] <TheMuso_Boston> Ok fair enough.
[03:09] <persia> Hobbsee: Just flexing then?
[03:09]  * TheMuso_Boston tries not to think about that in a dirty way.
[03:09] <ajmitch> TheMuso_Boston: that's a wise choice
[03:09] <persia> TheMuso_Boston: Think about intimidation
[03:10] <TheMuso_Boston> persia: If I'd not had a few beers earlier, it would be easier than it is.
[03:10] <persia> TheMuso_Boston: Right.  Timezones.  My sympathies.
[03:28] <LaserJock> we don't have a mozilla package?
[03:29] <LaserJock> what's our equivalent to iceape
[03:30] <Fujitsu> LaserJock: We killed off mozilla a couple of releases ago. I think we have iceape.
[03:30] <Fujitsu> !info iceape hardy
[03:30] <Fujitsu> !info seamonkey hardy
[03:30] <ubotu> iceape: The Iceape Internet Suite. In component universe, is optional. Version 1.1.4-1ubuntu2 (hardy), package size 29 kB, installed size 84 kB
[03:30] <ubotu> Package seamonkey does not exist in hardy
[03:30] <LaserJock> hmm, ok
[03:35] <bddebian> !info internet-explorer
[03:35] <ubotu> Package internet-explorer does not exist in gutsy
[03:35] <bddebian> ;-P
[03:40]  * bddebian kills the conversation again...
[03:41] <ajmitch> that's ok, we're used to that
[03:41] <bddebian> Aye :'-(
[03:52]  * TheMuso_Boston is outa here. Night folks.
[03:53] <ajmitch> bye
[03:53] <Fujitsu> Night TheMuso_Boston.
[04:01] <bddebian> Gnight TheMuso_Boston
[04:52] <moquist> I'm making a moodle-standalone metapackage. Should I be editing the debian/control file of the moodle package, or of a new package that only contains a debian directory?
[04:54] <moquist> LaserJock: ^^^^^^
[04:54] <moquist> LaserJock: and hi!
[04:55] <persia> moquist: It depends on several factors.  What is moodle-standalone intended to do?  Does it require any extra code beyond that in moodle?  Is there a reason it would be easier to maintain the package external to moodle?
[04:56] <moquist> persia: not necessarily. I'm just having trouble with it and wondered if the metapackage was supposed to be created separately.
[04:57] <moquist> persia: the 'moodle' package by itself will not install mysql-server or postgresql, and you must have one of them if debconf is going to successfully configure moodle for you.
[04:57] <persia> moquist: That sounds to me like a problem with either the recommends: or the postisnt.
[04:57] <moquist> persia: so moodle-standalone-mysql will depend on moodle and mysql-server, and moodle-standalone-postgresql will depend on moodle and postgresql.
[04:58] <persia> moquist: Does moodle recommend: mysql | postgresql ?
[04:58] <moquist> hehe... "postisn't"
[04:58] <moquist> persia: yes.
[04:58] <moquist> But we want the administrator to be able to choose a single package for installation and get a working configuration.
[04:59] <persia> moquist: I'm not sure I see any benefit to moodle-standalone.  Unless the user specifically requests otherwise, a database engine will be installed when moodle is isntalled.
[04:59] <LaserJock> well ...
[04:59]  * persia seems to be having issues with sn vs. ns
[04:59] <LaserJock> persia: the background is we're going to be shipping moodle in Edubuntu
[04:59] <LaserJock> so we need a good way of doing this at installation
[04:59] <moquist> LaserJock: you are now. :p
[05:00] <LaserJock> without messing up everybody else
[05:00] <moquist> LaserJock: I don't think -standalone is necessary for installation; preseeding can solve that
[05:00] <persia> LaserJock: Can Edubuntu not just seed a preferred database?
[05:00] <moquist> (unless I'm mistaken, which is very possible)
[05:00] <LaserJock> that could be
[05:00] <moquist> Recommends: is just for the administrator to read and respond to, yes?
[05:00]  * persia generally disapproves of more package names: it tends to confuse people
[05:01] <LaserJock> but we still were concerned about having a package for people to install
[05:01] <persia> moquist: Not quite.  the package installation tools install all recommends: unless specifically told not to do so (this wasn't true for feisty)
[05:01] <LaserJock> so *we* need to pick a db but people have a choice
[05:01] <LaserJock> a problem has been that there were too much debconf questions
[05:02] <moquist> persia: I ran 'apt-get install moodle' on a fresh gutsy the other day and it didn't work because it didn't install a database server, and Recommends: postgresql | mysql-server.
[05:02] <LaserJock> and not everybody is going to have a db engine install prior
[05:02] <Fujitsu> persia: The lintian run finally finished, and it looks like the results might actually be sort of sane.
[05:02] <persia> LaserJock: Right.  So if moodle recommends mysql | postgresql, and edubuntu recommends: moodle. mysql then most users will get a working moodle/mysql, and picky administrators will get a working moodle/postgresql
[05:02] <LaserJock> but Recommends are installed
[05:03] <LaserJock> *aren't
[05:03] <persia> moquist: For which apt?  apt-get only got updated recently.  aptitude and the GUI tools have been doing the right thing a little longer.
[05:03]  * moquist checks
[05:03] <LaserJock> persia: "right" is debatable ;-)
[05:04] <LaserJock> right now in synaptic and apt recommends are only installed for metapackages
[05:04] <persia> LaserJock: http://lists.debian.org/debian-devel-announce/2007/08/msg00000.html
[05:04] <LaserJock> persia: yes, I know, but that's not Ubuntu
[05:04] <Fujitsu> LaserJock: Yet.
[05:05] <persia> LaserJock: I was fairly sure that Michael intended to also implement it here
[05:05] <Fujitsu> We pioneered recommends-by-default, so why wouldn't we follow the completion of it in Debian? My *our* apt maintainer?
[05:05] <Fujitsu> *By, damnit.
[05:05] <moquist> LaserJock: it sounds to me like the -standalone packages aren't necessary, if apt in hardy will support Recommends:.
[05:07] <LaserJock> it would appear not
[05:07] <persia> moquist: Well, Recommends: by default, but not enforce it.  Still, meets your use case.
[05:07] <LaserJock> we still need simplified debconf though
[05:07] <persia> s//install/
[05:08] <moquist> LaserJock: Yes, and I think that's a separate issue.
[05:10] <moquist> bah. apt-ftparchive sources . complains "moodle has no source override entry / moodle has no binary override entry either". I've been reading the man-page but I don't grok it yet.
[05:10] <persia> moquist: Your Section doesn't match expections, likely
[05:11] <Fujitsu> moquist: You need to specify an override file, with lines in the form `package priority section'
[05:12] <moquist> Fujitsu: I can't fix this just by fixing the Section: line under Source: moodle?
[05:12]  * moquist notes that this seems to be a change in gutsy
[05:12] <moquist> I didn't get these errors (warnings?) in feisty.
[05:12] <persia> Fujitsu: Thanks for running that.  How bad do we look?
[05:12] <Fujitsu> moquist: You might be able to, but I'm not sure.
[05:12]  * moquist nods
[05:13] <Fujitsu> persia: We have around 70 more sources with issues, but 220 fewer binaries.
[05:14] <Fujitsu> I'll publish the results in a sec and set it to run regularly.
[05:14] <persia> Fujitsu: That's excellent.  To be honest, I'm actually more concerned with the binary packages.
[05:14] <Fujitsu> persia: Right, they're what matter to most people.
[05:15] <persia> Of course, most people seem to mostly run lintian agaisnt source packages, but that's another issue, for another day...
[05:15] <Fujitsu> It looks like a lot of people don't run lintian against their packages at all, but..
[05:16]  * moquist installs lintian
[05:16]  * Fujitsu blinks.
[05:16] <Fujitsu> Why do I see a maintainer "Maintainer: Ubuntu MOTU Developers<EMAIL_ADDRESS>[05:16] <persia> moquist: Install linda as well.  She looks at slightly different things, and doesn't whine as much.
[05:16]  * persia hides in shame
[05:17] <jdong> persia: is there one that fixes all the problems for you and cleans up your desktop icons too?
[05:17] <moquist> persia: heh. thanks...I think.
[05:17] <persia> jdong: Not yet, but if you have a candidate, I'd be happy to review :)
[05:17]  * Fujitsu growls at dholbach.
[05:18] <persia> Fujitsu: It wasn't me?  I thought I typed that once.
[05:18] <LaserJock> oh wow, 3 each of lipia, amd64, and i386 for PPAs
[05:18] <Fujitsu> We have a few variants on our maintainer:
[05:18] <Fujitsu> Ubuntu MOTU Developer<EMAIL_ADDRESS>[05:18] <Fujitsu> Ubuntu MOTU Developers<EMAIL_ADDRESS>[05:18]  * persia wants an ARM ppa
[05:18] <Fujitsu> Ubuntu MOTU Devolopers<EMAIL_ADDRESS>[05:18] <Fujitsu> LaserJock: Yeah, but only the old two are operational at the moment.
[05:19]  * persia votes for Ubuntu MOTU Developers<EMAIL_ADDRESS>[05:19] <persia> huh?  Never mind.
[05:19] <jdong> ubuntos -- the brown mentos!
[05:34]  * LaserJock pokes PPA with a stick
[05:36] <Fujitsu> LaserJock: Why?
[05:40] <LaserJock> I've got two packages I'm trying to get built tonight
[05:41] <LaserJock> and they're stuck in "needs building"
[05:41] <Fujitsu> Ah, yeah, the buildds weren't doing anything for several hours earlier.
[05:42] <Fujitsu> I suspect something on cesium fell over when the new buildds appeared.
[05:42] <LaserJock> hmmpf
[05:42]  * persia suspects that the concentration of sysadmins in a single geographical location reduces uptime
[05:42] <Fujitsu> persia: Not everyone is at UDS.
[05:42] <LaserJock> I was going to announce my packages to the forums this evening
[05:42] <Fujitsu> Spads isn't, IIRC.
[05:43] <persia> Fujitsu: Ah.  In that case, I'm wrong.  Hurrah!
[05:44] <LaserJock> samarium looks toasted
[05:44] <LaserJock> but thallium says Idle
[05:44] <LaserJock> as is iridium
[05:45] <Fujitsu> LaserJock: They're manual, no?
[05:46] <LaserJock> bah, yes
[05:47] <LaserJock> alrighty, I guess I'll give up on that for today
[05:47] <Fujitsu> Unfortunately, everybody will be asleep now, including those in London. Convenient.
[05:47] <LaserJock> the forums will just have to wait another day ;-)
[05:48] <persia> Fujitsu: Is there normally a sysadmin on this side, or are they all European/American?
[05:49] <LaserJock> who's American? Spads?
[05:49]  * persia thought there was someone in the Montreal office
[05:49] <Fujitsu> persia: AFAIK they're all in London. But I could be wrong.
[05:49]  * Fujitsu checks.
[05:50] <LaserJock> Montreal is not America ;-)
[05:50] <persia> LaserJock: Yes it is.
[05:50]  * persia used to live in the Americas, and is fairly well versed in the corrent and annoying inerudite meanings of "America"
[05:50] <LaserJock> I think that's highly debatable
[05:50] <persia> s/ent/ect/
[05:50]  * ajmitch hugs Hobbsee
[05:51] <ajmitch> hello
[05:51] <Fujitsu> persia: They're all listed as being in London, except elmo, and I know he is.
[05:51] <persia> LaserJock: Yep.  Highly so.  Still, timezone-wise, it applies.  I don't consider African vs. European sysadmins to be meaningfully different
[05:51] <persia> Fujitsu: Ah.  Interesting.  Thanks for checking.
[05:52] <Fujitsu> Oh, I see that that bhavi guy who tried to join every team in existence also tried to join ~canonical-sysadmins. Nice.
[05:53]  * Hobbsee hugs ajmitch.  hiya!
[05:53] <Hobbsee> Fujitsu: bhavi?  you mean there's another one?
[05:54] <Burgundavia> persia: if you think Montreal is in "America", you have serious issues
[05:54] <Fujitsu> Hobbsee: Yeah, but this was a few months back.
[05:54] <Hobbsee> ah, right
[05:54] <Fujitsu> Yay, http://people.ubuntu.org.au/~fujitsu/lintian/universe/.
[05:54] <Fujitsu> It seems to have actually worked.
[05:55] <persia> Burgundavia: I'll claim São Paulo is in America as well :)
[05:55] <Burgundavia> it is in the Americas, yes, but not in America
[05:55]  * persia doesn't understand Maintainer: (unknown)
[05:57] <Fujitsu> persia: Neither.
[06:00] <LaserJock> that's what we should do for MOTU :-)
[06:01]  * Fujitsu notes he missed several DebianMaintainerField variants before.
[06:01]  * persia considers bumping the upload count to consolidate all the errors
[06:02] <Fujitsu> Aha, gtkgo is the one causing<EMAIL_ADDRESS>[06:02]  * Fujitsu thinks people should check that sort of stuff on upload.
[06:03] <ajmitch> it's easy to glance at & miss
[06:03] <persia> Fujitsu: people?  Why not tools?  Add a lintian rule that complains if one uses the case-insensitive string "motu" in Maintainer, and doesn't use the appropriate string (same for "core", I'd think).
[06:03] <Hobbsee> i'm surprised that LP doesnt have a filter set up to reject those mails
[06:03] <Fujitsu> persia: That's a good idea.
[06:03] <Hobbsee> sorry, that the MOTU ML
[06:03] <Fujitsu> Hobbsee: Which mails?
[06:03] <Hobbsee> oh, my bad.
[06:04] <Hobbsee> i'm misreading - thought you were talking about accepted mails to the list
[06:04] <ajmitch> persia: dput hook :)
[06:04]  * persia suspects mail in the queue of unaccepted mail
[06:04] <ajmitch> refuse to upload if X,Y & Z conditions are not met
[06:04] <persia> ajmitch: That's harder.  What about things like the creation of the Ubuntu MOTU Torrents Team as a maintainer?
[06:05] <persia> Should dput first be patched?  I'd prefer advisories.
[06:05] <ajmitch> what about it? just have a blacklist of common problems
[06:05] <Hobbsee> of course, some of it are legitimate uses of not having the MOTU as the maintainer
[06:05] <Hobbsee> for stuff like siretart's xine-lib, which the recent mail was about.
[06:05] <ajmitch> yes, but misspellings are not legitimate
[06:05] <Fujitsu> Hobbsee: Right, which is why we grep for motu first.
[06:05] <Hobbsee> oh, of course.
[06:06] <Fujitsu> I particularly like Maintainer: Maintainer: Ubuntu MOTU...
[06:07] <Hobbsee> heh
[06:07] <Hobbsee> yes
[06:10] <persia> Fujitsu: Likely just cut & paste.  I know I've done that (although I am glad I don't appear to have uploaded the results)
[06:11] <LaserJock> update-mime-database is run by dh_instalmime isn't it?
[06:12] <Fujitsu> LaserJock: I think so.
[06:12] <Fujitsu> It is.
[06:12] <persia> LaserJock: You may also want to run update-desktop-database, for the MIME representations, depending on your MIME type.
[06:12] <LaserJock> this package has a postinst and prerm script that looks like it just has the dh_* stuff in it
[06:13] <LaserJock> so I'm thinking I should just get rid of them
[06:13] <persia> LaserJock: Does the package also use the dh_* calls?  Are the final results broken?  Sometimes a maintainer decided dh_foo wasn't flexible enough, or hand't heard of it.
[06:14] <LaserJock> they use dh_*
[06:14] <LaserJock> it looks like maybe the added dh_* later and didn't realize they didn't need their maintainer scripts anymore
[06:14]  * persia still suggests inspecting the resulting binaries
[06:15] <LaserJock> man this stuff takes so long
[06:15] <LaserJock> it's gonna take me all week to get one package done
[06:17] <Fujitsu> Haha, in the lintian source:
[06:17] <Fujitsu>         # Wookey really only has one name.  If we get more of these, consider
[06:17] <Fujitsu>         # removing the check.
[06:17] <Fujitsu> They've got an exception for this one maintainer who has just one name.
[06:19] <persia> That's the spelunking software, isn' it.  Hrm.  I should look at that again: it needs porting to wx2.6
[06:20]  * RAOF is a millionaire base-jumping spelunker
[06:20] <persia> RAOF: Do you use any cave mapping software with Ubuntu?
[06:21] <RAOF> persia: Yeah; I've got an integrated tablet PC built into my suit.
[06:21] <persia> RAOF: Which package do you use?
[06:22] <RAOF> Um, I can no longer continue the charade.
[06:22]  * persia has been duped, and gives up on building a moral lcase for RAOF to do the port
[06:22] <RAOF> You obviously didn't get the initial movie reference :)
[06:23] <RAOF> Is it python?
[06:23] <RAOF> NO!  Resist!
[06:23] <Fujitsu> Which port is this?
[06:24]  * RAOF really has to learn to not overcommit quite so much.
[06:26] <persia> Fujitsu: survex-aven needs to migrate from wx2.4 to something more recent (2.6 is preferred by the aforementioned single-named DD so that it may be adopted by Debian).  The trick is that the survex maintainer doesn't want wx strings in the survex code, but only in survex-aven because of the ugliness of WX unicode handling.
[06:27] <Fujitsu> persia: Ah.
[06:27]  * Fujitsu must depart now.
[06:27] <persia> heh
[06:28]  * RAOF thinks it would be awesome if all cross-platform stuff currently using wx* was magically converted to cross-platform gtk
[06:28] <persia> RAOF: converter scripts (yes, even in python) welcome :)
[06:29] <imbrandon> ello all
[06:29] <RAOF> Again, with the learning to not overcommit.  The correct response is *not* "hm... I wonder if that would be possible"!
[06:30]  * persia thinks that's an excellent response.  Perhaps followed by "Let me see..."
[06:30] <imbrandon> possible sure, gtk ? ugh, qt == <3 :P
[06:31] <RAOF> How cross-platform is QT?
[06:31] <persia> imbrandon: While I'm willing to believe the possibility of WX -> GTK semi-automated port, the backends of QT and WX are just far too different.
[06:31] <persia> RAOF: More than GTK, and for longer
[06:32] <RAOF> I knew it started out as more cross-platform.  It's just that I don't think I've *ever* seen a windows QT app.
[06:32] <persia> RAOF: Internet Explorer?
[06:32] <RAOF> What, really?
[06:32] <RAOF> Heh.  Cross platform *with* integration :)
[06:32] <Burgundavia> RAOF: qt was not free on windows until qt4
[06:32] <imbrandon> RAOF, ther are tons of windows QT apps
[06:32] <Burgundavia> opera is another good one
[06:33]  * RAOF has been insulated, obviously.
[06:33] <persia> RAOF: Now, here's the trick.  Find a closed-source non-Java non-QT app on Windows
[06:33] <Burgundavia> but RAOF is right in that there were not Free QT apps until recently, as you needed a QT license to use QT on platforms other than windows
[06:33] <Burgundavia> linux, rather
[06:33] <Burgundavia> personally, I think the KDE people are chasing a rathole with KDE-on-windows
[06:34] <persia> Burgundavia: No.  You could use the free QT license to develop for windows, as long as you wrote free software.
[06:34] <imbrandon> Burgundavia, kinda, you could use the cygwin qt3
[06:34] <imbrandon> to write gpl stuff
[06:34] <imbrandon> Burgundavia, why? i run KDE ( native ) on OSX daily
[06:35] <imbrandon> why not windows
[06:35] <Burgundavia> because it is a lot of development work for little benefit
[06:35] <imbrandon> native == !X11 port, but native QT on OSX
[06:35] <imbrandon> Burgundavia, nah it is actualy very little changes, and most are in mainline kde svn
[06:36] <Burgundavia> initial porting was probably easy
[06:36] <Burgundavia> now have fun with all the corner case bugs that are going to popup
[06:37] <imbrandon> you got to think, the base was already done for many many releases, QT, all that needed porting was a few things in ldelibs, then every kde apps works
[06:37] <imbrandon> kdelibs*
[06:37] <Burgundavia> umm, right
[06:37] <Burgundavia> software development doesn't work that way
[06:37] <imbrandon> kde apps very very very seldom work below the QT abstraction layer
[06:38] <imbrandon> Burgundavia, ummm sure not all, but in this case yes, think how long QT has been on windows, almost 11 years if not more
[06:38] <imbrandon> its not a "new" thing
[06:45]  * RAOF wonders if hitting his students with sticks would prevent them from trying to integrate discrete varables.
[06:45] <Hobbsee> unlikely
[06:45] <Hobbsee> see, this is why i dont take maths.
[06:46]  * RAOF wonders if hitting his students with *Hobbsee* would prevent them from trying to integrate discrete variables.
[06:46] <RAOF> You come in an easy-to-wield pack, right? :)
[06:48] <pwnguin> and fourrier transforms into a size suitable for storage in your backpack
[06:48] <RAOF> As long as you cutoff the infinite tail?
[06:49] <RAOF> Or is Hobbsee infinite in space and time? :)
[06:49] <pwnguin> infinite in length but not area :P
[06:49] <Hobbsee> RAOF: of course i'm infinite :P
[06:49] <Hobbsee> RAOF: infinte, by the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™
[06:50]  * persia suspects the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™ is not infinite
[06:50]  * RAOF imagines a museum exhibit... "Hobbsee over the ages"
[06:50] <pwnguin> Hobbsee: aren't you studying computers or something at University?
[06:50] <Hobbsee> pwnguin: yes.
[06:50] <Hobbsee> pwnguin: although currently i'm doing physics, optoelectronics and computing subjects :P
[06:51] <pwnguin> optoelectronics surely counts as maths
[06:52] <RAOF> pwnguin: Only for {} values of "maths"
[06:52] <RAOF> GAH!  This student has treated the continuous variables as discrete, and the discrete variables as continuous!
[06:52] <pwnguin> set values of maths?
[06:52] <RAOF> Empty values of maths
[06:52]  * RAOF lets fly a mighty roar
[06:52] <persia> RAOF: Just assume a regular pattern of reality shifts :)
[06:53] <pwnguin> well, ive seen my roommate's optoelectronics book, and i declare it to have enough formulas to be math-worthy
[06:53] <persia> pwnguin: Formula's aren't math.     This is not maths :)
[06:59] <pwnguin> RAOF: also, remember that students likely spend more time in the test than they give themselves for the homework. "oh crap, that's due in 50 minutes from now"
[06:59] <RAOF> pwnguin: Homework?  _What_ homework?  We don't give any homework.
[06:59] <Hobbsee> tutorials?
[06:59] <RAOF> Tests, and more tests!  Then exams!
[06:59] <Hobbsee> which must be predone?
[06:59] <pwnguin> well that makes sense now
[07:00] <pwnguin> your students are idiots because they've never had to take the time not to be
[07:00] <RAOF> Hobbsee: For a value of "pre-done" which closely approximates "glanced at the book that contains it"
[07:00] <Hobbsee> haha
[07:00] <persia> RAOF: Isn' t that just extra work for you?  You could send them home with tests, and make them mark it at the next recitation.
[07:00]  * RAOF suspects this appoximation is exact as the number of students approaches infinity.
[07:01] <Hobbsee> "oh look, why did everyone get full marks?"
[07:01] <pwnguin> heh
[07:01] <pwnguin> we had someone do that for a psych recitation class
[07:01] <RAOF> What's even better is that someone has done this test quite well... and not put any identification on it _at all_.
[07:01] <pwnguin> the dumbass TA basically brought the whole class before the honor board when they did the enevitable
[07:02] <RAOF> Ah, teaching.
[07:02] <Hobbsee> RAOF: oh, i've been known to do that - although that was only including my student #, and not my name
[07:02] <pwnguin> the algebra of nations: America + Britan == 0
[07:03] <pwnguin> its very similar to the algebra of computer design
[07:03] <pwnguin> Intel = -Motorola
[07:03] <pwnguin> whenever intel makes a design, motorola sees that and does the opposite
[07:03] <RAOF> pwnguin: So, which nation is 0?
[07:04] <pwnguin> it may have been wrong of me to bring up things like numbers
[07:04] <RAOF> Indeed.  Also, is it an actual algebra, a ring, or a field? :P
[07:04] <pwnguin> but ... antartica?
[07:04] <pwnguin> its probably a field
[07:05] <pwnguin> because if you take something and add america to it, it gets smaller ;)
[07:05] <pwnguin> actually, i havent studied number theory enough to know the difference aside from the math nutters nearby joking about it
[07:05] <RAOF> So it's isomorphic to a Z mod p, or Z mod p^n :)
[07:06]  * imbrandon explodes
[07:07] <pwnguin> anyways, im tempted to say that austrialia is zero, because if you add britian and australia, you wind up with britain again
[07:07] <pwnguin> spelling is not my strong point, i dont think
[07:08] <RAOF> Actually, all the elements are idempotent: country + country = country.
[07:09] <pwnguin> you heard it here first: RAOF declares Austrialia idempotent
[07:09] <pwnguin> RAOF: i should dig up some code people submit in undergraduate Operating Systems
[07:10] <pwnguin> they have four weeks per project and still go wildly wrong in some cases
[07:10] <RAOF> That at least has the benefit that it compiles, surely.
[07:10] <RAOF> It's at least syntactically correct.
[07:10] <pwnguin> well, one hopes
[07:10] <pwnguin> its -30 percent if it doesnt
[07:10] <pwnguin> and you likely wont be getting full credit in such a case even if it DID compile
[07:11] <pwnguin> my favorite was the "use a Condition Variable as part of a condition variable"
[07:12] <pwnguin> so what does new Condition() do? it sets up some local variables, and then calls new Condition()
[07:12] <RAOF> Stack space is for pansies, I say.
[07:12] <RAOF> Terminating recursion is boursoise.
[07:13] <pwnguin> there you go
[07:13]  * RAOF is utterly incapable of spelling that.
[07:13] <pwnguin> the compiler can do some pretty good optimizing tricks
[07:13]  * Hobbsee attempts to figure the gnome-hearts merge.
[07:13] <pwnguin> but it cant optimize away an infinite loop
[07:14] <persia> Hobbsee: gutsy gnome-hearts doesn't work at all: please fix it when you merge :)
[07:14] <Hobbsee> persia: yeah, i just noticed it didnt work in gutsy
[07:15] <Hobbsee> persia: looks like we can take debian's, which will likely break again, or go with upstreams.
[07:15] <Hobbsee> but, i thought the gnome people put the same packages into debian and ubuntu
[07:15] <Hobbsee> or at least, close to it
[07:15] <persia> Hobbsee: I suggest going with upstream, as we've upstream gnome-games for the cards, but I hope you'll keep the rules change for the jack of diamonds.
[07:15] <Hobbsee> persia: the round the moon?
[07:16] <persia> Hobbsee: Right.  Last I checked (several months back), upstream penalised you for jack of diamond for round-the-moon.
[07:16] <Hobbsee> persia: ah right - so the cards package is in our gnome-games, and not accidently synced from debian?
[07:17] <persia> Hobbsee: I thought so, but my memory is fuzzy, and I was only working on the code by proxy (for someone who is now no longer active)
[07:17] <Hobbsee> ...why are there no icons on my desktop?
[07:17] <pwnguin> because you asked it to hide them?
[07:17] <RAOF> Because you're using nouveau & a composite manager?
[07:17] <pwnguin> or perhaps nautilus crashed
[07:18] <persia> Hobbsee: Open up somewhere from Places... : it might just fix it.
[07:18] <Hobbsee> ah, so this was a mistake in stopping nautilus from starting up
[07:19] <persia> Hobbsee: Well, unless you don't want a desktop shell :)
[07:20] <imbrandon> wow multiarch live boot cd's ? nice
[07:20] <Hobbsee> well, i'd like my dsektop icons.  i'd guessed it was a preloading thing for nautilus
[07:31] <warp10> Hi all
[08:40] <Hobbsee> right.  a non-broken version of gnome-hearts.
[09:22] <coolbhavi> hello please synchronise my keys so that I can start uploading packages
[09:22] <coolbhavi> hello please synchronise my keys so that I can start uploading packages
[09:22] <persia> coolbhavi: You've joined the team?
[09:23] <ion_> Does it echo in here?
[09:23] <coolbhavi> yup contributors of ubuntu universe
[09:25] <persia> coolbhavi: Great.  Unfortunately, most of the REVU admins aren't around right now.  I'd suggest asking for a keyring sync in either 4 or 12 hours (unless someone wants to contradict me)
[09:27] <coolbhavi> Ok some days back I had asked the same and they told it would be over by an hour
[09:27] <persia> coolbhavi: In that case, it's probably done.  Have you tried to upload your candidate?
[09:27] <coolbhavi> How to check the keyring sync?
[09:28] <persia> coolbhavi: Checking is really frustrating, and only admins can check.  It7s very rarely done - it's easier to sync again.  Try uploading.
[09:29] <coolbhavi> Whats my login?
[09:29] <coolbhavi> and my pass
[09:29]  * ajmitch can sync now
[09:29] <persia> coolbhavi: Your login will be assigned to match the email in your changelog when you upload.  Once you've uploaded, you can recover your password with your key.
[09:30] <coolbhavi> ok can i login with my mail id and password?
[09:30] <ajmitch> keyring will take a few minutes to sync, just started it now
[09:30] <persia> coolbhavi: What did you upload?
[09:31]  * persia thanks ajmitch
[09:31] <coolbhavi> I want to upload a package apt write
[09:32] <coolbhavi> How to do it? Please help
[09:32] <persia> coolbhavi: Have you read the wiki page about uploading?
[09:33] <coolbhavi> No Link please
[09:35] <RAOF> coolbhavi: https://wiki.ubuntu.com/MOTU/Packages/REVU
[09:35] <persia> coolbhavi: Use RAOF's link :)
[09:36]  * RAOF suspects he just beat persia to the punch
[09:37] <coolbhavi> I already have the deb package then what to do?
[09:38] <persia> coolbhavi: Ubuntu doesn't accept binary uploads.  You'll need to upload the source.  That wiki page explains how.
[09:39] <imbrandon> wow , qemu without acceleration on a p200 is painfull
[09:39] <coolbhavi> Ok source means I have a perl script.. again Should i rebuild?
[09:39] <persia> coolbhavi: You'll want to build a source package.  `debuild -S -sa`
[09:40] <persia> imbrandon: What are you emulating?
[09:40] <imbrandon> x86, just tesing a livecd
[09:40] <imbrandon> err live-iso
[09:40] <imbrandon> :P
[09:41]  * persia imagines imbrandon wrestling with a wrathful plastic disc, intent on having him for dinner
[09:41] <imbrandon> heh
[09:41] <persia> imbrandon: For special pain, emulate a PowerPC and test the liveCD :)
[09:41] <imbrandon> i think i'm gonna call it a night on it though, i just got dropped to a busybox tem on boot
[09:42] <imbrandon> persia, hehe i have before, infact ...
[09:42] <persia> imbrandon: On your PII200?
[09:42] <imbrandon> i have setup a scratchbox env to build deb packages using qemu-ppc emulation to cross compile
[09:42] <imbrandon> is a P1 200
[09:42] <imbrandon> yes
[09:43]  * persia thinks imbrandon needs the build farm back
[09:43] <imbrandon> lol the scratchbox was on the build farm
[09:43] <imbrandon> it was just to see how hard it would be to make ppc packges on a x86
[09:43] <imbrandon> not very fun
[09:43] <persia> Right.  Umm.  Magic better build farm?
[09:44] <imbrandon> :)
[09:44] <imbrandon> its slowly getting back there
[09:44] <imbrandon> i have some hardware laying arround and some more on the way
[09:44] <imbrandon> i'm takin my time this time though to make sure it dosent all blow up overnight like last time
[09:44] <coolbhavi> Ok got it.... If we want to upload a update of an existing package What to do?
[09:44] <imbrandon> and actualy DESIGN the network and infra
[09:45] <persia> coolbhavi: In that case, you probably want to upload a debdiff to a bug.  See https://wiki.ubuntu.com/MOTU/Contributing/
[09:46] <coolbhavi> Got it
[09:46] <coolbhavi> Thanks
[09:49] <persia> imbrandon: No rush.  Something good is far better than something now.
[09:49] <imbrandon> yea thats my thinking , last time it wasent
[09:50] <persia> imbrandon: At the time, I suspect something now was better than something good: wasn't that prior to REVU, PPA, and all the other nice things we have now?
[09:50] <imbrandon> no i mean last time, i just threw some things up, not worring about quality as much
[09:51] <imbrandon> and yea it was prior to PPA and much of the new scripts but not
[09:51] <imbrandon> REVU
[09:52] <imbrandon> ugh, live-helper is great but .... ummm ... a bit buggy
[09:52] <imbrandon> probably works great for Debian, not so much if you plug ubuntu packages in
[09:57] <s1024kb> persia: Hello
[09:58] <s1024kb> persia: nice to meet you again
[09:58] <persia> s1024kb: Hello.  I'm about to head off: if you seek something specific from me, please tell me now :)
[09:59] <s1024kb> persia: excuse me, what did you mean?:)
[09:59] <s1024kb> persia: i am very happy to meet an old friend (old enough? haha) here
[09:59] <persia> s1024kb: My apologies for the confusion.  Nice to see you again.
[10:01] <s1024kb> persia: imagine when a person knows nobody in IRC... when he/she meet one who he/she had ever chatted with, he/she will feel very happy...:)
[10:01] <s1024kb> persia: It's afternoon here in China, i had just finished my job.
[10:02] <persia> s1024kb: Ah.  I understand now.  It's a bit later here, so I'm just leaving.  Have a good evening.
[10:32] <Hobbsee> ...we're doing what now?
[10:32] <Hobbsee> as if MOTU didnt already have enough to do
[10:32] <Hobbsee> http://www.mikesplanet.net/2007/10/ubuntu-forums-ubuntu-development-programming/
[10:34] <jpatrick> Hobbsee: with more people, we'll have less to do :)
[10:34] <Hobbsee> jpatrick: yeah, but i'm interested in using our resources for people who can be trained usefully.
[10:35] <Fujitsu> Did I miss the bit where we were told this might be happening?
[10:35] <Hobbsee> as in, get useful people, rather than people who either a) drain MOTU, or b) give up, when they realise that it's hard.
[10:35] <Hobbsee> Fujitsu: it's as good as done.  the expectation will now be on the forums, and the MOTU will get bitched at for not answering all the packaging queries.
[10:36] <Hobbsee> all discussed with...it seems...1 member of MOTU?
[10:36] <Hobbsee> based on how they go for testing stuff out, and providing useful things on the forum for that (or not), i cant see the packaging would be any better, when it's an order of magnitude harder.
[10:37] <Fujitsu> Hobbsee: One member of MOTU, or just dholbach?
[10:37] <Hobbsee> Fujitsu: dholbach is a member of MOTU
[10:37] <Fujitsu> He's.. sort of special, though.
[10:37] <RAOF> Sorry, what?
[10:38] <Hobbsee> Fujitsu: yeah, but he cant make a commitment on what the MOTU will do like that.
[10:38] <RAOF> The forums don't seem like a particularly awesome place for that sort of stuff.
[10:38] <Hobbsee> with any sort of real expectation that we'll jump on board.
[10:38] <Hobbsee> RAOF: yeah.  just read the link.
[10:38] <Fujitsu> RAOF: You'd think not.
[10:38] <Fujitsu> Hobbsee: That's what I meant. He's not exactly representative of the MOTU community.
[10:38] <Hobbsee> Fujitsu: oh, indeed, but i think he's attempted to act as one there
[10:39] <Hobbsee> ah, here's the implementation:
[10:39] <Hobbsee> Implementation
[10:39] <Hobbsee>     *
[10:39]  * Fujitsu is reading it now.
[10:39] <Hobbsee>       Possiblity of some approved MOTUs to moderate the packaging forum.
[10:39] <Hobbsee>     *
[10:39] <Hobbsee>       Scott Ritchie (YokoZar) has volunteered to moderate the forum
[10:39] <Hobbsee>     *
[10:39] <Hobbsee>       Provide a link to the forum in the MOTU IRC subject topic
[10:39] <Fujitsu> Steps for moderation: delete, delete, delete, delete.
[10:39] <Hobbsee> a)  no one will do it
[10:39] <Hobbsee> b)  great.  there's 1.
[10:39] <Fujitsu> Erm...
[10:39] <Hobbsee> c)  everyone will ignore it.  if they cant get new packages done off revu, what chance do we have of forums stuff?
[10:39] <Fujitsu> Why the heck do we want to send people *to* the forum?
[10:39] <Hobbsee> hahahah :)
[10:40] <Hobbsee> because the forum sheep refuse to come to us.
[10:40] <RAOF> I do my share of pointing.
[10:40] <Hobbsee> see, this is the problem - we dont just want to recruit people - we need to recruit *good* people.
[10:41] <Hobbsee> and doing it in a forums place is definetly not a good medium for that.
[10:41] <Fujitsu> Not Joe "wooot i'm going to package new compiz on crack" Random.
[10:41] <Hobbsee> exactly
[10:41] <RAOF> Maybe a forum *could* be a good place for some form of mentoring, though.  A nice shared place with easy markup, etc.
[10:41] <Hobbsee> oh, why does it break when i do it with checkinstall?
[10:41] <RAOF> Indeed.
[10:41] <Hobbsee> RAOF: doesnt help much when people don't search.  or RTFM.
[10:42] <Fujitsu> Or use checkinstall.
[10:42] <Hobbsee> even when pointed to the page.
[10:42] <RAOF> Most of the people on the forums don't want to make an Ubuntu-quality package.
[10:42] <Hobbsee> Fujitsu: they think all packaging gets done with checkinstall
[10:42] <RAOF> They just want their stuff, *now*.
[10:42] <Hobbsee> RAOF: most?  i'd guess for all
[10:42] <Hobbsee> exactly
[10:42]  * RAOF was on the forums first.
[10:42] <Fujitsu> RAOF: You seem to have recovered well.
[10:42] <Hobbsee> oh, that nutter is posting about his new distro again
[10:43]  * Hobbsee flamed the hell out of him when he queried her :)
[10:43] <RAOF> What, he queried you?
[10:43] <RAOF> It seems totally misjudged.
[10:43] <Hobbsee> oh yes
[10:44] <Fujitsu> Hobbsee: Who?
[10:44] <Hobbsee> he queried a whole bunch of people, who were prospective developers
[10:44] <Hobbsee> Fujitsu: http://ubuntuforums.org/showthread.php?t=598026
[10:44] <Fujitsu> Ohhh, forums.
[10:44] <Hobbsee> samfisher - when he had no forums post at all
[10:44] <Fujitsu> I haven't read them in a long time.
[10:44] <RAOF> So nothing good will come of it, basically.  The best we can hope for is for it to distract people who would otherwise distract *us*.
[10:44] <Fujitsu> Um, lovely.
[10:45] <Fujitsu> Sounds really productive.
[10:45] <RAOF> Heh: "Poll: is SMART data reliable".  Well, that seems like the proper use of democracy :)
[10:45] <Hobbsee> well, they have a wallpaper!  isnt that the start of *any* perfect new distribution?
[10:45] <ion_> raof: Haha
[10:45] <RAOF> Fujitsu: Indeed.  Also, absolutely, totally unlike Debian.
[10:45] <broonie> Hey, the Ubuntu wallpapers were good marketing for Ubuntu!
[10:45] <Fujitsu> The reason I am not working on Ubuntu is because there are numerous problems that are difficult to resolve and integrate because it is already there and stable, if you know what I am trying to say?  No one, absolutely no one, who is any fucking good will come near your project if its nothing more than a few airy ideas.
[10:46] <ion_> Poll: is rainy a weather?
[10:46] <RAOF> Also, will use RPM for KDE, and dpkg for Gnome (because apparently KDE is made by redhat)
[10:46] <Fujitsu> RAOF: That's what I thought when I saw the poll, yeah.
[10:46] <Hobbsee> exactly.
[10:47] <Fujitsu> Ooh, I want to join the project as an assembler!
[10:47] <Hobbsee> heh
[10:48] <Hobbsee> RAOF: oh *nice*.  i never got that far.
[10:48] <Hobbsee> *snort*
[10:48] <RAOF> Hobbsee: I have a low interest threshold when marking.
[10:48] <zul> what are we bad mouthing now?
[10:48]  * Fujitsu laughs at the Contact page.
[10:48] <RAOF> zul: desktop-linux
[10:48] <zul> RAOF: ah url?
[10:48] <Fujitsu> `Web Help' is a decent subject for a support email? I see.
[10:49] <RAOF> desktop-linux.org
[10:49] <Hobbsee> zul: the forums, us helping them package, and desktop-linux
[10:49] <Hobbsee> zul: which is from the forums, and just says there will be a perfect linux distro, with no details as to how.
[10:49] <Fujitsu> Must... implement... SIGECUTE...
[10:49] <Fujitsu> Hobbsee: But they have a wallpaper!
[10:49] <ajmitch> Fujitsu: and that's what *really* matters
[10:49] <RAOF> Hobbsee: Or even what perfect means, in this context.
[10:50] <Fujitsu> ajmitch: Duh.
[10:50] <zul> why would you need "Assemblers"?
[10:50] <Fujitsu> Oooh, their main focus is installation!
[10:50] <RAOF> Or even what current distros do badly.
[10:50] <Fujitsu> Our Linux project aims to fix all the problems of other distributions and still be a powerful Linux. Our main focus will be on installation.
[10:51] <ajmitch> because ubiquity sucks, right?
[10:51] <Fujitsu> Haha:
[10:52] <Fujitsu> Poll: [Idea] Can we lay off the polls?
[10:52] <Fujitsu> ajmitch: Obviously.
[10:52] <RAOF> Heh.  Everyone should build stuff as root, all the time.
[10:52] <ajmitch> RAOF: you don't?
[10:52] <ajmitch> what is this world coming to?
[10:52] <zul> i like their announcements
[10:52] <Hobbsee> RAOF: now go read my reply
[10:53]  * ajmitch hunts for a link
[10:53] <Hobbsee> http://ubuntuforums.org/showthread.php?p=3683057#post3683057
[10:54] <Fujitsu> Hobbsee: Ah, a sane response in that downgrading thread!
[10:54] <Hobbsee> Fujitsu: it was first via a privmsg - and then the guy started the thread.
[10:54] <ajmitch> harsh
[10:55] <Hobbsee> ajmitch: better harsh now, and them not poaching devs, and getting people to go do something useful instead
[10:55] <Hobbsee> although, Kmos might like it - lots to do, no mention of QA.
[10:55] <ajmitch> heh
[10:55] <Hobbsee> probably no trouble with getting upload rights at all.  might be a good fit.
[10:56] <Kmos> Hobbsee: what?
[10:56] <Hobbsee> Kmos: see http://ubuntuforums.org/showthread.php?p=3683057
[10:57] <lamego> Kmos, ignore it, is the always funny *i know it all*, *you suck* mentality
[10:57] <Hobbsee> now, i wish i knew it all.  but i dont.
[10:58] <jpatrick> I found this on their forum: "I personally like Ktorrent. I am not sure if that relies on KDE though."
[10:58] <lamego> just has funny and smart as the new desktop-linux.org
[10:58] <Hobbsee> jpatrick: yay.  well, that's very legitmate - because they're probably not sure what their definition of kde is, too.
[10:59] <lamego> Hobbsee, anyway, you like to pick someone to show you know *more*
[10:59] <RAOF> "To work perfectly, we will be using a scratch system."
[10:59] <Kmos> lamego: hehe
[10:59] <Hobbsee> lamego: sorry?
[10:59]  * zul ducks
[10:59] <RAOF> On the other hand, scratch apparently doesn't include package management.
[10:59] <Hobbsee> AUTOMATIX FTW!!!
[10:59] <Hobbsee> this is automatix v3 under another name?
[11:00] <jpatrick> "Yes, I think one of the main things keeping users away from Linux is package systems. " - idiot
[11:00] <Fujitsu> Hobbsee: Yay!
[11:00] <RAOF> Awww, it's so cute: http://desktop-linux.org/forum/directx-10-gaming-for-linux-t39.html
[11:00] <RAOF> "We should totally implement directX 10"
[11:01] <Hobbsee> would be nice.  implement it somewhere useful, like in wine.
[11:01] <Fujitsu> jpatrick: Oh? I know all the people I introduce to Linux from Windows would prefer to locate and compile their own software from scratch. Don't you?
[11:02] <RAOF> Hobbsee: They're already on it, thankfully.
[11:02] <jpatrick> Fujitsu: my dad is quite happy with apt since he started Kubuntu 4 days ago :)
[11:02] <Hobbsee> RAOF: yay!
[11:02] <lamego> Hobbsee, your particular non sense of inserting Kmos into your own jokes, could be interpreted as lack of respect, but because we all signed the CoC, I am sure and it was just bad humour :)
[11:03] <RAOF> Hobbsee: In fact, I think that the wine guys are going to try to do DX10-on-Windows, too.
[11:03] <Hobbsee> lamego: not at all.  i know Kmos likes being im multiple projects, and that may be one that he's interested in - based on how he's been acting in debian and ubuntu so far.
[11:04] <Hobbsee> lamego: would be the kind thing to do to pass it on, if i suspect he's something he's interested in, no?
[11:04]  * Hobbsee counts.  RAOF, jpatrick, zul, Fujitsu, ajmitch...how about we all hit the sponsorship queue?
[11:04] <Hobbsee> get it down to a reasonable size again
[11:05]  * ajmitch is crashing
[11:05]  * Hobbsee ponders....does respect for people also mean that they follow their processes?
[11:05] <Fujitsu> Hobbsee: You'd think so.
[11:05] <RAOF> Hobbsee: You can count me in on Sat, but for now, I really need to enter marks, go home & sleep
[11:06] <zul> hmmmm
[11:06] <Hobbsee> RAOF: okay.  you're still at $work?
[11:06] <Hobbsee> zul: you have no excuse :)
[11:06] <RAOF> $uni, yes.
[11:06] <Hobbsee> RAOF: where your $workplace == $uni :)
[11:06] <ajmitch> Hobbsee: I have the excuse of it being after midnight
[11:06] <zul> Hobbsee: sure I do, A. I just woke up B. Im still not dressed C. I have to feed liam D. I have to go to work, take your pick ;)
[11:06] <lamego> Hobbsee, let me interpret your question, Ubuntu and Debian can be compared to desktop-linux or whatever, as a motivation for someone to participate at ?
[11:09] <lamego> meeee
[11:09] <Hobbsee> lamego: oh, are you a forums person?
[11:09] <lamego> I am not painting anything, i am being factual
[11:09] <lamego> Hobbsee, I was, for support, when i had the time
[11:09] <Hobbsee> lamego: i didnt realise.  by "forums sheep", i actually meant those who are on the forums only, and who believe that everything is done on ubuntu in a forum - albeit a hidden one.
[11:09] <Hobbsee> lamego: based on the fact that your'e ehre, i doubt that's you.
[11:10] <Hobbsee> i'd say most of us likely started on the forums, and then left it for bigger and better things.
[11:10] <lamego> Hobbsee, ok, so I should feel better now, unlike last year which I was a sheep :)
[11:10] <Hobbsee> lamego: well... :)
[11:11] <Hobbsee> lamego: you're doing getdeb.  you're still stacks ahead of most people, in actually doing productive things in the area of ubuntu
[11:11] <Hobbsee> lamego: how many posts do you really think could have been avoided, on teh forums, if people had searched first?
[11:12]  * persia thinks that's the nature of forums
[11:13] <lamego> Hobbsee, well, how many quetions would have been saved if all people knew how to use google ? That is human nature, something you can't change accord yo your own experience
[11:13] <lamego> according
[11:14] <Hobbsee> why does my own experience tell me that you cant change human nature?
[11:14] <Hobbsee> i seem to have missed that part, and your arguments seem to be mighty weak.
[11:14] <Hobbsee> but this is true.  googling is a skill, and i wish more had it.
[11:14] <Hobbsee> or learnt it.
[11:15] <lamego> you are somehow classifying forums as a "lower" resource, more likely to attract less skilled people
[11:15] <Hobbsee> have you seen evidence to the contrary?
[11:16] <lamego> no, I totally agree with you, however, less skilled, also means, hopeful skilled people
[11:16] <Hobbsee> which, unfortunately, means that they need to make the jump between forum, and non-forum mediums.
[11:17] <persia> lamego: Hopefully skilled is great, and learning is great, but doesn't it make sense to learn by fixing some of the open bugs, rather than arbitrary packaging and forum discussion?
[11:17] <lamego> skilled people is already "in use" :P
[11:17] <Hobbsee> (because they will have to at some point, as we cant implement all development stuff effectively on the forums)
[11:18] <lamego> persia, actually I don't agree with packaging & bug fixing as a common task, packaging is for packages, distribution integrators, bugs, are for upstream providers, developers, which care about their core (the app) and not about the integration with a particular distro
[11:19] <Hobbsee> there are skilled people in many places.  those who know how to prioritize, learn, etc, tend not to be on forums - or active on forums - as they dont post, due to searching.
[11:19] <deadwill> mornin' ubunteros
[11:19] <Hobbsee> hiya deadwill
[11:19] <lamego> developer skills are usefull for packaging, but not a key requirement, understanding makefiles and install process is not app evelopment
[11:19] <persia> lamego: Ah.  My experience is that many bugs are related to packaging, and the rest are small.  Feeding patches upstream is one of the ways I define "skilled".
[11:19] <deadwill> Hobbsee, :)
[11:19] <zul> heh the forum users should just fork everything
[11:19] <Hobbsee> zul: forumbuntu?
[11:19] <Hobbsee> ubuntu forum remix?
[11:19] <zul> Hobbsee: sure whatever turns your crank
[11:21] <Hobbsee> zul: it would be interesting to see how far they got though.
[11:21] <zul> Hobbsee: sure i wouldnt use it though
[11:21] <Hobbsee> you make the assumption that it would release.
[11:22]  * zul must go do option C
[11:22] <RAOF> Ah, the not-awesome part of webmail.  When it breaks into hundreds of shiny, sharp pieces and all I want to do is *go home*!
[11:22] <Hobbsee> muhahahahaha.  [22:17] <Ganneff> yada has to die, its worse than old debmake
[11:23]  * Hobbsee agrees!  rid it from debian, so we can easily rid it from ubuntu!
[11:23] <Hobbsee> Fujitsu: perhaps someone should introduce the concept of yada on the packaging forum?  :)
[11:23] <Hobbsee> RAOF: no ssh into uni?
[11:23] <Fujitsu> Hobbsee: Yes!
[11:23]  * Hobbsee waves to EtienneG
[11:24] <Hobbsee> Fujitsu: which will have nice side effects, of course.
[11:24] <EtienneG> hello Hobbsee !
[11:24] <Fujitsu> Like causing all the forum packagers to die?
[11:24] <Hobbsee> Fujitsu: haha. no
[11:24] <RAOF> Hobbsee: Am in uni.  Plenty of SSH out, and in, but it doesn't help when I was *composing* a message.
[11:24] <Hobbsee> RAOF: ah, true
[11:24]  * RAOF makes a run for it anyway.
[11:24] <Hobbsee> RAOF: was thinking if you went home, and didyour uni work from there
[11:25] <Hobbsee> Fujitsu: no - it just wouldnt ever build in ubuntu - nor get accepted due to it.
[11:25] <Hobbsee> EtienneG: at UDS again?
[11:25] <lamego> persia, packaging bugs are most likely caused by less skilled people, the forum type of people which does not have an use for that particular problem, if they become experienced, then they will leave the forums and help you with the bug fixing
[11:25] <Fujitsu> Hobbsee: Ah, true.
[11:25] <persia> Does anyone happen to know the dctrl-tools magic to generate a list of reverse build-depends?
[11:26] <Hobbsee> persia: erm, let me look
[11:26] <EtienneG> Hobbsee, not this time
[11:26] <lamego> Junior teams are very important, even for major all-star senior teams :)
[11:26] <EtienneG> Hobbsee, are you ?
[11:26] <Hobbsee> EtienneG: oh, i thought you were an employee
[11:26] <Hobbsee> EtienneG: nope
[11:26] <Hobbsee> lamego: assuming they actually get good, at some point.
[11:26] <EtienneG> Hobbsee, yes I am, however, I am not a dev (support analyst)
[11:26] <Hobbsee> EtienneG: ahhhh.
[11:27] <Hobbsee> EtienneG: so you work with kurt?
[11:27] <Fujitsu> Only distro/Launchpad is at UDS, right?
[11:27] <persia> lamego: I'm not sure I agree with forum people == less skilled people, but that aside (and no, I don't want to discuss that uncertainty), I'm not sure of the value of any packages produced by individuals for whom one cannot be confident that packaging bugs can be fixed.
[11:27] <EtienneG> Hobbsee, hopefully, I will participate once a year, but since I was in Seville, I passed on this one
[11:27] <Fujitsu> Hi TheMuso_Boston.
[11:27] <lamego> Hobbsee, well, if you don't get juniors, you never get seniors, unless you expect someone else to handle the juniors for you :)
[11:27] <EtienneG> Hobbsee, yep, I am Kurt's colleague
[11:27] <Hobbsee> persia: grab http://damianv.com.ar/downloads/rbuildepend
[11:27] <Hobbsee> EtienneG:
[11:27] <Hobbsee> EtienneG: " You Poor Bastard"
[11:27] <Hobbsee> :)
[11:28] <TheMuso_Boston> Hey Fujitsu.
[11:28] <persia> Hobbsee: Cool.  Thanks.
[11:28] <EtienneG> Fujitsu, yes, pretty much, although we have a couple of support people from Mtl there too
[11:28] <Hobbsee> lamego: yes, but it's not a grading.
[11:28] <TheMuso_Boston> Not long got up, and doing my morning mail session. :)
[11:28] <lamego> persia, ah, and you believe that you (the team) can actually provide fixes for the entire *universe* ?
[11:28]  * persia waits for the transpacific lines to cleear
[11:28] <Hobbsee> persia: the grep-dctrl lingo i can never remember, although it says in here.
[11:28] <Hobbsee> and i think i wrote a rune for it, in my list of useful runes
[11:28] <persia> lamego: I believe the team can do that, but I also believe that the team is constantly growing.  I don't see value in division: we are all one team.
[11:29] <Fujitsu> The team has to, and the team normally does.
[11:29] <persia> Hobbsee: Yep.  That's my problem too.  I have a list of useful arcana, but still treat it as a grimoire
[11:29] <Hobbsee> hehe
[11:29]  * Hobbsee greps it.
[11:29] <Hobbsee> Fujitsu: in conjunction with debian
[11:29] <Fujitsu> Hobbsee: True.
[11:29] <persia> Hobbsee: Absolutely
[11:30] <Hobbsee> persia.meet( luk__ )  && luk__.meet( persia )
[11:30] <persia> luk__: Hi!  Nice to meet you :)
[11:30] <Hobbsee> luk__: have you seen persia's recent mail on QA to the motu mailing list?
[11:30] <lamego> persia, at the cost, of out-dated packages :)
[11:30] <luk_> hi persia
[11:30] <luk_> yes, I should still answer something I guess ;-)
[11:31] <persia> lamego: That's the nature of division.  If everyone packaging was packaging towards the same goal, that problem wouldn't exist.
[11:31] <Hobbsee> persia: luk_'s one of the debian release managers, and interested in qa collaboration between debian and ubuntu.
[11:31] <persia> luk_: Actually, that mail was more targeted towards getting tools to get a handle on the problems.  We're still a long way behind when it comes to understanding what needs to be done :)
[11:32] <luk_> lol
[11:32] <lamego> persia, not really, the goals are not always compatible, and there are not enough resources to cover all the goals
[11:32] <Hobbsee> lamego: there rarely are.  although ubuntu+debian don't do too badly.
[11:32] <persia> luk_: In terms of sending back, I'm still trying to think of a good model: monolithic packages isn't scaling, and telling everyone who submits a patch to Ubuntu to also submit one to Debian is pushing a lot of useless / meaningless patches into the BTS.
[11:33] <luk_> btw lucas did some piuparts run for Debian, but I still need some time to coordinate filing the bugs
[11:33] <Hobbsee> and getdeb, etc, is a help
[11:33] <Hobbsee> assuming people want to go browsing for each new version of each new app that htey want
[11:33] <persia> In terms of pulling from Debian, I'm hoping that once we can track stuff, we'll be able to adopt more of the existing Debian fixes, which should go a long way towards freeing resources to actually test stuff, and develop useful patches.
[11:34] <lamego> Hobbsee, I am not saying we are bad, I am just saying we can be better, we as, in ubuntu/debian, insert your prefered distro here :)
[11:34] <Hobbsee> lamego: agreed.  we can always do better :)
[11:35] <persia> lamego: Well, I'm uncertain about resources.  I agree about goals.  However, I argue that separation of focus leads to inadvertent duplicate work, which means that someone's effort is wasted.  By coordinating more closely, a greater total sum is accomplished.
[11:35] <luk_> that's why I'm interested in coordination of the efforts
[11:36]  * persia notes that my argument with lamego is in miniature a reflection of Debian's argument with Ubuntu, in some ways
[11:38] <Fujitsu> persia: That's true, to an extent.
[11:38] <lamego> I do have that Debian vs Ubuntu in my pocket for some future getdeb flamewar :P
[11:38] <Hobbsee> persia: excluding those who attempt to go back and fix it each time.
[11:38] <persia> luk_: As I see it, there are a few things to consider: 1) How to preserve valid Ubuntu/Debian variation without increased confusion;  2) How to make sure that QA efforts on both sides are shared smoothly; and 3) How to avoid culture clash (maintainer respect vs. raw collaboration)
[11:39] <Hobbsee> bdmurray: ping when you wake up.
[11:39] <Hobbsee> bdmurray: i'd like a bughelper rune done please.
[11:39] <persia> Hobbsee: I'd disagree.  Even where the Ubuntu and Debian packages are managed by the same person, there is frequently duplicated work due to the intentional differences between the distributions.
[11:39] <Hobbsee> persia: as in sync requests
[11:39] <Hobbsee> yes, perhaps.  main, more so, due to the rosetta exports
[11:39] <TheMuso_Boston> There was actually a discussion about this sort of colaboration between MOTUs and Debian at Fosscamp on the weekend. There were a lot of people involved, including people from core-dev, slangasek, and one or two people who are involved in Debian.
[11:40] <persia> Hobbsee: Main more so, yes.  Parts of universe in reflection, and parts of universe due to attention.
[11:40] <Hobbsee> TheMuso_Boston: i'm oh so glad that this was a public discussion, able for anyone to attend :)
[11:40] <Hobbsee> TheMuso_Boston: did you have a list of things from it?
[11:40] <luk_> persia: well I want to focus on point 2 for now...
[11:41] <TheMuso_Boston> Hobbsee: Not really, it was just an informal discussion. Nobody was taking notes or anything, and unfortunately there was no outside discussion via VoIP afaik.
[11:41] <persia> luk_: I'd agree that is the appropriate focus for our discussion, I just wanted to make sure that the other two were mentioned towards an understanding.
[11:41] <Hobbsee> TheMuso_Boston: *nods*.  thought that might be the case - like the launchpad discussion in sevilla.
[11:43] <persia> luk_: From the Ubuntu side, a lot of our coordinated efforts currently surround FTBFS, NBS, and unmetdeps.  I'm hoping we can expand that to piuparts stuff for this cycle, but I'm not confident we'll get much farther.
[11:43] <luk_> NBS?
[11:43] <Hobbsee> luk_: not built from source
[11:43] <persia> Our uncoordinated efforts are much wider, but given that they are uncoordinated, I'm less sure how to develop a plan to share without running into other issues.
[11:43] <Hobbsee> (binaries)
[11:44] <persia> luk_: NBS: leftover binaries due to library soname transitions, architecture changes in control, etc.
[11:44] <persia> luk_: In terms of those coordinated efforts, how can we best feed you?
[11:44] <luk_> I guess in Debian they are taken care of by a decruft run by ftp-masters
[11:45] <persia> luk_: We also do decruft, but as we don't have sid/testing we need to make sure there are no rdepends first, so there's a bit of API porting, etc.
[11:45] <luk_> ah ok
[11:46] <luk_> what do you exactly mean with feeding me? results/patches of test runs or do you mean tools/people? :-)
[11:48] <persia> luk_: I wasn't thinking specifically of anything: more that we generate variance to fix FTBFS, port rdepends for NBS, and various adjustments for unmetdeps.  This variance can be expressed as patches.  It might also be able to be highlighted in some way for attention.  How would Debian QA most like to receive this work?
[11:49] <persia> luk_: Also note that not all of it applies to Debian.  Examples include python2.5, WX2.8, kernel variations, etc.
[11:49] <Hobbsee> https://wiki.ubuntu.com/QATeam/Specs/DeveloperWeatherReport is starting ot look interesting.
[11:51]  * persia hopes universe is reported (perhaps on a second page)
[11:52] <Hobbsee> i think they're still trying to figure out *what* to do
[11:52] <luk_> well knowing where to look for particular kind of issues would be a start, in Debian most of these are found on http://svn.debian.org/wsvn/collab-qa and http://qa.debian.org/debcheck.php
[11:54] <persia> luk_: For debcheck, we usually target http://alt.qeuni.net/~william/debcheck/, although historically `apt-cache -i unmet` is more common.  If Ubuntu has a fix for Ubuntu, should that be a BTS entry?  Should someone be notified?
[11:54] <lamego> gst.ElementNotFoundError: playbin <- any idea ?
[11:55] <luk_> debcheck is mostly used for Recommends and Priority, though the last one lacks manpower
[11:55] <persia> lamego: The pipeline is broken, and can't figure out how to play the stream.
[11:55] <lamego> hum, I am running inside a schroot
[11:57] <luk_> If there is a fix for a Debian issue, a bug report with a patch attached would mostly be appreciated
[11:57] <persia> luk_: http://svn.debian.org/wsvn/collab-qa looks like a collection of tools to me.  I'm happy to try to organise running them against Ubuntu, and getting people to patch stuff, but that comes back to how to get stuff back.
[11:58] <luk_> yes, it's a collection of tools which are run mostly by lucas
[11:58] <Repsa_Jih> Hmm, I have a question about contributing packages to the universe repository.
[11:58] <persia> luk_: That's actually where we're lacking people most.  From what I understand both the DCT and Utnubu teams get excited each Debconf and UDS, but have difficulty coordinating closely (Utnubu tends not to be MOTU and DCT tends not to be DD), and fail to find the time to actually troll through the variance.
[11:58] <Repsa_Jih> I packaged my game- i think I did it correctly.
[11:58] <Repsa_Jih> I used dput to upload it
[11:59] <persia> Repsa_Jih: See Preparing new Packages in https://wiki.ubuntu.com/MOTU/Contributing
[11:59] <Repsa_Jih> It returned 'Succesfully uploaded packages' and then 'Not running dinstall'
[11:59] <luk_> if we would have some central repository where we can track version information next to the issues, it might be easier to coordinate the fixes
[11:59] <Repsa_Jih> Yeah, I read most of that.
[12:00] <persia> luk_: There are a few factors at work: 1) testing Ubuntu fixes against Debian, 2) sending the patches, 3) getting them applied to Debian (at least from this perspective)
[12:00] <persia> Repsa_Jih: That's the expected output.  It looks like the upload worked.  It should show on REVU in about 10 minutes.
[12:00] <Repsa_Jih> Oh, allright :) Thanks :)
[12:01] <Repsa_Jih> Another, thing, are there any 'lists' or 'requests' of applications that need packaging or upgrading?
[12:01] <persia> luk_: That actually sounds great.  Ideally something that could grab different types of bugs from both LP and the BTS, organise by package, and allow for dynamic commenting.
[12:01] <luk_> persia: in general yes, though for most of the issues of these runs it should be trivial to see if they fix the issue in Debian AFAICS
[12:01] <ScottK> Hobbsee: The MOTU/Debian discussion was part of fosscamp.  It was public to everyone at fosscamp (I was there too).
[12:01] <persia> Repsa_Jih: https://launchpad.net/ubuntu/+bugs?field.tag=needs-packaging
[12:02] <Repsa_Jih> Thanks
[12:02] <lamego> Repsa_Jih, what is your game ?
[12:02] <luk_> persia: yes, that would be great to have
[12:02] <Repsa_Jih> Annchienta, http://annchienta.sf.net/ a adventue 2d rpg
[12:02] <persia> luk_: Depends.  If the package has no variance, testing the patch against sid is easy, but the solution may need to be different for Debian, given different base packages.  If the package has variance, the patch needs to be altered to apply to the Debian package, and then again may not work.
[12:02] <Repsa_Jih> *adventure
[12:03]  * persia seeks a volunteer to draft a base spec (no, not a blueprint) on how a LP & BTS collaboration report site might work
[12:03] <ScottK> persia: But this is not the usual case.
[12:04] <Repsa_Jih> Lamego: sorry I can't seem to send private message because I am not registred here.
[12:04] <lamego> ah
[12:04] <Repsa_Jih> I'll register, hang on.
[12:04] <lamego> ok :)
[12:04] <persia> ScottK: I'm not sure about that.  Trolling the RC buglist right before release, I found that only about 50% of the Debian patches solved the issue for Ubuntu.  I'm not sure it wouldn't be the same in the other direction.
[12:04] <lamego> or just provide me a link for your building rules :)
[12:05] <persia> lamego: Wait a few minutes, and it will be public on REVU :)
[12:05] <luk_> persia: we are only talking about FTBFS and unmet dep issues, right?
[12:05] <ScottK> persia: OK.  Most of the time when sending stuff back to Debian, I know up front if it's a good fix for them or not.
[12:05] <Hobbsee> ScottK: right.  which no one was told about prior to fosscamp :)
[12:06] <persia> luk_: I'd think also NBS, just to speed your various library transitions, but sure, we can only talk about FTBFS and unmetdeps.
[12:06] <ScottK> Hobbsee: fosscamp didn't have a plan in advance.  Each day people just wrote on the board what they wanted to do.
[12:06] <persia> Hobbsee: fosscamp deliberately didn't have an agenda.  Some people there decided to talk about that.
[12:06] <lamego> persia, depending on the package complexity and quality I may be publishing it at the same time it gets the first comment on REVU :P
[12:06] <Hobbsee> fair enoguh
[12:07] <ScottK> Hobbsee: It was mostly getting to know each other kind of discussion.
[12:07] <Hobbsee> ScottK: guess a mailing list post wouldnt have been appropriate, about "we're having a discussion on this now" either - too many people == unproductive discussion
[12:07] <luk_> unmetdeps should be mostly trivial and FTBFS that are not toolchain specific should also mostly be trivial to see if they would apply for Debian or not, no?
[12:08] <persia> lamego: See, that's an example where collaboration could be useful: if it met the requirements for distribution, having you add a +1 would get it in faster.  If it doesn't, having you add the first comment explaining why would get it in faster.  Having you publish it means that someone else still has to do what you did.
[12:08] <ScottK> The most useful thing I got out of it was the notion that when dealing with Debian, you aren't dealing with an organization, but a bunch of individuals, so how you approach it and how it goes will vary widely.
[12:08] <Hobbsee> ScottK: right, yes.
[12:08] <ScottK> Hobbsee: I also got a DD to agree to sign my key so I can start NM.
[12:08] <luk_> lol
[12:09] <Hobbsee> you said.  well done :)
[12:09]  * ScottK is now feeling motivated.
[12:09] <persia> luk_: The operative word is should.  While many of us are likely to make best efforts, I'm just worried about a flurry of random "Doesn't work with python2.5" bugs from those who aren't as careful.
[12:09] <ScottK> As, right.  Forgot.
[12:09] <ScottK> As/Ah
[12:09] <luk_> yes, Debian is mostly a bunch of individuals, though luckily there are also some teams ;-)
[12:09] <lamego> persia, I am not a MOTU, I am reviewing every getdeb package, a la getdeb, which may is not Ubuntu QA, the packages which I am 100% to be Debian QA, are merges
[12:09]  * ScottK goes to make coffee.
[12:09] <lamego> for those, there is not much to review :)
[12:10] <luk_> persia: well you said something about faster library transitions ;-)
[12:10] <persia> lamego: Right.  That's good work.  Doing it for Ubuntu would be better, as it frees up more resources for more people.
[12:11] <lamego> persia, Right, but I prefer to do it for getdeb, because I can do more things, and I have a greater control of the entire release cycle
[12:11] <luk_> what's a getdeb package? I guess I should read some more documentation :-)
[12:11] <persia> luk_: While it doesn't always work, we tend to try to port things to newer APIs sooner.  That's an area where I'm more worried about cultural clash: we tend to work well with Debian teams, and some maintainers, but others tend to be vocal.
[12:12] <persia> luk_: An unofficial repo with newest upstream compiled against most recent stable release Ubuntu.  Policy compliance is variable, but the packages tend to work.  There's a small team maintaining it.
[12:12] <persia> lamego: Sure, it's just that when you do it that way, your effort has no benefit to Ubuntu.
[12:14] <lamego> persia, let's not go into the "outside of the community" again, how does an Ubuntu user using getdeb differs from a Ubuntu user using the repositories ?
[12:14] <lamego> persia, why not ? the building rules are all available, that is the packaging work
[12:14] <persia> lamego: From a user perspective, not much.
[12:15] <lamego> persia, from a developers perspective, the work is available, it may not be good enough for some projects, it may be for others
[12:15] <persia> lamego: Because it still needs the reviews, etc.  Further, often things don't work against the newest development stuff (because they are targeted at the released version).  Lastly, there often appears to be duplication of work done in Debian, which makes for double review.
[12:15] <lamego> you are not talking about work, you are talking about labor
[12:15] <lamego> i mean, MOTU labor
[12:16] <Hobbsee> lamego: from a user perspective, the ability to get automatic program and security updates.
[12:16] <lamego> Hobbsee, that is an acknowledge limitation, being worked
[12:16] <persia> lamego: Right.  That's why I said you would contribute more to Ubuntu by commenting on REVU entries: that means more hands, more can get done.
[12:17] <persia> lamego: Essentially, if we're all one team, keeping all of universe in shape is easier.
[12:18] <lamego> persia, universe aims development, getdeb aims current release, there is no enough people giving attention to the "current" release, from an users perspective
[12:19] <luk_> persia: is there some documentation about all the tools used for Ubuntu QA and where to find them and their results?
[12:19] <lamego> packaging is not all about a distro upgrade and security fixes, not from a end users perspective
[12:19] <persia> lamego: I agree that not enough people are following the current release.  On the other hand, I think I like the method backports uses better: first get it into the development release, then compile against the current release, then get a couple people to test it, then put it on everyone's workstation.
[12:20] <persia> lamego: No, that's a small portion of packaging.  packaging is about making sure users have good software to use, and that the software can be installed and uninstalled cleanly, and that the software is well integrated with the rest of the system.
[12:20] <lamego> persia, I don't have numbers to argue on this, but I am not sure how efficient back ports are, from a throughput perspective
[12:22] <persia> luk_: Not really.  The closest would be the thread starting https://lists.ubuntu.com/archives/ubuntu-motu/2007-October/002600.html, although we've a couple more bits filtering in.  I'll likely update https;//wiki.ubuntu.com/MOTU/TODO (or some subpage) with a more complete list this weekend.
[12:22] <persia> lamego: As I understand it, that's largely a matter of 1) not having very good advertising, and 2) not having very many testers.  I think backports needs a good web interface, some publicity, and a bigger testing team.
[12:23] <Fujitsu> Having backports easily enabled, and not upgrading to backports packages by default, would be a good start.
[12:24] <lamego> persia, I agree, if that happens getdeb can focus only on emerging packages, which are not going into the dev release
[12:24] <persia> Fujitsu: Wasn't someone looking at setting the right variables in Release.gz?
[12:24] <Fujitsu> persia: We know the variables to set, but it will require going through a couple of years of Soyuz quarantine, probably.
[12:24] <persia> lamego: That only creates differentiation.  Why not also get the packages into the development release, and perhaps also into Debian (if they are interested)?
[12:25] <persia> Fujitsu: years?  That's painful.
[12:25] <lamego> anyway, the concerns for packaging into dev, are very different, there you need to care about toolchain changes, policy changes, a lot of changes you dont need to address when packaging for current
[12:25] <Fujitsu> persia: You know how quickly LP moves, particularly new features suggested from the outside.
[12:25] <lamego> a backport can be much more time consuming then just packaging for current
[12:25] <persia> lamego: Actually, the toolchain changes tend to be minor, and the policy is there for a reason: we really don't want to break things (including the law)
[12:26] <Fujitsu> Policy isn't just there for the sake of being there.
[12:26]  * persia seeks a report from a backporting MOTU regarding the relative difficulty of backports
[12:26] <lamego> persia, because, providing the same QA levels, with the current small team (was 1 person at the beginning) would mean, 1 release/week or/day, something which is not compatible with a software portal
[12:26] <Fujitsu> lamego: So don't duplicate the work. Join the normal team?
[12:26] <persia> lamego: Right.  You can't do it alone.  Join the team, and we'll do it together.
[12:26] <ScottK> persia: It's generally quite easy.
[12:26] <lamego> persia, I mean, packaging policies, like moving to python-x.y, dropping php4, etc
[12:27] <ScottK> persia: Where it gets tricky is packages with lots of rdepends.
[12:27] <lamego> persia, I am not alone any longer, a few people have joined
[12:27] <persia> lamego: bring them all: we can certainly use the help.
[12:27] <luk_> persia: ok, I'll try to create a complete list of tools used and their results and issues within Debian QA during this month
[12:28] <persia> lamego: One of the things I'd really like to see for Hardy is a team focused on making sure that it gets a full suite of support, including security, SRU, and backports.  Currently, there have been no volunteers to drive this.
[12:28] <zul_> persia: because its a lot of work?
[12:29] <deadwill> people love SRU
[12:29] <deadwill> :D
[12:29] <persia> luk_: That would be great.  If you could tell me where it ends up (mail is fine, if IRC is awkward), I'll try to get you a list of equivalents (or get them created).
[12:29] <Fujitsu> The Debian security tracker should be able to be integrated-with, which will help with security support.
[12:29] <lamego> uff, I give up, the differences are so clear, and you keep looking at it is the same work but just done on a different team :P
[12:29] <Fujitsu> SRUs, well... we need a million people to triage bugs.
[12:29] <ScottK> lamego: There are differences, but there is also overlap.
[12:30] <persia> zul_: It's not actually that much work, it's more that most devs run the development release.  Having active people using the current release (and, even better the LTS release) makes it fairly easy.
[12:30] <luk_> what are the issues with SRU?
[12:31] <deadwill> luk_, is not an easy/practical task to deal
[12:31] <Fujitsu> luk_: Well, we need to identify the issues and work out if they're SRU-worthy, and then actually do them.
[12:31] <ScottK> luk_: It's not unusual for an SRU to sit in proposed for a long time due to lack of testers.
[12:31] <lamego> persia, I don't find such work appealing, specially SRU  which is great for enterprise managed environments and for core components, but an adoption blocker for home users universe
[12:31] <Fujitsu> ... how does SRU block adoption?
[12:32] <persia> lamego: Sure.  It needs more people.  Like I said, security, SRU, and backports.  I suspect you'd be of great benefit in backports, and would have good advice for those working on SRUs as to whether the new upstream fixes the issue properly, or it needs a target patch.
[12:32] <luk_> ScottK: where can I see what issues are identified and what issues need testing etc?
[12:32] <lamego> Fujitsu, when you can't provide users with key required features which were introduced after the release freeze, because of processes or because of lack of human resources to handle such upgrades
[12:33] <Hobbsee> or because they may break other things.
[12:33] <lamego> you bough this new gadget yesterday, which is only supported by the new upstream release X.Y, that will not go though SRU
[12:33] <Hobbsee> which is why the SRU is in.
[12:33] <Hobbsee> sure, but there are backports.  and that sounds kernel-ish.
[12:34] <ScottK> luk_: Look for bugs tagged verification-motu-needed to see where Universe SRUs need testing.
[12:34] <persia> luk_: https://launchpad.net/ubuntu/gutsy/+bugs is an example URL for gutsy.  Adjust the URL to suit.  It's not a perfect list for various reasons, but it's fairly close.
[12:34] <lamego> Hobbsee, right, I trust more on some upstreams than I trust on some SRUs, it all depends on who manages such upgrades, it depends also on the upstream QA :)
[12:34] <Hobbsee> lamego: indeed.  which is why we test too - for the case where upstream's QA fails.
[12:34] <ScottK> lamego: When was the last time an SRU was published and caused regression?
[12:34] <Hobbsee> if upstream's QA is good, then it should go fairly well.
[12:35] <Hobbsee> and quickly
[12:35] <Hobbsee> particularly universe
[12:35] <persia> lamego: Actually, for universe packages, gadget-foo only supported by upstream X.Y is sometimes considered, especially for upstreams with good QA.
[12:36] <lamego> persia, sure, the cost to develop a specific patch for an SRU, versus adopting the new upstream release which includes much more, is sometimes much higher compared to the effort of fixing any regression that you may be afraid to introduce
[12:37] <lamego> specially, being an universe package, and a non disruptive or blocking regression, which you would identify during the package validation, or, on a timely manner
[12:37] <Fujitsu> lamego: It's better to not have regressions at all, rather than be trying to fix them later.
[12:37] <persia> lamego: Depends on the upstream.  We often publish new upstream versions (especially in stable release series) for SRUs.  What we try to avoid is changes in behaviour - we don't want to break the user workflow.  For new features, we use backports.
[12:37] <lamego> Fujitsu, I could argue that, you don't have regressions, you have tons of bugs which were fixed upstream :)
[12:38] <Fujitsu> lamego: Right, then you find the patches that fixed them. Look at them. Note lack of regression potential.
[12:38] <lamego> how do you handler for example, game upgrades, which include the core network game changes ? is anyone insane enough to provide such a patch without going through an upstream release backporting ?
[12:38] <Fujitsu> No.
[12:39] <Fujitsu> Backports handle that.
[12:39] <Fujitsu> I don't think I've seen an SRU for that sort of things.
[12:39] <Fujitsu> *thing
[12:39] <persia> lamego: Those are generally cases where we want to push a new upstream.  Depending on the available servers, that may be a backport, or it may be an SRU (usually backports, as the process is faster)
[12:39] <lamego> right, on this particular case (there are others), SRU will keep a dead application on the repositories :)
[12:39] <lamego> I mean dead, because game servers, and windows gamers, move to the next version ;)
[12:40] <lamego> replace windows with others, to avoid OS comparison :P
[12:41] <persia> lamego: Why?  If the change to the network protocol is small enough to warrant SRU (or even -security, in some cases), I don't see how it would be dead.
[12:42] <lamego> persia, the network changes may not be small, and usually depends on other game features = new upstream release
[12:43] <lamego> anyway, this was just an example on for several cases, SRU may be a limitation, from an user's perspective, I clearly understand it's purpose from a QA perspective, specially if you are aiming enterprise
[12:43] <persia> lamego: Right.  If it's too big for SRU, we use a backport, and integrate for the next release.
[12:43] <persia> lamego: The important point is that *both* SRU and backport should be available, to reach all audiences.
[12:43] <lamego> persia, you could do it, but it is not being done, on a proper published form, it is not reaching the users
[12:44] <persia> lamego: Right.  We need advertising and testing.  Wanna help?
[12:45] <lamego> persia, I am doing it already, at the cost of the things that you get from backports, like working first on the dev release, do you want to help :) ?
[12:45] <luk_> are the packages listed on http://people.ubuntu.com/~ubuntu-archive/pending-sru.html#universe the ones that need more testing?
[12:45] <zul> /m/msg Hobbsee around still?
[12:45] <zul> doh..
[12:45] <Fujitsu> luk_: Quite possibly. I hadn't seen that page previously.
[12:46] <persia> luk_: They could well be.  I'm not sure how often that gets updated, and it doesn't reflect things that were rejected, but haven't been pulled from -proposed.
[12:46] <Repsa_Jih> I have to go, bye
[12:48] <lamego> persia, and don't get me wrong, I hope backports get into shape, there is a lot to be done on Ubuntu, it getdeb becomes irrelevant, next :)
[12:48] <persia> lamego: Actually, I'm fairly poor at packaging new software: I'm not sure I'd be a good candidate.
[12:49] <lamego> I have seen there are some blueprints for Hardy which aim to improve Ubuntu's software distribution
[12:50] <persia> lamego: I'm not sure I agree that getdeb should become irrelevant.  You've built a really nice UI, and a strong mirror system.  I'd just like to see more integration.  Specifically, 1) getting all the new stuff in getdeb into the repos & policy compliant, 2) making sure there is infrastructure to support security for getdeb, and 3) sharing resources with backports.
[12:50] <deadwill> This release of the ATI Catalyst™ Linux driver introduces the following new features:
[12:51] <deadwill> #  Support for Accelerated Indirect Rendering (AIGLX)
[12:51] <deadwill> wowww
[12:51] <deadwill> finally
[12:51] <deadwill> :)
[12:51] <lamego> persia, the problem is just one, lack of time and resources, but yes, we are working on it: https://wiki.ubuntu.com/GetDebPlan
[12:52] <hellboy195> deadwill: that was 2 weeks ago O_o
[12:53] <deadwill> hellboy195, heh, i only see that right now
[12:53] <luk_> persia: why are rejected items still mentioned is that a bug in that page or are rejeced packages still in -proposed?
[12:53] <persia> lamego: I like to see that.  I'd encourage you to look at pushing all the stuff not in Ubuntu into REVU (multidistrotools might help), and pulling from backports where possible to leverage those efforts.
[12:54] <hellboy195> deadwill: ^^. another 2 weeks and the new one arrives ;)
[12:54] <ScottK> luk_: Proposed generally doesn't get cleaned out.  Rejected stuff is generally not in *-proposed, but often stuff that's already been published is.
[12:54] <tuxmaniac> hello All. Can someone please tell me why I get this error during a pdebuild. I suppose I have libxft-dev and the necessary dev packages mentioned int he control file http://pastebin.ubuntu.com/1569/
[12:55] <tuxmaniac> the control file is pasted here http://pastebin.ubuntu.com/1570/
[12:56] <persia> luk_: As ScottK said, but also that removal from -proposed requires archive-admin attention, which is not always as available as we might want :)
[12:57] <persia> (and people forget to file removal bugs to ask for the attention)
[12:57] <luk_> hmm that feels like home (read Debian) :-)
[12:58] <persia> luk_: Yep.  For any distro, only so many people can actually have that level of access, or it all breaks down.  Unfortunately, there's not enough of them (and a fair number seem to be shared between us)
[13:01] <tuxmaniac> somebody aroud?
[13:02] <lamego> persia, we use a different approach for reviewing, http://wiki.getdeb.net/Automated_Build_System for the building, and launchpad bug records for the reviewing process communication
[13:02] <StevenHarperUK> Hi any MOTU's doing review on the REVU server today?
[13:02] <persia> tuxmaniac: Sorry.  Too many things at once.  I'm not sure of the specifics, but it looks like a library split.  Look for a libxext (or similar) library.
[13:03] <tuxmaniac> persia, no problem
[13:03] <tuxmaniac> :)
[13:03] <persia> StevenHarperUK: Yes, but you're unlikely to have easycrypt reviewed.  Your last request was < 15 hours ago, and the previous < 8 before that.  Please request less often, or wait for a REVU day.
[13:03] <Hobbsee> tuxmaniac: i wonder if you actually need libxft* itself - not the dev package
[13:03] <StevenHarperUK> persia: yeh I asked 2 times yesterday as the channel was so quiet
[13:04] <StevenHarperUK> persia: this is my once only request today
[13:04] <StevenHarperUK> persia: thanks for checking thou :p
[13:04] <persia> StevenHarperUK: Check irc.ubuntu.com :)
[13:06] <persia> StevenHarperUK: Also, to be fair, I'm in a different timezone than you, so my day doesn't match yours :
[13:06] <persia> )
[13:07] <StevenHarperUK> persia: I am sure my persistence will pay off, I am trying to contribute
[13:07] <persia> lamego: I think that's a great model, and likely results in good packages.  I was really just hoping to see that once you'd accepted something, if it wasn't in the archive, it also went to REVU so it could be included.
[13:08] <ScottK> StevenHarperUK: You just showed up at a bad point in the release cycle.  It'll pick up in the next week or two.
[13:08] <lamego> need to go now, I hope to continue this conversation other day :)
[13:08] <persia> StevenHarperUK: Your contribution is appreciated.  However we impose the 1/24hr rule (which sometimes means less than once a local day) in order to keep from being inundated with requests.  Persistence is good, but so is patience.
[13:09] <persia> lamego: OK.  I'm really interested in coordination (although I can't help with that stuff much), so please ping me anytime to continue.
[13:09] <lamego> ok :)
[13:10] <StevenHarperUK> Ok waiting......
[13:10] <zul> hey jono
[13:12] <persia> StevenHarperUK: Thanks.  Personally, I think the package is getting in much better shape, and that it may well likely get approved in the next REVU day (as long as you don't bump into the "too many requests" rule) :)
[13:12] <jono> hey zul
[13:12] <ScottK> Although asking more often (after you've fixed stuff) during a REVU day is generally OK.
[13:13] <StevenHarperUK> persia:its only improved because of how helpful you motu guys are.
[13:13] <persia> Ah.  Yes.  ScottK has a point.  During REVU day, anyone with an updated package should ask for each update.
[13:16] <StevenHarperUK> Is it Nov the 5th : the next one?
[13:16] <ScottK> If that's Monday, then yes.
[13:17] <StevenHarperUK> Ace I can't wait.
[13:20] <porthose> how can I tell if my package has been imported from debian? :)
[13:21] <persia> porthose: rmadison vs rmadison -u ubuntu does a good job.
[13:21] <persia> porthose: You could also check http://people.ubuntu.org.au/~fujitsu/motuscience/versions/universe.html
[13:22] <porthose> persia: thanks
[13:28] <Zelut> can anyone tell me why I can tab-complete a kernel-patch-openvz package but when I try to 'show' or install there is no such package available.
[13:28] <MarcC> How can I get in touch with the person who built GIMP for Gutsy?
[13:29] <persia> Zelut: What does apt-cache search kernel-patch-openvz report?  That might have a hint.
[13:30] <persia> MarcC: You can't: everything was built automatically.  What would you ask them if I had a different answer (perhaps we can help)
[13:30] <Zelut> persia: I get this: vzctl - server virtualization solution - control tools
[13:30] <MarcC> weellll...actually I thought that GIMP wasn't correctly finding the number of CPUs on a system
[13:31] <MarcC> but now it turns out the upgrade to Gutsy lost one of my cores :-/
[13:31] <Zelut> persia: and if I 'show' on that package I see this in the long description:
[13:31] <Zelut> OBSERVE! You need a Linux kernel patched with openvz support. You can use the package kernel-patch-openvz to build your custom Linux kernel.
[13:31] <MarcC> ...since GKrellm and Java both report 1 processor now too
[13:33] <persia> MarcC: That sounds more like a kernel issue or a BIOS issue (or possibly a hardware issue, although I doubt it).  Were I you, I'd report a bug.
[13:33] <ScottK> MarcC: You probably want #ubuntu for support.
[13:33] <MarcC> thanks persia
[13:34] <MarcC> ScottK: I asked there but honestly, it's too crowded, my question got lost I think. But I know this is not a support channel.
[13:35] <ScottK> MarcC: If a CPU is missing, then it's likely kernel.  If you want to hang out on a relevant development channel, that'd be #ubuntu-kernel, but I'd suggest spending some quailty time with Google before asking there.
[13:35] <MarcC> Thanks ScottK
[13:38] <MarcC>  it turns out that menu.lst for GRUB got changed so that the correct Kernel is no longer default. Thanks for the help.
[13:38] <ScottK> No problem.
[13:39] <persia> Zelut: My apologies: I'm not finding the LP page I want.  It's somewhere around https://launchpad.net/ubuntu/+source/vzctl/.  There should be information about binary packages; I suspect the control file needs a patch.  If you can fix it, please submit the fix.
[13:45] <geser> Zelut: the kernel-patch-openvz not included in Ubuntu (like other kernel-patch packages) as it won't apply on the Ubuntu kernel and Ubuntu doesn't want to maintain those patches that they work with the Ubuntu kernel
[13:46] <zul> Zelut: you are better getting the sources from upstream
[13:47] <zul> especially for openvz
[13:47] <geser> persia: as the openvz isn't in the Ubuntu kernel (I haven't checked if it is or not) should we still ship such tools in hardy?
[13:47] <zul> or wait for hardy
[13:48] <zul> i think there is a bof for that doday at UDS
[13:48] <Zelut> geser: I think the confusing thing is that tab-complete finds a kernel-patch-openvz package, yet nothing is there.
[13:49] <geser> Zelut: I guess it's because it is mentioned in Suggests for vzctl
[13:50] <persia> geser: Hrm.  That's an interesting question.  In some ways, I'm in favor of shipping foo-source, so that users can compile it against the kernel headers if they wish, but we should at least make the documentation clear.
[13:50] <zul> or they should be removed from universe
[13:52] <persia> zul: That's the other possibility.  It depends on the view of universe.  Do we provide everything else, or a useful set of software?  If the latter, what is our inclusion policy?
[13:53] <geser> persia: kernel-patch-* are different from foo-source as the first is a kernel patch (you need to build your own kernel) and the second is only a kernel-module (the kernel-headers should be enough)
[13:53] <geser> kernel-patch-* are already on the sync blacklist
[13:54] <persia> geser: Ah.  Right.  In that case, I'd argue for the removal of foo-tools where it requires kernel-patch-foo, based on the guideline that everything should be useful.
[13:54] <persia> (of course, if there is a foo-source for modules, I argue for inclusion)
[13:56] <zul> no, then they would break everytime the kernel ABI changes
[13:57] <persia> zul: Right, but the kernel ABI almost never changes for a real release.
[13:59] <zul> persia: it somtimes does, there were a couple of times during the dapper release cycle
[13:59] <bddebian> Heya gang
[14:00] <zul> persia: the ipw2200 sources should be removed as well
[14:00] <geser> Hi bddebian
[14:00] <persia> zul: Were any of those prior to Edgy release?  I'd think that LTS users who relied on module sources could be trusted to recompile.  Alternately, making a better hook for the automatic module tools might be nice.
[14:00] <zul> persia: yes in dapper
[14:01] <persia> zul: I completely agree with that.  The mainline support for .24 is much better.  I've been waiting for the official results of the kernel-team decision on .23 vs. .24
[14:01] <persia> zul: Ah.  That's not desireable.  Better tools are needed, I guess.
[14:01] <zul> its going to be .24 most likely
[14:02] <persia> zul: Has that been confirmed?  I thought the security team was still in hot debate.
[14:04] <zul> persia: i think 2.6.24 is being rebased now by the kernel team
[14:05] <persia> zul: So fast?  I'm glad to hear it, but it definitely highlights how hard it is to follow things from the other side of the globe :)
[14:06] <persia> zul: If yuou can confirm that, please file a removal bug for ipw2200
[14:06] <zul> sure
[14:08] <persia> zul: Thanks.
[14:08] <bddebian> Heya geser
[14:30] <norsetto> siretart: I see still some references in https://wiki.ubuntu.com/MOTU/Merging to motu-tools and multidistrotools. They are obsolete now right?
[14:35] <geser> norsetto: we still have some mdt setups but the mdt page is outdated
[14:36] <norsetto> geser: right
[14:36]  * persia notes that http://people.ubuntu.org.au/~fujitsu/motuscience/versions/universe.html is being updated hourly by a cron job.
[14:38] <luk_> what's DIF, I guess a Freeze, but which kind?
[14:39] <geser> Debian Import Freeze
[14:39] <geser> no auto-syncing of Debian packages anymore (only on request)
[14:43] <siretart> norsetto: sorry, no idea right now
[14:44] <norsetto> siretart: ok, thx
[14:51] <persia> norsetto: motu-tools is replaced by ubuntu-dev-tools.  multidistrotools is active, but not packaged.  See the URL I posted a bit back.
[14:54] <norsetto> persia: Right. What would be the alternative to lpbugs.py then, if any?
[14:55] <persia> norsetto: thekorn made a really nice python program, with optional GUI.  Unfortunately, while he told me the name, I've forgotten, and haven't found it.  If you can't catch thekorn, dholbach might remember the name.
[14:55] <norsetto> persia: ok, I remember using some tools from thekorn too
[14:56] <persia> norsetto: If you find it, please let me know.  I really want to be using it for hardy, but...
[15:07] <Hobbsee> persia: so when will you file a backport for gnome-hearts?
[15:07] <Hobbsee> you'll have to do the testing for it, too
[15:08] <persia> Hobbsee: Backport?  Is there no SRU option?  It completely fails, so there's little downside risk (not that I'm a good judge of SRU stuff).
[15:09] <ScottK> persia: pitti bought off on a new upstream version of Azureus due to not working at all, so it seems reasonable.
[15:09] <ScottK> for SRU
[15:10] <persia> ScottK: That's what I was thinking.  Essentially, due to differences between Debian and Ubuntu gnome-games and gnome-cards, gnome-hearts in gutsy is broken.  Hobbsee fixed it for hardy by pulling a new upstream and patching it wildly, but someone with a better SRU idea than I should review for gutsy.
[15:11]  * persia 's one and only SRU attempt, fixing a FTBFS + fail to run for feisty was rejected because it apparently didn't work despite local testing.
[15:11] <LaserJock> bummer
[15:12] <Hobbsee> persia: new upstream version.  might do a sru.
[15:12] <Hobbsee> persia: well, no, i pulled the debian version, adn pulled the troublesome patches.
[15:12] <Hobbsee> because they looked useful
[15:13] <Hobbsee> old code got mostly rewritten anyway - looks like debian's redone most of their packaging - adn they only had 2 patches anyway
[15:13] <Hobbsee> (originally)
[15:13] <persia> Hobbsee: Thank you.  The "crashes fro crack" bit is flipped on my worksttion, so things that work for me don't always seem to work for others, and I usually crash every few hours until the first dev kernel release for each new official stable release.
[15:14] <luk_> Hobbsee: s/adn/and/ or are you talking about the IRC nick 'adn'?
[15:14] <Hobbsee> luk_: no, it's the fact that i cant type for shit, especially after 2am :P
[15:16] <LaserJock> !ohmy | Hobbsee
[15:16] <ubotu> Hobbsee: Please watch your language and topic, and keep this channel family friendly.
[15:17] <LaserJock> hehehe
[15:17]  * ScottK moves to the other side of the room from LaserJock
[15:17] <Hobbsee> LaserJock: as i kept saying to our oscilloscope on monday, "die".
[15:17] <Hobbsee> :P
[15:17]  * persia decides that November 2nd should start later...
[15:18] <Hobbsee> to saying that, not for you yourself to die off
[15:18] <Hobbsee> perthe comments referred to the old version, btw
[15:18] <Hobbsee> bah
[15:35] <deadwill> hey LaserJock, hi!
[16:16] <LaserJock> hmm, I thought DaD was going away?
[16:20] <ScottK> LaserJock: After perhaps MoM provides equiavlent functionality.
[16:21] <ScottK> That part hasn't got done yet.
[16:22] <LaserJock> hmm
[16:22] <LaserJock> hopefully that gets done soon
[16:22] <LaserJock> it's really no fun looking at multiple places :/
[16:23] <ScottK> LaserJock: Unfortunately we are dependent on Canonical people to decide to pay attention to it.  They haven't yet.
[16:23] <LaserJock> ScottK: do you know if anybody has submitted a patch or anything?
[16:23] <StevenK> Personally, I don't think comments are *that* useful.
[16:23] <ScottK> LaserJock: How could they?  No one has the MoM source.
[16:24] <LaserJock> StevenK: I agree, but I don't want people getting mad at me cause I didn't look at DaD
[16:24] <LaserJock> ScottK: I thought there was an agreement about that
[16:24]  * StevenK doesn;t.
[16:24] <StevenK> (Look at DaD, that is)
[16:24] <ScottK> LaserJock: There was discussion.  AFAIK, no source actually got provided, but Adri2000 or Lutin would know better.
[16:24] <LaserJock> k
[16:24] <LaserJock> we should wrap that up as a part of the MOTU process review
[16:25]  * ScottK tends to look at DaD (it updates more frequently anyway) and then use whichever proposed merge seems cleaner.
[16:26] <LaserJock> I just can't ever remember the URL for DaD so I go with MoM
[16:26] <ScottK> LaserJock: ^^^ /topic
[16:26] <LaserJock> DaD's got a pretty slick look though
[16:27] <LaserJock> yeah, well, with irssi I don't really see topics
[16:27] <ScottK> Ah.
[16:27] <LaserJock> but yeah, that's true
[16:27] <ScottK> If I actually understood the color coding scheme on MoM, I might be more likely to look there.
[16:28] <LaserJock> yeah, I've never understood it, but it doesn't matter to me
[16:28] <LaserJock> I just merge stuff with my name on it then start looking for other things to do
[16:28] <ScottK> Speaking of which ...
[16:28] <ScottK> fernando: How goes courier?
[16:31] <fernando> ScottK: http://www.nerdgroup.org/fernando/files/courier_0.57.0-1ubuntu1.debdiff
[16:34] <ScottK> fernando: Why did you add Depends openssl to courier-pop-ssl?
[16:36] <ScottK> fernando: Or is that a previously existing difference that you've just documented?
[16:40] <ScottK> fernando: Looks pretty good.  Would you please file a merge request bug, attach that to the bug, and subscribe UUS?
[16:55] <norsetto> anyone here knows the differences between the light and dark green packages in MoM?
[16:58] <TheMuso_Boston> norsetto: i was told that the colours were something to do with priority.
[16:58] <norsetto> TheMuso_Boston: ok, so light lower and dark higher I assume !?
[17:02] <TheMuso_Boston> norsetto: I don't know.
[17:02] <norsetto> TheMuso_Boston: np, thanks :-)
[17:04] <norsetto> You guys may want to check https://wiki.ubuntu.com/MOTU/Merging; I have made extensive modifications and tried to bring it up to date with current tools and practices
[17:04] <norsetto> hmmm, better link here https://wiki.ubuntu.com/MOTU/Merging
[18:14] <ScottK> norsetto: I made some minor adjustments on the merges page.  It looks pretty good.
[18:14] <norsetto> ScottK: thx, I think that was really needed.
[18:16] <ScottK> The one change I made that is probably significant is the bit about filing bugs if you are working on a merge.  If you are the previous uploader, I don't think it's needed and I don't recall any MOTU meeting where it was agreed to.
[18:18] <norsetto> scottK: ah, well, in my mind that page is for new contributors, I assume MOTU know how to merge
[18:19] <james_w> Hi, I would like to have a merge upload reviewed, is there a pointer to documentation about getting a review I can read?
[18:19] <ScottK> norsetto: Right, but I don't want anyone to assume that the lack of a bug means it's a free for all.
[18:19] <ScottK> james_w: https://wiki.ubuntu.com/MOTU/Merging covers this.
[18:20] <norsetto> ScottK: ok, let me check then, perhaps I misunderstood you
[18:20] <hellboy195> ScottK: did you have already time to look for a motu that decided on gimp (we talked about it yesterday). If not I could also search for one by me own ;)
[18:24] <norsetto> scottK; well, contributors anyhow have to file the bug even if they were the previous uploaders
[18:25] <ScottK> hellboy195: No.  Gimp is in Main, so it would have been a core-dev, not a MOTU.
[18:26] <ScottK> norsetto: Agreed, it's just a question of making sure lack of a bug isn't thought to be meaningful.
[18:26] <hellboy195> ScottK: I mean the decision to put it NOT into updates but in backports
[18:27] <ScottK> hellboy195: Once again, not a MOTU, core-dev because the package is in Main.  No.
[18:27] <jdong> doko: what are we gonna do in Ubuntu to get swt-gtk v3.3? I'm looking to sync Azureus <IP_ADDRESS> from Debian for Hardy and need swt-gtk 3.3 to continue (not high priority)
[18:28] <hellboy195> ScottK: ok than I have to look for a core-dev. thx anyway
[18:28] <StevenK> Why would we put a new gimp into -updates?
[18:28] <StevenK> What is wrong with rc3 that justifies it?
[18:28] <ScottK> hellboy195: ^^^
[18:28] <james_w> thanks ScottK.
[18:28] <StevenK> If you say version number, that is *not* justification.
[18:28] <ScottK> james_w: You're welcome.
[18:28] <zul> the number is higher so it must be good
[18:28] <doko> jdong: build eclipse?
[18:29]  * StevenK kicks zul
[18:29] <zul> StevenK: ehehe..
[18:29] <hellboy195> ScottK: !?
[18:30] <zul> StevenK: oooh...shiney..
[18:30] <jdong> doko: :( is that going to be nontrivial?
[18:30] <ScottK> hellboy195: Look at what StevenK said just above my highlighting you and you'll have your GIMP conversation started.
[18:31] <hellboy195> ScottK: A thx. I only focused on you
[18:31] <jdong> doko: why don't we use separate source packages for swt-gtk like what Debian does?
[18:31] <hellboy195> StevenK: 2.4 final isn a new version. final is FINAL and I think everbody prefers a final and not a RC
[18:32]  * norsetto relax and watch the show
[18:32] <StevenK> hellboy195: Which is version number. And not justification.
[18:32] <ScottK> jdong: Building eclipse is impossible with < 1GB RAM.  1GB RAM will get it done in ~18 hours due to disk thrashing.  More memory gets it done a lot faster.
[18:32] <norsetto> scottk, jdong: confrmed :-(
[18:32] <hellboy195> StevenK: that mean the RC3 is the same then the final?
[18:32] <jdong> that sounds a bit silly to me.... why don't we split out swt-gtk into its own source package
[18:32] <jdong> like how Debian's been doing it
[18:33] <doko> jdong: because the "swt-gtk like" packages don't work for eclipse
[18:33] <StevenK> hellboy195: I'm not certain, which isn't the point. My point is we won't put a new upstream release into -updates.
[18:34] <jdong> doko: ok, so it will cause trouble when we upgrade eclipse to 3.3?
[18:34] <geser> in the "Ubuntu QA for hardy" thread it was mentioned that the archive should be linda & lintian clean. How strong do we want this? I'm doing a merge now and have the choice to sync or introduce new changes to fix lintian warnings.
[18:36] <hellboy195> StevenK: from RC3 to final is a new upstream version???? shouldn't ubuntu be stable and RC IS unstable to take it exact and final not. besides that already a bugfixrelease of gimp has been released
[18:36] <StevenK> How is the RC unstable?
[18:36] <doko> jdong: you need to package it. your next challange ;)
[18:36] <bddebian> heh
[18:36] <StevenK> Just because the version jumped from 2.4.0~rc3 to 2.4.0 means nothing.
[18:37] <ScottK> hellboy195: If you haven't looked, you need to look at the actuall bugs (if any) that were fixed to see if they are important.
[18:37] <zul> how is rc3 not stable?
[18:37] <hellboy195> StevenK: partially. but most times bugs from rc3 are fixed in the final
[18:37] <jdong> doko: would it be a bad idea to do what Debian does, ship libswt3.2-gtk for Eclipse that comes from Eclipse and libswt-gtk-3.{2,3} for other apps that use SWT?
[18:37] <pwnguin> hellboy195: maybe if you provided a diff between releases that suggested some fixes..
[18:37] <StevenK> hellboy195: Fine. I need examples, Launchpad bugs and *justification*
[18:38] <hellboy195> StevenK: the most justification is that final looks more stable and better than rc3 ;)
[18:38] <StevenK> That isn't justification.
[18:38] <doko> jdong: yes, if you do include the osgi bits
[18:38] <pwnguin> looks more stable
[18:38] <StevenK> That's conjecture
[18:39] <doko> jdong: and no, the debian packaging is insane, as man-di told you as well
[18:39] <ScottK> hellboy195: I'd suggest get some specific details and come back to speak with StevenK later.  He can probably fix it for you if he's convinced.
[18:39] <jdong> doko: got it, you don't think Debian packaging is done right :)
[18:39] <pwnguin> hellboy195: aside from vague gimp developer assurances that final means stable, is there any proof that final is MORE stable than the rc in Ubuntu?
[18:39] <norsetto> ScottK: ok, I think I understand what you are aiming at now. I'm just afraid that this could confuse new contributors in the unlikely case they have already worked on the previous case.
[18:40] <joejaxx> jdong: are you going to visit us anytime soon? :D
[18:40] <doko> jdong: the debian packaging for swt-gtk (and azureus); btw, you did want to re-add the missing patches, didnt you?
[18:40] <hellboy195> pwnguin: ScottK StevenK : well guys I didn't want to grumble or things like that. Sry for that. I was just wondering
[18:40] <jdong> joejaxx: probably Friday
[18:40] <ScottK> hellboy195: If there's a real justification for it, fine, but just it's a later release, isn't that.
[18:40] <joejaxx> jdong: oh ok :D
[18:41] <jdong> doko: I have good reason from upstream to conclude that the native tabbingtheming patches are in part responsible for its instability in Ubuntu
[18:41] <hellboy195> ScottK: well 2.2 to 2.4 isn't the same like a 2.4RC3 to 2.4
[18:41] <pwnguin> hellboy195: If there is proof, MOTU can consider that. but it just looks like an obsessive compulsive need to have the latest
[18:41] <jdong> doko: so I don't really see the sense in adding them back in when without them Azureus works perfectly fine
[18:42] <doko> "good reason" is a vapour statement
[18:42] <pwnguin> hellboy195: but without specific evidence, you're risking the current package quality for the reward of fixing nothing
[18:42] <ScottK> hellboy195: Agreed, but to make any change at all to a release requires technical justification.
[18:42] <StevenK> 2.4.0~rc3 to 2.4.0 is still a new upstream release
[18:42] <StevenK> Both are distinct releases.
[18:43] <hellboy195> pwnguin: ScottK okthx
[18:43] <pwnguin> hellboy195: like world nuclear politics, the best course of action in upstream release engineering is "trust, but verify"