=== pi-rho|away is now known as pi-rho [03:15] is anyone available? [03:19] * hyperair is semi-available [03:19] oh he disapeared. [03:39] I'm married and have a kid... definitely not available. [03:40] ok [07:40] Hello there I am haveig trouble when building it is my control file it is here http://paste.ubuntu.com/981264/ just wondering what I am doing wrong thanks for your time. Oh and the email address are in the control file I just took out for the paste. error is here http://paste.ubuntu.com/981275/ [07:41] thanks again [07:43] bobweaver: add a 2nd whitespace at the start of lines 2-7 [07:43] thanks [07:44] I always get that mixed up if it is one or two spaces [07:44] thanks again [07:48] <_ruben> that file could use some spellchecking and whitespace fixing :) [07:59] I am on it thanks _ruben === almaisan` is now known as al-maisan === chris_ is now known as Guest93312 [09:04] Can someone grant nomination on this bug? https://bugs.launchpad.net/ubuntu/+source/sphinx/+bug/997891 [09:04] Launchpad bug 997891 in sphinx (Ubuntu) "sometimes cannot build pdfs for de, sl, pt, es, nl, pl, or it locales" [Undecided,New] [09:05] geser: you around? :) [09:11] nigelb: sort of, why? [09:11] geser: I was wondering if you had the magical powers to ack the nomination on that bug. [09:11] should have as a MOTU [09:14] geser: Can you? :) [09:14] nigelb: sorry, I can't. It's either because it's in main or some other team membership is needed [09:14] AH. [09:15] I wonder if it needs release team. [09:17] https://launchpad.net/sphinx/trunk suggests it wants stub [10:12] nigelb, elky: Done. [10:13] iulian, woot thanks === al-maisan is now known as almaisan-away === vibhav is now known as Guest3189 === almaisan-away is now known as al-maisan === apachelogger_ is now known as apachelogger === yofel_ is now known as yofel === al-maisan is now known as almaisan-away [13:15] hm === vibhav is now known as Guest82292 === vibhav is now known as Guest34553 === Guest34553 is now known as vibhav === EvilResistance is now known as Resistance [15:56] hmm, where's the motu crowd, I'd thought you'd be in tha archive-reorg room by now :) [15:58] (ah here you are) [15:59] i got really good at timing how long the drive would take [15:59] been inching my alarm later and later all week [15:59] * ajmitch made it in time... [16:00] starting to feel the effects of too many sleepless nights though :) [16:24] * ScottK thinks being at a local UDS would be rough. [16:24] not getting a room at the hotel was a mistake, i think :) [16:25] broder: at least you get to sleep in your own bed [16:25] yes, although i don't get to sleep in it for nearly long enough [16:44] can someone help me in the package guide? [16:51] Laney: ping (one sec...) [16:52] if you're testing manual backporting, let me give you my patch to include an lp closer [16:52] (even though it will be ingored by lp, i feel moderately strongly hat we should have it there to capture history) [16:52] push it to udt? [16:53] also it looks like it doesn't pass -v [16:54] will land momentarily [16:54] i think that's mostly deliberate - we don't want to, e.g., close sru tasks [16:54] would it? [16:54] well, if there was a closer in the history between current archive version and backported version [16:55] and an sru task on that bug [16:56] EpikVision: What do you want help with? [16:56] EpikVision: no need to ask to ask. Please just ask your question [16:56] hahah [16:56] ok [16:56] Laney: pushed [16:56] http://developer.ubuntu.com/packaging/html/fixing-a-bug.html [16:57] I'm going through "Work on a fix" [16:57] Laney: hmm. actually, the real reason to include the lp closer is for the sake of AA review [16:57] vibhav: I've done all the steps to this point [16:57] EpikVision: What are you working on? [16:57] Fixing a bug. [16:58] from the packaging guide [16:58] I mean, which package [16:59] tomboy [16:59] EpikVision: Whcih bug? [17:01] vibhav: I don't think the guide goes through any bug. [17:01] but i was just following the steps, up to the section "Work on a fix" [17:01] I don't get why $ patch -p1 < ../bugfix.patch [17:01] is giving me an error. [17:02] EpikVision: You need to fing a bug to work on [17:02] alright then. [17:02] vibhav: I'm totally new to the scene. [17:02] and the package guide is confusing me. [17:02] IF no bug, no fix = NO changes in source [17:02] alright [17:02] EpikVision: Which part? [17:04] vibhav: "Work on a fix" [17:06] up to the code ($ edit-patch 99-new-patch), everything went fine [17:06] but I can't get past $ patch -p1 < ../bugfix.patch [17:07] vibhav: when I put that command, I keep getting [17:07] bash: ../bugfix.patch: No such file or directory [17:08] I cd-ed to tomboy/tomboy.dev [17:09] EpikVision: bugfix.patch needs to be the name of the patch [17:09] you made to fix the bug [17:09] ok [17:10] so how do I work on the fix, if it were necessary? [17:10] for this tutorial specifically? [17:10] * EpikVision scratches his head [17:12] EpikVision: what are you fixing in tomboy? [17:12] vibhav: as mentioned earlier, I was just following the package guide [17:13] ohh [17:13] hold on. [17:14] tumbleweed: I was just following the package guide [17:15] EpikVision: right, but that's the point where you need to fix something [17:15] tumbleweed: really? [17:15] I mean, edit some source code [17:15] well, sure, that's the point of that guide, right? :) [17:15] ok, do you any bitesized bug for tomboy that I should try? [17:15] you can find a bunch on harvest.ubuntu.com [17:17] tumbleweed: i'm at harvest, but I'm having trouble filtering the list to tomboy. [17:17] EpikVision: http://harvest.ubuntu.com/opportunities/package/tomboy/ [17:18] alright. [17:18] https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/386893 [17:18] Launchpad bug 386893 in tomboy (Ubuntu) "Searching within a notebook should inform the user that no results were found within that notebook" [Wishlist,In progress] [17:18] wait a min [17:18] nvm this one. [17:19] tumbleweed: is it courtesy to tackle a bug with no current assignee? [17:21] that person has been assigned for over a year [17:21] whoa [17:21] let's assume that they aren't going to do it [17:21] hahaha [17:22] ok [17:23] tumbleweed: so now that I'm at "Work on a fix" at this point [17:23] how can I delve into the source code? [17:24] I found the problem, figured out that the package could be looked through, and I branched the source package. [17:24] now how can I start with a fix? [17:25] EpikVision: there's a patch in the linked gnome bug that you should try [17:26] note that the patch author mentions it wasn't perfect yet [17:27] should, I should replace gnome-bug with myself? [17:27] what is 'gnome-bug' [17:28] the assignee [17:28] were you referring to the linked page I sent you earlier? [17:28] no. that's a linked bug. click on it [17:28] ohhh [17:29] ok, i clicked it. [17:30] what should I do? [17:30] * EpikVision feels slightly bewildered. [17:32] download the most recent patch and see if it applies? [17:33] ok, according to the package guide, what step am I at? [17:34] http://developer.ubuntu.com/packaging/html/fixing-a-bug.html [17:34] you are going to use patch patch, not edit patch [17:34] alright. [17:34] err patch, not edit-patch [17:35] it gives me (err: command not found.) [17:36] then install it :) [17:37] so, I should patch patch tomboy? [17:37] I cded to /tomboy/tomboy.dev [17:37] "patch patch" was a typo of mine [17:38] what is the syntax i need to patch tomboy? [17:38] I'm guessing (err patch ) [17:39] no, the packaging guide shows you the right syntax [17:39] where ../bugfix.patch is the name of the patch [17:39] quilt import should also work [17:40] sorry, yes that,s the best approach [17:40] then: quilt push [17:40] from within a quilt shell (which I assume edit-patch uses)? [17:40] I wrote (quilt import ../bugfix.patch) [17:41] but it gives me (Patch ../bugfix.patch does not exist.) [17:41] :( [17:43] * micahg is curious what manual backport testing is [17:44] ../bugfix.patch doesn't exist in my folder... [17:44] you need to download it from the bug first [17:44] and secondly: [17:45] <tumbleweed> [05/11/12 12:39:22] where ../bugfix.patch is the name of the patch [17:45] it might not be *named* bugname.patch [17:45] so you'll need to know (1) where you downloaded the patch to, and (2) what that patch's name is [17:45] micahg: it means us uploading it instead of archive admins using the script [17:45] EpikVision: after you download it from the bug [17:46] https://bugzilla.gnome.org/show_bug.cgi?id=588730 [17:46] Gnome bug 588730 in General "Searching within a notebook should inform the user that no results were found within that notebook" [Enhancement,New] [17:47] Resistance: I'm trying to tackle this bug, but I can't work on a fix. [17:47] How do I download it from here? [17:47] * Resistance looks [17:48] is it a good idea to add a patch that is not upstream? [17:48] * Resistance seems to be missing backlogs [17:48] * EpikVision is a new at this. [17:48] what's the package the bug is in? [17:48] tomboy [17:49] yup. I got the source code from a branch. [17:49] * Resistance reads the bug, and reads the equivalent LP bug [17:49] I'm following the outline provided by the Package guide [17:49] If I succeed, this would be the first bug I ever fixed. [17:51] EpikVision: did you check the upstream bug to confirm that the patch(es) that fix LP Bug 386893 (linked to the upstream bug) are *committed* upstream, and not just proposed? [17:51] Launchpad bug 386893 in tomboy (Ubuntu) "Searching within a notebook should inform the user that no results were found within that notebook" [Wishlist,In progress] https://launchpad.net/bugs/386893 [17:51] upstream, there's two bugs on there [17:51] unfortunatly I don't think this particular bug should be fixed in ubuntu [17:51] s/bugs/patches/ [17:52] jtaylor: i'm in agreement, it needs to be fixed upstream [17:52] * Resistance is on BugSquad, and is giving his opinion on this one [17:52] perhaps the fix(es) will show up in Quantal at some point? [17:53] after fixed upstream [17:53] ok then. [17:53] Resistance: what do you mean by "checking"> [17:54] EpikVision: i.e. go to the upstream bug, check both of the submitted patches and figure out which one is needed to fix the issue listed on that bug [17:54] there's two patches submitted to that upstream bug [17:54] one which was committed already and the other which is proposed [17:54] oh ok [17:55] having said this, i believe it needs upstream fixing. [17:55] jtaylor: any objection to me voicing my opinion on that on this bug? [17:55] (the LP bug) [17:56] Hi all! [17:56] Resistance: what's the link to go to the upstream bug? [17:57] its linked to the LP bug. [17:57] https://bugzilla.gnome.org/show_bug.cgi?id=588730 [17:57] Gnome bug 588730 in General "Searching within a notebook should inform the user that no results were found within that notebook" [Enhancement,New] [17:58] should I choose a committed one or a proposed one? [17:58] <jtaylor> unfortunatly I don't think this particular bug should be fixed in ubuntu [17:58] rather it needs to be fixed upstream [17:58] which means that it needs to be fixed in the program itself and applied for whatever version that gets included into [17:59] ah [17:59] and while it may be nice to really have in Ubuntu, it should ideally be fixed upstream [17:59] what's the downstream then? [17:59] i'm going to concur with jtaylor on this, it doesn't need fixing in ubuntu [17:59] alright. [17:59] perhaps, I'll find another one. [17:59] since I'm new, i need to tackle a bite-sized bug. [17:59] there's a list of bite-sized ones, isnt there? [18:00] * Resistance could have SWORN there was one [18:00] http://harvest.ubuntu.com/ [18:01] jtaylor: any objection to me stating your opinion (which is also my opinion) that this does not need fixing in ubuntu (but rather upstream) on the corresponding LP bug? [18:01] no [18:01] * EpikVision hopes to fix at least one bug today. [18:02] * EpikVision thanks Resistance and jtaylor for helping. [18:02] https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001 [18:02] Launchpad bug 395001 in pidgin (Ubuntu) "apt-get install of finch requires X11 (deps wrong)" [Medium,Triaged] [18:02] Is this a good one? [18:03] judging from the amount of comments probably not [18:04] also that again looks like an upstream issue [18:04] jtaylor: can you poke the LP people and see whether LP is having a comms issue with gnome-bugs' upstream tracker? [18:04] https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001 [18:04] Launchpad bug 395001 in pidgin (Ubuntu) "apt-get install of finch requires X11 (deps wrong)" [Medium,Triaged] [18:04] LP suggests that it is having a comms error [18:04] Resistance: maybe this is better. [18:05] EpikVision: FYI: jtaylor's higher up in the chain than I am, i'm pretty comfortable immediately trusting his assessment of bugs [18:05] https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/395001 [18:05] EpikVision: posting three times gets annoying [18:05] and in some cases is floody [18:05] https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/828359 [18:05] Launchpad bug 828359 in lightdm (Ubuntu) "Help strings for session related command line options not very informative" [Low,Incomplete] [18:05] I meant to get this one. I'm orry [18:06] might i suggest, EpikVision, that you not assign yourself to bugs willy-nilly? [18:06] just a small suggestion, is all [18:06] willy-nilly? [18:06] alright. [18:06] i'm noticing on 395001 you assigned yourself then removed yourself from assignee after jtaylor pointed out its an upstream bug [18:06] * Resistance looks at 828359 [18:06] sorry about that. [18:07] this one's marked as incomplete [18:07] I think I would like to be assigned a decent bug to start with. [18:07] I have poor judgment and choice. [18:08] :( [18:08] * Resistance quickly runs off for a cup of coffee [18:10] * EpikVision stares at the computer screen. [18:11] jtaylor: tumbleweed: sorry for interjecting and stealing your thunder, there [18:12] broder: can we have it API close the bug with -c à la syncpackage? [18:12] Resistance: no problem I ran off to the canonical shop in UDS between sessions :) [18:13] :P [18:13] tumbleweed: got a bunch of goodies? [18:13] * Laney need to get something [18:13] got a voucher [18:13] ajmitch: yar, a new backpack and a hoodie [18:13] * ajmitch has a hoodie & fleece jacket [18:13] plus some special orders for people in ZA :) [18:14] * Resistance should make an effort to attend UDS in the future. [18:15] * EpikVision had much fun at UDS. [18:15] the past two UDS, i've been showing up remotely, although i did a lot of lurking this one [18:17] I love that we have remote participation, but it's really hard to actually participate when you aren't there in person [18:18] mhm [18:18] * tumbleweed is glad to be here [18:18] i should point out, though, that when people actually talk loudly enough to be heard over the live audio streams, it makes life easier [18:18] * Resistance stopped by the MOTU BoF session yesterday [18:18] (remotely of course) [18:18] some people seem incapable of speaking up :) [18:19] mhmn [18:19] having said this, i could have said "Turn up the volume", but that crinkling noise was already too loud xD [18:19] (there was crinkling somewhere near the mic) [18:19] * ajmitch blames highvoltage [18:21] https://bugs.launchpad.net/unity-2d/+bug/813041 [18:21] Launchpad bug 813041 in unity-2d "[launcher] Drag And Drop should only be activated with the left mouse button." [Low,Triaged] [18:21] guys, I think this one is ok. [18:22] the most useful thing you can do there is to provide a patch [18:22] mhm [18:22] providing a patch? [18:22] aw, man, how is it i can just down a cup of coffee without realizing it... [18:22] * Resistance goes off to get another cup [18:22] haha [18:22] * EpikVision laughs [18:23] I should use http://developer.ubuntu.com/packaging/html/udd-patchsys.html [18:28] that bug'd need a patch at the most, that's the best you can do, its triaged upstream (with the Unity project) [18:28] tumbleweed: [18:28] tumbleweed: since you are UDS, can you lend a prospective developer a hand? [18:28] *are at [18:28] EpikVision: UDS is a busy time for devs :P [18:28] i think you'll need some patience ;P [18:28] perhaps so... [18:28] * Resistance is intentionally not bugging the MOTUs much during UDS, even though their attention is necessary for a sync request from Debian for Quantal [18:29] EpikVision: what are you needing a hand with? [18:29] determining what is a proper bug to fix. [18:29] how to recognize a easy bug from a hard bug [18:29] etc. [18:29] lol [18:29] bitesize tag is an esay way to find an easy bug [18:30] some bitesize ones aren't meant to be fixed, I noticed during this discussion. [18:30] or a starter can't try them. [18:30] probably because they're already merged/committed upstream [18:30] right, so for each bug we make a decision on where we want to fix it [18:31] for the first one you did, the one i came in on, that was already filed upstream and merged upstream with a fix [18:31] so that didn't need fixing in Ubuntu [18:31] ahh ok [18:31] i didnt look at that second one very well [18:31] * Resistance was too busy focusing on the need for coffee [18:31] oh my [18:31] but if it's serious enough, we can apply the patch in Ubuntu rather than wait for the new version from the upstream that fixes the bug [18:31] mhm [18:32] i c. [18:32] starters should try simple bugs then. [18:32] like typos [18:32] yep. [18:32] well, even then, minor fixes arent always accepted [18:33] btw, does anyone know alejandro's irc name? [18:33] user-visible typos are a great thing to start with [18:33] i agree [18:33] alrighty then, where and how can I find a bunch of them? [18:34] search for spelling / typo on bugs.launchpad.net/ubuntu ? [18:34] the easy-to-fix stuff is good, including the bitesize bug i took up / filed against php5 to use unix sockets instead of TCP sockets, which was accepted upstream and exists in 5.4 in some debian repo :P [18:34] that was a very easy to fix one ;P [18:34] yeah, what tumbleweed suggested would work [18:34] (default setup, on that php5 bug/wishlist request, btw ;P) [18:34] speaking of which... [18:35] tumbleweed: who do i need to prod about server packages, such as php5 and whether they'll update to whatever the latest is in debian for Quantal? [18:35] Resistance: can you give an overview of the way of the developer? [18:35] the ubuntu server team? [18:35] i *should* be honest and point out that my duties with bugs primarily are deciding what's triage-worthy, and then filing it upstream as necessary [18:35] nowadays i dont usually patch/fix bugs [18:35] unless they're in the nginx project's PPAs, because i'm the manager of that ppa's lucid packages... :P [18:36] wow, that's awesome. [18:36] OW! hot coffee! [18:36] * highvoltage kind of stumbles in [18:36] but to be honest, most bugs for that are fixed upstream, or have patches upstream that get included in the package [18:37] (eek I've missed a lot) [18:37] (in regards to nginx's ppas which are more up to date than the repos) [18:37] highvoltage: meh, that's what scrollbacks and ubuntu logs are for :P [18:37] Resistance: the last person who touched it is responsible for merging it from Debian [18:38] tumbleweed: ah, i see. [18:38] how do i determine who was responsible for merging from debian? [18:38] changelog entries? [18:38] Laney: eh...i'm a bit iffy on that one - it has the same problem as syncpackage but worse since the upload hits unapproved [18:38] yes [18:38] merges.ubuntu.com (which is currently a little out of date) [18:38] I would just leave it open though [18:38] I think most backporters are capable of doing that :-) [18:39] huh? [18:39] what? [18:39] just don't press yes until it gets accepted [18:39] ....that could take days, though [18:40] it could [18:40] the one i just did took 12 minutes [18:40] that's because cjwatson and i were sitting next to each other and testing manual backporting [18:40] you are always free to quit and not do it [18:40] fine. [18:40] i'm fine with adding the option [18:43] bah. connection fail. in any case, colin and i came up with a list of changes we want to see in backportpackage before we start using it for heavy-duty backporting [18:43] i will add bug closing to that list [18:44] ty [18:45] in case you're curious, the changes are: switching from ~precise1 to ~ubuntu12.04.1 and passing -v because (a) that's what was always done and (b) it won't close bugs [18:45] (the -backports pocket is special cased to never be able to close bugs) [18:46] interesting [18:46] broder: mind if i pick your brain about requesting a package sync? [18:47] Resistance: i'm about to go afk for a while. asking the channel would probably be better [18:47] if i use requestsync to request a sync from Debian unstable to Quantal, do i put quantal or something else for the target release? [18:47] simple question, just a question of what to put in for target release [18:47] bug 997201 is weird [18:47] Launchpad bug 997201 in qwt (Ubuntu) "libqwt-dev (6.0.0-1ubuntu1) in update loop" [Undecided,New] https://launchpad.net/bugs/997201 [18:47] how can that happen? [18:48] Resistance: yes, quantal is correct [18:48] just wanted to make sure, thanks. [18:48] though you shouldn't have to specify anything - it should default to the current devel release [18:50] broder: reminder that i'm on natty still (waiting for a replacement drive to come in), i'd rather not chance it ;P [18:50] requestsync will ask you to confirm what it's doing before it does anything [18:51] yeah, well i'm in the habit of putting information into the fields just to make sure it has the right info [18:51] * Resistance made the mistake of not doing that before when packaging things, and ran into all sorts of crap from pbuilder when it locally-build the package he was building [18:51] locallybuilt* [18:51] bah, stupid keyboard [18:52] https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/998195 <-- in case someone can take a look at this [18:52] Launchpad bug 998195 in boinc (Ubuntu) "Sync boinc 7.0.27+dfsg-3 (universe) from Debian unstable (main)" [Undecided,New] [18:52] (it builds in Quantal, i tested locally, and in a Quantal VM) [18:53] bah, more firefox updates >.> [19:05] How brave would it be to upgrade from maverick directly to precise? [19:07] Huhm, I guess I should redirect myself to #ubuntu :) [19:07] probably it should display an "I uploaded this, please wait for it to be approved" message too [19:07] syncpackage could also do this during freezes ^o) [19:08] or we should have a separate tool that looks at recent syncs / backports uploaded by you that have open bugs nad closes them [19:09] i'm thinking of Fix Committed which the same tool could/should do [19:09] for Fix Released, maybe closemybugsd would be nicetm [19:09] ™ [19:10] well, maybe not backportpackage unless that is driving dput for you [19:10] wow, 500mb ram and 380mb swap. this is going to be fun :) [19:10] huh, what machine is this?! [19:11] two cores atom 1.6 ghz, hmmm [19:11] an aspire one netbook [19:12] I think it was one which had ubuntu preintalled back then [19:12] the display is broken, and there are some keys missing (I am typing on the rubber thingies mostly ;) [19:13] It's the best I could get as a quick replacement for my hp laptop that doesn't want to charge anymore [19:13] sounds like an enjoyable piece of hardware :-) [19:13] Didn't know you are also into masochism like me, Laney ;) [19:14] heh [19:15] Reminds me of the days when the m key on my compaq notebook b0rked. [19:15] I tweaked the keyboard bindings and even managed to get used to have the m above the tab key. [19:18] sfvbm right alt menu and right windows key, also right shift key, those are the keys that are missing the regular plastic above the rubber thingy [19:19] also, for additional fun, they keyboard layout is some qemrtz [19:19] anyone got a clue which language uses qemrtz? [19:19] italian potentially? [19:30] if i've filed a sync request for a bug on LP in which the package that is being synced to Quantal closes that bug, should I set the bug that the sync request will close to "In Progress" (and assign the bug to someone involved with getting that sync request completed)? [19:31] assuming the bug has "confirmed" as its current status [19:33] Resistance: mention all the bugs that this will close in the sync request [19:33] (assuming they aren't closed in the changelog) [19:33] they are closed in the changelog [19:34] perfect [19:34] but the LP bug that's being closed, does it need "In Progress" set to its status with the sync request having been filed? [19:35] you can, if you are worried that someone else is going to look at them [19:36] now i assume i just wait for someone on the sponsors team to see the sync request? [19:36] yes [19:36] * Resistance has all the patience in the world, then, on that one :) === ara is now known as Guest39400 === bregma is now known as bregma|afk === bregma|afk is now known as bregma === ara is now known as Guest22943 [21:39] hello there I am trying to find information about " Traditional Packaging " is it like make upstream make make or autotolls/whatever then start the debian package with dh_make -e -c < license -f foo.tar then make all your debian/* then make tar ball foo.orig.tar.gz then build package with fakeroot and dpkg-buildpackage -F ? [21:40] This is why I ask http://developer.ubuntu.com/packaging/html/traditional-packaging.html [21:49] bobweaver: In very general terms yes. [21:50] That packaging guide is using "traditional packaging" to mean packaging without using UDD. [21:50] * Laney tries to say "packaging" some more [21:58] * ScottK thinks of it more as "way that works reliably" than "traditional". [21:59] * Laney looks forward to reviewing that patch to the guide [21:59] ahh cool so like a hardened package ? or like very sound package [22:00] quilt is verry confusing for new comer like me and that guide if that helps at all [22:00] Quilt is confusing to a newcomer period. [22:00] :) [22:01] I don't recall exactly why, but I had a lot of trouble with it. [22:01] Now I've gotten past it, but it's definitely a barrier to entry. [22:05] thanks ScottK [22:06] there was also something in the ,manual about RCD or something like that and I do not know what that is either I am looking for it now. [22:06] I can not belive that I deleted my Quesytions file then again it was 4 am [22:11] ok so I found it it is under the section Limitations of UDD¶What is RCS on top of RCS. ? [22:12] bobweaver: RCS = revision control system [22:12] both bzr and quilt are RCSs [22:13] ahh thanks that should be in maunal ? I should file bug ? [22:13] or shouldd I just add that and push my branch ? [22:14]