a tag? [20:38] <benonsoftware> ryan__: Yes, inside <html> is a <head> which desribs the page and the tag <title> its in there [20:38] <benonsoftware> So for example: [20:38] <benonsoftware> <!DOCTYPE html> [20:38] <benonsoftware> <html> [20:38] <benonsoftware> <head> [20:38] <benonsoftware> <title>Google

=== jordan_ is now known as jordan [00:31] hello there... [00:31] my first time boot here.. === kevjava_ is now known as kevjava [00:47] ysnoi, welcome - o/ [00:47] !logs [00:47] Logs for all classroom sessions that take place in #ubuntu-classroom can be found on http://irclogs.ubuntu.com/ [01:13] hi codepal...I've been disconnected after I use lernid and XChat at the same time... [01:13] ysnoi, aha - you've learnt something then! [01:13] don't use both at the same time! [01:13] :D [01:14] im just curious...1st time here [01:14] ysnoi, if you want to read what happened in this class this morning you can visit [01:14] !logs [01:14] Logs for all classroom sessions that take place in #ubuntu-classroom can be found on http://irclogs.ubuntu.com/ [01:15] ok thanks...i'll get to it [01:18] ah..so it's in html and txt file format...got it [01:19] codepal: you have two colors on username...may I know why? [01:25] ysnoi, maybe because when I speak your nickname it changes. [01:25] let's try... [01:25] yeah.. [01:25] +1 [01:26] can i ask anything here? [01:26] like how can I change my username? [01:26] on this chat [01:26] - /nick someother [01:27] irc uses '/' to give access to commands [01:27] i don't get it [01:27] - /ysnoi TheYsNoi [01:27] when u use it correctly with the '/' as the first thing on a line [01:27] take off the '-' [01:27] and space [01:28] - ysnoi TheYsNoi [01:28] /nick TheYsNoi [01:28] ^^ just that [01:28] haha... [01:29] and sessions aren't starting again here for several hours, 15:00 UTC (it's 1:30 UTC now) [01:30] - /ysnoi TheYsNoi [01:30] pleia2, how'd you do that? [01:30] escaping '/' [01:31] codepal: using irssi: / /command [01:31] "/ " escapes commands [01:31] ah, thanks! === ysnoi is now known as TheYsNoi [01:31] yes... [01:31] I got it... [01:32] thanks pleia2 and codepal [01:32] obviously different for different IRC clients... [01:32] TheYsNoi, in any case, we're glad your getting familiar with IRC [01:33] thanks a lot codepal [01:34] TheYsNoi, do you want a IRC lessson? [01:34] i'm using XChat...I was starting to connect to this channel last night but I got connected to mint instead... [01:35] until I saw freenode and ubuntu-classroom [01:36] IRC lesson? [01:36] in some you use /say instead [01:38] TheYsNoi, -- http://en.wikipedia.org/wiki/Wikipedia:IRC/Tutorial -- Take a read, hopefully you'll be able to work out some things for yourself [01:38] using /msg Chanserv help && /msg Nickserv help [01:39] opening now in browser...i'll take a look on it... [01:39] TheYsNoi, there are many channels on freenode on different topics, just 'remember the rules' [01:39] thanks codepal [01:39] see also http://freenode.net/ - especially for the quirks of this network [01:40] yeah, freenode.net needs a web redesign - I hate it [01:40] http://linuxlibrary.org/command-line/irc-internet-relay-chat/ for a quick, basic run down of commands [01:44] ah...so pidgin has also an IRC support [01:44] Yep [01:46] ok..i'll try adding an account.. [02:18] hey codepal.. [02:19] yeah? [02:20] I tried registering my nickname on NickServ as TheYsNoi but the username that arrived on my mail is TheYsNoi1? is this normal? [02:20] I hate having 1 on my nick.. [02:21] well maybe you can ignore the registration email ( you don't have to confirm ) [02:22] think hard about your nickname - it defines your first impression with many people. [02:22] and try again - you still can retry signing up with TheYsNoi, [02:22] if you want [02:22] maybe because when I register my nick on Pidgin, i'm also here as TheYsNoi.. [02:23] that would be it [02:23] possibly [02:23] you can register in XChat instead [02:23] if so, I need to logout here and try again... [02:23] or do that, yeah! [02:24] or, i will logout on pidgin and register here [02:25] is this server irc.ubuntu.com? [02:26] it doesn't really matter which server does it? [02:27] ah ok..i'll try now.. [02:27] whenever you log in you can get a different server that's still connected to this network [02:27] lot's of servers make up the freenode network [02:29] NickServ REGISTER [02:29] is that correct syntax codepal? [02:30] yup [02:30] remember, you can find help on most commands using /msg nickserv help command [02:31] or /msg chanserv help command [02:31] yeah... [02:32] i learned that today from you... [02:33] you might like a cloak which hides your ip address -- so people don't try hacking you -- in the channel #freenode [02:33] just ask nicely for a cloak [02:33] also you probably want to learn how to connect via SSL (more securely) [02:33] how? [02:33] which can get complicated.... [02:34] ask in #freenode for help or your IRC clients channel [02:34] ie #xchat / #pidgin [02:34] and don't forget you can use www.google.com [02:35] yeah...may I get to it one day.. [02:35] i'm on familiarization now.. [02:35] it's my rest day today..hehhe [02:42] yes..i'm done on registration.. === TheYsNoi is now known as ysNoi [02:44] test === ysNoi is now known as TheYsNoi [02:44] test 2 === kanliot is now known as kanliot111111111 [03:15] hello === ysnoi is now known as TheYsNoi [03:52] hmnnn... [03:54] anybody? [03:56] Hello [04:00] hi benon [04:18] join #ubuntu-release [05:43] [05:44] [05:44] [05:44] [05:44] === mintos is now known as mintos_out === user__ is now known as rockys === Partyschaum is now known as Partyschaum^away === Partyschaum^away is now known as Partyschaum === muthusuba_ is now known as muthusuba === greyback is now known as greyback|lunch === Adriaan is now known as Guest3208 === allan_ is now known as Rehhoff [12:59] anybody? [12:59] what is the link to the timetable again? === ysnoi is now known as TheYsNoi [13:01] nevermind === yofel_ is now known as yofel === greyback|lunch is now known as greyback === dduffey_afk is now known as dduffey === ublinx is now known as jmarc [14:53] Everyone ready for the UDW Day 2? [14:55] metasansana: is that you ? [14:57] dpm, sure :) [14:58] Alright my friends! WELCOME TO DAY 2! [14:58] Again a few organisational bits before dpm takes over the stage... [14:59] Please make sure you all join #ubuntu-classroom-chat because that's where all the chat and questions go [14:59] also please make sure you prefix all your questions with QUESTION, ie [14:59] QUESTION: dpm, how much do you like metal music? [14:59] you can find the schedule at https://wiki.ubuntu.com/UbuntuDeveloperWeek along with all the logs of the sessions yesterday if you missed them [15:00] I hope you have a fantastic time today [15:00] big hugs from me === metasansana_ is now known as metasansana [15:00] (do I really have to answer that question...?) [15:00] and I pass on the mic to David "dpm" Planella who talks about "Bringing your app to Ubuntu " [15:00] * dholbach hugs dpm [15:00] the stage is yours [15:00] :) [15:00] * dpm hugs dholbach while catching the mike [15:01] Logs for this session will be available at http://irclogs.ubuntu.com/2012/02/01/%23ubuntu-classroom.html following the conclusion of the session. === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: Bringing your app to Ubuntu - Instructors: dpm [15:01] Allright, how's everyone doing? [15:01] I am doing well. [15:01] good :) [15:01] awake [15:02] cool [15:02] ok, awesome [15:03] let's wait a minute for stragglers to come in and then we can start [15:04] I hope you all are enjoying UDW so far... [15:04] dholbach tells me yesterday was awesome! [15:04] Anyway, let's get started [15:05] Hi everyone and welcome to the first session of Ubuntu Developer Week Day 2! [15:05] During the next hour I'll be talking about how to submit your apps to Ubuntu, [15:06] so that they get published in the Software Centre [15:06] to be distributed to millions of users that will surely enjoy your cool software :) [15:06] But it will not be just a talk: I'll make sure that there is plenty of time for everyone [15:07] to participate and ask their questions at the end. However, feel free to interrupt me during the [15:07] rest of the session if you've got any questions. [15:07] Just remember to prepend them with QUESTION: on the #ubuntu-classroom-chat channel [15:07] Throughout the talk I will be referring to different places in the Ubuntu App Developer site, [15:07] which is the central place for anyone wanting to create and publish their apps in Ubuntu. [15:08] Here's where it lives: [15:08] http://developer.ubuntu.com [15:08] ... and without further ado ... [15:08] let's get rolling! [15:08] [15:09] Creating your app [15:09] ================= [15:09] [15:09] Well, the first step is obvious, you have to create your app, [15:09] which is basically the time when you materialise that cool idea into beautiful software. [15:09] I will not dwell too much on this subject, as it's beyond the scope of the session, [15:10] However, I'll just add a couple of tips for app authors. [15:10] If you're considering writing a new application for Ubuntu, I'd recommend to use [15:10] the standard set of tools available from the Ubuntu archive. [15:10] They are an extremely powerful and versatile bunch of tools [15:11] which will not only put everything you need to write software at your fingertips, [15:11] but also will help you following good development practices. [15:11] And they're all Free Software and also free as in free beer! [15:12] I see we've got a question already, but let me show you something first: [15:12] You've got an overview of our recommendations to write new apps here: [15:12] http://developer.ubuntu.com/get-started/quickly-workflow/ === jincreator1 is now known as jincreator [15:12] ryan___ asked: Which programming language do you perfer to use to develop Ubuntu apps? [15:13] as you can see from the table in the link above, we're currently recommending Python [15:13] as a language to write new apps [15:13] What we've also got is a tool called quickly, which puts all those technologies together [15:14] You can learn more about it here, it's got a nice and short video tutorial [15:14] to show you how to write a basic functional template for your app in 3 minutes: [15:14] http://developer.ubuntu.com/get-started/ [15:14] However, if you've already written an application with another set of tools, [15:15] or if you do prefer another choice of toolkit, that's also ok! [15:15] We're providing these recommendations to make it easy for app authors to get started [15:15] and provide a smooth path for publishing their apps. [15:15] However, we acknowledge the diversity of the whole Open Source ecosystem, [15:16] so you can basically submit your apps using your weapon of choice. [15:16] Just remember that our recommendations will make things easier, though! [15:16] metasansana asked: why phython? [15:18] we chose quickly because it's an easy to learn high level language, which is open source and it's got first class support in Ubuntu. [15:18] apart from that, it comes with a rich library of functions to do virtually anything you want [15:19] Continuing on this subject, [15:19] also, commercial apps (more on those in a minute) might be written in a completely different set of tools, and we want to be inclusive to them too. [15:20] ryan___ asked: does Quickly support the Microsoft Visual Basic programming language? [15:21] quickly just puts together a set of tools, it's not an IDE that supports languages, although conceivably could be extended to support other languages [15:22] however, to answer the question, quickly intendedly only supports python, no Visual Basic [15:22] ok, moving along [15:22] [15:22] Which types of apps qualify [15:22] =========================== [15:22] [15:22] There are thousands of apps available in the Ubuntu archive already, which usually get in there through other means. [15:22] Many of these fall into the category of system software, or big applications that are part of the Ubuntu platform. [15:23] They are also subject to strict policies to ensure the security and quality of the software, [15:23] as well as to ensure that they are indeed Free Software and can be distributed with Ubuntu. [15:23] So in order to differentiate from these archive applications, I'll call the process we'll be talking about today, "the app developer process". [15:24] Ultimately though, they are all published through the Software Centre [15:25] So to answer the first question, these are the 3 broad categories under which apps to be submitted through the app developer process fall: [15:25] * Paid for apps [15:25] * Gratis apps with proprietary licenses [15:25] * Gratis apps with Open Source licenses [15:25] Notice that as well as open source, we're also embracing commercial applications [15:25] to give the opportunity to app authors and Canonical to make revenue of application sales. [15:26] This should give you a rough idea, but ultimately you will need to know the whole [15:26] details to see if your app qualifies for the app developer process. [15:26] [15:26] - For paid for and gratis+proprietary apps: [15:26] http://developer.ubuntu.com/publish/commercial-software-faqs/ [15:26] - For gratis+open source apps: [15:27] https://wiki.ubuntu.com/AppReviewBoard/Review/Guidelines [15:27] Ok, next is where it gets interesting: how to actually submit your app! [15:27] [15:27] 1. Submitting your app [15:27] ====================== [15:27] [15:27] Ok, so all that cleared up, by this point you've already have a working app you'd [15:27] like the world to see and enjoy. [15:28] The good news is that we've got an easy, streamlined and web-based process [15:28] to make it easy for you to to publish, keep track of, monitor and update your apps. [15:28] For this, we've developed a tool especially for app developers. [15:28] It's called My Apps and you'll find it on the app developer site: [15:28] https://myapps.developer.ubuntu.com [15:29] You'll see that it's easy and intuitive to use, and the first thing you'll want to do is to sign up for it [15:29] to enter the Ubuntu app developer programme and start using it straight away :-) [15:29] Signing up it's free, and again, it's a matter of a couple of minutes. [15:29] The process is based on Ubuntu's single login, [15:30] so if you've got an Ubuntu SSO account already, it will be even quicker. [15:30] Simply go to https://myapps.developer.ubuntu.com, either click on the "Sign in or register" link at the top right hand side [15:30] or the "Submit a new application" button, and the website will guide you through the process. [15:30] Before you continue the process of submitting the app though, you might want to read the quickstart guide on: [15:31] http://developer.ubuntu.com/publish/ [15:31] It will show you the basic steps you will be following and give you some useful tips along the way. [15:31] Let's go quickly through them: [15:31] 1 - Set up your My Apps account - you've already done that :) [15:31] 2 - Prepare your app's icons and screenshots - you will want your app to be [15:31] appealing to users, so make sure you've got nice screenshots and icons, in all recommended sizes [15:32] 3 - Add your application details - here you'll be describing your app and making it easily [15:32] discoverable in the Software Centre. Make sure the description is clear and use a spell-checker to avoid typos [15:32] 4 - Choose your price - if your app is paid for, you'll have to decide the price in USD at this point [15:32] The minimum price is $2.99 [15:32] 5 - Have an archive of your application ready to upload - here's where you upload your actual app to MyApps. More on this in a minute [15:32] 6 - Your app will be reviewed - before it gets into the wild, your app needs to be reviewed and QAd. More on this in a minute too. [15:33] So going back on the step of uploading your app, [15:33] Ideally, you should submit a Debian source package. A Debian source package consists of 3 files (with extensions .dsc, diff.gz, orig.tar.gz), which you should put in a compressed archive (a tarball, zip file, rar...) and upload into My Apps. This will allow reviewers to easily test and publish your app. [15:33] *However*, there are some important caveats: [15:34] * If your app is commercial or proprietary software: we still recommend uploading a Debian source package, but if you are not experienced in packaging you can also upload either your binary executables and all files needed to run your app in a compressed archive, a binary Debian package (.deb), your source code in a compressed archive, and the commercial packagers will package and publish it for you. [15:34] Very soon we'll have automatic packaging in place, but more details on that when it's all deployed and working [15:35] * If your app is Free Software and gratis: we recommend using a Personal Packaging Archive (PPA). You can specify the location of your PPA in the 'Any additional notes for the application reviewer' text box in the Overview tab of your app's entry in My Apps. You can also learn more about PPAs in the packaging section of the Ubuntu App Developer Site [15:35] developer.ubuntu.com/packaging [15:36] We've got a few questions coming in, and they're related to reviewing [15:36] Let me talk a bit about review and then answer them [15:36] [15:37] 2. Reviewing your app [15:37] ===================== [15:37] [15:37] After your application has been submitted, and depending of the type of app, one of two things will happen: [15:38] * If it's a paid for or a gratis+proprietary app, it will be reviewed by the Canonical reviewers team. If necessary, they will package it for you and QA it. Very soon, though, we'll be able to automatically package those. [15:38] * If it's a Free Software+gratis app, it will generally be reviewed by a team of volunteers called the Ubuntu App Review Board (ARB) [15:39] In any case, reviewers will get in touch with you as soon as they start reviewing [15:39] your app, and you will be notified of any app state changes by e-mail. [15:39] For all the exact details of an application's lifecycle in My Apps, check out: [15:39] http://developer.ubuntu.com/publish/application-states/ [15:39] Now onto the questions: [15:40] cielak asked: I have been interested in the review process for some time, and I would like to somehow help the ARB team. Is there any way I could participate and help them? [15:40] they'd be delighted to hear that! [15:40] you can jump into the #ubuntu-arb channel and ask how to help, or you can contact the ARB through e-mail [15:41] https://wiki.ubuntu.com/AppReviewBoard [15:41] you'll find all the details there [15:41] ryan___ asked: how long does it take after you submit an application to Ubuntu before it shows up in the Ubuntu Software Centre? [15:43] it depends on your application, and if it's easy to review and QA, or if it's a commercial app, if it needs to be packaged and it's easy to do [15:44] it can take from some hours to some days, but it varies on an app by app basis [15:44] You'll find some more details there: http://askubuntu.com/questions/97272/how-long-does-it-take-to-complete-the-review-stages-in-ubuntu [15:45] dmj726 asked: How will proprietary apps be reviewed for security? [15:46] apps submitted through the app developer process are not subject to the same security policies of those in the Ubuntu archive [15:47] let me ask davmor2 to provide some more details in a minute [15:47] Gontxo-Vitoria asked: If I make a app that is foss, i can't not sell it in ubuntu? [15:47] yes, you can also sell free software apps! [15:48] http://developer.ubuntu.com/publish/commercial-software-faqs/ covers that too [15:48] pawel_st asked: As an app author, am I obliged to support all currently supported Ubuntu releases, or can I target a specific (latest) Ubuntu release with my app? [15:49] we recommend you to support as many releases for the sake of making your app more widely available, but we do not enforce you to do it [15:49] dmj726 asked: I've seen magazine issues and books in the Ubuntu Software Center. How would one publish something like that through Ubuntu? [15:50] I'm not sure I understand the question, we already publish them in Ubuntu, which means making them available in the Software Centre! [15:50] I've got some more details on the security question from davmor2: [15:50] dmj726 asked: How will proprietary apps be reviewed for security? reference to this, you are currently limited to which directories you can write to. However security is strictly the responsibility of the application developer and it is they that become liable for any breach of these ref the developer contracts [15:51] There are 10 minutes remaining in the current session. [15:51] pawel_st asked: What are acceptance criteria for commercial apps? Is acceptance process transparent? Is this only about packaging quality etc., or are there other criterias such as conformance to patents etc.? Can I get an early draft of my application reviewed against acceptance criteria before investing time and effort into its further development? [15:53] if it's not covered on http://developer.ubuntu.com/publish/commercial-software-faqs/, then it's on an app-by-app basis. I'd recommend submitting the draft of your application and then reviewers will get in touch with you [15:53] cwayne asked: how long will an app stay in 'pending review' state for? [15:54] you can find the details here: http://askubuntu.com/questions/97272/how-long-does-it-take-to-complete-the-review-stages-in-ubuntu [15:54] any more questions? [15:55] dmj726 asked: Are commercial apps vetted for any sort of quality to avoid malicious apps? [15:55] There are 5 minutes remaining in the current session. [15:55] dmj726: so there is a developer review and qa steps to pick up on obviously broken/unistallable apps as for malicious this again falls to the liability of the app developer. [15:56] so if there are no more questions for now, just a quick reminder on how to get help or get in touch [15:56] [15:56] Getting help [15:56] ============ [15:56] [15:56] If you need any help or if you've got any questions, be it during or before the [15:56] publishing step, there is an awesome, awesome community of app developers out [15:56] there just like you, willing to lend a hand [15:56] Check out: [15:57] http://developer.ubuntu.com/community/ [15:57] From there, I'd like to highlight: [15:57] Real-time chat: http://webchat.freenode.net/?channels=ubuntu-app-devel [15:57] i.e. the #ubuntu-app-devel IRC channel on Freenode [15:57] Askubuntu: http://www.askubuntu.com/questions/ask?tags=application-development [15:58] For all your app development related questions [15:58] Mailing list: https://lists.ubuntu.com/mailman/listinfo/ubuntu-app-devel [15:58] Also for all your questions and longer discussions [15:58] And finally, here's an overview on how to stay up to date: [15:58] http://developer.ubuntu.com/2011/11/building-the-ubuntu-app-development-community-i-communication-channels/ [15:59] PaoloRotolo asked: If you have uploaded an app without packaging, after the packaging by review board, can you ask to download the packaged app? === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - https://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Questions in #ubuntu-classroom-chat || Event: Ubuntu Developer Week - Current Session: How to update a package to the latest upstream version in the repositories - Instructors: coolbhavi [16:00] For Free Software gratis apps, we currently recommend packaging your application yourself and put it in a PPA [16:00] Logs for this session will be available at http://irclogs.ubuntu.com/2012/02/01/%23ubuntu-classroom.html following the conclusion of the session. [16:00] thanks dpm :) [16:00] Hi all I am Bhavani Shankar a 24 year old ubuntu developer from India and I am going to take you through the process of upgrading packages in the ubuntu archive [16:01] Before we start a bit of dev environment preparation; Make sure you have packaging-dev package installed if you are running on oneiric :) or please go through the session logs of dholbach's session yesterday :) [16:01] So lets start :) [16:01] Upgrading a package generally means upgrading a package to the latest upstream version in the ubuntu archive [16:02] normally, we would get the update from debian in the form of a merge or a sync, but there are cases when we don't, like for example if debian is in a freeze, or the package is orphaned, or its a native ubuntu maintained package [16:02] or we simply need it urgently (in case of a RC bugfix, for instance), and then pass the result back to debian [16:03] So assuming there are no doubts lets move on :) [16:03] so, we now know we have a new upstream version, first thing to do is to get it [16:03] We can either download it using wget or uupdate [16:04] Or if we have a watch file under debian directory in the current package, we can use that giving the command "uscan" at the source tree root [16:04] (More on debian/watch here http://wiki.debian.org/debian/watch) [16:04] uscan --verbose would say a bit more about what we are trying to do (in fact uscan calls upon uupdate :) more on uupdate: please see man uupdate) [16:05] finally, there could be a get-orig-source target in debian/rules that we can use [16:05] by executing "make -f debian/rules get-orig-source" in the source tree [16:06] A check here: be careful to read the previous entries of debian/changelog as the previous packager could have mentioned something he did with the previous version of the upstream tarball (like for instance repacking the tarball) which comes in detail later in the session [16:07] ok, now that we have an upstream tarball, we need to rename it in accordance to our policy foo-1.1.tar.gz will become foo_1.1.orig.tar.gz [16:07] In the simplest case is if there are no changes to packaging and no changes outside of debian [16:08] Just untar your tarball, copy the old debian dir to the new source tree, Add a changelog entry and Build the package :) [16:08] I wish all the updates were so simple :) [16:09] (Previously prior to dpkg-source version 3.0 if the the previous packager made inline changes instead of using a patch system, (you could check this by checking the old diff.gz), Just making changes inside the debian directory would'nt be enough, you needed to run the patch the present version of the package manually and there you would experience some pain in some changes being obsolete and couldnt apply anymore or you would run uup [16:09] date ../foo_2.orig.tar.gz in the old version src tree to automate the whole manual process.) [16:10] But now thanks to dpkg-source version 3.0 which generates a debian-changes-* file while building if there are any changes outside the debian directory and wrt policy 3.9.2 throws out a lintian warning too :) [16:10] ( More about dpkg-source version 3.0 here: http://wiki.debian.org/Projects/DebSrc3.0) [16:11] A more complex scenario of updating a package would involve the following checks normally: [16:11] Checking licenses of all the files in the tarball (licensecheck -r --copyright command) [16:11] Checking if all the patches in the previous version are perfectly applicable or obsolete [16:12] Checking if there are new dependencies required for the new version of the package (this is usually reported in upstream ChnageLog, but sometimes you only discover it by looking at upstream autoconf files (or Makefile)) [16:12] Checking if the package installs files in a different manner for instance, any change in file locations (We may need to change our packaging then) [16:13] Checking if the package has a man page, desktop file, icons et al and we may want to install those or for ex. there is a .desktop file already existing we may want to validate the same. (desktop-file-validate) [16:13] sometimes upstream changes few things which need you to change compilation flags [16:14] if upstream is a library particular care has to be taken [16:14] checking if API/ABI change is reflected in SONAME/version (More on SONAME here: http://en.wikipedia.org/wiki/Soname) [16:15] (check-symbols command can help you in that) [16:15] you may need a library transition, which involves perhpas rebuilding many packages already in the archive [16:16] Perhaps at this point its better to go through a simple example for us to get started hands on :) [16:16] I hope I am not speeding up the session [16:17] Okay lets get started with our hands on :) [16:18] The package I am using as an example is my own debian package mobile-broadband-provider-info (Which I havent updated in quite sometime due to my schedule of things lately) [16:19] Type in a terminal mkdir m-b-p-i && cd m-b-p-i && dget -x https://launchpad.net/ubuntu/+archive/primary/+files/mobile-broadband-provider-info_20111113-1ubuntu1.dsc [16:19] Which will download the latest available version in ubuntu i.e 20111113-1ubuntu1 (Note: I'm not using apt-get source mobile-broadband provider info as it will download the respective SRU versions for oneiric,natty,maverick or lucid) [16:20] I ll wait for sometime now for those who are downloading the package [16:21] QUESTION: I'm getting an error Validation FAILED!! [16:22] obounaim, please do gpg --recv-keys [16:22] and retry dget -x https://launchpad.net/ubuntu/+archive/primary/+files/mobile-broadband-provider-info_20111113-1ubuntu1.dsc [16:23] or simple one pull-lp-source mobile-broadband-provider-info [16:25] so assuming everything is fine lets move on === Partyschaum is now known as Partyschaum^away [16:26] now if you do a cd mobile-broadband-provider-info-20111113/ and look in you will find a debian directory and most of our work is concentrated in around the debian directory normally [16:27] now if you look inside the debian directory you will see a changelog control mobile-broadband-provider-info.docs copyright rules watch files and a source directory [16:28] QUESTION: bzr branch lp:ubuntu/mobile-broadband-provider-info will work? [16:29] yes it will but m not explaining distributed devel method herr :) [16:30] its a more conventional explanation here for a start off :) [16:31] obounaim, QUESTION: i don't have the mobile-broadband-provider-info-20111113/ directory ? [16:31] Please make sure you extracted the source properly [16:34] ok so now moving on, inside the source directory you will find a file called format which contains something as "3.0 (quilt)" which specifies that this is a dpkg-source version 3.0 package [16:34] Now if you look at the watch file it states that its a dummy watch file (which I created to satisfy lintian as the package is maintained and updates are pushed into git and no orig tarball is available for same for a dynamic update (once in 1 month, 2 months)) [16:35] Now since the debian/watch file is unavailable if you take a look at debian/rules file you can see that we have defined a get-orig-source target. [16:37] Now to parse through the get-orig-source rule you saw in debian/rules, you need to install automake and git-core packages as specified in the debian/rules file [16:39] assuming there are no doubts at this point, lets move on [16:41] So, running make -f debian/rules get-orig-source inside mobile-broadband-provider-info-20111113/ directory will download the latest version of the changes in git-head and converts the same to a tarball mobile-broadband-provider-info-20120201 and untars it creating a directory mobile-broadband-provider-info-20120201 going by the sequence of commands under get-orig-source in debian/rules [16:42] Now since there are no changes or patches outside the debian directory copy the debian directory from mobile-broadband-provider-info-20111113/ to mobile-broadband-provider-info-20120201/ [16:43] Once done navigate to the debian directory in the new source tree and type dch -i and give a version as 20120201-0ubuntu1 (-0ubuntu1 since this version is not present yet in debian but in ubuntu) targetted to precise since that is the devel version presently [16:46] (Looks something like mobile-broadband-provider-info (20120201-0ubuntu1) precise; urgency=low) [16:46] And update the changelog as * Merging upstream version 20120201 from git and make a list of upstream changes mapping the LP bugs closed in the changelog (Changelog writing will be taken up as a seperate topic by myself tomorrow where I'm going to explain changelog writing specifics) [16:48] QUESTION: I heard about fakeroot. What's difference between fakeroot debian/rules ~ and make -f debian/rules ~ ? [16:50] There are 10 minutes remaining in the current session. [16:50]

to

with

being the biggest heading and