[02:13] hey, how are you! [02:13] hello people´. [02:20] good,you? [06:04] hello jrib :-) [06:04] hi [06:04] so i've downloaded the patch [06:05] doesn't matter where the patch is, just where you are [06:05] ok [06:05] so... where are you? [06:05] well i downloaded the .tar.gz and extracted it [06:05] and i'm in that directory (this is kdebluetooth btw) [06:05] what does 'pwd' say? [06:06] /home/wolfie/Desktop/kdebluetooth-1.0_beta2 [06:06] ok [06:06] and 'ls'? [06:06] lots of files [06:06] any in particular we're lookin for? [06:06] and 'ls -d */'? [06:06] acinclude.m4 configure kdebluetooth Makefile.in [06:06] aclocal.m4 configure.files kdebluetooth.kdevelop po [06:06] admin configure.in kdebluetooth.kdevelop.pcs README [06:06] AUTHORS configure.in.in kdebluetooth.kdevses stamp-h.in [06:06] bemused.patch COPYING kdebluetooth.tag subdirs [06:06] ChangeLog Doxyfile Makefile.am VERSION [06:06] config.h.in INSTALL Makefile.am.in [06:07] and admin/ kdebluetooth/ po/ [06:07] !paste [06:07] ok [06:07] !paste [06:07] guess ubotu isn't in here [06:07] so... is there a "bemused" directory in kdebluetooth/ ? [06:08] yes [06:08] ubotu is sleeping [06:08] ok [06:08] do you understand what -p does with patch? [06:08] somewhat [06:08] something to do with the location of something [06:08] heh [06:08] :-[ [06:08] h [06:09] open up your patch in a text editor for a sec [06:09] ok [06:09] see those first two lines? [06:09] yea [06:09] one looks like a directory and the other one some kind of address [06:10] they tell patch the path to the files it needs to patch [06:10] kdebluetooth/bemused/kbemusedsrv.cpp.old kdebluetooth/bemused/kbemusedsrv.cpp [06:10] ahhh [06:10] i see [06:10] so if i'm in that directory, i don't have to worry about -p right? [06:10] so you are fine without a -p right [06:10] i should be [06:11] ok so recap [06:11] if you were in kdebluetooth, then you would strip the first '/' with -p1 [06:11] but if i'm in bemused [06:11] i'm fine [06:11] correct? [06:11] no [06:11] well [06:11] ? [06:12] where you are now, you would use -p0 to tell it not to strip anything [06:12] ok [06:12] and by strip you mean take stuff off the end of where it thinks the files are [06:12] right? [06:12] if you pass no -p then it strips everything and you need to be in the same dir [06:13] ok [06:13] kdebluetooth/bemused/kbemusedsrv.cpp with -p1 will be bemused/kbemusedsrv.cpp [06:13] well, if i ls right now i see both files [06:13] kdebluetooth/bemused/kbemusedsrv.cpp with -p2 will be kbemusedsrv.cpp [06:13] what does 'pwd' return? [06:14] /home/wolfie/Desktop/kdebluetooth-1.0_beta2/kdebluetooth/bemused [06:14] ok [06:15] ok so i should run patch with no -p correct? [06:15] or with -p0 [06:15] or are both the same [06:15] that is ok here because both files are kdebluetooth/bemused/kbemusedsrv.cpp and kdebluetooth/bemused/amarokcontroller.cpp [06:15] no -p [06:15] ok i get it [06:15] and this is going to compile the whole program using that patch [06:15] correct? [06:15] -p0 would say no [06:15] I mean: no [06:16] patch just patches (modifies) files [06:16] oh [06:16] so i have to have it installed first [06:16] you should have patch [06:16] cuz i'm running patch right now and the terminal is just kind of, froze [06:16] hit ctrl-c [06:16] no output [06:17] that kills the program right? [06:17] the syntax is: patch > /path/to/file.patch [06:17] ugh [06:17] the syntax is: patch < /path/to/file.patch [06:18] oh! [06:18] it works [06:18] i did not think the < was needed for some reason [06:18] wow thanks [06:19] so now that the files are patched [06:19] i have to compile the whole thing right, with those patched files? [06:19] yes [06:20] ok and i think that link you gave me will help with that [06:20] dpkg-buildpackage [06:20] yes [06:20] ok [06:20] i'll go try to figure out how that works [06:20] i'll ask if i have any questions [06:20] :-) [06:23] ok so where exactly does dpkg need to be run from? [06:24] it says "from the directory that was created for the package after downloading" [06:24] i didn't use apt-get to download the package, i just got it from the website, so its on my desktop [06:24] and i'm in the directory, but dpkg returns dpkg-parsechangelog: error: cannot open debian/changelog to find format: No such file or directory [06:24] then follow the first set of instructions ubotu sent [06:25] then you don't get a package though [06:26] ? [06:26] i'm sory i don't follow [06:26] deb [06:26] you don't get a deb if you don't use apt to grab a source package [06:26] oh i see [06:26] ok, let me go try this over with apt-get then [06:29] jrib:kdebluetooth-1.0_beta2 [06:29] er h/o [06:30] Unable to find a source package for kdebluetooth-1.0_beta2 [06:30] that's not the name of the package [06:30] no need to ping me in two channels :) [06:30] oh sorry [06:30] i don't know if you keep checking here [06:31] how do i find the name of the package? cuz i need that particular beta version [06:32] you know what, i was looking at the wrong link, i never checked the prvt message from ubotu [06:32] let me go read that real quick :-) [06:39] night [06:42] jrib: 73 [06:42] n2diy: ? [06:42] 3874 [06:42] i win [06:43] jrib: google 73 [06:43] The Romans capture Masada ? [06:44] The atomic number of tantalium ? [06:45] jrib: Wait please? [06:45] k [06:46] jrib: Try this: http://www.ac6v.com/73.htm#73 [06:49] cool, never knew that [06:54] jrib: 10-4 :) [06:55] 73 [06:58] jrib: 73 OM :) [07:05] jrib still here? [08:30] hello Fritha - welcome to ubuntu-classroom [14:02] hi [14:03] aleph1: is this after an upgrade or just random apt breakage? [14:03] powercut in the middle of "aptitude update" [14:04] that wouldn't do it [14:04] "upgrade" maybe? [14:04] sorry. yeah [14:04] but I think I have found a solution. [14:04] k [14:04] I replaced /etc/init.d/mysql with "exit 0" [14:05] but thanks! :) [14:05] aleph1: glad you got it [14:57] MOTU Q&A session in two minutes [14:59] I forgot the name of the other channel :/ [14:59] hello everybody :) [14:59] welcome to the MOTU Q&A Session! [14:59] who do we have here - can we go through a round of introductions? :) [14:59] Oh, this isn't Open Week yet :) [15:00] I'm Daniel Holbach, MOTU for quite a while now and trying to make becoming a MOTU as easy and enjoyable as possible. :) [15:01] who else do we have here? :) [15:01] I'm Emmet Hikory, MOTU, and active with QA and library porting. [15:01] I'm Fernando Ribeiro, trying to be a MOTU. [15:02] hey rulus, ntaylor0909, nalioth_, welcome to the session - we're just going through a round of introductions [15:02] me... Adam Sommer I'm relatively new to the community and looking for ways to contribute. Was at another QA meeting, but was called away before the end. [15:02] im chuck short, member of the motu team amongst other things [15:02] * dholbach high-fives sommer [15:02] I'm Michael Bienia, MOTU [15:03] who of you is interested in becoming a MOTU and has prepared some questions for us? :) [15:03] dholbach: I'm just listening :) [15:03] andrea gasparini, not motu. [15:03] :-P [15:03] I'm interested, but didn't come prepared with anything specific. [15:03] sommer, rulus, gaspa: great to have you around [15:04] anything you'd like to know about MOTU? contributing or ubuntu development? [15:04] there' s already a roadmap, or a list of things that i can do to help ubuntu development? [15:05] gaspa: sure [15:05] on http://wiki.ubuntu.com/MOTU/TODO we list quite a lot of different things you can start looking into === allee_ is now known as allee [15:05] the 'bitesize' bugs for example are suited for new contributors for example [15:05] 'packaging' bugs deal with packaging related problems, that *might* be easy to fix [15:05] dholbach: ok, i saw only the hardy roadmap, but it's quite vague. [15:06] gaspa: we'll be fixing a lot of bugs, so I think that's a good way to get involved in the MOTU team [15:06] yep, just starting in it ;) [15:07] http://wiki.ubuntu.com/MOTU/Recipes will help you to play with the tools we use most [15:07] perhaps gaspa is referring to this: https://wiki.ubuntu.com/UbuntuDevelopment ? [15:07] gaspa: and sometimes if you are doing stuffs on a bug with a MOTU called norsetto as a mentor on this bug, be prepared to do a lot of things, even for a bitesize bug... But you'll learn a lot... [15:08] huats: I never asked you to do a triple somersault ..... [15:08] hey nealmcb [15:08] norsetto: not yet :) [15:08] gaspa: You might also take a look at https://wiki.ubuntu.com/MOTU/Contributing, which has some suggestions on using the tools, and some of the basic processes for getting things uploaded. [15:08] dholbach: :-D [15:08] norsetto: I was referring to https://wiki.ubuntu.com/HardyReleaseSchedule?highlight=%28hardy%29 [15:09] gaspa: right, that page only explains the various phases of the release cycle we'll go through [15:09] dholbach: howdy. I was late to the other discussion, just caught up on the log, and figured I'd lurk some more here [15:09] and it's not even a final document yet :) [15:09] gaspa: yes, but I think if you want to know more about ubuntu development, you really should look at the wiki link I posted [15:09] dholbach: in fact i wasn't satisfied. ;) [15:09] nealmcb: excellent :) [15:09] gaspa: That's more a schedule to keep track of how release management affects our work. The goals are more to implement as many features as we want prior to Feature Freeze, and fix as many bugs as possible. [15:10] persia: fix bugs? which bugs? [15:10] any other questions around packaging, MOTU, Ubuntu Development, processes? [15:10] * norsetto forgot that the Bug Master is in the room [15:10] norsetto: All of them would be great, but most new people would do best with those with the bitesize tag. === nalioth__ is now known as nalioth [15:11] norsetto: you mean the packaging king right ? [15:11] he must mean seb128 and pedro_ :) [15:11] dholbach: I have one question for you [15:11] :-) [15:11] huats: fire away [15:11] dholbach: how can a contributor submit a patch? [15:11] norsetto: good question :) [15:12] it's all explained at http://wiki.ubuntu.com/SponsorshipProcess [15:12] * norsetto writes that down [15:12] right now, do what distribution we put in the changelog ? gutsy or gutsy-proposed ? [15:12] the gist of it is: if you're fixing a bug, attach the patch that you've produced and subscribe the reviewer team to it [15:12] for main/restricted that's ubuntu-main-sponsors [15:12] huats: hardy [15:12] for universe/multiverse that's ubuntu-multiverse-sponsors [15:13] Whoa even I didn't know about requestsponsor [15:13] s/ubuntu-multiverse-sponsors/ubuntu-universe-sponsors/ [15:13] If you've never produced a patch before: https://wiki.ubuntu.com/MOTU/Recipes/Debdiff might help you with that [15:14] persia: yes, sorry - was a bit distracted, as I just got a call :) [15:14] hiya blueyed [15:15] Hi dholbach :) [15:16] huats: if you want to fix a bug in gutsy (it's already release, so we can't upload to 'gutsy' itself any more), you'll need to follow http://wiki.ubuntu.com/StableReleaseUpdates [15:16] (which has both instructions for main and universe) [15:16] ok, if i decide to write a patch for a bug in https://wiki.ubuntu.com/MOTU/TODO, what should i do to prevent someone else from making the same work? [15:17] I just noticed that seb128 didn't do the most uploads after all: http://ubuntu.joejaxx.org/ :-) [15:17] gaspa: you should assign the bug to yourself [15:17] norsetto: i can't [15:17] i launchpad i can't modify nothing of the bug. [15:17] gaspa: you can't!? Ask for membership in the bugsquad then [15:17] gaspa: you need to login to launchpad and click for example on the status of the bug [15:17] norsetto: that's not required [15:18] dholbach: ah, yes, perhaps he is not logged [15:18] ... i wasn't able to do it... i'll retry... [15:18] no ,i'm logged... [15:18] gaspa: click for example on the status of the line in the middle of page, which has the status/sourcepackage etc information [15:19] i'll retry later, maybe i lost something. [15:19] gaspa: and follow up with information on the bug as you have new findings to report, that's also important to not do the same work twice [15:19] gaspa: alright, let me know if things still go wrong, or ask on #launchpad [15:19] yep [15:19] ah, but... [15:19] is there going to be Q&A meeting? [15:20] nxvl: right now [15:20] welcome nxvl :) [15:20] nxvl: #ubuntu-classroom [15:20] here or in #ubuntu-meetings? [15:20] I am experiencing some timeout with LP today too... so may be it is related to your pb gaspa [15:20] nxvl: here [15:20] if I assign the bug to me, when does it becomes fixed? when i attach a debdiff? [15:20] :D [15:20] gaspa: When it gets uploaded. The changelog in your debdiff will close the bug. [15:21] gaspa: You'll unassign yourself when you add the debdiff, and use http://wiki.ubuntu.com/SponsorshipProcess to get a sponsored upload. [15:21] dholbach: thanks to the rocking contributors we had in the desktop team this cycle ;-) [15:21] gaspa: when you subscribe u-u-s, if your patch is accepted, the sponsor will mark the bug as fix-committed, and then, as persia said [15:22] seb128: care to advertise the DesktopTeam and what contributors can do in it? :) [15:22] the desktop team is a wonderful place to contribute to the Ubuntu desktop ;-) [15:23] Desktop Team definitely rocks :) [15:23] we have a nice IRC channel (#ubuntu-desktop), a mailing list, a wiki (https://wiki.ubuntu.com/DesktopTeam) [15:23] the wiki has a summary of the team and pointers, we also have a TODO on https://wiki.ubuntu.com/DesktopTeam/TODO [15:24] we welcome questions, etc on #ubuntu-desktop and usually contributors find sponsor easily for their patches or updates so feel free to join ;-) [15:24] dholbach: good enough ? ;-) [15:24] seb128: what was that thing about champagne free for any patch uploaded? [15:24] seb128: sounds good - especially the kick-ass DesktopTeam/TODO page :) [15:24] seb128: If I wasn't already convinced I would have been.... [15:25] coNP[uni] is one of the rocking contributors which joined the team this cycle ;-) [15:25] some things we are looking at for hardy BTW [15:25] It is not impossible to become a MOTU [15:25] :) [15:26] - packaging GNOME 2.21.n to 2.22.1, listing annoy glitches laying around for too long that we should fix for the coming lts, make the wiki documentation nicer, and maybe switch to packaging in bzr if we can make the workflow easy enough ;-) [15:26] that sounds like a lot of action in the hardy cycle :-) [15:26] yes [15:27] would also be nice to have some webpage summary for things like version of the package in ubuntu, debian, upstream [15:27] patches browsable easily for upstream also [15:27] also experimental versions [15:28] well, I've abused enough this classroom with desktop advertising, I'm waiting for you on #ubuntu-desktop now ;-) [15:28] but yeah - sounds like a nice small project for somebody :) [15:28] ok. any other questions? [15:29] maybe a problem somebody has, we look at together? [15:30] * norsetto welcomes giftnudel to the MOTU Q&A session [15:31] /me admits to still reading the packaging guide [15:31] sommer: that's no problem [15:31] norsetto, coNP[uni], huats: do we have an easy bug we can tackle in the remainder of the session? [15:31] sommer: That's great. Reading is probably the best way to get questions :) [15:31] * norsetto checks [15:31] bug 1 [15:31] Oh, no :( [15:32] is it better to be proficient with packaging from scratch section before moving on? [15:33] or jump to the more automated tools? [15:33] bug 154399 seems a nice bitesized one [15:34] ubotu seems to be sleeping: https://bugs.edge.launchpad.net/ubuntu/+source/util-linux/+bug/154399 [15:34] sommer: I think it's good to work on easy bugs to get a feeling of what you're dealing with [15:34] sommer: I'd recommend reading the entire guide to build familiarity, and then working with a bunch of different packages while chasing bugs, to see different implementations. That will likely give a better understanding than trying to understand completely from the guide. [15:34] persia, dholbach: ah, sounds good [15:34] norsetto: ok, so how do we attempt to fix it? [15:35] sommer: That's the big advantage of open-source :) it's easy to build on others work. [15:35] dholbach: well, I would first check if nfs-utils is in the repo [15:35] dholbach: for instance apt-cache search nfs-utils [15:36] make sure you have an updated cache first [15:36] anyone has done that? [15:36] I don't have it [15:37] I have a source package called nfs-utils though - I used apt-cache showsrc nfs-utils for that [15:37] anyone know what that is? [15:38] do you know what is a source package? [15:38] dholbach: will you or shall I? [15:38] norsetto: go ahead :) [15:39] * coNP[uni] votes for norsetto :) [15:39] isn't a source package a package that will build multiple binaries? [15:39] ok, I try ..... [15:39] sommer: you can have one or more binaries built from a source package [15:39] sommer: yes, a source package its a pacjage that contains, as the name says, the sources, and the instructions for the build system on how to make binaries out of it [15:40] you download source packages with the apt-get command too; for instance apt-get source nfs-utils [15:40] if you have a deb-src line in /etc/apt/sources.list [15:41] so, you see, in this case there is a source package for nfs-utils, but there is no binary package [15:41] geser: yes ;-) [15:41] and the binary package is the .deb package that gets actually installed [15:41] if you do an apt-cache search nfs-utils you will see that nfs-utils is actually provided by another package, its a virtual package [15:42] Actually you can also download a source package for a binary package, with apt-get source [15:42] So you don't have to know the source package name. [15:43] now you just have to check if the man page object of the bug is really provided by the nfs-common package [15:43] one way to do it (there are many) is to download it, and check its content with a dpkg -c command [15:44] isn't it sufficient to look at the file list for that? [15:45] giftnudel: you mean the one at http://packages.ubuntu.com/? As I said, there are many ways to do it [15:45] well, you explained it already :) [15:45] so to address the bug, would you change the mount man page to say install nfs-common instead of nfs-util? [15:45] sommer: if the man page is indeed in nfs-common, yes [15:46] norsetto: but it may not be? [15:46] ah you check the nfs-util package, correct? [15:46] sommer: I would also check the options section, to see that it indeed contains the mount options for nfs and nfs4 [15:47] ls [15:47] ups :) [15:47] sommer: this is also a check if the information from the bug is correct [15:48] yep, mount has options for nfs and nfs4 [15:49] sommer: we should check that in the nfs man page too [15:50] norsetto: okay, I'm not finding anything in the mount man page about nfs-utils though. [15:51] sommer: what distribution are you using? [15:51] norsetto: Gutsy [15:51] well I can see it there [15:51] * geser too [15:51] right at the bottom [15:51] I did man mount... is that right [15:51] yes [15:52] then go to the end and you should see it [15:52] woops I'm blind [15:52] I see it now [15:53] sommer: I think it is because using space you end up with the header just at the end, so you may miss it [15:54] norsetto: I used /nfs to do a search and when it highlighted the nfs part I skipped over the -utils at the end... heh [15:55] has any of you tried to check the nfs-common package, and its nfs page? [15:55] at least the dpkg seems to contain it and debian/nfs-common.manpages wants to install it :) [15:55] norsetto: trying to install it now. [15:56] also checking it with: http://packages.ubuntu.com/cgi-bin/search_contents.pl?word=nfs.5.gz&searchmode=searchfilesanddirs&case=insensitive&version=gutsy&arch=i386 [15:57] ok, so we checked the correctness of the bug report, the solution given was correct, do we all agree? [15:57] I concur [15:58] what do we do now? :) [15:58] how do we actually patch this out, anyone? [15:58] well, in the mount source package change the string? [15:58] move the man page back to nfs-util, or change the man page of mount? [15:59] the first idea is also nice :) [15:59] sommer: well, I think changing the man page of mount is more appropriate, but, is there anything else we should check first? [15:59] why it was changed? [16:00] sommer: exactly ..... [16:00] probably in nfs-util changelog? [16:00] sommer: could be, we could also ask upstream, perhaps is something specific to ubuntu [16:01] maybe there's a patch in debian already ... [16:01] giftnudel: good point [16:01] norsetto: anyhow, for the sake of the exercise, lets suppose we need to patch this [16:02] how would we go about it? [16:03] apt-get source mount [16:03] in which source package is the mount man page? [16:03] then find the man page file and edit it [16:04] util-linux? [16:04] sommer: yes, it's in tehre [16:04] sommer: thats what the reported said, seems like he knows what is doing, but lets check it [16:04] hi, Q&A still going on ? [16:05] proppy: right now norsetto helps us to fix https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/154399 [16:06] ok, so everybody agrees is in there? [16:06] ok [16:06] finding the offending file is not that difficult, but then [16:07] giftnudel: yes? [16:07] editing is not appropriate, so we need a patch, right? [16:07] using cdbs-edit-patch ? [16:08] proppy: is the package using it already? [16:08] how do you see that? [16:08] giftnudel: why isn't editing the file appropriate? [16:08] by checking dependencies in control and include in rules [16:09] there is also a nice util you can use to determine what patch system a package is using, its called what-patch, and its in ubuntu-dev-tools [16:09] sommer: since you won't easily remember every modification you've done... so there are tools to help you.... norsetto just mentions... [16:09] sommer: giftnudel: It depends on the package. In general, patches are preferable to direct edits, but some packages don't use patches, and we avoid adding patch systems. The tool norsetto advises may be the easiest way to decide. [16:10] sommer: you will edit the file, but with the tool [16:10] ah... thanks I'm with ya [16:10] pardon a query out of the blue: what is u-u-s? [16:10] sommer: if the file you need to edit is not in debian/ then I've been told you need to patch [16:10] nealmcb: ubuntu-universe-sponsors [16:11] :-) [16:11] * proppy apt-get sourcing the package [16:11] nealmcb: http://wiki.ubuntu.com/SponsorshipProcess [16:11] it doesn't seem that util-linux has patches in it already, at least I see none and the control file doesn't have dependencies on a patch system [16:11] proppy: that's what I remembered, too [16:12] so it's cool to directly edit this package? [16:12] giftnudel: I think you are correct, so in this case we have two options, either we do an inline patch or we include ourselves a patch system [16:13] personally, I will never go for inline, even in a simple case like this, but others may have differnt opinions [16:13] what are we working at? i losted lot of the conversations :S [16:13] norsetto: Please reconsider. For many packages, we try to sync back to Debian, and some Debian maintainers are strongly opposed to patch systems, as it breaks their workflow. [16:14]