[03:49] jono: Please test [03:50] thanks Flannel [03:50] works :) [03:50] great :) [03:50] why is it set like this at the moment? [03:50] either someone forgot or spam [03:50] gotcha [03:50] thanks! [03:50] I am just testing some Lernid fixes [03:51] haha [03:51] everything seems to be working pretty well [03:51] That one was a doozy. ;) [03:51] lol nha [03:51] nhaines, [03:51] it now has a more native IRC pane [03:51] app indicator support [03:51] and a bunch of fixes, ready for dev week [03:51] Ooh! Just in time. :) [03:51] oh great :) [03:51] just want to fix up some last bits and then release a package [03:52] :) [03:53] jono, you got rid of webchat? (native irc?) [03:53] nigel_nb, yep [03:53] awesome! looking forward to UDW [03:56] jono, did you fix the IRC backend to fragment the window viewer, so it does not use two nicks? [03:57] paultag, hm, I think so, I only see jonobacon and not lernid_jonobacon ;) [03:57] awesome :) [03:57] Then again I was not in -chat [03:57] Ah, there it is. Well done jono [03:58] just finalizing some fixes [03:58] and then will pump out a release [04:01] Can lernid point at a proxy for client multiplexing, or does it always connect here? [04:06] I don't understand how to get session information into Lernid. :) [04:06] Perhaps lernid can ship with bindings for Firefox. So we can send lernid:// URLs to new users [04:07] lernid://irc.freenode.net/#ubuntu-classroom [04:07] and tweet the hell out of it :) [04:13] anyone on Karmic here? [04:13] jono, yo [04:13] paultag, are you on Karmic? [04:13] jono, yes [04:13] paultag, could you check out Lernid and test it? [04:13] jono, sure thing, off your PPA? [04:14] bzr branch lp:lernid [04:14] and then: [04:14] quickly run [04:14] Sure [04:14] make sure you have it's dependenices [04:14] jono, sure thing. Let me give it a go [04:14] thanks paultag! [04:14] sure thing [04:21] paultag, any luck? [04:22] jono, working on getting EventManager in place [04:22] jono, is it in the repos? [04:22] paultag, EventManager in place? [04:22] no, like I say, I just want you to check out the code and run it [04:22] bzr branch lp:lernid [04:22] and then: [04:22] quickly run [04:23] jono, oh, I was doing setup. Gimme a sec to grab quickly [04:23] cool [04:24] I just want someone to test it on Karmic [04:24] I am running Lucid [04:24] Righto [04:25] jono: I can test it after the Ubuntu California meeting. [04:25] Jeez, quickly is huge [04:25] nhaines, can you test, would be awesome [04:25] nhaines, oh christ. I'm glad I'm not there ;) [04:25] jono, another minute or so [04:25] jono: I'd be happy to. :) [04:26] thanks paultag [04:26] cheers nha [04:26] cheers nhaines [04:29] jono, it's up. Let me hammer on her [04:30] paultag, cool, join Ubuntu Example Week [04:30] jono, I did, it bombed out. No IRC connection [04:30] Oh, there I am [04:33] jono, looking good so far [04:34] paultag, cool, check Lernid [04:34] jono, I have it up :) [04:40] Heh, longest. LoCo meeting. ever. [04:49] I'm really looking forward to seeing Bazaar Explorer. Sounds awesome. [04:53] QUESTION: Will I get an error in lernid with this? [04:54] already tried nhandler :) [04:54] night nhandler, nhandler_lernid :) [04:54] ANSWER: Nope. But it might be a good idea to add an anchor at the start of the UDW schedule so that lernid can display the timetable portion of the page (which is the most interesting part) [04:59] Looks like I'm missing gtkmozembed [04:59] nhaines: If you are running the bzr version, it won't pull in the dependencies. Install lernid from a ppa first, and then run it from bzr [05:00] Details! [05:01] Hehe, let me do that. [05:14] test... [05:14] Hm, seems to be working. [05:14] Maybe. :) [05:31] Quickly is so awesome. [07:17] test [07:59] hallo [08:08] Hello [08:21] - [08:23] Hi all === qwebirc51456 is now known as Hammerhard [08:23] I wanted to ask, the times of the classes are based on what timezone? [08:24] they are based on the UTC timezone [08:25] Hammerhard: So, there's going to be a Django class today? [08:25] yes [08:26] maybe this can help you, but it's in german [08:26] http://ikhaya.ubuntuusers.de/2010/01/24/ubuntu-developer-week-im-januar-2010/ [08:26] Hammerhard: thank you very much. I will do my best to attend as many of the classes as possible. === deegee_1 is now known as deegee [08:47] Omar8714: this might help: https://wiki.ubuntu.com/Lernid === ulysses__ is now known as Guest84713 === amik is now known as amichair [09:44] For some reason, when I open lernid, I automatically get connected to a an Ubuntu chatroom in Spannish. [09:44] How do I fix that? [09:44] jono: ^--. [09:47] ahh.. no that was nothing. Sorry. :) === tobias is now known as Guest7679 [09:48] Omar87, np :) === tobias is now known as Guest85872 [09:53] !ping [09:53] Here I am, brain the size of a planet and you expect me to respond to a ping? How depressing. [09:53] Here I am, brain the size of a planet and you expect me to respond to a ping? How depressing. [10:08] and this is the classroom where the instructor will speak [10:23] Has the classroom event been canceled? [10:23] No. It hasn't started yet. [10:23] Check the wiki, but I think it starts around 15:00 UTC. [10:23] Right now, it's about half past ten. [10:24] persia: thank you for clearing that up...I had no idea why I thought it was at 10 UTC [10:24] *have no idea why [10:27] first is at 16:00 utc [10:27] @now [10:27] Current time in Etc/UTC: January 25 2010, 10:27:15 [10:28] I seem to know why now..somehow when I imported the iCal available at the wiki into thunderbird everything starts at "10 a.m."..not sure why that happened [10:31] I must be losing it..that is exactly when the classes start in my timezone..10 a.m. CST [10:32] Then you better sleep fast :) [10:32] heading that way now :) [10:32] or get some coffee ;) [10:34] nah, think I'll opt for sleep..won't retain much after being awake 24+ hours :D [10:34] :D [11:10] hi all [11:12] есь кто живой? [11:53] http://ubuntu.com === Yos is now known as Yos_ === Yos_ is now known as Yos === openweek3 is now known as dave === dave is now known as emdave === zen is now known as Guest58025 [12:58] Hi all. [13:21] good afternoon everyone, todays sessions will begin at 16:00 UTC [13:21] @now [13:21] Current time in Etc/UTC: January 25 2010, 13:21:06 [13:55] @now [13:55] Current time in Etc/UTC: January 25 2010, 13:55:46 [14:54] ls [14:55] @now [14:55] Current time in Etc/UTC: January 25 2010, 14:55:22 [14:57] übrigens ist tiledqt in meinem PPA nun nutzbar === dholbach_ is now known as dholbach === Mcb is now known as Guest86349 [15:13] date -u [15:14] thetofucube, in your terminal [15:14] @now [15:14] Current time in Etc/UTC: January 25 2010, 15:14:36 [15:16] opps wrong window [15:16] @now [15:16] Current time in Etc/UTC: January 25 2010, 15:16:17 [15:16] thanks === nigelbabu is now known as Guest32940 [15:49] Hi all! [15:49] * thebwt waves at xteejx [15:50] hey [15:50] I think chatter is supposed to go to #ubuntu-classroom-chat [15:50] testing... [15:52] thebwt: yes.. it is :-) [15:55] Hi thebtw :) [15:56] [SLIDE 1] [16:00] HELLO EVERYBODY! WELCOME TO UBUNTU DEVELOPER WEEK! [16:00] I'm very very happy you all made it here [16:00] First I'll talk about a few organisational things before we dive into session 1 "Getting Started with Ubuntu Development"! [16:01] first of all: for those of you who are not using lernid to connect to Ubuntu developer week: [16:01] - #ubuntu-classroom is for the presentation only, so please keep chatter out of the channel === Mcb is now known as Guest69733 [16:02] - #ubuntu-classroom-chat for discussion and for questions (please prefix with QUESTION:, ie: "QUESTION: What does xyz mean?") [16:03] - I put up some slides at http://people.canonical.com/~dholbach/ubuntu-development-getting-started.pdf which should at least give you a nice link collection - lernid users will see those slides as we move on through the session [16:03] if you have general questions about the schedule, you can find it at https://wiki.ubuntu.com/UbuntuDeveloperWeek [16:03] [SLIDE 1] [16:04] dholbach: nothing here. [16:04] another organisational note: [16:04] if you plan to be here the full week and speak more languages than just English, consider adding yourself to the bottom of https://wiki.ubuntu.com/UbuntuDeveloperWeek [16:05] rmunn_: lernid only clients can't get to #lernid [16:05] howdy [16:06] so for example: [16:06] Catalan: #ubuntu-cat [16:06] Danish: #ubuntu-nordic-dev [16:06] Finnish: #ubuntu-fi-devel [16:06] German: #ubuntu-classroom-chat-de [16:06] Spanish: #ubuntu-classroom-chat-es [16:06] French: #u-classroom [16:07] it'd be great if you would help out translating questions and answers for those who are not comfortable speaking in English yet :) [16:07] (thanks in advance) [16:07] [SLIDE 1] [16:07] when it will start? [16:08] thanks a lot jussi01 [16:08] ok... let's get started :) [16:09] so what we're going to cover during the session is the following: [16:09] - get a basic development environment set up (gpg key, tell the packaging tools who we are, get pbuilder set up, etc.) [16:09] - cover the basics of contributing [16:09] - and hopefully answer lots of questions :) [16:10] [SLIDE 2] [16:10] so first of all, please run: [16:10] sudo apt-get install --no-install-recommends ubuntu-dev-tools build-essential pbuilder dpkg-dev gnupg [16:10] this will install a bunch of packages we are going to need [16:11] build-essential will pull in compilers and general tools for building packages [16:11] gnupg we will need to sign packages (or encrypt data generally) [16:12] ubuntu-dev-tools itself contains a lot of useful tools and will pull in a few others we are going to need to packaging and every-day tasks [16:12] also please enable "Source code" in System -> Software Sources -> Ubuntu Software === zen is now known as Guest4939 [16:13] a question that is asked a lot of times is: "Do I really need to run the current development release? Won't that break my system?" [16:13] The answer is "yes, for building and testing you need one form 'latest development release'" [16:13] to do that in a sane way, you better check out https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases [16:14] Also we do have these very fine sessions lined up for this week which talk about a similar topic: [16:14] TODAY, 19.00 UTC - Working on the Bleeding Edge -- kees [16:14] Wed 27th Jan, 19.00 UTC, Developing and Testing in KVM --kirkland [16:15] QUESTION: Do any of the classes cover how to use debhelper and CDBS? [16:15] xteejx71: there is no explicit "debhelper and cdbs" session, but I'm sure that some sessions will cover it briefly [16:15] in any case I can recommend https://wiki.ubuntu.com/PackagingGuide [16:15] [SLIDE 3] [16:16] ok, let's start with setting up a gpg key [16:17] gnupg stands for GNU privacy guard and can be used to sign and encrypt data in general (you'll see it in use very often with emails, but also general files) [16:17] we use it to prove that one person (and nobody else) made a particular change to a file [16:18] < LumpyCustard> Question: What is the command to show the current gpg keys on the system? [16:19] thanks cjohnston [16:19] LumpyCustard: gpg --list-keys should do that [16:19] < xteejx71> QUESTION: Do the gpg keys *have* to be registered with Launchpad? [16:19] so if you already have a key set up, you can skip this step obviously [16:20] xteejx71: it's necessary to use a PPA (Personal Package Archive) or to upload a package to Ubuntu (once you are part of any of the uploader teams) [16:20] ok... so to generate a key you run the following [16:21] gpg --gen-key [16:21] it's generally safe to just stick to the defaults [16:21] if you want to have more information on setting gpg up, check out https://help.ubuntu.com/community/GnuPrivacyGuardHowto [16:22] now you tell gpg your name and your email address [16:22] a comment is not necessary [16:22] now it will create the key and that's likely going to take a bit longer [16:23] (it will take random numbers from whatever your machine is doing right now to put that key together) [16:23] < Navaneeth> QUESTION: How can I upload a package to ubuntu repository? Where is that information documented? [16:23] Navaneeth: we'll get to that later on [16:23] < bullgard> QUESTION I obtain: "public key not found." What should I do? [16:24] bullgard: it likely means that you have no key set up yet? [16:24] bullgard: I don't know what you just did, so can somebody please try to debug the problem with bullgard in #ubuntu-classroom-chat? [16:24] cjohnston: next? [16:24] < bullgard> QUESTION I obtain: "public key not found." What should I do? [16:24] cjohnston: next? [16:25] < Paddy_NI> QUESTION: What is the comment generally used for? [16:25] sorry [16:25] Paddy_NI: gpg is used to create the key with which we sign data, files and emails or encrypt and decrypt them - you actually don't use the command itself very often, but there's other tools which rely on it [16:26] alright, so let's move on to the next topic :) [16:26] pbuilde [16:26] pbuilder [16:26] [SLIDE 4] [16:26] pbuilder is a great tool to test-build packages in a clean and minimal environment [16:27] < fubarrrr44> QUESTION: Why do I need root permissions to (just) build a .deb package? (wi th rpm this is not needed) [16:27] whenever you start a build it will set up a minimal environment, install the build-dependencies, start the build itself and remove the build-dependencies afterwards again (it will cache them though) [16:27] fubarrrr44: pbuilder uses chroot internally [16:28] fubarrrr44: if you use just "debuild" (and install the build-dependencies on your "live system"), you don't need root permissions either [16:28] the maint points of pbuilder are: [16:28] - keep your live system clean (you don't need to install 427697426246 build dependencies) [16:29] - make sure the package builds in a minimal, unmodified environment [16:29] there are other tools that do similar jobs, and there's pbuilder-dist (in the ubuntu-dev-tools package), which is great [16:29] there's more info on https://wiki.ubuntu.com/PbuilderHowto [16:30] please edit ~/.pbuilderrc in your favourite editor [16:30] and add this to it: [16:30] COMPONENTS="main universe multiverse restricted" [16:30] then save the file [16:30] then run [16:30] sudo pbuilder create [16:30] this, too, will take a while [16:30] as it will create a minimal system "from scratch" [16:31] ok, let's crack on [16:31] [SLIDE 5] [16:31] now we'll tell the development tools who we are [16:31] please edit ~/.bashrc with your favourite editor [16:32] and add something like this to the end of it: [16:32] export DEBFULLNAME='Daniel Holbach' [16:32] export DEBEMAIL='daniel.holbach@ubuntu.com' [16:32] afterwards please save the file [16:32] and run [16:32] source ~/.bashrc [16:32] (or restart your terminal) [16:32] by setting DEBFULLNAME and DEBEMAIL: [16:33] - you don't have to type in your email address [16:33] - and name [16:33] < xteejx71> QUESTION: I never done the COMPONENTS bit before...does this make a difference when using pbuilder? [16:33] - and gpg key id all the time [16:33] and ... PLEASE ... use your own name and email address! [16:33] :-) [16:33] xteejx71: if you want to use universe and multiverse to build packages, then yes, you need it [16:34] are there any more questions? please keep them coming in #ubuntu-classroom-chat [16:34] if not, I'll keep on talking about a few things while pbuilder and gpg are doing their thing [16:34] < ulysses> QUESTIN: Can I use characters in DEBFULLNAME like 'ó' and 'á'? [16:35] ulysses: yes, I'd be surprised if that wouldn't work :) [16:35] < xteejx71> QUESTION: Can pbuilder be used to create anything other the the Lucid environment? [16:36] xteejx71: yes, have a look at https://wiki.ubuntu.com/PbuilderHowto - there's some variable you need to set, or use pbuilder-dist which can easily cope with multiple parallel pbuilders [16:36] alright... let's talk about the release schedule for a bit [16:36] < xteejx71> QUESTION: If I already have run 'sudo pbuilder create' will this overwrite the old one or create a new one? [16:36] xteejx71: I think I creates a new one [16:36] xteejx71: might be best to check the manpage [16:37] [SLIDE 6] [16:37] https://wiki.ubuntu.com/LucidReleaseSchedule [16:37] that's the current release schedule we have for this cycle [16:37] you can see that we're in the "yellow phase" right now [16:37] in every cycle we roughly do the following: [16:38] - set up the toolchain (the core build tools) [16:38] - discuss features at the Ubuntu Developer Summit [16:38] - merge changes from Upstream and Debian [16:38] - work on features [16:38] - debug problems [16:38] - polish [16:38] - release [16:39] it was just pointed out that we're in the orange phase... yeah, that's right :) === dragon is now known as Guest85410 [16:39] < kjele> Question: When I build with pbuilder it pulls down the required dependencies to compile the program. Is it possible to make sure it does not download each time I try to build? [16:39] as you can easily see, the later it gets in the release cycle, the more conservative we get about changes [16:39] towards the end we focus more on testing and obvious good bugfixes than on "crack of the day" [16:40] kjele: it does cache those build-depends by default [16:40] so if you ask the question "How can I help out?" or "What can I do?" it heavily depends on where we stand in the release cycle [16:40] < Navaneeth> QUESTION: I heard ubuntu is not contributing to upstream. is that correct? If yes, why? [16:41] Navaneeth: that's not correct [16:41] Navaneeth: if you have a look at https://wiki.ubuntu.com/Upstream you can see that we put a lot of energy in collaborating effectively with upstreams [16:41] maybe I should clarify what "upstreams" are and how everything fits in one picture [16:42] if you imagine millions of Ubuntu users on the one side [16:42] and thousands of software projects like the kernel, like X, like GNOME, KDE, like Mozilla, like the authors of the crack-attack game and lots of others [16:42] on the other side [16:43] then Ubuntu (and other distributions) stand in the middle and try to make the conversation happen between the two of them [16:43] those "software authors" on the other side are our upstreams [16:44] here's a list of things we contribute to upstream projects: [16:44] - exposure of their software (distributions are the best way to get great software without hassle) [16:45] - well-researched bug reports: we get LOADS and LOADS of bug reports every day and we put a lot of work into making them top-notch reports by automatically getting debug stacktraces, etc etc - basically we filter "defect reports" for upstream project [16:45] s [16:45] - we test their software in lots of different scenarios [16:45] - and we forward patches [16:46] sure there's not a group of Ubuntu developers for every piece of software that exists [16:46] but we put a lot of hard work into working with Upstream projects [16:46] < fubarrrr44> QUESTION: How do I prevent pbuilder from doing clean up after work (to look at the generated chroot environment)? [16:46] check out "Adopt-an-Upstream" by jcastro and dholbach on Thursday [16:47] fubarrrr44: you can use sudo pbuilder login or just chroot for testing [16:47] https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases might be helpful oto [16:47] too [16:47] < LumpyCustard> Qn: How do I register the gpg key I've just made with Launchpad? [16:47] LumpyCustard: great question! [16:48] so first of all to find out your gpg key id, do the following: run [16:48] gpg --fingerprint your.name@email.com [16:48] for me it displays the following: [16:48] pub 1024D/059DD5EB 2007-09-29 [16:48] Schl.-Fingerabdruck = 3E5C 0B3C 8987 79B9 A504 D7A5 463A E59D 059D D5EB [16:48] uid Daniel Holbach ....... [16:48] 059DD5EB is my "KEY ID" [16:48] now to send you public key (your private key will always stay safe) to the keyservers so others can verify your signatures: [16:49] gpg --send-keys KEYID [16:49] and to register your key with Launchpad, head to https://launchpad.net/people/+me/+editpgpkeys [16:50] Ok... if your pbuilder is set up, you might want to try the following: [16:50] apt-get source hello [16:50] sudo pbuilder build hello_*.dsc [16:51] if you follow the output from pbuilder closely you will see how it first sets up the initial minimal environment, then download additional build dependencies, then build the package, then remove the build environment again [16:51] depending on your net connection and the speed of your CPU and disk it might take a little bit [16:52] < IdleOne> QIESTION sorry if you covered this already but what if I already have a key uploaded to launchpad, how do I use it? [16:52] IdleOne: just head to https://launchpad.net/people/+me/+editpgpkeys and use your existing key [16:52] https://help.launchpad.net/YourAccount/ImportingYourPGPKey will help too [16:53] something I forgot to mention when we were talking about the relase cycle [16:53] really really important fixes we need after a release is "out there" are SRUs [16:53] SRU is short for Stable Release Updates [16:54] basically it's for REALLY IMPORTANT stuff, and the packages that you get through xyz-updates [16:54] the procedure and criteria for SRUs are listed here: https://wiki.ubuntu.com/StableReleaseUpdates [16:54] < n3rd> Question : Is there a way to make a single deb out of multiple binaries, say for example i call it server.deb it must install few binaries ask per my tweaks like apache, tomcat, activemq so on [16:55] also there's a small cheat-sheet regarding the release cycle over here: http://people.canonical.com/~dholbach/cheatsheet.pdf [16:55] [SLIDE 7] [16:55] n3rd: yes, you would create an empty binary package that has the following line in debian/control: "Depends: apache, tomcat, activemq" [16:55] we'll talk a bit more about that in the next session [16:56] there's two final things I'd like to mention in this session (before we start the next one): [16:56] - head to #ubuntu-motu on irc.freenode.net if you have any problems - there's great people who are able to help and who will become friends after a while :-) [16:56] - bookmark https://wiki.ubuntu.com/MOTU/GettingStarted - it links to everything that's important [16:57] let's all take a few minutes break before move on to "Fixing small bugs in Ubuntu" :-) [17:02] Alrighty... welcome back to Ubuntu Developer Week - this time it's "Fixing small bugs in Ubuntu" :-) [17:02] I picked a few small bugs and I hope a few things will be clearer: [17:03] - how to use basic tools in every day situations later on [17:03] - learn the process of fixing something, how to propose the fix to get accepted, etc. [17:03] so we're not going to cover kernel hacks, crazy C++ stuff or anything else in here :-) [17:04] ok... the first bug I want us to have a look at is: https://bugs.launchpad.net/ubuntu/+source/fsniper/+bug/486612 [17:05] if you check it out, you'll see that indeed it is a small bug, it's about a typo in the package description of fsniper [17:05] to confirm it, just run [17:05] apt-cache show fsniper [17:05] and it says this towards the end: [17:05] This packages comes with no generic rules, so you must write [17:05] them yourself. [17:05] so... we're going to fix it! [17:06] first of all, let's get the package source: [17:06] apt-get source fsniper [17:06] if you run ls you will see that it downloaded a .orig.tar.gz, a .diff.gz and a .dsc file [17:06] and that it created a directory called fsniper-1.3.1 [17:07] ok, here's how it all fits together: [17:07] < vishalrao_dsktop> QUESTION: where does apt-get source store source files? [17:07] - orig.tar.gz is the file that the upstream authors released on their website as the source code [17:07] - .diff.gz is the compressed set of changes we make to make the package build the "debian or ubuntu way" [17:08] - .dsc is just meta-data like md5sums etc [17:08] apt-get downloaded the source from the archive, checked the md5sum, untarred the .orig.tar.gz file and applied the .diff.gz changes [17:09] ok... let's fix this bug now :) [17:09] cd fsniper-1.3.1/ [17:09] cat debian/control [17:09] debian/control was added (among other things) by the Debian/Ubuntu maintainers of the package [17:10] and it describes the source and the resulting binary package (in this simple case just one binary package) [17:10] < michae> QUESTION : no fsniper dir . Normal? [17:10] the description at the bottom is what we need to fix [17:10] this call ought to fix it for us: [17:10] sed -i 's/packages/package/g' debian/control [17:11] michae: I'm sorry, I don't understand your question... can somebody help michae debug the problem in #ubuntu-classroom-chat please? [17:11] < thebwt-lernid> QUESTION: couldn't we just open our favorite editor and fix it as well? Why use sed? [17:12] thebwt-lernid: yes, that'd work too and we'll make more use of the editor in due course :) [17:12] ok... some folks said they ran into trouble because dpkg-dev was not installed - please make sure you have it [17:13]