/srv/irclogs.ubuntu.com/2008/01/15/#ubuntu-classroom.txt

=== bigon is now known as bigon`
=== andrew__ is now known as null-cipher
* AxCray_ Binar06:04
=== AxCray_ is now known as Binar
KcRiderHi12:28
plasticman..13:05
gusse02leave13:05
pipedream.14:07
pipedreamwasn't there a class today?14:07
=== Pricey is now known as PriceChild
pleia2the only thing on the agenda is for the 17th14:10
imzaphodmotu class today 16:00 - 17:30 utc14:11
dholbachpleia2: the packaging 101 session will be today14:16
pleia2dholbach: what is the schedule for that exactl?14:16
* pleia2 really must start keeping track of this :)14:17
pipedreamoh14:17
pipedreamutc14:17
dholbachhttp://fridge.ubuntu.com14:17
pipedreamhere in cape town that is another 2 hours14:17
dholbachsame here :)14:17
=== nxvl_ is now known as nxvl
angoram i right that todays "event" is starting at 6pm utc? ( in germany 7pm?)15:30
durgisI thought it was 16:00 or 4 pm.15:30
pleia2durgis is correct15:30
angorso it starts in half an hour?15:31
dholbachangor: yeah :)15:31
angorcool, thanks :)15:31
dholbachbring it on!15:31
angori hope nobody minds if i log this, for later use or as a transscript for ubuntuusers.de (if nobody else logs it)15:32
dholbachangor: no, that's great15:32
angorif somebody wants his name deleted, he/she/it should contact me so that i can cut it out15:33
dholbachangor: this channel is logged publically anyway: http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt15:34
angoroh, yeah, did not think of it15:34
angor^^15:34
angorthen forget about it15:35
angorbrb15:35
angorre, is the "motuguide" also understandable for packaging beginners?15:42
=== virilius is now known as edfonseca
pipedreambits of it15:43
pipedreamone has to read quite a bit to understand the full debian package15:44
pipedream(not there yet)15:44
pipedreamand then there is all this pbuilder stuff on top15:44
edfonsecavamos ao coffee entao?15:44
pipedreammany ways to skin a deb15:44
angorwell, 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 info15:45
RoyShi leute15:50
pipedreamangor: not that I'm there yet!15:51
angorhallo roys, hier ist englisch angesagt ;)15:51
RoySooops15:52
RoySsorry15:52
=== matthew is now known as MattBD
=== Per is now known as md2perpe
=== bigon` is now known as bigon
dholbachWelcome to the Packaging 101 Session!16:00
dholbachHow are you all doing?16:00
GuiteHi. Fine, thanks16:00
hellboy195excited ;)16:00
Hit3k:D16:00
durgisGood here.16:00
Soltyfine :>16:00
voriangood :)16:00
LucidFoxWhat they said. :)16:00
dholbachGreat - who of you wants to become a MOTU? :-)16:00
* hellboy195 :)16:00
LucidFoxI do.16:00
Hit3k<----16:00
* vorian raises his hand16:00
* warp10 raises a finger16:00
* Guite wants to maintain a particular package...16:00
grayravenI do16:00
Guitedo not know if this requires being a MOTU ;)16:01
dholbachROCK AND ROLL :-)16:01
* dantalizing wants ta16:01
dholbachgreat to hear that16:01
dholbachGuite: I'll answer the question in a bit16:01
doluuI do16:01
dholbachSo what does it take to become a MOTU? Best point to start is http://wiki.ubuntu.com/MOTU/GettingStarted16:01
dholbachit links to all the necessary information and takes you by the hand on your way to MOTU membership :)16:02
dholbachthere are three areas on the wiki that are important to become an Ubuntu developer16:02
dholbachFirst of all http://wiki.ubuntu.com/UbuntuDevelopment - which links to all information about Development processes16:02
dholbachso things like how to merge, how to do a sync request, how the archive machinery works and so on16:03
dholbachhttp://wiki.ubuntu.com/PackagingGuide has a lot of information about packaging - so all the bits that are necessary to build packages from source code16:03
dholbachand last but not least http://wiki.ubuntu.com/MOTU - which has information about the MOTU team, its events, its governance, etc16:03
* LucidFox raises his hand16:04
dholbachLucidFox: fire away16:04
LucidFoxis the packaging guide on th wiki older or newer than the one on help.ubuntu.com?16:04
dholbachLucidFox: 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 places16:04
dholbachthese three wiki namespace are the definite areas you should hit up, when you run into problems16:05
dholbachSo what's the process for becoming a MOTU?16:05
dholbachIt'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 daemons16:06
pipedreambuild daemons++16:06
Guitek16:06
dholbachafter 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 application16:07
dholbachand that's it16:07
Guiteprobationary period ^^16:07
dholbachcoming 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 sponsors16:07
dholbachare there any questions?16:08
civijawho are the sponsors and how can we find them?16:08
dholbachcivija: good question :)16:08
xander21cquestion: Which the basic kwnolege you need to become MOTU?16:08
dholbachit's what I wanted to explain next :-)16:08
GuiteThe package I am going to maintain does neither exist in Debian nor Ubuntu yet. Hopefully this is no problem?16:09
dholbachto 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
dholbachcivija: with this process you don't need to know who's going to deal with it, it will always be different people in the team16:09
civijaaha, tnx16:10
dholbachhttp://people.ubuntu.com/~dholbach/sponsoring/ is an overview of things that need sponsoring at the moment16:10
dholbachxander21c: 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 problems16:10
warp10dholbach: if a contributor has worked on a number of packages, is there a way to know which sponsors upped his own work?16:11
dholbachso 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 own16:11
nxvlxander21c: nice to see you around here!16:11
dholbachGuite: if the package is not in ubuntu/debian yet, that's not a problem - http://wiki.ubuntu.com/UbuntuDevelopment/NewPackages talks about this case16:12
Guitethx already found it :)16:12
xander21chi nxvl16:12
dholbachwarp10: the people who sponsor your work will most likely comment on your sponsoring bug reports16:12
dholbachwarp10: also the mail that goes to hardy-changes (every upload is announced there) will be CCed to them if I remember correctly16:13
dholbachif not it will at least be signed with they gpg key16:13
dholbachany other questions?16:13
nxvldholbach: no, it is't CCed16:13
dholbachnxvl: ok, then at least the signature will tell you who uploaded it16:14
nxvldholbach: yes, that's right16:14
zhaozhouOh, got here too late! /me scrolls up to get ahead again.16:14
* highvoltage got here too late too16:14
dholbachalrighty - let's take a look at the current release schedule: https://wiki.ubuntu.com/HardyReleaseSchedule16:14
dholbachas you can see on Feb 14th FeatureFreeze is coming up16:15
dholbachthis has a number of implications on what we work on16:15
dholbachfrom that point on we need special exceptions for new upstream versions of packages, also exceptions for completely NEW packages16:15
dholbachalso given that Hardy will be an LTS release we put a lot of effort into quality assurance right now16:16
dholbachhttps://wiki.ubuntu.com/MOTU/TODO lists a lot of bugs we work on16:16
dholbachsome of them are tagged as 'ftbfs' (fails to build from source)16:17
dholbachothers as 'unmetdeps' (these fail to install due to unmet dependencies)16:17
dholbachother as 'bitesize' (suitable for new contributors)16:17
dholbachetc etc.16:17
dholbachthere's a lot of work to be done and a lot of things to get started with :-)16:17
dholbachany more questions?16:18
ucapdholbach: 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 FF16:18
dholbachucap: that's absolutely OK16:18
dholbachit happens a lot that people change job, move, do something else, then get back again and that's perfectly acceptable16:18
dholbachwarp10: fire away16:18
warp10dholbach: Feature Freeze means that merges/syncs are completely stopped, except for exceptions?16:19
nxvlyou can also browse the bitesize list of bugs on LP -> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=bitesize16:19
LucidFoxdholbach> I have a question about the /sponsoring page. What do the numbers in parentheses after usernames mean?16:19
dholbachwarp10: merges and syncs are fine, except when they deal with new upstream versions16:19
dholbachwarp10: we just try to focus on fixing instead (if a fix involves a new upstream version that's mostly fine)16:20
dholbachthanks nxvl16:20
warp10dholbach: so, merging foo 1.2.3-1 if in ubuntu we are at 1.2.2-1ubuntu1 isn't fine?16:20
dholbachLucidFox: I subscribe people to sponsoring bugs, and the value in parentheses is the age of the subscription in days16:20
highvoltagedholbach: 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
dholbachwarp10: after FF it'd require an exception16:20
warp10dholbach: ok, great. ty :)16:20
dholbachhighvoltage: 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:21
LucidFoxRegarding 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
highvoltagedholbach: great, I think I'll try that with the tutorial then!16:22
dholbachok... any more general questions? please: also if you don't understand items in the questions and answers, please ask16:22
=== dantalizing_ is now known as dantalizing
dholbachLucidFox: the membership of ubuntu-bugcontrol shouldn't matter in that regard - if it says 'confirmed' in the wiki, set it to confirmed16:23
dholbachLucidFox: it will show up on the overview page in any case16:23
dholbachanything else?16:23
dholbachalright... let's get started with out first Tutorial then!16:24
aualini didn't miss anything? :O16:24
dholbachwe'll deal with the problem that highvoltage asked about: you have a fix ready and want to generate a patch16:25
dholbachaualin: check  http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt  later16:25
aualinok, thx16:26
dholbachfirst of all, we'll set two variables to let the packaging tools know who we are16:26
dholbachplease edit your   ~/.bashrc16:26
dholbachand add something like this to the bottom:16:26
dholbachexport DEBFULLNAME='Daniel Holbach'16:26
dholbachexport DEBEMAIL='daniel.holbach@ubuntu.com'16:26
aualinwhat if i use zsh?16:26
dholbachaualin: you can use   ~/.zshrc   too (if that is its configuration file)16:26
aualinit is16:27
dholbachwe just want to make sure the variables are set, when we run our tools16:27
dholbachso once you've done that, run16:27
aualinok16:27
dholbach  source ~/.bashrc16:27
dholbachto make sure it's active in the current session16:27
dholbachall set?16:27
aualinsure16:27
dholbachRock and Roll16:27
dholbachnext we'll install a couple of tools we'll need along the way16:28
dholbach  sudo apt-get install devscripts build-essential wget fakeroot16:28
dholbachdevscripts and fakeroot are necessary for the packaging build process16:28
h3balready installed ;)16:28
dholbachbuild-essential will pull in things like gcc and make you need to build source16:28
dholbachwget is used for downloading things from http or ftp16:29
Hit3kfirst thing I always install on an ubuntu system16:29
zhaozhouHit3k, ++16:29
dholbachok... next we'll download the source for a package I broke so we can fix it16:29
dholbach dget -x http://people.ubuntu.com/~dholbach/motu/ubuntu-artwork_40.dsc16:29
oldsamdget??16:29
aualinwget ?16:30
oldsamnot wget?16:30
dholbachdget :)16:30
aualinoh...16:30
aualincool16:30
javamaniacdebian get16:30
oldsamahh16:30
dholbachthis will download the .dsc file and additionally the .tar.gz16:30
LaneyWhat's a .dsc file?16:30
dholbachthen check the checksums and extract it for us16:30
doluugot it16:30
dholbachLaney: good question16:30
aualina specifcation file?16:30
dholbachrun     cat ubuntu-artwork_40.dsc16:30
inkbuntudebian source code?16:30
dholbachit contains information about the version of the source package, what the build-depends are, a checksum and so on16:31
Hit3kso its a description?16:31
aualinlike the control file in debian subdirectory?16:31
dholbachaualin: it contains part of it16:32
aualinok16:32
dholbachit'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 package16:32
aualinok16:32
aualinitsn't there usually a diff file also?16:32
dholbachexactly16:32
zhaozhouWhat does dsc stand for?16:33
LucidFoxThe log so far, for those who joined later: http://lucidfox.org/stuff/packaging101.txt16:33
dholbachthis 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 it16:33
jaw^vovoidbadvista, awesome nick16:33
oldsamzhazhou: debian source code16:33
badvistathanks16:33
zhaozhouoldsam, okay (: thank you16:33
dholbachzhaozhou: I'm not sure about "debian source code"... hmmm - I'll find out during the session, let's move on :)16:34
dholbach cd ubuntu-artwork-4016:34
dholbach cat debian/control16:34
dholbachif you look at the control file, you'll note that it contains two stanzas16:34
zhaozhouDeSCribtion perhaps..16:35
dholbachthe first one if about the source package and the second one is about the resulting binary package16:35
jaw^vovoidbadvista, I support the badvista campaign somewhat on my vsxu.com site :)16:35
dholbachsource package (.dsc, .tar.gz), binary package (.deb)16:35
dholbachBuild-Depends: debhelper (>= 5), cdbs       specifies which packages are needed to build the package16:35
dholbachto install them, we simply run:16:36
badvistajaw^vovoid: yes ok, i stole it from the fsf :D16:36
aualincdbs is a kind of framework?16:36
dholbach  sudo apt-get build-dep ubuntu-artwork16:36
dholbachcan 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
jaw^vovoidbadvista: no problem with that IMO ;)16:36
dholbachaualin: right... CDBS stands for common build system for Debian packages16:36
aualinah16:37
dholbachit's a set of Makefiles that simplify the package build system a lot16:37
Beber80if a package needs a particular kernel module, would it appear in the dependencies ?16:37
dholbachI 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 packaging16:37
aualinok16:37
aualinsounds good :D16:37
dholbachbut that's not really relevant for our example today :)16:37
dholbachBeber80: that depends: Dependencies at install time go into Depends:, packages needed to build it go into Build-Depends16:38
highvoltagedholbach: what's the difference between debhelper and cdbs? or should I ask later?16:38
dholbacheverybody all set with build-depends?16:38
dholbachhighvoltage: CDBS makes use of debhelper16:38
aualini run arch at the moment16:38
doluuyep16:39
dholbachalright16:39
subterrificyes, after lots of scrollkeeper parser errors16:39
aualinso, debhelper is a framework for debhelper?16:39
dholbachso let's try to build it16:39
* highvoltage had to add source uri's, it's updating so I'm a bit behind, but I'll catch up16:39
dholbachlet's run16:39
dholbach  debuild -us -uc16:39
LucidFoxaualin> debhelper is a collection of scripts that simplify writing debian/rules files16:39
doluudholbach: where?16:39
LucidFoxand CDBS is built atop debhelper16:39
aualinLucidFox: ok16:39
dholbachdoluu: in the ubuntu-artwork-40 directory16:39
doluuok16:40
dholbachdoes it work for anybody?16:40
Hit3kI got an error16:40
h3bno, error16:40
dholbachHit3k: which one is it?16:40
aualinshould we not run fakeroot debuild -us -uc?16:40
Jergarme tto16:40
dholbachaualin: debuild uses fakeroot itself16:40
aualinah...16:40
dholbachJergar: what's the error message?16:40
LaneyOh no, an error!16:40
Jergar Aufruf von stat für „./xxxdistributor-logo.png“ nicht möglich16:40
da1l6cp: cannot stat `./xxxdistributor-logo.png': No such file or directory :(16:40
durgisdebuild: fatal error at line 1247:16:40
durgisfakeroot debian/rules binary failed16:40
dholbachexactly, that's the one16:40
Hit3kthats mine except in english16:40
doluuno, error16:41
dholbachthe call that raise the error was:    dh_install -pubuntu-artwork16:41
aualinwe need to change the path, right?16:41
durgisah, yes, a bit farther up I see.16:41
dholbachso when the files were supposed to be installed into the package, it could not find `./xxxdistributor-logo.png'16:41
durgisls -lrt16:42
dholbachif you type     ls16:42
durgishehe16:42
* highvoltage got the same error :)16:42
dholbachyou'll see how it's supposed to look like16:42
doluudistributor-logo.png16:42
dholbachnow if we edit    debian/install    we can change it to distributor-logo.png16:42
dholbachbefore we build it again, let's document the change in debian/changelog16:43
dholbachjust run16:43
dholbach  dch -i16:43
dholbacha few things worth noting:16:43
dholbach - 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 that16:44
dholbach - be sure that the string next to the version number says  "hardy"16:44
dholbach(that's the current development branch and the only thing we can upload to)16:45
jwill2got kicked about 2 mins ago....where's the log again?16:45
h3bquestion: dch doesn't use $DEBEMAIL, ist this right?16:45
Hit3k_Is it possible to make patches for hardy on gutsy?16:45
dholbachh3b: it should16:45
hellboy195dholbach: * Fix Path of the Logo in debian/install    <-- something like this?16:45
dholbachHit3k_: yes, but it's preferrable if you could test things on the branch you upload it to :)16:45
dholbachjwill2: check  http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt  later16:46
subterrifich3b: i had that same problem, looking into it now16:46
dholbach - make sure the version number is 41 (this is the special case of a 'native' package)16:46
ucapwhat about urgency? how do I decide what to set it to in the changelog?16:46
h3bsubterrific: echo $DEBEMAIL?16:47
dholbachsubterrific, h3b: did you run      source ~.bashrc   ?16:47
h3bit works...16:47
dholbachsource ~/.bashrc16:47
doluudch renamed my current directory :)16:47
dholbachucap: we don't use 'urgency' in Ubuntu land16:47
aualinor, source ~/.zshrc16:47
h3bforgot the E in DEB'E'MAIL ;)16:47
dholbachright16:47
dholbachh3b: ok16:47
highvoltageh3b: you have to log in again before the .bashrc changes will take effect16:47
dholbachhellboy195: yes, that's OK - here's what I put into mine:16:47
highvoltageoh, sorry, I'm catching up16:47
dholbachubuntu-artwork (41) hardy; urgency=low16:48
dholbach  * debian/install: fixed file name.16:48
dholbach -- Daniel Holbach <daniel.holbach@ubuntu.com>  Tue, 15 Jan 2008 17:43:45 +010016:48
Jergarparsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 416:48
Jergarparsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 416:48
Jergarparsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 416:48
Jergarparsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 416:48
Jergarparsechangelog/debian: error: found start of entry where expected start of change data, at file debian/changelog line 416:48
Jergargot parsechangelog/debian: error: found start of entry where expected start of change data16:48
Jergarsorry16:48
highvoltagedholbach: how os "  * Renamed xxxdistributorlogo.png to distributerlogo.png in debian/install16:48
highvoltage" ?16:48
Hit3k_dholbach, so as we just have to be descriptive?16:48
hellboy195highvoltage: I suppose too long16:48
highvoltageah16:48
dholbachhighvoltage: that's fine too... I usually put the name of the file I changed first, but yours is good too16:48
dholbachHit3k_: yeah16:48
dholbachJergar: if you could pastebin your entry somewhere, we could examine it later16:49
Jergarok16:49
dholbachalrighty... let's see if with our new change it builds again16:49
dholbachlet's run   debuild -us -uc    again16:49
Hit3k_:D16:50
dholbachif you now run          ls ..          it will show you a shiny  *.deb   package16:50
dholbachwe just fixed our first FTBFS :)16:50
dholbachok, how would we submit a patch?16:50
hellboy195dholbach: ignore lintian about the standards version?16:51
dholbachhellboy195: yeah16:51
doluuFTBFS?16:51
dholbachdoluu: Fails To Build From Source16:51
doluusorry16:51
dholbachyou can find a lot of abbreviations on     http://wiki.ubuntu.com/UbuntuDevelopment/Abbreviations16:51
dholbachdoluu: no problem - just ask :)16:51
dholbachwe'll build a new source package of our new version now16:52
dholbachwe'll run        debuild -S16:52
dholbachwhich will not build a binary package (.deb) but a new source package16:52
=== robert00frag_ is now known as robert00frag
dholbachdone?16:52
hellboy195dholbach: may I ask you what the "-sa" option does?16:52
dholbachhellboy195: 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.gz16:53
Hit3k_I need my gpg key which isn't on this computer16:53
dholbach(which in our case does not apply anyway)16:53
doluuisn't debuild use env vars we exported before?16:53
dholbachHit3k_: ignore the warning for now16:53
Hit3k_ok16:54
dholbachdoluu: it should16:54
oldsamls16:54
oldsamsry16:54
dholbachif 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:54
doluuwhat if I dont have a key?16:55
dholbachif you now run:16:55
dholbach  ls ..; debdiff ubuntu-artwork_40.dsc ubuntu-artwork_41.dsc16:55
dholbachyou will get a debdiff that's suitable for attaching to a bug report16:55
dholbachdoluu: you'll need to generate on16:55
durgisls -lrt16:55
aualindoluu: gpg --gen-key16:55
dholbachone16:55
durgisgah...16:55
doluudholbach: ok16:55
Laneys/ls/cd ?16:55
dholbachnot for this tutorial, but for general work, you'll have to16:55
dholbachhttps://help.ubuntu.com/community/GnuPrivacyGuardHowto for more information on that16:55
geserdoluu: a gpg key is only needed for uploading e.g. REVU or as a MOTU to the archive16:56
dholbachLaney: yes, sorry16:56
dholbach  cd ..; debdiff ubuntu-artwork_40.dsc ubuntu-artwork_41.dsc16:56
dholbachdebdiff 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 sponsored16:56
dholbachhttp://wiki.ubuntu.com/SponsorshipProcess has more information to get that done16:57
highvoltageah, my version ended with ubuntu1, not 4116:57
dholbachhighvoltage: yeah, this was a special case16:57
dholbachok... end of tutorial 1 - everybody still excited?16:57
h3byes16:57
* highvoltage is super-excited16:58
Hit3k_:D16:58
vorianw00t16:58
dholbachNICE - that's what I want to hear :-)16:58
dantalizing+1 excited16:58
doluuit's easier than I was expecting16:58
dholbachlet's press on then16:58
highvoltageyes, me too, I with I attended a motu-class ages ago16:58
M2AUdamn, I missed it >.<16:58
dholbachnext we'll try to update a package to a new upstream version16:58
pak33m|workwoohoo16:58
Hit3k_yay16:58
dholbachM2AU:  check  http://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt  later16:59
M2AUthanks!16:59
dholbachalright... let's get the source for the hello package:16:59
dholbach dget -x http://archive.ubuntu.com/ubuntu/pool/main/h/hello/hello_2.2-2.dsc16:59
LucidFoxhttp://lucidfox.org/stuff/packaging101.txt <-- log updated16:59
dholbachand now let's get the new upstream version of hello16:59
dholbach wget http://ftp.gnu.org/gnu/hello/hello-2.3.tar.gz17:00
dholbachthe GNU hello guys will probably wonder about the sudden interest in the new hello tarball :-)17:00
Hit3k_haha17:00
highvoltageheh17:00
aualin:P17:00
warp10lol17:00
dholbachok, we'll do this the manual way, there are other tools to update packages in a semi-automated way17:01
dholbachfirst we unpack the new upstream tarball17:01
dholbach tar xfz hello-2.3.tar.gz17:01
highvoltage(not that the "z" is needed in ubuntu anymore :) )17:01
dholbachthen rename it to the standard name of tarballs in debian/ubuntu source packages17:01
dholbach mv hello-2.3.tar.gz hello_2.3.orig.tar.gz17:02
dholbachif you look at the files we downloaded, you'll notice these three:17:02
dholbachhello_2.2-2.diff.gz  hello_2.2-2.dsc  hello_2.2.orig.tar.g17:02
dholbachoops17:02
dholbachhello_2.2-2.diff.gz  hello_2.2-2.dsc  hello_2.2.orig.tar.gz17:02
highvoltageshould we just rename 2.2, dholbach?17:02
doluuright, I see17:03
dholbachhello_2.2.orig.tar.gz was the upstream tarball that was downloaded of the GNU page17:03
dholbachthe .diff.gz file is the changes the maintainer had to make to make it build in debian/ubuntu17:03
dholbachthis usually contains the  debian/  directory17:03
dholbachhighvoltage: hm?17:03
dholbachhighvoltage: mv hello-2.3.tar.gz hello_2.3.orig.tar.gz     is the only thing you need to rename17:03
dholbachnow we'll manually copy over the   debian/   changes from the old version to the new one17:04
dholbach cp -r hello-2.2/debian/ hello-2.3/17:04
doluudone :17:04
dholbach(applying the old patch would be more elegant)17:04
dholbachnow we'll document our changes to the package17:04
dholbach cd hello-2.317:05
dholbach dch -i17:05
dholbacha notice saying  " * New upstream release"  should be enough for now17:05
dholbachmake sure you have   hardy   as upload target17:05
doluuversion number will be 2.3-0ubuntu1? or 2.3-ubuntu1?17:06
dholbachand also make sure     2.3-0ubuntu1    is the version number17:06
dholbachcan anybody explain why it's "2.3-0ubuntu1"?17:06
aualinsince we made changes we add 1 on the end17:06
dholbachthe version before that was   2.2-2   - what does that mean?17:06
doluu0 is debian version17:06
aualinand the package is for ubuntu17:06
vorianit's an ubuntu delta17:07
jwill20 is because it doesn't exist in Ubuntu yet17:07
dholbach2.2 means the upstream version number (the 2.2 released tarball from GNU)17:07
aualinthat we made it ubuntu-friendly and updated it to 2.317:07
dholbach-2 means the second revision in debian17:07
doluuubuntu1 means it's first revision in Ubuntu, right?17:07
dholbachwe updated to 2.3, therefore introduced ubuntu changes and since the package is not in debian yet, we'll call it 0ubuntu117:07
highvoltagehow can a program that just prints "Hello world" have so much revisions and versions!?17:08
dholbachdoluu: first version that introduced ubuntu changes over the debian version17:08
aualinit's international17:08
doluugot it17:08
Hit3k_highvoltage, they keep spelling hello wrong perhaps?17:08
dholbachhighvoltage: good question -    less Changelog       will probably help :)17:08
dholbachalrighty17:08
highvoltagecool, will do that!17:08
aualinnah, the say hello world in a lot of languages17:08
dholbachlet's try to build it17:08
dholbach debuild -us -uc17:08
dholbachI get this error:    dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address17:09
dholbachwho gets it too?17:09
Hit3k_I do17:09
dholbachHit3k_: you used a ubuntu.com mail address?17:09
doluubuilding .......17:09
Jergarfinished :-)17:09
Hit3k_dholbach, don't have one17:09
hellboy195dholbach: I have 3 lintian warnings but I doesn't aborted :)17:10
durgismine appears to finish as well.17:10
dholbachthe error message I got complains about the Maintainer field in debian/control17:10
doluufinished :)17:10
dholbachsome of you might not have gotten it due to the version of dpkg or depending on which email address you used17:10
Laneydurgis: I get that warning right at the top of the output17:10
dholbachHit3k_ and I will fix the problem we have right now :)17:11
durgisLaney: ah, yes there is a warning there.17:11
dholbachour friends at Debian decided that we need to change the Maintainer field on Ubuntu uploads but still preserve the original maintainer17:11
highvoltagehmm, I used my ubuntu address and got the same error17:11
dholbachhttp://wiki.ubuntu.com/DebianMaintainerField has more information about that17:11
dholbachwe'll edit   debian/control17:12
greg-gdholbach: quick question, will the packages you used (the one on your webspace) be available later for those that can't participate now?17:12
dholbachand change Maintainer: Santiago Vila <sanvila@debian.org> to:17:12
dholbachXSBC-Original-Maintainer: Santiago Vila <sanvila@debian.org>17:12
dholbachMaintainer: Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com>17:12
dholbachgreg-g: yes17:13
greg-gthanks17:13
dholbachthat way the original maintainer will still be documented17:13
dholbachbut they won't get mails by ubuntu users who want to mail "the maintainer"17:13
dholbachnow we'll document it in debian/changelog17:14
dholbachjust run    dch     now17:14
h3bshould i change the email to: ...@ubuntu.com?17:14
dholbach  * debian/control: adhere to http://wiki.ubuntu.com/DebianMaintainerField17:14
dholbachshould be good17:14
dholbachh3b: change Maintainer: Santiago Vila <sanvila@debian.org> to:17:15
dholbach XSBC-Original-Maintainer: Santiago Vila <sanvila@debian.org>17:15
dholbach Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com>17:15
dholbachnow if we build it again:    debuild -us -uc   (this ommits the signing step at the end)17:15
dholbachit should build fine for you :)17:15
Hit3k_yep17:16
dholbachso we should have          hello_2.3-0ubuntu1.diff.gz    hello_2.3-0ubuntu1.dsc      hello_2.3.orig.tar.gz       (source package)                 and               hello_2.3-0ubuntu1_i386.deb     (binary package right now)17:16
dholbachexcellent :-)17:17
dholbachany questions about it?17:17
dholbachany more general questions?17:17
aualinnope17:17
marioyes17:17
subterrificdholbach: well i figured out my DEBEMAIL problem17:17
dholbachmario: fire away17:18
dholbachsubterrific: great17:18
highvoltagedholbach: I have a question... we just packaged source code, right?17:18
emil_sI have a hello_2.3-0ubuntu1_i386.build and hello_2.3-0ubuntu1_i386.changes to.17:18
mariocan i make out of any sources (tar.gz) a Binary (deb)?17:18
highvoltagedholbach: but a source package doesn't necasarily contain just source?17:18
dholbachhighvoltage: we fixed a bug in an existing source package and updated an existing source package to a new version17:18
dholbachemil_s: .build is a log and .changes is another meta-data file17:19
JergarI have a  hello_2.3-0ubuntu1_i386.deb17:19
subterrificdholbach: for some reason nothing after the line: . /etc/bash_completion is executed, perhaps a hardy bug?17:19
dholbachhighvoltage: no, not at all - there .png files, etc17:19
emil_sOk, ten it's fine :)17:19
dholbachJergar: great - that means it built :)17:19
=== binar__ is now known as binarity
Jergardholbach: yes great17:20
dholbachsubterrific: oh? I certainly don't have that bug on hardy17:20
Hit3k_how do we upgrade to the hardy alpha if we aren't already running it?17:20
dholbachmario: yes, in some cases it will be harder, depending on how the upstream build system works17:20
Jergarso I can download some ubuntu-packages  and try to fix some17:21
dholbachmario: some use the  ./configure && make && sudo make install  mechanism, others don't have a build system at all and just ship a bunch of files, some python code might use   ./setup.py   etc17:21
dholbachHit3k_: I'm not sure the        gksu "update-manager -c -d"    will work now already17:22
highvoltagedholbach: aaah, so a source package doesn't always necassarily automagically result in a binary package?17:22
dholbachyou can also look into using a chroot http://wiki.ubuntu.com/DebootstrapChroot17:22
dholbachor use ubuntu on a spare partition or in a VM17:22
mariodholbach: thank you17:22
dholbachhighvoltage: it depends on how you organise the debian/rules file (how the debian build process makes use of the upstream build process)17:23
dholbachin most cases it's quite straight-forward - and if you work on existing packages you mostly won't have to bother about it17:23
highvoltagedholbach: so it doesn't always?17:23
dholbachhighvoltage: sometimes it requires changes to the build system, but as I said: with the most upstream projects it works fine17:24
highvoltageah ok17:24
dholbachI personally recommend working on existing packages to get a feeling of what you're working with17:24
dholbachthe bitesize bugs are a good start17:24
dholbachthere are also bugs tagged packaging17:24
mariosorry, but what is a "upstream project"?17:24
dholbachmario: good question :-)17:24
mario;)17:25
subterrificdholbach: this is a clean install from the latest hardy alpha iso and upgraded as of last night. i'll look into it more and perhaps file a bug17:25
dholbachGNOME or Mozilla are upstream projects17:25
dholbachpeople who write source code and distribute source tarballs17:25
dholbachwe at the Ubuntu end grab those tarballs and integrate them into UBuntu17:25
dholbachsubterrific: excellent17:25
pak33m|workdholbach: dholbach: highvoltage: we fixed a bug in an existing source package and updated an existing source package to a new version <------- did we really fix a bug or did we just learn how to perform a manual build assuming that we had fixed a bug ? i don't know if i missed where we fixed a bug.17:26
dholbachpak33m|work: you're right... I broke the package myself for the purpose of this tutorial :)17:26
dholbachok... I'd like to invite all of you to Friday's MOTU Q&A session17:27
dholbachit will be at the same place and at 13:00 UTC17:27
pak33m|workdholbach: ah, that's right thank you17:27
highvoltagepak33m|work: well, renaming a debian/install file to make it build is like fixing a bit, we're going more through the dances of how to do it than fixing real-life bugs, that's generally how tutorials go :)17:27
dholbachhttp://wiki.ubuntu.com/MOTU has all the relevant dates on the top of the page17:27
Hit3k_Do you have to be an ubuntu member to become a motu?17:27
hellboy195dholbach: why always Friday 13.00 UTC? many are working or still at school at that time :(17:28
dholbachHit3k_: no... MOTU membership includes Ubuntu membership17:28
dholbachHit3k_: so you can go straight for MOTU17:28
dholbachhellboy195: it fits my schedule quite well - I'm trying to find people in other timezones to repeat it at a different time17:28
dholbachI'll announce it once I've succeeded finding somebody17:28
Jergardholbach: Thanks if my new Dell comes on friday i will come to the Q&A session17:28
doluudholbach: thanks17:28
dholbachI'd like to point you to  http://wiki.ubuntu.com/MOTU/GettingStarted  again17:29
dholbachthe last point it about blogging17:29
doluume too, see ya at Q&A session17:29
highvoltagedholbach: thanks, I learned things in this session, it feels great!17:29
dholbachif you want to get started as a MOTU, it'd be great if you blog about your experience and let others know how it goes17:29
Mika1860I missed the main part of the packaing session. however I' curious about it. is there a log or something?17:29
dholbachalso if you have ideas on how to make MOTU more fun let me know17:29
dholbachhttp://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt17:30
Mika1860thx17:30
hellboy195dholbach: ubuntu/gnome t-shirts,mugs for free ^^17:30
pak33m|workdholbach: thank you for the tutorial17:30
dholbachhellboy195: drop me an email :)17:30
vorianpfft gnome17:30
dholbachthanks everybody for showing up - I had a GREAT time17:30
Hit3k_thank you for the tutorial17:30
dholbachand hope to see you as MOTUs soon!17:30
vorianthanks dholbach17:30
hellboy195vorian: gnome! WTF17:30
h3bthanks17:30
mariothanks17:30
Jergarthanks17:31
badvistathanks17:31
highvoltagethanks17:31
Soltythanks17:31
dantalizingvery nice17:31
warp10thank you dholbach :)17:31
highvoltagewhohoo! nice ladder17:31
hellboy195thanks17:31
hellboy195cya guys17:32
* Hit3k_ goes to find bugs to fix17:32
mariocya17:32
h3bdholbach: just a question: i have tried to build hello-2.3 again and got an error:17:33
h3b/usr/bin/make -i distclean17:34
h3bmake[1]: *** Keine Regel, um »distclean« zu erstellen.  Schluss.17:34
h3bwhy no target to make distclean?17:35
subterrifich3b: did you edit the Makefile by mistake?17:39
subterrifich3b: make -i distclean works for me17:39
h3bno.17:39
da1l6doesn't work here either17:40
h3bhmm... i'll try again. need a second17:40
dholbachcan you put the log into pastebin.ubuntu.com?17:40
h3bdholbach: http://pastebin.ubuntu.com/3583/17:43
LucidFoxgah, too late17:44
h3b:(17:44
h3bhmm...17:45
subterrifich3b: you need to change debian/changelog to have the correct version number17:45
h3bdch -i17:45
h3b?17:45
h3bright?17:45
subterrificwell if you already ran that, but didn't put the right version number you can just manually edit your last entry17:46
LucidFoxh3b> there are more serious problems than just that17:46
LucidFoxyour changes contain binary files17:47
LucidFoxtry running debian/rules clean17:47
h3bsubterrific: thanks, forgot to change the version to 2.3 ;-)17:47
subterrificLucidFox: that was his only problem, it was just causing other problems17:48
h3bnow it works :-)17:48
LucidFoxAh, yes, I see17:48
LucidFoxhe was using the old orig.tar.gz17:48
subterrificcheck this out http://pastebin.ubuntu.com/3585/17:48
LucidFoxIn the future, when upgrading to a new upstream release, you can use "dch -v new.version-tag" instead of "dch -i"17:49
LucidFoxfor example, "dch -v 2.3-0ubuntu1"17:49
h3bah, ok.17:49
h3bthank you all.17:51
h3bso, i leave. bye.17:51
guatakaexit17:57
=== bigon is now known as bigon`
=== bigon` is now known as bigon
nathandbbDoes anyone have a link to the MOTU session that was here an hour ago??18:34
civijahttp://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt18:35
nathandbbThank you -- thinkpad crashed when I undocked it -- lost my log18:50
=== civija_ is now known as civija
kduboiswas there a become-a-motu meeting here today?19:33
zhaozhoukdubois, it was.19:35
ketzalhi19:45
=== bigon is now known as bigon`
=== bigon` is now known as bigon
SurgeWhere is it possible to find transcript from the training session earlier today?21:04
ToyKeeperhttp://irclogs.ubuntu.com/2008/01/15/%23ubuntu-classroom.txt21:05
SurgeToyKeeper: thanks a lot21:08
NetoX_damm, i think i am late for the class xD23:13
NetoX_さあ23:25

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!