[00:44] Hi pinkey :) [01:16] boredandblogging: hi there nick, nice podcast === ssweeny is now known as rmonroe === rmonroe is now known as ssweeny === rgreening_ is now known as rgreening === woody86_ is now known as woody86 [02:34] hello [02:43] hi [02:43] hi [02:43] hii === rgreening_ is now known as rgreening [02:44] =) [02:44] :) [02:50] ignore: #ubuntu-classroom CRAP NOTICES SNOTES CTCPS JOINS PARTS QUITS KICKS MODES WALLOPS NICKS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS [02:52] thilmegil: I assume you want it to be writable by users other than root? [02:52] jrib: yes i want all partitions except for / to be writtable by me [02:52] thilmegil: so what chown command did you try? [02:53] jrib: before my latest re install i had tried sudo chown R- kenny:kenny /path/to/drive [02:54] thilmegil: the - goes before the R [02:54] jrib: the dash may have been in front of the R i was being walked through by a person from #ubuntu [02:54] do that now [02:54] jrib: ok [02:54] thilmegil: and by /path/to/drive you mean /path/to/mount/point right? [02:55] jrib: yes [02:55] jrib: sorry still switching from windows in my head [02:56] jrib: chown has been run [02:56] ls -ld again [02:57] jrib: now it says kenny kenny where before it said root root [02:57] thilmegil: you should be able to write now [02:57] so i have to do this for all of my mount points? [02:57] thilmegil: for the ext ones, yes [02:57] jrib: what about chmod? do i need to do that? [02:58] thilmegil: no [02:58] what about my ntfs mount points? [02:58] thilmegil: use ntfs-config [02:58] is this a program or a command? [02:58] programs are commands, no? [02:59] thilmegil: you install it in synaptic though [02:59] it shows up in your menu somewhere [02:59] ok thank you. a program is a list of commands where as a command alone is one command [02:59] at least thats my simpleton view of it [02:59] i could be way off base [02:59] but thank you for your help [03:01] thilmegil: no problem === a1len__ is now known as a1len____ === a1len____ is now known as a1len === PrivateVoid_ is now known as PrivateVoid === Silvy is now known as Fierelin === Fierelin is now known as Silvy === Silvy is now known as Fierelin === alberto is now known as Guest68478 [08:15] ... [08:23] hi === Rafik_ is now known as Rafik [10:34] may i ask when will be the next session ? [10:35] sumit: look in the topic [10:36] thankx === rgreening1 is now known as rgreening === agoodNando is now known as agood_away [13:41] how to uninstall kubuntu from ubuntu [13:45] junaid, sudo apt-get remove kubuntu-desktop [13:49] hi [13:50] hi [14:02] hi [14:22] hi [14:22] when the classroom start? [14:22] hi [14:22] hophet, topic [14:30] knome: lets go [14:30] 30mins until the first session. [14:32] "How to help maintain the packages" [14:32] or the tree [14:33] edubuntu. [14:35] sorry, i get it! === tad is now known as rrittenhouse === dholbach_ is now known as dholbach === agood_away is now known as agoodNando [15:02] Good morning everybody! [15:02] hello [15:02] Welcome to the 2nd day of the Ubuntu Open Week [15:02] good morning [15:03] good evening [15:03] you'll have to forgive me a little bit, it's 7am local time and I'm still waking up ;-) [15:04] OK, so we're going to start off the day with a project that is near and dear to my heart, Edubuntu [15:04] has everybody heard about Edubuntu? [15:04] yep [15:04] yes [15:04] awesome [15:05] üdv [15:05] for those of you who don't know, Edubuntu is the Ubuntu "derivative" dedicated to education [15:05] it's an officially supported derivatives, just like Kubuntu [15:05] but rather than focusing on a different desktop environment, it's focused on a different target [15:06] specifically, bringing Ubuntu, open source, free software to kids, students of all ages, teachers, and schools [15:07] Edubuntu has worked on that target by creating a great classroom server [15:08] Edubuntu had pushed LTSP (Linux Terminal Server Project) into schools around the world [15:08] it's also tried to include the best the free software world has to offer in educational tools, such as gcompris, KDE Edu, tux4kids [15:09] QUESTION: can you explain about ltsp a little bit? [15:09] well, I'm not going to go into huge detail about it here, but it's really pretty awesome, IMO [15:09] lol [15:09] the basic idea is that you have a central server, where all the programs and administration takes place [15:10] then "thin clients" connect to that server and an "image" is loaded up in RAM on the client that then connects to the server [15:10] so you can run say 30 clients off of one server [15:10] and you have *1* machine to administrate [15:10] the thin clients don't even need a hard drive [15:11] I would point people to http://ltsp.org and #ltsp for more info [15:11] LTSP is not only used a lot in education, but also in corporate settings [15:12] and you can install it from the Ubuntu Alternate CD [15:12] any other questions so far? [15:12] ok, moving on then :-) [15:13] QUESTION: Can Edubuntu used in primary school and in secondary school as well? [15:13] Edubuntu can be used in *any* school, IMO [15:13] we've used it in university labs before [15:13] the "theme" is quite a bit more suited for young children and elementary schools [15:14] but that can easily be changed [15:14] we try to have 2 themes generally, a "young" one and one that's more suitable for secondary and tertiary [15:14] Question: How edubuntu protects or promote the free knowledge? [15:15] in terms of applications, it's mostly focused on pre-school and elementary right now, but I'm trying to move us more into secondary and tertiary as well [15:15] Well, Edubuntu certainly tries to protect and promote free knowledge by protecting and promoting free software [15:16] As the project develops I think we are going to start seeing more "free" content as well, we've thought about things like including free, scaled down Wikipedia content for instance [15:17] UESTION: Are there any architectural differences in Edubuntu vs Ubuntu? or is there difference in softwares only? [15:17] QUESTION: What are the most obvious difference for a desktop user between Edubuntu and Ubuntu? [15:17] ok, so that brings me to some technical bits of what exactly Edubuntu is [15:17] so technically right now Edubuntu is shipped as an addon CD to Ubuntu [15:18] Edubuntu started it's history (ancient by Ubuntu standards ;-) ) as a normal derivative [15:18] 1 CD installer with LTSP and some educational apps [15:18] however we out grew our single CD [15:19] so over a year ago we split into 1 installer CD + 1 addon CD [15:19] then for Hardy (8.04) we decided to drop the installer CD as it was mostly redundant with the existing Ubuntu CD [15:19] so LTSP now resides on the Ubuntu Alternate CD [15:19] and the educational programs are on the Edubuntu CD [15:20] but Edubuntu is really educational content [15:20] we "derive" from Ubuntu in that we require an Ubuntu desktop as a base [15:21] we're also working some on package that would base off of Kubuntu, but we haven't had a ton of interest there [15:21] so the most obvious differences are going to be 1) theme, artwork 2) a lot of educational programs in the menu [15:22] 3) LTSP goodness if you want it [15:22] QUESTION: What about the communication with other similar project like skolelinux, etc? Is it going to be extended? [15:22] We naturally have pretty good communication with Debian, as Ubuntu as a whole derives from Debian [15:22] q/win 21 [15:23] in the past people from K12LTSP and skolelinux have come to some of the Ubuntu Developer Summits [15:23] we try to keep good communication open, especially around LTSP, but of course that can always be improved [15:23] QUESTION: what edubuntu can offer to a programmer student for example? [15:24] well, Edubuntu specifically isn't going to offer you much right now [15:24] Ubuntu is simply *awesome* for programming students though [15:25] and Edubuntu has had a Google Summer of Code project for instance working on a Python "test" grader and teaching tool [15:25] but people should realize that Edubuntu is a very small community [15:25] with only 2-3 developers at any given time [15:26] so we'd love to see people join and work on new educational apps, but we mostly rely on other people (called upstreams) to write software [15:26] telebovich: does that answer your question some? [15:26] yes [15:26] so Edubuntu is the first official derivative to do the addon thing [15:27] I think we might see more of it [15:27] but it does create some unique issues [15:27] as people are used to 1 CD installs [15:27] but it gives us 700MB of room for the stuff that kids, students, teachers, and schools really care about [15:28] now we want to fill that up with the best open source/free software and content [15:29] so that's most of the info on what Edubuntu actually is: a addon CD on top of Ubuntu that can be used to either set up a Classroom Server (via LTSP) or a educational workstation [15:29] QUESTION: What are the biggest challenges facing Edubuntu and getting it into schools? [15:29] ok, that's a really good question [15:30] it really surprised me how hard it is to get Edubuntu (or any Linux OS) into schools [15:30] on the face of it one my think, "well it's so much cheaper, it's simple" [15:30] *might [15:30] but there are 2 primary challenges [15:30] 1) cost of transition [15:31] it takes quite a bit of work to completely convert a school from all-Microsoft to all-Edubuntu [15:31] and in fact most schools will never reach that [15:31] most schools have a mixed environment of Edubuntu in classroom labs and Microsoft elswhere [15:31] Hello !! [15:32] 2) curriculum inertia or curriculum conformance [15:32] schools have standard ways of doing things [15:32] many schools are mandated as to what they must teach in a computer curriculum [15:32] and quite often standards are wrapped around Microsoft products (such as MS Office) [15:33] or there are programs that students must use for testing, etc. that only run on Windows [15:33] that's a pretty big hurdle there, but in many areas of the world we're gaining ground [15:33] the Latin American countries really seem to be grabbing on to open source/free software [15:34] some European countries also are doing quite a bit [15:35] QUESTION: i'd like to know more about whether you plan on supporting common windows packages through wine/vms etc [15:35] ;-) [15:35] at this time we really don't have any plans to no [15:35] Some european countries ? Which ones ? I'm just curious [15:35] Spain and Macedonia are the ones that come to mind [15:36] thanks [15:36] Macedonia ordered up 100k Edubuntu computers for it's schools [15:36] comment: in latin american, especially Venezuela, the Free Software is winning big battles against the bussiness model of Microsoft... elementary school is right now teaching Ubuntu an Debian as the first Operative Sysytem [15:37] the problem with supporting particular windows programs, is that there are so very many of them [15:37] and this is a general issue with educational OSes in general [15:37] i live in Venezuela :) [15:37] me too :P [15:37] each country require different programs, each state, district, town, etc. may have it's own requirements [15:37] so it's very difficult for use to go through all the possibilities [15:38] I see [15:38] so our current strategy is to provide the best free/open source bits and let schools adapt them and put them together as needed [15:38] *however* wine is certainly available to them [15:38] but with only 2-3 developers we don't have resources to go through and make sure Windows apps work in wine [15:39] but it would be, IMO, a very cool project to have somebody test common Windows educational apps and put that on a wiki page [15:39] UESTION: there are any ideas about the fact that not only help the schools using Edubuntu, but as something to interact with school-developers? [15:39] darn, I keep missing that Q :-) [15:40] no problem we know what you meant [15:41] well, we really try to get the whole "stack" of people involved in education sort of "in the loop" [15:41] we talk to students, teachers, IT admins, school administrators, all the way up to occasionally Ministers of Education or similar [15:42] I'd personally *love* to interact with people who are writing educational code [15:42] I want to know how I, as an Edubuntu developer, can make their life easier as well as perhaps give a place for their code to live that will help other people [15:43] we have had a couple Ubuntu Education Summits [15:43] that are similar to the Ubuntu Developer Summits, but more about education and how we can get Linux into schools [15:44] we also have a fairly active mailing list, edubuntu-users (on lists.ubuntu.com) that often has discussion on new apps, etc. [15:44] UESTION: Are there any other projects that are available as addon CDs like Edubuntu is? The idea of having a common base system and being able to add specific functionality by downloading one CD seems quite useful [15:44] not in the "official" Ubuntu landscape no [15:45] most derivatives need to have a different CD because they're changing core "bits" [15:45] like the desktop environment (for Xubuntu and Kubuntu) [15:45] perhaps outside the Ubuntu bioshpere? [15:45] I think as we work on smoothing out some of the rough spots of having and addon CD it might get better [15:46] well, there are a number of projects that do "addon" stuff [15:46] but usually it's sort of unofficial and scripted [15:46] i.e. "run this shell script and it will install all the goodies" [15:46] we actually use Ubuntu's Add/Remove technology and have our own little "installer" hook [15:47] so that when you pop in an Edubuntu CD it pops up a dialog for you to start installing software [15:47] and we try to bundle it in such a way as to make it easy for people to install "bundles" of software [15:47] and we'll certainly be developing that as we go along [15:48] QUESTION: As it's unlikely developers will target only Linux, do Edubuntu developers recommend a particular development environment for cross platform educational tools? Java, Flash, .Net, Web/AJAX? [15:48] well, Ubuntu loves Python [15:48] and so do I [15:49] if you're going to either teach programming or are comfortable enough to use a "real" programming environment I'd certainly recommend Python [15:49] Flash is always tricky as we don't yet have a very stable/reliable free flash player [15:49] between Java, .Net/mono, and python I'd personally pick Python [15:50] for toolkits it's sort of up to you [15:51] I think Qt is particularly good in terms of having a nice looking, cross-platform, and easy to code GUI toolkit [15:51] so PyQT is a good option to look at [15:51] Ruby rocks for sure [15:52] but it doesn't quite have as much as Python in terms of libraries that would be relevant for education, IMO [15:52] if you look at things like pygame and even scipy/matplotlib for sciences [15:52] *but* bottom line [15:52] Ubuntu is a great place to code [15:53] just like most Linux distros [15:53] because we have C/C++, ruby, python, Java, .Net/mono, .... [15:53] and it's all free and open source software [15:53] so students can dig into their computers and learn about things [15:54] rather than just being stuck learning how to run menus on some proprietary app [15:54] I think that's one of the true goals of Edubuntu [15:55] to get students to not just use their computer but to really think about how they can effectively change their software to suit their needs [15:55] ok, we're getting close to the end here [15:55] are there any last questions? [15:55] thanks for the answers [15:56] Thank you [15:56] QUESTION: Why doesn't Shipit distribute Edubuntu? [15:56] I think that could be due to being an Addon CD [15:56] for us to completely ship the everything you need we'd have to ship 2 CDs [15:57] as postage/printing isn't free Canonical makes decisions on what it can afford [15:57] I'd like to get it back for sure in the future though [15:58] Thanks Laserjock, it was a very nice presentation....clap, clap, clap, clap [15:58] OK, in the last couple minutes here I'd like to give you some resource and give a bit about what you can do to help [15:58] Our website is http://www.edubuntu.org [15:58] we also use the ubuntu wiki so there's resources at https://wiki.ubuntu.com/Edubuntu [15:59] thanks a lot LaserJock [15:59] thanks LaserJock! [15:59] we have an IRC channel, #edubuntu, and 2 mailing lists, edubuntu-devel and edubuntu-users on lists.ubuntu.com [15:59] we also have a number of Launchpad teams that people can join [15:59] we need *all* kinds of contributors from all technical levels [16:00] artists, documentation writers, bug squashers, packagers, coders, support people, etc. [16:00] NOTE: we will be having a planning IRC meeting tomorrow at 18:00 UTC in #ubuntu-meeting [16:01] if you have *any* interest in Edubuntu please try to stop by, we'll make it worth your time [16:01] and with that I'm done :-) [16:01] HELLO MY FRIENDS! :-) [16:01] * sebner hugs dholbach =) [16:01] Who's here for the "Packaging 101" session? :-) [16:01] me [16:01] me [16:01] * lobo-ptr puts his fiiiiiiiinger up [16:01] hi :-) [16:01] +1 [16:01] me [16:01] yup [16:02] Clap, clap, clap! [16:02] and I guess the rest of the 237 people in here are just too shy to say "me me me!" :-) [16:02] Cheers LaserJock.. Good luck! [16:02] alright... let's get cracking [16:02] * stefanlsd hugs dholbach! [16:02] dholbach: Thay all agree [16:02] * dholbach hugs stefanlsd back :) [16:03] heh [16:03] * sebner feels ignored by dholbach :P [16:04] my name is Daniel Holbach, I've been member of the MOTU team for quite a while, have been involved in all kinds of teams but what I always got back to was: listening to new contributors, trying to find out what could make their lives easier and hear lots of enthusiasm in our ubuntu development community every day [16:04] * dholbach hugs sebner back :) [16:04] :) [16:04] as you can see (first lesson maybe): we hug a lot in the Ubuntu community :-) [16:04] so what are we going to do in the session? [16:05] we'll take a look at a simple package, identify all the key parts and I'll try to answer all the questions that come up [16:05] these key parts you will find in any package you might touch later on [16:05] there's one tool we're going to need, so please run [16:05] sudo apt-get install devscripts [16:05] and afterwards: [16:05] dget -xu http://daniel.holba.ch/motu/hello-debhelper_2.2-2.dsc [16:06] please let me know in #ubuntu-classroom-chat if you have any questions or run into trouble [16:06] m2a [16:07] what this does is: get the source package of hello-debhelper (eqivalent of 'apt-get source hello-debhelper' - I just wanted to make sure we all have the same source package we're looking at) [16:08] (you might need to run dget -x if you're on hardy) :) [16:08] if you look at your current working directory, you'll see three files and a directory [16:08] ... at least ... :) [16:09] hello-debhelper_2.2.orig.tar.gz is the unchanged upstream tarball that was released on the GNU FTP page [16:09] hello-debhelper_2.2-2.diff.gz is the compressed patch (set of changes) we need to apply to make the source package build in the debian/ubuntu world [16:10] hello-debhelper_2.2-2.dsc contains some metadata like md5sums, etc [16:10] the hello-debhelper-2.2 directory is the extracted tarball plus the applied packaging changes [16:10] QUESTION: When I install devscripts, apt-get install Exim. Why? [16:11] demas_: it's pulled in via some recommends - you can safely remove it (or install without recommends - can somebody help demas_?) [16:11] thanks [16:11] cd hello-debhelper-2.2 [16:11] demas_: I like to install ssmtp first instead. exim wont be pulled in then. [16:12] demas_: try with --no-install-recommends [16:12] if you check the contents of the directory you will see that it looks and feels like a regular source tarball you downloaded [16:12] with the exception of the debian/ directory [16:12] cd debian/ [16:13] this directory contains all the files that are needed to make the package build "our way" [16:13] what does that mean? [16:13] hello-debhelper is a simple project written in C, if you'd build it yourself, you'd probably run something like: ./configure --make-it-extra-fancy; make; sudo make install [16:14] if it was a python project, you'd probably run: python setup.py build; sudo python setup.py install or some such [16:14] etc. etc. [16:14] a lot of projects require different methods to make them build or install stuff to some directory [16:15] in the Debian / Ubuntu packaging world we just apply one build process, for all kinds of packages [16:15] ok, let's check out the contents one by one [16:15] changelog is what the name says: it describes all the changes that were made [16:16] but only the changes necessary for the packaging - it's not an upstream changelog [16:16] if you look at the top line you can see [16:17] (-) ; urgency= [16:17] upstream version is 2.2 [16:17] debian revision is -2 [16:17] that means 2 revisions of the upstream 2.2 have been uploaded to debian [16:17] it was not modified in Ubuntu at all [16:18] (you can ignore the urgency setting, we don't use it in Ubuntu) [16:18] sorry in the changelog, the first rows are like this, to me: [16:18] 2006-11-23 Karl Berry [16:18] * Version 2.2. [16:18] [16:18] * Makefile.am (po-check): add utility target (from coreutils). [16:18] catonano: we're in the debian/ directory [16:18] catonano: take a look at debian/changelog [16:18] oh yes, sorry [16:19] but you're right... ChangeLog is the upstream changelog (containing information from the software authors) [16:19] every changelog entry should contain useful information about what was changed [16:19] this is very important, especially in Ubuntu [16:20] we maintain all packages as a team - even if you don't mind figuring out what the hell you changed half a year ago, it's very nice if you colleagues and friends don't have to guess what [16:20] * did some changes to make it work again [16:20] means :) [16:20] also it contains the timestamp of the change and who changed it [16:21] we have a fancy tool in devscripts called dch that automatically adds templates for you, so you don't have to figure it out yourself :) [16:21] we can ignore the compat file, it's not so interesting (compatibility setting for debhelper, that was used for the packaging) [16:22] ahem...I'm sorry I have to ask a stupid question again :-( [16:22] catonano: no problem - would you mind asking in #ubuntu-classroom-chat the next time? :) [16:22] catonano: shoot [16:22] I can't find the debian folder. This is what I see: [16:22] adriano@adriano-laptop:~/debhelper/hello-2.2$ ls [16:22] ABOUT-NLS ChangeLog configure.ac INSTALL NEWS tests [16:22] aclocal.m4 ChangeLog.O contrib Makefile.am po THANKS [16:22] AUTHORS config.in COPYING Makefile.in README TODO [16:22] build-aux configure gnulib man src [16:22] adriano@adriano-laptop:~/debhelper/hello-2.2$ [16:23] catonano: go back to the directory with the .dsc .diff.gz and .orig.tar.gz files [16:23] I'm there [16:23] and run dpkg-source -x hello-debhelper_2.2-2.dsc [16:23] it's the magic command that dget -x(u) runs for you [16:24] alright... let's crack on [16:24] the next file is important and maybe a bit less obvious [16:24] thanks, I saw that [16:24] control contains information about the source package and the binary packages [16:24] so what's the difference? [16:25] the source package comprises of the .diff.gz .dsc and .orig.tar.gz files and is what we need to hack on packages, it contains source [16:25] the binary packages are the .deb files that my mother does not know about, but installs and updates regularly :) [16:25] QUESTION: Where can I find more information about dch? Do I need to launch this script or it is a part another script? [16:26] demas_: just run man dch - I'll give you a couple of links for more infos and tutorials later on [16:26] thanks [16:26] alright... control file [16:26] if you take a closer look at it, you will see that it's split into two stanzas [16:26] the first one is always about the source package [16:26] and the following ones (in our case luckily just one) are about the resulting binary packages [16:27] the source package definition contains: the name of the source (usually just what the upstream developers decided to call it), some section, some priority and a maintainer field [16:28] these should be pretty obvious (the debian policy explains which values are allowed for the priority and the section) [16:28] Standards-Version describes which version of the debian-policy the package complys with [16:28] in this case it's 3.7.2 [16:29] the next line is very interesting: it tells us which packages are required to build the package [16:29] this is nothing my mother has to install to get the all the goodness that hello-debhelper is, it's what we need to build the package [16:29] and also what the build machines in the data center need to build the package [16:30] so what happens when I upload a source package to the build machines? [16:30] first it will check the GPG signature to see if it was really me who uploaded it, it will check if it knows about me at all [16:30] then unpack the source package, then enter a minimal environment (that contains nothing but just a few build tools), then install the build-depends [16:31] this is to make sure that it builds in a clean environment [16:31] you will explicitly have to point out what's required :) [16:31] QUESTION: what is the Standards-Version used for? Won't lintian complain in different contexts, about the Standards-Version you use? === syslogd_ is now known as syslogd [16:32] cyphermox: if you're the package maintainer and you learn that the new debian policy requires something, you will make the necessary fixes and update the Standards-Version [16:32] for those of you who don't know: lintian is a tool that checks for all kinds of mistakes in packaging, it's seriously good stuff [16:33] cyphermox: lintian will always want you to use the newest debian-policy it knows about :) [16:33] alright! [16:33] but bumping the standards-version just for the sake of bumping it is unnecessary and you shouldn't do an upload of a package just for that :) [16:33] QUESTION: What would Depends look like if we had some real dependencies? [16:33] wolfger: I'll get to the depends in just a sec [16:33] let's get to the binary package section now [16:34] the name is pretty obvious: it's the name of the package that my mother might install [16:34] Architecture is interesting: in our case it's "Any" and will tell the build machines to build this on every architecture that's available in the data center [16:34] so i386, amd64, powerpc, hppa, lpia, sparc, etc [16:35] this is necessary if you have architecture dependent code [16:35] compiling C code on i386 and on amd64 will give you different results [16:35] if your package just needs a few python scripts or just ships some HTML files (something-doc package), you will set Architecture: all [16:36] which means: all architectures will use one and the same package (and the package gets only built on one build machine) [16:36] now we get to "Depends:" [16:36] this is the packages you need to install to make the package work [16:36] in our cases it's pretty funny: ${shlibs:Depends} [16:37] this doesn't look like a package name, right you are :) [16:37] it's a substitution variable [16:38] ${shlibs:Depends} will at the end of the build be replaced with all the names of packages that contain libraries that the binary files in hello-debhelper are linked against [16:38] I hope that was not too cryptic :) [16:39] so if /usr/bin/hello in the resulting hello-debhelper package is linked against /lib/libc.so.6 the package will automagically depends on libc6 [16:39] dholbach: QUESTION: "Architecture: all" Vs. "Architecture: any" difference ? [16:40] bhk_f: I explained it above, in short: "any" => build on every release architecture because of architecture dependant resulting code (C, C++, etc, etc), "all": all architectures use the same package, architecture indepedent [16:40] QUESTION: If I modify someone elses package and build new sources (and binaries), should I use Original-Maintainer or XSBC-Original-Maintainer? What's XSBC? [16:41] poef: that's an Ubuntu speciality. our friends at Debian asked us to change the maintainer fields whenever we do changes so they don't get mails from our users about bugs, etc [16:41] https://wiki.ubuntu.com/DebianMaintainerField has more info about that and the update-maintainer tool (ubuntu-dev-tools package) is useful for that [16:42]