[12:15] <_Enchained> uploading...
[12:20] <_Enchained> bddebian: http://revu.tauware.de/details.py?upid=4275 :)
[12:20] <bddebian> _Enchained: OK
[01:10] <enyc> * I need to solicit more testing of qpsmtpd fix in dapper https://launchpad.net/bugs/78005 ** ;-)
[01:10] <Ubugtu> Malone bug 78005 in qpsmtpd "[SRU]  request: dapper:qpsmtpd fix for bug #72602" [Undecided,Fix committed]  
[01:11] <ajmitch> you'll need to find people that use it then
[01:11] <enyc> * I need to solicit more testing of qpsmtpd fix in edgy https://launchpad.net/bugs/77485 ** ;-)
[01:11] <Ubugtu> Malone bug 77485 in qpsmtpd "[SRU]  request: edgy:qpsmtpd fix for bug #72602" [Undecided,Fix committed]  
[01:11] <enyc> ajmitch: hehehehe
[01:12] <enyc> ajmitch: theres me... and theres Sheer... bah
[01:12] <enyc> ajmitch: o well cant win everything ;-)
[01:27] <keescook> cool.  -security updates will be showing up in the -changes lists soon.  :)
[01:28] <Nafallo> scary :-P
[01:28] <Nafallo> is that a feature or a bug? :-)
[01:28] <ajmitch> more like expected behaviour
[01:28] <keescook> well, it was intended as a feature, but evolved into a bug, I guess.
[01:29] <Nafallo> I would expect them to be hidden as long as possible. or atleast until the USN :-)
[01:31] <sistpoty> seems like I don't need to write the motu-swat report then :)
[01:31] <Nafallo> sistpoty: :-P
[01:35] <Nafallo> Fujitsu: ! :-D
[01:35] <Fujitsu> Hi Nafallo.
[01:39] <Nafallo> Fujitsu: :-)
[02:26] <ajmitch> hello Hobbsee 
[02:27] <Hobbsee> hey ajmitch 
[02:28] <rexbron> any one up for a review, check out upid 4276
[02:34] <sistpoty> rexbron: give me 10 minutes, then I'll take a look
[02:35] <bddebian> rexbron: I'm working on stuff, which package?
[02:37] <rexbron> bddebian: soma
[02:37] <Nafallo> sistpoty: http://revu.tauware.de/details.py?upid=4271
[02:37] <Nafallo> bddebian: http://revu.tauware.de/details.py?upid=4271
[02:37] <Nafallo> :-)
[02:42] <bddebian> OK, let me get the kids to bed
[02:42] <bddebian> Wait a minute, soma, wtf?? :-)
[02:42] <rexbron> bddebian: ?!?
[02:44] <bddebian> rexbron: I thought we were done with that one? :-)
[02:44] <Nafallo> bddebian: if you take pictures of them I'll wait :-)
[02:44] <rexbron> bddebian: Murrine
[02:44] <rexbron> bddebian: soma is still in the works
[03:07] <bddebian> Nafallo: pictures?
[03:08] <Nafallo> bddebian: or photos. whichever :-P
[03:10] <bddebian> Uhm, they are 7,5, and 3, what type of photos were you thinking of?
[03:11] <Nafallo> just wanted to see them :-)
[03:11] <bddebian> Ah, OK :-)
[03:20] <sistpoty> rexbron: is soma only i386 specific?
[03:20] <rexbron> I have not tested it with anything else
[03:21] <rexbron> sistpoty: I do not know, I would not think so (even though I have it as i386), but am unable to test it
[03:21] <rexbron> sistpoty: I will contact upstream for more info
[03:22] <sistpoty> I'll do a test-compile on amd64... (don't have a i386 pbuilder at hand, and am too lazy to build in a chroot right now *g*)
[03:22] <sistpoty> rexbron: there are two Makefile's in the diff... seems like you should clean these
[03:23] <rexbron> sistpoty: I am unclear why the make files are different, might have built it and forgot to clean. Sugested course of action?
[03:23] <rexbron> other than make clean?
[03:24] <sistpoty> rexbron: maybe you could look if make clean actually cleans these... 
[03:24] <Nafallo> thanks bddebian *hug*
[03:26] <Nafallo> now I just need sistpotys +1 aswell ;-)
[03:26] <sistpoty> Nafallo: you're next in the queue after soma ;)
[03:26] <Nafallo> sistpoty: I know :-)
[03:26] <sistpoty> rexbron: at least it *builds* fine on amd64
[03:26] <rexbron> sistpoty: ffmpeg is not being used, it is building against the ubuntu binaries. The other makefile, I am not sure, I will diff the two and see if there are any real changes
[03:26] <rexbron> sistpoty: 
[03:27] <rexbron> sistpoty: then do the packages get the all architechture
[03:27] <rexbron> or just i386, amd64 and ppc
[03:27] <sistpoty> rexbron: make 'em any please
[03:27] <rexbron> sure
[03:27] <sistpoty> (all means not arch-specific)
[03:30] <rexbron> sistpoty: I will upload a new version
[03:30] <rexbron> bddebian: I will need you to look at soma again soon
[03:30] <sistpoty> rexbron: please wait a minute, there are some more issues
[03:30] <rexbron> oh ok
[03:30] <bddebian> Gah, why do I bother reviewing? :-(
[03:30] <sistpoty> rexbron: if you don't need the shipped ffmpeg, please remove it from the orig-tarball and add a dfsg1 to the upstream version. Otherwise soma would quite certainly get demoted to universe
[03:31] <sistpoty> demoted to multiverse even
[03:31] <bddebian> Nafallo: Don't get too excited, sistpoty will find all the shit I missed :-)
[03:31] <sistpoty> (and I guess archive admins don't like to review ffmpeg due to patent issues *g*)
[03:31] <rexbron> sistpoty: then the ffmpeg in debian copyright would be removed aswell
[03:31] <sistpoty> rexbron: sure
[03:32] <rexbron> anything else?
[03:32] <rexbron> sistpoty: ^
[03:32] <sistpoty> rexbron: give me a minute please... I'm still looking ;)
[03:32] <Nafallo> bddebian: hopefully :-)
[03:34] <rexbron> sistpoty: so the version would be soma_0.41-dfsg1ubuntu1? Even though it is not in debian?
[03:34] <rexbron> sistpoty: or _0.410+dfsg1ubuntu1
[03:34] <rexbron> sistpoty: or _0.41-0+dfsg1ubuntu1 rather
[03:35] <sistpoty> rexbron: s.th. like 0.41.dfsg1-1ubuntu1
[03:35] <rexbron> ok
[03:35] <sistpoty> rexbron: as the dfsg-part should be part of the upstream version (and thus before the minus)
[03:35] <rexbron> sistpoty: . or + between upstream and dfsg?
[03:36] <sistpoty> rexbron: whatever you prefer ;)
[03:36] <rexbron> ok
[03:36] <sistpoty> rexbron: however not 0.41 ;)
[03:36] <rexbron> opps, thats Murrine
[03:36] <sistpoty> *g*
[03:36] <rexbron> differnt source package
[03:38] <sistpoty> rexbron: what are soma-check and soma-config for? for server-configuration?
[03:41] <rexbron> sistpoty: I think so, that is the decription in control is what is given on the soma site
[03:41] <rexbron> actually, that is just for the first couple 
[03:41] <rexbron> sistpoty: they check the config files and allow other soma programs to configure the server, I believe
[03:42] <sistpoty> rexbron: please include these in the somad package, as these are really very small packages (and otherwise would bloat the packages file)
[03:43] <rexbron> I can merge them into the somad.install file
[03:43] <sistpoty> rexbron: and maybe the client might suggest the server? (not sure if that makes sense though, so I'll leave that to you)
[03:44] <rexbron> the client is the command line interface to the server, so it maybe should depend?
[03:44] <rexbron> or recommends, as they are installed by default
[03:45] <sistpoty> rexbron: so I'd pretty much need the client to use the server?
[03:45] <rexbron> I think so
[03:46] <rexbron> its the interface to the server daemon
[03:46] <rexbron> sistpoty: ^
[03:46] <sistpoty> rexbron: then I'd say to simply include this one in the somad package... if it doesn't make much sense to have the server without the "client"
[03:47] <sistpoty> (actually I've guessed that client means s.th. different here...)
[03:48] <rexbron> ok I think that would work, should the binary package be renamed then to just soma, or maybe soma-server (as there is a soma-player)
[03:48] <sistpoty> bddebian: why?
[03:49] <sistpoty> rexbron: not quite sure... moment please
[03:49] <bddebian> Because I suck
[03:49] <sistpoty> bddebian: no, you don't :P
[03:49] <bddebian> sistpoty: Sure I do, ask ajmitch :-)
[03:50] <sistpoty> hrhr
[03:50] <sistpoty> rexbron: actually choose what name you prefer... both make sense to me
[03:50] <rexbron> I am going with server for consistency
[03:50] <sistpoty> ok
[03:51] <rexbron> sistpoty: anything more that you can see?
[03:51] <sistpoty> rexbron: nope... others than that the package is really lovely
[03:51] <rexbron> yay
[03:52] <aSt3raL_> hello
[03:52] <rexbron> sistpoty: Would you be able to examine it again in about 1/2h?
[03:52] <aSt3raL_> what do you guys need help with?
[03:52] <sistpoty> rexbron: not quite sure if I'm still up then... in case I'm asleep already I'll promise to look at it tomorrow though
[03:53] <aSt3raL_> ive been using ubuntu for a couple years and am interested in helping
[03:54] <sistpoty> aSt3raL_: we need help with everything... from triaging bugs, to making new packages to getting our documentation in a better shape
[03:55] <sistpoty> aSt3raL_: have you read https://wiki.ubuntu.com/ContributeToUbuntu yet?
[03:55] <aSt3raL_> i have not
[03:56] <sistpoty> aSt3raL_: please do... it should give you a first overview ;)
[03:57] <sistpoty> Nafallo: please don't exceed 80 chars in debian/copyright... this is really hard to read ;)
[03:59] <sistpoty> Nafallo: the descriptions/extended descriptions could be a little bit more verbose... what will I get from the different wave-look packages? usplash-images? wallpapers? sounds? anything else?
[04:00] <Nafallo> sistpoty: doesn't the short description say? :-)
[04:01] <sistpoty> Nafallo: well, it could be more verbose ;)
[04:01] <Nafallo> and the packagenames are straightforward aswell :-)
[04:01] <Nafallo> IMO :-)
[04:03] <sistpoty> Nafallo: I guess the average user wouldn't figure that splashes are bootup screen splashes
[04:03] <sistpoty> Nafallo: but that's not a showstopper for me ;)
[04:04] <Nafallo> hehe, the package is actually a fork from the other artwork packages, so I'll just blame dholbach anyway :-)
[04:06] <Nafallo> sistpoty: is it +1 without extra review with the reformat I'm making? or do you see something else? :-)
[04:06] <sistpoty> Nafallo: actually I'd like to see it as either a native package or bug upstream to remove the debian-dir ;)
[04:06] <sistpoty> :P
[04:07] <Nafallo> dooh
[04:07] <Nafallo> I know I forgot something ;-)
[04:07] <sistpoty> Nafallo: gives a PITA if someone wants actually remove a file from the debian-dir otherwise
[04:07] <Nafallo> the upstream packager will fix that before he uploads it to the archive :-)
[04:07] <Nafallo> ;-)
[04:08] <sistpoty> Nafallo: ok, then take this +1 and use it once you have fixed the issues ;)
[04:08] <Nafallo> sistpoty: thanks dude *hugs*
[04:08] <sistpoty> Nafallo: thanks for your contribution ;)
[04:09] <Nafallo> *grins*
[04:14] <rexbron> sistpoty: should the modified tarball have the dfsg versioning aswell?
[04:14] <sistpoty> rexbron: yes, it should... because it's not the original tarball but something different
[04:14] <rexbron> ok cool
[04:15] <sistpoty> (that's the reason I wanted the dfsg to be part of the upstream version)
[04:15] <rexbron> I see
[04:22] <sistpoty> ok, I'm off to bed now
[04:22] <sistpoty> gn8 everyone
[04:22] <Nafallo> sistpoty: gnight
[04:26] <LaserJock> man, gotta love spam warning about spam/viruses/spybots
[04:28] <TheMuso> LaserJock: heh
[04:46] <rexbron> LaserJock: Would you be able to do a review? upid 4279
[04:50] <TheMuso> rexbron: I am doing a test build now. There is something I want to make sure of before saying anything, as I haven't had much to do with cdbs previously.
[04:51] <rexbron> TheMuso: cool
[05:09] <rexbron> TheMuso: how goes it?
[05:10] <TheMuso> its built, but I'm just checking something first
[05:10] <TheMuso> ok no what I was looking for seems to be taken care of by cdbs.
[05:11] <TheMuso> rexbron: What are you worried about re changelog?
[05:11] <TheMuso> And there is a dfsg in the changelog entry. What was removed?
[05:11] <rexbron> too many entries
[05:11] <rexbron> TheMuso: ffmpeg
[05:11] <rexbron> TheMuso: it is using ubuntu binaries 
[05:11] <rexbron> TheMuso: Should the dfsg change be listed?
[05:12] <TheMuso> In the new entry, it is probably worth stating that ffmpeg was removed, and the Ubuntu binaries used. Other MOTUs may be able to ffer comment on that however.
[05:15] <rexbron> TheMuso: Found anything else?
[05:15] <TheMuso> But having two entries is fine, as they are for different releases.
[05:16] <TheMuso> rexbron: Looking again. Was just checking that the later version was greater than the former in the changelog.
[05:16] <rexbron> hmm?
[05:16] <TheMuso> dpkg has a command that allows you to compare whether one version number is greater than another.
[05:17] <rexbron> ok
[05:18] <TheMuso> I don't understand why your copyright file is layed out as it is. I'd rather leave those more experienced with licensing to confirm that.
[05:19] <rexbron> TheMuso: LaserJock directed me to do it like that
[05:19] <rexbron> so I will run it by him to make sure is it up to snuff
[05:20] <rexbron> but you are suposed to list the licence and copyright of everyfile that is distributed in the source package
[05:21] <TheMuso> rexbron: I know that.
[05:21] <TheMuso> Most other copyright files I've seen have been simpler than that, thats all.
[05:21] <LaserJock> what did I do?
[05:21] <rexbron> LaserJock: just the debian/copyright file for Soma
[05:22] <TheMuso> Shouldn't the libsoma-dev be in section libdevel?
[05:22] <rexbron> at sisypot's direction, ffmpeg was removed from the upstream tar ball and dfsg versioning was added
[05:22] <rexbron> TheMuso: was not sure,
[05:22] <rexbron> you would know better than I
[05:22] <TheMuso> hmm maybe not
[05:23] <rexbron> it is the devel files for a lib, but the source package is for a program
[05:23] <rexbron> if that makes a difference
[05:23] <TheMuso> I don't think it matters.
[05:23] <rexbron> LaserJock: what is your take on the above?
[05:23] <TheMuso> I have just looked at two other packages. One has libdevel, one has devel.
[05:25] <TheMuso> SO I don't *think* it matters.
[05:28] <TheMuso> I haven't looked very hard, but libdevel is a valid section so I dunno.
[05:28] <TheMuso> Other packages use it, so it shouldn't be a problem
[05:29] <TheMuso> rexbron: Any reason for the binary/clean target in debian/rules?
[05:29] <rexbron> so it should not be a problem either way>
[05:30] <TheMuso> No.
[05:30] <rexbron> TheMuso: sometimes config.log does not get removed, and that can gum up the build
[05:30] <rexbron> but if it is in pbuilder, should be unnessicary now
[05:30] <TheMuso> According to the rules file, its config.status you are removing.
[05:30] <rexbron> ..
[05:30] <rexbron> that is old
[05:31] <rexbron> need to fix that
[05:31] <TheMuso> Why aren't you building the python stuff?
[05:32] <rexbron> really buggy build process
[05:32] <TheMuso> How so?
[05:32] <rexbron> like to try and install itself on the system instead of following any prefixes
[05:32] <rexbron> same with phpsoma
[05:33] <rexbron> I have contacted upstream about it and it is getting fixed in the next major release
[05:34] <rexbron> TheMuso: ok, the binary rules is fixed, and so is libsoma-dev's section
[05:34] <LaserJock> build and clean are required rules
[05:34] <rexbron> LaserJock: cdbs
[05:34] <TheMuso> LaserJock: Cdbs takes care of those I thought
[05:35] <LaserJock> ah, it's cdbs
[05:35] <LaserJock> my bad
[05:35] <rexbron> np
[05:36] <TheMuso> rexbron: The section for the dev package doesn't have to be libdevel as far as I have seen from other apckages.
[05:37] <rexbron> is there any reason not to?
[05:37] <rexbron> ( as I will need to reupload any way
[05:38] <TheMuso> Well some major libraries for the syste are libdevel, so I guess its a good idea to use it.
[05:39] <rexbron> if there is an issue, it will be fixed
[05:40] <TheMuso> Well you changed to libdevel so I think you're safe.
[05:40] <TheMuso> ooo storm coming.
[05:40] <rexbron> :0
[05:40] <rexbron> TheMuso: 
[05:41] <rexbron> TheMuso: So if I re-upload, and the debdiff is good, is there a stamp of approval?
[05:42] <TheMuso> Re-upload and I'll have a look at the differences.
[05:47] <rexbron> TheMuso: I need sleep, the upload is done
[05:48] <rexbron> so if there are issues, just leave a nice comment
[05:49] <TheMuso> rexbron: SUre.
[06:20] <LaserJock> is there still no website for falcon?
[07:02] <TheMuso> Bah! I am not finding revu very intuative. I've managed to place comments on the wrong date every bloody time!
[07:04] <TheMuso> SOrry those on the revu ml. I'll know better for next time. grrr :S
[07:58] <\sh> moins
[08:02] <\sh> geser: ping xmms2 again, do you think debian/rules should execute scons in clean target? 
[08:22] <zakame> good afternoon MOTUs
[08:23] <TheMuso> Hey zakame.
[08:23] <zakame> hello TheMuso
[08:24] <\sh> hey zakame
[08:24] <zakame> hello \sh!
[08:36] <\sh> moins raphink
[08:37] <raphink> hi \sh :)
[08:37] <raphink> how are you doing today \sh ?
[08:42] <\sh> raphink: well, I was early in the office...and right now, I'm fighting against tickets and broken hardware :(
[08:42] <\sh> and until now no coffee
[08:53] <raphink> :(
[08:53] <raphink> I'm going to have another day fighting with backports here ;)
[08:53] <raphink> but thanks to buildd, it won't be that long :)
[09:58] <raphink> hi phanatic
[09:58] <phanatic> morning raphink 
[09:58] <raphink> :)
[09:59] <raphink> what's up?
[10:01] <zakame> yo raphink phanatic dholbach
[10:01] <zakame> what are you guys down with? :)
[10:01] <raphink> hi dholbach zakame
[10:01] <dholbach> good morning
[10:01] <dholbach> hey zakame
[10:01] <dholbach> hey raphink
[10:01] <phanatic> hey zakame and dholbach
[10:02] <ajmitch> hi dholbach, everyone
[10:02] <zakame> yo ajmitch
[10:02] <ajmitch> hey zakame 
[10:02] <phanatic> raphink: just got back from the bazaar sprint in amsterdam :)
[10:02] <raphink> oh really?
[10:02] <raphink> I didn't know about this one :)
[10:02] <raphink> I was in A'dam 2 days ago :)
[10:02] <raphink> got back on Sunday evening
[10:02] <dholbach> hey ajmitch
[10:03] <raphink> hi ajmitch :)
[10:04] <phanatic> raphink: heh, i got back on Monday evening... funny :)
[10:04] <raphink> yes :)
[10:04] <raphink> I almost got back on Monday 
[10:04] <raphink> but I thought it would be better to keep my vacation for later :)
[10:05] <phanatic> :)
[10:05] <phanatic> i also have to work now, and university starts next week
[10:06] <raphink> ok
[10:08] <phanatic> i just dist-upgraded to feisty... had long time without development versions :)
[10:09] <raphink> hehe
[10:21] <RAOF> Is anyone around to review http://revu.tauware.de/details.py?upid=4132 ?
[10:21] <RAOF> I'm not the uploader, but I'd really like to get that into Feisty, if at all possible.
[10:22] <RAOF> I should have a REVU account.  Can I help?
[10:23] <raphink> you sure can help
[10:23] <raphink> you can review the package and send me the comments
[10:23] <raphink> I'll publish them
[10:41] <dholbach> didn't somebody have a pimped, updated html version of 'apt-cache -i unmet' somewhere?
[10:42] <dholbach> it should be linked from from MOTUTodo
[10:45] <Hobbsee> dholbach: i thought the people submitted bugs for that
[10:45] <dholbach> oh, hm
[10:49] <dholbach> maybe i could hack bughelper to find if a certain bug has already been filed
[10:49] <dholbach> that way we could automate the process of filing bugs
[11:52] <cyberixae> Does the requested packages go trought some proces?
[11:52] <cyberixae> Or do they just sit on the wiki?
[11:58] <Hobbsee> cyberixae: they sit on the wiki until someone looks at it, thinks it looks interesting, and packages it.
[12:03] <ajmitch> hm, that could be why sound is going nuts
[12:03] <ajmitch> fan warning when I went to reboot..
[12:07] <ajmitch> curses, dead fan on the motherboard
[12:07] <Hobbsee> heh
[12:07] <Hobbsee> oh dear
[12:07] <ajmitch> yeah, well
[12:07] <StevenK> ajmitch: On the north bridge?
[12:07] <TheMuso> May need a good clean.
[12:07] <ajmitch> probably
[12:08] <StevenK> Most north bridges don't run hot enough for a fan.
[12:08] <tepsipakki> ajmitch: just replace it with a passive heatsink ;)
[12:08] <StevenK> There are exceptions. :-)
[12:09] <ajmitch> hm, I think it could be the southbridge
[12:09] <ajmitch> it's an amd64 anyway
[12:10] <StevenK> The {north,south}bridge on my amd64 is passively cooled.
[12:10] <ajmitch> well it was causing enough problems with sound :)
[12:10] <StevenK> Then again, it's a *tiny* SFF case with an enormous CPU fan and good air flow. :-)
[12:10] <ajmitch> yeah, this is a fulltower case
[12:10] <ajmitch> and it's fairly warm in here at the moment
[12:11] <StevenK> Heh
[12:11] <ajmitch> I was wondering, the motherboard temperature was slightly higher than usual 
[12:12] <ajmitch> I was curious
[12:14] <ajmitch> what a pain, it hasn't
[12:15] <StevenK> ajmitch: I'd clean it, like TheMuso suggested.
[12:15] <StevenK> Blasting it with compressed air if you have some handy may well help.
[12:16] <ajmitch> I don't have any on hand
[12:16] <ajmitch> & I usually wouldn't expect the fan to stop dead
[12:16] <StevenK> Most fans are very simple. :-)
[12:17] <ajmitch> quite :)
[12:44] <ajmitch> oh zope
[12:44] <Fujitsu> Yeah.
[12:44] <Fujitsu> I was thinking of you.
[12:44] <Fujitsu> :P
[12:44] <Fujitsu> Unfortunately, there's no new release, but Twisted 2.5 breaks it.
[12:45] <Fujitsu> So, we either have broken Zope, or assemble a SVN HEAD web2, somehow.
[12:45] <ajmitch> breaks in what way?
[12:45] <Fujitsu> The release tarball doesn't seem to bear any resemblance to the stuff that's in SVN; it's got a fair bit of extra stuff in the root.
[12:46] <Fujitsu> Er, Zope won't start...
[12:46] <Fujitsu> Bug #83053
[12:46] <Ubugtu> Malone bug 83053 in twisted-web2 "AttributeError: components.Interface" [High,Confirmed]  https://launchpad.net/bugs/83053
[12:46] <Fujitsu> I ran into it a while ago.
[12:47] <ajmitch> right, so it's a nice chain of brokenness
[12:48] <Fujitsu> Sorta.
[12:48] <Fujitsu> Basically, everything is solved if we get a new web2.
[12:48] <Fujitsu> I don't know, but it wasn't overly sane.
[12:48] <ajmitch> oh, doko did
[12:48] <Fujitsu> (and web2 is in main... aren't we getting rather close to ultimate-freeze?)
[12:48] <ajmitch> python 2.5 compatibility
[12:49] <Fujitsu> OK.
[12:49] <Fujitsu> A little more sane, then.
[12:49] <ajmitch> but a new web2 isn't really out, and will it still work with zope?
[12:49] <ajmitch> doko is also the twisted-web2 maintainer for debian
[12:49] <Fujitsu> Ah, so it's doko's problem. Goodo.
[12:49] <Fujitsu> It might work, but I'm not sure.
[12:49] <ajmitch> yep
[12:50] <doko> Fujitsu: no, zope3 doesn't work with 2.5
[12:50] <Fujitsu> Crap.
[12:50] <Fujitsu> That's not what I wanted to hear.
[12:50] <ajmitch> hi doko 
[12:50] <Fujitsu> (it wasn't a great first impression when I tried to start Zope for the first time a week ago, and I got that :-/)
[12:50] <ajmitch> what were you playing with zope for?
[12:51] <Fujitsu> Why not?
[12:51] <ajmitch> because it requires a large non-refundable investment of time & sanity
[12:51] <Fujitsu> Pfft.
[12:52] <Fujitsu> doko: Is the incompatibility likely to be fixed in the near future?
[12:52] <ajmitch> good fun though
[12:52] <Fujitsu> That's what I thought.
[12:56] <doko> zope doesnt adopt new python versions very fast
[12:56] <Fujitsu> I
[12:56] <Fujitsu> *I'll take that as a no, then :(
[12:58] <TheMuso> ajmitch: SO its dead dead.
[12:59] <Fujitsu> siretart: I note that you have a million and one branches on the mplayer product. Can you please set the ones that have been merged into ubuntu to Merged, etc?
[01:00] <ajmitch> TheMuso: well it's not spinning
[01:01] <TheMuso> right
[01:02] <ajmitch> ugh, someone had to add NM to ubuntu-desktop
[01:02] <ajmitch> now it claims I have no network, and so certain apps won't connect
[01:02] <Fujitsu> Ah, finally.
[01:03] <siretart> Fujitsu: I haven't done an mplayer upload since ages, you should ask Nafallo
[01:03] <Fujitsu> ... It's good except for cases like that :P
[01:03] <Fujitsu> siretart, but you own the branches.
[01:03] <Fujitsu> They're merged, but still have status New.
[01:03] <Fujitsu> You are the only one with permissions to change the status on your branches.
[01:04] <ajmitch> of course there's no obvious way to configure NM
[01:04] <siretart> don't expect random user branches to be authoritative
[01:04] <Fujitsu> ajmitch, configuration? What configuration?
[01:04] <siretart> Fujitsu: I do think we should have a motumedia mplayer team branch, which is authoritative
[01:04] <ajmitch> Fujitsu: the bits that make things go
[01:04] <Fujitsu> siretart, but it's useful to minimise clutter on the page.
[01:04] <siretart> Fujitsu: if there isn't one, let's please create one
[01:04] <siretart> Fujitsu: right. Is there a way to remove branches from launchpad?
[01:04] <Fujitsu> siretart, the ubuntu-dev one is authoritative.
[01:05] <Fujitsu> No, but they will vanish from the main list if set to Merged/Abandoned.
[01:05] <siretart> interesting. will do so then, after we have an authoritiatvive one
[01:05] <Fujitsu> We do.
[01:05] <Fujitsu> ~ubuntu-dev/ubuntu.
[01:05] <siretart> oh
[01:06] <Fujitsu> (but they're already merged, so you simply need to modify the status field on yours that have been merged)
[01:08] <siretart> aah, abandoned branches don't show up in the list. interesting
[01:08] <Fujitsu> (they should actually be Merged, but they achieve similar things)
[01:09] <siretart> Fujitsu: do you use bzr-builddeb for building?
[01:09] <Fujitsu> I don't, no.
[01:09] <Fujitsu> I've not looked at it.
[01:11] <Fujitsu> Thanks for doing that, the list is somewhat cleaner now.
[01:13] <siretart> Fujitsu: I changed the maintainer of the mplayer lp product to motumedia
[01:13] <Fujitsu> siretart, I was also going to suggest that :)
[01:15] <Nafallo> siretart: I do
[01:15] <Nafallo> siretart: it rocks :-)
[01:17] <siretart> Fujitsu: http://bazaar.launchpad.net/~ubuntu-dev/mplayer/upstream-ubuntu does not seem to contain the packaging branch for mplayer since it doesn't contain any debian/ dir. don't we have some branch which has it?
[01:18] <siretart> Nafallo: :)
[01:18] <Fujitsu> siretart, ~ubuntu-dev/mplayer/ubuntu does.
[01:18] <Fujitsu> upstream-ubuntu is the stripped upstream archive.
[01:19] <siretart> k
[01:58] <siretart> Fujitsu: welcome to motumedia :)
[02:13] <RAOF_> raphink: I've uploaded a new gnome-compiz-manager with manpages. http://revu.tauware.de/details.py?upid=4281
[02:14] <RAOF_> Since I didn't add my name to the changelog, it seems REVU won't let me comment on that upload.  Should I have added a changelog entry?
[02:17] <Adri2000> RAOF: no, use dput -f
[02:18] <Adri2000> RAOF_: ^
[02:18] <RAOF_> Adri2000: It's already on REVU, though, and the packaging was done by someone else.
[02:18] <Adri2000> well yes, sorry, I can't read...
[02:19] <RAOF_> I just added manpages, and fixed the build-dep version on debhelper, so my name isn't on the changelog :)
[02:20] <RAOF_> Although, if you can, I'd love you to review & advocate it :)
[02:22] <Adri2000> I'm not sure to understand, it's a NEW package, right? ie. not yet in debian or in ubuntu
[02:22] <Hobbsee> RAOF_: yes, that's normal
[02:22] <Hobbsee> RAOF_: if you're not the guy in the changelog, or not a MOTU, you wont be able to respond in the package in REVU.  oh wait.  are you logged in?
[02:23] <RAOF_> Yes, I'm logged in.
[02:23] <Hobbsee> Adri2000: can just anyone who's signed in respond to any package on REVU?
[02:23] <ajmitch> no
[02:23] <Hobbsee> didnt think so.
[02:23] <RAOF_> Only MOTU.
[02:24] <RAOF_> Uploaders get to respond to their own uploads, as long as they have their name on the changelog, apparently :)
[02:24] <Adri2000> I see the last upload is from gandalfn@club-internet.fr, and it doesn't seem to be you RAOF_
[02:25] <RAOF_> Adri2000: But the current debdiff has the manpages I wrote in them.
[02:25] <Adri2000> ohh, I understand now
[02:25] <RAOF_> Down the bottom, upload as of feb 07
[02:25] <RAOF_> :)
[02:26] <RAOF_> Should I have added my name somewhere official?  Or is it ok?
[02:26] <Adri2000> in fact, we can't see if an upload has really been made by the user mentioned at the top of the page ("from user ...") :s
[02:26] <Adri2000> is it right ajmitch?
[02:27] <ajmitch> obviously not, since it only goes on the changelog, not the signature
[02:28] <RAOF_> There's nothing else I can do to help it along, is there?
[02:28] <RAOF_> I can get some sleep, too?
[02:29] <ajmitch> generally if you upload it to REVU, you take responsibility to fix it up as we suggest
[02:30] <RAOF_> Certainly.
[02:30] <ajmitch> night all
[02:30] <RAOF_> Is anyone likely to suggest things for me to fix in the next 8 hours? :)
[02:30] <Hobbsee> night ajmitch 
[02:30] <RAOF_> night, and thanks ajmitch
[02:36] <Adri2000> RAOF_: during the REVU sprint probably (beginning tomorrow): https://lists.ubuntu.com/archives/ubuntu-motu/2007-February/001253.html
[02:37] <RAOF_> Oh, excellent.  See you on here tomorrow, then.
[02:38] <Adri2000> yep, here it's today 2 pm
[02:39] <RAOF_> Oh, where as here it's tomorrow 12:30 am.  Probably time to bail.
[03:00] <rexbron> TheMuso: Soma: Fixed and reuploaded
[03:17] <davromaniak> ping slomo 
[03:29] <esaym> How hard would it be for a newbie to make a package to upgrade amarok to the lastest version?
[03:30] <esaym> I have compiled software before but I have not ever made packages
[03:30] <esaym> I would like to give it a shot
[03:33] <Adri2000> esaym: it is already the latest version
[03:33] <slomo> davromaniak: pong
[03:34] <davromaniak> slomo, I packaged youtranslate, and it's in mono, and some people told me that you know mono
[03:35] <esaym> version 1.4.5 has been out awhile
[03:35] <slomo> davromaniak: yes so if you know packaging in general read http://pkg-mono.alioth.debian.org/cli-policy/
[03:35] <esaym> and kubuntu is still at 1.4.3
[03:35] <esaym> instead of bitching about it I figured I would try and update it.....
[03:35] <Adri2000> esaym: amarok | 2:1.4.5-0ubuntu2 | http://archive.ubuntu.com feisty/main Packages
[03:36] <davromaniak> I read it, and I think my package respects this policy, and I ask you to review it, when you will have some stare time
[03:36] <esaym> yes but will that work in dapper?
[03:36] <Adri2000> esaym: there won't be any new upstream version in stable releases (breezy, dapper, edgy)
[03:36] <davromaniak> hmmm, spare time
[03:36] <esaym> so even if I made a package it would not be used?
[03:38] <Adri2000> esaym: there are packages available for edgy: http://kubuntu.org/announcements/amarok-1.4.5.php (but not officially supported) made by Riddell (kubuntu developer)
[03:38] <esaym> Adri2000? anyone?
[03:38] <esaym> oh hmm
[03:38] <davromaniak> so slomo, here a link : http://revu.tauware.de/details.py?upid=4144
[03:39] <slomo> davromaniak: sure send me a mail with the url to slomo@ubuntu.com... bbl
[03:39] <davromaniak> ok  thanks
[04:12] <bddebian> Heya gang
[04:13] <raphink> hi bddebian
[04:13] <bddebian> Heya raphink
[04:14] <esaym> is there a 100% noob guide to making kubuntu packages?
[04:33] <_Enchained> Hi motus :)
[04:40] <raphink> imbrandon: just saw that you added dh_iconcache to the j2se1.4-amd64 package but you didn't upgrade the debhelper version (dh_iconcache is for debhelper5 only)
[04:40] <raphink> hmm well I'll fix it
[04:40] <bddebian> Heya _Enchained
[04:40] <raphink> it'll be faster :)
[04:42] <raphink> hi ivoks :)
[04:45] <_Enchained> bddebian: a little question :
[04:46] <_Enchained> In dvd95 (that you have advocate), there was a debian/ folder in the "real" orig.tar.gz
[04:46] <bddebian> Yes
[04:47] <_Enchained> I've removed it from my orig.tar.gz and wrote it in changelog
[04:47] <_Enchained> After emailing upstream,
[04:47] <bddebian> OK
[04:47] <_Enchained> He send me a corrected tarball
[04:47] <_Enchained> without this useless folder
[04:47] <_Enchained> and will update it on sourceforge
[04:48] <_Enchained> so should I remake the package ?
[04:48] <_Enchained> as the changelog is not the true (now)
[04:48] <_Enchained> or it's ok..
[04:49] <_Enchained> (I hope you understood the question^^)
[04:50] <raphink> esaym: did you read the ubuntu packaging guide?
[04:51] <bddebian> _Enchained: Ideally you should re-build with the new tarball
[04:51] <esaym> I am reading the debian one
[04:51] <esaym> which one are you talking about raphink
[04:52] <_Enchained> ok bddebian (in fact I have just to remove the comment about modified tarball in changelog...)
[04:53] <raphink> esaym: the one that is on http://help.ubuntu.com 
[04:53] <raphink> esaym: which was written because the debian one is too complicate for most people
[04:55] <esaym> raphink: no I didn't see that one
[04:55] <esaym> thank you
[04:55] <raphink> well now you know it ;)
[04:55] <esaym> the debain one is kinda over my head ;)
[04:55] <raphink> it's also included in Ubuntu/Kubuntu
[04:55] <raphink> locally
[04:56] <raphink> esaym: yes it's not very easy, eventually you might ask a mentor to help you, too
[04:56] <esaym> yea I keep forgetting about that
[04:56] <esaym> I hope to update some apps on dapper which is no longer really being supported
[04:56] <esaym> as far as bug fixes
[04:57] <raphink> well dapper is frozen
[05:00] <raphink> so it's normal for it to not be updated so much
[05:00] <esaym> yes I think thats kinda crappy
[05:01] <raphink> why ?
[05:01] <esaym> Well there are still plenty of bugs in it
[05:01] <esaym> I don't think they should just leave it like that
[05:01] <raphink> what do you propose ?
[05:01] <raphink> to update with newer versions of packages?
[05:01] <raphink> or to include patches to fix each bug?
[05:02] <esaym> I don't want to have to do a massive upgrade every six months to get updated software
[05:02] <raphink> there are security updates for dapper
[05:02] <raphink> and normal updates, too
[05:02] <raphink> but not for every little bug
[05:02] <esaym> amarok has a couple of bugs in it that have been fixed in the lastest version
[05:02] <raphink> otherwise we would spend all our time taking care of dapper
[05:02] <raphink> instead of developping fesity
[05:02] <raphink> feisty
[05:02] <esaym> Yes I know
[05:03] <_Enchained> bddebian: dvd95 with the new orig tarball is incoming
[05:03] <raphink> esaym: can you add a patch to fix the bugs without having to backport amarok?
[05:03] <bddebian> _Enchained: OK
[05:03] <raphink> if you need the latest version of amarok, use the backports
[05:03] <raphink> I'm sure it's there
[05:03] <esaym> I don't know what to do hence why I decided to try making my own packages because I like dapper and don't want to upgrade
[05:04] <esaym> There is nothing in the backports for dapper for amarok
[05:05] <esaym> amarok backport for dapper is version 1.4.3, the same that was already installed
[05:05] <raphink> amarok engines are backported
[05:06] <esaym> amarok-engines (2:1.4.3-0ubuntu8~dapper1??
[05:06] <esaym> still says 1.4.3
[05:06] <raphink> the whole point of having a frozen release is that packages are _frozen_
[05:06] <raphink> if you want amarok 1.4.5 for dapper
[05:06] <raphink> you can try backporting it
[05:06] <raphink> just set a dapper pbuilder and rebuild it :)
[05:06] <esaym> how would I go about that?
[05:07] <raphink> there's a doc on the wiki to set pbuilders :)
[05:07] <esaym> hmm
[05:07] <_Enchained> bddebian: it's ok http://revu.tauware.de/details.py?upid=4286
[05:07] <raphink> https://wiki.ubuntu.com/PbuilderHowto
[05:07] <raphink> esaym: look at this page, set a pbuilder (which you will need to make and test packages anyway)
[05:07] <raphink> and backport amarok for dapper :)
[05:08] <raphink> and soon you'll understand why we don't do it :)
[05:08] <raphink> (backporting is kind of my job, I'm currently backporting tomcat5 for sarge, and it's not fun, trust me ;) )
[05:08] <esaym> lol is it buggy or something?
[05:08] <raphink> esaym: programs in GNU/Linux use shared libraries
[05:08] <raphink> new programs use new libraries
[05:08] <esaym> yea sounds like a mess
[05:08] <raphink> very often, when you need to backport a program, it depends on new libraries
[05:09] <raphink> that are not in the old version of the distro
[05:09] <esaym> I was wondering about that
[05:09] <raphink> so you have to backport these new libraries
[05:09] <raphink> and then you have to set a limit to what you backport
[05:09] <raphink> in order to 
[05:09] <esaym> thats was why I wanted to build the lastest version from source and make a package
[05:09] <raphink> 1) not spend more time on it than you should
[05:09] <raphink> 2) not break other apps depending on these libs
[05:09] <raphink> currently, i'm rebuilding tomcat5 for sarge
[05:10] <raphink> and I'm already at the 3rd level of backports
[05:10] <esaym> sounds like it would just be easier to make a package from the source?
[05:10] <raphink> since tomcat5 build-depends on java-gcj-compat-dev which itself depends on  gcj-4.1
[05:10] <raphink> and none of these are in sarge
[05:10] <raphink> now in some cases
[05:10] <raphink> for example, valgrind for amd64
[05:10] <raphink> you just can't do it
[05:10] <raphink> valgrind for amd64 requires a new gcc lib to build
[05:11] <raphink> and it's not reasonable to backport the toolchain
[05:11] <raphink> esaym: I'm talking about making a package from the source
[05:11] <raphink> not about anything else
[05:11] <esaym> hmm
[05:11] <raphink> new programs depend on new libraries, new compilers, and so on
[05:11] <esaym> Yea I got that
[05:11] <raphink> backporting is not the easiest thing ever ;)
[05:12] <raphink> but it's fun :)
[05:12] <esaym> I thought backporting = taking an already built package for another distro and making it work for an older distro?
[05:12] <raphink> yes exactly
[05:13] <esaym> well then what is making a package from source?
[05:13] <raphink> if you have a hard time seeing the problem with software, try to think about hardware maybe
[05:13] <raphink> say you want to add some new RAM to your machine
[05:13] <raphink> but in order to do that
[05:13] <raphink> you need to upgrade your motherboard
[05:13] <raphink> but then your CPU is too old and you have to change it
[05:13] <esaym> Yes I understand the dependencies
[05:13] <raphink> well that's about it
[05:13] <esaym> Thats why I don't use Slackware... ;)
[05:13] <raphink> dependencies can make backports a mess
[05:14] <esaym> I dont get how you say backporting and biulding from source are the same thing though?
[05:15] <raphink> all packages in Ubuntu are built from source
[05:15] <raphink> hmm except for non open-source ones
[05:15] <raphink> ;)
[05:15] <esaym> I guess I am just really lost
[05:15] <esaym> I got to get to class
[05:15] <esaym> I am late
[05:16] <raphink> ok
[05:16] <raphink> see you later :)
[05:16] <esaym> I will try and catch you later on
[05:20] <\sh> re moins
[05:20] <bddebian> wb \sh
[05:21] <raphink> hi \sh
[05:25] <\sh> guys, if you want to have a nice hardware in your DC, checkout the new HP BL35-c class blade series ;)
[05:27] <raphink> :)
[05:55] <Le-Chuck_ITA> Hi all, What is REVU?
[05:57] <Le-Chuck_ITA> https://wiki.ubuntu.com/REVU2Spec
[05:57] <Le-Chuck_ITA> looks interesting
[05:58] <Le-Chuck_ITA> so if I sign my name there I will be enabled to fix bugs myself and, with successful review, these patches will be applied directly? And to which distribution?
[05:59] <Le-Chuck_ITA> and why am I talking alone? :)
[05:59] <dholbach> hey Le-Chuck_ITA
[06:00] <dholbach> if you are talking about getting patches / packages uploaded to Ubuntu, you might want to refer to https://wiki.ubuntu.com/SponsorshipProcess
[06:00] <Le-Chuck_ITA> Hi! You confirmed a bug of mine recently so I am happy to meet you
[06:00] <dholbach> :)
[06:01] <Le-Chuck_ITA> no I am talking of something like fixing a small bug in a forgotten universe package
[06:01] <dholbach> yeah, that's what I talk about also :)
[06:01] <Le-Chuck_ITA> and getting that uploaded so that successive upgrades will not delete my fix
[06:01] <dholbach> right
[06:01] <dholbach> the process is outlined in the wiki page I mentioned
[06:02] <Le-Chuck_ITA> isn't sponsorship for new packages only?
[06:02] <dholbach> no
[06:02] <Le-Chuck_ITA> and what is revu for, then?
[06:02] <dholbach> uploading a source package for somebody who's not in ubuntu-dev or ubuntu-core-dev  =  sponsoring an upload
[06:02] <Le-Chuck_ITA> ok
[06:03] <dholbach> we use revu for NEW packages and sometimes for package updates
[06:03] <dholbach> if you have a small fix, attaching the debdiff to a launchpad bug is more intuitive
[06:03] <Le-Chuck_ITA> yes but if the package has no maintainer nobody will ever fix
[06:04] <dholbach> that's why you subscribe a sponsor team to the bug
[06:04] <dholbach> if you read the document you'll see that it makes sense
[06:04] <Le-Chuck_ITA> ah ok just reading it now
[06:04] <dholbach> ok
[06:04] <Le-Chuck_ITA> yes it makes sense
[06:05] <dholbach> ok cool :)
[06:06] <Le-Chuck_ITA> will there be any lesson on how to properly create a debdiff or will I always have to stick with the debian-related "official" document? E.g. to know what "DEBEMAIL" is
[06:06] <Le-Chuck_ITA> for
[06:07] <Le-Chuck_ITA> Yes this is a request for a lesson :)
[06:10] <Le-Chuck_ITA> ok this is asking too much
[06:10] <Le-Chuck_ITA> my last question is:
[06:10] <Le-Chuck_ITA> suppose that upstream released two major versions since the version in feisty of a package
[06:10] <Le-Chuck_ITA> and the package is in debian
[06:10] <Le-Chuck_ITA> how will I ever get the new version  in feisty? Should I bug debian first?
[06:11] <_Enchained> bddebian: dvd95 is uploaded ? I don't see it on revu (the new "clean")
[06:11] <bddebian> _Enchained: Aye, I uploaded it again
[06:12] <Le-Chuck_ITA> of a universe package, of course
[06:13] <dholbach> Le-Chuck_ITA: a normal diff is fine too
[06:13] <_Enchained> bddebian: it's ok (I've just changed the changelog)
[06:13] <Le-Chuck_ITA> this is for the debdiff issue, I see - but what about getting new versions of universe packages in ubuntu?
[06:14] <dholbach> Le-Chuck_ITA: for a debdiff you: dch -i (create a new changelog entry), run debuild -S (create a new source package), run: debdiff bla1.dsc bla2.dsc > bla.debdiff and attach the debdiff to the bug
[06:14] <dholbach> Le-Chuck_ITA: for that we use REVU
[06:14] <dholbach> http://wiki.ubuntu.com/REVU should have more information about that
[06:14] <Le-Chuck_ITA> so I can upload a new upstream version of an existing package to REVU and have somebody look at it?
[06:14] <Le-Chuck_ITA> this is great information
[06:14] <Le-Chuck_ITA> for me at least .)
[06:14] <dholbach> yeah :)
[06:14] <dholbach> cool :)
[06:15] <Le-Chuck_ITA> I finally have a goal
[06:15] <Le-Chuck_ITA> :) :)
[06:15] <Le-Chuck_ITA> and - well I promised that was my last question - should then the changes merged to debian unstable?
[06:16] <dholbach> if you have a interest in the package, it's a very good thing to build a good communication channel with the debian maintainer
[06:17] <dholbach> and sending patches is a very good way to do that :)
[06:18] <Le-Chuck_ITA> ok I understand - so there is no problem in having a newer version in ubuntu than in debian, but one usually sends patches to the debian maintainer so that versions can be kept in sync
[06:20] <geser> Le-Chuck_ITA: are you wanting to get a new upstream version of a package into Ubuntu or just bugfixes to the current one?
[06:20] <Le-Chuck_ITA> two different issues
[06:20] <Le-Chuck_ITA> one is lyx, another one is xournal, but there are others on my todo list
[06:21] <Le-Chuck_ITA> lyx needs a fix, xournal newer version after I test that 
[06:21] <Le-Chuck_ITA> I use them both a lot of hours per day and feel like I can improve their situation in ubuntu, that's all
[06:22] <geser> just to let you know: tomorrow is UVF (UpstreamVersionFreeze): no new upstream version are allowed anymore
[06:24] <Le-Chuck_ITA> hmmm
[06:25] <Le-Chuck_ITA> the best I could do for today is to post a ordinary diff between new package of xournal (I downloaded it right now)
[06:25] <Le-Chuck_ITA> but would it get any chance of being uploaded for tomorrow?
[06:27] <geser> it depends if you find someone to review your changes and do the upload
[06:28] <Le-Chuck_ITA> my changes will be the patch to the sources so it would be a big review
[06:28] <Le-Chuck_ITA> hem
[06:28] <Le-Chuck_ITA> ehm
[06:28] <Le-Chuck_ITA> I mean: my changes will be the diff between xournal 0.3.1 and xournal 0.3.3
[06:29] <Le-Chuck_ITA> so I don't expect anybody review upstream code
[06:29] <geser> more important are the fixes for the packaging (if needed)
[06:29] <Le-Chuck_ITA> I hope there is none of them
[06:29] <geser> s/fixes/changes/ :)
[06:30] <Le-Chuck_ITA> getting debian source right now
[06:30] <Le-Chuck_ITA> er
[06:30] <Le-Chuck_ITA> s/debian/ubuntu
[06:31] <geser> doesn't make a difference as the source package is the same
[06:32] <Le-Chuck_ITA> yes I know :)
[07:05] <\sh> hmmm..anyone tried aixgl with normal radeo drivers on feisty?
[07:05] <highvoltage> video killed the radeo star
[07:11] <jharr> what does everyone recommend for a patch manager?
[07:15] <hub> jharr: what do you mean?
[07:16] <LaserJock> jharr: if you're using debhelper I'd go with dpatch, for cdbs I'd go with simple-patch-sys or whatever it's called
[07:21] <Adri2000> simple-patchsys :)
[07:21] <Adri2000> .mk
[07:23] <jharr> is there any disadvantage to using cdbs? (I'm guessing there's some limitations to it)
[07:29] <hub> jharr: for standard packages, none
[07:29] <hub> jharr: beside the fact that lot of debian packager don't like it
[07:55] <Le-Chuck_ITA> what decides the version of a debian package when building a package?
[07:55] <Le-Chuck_ITA> I mean when packing the source with dpkg-source
[07:55] <Le-Chuck_ITA> I can't find any reference to the version in debian/control or other files
[07:56] <Le-Chuck_ITA> is it just the .orig file name?
[07:56] <Le-Chuck_ITA> that gives the version?
[07:57] <LaserJock> debian/changelog
[08:00] <Le-Chuck_ITA> ok and how do I generate that since it seems that by hand it is not so good (there is the date for example)?
[08:01] <bddebian> dch -i
[08:01] <Le-Chuck_ITA> oh thanks 
[08:01] <bddebian> From the src dir not the src/debian dir btw :-)
[08:01] <LaserJock> hm?
[08:02] <LaserJock> you can run dch from debian/
[08:02] <bddebian> You can?
[08:02] <bddebian> hmm
[08:02] <Le-Chuck_ITA> last version is 0.3.1-2
[08:03] <Le-Chuck_ITA> new upstream version is 0.3.3
[08:03] <Le-Chuck_ITA> what do I write? 0.3.3-1?
[08:03] <Le-Chuck_ITA> sorry for bothering with all this newbieness
[08:04] <LaserJock> that would be what the Debian version would be
[08:04] <LaserJock> since we need to keep the ability to sync/merge between Debian and Ubuntu
[08:04] <LaserJock> we use special versioning if we modify a package
[08:05] <LaserJock> if 0.3.3 isn't in Debian yet you would do 0.3.3-0ubuntu1
[08:05] <Le-Chuck_ITA> ok
[08:05] <LaserJock> the 0 is for the Debian revision, in this case it's not there yet so it's 0
[08:05] <Le-Chuck_ITA> perfect
[08:06] <Le-Chuck_ITA> and the 1 after ubuntu?
[08:06] <LaserJock> yeah
[08:06] <LaserJock> that's the 1st revision in ubuntu
[08:07] <LaserJock> if we needed to fix something say in the packaging we would go to 0.3.3-0ubuntu2
[08:07] <Le-Chuck_ITA> ok
[08:09] <Le-Chuck_ITA> oh, and the original source needs autogen.sh to be run
[08:09] <Le-Chuck_ITA> the debian source does not
[08:09] <Le-Chuck_ITA> will I upload orig.tar.gz
[08:09] <Le-Chuck_ITA> with the configure script already present?
[08:10] <LaserJock> do it the way debian does it
[08:13] <LaserJock> are we basically done with merge/sync ?
[08:14] <LaserJock> we've got 12/42 for merges/updated merges on MoM
[08:15] <bddebian> A lot of the merges left cannot be done
[08:15] <bddebian> Not sure about the updated ones
[08:20] <Le-Chuck_ITA> ok
[08:20] <Le-Chuck_ITA> I got my new debian package
[08:20] <Le-Chuck_ITA> now
[08:20] <Le-Chuck_ITA> what
[08:22] <bddebian> dput revu foo.changes ;-)
[08:25] <Le-Chuck_ITA> will it help me signing the dsc
[08:26] <Le-Chuck_ITA> or should I do that before?
[08:26] <Le-Chuck_ITA> I have the .orig, the .diff and the .dsc
[08:26] <Le-Chuck_ITA> hmm
[08:27] <bddebian> dpkg-buildpackage or debuild -S -sa
[08:27] <Le-Chuck_ITA> I already built the binary package with "debian/rules binary"
[08:28] <bddebian> Noooo :-)
[08:28] <Le-Chuck_ITA> I am not getting the point it seems :)
[08:28] <Le-Chuck_ITA> not in the same source dir
[08:28] <Le-Chuck_ITA> I didn't that in the same source dir but in a copy
[08:30] <LaserJock> we have tools to automate building
[08:30] <LaserJock> you shouldn't need to run debian/rules manually
[08:30] <Le-Chuck_ITA> ok 
[08:30] <Le-Chuck_ITA> but I don't have to build the package but to upload the source
[08:30] <Le-Chuck_ITA> isn't it?
[08:30] <LaserJock> right, although it *is* a good idea to test it before you upload :-)
[08:31] <Le-Chuck_ITA> well ok 
[08:31] <Le-Chuck_ITA> I have to unpack the source again using dpkg-source?
[08:32] <LaserJock> do you have devscripts installed?
[08:33] <Le-Chuck_ITA> yes I ran debbuild now
[08:33] <Le-Chuck_ITA> now my .dsc is signed
[08:33] <bddebian> Cool, now pbuild it and make sure it builds :)
[08:33] <Le-Chuck_ITA> but my e-mail address is not therein???
[08:35] <Le-Chuck_ITA> ok will take ages but seems I am really getting there
[08:35] <Le-Chuck_ITA> and this makes me happy
[08:35] <LaserJock> Le-Chuck_ITA: have you seen the Ubuntu Packaging Guide?
[08:35] <Le-Chuck_ITA> I was expecting this question
[08:36] <Le-Chuck_ITA> the package I am preparing is already in ubuntu, only new upstream version
[08:36] <Le-Chuck_ITA> yes I should read the guide
[08:36] <LaserJock> well, the packaging guide doesn't have so much on new upstream versions (yet)
[08:36] <LaserJock> but it does have a fair amount on how to build the packages and things like that
[08:37] <LaserJock> that's why I wondered
[08:37] <Le-Chuck_ITA> in general I know that I should read more documentation before entering the ubuntu "packaging system"
[08:37] <Le-Chuck_ITA> but soon or later I have to start, and I will not have that much time soon
[08:37] <LaserJock> heh
[08:37] <LaserJock> well don't worry about it too much
[08:37] <LaserJock> do what you can and ask questions here if you need help
[08:38] <Le-Chuck_ITA> I am not worrying as you can see :)
[08:38] <Le-Chuck_ITA> thanks for help
[08:38] <Le-Chuck_ITA> you all
[08:39] <LaserJock> np, thanks for helping out
[08:47] <Lutin> bddebian: could you have a look at http://revu.tauware.de/details.py?upid=4288 if you have some time please ? :)
[08:47] <Nafallo> !info 915resolutions edgy
[08:47] <ubotu> Package 915resolutions does not exist in edgy
[08:47] <geser> Nafallo: 915resolution
[08:47] <Nafallo> !info 915resolution edgy
[08:47] <ubotu> 915resolution: resolution modification tool for Intel graphic chipset. In component universe, is extra. Version 0.5.2-4ubuntu1 (edgy), package size 14 kB, installed size 128 kB (Only available for i386 amd64 kfreebsd-i386 kfreebsd-amd64)
[08:47] <Nafallo> thanks geser :-)
[09:07] <Lutin> bddebian: thanks for your review
[09:08] <bddebian> NP
[09:09] <Le-Chuck_ITA> ok it builds under pbuild
[09:09] <Le-Chuck_ITA> I signed the dsc
[09:09] <Le-Chuck_ITA> the checksums of the other two files are in the signed dsc
[09:10] <Le-Chuck_ITA> what remains to do
[09:10] <Le-Chuck_ITA> the upload
[09:10] <Le-Chuck_ITA> ?
[09:11] <Lutin> bddebian: what d oyou think of the readme.debian ? I did that way because it's the way other nautilus-scripts are packaged
[09:11] <Le-Chuck_ITA> Next, ask the REVU admins in #ubuntu-motu or at  keyring@tiber.tauware.de to re-sync the REVU uploaders keyring, which grants you upload rights to REVU
[09:11] <bddebian> Lutin: I think it's OK, I was mainly asking
[09:13] <Lutin> bddebian: ok, reuploading now with a good desktop file :)
[09:13] <Le-Chuck_ITA> Uploading to ubuntu (via ftp to upload.ubuntu.com):
[09:13] <Le-Chuck_ITA>   xournal_0.3.3-0ubuntu1.dsc: done.
[09:13] <Le-Chuck_ITA>   xournal_0.3.3.orig.tar.gz: exiting due to user interrupt.
[09:13] <Le-Chuck_ITA> damnit
[09:14] <Le-Chuck_ITA> did I just make a little mess?
[09:14] <Le-Chuck_ITA> forgot to add "revu" to dput
[09:15] <phanatic> Le-Chuck_ITA: no, it'll be rejected automatically
[09:15] <Le-Chuck_ITA> ok 
[09:16] <Le-Chuck_ITA> now I have to find someone who wants to review the upload for tomorrow
[09:16] <Le-Chuck_ITA> since it's a new upstream version
[09:18] <Lutin> bddebian: updated :)
[09:18] <bddebian> OK
[09:19] <Le-Chuck_ITA> To decrypt your password, type the following into your shell:  > gpg -d <<EOT ; echo  Now paste the text below, and enter EOT<return>  
[09:19] <Le-Chuck_ITA> and there is nothing below
[09:19] <Le-Chuck_ITA> hmmm
[09:19] <Le-Chuck_ITA> suspicious
[09:21] <Le-Chuck_ITA> Mod_python error: "PythonHandler mod_python.publisher"  Traceback (most recent call last):    File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch     result = object(req)    File "/usr/lib/python2.4/site-packages/mod_python/publisher.py", line 136, in handler     result = util.apply_fs_data(object, req.form, req=req)    File "/usr/lib/python2.4/site-packages/mod_python/
[09:21] <Le-Chuck_ITA> sorry for flood
[09:21] <Le-Chuck_ITA> this happened on revu
[09:24] <Le-Chuck_ITA> anyone here?
[09:24] <Le-Chuck_ITA> did I scare everybody :)
[09:25] <bddebian> What do you mean that is happening on REVU?
[09:25] <Le-Chuck_ITA> on the website
[09:25] <Le-Chuck_ITA> revu.tauware.de
[09:26] <Le-Chuck_ITA> I am trying to recover my password 
[09:26] <bddebian> Ohh
[09:26] <Le-Chuck_ITA> maybe I am just not yet synced
[09:26] <Le-Chuck_ITA> because trying with some random letters I get a PGP block
[09:26] <Le-Chuck_ITA> which I suppose are tests made in the DB by administrators
[09:26] <Le-Chuck_ITA> nice security by the way :) :)
[09:27] <Le-Chuck_ITA> and trying some other less common random letters I get the same problems
[09:27] <Le-Chuck_ITA> (trying some random letters, I mean, as e-mail address for the password recovery)
[09:29] <Lutin> thanks bddebian :)
[09:31] <Le-Chuck_ITA> what do I do?
[09:31] <bddebian> NP, though I'm not sure what my reviews are worth lately.  sistpoty and/or Adri2000 might rip it apart yet :-)
[09:34] <Le-Chuck_ITA> guys
[09:34] <Le-Chuck_ITA> I have to end my session and go to cook my pumpkin
[09:35] <jharr> I think the recent feisty updates busted lvm2 on the installer
[09:37] <jharr> http://137.48.138.204/~jharr/motu/
[09:37] <jharr> That preseed file worked perfectly last night
[09:38] <Le-Chuck_ITA> bddebian, LaserJock? please don't leave me alone I am scared of the evil pipe breaker
[09:38] <TheMuso> Hey MOTUs.
[09:38] <bddebian> Heya TheMuso
[09:38] <bddebian> Le-Chuck_ITA: The evil pipe breaker?
[09:38] <Le-Chuck_ITA> yes I can't recover my password and thus complete my work
[09:38] <Le-Chuck_ITA> don't know why but has to do with the above exception
[09:38] <Le-Chuck_ITA> broken pipe
[09:39] <bddebian> I don't know much about the password recovery stuff these days :_(  I know it was broken but I thought that it was fixed .
[09:39] <Le-Chuck_ITA> but I suspect this is just because the database of registered keys should be synced
[09:39] <geser> Le-Chuck_ITA: have you already uploaded successfully to revu?
[09:39] <Le-Chuck_ITA> no this is my first time :)
[09:40] <geser> you should get a password with your first upload
[09:40] <Le-Chuck_ITA> How to log in  After your first upload, you will be automatically registered to the database and assigned a random password. Use the email address you used in the changelog file of your upload as the login name, and press the 'recover password' link, so as to receive your password by email.   
[09:41] <Le-Chuck_ITA> hen, ask  to be added to the Ubuntu Universe Contributors team. Next, ask the REVU admins in #ubuntu-motu or at  keyring@tiber.tauware.de to re-sync the REVU uploaders keyring, which grants you upload rights to REVU
[09:41] <Le-Chuck_ITA> the latter was to be done first
[09:41] <Le-Chuck_ITA> I am in the ubuntu universe contributors team
[09:42] <Le-Chuck_ITA> but what about the "REVU uploaders keyring"?
[09:43] <ajmitch> so you asked, but didn't wait for someone to sync it
[09:44] <Le-Chuck_ITA> to be precise I dumbly thought that since I could upload, the sync must have been automatized
[09:44] <Le-Chuck_ITA> I asked anyway
[09:44] <Le-Chuck_ITA> but didn't wait
[09:45] <Le-Chuck_ITA> will have to redo the upload?
[09:46] <Le-Chuck_ITA> ajmitch: who are the REVU admins?
[09:46] <ajmitch> please wait, I'm resyncing it now
[09:46] <Le-Chuck_ITA> ok I see you are one :)
[09:46] <Le-Chuck_ITA> ok should I upload again with -f
[09:47] <ajmitch> no, I said wait
[09:47] <Le-Chuck_ITA> ok ok sorry
[09:51] <fredl> hi, can I request for something to be packaged in Ubuntu here?
[09:52] <LaserJock> not exactly
[09:52] <LaserJock> it's not that you can't
[09:52] <LaserJock> it's just not the best place
[09:52] <fredl> so what's the best place? somebody on #ubuntu just sent me here.
[09:53] <LaserJock> fredl: for now https://wiki.ubuntu.com/MOTU/Packages/Candidates
[09:53] <fredl> tnx LaserJock
[09:53] <LaserJock> in the future we will be using Launchpad
[09:53] <ajmitch> ah, the grand & glorious future
[09:53] <LaserJock> of course ;-)
[09:53] <LaserJock> well, we could actually do it now
[09:54] <LaserJock> people just have to tag it right
[09:54] <ajmitch> ie, you have to have people going through the bug list every day to manage it :)
[09:55] <Le-Chuck_ITA> ajmitch: I have to go away for half an hour
[09:55] <Le-Chuck_ITA> leaving chat opened
[09:56] <fredl> hmm I have to sign up for the wiki to edit that page? :P
[09:56] <Le-Chuck_ITA> after the sync will I have to reupload or will I act like I had done things in order?
[09:56] <LaserJock> fredl: yes
[09:56] <fredl> fair enough
[09:56] <ajmitch> Le-Chuck_ITA: it should be there now
[09:57] <Le-Chuck_ITA> ok will try before I leave :)
[09:57] <LaserJock> fredl: we can't have people/bots spamming everything
[09:59] <Le-Chuck_ITA> thank you ajmitch
[09:59] <Le-Chuck_ITA> everything is ok now
[10:00] <ajmitch> hey azeem 
[10:00] <Le-Chuck_ITA> Last, but the most important:
[10:00] <LaserJock> hi azeem and Fujitsu 
[10:01] <Le-Chuck_ITA> Is there anybody who is willing to review my "new upstream release" of xournal on REVU before tomorrow?
[10:01] <Fujitsu> Hey LaserJock.
[10:01] <ajmitch> bddebian: why is bibus on revu with that version?
[10:01] <LaserJock> Fujitsu: you use geda or oregano?
[10:01] <fredl> hmm some structure in that Wiki page would be nice though :P
[10:01] <Fujitsu> LaserJock: No.
[10:01] <Fujitsu> Le-Chuck_ITA, which version is it?
[10:01] <Le-Chuck_ITA> 0.3.3
[10:02] <LaserJock> ajmitch: because ...
[10:02] <ajmitch> LaserJock: some hysterical raisins?
[10:02] <LaserJock> heh
[10:02] <bddebian> ajmitch: ??
[10:02] <LaserJock> I think dch just failed him
[10:02] <LaserJock> bddebian: it's 1ubuntu1
[10:02] <bddebian> Oh yeah it is suppose to be 0ubuntu1
[10:02] <bddebian> I just haven't fixed it yet since no one has looked at it :-)
[10:02] <bddebian> Or at least commented on it anyway
[10:02] <LaserJock> I did notice that
[10:03] <LaserJock> but haven't had time to go through it properly
[10:03] <ajmitch> LaserJock: but you assumed that a deity would have a reason for it?
[10:03] <LaserJock> nah
[10:03] <Fujitsu> I note that xournal is now in Debian, and has 0.3.2-1. Mightn't it be advisable to base it off that instead?
[10:03] <Le-Chuck_ITA> omg
[10:03] <Le-Chuck_ITA> I didn't think about this
[10:03] <LaserJock> :-)
[10:04] <Le-Chuck_ITA> however I suspect that nothing changed at all
[10:04] <Le-Chuck_ITA> it might be quicker to check this
[10:04] <LaserJock> I'm too busy trying to add move MOTU Science to Main  for reviews :/
[10:04] <Fujitsu> It's likely to be packaged differently.
[10:04] <Le-Chuck_ITA> why?
[10:04] <Le-Chuck_ITA> it is a recent addition
[10:04] <Fujitsu> Because it seems unrelated to our packasge.
[10:04] <Fujitsu> *package
[10:04] <Fujitsu> (and it's always a good idea to minimise deviance from Debian)
[10:05] <Le-Chuck_ITA> ok will reupload
[10:05] <Le-Chuck_ITA> nah
[10:05] <Le-Chuck_ITA> tomorrow is new upstream release freeze right?
[10:05] <Le-Chuck_ITA> is this a strict deadline?
[10:05] <Fujitsu> Unless it fixes bugs and not much else, yes.
[10:06] <LaserJock> man, safari needs to allow for multiple rows of tabs or something
[10:06] <Fujitsu> LaserJock: No, Safari needs to die.
[10:06] <LaserJock> heh
[10:07] <LaserJock> I've tired 5+ browsers on my mac
[10:07] <LaserJock> none of them are all that great
[10:07] <Fujitsu> Why Safari? Because it's the most Aquaish?
[10:07] <fredl> there, Wiki updated :)
[10:07] <LaserJock> most integrated
[10:08] <LaserJock> and it's fast
[10:08] <LaserJock> fredl: thanks
[10:08] <fredl> ur welcome :)
[10:08] <fredl> is the order where I place it important?
[10:08] <LaserJock> it's supposed to be alphabetical I think
[10:09] <LaserJock> man, do I have a junior job for MOTU Hopefuls for after FF
[10:10] <LaserJock> we have to email people?
[10:10] <LaserJock> :-)
[10:10] <ajmitch> well, the list :)
[10:10] <rexbron> LaserJock: Would you have time to review a package?
[10:10] <LaserJock> I don't even know when it is
[10:10] <ajmitch> so that people know what to do when the Freeze Hits
[10:11] <fredl> ehr... well then I might have to re-edit it :P
[10:11] <LaserJock> I'm not sure I even know
[10:12] <LaserJock> other then they have to start doing UVFe requests
[10:12] <Fujitsu> Is there a set time? End of the 8th UTC?
[10:12] <ajmitch> bugs assigned to motu-uvf, 2 ACKs needed, etc
[10:13] <ajmitch> Fujitsu: general freeze time is when the devel meeting starts
[10:13] <LaserJock> Fujitsu: there never seems to be a set time for Freezes
[10:13] <ajmitch> LaserJock: YAY!
[10:13] <LaserJock> we had the one freeze that started when dholbach went to bed
[10:13] <Fujitsu> ajmitch: Indeed, I failed to notice that this coincided with a devel meeting. That does make sense though.
[10:13] <Fujitsu> LaserJock: Heheh, I remember that.
[10:14] <LaserJock> I think we had one where it froze when mdz said "I've had enough"
[10:14] <LaserJock> but lately they have been doing it by devel meetings
[10:14] <ajmitch> or the freeze where the publisher & buildds ran for the last time before release
[10:14] <Fujitsu> Hahahhaha:
[10:14] <Fujitsu> `Welcome to the Launchpad private beta. Please do not post screenshots publicly. Bug reports and feedback welcome.'
[10:14] <Fujitsu> I presume that's after the blog post last night.
[10:14] <ajmitch> haha
[10:14] <LaserJock> I wondered
[10:14] <ajmitch> nice
[10:14] <ajmitch> yeah
[10:15] <phanatic> Fujitsu: it was also revealed by Joey Stanford last week
[10:15] <ajmitch> phanatic: oh?
[10:15] <phanatic> ajmitch: in his Launchpad presentation he blogged about
[10:15] <ajmitch> naughty people, leaking s3kr3t c0d35
[10:15] <LaserJock> og's post is still up too
[10:15] <LaserJock> on planet anyway
[10:16] <phanatic> LaserJock: yup, no way back anymore :)
[10:16] <ajmitch> hi gpocentek 
[10:16] <LaserJock> what is there to blog about?
[10:16] <ajmitch> shiny
[10:16] <Fujitsu> LaserJock, it'll vanish from planet within a couple of hours if it does so from his blog.
[10:17] <Fujitsu> Shiny/blinding, yes.
[10:17] <LaserJock> "The new LP is shiny"
[10:17] <LaserJock> that's not much of a blog post
[10:17] <LaserJock> I wish we could test speed with it though
[10:17] <LaserJock> like compare to what is there now
[10:17] <Fujitsu> That would be nice...
[10:17] <Fujitsu> It's apparently running on comparable hardware now (or was going to be after the last dev meeting)
[10:17] <LaserJock> because I wonder how much the bling is going to affect performance
[10:18] <ajmitch> LaserJock: why should it?
[10:18] <enyc> ;-)
[10:18] <ajmitch> enyc: you're probably right
[10:18] <enyc> so they cant go test my bugreports lol
[10:18] <enyc> how silly
[10:18] <LaserJock> ajmitch: cause it seems slower to me, I think
[10:19] <Fujitsu> LaserJock: Before the last dev meeting, it was sharing a server with... something else, can't remember what.
[10:19] <LaserJock> k
[10:19] <Le-Chuck_ITA> Fujitsu: the only thing I had to do in the new debian source is dch -i :)
[10:20] <Le-Chuck_ITA> and change a dependency from xpdf-reader to poppler-utils
[10:20] <Le-Chuck_ITA> I uploaded the new package
[10:20] <Fujitsu> And you might want to put the .desktop in as well.
[10:20] <Fujitsu> Ah.
[10:20] <Le-Chuck_ITA> the .desktop er isn't that already there...
[10:20] <Le-Chuck_ITA> no
[10:20] <Le-Chuck_ITA> I am a mess maker :) if you have an english word for that
[10:20] <Fujitsu> The .desktop was in the Ubuntu one, but isn't in Debian.
[10:21] <LaserJock> Fujitsu: does beta use the same database? like if I change things in beta they'll show up in the "old" LP
[10:21] <Le-Chuck_ITA> and that was the main reason I wanted xournal in ubuntu some month ago
[10:21] <Fujitsu> LaserJock, yep. I don't use normal LP any more.
[10:21] <LaserJock> only demo uses a different one?
[10:21] <Fujitsu> And staging.
[10:22] <LaserJock> ah
[10:22] <Fujitsu> It was originally not going to be on the production DB, then I brought up the fact that few people would use it if they couldn't use it for proper work.
[10:22] <LaserJock> mhm
[10:23] <ajmitch> mm, I should probably switch to using beta fulltime
[10:23] <Fujitsu> ajmitch, that's a good idea.
[10:23] <Adri2000> is there any requirement to join launchpad-beta-testers?
[10:23] <ajmitch> as long as I can get to things with similar urls
[10:23] <ajmitch> Adri2000: your soul
[10:23] <Fujitsu> ajmitch, just stick beta. on the front.
[10:23] <Le-Chuck_ITA> Fujitsu: xournal.sharedmimeinfo, xournal.desktop and xournal.install
[10:24] <Le-Chuck_ITA> should I just copy them to debian?
[10:24] <Fujitsu> (well, behind the application domain, if there is one)
[10:24] <Fujitsu> Le-Chuck_ITA, yep, and you'll need to add a section to the install rule to put them in the right place.
[10:24] <ajmitch> of course there are still a few things missing in the beta ui
[10:24] <Fujitsu> Like?
[10:25] <ajmitch> & there are things just broken :)
[10:25] <ajmitch> eg your personal page, "working on..."
[10:25] <ajmitch> which should show in progress bugs
[10:25] <Fujitsu> Heheh.
[10:25] <Fujitsu> Yeah.
[10:26] <Fujitsu> Isn't the `working on' bit only new to production?
[10:26] <ajmitch> and fooix the wonder toaster?
[10:26] <ajmitch> no
[10:26] <ajmitch> well
[10:26] <ajmitch> it's new
[10:26] <ajmitch> i don't recall when I saw it
[10:26] <ajmitch> but it was only recently on lp
[10:26] <Le-Chuck_ITA> binary/xournal::
[10:26] <Le-Chuck_ITA>         dh_installmime
[10:26] <Le-Chuck_ITA> binary/xournal::
[10:26] <Le-Chuck_ITA>         dh_installmime
[10:27] <Le-Chuck_ITA> oh sorry
[10:27] <Le-Chuck_ITA> does dh_installmime at the end of the install rule suffice?
[10:27] <Le-Chuck_ITA> and what about postrm
[10:27] <ajmitch> so many confusing things in the beta UI
[10:29] <Le-Chuck_ITA> Fujitsu: I am not sure I am the right person to do this upload
[10:29] <Le-Chuck_ITA> the rules files are different in 0.3.1
[10:29] <Le-Chuck_ITA> ubuntu and 0.3.2 debian
[10:29] <Fujitsu> The Debian version doesn't use CDBS.
[10:29] <Fujitsu> I'll have a look and see what needs to be taken across from the Ubuntu package.
[10:30] <Fujitsu> Ah, it's like that.
[10:30] <Le-Chuck_ITA> in the ubuntu package there are the post-install and pre-rm scripts
[10:30] <Le-Chuck_ITA> I suppose cdbs made those
[10:32] <Q-FUNK> guys, i need advice on how to proceed:  I need to update a more recent version of a package directly into ubuntu, while debian will get it only later once etch is out.
[10:32] <Le-Chuck_ITA> in any case I tried, I have to go now - it's really too late. I declare myself available to work more on this (maybe later, and for sure...) tomorrow morning
[10:32] <Le-Chuck_ITA> Fujitsu: I really would like to understand how to end such a process
[10:32] <Le-Chuck_ITA> for learning purposes :)
[10:34] <Fujitsu> Basically, you need to add dh_installmime (or whatever it is) and dh_desktop to the `binary-arch: build install' rule.
[10:34] <LaserJock> so are the teams going to get big emblems? that big orange box is annoying me
[10:35] <Le-Chuck_ITA> Fujitsu: will you try to get the new version in feisty in my place, or will I try to do this tomorrow, or will I give up?
[10:35] <Fujitsu> If you don't have time, I'll do it.
[10:36] <LaserJock> ajmitch: does https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6 look right
[10:36] <ajmitch> ooh, LaserJock took my delegation seriously? :)
[10:37] <Le-Chuck_ITA> not tonight and don't know if tomorrow morning is too late 
[10:37] <Fujitsu> It may be too late.
[10:37] <Le-Chuck_ITA> ok so I ask you if it is simple to do that in my place 
[10:37] <Le-Chuck_ITA> and in that case to leave a comment on my upload or send me a mail
[10:37] <Le-Chuck_ITA> I will see how things are tomorrow :)
[10:38] <Le-Chuck_ITA> and act consequently 
[10:38] <LaserJock> ajmitch: yes I did
[10:39] <Fujitsu> Yep, I shall do so.
[10:39] <Le-Chuck_ITA> thank you very much
[10:39] <ajmitch> LaserJock: borrowed from the old Processes/UVF page?
[10:39] <Fujitsu> No problem, and thanks for trying to update it :)
[10:39] <Le-Chuck_ITA> goodbye to everybody and thanks, I learned a lot
[10:40] <Fujitsu> Thanks for the help, we need it.
[10:40] <Le-Chuck_ITA> NP :P bye
[10:40] <ajmitch> LaserJock: looks ok, I think
[10:45] <LaserJock> ajmitch: ok, then shall I send the email?
[10:45] <ajmitch> LaserJock: may as well
[10:47] <LaserJock> I'm having a smashing email day ;-)
[10:47] <ajmitch> yay
[10:47] <LaserJock> at least until they all start bouncing or something
[10:47] <ajmitch> heh
[10:47] <ajmitch> sent about 50 today?
[10:48] <LaserJock> me? heavens no
[10:48] <LaserJock> maybe 3
[10:49] <LaserJock> should I use "Imminent" in the subject so it sounds all official? ;-)
[10:50] <ajmitch> certainly
[10:50] <ajmitch> like 'Impending Doom'
[10:51] <LaserJock> heh, I like that better
[10:51] <ajmitch> lucky slomo, he'll get flooded with bugs
[10:51] <LaserJock> I should add a nice soundtrack to my email
[10:51] <ajmitch> oh the beta team display sucks
[10:52] <Fujitsu> LaserJock, with a lot of nice jarring chords.
[10:52] <ajmitch> doesn't display team members on the overview page
[10:52] <slomo> ajmitch: i'm already flooded with bugs... this few more bugs don't hurt i hope ;)
[10:52] <LaserJock> I like the "idea" but I want to see the members
[10:52] <ajmitch> slomo: another 20 a day won't hurt
[10:52] <ajmitch> so it's dholbach, siretart & slomo to the rescue
[10:54] <Fujitsu> slomo: Can you please check your two branches on the mplayer product, and mark them Merge or Abandoned as appropriate?
[10:54] <Fujitsu> *Merged
[10:56] <slomo> ajmitch: not you again as number 4?
[10:57] <slomo> Fujitsu: sure... nice that you want to care for mplayer now, i'm not interested in it anymore ;)
[10:57] <Fujitsu> I use it a lot, so I may as well.
[10:57] <ajmitch> slomo: maybe
[11:00] <Fujitsu> slomo: Much better :P)
[11:00] <Fujitsu> *:)
[11:00] <bddebian> ajmitch: So, did you review bibus? :-)
[11:01] <LaserJock> ajmitch: just to be clear, new Debian revisions are OK during UVF right?
[11:01] <ajmitch> LaserJock: of course
[11:01] <ajmitch> bddebian: heh, no
[11:01] <bddebian> :'-(
[11:01] <ajmitch> bddebian: that would require effort
[11:01] <LaserJock> ajmitch: well you know, I always send out an email like this and half of what I say turns out to be wrong ;-)
[11:01] <Adri2000> yay
[11:02] <LaserJock> bddebian: I'll do it soon
[11:02] <ajmitch> LaserJock: that's fine, as long as the half that's right is the important half
[11:03] <LaserJock> :-)
[11:03] <slomo> Fujitsu: sure... nice that you want to care for mplayer now, i'm not interested in it anymore ;)
[11:03] <slomo> Fujitsu: done
[11:03] <Fujitsu> Thanks.
[11:08] <TheMuso> Wooo. Planet is broken.
[11:08] <LaserJock> does motu-uvf really want UVFes assigned to them?
[11:08] <slomo> LaserJock: yes... at least last time we handled it that way
[11:09] <LaserJock> k, just making sure
[11:10] <ajmitch> it makes a difference with the mail
[11:11] <LaserJock> ah, interesting. hadn't thought of that
[11:12] <LaserJock> hmm, the FreezeExceptionProcess page just says: "Once one of the  team members marks the bug as Confirmed you can proceed with uploading."
[11:13] <LaserJock> so does that mean 2 have to ack and the 2nd will mark it Confirmed?
[11:13] <ajmitch> yes, usual process
[11:13] <LaserJock> or is it just 1 ack
[11:13] <ajmitch> 2 acks, 2nd marks as confirmed
[11:13] <ajmitch> it allows for the team to shuffle their process & others don't have to care
[11:14] <ajmitch> eg if there were 500 bugs submitted, it may be better to do 1 ack
[11:16] <LaserJock> it's also a bit more confusing in a sense as people don't know what to expect
[11:16] <LaserJock> but I think the flexibilty argument is good
[11:17] <LaserJock> ajmitch: argg, I lost the url to your bug list
[11:18] <ajmitch> that's ok
[11:18] <ajmitch> it's in the topic, you know :)
[11:18] <LaserJock> bah
[11:21] <LaserJock> uggg
[11:21] <LaserJock> I hate clouds
[11:21] <ajmitch> you know you want it
[11:21] <LaserJock> I just want what *I* want darn it
[11:22] <Lutin> revu admin around ? seems that  videomanager_0.5-0ubuntu1.dsc is stuck somewhere, could you nuke it ?
[11:22] <LaserJock> not what every dope on the web wants
[11:22] <ajmitch> Lutin: done
[11:22] <Lutin> ajmitch: thanks
[11:23] <LaserJock> ajmitch: should I send this to ubuntu-devel-announce too?
[11:23] <ajmitch> I'd wait & find out if mdz is going to announce something for main
[11:23] <ajmitch> maybe
[11:24] <LaserJock> not "just", you're a core-dev too
[11:24] <Fujitsu> A MOTU with main upload privileges, I think :P
[11:24] <ajmitch> small details
[11:24] <LaserJock> I'll just send it to ubuntu-motu for now I think
[11:24] <LaserJock> it's probably too much hand-holding for core-devs ;-)
[11:26] <LaserJock> sent
[11:26] <LaserJock> I really wish the "tell my why in the world I'm getting bug mails" bug would get fixed
[11:31] <ScottK> I have two new upstream releases for REVU.  They should be simple enough (I hope) as they have no packaging changes from the previous releases: http://revu.tauware.de/details.py?upid=4293 and http://revu.tauware.de/details.py?upid=4294 - I'd appreciate a look when one of you MOTUs has a moment.
[11:34] <TheMuso> rexbron: Any reason why the soma client binary is in the soma-server package?
[11:35] <bddebian> haha 
[11:36] <ScottK> bddebian: Hi there.  What's funny, me showing up with two updates just after the UVF warning goes out?
[11:37] <bddebian> ScottK: No, poor rexbron getting crap from TheMuso after sistpoty basically had him re-create the whole package :-)
[11:37] <ScottK> Ah.
[11:38] <bddebian> Anyway, gotta run, I'll catch you all in a few
[11:43] <_ion> Could some MOTU please review <http://revu.tauware.de/details.py?upid=4133>? That's not packaged by me, but i'd *really* like to have the package in Feisty. It contains the compiz 'state' plugin, which allows you to define rules such as "open all firefox windows to the desktop 1", "view mplayer windows brighter than other windows".
[11:44] <rexbron> TheMuso: the client is just a commandline prog to interface with the daemon
[11:44] <rexbron> the daemon is unuseable really without it
[11:44] <TheMuso> Ok then.
[11:44] <lifeless> 'someone' should package http://reprap.org/bin/view/Main/RepRapLinuxSoftware
[11:45] <lifeless> I'll probably get to it next weekend
[11:47] <rexbron> TheMuso: give me a heads up of you advocate it
[11:48] <TheMuso> rexbron: 
[11:48] <TheMuso> rexbron: Have a look on the revu page.
[11:48] <rexbron> :)
[11:49] <rexbron> ok now to find someone else to review it
[11:59] <mohammad> I had uploaded a package to http://revu.tauware.de/ a few months ago, Now I have fixed some bugs and trying to upload the new package
[11:59] <rexbron> hey anyone up for a review? upid 4284
[11:59] <mohammad> but I couldnt I recieve the following error in email
[12:00] <mohammad> Rejected:Signer has no upload rights at all to this distribution.
[12:00] <mohammad> would you please give me some hints what I should do?
[12:01] <ajmitch> mohammad: make sure you're in the ubuntu-universe-contributors group on launchpad, then ask for the keyring to be resynced here
[12:01] <ajmitch> bacl later
[12:01] <ajmitch> s/bacl/back/
[12:02] <Adri2000> mohammad: are you sure to use dput *ubuntu* .changes?
[12:04] <mohammad> ajmitch: I am sure in the ubuntu-universe-contributors group on launchpad
[12:04] <Adri2000> mohammad: err, I'm tired, I meant are you sure to use dput *revu* .changes?
[12:04] <mohammad> Adri2000: yes I use dput. even I invoke it with -f command
[12:05] <Adri2000> if you upload to ubuntu that won't work, you have to specify that you want to upload to revu with 'dput revu .changes'
[12:05] <mohammad> Adri2000: dput -f zekr_0.5.0b2-0ubuntu1_source.changes 
[12:06] <Adri2000> try dput -f revu zekr_0.5.0b2-0ubuntu1_source.changes
[12:07] <mohammad> Adri2000: I did it, now I should wait 5 minutes to be able to see the result :)
[12:10] <racarr> Is beryl not going in universe for feisty?
[12:11] <LaserJock> not if people don't upload it 
[12:11] <LaserJock> and if it doesn't get approved
[12:11] <LaserJock> but otherwise yeah :-)
[12:13] <racarr> Well, err, it hasn't happened so far and feature freeze is soon :/
[12:13] <mohammad> Adri2000: thank you for your help my package was updated successfully. :)
[12:13] <Adri2000> :)
[12:14] <LaserJock> racarr: exactly