=== Red-Sox [n=jonny@unaffiliated/red-sox] has joined #ubuntu-classroom === merriam_ [n=merriam@85-211-21-215.dyn.gotadsl.co.uk] has joined #ubuntu-classroom === sacater [n=sacater@ubuntu/member/colchester-lug.sacater] has joined #ubuntu-classroom === croppa [n=stuart@135.27.233.220.exetel.com.au] has joined #ubuntu-classroom === xeruno [n=xeruno@cable200-116-11-46.epm.net.co] has joined #ubuntu-classroom === PWill [n=paul@unaffiliated/pwill] has joined #ubuntu-classroom === tonyyarusso [n=anthony@ubuntu/member/tonyyarusso] has joined #ubuntu-classroom === Crusher [n=You@ppp121-45-43-149.lns10.adl2.internode.on.net] has joined #ubuntu-classroom === ubuntulog [i=ubuntulo@trider-g7.fabbione.net] has joined #ubuntu-classroom === Topic for #ubuntu-classroom: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts === Topic (#ubuntu-classroom): set by nalioth at Fri Jun 8 21:28:23 2007 === croppa [n=stuart@135.27.233.220.exetel.com.au] has joined #ubuntu-classroom === elkbuntu [n=melissa@ubuntu/member/elkbuntu] has joined #ubuntu-classroom === PriceChild [n=pricechi@ubuntu/member/pdpc.supporter.student.PriceChild] has joined #ubuntu-classroom === dholbach [n=daniel@ubuntu/member/dholbach] has joined #ubuntu-classroom [01:47] MOTU Q&A session in 12 minutes === flohack [n=hacki@chello084115131198.3.graz.surfer.at] has joined #ubuntu-classroom [01:48] HEY flohack [01:49] Hi! I'll wait until 14.00 before I repost my question === jussi01 [n=jussi@oul088-gw3.netplaza.fi] has joined #ubuntu-classroom [01:49] heya jussi01 === BugMaN [n=BugMaN@nat.cabi.uniroma1.it] has joined #ubuntu-classroom [01:49] hi dholbach :) [01:49] hi === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #ubuntu-classroom === flohack is back [01:49] hey guys :) === jussi01 hugs Hobbsee Hello! [01:49] hiya! === Hobbsee is not here === porthose [n=charliej@67.60.186.55] has joined #ubuntu-classroom === siretart [i=siretart@ubuntu/member/siretart] has joined #ubuntu-classroom === TheMuso [n=luke@ubuntu/member/themuso] has joined #ubuntu-classroom === Goliath23 [n=david@vidsolbach.de] has joined #ubuntu-classroom [01:57] hi-bye Hobbsee :) === DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-classroom [01:59] hello everybody - welcome to another MOTU Q&A session [01:59] if you're here for the session, please quickly introduce yourself :-) [02:00] I'm Daniel Holbach, MOTU for quite a long time now and trying to make it as easy as possible to join the developer crowd - if you still have questions after the session, please mail me with anything [02:00] Who else do we have here? :-) === seb128 [n=seb128@ubuntu/member/seb128] has joined #ubuntu-classroom [02:00] Hi! I'm one of the developers of ktikz, a small application designed for scientific writers who use TikZ for drawing their illustrations. I try to get ktikz into Ubuntu :-) [02:01] great to have you here flohack [02:01] Hi. I am Luke Yelavich, a MOTU since January, and packaging lead for the UbuntuStudio project, as well as a regular accessibility team contributer. [02:01] seb128: we're going through a round of introductions atm [02:01] Don't laugh at the name ktikz please...not one of my most creative inventions I know gg [02:02] Hi, I'm Sebastien and I'm working on the Ubuntu Desktop for canonical [02:02] flohack: don't worry - I think there are names for software that are worse :) [02:02] anybody else? [02:02] Hi! I'm Maurizio, i try to improve my skills on packages activities === AstralJava [n=jaska@e82-103-217-184.elisa-laajakaista.fi] has joined #ubuntu-classroom [02:02] great to have you here, BugMaN [02:02] hey, I'm Lyz, I do some software packaging for Debian, will sort of be lurking (I'm at work) but am interested in starting to pick up on how things work in MOTU === adam_b [n=adam@bumble.xosia.com] has joined #ubuntu-classroom [02:03] AstralJava, adam_b: we're going through a quick round of introductions atm - nice you are stopping by :) [02:03] pleia2: excellent [02:03] Hi I packaged ampache for debian, just hanging out [02:04] porthose: nice to see you again [02:04] :) [02:04] ok, maybe everybody else will introduce themselves during the session; let's go :-) [02:04] the documents I can suggest to all those of you who are new to packaging are [02:04] - https://wiki.ubuntu.com/MOTU (of course) [02:05] - https://wiki.ubuntu.com/MOTU/Recipes (to start playing with tools you use for packaging everyday) [02:05] - https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/ (to look up whatever might be new to you) [02:06] https://wiki.ubuntu.com/MOTU/Documentation (has important links to all kinds of packaging docs) [02:06] who of you started packaging new software or working on existing packages already? === agoliveira [n=adilson@201.22.83.196.adsl.gvt.net.br] has joined #ubuntu-classroom [02:07] new [02:07] I just uploaded ktikz to REVU, could someone please give me a link to the review procedure, or explain? Do I have to ask someone here for a review explicitly, or are you reviewing packages all the time and should I just wait until my package is reviewed? [02:07] Hei, Im Jussi, Im a motu mentoree - hopefully one day I'll get to MOTU. Im also part of the ubuntu studio team [02:07] so that would be new then [02:07] flohack: yes, that's a NEW package === agoliveira [n=adilson@201.22.83.196.adsl.gvt.net.br] has left #ubuntu-classroom [] [02:08] flohack: good question... the MOTU policy says that two MOTUs will have to give a positive review for your package [02:08] Yes that's clear from the docs [02:08] Since we are close to a release, bug fixing is more of a priority at the moment, so your package likely won't be looked at till next cycle. [02:08] flohack: you can ask for reviews on #ubuntu-motu on the ubuntu-motu-mentors@ mailing list, but at the moment we're in NewPackagesFreeze [02:08] so we're focusing more on existing bugs, etc [02:08] dholbach: That too. [02:09] flohack: but it does not hurt to send a mail to ubuntu-motu-mentors@; somebody with a bit of free time will look after your package [02:09] I thought that was just for main atm...but you just released beta...which probably introduced the freeze i suppose [02:09] flohack: The freeze has been in place for a few weeks actually. [02:09] http://wiki.ubuntu.com/GutsyReleaseSchedule has more info on all the freezes === Baby [n=miry@195.37.62.208] has joined #ubuntu-classroom [02:09] During next release cycle will MOTU be reviewing packages in PPA's === norsetto_ [n=Cesare@host49-197-dynamic.19-79-r.retail.telecomitalia.it] has joined #ubuntu-classroom [02:10] porthose: yes, if they have bugs with needs-packaging assigned to them [02:10] porthose: They would be better on revu, as there is a comments system that allows for viewing of what has been reviewed, and what needs work etc. [02:10] IMO [02:10] Is FeatureFreeze the relevant deadline for new Universe packges? [02:11] yes, it's as TheMuso says; we currently are in a state where we have not integrated the PPA system into our review processes fully yet [02:11] Cool Thx [02:11] flohack: yes, https://wiki.ubuntu.com/FeatureFreeze [02:12] Who of you worked on existing packages already? Like applied a patch? [02:12] me :-) [02:12] me [02:12] me sometimes :) [02:12] o/ [02:13] great :) [02:13] how did you get your packages uploaded? [02:14] first of all, I'm pleased to see that you are working on existing packages like that - that's one thing I like about MOTU: if there's a bug that bothers you, it's very easy to just change it and get things fixed === ian_brasil [n=ian@dasasob.nokia.com] has joined #ubuntu-classroom === huats [n=huats@194.98.120.3] has joined #ubuntu-classroom [02:14] did you make use of https://wiki.ubuntu.com/SponsorshipProcess to get the change included in Ubuntu or did you ping somebody to get it done? [02:15] yes, usual i'm subscribe bug to universe or main sponsors [02:15] no, pinged === Riddell [i=jr@kde/jriddell] has joined #ubuntu-classroom [02:15] nice page to know though :) [02:16] BugMaN: nice [02:16] jussi01: yeah, it's good to use that process, because you're not blocked on individual persons, who might or might not have time [02:16] dholbach: i done that via LP and not with a tool [02:16] Thank you very much for helping! Unfortunately I have to get back to my thesis. Keep up the good work! [02:16] jussi01: also you get input from not just one, but lots of different people [02:16] flohack: let me know how your attempts at becoming a MOTU go [02:17] I'll do! [02:17] flohack: I'm keen to see you on that team and keen to see you project in Ubuntu soon [02:17] rock on! [02:17] thanks! === flohack [n=hacki@chello084115131198.3.graz.surfer.at] has left #ubuntu-classroom [] [02:17] BugMaN: yeah that's fine too; as long as ubuntu-*-sponsors are on the bug [02:17] does anybody have any concrete questions? === DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-classroom [02:17] any package or problem we could take a look at together? [02:18] dholbach: is there a list of things you need to know for becoming a motu? [02:19] jussi01: good question [02:19] jussi01: no, there's not; but the process is very easy and very straight-forward [02:19] My answer to that would be, you can't know everything, but you need to know where to go to get the answers you seek. === slytherin [n=Salazar@pdpc/supporter/base/slytherin] has joined #ubuntu-classroom [02:19] 1) basically you contribute changes, new packages, patches, etc by the process described above [02:20] THings you do need to know, are how to read and understand diffs, understand the commonly used files in the debian directory, and how a package goes together. [02:20] 2) at some stage your sponsors tell you "hey man, you should be able to do this yourself; you're doing good work" [02:20] 3) you send a small application to the MOTU Council [02:20] 4) You become MOTU [02:20] ahhh :) [02:20] https://wiki.ubuntu.com/MOTU/Hopeful/Recruitment is the process for that [02:20] cool. thank you [02:20] it's really straight-forward and it takes people like norsetto just a few weeks ;-) === dholbach hugs norsetto === norsetto hugs dholbach back [02:21] (and people like jussi01 a few years...lol) [02:21] but TheMuso has a good point: it's really important to know who to ask and when to ask other people [02:21] that's why it's good to be on the ubuntu-motu and ubuntu-motu-mentors mailing lists and ask people if you're unsure [02:21] also to get your packages reviewed by a variety of people [02:22] jussi01: I doubt that :-) [02:22] Agreed. Getting known amongst the MOTUs, means a better chance of becoming one yourself. === gpocentek [i=gauvain@ubuntu/member/gloubiboulga] has joined #ubuntu-classroom [02:22] hey gpocentek [02:22] hello dholbach [02:22] dholbach: :) One more question - is it necessary to become an ubuntu member before becoming a motu? [02:22] jussi01: No. [02:23] jussi01: no, motu membership includes ubuntumembers membership [02:23] ok. :) [02:23] if you want to get involved with the MOTUs and don't know what to work on: https://wiki.ubuntu.com/MOTU/TODO has a variety of easy bugs and packages to fix [02:23] for example the weekly bitesize tasks at the bottom of the page [02:23] jussi01: and you will notice that everyone is very nice with you when you start (even after ofcourse...) === TheMuso has been trawling the big pile of universe bugs lately, and found a fair few that he could fix. [02:24] huats: very true :) [02:24] SO theres plenty there, just be prepared to do some bug triaj along the way. :p [02:24] https://launchpad.net/ubuntu/+bugs?field.tag=unmetdeps for example [02:24] jussi01: a little word of advice from a fresh motu: don't be shy or afraid to ask, ask, ask, and when in doubt ask. oh, and ask [02:24] that's a list of bugs of packages that are not installable in gutsy at the moment === jussi01 needs to head home from work, will catch you all later. [02:25] jussi01: Thanks for dropping by. [02:25] norsetto: thanks...dont worry... I do [02:25] jussi01: see you around and let me know how things go [02:25] hi ..i have just ported a couple of apps to ubuntu mobile. I assume that I need to make the .deb packages now and then ping someone when it is done ..is this the correct procedure. Also is there a canonical tutorial for packaging? [02:25] dholbach: for those bugs it's better to have a pbuilder envy for gutsy to test? [02:25] dholbach: np. I will [02:25] BugMaN: and probably a chroot to test-install the packages in afterwards [02:25] BugMaN: but yeah, that's a requirement [02:26] dholbach: [02:26] dholbach: ok [02:26] dholbach: Do we have a good document explaining what a chroot is? [02:26] ian_brasil: I can paste you a few documentation links I mentioned at the beginning of the session [02:26] cool [02:26] TheMuso: DebuggingProgramCrash has one I think [02:26] dholbach: ah ok. [02:27] sudo mkdir /chroots; sudo debootstrap gutsy /chroots/gutsy should work I think [02:27] (getting debootstrap from -backports is necessary for that) [02:27] TheMuso: I find this very good https://wiki.ubuntu.com/DebootstrapChroot [02:27] ah nice [02:27] norsetto: Yeah thats another good one, but it uses the slowly phasing out dchroot. [02:28] ian_brasil: after that uploading them and asking for review using http://wiki.ubuntu.com/SponsorshipProcess will get you reviews for those packages [02:28] TheMuso: yes, but it says so ;-) [02:28] I use LVM snapshots with chroots and sbuild personally. [02:28] ian_brasil: after having gone through a bunch of successful sponsored uploads, people will ask you to become a MOTU yourself and you can send an application to the MOTU Council [02:29] ian_brasil: that's basically it [02:29] any more questions? [02:29] any packages / patches we should look at together? [02:29] dholbach: that helps a lot...thx [02:31] dholbach: i have a technical question. debuild fails on my machine here with an error message. [02:31] can I post it? [02:31] Goliath23: fire away [02:31] !ask | goliath23 [02:31] goliath23: Don't ask to ask a question. Just ask your question :) [02:31] checking if C++ programs can be compiled... no [02:31] configure: error: Your Installation isn't able to compile simple C++ programs. [02:31] Check config.log for details - if you're using a Linux distribution you might miss [02:31] a package named similar to libstdc++-dev. [02:31] Goliath23: DO you have build-essential installed? [02:31] Goliath23: do you have build-essential installed? [02:31] I have the standard c++ libs installes. on my computer at home debuild works fine [02:31] hehe [02:32] yes [02:32] is this a certain package? [02:32] or some other software? [02:32] nono, ist ksplash-engine-moodin [02:32] works fine and builds fine at home [02:32] try sudo apt-get build-dep ksplash-engine-moodin [02:33] nothing installed [02:33] then config.log will have the answer [02:33] can I somehow remove and reinstall build-essential and all deps of it? [02:33] Goliath23: can you paste your configure.log to pastebin? [02:33] #ifdef __cplusplus [02:33] extern "C" void std::exit (int) throw (); using std::exit; [02:33] configure: exit 1 [02:33] norsetto: sure [02:34] http://pastebin.com/m658d4398 [02:34] Is there any page mentioning what kind of changes can/should/should not be done when creating a package from existing debian package? [02:35] slytherin: What reason do you have to modify a debian packge for Ubuntu === LjL [n=ljl@ubuntu/member/ljl] has joined #ubuntu-classroom [02:35] Usually f possible, its better to send the fix to Debian, and sync accross to Ubuntu. [02:35] slytherin: not to my knowledge. but there's an easy rule of thumb: if it addresses a certain need that we can't achieve by syncing from debian, keep the changes as small as possible [02:35] norsetto: hm, line 1012 something about pthread.. [02:36] TheMuso: ex. I modified copyright year and download url in debian/copyright of a package. I also added version for libvorbis-dev as per my understanding of configure sript. [02:36] slytherin: the thing is: we re-merge all our changed packages with debian in the beginnign of the release cycle and the bigger your change, the more conflicts it's probably going to have with a new version from debian we're merging with [02:37] slytherin: That sounds like something that could go to Debian, and synced accross. [02:37] dholbach: That is right. That is why I wanted to know if their are any guidelines. [02:37] slytherin: that sounds like cosmetical changes the user probably has no benefit of [02:37] slytherin: no strict guidelines, but bear in mind that you or somebody else will have to re-do your changes to package when merging again [02:38] Goliath23: yes, sounds like an header problem [02:38] dholbach: hmm [02:38] slytherin: does that make sense? [02:38] dholbach: yes, it does [02:38] ok [02:39] Goliath23: what kind of modifications did you do? [02:39] dholbach: no modifications.. I guess I'll be able to continue from here... I guess I have to remove some deprecated libsomthing-dev ... [02:39] Goliath23: try reinstalling libc6-dev [02:40] kk, thanks guys [02:40] Hey all [02:40] generally a: sudo apt-get install devscripts build-essential fakeroot; sudo apt-get build-dep ; fakeroot apt-get source -b should enable you to build it [02:40] ah... apt-get remove --purge libpthread-dev did the job! [02:40] hey huats [02:41] any more packaging problems? any packages we should look at? [02:41] oups I thought Goliath23 was over... I let you finish and then I ask mine :-) [02:41] huats: fire away [02:41] i'm finished [02:41] ian_brasil: any mobile packages you have lined up? :) [02:41] I have problems for solving bug #36733 [02:42] the rubber part.... [02:42] oh, the py[co] one? :) [02:42] yep [02:42] bug 36733 === dholbach remembers the bug number :) [02:42] https://bugs.launchpad.net/ubuntu/+source/adonthell/+bug/36733 [02:42] you saw it so many times... [02:42] yes :) [02:42] alright, which source package are we looking at? [02:43] well I have been searching a way to remove the pyc and the only one was to make a find /rm [02:43] rubber? [02:43] rubber [02:43] yep [02:43] is ubotu sleeping? Why didn't he read the bug description for us? [02:43] slytherin: no idea [02:43] i have ported gpodder and liferea to UME [02:43] ian_brasil: wow - nice [02:43] i python and i C app [02:43] so I tried to insert that in debian/rules inside the install target [02:43] but nothing seems to work... [02:44] can you post the new rules file somewhere? [02:44] yep [02:44] pastebin.... [02:44] does everybody understand what huats' bug is about? [02:44] I am writing the UME Guide so my idea is to document the whole MOTU process for other mobile devs [02:44] ian_brasil: that's great - we should chat about that at some stage [02:44] for sure..i was hoping you would say that :) [02:44] is there a way to setup multiple pbuilder like one for feisty, one for gusty etc? [02:45] porthose: I think that's documented too on PbuilderHowto [02:45] porthose: Yes. There is a script in ubuntu-dev-tools to do this I think. [02:45] yeah [02:45] pbuilder-dist [02:45] huats: do you have the rules file up somewhere? [02:45] paste.ubuntu.com/491/ [02:45] Thx [02:46] sorryfor the delay (the file was on another compuer) [02:46] I have put in purpose the find/rm twice === DBO [n=DBO@unaffiliated/dbo] has joined #ubuntu-classroom [02:47] huats: WHy did you put the find line twice? [02:47] TheMuso: juste to shiw you where I have tried to use it === dholbach does a test build: apt-get source rubber; #download rules file, stick into debian/rules [02:47] s/shiw/show/ [02:47] huats: Right [02:47] huats: Wht has worked, and what hasn't? [02:48] nothing has worked... it builds correctly, but the .pyc are still there... [02:48] Right. [02:49] huats: Have you considered building the package step by step by hand, and attempting to determine which step creates the files? By steps I mean, fakeroot debian/rules clean, ./debian/rules build, fakeroot debian/rules install and fakeroot debian/rules binary [02:49] TheMuso: no but I'll be very interested in doing it... [02:49] I personally have found this very helpful, especially recently, in finding problems. [02:50] TheMuso: how can I do that ? [02:51] TheMuso: after a pbuilder login or not ? [02:51] huats: You need to make sure you have all the package's build-dependencies installed, and run the above commands manually. [02:51] huats: If you can login to a pbuilder, and get the package into the chroot, thats great, but things like this need a general purpose chroot handy. [02:52] i.e not specifically for pbuilder use. [02:52] TheMuso: ok so I chroot to my pbuilder env [02:52] TheMuso: and the I can build it step by step... [02:53] huats: Yes. [02:53] dholbach: you may want to look at my changes some time today: https://wiki.ubuntu.com/MOTU/Mentoring/Contributor [02:53] norsetto: will do [02:54] I found the problem [02:54] install: build [02:54] dh_testdir [02:54] dh_testroot [02:54] dh_clean -k [02:54] dh_installdirs [02:54] $(MAKE) install prefix=$(CURDIR)/debian/rubber/usr [02:54] find $(CURDIR) -name '*.pyc' -exec rm {} \; [02:54] # Build architecture-independent files here. [02:54] this will make it work [02:54] you have to put *.pyc into '' [02:54] dholbach: I know [02:54] dholbach: :-) [02:54] find is funny like that at times. [02:54] else the shell will expand it to the first thing it finds [02:55] ok great :) [02:55] another bug solved [02:55] dholbach: oh [02:55] huats: let me know when you put up the debdiff for the fix :-) [02:55] dholbach: I had misread your sentence [02:55] dholbach: ok [02:55] dholbach: sorry for bothering... [02:55] huats: does it make sense? [02:55] huats: no, you're not bothering at all [02:56] huats: what do you think how many times I made that particular mistake [02:56] huats: This is what we are here for. [02:56] dholbach: yes... you use the same command at the same place, but with the correct syntax... [02:56] it's a mistake that's easy to make [02:56] dholbach: Often not quoting the name parameter stuff works. [02:56] in debian/rules you often mix shell code with Makefile code [02:56] it's easy to be wrong there [02:56] As I said, find can be an unusual beast. [02:57] yes [02:57] any other bugs you want to talk about? if not I have one === TheMuso will be heading off to bed soon, so won't be round much longer. [02:57] I talked about 'unmetdeps' bugs before; package that are not installable because their dependencies cannot be resolved [02:57] I'll make this the last one then [02:58] we should have another session next week :) === norsetto keeps TheMuso awake by hammering him on the head every 30 sec [02:58] https://bugs.launchpad.net/ubuntu/+source/wammu/+bug/145538 is one of the list I mentioned earlier [02:58] norsetto: you're so mean [02:58] norsetto: DO you want me to fix bugs, or not? :) [02:58] can anybody find out what the problem is with this bug? === norsetto keeps TheMuso awake by gently hammering him on the head every 30 sec [02:59] norsetto: DO you want me to fix bugs, or not? :) [02:59] To fix bugs, I need sleep at some point. [02:59] if you look at the bug you will notice that it mentions amd64 - you can ignore that === norsetto sings a lullaby to TheMuso [02:59] this bug affects all architectures === TheMuso listens to the lullaby, and then sings along with it, singing a harmony. [03:00] so? anybody up for fixing the bug? :) === norsetto notice all the cats are suddendly fleeing his house .... [03:01] ok, maybe we can get this one fixed next time or you can look at it and let me know what you find :-) [03:01] dholbach: give them time to donwload the source :-) [03:02] you don't need to download the source if you're on gutsy [03:02] just try to install it by running sudo apt-get install --dry-run wammu [03:03] dholbach: Often though, you do need to look atht e source package to get a good idea of why the unmet dep is the way it is. [03:03] TheMuso: absolutely === TheMuso makes the meeting the last task for tonight. [03:05] wammu: Depends: python-gammu (>= 0.21) but it is not going to be installed [03:05] AstralJava: yep [03:05] AstralJava: and why is that? [03:05] dholbach: the dry run was happy to install (until I updated repositorys, then as AstralJava) [03:06] why is this not possible to install? [03:06] Hang on, I'll get the source. :) [03:06] AstralJava: no need yet ..... [03:06] python-gammu is only 0.20-1 [03:06] exactly [03:06] so we need to get a newer version from Debian [03:07] Heh, didn't think of that. [03:07] http://packages.debian.org/src:python-gammu [03:07] dholbach: thats ok with freeze? [03:07] https://wiki.ubuntu.com/UbuntuDevelopment#SyncingAndMerging is the process for that [03:08] adam_b: it will have to get a FeatureFreeze exception [03:08] https://wiki.ubuntu.com/FreezeExceptionProcess#head-1d28045481b8803d4815989e93edc4206f4848c4 [03:08] but I'm sure it will get granted, because it fixes a serious bug [03:08] does anybody of you want to work on that? [03:08] and follow up with our findings on the bug report? === AstralJava can volunteer if no one else wants to [03:09] AstralJava: that's great [03:09] AstralJava: be sure to let me know if it gets stuck somewhere [03:10] AstralJava: Great. Feel free to ask me any questions if you have any. [03:10] so you see; sometimes being a MOTU is some kind of detective work [03:10] what about testing if wammu really needs the new version of python-gammu? [03:10] and it's important to follow up on bug reports with what you've found out [03:10] Sure thing, and dholbach, TheMuso is my sponsor so I'll see him first before bugging all the world. :) [03:10] Oh wait, no that's wrong. [03:10] Nevermind. === AstralJava is still a bit buggered-up because of the flu [03:10] AstralJava: mentor. [03:11] Heh, yeah that too. :) [03:11] adam_b: we inherited both versions from Debian (no Ubuntu changes), so the debian maintainer must have thought that it's necessary to have that new version [03:11] adam_b: note as well the version of wammu [03:11] adam_b: as it happens the debian maintainer is also the upstream author, so it's probably right what he's doing :-) === porthose thinks this has been a good Q&A session :) [03:12] adam_b: but you're right; sometimes version numbers are too strict and you can "bend" them to make packages installable again [03:12] adam_b: in this case I think it's not applicable [03:12] porthose: thanks a lot for that [03:12] it's been great to have you all around [03:12] ahh ok, and probably worth checking that the newer python_gammu dosnt need any other new things? [03:12] and make sure you're on the ubuntu-motu-mentors list, then I'll announce the next session there [03:12] dholbach: quick policy question? [03:12] everybody a good applause for dholbach! [03:12] adam_b: exactly [03:12] Great to see the Q&A sessions are attracting peopl. [03:12] people [03:12] pleia2: fire away === norsetto applauds [03:13] thanks a lot... applaud yourselves too - you all were great [03:13] and I hope to see you all as MOTUs soon :-) === porthose claps === TheMuso seconds dholbach. [03:13] so I'm wondering what the opinion is about packaging in general because of my involvement with Ubuntu-Women, we've sort of been pushing women to contribute directly to Debian rather than Ubuntu since it'll benefit both distros === huats claps [03:14] pleia2: right... that's a valid point [03:14] so is this appropriate? [03:14] pleia2: I can only speak for myself: I contribute to Ubuntu, because I use Ubuntu and test things on Ubuntu [03:14] I do tend to suggest they check out their package in Ubuntu too, see how it's doing and all, if it needs help === pleia2 nods [03:14] pleia2: but I have close contact to debian developers, so I let them know about things I do [03:15] Thank you norsetto, dholbach, TheMuso and all others for having us here. :) Great job. [03:15] pleia2! [03:15] hey Hobbsee :) [03:15] or another example: if I package a new software, I follow up on a debian RFP (request for package) or ITP (intent to package) bug to let them know, that I've already done the work in UBuntu, so they can benefit from that [03:15] dholbach: good to know, thanks [03:16] pleia2: so my answer would be something like: to contribute to Debian (and make other people benefit from our work too) you don't have to be a debian developer [03:16] as long as you're easy to work with and maintain good channels of communication [03:16] I hope that makes sense [03:17] well the RFP and ITP bug notification if you package in ubuntu is a great idea [03:17] of course, it helps that there are DD's around that you can persuade to upload your package to debian too [03:17] I come from Debian, so that's why my dev work is over there, and it's neat to see my packages end up in Ubuntu too ;) [03:18] Well folks, I must be off. Hope to see all you hopefuls around ni the community, asking questions, and fixing bugs/updating packages. === norsetto notices the use of thw word "persuade" [03:18] s/ni/in/ [03:18] I'm off for lunch now [03:18] enjoy, thanks! [03:18] I'll let you all know on ubuntu-motu-mentors about the next session [03:18] TheMuso: thanks for sticking with us so late :-) [03:18] thanks a lot to all of you again! [03:19] norsetto: This is my normal time for staying up anyway. [03:19] TheMuso: finally the hammer thing will stop :-) [03:19] Thanks again. [03:19] huats: heh. [03:19] thanks all once again.... [03:19] Thanks to all [03:19] dholbach: will you put the log of this meeting somewhere ? [03:20] well daniel or someone else :-) === TheMuso [n=luke@ubuntu/member/themuso] has left #ubuntu-classroom [] === porthose [n=charliej@67.60.186.55] has left #ubuntu-classroom [] === AstralJava [n=jaska@e82-103-217-184.elisa-laajakaista.fi] has left #ubuntu-classroom [] [03:22] huats: http://daniel.holba,ch/temp/motu-qa.log [03:23] it'd be nice if somebody could put this into some better place [03:23] maybe on the wiki somewhere [03:25] dholbach: ok thanks [03:25] de rien [03:25] dholbach: :-) === dholbach needs to get his computer repaired, so see you later [03:25] dholbach: perhaps in the MOTU/School section === dholbach -> lunch [03:25] dholbach: I have provided the debdiff to correct the rubber pb... [03:26]