[00:28] <psusi> how does nautilus decide what to open a given file with and the other menu options?  I thought there was a gconf key that listed that sort of thing for each mime type, but I can't find it
[00:29] <psusi> I could have sworn that you used to be able to right click on a cd-rw and choose blank, but it looks like that doesn't work now because nautilus thinks it is a "folder" instead of a cd-rw...
[01:42] <c2tarun> An application epdview. Debian has its new version, I tried to build the native new Debian version for natty but it failed. So sync cannot be possible. I need to merge it. Can anyone please help.
[01:47] <persia> Why does it need to be merged?
[01:47] <persia> Does it include a cool new feature?  Does it fix a useful bug?
[01:49] <c2tarun> persia: well there should be something that made debian included the newer version.
[01:51] <persia> Sure, but after DebianImportFreeze, there needs to be a reason to do a merge or sync.
[01:52] <persia> Reasons vary: could be fixing a bug, could be a new cool feature, could be beause you really, really want to merge it.
[01:52] <persia> Doesn't matter what the reason is, but there needs to be *some* reason.
[01:52] <persia> So, either find a reason to do this merge, or find something else that needs doing.
[01:54] <c2tarun> persia: well I am new so I dont know much :( but they applied all the patches that somehow needed a change in the build-dependencies.
[01:54]  * c2tarun (But I was wondering patches are also there in previous version, they are just applied by upstream, why we didn't added the new build-dependency requirement in previous version?)
[01:55] <persia> Being new only means you have a greater opportunity to learn :)
[01:56] <persia> My recommendation would be to start by looking at the upstream changelog and the Debian changelog.  Then compare these to the diff in the code.
[01:56] <persia> See if any of that looks interesting to you, or like a good reason to merge it.
[01:56] <artfwo> c2tarun: I see there have been a number of "hardening" changes, debian version is more secure, and that's good for a PDF viewer
[01:57] <c2tarun> artfwo: this security reason is enough? and there was no change in the source code, can just by importing one library make the application more secure?
[01:59] <artfwo> building against hardening-includes is supposed to make things harder to break. is this reason enough for you? :)
[01:59] <micahg> yes, I'd say that's worth pulling in if the FTBFS can be fixed
[01:59] <micahg> c2tarun: it needs a merge anyways since there's an UBuntu change
[02:00] <c2tarun> micahg: cool :) so can you help me a bit please in merging?
[02:01] <micahg> c2tarun: would you like to fix blobwars for me :)
[02:01] <c2tarun> micahg: sure :)
[02:02] <micahg> c2tarun: I was half joking, but that one we can fix after feature freeze as well
[02:03] <c2tarun> micahg: feature freeze means? debian has a newer version and can you please tell me where to find the PTS page for blobwar?
[02:03] <micahg> c2tarun: just make sure there's a bug filed and I'll milestone it for 11.04 beta
[02:04] <micahg> c2tarun: I've already started working on blobwars, so don't worry about it, I was just saying, I have my own FTBFS to fix ATM :)
[02:04] <c2tarun> micahg: what kind of bug I should be? sync or merge?
[02:04] <micahg> c2tarun: merge since there's an Ubuntu change
[02:04] <c2tarun> micahg: oh.. :)
[02:05] <c2tarun> micahg: ok :) i'll file the bug? do I hv to subscribe any team to that bug?
[02:05] <persia> c2tarun, No, just assign yourself
[02:06] <c2tarun> persia: myself? but micahg already started working on blobwars.
[02:07] <persia> c2tarun, for epdview (unless you decided not to do it)
[02:07] <c2tarun> persia: i'll merge epdfview :)
[02:08] <micahg> c2tarun: I was suggesting filing a bug for epdfview
[02:08] <c2tarun> micahg: yeah :) sorry I got it wrong. I am doing that
[02:11] <c2tarun> micahg: bug 721054
[02:13] <micahg> c2tarun: milestoned, thanks
[02:22] <c2tarun> In uploading the package for a merge bug on LP what files should be attached one is the latest ubuntu1.debian.tar.gz, any other files that might help in reviewing?
[02:23] <micahg> c2tarun: debdiff from Debian version to Ubuntu version
[02:23] <persia> I usually request a debdiff between latest Debian revision and the candidate revision.
[02:24] <c2tarun> ok i'll get the debdiff from current debian version to ubuntu version, persia: what do you mean by candidate revision?
[02:25] <persia> The revision that you've prepared, which you are presenting as a candidate to be included in Ubuntu.
[02:27] <c2tarun> persia: ok, done :)
[02:29] <micahg> c2tarun: no, you're still removing all the patches and adding them back as one big one
[02:30] <c2tarun> micahg: ya those are already applied. did i miss something?
[02:31] <micahg> c2tarun: idk, seems something funny about merging with source format 3
[02:32] <c2tarun> micahg: so what can i do?
[02:32] <c2tarun> micahg: I mean to fix this?
[02:33] <persia> c2tarun, Do you understand the nature of the issue?
[02:33] <micahg> c2tarun: I don't know offhand, I'm having a weird issue myself trying to merge eclipse
[02:33] <c2tarun> micahg: ok, no prob :) I'll ask it on channel someone will reply thanks :)
[02:35] <c2tarun> I can fix the indentation problem of changelog + i'll add an entry of dropping all the patches. But I dont know how to remove that big patch, can anyone please help. bug 721054
[02:35] <micahg> c2tarun: no, the patches shouldn't be dropped
[02:36] <c2tarun> micahg: but they are already applied. I checked.
[02:37] <persia> c2tarun, You may want to read more about Format: 3.0 (quilt).
[02:37] <persia> In the dpkg documentation.
[02:37] <persia> The patches are not applied upstream: they're just applied in the unpacked Debian source.
[02:38] <c2tarun> persia: I also thought that may be one condition, but I tried to remove all of them first by quilt pop :(
[02:39] <c2tarun> persia: ping
[02:41] <persia> Why do you ping me?
[02:42] <c2tarun> persia: I am not getting, I checked by removing all the patches, and none of them were applied at the time I checked that are they applied or not. Then  why shouldn't I remove those patches?
[02:43] <persia> c2tarun, So, if you look at your debdiff, you may notice debian/patches/debian-changes-0.1.7-5ubuntu1
[02:44] <persia> That is produced because of differences between the unpacked source and the source in the original upstream artifact.
[02:44] <persia> Precisely how you reached that state is something I don't know, but I presume you can reproduce by experimentation.
[02:47] <c2tarun> persia: ya somehow it didn't makes sense. the patches are included in the new debian version. How can they be applied? If they are applied already than they should have been removed from the debian version as well. And since they are included it means that they are not applied. Can you please explain me one last thing please, how is the patch applied in the version I am working on?
[02:48] <persia> Which patch?
[02:48] <c2tarun> persia: all of them
[02:49] <persia> Are you asking why the patches in debian/patches are applied when you unpack the source?
[02:50] <c2tarun> persia: No I am asking how to remove the patches that get applied automatically when we unpack the source.
[02:50] <persia> assuming bash: `export QUILT_PATCHES=debian/patches; quilt pop -a`.  Why would you wish to do this?
[02:51] <persia> Note that the above line is specific to this type of package.  There are many other sorts of packages that require different treatment.
[02:51] <c2tarun> persia: quilt pop -a is not working, and unless I dont pop the applied patches how can i build the source package?
[02:53]  * c2tarun by not working I mean getting the message no patches applied
[02:53] <persia> That sort of package presumes the patches have been applied when you build the source package.  Unapplying them will result either in them being reapplied or unexpected behaviours, depending on other changes to the package at the same time.
[02:53] <persia> Did you export QUILT_PATCHES first?
[02:53] <c2tarun> persia: nope, let me do that
[02:54] <c2tarun> persia: can I include it in my .bashrc, I think I gonna need it very often
[02:54] <persia> No.
[02:54] <persia> If you want to include something to work by default, read the docs on the quilt package, which has some suggested ways to handle it.
[02:54] <c2tarun> persia: ok sure
[02:56] <c2tarun> persia: I just checked that export* line is already in my .bashrc. still I was not ablt to pop that patch.
[02:56] <c2tarun> *pop any patch
[02:57] <persia> That export line won't work unless used in the right context.
[03:04] <persia> I believe the correct solution is to modify .quiltrc in specified ways, not .bashrc
[03:10] <c2tarun> persia: I uploaded a new debdiff, can you please take a look.
[03:12] <persia> You don't need to upload the debian.tar.gz.  Only the debdiff.
[03:12] <c2tarun> persia: ok :) from next time i'll get the debdiff only
[03:13] <persia> That looks well-formed.  Do you see the difference between this and your other debdiff?  Do you understand how it got each way?
[03:13] <c2tarun> persia: yup :) finally ;)
[03:14] <persia> So, tell me :)
[03:15] <c2tarun> persia: can you please sponser it? :)
[03:16] <udienz> micahg, i try to merge conkeror in bug 720069. seems like its is mozilla seed
[03:16] <persia> c2tarun, If you tell me about the difference between this debdiff and the other one
[03:20] <c2tarun> persia: this is a clean diff containing only the info of one poppler patch. This is the actual differece because earlier patches are not applied, somehow I did something that applied them. Since those patches are also in the ubuntu version so they are not the difference ;) hence not in this debdiff :)
[03:21] <persia> Excellent, and do you know what you did before that applied them?
[03:21] <c2tarun> persia: all other things are legitimate, as changes for ubuntu releases in changelog.
[03:22] <c2tarun> persia: sorry not getting what you are asking ?
[03:22] <persia> Do you know what went wrong the first time?
[03:24] <c2tarun> persia: yup, everything started with the changes made by mom in series, while fixing that may be somehow I applied those patches, that quilt pop was exectued by me before fixing that series file. so I checked that they are applied and that was wrong.
[03:25] <c2tarun> *series=> debian/patches/series
[03:25] <persia> Cool.  Now you know.  I often find that when I make a mistake I have a much lower chance of repeating it if I understand what went wrong.
[03:25] <c2tarun> persia: yup :)
[03:26] <persia> And, it's always worth checking your debdiff carefully (even if you're not seeking sponsorship).  make sure you intend all the changes that appear, and if something is confusing, try to sort that first, before sending to sponsors/uploading.
[03:37] <Yanks> !ops
[03:37] <Yanks> you know ur motherboard has 250$ worth of gold in it?
[03:37] <Yanks> !ops
[03:38] <Yanks> !staff
[03:39] <Yanks> !ops
[03:41] <persia> Yanks, May I help you?
[03:41] <Yanks> who the fuck r u
[03:41] <persia> !ohmy > Yanks
[03:41] <Yanks> fuck u ubottu
[03:41] <psusi> someone please boot this jackwaggon spammer that has already bene booted from +1
[03:42] <Yanks> please fucking ban me
[08:47] <novicedeveloper> hi. i want to start developing for ubuntu. But not getting the right way to start with. I checked the bug squad but it was confusing. i am confused.
[08:49] <novicedeveloper> please help
[08:51] <novicedeveloper>  hi. i want to start developing for ubuntu. But not getting the right way to start with. I checked the bug squad but it was confusing. i am confused. please suggest something.
[08:51] <artfwo> novicedeveloper, I'd suggest you start by reading https://wiki.ubuntu.com/ContributeToUbuntu#Maintaining Ubuntu
[08:52] <novicedeveloper> artfwo: thank you. but i hav queries also.
[08:52] <artfwo> if you have them, ask :)
[08:53] <novicedeveloper> artfwo:  cant i start wuth coding directly instead of entering into  correcting bugs and then strart coding?
[08:53] <novicedeveloper> :)
[08:53] <artfwo> of course
[08:53] <novicedeveloper> artfwo:  so how can i do that?..:P
[08:53] <artfwo> but I think, it's easier to start by fixing bugs
[08:54] <artfwo> that's described in the same page as above: https://wiki.ubuntu.com/ContributeToUbuntu#Writing%20Code
[08:55] <novicedeveloper> artfwo: ok.. :) .. now in bug fixing i would like to go with something related to kernel.
[08:55] <novicedeveloper> artfwo: so can u please suggest something related to this?.. :)
[08:56] <artfwo> I am not much into kernel development :)
[08:56] <mok0> Why would the buildd not be able to find gcc?? See this build: https://edge.launchpad.net/ubuntu/+source/collectd/4.10.1-2.1/+buildjob/2101835
[08:57] <artfwo> novicedeveloper, but there's a dedicated wiki page as well: https://wiki.ubuntu.com/Kernel/Dev
[08:57] <dholbach> good morning
[08:57] <mok0> goodmorning dholbach
[08:57] <novicedeveloper> artfwo: ok. i may find something good there.. :).. thnakyou
[08:57] <novicedeveloper> dholbach: good morning
[08:57] <novicedeveloper> artfwo: *thank you
[08:58] <dholbach> hi mok0
[08:59] <novicedeveloper> artfwo: thankyou for help.. there is lot given in  https://wiki.ubuntu.com/Kernel/Dev.. i will read it.. :)
[09:01] <novicedeveloper> dholbach: hi. i have read your class of "Getting started with ubuntu development".. it was teally informative.. hope to look forward help from you... :)
[09:01] <dholbach> novicedeveloper, that's great
[09:01] <novicedeveloper> dholbach: *really
[09:01] <dholbach> if you have any questions, just ask in here - there's always somebody around who can try to help you
[09:02] <novicedeveloper> dholbach: ok. thanks.. :)
[09:02] <dholbach> ROCK ON! :)
[09:03] <novicedeveloper> dholbach: yooo.... \o/...
[09:03] <dholbach> :-D
[09:12] <mok0> dholbach: what was the idea re: the ubuntu-packaging guide? It still seems to be a stub
[09:13] <dholbach> mok0, did you check out lp:ubuntu-packaging-guide?
[09:13] <dholbach> that's where it happens :)
[09:14] <mok0> dholbach: I did, but I don't see any action
[09:14] <dholbach> mok0, I contributed 3 guides to it and barry is working on getting UDD docs merged in
[09:15] <dholbach> some other bugs are assigned and work is in progress
[09:15] <dholbach> it's not a fast moving target (yet), but there's actually people working on it
[09:15] <mok0> dholbach: Any coordination going on? I'd like to contribute, but not sure what is needed
[09:16] <dholbach> mok0, we filed bugs for articles that we'd like to see - we use merge proposals to peer-review stuff that goes in
[09:16] <mok0> dholbach: Is the idea that it should replace what's on the Wiki?
[09:16] <mok0> dholbach: I'll go check out the LP project I guess
[09:17] <dholbach> mok0, in the long run, yes probably - for now we want to create useful articles that are task-based (as opposed to one huge guide) and additional knowledge base articles that deal with more general topics
[09:17] <dholbach> there's also a spec that explains which old content we could merge in, but what might need updating
[09:17] <dholbach> let me get the link
[09:18] <dholbach> https://wiki.ubuntu.com/Specs/ImprovePackagingGuide
[09:18] <mok0> dholbach: I'll grab bug #704845
[09:19] <mok0> dholbach: I drafted something on the wiki for that
[09:19] <dholbach> sweet
[09:19] <dholbach> thanks a bunch mok0
[09:19] <dholbach> Laney, ^
[09:19] <dholbach> yoohoo! :)
[09:19] <Laney> :-)
[09:20] <mok0> Laney, dholbach actually, come to think of it, what I drafted was the reverse: a guide for upstreams on how to work with Ubuntu
[09:21] <mok0> Laney: dholbach, but perhaps it makes sense to put in the same guide?
[09:21] <dholbach> that might be interesting as well
[09:21] <dholbach> yeah, if not in the "task-based" section, it would be an excellent "knowledge-base" article
[09:21] <dholbach> I'll work with barry to get his huge branch in, then I'll juggle pieces around a little bit
[09:21] <dholbach> but if you make it a separate article for now, we'll have no problems integrating it
[09:22] <mok0> dholbach: I might as well start there
[09:23] <dholbach> thanks a lot mok0
[09:23] <mok0> dholbach: I guess I should join the team
[09:23] <dholbach> you already are
[09:23] <dholbach> ubuntu-dev and ubuntu-core-doc are in there
[09:23] <mok0> dholbach: heh, indeed
[09:23] <dholbach> :-D
[09:24] <mok0> dholbach: so work-flow is to work in a branch ?
[09:24] <dholbach> yes, branch from lp:ubuntu-packaging-guide, commit, push to a separate branch, propose merge
[09:25] <dholbach> I'll do my best to review as quickly as possible and get more other folks involved in reviewing stuff as well
[09:25] <dholbach> Laney, ^ :)
[09:25] <mok0> dholbach: great
[09:29] <slomo> hi, is anybody updating gst-plugins-bad0.10, gst-plugins-ugly0.10 and their multiverse variants?
[09:37] <mok0> dholbach: I also wrote this draft: https://wiki.ubuntu.com/GettingStartedDraft
[09:37] <mok0> dholbach: but I ran out of ideas and time
[09:38] <dholbach> mok0, I wrote three articles "Very general introduction to Ubuntu Development", "Getting set up" and "how to fix a bug" - I could imagine that some of the info in your article would be very helpful to get merged in there - what do you think?
[09:39] <mok0> dholbach: perhaps, but this is more like a self-paced course, with exercises etc
[09:40] <dholbach> I like the idea of exercises
[09:41] <mok0> dholbach: yes, it's a good way to get people started
[09:41] <dholbach> I'm not sure what's the best way of integrating them
[09:41] <dholbach> if you have a good suggestion, I'm all ears :)
[09:45] <mok0> dholbach: The three articles you mentioned ^ , where are they?
[09:45] <dholbach> in the root directory?
[09:45] <dholbach> err root of the source tree :)
[09:45] <dholbach> the .rst files
[09:45] <mok0> dholbach: ah, they are already in the branch, I see
[09:45] <dholbach> rock!
[09:46] <mok0> dholbach: I will reformat to rst and add my gettingstarteddraft, then we can work on it together
[09:46] <mok0> dholbach: perhaps merge etc
[09:47] <mok0> dholbach: I can't find my upstream guide on the wiki.
[09:47] <mok0> dholbach: It's lost in the jungle
[09:48] <mok0> dholbach: and I can't see that I have a link to it... :-/
[09:48] <mok0> The problem with wikis...
[09:48] <dholbach> ok, let's start with the gettingstarteddraft
[09:49] <dholbach> I hope that once we have a lot of content in the branch we can sit together and think of a good structure for it
[09:50] <dholbach> the way I see it right now, it'd be good to have some kind of simple landing page that links you to the knowledge base articles (common problems to avoid when packaging, DEP-3, how to triple-check your new package, etc.) and lists tasks that people who like to do (fix a simple bug, update a package to a new version, propose a change for sponsorship, etc.) - I realiase that this might not be the perfect recipe for everything, but I feel it's a
[09:50] <dholbach>  good start
[09:51] <mok0> dholbach: sounds good
[09:52] <mok0> dholbach: is there another way to search the wiki? The search field only searches titles.
[09:53] <dholbach> there should be a link to "full text search" no?
[09:54] <mok0> dholbach: ah. Google :-)
[09:54] <mok0> https://wiki.ubuntu.com/UpstreamGuide
[09:54] <dholbach> yeehaw
[09:57] <dholbach> so who apart from mok0 is interested in helping out with the packaging guide?
[09:57] <dholbach> it'd be really nice if you all signed up for the team mailing list
[09:57] <dholbach> and checked https://code.launchpad.net/ubuntu-packaging-guide/+activereviews every now and then
[10:03] <mok0> dholbach: on the mL now. Can you give me a hint how to render .rst text?
[10:03] <mok0> dholbach: format seems simple enough
[10:03] <dholbach> run "make html"
[10:04] <dholbach> and open the file in _build/html/ in a browser
[10:04] <mok0> dholbach: ah :-)
[10:04] <dholbach> there might be an immediate "rst viewer", but I don't know
[10:04] <dholbach> that's what I did :)
[10:04] <mok0> dholbach: didn't notice the Makefile in there...
[10:05] <dholbach> if you prefer pdf, you can run "make pdf" too (and lots of other things)
[10:05] <dholbach> for .pdf you might need all the build-deps of the package though
[10:41] <mok0> dholbach: is this packaging-guide meant to go online as HTML sometime?
[11:12] <dholbach> mok0, yes
[14:02] <hggdh> what replaces multilib in karmic? gcc-multilib and gcc-4.4-multilib are both phantom packages
[14:24] <hggdh> bah, just an amazingly restricted sources.list
[14:51] <Laney> debfx: cheers for the haskell help \o
[16:08] <c2tarun> what is revision control?
[16:09] <micahg> c2tarun: http://en.wikipedia.org/wiki/Revision_control
[17:22] <debfx> Laney: you're welcome :)
[17:40] <c2tarun> I was trying to grab a package for merging or sync ( as needed) I got this warning http://paste.ubuntu.com/568832/ What does it mean?
[17:41] <micahg> it means the Debian source is maintained in svn
[17:42] <c2tarun> micahg: so what is so special with it? I mean why a warning?
[17:43] <micahg> c2tarun: it points people to where the packaging code lives if they want to work on it,
[17:43] <c2tarun> micahg: ok.
[17:48] <c2tarun> micahg: whenever we grab a package using the grab script, it unpacks the tarball and applies all the patches. but when I try to remove those patches by quilt pop -a then I always get the message no patches removed. Why so?
[17:49] <c2tarun> ls
[17:49] <c2tarun> oops :(
[17:49] <micahg> c2tarun: no, it doesn't necessarily apply all the patches
[17:49] <micahg> c2tarun: you probably need to set up .quiltrc
[17:50] <c2tarun> micahg: do you mean export QUILT_PATCH=debian/patches line in .quiltrc?
[17:51] <micahg> QUILT_PATCHES
[17:51] <c2tarun> micahg: yup my bad sorry :( ok i'll do it.
[23:44] <grunthus> Hi, I have been working on a bugfix, need a little help with commit and push commands
[23:46] <grunthus> First, after bzr ci, in the text editor, should I describe changes in same fashion as with changelog files?
[23:50] <lifeless> install bzr builddeb
[23:50] <lifeless> then you can just use debcommit
[23:53] <grunthus> Hi lifeless, AFAIK, because its the trunk, there is no deb
[23:54] <grunthus> bug 715820