[00:53] * hggdh is away: walking the dogs === picard_p1ns_kirk is now known as picard_pwns_kirk === hggdh is now known as hggdh|away [05:00] date -u [05:02] Socceroos_work, in your terminal [05:03] :D [05:18] :) [05:20] . [06:08] date -u === dholbach changed the topic of #ubuntu-classroom to: Ubuntu Classroom || https://wiki.ubuntu.com/Classroom || https://lists.ubuntu.com/mailman/listinfo/Ubuntu-classroom || Next Event: Ubuntu Developer Week: https://wiki.ubuntu.com/UbuntuDeveloperWeek | Questions about the presentation in #ubuntu-classroom-chat (prefix with QUESTION: ...) | Run date -u (in a terminal) to find out what UTC time is right now [06:12] :) [06:58] date -me === persia_ is now known as persia === ALAY1 is now known as ALAYA [08:18] hello : ) === AdiB is now known as adibdimitri [09:25] -u [10:53] === dholbach_ is now known as dholbach === hggdh_ is now known as hggdh__ [15:09] sorry, wrong window :-) annd the pw is changed for sure. === hggdh__ is now known as hggdh === superm1 is now known as superm1|away [16:55] ~o~ \o/ ~o~ [16:56] Are you ready for Ubuntu Developer Week - Day 2? [16:56] no [16:56] yes! [16:57] huhu dholbach :D [16:57] come on... who's here for another day of Ubuntu Developer action? :-) [16:57] uh, well, then [16:57] yay! [16:57] \o [16:57] \o/ [16:57] hey [16:57] \o/ [16:57] * balachmar is here [16:57] o/ [16:58] I am [16:58] me too! can we have a beijing olympics opening ceremony style countdown :) [16:58] me too [16:58] * Volans I am too [16:58] me three? [16:58] woohoo, excellent - grab something drink a snack, lean back and enjoy === superm1|away is now known as superm1 === fabian23_ is now known as fabia1 [16:59] * takdir too === fabia1 is now known as fabian23_ [17:00] * mruiz waves [17:00] alright... let's get started - my name is Daniel Holbach, I've been working with the MOTU team since hoary and work for Canonical for quite a while, trying to make developing Ubuntu as fun as possible [17:01] together we're going to grab some low-hanging fruit and fix a bug together [17:01] questions please in #ubuntu-classroom-chat, prefixed with "QUESTION: ..." [17:02] for those of you who are participating can you please just mention which Ubuntu release you are on and if you have a fast/slow connection to the net? [17:02] in here is fine [17:02] 8.10 - 8meg [17:02] hardy - 8meg [17:02] just fast/slow is fine :-) [17:02] 8.04 fast [17:02] 8.10 , 10meg [17:02] 8.04 fast [17:02] fast :) [17:02] I don't want you to start measuring now :-) [17:02] 8.04 fast [17:02] hardy - medium [17:02] 8.04 fast [17:02] heh [17:02] intrepid, medium [17:02] 8.10 - slow [17:03] hardy - medium [17:03] 7.10 + pbuilder-intrepid - 7meg [17:03] 8.04 Medium (relative)// [17:03] 8.10 - slow [17:03] ok.. 8.04, 8.10 and 7.10 should be fine AFAIK - if you run into problems or have questions, please raise it on #ubuntu-classroom-chat [17:03] we need to do some preparations first [17:03] 8.10 16mbit :P [17:04] those of you who have a reasonably fast connection will install pbuilder [17:04] please do the following: [17:04] sudo apt-get install pbuilder devscripts [17:04] then edit ~/.pbuilderrc [17:04] hardy slow [17:04] and put [17:04] COMPONENTS="main universe multiverse restricted" [17:04] into it [17:04] then run [17:04] sudo pbuilder create [17:05] we'll let that run in the background as it will take some time [17:05] everybody else please just install devscripts [17:05] pbuilder is a tool with which we can test-build source packages in a minimal environment [17:06] what I just mentioned was the short cut, https://wiki.ubuntu.com/PbuilderHowto has more information [17:06] ok... while that's running, let's start looking for those low-hanging fruit :-) [17:07] a while ago I started an effort called Harvest - it's basically a webpage that pulls data from various sources and displays that information per package [17:07] http://daniel.holba.ch/harvest [17:07] QUESTION: which distro pbuilder should have created ? [17:07] tacone: the ones that were mentioned before should all be fine [17:08] if you click on the "Sourcepackage list" link it will present you with an awfully long list of "opportunities" [17:08] let's fast-forward to http://daniel.holba.ch/harvest/handler.py?pkg=djvulibre [17:08] QUESTION: how I can use local mirror server in pbuilder instead of archive.ubuntu.com [17:09] mazaalai: please check out https://wiki.ubuntu.com/PbuilderHowto - it should have that information [17:09] MIRRORSITE="http://us.archive.ubuntu.com/ubuntu" I think [17:10] ok, everybody at http://daniel.holba.ch/harvest/handler.py?pkg=djvulibre right now? [17:10] it shows three opportunities [17:10] 2 fedora patches [17:10] and one from the "opportunities" list [17:10] errr [17:10] and one from the "patches" list [17:10] please click on the 255695 link [17:10] patches means: this is a bug with a patch attached [17:11] as you can see, Harvest makes it easy to gather all that kind of information about packages that you're interested in [17:11] amont them are: patches in Launchpad, upgrade requests, fedora patches, if the package does not build from source right now, etc etc [17:12] sometimes it takes a bit to find something suitable to work on (because you don't know the package well enough or the bug is too complicated and so on), but Harvest is a good start to find those low hanging fruit [17:12] ok... the bug report says something's wrong with the manpage of c44 (which is included in the package) [17:13] let's see if that's true, please run [17:13] dget http://daniel.holba.ch/motu/djvulibre_3.5.20-7ubuntu1.dsc [17:13] for those of you who attended Packaging 101 yesterday, you already notice which files were downloaded and what they are their for [17:14] QUESTION: do I want to do dget in a seperate folder, or does it put it into the pbuilder stuff? [17:14] balachmar: as you like it, you can run it from a special directory if you like, no problemo [17:14] ls [17:14] it downloaded a .orig.tar.gz a .dsc and a .diff.gz file [17:15] short version: .orig.tar.gz is the unmodified tarball that the software authors released on their homepage, .diff.gz the compressed set of changes we need to apply to make it build "our way" and become a nice .deb package in the end, the .dsc file contains metadata like md5sum, etc [17:16] alright [17:16] please run dpkg-source -x djvulibre_3.5.20-7ubuntu1.dsc [17:16] this will extract the tarball, then apply the compressed patch [17:16] QUESTION: it says "dscverify: can't find any Debian keyrings "? [17:17] mitesh: it's a warning, you can safely ignore it [17:18] QUESTION: I get dpkg-source: error: File ./djvulibre_3.5.20.orig.tar.gz has size 1359872 instead of expected 2426487 ? [17:18] fluteflute: sorry for that, I'm just fixing the mistake [17:19] sorry for that everybody, please run the commands again [17:19] that is: [17:19] dget http://daniel.holba.ch/motu/djvulibre_3.5.20-7ubuntu1.dsc [17:20] dpkg-source -x djvulibre_3.5.20-7ubuntu1.dsc [17:20] thanks for bearing with me :) [17:20] OK [17:20] :) [17:21] :) [17:21] let's try to find out if the problem that Mr Ralph Corderoy describes is still valid [17:21] cd djvulibre-3.5.20/tools [17:21] nroff -man c44.1 | less [17:22] this will display the manpage [17:22] and since he alread mentions that it's around the "PPM" bit in the text, we can run: [17:22] ls [17:22] nroff -man c44.1 | grep -a1 -b1 PPM [17:22] you should see the ".SM" bit he is referring to in the bug report [17:23] everybody can see that? [17:23] let me rephrase: can you guys see that too? :) [17:23] yes [17:23] yes [17:23] yes [17:23] yes [17:23] yeehaw [17:24] yes [17:24] yes [17:24] great [17:24] I get troff: fatal error: can't open `c44.1': No such file or directory [17:24] just wanted to make sure I hadn't lost you on the way :) [17:24] tacone: are you in djvulibre-3.5-20/tools ? [17:24] djvulibre-3.5.20/tools [17:24] no ok, my fault, sorry [17:24] alright, let's go on [17:25] let's all download the patch that Ralph Corderoy is suggesting [17:25] I'll assume you put it into ~ for now :) [17:25] please run [17:25] patch -p0 < ~/c44.1.patch [17:26] in my case it safely applied [17:26] anybody got any problems? [17:26] it must be in djvulibre-3.5.20/tools, right? [17:26] mazaalai: no, it doesn't matter where you put the patch, it's just important that you are in the directory, when you run the patch command [17:27] dholbach, successful == .PM shouldn't be there? [17:27] techno_freak: I'm coming to that :) [17:27] QUESTION : it says bash: /home/mitesh/c44.1.patch: No such file or directory [17:27] mitesh: did you download the patch from the bug report to ~? [17:27] QUESTION: where can i download the patch from? [17:27] https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/255695 [17:27] Launchpad bug 255695 in djvulibre "c44(1) man page outputs splurious `.SM' macro invocation" [Undecided,New] [17:28] the patch operation should take a second at best [17:28] wget -c http://launchpadlibrarian.net/16614829/c44.1.patch [17:28] ok... once you've applied the patch please run [17:28] nroff -man c44.1 | grep -a1 -b1 PPM [17:28] again [17:28] can you still the ".SM" bit there? [17:29] no [17:29] nope [17:29] no :D [17:29] done...no [17:29] nope [17:29] ok, it's gone [17:29] no [17:29] gone [17:29] excellent, seems that Ralph Corderoy has done good work :) [17:29] ok... now [17:30] as we want to fix the bug in Ubuntu we need to add a changelog entry to explain what we changed and why [17:30] this all happens in debian/changelog [17:30] so please run: [17:30] cd .. [17:30] dch -i [17:30] this will fire up an editor with a template changelog entry [17:31] I won't go through all the specifics in it, read the Packaging 101 log from yesterday or check out the videos on http://youtube.com/ubuntudevelopers [17:31] there's also https://wiki.ubuntu.com/PackagingGuide to find out more about it [17:32] just make sure that the top entry says "intrepid" in the first line and that your mail address and name is correct [17:32] QUESTION: how do you change the dhc template so it uses the correct email? [17:32] and for those running hardy and gutsy? [17:32] fabian23_: dch -i -D intrepid [17:33] Oli`` is right, I should have explained that before, for now just edit it manually, I'll tell you later how to fix it for the next times you're going to use the tool [17:33] fabian23_ asks an important question: why not hardy, why intrepid? [17:33] because we can just make changes in the current development release which is intrepid [17:33] all the other releases have been closed [17:34] there's the hardy-updates process which works differently, for now the link https://wiki.ubuntu.com/StableReleaseUpdates should be enough [17:34] ok, let's document our changes [17:34] that's the crucial step, because our fellow developers should not have to guess where our ideas came from [17:34] I'll put in something like this: [17:35] * tools/c44.1: applied patch from Ralph Corderoy to fix the manpage markup. (LP: #255695) [17:35] three things are worth noting: [17:35] 1) explicitly named the files that were changed in the upload [17:36] 2) I gave credit to the person who provided the fix [17:36] 3) I mentioned which bug report in Launchpad this is all about [17:36] in addition to that (LP: #) will automatically close the bug once it got uploaded to the build daemons [17:36] QUESTION: shouldn't we use a patch system ? [17:36] tacone: good question [17:37] there's going to be another session on Sep 3rd at 20:00 UTC about patch systems [17:37] this package does not use a patch system itself and directly applies changes to the source, so we'll do the same [17:38] once we're done with that, please save the file [17:38] and run debuild -S [17:39] this will rebuild the source package (not build the package itself) and refresh the .diff.gz [17:39] if you run [17:39] ls .. [17:39] you will notice that there are two .diff.gz files now [17:39] the one we downloaded and the second one we created ourselves [17:40] since the question about patch system comes up again in #ubuntu-classroom-chat: [17:40] if the Debian package we're attempting to fix does not add a patch system itself and patches the source inline (as opposed to adding patch files in debian/patches) we will do the same [17:40] dholbach: running debsign failed [17:40] QUESTION: why dosen't debuild -S find my private gpg key? [17:40] that's to be expected, I'll enlighten you about it in a bit - it's safe to ignore right now [17:40] QUESTION: /bin/bash: dh_testdir: command not found where can i find it? which package? [17:41] chombium: sorry..... sudo apt-get install debhelper [17:41] tx [17:41] ok [17:41] now please run: [17:42] cd ..; debdiff djvulibre_3.5.20-7ubuntu{1,2}.dsc > djvulibre.debdiff [17:42] debdiff is a great utility that will compare the two revisions of debian source packages and print out the diff [17:43] can you all please go to http://paste.ubuntu.com and paste the contents of your djvulibre.debdiff into it and give the link to your sourcepackage here? [17:44] fluteflute, ^^ [17:44] who managed to produce a djvulibre.debdiff ? [17:45] dholbach: http://paste.ubuntu.com/42746/ [17:45] can you please post the contents of that file on http://paste.ubuntu.com and give the link here? [17:45] dholbach: http://paste.ubuntu.com/42747/ [17:45] http://paste.ubuntu.com/42748/ [17:45] Coper: looks good! [17:45] http://paste.ubuntu.com/42752/ [17:45] tacone: looks good [17:45] http://paste.ubuntu.com/42749/ [17:46] http://paste.ubuntu.com/42750/ [17:46] http://paste.ubuntu.com/42754/ [17:46] riot_le: looks good too [17:46] http://paste.ubuntu.com/42753/ [17:46] http://paste.ubuntu.com/42755/ [17:46] http://paste.ubuntu.com/42756/ [17:46] http://paste.ubuntu.com/42757/ [17:46] vishr: looks good as well, I'd just indent the 2nd line of the changelog entry a bit [17:47] palango: the same goes for yours [17:47] ok [17:47] balachmar: yours is OK, I'd just wrap the line in the changelog entry [17:47] KennethVenken: same as balachmar [17:47] http://paste.ubuntu.com/42758/ [17:47] http://paste.ubuntu.com/42759/ [17:48] swingnjazz: please the contents of the file, not the command line output [17:48] Oli``: same as balachmar [17:48] @dholbach the famous 60 characters or something? [17:48] Bijoy: was that the whole file? [17:48] uuh, sorry for that [17:48] balachmar: yeah, editors like vi make it easier for you [17:48] techno_freak: same as balachmar's :) [17:49] takdir: your changelog entry is a bit short [17:49] chombium: your changelog entry is empty [17:49] dholbach, ok [17:49] other than that: W E L L D O N E [17:49] I mean... [17:49] _ _ _ [17:49] __ _____| | | __| | ___ _ __ ___ [17:49] \ \ /\ / / _ \ | | / _` |/ _ \| '_ \ / _ \ [17:49] \ V V / __/ | | | (_| | (_) | | | | __/ [17:49] \_/\_/ \___|_|_| \__,_|\___/|_| |_|\___| [17:49] [17:49] everybody! [17:49] QUESTION: I see that in the debdiff there are entries also for autogenerated files, we should leave them or use filterdiff? [17:50] Volans: good question [17:50] sorry, my bad, I'll paste again [17:50] config.guess and config.sub are build helpers that were automatically updated and can be filtered out - it makes reviewing a lot easier [17:50] QUESTION: Is there a reason why there's a ~200 line difference in diff size between some of ours? [17:50] Oli``: that's due to what I just said above [17:50] REMARK: But the command dch -i started nano not vi [17:50] balachmar: you're right [17:51] so let's fix all the GPG, Name, Email address, Editor issues you all saw before [17:51] if you all use bash as your shell (the default), then please edit ~/.bashrc [17:51] http://paste.ubuntu.com/42762/ [17:51] http://paste.ubuntu.com/42761/ [17:51] and add something like this at the end of it: [17:51] export DEBFULLNAME='Daniel Holbach' [17:51] export DEBEMAIL='daniel.holbach@ubuntu.com' [17:51] export EDITOR=vim [17:51] then save the file and run: [17:52] source ~/.bashrc [17:52] swingnjazz: better, I'd just wrap the line of the changelog entry [17:52] Bijoy: I'd indent the second line of the changelog entry a bit [17:52] other than that: GREAT [17:52] QUESTION: So what to do now we have patched it? [17:53] that's the good question :-) [17:53] let's build the package and see if after our changes it still builds [17:53] if your pbuilder command has finished, please run [17:53] sudo pbuilder build djvulibre_3.5.20-7ubuntu2.dsc [17:53] this is going to take a while [17:54] in the meantime, I'm going to explain once you've found that: [17:54] 1) the package still builds [17:54] 2) once you installed the new package, your system still works [17:54] 3) all is good [17:54] (testing is crucial, but we don't do it in the 6 remaining minutes) [17:55] what happens once all tests passed and you're happy with everything? [17:55] you'll follow the sponsoringship process [17:56] Sponsoring means: somebody who has upload privileges already will review your debdiff (you'll attach it to the bug in question) and if they're happy with what you've done, sign the source package with their GPG key and upload it [17:56] https://wiki.ubuntu.com/SponsorshipProcess has more information about that [17:56] (all the links I mentioned before are on https://wiki.ubuntu.com/MOTU/GettingStarted <- that's the one you should bookmark) [17:56] QUESTION: Is there a way to mark a bug as being worked upon? [17:56] very important question [17:56] yes, there is [17:57] you will click on the little arrow on the yellow bar in the middle of the bug report [17:57] and set yourself as the assignee and set it to in progress [17:58] as you can see: fixing Ubuntu is not always rocket science, but more a matter of detective skills and careful testing and asking questions [17:58] the door to #ubuntu-motu is always open and you can ask questions there [17:59] please read the sponsorship page carefully when asking for sponsorship [17:59] any more, maybe general questions? :) [17:59] we have a minute left :) [17:59] OK, we'll have a nother session on thursday [17:59] fixing bugs again :-) [18:00] thanks everybody, you really ROCK [18:00] do you publish this HowTo in the Wiki too? [18:00] but important ones since FF is here :P [18:00] thanks a lot dholbach :) [18:00] +1 [18:00] thanks! [18:00] thanks dholbach [18:00] \o/ [18:00] thanks a lot dholbach [18:00] I'll repeat what I said yesterday: I'd like to see your names connected to Ubuntu Development soon, so make me proud! :-) [18:00] thanks to you [18:00] I am going to find some fruit straight away! [18:01] Thank you Daniel! [18:01] next up is the unstoppable David Futcher (bobbo) who is going to introduce you to bzr [18:01] thanks everybody! [18:01] thx dholbach [18:01] bobbo: the stage is yours :-) [18:01] thanks dholbach ! [18:01] Hey! My name is David Futcher and today I'll be giving you a simple introduction to the Bazaar (BZR) Distributed Version Control system (dont worry if you dont know what that means, we'll get to that a bit later on). [18:02] I like to answer questions, so, if you have any, please do not hesitate to ask. Prefix your question with QUESTION: and ask it in #ubuntu-classroom-chat. [18:02] I have never done a UDW session before, so this session may be quite short or even run over, but we will cross that bridge when we come to it. If I am going too fast at any point, please shout and #-chat and I'll slow down :) [18:02] So who is all here? Raise your hand in #-chat so I can see it! [18:02] \o/ [18:03] o/ [18:03] wahey, we have some people! [18:03] * palango raises his hand [18:03] Before we get started we need to install some packages. Run sudo apt-get install bzr bzrtools to make sure you have everything we will need. It would also be handy if you have a Launchpad account (I guess most of you do), though its not absolutely necessary, but you might have to skip out some of the session later on. [18:03] shout when you have all this installed and we can get started :) [18:04] Awesome, everyone seems to be ready, lets get started! [18:05] ## What is BZR? [18:05] (This section is a bit heavy on reading, but we will get to some practical examples soon) [18:05] azaar is a tool for helping people collaborate on open-source software. It tracks the changes that you and other people make to a group of files - such as software source code - to give you snapshots of each stage of their evolution. [18:05] Using that information, Bazaar can effortlessly merge your work with other people's. [18:06] Tools like Bazaar are called version control systems (VCS) and have long been popular with software developers. [18:06] Bazaar's ease of use, flexibility and simple setup make it ideal not only for software developers but also for other groups who work together on files and documents, such as technical writers, web designers and translators. (I used Bzr when writing this session) [18:07] Many traditional VCS tools require a central server which provides the change history or repository for a tree of files. [18:07] To work on the files, users need to connect to the server and checkout the files. This gives them a directory or working tree in which a person can make changes. [18:07] To record or commit these changes, the user needs access to the central server and they need to ensure they have merged their work with the latest version stored before trying to commit. This approach is known as the centralized model and its not too great. [18:08] The centralized model has proven useful over time but it can have quite a few drawbacks. It makes it harder for new developer to come to the project and make more than a few small patches, while with Bzr, a developer can easily create a branch that adds large new features or massive code changes. [18:08] Distributed VCS tools (like bzr) let users and teams have multiple repositories rather than just a single central one. In Bazaar's case, the history is normally kept in the same place as the code that is being version controlled. [18:08] This allows the user to commit their changes whenever it makes sense, even when offline. Network access is only required when publishing changes or when accessing changes in another location. [18:08] Everyone with me so far? [18:09] yes [18:09] yup [18:09] yep [18:09] yep [18:09] yes [18:09] great! [18:09] ANSWER: Yep. [18:09] yes [18:09] Thats the end of the boring reading stuff, now onto some examples [18:10] OK, so now you what what BZR is, and what it allows us to do, lets try it out. We are going to create a branch of GNU Hello. We need to grab the programs tarball and extract it: [18:10] Open up a terminal and run: [18:10] wget http://bobbo.me.uk/ubuntu/udw/hello-2.3.tar.gz [18:10] tar -xvf hello-2.3.tar.gz [18:10] cd hello-2.3 [18:10] QUESTION: What are the differences between bzr and git? [18:11] nemphis: I am not too sure (I have never used Git), but reading http://bazaar-vcs.org/BzrVsGit should tell you all you need to know :) [18:11] Running 'ls' in your newly extracted hello-2.3 dir should show you the whole source tree for GNU Hello [18:12] now we need to tell bzr to look after this source for us [18:12] bzr init [18:12] (everything indented with 4 spaces should be run in a terminal :) [18:12] QUESTION: what does ubuntu/cannonical use bazaar for? [18:13] okar_: Ubuntu/Canonical use it for quite a few things [18:13] mainly just for storing source code to applications we maintain [18:13] but it is also used for storing documentation and for application packaging for the MOTU team [18:14] bzr init will create all the files and directories that bzr needs to be able to add revisions in ./.bzr. You normally wont need to touch anything in that directory, but its good to know it is there so you dont accidentally hose it and lose all your revision history, which isnt too awesome. === arkara is now known as wantilles [18:15] OK, now we have told Bzr to setup revision control in the directory, we need to tell it where all out files are: === wantilles is now known as arkara [18:16] bzr add [18:16] This should recurse through all the directories and add all the files it can find to bzr. [18:16]