[12:17] <Kyral> I think I need to get more work done for this...
[12:17] <azeem> hey Kyral
[12:17] <Kyral> hey
[12:18] <Kyral> Man the Debian guys ripped me a new one on the RFS lol
[12:19] <Kyral> I think I should make a new revision to EasyChem
[12:20] <Kyral> azeem: Wanna sponsor it?
[12:21] <ogra> 8-O
[12:22] <womble> Kyral: You mean they told you what was wrong with it and asked you to fix it before upload?
[12:23] <Kyral> I dunno if it was personal opinion or like fix it
[12:23] <Kyral> Most of it was all about using dh_install instead of install -d
[12:29] <Kyral> Yah the emails were like "You could have saved some work if you did foo instead of bar"
[12:30] <Kyral> http://lists.debian.org/debian-mentors/2006/01/msg00136.html
[12:31] <womble> Those criminals, telling you how to package better.  <grin>
[12:32] <Kyral> yah yah
[12:32] <Kyral> I'm a beginner sheesh :P
[12:33] <\sh> Kyral: be gratefull to get those opinions
[12:33] <azeem> Kyral: did you get feedback from other people besides Florian Ernst?
[12:33] <Kyral> \sh: I know :P
[12:33] <Kyral> azeem: yah
[12:33] <azeem> and the description argument by jdthood
[12:34] <Kyral> description argument?
[12:36] <azeem> in reply to the ITP
[12:36] <Kyral> I didn't recieve that, I don't think
[12:37] <azeem> http://lists.debian.org/debian-devel/2006/01/msg00815.html
[12:37] <azeem> ah, it was Frank Kuester not jdthood
[12:37] <Kyral> Actually there is a long one
[12:37] <Kyral> I was just too tired to type it in lol
[12:38] <Kyral> yah yah
[12:38] <azeem> ;)
[12:42] <Kyral> apt-cache show easychem if you really wanna see it
[12:45] <Kyral> This is what I get for being lazy
[12:58] <azeem> Kyral: did you consider some of the suggestions you got on -mentors?
[12:58] <Kyral> about install and stuff?
[12:58] <azeem> Kyral: I think the prefix thing might be reasonable to do, but if you want to patch the Makefile to behave properly, that sounds fine
[12:58] <azeem> yeah
[12:59] <Kyral> Makefile is already patched in Universe :P
[12:59] <azeem> yeah, I meant fine continueing to do so
[01:00] <Kyral> ah
[01:00] <azeem> Kyral: if you make a new revision, I can upload it to Debian, sure
[01:01] <Kyral> change prefix?
[01:01] <azeem> 00:13 < Kyral> I think I should make a new revision to EasyChem
[01:01] <Kyral> Actually the next revision I wanted to make I would use CDBS ;P
[01:02] <Kyral> I mean, IMO its fine right now
[01:02] <Kyral> If upstream releases a new version, then I would make the changes along with the new upstream ver
[01:09] <Kyral> "Ubuntu Padder"?
[01:11] <azeem> Kyral: ok, just tell me when I should upload something.  However, during daytime (until around 8PM CET), I am usually at the Uni and unable to upload things, just fyi
[01:11] <Kyral> http://netswitch.tuxfamily.org/en/downloads.html
[01:11] <Kyral> well, the package in Universe builds fine in Sid...
[01:11] <Kyral> Just a matter of changing the revision from -0ubuntu1 to -1
[01:12] <azeem> ok
[01:13] <azeem> btw, Daniel Leidert packaged easychem for Debian/Ubuntu as well
[01:13] <Kyral> Oh he did?
[01:13] <Kyral> First I've heard lol
[01:13] <azeem> http://debian.wgdd.de/debian/dists/unstable/main/source/science/ , if you want to have a look
[01:14] <Kyral> when did this happen?
[01:15] <Kyral> okay I see it
[01:15] <azeem> yesterday
[01:15] <azeem> :)
[01:15] <azeem> * Initial release from Ubuntu package.
[01:15] <Kyral> yah
[01:15] <azeem> ok, so no work duplicated, yay
[01:15] <Kyral> well at least gimme credit for the XPM :P
[01:17] <azeem> so, should I make this look like an NMU, or can you provide a -1 package I should build/upload?
[01:17] <Kyral> if he already did it then its null ;P
[01:17] <azeem> well, he's no DD either, it's his personal site
[01:18] <Kyral> Now I'm confused
[01:18] <azeem> I was just pointing it out for informational purposes :)
[01:18] <Kyral> so he just made it for his own use?
[01:19] <azeem> well, he probably has some users, there are some other packages there already
[01:19] <azeem> I'm trying to get them into Debian, but I've been slacking
[01:19] <Kyral> yah I have the package in my little webspace
[01:19] <Kyral> http://people.clarkson.edu/~petermcv/debian/
[01:19] <Kyral> I should upload the orig.tar.gz shouldn't I
[01:20] <azeem> I have that already
[01:20] <Kyral> yah thats the revision I made switching it to Sid
[01:22] <Kyral> that one okay?
[01:29] <azeem> yeah, works fine
[01:29] <Kyral> kk
[01:30] <azeem> Kyral: hrm, you might want to close the ITP bug in the changelog
[01:30] <azeem> but you can also do it manually afterwards if you want
[01:30] <Kyral> That was made before the ITP bug lol
[01:30] <azeem> heh, I thought so
[01:30] <Kyral> and I'd have to redownload that pack...I kinda nuked my /workspace dir...
[01:30] <azeem> ok, no worry then, I'll upload it?
[01:31] <Kyral> eh I can close the bug
[01:31] <Kyral> just gotta remember how to apply the diff.gz to the orig
[01:31] <azeem> dpkg-source -x foo.dsc
[01:31] <Kyral> ah
[01:31] <Kyral> ty
[01:35] <Kyral> It would be "Closes ITP <num>"?
[01:36] <Kyral> Debian 347849
[01:36] <Ubugtu> Debian bug 347849: "easychem -- Draw high-quality molecules and chemical 2D formulas" Package: ITP, Severity: wishlist, Maintainer: wnpp@debian.org</a http://bugs.debian.org/347849
[01:36] <Kyral> or that...
[01:37] <azeem> Closes: #347849
[01:38] <Kyral> want me to just send up the diff.gz?
[01:38] <lucas> crimsun: you are around ?
[01:38] <azeem> Kyral: .diff.gz and .dsc is enough, yes
[01:39] <Kyral> okay
[01:39] <Kyral> gimem a sec
[01:40] <Kyral> okay it should be where the others are
[01:43] <azeem> Kyral: oh, I'd like to spare you from Debian flames :)  If possible, just add the Closes: #347849 to the -1 changelog entry, no need for -2
[01:43] <azeem> there are some people around who do nothing but check new uploads for bug-closing errors :)
[01:44] <azeem> "* Packaged for Debian Unstable (Closes: #347849)" should be perfect as changelog
[01:44] <azeem> sorry for the trouble
[01:46] <Kyral> done and uploaded
[01:47] <azeem> perfect
[01:51] <azeem> Kyral: uploaded
[01:51] <Kyral> coool.....
[01:51] <Kyral> too bad packages.debian.org is down...
[01:51] <azeem> packages.debian.net/easychem
[01:51] <azeem> well, but it won't be there until the day after tomorrow I guess
[01:52] <azeem> Debian only puts new .debs into the archive once a day, in about 19 hours
[01:52] <Kyral> So why doesn't the Debian Package Search use that?
[01:52] <azeem> I think there is work underway to reinstate packages.debian.org
[01:52] <Kyral> ah
[01:52] <azeem> btw, packages.debian.org/unstable/science/easychem will work, as well
[01:53] <azeem> just not the searching stuff
[01:53] <Kyral> yah because I found a thing for Firefox that adds the Debian Package Search to the Searchbar :D
[01:54] <lifeless> google searches just fine ;0
[01:54] <Kyral> yah, but its nice to have it right on the searchbar ;P
[01:54] <azeem> ok, good night y'all
[01:54] <Kyral> ty azeem
[01:57] <Kyral> Is the MIT License valid for packages?
[01:59] <lifeless> what do you mean ?
[01:59] <Kyral> http://www.gnomefiles.org/app.php?soft_id=1253
[02:00] <lifeless> sorry, that does not tell me what you mean
[02:00] <Kyral> I mean is it alright to package something that uses that License
[02:02] <lifeless> yes
[02:02] <Kyral> okay
[02:03] <lifeless> MIT licence is open source
[02:04] <Kyral> hmm
[02:04] <Kyral> I don't think I saw an ITP for that
[02:05] <azeem> it probably got kicked out of every distro, considering it is GTK-1.2
[02:06] <Kyral> lol
[02:06] <Kyral> the Screenshot doesn't really look it
[02:06] <Kyral> http://gtkedit1.sourceforge.net/#screenshot
[02:07] <Kyral> and it does what he targetted it for...
[02:08] <Kyral> More software in the Repos is good no?
[02:14] <Kyral> well, got the emails from the Debian Archive
[02:29] <Susana> hello
[02:30] <Susana> clisp has unmet dependencies in dapper
[02:30] <Susana> is this normal because it is under construction, or should i report it?
[02:31] <lucas> you should report it
[02:31] <Susana> ok
[02:31] <Susana> thanks
[02:31] <Susana> :)
[02:56] <Kyral> damnit
[02:56] <Kyral> what package do I need if a cpp file has #include "Python.h"
[02:56] <Lathiat> python-dev ?
[02:57] <Kyral> ain't wokring
[02:57] <Lathiat> capital P is sus
[02:57] <Lathiat> and " "
[02:57] <Lathiat> its probably a custom header ?
[02:57] <Kyral> which isn't included
[02:57] <Kyral> it has "PyObject"
[02:58] <Kyral> I'm thinking python2.4-cxx-dev might work
[03:02] <Kyral> screw this I'm emailing the dev with the diff,gz :P
[03:26] <lamont-away> and the cool part is that debian actually has the right build-deps. :-)
[03:26] <Kyral> lol
[03:26] <Kyral> The cool part is that I got my first package into Debian :P
[03:29] <lamont-away> meanwhile?
[03:29] <mr-russ> Kyral: what package?
[03:30] <Kyral> EasyChem
[03:30] <Kyral> Azeem uploaded for me
[03:34] <mr-russ> Kyral: cool, now you can update your website to say it's in debian :)
[03:34] <Kyral> mr-russ: hehe
[03:35] <Kyral> I'll wait until the thing is actually added by the script thingy
[03:35] <mr-russ> I know very little about how debian actually works.
[03:36] <mr-russ> I have a package that was forked by me and a different fork was done by a debian user.
[03:36] <mr-russ> I'm now trying to merge the forks back together, but it's hard work contacting the dev and making things happen.
[04:16] <Kyral> Hey LJ
[04:25] <LaserJock> hi Kyral, just read the backlog, good going getting EasyChem into Debian
[04:26] <Kyral> yup
[04:26] <Kyral> now I'm going BOFH on someone
[04:26] <LaserJock> ?
[04:26] <Kyral> on the Undernet
[04:27] <LaserJock> well, I asked somebody how their ITP was going and they want me to take it over
[04:28] <Kyral> Damnit
[04:28] <Kyral> I cannot go into full BOFH mode
[04:31] <marcin> hello MOTU
[04:31] <Kyral> hello
[04:31] <marcin> got a question
[04:32] <marcin> I'm emacs user and would like to make some packages with emacs libraries
[04:32] <marcin> but unfortunately there is already a lot of emacs related packages in debian/ubuntu
[04:33] <Kyral> emacs++
[04:33] <marcin> unfortunately they usually aren't up to date
[04:33] <Kyral> in either Sid or Dapper?
[04:33] <marcin> and sometimes they are broken or they don't work like they should
[04:34] <marcin> well I cannot say nothing about dapper
[04:34] <marcin> because dapper doesn't want to boot on my second machine since last apt-get upgrade
[04:35] <marcin> anyway in my humble opinion debian packages are propably "best on market"
[04:35] <marcin> but they sucks...
[04:35] <Kyral> what packages?
[04:35] <marcin> and their naming convention sucks pretty much
[04:36] <marcin> Kyral: I really don't want to report bugs here... lot's of them
[04:36] <Kyral> no I meant packages ;P
[04:37] <marcin> hmm afair jde is broken
[04:37] <marcin> not sure about dapper but propably is not installable
[04:37] <marcin> (if you really want examples)
[04:37] <Kyral> ICK Java
[04:38] <marcin> lua-mode in debian is broken will not byte-compile
[04:39] <marcin> anyway it's not bugzilla here
[04:39] <marcin> I just would like to ask about ubuntu
[04:40] <marcin> is ubuntu going to keep all these debian packages?
[04:40] <marcin> or are there any plans to create ubuntu-specific emacs packages?
[04:41] <marcin> because currently emacs related packages in ubuntu are 100% "compatible" with debian packages
[04:41] <marcin> and another thing: is there any naming convention for emacs packages?
[04:42] <LaserJock> I would think there would only be Ubuntu specific packages if they are needed, usually it works better for us is to get the fix in Debian and sync
[04:42] <marcin> because in my opinion currently it's pretty hard to find emacs packages because they all got weird names
[04:43] <marcin> and it's hard to sort/filter emacs packages in ubuntu and debian too
[04:46] <LaserJock> marcin: if a package doesn't work for you try searching Malone and if you can't find an already opened bug about your problem file a new one
[04:47] <LaserJock> marcin: the naming comes from Debian and I don't see any conventions right off hand but you might be able to ask debian-devel or something
[04:47] <marcin> LaserJock: well debian-devel... nnno I don't think so ;)
[04:48] <marcin> LaserJock: and about bugs... ok I'll try to file some bug reports
[04:48] <marcin> LaserJock: but in fact I went other way - I just already created about 60 emacs related packages
[04:49] <marcin> LaserJock: with different and more logical naming convention, with cdbs and lot of other improvements
[04:49] <marcin> LaserJock: and I got my own apt repository on localhost with these packages
[04:50] <LaserJock> well, if you want to get your packages into Ubuntu you should look at https://wiki.ubuntu.com/REVU and get them on REVU
[04:50] <marcin> LaserJock: and they work really great but they got different names, different rules etc.
[04:50] <LaserJock> I really don't know about the naming conventions though
[04:50] <marcin> LaserJock: than these from debian
[04:51] <marcin> LaserJock: well my naming convention is pretty simple
[04:51] <marcin> LaserJock: I just use 'emacs' as prefix for all my packages
[04:51] <marcin> LaserJock: so it's easy to find them in synaptic etc.
[04:51] <marcin> LaserJock: just like python or perl packages
[04:51] <LaserJock> so did you just take the debian packages and rename/fix them? or are they original?
[04:52] <marcin> they use debian emacs policy
[04:52] <marcin> with all these emacsen install/remove etc.
[04:52] <marcin> emacsen-common stuff
[04:53] <marcin> but their 'rules' are original
[04:53] <marcin> because I started to use 'cdbs' in my packages
[04:54] <LaserJock> marcin: hmm, have you talked to the Debian maintainers at all?
[04:55] <marcin> I've been trying on #debian-devel or something... few months ago
[04:56] <marcin> and.. I don't want to start this again
[04:56] <LaserJock> well, I can imagine the response :-)
[04:56] <marcin> so, you propably understand :)
[04:57] <marcin> anyway..
[04:57] <LaserJock> yeah, but maybe you could file a BTS bug or something and talk to the actual maintainers if you feel a change is really needed
[04:58] <marcin> well but you know... I don't want to talk to Debian maintainers...
[04:58] <marcin> and this is why I ask here - about Ubuntu plans etc.
[04:59] <LaserJock> right, but I don't think messing with that many packages in Ubuntu is the solution
[04:59] <marcin> right but Ubuntu is known as something 'revolutionary' and innovative
[05:00] <Kyral> eh
[05:00] <marcin> so I just wonder if this is only related to gnome or maybe emacs packages could change too
[05:00] <Kyral> I sometimes call it Debian For Beginners
[05:00] <LaserJock> I mean the basic idea is that we really don't have the manpower to create a lot of changes, we have to maintain every change we make and for Universe there are only ~ 35 MOTU for >1500 packages
[05:01] <LaserJock> Kyral: I don't see it that way at all but whatever ;-)
[05:01] <marcin> LaserJock: well I agree but there are two things
[05:02] <marcin> 1. emacs packages doesn;t change very often
[05:02] <marcin> (in fact there is a lot of packages that are almost unmaintained)
[05:03] <Kyral> hey Amaranth
[05:03] <marcin> 2. if we'll use cdbs in these packages they will be clean and simple and easy to maintain
[05:03] <marcin> and well it's point 3 - I already maintain about 60 packages for myself and I propably could do this for ubuntu
[05:04] <LaserJock> marcin: I can see 1 but I don't know that 2 is necissarily true and with 3 you are welcome to submit your packages to REVU
[05:05] <marcin> LaserJock: well are you sure that I can put them in REVU ?
[05:05] <LaserJock> sure, they may not get in but you can at least get them reviewed
[05:05] <marcin> LaserJock: they will conflict with almost evry debian package...
[05:06] <marcin> LaserJock: (because they got different names...)
[05:06] <LaserJock> that is why I am saying that you are better off probably getting the changes you want in Debian rather than Ubuntu
[05:07] <marcin> LaserJock: well but it's _really_ hard to talk with them...
[05:07] <LaserJock> I can understand that
[05:07] <marcin> anyway it's 5 am and I really should go to sleep for a while
[05:08] <marcin> so, propably tomorrow I'll just try to upload some packages to REVU
[05:08] <LaserJock> marcin: I am really glad you care about these packages and that you are taking time to try to fix them
[05:08] <marcin> I'll select packages that are not available in ubuntu now
[05:08] <marcin> and we will see
[05:08] <LaserJock> marcin: I just don't know if Ubuntu is able to make that dramatic of a change right now
[05:09] <marcin> anyway.. can I upload breezy packages to REVU?
[05:09] <Kyral> no...
[05:09] <Kyral> Dapper
[05:09] <marcin> (emacs packages are in fact 'platform' 'compiler' etc independent... )
[05:09] <marcin> welll then I need to wait for flight 3
[05:10] <marcin> because currently my dapper is just broken
[05:10] <LaserJock> marcin: you can alway use a dapper pbuilder
[05:10] <marcin> I cannot boot... and got no idea why
[05:10] <marcin> hmmm
[05:11] <marcin> ok I'm too tired now
[05:11] <marcin> I'll be back tomorrow
[05:11] <marcin> thanks and night to all
[05:11] <LaserJock> good night marcin
[05:30] <LaserJock> hi ogra
[07:41] <dholbach> GOOD MORNING!
[07:43] <zakame> hi MOTUs :)
[08:34] <mr-russ> If two repositories have the same package, which one will be chosen?
[08:35] <mr-russ> of what is the smart way to apply custom changes to a package that you want distributed?
[08:35] <mr-russ> s/of/or
[09:02] <lucas> hi motus
[09:08] <siretart> morning!
[09:19] <mr-russ> hi
[09:26] <dholbach> hello mr-russ, siretart, lucas
[09:27] <lucas> dholbach: there are lots of merges/syncs waiting for review on malone
[09:27] <lucas> the problem is LP considers "fix commited" bugs as "fixed", so they are hidden from the default listing
[09:29] <lucas> https://launchpad.net/people/motureviewers/+assignedbugs?field.searchtext=&search=Search&orderby=datecreated&advanced=1&field.include_dupes.used=&field.statusexplanation=&field.status%3Alist=Unconfirmed&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status-empty-marker=1&field.severity-empty-marker=1&field.attachmenttype-empty-marker=1
[09:29] <lifeless> echannel jaldhar ? ;)
[09:29] <lucas> (35 results)
[09:29] <lifeless> bah
[09:29] <lifeless> I meant jamesh
[09:30] <lifeless> except tab complete is borking
[09:32] <lucas> lifeless: yeah, it should really do some mind-reading to know which nick you wanted to talk to ;)
[09:32] <lifeless> nah
[09:32] <lifeless> if I type james and hit tab
[09:32] <lifeless> it wont bring up jamesh in this channel
[09:33] <lucas> yeah, that's because jamesh is not here
[09:34] <lifeless> oh, irssi got confused
[09:34] <lifeless> it had jamesh in the scrollback
[09:34] <lifeless> until I paged up and down enough
[09:37] <dholbach> lucas: yeah, that occured to me too
[12:52] <slomo> shawarma: ping?
[01:10] <KriS83> Hi
[01:10] <Yagisan> KriS83: G'day
[01:11] <KriS83> I have a probably not to often asked question
[01:12] <KriS83> I am looking for a Howto of how to build a dummy deb which contains only a single file and after installing this file I want to run a postinst script
[01:12] <KriS83> Lets say this file is a single precompiled binary
[01:12] <KriS83> Any ideas for some good Howto?
[01:13] <marcin`> KriS83: maint-guide?
[01:13] <KriS83> marcin`, this explains on how to do all of this when wanting to compile during package creation
[01:14] <KriS83> Which I do not want to do
[01:14] <marcin`> KriS83: so.. just skip these parts
[01:14] <KriS83> I have a fnished file not having to be compiled anymore
[01:14] <marcin`> KriS83: and implement only postinst
[01:14] <marcin`> KriS83: you could use cdbs
[01:15] <marcin`> KriS83: and include only debhelper.mk
[01:15] <marcin`> KriS83: and then postinst/yourpackage
[01:15] <marcin`> KriS83: just copy this precompiled library and run your postints script
[01:15] <KriS83> right, I'll give that a try
[01:15] <marcin`> KriS83: take a look at cdbs documentation
[01:16] <KriS83> sure, thx
[01:17] <marcin`> KriS83: np, your 'rules' file propably could have just few lines
[01:17] <marcin`> KriS83: include /usr/share/cdbs/1/rules/debhelper.mk
[01:18] <marcin`> and then install/your package with copy (to put your precompiled lib where you need)
[01:18] <marcin`> and postinst/your_package.... that's all
[01:19] <KriS83> building a deb file is way more complicated than rpms :-/
[01:19] <StevenK> KriS83: Not really.
[01:20] <StevenK> KriS83: There is just a lot of tools to help.
[01:20] <KriS83> I think so :)
[01:20] <StevenK> Which means learning those tools.
[01:20] <marcin`> KriS83: well I also thought so, but in fact the only difference is
[01:20] <KriS83> well with a rpm I have one single file *.spec edit it to my need running rpmbuild finished :)
[01:21] <marcin`> KriS83: that rpm use shell script while deb uses makefile
[01:21] <marcin`> KriS83: use dh_make to generate files you need automagically
[01:21] <marcin`> KriS83: and then just edit them
[01:30] <siretart> StevenK: around?
[01:31] <siretart> StevenK: do you have an idea why linda is bugging me about not able to find a suitable .mo file?
[01:34] <StevenK> What's the error?
[01:35] <JRe> anyone else than me have trouble running Java SWT programs with dapper (eg. Azureus)
[01:36] <JRe> (seems to be coming of the way libgtk get compiled)
[01:36] <StevenK> Ripping - title #1: 13130000.00%, 135 fps, elapsed 00:01:50, ETA 00:-1:04
[01:37] <Yagisan> StevenK: dvd::rip is cool, but how are you getting 135fps ????
[01:38] <StevenK> Yagisan: Um, I have a dual Athlon? :-)
[01:38] <StevenK> Yagisan: What do you usually get?
[01:39] <Yagisan> StevenK: I have a dvd::rip cluster here, with amd64 (15-25fps) + duron (8-15fps)+ several p2s (1-5fps each)
[01:40] <Yagisan> StevenK: you are much quicker
[01:40] <StevenK> Both processors got smashed.
[01:40] <StevenK> I have no idea, actually.
[01:45] <StevenK> Yagisan: That was a direct rip to disk, mind you.
[01:45] <StevenK> Now I'm doing a transcode, and it's 15
[01:46] <Kyral> Morning
[01:48] <StevenK> Dual pass encoding gets me 45
[01:51] <buxy> siretart: did you see utnubu-discuss ? it looks like amaya will sponsor your package and the one of sistpoty in Debian :)
[01:55] <siretart> buxy: I just answered! :)
[01:58] <eazel7> hi
[01:59] <Yagisan> StevenK: sorry - bub woke up. I noticed when using transcode the system is less responsive, then when using mencoder on the same source
[01:59] <eazel7> I'm needing some help about building dapper packages on breezy
[01:59] <eazel7> could you help me?
[02:00] <Kyral> PBuilder?
[02:00] <Yagisan> eazel7: please be specific
[02:00] <eazel7> works for an amd64?
[02:00] <Kyral> I'm sorry I wish I could help more but I have to run to class
[02:01] <Yagisan> eazel7: I'm also on amd64 - what are you trying to backport ?
[02:01] <eazel7> I'll try, I want to build an amd64 breezy package for the mono
[02:01] <eazel7> kinda
[02:01] <eazel7> for the latest monodevelop too (much more stable than the others, if you've seen it)
[02:02] <eazel7> I used to use a binary repository for that, but now that I've switched to amd64 it's useless
[02:02] <eazel7> so I want to backport form dapper to breezy
[02:03] <eazel7> what do you suggest me to do?
[02:04] <Yagisan> eazel7: simplest way is to ask backports to backport mono and monodevelop
[02:05] <Yagisan> eazel7: otherwise start by building a pbuilder
[02:05] <Yagisan> eazel7: for breezy
[02:05] <siretart_> darn, router to tauware.de died
[02:05] <Yagisan> eazel7: then download the source packages for mono and monodevelop from dapper
[02:05] <eazel7> ok, I'll do
[02:06] <eazel7> what 'Invalid Release file, no entry for main/binary-amd64/Packages' means? (after pbuilder create)
[02:06] <Yagisan> eazel7: ubuntu-backports@lists.ubuntu.com
[02:07] <Yagisan> eazel7: try pbuilder create again
[02:16] <siretart> \sh: why do you say that we motus don't maintain packages?
[02:17] <\sh> siretart: because we don't...not in the sense of Debian (IMHO(
[02:17] <siretart> \sh: I think differently. We DO maintain the packages in ubuntu
[02:18] <Q-FUNK> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348281
[02:18] <Ubugtu> Debian bug 348281: "please add these Debian and Ubuntu floater variants" Package: gnome-screensaver, Version: gnome-screensaver/0.0.23-1., Severity: wishlist, Maintainer: guilherme.pastore@terra.com.br (Guilherme de S. Pastore)</a
[02:18] <\sh> siretart: well...we change them, fix bugs, yes. and it happens that the next time we see the package again, all bugs are fixed by debian or upstream and we sync. so no work for this package anymore
[02:19] <Q-FUNK> includess goodies for Dapper.
[02:19] <siretart> and I also think there are some MOTUs, who are indeed willing to work on the package at the debian side. since this decreases divergence, its a win-win situation
[02:19] <Q-FUNK> siretart: thanks for your reply to my comment on debian-devel.
[02:19] <lucas> siretart: the problem is: do we have time for this ?
[02:19] <lucas> and the answer is probably: no
[02:19] <\sh> siretart: that's what I said, yes. But by default "MOTU Team" as maintainer ... I would say no
[02:20] <lucas> it would piss off some MOTUs to see ubuntu-motu in the 'Maintainer:' field
[02:20] <\sh> siretart: if a maintainer, then the utnubu team, because they will push the packages into debian, as global team for taking care about the collab work
[02:20] <siretart> Q-FUNK: I'm very happy that you gave me the chance to write my lines in that context. so I'd have to thank you! :)
[02:21] <\sh> lucas: "not pissing off" but if it's appropriate...I don't know
[02:21] <siretart> lucas: In that case, I wouldn't care. I mean, why should they be annoyed when MOTUs are working on packages in debian.. *shrug*
[02:22] <lucas> siretart: do you already have some packages in Debian ?
[02:22] <Q-FUNK> siretart: I have to run now, but I'll be back in about 2 hours. let's see how I can help motu.
[02:22] <siretart> \sh: whats the rationale for not using the MOTU Team?
[02:22] <lucas> the number of mails you receive is quite important
[02:22] <lucas> (for each package)
[02:22] <siretart> lucas: yes, I currently maintain 4 packages in debian
[02:22] <lucas> I'm not sure those mails are of interest for ubuntu-motu
[02:22] <siretart> Q-FUNK: :) - cu later!
[02:22] <\sh> siretart: because some motus don't want have direct bindings towards debian
[02:23] <siretart> \sh: debian is our upstream. so there is no point in denying 'direct bindings towards debian'
[02:23] <\sh> siretart: and when the official MOTU Team is in the maintainer field, the official MOTU team is responsible. I wouldn't want that.
[02:24] <\sh> siretart: regarding the debian politics
[02:24] <Yagisan> \sh: if it is in universe/multiverse, we (MOTU) *are* responsible for it, no matter whose name is there.
[02:24] <lucas> another problem with ubuntu-motu in Maintainer: is that the sponsoring DD will have to be subscribed to ubuntu-motu
[02:24] <Yagisan> \sh: otherwise - don't sync those packages
[02:25] <lucas> Yagisan: we are talking about getting some packages into debian
[02:25] <lucas> with the collab-maint and utnubu projects
[02:25] <siretart> \sh: debian politics? huh?
[02:25] <Yagisan> lucas: I must be missing part of the log then. Don't mind me
[02:26] <eazel7> ttya
[02:26] <\sh> Yagisan: you don't understand...the official motu team can't (in my POV) be a maintainer for packages in debian. But we can create a subteam, which can handle those things. And everybody who wants to work on this, can subscribe to the team
[02:26] <lucas> Yagisan: not of the log, of some mails to utnubu-discuss@lists.alioth.d.o ;)
[02:26] <\sh> siretart: see my comment to Yagisan
[02:26] <siretart> aha, so a subteam would be okay for you..
[02:27] <azeem> that subteam could be named... "Utnubu"
[02:27] <ogra> heh
[02:27] <azeem> or maybe renamed to something else if the name is inappropriate
[02:27] <Mithrandir> debubu.
[02:27] <lucas> \sh: it's not really a subteam, since DDs will join the team too, as well as (maybe) developers from other CDDs
[02:27] <\sh> siretart: yes, because I could concentrate on my normal universe work, but don't have to deal with problems of packages inside debian, because i don't use it and can't fix bugs in debian.
[02:27] <ogra> Mithrandir, debuntu rather :)
[02:27] <siretart> Mithrandir: this one sounds truely funny :)
[02:28] <azeem> ubuntian
[02:28] <\sh> lucas: but you get my point :)
[02:28] <Mithrandir> ogra: doesn't sound so cool
[02:28] <ogra> true :)
[02:28] <lucas> \sh: I agreed with you from the start ;)
[02:28] <Mithrandir> ububian would also work.
[02:29] <lucas> collab-maint seems OK to me
[02:29] <\sh> siretart: so the core motu team can't be responsible for packages in debian, as well thinking about new members of motu...
[02:29] <siretart> well, if the alioth utnubu team won't object, I'd be happy to join the utnubu team to maintain packages there
[02:30] <siretart> \sh: I don't quite get why this is prohibited
[02:30] <lucas> I'd like to have utnubu be about general collaboration between ubuntu and debian
[02:30] <lucas> collab-maint should do the collaborative maintenance
[02:31] <ogra> lucas, in their initial announcement they said they wanted to take over maintenance
[02:31] <ogra> (utnubu)
[02:31] <Yagisan> Can someone tell me why having Ubuntu MOTU as the maintainer is wrong, when that is where the packages come from - I really don't understand why we can't be credited, but Debian maintainers must
[02:31] <\sh> siretart: volunteers are entering the MOTU team now and then...and I don't want to tell them, that they need to be responsible for packages which are coming now from debian. That they have to install somehow a working debian distro and fix bugs there as well.
[02:31] <ogra> so just leave them do what they defined once ;)
[02:31] <\sh> siretart: this is not the work of MOTU...
[02:32] <ogra> Mithrandir, no widescreen detection in my liveCDs ...
[02:32] <Mithrandir> ogra: it just does dpkg-reconfigure xserver-xorg
[02:33] <ogra> Mithrandir, but else they work wondeful, the speedup you built in is impressing
[02:33] <ogra> yup
[02:33] <\sh> siretart: the difference is: we are working on Ubuntu, but fixing bugs in debian, I can't and I don't want. Because I don't have the infrastructure for correct testing for debian. And it bytes with the description of the MOTU team.
[02:33] <ogra> i wonder how daniels solved it in breezy, i have a similar prob with ltsp
[02:34] <Mithrandir> ogra: sweet. :-)
[02:34] <Yagisan> \sh: If WE are the upstream for those packages - they can sync with US to fix it.
[02:34] <Yagisan> \sh: what is good for the goose, is good for the gander
[02:34] <\sh> siretart: free will work for debian, next to the normal MOTU work, is quite ok..and a special formed team can do that, without anyone to be forced to do things, he/she doesn't want
[02:35] <siretart> \sh: I see things a bit different
[02:35] <siretart> \sh: first of all, we are talking about packages which are in ubuntu only. if there is someone who is willing to maintain it in debian properly on his own, he is free to file an ITP
[02:36] <siretart> \sh: those ubuntu only packages are currently maintained by the MOTU team
[02:37] <siretart> \sh: I'm thinking about nearly all packages imported through revu e.g. I don't expect their submitters to care for their packages properly
[02:37] <Yagisan> siretart: hey - I care for my packages
[02:37] <Yagisan> siretart: I've never had one accepted, but still ..
[02:37] <siretart> \sh: lucas tried to raise this discussion the last motu meeting, but everyone agrees that in the end the submittors cannot be obliged to care for them
[02:38] <siretart> Yagisan: yes, I also care for my own packages, right. but there are also quite a lot of packages, which are submitted once and then more or less orphaned, I assume
[02:38] <\sh> siretart: well, I would respect the will of the original creator. If he is ok with it, that his package goes into debian, ok. The decision to be made for this situation: does the creator wants to be maintaining the package in debian, or the collab team.
[02:39] <\sh> siretart: if the package maintainer doesn't want to include his package into debian, we should respect that
[02:39] <siretart> \sh: for these specific packages, I think it is reasonable to maintain it in debian, too, under the assumption that there are debian users, you care about their integration into debian. we care for the integration into ubuntu
[02:39] <Mithrandir> \sh: Debian is free to include any free software as they see fit, I don't see any reason to ask for permission.  Notifying the author is nice, though.
[02:40] <\sh> siretart: those "orphaned" packages should be removed then completly. if there is no action in about let's say 2 release cycles
[02:40] <siretart> \sh: if the creator of the package would care seeing them in debian, he would have filed an ITP, no?
[02:40] <lucas> \sh: I think the general opinion about this is "we don't"
[02:40] <\sh> Mithrandir: when someone is there to take over the reponsibilty, ok :)
[02:40] <lucas> the policy is currently that we prefer having a broken package than no package at all
[02:40] <Yagisan> siretart: no - I won't - debian is far too unwelcoming at this stage
[02:41] <siretart> \sh: we don't have any means or statistics to track those 'orphaned' packages in ubuntu. we don't even have enough ressources and motivation to find them
[02:41] <lucas> siretart: I added the status of popcon.u.c to tomorrow's TB meeting. Be there to say that popcon.u.c is important ;)
[02:41] <\sh> siretart: to find this out, is quite an easy thing...I use my search function for -changes :)
[02:42] <siretart> Yagisan: and thats the actual problem: debian has a much higher expectation from maintainers caring for their packages
[02:42] <siretart> lucas: uff, at what time is the TB meeting?
[02:42] <lucas> 20 utc
[02:42] <lucas> (I think)
[02:42] <siretart> \sh: I hope you agree thats a really poor metric
[02:42] <Yagisan> siretart: I'm not a programming guru, so I'd never be good enough for them. That doesn't mean I'm dumb, or can't maintain packages, but they just discourage users from joining in
[02:42] <\sh> siretart: but again, I don't agree that the core motu team should be mentioned as debian maintainer for the package. I, and this is IMHO, can't work on bugs in debian, because I don't use plain debian
[02:43] <siretart> lucas: 2000utc is very unconvinient for me. I can attend not before 2100utc
[02:43] <siretart> Yagisan: you don't need to be a programming guru to be a DD
[02:44] <lucas> try to join at 2100 utc, maybe popcon won't be discussed before
[02:44] <siretart> I'll try
[02:44] <\sh> siretart: it's the best metric we have, for universe. If there was a package upload in hoary, and no package upload in breezy and dapper, and the package itself is ftbfs (which we can find out), I'm glad to remove/morgue it.
[02:45] <siretart> \sh: I wouldn't want to remove working and functionally great packages, just because nobody uploaded them for 2 years
[02:45] <Yagisan> siretart: after following the lists for *years*, I am aware I won't meet the criteria. Not for a while anyway.
[02:45] <siretart> \sh: neither would I like to see bogous upload just to save packages from your metric :/
[02:47] <\sh> siretart: anyways...I would like to see a different team which want to work on packages which are in ubuntu, but not in debian yet, and if those packages are reaching debian, I see it as upstream. Seeing the core MOTU team as debian maintainer, I don't
[02:47] <Yagisan> \sh: If they go from us to debian, we are upstream
[02:47] <\sh> a clean separation is much better, then to force people doing work they don't want to do
[02:49] <siretart> \sh: why do you think anyone is forced to do anything?
[02:49] <\sh> Yagisan: no..someone is upstream, the core MOTU team as it exists now, can't be upstream, in my eyes. but to stop the discussion now, we should put this on the TB agenda, and let us find a solution.
[02:50] <\sh> siretart: "forced" is wrong, I would say, the responsibilities are changing then...the core motu team is then responsible for bugs in debian, which is not possible for an Ubuntu team, where not everybody is using a plain debian install.
[02:52] <\sh> .oO(despite the fact, that ubuntu is a debian derivative...)
[02:54] <sivang> what the ..... http://www.flickr.com/photos/86444323@N00/81971182/ :)
[02:58] <Yagisan> sivang: needs more ethnic groups
[03:01] <sivang> Yagisan: I'll say ! :)
[03:14] <marcin`> hello MOTU
[03:14] <marcin`> got a question
[03:14] <marcin`> could someone tell me what should I put into 'editors' category?
[03:14] <marcin`> and what in 'devel'?
[03:15] <marcin`> I got this question because in universe there are emacs related packages
[03:15] <marcin`> and I wonder why css-mode is in editors while tiger-mode is in devel
[03:16] <marcin`> could someone point me to some policy document where is defined what goes to editors category?
[03:19] <marcin`> it's so quiet here...
[03:25] <Yagisan> marcin`: I'd say most people are busy at the moment
[03:25] <Yagisan> marcin`: myself included
[03:26] <marcin`> Yagisan: no problem
[03:27] <lucas> marcin`: sections are not very useful
[03:27] <lucas> debian has a replacement called "debtags"
[03:34] <dholbach> marcin`: but you can check which other packages are in those sections in synaptic/dselect/aptitude/.. - i think this is the best way to figure out
[03:36] <Gloubiboulga> hello
[04:31] <Q-FUNK> siretart: re
[04:32] <Kyral> if anyone has a second to review LaptopTemp http://revu.tauware.de/details.py?upid=1510 would be great. It works fine (running it right now on my laptop :D)
[04:43] <lapo> hi
[04:43] <Kyral> hello
[04:43] <lapo> is there an ubuntu art channel?
[04:43] <Kyral> uh....dunno
[04:45] <Q-FUNK> lapo: #ubuntu-artwork if I recall
[04:45] <lapo> Q-FUNK, tnx
[04:47] <Kyral> when is the UVF anyway
[04:59] <nlindblad> are you guys really the masters of the universe?
[05:01] <Yagisan> nlindblad: you forgot multiverse too.
[05:01] <nlindblad> right
[05:01] <Yagisan> nlindblad: actually, I don't know if we are all guys here
[05:02] <nlindblad> I though 'guys' could be used no matter the sex
[05:03] <Yagisan> nlindblad: what's on your mind ?
[05:04] <nlindblad> you mean why I'm here?
[05:04] <Yagisan> nlindblad: exactly
[05:04] <nlindblad> well, I love (K)Ubuntu
[05:04] <nlindblad> and I'd love to commit back
[05:05] <Yagisan> nlindblad: excellent
[05:06] <nlindblad> it is?
[05:07] <Yagisan> nlindblad: how would you like to help ?
[05:07] <Yagisan> nlindblad: I should probably disclaim now, that I'm not actually a MOTU
[05:09] <nlindblad> Yagisan: I'd love to discuss the different ways to help
[05:09] <nlindblad> are you here later on?
[05:09] <nlindblad> because I'll be away for an hour or two
[05:10] <Yagisan> nlindblad: It's 3:10am here - I should have been in bed a long time ago. The others are very helpful though, if I'm not here, or don
[05:10] <Yagisan> 'don't seem to answer
[05:10] <nlindblad> right
[05:10] <nlindblad> :D
[05:10] <nlindblad> nice to speak to you anyway
[05:17] <siretart> hi folks
[05:50] <LaserJock_away> azeem: ping?
[05:51] <azeem> heya
[05:51] <LaserJock_away> azeem: I inherited a ITP yesterday for Gausssum, have you heard of it?
[05:52] <azeem> nope
[05:52] <azeem> is that a frontend for gaussian?
[05:52] <azeem> hrm
[05:52] <LaserJock_away> it is a python program for looking at gaussian and GAMESS output
[05:52] <azeem> Thottbot World of Warcraft: Character Profiles
[05:52] <azeem> Gaussum, 60, Druid
[05:52] <azeem> not that :)
[05:53] <LaserJock_away> it uses Gnuplot and can give you Density of States, IR spectra, etc.
[05:53] <azeem> that sounds nice
[05:53] <LaserJock_away> azeem: http://gausssum.sourceforge.net/ is the URL
[05:54] <azeem> does it look nice as well? =)
[05:54] <azeem> thanks
[05:54] <LaserJock_away> I came across it about a year ago when I was doing a lot of Gaussian calculations.
[05:54] <LaserJock_away> Gaussian in very hard to get the data out of
[05:54] <azeem> they are running pymol there in the background
[05:54] <LaserJock_away> you basically have to make a perl script to find what you want
[05:55] <azeem> yeah
[05:56] <azeem> the plots don't look publication-ready and the GUI seems a bit strange, but it sure sounds useful
[05:56] <LaserJock_away> anyway, I saw and ITP and emailed the guy about it and he said he didn't want it anymore (no faith in debian-mentors I think he said)
[05:56] <LaserJock_away> well, there is a Gausssum2 being worked on in CVS
[05:57] <azeem> heh
[05:57] <LaserJock_away> I think it might be significantly better when it is released
[05:58] <LaserJock_away> anyway, I think I will try to fix this guys package and email you when it is done. Does that sound OK?
[05:59] <LaserJock_away> I wish I had something like Gausssum when I was taking a computational chemistry class ;-)
[06:00] <azeem> LaserJock_away: sure, sounds fine
[06:01] <LaserJock_away> azeem: ok, just wanted to give you a heads up
[06:01] <LaserJock_away> azeem: btw, I don't suppose you could make one of the Extramadura meetings they have been talking about on debian-science?
[06:01] <azeem> I haven't followed closely, but probably not
[06:02] <LaserJock_away> they were talking about having a session on MOTUSciece collaboration but I don't know that anybody from Ubuntu will be there :(
[06:16] <hyperactivecrond> where does one actually download the coc?
[06:16] <hyperactivecrond> probably wrong channel.. sorry
[06:18] <hyperactivecrond> never mind. found it
[06:59] <thierry> does dh_ruby exist?
[07:03] <LaserJock> thierry: I don't see one
[07:03] <thierry> k
[07:04] <thierry> LaserJock : do you know how I could clean a specific file in the rules file?
[07:12] <LaserJock> thierry: I think you can use rm
[07:19] <thierry> LaserJock : rm wasn't for deleting file??
[07:42] <LaserJock> thierry: what are you trying to do?
[07:44] <_nlindblad> hello again
[07:44] <LaserJock> hi _nlindblad
[07:45] <nlindblad> is Yagisan not with us any more?
[07:46] <LaserJock> nlindblad: check his away message ;-)
[07:49] <nlindblad> how?
[07:50] <LaserJock> nlindblad: depends on your client but I get : I'm not available because I am attending to her royal highness, the revered and exulted baby.
[07:50] <nlindblad> okey
[07:51] <nlindblad> what different ways are there to commit back to (K)Ubuntu?
[07:52] <LaserJock> nlindblad: like ways to help out?
[07:52] <nlindblad> yeah
[07:53] <LaserJock> nlindblad: well, basically in any way you want
[07:53] <LaserJock> nlindblad: you can work on documentation, or fixing bugs, or maintaining packages
[07:54] <nlindblad> okey
[07:54] <nlindblad> any more ways?
[07:54] <LaserJock> nlindblad: testing, reporting bugs, advocacy
[07:55] <nlindblad> okey
[07:56] <LaserJock> nlindblad: take a look at https://wiki.ubuntu.com/HelpingUbuntu
[08:02] <nlindblad> I'll do that, thanks
[08:04] <LaserJock> nlindblad: np, hopefully that helps
[08:28] <Q-FUNK> siretart: back?
[08:45] <siretart> Q-FUNK: I'm currently in the pub, with wifi access :)
[08:45] <siretart> we are having our regulars table on monday
[08:45] <Q-FUNK> oh :)
[09:15] <Kyral> yo
[09:16] <LaserJock> hi Kyral
[09:21] <LaserJock> has any MOTUs been keeping track of all the merge work Yann has been doing?
[09:46] <LaserJock> lucas: ping?
[09:46] <greenpenguin13> LaserJock, pong
[09:47] <lucas> LaserJock: pong
[09:47] <LaserJock> lucas: is there a way to put a time stamp in the versions2html output?
[09:48] <lucas> you mean sthing like "generated ..... " at the bottom ?
[09:48] <LaserJock> lucas: I was thinking more like at the top
[09:49] <LaserJock> lucas: I think it is pretty important to know when the list was created when packages change so fast
[09:49] <LaserJock> anyway, just a though
[09:49] <LaserJock> t
[09:49] <lucas> the problem is it depends on when the archive is updated, for example
[09:49] <lucas> but I can add a timestamp, yes
[09:50] <LaserJock> hmm, so maybe you can read when the archive has last been updated
[09:51] <LaserJock> lucas: btw, is the mdt bzr repo ok to update from, you said to wait a while but that was a while ago ;-)
[09:51] <lucas> well it is
[09:52] <lucas> but make a backup first
[09:52] <lucas> I don't know what you changed exactly
[09:52] <lucas> merging might break stuff
[09:53] <LaserJock> lucas: I haven't changed anything
[09:57] <lucas> ok
[09:58] <lucas> you can update now. I added a footer with a link to the wiki page and the generation time
[09:59] <LaserJock> lucas: cool, thanks
[10:05] <Kyral> hgmm
[10:14] <LaserJock> Kyral: how is that going for you?
[10:16] <Kyral> eh
[10:16] <Kyral> convienent
[10:17] <Kyral> but I dunno how to make it sign automagically
[10:17] <LaserJock> man debuild
[10:24] <phanatic> hi people
[10:25] <Kyral> yo
[10:26] <LaserJock> Kyral: have you tried pdebuild?
[10:26] <Kyral> nope
[10:27] <LaserJock> Kyral: pbuilder + debuild
[10:27] <Kyral> niiice
[10:27] <Kyral> where is it?
[10:29] <Kyral> I can't find it in Dapper
[10:29] <phanatic> Kyral: in the pbuilder package
[10:30] <phanatic> it's part of it as i see
[10:30] <Kyral> oh lol
[10:42] <Evaso> hi guys any plan to sync Spe package... seems that many upstream releases was missed on debian?
[10:43] <lucas> Evaso: some urls would be nice
[10:43] <lucas> (just because I'm lazy)
[10:43] <Evaso> lucas: http://www.stani.be/python/spe/blog/
[10:44] <lucas> and what's the ubuntu package ?
[10:44] <Evaso> upstream : SPE 0.8.1.d ubuntu: 0.7.5c
[10:44] <Evaso> lucas: http://packages.ubuntu.com/cgi-bin/search_packages.pl?searchon=names&version=all&exact=1&keywords=spe
[10:44] <slomo> debian is 0.7.5c too
[10:45] <Evaso> yes
[10:45] <Evaso> i think that debian maintainer is not packaging anymore the upstream packages but the debian package is not orphaned
[10:47] <lucas> the debian maintainer is an ubuntu developer
[10:47] <lucas> doko: ping ?
[10:48] <lucas> doko: Evaso here is wondering whether you plan to package the new upstream version of 'spe' (see debian bug 341192 too)
[10:48] <Ubugtu> Debian bug 341192: "New upstream release" Package: spe, Version: spe/0.7.5c-1., Severity: wishlist, Maintainer: Matthias Klose  http://bugs.debian.org/341192
[10:49] <doko> lucas: sorry, currently no time. please go ahead
[10:49] <Evaso> lucas: i had alread seen this bug
[10:50] <slomo> lucas: just do it yourself ;)
[10:52] <Evaso> debian has skipped 0.7.5.d 0.7.5.f 0.8.0.a 0.8.0.b 0.8.0.c 0.8.1.b 0.8.1.c 0.8.1.d
[10:52] <lucas> ah ah I wasn't planning to do it myself :-)
[10:53] <slomo> lucas: why? ;)
[10:53] <Kyral> doko do you have a watchfile on that pack?
[10:54] <Evaso> Kyral: seems that spe doesnt has watch file http://dehs.alioth.debian.org/maintainer.php?name=spe&Find=Find
[10:55] <Kyral> I'll do it
[10:55] <Kyral> should be easy
[10:55] <slomo> Kyral: well... not necessarily...
[10:55] <slomo> Kyral: doko asked me to do some patches... maybe you have to port them to the new version :P
[10:55] <Evaso> Kyral: it have http://dehs.alioth.debian.org/wwiz_detail.php?id=3818680&type=watch
[10:56] <slomo> Kyral: but when you're done i can take a look at it and upload it...
[10:56] <Evaso> but has not any active url all are commented as u can see in the link
[10:56] <Kyral> slomo: right now I'm planning to Diff the two ;P
[10:56] <Evaso> Kyral: the actual watch file is here http://dehs.alioth.debian.org/wwiz_detail.php?id=3818680&type=watch
[10:56] <Gervystar> is it already known that the latest beagle package is actually broken? (dist-upgraded to dapper yesterday and ready to file bugs :-) )
[10:56] <slomo> Kyral: http://people.ubuntu.com/~scott/patches/spe/
[10:56] <slomo> Gervystar: yes, it's known
[10:57] <Kyral> eez
[10:57] <Kyral> it was easy to make a watchfile
[10:57] <Kyral> I'll just let uscan handle it :D
[10:57] <slomo> ?
[10:58] <slomo> why do you need a watchfile to make it easier now? just get the tarball and use uupdate
[10:58] <Evaso> here if you need there are upstream info of all the debian packages: http://dehs.alioth.debian.org/dehs_debianqa.txt
[10:59] <Kyral> slomo: One I'd make a watchfile for it
[10:59] <Evaso> and here there is a list of packages (with watch file) that seems not in sync with upstream version http://dehs.alioth.debian.org/no_updated.html
[11:00] <Evaso> clicking ond the upstream version you could view upstream NEWS/Changelog for see bug fixed and new features not included in debian/ubuntu
[11:04] <slomo> Kyral: well, i'll get to bed :) upload to revu and give me the url in a query... and i'll upload it tomorrow ;)
[11:04] <slomo> gn8 everybody
[11:06] <LaserJock> Evaso: it would be interesting to see how the no_updated.html list compares to the list of orphaned packages
[11:06] <Kyral> doko: You mind me putting myself as Maintainer for this?
[11:08] <Evaso> LaserJock: i think i quite trivial to compare simply parse this semplified version http://dehs.alioth.debian.org/no_updated.txt
[11:14] <Kyral> ping doko
[11:15] <Kyral> meh I dunno if I should just make the changelog entry or change the Maintainer as well
[11:16] <Kyral> Evaso: what was the Ubuntu bug?
[11:16] <Evaso> Kyral: what Ubuntu bug?
[11:17] <Kyral> I really wanna know if Doko wants to give up Maintainership of the Package
[11:17] <Evaso> Kyral: do u mean in the watch file?
[11:17] <Kyral> I mean if he has no time I can take it over
[11:18] <lucas> Kyral: you should start preparing an upgraded package that maybe doko can quickly review
[11:18] <Kyral> its already upgraded :P
[11:19] <lucas> it would be better to upload it to debian first, so it would be synced into ubuntu
[11:19] <Kyral> yah...and lintian is throwing warnings
[11:20] <Kyral> I have to clean up the package...
[11:22] <Kyral> not to mention make it build..
[11:27] <Kyral> meh..
[11:27] <Kyral> I'll reapply stuff
[11:27] <Kyral> I need DINNER
[11:57] <chninkel> would be nice if some MOTU could have a look at the merge I've done before UVF
[11:57] <chninkel> the list is merge/sync is almost this one:
[11:57] <chninkel> https://launchpad.net/people/yann-pleiades/+reportedbugs?field.searchtext=&search=Search&orderby=-priority%2C-severity&advanced=1&field.assignee=&field.unassigned.used=&field.include_dupes.used=&field.statusexplanation=&field.status%3Alist=Fix+Committed&field.status-empty-marker=1&field.severity-empty-marker=1&field.attachmenttype-empty-marker=1
[11:59] <chninkel> can I directly request sync ?
[11:59] <LaserJock> chninkel: you need to get a MOTU to request a sync for you
[12:00] <chninkel> it's what I just asked
[12:00] <chninkel> but there so not so much people around at this time
[12:00] <LaserJock> but if you do it directly elmo will probably ignore you ;-)
[12:00] <chninkel> LaserJock: ok
[12:00] <chninkel> so I can't do anything
[12:00] <chninkel> :(
[12:00] <LaserJock> chninkel: you might try to email dholbach or \sh or ajmitch
[12:01] <LaserJock> with a list of your requests
[12:01] <LaserJock> if they aren't around
[12:01] <chninkel> maybe on ubuntu-motu@lists.ubuntu.com ?
[12:01] <LaserJock> chninkel: I see you've been doing lots of merge work, you just need to bug people here or by email to review your merges or request syncs
[12:02] <chninkel> LaserJock: yes I see that
[12:02] <chninkel> I thought motu regularly look at bugs assigned to reviewers
[12:02] <LaserJock> chninkel: yeah, if you get a list together it would be good to email ubuntu-motu
[12:02] <chninkel> and indeed some of my merges were taken in account
[12:02] <LaserJock> chninkel: well, when they are busy they need a little poking