=== bigon is now known as bigon` === andrew__ is now known as null-cipher [06:04] * AxCray_ Binar === AxCray_ is now known as Binar [12:28] Hi [13:05] .. [13:05] leave [14:07] . [14:07] wasn't there a class today? === Pricey is now known as PriceChild [14:10] the only thing on the agenda is for the 17th [14:11] motu class today 16:00 - 17:30 utc [14:16] pleia2: the packaging 101 session will be today [14:16] dholbach: what is the schedule for that exactl? [14:17] * pleia2 really must start keeping track of this :) [14:17] oh [14:17] utc [14:17] http://fridge.ubuntu.com [14:17] here in cape town that is another 2 hours [14:17] same here :) === nxvl_ is now known as nxvl [15:30] am i right that todays "event" is starting at 6pm utc? ( in germany 7pm?) [15:30] I thought it was 16:00 or 4 pm. [15:30] durgis is correct [15:31] so it starts in half an hour? [15:31] angor: yeah :) [15:31] cool, thanks :) [15:31] bring it on! [15:32] i hope nobody minds if i log this, for later use or as a transscript for ubuntuusers.de (if nobody else logs it) [15:32] angor: no, that's great [15:33] if somebody wants his name deleted, he/she/it should contact me so that i can cut it out [15:34] angor: this channel is logged publically anyway: http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt [15:34] oh, yeah, did not think of it [15:34] ^^ [15:35] then forget about it [15:35] brb [15:42] re, is the "motuguide" also understandable for packaging beginners? === virilius is now known as edfonseca [15:43] bits of it [15:44] one has to read quite a bit to understand the full debian package [15:44] (not there yet) [15:44] and then there is all this pbuilder stuff on top [15:44] vamos ao coffee entao? [15:44] many ways to skin a deb [15:45] well, then i can keep it for later use :) so i´ll just be quiet and listen so that i can understand it later , thanks for the info [15:50] hi leute [15:51] angor: not that I'm there yet! [15:51] hallo roys, hier ist englisch angesagt ;) [15:52] ooops [15:52] sorry === matthew is now known as MattBD === Per is now known as md2perpe === bigon` is now known as bigon [16:00] Welcome to the Packaging 101 Session! [16:00] How are you all doing? [16:00] Hi. Fine, thanks [16:00] excited ;) [16:00] :D [16:00] Good here. [16:00] fine :> [16:00] good :) [16:00] What they said. :) [16:00] Great - who of you wants to become a MOTU? :-) [16:00] * hellboy195 :) [16:00] I do. [16:00] <---- [16:00] * vorian raises his hand [16:00] * warp10 raises a finger [16:00] * Guite wants to maintain a particular package... [16:00] I do [16:01] do not know if this requires being a MOTU ;) [16:01] ROCK AND ROLL :-) [16:01] * dantalizing wants ta [16:01] great to hear that [16:01] Guite: I'll answer the question in a bit [16:01] I do [16:01] So what does it take to become a MOTU? Best point to start is http://wiki.ubuntu.com/MOTU/GettingStarted [16:02] it links to all the necessary information and takes you by the hand on your way to MOTU membership :) [16:02] there are three areas on the wiki that are important to become an Ubuntu developer [16:02] First of all http://wiki.ubuntu.com/UbuntuDevelopment - which links to all information about Development processes [16:03] so things like how to merge, how to do a sync request, how the archive machinery works and so on [16:03] http://wiki.ubuntu.com/PackagingGuide has a lot of information about packaging - so all the bits that are necessary to build packages from source code [16:03] and last but not least http://wiki.ubuntu.com/MOTU - which has information about the MOTU team, its events, its governance, etc [16:04] * LucidFox raises his hand [16:04] LucidFox: fire away [16:04] is the packaging guide on th wiki older or newer than the one on help.ubuntu.com? [16:04] LucidFox: newer - I spent a lot of time to merge other packaging information into it, I split it up, so that the contents can be re-used in other places [16:05] these three wiki namespace are the definite areas you should hit up, when you run into problems [16:05] So what's the process for becoming a MOTU? [16:06] It's pretty straight-forward: you contribute patches and packages and members of the MOTU team will review them, discuss them with you and sign them with their gpg keys once they are OK, then upload to the build daemons [16:06] build daemons++ [16:06] k [16:07] after you've done that for a while and your sponsors (the people who "sponsored" your uploads) have only good things to say about you, you mail the MOTU Council who will then take a look at your application [16:07] and that's it [16:07] probationary period ^^ [16:07] coming back to Guite's question: if you prefer to not go through the process, you can get changes to the one package you care about uploaded by sponsors [16:08] are there any questions? [16:08] who are the sponsors and how can we find them? [16:08] civija: good question :) [16:08] question: Which the basic kwnolege you need to become MOTU? [16:08] it's what I wanted to explain next :-) [16:09] The package I am going to maintain does neither exist in Debian nor Ubuntu yet. Hopefully this is no problem? [16:09] to get a patch uploaded, you file a bug report on the package it's about, attach the patch and subscribe a) ubuntu-main-sponsors (if it's in main/restricted) or b) ubuntu-universe-sponsors (if it's in universe/multiverse) [16:09] civija: with this process you don't need to know who's going to deal with it, it will always be different people in the team [16:10] aha, tnx [16:10] http://people.ubuntu.com/~dholbach/sponsoring/ is an overview of things that need sponsoring at the moment [16:10] xander21c: the most important thing if you want to joing the MOTU team is: you're a good team player and you're motivated to find solutions for problems [16:11] dholbach: if a contributor has worked on a number of packages, is there a way to know which sponsors upped his own work? [16:11] so it's not really important if you're a C hacker since 10 years, it's much more important that you ask if you have a question and people can trust you, but also you're willing to read docs and try to find out on your own [16:11] xander21c: nice to see you around here! [16:12] Guite: if the package is not in ubuntu/debian yet, that's not a problem - http://wiki.ubuntu.com/UbuntuDevelopment/NewPackages talks about this case [16:12] thx already found it :) [16:12] hi nxvl [16:12] warp10: the people who sponsor your work will most likely comment on your sponsoring bug reports [16:13] warp10: also the mail that goes to hardy-changes (every upload is announced there) will be CCed to them if I remember correctly [16:13] if not it will at least be signed with they gpg key [16:13] any other questions? [16:13] dholbach: no, it is't CCed [16:14] nxvl: ok, then at least the signature will tell you who uploaded it [16:14] dholbach: yes, that's right [16:14] Oh, got here too late! /me scrolls up to get ahead again. [16:14] * highvoltage got here too late too [16:14] alrighty - let's take a look at the current release schedule: https://wiki.ubuntu.com/HardyReleaseSchedule [16:15] as you can see on Feb 14th FeatureFreeze is coming up [16:15] this has a number of implications on what we work on [16:15] from that point on we need special exceptions for new upstream versions of packages, also exceptions for completely NEW packages [16:16] also given that Hardy will be an LTS release we put a lot of effort into quality assurance right now [16:16] https://wiki.ubuntu.com/MOTU/TODO lists a lot of bugs we work on [16:17] some of them are tagged as 'ftbfs' (fails to build from source) [16:17] others as 'unmetdeps' (these fail to install due to unmet dependencies) [16:17] other as 'bitesize' (suitable for new contributors) [16:17] etc etc. [16:17] there's a lot of work to be done and a lot of things to get started with :-) [16:18] any more questions? [16:18] dholbach: if I don't have the time to contribute on a regular basis, but still want to work on a few things I care about every now and then, is this okay with you? or are you looking for more dedicated contributors? [16:18] * warp10 has one about FF [16:18] ucap: that's absolutely OK [16:18] it happens a lot that people change job, move, do something else, then get back again and that's perfectly acceptable [16:18] warp10: fire away [16:19] dholbach: Feature Freeze means that merges/syncs are completely stopped, except for exceptions? [16:19] you can also browse the bitesize list of bugs on LP -> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=bitesize [16:19] dholbach> I have a question about the /sponsoring page. What do the numbers in parentheses after usernames mean? [16:19] warp10: merges and syncs are fine, except when they deal with new upstream versions [16:20] warp10: we just try to focus on fixing instead (if a fix involves a new upstream version that's mostly fine) [16:20] thanks nxvl [16:20] dholbach: so, merging foo 1.2.3-1 if in ubuntu we are at 1.2.2-1ubuntu1 isn't fine? [16:20] LucidFox: I subscribe people to sponsoring bugs, and the value in parentheses is the age of the subscription in days [16:20] dholbach: maybe this is too big a question, but what if I wanted to create the init scripts for the Pyro event server (178948), where would I start? would I download the source package from the hardy archives and once it's fixed, send it to revu? [16:20] warp10: after FF it'd require an exception [16:20] dholbach: ok, great. ty :) [16:21] highvoltage: you'd download the source, work on the init scripts to get them right, then prepare a debdiff (that's one of the tutorials I wanted to show), attach it to a bug report, get it sponsors - done :-) [16:22] Regarding bugs: the wiki says that I should set the status to Confirmed when subscribing sponsors. I'm a member of bug control - should I use Confirmed or Triaged? [16:22] dholbach: great, I think I'll try that with the tutorial then! [16:22] ok... any more general questions? please: also if you don't understand items in the questions and answers, please ask === dantalizing_ is now known as dantalizing [16:23] LucidFox: the membership of ubuntu-bugcontrol shouldn't matter in that regard - if it says 'confirmed' in the wiki, set it to confirmed [16:23] LucidFox: it will show up on the overview page in any case [16:23] anything else? [16:24] alright... let's get started with out first Tutorial then! [16:24] i didn't miss anything? :O [16:25] we'll deal with the problem that highvoltage asked about: you have a fix ready and want to generate a patch [16:25] aualin: check http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt later [16:26] ok, thx [16:26] first of all, we'll set two variables to let the packaging tools know who we are [16:26] please edit your ~/.bashrc [16:26] and add something like this to the bottom: [16:26] export DEBFULLNAME='Daniel Holbach' [16:26] export DEBEMAIL='daniel.holbach@ubuntu.com' [16:26] what if i use zsh? [16:26] aualin: you can use ~/.zshrc too (if that is its configuration file) [16:27] it is [16:27] we just want to make sure the variables are set, when we run our tools [16:27] so once you've done that, run [16:27] ok [16:27] source ~/.bashrc [16:27] to make sure it's active in the current session [16:27] all set? [16:27] sure [16:27] Rock and Roll [16:28] next we'll install a couple of tools we'll need along the way [16:28] sudo apt-get install devscripts build-essential wget fakeroot [16:28] devscripts and fakeroot are necessary for the packaging build process [16:28] already installed ;) [16:28] build-essential will pull in things like gcc and make you need to build source [16:29] wget is used for downloading things from http or ftp [16:29] first thing I always install on an ubuntu system [16:29] Hit3k, ++ [16:29] ok... next we'll download the source for a package I broke so we can fix it [16:29] dget -x http://people.ubuntu.com/~dholbach/motu/ubuntu-artwork_40.dsc [16:29] dget?? [16:30] wget ? [16:30] not wget? [16:30] dget :) [16:30] oh... [16:30] cool [16:30] debian get [16:30] ahh [16:30] this will download the .dsc file and additionally the .tar.gz [16:30] What's a .dsc file? [16:30] then check the checksums and extract it for us [16:30] got it [16:30] Laney: good question [16:30] a specifcation file? [16:30] run cat ubuntu-artwork_40.dsc [16:30] debian source code? [16:31] it contains information about the version of the source package, what the build-depends are, a checksum and so on [16:31] so its a description? [16:31] like the control file in debian subdirectory? [16:32] aualin: it contains part of it [16:32] ok [16:32] it's not necessary that we go through all attributes of it right now, it's just important to know that a .dsc and a .tar.gz are the minimum to call something a source package [16:32] ok [16:32] itsn't there usually a diff file also? [16:32] exactly [16:33] What does dsc stand for? [16:33] The log so far, for those who joined later: http://lucidfox.org/stuff/packaging101.txt [16:33] this is a bit of a special case: we are the upstream maintainer of ubuntu-artwork, which means that we, in Ubuntu, control all the pieces that go into it [16:33] badvista, awesome nick [16:33] zhazhou: debian source code [16:33] thanks [16:33] oldsam, okay (: thank you [16:34] zhaozhou: I'm not sure about "debian source code"... hmmm - I'll find out during the session, let's move on :) [16:34] cd ubuntu-artwork-40 [16:34] cat debian/control [16:34] if you look at the control file, you'll note that it contains two stanzas [16:35] DeSCribtion perhaps.. [16:35] the first one if about the source package and the second one is about the resulting binary package [16:35] badvista, I support the badvista campaign somewhat on my vsxu.com site :) [16:35] source package (.dsc, .tar.gz), binary package (.deb) [16:35] Build-Depends: debhelper (>= 5), cdbs specifies which packages are needed to build the package [16:36] to install them, we simply run: [16:36] jaw^vovoid: yes ok, i stole it from the fsf :D [16:36] cdbs is a kind of framework? [16:36] sudo apt-get build-dep ubuntu-artwork [16:36] can we try to keep the chatter elsewhere? I don't mind questions, but chatter can go to #ubuntu-offtopic or some other place - thanks :) [16:36] badvista: no problem with that IMO ;) [16:36] aualin: right... CDBS stands for common build system for Debian packages [16:37] ah [16:37] it's a set of Makefiles that simplify the package build system a lot [16:37] if a package needs a particular kernel module, would it appear in the dependencies ? [16:37] I like using CDBS, it has the disadvantage that a lot of things happen behind the scenes and it's not really obvious for somebody who begins packaging [16:37] ok [16:37] sounds good :D [16:37] but that's not really relevant for our example today :) [16:38] Beber80: that depends: Dependencies at install time go into Depends:, packages needed to build it go into Build-Depends [16:38] dholbach: what's the difference between debhelper and cdbs? or should I ask later? [16:38] everybody all set with build-depends? [16:38] highvoltage: CDBS makes use of debhelper [16:38] i run arch at the moment [16:39] yep [16:39] alright [16:39] yes, after lots of scrollkeeper parser errors [16:39] so, debhelper is a framework for debhelper? [16:39] so let's try to build it [16:39] * highvoltage had to add source uri's, it's updating so I'm a bit behind, but I'll catch up [16:39] let's run [16:39] debuild -us -uc [16:39] aualin> debhelper is a collection of scripts that simplify writing debian/rules files [16:39] dholbach: where? [16:39] and CDBS is built atop debhelper [16:39] LucidFox: ok [16:39] doluu: in the ubuntu-artwork-40 directory [16:40] ok [16:40] does it work for anybody? [16:40] I got an error [16:40] no, error [16:40] Hit3k: which one is it? [16:40] should we not run fakeroot debuild -us -uc? [16:40] me tto [16:40] aualin: debuild uses fakeroot itself [16:40] ah... [16:40] Jergar: what's the error message? [16:40] Oh no, an error! [16:40] Aufruf von stat für „./xxxdistributor-logo.png“ nicht möglich [16:40] cp: cannot stat `./xxxdistributor-logo.png': No such file or directory :( [16:40] debuild: fatal error at line 1247: [16:40] fakeroot debian/rules binary failed [16:40] exactly, that's the one [16:40] thats mine except in english [16:41] no, error [16:41] the call that raise the error was: dh_install -pubuntu-artwork [16:41] we need to change the path, right? [16:41] ah, yes, a bit farther up I see. [16:41] so when the files were supposed to be installed into the package, it could not find `./xxxdistributor-logo.png' [16:42] ls -lrt [16:42] if you type ls [16:42] hehe [16:42] * highvoltage got the same error :) [16:42] you'll see how it's supposed to look like [16:42] distributor-logo.png [16:42] now if we edit debian/install we can change it to distributor-logo.png [16:43] before we build it again, let's document the change in debian/changelog [16:43] just run [16:43] dch -i [16:43] a few things worth noting: [16:44] - if you do changes in any package, document them as detailed as possible, the next person to look at the package will be VERY happy about that [16:44] - be sure that the string next to the version number says "hardy" [16:45] (that's the current development branch and the only thing we can upload to) [16:45] got kicked about 2 mins ago....where's the log again? [16:45] question: dch doesn't use $DEBEMAIL, ist this right? [16:45] Is it possible to make patches for hardy on gutsy? [16:45] h3b: it should [16:45] dholbach: * Fix Path of the Logo in debian/install <-- something like this? [16:45] Hit3k_: yes, but it's preferrable if you could test things on the branch you upload it to :) [16:46] jwill2: check http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt later [16:46] h3b: i had that same problem, looking into it now [16:46] - make sure the version number is 41 (this is the special case of a 'native' package) [16:46] what about urgency? how do I decide what to set it to in the changelog? [16:47] subterrific: echo $DEBEMAIL? [16:47] subterrific, h3b: did you run source ~.bashrc ? [16:47] it works... [16:47] source ~/.bashrc [16:47] dch renamed my current directory :) [16:47] ucap: we don't use 'urgency' in Ubuntu land [16:47] or, source ~/.zshrc [16:47] forgot the E in DEB'E'MAIL ;) [16:47] right [16:47] h3b: ok [16:47] h3b: you have to log in again before the .bashrc changes will take effect [16:47] hellboy195: yes, that's OK - here's what I put into mine: [16:47] oh, sorry, I'm catching up [16:48] ubuntu-artwork (41) hardy; urgency=low [16:48] * debian/install: fixed file name. [16:48] -- Daniel Holbach Tue, 15 Jan 2008 17:43:45 +0100 [16:48] parsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 4 [16:48] parsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 4 [16:48] parsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 4 [16:48] parsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 4 [16:48] parsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 4 [16:48] got parsechangelog/debian: error: found start of entry where expected start of change data [16:48] sorry [16:48] dholbach: how os " * Renamed xxxdistributorlogo.png to distributerlogo.png in debian/install [16:48] " ? [16:48] dholbach, so as we just have to be descriptive? [16:48] highvoltage: I suppose too long [16:48] ah [16:48] highvoltage: that's fine too... I usually put the name of the file I changed first, but yours is good too [16:48] Hit3k_: yeah [16:49] Jergar: if you could pastebin your entry somewhere, we could examine it later [16:49] ok [16:49] alrighty... let's see if with our new change it builds again [16:49] let's run debuild -us -uc again [16:50] :D [16:50] if you now run ls .. it will show you a shiny *.deb package [16:50] we just fixed our first FTBFS :) [16:50] ok, how would we submit a patch? [16:51] dholbach: ignore lintian about the standards version? [16:51] hellboy195: yeah [16:51] FTBFS? [16:51] doluu: Fails To Build From Source [16:51] sorry [16:51] you can find a lot of abbreviations on http://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations [16:51] doluu: no problem - just ask :) [16:52] we'll build a new source package of our new version now [16:52] we'll run debuild -S [16:52] which will not build a binary package (.deb) but a new source package === robert00frag_ is now known as robert00frag [16:52] done? [16:52] dholbach: may I ask you what the "-sa" option does? [16:53] hellboy195: the "-sa" option is not necessary in this case, it's just relevant if you want to upload a source package somewhere and specifically want to include the .orig.tar.gz [16:53] I need my gpg key which isn't on this computer [16:53] (which in our case does not apply anyway) [16:53] isn't debuild use env vars we exported before? [16:53] Hit3k_: ignore the warning for now [16:54] ok [16:54] doluu: it should [16:54] ls [16:54] sry [16:54] if you get a warning about a GPG key it's not relevant right now (might be due to exact mail address not being on your gpg key as an id) [16:55] what if I dont have a key? [16:55] if you now run: [16:55] ls ..; debdiff ubuntu-artwork_40.dsc ubuntu-artwork_41.dsc [16:55] you will get a debdiff that's suitable for attaching to a bug report [16:55] doluu: you'll need to generate on [16:55] ls -lrt [16:55] doluu: gpg --gen-key [16:55] one [16:55] gah... [16:55] dholbach: ok [16:55] s/ls/cd ? [16:55] not for this tutorial, but for general work, you'll have to [16:55] https://help.ubuntu.com/community/GnuPrivacyGuardHowto for more information on that [16:56] doluu: a gpg key is only needed for uploading e.g. REVU or as a MOTU to the archive [16:56] Laney: yes, sorry [16:56] cd ..; debdiff ubuntu-artwork_40.dsc ubuntu-artwork_41.dsc [16:56] debdiff ubuntu-artwork_40.dsc ubuntu-artwork_41.dsc > debdiff would give you the patch file you'd attach to a bug report to get it sponsored [16:57] http://wiki.ubuntu.com/SponsorshipProcess has more information to get that done [16:57] ah, my version ended with ubuntu1, not 41 [16:57] highvoltage: yeah, this was a special case [16:57] ok... end of tutorial 1 - everybody still excited? [16:57] yes [16:58] * highvoltage is super-excited [16:58] :D [16:58] w00t [16:58] NICE - that's what I want to hear :-) [16:58] +1 excited [16:58] it's easier than I was expecting [16:58] let's press on then [16:58] yes, me too, I with I attended a motu-class ages ago [16:58] damn, I missed it >.< [16:58] next we'll try to update a package to a new upstream version [16:58] woohoo [16:58] yay [16:59] M2AU: check http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt later [16:59] thanks! [16:59] alright... let's get the source for the hello package: [16:59] dget -x http://archive.ubuntu.com/ubuntu/pool/main/h/hello/hello_2.2-2.dsc [16:59] http://lucidfox.org/stuff/packaging101.txt <-- log updated [16:59] and now let's get the new upstream version of hello [17:00] wget http://ftp.gnu.org/gnu/hello/hello-2.3.tar.gz [17:00] the GNU hello guys will probably wonder about the sudden interest in the new hello tarball :-) [17:00] haha [17:00] heh [17:00] :P [17:00] lol [17:01] ok, we'll do this the manual way, there are other tools to update packages in a semi-automated way [17:01] first we unpack the new upstream tarball [17:01] tar xfz hello-2.3.tar.gz [17:01] (not that the "z" is needed in ubuntu anymore :) ) [17:01] then rename it to the standard name of tarballs in debian/ubuntu source packages [17:02] mv hello-2.3.tar.gz hello_2.3.orig.tar.gz [17:02] if you look at the files we downloaded, you'll notice these three: [17:02] hello_2.2-2.diff.gz hello_2.2-2.dsc hello_2.2.orig.tar.g [17:02]