[01:25] would a MOTU be so kind as to review my package? Thanks in advance! http://revu.ubuntuwire.com/details.py?package=lmalinux [02:11] How do you convert a patch, my.patch, into a format dpatch will understand? [02:29] jsmidt: Use dpatch-edit-patch. See it's man page. [02:29] it's/its [02:33] ScottK, thanks [03:19] txwikinger: Would you please update ichthux-meta to drop arts. We're trying to get it removed from Jaunty: https://wiki.kubuntu.org/RemoveArts [03:19] Please mark on the wiki page when you've done it. [03:19] ScottK: ok.. will do [03:20] Thanks [03:20] np [04:10] I just started trying to package a new package today for Universe - is Jaunty still worth targeting? Is it possible to add new packages to Jaunty? [04:11] chrismurf: New packages can still be added. But Feature Freeze is coming up soon. So if you want to get it into Jaunty, you might want to get it finished and uploaded to REVU asap [04:13] nhandler, thank you -- first package, so I will do what I can -- just wondering if I should try and target Jaunty or go +1 [04:15] chrismurf: You can try and target Jaunty. Worst case scenario is that you have to change one word in your changelog for Jaunty+1 [04:15] Fair enough :-) [04:16] chrismurf: You could also upload it to your PPA until the Jaunty+1 repositories open up [04:16] done for intrepid ;-) === bluesmoke is now known as Amaranth [05:09] Can somebody recommend an MIT licensed package to use as a reference for 'debian/copyright'? All examples seem to be GPL/GPL. [05:09] better yet, a way to use apt-cache or otherwise to find such a package :-) [05:53] Anybody up for reviewing a first package? It's a python library for doing geographical projections, pyproj. http://revu.ubuntuwire.com/p/pyproj [06:33] good morning [06:34] good morning [06:35] hi chrismurf, hi iulian [06:35] Morning dholbach. [06:35] Hiya dholbach ! [06:35] hi fabrice_sp [06:35] Morning iulian [06:35] Hey fabrice_sp. [06:36] how's life, guys? :) [06:38] dholbach, as usual (even if a bit colder than usual, with snow some days ago in Madrid :-) ) [06:38] life's good - just got my first package into REVU, getting towards bedtime, and had a pleasant weekend :-) [06:38] chrismurf: nice [06:39] fabrice_sp: it's snowing here too right now [06:39] dholbach, but it's more normal, in your case, isn't it? [06:39] :-) [06:39] I guess so :) [06:40] How are you doing? [06:44] good good, thanks :) [06:45] If any MOTU's have an interest in reviewing said package, it'd be much appreciated : http://revu.ubuntuwire.com/p/pyproj (it's a python library for doing geographical / map projections) [07:04] chrismurf, please don't ask each hour for a review [07:04] fabrice_sp, I'm off to bed soon, figured I'd try one more time before crashing [07:04] apologies if I'm over exuberant, I promise not to saturate motu with "pay attention to ME" :-) [07:05] thanks for the friendly reminder [07:05] take care all, thanks for the guidance today [07:05] chrismurf, the more you request attention, the less you will have :-) [07:06] I'll try to have a look at your package this evening [07:06] OK - not what the tutorial left me thinking - I'll bear that in mind [07:06] (even if I'm not a MOTU) [07:06] the tutorial suggested it was beneficial to ask in MOTU [07:07] is it better to just leave it sitting in REVU? [07:07] let people get to it when they do? [07:07] chrismurf, yes, but no more than 2 times a day, I think [07:07] okay, well I've used my two ;-) [07:07] lol [07:07] thanks - take care [07:07] bye [08:23] good morning [08:25] hi dholbach [08:46] RainCT: hrm, why are you writing 'acked' in your own sync requests? :-) [08:56] slangasek: For karma? ;) [08:57] heh === quadrispro1 is now known as quadrispr0 === quadrispr0 is now known as quadrispro1 === quadrispro1 is now known as quadrispro [09:30] Laney: does the new openarena need the new -data? [09:47] dholbach: have you read my messages? :) [09:47] quadrispro: yes and I replied :) [09:49] dholbach: doh, my connection was lost :( [09:49] just replied again [09:50] dholbach: thank you very much ;) [09:50] anytime :) [10:27] Does anyone know when debuild stopped ignoring .bzr directories? [10:28] did you pass -i to it? [10:32] soren: i am doing -i.bzr now, but it always used to work without it. so was just wondering when it changed [10:32] stefanlsd: How exactly were you invoking debuild before? [10:33] keyword being: "exactly" [10:33] soren: debuild -S -sa [10:33] In that case, I'm clueless. [10:33] :) [10:34] soren: hehe. yeah. wierd. cause i've always made bzr trees of packages im working with, it always used to ignore the .bzr stuff. now it fails. shrug === thekorn_ is now known as thekorn [11:05] dholbach: I don't think it needs it, but there is a sync coming up for that anyway [11:05] actually I can't request it until tonight, so it'd be good if you could [11:05] (it works fine) === quadrispro1 is now known as quadrispro [11:25] Hi all, if there's a package that I have in Debian but it's way old because Debian has been in freeze for a while, is it too late to ask for universe to be updated with a more recent release? [11:27] lamothe: Not at all, you have until the 29th. [11:27] lamothe: what is it [11:27] mok0: jpds: me-tv. [11:27] * mok0 looks [11:28] I've been kinda keeping experimental up to date ... but I'm not a DD ... and my uploader is AWOL. [11:28] wow.......this room seems bigger than I remember [11:28] lamothe: it's in experimental? [11:29] mok0: Debian experimental. [11:29] rocco: this is not a room, it's achannel ;-) [11:29] mok0: Did I say the wrong thing? [11:29] lamothe: no === rocco is now known as cbx33 [11:29] ahh that's better [11:30] maybe it's not a room in the physical sense [11:30] lamothe: why do you think that? [11:31] mok0: Oh, no reason, I think that you couldn't find it in experimental. I misinterpreted your question. [11:31] *though [11:32] lamothe: he, I found it. OK, you need to file a sync-request bug on LP, see here: [11:32] You wouldn't guess but English is my first language. ;) [11:32] https://wiki.ubuntu.com/SyncRequestProcess [11:32] mok0: Ta! [11:32] lamothe: Ah, well that explains it :-) [11:33] lamothe: plz check to see that it builds on Jaunty also [11:33] lamothe: because we are well past DIF [11:34] mok0: Sure, without a doubt I will do that. I think that it's always a good idea to build it on the target system. [11:34] lamothe: great! Thanks! [11:34] But should I then use Utnubu ... is it still around. [11:34] * lamothe looks [11:35] lamothe: eeerr? [11:35] http://wiki.debian.org/Utnubu [11:35] lamothe: your app is already in Debian [11:36] mok0: I thought that Utnubu synced changes back into Debian. [11:36] ScottK: could you explain what you mean by "tame ezsetup"? [11:36] lamothe: but are there changes? I thought you just want to bring the version from Debian experimental to jaunty [11:37] mok0: Oh .. yeah, I didn't think of that [11:37] I just thought that I could build one for Jaunty. [11:37] mok0: Either way, I'm easy. [11:38] lamothe: I already checked to see that there are no Ubuntu-specific changes in me-tv, so what we need to do is a straight sync. Archive admins have scripts for that [11:38] james_w: Sure. ezsetup will try and download updates from the internet if they are missing. In my case I didn't have python-setuptools installed on my system where I was building it, so it tried to install it from cheeseshop. [11:38] I'm mostly on Ubuntu nowadays and sometimes I lose my Debian uploader. [11:39] james_w: Generally we patch packages to not do that. [11:39] ScottK: so what not add python-setuptools as a Build-Depends? [11:39] No, just disable the ezsetup part. [11:39] lamothe: theres a cli-tool called requestsync if your'e into that sort of thing [11:40] james_w: You'll see I just commented out two lines in setup.py. [11:40] lamothe: if you invoke that with the --lp switch it talks directly to LP [11:40] ScottK: yeah, I can see it, but ezsetup is about more than just downloading dependencies [11:40] mok0: Wow that's pretty neat. [11:40] lamothe: yep :-) [11:41] james_w: If it's trying to download updated packages from outside the repositories, then it's wrong. [11:42] ScottK: I agree. [11:42] lamothe: I think the default is to sync from "unstable", you have to thrown another switch to say "experimental" [11:42] I'm not suggesting that we let it [11:42] * lamothe is foofling [11:42] That's what I was trying to prevent, if there's a better way, I'm quite OK with it. [11:42] lamothe: Add: -d experimental [11:42] There you go [11:43] jpds, the online manpage :-P [11:43] jpds: Thanks ... I'm just trying to find the actual script ... not in repos? [11:43] lamothe: It's in the ubuntu-dev-tools package [11:43] anyone try the latest alternate cd with hd-image? [11:43] mok0: Morning to you too :-p [11:43] jpds: heh [11:44] jpds: Thanks again [11:44] I am looking at a blue sky for the first time in weeks [11:44] Makes me all cheery [11:45] mok0: Thanks for your help also. [11:46] lamothe: I don't think Utnubu is active [11:46] lamothe: np [11:47] Ok, off to find a uploader [11:51] hello. I'm trying to merge wordpress_2.7-1 from debian experimental with our 2.5.1-8ubuntu1... I'm learning yet (first merge tentative). I'm trying to view the diffs with Meld. but before that I have to apply the debian's diff first.. can any one please help me on that ? [11:54] Rafik_: Do you mean 11ubuntu1? [11:54] You should just look at the diff that was applied between -11 and -11ubuntu1 and then see which of those changes we still need [11:54] (also, thanks for letting me know that this was uploaded. /me runs off to update his blog) [11:55] Laney> apt-get source downloaded from intrepid-updates/universe wordpress 2.5.1-8ubuntu1.1 [11:56] Laney> btw, thanks for your blog post, I was reading it :) [12:01] hi there :) someone to revu this please ? http://revu.ubuntuwire.com/p/skrooge [12:08] * mok0 takes a look [12:10] Tonio_: The shared object libraries are not meant for development work, right? In that case, we might prefer them to go into /usr/lib/scrooge [12:11] Tonio_: I can't yet see if it's possible to make that happen [12:11] mok0: I can ping upstream about the issue, indeed, and will make it [12:11] mok0: but I'm not ready to maintain such a patch, to be honnest :) [12:12] Tonio_: heh, well just a thought [12:13] mok0: and btw, it should go /usr/lib/kde4/ [12:13] mok0: but you're right, upstream has to be notified on that point :) [12:14] Tonio_: yes I guess you're right [12:41] mok0: how's the packaging appart from that ? :) [12:42] Tonio_: It looks alright, I am putting the final words into the review now [12:42] mok0: super, thanks :) [12:44] Tonio_: OK, have fun ;-P [12:47] mok0: thanks fot the revu :) [12:47] mok0: one thing I don't understand is about the man page [12:47] Tonio_: np! [12:47] Tonio_: ok? [12:47] mok0: when was it decided that desktop apps should have a super-overdocumented man page ? [12:48] mok0: they already have docs btw and are not intended to be used the command line way ;) [12:48] Tonio_: at least it wasn't decided that the manpage is a formality [12:49] of course it's fine to describe all options when they are to be used that way, but writting a complete book about generic kde/qt options... [12:49] Tonio_: no that's not the point, you don't need to explain options, but what the program can do [12:49] hum oki :) [12:49] and about lintian, that drives me nuts :) [12:50] Can you use it for business? What are the principles it works on? Does it rely on a database? Webpage? [12:50] oki :) [12:50] What banking system does it communicate with [12:50] etc [12:50] everyone has different expectations, override/no-override, etc.... this is very likely to the guy revuing :) [12:50] mok0: is there is clear policy for this ? [12:51] Tonio_: those are things I want to know as a user, explained in a plain language [12:51] Tonio_: Well, I think it's up to the disgression of the MOTUs and I like to see well written man pages [12:51] mok0: well as a user, you would go in the app documentation :) but that's just a personal feeling ;) [12:52] Tonio_: I always check the man page [12:52] mok0: but I get your point, sure :) I just have the feeling that everyone has different expectations with packaging on revu :) [12:53] Tonio_: We all have our favourite horses to whiip [12:53] whip [12:53] mok0: sure :) [12:53] mok0: that's not personal, just that for example, when I package, I NEVER know if I have to override or not lintian warnings [12:54] cause some people like it, some don't, some expect it etc... [12:54] Tonio_: Sometimes lintian warnings are not relevant [12:54] Tonio_: but I just prefer to switch them on when the package is finished [12:55] mok0: so do I [12:55] Tonio_: and one of yours is not used by lintian anywat [12:56] mok0: I just get lost are packaging expectations.... changing every 2 weeks... I'm packaging for 4 years, and I'm still lost when it comes to revu :) [12:57] N: Lintian discovered an unused override entry in its database. Please [12:57] N: remove it from the overrides file if it is not needed anymore. [12:57] mok0: anyway, let's fix te points :) [12:57] Tonio_: It's obvious that you are experienced. You just have to roll with the punches [12:57] :-P [12:58] Tonio_: We have to find out if it's relevant to make a .symbols file for plugins [12:59] mok0: I have no opinion on that point to be honnest... [12:59] Tonio_: Yeah... it's only a recommendation so far, anyway [12:59] mok0: about debian/watch, the issue is the debian side.... sometimes working sometimes not [13:00] Tonio_: just use sf.net/ [13:00] Tonio_: oh, and use ([\d.]*) instead of what you have [13:01] mok0: stupid man pages :) hehe [13:01] mok0: http://sf.net/skrooge/skrooge-([\d.]*)\.tar\.gz this way ? [13:03] Tonio_: yeah looks right [13:03] mok0: won't be relevant with the 403, since that's random :) [13:03] heh [13:03] mok0: just tried twice, one 403, and one working :) [13:04] Tonio_: ydrk, what a nuissance [13:04] Tonio_: I've never had the Debian PHP service work for me [13:05] mok0: yup, I'll ping debian if that continues all day long [13:05] Anyone seen this ftbfs before - http://launchpadlibrarian.net/22389029/buildlog_ubuntu-jaunty-i386.gromacs_4.0.3-1_FAILEDTOBUILD.txt.gz [13:05] essentially libtool: Version mismatch error. This is libtool 2.2.6 Debian-2.2.6a-1ubuntu1, but the libtool: definition of this LT_INIT comes from an older release [13:05] mok0: http://pastebin.com/m7ef2029d not working [13:06] Tonio_: sh*t [13:06] mok0: http://pastebin.com/m618428fe works :) [13:06] mok0: just need to be patient, I'd say :) [13:06] Tonio_: Guess so :-/ [13:07] * mok0 wishes Debian would get Lenny off the shelf so we could all get on with things [13:07] what I don't get is the 403.... that's an authorization issue, not an overloaded service or so... [13:07] For example, fix webservices that are borken [13:07] a 500 error would be more understandable [13:09] stefanlsd: hmm, strange [13:10] It's libtool acting up [13:11] stefanlsd: libtool issues some warnings in the beginning [13:11] libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and [13:11] libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am [13:13] mok0: mm. we dont have a m4 directory. will make it and try add that stuff tho [13:13] stefanlsd: well, ok, wonder why it issues that statement then [13:14] stefanlsd: perhaps you should avoid libtoolize === LucidFox_ is now known as LucidFox === zpowers is now known as Milyardp === Milyardp is now known as Milyardo [13:41] mok0: yeah. thanks. not doing that seems to "fix it". [13:42] stefanlsd: great [13:42] stefanlsd: There are some issues with libtool 2.2 and aclocal [14:28] would a MOTU be so kind as to review my package? Thanks in advance! http://revu.ubuntuwire.com/details.py?package=lmalinux [14:28] oh mok0 - thanks for advocating! [14:29] sven777: you're welcome === _neversfelde is now known as neversfelde [14:37] is revu supposed to send out emails when comments are posted? [14:38] nm - didn't realize you have to set the preference before emails happen [14:38] I thought the "subscribe" was enough to make it happen [15:04] Hi. I could use a bit of help with a build failure report. http://launchpadlibrarian.net/22413534/buildlog_ubuntu-jaunty-powerpc.mumble_1.1.7-1_FAILEDTOBUILD.txt.gz seems to indicate the problem is in the libqt4-opengl-dev package. The package has successfully built on lpia, and the other archs are still "needs to be built". The package did build successfully on i386, amd64 and lpia in my PPA. I don't have personal access to a PPC machine, so I can't try to [15:05] nixternal: THANKS :) [15:05] hey huats [15:05] hey dholbach [15:06] how's life in France? :) [15:08] Heya gang [15:08] slicer: Likely you need to wait until the package is built on ppc and then ask a MOTU to retry the build. [15:10] ScottK: Ah, so the packages I'm depending on might not be built yet? That explains a lot :) [15:11] Yes [15:11] I didn't actually look, but from your decscription that's what it sounds like. [15:21] ScottK: Hmm. Googling around and looking at other packages didn't reveal anything. I'll wait and see how the other builds go, and if they work fine, I'll request a rebuild. Thanks for your help :) [15:30] Hi. Need a second advocate for libmirage. [15:38] henrik-hw0: *sigh* [15:38] :-) [15:38] mok0: hi. === cassidy` is now known as cassidy [15:42] * henrik-hw0 attempts bribing with waffles & jam. [15:43] henrik-hw0: I don't think there are any MOTUs in revuing mode present ATM [15:52] er.. how do we specify in the changelog the changes used in Ubuntu? Something like "* Kept Ubuntu changes:" and I start laying them out? [15:52] (talking about a merge) [15:53] savvas: Something like "Remaining Ubuntu changes:" and this a list under that [15:54] Remaining! And I was wondering about that, thanks Amaranth :) [15:58] I thought remaining meant the changes that had to be done, which didn't make much sense heh [15:59] dholbach: no problemo! [15:59] * nixternal hugs #ubuntu-motu [16:01] mok0: re latest motu-meeting, did you have chance to obtain REVU db? [16:01] DktrKranz: yes I did [16:02] I have it now :-) [16:02] cool! [16:02] DktrKranz: working on my mockup === ogra_ is now known as ogra [16:03] does anyone know why OO.o is packages with a shell script (/usr/bin/ooffice) that simple calls soffice with the same arguments. That is all the script does (well it also obfuscates other applications ability to identify OO.o) [16:03] DktrKranz: I have a few issues with the schema, however. Some relations are _very_ complicated to extract [16:04] DktrKranz: ... which also makes them quite slow [16:05] mok0: do you know if mysql or postgres is required? [16:05] DktrKranz: postgresql [16:05] DktrKranz: fortunately [16:06] for REVU yes, not for my hosting [16:06] it only has mysql :( [16:06] DktrKranz: don't you have an account on spooky? [16:06] no [16:07] You'll have to run a server on localhost [16:08] like me ^^ [16:08] I can setup a VM for that [16:08] ... and me [16:08] VM with sid... [16:09] DktrKranz: You don't really need a VM for that (unless you want to imitate the setup on spooky so that the incoming uploads processing scripts work) [16:09] -czf codelite_$(UPSTREAM_VERSION)+dfsg.orig.tar.gz \ [16:09] codelite-$(UPSTREAM_VERSION)+dfsg [16:09] <-- what could possibly make this end up as codelite_+dfsg.orig.tar.gz followed by codelite-1.0.2579+dfsg?! [16:09] * hyperair curses [16:09] it's the same damn variable why doesn't it substitute the same damn value?! [16:10] hyperair: calm down :P [16:10] hyperair: It's not our fault :-( [16:10] RainCT: so, only apache and postgres is needed to run a REVU instance? [16:10] yeah yeah it isn't. [16:10] hehe [16:10] * hyperair yells at the wall and hammers on it [16:10] DktrKranz: for the web interfaces, yes [16:10] DktrKranz: yes [16:10] mmmh === freeflyi1g is now known as freeflying [16:11] DktrKranz: and you can configure apache and pg to only run when you start it (that's how I have it on my laptop) [16:11] I see [16:12] RainCT: are you able to process uploads with that instance? [16:12] DktrKranz: No, but if necessary you can import them semi-manually :P. [16:12] a feature I'd like to see is sending mails about preferred procedure to upgrade a package [16:12] which is attaching .diff.gz to bug repotrs [16:12] DktrKranz: fixing the scripts is on my TODO (actually, I've already started doing some work on them) [16:14] DktrKranz: Uhm.. Like a "Hurray! You upload has been sponsored! Now don't forget to continue watching for it, and .. " [16:14] DktrKranz: or rather when someone uploads a package which is already in Ubuntu? [16:15] both :) [16:17] but REVU is designed for NEW packages, using it for already available packages is a waste of time/resources [16:18] Hehe. Oaky. So the first one is blocking on detecting when a package is sponsored, and the second one is blocking on the new/upgrade detection code properly working ;) [16:18] so, we should encourage contributors to use LP instead [16:18] *Okay, even [16:18] Will a MOTU please peek at pyproj? [16:18] I'd certainly pay you homage [16:18] it's my very first .deb [16:18] but my excitement will ebb [16:18] if nobody responds to my barrage [16:18] LP is not the right place itself, but that's it [16:18] DktrKranz: I've heard of people (don't remember whom) that at some cases prefer to look at packages on REVU [16:18] DktrKranz: yeah, or ppa's [16:18] (http://revu.ubuntuwire.com/p/pyproj) :-) [16:19] * DktrKranz proposes to use mentors.debian.net [16:19] * RainCT proposes Debian to use REVU for mentors.debian.net *g* [16:20] RainCT: TBH, I prefer REVU too. But we need an unique place to manage such things [16:20] REVU for all [16:20] REVU for NEW only [16:21] core-devs from Canonical usually look at LP only, though [16:22] Actually, making revu.ubuntuwire.com more Debian friendly (like showing DDs as such and giving them review permissions and the like) is something I've been thinking about a bit.. Not sure if anyone would make use of that, though [16:23] well, REVU is free software, I think they could use it as well, even if I heard of some issues with mentors [16:23] *mentors.d.n [16:23] REVU FTW [16:24] DktrKranz: Anyway, so you want to contribute to REVU? :) [16:24] REVU would fix a recent discussion on debian ML about using a new Debian revision to fix sponsor's comments [16:25] heh, right [16:25] RainCT: I'd like to [16:25] this cycle I'm more code-oriented :) [16:26] less packages, more commits [16:26] (They also have that GSoC thing, though. But I've no idea what is happening with it) [16:26] DktrKranz: that's good for your LP karma ;) [16:26] DktrKranz: we were chatting about the advantages of having the REVU source packages in bzr repo [16:26] RainCT: I used to have > 35 million karma, I had karma stomachache :) [16:27] lol [16:27] DktrKranz: About wanting to contribute, that's great :). Just ask if you have any question (and if you don't know what to do just ask, too, and I'll give you something from my TODO :P). [16:27] * mok0 thinks as long as a source package has revision -0ubuntu* we should maintain them in bazaar [16:28] RainCT: do you have anything stupid enough to be fixed by a dumb Ubuntu developer like me? :) [16:28] mok0: mmmh... explain it better [16:28] DktrKranz: ok [16:29] DktrKranz: source package is sitting in a repo in LP. Uploader fixes stuff in own branch, pushes to repo [16:29] DktrKranz: There is a syntax eror in your messsage. "dumb", "Ubuntu developer" and "you".. how can those concepts be related? ;P [16:29] DktrKranz: REVUer pulls changes evaluates, posts comment on REVU [16:29] DktrKranz: Reviewer can fix tiny bits and pieces if necessarty [16:30] I think REVU itself is similar to VCS [16:30] DktrKranz: sometimes you feel cruel by asking for a tiny fix before advocation, e.g. spelling mistake or something [16:30] DktrKranz: It is [16:31] DktrKranz: we just need to have revu on top of bzr instead [16:31] DktrKranz: this is a proposal for the long term though [16:31] if distributed-development stage5 takes place, it's not that long term :) [16:31] DktrKranz: I think there's a bunch of MOTUs who still does not want to work that way [16:32] RainCT: no syntax error, it's core language now :) [16:33] DktrKranz: What's the current status of distrib-devel? [16:33] DktrKranz: bug #172895 should be easy [16:33] Launchpad bug 172895 in revu "have link to dsc file in mails" [Wishlist,In progress] https://launchpad.net/bugs/172895 [16:33] mok0: I don't know, james_w is the rockstar there. [16:34] DktrKranz: I can grep the mailing lists [16:34] btw, does someone know which month the next UDS will be? [16:34] RainCT: mind subscribing myself? [16:34] it is progressing [16:34] RainCT: Isn't it usually about a month or two after a release? [16:34] DktrKranz: done [16:34] should have some more announcements soon I hope [16:34] james_w: exiting! [16:35] james_w: ... err exciting is what I wanted to say :-) [16:35] mok0: yep, but I'd like to know something more exact to see how it fits my schedule :P [16:35] heh :-) [16:36] but well, nvm [16:37] james_w: So, is the idea to have one "upstream" trunk, with a branch off that containing debian/ and other branches containing patches? [16:37] uhm.. what's the URL of that ubuntu-nl uploads feed? [16:37] mok0: that's one possibility [16:38] mok0: the main effort at the moment is to get an "upstream" branch, then a "debian" off that, then an "ubuntu" off that [16:38] james_w: ah cool [16:38] once we have that then we can start to get more adventurous [16:38] james_w: what about branches originating in Ubuntu? [16:39] james_w: they only have the debian branch I guess [16:39] james_w: Ah, I wanted to ask.. Why is the NoMoreSourcePackages spec called like that? Is it that source packages will continue existing, but being generated by bzr-buildpackage; or is there something more? [16:39] james_w: how do you achieve that in practise? You need a separate directory for each branch? [16:40] debian native packages won't have the upstream branch, ubuntu native packages will just be an ubuntu branch [16:40] RainCT: that's one proposal for what could happen. We're not directly working towards it right now. [16:41] RainCT: though some plans may make it that most Ubuntu developers never really touch source packages, they are just created by launchpad as needed [16:41] mok0: yeah, you currently need one directory per branch. [16:41] Yeah, source package are just a transport mechanism anyway [16:42] james_w: Hm, ok, I am used to working with git, where you check out branches in the same directory [16:42] james_w: so you need another level of directory to contain the branches for a project, I guess [16:44] mok0: that's the way most people do it [16:44] ok [16:44] there is a proposal currently for how to do the git-style branching [16:45] that is, the loom stuff? [16:45] Another problem we have is that more and more upstream don't have regular releases, because they ask users to pull from their VSCs [16:45] james_w: that would be cool === hefe_bia_ is now known as hefe_bia [16:46] So the whole concept of "watch" files etc. is in trouble [16:47]