[00:21] <jscinoz> hmm
[00:22] <jscinoz> looks like someone misspelled cache in the description of the packagekit packages :P
[01:53]  * nhandler is away: Away
[02:13]  * nhandler_AFK is back (gone 00:20:39)
[02:20] <marnold> hmmm
[02:21] <marnold> opps sorry erong window
[02:21] <marnold> wrong*
[04:02]  * nhandler is away: Away
[04:32] <Hobbsee> bah.  jono's gone
[04:33] <ajmitch> given the time, I'm not surprised
[04:35] <Hobbsee> well it was 7.36am local time of the ping
[04:37] <ajmitch> maybe he looked at the thread on ubuntu-devel-discuss & gave up in despair
[04:37] <ajmitch> poor nixternal, being a microvell shill
[04:43] <ScottK> It was pretty ironic that he got singled out.
[04:44] <ajmitch> He dared to defend opensuse
[04:44] <ajmitch> That Mark Fink fellow does seem slightly irrational though
[04:45] <ScottK> For some large definition of slightly, yes.
[04:45] <persia> Could be a short definition too.  "very" works well.
[04:46] <ajmitch> well, it provided some entertainment this morning when I sat down to read email :)
[04:57] <jono> Hobbsee: ping?
[04:58] <ajmitch> ah, there he goes
[05:00] <ajmitch> Hobbsee was around just 25 minutes ago
[05:01] <LaserJock> man, I wonder what power that pointy stick of doom holds that she can summon people half a world away ;-)
[05:01] <ajmitch> It can even summon people from on vacation
[05:01] <jono> heh
[05:01] <persia> ajmitch: Never underestimate the power of the Long Pointy Stick
[05:02] <Hobbsee> jono: pong
[05:02] <Hobbsee> LaserJock: hah.  it's very powerful.
[05:02] <jono> Hobbsee: :)
[05:02]  * ScottK considers popcorn.
[05:03] <ajmitch> persia: it's certainly scary, that's for sure
[05:04] <Hobbsee> ajmitch: it's been known to almost set someone's house on fire, too
[05:04] <ajmitch> uh oh
[05:05]  * ajmitch had better get home quick
[05:09]  * imbrandon hides his flamable house
[05:10] <Hobbsee> imbrandon: you have an *in*flammible house?
[05:11] <imbrandon> nope the stick could bring its wrath down on it if wanted, thus i hid it
[05:12] <ajmitch> hello imbrandon
[05:12] <imbrandon> heya ajmitch
[05:12]  * imbrandon replaced his xbox with ubuntu+xbmc :)
[06:58] <dholbach> good morning
[07:01] <ajmitch> hi dholbach
[07:01] <dholbach> hi ajmitch
[07:08] <geser> good morning dholbach
[07:08] <dholbach> hi geser
[07:13] <nxvl> morning!
[07:13] <nxvl> dholbach: i was looking for you
[07:14] <dholbach> hi nxvl
[07:14] <nxvl> dholbach: did you have the gobby document we use on the Packaging Jam on Prague?
[07:14] <nxvl> i going to run some packaging Jams here
[07:14] <nxvl> and i want to merge some docs
[07:14] <dholbach> nxvl: no I'm sorry - I didn't save it
[07:14] <nxvl> to prepare my material
[07:14] <dholbach> nxvl: https://wiki.ubuntu.com/PackagingGuide/HandsOn should be a good start though
[07:14] <nxvl> mm
[07:15] <nxvl> dholbach: yes, i was looking at this doc, i just want some more for the examples
[07:15] <dholbach> nxvl: try fixing a bitesize bug
[07:16] <nxvl> dholbach: yep, i will
[07:16] <nxvl> if i have time
[07:16] <nxvl> since it's a conference i have been invited i don't know how much time i have
[07:16] <nxvl> i'm going to have some sleep
[07:16] <dholbach> nxvl: I'm sure it's going to be great! :)
[07:16] <nxvl> see you later!
[07:17] <nxvl> dholbach: i hope!
[07:17]  * dholbach hugs nxvl
[07:17]  * nxvl HUGS dholbach back
[07:36] <\sh> why nobody tells me, that I'm now a member of motu sru team?
[07:37] <persia> \sh: Well, you're supposed to be subscribed to ubuntu-motu@ ...
[07:37] <\sh> persia: it's monday morning...and I'm trying to catch up
[07:37] <\sh> :)
[08:04] <\sh> hmm....
[08:09] <\sh> I shouldn't read email in the morning...
[08:12] <theseinfeld> anybody up for http://revu.tauware.de/details.py?package=libdc1394-22
[08:13] <theseinfeld> revu?
[08:15] <theseinfeld> anybody?
[08:15] <theseinfeld> :D
[08:15]  * theseinfeld feeling anxious today...
[08:17] <theseinfeld> dholbach? :)
[08:18] <dholbach> hiya theseinfeld
[08:18] <theseinfeld> lool LucidFox Hobbsee persia? It should be quite ready by now...
[08:18] <theseinfeld> howdy ho :)
[08:18] <theseinfeld> how is your monday morning dholbach :)
[08:19] <dholbach> theseinfeld: fine, but quite busy
[08:19] <persia> theseinfeld: Why ping us?
[08:19] <Hobbsee> theseinfeld: ?
[08:19] <theseinfeld> damn, mine is quite quiet :) dholbach. Well, I guess I can wait for a better morning :)
[08:20] <theseinfeld> You were reviewing the package earlier... Thought to give it a try since is there, dead since the feature freeze :)
[08:20] <LucidFox> hello theseinfeld
[08:20] <theseinfeld> hell o LucidFox
[08:20] <LucidFox> I'll review your package when I have some free time - which I currently don't have, sorry
[08:21] <theseinfeld> ok
[08:21]  * Hobbsee doesn't recall reviewing it, per se.
[08:22]  * theseinfeld might be wrong. He must recall the name from some other things...
[08:23] <persia> theseinfeld: I still don't see the point of parallel source packages, especially for a new cycle.
[08:23] <theseinfeld> it was well explained...
[08:24] <theseinfeld> basically, to put it short, until we get all the rdeps to change to new one, we have to use both
[08:24] <theseinfeld> there are big packages like mplayer and blender
[08:25] <theseinfeld> I don't think I can get those guys to change the dependency to the new API in one increment :)
[08:26]  * theseinfeld wonders as persia
[08:26] <theseinfeld> perisia, you in Tokyo?
[08:26]  * lool waves
[08:27] <persia_> theseinfeld: The point is that for intrepid, there's absolutely no value to releasing in the middle of a transition.  Just push the updated API with the new binary package name, and rebuild all the rdepends.
[08:27] <persia_> For Hardy, it made some sense, as the package was being discussed late in the cycle.
[08:28] <theseinfeld> it will not work
[08:28] <theseinfeld> the rdepends
[08:28] <theseinfeld> to rebuild
[08:28] <theseinfeld> it has a different API
[08:28] <theseinfeld> ABI
[08:28] <theseinfeld> everything is changed in the new package
[08:28] <theseinfeld> well, almost
[08:28] <theseinfeld> so...
[08:28] <persia> theseinfeld: Right, so we port it.
[08:29] <theseinfeld> I have no power to rebuild all the rdepends
[08:29] <theseinfeld> :D
[08:29] <theseinfeld> and the idea was to have them both working together
[08:29] <persia> theseinfeld: As much as you have power to include a package.
[08:29] <theseinfeld> the new one will work later also with the Juju stack in the kernel
[08:29] <persia> Right, so let's just use the new one
[08:29]  * persia wants more juju
[08:30] <theseinfeld> it is like saying lets just use KDE4
[08:30] <theseinfeld> you still can go one round in parallel
[08:30] <persia> theseinfeld: Right, and for intrepid, we are saying that.
[08:30] <theseinfeld> yes, persia, it was quite an effort to get it run in parallel
[08:31] <persia> I guess they could be in parallel.  I just don't see the point.
[08:31] <theseinfeld> LOL
[08:31] <theseinfeld> the point is that we cannot just take the old one yet
[08:31]  * Hobbsee beats persia with a stick.
[08:31] <persia> OK.  When you introduce a source package for a library with changed binary package names, the rdepends show on NBS.
[08:31] <Hobbsee> persia: now you're green.  stop it.  go back to light blue.
[08:32] <persia> Then, it just takes clearing NBS.
[08:32] <persia> Hobbsee: I can be any color I want!
[08:32] <Hobbsee> persia: no you can't!
[08:32]  * Hobbsee gets out the Long Pointy Stick of DOOM!!!!!!!!!!!!!!!™
[08:32] <persia> theseinfeld: As proof of concept, try the rdepends builds in a PPA.  I suspect that the failures ought be easy to clean.
[08:33] <persia> Further, I'd rather consider them bugs.  We still ship wx2.4, which is unfixable outside en_US, as a result of trying to have things in parallel.
[08:33] <Hobbsee> \o/.  persia is now light blue again.
[08:33]  * persia is *always* in awe of the Long Pointy Stick of DOOM!!!!!!!!!!!!!!!™
[08:34] <Hobbsee> hehe
[08:34]  * theseinfeld is confused...so which colour is the package then?
[08:35] <persia> theseinfeld: packages don't have colours, although they may be components of flavours
[08:35] <theseinfeld> LOL
[08:36] <theseinfeld> seriously, persia, I don't think there is going to be easy way with rdepends as the library is completely rewritten. I mean, there are different headers, different API, different functions, structures
[08:36] <theseinfeld> I can try, and if it fails :)
[08:36] <theseinfeld> then, what do I get?
[08:37] <theseinfeld> persia, what is the price? Can I be yellow :)
[08:37] <dave_> interested in MOTU!
[08:37] <persia> dave_: What do you like to do?
[08:37] <dave_> Beryl-Compiz
[08:37] <persia> theseinfeld: Sure.  It requires porting some apps.  Why not do it between now and September?
[08:38] <persia> dave_: Hmm.  I didn't think we shipped that anymore.  How about just compiz?
[08:38] <dave_> Have no Idea were to start! Kinda of a newbie.
[08:39] <dave_> I find Beryl easier to use. Have Issues getting compiz to work well!
[08:39] <persia> dave_: Well, MOTU is resposible for the Universe and Multiverse repositories.  With the help of about 300 other people (of which you could be one), we try to fix all the outstanding bugs, handle library transitions, ensure everything can install, and generally keep the software up-to-date.
[08:39] <theseinfeld> persia, did you check that debian has it like this?
[08:39] <theseinfeld> http://packages.debian.org/lenny/libdc1394-22
[08:40] <persia> https://wiki.ubuntu.com/MOTU/Contributing has some hints to get you started.  Basically, pick a package, fix it, and get it into the repos.  Then find another package.
[08:40] <dave_> Ok i'll give that a try thanks!
[08:40] <theseinfeld> maybe dave_ could do the blender with libdc1394-22
[08:40] <theseinfeld> :D
[08:40] <persia> theseinfeld: I didn't.  I still don't agree it should be a separate source package.  Further, if Debian has it like that, I don't see any point to something on REVU: hasn't it already been sync'd from Debian?
[08:41] <theseinfeld> nope
[08:41] <theseinfeld> it was not sync'ed as they got it a bit wrong, and since I couldn't get it through to them, I wanted to get through to ubuntu
[08:42]  * persia looks at https://launchpad.net/ubuntu/+source/libdc1394-22 , and doesn't trust that assertion.
[08:42] <persia> Mind you, I still think it's wrong, but that argument is apparently already lost...
[08:43] <theseinfeld> so, all my effort is gone the drains?
[08:43]  * theseinfeld is totally confussed now...
[08:45] <persia> theseinfeld: Submit a patch against the current libdc1394-22 in intrepid.
[08:47] <theseinfeld> where to? persia
[08:48] <persia> theseinfeld: If you want to implement a change, submit a patch against the current package in intrepid.
[08:48] <theseinfeld> to the libdc1394 project?
[08:48] <persia> To a bug in launchpad against the libdc1394-22 source
[08:48] <theseinfeld> all righty then
[08:49] <persia> For best chance of success, submit the patch in debdiff format against an update, and subscribe the universe sponsors.
[08:49] <devfil> anyone can review a package on REVU?
[08:49] <persia> devfil: Anyone can review a package, but not everyone can advocate.
[08:51] <devfil> Someone can review and advocate a package in REVU?
[08:52] <persia> devfil: If you're seeking review, best to include the URL to the package, and the number of current advocates.
[08:52] <devfil> persia: I wrote bad
[08:52] <persia> devfil: No worries :)
[08:52] <devfil> persia: is a new package
[08:52] <devfil> http://revu.ubuntuwire.com/details.py?package=galaxium
[09:08] <theseinfeld> persia, can you help me with the debdiff bug reporting?
[09:09] <persia> theseinfeld: What sort of help do you require?
[09:09] <theseinfeld> ok
[09:09] <theseinfeld> so, I am the maintainer in launchpad for the libdc1394 project which is related to the libdc1394
[09:09] <theseinfeld> now
[09:10] <theseinfeld> report bug, what do I fill there to get into the right place for the source?
[09:10] <theseinfeld> like, https://edge.launchpad.net/libdc1394/+filebug-advanced
[09:10] <persia> You want soemthing like https://launchpad.net/ubuntu/+source/libdc1394-22/+filebug-advanced.
[09:11] <persia> It's important that it gets filed against the Ubuntu project if you want to change something in Ubuntu, and important that you use the correct source name (as we have this split, especially designed to support lazy upstreams)
[09:12] <theseinfeld> it won't be lazy if I am in
[09:12] <theseinfeld> :D
[09:12] <theseinfeld> do I need any tags there?
[09:13] <persia> theseinfeld: Not specifically you, but all the various applications for whom porting will now not be RC for intrepid, as the old API is still available.
[09:15] <theseinfeld> persia, you mean rdepends?
[09:15] <persia> theseinfeld: precisely
[09:16] <theseinfeld> apt-cache rdepends libdc1394-13, persia, to be more prcise, for the old library and not for the new -22 library
[09:16] <persia> theseinfeld: It doesn't matter, as we have two source packages.  I'd like to see libdc1394-13 dropped, end encourage anything towards that goal.
[09:18] <theseinfeld> ok, so it is better to include every old rdepends to get people acknowledge the new upstream API
[09:19] <persia> theseinfeld: For what?  Now I'm afraid I've confused you.
[09:19] <theseinfeld> for the tags in the bug report
[09:19] <theseinfeld> :D
[09:19] <persia> You don't need any tags (I think)
[09:20] <theseinfeld> persia, do you agree that I should put all the rdepends pkgs ?
[09:20] <persia> theseinfeld: For what?
[09:20] <theseinfeld> OK
[09:20] <theseinfeld> no, I got it all wrong
[09:20] <theseinfeld> I asked if I need any tags and you answer something that left me think I should use the apps from rdepends
[09:20] <theseinfeld> ;D
[09:21]  * theseinfeld too fast...
[09:23] <theseinfeld> persia, check this out: https://bugs.edge.launchpad.net/ubuntu/+source/libdc1394-22/+bug/238492
[09:23] <huats> morning everyone
[09:26] <persia> theseinfeld: 1) Possible improvements: describe the specific improvements from using the changes in the bug description, 2) try to find something a little more "in-between" for a candidate (as that's a massive diff, and some to no clear benefit (e.g. CDBS)
[09:28] <theseinfeld> persia, you mean I should add those?
[09:29] <persia> theseinfeld: I was thinking more in terms of modification than addition, but it would increase the chances that such a change would be accepted.
[09:35] <theseinfeld> added some comments
[09:35] <theseinfeld> check again bug 238492
[09:36] <theseinfeld> persia, have to go lunch...
[09:36] <theseinfeld> persia see you after...
[09:57] <sistpoty|work> hi folks
[09:58] <\sh> moins sistpoty|work
[09:58] <sistpoty|work> hi \sh
[10:29] <devfil> Someone can review galaxium package on REVU? http://revu.ubuntuwire.com/details.py?package=galaxium
[10:43] <devfil> Someone can review galaxium package on REVU? http://revu.ubuntuwire.com/details.py?package=galaxium
[10:47] <persia> devfil: I'd encourage you not to ask about a given package more than once a day.
[10:47] <persia> Some people use this as a criteria for packages to skip.
[10:47] <devfil> persia: ok
[10:47] <persia> Also, be especially careful when there isn't much other traffic in the channel: some people mute parts/joins and so they see things as duplicate.
[10:47] <sebner> persia: I love and I hate you :P
[10:49] <persia> sebner: Then I'm doing things correctly :)  (cf. De Principatibus)
[10:50] <sebner> persia: hrhr. nexuiz \o/,  but less time for school ^^
[11:20] <theseinfeld> persia, I am back...
[12:26] <\sh> guys, is anyone familiar with ggz and especially ggz-config?
[13:16] <devfil> Someone can review galaxium package on REVU? http://revu.ubuntuwire.com/details.py?package=galaxium
[13:25] <x_dimitri> Hi guys, I'm an ubuntu enthusiast and would like to get involved with ubuntu as a contributing developer. ﻿I have read the docs on wiki.ubuntu.com and would like practical advice on skills to master (programming language(s), paradigms, e.t.c, - anything you deem useful/important) in order to get involved. What say ye?
[13:26] <persia> x_dimitri: It really depends on what you want to do.
[13:26] <persia> If you want to maintain packages, the best skills to develop are make and shell.
[13:26] <persia> Beyond that familiarity with any and all programming languages is beneficial.
[13:27] <persia> As is an understanding of how the various bits fit together into the whole.
[13:28] <persia> As a way to get started, I'd recommend looking through triaged bugs.  When you find one you understand, develop a solution.  After a few of these, the answers you get here, and the things you research towards a solution will probably help guide your next bug.
[13:29] <x_dimitri> persia: ok...
[13:29] <persia> x_dimitri: Good luck, and please ask if you have any questions.  We're generally glad to help, although more likely to provide pointers to things than actually explain them.
[13:30] <x_dimitri> persia: yup, I noticed that
[13:31] <x_dimitri> I guess go through the wiki again, but what I seem to understand so far, is that bug reporting is the only way in... i.e. as an Ubuntero..
[13:31] <x_dimitri> is that correct?
[13:32] <joaopinto> you can report bugs, fix bugs, update packages, etc
[13:35] <x_dimitri> joaopinto: it appears there's different levels of involvement: ubuntero, motu, e.t.c
[13:38] <persia> x_dimitri: There are different levels of involvement, but aside from "Ubuntero", all are granted as recognition of past work done.
[13:38] <persia> The first step is to declare yourself bound by the code of conduct, and beholden to the Community Council (Ubuntero).
[13:38] <persia> That done, you are welcome to do anything, and if you do it well, your work will become part of Ubuntu.
[13:38] <persia> With a body of well-done work, you may be granted additional roles or titles.
[13:42] <x_dimitri> persia: ok, thank you
[13:43] <x_dimitri> How is that declaration done? I didn't find any web-based means to do this (a form maybe). There was a document that was meant to be downloaded... Could you point me in the right direction?
[13:44] <persia> x_dimitri: Download and sign the Code of Conduct from your launchpad account.  Be sure that you take care to keep your GPG key once you've done so, as GPG is used for authentication in a number of places.
[13:48] <x_dimitri> persia: ok, thank you.
[13:48]  * ScottK suggests reading it before you sign it.
[13:48] <ScottK> ;-)
[13:49] <x_dimitri> ScottK: :-)
[13:55] <mouz> I fixed bug 198292. Would anyone like to sponsor it as an update? I posted the debdiff in launchpad.
[14:03] <persia> mouz: Generally it's best practice to attach debdiffs for both the current development release and an SRU candidate.  I'd recommend ubuntu0.1 for hardy and ubuntu1 for intrepid: beyond that the fix ought be essentially the same.
[14:03] <persia> Also, motu-sry has yet to indicate whether this patch is acceptable for upload.  Until that happens, it will not be uploaded to hardy-proposed.
[14:10] <leonel> ScottK: clamav 0.93.1   is out ...
[14:14] <mouz> persia: ok thanks. I will create those.
[14:18] <popey> if I do "apt-get build-dep firefox", and then later want to remove those build-deps, what apt incantation can i use?
[14:24] <gnomefreak> popey: deborphan?
[14:24] <gnomefreak> there is no apt removal for build-deps
[14:24] <\sh> grmpf..
[14:25] <\sh> has anyone problems with mono on intrepid?
[14:25] <\sh> looks like mono is somehow b0rked
[14:26] <popey> hmm, thats a shame
[14:30] <gnomefreak> popey: i have seen them show up in autoremove but i dont remember what triggers it
[14:31] <gnomefreak> \sh: mono is used system wide can you give an example?
[14:32] <gnomefreak> popey: pbuilder IIRC removes them once package is done but i dont use pbuilder i use chroots
[14:32] <popey> problem is if you used neither, you have lots of build deps kicking around
[14:32] <popey> and no way to identify / remove them easily
[14:33] <gnomefreak> maybe removing *.dev
[14:33] <\sh> gnomefreak: I'm trying to build muine
[14:33] <\sh> gnomefreak: and it failes because of not installable b-ds
[14:33] <gnomefreak> but that is a long shot, and you should always use one or the other when building packages since there is no easy way to remove the clutter
[14:34]  * \sh uses sbuild , as it's used by our buildds :)
[14:34] <gnomefreak> \sh: i havent tried to build anything with mono since most if not all mozilla apps dont use it
[14:35]  * nhandler_AFK is back (gone 10:32:19)
[14:37] <persia> popey: A recipe that works for me is to always use aptitude to install anything I want, and make everything else as automatically installed.  I only use apt-get for build-dep, so everything apt-get installed is automatically marked for removal next time I run aptitude.
[14:37] <popey> hmm
[14:37] <popey> thats an idea
[14:51] <ScottK> leonel: I saw.  Am about to look to see if there are any security fixes.
[14:53] <Hobbsee> nhandler: please turn off that away message
[14:54] <nhandler> Hobbsee, I think I disabled it now. It was an xchat setting
[14:54] <Hobbsee> nhandler: yeah, i realised.
[14:54] <Hobbsee> nhandler: thanks
[14:55] <nhandler> Hobbsee, np
[15:15] <ScottK> leonel: One security fix.  Do you have time to work on it?
[15:18] <leonel> ScottK: any cve ??
[15:18] <ScottK> leonel: Not that I can find.
[15:19] <leonel> ok  I'll check that
[15:19] <ScottK> Changelog says fix possible memory access and they committed it at the same time as the release, so it's a security fix.
[15:20] <leonel> libclamav/petite.c: fix possible invalid memory access (bb#1000)
[15:20] <leonel> 			Reported by Damian Put  <-- is this ??
[15:21] <ScottK> Yes.
[15:21] <ScottK> The bug is also marked private in their bugzilla.
[15:21] <leonel> ScottK: ok  I'll check it and see any diff with 0.93
[15:21] <ScottK> leonel: I've looked at the source already
[15:22] <ScottK> leonel: If you diff libclamav/petite.c between 0.93 and 0.93.1 you'll get a diff that looks like it will apply cleanly to our 0.92.1 package.
[15:22] <leonel> perfect !
[15:23] <leonel> ScottK:  I'll start workin on in in 2 hours   it's ok with you ??
[15:24] <ScottK> leonel: Yes.
[15:31] <ScottK> leonel: I'll file a bug for you to work on.
[15:31] <leonel> ScottK: ok
[15:38] <ScottK> leonel: Bug #238575 - The diff is in the bug, it just needs to be packages for each release.
[15:38] <leonel> ScottK:  Thanks ..
[15:38] <leonel> I start in 2hours
[15:39] <ScottK> Great.  I'm assigning it to you ....
[16:10] <lool> slangasek: w00t
[16:10] <lool> slangasek: Any idea why virtualbox-ose-modules is built against -17 in intrepid instead of -16?
[16:11] <lool> I'm adding lpia support to it, but it wont build for me as there's no -17 kernel package in intrepid
[16:12] <lool> slangasek: Also, I'd be tempted to do the same in hardy-proposed if you don't mind :)
[16:20] <lukehasnoname> any idea when soren will be on? PS
[16:20] <lukehasnoname> er, dang, wrong channel.
[16:24] <norsetto> TartePoireauxCra? TartePoireauxGras!?
[16:25] <norsetto> TartePoireauxCravattes!
[16:31]  * ScottK doesn't know what norsetto is one, but he might like to have some of it.
[16:32] <norsetto> ScottK: neah, I don't think you will like my version, huats one might be better
[16:32]  * Hobbsee force feeds ScottK automatix.
[16:32] <Hobbsee> (3)
[16:34] <huats> norsetto: :)
[16:34] <huats> sorry guys for the change of nick :)
[16:35] <huats> and it was TartePoireauxCrabe
[16:35] <huats> :)
[16:38] <norsetto> huats!!!
[16:38] <huats> norsetto !!!
[16:40]  * ScottK gets ill and spews
[17:24] <bddebian> Heya gang
[17:27] <slangasek> lool: er, no, I have no idea of anything wrt virtualbox-ose-modules in intrepid
[17:29] <lool> slangasek: Ok, ogra hinted me at you
[17:29] <lool> slangasek: Nevermind then; thanks
[17:30] <ogra> lool, i thought i saw a conversation about vbox last week, apparently wrongly, sorry
[17:30] <slangasek> sure, I had a conversation with blueyed about vbox in hardy-proposed...
[17:31] <ogra> yeah, thats what i meant
[17:31] <ogra> lool was asking why he didnt do a -19 instead
[17:32] <lool> I'll go and fix vbox in intrepid then
[17:32]  * sistpoty|work heads home... cya
[17:32] <slangasek> well, neither -17 nor -19 is present in intrepid currently
[17:33] <ogra> indeed
[17:33] <slangasek> so I don't know what the upload in intrepid is about at all
[17:33] <ogra> enabling lpia
[17:33] <ogra> we cant use vbox for lpia at 800x480 bwithout the vbox video driver which is in the guest modules
[17:33] <laga> what's so special about lpia? is it different from i386?
[17:34] <ogra> yes
[17:34] <lool> ogra: blueyed uploaded a new version to intrepid to move from -16 to -17
[17:34] <lool> But -17 never made it to intrepid AFAIK
[17:34] <ogra> lool, right and currently we have -19
[17:34] <lool> I noticed while adding lpia that it simply wouldn't build ATM
[17:34] <lool> ogra: That's hardy; intrepid still has -16 I think
[17:34] <ogra> you need to add lpia to the configure script
[17:34] <ogra> its not an accepted arch without that hack
[17:36] <ogra> which is all my patch does, changing control everywhere from s/i386/i386 lpia/ and adding lpia to the x86 list of arches
[17:36] <lool> ogra: I'm interested in that last part
[17:36] <lool> I also updated control and rules
[17:37] <lool> I'm looking at configure ATM, I also had a look at the modules/virtualbox-ose Makefile, but I didn't get where the arches came from
[17:37] <lool> (yet :)
[17:40] <ogra> lool, line 254
[17:40] <ogra> must be: i[3456789]86|x86|i86pc|lpia)
[17:40] <ogra> trivial :)
[17:40] <ogra> the first part of that regex is pretty optimistic *grin*
[17:41] <lool> ogra: Well I checked this part and connected to my lpia Q1 and uname -m would return i686
[17:41] <ogra> dpkg hands over lpia i think
[17:41] <ogra> during build
[17:41] <lool> ogra: BUILD_CPU=`uname -m` 2 lines above?
[17:42] <ogra> not sure which source you are using there
[17:42] <ogra> mine as
[17:42] <ogra> has
[17:42] <ogra>  BUILD_CPU=`dpkg --print-architecture`
[17:42] <lool> ogra: aha
[17:42] <leonel> I had my pbuilder on a gutsy install   that gutsy got upgraded to  hardy ..  the  pbuilder install ... was  moved to hardy  or is still for  gutsy ???
[17:42] <ogra> (not added by me)
[17:42] <lool> ogra: I'm looking at 1.5.6-dfsg-6ubuntu1
[17:43] <ogra> hmm
[17:43] <ogra> same here
[17:43] <ogra> from april 9
[17:43] <lool> ogra: Oh, yours is probably patched
[17:43] <lool> ogra: Got it now
[17:44] <lool> lala
[17:45] <lool> ogra: IMO it should be using dpkg-architecture -qDEB_HOST_GNU_CPU instead of dpkg --architecture, what do you think?
[17:45] <ogra> sounds good
[17:49] <bluefoxicy> what the hell ass balls
[17:49] <bluefoxicy> if X gets killed you cannot log in again until you reboot
[17:49] <laga> #define killed
[17:50] <bluefoxicy> rm -rf /tmp doesn't fix it, neither does killall $(ps -e u | grep id -un | awk '{print $2}')
[17:50] <bluefoxicy> laga:  ctrl+alt+backspace, which happens fairly often by accident through confusion
[17:50] <bluefoxicy> i.e. switching virtual desktops, deciding to backspace over a character
[17:51] <bluefoxicy> I tried killing all the user's processes and removing all temporary files owned by the user to no end
[17:51] <laga> doesnt happen here
[17:52] <bluefoxicy> laga:  ctrl+alt+bs doesn't kill X there?
[17:53] <laga> it does, but i can still login afterwards
[17:53] <bluefoxicy> doesn't let me in, I get a blank desktop with a white box in the top left with nothing in it
[17:55] <bluefoxicy> also virtualbox seems to be unsupported <_<
[17:55] <bluefoxicy> its modules are in main for an old kernel, universe for a newer kernel, and not present for current o_o
[17:55] <bluefoxicy> oh, I'm on proposed, ok
[17:57] <bluefoxicy> the updated kernel (2.6.24-18, hardy-updates) still has a matching universe virtualbox driver though, instead of main
[17:57] <bluefoxicy> though, the 2.6.24-17 driver says it's in main but maintained by Ubuntu MOTU
[18:20] <mouz> persia: about bug 198292. The version queued for the development release is patched in Debian for the same bug. So my reasoning is: it need not be patched for Ubuntu (for this bug). Am I right? Does that mean posting a debdiff for 1ubuntu0.1 suffices, or is there still a need for 2ubuntu1 then?
[18:28] <jdstrand> kees: so I was looking at getting mutt to help me with bug triage, and came acroos 'pipe-message'-- have you used it much with macros?
[18:28] <kees> jdstrand: to some extent, yeah.  I think the USN builder, for example, uses it.
[18:29] <jdstrand> kees: actually it does not
[18:29] <kees> oh?
[18:29] <jdstrand> kees: I was using it as an example, and then came across something that would be better
[18:29] <kees> ah, you're right, i use "editor" to do the evilness
[18:29] <jdstrand> kees: with usn builder, you use a trick with the set editor
[18:29] <jdstrand> kees: check this out:
[18:30] <jdstrand> macro index \cB "<pipe-message>~/ubuntu/security/scripts/lp-status<enter>"
[18:30] <kees> cool, yeah
[18:30] <jdstrand> kees: that macro pipes the message (or tagged messages) to that command
[18:30] <kees> I have some really old stuff:
[18:30] <kees> macro index \cu "<enter-command>unset wait_key\n<pipe-message>urlview\n<enter-command>set wait_key\n"
[18:30] <jdstrand> kees: yeah
[18:30] <kees> I think bdmurray has a ton of these kinds of things for doing his triage-via-email stuff
[18:32] <jdstrand> kees: what is nice is that I have a script called 'bug-status.py', so I then wrote lp-status to be http://paste.ubuntu.com/18838/
[18:33] <jdstrand> kees: this then outputs various stuff in mutt that I can use to start processing things
[18:33] <jdstrand> kees: anyhoo-- I knew you liked 'stupid mutt tricks' so thought I'd pass it along
[18:34] <kees> nice, yeah, thanks :)
[18:41] <vbabiy-laptop> Hey guys are we going to to have the RC2 of firefox on Hardy or you guys waiting for the final?
[19:15] <ScottK> vbabiy-laptop: #ubuntu-mozillateam would be a more likely place to get an answer to that question.
[19:21] <vbabiy-laptop> thanks ScottK
[19:50] <jdstrand> kees: do you have a script for approving 'nominate for release' bugs?
[19:50]  * jdstrand likes to glom onto kees' scripts
[19:53] <nhandler> Is it really necessary to add the "patch" tag to a bug that you patch? Or is it sufficient to just check the box that says, "This attachment is a patch"?
[20:14] <jpds> nhandler: I think the patch tag is just to make searching easier.
[20:16] <nhandler> jpds, Does that mean that it isn't a requirement. If that is the case, someone should update https://wiki.ubuntu.com/MOTU/Contributing.
[20:18] <jpds> nhandler: I think you may wish to tag it, yeah
[20:18] <nhandler> jpds, Ok, thanks.
[20:37] <leleobhz> what parameters i need to use in lintian to know a package is compilant?
[20:38] <leleobhz> and how can i open a itp bug?
[20:40] <ScottK> leleobhz: File a regular bug in Launchpad against Ubuntu and then tag it 'needs-packaging'.
[20:41] <geser> leleobhz: simply run lintian once on the source package and once on the generated debs, or simplified on the _<arch>.changes file from the build to check both
[20:42] <leleobhz> geser: some special parameters
[20:42] <leleobhz> ScottK: and can i send my package to repositories?
[20:42] <leleobhz> ScottK: or must to use REVO?
[20:42] <leleobhz> geser: only lintian .changes?
[20:42] <leleobhz> no parameters?
[20:43] <ScottK> !REVU | leleobhz
[20:43] <ScottK> That's where you send it.
[20:43] <geser> leleobhz: I use normally no paramters, sometimes -i to get a more verbose output on warnings and errors
[20:43] <leleobhz> E: uniconvertor_1.1.2-1_i386.changes: bad-distribution-in-changes-file hardy
[20:44] <leleobhz> someone know how can i solve this?
[20:45] <leleobhz> ScottK: ill file the but
[20:45] <leleobhz> bug
[20:45] <geser> leleobhz: for Ubuntu the version should end in -0ubuntu1 if the package (or that version) doesn't exist in Debian
[20:45] <leleobhz> ScottK: need i redirect the bug for someone?
[20:46] <geser> but I don't know if lintian knows about the Ubuntu versioning scheme and will stop complaining after you fixed the version
[20:47] <ScottK> leleobhz: No.
[20:47] <ScottK> geser: It does.
[20:47] <RainCT> geser: I think lintian recognizes the -Xubuntu1 as Ubuntu distribution, but  I might be wrong though
[20:47] <leleobhz> can i send a package to revu to be fixed?
[20:47] <leleobhz> well
[20:47] <leleobhz> dont recognized
[20:47] <RainCT> leleobhz: yes, just re-upload
[20:49] <leleobhz> RainCT: well, i think now i must to send the package because i cant think what more is wrong
[20:49] <leleobhz> can i fix it latter and send to review?
[20:49] <leleobhz> (and what i need to do to put it on oficial repositories?)
[20:59] <neurobuntu> has anybody here used svn-buildpackage?
[21:01] <kees> jdstrand: don't have nominate script, no.  that might be kinda handy.
[21:03] <leleobhz> well, my first almost-correct package uploaded!!!!
[21:03] <neurobuntu> does anybody know of any nightly build utilities?
[21:07] <leleobhz> ive uploaded a package that exists into revu, but in a old version
[21:07] <leleobhz> what can i do
[21:09] <emgent> heya
[21:19] <mouz> If I fixed a bug for Hardy, but upstream fixes the same for Intrepid, no ubuntu patch is needed for Intrepid anymore, right?
[21:20] <devfil> mouz: right
[21:28] <devfil> Someone can review galaxium package on REVU? http://revu.ubuntuwire.com/details.py?package=galaxium
[21:38] <geser> devfil: is it a mono app?
[21:38] <devfil> geser: yes
[21:38] <geser> devfil: are you aware of http://pkg-mono.alioth.debian.org/cli-policy/
[21:38] <geser> ?
[21:39] <devfil> geser: ehm no, what I should do with cli policy?
[21:40] <devfil> geser: put it in copyright?
[21:40] <LaserJock> siretart: ping
[21:41] <geser> devfil: not in copyright, but read and apply it to debian/rules
[21:42] <geser> devfil: I'm not familiar with that sub-policy but I know that there is dh_clideps to automagically discover the dependencies on -cil packages
[21:42] <geser> devfil: it might help you to package a mono application correctly
[21:43] <leleobhz> while compiling a package with cdbs and python, should i use 2.4 or 2.5 version?
[21:43] <devfil> geser: thanks for the link
[21:43] <geser> leleobhz: what kind of python package? python app? python lib? python module?
[21:44] <leleobhz> app
[21:44] <leleobhz> geser: because pdebuilder try to compile the package with python2.4 but even with python-support and python2.4-dev  gcc dies saying have no Python.h
[21:44] <geser> leleobhz: the default python version (which is currently 2.5)
[21:45] <leleobhz> hmm
[21:45] <geser> leleobhz: gcc? so it's not pure python?
[21:45] <leleobhz> geser: i think it isnt
[21:46] <leleobhz> geser: if i use dpkg-buildpackage everything goes ok
[21:46] <leleobhz> but using pdebuilder i got this problem
[21:46] <geser> leleobhz: then you're probably missing a build-dependency
[21:46] <geser> how does your build-depends look like?
[21:46] <leleobhz> well, its Python.h]
[21:46] <leleobhz> Build-Depends: cdbs, debhelper (>= 5), python2.4-dev, python-support, perl
[21:47] <leleobhz> (perl for pod2man)
[21:48] <geser> leleobhz: if possible try to build it once for python2.4 and once for python2.5 (i.e. all supported python-versions)
[21:48] <geser> but if you have to choose one: python2.5 as this is the default
[21:48] <leleobhz> geser: can i use both?
[21:49] <geser> in the first case (2.4 and 2.5) build depend on python-all-dev, in the second (2.5 only) on python2.5-dev
[21:49] <geser> leleobhz: yes, python modules use it to build for python2.4 and python2.5
[21:49] <leleobhz> geser: another. im packaging a package yet archived on revu..
[21:49] <leleobhz> geser: but ive found this after upload
[21:50] <chaos386> hi there, is this the right place to report a package dependency issue?
[21:50] <leleobhz> (but im using cdbs and the original normal build)
[21:50] <leleobhz> geser: so, what i need to do?
[21:50] <geser> leleobhz: find someone who is more familiar with cdbs than me :)
[21:51] <leleobhz> geser: my doubt is about the duplicity
[21:51] <geser> chaos386: bugs should be filed in Launchpad
[21:52] <chaos386> even if the fix is already known?
[21:52] <geser> leleobhz: if it only works for one version, then it's IMHO ok to build for only one version (e.g. it doesn't use different dirs for the compiled parts)
[21:53] <norsetto> devfil: package doesn't build for intrepid (probably not a fault of the package), tarball from get-orig-source and your tarball are different
[21:53] <geser> chaos386: mention the fix also in the bug
[21:53] <chaos386> geser: ok, thanks
[21:53] <devfil> norsetto: I used get-orig-source to do the tarball
[21:54] <norsetto> devfil: well, try again because they do not match
[21:54] <emgent> hi norsetto :)
[21:54] <norsetto> emgent: 0/
[21:55] <leleobhz> geser: well, my package ill be moderated right?
[21:55] <leleobhz> i need do more than send the source?
[21:56] <norsetto> devfil: most probably is just the compression level
[21:57] <devfil> norsetto: there are other problems in the package?
[21:57] <norsetto> devfil: probably, I still haven't got past the build stage though ;-)
[22:00] <norsetto> devfil: which tar did you use?
[22:00] <devfil> norsetto: czf
[22:00] <norsetto> devfil: I mean version
[22:01] <devfil> norsetto: version of tar or the svn revision?
[22:01] <norsetto> devfil: tar version
[22:02] <devfil> norsetto: 1.19-3
[22:03] <norsetto> devfil: ok, this could explain it then, I used a different version
[22:05] <norsetto> devfil: what are the dll included with the tarball?
[22:06] <devfil> norsetto: agsXMPP, Mono.Nat and ProxySocket
[22:07] <norsetto> devfil: yes, what are they?
[22:07] <devfil> norsetto: I am not understanding
[22:08] <geser> leleobhz: you mean upload to REVU?
[22:08] <norsetto> devfil: are they needed for the package to work? where are the sources?
[22:08] <leleobhz> geser: yeap
[22:08] <geser> leleobhz: there is no moderation
[22:08] <devfil> norsetto: they are in dlls dir and yes, they are needed to work
[22:09] <ScottK> leonel: Debdiffs look good so far.  Why did you number the Dapper on dapper3 instead of dapper2ubuntu1 in line with what you did for the others?
[22:09] <leleobhz> geser: but i need do more than this?
[22:09] <geser> have you read https://wiki.ubuntu.com/MOTU/Packages/REVU ?
[22:09] <norsetto> devfil: and the sources? If you give no sources you can't use GPL as you did
[22:09] <ajmitch> hello
[22:11] <geser> good night *
[22:11] <devfil> norsetto: sources aren't in the package but there are some licenses about dlls
[22:11] <norsetto> devdil: also for this: docs/Extension paths.pdf
[22:12] <norsetto> devfil: then the package could go to multiverse but we need to check the licenses and they have to be added to copyright
[22:12] <devfil> norsetto: ok, I'm going to add the licenze in copyright file
[22:12] <leleobhz> geser: yep... its a little of unsure
[22:13] <norsetto> devfil: and this: build/libmimic.so
[22:13] <devfil> norsetto: -.-' I'm going to kill me :P
[22:13] <geser> when your key is in the keyring on REVU then your upload should get automatically accepted and appear a few minutes later on the overview page
[22:13] <norsetto> devfil: also please check what is all the stuff under build, I don't think you install any of these themes tarballs?
[22:14] <norsetto> devfil: for so little? :-)
[22:14] <devfil> norsetto: for you is a litte think, for me is a big problem
[22:14] <devfil> norsetto: themes are installed
[22:15] <leleobhz> geser: ok
[22:15] <norsetto> devfil: ok, perhaps it is worth making a separate package if they are relatively big
[22:16] <devfil> norsetto: they aren't big
[22:16] <devfil> norsetto: the package will be bigger only 1.9MB
[22:17] <leleobhz> E: uniconvertor_1.1.2-0ubuntu2_source.changes: checksum-mismatch-in-changes-file md5 uniconvertor_1.1.2-0ubuntu2.dsc
[22:17] <leleobhz> how can i fix it?
[22:17] <norsetto> devfil: well, they add to 1 MB, this is big in my book
[22:18] <devfil> norsetto: but I will need to change sources, themes are installed by sources
[22:19] <norsetto> devfil: no, just use proper install files and add another -themes package in control
[22:20] <norsetto> devfil: what is in these themes, is it just one theme or several?
[22:20] <devfil> norsetto: is one theme
[22:20] <devfil> extra
[22:20] <norsetto> devfil: ok, then it makes sense to package it separately
[22:21] <devfil> norsetto: "just use proper install files"... how?
[22:22] <norsetto> devfil: check man dh_install (and you need to add dh_install to the install target)
[22:23] <devfil> norsetto: ahhh ok, dh_install to don't install in the main package and to install in themes package, sure
[22:23] <norsetto> devfil: I mean, binary-arch target
[22:24] <norsetto> devfil: since you do that also move the icon installation from rules (using cp) to install (using install file)
[22:25] <norsetto> devfil: and pls. add a desktop file
[22:25] <devfil> norsetto: already exists...
[22:25] <norsetto> devfil: from upstream?
[22:26] <devfil> norsetto: yes, desktop file and .png icon
[22:26]  * norsetto checks it
[22:26] <devfil> norsetto: it looks like good
[22:28] <norsetto> devfil: Application;Network;InstantMessaging misses a ; at the end
[22:28] <devfil> norsetto: I will add a patch
[22:29] <norsetto> devfil: I think also application is not a good category
[22:30] <norsetto> devfil: and please re-edit the Comment so that its gnome HID compliant
[22:30] <devfil> norsetto: GNOME;Network; ?
[22:30] <leleobhz> E: uniconvertor_1.1.2-0ubuntu3_i386.changes: checksum-mismatch-in-changes-file md5 uniconvertor_1.1.2-0ubuntu3.dsc
[22:30] <leleobhz> someone know why its doing this?
[22:30] <devfil> norsetto: the comment?
[22:33] <devfil> I'm going to sleep
[22:33] <devfil> bye
[22:41] <leonel> ScottK: the  dch -i did the  numbering   and all I've seen finish with  ubuntuX ...
[22:41] <leonel> ScottK: working on Hardy
[22:42] <ScottK> leonel: Great.
[22:42] <ScottK> leonel: I think 2ubuntu1 is more correct for dapper
[22:43] <leonel> should I redo the debdiff ?
[22:44] <norsetto> night all
[22:59] <cody-somerville> ScottK, Do you want to peer-review an SRU I just reviewed?
[23:14] <laga> jono: re severed fifth: it might be a good thing if you put a nice and short explanation of what your project actually _is_ somewhere accessible. your post to the planet doesn't explain it, the main page of the severed fifth website doesn't explain it either and i don't know if everyone really wants to read that very, very long news entry on the web site.
[23:14] <laga> jono: disclaimer: i've got a headache and i'm cranky, so i might have missed something :)
[23:27] <Nightrose> +1's that