=== pollywog_ is now known as Pollywog [05:31] can i setup a server on my jaunty desktop for experiment purposes ..like .. checking my php and mysql skills.. using websites..etc...? === dholbach_ is now known as dholbach [06:14] Upcoming: 2 Apr @ 06:00 UTC: Fixing an Ubuntu bug... isnt that now? [06:14] in 45 minutes, I think ^_^ [06:14] yep [06:14] oh sry mixed up [06:14] run date -u in a terminal [06:15] it'll tell you what UTC time it is [06:16] dholbach: thx. clearly shows my need for the classroom ^^ [06:31] dholbach, hello [06:31] hiya balarka [06:32] dholbach, the presentation is going to start in few minutes right? [06:32] yep [06:32] great! [06:32] i am sorry if i disturbed you [06:32] but just want to confirm it didnt start already :) [06:33] no worries :) [06:33] thanks.. [06:39] dholbach, a quick ques.. this presentation is aimed at fixing an ubuntu bug.. and i am very dumb at open source and wanted to start from first [06:40] dholbach, am confused if this is for me [06:40] dholbach, as i am completely a novice programmer for ubuntu [06:40] I think it is okay, balarka, I am also confused [06:41] Pollywog, :) [06:42] don't worry guys - we can't cover everything in much detail but as long as you get an idea from it and have fun and know which questions to ask later, we're all good :) [06:42] that sounds good [06:44] how long will the presentation take? I have to go to work some time...;) [06:44] decumanus_: we'll try to stay within the hour with questions [06:45] but if there are followup questions, I'm happy to take them [06:45] ok thanks! [06:45] decumanus_: your in the CZ aren't you? [06:46] yes [06:46] I love it there... [06:47] akgraner: so do I:-) [06:47] I got to stay in Brno for about 2 months... [06:47] oh... who of you guys is multilingual? [06:48] if you are, could you hang out in #ubuntu-classroom- (like #ubuntu-classroom-fr) too and translate questions for team mates that are not too familiar with English yet? [06:50] akgraner: Prague here, but also like Brno:-) [06:51] decumanus_: I love Prague as well [06:52] decumanus_: I spent all day on the Charles Bridge [07:00] time is up! [07:00] ok my friends... the bells are tolling 8 o' clock here, so it's 6:00 UTC - ready to start! [07:00] who's here for some packaging training action? [07:00] me [07:00] m [07:00] me [07:00] me 2 [07:01] me too :) [07:01] me [07:01] me [07:01] me [07:01] me [07:01] muah! [07:01] fantastic [07:02] ok... so we're going to take a look at a few bugs I selected beforehand [07:02] and try to see what we can do about them [07:02] me [07:03] a category of bugs that is predestined for doing that is what you get when you click on the "xxxxx bugs fixed elsewhere" link on https://bugs.launchpad.net/ubuntu === dave_ is now known as pkpdjh [07:03] these are bugs that were filed in Ubuntu, our Bug Squad identified they were upstream problems (so no bugs that we introduced ourselves), forwarded those bugs to the upstream bug trackers and they were fixed there [07:03] before we get started, we need to set up a few things [07:04] could you please either 1) use the "Software Properties" dialogue to enable Sources or 2) add something like "deb-src http://archive.ubuntu.com/ubuntu/ jaunty restricted main multiverse universe" to /etc/apt/sources.list and run sudo apt-get update [07:05] I am running Hardy and Intrepid, not yet Jaunty [07:05] once you're done with that, please install the following packages: [07:05] cdbs bzr ubuntu-dev-tools devscripts [07:05] Pollywog: OK, then please adjust that line [07:06] k [07:06] next please add something like this to your ~/.bashrc file [07:06] export DEBFULLNAME='Daniel Holbach' [07:06] export DEBEMAIL='daniel.holbach@ubuntu.com' [07:07] (if you use a different shell, please use whatever config file that shell has, bash should be the default) [07:07] where do we ask questions? [07:07] just in here [07:07] afterwards either restart your terminal, or run source ~/.bashrc [07:07] oh nvm, Pollywog asked it i guess. apt-get complained about dist parse [07:08] posingaspopular: can you put up the log of that at http://paste.ubuntu.com ? [07:08] dholbach, so i put this line deb-src http://archive.ubuntu.com/ubuntu/ hardy restricted main multiverse [07:09] dholbach, is this correct ? [07:09] dholbach, i am using hardy [07:09] balarka: add universe to the end of the line too [07:09] dholbach, oh ok [07:09] dholbach, done [07:09] so what we did up until now 1) tell apt where to get source code of packages, 2) install a few tools we're going to need, 3) tell the packaging tools who you are (that simplifies a bunch of things later on) [07:09] dholbach: http://pastebin.com/d56816cc [07:10] posingaspopular: try removing the space in front of the last lines [07:10] dholbach, you mean add export lines at the end of bashrc file? [07:10] balarka: yes [07:10] ah no, i didnt add it correctly. didnt add the actual (universe, mulitverse, etc) at the end of the line [07:10] dholbach, ok [07:11] dholbach: should the .bashrc changes reflect the launchpad account settings? [07:11] posingaspopular: I guess " deb...." instead of "deb....." is the problem [07:11] hassanibraheem: it's generally a good idea to have that email address registered with Launchpad, but not relevant now [07:11] dholbach: ok [07:12] hassanibraheem: your preferred one will do [07:12] ok... who's not set yet? :) [07:13] dholbach, regarding the 3 point [07:13] uhmm i may be outa luck. running debian and unable to get ubuntu-dev-tools [07:13] dholbach, you meant to say we need to put [07:13] our name and address [07:13] brand0con: ignore ubuntu-dev-tools for now then [07:13] ok [07:13] in the export lines? [07:13] everything else is good [07:13] brand0con: rock on [07:13] balarka: yep [07:13] just add something like this to the end of the file [07:13] export DEBFULLNAME='Daniel Holbach' [07:13] export DEBEMAIL='daniel.holbach@ubuntu.com' [07:13] dholbach, so we dont have any @ubuntu.com address [07:14] dholbach, so any outside email address should be fine? [07:14] that's not necessary now [07:14] yep [07:14] dholbach, got it [07:14] dholbach, sure [07:14] super, so let's crack on [07:14] I thought we'd pick https://bugs.launchpad.net/ubuntu/+source/subvertpy/+bug/323270 first [07:15] the problem is in a python module, when used with python 2.6 (default in jaunty) it emits a warning about the deprecated use of another python module [07:15] luckily the problem has been solved by upstream already [07:15] * ara reads the bug report [07:16] everybody who is on jaunty, please run [07:16] apt-get source subvertpy [07:16] everybody else, please run [07:16] dget -xu https://launchpad.net/ubuntu/jaunty/+source/subvertpy/0.6.1-1build1/+files/subvertpy_0.6.1-1build1.dsc [07:16] this will download the source package for you [07:16] what does the u do? [07:16] so what's a source package? [07:16] * sianis is done [07:17] dget? is that a typo? [07:17] Pollywog: no [07:17] k [07:17] maco: it allows unauthenticated sources to be downloaded and unpacked [07:17] Hobbsee: thanks. ive only used -x [07:17] maco: (if you don't have the GPG key of the person who signed it) [07:17] dholbach, it says dget is not installed [07:17] balarka: install devscripts please [07:17] dholbach, sure [07:17] * silentsno downloaded the source for subvertpy. [07:18] a source package is what we need to build .deb packages [07:18] ls [07:18] dholbach, it says unknown option u [07:18] when i type dget command [07:18] as above [07:18] Question: so is the upstream patch already uploaded into this source package that we just downloaded? [07:18] it consists of 1) the .orig.tar.gz which is the unmodified tarball the upstream authors released on their homepage, 2) the .diff.gz: the compressed set of changes we need to make to build it "the debian/ubuntu way" and 3) .dsc file which is meta data like md5sums and so on [07:19] balarka: just use dget -x then [07:19] silentsno: no, that's our job :) [07:19] we'll get to that in a sec [07:19] does everything I said above make sense? [07:19] any questions right now? [07:19] yes [07:19] * silentsno nods his head. [07:20] silentsno: the stuff that's just been unpacked is what ubuntu currently has in jaunty for that package, fyi [07:20] ok perfect [07:20] dholbach, yes.. got the downloaded things [07:20] the great thing is: this works for every package in Ubuntu [07:20] I got 404's [07:20] you have all the source code just seconds away from you [07:20] dholbach, quick ques.. so can i treat a package as a class or module? [07:20] dholbach, or any spl entity? [07:20] nvm I think I had a typo [07:20] Pollywog: can you put up the log at http://paste.ubuntu.com ? [07:21] looks good now [07:21] balarka: a package is just a piece of software, it can be an end-user application, a small tool or a library that other tools use [07:21] dholbach, ok [07:21] in our case it's a "python module", so a piece of code that other packages written in python make use of [07:22] dholbach, got it [07:22] super [07:22] if you run [07:22] cd subvertpy-0.6.1 [07:22] less debian/copyright [07:22] what's the use of the command? [07:22] you will see information about the copyright and everything - right now we're just interested in "where do we get the sofware from?" [07:23] tashuiwuhen_: which command do you mean? [07:23] less [07:23] it will display the content of debian/copyright in a "pager" [07:23] which means you can scroll up and down using arrow keys, etc [07:23] once you're bored, you can type 'q' [07:24] "more" or "cat" would have worked too :) [07:24] 0,got it,thanks [07:24] super [07:24] we're interested in this line [07:24] It was downloaded from http://launchpad.net/subvertpy. [07:24] if you don't know where a particular package has its code from, debian/copyright should always tell you [07:25] so subvertpy is hosted on Launchpad, just like Ubuntu is [07:26] the great thing is, we can now do something like [07:26] bzr branch lp:subvertpy [07:26] to get the source code [07:26] (maybe run cd .. beforehand) [07:26] dholbach, didnt we get the code already? [07:26] by dget command? [07:27] balarka: that's what's in Ubuntu right now [07:27] Question: lp is because of "launchapd"? [07:27] balarka: now we get the current tip of what the upstream developers have been working on [07:27] cel_: exactly [07:27] ok, thanks [07:27] I get unknown repository format [07:27] me too [07:27] dholbach, ques.. who are the upstream developers? [07:28] balarka: the software authors of "subvertpy" [07:28] dholbach, oh ok [07:28] ok, let's take a different approach then [07:28] Pollywog: you need a newer bzr [07:28] hmmm [07:28] I am running Intrepid how old could it be [07:28] dholbach, it says bzr is not installed [07:28] I get the same error (using Intrepid) [07:28] dholbach, which version is preferable to install [07:28] balarka: install the bzr package then please [07:29] balarka: sudo apt-get install bzr [07:29] ok [07:29] dholbach, i get parse error at the end [07:29] dholbach, for sudo apt-get install bzr [07:29] dholbach, command [07:30] balarka: anything wrong in /etc/apt/sources.list then? [07:30] /var/lib/scrollkeeper/C/scrollkeeper_extended_cl.xml:5852: parser error : Extra content at the end of the document [07:30] peopel with older distros might need the https://launchpad.net/~bzr/+archive/ppa repository [07:30] Pollywog: basically anyone not on jaunty needs that ppa [07:30] balarka: that's an unrelated problem [07:30] maco: ty [07:30] I get Unknown branch format on hardy [07:30] dholbach, i dont think so.. as sudo apt-get update went fine [07:30] dholbach, without any errors [07:30] ok... hold off from running bzr branch lp:subvertpy then [07:30] ***** NON JAUNTY USERS: see the PPA JanC linked [07:30] we'll use a different approach [07:31] dholbach, sure [07:31] me,too,spych102 [07:31] no PPA needed then :) [07:31] so if you head to http://launchpad.net/subvertpy - it takes you a few clicks to get to https://code.launchpad.net/~jelmer/subvertpy/trunk-mirrored [07:31] which shows the revision history of what the upstream developers of subvertpy been up to [07:32] if you click on the "Source Code" link, it will show you the source code [07:32] dholbach: what is the syntax in /etc/apt/sources.list for the ppa? [07:32] posingaspopular: forget about the PPA for now [07:33] "Please try again" Sorry, there was a problem connecting to the Launchpad server. [07:33] ha ha, I am having the same problem too [07:33] me too [07:33] Thats from clicking on the SourceCode link [07:33] first packaging training session - everything needs to go wrong now [07:33] :-)))) [07:33] :) [07:33] :) [07:33] thats the spirit! [07:33] I just told the developers :) [07:33] it just came up for me [07:33] ok, so back to https://bugs.launchpad.net/ubuntu/+source/subvertpy/+bug/323270 for a minute [07:34] the first comment says: [07:34] Using Python 2.6: [07:34] ...Lib\site-packages\subvertpy\delta.py:21: DeprecationWarning: the md5 module is deprecated; use hashlib instead [07:34] import md5 [07:34] we shldnt leave me too! [07:34] what we need to check out now is subvertpy/delta.py - this seems to be where the problem is right now [07:35] dholbach: the source line at line 21 [07:35] exactly [07:35] I'll fast-forward a bit for now [07:35] http://bazaar.launchpad.net/%7Ejelmer/subvertpy/trunk-mirrored/changes?filter_file_id=delta.py-20080316001917-xyng7m3jlxvdc4c9-1 [07:35] shows the changes which have been done to the upstream code repository for that file [07:36] does anyone see which revision number might solve our problem? [07:36] 2016 [07:36] dholbach: 2016 [07:36] yes 2016 [07:36] does everybody see the connection there? :) [07:36] ok, so let's head over to http://bazaar.launchpad.net/%7Ejelmer/subvertpy/trunk-mirrored/revision/2016 [07:36] yes [07:36] yes:-) [07:37] yes [07:37] and click on the "Download diff" link [07:38] dholbach, i could see someone used a deprecated method i guess [07:38] dholbach, i am not good at python [07:38] :) [07:38] in this case we'll trust upstream [07:38] if you cd into subvertpy-0.6.1/ again [07:38] and (if you have ubuntu-dev-tools installed) run what-patch [07:39] can anyone see the message it puts out? [07:39] where should we put the diff file [07:39] silentsno: just save it somewhere you can find it again :) [07:39] dholbach: It says patchless? [07:39] command not found? [07:39] dholbach: patchless [07:39] Crusher, sianis: exactly [07:40] so what does what-patch do? [07:40] posingaspopular: you have ubuntu-dev-tools installed? [07:40] tell you patching system its using [07:40] oh, the command is 'what-patch' not 'run what-patch' :P [07:40] it tell us, if the package maintainer decided to store additional patches on top of the regular code [07:40] got it [07:40] err, in which way the maintainer decide to store patches [07:41] dholbach: you mean as in a patch management system? [07:41] dholbach, what are we trying to achieve [07:41] in our case the maintainer decide to just patch the source directly [07:41] here? [07:41] maco: exactly [07:41] dholbach, i am kind of lost [07:41] balarka: so the packgae in Ubuntu right now is broken [07:41] dholbach, ok [07:41] you mean they patched it rather than give us the patch to use? [07:41] well that's much cleaner than the grepping in debian/control dtchen told me to do [07:41] balarka: we found out that it's fixed by the software authors already, we found out what the fix is and downloaded it [07:41] balarka: now we need to apply it to the package [07:42] dholbach: so, in that case, the ubuntu source is just the upstream code with no additional ubuntu changes... right? [07:42] dholbach, so the diff we downloaded has the patch? [07:42] dholbach: Deprecation is a warning and not an error, isn't it? [07:42] hassanibraheem: that we can not tell, you're right "patchless" is a bit misleading there - I'll make a note [07:42] hassanibraheem: what it means to say is "patches are directly applied on the source and not stored separately" [07:42] Pollywog: they can't just send the patch to everybody on the internet ;) [07:43] k [07:43] what other valid output could I expect, other than "patchless?" [07:43] I was not sure if I understood [07:43] sianis: yes, but may become an error in the future - also the warning might be a bit disturbing if you get it every day :) [07:43] dholbach: oh, ok [07:43] balarka: yep [07:43] dholbach: you got roght :P [07:43] ok [07:44] problem here will be the patch level if we all did not put our patch file in the same place, I think [07:44] blfgomes: quilt, cdbs, yabba...i assume it just spits out their names directly [07:44] dholbach, so how do we know that. .that the patch is seperate and the patch has not already been applied to the code [07:44] blfgomes: https://wiki.ubuntu.com/PackagingGuide/PatchSystems [07:44] maco, Crusher: thanks [07:45] balarka: exactly [07:45] balarka: because if it had been applied already, the bug wouldn't exist, right? [07:45] balarka: the code that ubuntu has is older and without this updates that we will apply [07:45] Hobbsee, but if the bug is already there.. why dont the devs fix it [07:45] and give? [07:46] balarka: and you know that the bug still exists, thus, it's not been applied. Also, when you later use patch (or similar tools), it will warn you if it's already been applied, and ask you if you want to revert it [07:46] balarka: it has been fixed upstream in a new version. we're backporting the fix. [07:46] balarka: because you're "the dev" in terms of ubuntu, and you're fixing it. [07:46] maco, Hobbsee thanks [07:46] maco: thanks that answers my puzzlement as well [07:47] so I just tried applying the patch and this is what I got: [07:47] patching file subvertpy/delta.py [07:47] Hunk #2 FAILED at 86. [07:47] (note: you'll sometimes see pulling commits back into an older version referred to as "cherrypicking") [07:47] Hobbsee, so if i am the dev.. why would i put the patch someone else done already? [07:47] to say it simple: some people write software, and others make sure it works in their distro ;) [07:47] Hobbsee, i am little confused here [07:48] balarka: right, so there are two types of developers, right? [07:48] balarka: there's the people who write the software, and the people who package the software to get it into ubuntu [07:48] Hobbsee, you mean core and MOTU? [07:48] dholbach: mee too [07:48] balarka: what Ubuntu does is integrate software from lots of other projects, subvertpy being one of them [07:48] am I correct that the upstream authors submitted the patch and it is our job to apply it to the version in Ubuntu? [07:48] Pollywog: exactly [07:48] balarka: like authors who write a book, and librarians, who sort books and organise them in their libraries [07:48] Hobbsee, that was perfect example [07:48] balarka: but, if an author changes their book, and republishes it, it doesn't mean that the library shelves magically change [07:49] Hobbsee, thanks [07:49] Hobbsee, got the point [07:49] the librarian still has to do the work in finding another book, etc [07:49] cool :) [07:49] ok... cool - are we all clear on where we stand right now [07:49] nice explanation Hobbsee, ty [07:49] I think I have it [07:49] nanbanjin: :D [07:49] great [07:49] I'm good. Thanks, Hobbsee for the analogy. [07:50] Hobbsee, appreciated! [07:50] :) [07:50] Hobbsee++ [07:50] :-))) [07:50] ok great [07:50] the dead horse has been beaten [07:50] I just tried applying the upstream patch, this is what I got: [07:50] patching file subvertpy/delta.py [07:50] Hunk #2 FAILED at 86. [07:50] you get this every now and then when there have been a lot of changes in the upstream code and we didn't catch up yet [07:51] dholbach, so how to apply the patch? [07:51] what we'd need to do is apply the changes manually or at least parts of them [07:51] balarka: I'll get to that in a sec [07:51] dholbach, any specific command? [07:51] when you patch, is there still a "--dry-run" option in patch? [07:51] dholbach, sure.. [07:51] I just updated the patch to work properly :-) [07:51] so if you run [07:51] hehe [07:51] wget http://people.ubuntu.com/~dholbach/patch [07:52] you should get the patch file that's going to work for us [07:52] Pollywog: yes [07:52] if you [07:52] cd into subvertpy-0.6.1 again [07:52] and run [07:52] patch -p1 < ~/patch [07:53] (or wherever you downloaded the "patch" file to) [07:53] it is going to apply the updated changes [07:53] you should get something like this as the output [07:53] patching file subvertpy/delta.py [07:53] did that work for everybody? [07:53] yes [07:53] looks like that worked here [07:53] yes, worked [07:53] nope [07:53] perhaps an explanation of how to figure out and manually update patches would be in order at some point...even just as a blogpost on that packaging howto blog you've got, dholbach? [07:54] dholbach, is patch a command? [07:54] * silentsno patched file delta.py [07:54] maco: definitely [07:54] balarka: yes [07:54] it should be in the patch package [07:54] it gives No such file or directory [07:54] does the patch level depend on where we put the patch file? [07:55] Pollywog: it depends on how deeply into the source package it needs to go [07:55] sudo apt-get install cdbs bzr ubuntu-dev-tools devscripts (should give you all the tools) [07:55] Pollywog: i'm told "count the slashes" [07:55] maco: ty [07:55] i'm told "No such file or directory" [07:55] dholbach: what is the difference between the revision we downloaded from LP and your patch we downloaded [07:55] I want to package a java-library. It was called xtvd-lib by upstream and was placed at a directory called xtvd-lib. My control-file says "Source: xtvd-lib" and "Package: libxtvd". How can I use the same name for the source- and the binary-package? [07:55] Pollywog: it depends on from where the "diff" was run [07:55] aladin: can we please cover that later on? [07:55] dholbach: ty [07:55]