[12:02] <raphink> do it again
[12:02] <raphink> and give me the new url when it's done
[12:02] <lfittl> raphink: he did a native upload, that also happens if you don't have a orig.tar.gz
[12:02] <raphink> (check it's created the orig.tar.gz before uploading again)
[12:03] <raphink> hmmm
[12:03] <lfittl> segfault: make sure there is a file named roundcue_0.1.orig.tar.gz
[12:03] <raphink> what do you mean by native upload lfittl ?
[12:03] <raphink> :s
[12:03] <raphink> oki
[12:03] <segfault> roundcube_webmail_0.1-20051021.tar.gz
[12:03] <lfittl> raphink: upload without using an upstream source ;)
[12:03] <raphink> segfault: you should either rename the original tar.gz to orig.tar.gz
[12:03] <segfault> that was the name of the upstrem package
[12:03] <segfault> heh
[12:03] <raphink> segfault: rename it
[12:03] <raphink> lfittl: ok :)
[12:04] <raphink> segfault: mv it to roundcube_webmail_0.1.orig.tar.gz
[12:04] <segfault> k
[12:04] <lfittl> segfault: name of the upstream package is not important, important is the name and version of your sourcepackage
[12:04] <raphink> actually
[12:04] <raphink> is the version really 0.1 ?
[12:04] <lfittl> raphink: his sourcepackage name is roundcube without webmail ;)
[12:04] <raphink> isn't it 0.1-20051021 ?
[12:05] <raphink> yes
[12:05] <segfault> is it wrong? should i include the date?
[12:05] <raphink> why not keep webmail in the sourcepackage name segfault ,
[12:05] <raphink> segfault: depends if the date is part of the version number
[12:05] <segfault> too big? the project name itself is just roundcube
[12:05] <raphink> segfault: if the date is used as a sub-version of 0.1 then yes
[12:06] <raphink> segfault: roundcube-webmail would be fine for a name, too
[12:06] <segfault> ok, i'll change it
[12:07] <lfittl> upstream released other 0.1 versions, make sure to change the version number to 0.1-20051021
[12:07] <raphink> lfittl: that's what i'd think too
[12:07] <raphink> :)
[12:08] <segfault> roundcube-webmail_0.1-20051021
[12:08] <raphink> yes
[12:08] <lfittl> :)
[12:08] <raphink> so the upstream tarball will be renamed to (or linked from) roundcube-webmail_0.1-20051021.orig.tar.gz
[12:09] <segfault> iirc, i didn't use it too because of dh_make complained about it
[12:09] <raphink> then you change your debian/control aswell ;)
[12:09] <segfault> but its ok now
[12:09] <raphink> and the source package dir name
[12:09] <raphink> and you run dpkg-buildpackage again ;)
[12:09] <raphink> segfault: dh_make might complain about things and still be wrong ;)
[12:09] <raphink> dh_make is helpful but we still package manually
[12:09] <raphink> :)
[12:10] <raphink> for good reasons
[12:12] <segfault> i see
[12:12] <raphink> wb Kyral
[12:13] <Kyral> ty
[12:14] <segfault> the directory must have package-version, while orig.tar.gz uses package_version
[12:14] <segfault> why?
[12:14] <raphink> that's policy ;)
[12:15] <segfault> right
[12:16] <segfault> http://revu.tauware.de/details.py?upid=1385
[12:16] <raphink> lets see
[12:17] <segfault> i haven't made a nice postinst script, i'm still fighting with debconf.
[12:18] <segfault> most of its parts i got from phpldapadmin's source
[12:19] <raphink> E: roundcube-webmail source: declares-possibly-conflicting-debhelper-compat-versions 4 4
[12:19] <lfittl> segfault: You could change the apache in "Depends: apache | httpd" to apache2, since that is our default webserver now ;)
[12:19] <raphink> remove the debhelper compat declaration from debian/rules
[12:20] <raphink> and use only debian/compat and debian/control for it
[12:20] <segfault> ok
[12:20] <raphink> distribution is dapper, not unstable
[12:20] <lfittl> maybe changing the debhelper compat level to 5 would be good
[12:21] <raphink> yes, too
[12:22] <segfault> ok, changed
[12:22] <segfault> uploading again..
[12:22] <lfittl> :)
[12:23] <segfault> how do i remove with dcut? i pressed ctrl+c.
[12:23] <raphink> segfault: no
[12:23] <segfault> heh
[12:23] <raphink> I'm still commenting
[12:23] <raphink> its not done yet
[12:23] <segfault> raphink: ah, right, sorry
[12:23] <minghua> segfault: the reason orig.tar.gz must be named package_version is that there can be character "-" in the package name, such as your case
[12:24] <minghua> segfault: the directory name is based on the debian/changelog, so it knows exactly which part is package name, which part is version number
[12:24] <minghua> as for why such inconsistency exists, I don't really know :-(
[12:25] <segfault> humm, thanks for the explanation
[12:26] <raphink> is this your first package segfault ?
[12:27] <raphink> if so, you didn't choose the easiest one to begin with ;)
[12:27] <raphink> segfault: give me a good reason why your package would modify the apache config
[12:28] <raphink> wb seth_k|lappy
[12:30] <raphink> segfault: first comments sent ;)
[12:32] <lfittl> segfault: building the package in my pbuilder fails
[12:32] <lfittl> cp: cannot create regular file `debian/roundcube/usr/share/doc/roundcube/INSTALL.roundcube': No such file or directory
[12:32] <raphink> I'll test the build once the first comments are taken in consideration :)
[12:33] <lfittl> good idea :)
[12:33] <lfittl> although this should be a missing mkdir, and easy to fix
[12:33] <raphink> and I'd first like to know if postinstall and prerm are necessary
[12:33] <raphink> and why they'd modify apache.conf
[12:34] <segfault> i'll read now, wait
[12:36] <segfault> well, it was in case the user is using apache-1.3
[12:36] <segfault> in case of apache2, it uses "apache.conf", which stays in /etc/roundcube
[12:37] <segfault> and creates a link inside /etc/apache2/conf.d
[12:37] <lfittl> then drop the apache-1.3 part
[12:37] <segfault> but since it now depends only on apache2, i'll remove the httpd entries
[12:37] <segfault> in the postrm
[12:37] <segfault> err, postinst.
[12:37] <raphink> what's the use of the postrm and postinst otherwise?
[12:38] <raphink> I see it activates some modules
[12:38] <raphink> but these modules are already activated by the postinst of the libapach2-mod-* packages
[12:38] <raphink> corresponding
[12:38] <raphink> so you don't need to do that
[12:38] <raphink> I don't see a reason why your package should touch apache.conf at all so far
[12:39] <segfault> well, i got it from phpldapadmin
[12:39] <segfault> all it does is append conf.d as a modular directory if it doesn't exist in the conf file
[12:40] <segfault> in the case of apache2, it does exist by default, so its not necessary to create it
[12:41] <segfault> i'll change it
[12:41] <segfault> for some reason, debconf questions are not showing up after install
[12:41] <raphink> segfault: i'd like it if you could keep only what's necessary, or even remove the postinst and prerm
[12:41] <raphink> segfault: how about when you run dpkg-reconfigure ?
[12:42] <raphink> talking about debconf
[12:42] <raphink> according to policy
[12:42] <raphink> debconf questions should be ask in config, not in postints
[12:42] <raphink> postinst should ask no question
[12:43] <raphink> only apply the actions required by choices made in config with debconf
[12:43] <sistpoty> hi folks
[12:43] <segfault> i'll clean it up now, removing the apache1 stuff
[12:43] <raphink> hi sistpoty :)
[12:43] <raphink> ok
[12:44] <raphink> how are you sistpoty ?
[12:44] <sistpoty> raphink: I'm fine, thx... how are you?
[12:44] <raphink> I'm fine too :)
[12:45] <raphink> sistpoty: trying to think of a job to do ;)
[12:45] <raphink> and bugging everybody about it ;)
[12:45] <sistpoty> hehe
[12:45] <raphink> lol
[12:45] <lfittl> hi sistpoty, could you archive 1 package, and delete another one on revu?
[12:45] <raphink> just so you're prepared ;)
[12:45] <sistpoty> hi lfittl
[12:45] <sistpoty> lfittl: sure, which ones?
[12:45] <raphink> lfittl: which ones?
[12:45] <raphink> ;)
[12:45] <sistpoty> :)
[12:46] <lfittl> sistpoty: delete http://revu.tauware.de/details.py?upid=1384, because we decided to change source package name 5min ago
[12:46] <lfittl> and archive http://revu.tauware.de/details.py?upid=1148 as its uploaded ;)
[12:46] <raphink> :)
[12:47] <raphink> http://revu.tauware.de/details.py?upid=1384, archived :)
[12:47] <lfittl> right, as a reviewer you could archive too :)
[12:47] <raphink> yep
[12:47] <raphink> but I can't delete
[12:48] <lfittl> yep i know that only admins are allowed to do this
[12:48] <sistpoty> raphink: lol, I guess I unarchived it again
[12:48] <raphink> haha
[12:48] <seth_k|lappy> raphink, you can archive? oh you're in trouble now, I"ll be giving you things to archive all day :P
[12:48] <sistpoty> no, old problem... there were more then one uploads
[12:48] <raphink> playing ping pong with packages sistpoty ?
[12:48] <raphink> seth_k|lappy: I can archive packages on REVU
[12:49] <raphink> I doubt there's packages to archive everyday ;)
[12:49] <seth_k|lappy> sistpoty, want to review a KDE style for me (already has one advocate and 2 positive reviews) http://revu.tauware.de/details.py?upid=1375
[12:49] <sistpoty> seth_k|lappy: ok... will take a look
[12:49] <seth_k|lappy> thanks sistpoty :)
[12:49] <raphink> seth_k|lappy: funnily enough, we're both halfway to MOTU
[12:49] <raphink> seth_k|lappy: you've got the membership part, i've got the reviewer one
[12:50] <raphink> seth_k|lappy: we could merge ;)
[12:50] <raphink> lol
[12:50] <seth_k|lappy> raphink, http://revu.tauware.de/details.py?upid=1257 http://revu.tauware.de/details.py?upid=1365 http://revu.tauware.de/details.py?upid=1230
[12:50] <raphink> j/k
[12:50] <seth_k|lappy> archive those :P
[12:50] <raphink> k
[12:50] <seth_k|lappy> thanks :)
[12:50] <raphink> please ;)
[12:50] <lfittl> raphink: could you delete one of the advocates on http://revu.tauware.de/details.py?upid=1284 for me? :)
[12:50] <lfittl> the package is not yet ready for upload
[12:50] <raphink> ok
[12:51] <sistpoty> raphink: only admins can delete advocates iirc
[12:51] <lfittl> k, then sistpoty: could you do it for me? :)
[12:51] <raphink> sistpoty: oh yes
[12:51] <raphink> i can only remove mine if I ever put any huhu
[12:52] <sistpoty> lfittl: I guess it would be good to keep the advocates (further checking will be easier)... but I can delete them and write some comment bout it ;)
[12:52] <raphink> seth_k|lappy: packages archived
[12:52] <lfittl> sistpoty: I will just make a minor change and upload again
[12:52] <segfault> must the "copyright holder" be dated?
[12:52] <lfittl> segfault: yes
[12:53] <seth_k|lappy> segfault, make sure and date each year the person holds copyright
[12:53] <raphink> a copyright is "(C) YYYY Author Name"
[12:53] <seth_k|lappy> e.g. (c) 2003, 2004, 2005 Foo Bar
[12:53] <raphink> a copyright is "(C) YYYY Author Name author@mail.ext"
[12:53] <seth_k|lappy> ah right, and e-mail address
[12:53] <segfault> ok
[12:53] <raphink> seth_k|lappy: 2003-2005 is fine too
[12:53] <raphink> imo
[12:53] <seth_k|lappy> yep
[12:54] <raphink> although the FSF likes to write the whole list of years ;)
[01:06] <segfault> Uploading via ftp roundcube-webmail_0.1-20051021-0ubuntu1.dsc: Error '553 Could not create file.'
[01:06] <segfault> can anyone erase it?
[01:07] <raphink> use -f
[01:07] <raphink> dput -f
[01:07] <raphink> to force the upload
[01:07] <segfault> i did
[01:07] <raphink> hmm
[01:07] <raphink> ok
[01:07] <raphink> let's see
[01:07] <segfault> i pressed ctrl+c some time ago while uploading
[01:08] <raphink> hmm
[01:08] <raphink> sistpoty: any idea,
[01:08] <raphink> ?
[01:08] <segfault> Note: This problem might be caused by files already existent on the server.
[01:08] <segfault>       For the official Debian upload queues, the dcut(1) utility can be used
[01:08] <segfault>       to remove stale files from unsuccessful uploads.
[01:09] <raphink> I don't think you can use dcut with REVU
[01:09] <raphink> not sure
[01:09] <seth_k|lappy> you can't
[01:09] <seth_k|lappy> I tried once
[01:09] <seth_k|lappy> sistpoty will have to remove the files
[01:09] <seth_k|lappy> (or another admin)
[01:09] <raphink> yep
[01:10] <sistpoty> I'm on it ;)
[01:10] <segfault> thanks
[01:10] <raphink> :)
[01:12] <sistpoty> segfault: files should be gone
[01:13] <segfault> yeap, thanks again
[01:13] <raphink> sistpoty: could you have a look at kalcul please while you're there?
[01:14] <raphink> http://revu.tauware.de/details.py?upid=1310
[01:14] <sistpoty> raphink: I'll add it to the q... I'm still on the kde style ;)
[01:14] <seth_k|lappy> get in line, raphink ;)
[01:14] <raphink> it's ready to go ;)
[01:14] <raphink> oh ok :)
[01:14] <seth_k|lappy> hehehe
[01:15] <sistpoty> hehe
[01:15] <raphink> hey I'm number 2 :D
[01:17] <segfault> http://revu.tauware.de/details.py?upid=1386
[01:17] <segfault> anyone?
[01:17] <segfault> :)
[01:18] <raphink> yep
[01:19] <raphink> you still miss the / in debian/dirs segfault
[01:20] <raphink> I don't know that you need to use .../roundcube-webmail dirs
[01:20] <raphink> but I'm pretty sure you need to have absolute paths
[01:21] <segfault> where?
[01:21] <raphink> debian/dirs
[01:21] <raphink> you use usr/share/ etc...
[01:21] <segfault> are those / in debian/dirs really necessary? i haven't seen one debian/dirs using it
[01:21] <raphink> I think it should be /usr/share/etc.
[01:21] <raphink> not sure
[01:21] <raphink> hmm I'l have a look at policy
[01:22] <segfault> so far i read phpldapadmin and snort sources
[01:22] <segfault> what do you mean with /usr/share/etc?
[01:23] <segfault> put the roundcube configs there?
[01:23] <raphink> cant' find it
[01:23] <raphink> keep it so
[01:23] <raphink> no, no nevermind
[01:23] <lucas> on http://ox.blop.info/bazaar/universe-versionslist.html.gz, packages are now sorted according to popcon results
[01:23] <raphink> great lucas :)
[01:23] <lucas> it makes it easier to determine on which merges/syncs you should work first
[01:23] <lfittl> :)
[01:23] <raphink> rock
[01:24] <lucas> it took me 4 hours
[01:24] <raphink> wow
[01:24] <raphink> :)
[01:24] <lucas> I had to understand how python-apt worked to write a script that convert binary package names to source package names efficiently
[01:24] <lucas> and libapt-pkg really is evil ;)
[01:24] <raphink> ;)
[01:25] <lucas> wesnoth	1.1-1	1.0.2-1ubuntu1
[01:25] <lucas> this one should be high priority :-)
[01:25] <raphink> oh yeah :D
[01:25] <raphink> I could do it :)
[01:25] <raphink> as my first merge :)
[01:26] <raphink> segfault: you miss the Homepage: at the end of the long description in debian/control
[01:27] <lucas> raphink: go ahead with wesnoth
[01:27] <lfittl> lucas: dholbach might be interested in adding news about that to the motu report :)
[01:27] <lucas> lfittl: I first have to move the list elsewhere
[01:28] <raphink> lucas: I'll go as soon as i'm done reviewing
[01:28] <lucas> I have a brand new account on tiber
[01:28] <raphink> :)
[01:28] <lfittl> always nice to have :)
[01:29] <segfault> done
[01:29] <raphink> segfault: I believe you don't need debian/conf anymore
[01:29] <lfittl> we only have 2 weeks left for merges, right?
[01:29] <lucas> yes
[01:29] <raphink> segfault: both?
[01:29] <raphink> now let's see if it builds ;)
[01:30] <lfittl> maybe I should work on some :)
[01:30] <segfault> yes i do, it has the conf file which will be linked to /etc/apache2/conf.d
[01:30] <segfault> but i still dont get asked if i want to restart my web server, which should be done in debian/config
[01:30] <raphink> segfault: ok
[01:31] <raphink> wait
[01:31] <raphink> builds fine on my chroot
[01:31] <raphink> now let's update pbuilder and try :)
[01:31] <segfault> i'll update my pbuilder now
[01:32] <raphink> oh, an important point segfault
[01:32] <raphink> this is not compiled code
[01:32] <raphink> so architecture is all, not any
[01:32] <raphink> segfault: in debian/control : architecture: all
[01:32] <segfault> what's the difference?
[01:33] <raphink> segfault: any means it builds on any architecture
[01:33] <raphink> all means it doesn't need to be compiled
[01:33] <slomo> all is one package for all arches, any one package for each arch
[01:33] <sistpoty> hi slomo
[01:33] <segfault> humm, rock
[01:33] <raphink> since this is a php package, you don't need to compile the source, so it's all
[01:33] <raphink> hi slomo :)
[01:33] <slomo> raphink: well, in the case of mono for example it is compiled... but arch indep anyway ;)
[01:33] <slomo> hi sistpoty, raphink :)
[01:34] <raphink> segfault: you'll get a lintian output about Build-Depends-Indep once you change this
[01:34] <sistpoty> slomo: you have main upload rights? could you review a package for me please?
[01:34] <raphink> ignore it, since debhelper is not to be put in Build-Depends-Indep
[01:34] <segfault> ok
[01:34] <raphink> good idea seth_k|lappy
[01:34] <slomo> sistpoty: sure
[01:34] <raphink> I'll do the same then
[01:34] <seth_k|lappy> raphink, maybe we should do it together instead of making him do it twice :P
[01:35] <raphink> that's my idea seth_k|lappy ;)
[01:35] <raphink> I'll do wesnoth
[01:35] <raphink> which one will you do seth_k|lappy ?
[01:35] <seth_k|lappy> http://people.ubuntu.com/~scott/ongoing-merge/superkaramba/
[01:35] <lucas> sistpoty: can you install 'ruby' on tiber ?
[01:35] <sistpoty> slomo: http://revu.tauware.de/details.py?upid=1381 (0.0.8 was uploaded by siretart already)
[01:35] <raphink> ok
[01:35] <lfittl> I think I will join the party and also do a merge :)
[01:35] <sistpoty> lucas: mom...
[01:35] <raphink> wait till I finish to review this package
[01:35] <seth_k|lappy> It's extremely trivial, yet I don't know what the correct way to go is
[01:36] <slomo> sistpoty: ok... will do :)
[01:36] <raphink> sistpoty: you call lucas mom? ;)
[01:36] <seth_k|lappy> so I think I just need some rules-of-thumb and guidelines
[01:36] <raphink> i'l surprised sistpoty ;)
[01:36] <sistpoty> no, mom for moment please ;)
[01:36] <raphink> haha
[01:36] <sistpoty> I guess that's a stupid german shortcut
[01:36] <raphink> ;)
[01:37] <sistpoty> lucas: done
[01:37] <raphink> segfault: ok change the architecture and it's fine for me
[01:37] <lucas> thanks
[01:37] <raphink> :)
[01:37] <segfault> woo, nice
[01:37] <segfault> you checked that debconf stuff?
[01:37] <raphink> segfault: have it reviewed by MOTUs now ;)
[01:37] <raphink> oh no
[01:38] <raphink> I will
[01:38] <raphink> thanks for reminding me
[01:38] <raphink> I will, now
[01:38] <segfault> thanks
[01:39] <raphink> doesnt work
[01:39] <raphink> it asks questions when I run dpkg-reconfigure though
[01:40] <raphink> segfault: just a note on the config/postinst : you could echo a "Restarting roundcube-webmail server..." in postinst
[01:40] <raphink> postinst should not be verbose, but this is nice to read ;)
[01:41] <sistpoty> seth_k|lappy: polyester is nice... looks just like plastik :)
[01:41] <seth_k|lappy> sistpoty, it's shinier :P
[01:41] <sistpoty> yeah
[01:42] <slomo> sistpoty: this new file... you don't do anything with it... is this intentional?
[01:42] <raphink> segfault: on `dpkg --purge roundcube-webmail' : rmdir: /etc/roundcube-webmail: No such file or directory
[01:42] <sistpoty> slomo: what new file?
[01:42] <raphink> check that segfault
[01:42] <slomo> sistpoty: this ppd thing
[01:42] <sistpoty> slomo: no, since it's by far not a good ppd for the 1400W, just s.th. to have a start... (see README.debian)
[01:43] <raphink> well actually no
[01:43] <sistpoty> seth_k|lappy: just a small note: don't install an empty TODO file (actually you might bring this to upstream, that they shouldn't provide a 2-byte empty TODO file ;)
[01:43] <sistpoty> seth_k|lappy: but it's fine as it is
[01:43] <raphink> segfault: you there?
[01:43] <segfault> yes
[01:43] <raphink> ok
[01:43] <segfault> should i remove the rm on purge?
[01:44] <slomo> sistpoty: ok, uploaded :)
[01:44] <raphink> don't both with the --purge stuff segfault
[01:44] <seth_k|lappy> sistpoty, cool :) I'll tell upstream (I have a few other things to tell them too... notice that I had to change orig.tar.gz)
[01:44] <sistpoty> thx slomo
[01:44] <seth_k|lappy> sistpoty, thanks a lot for reviewing it for me :)
[01:44] <lucas> http://tiber.tauware.de/~lucas/versions/universe.html
[01:44] <lucas> new, stable, location
[01:44] <sistpoty> seth_k|lappy: you did? damn I didn't see this... for what reason did you have to change it?
[01:44] <raphink> graet
[01:45] <lucas> I haven't set up the cron yet
[01:45] <lucas> will do tomorrow
[01:45] <seth_k|lappy> sistpoty, it FTBFS'd otherwise. I had to remove configdialog.{h,cc} or the build bombed
[01:45] <seth_k|lappy> sistpoty, that was Riddell's recommended solution.
[01:45] <seth_k|lappy> sistpoty, please see http://seth.pastebin.com/488266
[01:45] <sistpoty> seth_k|lappy: but that's no reason to change the orig-tarball... you can remove them during clean
[01:46] <raphink> segfault: add the echo in postinst though please
[01:46] <seth_k|lappy> sistpoty, hmm
[01:46] <segfault> no problem if it will show 2 messages? the echo one, and the other from the apache2 init script
[01:47] <sistpoty> seth_k|lappy: deletion of files doesn't go into .diff.gz... so it's safe to remove files during clean, that shouldn't be there when the package is built
[01:47] <raphink> segfault: two messages is fine. It just should not be verbose. Two messages for a good reason is fine imo.
[01:48] <seth_k|lappy> sistpoty, okay. Hold off on the upload and I'll look at how to do that with a cdbs rules file (I could do it with a normal one but don't know how with cdbs)
[01:48] <sistpoty> seth_k|lappy: ok... hehe I've got no real clue bout how to do it with cdbs either
[01:50] <sistpoty> seth_k|lappy: no... the orig is called orig because it *is* the upstream tarball. It may only be changed if s.th. in it cannnot be distributed (or repacked if wrong format)
[01:50] <raphink> segfault: give me the new url when its uploaded
[01:52] <segfault> sure, just a minute
[01:52] <raphink> seth_k|lappy: are you doing your merge tonight or shall we do it tomorrow?
[01:52] <raphink> or just wait for crimsun to be there
[01:53] <slomo___> hmm... network troubles :)
[01:53] <slomo___> sistpoty: but it's uploaded now ;)
[01:53] <seth_k|lappy> raphink, just waiting on crimsun
[01:53] <sistpoty> slomo___: cool, thx :)
[01:53] <seth_k|lappy> sistpoty, okay, I found how to change stuff in the clean rule... will fix and reupload
[01:53] <raphink> ok seth_k|lappy
[01:53] <raphink> will do too
[01:53] <slomo___> sistpoty: have fun :)
[01:55] <raphink> segfault: once installed, how are we supposed to access the webmail ?
[01:55] <raphink> ;)
[01:56] <segfault> it must be configured, in /usr/share/roundcube-webmail/config
[01:56] <segfault> tomorrow i'll try to put those stuff in the postinst script
[01:57] <segfault> http://revu.tauware.de/details.py?upid=1392
[01:57] <raphink> segfault: the default system-wide dir for apache is /var/www
[01:57] <raphink> so it might be nice to make a link from /var/www/roundcube-webmail to /usr/share/roundcube-webmail maybe
[01:58] <raphink> so users can access the webmail on http://localhost/roundcube-webmail by default
[01:58] <segfault> that's included in /etc/roundcube-webmail/apache.conf
[01:58] <raphink> I don't seem to see anything in /var/www after the install though
[01:59] <segfault> it won't
[01:59] <segfault> it creates an alias in apache.conf
[01:59] <raphink> why?
[01:59] <ajmitch> morning :)
[01:59] <segfault> which is not updated, by the way
[01:59] <segfault> hehe
[01:59] <raphink> I mean, phpmyadmin creates a link in /var/www
[01:59] <raphink> why wouldn't your package do the same?
[01:59] <raphink> morning ajmitch
[02:00] <segfault> they're different approaches
[02:00] <segfault> with the same result, though
[02:00] <raphink> sure
[02:00] <raphink> as long as they work ;)
[02:01] <segfault> yeah, hehe
[02:01] <raphink> you could add an echo in postrm too, when you restart apache2
[02:04] <raphink> there, commented :)
[02:04] <segfault> done
[02:04] <raphink> ok
[02:05] <raphink> now ask a MOTU to review it :)
[02:05] <segfault> any MOTU around?
[02:05] <segfault> :P
[02:05] <raphink> hehe
[02:05] <segfault> thanks for the help raphink
[02:06] <raphink> you're welcome
[02:07] <raphink> sistpoty: did you get up to my package?
[02:07] <seth_k|lappy> he had to go out for a smoke because my package was so scary :P
[02:07] <raphink> oh yeah right
[02:07] <raphink> LOL
[02:07] <sistpoty> re ;)
[02:07] <sistpoty> raphink: I'm just about it
[02:07] <raphink> re sistpoty
[02:07] <raphink> me me !
[02:08] <sistpoty> +t
[02:08] <seth_k|lappy> haha
[02:08] <raphink> :)
[02:14] <raphink> ok well
[02:14] <raphink> I think I'll go to bed
[02:14] <raphink> seth_k|lappy: merges tomorrow evening ?
[02:14] <sistpoty> raphink: got a minute for kalcul review?
[02:14] <seth_k|lappy> raphink, sure thing
[02:14] <raphink> sure sistpoty
[02:15] <raphink> hopefully wesnoth will still be available for my merge tomorrow :)
[02:15] <sistpoty> raphink: automake1.6 is no longer in the archives, so it ftbfs
[02:15] <raphink> really?
[02:15] <raphink> hmm
[02:15] <raphink> I've got other packages that entered dapper with automake1.6
[02:15] <seth_k|lappy> yeah, 1.{5,7,8,9} are there, but not 1.6
[02:15] <raphink> when was it removed?
[02:15] <sistpoty> raphink: iirc a bug to remove it was filed some time ago in debian
[02:15] <raphink> oh ok
[02:16] <raphink> hmm then let's use 1.9
[02:16] <raphink> by default
[02:16] <raphink> does it build with 1.9?
[02:16] <sistpoty> raphink: the orig-tarball is changed... (some autotools-stuff)... would be good to just do bunzip2 tarball gzip -9 tarball
[02:16] <raphink> seth_k|lappy: 1.5 was removed too it seems
[02:16] <sistpoty> raphink: haven't tried with 1.9 yet
[02:16] <raphink> sistpoty: yeah I removed these stuff from orig tarball because lintian was screaming I think
[02:17] <sistpoty> raphink: and to be picky: in debian/copyright the fsf-address is missing
[02:17] <raphink> hmm
[02:17] <sistpoty> raphink: please just unpack/repack the orig... (without untarring it)... lintian wouldn't complain about autotools-stuff iirc, eventually about cvs or s.th.
[02:17] <raphink> right
[02:18] <raphink> yes maybe cvs
[02:18] <raphink> isn't it in the changelog?
[02:18] <raphink> hmm no
[02:18] <raphink> weird
[02:18] <sistpoty> nope
[02:18] <raphink> i'll repackage ok
[02:18] <seth_k|lappy> sistpoty, I patched it. I am reuploading... mind looking once more in a second?
[02:19] <sistpoty> raphink: if lintian complains about cvs... just ignore it (and complain at upstream) or make lintian quiet
[02:19] <sistpoty> seth_k|lappy: not at all... I guess this will be a trivial change only?
[02:19] <seth_k|lappy> yep, two lines
[02:19] <sistpoty> :)
[02:19] <seth_k|lappy> clean::
[02:19] <rbelem> hello folks
[02:19] <seth_k|lappy> rm -f client/config/configdialog.{h,cc}
[02:19] <seth_k|lappy> :)
[02:24] <seth_k|lappy> sistpoty, I built it again in a pbuilder to make sure my fix worked. It did fine, so reuploading to REVU :)
[02:26] <sistpoty> :)
[02:26] <raphink> sistpoty: argh just remembered I don't have my key here ;)
[02:26] <raphink> shall I give you a diff?
[02:26] <raphink> :s
[02:26] <raphink> or just wait til I get to a comp with my key?
[02:27] <sistpoty> raphink: if you don't mind, just wait till you get to your key... I promise to take a look tomorrow ;)
[02:27] <raphink> ok
[02:27] <raphink> thanks
[02:28] <raphink> I'll work on it tomorrow then
[02:28] <raphink> :)
[02:29] <raphink> good inght
[02:29] <raphink> night
[02:29] <sistpoty> gn8 raphink
[02:29] <raphink> bubbye
[02:31] <seth_k|lappy> sistpoty, http://revu.tauware.de/details.py?upid=1394 :)
[02:32] <sistpoty> seth_k|lappy: k
[02:32] <seth_k|lappy> ty
[02:32] <raphink|sleep> seth_k|lappy: i thought the builddialog stuff would prevent it from building?
[02:32] <raphink|sleep> configdialog stuff sorry
[02:33] <seth_k|lappy> raphink|sleep, correct, but sistpoty had me remove it in the clean:: target instead of from .orig
[02:33] <seth_k|lappy> Riddell said that he and the debian qt/kde maintainers like to change .orig, but MOTUs don't like that :P
[02:33] <raphink|sleep> yes
[02:33] <raphink|sleep> if you remove it in the clean
[02:33] <raphink|sleep> it'll be remove _after_ it's built
[02:33] <raphink|sleep> so it won't build imo
[02:33] <raphink|sleep> it should be removed in a step before building
[02:33] <raphink|sleep> imho
[02:34] <sistpoty> raphink|sleep: iirc clean is called before actual building, but I would have to look at the policy to be sure ;)
[02:34] <raphink|sleep> sistpoty: ok
[02:34] <raphink|sleep> I'm not really sure of it
[02:34] <Riddell> seth_k|lappy: does that work, it'll need to redo the make -f Makefile.cvs
[02:34] <seth_k|lappy> sistpoty, it is
[02:34] <seth_k|lappy> Riddell, it built for me
[02:35] <seth_k|lappy> in a pbuilder
[02:35] <raphink|sleep> bye
[02:35] <seth_k|lappy> bye raphink|sleep :)
[02:35] <seth_k|lappy> that's kinda what I thought Riddell, which is why I built it myself once to make sure
[02:45] <seth_k|lappy> Riddell, did it bomb out?
[02:47] <Riddell> seth_k|lappy: hmm, my chroot has gone weird
[02:47] <sistpoty> seth_k|lappy: built for me, good to upload
[02:48] <sistpoty> Riddell: do you want to review again or can I upload polyester?
[02:49] <Riddell> sistpoty: give me 1 minute
[02:49] <sistpoty> Riddell: sure
[02:54] <Riddell> sistpoty: go for it
[02:54] <sistpoty> Riddell: ok ;)
[02:57] <sistpoty> seth_k|lappy: polyester uploaded
[02:57] <seth_k|lappy> cheers sistpoty, I'll stop bugging you for today
[02:57] <seth_k|lappy> I appreciate it
[02:57] <seth_k|lappy> (stop bugging unless of course you want more stuff to review :P)
[02:57] <sistpoty> you're welcome... thx. for your contribution ;)
[02:58] <sistpoty> well, I guess I'll do one or two merges... and if my girlfriend hasn't come home till then, I'll go for another review ;)
[02:58] <seth_k|lappy> haha
[02:58] <seth_k|lappy> it's a deal
[02:59] <sistpoty> *g*
[02:59] <seth_k|lappy> sistpoty, if she hasn't come home, http://revu.tauware.de/details.py?upid=1378 ;)
[02:59] <sistpoty> seth_k|lappy: k
[03:04] <seth_k|lappy> while you're at it, make it so uploaders can archive their own uploads ;)
[03:05] <sistpoty> seth_k|lappy: will do for revu2 ;)
[03:05] <seth_k|lappy> yay ;)
[03:06] <sistpoty> damn, I should write on it again, otherwise it will never get finished
[03:06] <seth_k|lappy> sistpoty, hum, I think you uploaded polyester twice
[03:06] <seth_k|lappy> I got 2 emails exactly the same
[03:06] <sistpoty> erm... no I uploaded only once
[03:07] <seth_k|lappy> oh well, weird :)
[03:07] <sistpoty> seth_k|lappy: mails from revu or from katie?
[03:09] <hub> can someone unarchive and/or explain the latest comments of http://revu.tauware.de/details.py?upid=840
[03:09] <seth_k|lappy> sistpoty, from katie
[03:09] <sistpoty> seth_k|lappy: that's strange... did she accept or refuse the upload then?
[03:10] <seth_k|lappy> sistpoty, it is NEW so I just got two e-mails with the subject "polyester_0.6.5-0ubuntu1_source.changes is NEW"
[03:11] <sistpoty> seth_k|lappy: no idea really *g*
[03:12] <seth_k|lappy> np :)
[03:12] <at1as> Stupid noob question...  Is anyone else having issues with transcode/libdvdcss2 on ubuntu?
[03:12] <at1as> I'm no longer able to successfully rip and encode my DVDs.
[03:13] <at1as> on Breezy.
[03:13] <hub> at1as: mpaa is watching your back
[03:13] <sistpoty> hub: what's unclear about libiptcdata?
[03:14] <hub> well what is wrong?my latest comment explain all my "observations"
[03:14] <hub> like what is against the policy
[03:15] <at1as> thanks
[03:15] <at1as> At least someone is ;)
[03:16] <sistpoty> hub: for the -doc: usual place would be to install to /usr/share/doc/<packagename>... not quite sure whether gtk-doc might be ok here as well
[03:16] <hub> well, upstream seems to put it there, and don't see obviously how
[03:17] <hub> looks like what gtk-doc generates
[03:18] <hub> sistpoty: there is already a lot of things in my /usr/share/gtk-doc
[03:18] <hub> including rhythmbox
[03:20] <sistpoty> hub: I have no such dir, since I'm using kde... and I have no clue, what would reside in gtk-doc
[03:22] <hub> http://www.gtk.org/gtk-doc/
[03:25] <sistpoty> hub: so devhelp will look in .../gtk-doc? and inside your doc-package is html?
[03:25] <hub> it is
[03:25] <hub> it is generated by gtk-doc
[03:25] <hub> that's why
[03:26] <sistpoty> ah, k... then this seems the right place
[03:27] <sistpoty> (maybe you could add a link into /usr/share/doc, but that would only give extra points for polishing)
[03:28] <sistpoty> for the -dbg package this feels the right place to be... but according to the bug report, you are right ;)
[03:28] <hub> the .so are not .so just symbols
[03:29] <sistpoty> ah, /me learned another lesson :)
[03:31] <dholbach> Lathiat: are you there?
[03:31] <hub> hey dholbach
[03:31] <dholbach> hey hub :)
[03:33] <at1as> hub: Is there actually something that breaks dvdcss in breezy?
[03:34] <at1as> I had no troubles viewing or encoding dvds in warty
[03:34] <hub> at1as: no idea. I have a DVD player under my TV
[03:34] <hub> at1as: so I don't use the DVD on the laptop
[03:34] <hub> at1as: sorry
[03:37] <sistpoty> hub: libiptcdata is fine for me... since the debdiff is small, I'll upload
[03:37] <hub> ok thanks
[03:38] <Kyral> Umm, guys, there is a guy saying he got an email from  K-Concepts Communications Consultants co., LTD saying they contact(contracted?) with Ubuntu
[03:38] <ajmitch> that's interesting
[03:38] <ajmitch> why tell us? ;)
[03:38] <Kyral> because I was hoping someone would know? Because I don't?
[03:39] <ajmitch> what difference would it make?
[03:39] <ajmitch> I've never heard of them
[03:39] <Kyral> dunno, guy is concerne
[03:39] <Kyral> d
[03:39] <ajmitch> about?
[03:39] <Kyral> if its legit
[03:39] <ajmitch> probably not
[03:40] <ajmitch> they probably just use ubuntu
[03:40] <at1as> hub: thanks anyway.  I also have a dvd player, but I also use mythtv, and it is so much easier to view videos if they're on the hd :)
[03:40] <ajmitch> looks to be a taiwanese outfit
[03:40] <Kyral> so I should tell him its prolly sketchy?
[03:40] <hub> at1as: yeah I get that
[03:41] <ajmitch> the last news on their site is from 2002 (at least in the english section)
[03:41] <Kyral> so busted?
[03:41] <minghua> Kyral: who is that guy? BlueT_ on freenode?
[03:41] <ajmitch> who knows?
[03:41] <Kyral> minghua: yah
[03:42] <Kyral> why?
[03:42] <Lathiat> dholbach: yep
[03:43] <hub> dholbach: is there a time I'll get the keys of the universe>
[03:43] <hub> ?
[03:43] <dholbach> Lathiat: could you please join #ubuntu-meeting?
[03:43] <dholbach> hub: keys? universe?
[03:43] <hub> dholbach: to upload :-0
[03:43] <minghua> well, then no big deal, the K-concepts company basically said they _probably_will_ be responsible for the Ubuntu events in Taiwan in the future
[03:43] <hub> dholbach: just wondering:-)
[03:43] <ajmitch> minghua: right
[03:43] <dholbach> hub: talk to elmo about that. write a mail.
[03:43] <ajmitch> minghua: which is quite reasonable
[03:43] <hub> okay
[03:43] <Kyral> minghua: you wanna handle it?
[03:43] <Kyral> minghua: I'm just a programmer lol
[03:44] <ajmitch> considering that there's this asian business tour happening :)
[03:44] <ajmitch> Kyral: as are most people here :P
[03:44] <minghua> Kyral: I don't see them claiming they have contracted from ubuntu, contacted with, maybe, but they are not claiming that either
[03:44] <Kyral> yah but I no good with business things :D
[03:44] <Kyral> minghua: mind PMSGing him?
[03:44] <Lathiat> dholbach: yep
[03:45] <minghua> the letter is at http://bluet.org/~matthew/priv/email-Vicky-kconcepts.txt for those who can read traditional Chinese (I doubt many here :-P)
[03:45] <dholbach> Lathiat: merci, it's a meeting about Dapper Status.
[03:45] <hub> can someone archive this http://revu.tauware.de/details.py?upid=1339
[03:45] <hub> dholbach beat me to upload
[03:45] <dholbach> hub: will do.
[03:46] <minghua> Kyral: I can't handle that either, as I don't know the ubuntu PR department either
[03:46] <dholbach> arg... somebody else archive it please - I don't have my password here.
[03:46] <Kyral> minghua: I just pasted your answer ;P
[03:46] <dholbach> hub: feel free. :-)
[03:46] <hub> dholbach: neither :-/
[03:46] <hub> dholbach: I have to fix something upstream first :-)
[03:47] <minghua> ...
[03:47] <minghua> I can talk with BlueT_, I suppose
[03:49] <sistpoty> hub: archived
[03:49] <hub> sistpoty: thankds
[03:51] <dholbach> thanks Lathiat
[03:56] <psusi> can someone help me figure out how to manage my patch to the udftools package?  it doesn't appear to be using either dbs or dpatch.. it just has patch-n-description.diff files in the debian dir
[04:00] <whiprush> \sh_away: motu transcript story is fridged, I appreciate the CC.
[04:02] <ajmitch> eek
[04:02] <ajmitch> it needed a lot of tidyup
[04:03] <Kyral> lol
[04:22] <sistpoty> gn8 everyone
[04:22] <ajmitch> night
[04:24] <psusi> can someone help me figure out how to manage my patch to the udftools package?  it doesn't appear to be using either dbs or dpatch.. it just has patch-n-description.diff files in the debian dir
[04:24] <psusi> is there another patch management tool I should read up on, or is this just done by hand with diff?
[04:24] <hub> crap
[04:24] <hub> libsane do no install
[05:47] <SEJeff> I just downloaded the source of a program and changed ${packagename}/debian/control and would like to rebuild a binary package from that. How do I do that?
[05:47] <SEJeff> I am very familar with redhat packaging and the equivalent redhat command would be rpmbuild -bb packagename.spec
[05:49] <psusi> SEJeff, I'm in the middle of learning that myself...
[05:49] <psusi> cd ${packagename} and debuild -S
[05:49] <psusi> that will make a new source .deb in ..
[05:49] <psusi> then pebuilder build the_new_source.deb
[05:50] <psusi> err, actually, it is pebuilder build ${packagename}.dsc
[05:52] <psusi> the debuild -S sets up what you would get if you extract a source .deb.. which is the .orig.tar.gz, the .dsc, and so on
[05:54] <psusi> damnit... I keep typing pEbuilder... it's just pbuilder
[06:02] <SEJeff> psusi, pebuilder is for windows live cds :)
[06:02] <SEJeff> psusi, I'll try that out, thanks
[06:03] <psusi> right now I'm trying to figure out how to get it to actually assemble the other files into the .deb ;)
[06:03] <psusi> since I'm satisfied with my changes and the resulting binary package pbuilder generates looks good
[06:07] <SEJeff> psusi, '/usr/bin/dpkg-buildpackage: debian/rules: /usr/bin/make: bad interpreter: Permission denied' I got this problem yesterday with a perl script, any ideas?
[06:08] <psusi> ls -al /usr/bin/make
[06:08] <SEJeff> psusi, -rwxr-xr-x 1 root root 139920 2005-12-16 22:01 /usr/bin/make those are correct
[06:08] <psusi> hrm.... odd
[06:09] <psusi> looks like it is saying it could not execute /usr/bin/make in response to the shbang in debian/rules
[06:09] <psusi> try doing this as root
[06:09] <SEJeff> I had #!/usr/bin/perl -w in a script I wrote and it gave the same thing
[06:09] <SEJeff> psusi, that was the first thing I tried after I got that error... same message
[06:10] <psusi> wonky
[06:10] <psusi> strace it? ;)
[06:11] <SEJeff> psusi, I'm just trying to fix the broken gnome-schedule in dapper as I want to use it. I will try to fix it tomorrow
[06:11] <SEJeff> night
[06:13] <psusi> night
[06:14] <minghua> SEJeff: the simplest way is dpkg-source -b package-version
[06:14] <minghua> SEJeff: package-version being the directory of the whole source tree
[06:15] <minghua> SEJeff: your "bad interpreter" error still look strange though and may be unrelated
[09:25] <zakame> afternoon MOTUs :)
[09:31] <minghua> hi zakame, I have a question for you
[09:31] <minghua> zakame: do you remember requesting a sync on octave2.1 for me?
[09:31] <minghua> it doesn't seem to arrive (yet)
[09:33] <zakame> minghua: no, I haven't requested that, iirc, I was hesitant 'coz someone else may had requested it already ;)
[09:33] <minghua> oh okay
[09:33] <zakame> minghua: if it's not, then I'll do it now :)
[09:34] <minghua> zakame: it is not, so please do, thanks :-)
[09:34] <zakame> minghua: hm last build was on Dec 24
[09:34] <Gloubiboulga> morning
[09:34] <zakame> but 'tis a ubuntu version, so I'll request then :)
[09:34] <minghua> zakame: that's doko's libstdc++ transition rebuild upload
[09:35] <zakame> morning Gloubiboulga
[09:35] <zakame> yep
[10:30] <segfault> any MOTU around?
[10:35] <segfault> http://revu.tauware.de/details.py?upid=1396
[11:39] <segfault> any MOTU around?
[11:40] <jpatrick> segfault: maybe ajmitch ?
[11:41] <segfault> dunno if he's around
[11:41] <zakame> segfault: why? :)
[11:43] <segfault> http://revu.tauware.de/details.py?upid=1396
[11:43] <segfault> :)
[11:43] <segfault> to review it
[12:02] <dholbach> hellas
[12:03] <lfittl> morning dholbach :)
[12:03] <dholbach> hey lfittl
[12:04] <segfault> dholbach: are you busy?
[12:04] <dholbach> segfault: why do you ask? :)
[12:04] <lfittl> he needs a motu for reviewing his package ;)
[12:04] <segfault> dholbach: can you review one package? http://revu.tauware.de/details.py?upid=1396
[12:05] <segfault> its kinda simple
[12:05] <dholbach> segfault: will do in a sec and tell you what i find
[12:05] <dholbach> segfault: need to get up to scratch with mails and the like first
[12:05] <segfault> dholbach: sure, no prob
[12:05] <jpatrick> dholbach: noone has taken a peek at my lmms: http://revu.tauware.de/details.py?upid=1280 :(
[12:06] <dholbach> jpatrick: will do
[12:07] <jpatrick> thanks
[12:10] <Nafallo> wow
[12:10] <Nafallo> 10 packages left for merging. good job guys! :-)
[12:10] <lfittl> Nafallo: don't forget the 190 assigned merges ;)
[12:11] <Nafallo> those are assigned and handled already, no?
[12:12] <lfittl> they are assigned but not fixed, meaning the merge is not done yet
[12:12] <dholbach> who would like to proofread/add-stuff to http://wiki.ubuntu.com/MOTUReportDraft?
[12:12] <jpatrick> dholbach: new MOTU hopefuls: Me
[12:13] <Nafallo> hmm, that means people are working on them atleast :-P
[12:13] <Nafallo> (and what I meant)
[12:13] <lfittl> k, then you are right :)
[12:13] <dholbach> jpatrick: would you care enough to add it?
[12:14] <jpatrick> dholbach: I have to be a member first
[12:14] <dholbach> jpatrick: to the MOTUReportDraft page?
[12:15] <dholbach> segfault: wouldnt you have to depend on *debconf?
[12:16] <segfault> dholbach: humm, i think so... i forgot it. can you tell me why after installing the deb, i dont get asked by debconf if i want to restart the browser?
[12:17] <segfault> err, the web server.
[12:17] <segfault> config seems to be ok
[12:17] <dholbach> segfault: not really, i'd have to compare with other packages to do that
[12:18] <lucas> dholbach: I'd like to add something
[12:18] <lucas> about the fact that lists of package versions are available
[12:19] <lucas> but I still have to do some work on them
[12:19] <lucas> what's your deadline ?
[12:19] <tseng> Ubugtu: seen crimsun
[12:19] <lucas> tseng: he said he was gone for 2 days, been visiting a friend who is ill
[12:19] <dholbach> lucas: just go ahead and add it - i'd like to get the news out, but it's not mission-critical or something
[12:20] <tseng> lucas: thanks.
[12:20] <lucas> can I work on that tonight ? does that fit ?
[12:20] <lucas> I have to do some real-world work sometimes ;)
[12:24] <zakame> hm why is robotour in multiverse?
[12:25] <dholbach> lucas: it's ok :)
[12:40] <Nafallo> hmm, could someone remove pessulus from "new merges" on our mom-interface? :-)
[12:41] <Nafallo> we are newer than debian already :-)
[12:46] <jpatrick> morning raphink
[12:46] <raphink> hi jpatrick
[12:50] <jpatrick> raphink: might want to add yourself here: https://wiki.kubuntu.org/MOTUReportDraft
[12:50] <raphink> what's that for?
[12:51] <jpatrick> next MOTU report
[12:51] <raphink> oh yeah
[12:51] <jpatrick> under "new MOTU hopefuls"
[12:51] <raphink> and seth too
[12:51] <raphink> but i'm not even a member yet
[12:51] <raphink> but ok
[12:51] <jpatrick> just a hopeful
[12:52] <raphink> hop
[12:55] <jpatrick> someone care to poke lmms? : http://dot.kde.org/1113428593/
[12:55] <jpatrick> damn wrong link
[12:55] <jpatrick> http://revu.tauware.de/details.py?upid=1280
[01:41] <segfault> http://revu.tauware.de/details.py?upid=1397
[01:51] <rtcm> hi, is there an RCS where the source packages in ubuntu are maintained?
[02:17] <lucas> it depends on the package
[02:17] <lucas> some of them are just debian's
[02:17] <lucas> some are maintained somewhere in bzr
[02:17] <lucas> etc
[02:17] <lucas> you can get the source for a package by running apt-get source <package name>
[02:18] <lucas> if you have sources lists in your /etc/apt/sources.list
[02:22] <rtcm> lucas: and where can I find the ones that are maintained in a RCS?
[02:27] <azeem> rtcm: there is no easy way to find out, I think
[02:37] <nomed> how can i check if my request to join a team has been sent ?
[02:37] <tepsipakki> nafallo: is there hope to get aac/m4a-support for gtkpod, because otherwise it can't read the metadata from those and syncing fails
[02:37] <tepsipakki> I know about the license..
[02:38] <rtcm> azeem: hmm, ok then, thanks
[02:43] <Nafallo> tepsipakki: I have no idea, I just merged it.
[02:44] <Nafallo> tepsipakki: you should ask MOTUMedia (i.e. slomo ;-)).
[02:45] <Nafallo> what shall we do with linux-kernel-di-*-2.6? merge them?
[02:45] <slomo> tepsipakki: this would mean moving gtkpod to multiverse as the faad/faac is located there...
[02:47] <tepsipakki> slomo: so it's a no-go? would it be ugly to have a "gtkpod-aac" or similar in multiverse?
[02:48] <tseng> it would
[02:48] <tseng> but there isnt another way
[02:48] <slomo> tepsipakki: would be possible if someone does it :)
[02:48] <tseng> if you google a few people have already rolled gtkpod-aac
[02:49] <tepsipakki> i've tried to compile it on breezy, but didn't succeed
[02:49] <tepsipakki> slomo: :)
[02:49] <slomo> what was the problem?
[02:50] <tepsipakki> funny that rhythmbox which is in main, can play stuff from my ipod quite happily
[02:50] <slomo> because it uses gstreamer... and there is a gstreamer plugin for aac/m4a in multiverse which you have installed ;)
[02:50] <tepsipakki> slomo: yeah of course
[02:51] <tepsipakki> slomo: would gtkpod-aac need to have it's own source-package, if it was in multiverse?
[02:51] <slomo> yes
[02:51] <slomo> i.e. a copy of the gtkpod sourcepackage with that very small change...
[02:52] <slomo> ugly duplication but the only way :/
[02:52] <tepsipakki> yes. heck, I might do it after I've upgraded my home computer (not until fglrx works with dapper completely)
[02:53] <tepsipakki> I believe here are plenty of people to push the (source) package once it is done? I'm still just an ubuntero
[02:54] <tepsipakki> or would it mean that the uploader is the maintainer, or can a non-member be?
[02:55] <slomo> you can be the maintainer... and it will be fairly easy to find someone to upload it once it's done and good :) if you have any questions on what changes need to be done etc feel free to ask here ;)
[02:56] <tepsipakki> yes, sure. thanks!
[02:56] <tepsipakki> I've done some packaging before, so it's not completely foreign
[02:57] <slomo> damn, istanbul segfaults :(
[02:58] <tepsipakki> which reminds me that I promised to package libgssapi and librpcsecgss this week..
[02:59] <segfault> slomo: can you review http://revu.tauware.de/details.py?upid=1397?
[03:04] <lucas> segfault: please stop bugging MOTUs about reviews. your priority should be to fix existing software currently, and work on merges and syncs
[03:36] <zakame> evening MOTUs :)
[04:14] <Nafallo> hmm
[04:18] <Nafallo> ajmitch: hi!? :-)
[04:18] <zakame> heya Nafallo
[04:18] <Nafallo> zakame: hi there :-)
[04:19] <Nafallo> anyone knows if we should merge linux-kernel-di-*-2.6 or not? :-)
[04:19] <zakame> hm I remember ajmitch saying not, iirc
[04:19] <Nafallo> why is it still on the mergelist then? :-P
[04:20] <Nafallo> and for pessulus, kmess and kguitar we are already newer than Debian ;-)
[04:20] <Nafallo> so nothing to do :-P
[04:20] <zakame> pretty unsure of it myself... I can't recall what reason was there not to do a merge/sync test on those :)
[04:21] <zakame> indeed, that's why I'm working on my Debian pkgs for a change :P
[04:21] <Nafallo> :-)
[04:21] <Nafallo> I better help my girls clean my computerparts :-P
[04:21] <Nafallo> later all :-)
[04:21] <zakame> and learning cdbs too :)
[04:21] <zakame> cya Nafallo :)
[04:40] <zakame> wow, why didn't I learn cdbs in the first place? :P
[04:42] <ajmitch> because cdbs is evil
[04:42] <zakame> buwahaha voodoo
[04:43] <tseng> <3 voodoo
[04:43] <jamessan> zakame: because it's better to know how things work behind the scenes first :)
[04:43] <tseng> thats why i use ruby on rails
[04:43] <zakame> jamessan: yup :)
[04:44] <ajmitch> tseng: zope 3 all the way
[04:44] <ajmitch> don't you want your apps to turn out like launchpad?
[04:44] <tseng> ajmitch: sigh
[04:44] <tseng> no
[04:44] <tseng> at least use django
[04:44] <tseng> ORM for the win
[04:44] <zakame> jamessan: now I know why Manoj's debian-dir was a bit like cdbs, except for the verbosity
[04:45] <jamessan> zakame: I don't think I've heard of debian-dir before
[04:46] <zakame> jamessan: http://arch.debian.org/arch/private/srivasta
[04:49] <tseng> ajmitch is so advantgard he uses debian-dir with bzr
[04:50] <zakame> w00t
[04:50] <zakame> I've yet to play with bzr :(
[04:51] <tseng> bzr is magic crack
[04:58] <psusi> diff/patch rule all! ;)
[04:58] <ajmitch> tseng: I do?
[05:05] <tseng> ajmitch: something like that, no?"
[05:46] <Yagisan> \sh_away: When you get back I'd like to talk to you about Ubuntu's wine package for dapper. I saw you were the last to touch it, and I'd like to discuss some (future) packaging issues with it. Alternatively, point me in the direction of someone more appropriate.
[05:46] <Yagisan> \sh_away: I'm logged in ATM, but I'll most likely be in bed soon. feel free to msg me.
[05:52] <zakame> gn8 all
[05:53] <greenpenguin13> n8 zakame
[05:54] <zakame> :)
[06:16] <jpatrick> can someone look at http://revu.tauware.de/details.py?upid=1380 ?
[06:51] <\sh> moins
[07:02] <Nafallo> \sh: you have bzr-trees all aspects of gajim? :-)
[07:02] <\sh> Nafallo: sure :)
[07:03] <Nafallo> urls? :-)
[07:03] <\sh> Nafallo: right now it's local only...but I will push them during the weekend on tiber
[07:03] <Nafallo> ah, oki :-)
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:18 gajim-0.9.1
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:28 gajim-0.9.1-debian-copying
[07:04] <\sh> drwxr-xr-x   4 shermann shermann 4096 2006-01-05 18:45 gajim-0.9.1-debian-dir
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:31 gajim-0.9.1-debian-group-patch
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:46 gajim-0.9.1-package
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:24 gajim-0.9.1-ubuntu-human
[07:04] <\sh> drwxr-xr-x   7 shermann shermann 4096 2006-01-05 18:25 gajim-0.9.1-ubuntu-launchpad-integration
[07:04] <\sh> this is my repos :)
[07:04] <\sh> where gajim-0.9.1-package is the merged gajim-0.9.1 tree with all other branches and a nested debian dir branch
[07:05] <\sh> I played before only with diffs between revisions just like svn...
[07:05] <Nafallo> ahh, looks like some stuff isn't in the current uploaded package :-P
[07:05] <\sh> but now I remembered siretarts way of doing things and HCT as well, and this way it's more easier for me to keep track
[07:05] <\sh> what?
[07:05] <Nafallo> gajim-0.9.1-debian-*? :-)
[07:06] <\sh> ah ... I just got rid of the patch system :)
[07:06] <Nafallo> ehm, copying and group patch :-P
[07:06] <\sh> everything is now in the debdiff
[07:06] <\sh> it's in :)
[07:06] <Nafallo> hehe, nice :-)
[07:06] <Nafallo> I never really liked the patchsystem :-)
[07:06] <\sh> the only patch I dropped is the debian xpm stuff
[07:07] <\sh> well...I try to change everything to diff.gz for the packages I brought in :)
[07:07] <Nafallo> hmm, is it really in? it's not in our current debian/patches :-P
[07:09] <\sh> Nafallo: there is no debian/patches anymore I merged the new 0.9.1-2 rev
[07:09] <Nafallo> is that uploaded?
[07:09] <\sh> Nafallo: yes just now
[07:09] <Nafallo> oh
[07:10] <\sh> Accepted gajim 0.9.1-2ubuntu1 (source)
[07:10] <Nafallo> sources is not in the archive yet :-P
[07:10] <\sh> Date:
[07:10] <\sh> 2006-01-05 19:00
[07:10] <\sh> just 10 minutes ago
[07:12] <jpat|away> \sh: can you look at my lmms?: http://revu.tauware.de/details.py?upid=1280
[07:12] <Nafallo> yea, should go in with the :03 run :-)
[07:13] <\sh> Nafallo: it has to compile first :)
[07:13] <Nafallo> no, the source have to go in before it can compile :-)
[07:13] <\sh> jpat|away: sure one moment :) I have to close my bugs first :)
[07:13] <\sh> Nafallo: sure
[07:13] <Nafallo> so I can apt-get source anytime now :-)
[07:13] <\sh> Nafallo: but it takes some time ever :)
[07:14] <slomo> Nafallo: not online in jabber? :P
[07:14] <Nafallo> slomo: ehm, yes I am?
[07:14] <slomo> not for me... hmm
[07:14] <Nafallo> I just sent you "test"
[07:15] <slomo> hmm... nothing happened here... \sh, your server is broken ;P
[07:15] <\sh> slomo: what?
[07:16] <\sh> you mean jabber?
[07:16] <\sh> i'm on :)
[07:16] <slomo> yes... i was connected since 2 hours and now nafallo's messages don't get here ;)
[07:16] <\sh> slomo is offline :)
[07:16] <\sh> nafallo is now online
[07:16] <\sh> slomo is now online
[07:17] <slomo> ah, now it's better
[07:17] <Nafallo> slomo: you got "test :-)"
[07:17] <Nafallo> ?
[07:17] <slomo> no
[07:18] <slomo> Nafallo: did you get my message?
[07:18] <\sh> Nafallo: you got my test it message?
[07:18] <Nafallo> \sh, slomo: nope
[07:18] <\sh> slomo: and my hello message?
[07:19] <slomo> nope
[07:19] <\sh> i'm with kopete now
[07:19] <\sh> and I can see you online
[07:19] <slomo> i see you all online now... but no messages ;)
[07:19] <Nafallo> \sh: you got "test"?
[07:19] <\sh> write something to me pls
[07:20] <\sh> Nafallo: no
[07:20] <slomo> \sh: done... did you get something?
[07:20] <Nafallo> something is wrong somewhere then...
[07:20] <\sh> also not
[07:20] <\sh> but I'm talking to another guy
[07:20] <Nafallo> hmm
[07:20] <Nafallo> so client-server-client broken? :-P
[07:21] <\sh> gajim?
[07:21] <slomo> yes
[07:21] <Nafallo> yes
[07:21] <Gloubiboulga> slomo, do you have some time for a review?
[07:21] <slomo> Gloubiboulga: no... i must leave in -1 minute =)
[07:21] <\sh> try hmm...gaim or psi or kopete to be sure that it's not the server
[07:21] <slomo> Gloubiboulga: but i could add it to my todo list... just give me the url
[07:21] <Gloubiboulga> ok
[07:22] <Gloubiboulga> http://revu.tauware.de/details.py?upid=1362
[07:22] <Gloubiboulga> thanks slomo
[07:23] <slomo> bbl
[07:30] <Nafallo> \sh: did you get the last three messages after "nice..file a bug" ?
[07:31] <\sh> no
[07:31] <Nafallo> xml-console says you didn't :-P
[07:31] <Nafallo> http://paste.ubuntu-nl.org/6656
[07:32] <\sh> what is this shit? ,)
[07:32] <Nafallo> console output :-P
[07:33] <\sh> yes...but Byte has no attribute encoding?
[07:33] <\sh> what they are doing
[07:33] <\sh> it's dbus magic
[07:33] <Nafallo> nice that this gajim is in breezy-backports ;-)
[07:34] <\sh> damn
[07:35] <\sh> are u using the backports version?
[07:35] <Nafallo> nope
[07:35] <Nafallo> my girlfriend is :-)
[07:35] <\sh> and this message is from your gf?
[07:35] <Nafallo> nope, my dapper laptop :-)
[07:35] <\sh> hmmm...
[07:35] <Nafallo> haven't tried to reproduce it on breezy yet.
[07:36] <Nafallo> when did gajim start to use dbus? :-P
[07:37] <\sh> since 0.9?
[07:37] <\sh> and since gajim-remote?
[07:39] <Nafallo> ah
[07:41] <Nafallo> hmm
[07:41] <Nafallo> libnotify is dbus, no?
[07:41] <\sh> no.
[07:41] <\sh> it's libnotify
[07:41] <Nafallo> damn :-P
[07:41] <\sh> it has to do something with gamin bla....
[07:42] <Nafallo> I wonder why it tries to use dbus then... since I have never even touched gajim-remote :-P
[07:42] <\sh> libnotify is messaging dbus for triggering some things..like notifying the taskbar
[07:43] <\sh> IMHO :)
[07:43] <\sh> Need to buy some cigarettes
[07:43] <Nafallo> gaah
[07:43] <Nafallo> this started after the new notify thingie :-P
[07:45] <Nafallo> baah. food now anyway :-P
[07:46] <flujan> hi guys.
[07:46] <flujan> I send a e-mail to the list
[07:46] <flujan> I want to help the motu project
[07:46] <flujan> daniel holbach point me this channel
[07:47] <flujan> i'm not a active irc user, but... let it go!!!
[07:47] <flujan> ;)
[07:47] <flujan> hello
[07:48] <Gloubiboulga> hi flujan
[07:48] <Gloubiboulga> it's very quiet tonight
[07:48] <flujan> hum... i'm in Brazil so here is about 6 pm
[07:48] <flujan> ;)
[07:49] <Gloubiboulga> maybe you should ping dholbach...
[07:50] <flujan> how can I do that?
[07:50] <Gloubiboulga> I just did :)
[07:50] <flujan> ping dholbach
[07:50] <Gloubiboulga> you just have to write his nick
[07:51] <flujan> dholbach
[07:51] <Gloubiboulga> I guess he's away from computer
[07:51] <flujan> hum... ok
[07:58] <dholbach> pong
[07:58] <dholbach> i was on the phone
[07:58] <flujan> hi daniel
[07:58] <flujan> I join the channel but there's no living here. ;)
[07:59] <flujan> so, who is the project leadr?
[07:59] <tseng> there isnt a "leader"
[08:00] <dholbach> sabdfl (Mark Shuttleworth) is the project leader :)
[08:00] <dholbach> flujan: we're trying to do everything as a big family :)
[08:01] <flujan> ok, but someone take the decisions for instance... what package one should maintain
[08:02] <dholbach> everybody decides that in consensus
[08:02] <dholbach> and we do team maintenance
[08:02] <dholbach> but surely respect the area of expertise of others
[08:02] <dholbach> i wouldn't meddle with mono packages, if i didn't have to :)
[08:03] <dholbach> i let tseng and slomo do the dirty work there
[08:03] <flujan> so... i'm not need anything special... I only use postgresql and zope
[08:03] <flujan> ahuaha understood...
[08:03] <dholbach> :)
[08:03] <tseng> yay mono
[08:04] <flujan> So, the multiuniverse packages... Which packages is in the wishlist and are "aproved" to be merged?
[08:04] <flujan> I can take one of this packages and try my best
[08:05] <flujan> ;)
[08:05] <dholbach> there are merges to do, i hope somebody else can introduce you to this
[08:05] <dholbach> there are a *lot* of bugs in launchpad assigned to the 'motu' team, which need cleaning up and triaging
[08:05] <Kyral> ack
[08:05] <dholbach> and if you'd like to package something new, you'd better hurry - dapper has a *very* early upstream version freeze atm
[08:05] <Nafallo> dholbach: are there? only 5 that seems not to be merges on the mom-list-thingie :-)
[08:06] <tseng> dholbach: (how soon again?)
[08:06] <Kyral> I need to complain to hwdata upstream
[08:06] <Kyral> tseng: I was just about to ask that :D
[08:06] <dholbach> tseng: main is definitely 19th of January
[08:06] <tseng> damn
[08:06] <dholbach> tseng: and for Universe we have to ask for 1-2 weeks of delay
[08:06] <Kyral> Universe?
[08:06] <dholbach> tseng: because it'd be unfair
[08:06] <dholbach> i'll try to raise the point
[08:06] <tseng> so we'll get mono 1.1.13.1 maybe
[08:06] <Kyral> Okay I should be able to get yamysqlfront in
[08:06] <dholbach> Dapper wil be rocking stable, so we better hurry, if we want upstream stuff to get in (as well as NEW packages)
[08:07] <dholbach> we will concentrate on fixing up whatever we can after UVF
[08:07] <dholbach> and we'll do well
[08:07] <flujan> is ther orphan packages? With orphan I mean a package without a maintainer
[08:07] <tseng> packages dont have maintainers here
[08:07] <dholbach> flujan: we inherit packages from Debian
[08:07] <Kyral> you got it sir
[08:07] <dholbach> woohoo!
[08:07] <ogra_ibook> flujan, you just grab what you like and work on it :)
[08:08] <ogra_ibook> flujan, no bureaucracy
[08:08] <dholbach> the last two weeks everything will be fixed and we just have to organize the Release Parties - i know it
[08:08] <Kyral> lol
[08:08] <ogra_ibook> haha
[08:08] <Kyral> PARTY!! WOHOO!
[08:08] <segfault> hallo
[08:08] <flujan> ok so... where can i grab something?
[08:08] <Kyral> I can hear Jeff's voice (AGAIN) going "we do NOT have a drinking problem in this project!"
[08:09] <flujan> i like to work with bugfixes
[08:10] <Kyral> then you can complain to hwdata upstream lol
[08:10] <ogra_ibook> just dig through the bugtracker on launchpad.net ... if you find some intresting bugs, grab them and attach a patch to the bug with a fix
[08:11] <flujan> ok
[08:11] <flujan> another thing..
[08:12] <flujan> I worked with slackware since 7.0
[08:12] <Kyral> Actually could we check to see if we could use the hwdata package from Breezy?
[08:12] <flujan> now, I need some help creating packages to ubuntu
[08:13] <ogra_ibook> there are some pages on the wiki that are packaging related ... mainly you should take a look at the debian new maintainers guide
[08:13] <ogra_ibook> thats good for a starting point
[08:13] <Kyral> upstream changed something that borked Kickstart
[08:14] <flujan> ok, so I will check it and will keep an eye in the mailing list
[08:15] <ogra_ibook> yup
[08:15] <ogra_ibook> and hang around here, this is where the main work happens ...
[08:15] <Kyral> Oh if anyone has a sec, archive EasyChem
[08:15] <Kyral> ty
[08:18] <segfault> any MOTU with spare time to review one package?
[08:23] <jpatrick> \sh: I'm here now :)
[08:27] <flujan> hum... there is a lot of bugs that already have a debian patchs ...
[08:27] <Kyral> then ask them to be synced from Debian
[08:27] <jpatrick> dholbach: do you have time for http://revu.tauware.de/details.py?upid=1280 ?
[08:29] <\sh> jpatrick: checking right now
[08:29] <jpatrick> thanks
[08:30] <Nafallo> \sh: #ubuntu-im ? :-)
[08:31] <dholbach> jpatrick: i'm just doing an libxml update and wanted to look in gnome-system-tools and gthumb next
[08:31] <jpatrick> okay
[08:33] <dholbach> hey jdahlin
[08:33] <jdahlin> hi dholbach
[08:34] <dholbach> jdahlin: new kiwi version, or what? ;-p
[08:34] <jdahlin> dholbach: oh, not at the moment :-)
[08:34] <jdahlin> I did release a new gazpacho release a few moments ago thou
[08:34] <jdahlin> however, I was mainly here trying to figure out why dosemu is broken in breezy
[08:35] <dholbach> jdahlin: i asked in #ubuntu-desktop already, who wanted to package it
[08:35] <dholbach> jdahlin: nobody stepped up yet and if nobody does, after i fixed the other updates, i'll do it myself
[08:35] <dholbach> no idea about dosemu though
[08:35] <jdahlin> dholbach: it's in debian, so maybe I should push the debian maintainer
[08:36] <dholbach> i was just having a look into debbugs
[08:36] <dholbach> maybe it's fixed in dapper already and you'd just have to backport the fix
[08:36] <jdahlin> rebuilding dosemu using gcc 2.95 seems to work (it doesn't build with a recent version)
[08:36] <Ubugtu> GCC bug 2: "ICE on template with aggregates" Product: gcc, Component: c++, Severity: normal, Assigned to: unassigned@gcc.gnu.org, Status: RESOLVED, Resolution: FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2
[08:36] <dholbach> argargarg
[08:37] <\sh> how do someone burn mdf images?
[08:39] <lfittl> \sh: convert it to iso by using mdf2iso
[08:40] <\sh> lfittl: which package is this in?
[08:40] <lfittl> mdf2iso ;)
[08:40] <raphink> ;)
[08:41] <\sh> not in breezy
[08:41] <raphink> it's in dapper at least ;)
[08:41] <lfittl> oh sry thought you were on dapper
[08:41] <lfittl> yep it's only in dapper
[08:41] <\sh> ah is it in dapper?
[08:42] <\sh> ok...trying to backport
[08:48] <Gloubiboulga> dholbach, I'm having a look at malone #6437 , should I also change stuff like debhelper version (it's >=4.0.0) ?
[08:48] <Ubugtu> Malone bug 6437: "schedule (Ubuntu) - wrong dependencies" Fix req. for: gnome-schedule (Ubuntu), Severity: Normal, Assigned to: MOTU, Status: New http://launchpad.net/bugs/6437
[08:49] <dholbach> Gloubiboulga: if we require it, yes - else: not really, because we'll have to merge it next time too
[08:49] <Gloubiboulga> ok, I just change the dependencies, and produce a debdiff then
[08:51] <\sh> jpatrick: done
[08:52] <jpatrick> woohoo
[08:52] <jpatrick> next one i have is: http://revu.tauware.de/details.py?upid=1380
[08:54] <LaserJock> hi everybody!
[08:54] <jpatrick> hi LaserJock
[08:54] <Gloubiboulga> hello LaserJock :)
[08:55] <LaserJock> I'm back from the dialup land so hopefully I can get some work done ;-)
[08:55] <Kyral> Yea LJ
[08:59] <LaserJock> wow, I have over 500 packages to upgrade
[09:01] <raphink> LaserJock: same here
[09:01] <raphink> just upgraded 495 packages
[09:01] <raphink> ;)
[09:04] <raphink> wb Kyral
[09:12] <Amaranth> anyone know if python compiled with gcc 3.3 would work with pyqt4 compiled with gcc 4?
[09:12] <Ubugtu> GCC bug 3: "Nested types sometimes not visible" Product: gcc, Component: c++, Severity: normal, Assigned to: nathan@gcc.gnu.org, Status: RESOLVED, Resolution: FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3
[09:12] <Ubugtu> GCC bug 4: "Test PR" Product: gcc, Component: other, Severity: normal, Assigned to: unassigned@gcc.gnu.org, Status: RESOLVED, Resolution: FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=4
[09:12] <Amaranth> *boggle*
[09:12] <Nafallo> LOL
[09:12] <Nafallo> Seveas: !!! ^
[09:13] <Seveas> hehe
[09:13] <Seveas> I added some more zillas :)
[09:14] <Amaranth> gccbug, perhaps?
[09:14] <Seveas> @bugtracker remove gcc
[09:14] <Ubugtu> The operation succeeded.
[09:14] <Nafallo> could it be smartar about 3.3 (dots) ? :-P
[09:39] <raphink> seth_k|lappy: are you around?
[09:39] <seth_k|lappy> raphink, indeed
[09:39] <seth_k|lappy> but I'm about to leave for work
[09:39] <raphink> oh ok
[09:39] <raphink> :)
[09:40] <raphink> I'll see if I can merge wesnoth :)
[09:40] <seth_k|lappy> yeah, go ahead and go for it ;) I won't be back until late
[09:41] <raphink> ok
[09:42] <raphink> ouch
[09:42] <raphink> 32MB debdiff!
[09:42] <jpatrick> ouch
[09:43] <raphink> lol
[09:43] <raphink> big changes in wesnoth :)
[09:43] <raphink> so let's see
[09:43] <seth_k|lappy> well it is a new upstream version, so nurr
[09:43] <raphink> first thing to do is to file a bug, right?
[09:43] <seth_k|lappy> they change a lot of stuff
[09:43] <seth_k|lappy> yes, first file an LP bug with the title 'wesnoth: merge new debian version'
[09:43] <raphink> yes, thankfully ;)
[09:43] <seth_k|lappy> and mark it Accepted and assign it to you
[09:43] <raphink> ok
[09:44] <raphink> manually?
[09:44] <seth_k|lappy> there's no automatic way to do it
[09:44] <raphink> ok
[09:44] <raphink> I'll do my first merge manually
[09:44] <seth_k|lappy> you can use the LPEmailInterface crack to do it all at once though
[09:44] <seth_k|lappy> good luck :P
[09:44] <raphink> this is better to understand how the automatic tool work
[09:44] <raphink> haha
[09:44] <raphink> thanks ;)
[09:46] <raphink> grr spamassassin eats all my CPU
[09:46] <raphink> :s
[09:46] <seth_k|lappy> oh, raphink, I hear the best way is to start with the debian package and the ubuntu patch, and then look at the differences between those two
[09:46] <seth_k|lappy> instead of the other way around
[09:46] <raphink> hmm ok
[09:47] <raphink> so I extract the debian package
[09:47] <raphink> and I look at the ubuntu patch?
[09:47] <raphink> or what?
[09:49] <raphink> do I put MOTU: my name
[09:49] <raphink> even if I'm no MOTU?
[09:53] <Gloubiboulga> good night
[09:53] <raphink> hi glou
[09:53] <raphink> bi
[09:53] <raphink> :s
[09:53] <raphink> hi lucas
[09:53] <jpatrick> raphink: have to get to that meeting :/
[09:53] <raphink> ok
[09:53] <lucas> hi :)
[09:53] <raphink> what meeting?
[09:54] <jpatrick> CC
[09:54] <raphink> jpatrick: CC is not today
[09:54] <jpatrick> I know
[09:54] <raphink> ;)
[09:54] <raphink> I'm sure you'll manage to be there don't worry ;)
[09:55] <jpatrick> if I run...
[09:55] <raphink> anyone knows where I can find a tarball of motu-tools ?
[09:55] <raphink> instead of downloading the files one by one
[09:55] <lucas> raphink: where do you download them from ?
[09:55] <raphink> lucas: I see http://tiber.tauware.de/~shermann/motu-tools/
[09:56] <raphink> but that's not very convenient to download
[09:56] <raphink> a tarball would be nicer
[09:56] <lucas> then bzr branch http://tiber.tauware.de/~shermann/motu-tools/
[09:56] <raphink> ;)
[09:56] <raphink> hmm that's the link I gave
[09:56] <lucas> yeah and I added bzr branch ;)
[09:56] <jpatrick> raphink: http://revu.tauware.de/details.py?upid=1160
[09:56] <raphink> which means?
[09:57] <lucas> do you know what bzr means ?
[09:57] <raphink> jpatrick: not sure this is the same
[09:57] <raphink> yes lucas but I don't know how to use it yet
[09:57] <lucas> ok
[09:57] <raphink> ;)
[09:57] <lucas> install it, and type bzr branch http://tiber.tauware.de/~shermann/motu-tools/
[09:57] <lucas> that's everything you need to know for now
[09:57] <raphink> bzr is a new equivalent to cvs/svn right?
[09:57] <raphink> oh ok
[09:57] <raphink> :)
[09:57] <raphink> thanks
[09:58] <lucas> there's a good bzr tutorial somewhere on the web
[09:58] <lucas> I don't remember exactly
[09:58] <raphink> :)
[09:58] <raphink> I'll look at it later on
[09:58] <raphink> right now I'm wanting to merge wesnoth :)
[09:59] <lucas> ok
[09:59] <lucas> regarding wesnoth, it seems the patch was caused by the -t version not working
[09:59] <raphink> hmm ok
[09:59] <lucas> s/version/option/
[09:59] <raphink> I'll have a look
[09:59] <lucas> looking at the changelog
[10:00] <lucas> so, you just have to download and build the debian version, and see if -t works fine
[10:02] <raphink> bzr branch http://tiber.tauware.de/~shermann/motu-tools/ doesn't seem to work
[10:03] <lucas> erm, it's supposed to
[10:04] <raphink>  $ bzr branch http://tiber.tauware.de/~shermann/motu-tools/
[10:04] <raphink> bzr: ERROR: URLError instance has no attribute 'code'
[10:04] <raphink>   command: '/usr/bin/bzr' 'branch' 'http://tiber.tauware.de/~shermann/motu-tools/'
[10:04] <raphink>       pwd: u'/home/raphink/debs/merges'
[10:04] <raphink>     error: exceptions.AttributeError
[10:05] <raphink>   at /usr/lib/python2.4/site-packages/bzrlib/transport/http.py line 146, in get()
[10:05] <raphink>   see ~/.bzr.log for debug information
[10:05] <raphink> sorry can't acess the pastebin so ;)
[10:07] <raphink> lucas: http://ubuntu.pastebin.com/492353
[10:10] <lucas> it works for me
[10:10] <lucas> ***lucas@blop:/tmp% bzr --version                                           (2)
[10:10] <lucas> bzr (bazaar-ng) 0.6
[10:10] <raphink> ok good
[10:10] <raphink> I'll see about that later on
[10:11] <raphink> I got all the files manually ;)
[10:11] <raphink> [MAIL] 
[10:11] <raphink> method=SMTP or sendmail
[10:11] <raphink> what shall I take ?
[10:11] <dholbach> Have a nice evening - I'm off.
[10:11] <raphink> bye dholbach
[10:11] <lucas> SMTP
[10:11] <raphink> ok
[10:12] <raphink> that seems easier
[10:12] <lucas> sendmail might produce problems if your local mail server is not correctly set up
[10:12] <lucas> raphink: wget -r -np -nH http://tiber.tauware.de/~shermann/motu-tools/
[10:12] <lucas> would have worked too
[10:12] <raphink> ok
[10:12] <raphink> thanks
[10:12] <raphink> :)
[10:13] <raphink> hmm
[10:13] <raphink> I'm using gmail as my mailbox
[10:13] <raphink> can I set that for merges?
[10:13] <raphink> smtp uses a weird port
[10:13] <raphink> oh yes I can set it
[10:13] <raphink> hehe
[10:13] <raphink> sorry
[10:13] <raphink> stupid question
[10:14] <raphink> hop :)
[10:16] <raphink> hmm
[10:16] <raphink> it seems lpbugs.py failed to send
[10:20] <raphink> http://ubuntu.pastebin.com/492373
[10:20] <raphink> :(
[10:20] <raphink> any idea
[10:20] <raphink> ?
[10:21] <raphink> Kyral: did you ever get something like this ? http://ubuntu.pastebin.com/492373
[10:22] <LaserJock> Kyral_: are you testing your irssi+screen or something?
[10:22] <Kyral> no...
[10:22] <Kyral> Yanno how DNS hated my laptop?
[10:22] <Kyral> err
[10:23] <Kyral> Desktop?
[10:23] <Kyral> .....
[10:23] <raphink> :s
[10:23] <Kyral> DIE IMPOSTER!
[10:23] <LaserJock> raphink: you have updated your motu-tools?
[10:23] <raphink> I have just downloaded the last version LaserJock
[10:23] <raphink> and just set it up
[10:23] <Kyral> brb
[10:24] <Kyral> ...I'm gonna restart my machine...
[10:24] <Kyral> this is odd
[10:24] <raphink> LaserJock: any idea?
[10:24] <Kyral> or...
[10:24] <LaserJock> raphink: I used to get stuff like that but I don't anymore, I don't think
[10:25] <raphink> LaserJock: http://ubuntu.pastebin.com/492382
[10:25] <Kyral> Rogue Irssi Session
[10:25] <raphink> these are my settings, if ever there's something wrong in them
[10:25] <LaserJock> raphink: you need auth?
[10:26] <raphink> LaserJock: for gmail yes
[10:26] <LaserJock> raphink: that could be the problem
[10:26] <raphink> why?
[10:27] <LaserJock> raphink: cause I don't need auth and it works for me ;-)
[10:27] <raphink> hehe
[10:27] <raphink> well I have to use the email I use to log to LP right?
[10:27] <Kyral> Yanno how my DNS hated me for a while?
[10:27] <LaserJock> yes, I believe so
[10:27] <lucas> raphink: can you use your provider's SMTP server ?
[10:28] <raphink> lucas: to send from my gmail add ?
[10:28] <raphink> not sure
[10:28] <lucas> you should be able to
[10:28] <raphink> I could try
[10:28] <raphink> ok
[10:28] <raphink> seems to work lucas thanks
[10:28] <raphink> :)
[10:29] <raphink> at least I got no error (yet)
[10:29] <raphink> where do I see if it worked?
[10:29] <lucas> if a bug gets created on LP
[10:30] <raphink> for the wesnoth package ?
[10:30] <lucas> yup
[10:30] <raphink> oh yes I see it :)
[10:30] <raphink> hehe
[10:30] <raphink> hehe
[10:31] <ajmitch> morning
[10:31] <LaserJock> hi ajmitch
[10:31] <raphink> hi ajmitch
[10:34] <LaserJock> ajmitch: do you have a minute to review plotdrop?
[10:34] <ajmitch> nope
[10:34] <LaserJock> oh well ;-)
[10:35] <hub> ajmitch: I went dapper directly
[10:35] <ajmitch> hub: I'll put up some info on the laptop testing pages
[10:36] <hub> canonical laptop?
[10:37] <ajmitch> no, that was nicked in montreal
[10:37] <hub> ah
[10:37] <ajmitch> this is a new one I got about 30 min ago
[10:37] <hub> yeah I got that
[10:38] <hub> ajmitch: ah. I wiped windows
[10:38] <hub> to claim my refund
[10:38] <ajmitch> heh
[10:39] <raphink> can anyone take me through my merge so I do it properly?
[10:39] <raphink> :s
[10:41] <raphink> lucas: from extracting the source and look at the files, it seems the -t stuff has been restored in Debian, too
[10:41] <raphink> lucas: and there's no patch to be checked
[10:41] <raphink> lucas: so I should sync?
[10:41] <lucas> you tested ?
[10:41] <lucas> please describe 'it seems' :-)
[10:42] <raphink> hehe
[10:42] <raphink> well
[10:42] <raphink> ok
[10:42] <raphink> in the _ubuntu.debdiff
[10:42] <lucas> also, remember that you have to check that the package builds on dapper
[10:42] <lucas> ideally using pbuilder, or within a quite clean chroot
[10:42] <raphink> I see that the diff described in changelog was on wesnoth-1.0.2/debian/wesnoth-data.install
[10:43] <raphink> the ubuntu package had restored a line in this
[10:43] <raphink> I extracted the new debian package
[10:43] <raphink> and checked that this line is there
[10:43] <lucas> ok
[10:43] <raphink> :)
[10:43] <lucas> build, install, test :-)
[10:43] <raphink> now I should just check if it build in my dapper pbuilder
[10:43] <raphink> :)
[10:44] <raphink> so updating it :)
[10:45] <raphink> that's all that is to do, right?
[10:46] <lucas> yes
[10:46] <raphink> ok :)
[10:46] <raphink> I use pbuilder for all my reviews
[10:46] <raphink> in addition to using dchroot to test debuild && debuild -S -sa
[10:47] <raphink> :)
[10:48] <hub> ajmitch: what kind of laptop is it?
[10:51] <ajmitch> hub: acer travelmate
[10:51] <ajmitch> P-M 2GHz, 1GB RAM, 100GB HDD
[10:51] <ajmitch> should be good enough to compile a bit of stuff
[10:52] <hub> I don't have that big
[10:52] <hub> still way better than my old and desktop
[10:54] <raphink> ooh nice laptop
[10:54] <raphink> :)
[10:55] <raphink> checking for Py_Finalize in -lpython2.4... no
[10:55] <raphink> checking for Py_Finalize in -lpython2.4... (cached) no
[10:55] <raphink> checking for Py_Finalize in -lpython2.4... (cached) no
[10:55] <raphink> configure: error: Python development libraries required
[10:55] <raphink> make: *** [config.status]  Error 1
[10:55] <raphink> pbuilder: Failed autobuilding of package
[10:55] <raphink> :( :(
[10:55] <raphink> what's that ?
[10:55] <raphink> the package depends on python-dev (>=2.3)
[10:55] <raphink> and I saw it install
[10:55] <raphink> :s
[10:56] <Kyral> Damn there are a lot of updates
[10:58] <Kyral> This prelink is gonna HURT
[10:58] <raphink> grrr FTBFS
[10:58] <raphink> and I don't get why!
[10:59] <Kyral> it tells you
[10:59] <raphink> yes it tells me
[10:59] <raphink> Python development libraries required
[10:59] <Kyral> yah
[10:59] <raphink> but they are installed
[10:59] <raphink> so it doesn't help
[10:59] <Kyral> dlocate -S Py-Finalize?
[11:00] <raphink> nothing
[11:00] <raphink> :
[11:00] <raphink> :s
[11:00] <raphink> do you think this is a bug with python dev ?
[11:01] <lucas> wow
[11:01] <lucas> apt-cache is sooooo broken
[11:01] <lucas> I mean apt-cache depends and apt-cache rdepends
[11:01] <Kyral> broken in a good way or?
[11:02] <lucas> it's not believable
[11:02] <Kyral> lucas calm down
[11:02] <Kyral> breath
[11:02] <Kyral> broken good or broken bad
[11:03] <lucas> apt-cache --important --recurse depends amavisd-new |less
[11:03] <Kyral> ...?
[11:03] <lucas> see how it ends up listing ruby as a recursive dependancy
[11:03] <Kyral> on?
[11:03] <lucas> amavisd-new suggests apt-listchanges
[11:03] <lucas> apt-listchanges depends on ruby
[11:03] <lucas> so amavisd-new "recursively-depends" on ruby
[11:04] <lucas> even if there's a suggest in between
[11:06] <raphink> I don't get what's wrong with this python stuff :s
[11:07] <ajmitch> raphink: it is in python2.4-dev, really
[11:07] <raphink> ajmitch: ok so python2.4-dev is broken?
[11:07] <lucas> [22:55:47]  <raphink> the package depends on python-dev (>=2.3)
[11:07] <lucas> does it build-dep or dep on it ?
[11:08] <raphink> build-dep lucas
[11:08] <raphink> and I checked pbuilder was installing it
[11:08] <ajmitch> raphink: no it's not broken
[11:08] <ajmitch> raphink: your package is the one that is broken
[11:08] <raphink> hmm
[11:08] <raphink> ajmitch: does that mean I have to patch configure?
[11:08] <lucas> somebody good at perl here ?
[11:09] <ajmitch> raphink: you do what is needed to fix it cleanly
[11:09] <raphink> ok
[11:09] <lucas> I'd need a very small patch to apt-rdepends
[11:09] <lucas> but my perl really sucks
[11:22] <lucas> nobody knowing even basic perl here ?
[11:22] <hyakuhei> how basic?
[11:27] <LaserJock> man, I wish there was a #ubuntu-advanced or something
[11:27] <raphink> hmm
[11:28] <lucas> for my $opt (@configoptions) {
[11:28] <lucas>   my $o;
[11:28] <lucas>   my $v;
[11:28] <lucas>   ($o, $v) = split(/\=/,$opt,2);
[11:28] <raphink> my pb seems to come from the transition python2.3 -> python2.4
[11:28] <lucas> how can I write this in a cleaner way ? :)
[11:29] <raphink> debian hasn't gone through the python2.4 transition yet?
[11:29] <hyakuhei> 2.4.2 in ubuntu breezy
[11:30] <raphink> hmm
[11:30] <raphink> FTBFS on sid too
[11:30] <raphink> :s
[11:30] <lucas> seems strange that a package that FTBFS is in debian
[11:31] <raphink> well the merged one from MoM
[11:31] <raphink> is FTBFS on sid
[11:31] <raphink> checking for Py_Finalize in -lpython2.3... no
[11:31] <raphink> checking for Py_Finalize in -lpython2.3... (cached) no
[11:31] <raphink> checking for Py_Finalize in -lpython2.3... (cached) no
[11:31] <raphink> configure: error: Python development libraries required
[11:31] <raphink> make: *** [config.status]  Erreur 1
[11:31] <raphink> debuild: fatal error at line 768:
[11:31] <raphink> dpkg-buildpackage failed!
[11:32] <raphink> (sid)
[11:32] <raphink> ;)
[11:32] <raphink> in my sid chroot
[11:32] <raphink> that I just updated
[11:32] <raphink> sure
[11:32] <raphink> :)
[11:32] <raphink> I'll try with the debian source
[11:32] <raphink> and if it works I'll check the diff
[11:33] <lucas> ah
[11:33] <lucas> which source did you tried ?
[11:33] <lucas> the MoM one ?
[11:33] <raphink> yes
[11:33] <lucas> never trust the MoM sources
[11:33] <raphink> since the MoM source doesn't build in dapper
[11:33] <raphink> I tried to build it in sid
[11:33] <raphink> and it doesn't build either
[11:33] <raphink> so I'll try to build the debian source in sid
[11:33] <lucas> syncing means overriding local changes by using the debian source instead
[11:34] <raphink> and if it works (it shoudl work) try to find where in the diff it fails
[11:34] <lucas> the sources on MoM are often broken
[11:34] <raphink> lucas: so what do I do?
[11:34] <lucas> use the debian sources
[11:34] <raphink> oh ok
[11:34] <lucas> do you know how to get them ?
[11:34] <raphink> I try to build the package in dapper from the debian sources?
[11:34] <lucas> yup
[11:34] <raphink> well I apt-get source in my sid chroot ;)
[11:34] <raphink> hehe
[11:35] <lucas> heh
[11:35] <raphink> that works ;)
[11:35] <raphink> and now I just have to leave the chroot and build in dapper
[11:35] <raphink> hmm interesting
[11:35] <lucas> (just a little advertisement for mdt)
[11:35] <raphink> ;)
[11:35] <raphink> not sure I'll remember it though
[11:35] <raphink> :)
[11:36] <lucas> syntax is 'mdt <command>'
[11:36] <raphink> ok
[11:36] <raphink> :)
[11:36] <lucas> command here is 'dist-apt-get <distrib> <subcommand>'
[11:36] <lucas> dist-apt-get means running apt-get with the apt database from <distrib>
[11:36] <raphink> lucas: so if the debian source builds in dapper
[11:36] <raphink> and I checked the change made in ubuntu previously was in the debian source
[11:36] <raphink> it goes for sync
[11:37] <raphink> right?
[11:37] <lucas> exactly
[11:37] <raphink> just geting sure I understand everything
[11:37] <raphink> what's the use of the MoM source?
[11:37] <raphink> if it's broken most of the time
[11:37] <ajmitch> it's not broken most of the time
[11:37] <raphink> it's just a merge suggestion?
[11:37] <lucas> I use MoM because it's the easiest way to get the diffs
[11:37] <ajmitch> and yes it's a merge suggestion
[11:37] <raphink> hmm
[11:38] <ajmitch> blindly trusting it is bad
[11:38] <raphink> what exactly is the -1ubuntu1 source provided by MoM
[11:38] <ajmitch> but so is ignoring it
[11:38] <raphink> ?
[11:38] <raphink> and how is it gotten?
[11:38] <ajmitch> it's the debian & ubuntu changes merged automatically
[11:38] <raphink> ok
[11:38] <lucas> yup, debian source + merge patch
[11:38] <raphink> ok
[11:38] <raphink> where does the merge patch come?
[11:39] <lucas> probably from interdiff between ubuntu and debian patches
[11:39] <lucas> but not sure at all
[11:39] <raphink> hmm
[11:39] <ajmitch> plus some more magic
[11:39] <raphink> so the easiest thing is to check first if the Debian source builds in dapper
[11:39] <raphink> without a change?
[11:39] <ajmitch> it's more than just a simple diff call
[11:39] <raphink> and then check if the previous patches from ubuntu were merged
[11:39] <raphink> ?
[11:39] <ajmitch> I'd check the source first
[11:39] <lucas> raphink: no, the first check the changelogs
[11:39] <lucas> to know what happened
[11:40] <lucas> then, the source, to know exactly what happened :)
[11:40] <raphink> ajmitch: what source?
[11:40] <raphink> ajmitch: the debian one? the ubuntu one? the mom one?
[11:40] <ajmitch> I go for the ubuntu debdiff first
[11:40] <ajmitch> looking at the changelog
[11:40] <ajmitch> and see what is in the merge debdiff
[11:40] <lucas> ah, /me prefers to go second for the debian debdiff
[11:41] <ajmitch> I look at that last :)
[11:41] <lucas> or directly the debian source, depending on the complexity of the changes
[11:41] <lucas> raphink: both are corrects, and you might prefer a third solution
[11:41] <ajmitch> sigh, this laptop doesn't go into native resolution on a breezy install
[11:41] <ajmitch> what a pain
[11:41] <raphink> I guess I just have to find my way
[11:42] <raphink> the thing is that I really have to understand all the steps anyway
[11:42] <raphink> to not forget one
[11:42] <lucas> well, when you have understood everything, just add/improve MOTUMerging
[11:42] <raphink> sure
[11:42] <raphink> :)
[11:47] <raphink> lucas: ok now looking in the _real_ debian source (instead of mom) and understanding a bit better (hopefully) what's going on, I see that the -t stuff in wesnoth-data.install was NOT merged in Debian
[11:47] <raphink> ;)
[11:47] <lucas> :-)
[11:47] <raphink>  $ grep scenario  wesnoth-data.install
[11:47] <raphink> debian/tmp/usr/share/games/wesnoth/data/scenarios/multiplayer
[11:47] <raphink> debian/tmp/usr/share/games/wesnoth/data/scenarios/tutorial
[11:47] <lucas> then check if you can reproduce the bug
[11:47] <raphink> so that means we need to apply it again
[11:47] <raphink> ;)
[11:47] <raphink> I guess
[11:47] <lucas> (maybe it was fixed in another way)
[11:47] <lucas> if it isn't, prepare the merge
[11:47] <raphink> hmm
[11:48] <raphink> you mean compiling the package and checking if -t works?
[11:48] <lucas> yes
[11:48] <raphink> ok
[11:48] <raphink> it's building in my pbuilder rightnow
[11:48] <raphink> long build ;)
[11:48] <raphink> 43MB sources
[11:48] <raphink> so I'll go prepare a tea while it's building
[11:48] <lucas> and don't forget to read https://wiki.ubuntu.com/ContributingToDebian to know how to report the bug to debian (if not already reported)
[11:48] <raphink> :)
[11:48] <lucas> so next time, you can do a sync instead of a merge
[11:49] <raphink> mhm
[11:49] <raphink> lucas: I wrote this page with you, so I read it several times already ;)
[11:49] <lucas> yep I know, but I'm just playing a personal game of mentioning as often as possible here :)
[11:50] <lucas> also, make sure to put as much info as possible in the changelog (launchpad bug number, debian bug number). So next time it's much easier to understand what was the bug, and check if it was fixed in debian.
[11:51] <raphink> ok
[11:51] <raphink> pfiew huge work ;)
[11:53] <raphink> :)
[11:55] <Kyral> gah....beagled is still busted
[11:58] <raphink> lucas: faster way : installing wesnoth in my sid chroot and testing -> unknown scenario 'test'
[11:59] <lucas> works too, but what if the bug was caused by ubuntu, not debian ?
[11:59] <raphink> I don't think so
[11:59] <raphink> it's just linking to a campaign named root
[11:59] <lucas> (a bug which only shows up on ubuntu, not on debian)
[11:59] <raphink> or so
[11:59] <raphink> and if it doesnt work in the sid chroot
[12:00] <raphink> I doubt it works in a real sid
[12:00] <lucas> yeah I know, it was just to mention that
[12:00] <lucas> it's just better to check on dapper
[12:00] <lucas> depending on the fixes, it might not be necessary
[12:00] <raphink> yes but while it's compiling in dapper
[12:00] <lucas> ah ok
[12:00] <raphink> at least I can check that it doesn't work in sid
[12:00] <lucas> yes, true
[12:01] <lucas> so it allows you to file a better bug in debian too :-)
[12:01] <lucas> what's the LP bug id of the missing scenario bug ?
[12:01] <lucas> (or URL)