[02:25] ok [02:25] ok [02:26] right, what does the fdisk prompt say now? [02:26] Command (m for help): ? [02:26] root@phlak [02:26] Last cylinder or +size or +sizeM or +sizeK (358-5169, default 5169): 5169 [02:26] Command (m for help): t' [02:26] Partition number (1-4): 1 [02:26] Hex code (type L to list codes): 83 [02:26] Command (m for help): t [02:26] Partition number (1-4): 2 [02:26] Hex code (type L to list codes): 82 [02:26] futurama141: Do you really have bad sectors on your hard disk, or was oinck just joking about it ? [02:26] Changed system type of partition 2 to 82 (Linux swap / Solaris) [02:26] Command (m for help): [02:27] root@Phlak:~# [02:27] root@Phlak:~# p [02:27] -bash: p: command not found [02:27] root@Phlak:~# Partition number (1-4): 3 [02:27] -bash: syntax error near unexpected token `(' [02:27] root@Phlak:~# First cylinder (358-5169, default 358): 358 [02:27] -bash: syntax error near unexpected token `(' [02:27] i dont know!! [02:28] futurama141, hmm, for some reason fdisk's quit and gone back to the shell [02:28] so what do i do? [02:28] futurama141, what does this command give you? fdisk -l /dev/hda # or whatever your disk is [02:28] mika_videodev, we can use fsck to check the swap partition - then zero it out again [02:28] futurama141: Ok, if you did not mention anything about bad sectors first, then it was just oinck joking. In that case you can forget everything about bad sectors. [02:29] unop: can you really use fsck to check a swap partition, or do you mean you need to first change it to a linux partition, then chechk, and fionally change back to swap partition ? [02:30] mika_videodev, the latter [02:31] futurama141, you still there? [02:31] try cfdisk, it is easier to use [02:31] yea [02:31] i have no clue [02:31] futurama141, copy and paste the output of that command. [02:31] futurama141: cfdisk /dev/hda [02:31] it wont [02:31] it wont paste [02:32] futurama141, ok, never mind that then. do what mika_videodev suggested [02:32] well, if fdisk for some reason was interrupted before a normal write and quit, I guess it did not save any of it's changes, and the partition table is in whatever state it was before starting to use fdisk [02:33] mika_videodev, it's plausible that fdisk was manuall interrupted too [02:33] manually* [02:33] and: if you have the ubuntu's install iso somewhere, it may be wiser to save it to an existing partition (you may format it but do not delete and re-create) [02:34] burn ubuntu iso to cd in phlak: help please? [02:34] formatting with mke2fs can also check for bad sectors if you suspect there are some (but it needs an option to do that) [02:35] wait, how do i install gparted? [02:35] for that to work, you either need 2 optical drives (one for phlak, one that can write to a cd-r) [02:35] or else, you must load the plack to ramdisk [02:35] futurama141, you said you had no CDs [02:35] i dont [02:36] futurama141, so how can you burn the ISO then? [02:36] nevermind [02:36] i would do that witk k3b, but it is possible to do it with just a command line tool as well.... [02:36] futurama141, come on make up your mind, we haven't got time for indecision. what do you want to do? [02:36] i only have one OD [02:36] futurama141, do you want to continue formatting the disk? [02:36] i want to get the hard drive formatted [02:37] check what partition(s) do you have right now on the hard disk before deciding what to do [02:37] new terminal [02:37] sudo -i [02:37] futurama141, ok, follow mika_videodev .. he'll help you with cfdisk [02:37] you can format with mke2fs if you don't need to modify partition sizes [02:37] i dont know what that is, but ok [02:37] i dont know if i have any partitions [02:38] mika_videodev, just create three partitions .. one for the ISO to be placed, one for swap and another for / [02:38] mke2fs is a tool with what you can format already existing partitions [02:38] fdisk -l will tell you, but not modify anything [02:38] it wil also tell you the size of the hard disk [02:38] ok how to i copy and paste text from the terminal? [02:40] futurama141: didn't you already do some copy&paste with the mouse ? [02:40] oh! [02:40] i did, but i didnt know how i did it [02:40] i figured it out [02:40] ok, check this... [02:40] (root@Phlak)(6/ttyp0)(04:40pm:08/31/08)- [02:40] (#:~)- sudo -i [02:40] root@Phlak:~# fdisk -l [02:40] Disk /dev/hdc: 40.0 GB, 40020664320 bytes [02:40] 240 heads, 63 sectors/track, 5169 cylinders [02:40] Units = cylinders of 15120 * 512 = 7741440 bytes [02:40] Device Boot Start End Blocks Id System [02:40] /dev/hdc1 * 1 5168 39070048+ 7 HPFS/NTFS [02:40] root@Phlak:~# [02:41] oh, you have one gigantic partition of NTFS type covering all of the disk space (NTFS = used in win 2000, XP and possibly vista) [02:42] And you are ok to delete all data on that win XP partition ? [02:42] yes [02:43] in that case, I'd first try to test this: mke2fs -c /dev/hdc1 (note: some more options may need to be used too... !) [02:43] root@Phlak:~# mke2fs -c /dev/hdc1 [02:43] mke2fs 1.36 (05-Feb-2005) [02:43] /dev/hdc1 is mounted; will not make a filesystem here! [02:43] root@Phlak:~# [02:44] you need to first umount /dev/hdc1 [02:45] root@Phlak:~# unmount /dev/hdc1 [02:45] -bash: unmount: command not found [02:45] root@Phlak:~# [02:45] umount [02:45] ok [02:45] root@Phlak:~# umount /dev/hdc1 [02:45] root@Phlak:~# [02:46] it's now unmounted [02:46] ok ... [02:46] now: if you suspect there may be bad sectors: try this: ... [02:46] idk [02:47] mke2fs -c -j -m 1 - L somename /dev/hdc1 [02:47] or, if you are quite SURE there are bad sectors, then ... [02:47] somename? [02:47] otherwise same, but mke2fs -c -c -j ... [02:47] futurama141, somename is the label you want to assign for the partition [02:47] you can put there whatever name you want to give your partition [02:48] if you think it is very likely / sure there ARE bad sectors, then it's a good idea to put that -c there twice. It is slower, but will check the disk more carefully for bad sectors [02:48] root@Phlak:~# mke2fs -c -j -m 1 - L barf /dev/hdc1 [02:48] mke2fs 1.36 (05-Feb-2005) [02:48] mke2fs: bad blocks count - L [02:48] root@Phlak:~# [02:49] futurama141, you have a space between - and L there [02:49] mika_videodev, and why adjust -m .. 5% is good [02:49] uop, do you have any idea why it answers like "mke2fs: bad blocks count - L" - ??? [02:50] mika_videodev, the command wasn't entered in right [02:50] yes, you can put -m 5 also if you like. It just tells how many % is reserved for the root user only [02:50] oh, it should be -L with NO space ... [02:50] mika_videodev, yes, and 5% is a good default .. it allows you to recover the system with ease should your disk get filled up [02:51] mika_videodev, and since this is his system - leave the defaults be [02:51] futurama141, for general use, unop is correct. I just copied the line I used to format additional partitions for video usage ... [02:52] futurama141: in that case mke2fs -c -j -L barf /dev/hdc1 would be fine [02:53] but how can the amount of system RAM be checked ? [02:54] unop: are you aware of some way to force the kernel reread the partition table and immediately switch to use the version just read ? [02:55] mika_videodev, errm, no [02:55] heh.. he's left - just great [02:55] futurama141: if you have 3 people standing behind you and have no CD-R's (but do have a CD or DVD writer), why not send someone shopping for a CD-R ? [02:56] mika_videodev, he's gone [02:56] unop: seems so. But if there is such a command to the kernel, I'd like to know about it too ! [02:58] mika_videodev, I'm not aware of a way .. but i presume if you can umount all filesystems, you should be able to make changes to partitions then remount them -- might struggle with / tho [02:58] I don't understand why such a comman does not exist. It could be implemented so, that mounted partitions stay as they are, and prevent the space occupied by them to be uses as another partition that overlpas the space, but is not exactly the same partition, possibly just with different ordinal number. [02:58] mika_videodev, all this in runlevel 1 off course [02:59] For example the makers of gparted argued about this, but the kernel folks just decided to ignore the matter [03:01] mika_videodev, well, i'd say it wouldn't be safe for you to adjust partition boundaries without first unmounting the filesystems on them .. because the kernel could be accessing a set of files in the area of disk you are modifying and you wouldn't want it to panic on you. [03:02] in any case .. the need for something like this is trivial, and you can always do something similar by booting the system offline or in recovery mode [03:03] of course, it is better to NOT delete/modify a partition that is mounted. But outside of the area occupied by any mounted partitions, there is no reason to prevent modifying / adding / deleting other (not mounted) partitions. [03:27] hello [03:27] test message [03:30] test message received. [03:30] yep, its working on my end. [03:30] :D === dholbach changed the topic of #ubuntu-classroom to: Ubuntu Classroom || https://wiki.ubuntu.com/Classroom || https://lists.ubuntu.com/mailman/listinfo/Ubuntu-classroom || Next Event: Ubuntu Developer Week: https://wiki.ubuntu.com/UbuntuDeveloperWeek | Questions about the presentation in #ubuntu-classroom-chat (prefix with QUESTION: ...) === Socceroos is now known as Socceroos_work === EdwinMoore is now known as EdwinMoore_ === EdwinMoore_ is now known as curdsy === curdsy is now known as EdwinMoore === buunso is now known as buunso_ === buunso_ is now known as buunso === e-jat is now known as fendora === fendora is now known as e-jat === e-jat is now known as fenris- === tm_work is now known as themoler === dholbach_ is now known as dholbach === thekorn_ is now known as thekorn === ALAY1 is now known as ALAYA === krazyd__ is now known as krazyd === krazyd___ is now known as krazyd [14:33] exit [15:02] \join #ubuntu-classroom-chat === thekorn_ is now known as thekorn [15:11] @schedule rome === krazyd___ is now known as krazyd [15:31] woooooo [15:33] welcome everybody - 1h25m to go until the first session! :-) [15:36] :) [15:38] dholbach: I'm ready :P [15:38] me too... just 2 more hours [15:41] * popey hugs dholbach [15:41] * dholbach hugs popey back [15:42] \o/ [15:48] * Sulabh pokes bibstha [15:56] silly developers. hugs are for bug testers. [15:57] * popey is weary of hugging Myrtti === dholbach changed the topic of #ubuntu-classroom to: Ubuntu Classroom || https://wiki.ubuntu.com/Classroom || https://lists.ubuntu.com/mailman/listinfo/Ubuntu-classroom || Next Event: Ubuntu Developer Week: https://wiki.ubuntu.com/UbuntuDeveloperWeek | Questions about the presentation in #ubuntu-classroom-chat (prefix with QUESTION: ...) | Run date -u to find out what UTC time is right now [16:01] date -u [16:01] whoops! [16:01] run in terminal ;) [16:01] lun set 1 14:58:53 UTC 2008 [16:01] nellery: Yeah... [16:01] Understood it after a while :P === fschrat is now known as fnordschrat === fnordschrat is now known as fschrat === emgent is now known as emgent`NL === fschrat is now known as fnordschrat [16:24] date -u [16:24] Mon Sep 1 15:24:17 UTC 2008 [16:26] uname -a [16:26] No output? [16:27] No output. :( [16:27] date -R [16:27] Linux h1079978 2.6.15-51-server #1 SMP Tue Feb 12 17:12:18 UTC 2008 i686 GNU/Linux [16:28] Linux fuck 2.6.26-ARCH #1 SMP PREEMPT Tue Aug 26 21:15:43 UTC 2008 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ AuthenticAMD GNU/Linux [16:28] \o/ [16:28] clever hostnames... [16:28] Yeah [16:29] Why are you spamming the output of uname -a? [16:31] I can't consider one post spam. [16:37] date -u [16:37] sorry [16:38] mcas sorry, i'm taken. [16:39] (but there are plenty of fish in the sea) [16:39] CShadowRun: -_- [16:39] :D [16:39] CShadowRun: can't you get back to playing WoW unfairly? :P [16:40] i only did that as a proof of concept :p [16:40] cupe^: collectively when it's a semi-large amount of output, though... [16:40] i'm messing with python again now :D [16:40] Anyway, as jpds said, on-topic here. [16:40] Back to -uk for off-topicness. [16:40] there is #ubuntu-classroom-chat too [16:42] But even that should stay mildly on-topic, no? [16:42] I thought it was the place to ask relevant questions, send notes behind the teacher's back, etc.. [16:43] :D [16:52] Hello [16:52] yeah, there's usually a bit of chat/banter in -chat [16:57] hckoe: ircing as root? [16:57] so how are you all doing? everybody excited? :-) [16:57] dholbach: very (:) [16:58] yup [16:58] yes^^ [16:58] Yeah [16:58] * nxvl waves [16:58] dholbach +1 [16:58] i'm just here for the free soda [16:58] Have no idea what will happen though [16:58] But sounds like fun [16:58] yeah... [16:58] :-) [16:58] * daradib is ready for the excitement [16:58] \o.o [16:59] a thunderstorm is coming up here... let's hope it will not kick me out of the net ;-) [16:59] neither me nearby [16:59] hi bullgard4 [16:59] Ok my friends.... are you ready for another Ubuntu Developer Week? [17:00] let's get cracking :-) [17:00] dholbach: YES! [17:00] * Tm_T hides [17:00] YES [17:00] yep [17:00] dholbach, YES, rock on! [17:00] yes! [17:00] get it on!! [17:00] Some people might know me already, I'm Daniel Holbach, living in Berlin, Germany and always had a lot of love for the MOTU team, and work for Canonical for ~3 years now. [17:00] wooohoooo! [17:01] I'll try to answer a few of the regular Developer Week questions beforehand [17:01] wooooo [17:01] the schedule is up here: https://wiki.ubuntu.com/UbuntuDeveloperWeek - and please use 'date -u' (in the terminal) to find out which UTC time we have right now :) [17:02] questions go into #ubuntu-classroom-chat, please prefix them with QUESTION: [17:02] I'll take a look over there and copy them all over every once in a while [17:02] let's try not to have too many disturbances in the session itself [17:02] OK... who's here for the "Packaging 101" session? :-) [17:02] * dholbach expects a lot of raised hands [17:02] I am [17:02] \o [17:03] I am === hckoe_ is now known as hckoe [17:03] ME! [17:03] i am [17:03] * techno_freak raises hand [17:03] o/ [17:03] * daradib raises hand [17:03] _o/ [17:03] here [17:03] \o/ [17:03] * jrib [17:03] me me [17:03] * qense is partially here! [17:03] * Oli`` raises both hands [17:03] me [17:03] * Shunpike raises hand [17:03] * jpds too. [17:03] here! [17:03] Ay [17:03] me too [17:03] * kevjava raises hands sheepishly. [17:03] here! [17:03] even though I will not be present o/ :) [17:03] * xander21c raisees hand [17:03] Me [17:03] hello! [17:04] excellent... I'm very excited and very happy you're all here [17:04] just to make clear what you can expect during the session [17:04] in this session we're not going to package something from scratch, instead I'll talk you through the bare-bone structure of a package, so the stuff that makes a package build and you will encounter in almost all packages [17:05] I'll try to answer as many questions as possible [17:05] for more info, I'd recommend https://wiki.ubuntu.com/MOTU/GettingStarted [17:05] and of course http://youtube.com/ubuntudevelopers [17:05] ok... let's get started [17:05] please all install the devscripts package [17:05] sudo apt-get install devscripts [17:06] it contains tools we need for packaging and that make your life a lot lot easier [17:06] afterwards, please get the source package we're going to look at together today [17:06] dget http://daniel.holba.ch/motu/hello-debhelper_2.2-2.dsc [17:07] if I'm too fast or something doesn't work or I'm unclear, please ask in #ubuntu-classroom-chat [17:07] if you look at the downloaded files you will notice there's a .dsc a .diff.gz and a .orig.tar.gz [17:08] it's the first thing you'll notice: we're not talking about .deb files (binary packages), but source packages [17:09] when you start doing ubuntu development, you will always deal with those kind of files, so let's take a closer look [17:09] the .orig.tar.gz is the original unmodified source code tarball that was released on the homepage of the upstream developers (software authors) [17:09] the .diff.gz is the compressed patch we apply to make it build "our way" [17:09] what does "our way" mean? [17:10] we need to add a bunch of instructional files to be able to apply ONE build process to all kinds of source packages (no matter if they are python, PHP, C, C++, etc) [17:10] dscverify: can't find any Debian keyrings [17:11] you can safely ignore that warning [17:11] now please run [17:11] dpkg-source -x hello-debhelper_2.2-2.dsc [17:11] dpkg-source will then extract the tarball and apply our patch [17:11] the .dsc file is used to check the md5sum and so on (it contains a bit of meta-data about the source package) [17:12] QUESTION : we need to add a bunch of instructional files to be able to apply ONE build process to all kinds of source packages. Could you elaborate this please ? [17:12] raseel: some of you might have tinkered with ./configure; make; sudo make install when building software from source [17:12] yes [17:12] this applies to most of the packages that use the auto tools (automake, autoconf, etc) [17:13] but there's lot of other cases, for example python packages that use distutils need python setup.py build, python setup.py install etc [17:13] some packages don't have an upstream build system at all, but just contain a few files that need to be shipped === duluu is now known as mazaalai [17:14] I'll get to the "Makefile" part of the source package in a bit, basically we expect a few Makefile targets (clean, install, etc) to be around, so all packages can be built "in the same way" [17:15] ok, let's get cracking and dive in [17:15] cd hello-debhelper-2.2 [17:15] and check out debian/changelog [17:15] debian/changelog has a very strict format you need to adhere to [17:16] fortunately there's the dch tool in devscripts that makes the task easier [17:17] each upload specifies: the name of the source package, the revision, the part of Ubuntu (or Debian) it is uploaded too, the changelog entry text itself and who made the particular upload [17:17] (plus the timestamp) [17:17] whenever you work on packages you need to put some good effort into making it clear WHAT you changed and WHY [17:18] in Ubuntu we maintain all packages a one big team, therefore the next uploader should not have to guess where you got a patch from, why it was applied and the tricky conditions under which you made a package build :-) [17:18] let's take a look at the topmost entry [17:18] the upload has the revision number 2.2-2 and was uploaded to "unstable" [17:19] 2.2 (the part in front of the dash) means: this is the upstream release that was packaged [17:19] (remember the hello-debhelper_2.2.orig.tar.gz which basically said: these are the unmodified changes that upstream released as 2.2 on their homepage) [17:19] QUESTION : Does the debian/changelog file exist for only Debian packages ? [17:19] good question [17:20] no... whenever we make a change in Ubuntu we describe our changes in the same file [17:20] what changes is the version number [17:20] if I was to change a tiny bit in the package, I'd upload 2.2-2ubuntu1 [17:20] which would mean: [17:20] - 2.2 was released upstream [17:20] - 2 revisions have been made in Debian [17:20] - 1 in Ubuntu [17:21] then I'd forward my change to the Debian maintainer, he'd incorporate it in [17:21] 2.2-3 [17:21] and we could "sync" the package from Debian again [17:21] QUESTION: so ubuntu counter gets resetted after each debian release ? [17:22] tacone: "resetting the counter" would mean: overwriting all Ubuntu changes with the changes that have happened in Debian [17:22] if you decide to do that you need to be V E R Y careful [17:22] and when I say very, I mean [17:22] [17:22] __ _____ _ __ _ _ [17:22] \ \ / / _ \ '__| | | | [17:22] \ V / __/ | | |_| | [17:22] \_/ \___|_| \__, | [17:22] |___/ [17:22] :-D [17:23] if you're not careful enough you might drop other small bits that were important to Ubuntu users and might be a regression [17:23] so in cases where we're not able to sync straight-away (different opinions of maintainers, upstream, etc) we need to merge [17:23] QUESTION:And if it is NOT a Debian package ? [17:23] raseel: can you elaborate? [17:23] raseel: you mean if we inherited a package from "some other place"? [17:24] yes [17:24] we'd still add "ubuntu1" to the version string to indicate that we did an Ubuntu-local change [17:24] in cases where there are no "ubuntu" revisions the sync happens automatically at the beginning of the release schedule [17:25] QUESTION: then I don't understand. If debian releases 2.2-3 which number shall my next release (for ubunt) have ? [17:25] tacone: if you need to merge, it'd be 2.2-3ubuntu1 [17:25] (carry over important Ubuntu changes) [17:25] NEW QUESTION: Isn't this a bit weird? If I'm right this means that 2.2-2ubuntu1 could be exactly the same as 2.2-3. [17:25] qense: it could, you need to make sure that it IS exactly the same [17:25] QUESTION: What if you take a source from SuSE, would that work? [17:25] jscurtu: no, the build process is different there [17:25] QUESTION: what does 0ubuntu1 mean? [17:26] it means we introduced a new upstream version in Ubuntu before we got it from Debian [17:26] ok... let's move on, just 31m left :) [17:26] I hope the concept of debian/changelog is almost clear now - if not, the other sessions this week of the Packaging Guide will enlighten you :) [17:27] let's take a look at debian/control together [17:27] you will see that it consists of two stanzas (at least two, two now because it's a simple package) [17:27] the first one is about the Source package, the following one(s) are about binary package(s) [17:28] a source package needs a name, a section and a maintainer [17:28] the Standards-Version gives us a clue which version of the Debian Policy (THE document if you need to know about packaging rules) the package complies with [17:28] and a very very intersting other bit: Build-Depends [17:29] Build-Depends means: this is the bare minimum of packages that are required to build the package [17:29] what happens if I upload a revision to the build daemons (soyuz) is: [17:30] the will extract the package (just like we did), copy it into a minimal build environment (chroot containing build-essential which gives us make, etc), then install the build-depends [17:30] and then attempt to build it [17:30] in this case only debhelper is required (of a version >= 5) [17:30] let's take a look at the second stanza [17:31] it describes the resulting binary packages (all files that are going to be installed into the package go into one package) [17:31] it has a package name and description (that turns up in synaptic, adept, etc) [17:31] and two interesting bits: Architecture and Depends [17:32] Depends is easy to explain: it's the binary packages this resulting binary packages requires to be installed [17:32] ${shlibs:Depends} is just a bit incomprehensible [17:32] if you run this on a terminal [17:32] apt-cache show hello-debhelper | grep ^Depends [17:33] you will get something like this: [17:33] Depends: libc6 (>= 2.5-0ubuntu1) [17:33] this means the hello-debhelper package that is in the archive needs libc6 to be installed [17:33] the process how we get from ${shlibs:Depends} to libc6 is very interesting and I can only briefly explain it here [17:34] basically the build process will figure out which shared libraries the binaries (stuff in /usr/bin/ or /usr/lib/ etc) in our package are linked against and which package they are in [17:34] and substitute ${shlibs:Depends} with the right dependencies [17:35] this is a very very awesome piece of voodoo that happens automatically during the build :) [17:35] "Architecture: any" means build this source package individually on all the available architectures in the data center [17:36] in the data center we have supported architectures like amd64 and i386 and community ports like powerpc, sparc, hppa, ia64, lpia, etc [17:36] if you build C source for example you want the source to be built on each and every architecture individually [17:37] if you use "Architecture: all" it will mean: this package can be used on ALL architectures (package that contains artwork or a few python scripts that don't need to be compiled) [17:38] QUESTION: Some more explanation on "Section" part of the control file would help [17:38] Check out http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections [17:38] QUESTION: Doesn't ${shlibs:Depends} work in the Build-Depends field? Why not? [17:38] no there isn't, you need to specify them manually [17:39] there are indicators for build-depends though (configure.in or configure.ac in packages using autoconf, or setup.py in python distutils packages) [17:39] QUESTION: I can't find a package "shlibs"... if it's not a package, what is it? (or if this is part of the voodoo, where can I read more about the voodoo :)) [17:39] kevjava: it's just placeholder that will be substituted after the build [17:40] it could be #PLEASE_SUBSTITUTE_WITH_SHARED_LIBRARY_DEPENDS# but it's ${shlibs:Depends} :-) [17:40] alright, let's crack on [17:41] debian/copyright is another critical part of the package [17:41] critical for different reasons though - it has little to do with the actual build process, but it makes sure we reflect all the copyright holders, copyrights and upstream authors in the package [17:42] there is content we can't ship because of licenses that forbid us to make changes, etc [17:42] this section is (when you create a package from scratch) something you need to pay a lot of attention to [17:42] Steve Langasek will talk about "How to avoid making Archive Admins unhappy" later this week [17:43] basically it need to contain: [17:43] - the upstream authors [17:43] - ALL copyright holders (make sure you check all files) [17:44] - ALL licenses of all files [17:44] in most cases it will be easy (COPYING file says GPLv3) and you just need to double-check [17:44] be very careful, there's a lot at stake if we slip code into the archive (even worse: on the CDs) we're not allowed to redistribute, etc [17:45] once again: the packaging guide has more info about it [17:45] https://wiki.ubuntu.com/PackagingGuide [17:45] QUESTION: so you have to copy the content from all the license files in there ? [17:46] tacone: yes, the source tarball should ship the verbatim license texts all itself and you need to reiterate them (and/or point to /usr/share/common-licenses/ if they're available there) [17:47] fnordschrat> QUESTION: i noticed some version strings like "2:1.0~rc2-0ubuntu13" what does the "2:" mean [17:47]