[00:15] <EzraR> what package would the default sudoers file be in?
[00:16] <EzraR> or better yet what is the command that will tell me?
[00:18] <EzraR> dpkg-query -S sudoers
[00:18] <EzraR> nm...
[00:20] <sbeattie> EzraR: it's created in sudo's postinst script; you can see it in /var/lib/dpkg/info/sudo.postinst
[00:23] <EzraR> thnx
[06:06] <fabrice_sp> hi porthose are you processing the sponsor queue?
[06:07] <porthose> fabrice_sp, was actual fix to head to bed
[06:08] <fabrice_sp> porthose, ok:_ just ot know as I was beginning to look at a sync that you ack, so I just wanted to know if 2 people werer processing the queue to be more carefull :-)
[06:08] <fabrice_sp> have a good night then ;-)
[06:09] <porthose> fabrice_sp, you to :)
[06:09] <micahg> LucidFox: maybe ask fabrice_sp if you want a second opinion
[06:09] <fabrice_sp> I just woke up ;-)
[06:09] <micahg> fabrice_sp: don't worry, easy Q
[06:09] <LucidFox> hello fabrice_np
[06:09] <fabrice_sp> ?
[06:09] <fabrice_sp> hello :-)
[06:09] <LucidFox> I have a question!
[06:10] <fabrice_sp> I just woke up so I may be slow :-)
[06:10] <LucidFox> Right now Maverick has pinta 0.3-2ubuntu1, the Ubuntu changes were merged upstream, so we were just going to sync 0.4+dsfg-1 from DEbian
[06:10] <fabrice_sp> sounds the right thing to do
[06:10] <LucidFox> But now I discovered a new grave bug, and while discarding the old Ubuntu changes, I'm going to upload -1ubuntu1 with a new patch
[06:11] <LucidFox> Should I keep the changelog entry from -2ubuntu1?
[06:11] <fabrice_sp> I did the same some time ago, and kept it
[06:11] <fabrice_sp> but I added in the last entry: Merge with Debian. Nochanges left
[06:11] <fabrice_sp> and added my entry
[06:12] <fabrice_sp> but I think it's more a question of taste
[06:12] <fabrice_sp> as actually, requesting the sync would have deleted them
[06:17] <LucidFox> Great, for some reason none of the patches from git apply, even though the code is exactly the same :(
[06:17] <LucidFox> guess I'll have to apply them manually
[06:18] <fabrice_sp> strange
[06:18] <fabrice_sp> I may be because of debsrc3.0?
[06:18] <LucidFox> *facepalm* I'm stupid
[06:18] <LucidFox> I was trying to apply them not from the source directory, but from the one above
[06:18] <fabrice_sp> it's a common error :-)
[06:19] <fabrice_sp> I usually do it when a debdiff comes from bzr as it has to be applied as p0, and not p1
[06:20] <LucidFox> :)
[06:36] <LucidFox> +		// This function should not be public! It is only like this to minimize the diff.
[06:36] <LucidFox> +		// It should be changed to protected in upstream git here and in all derived classes.
[07:31] <dholbach> good morning
[07:31] <somethinginteres> I'm fixing a bug here (needs to be submitted to debian so I am following https://wiki.ubuntu.com/Debian/Bugs: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/604636 I just want to check that the correct way to get the source for submitting to debian is 'apt-get source cheese' b/c I am getting this output in terminal: http://paste.ubuntu.com/462834/
[07:32] <somethinginteres> I orginally downloaded the source from bzr but when I used 'submittodebian' it complained about no 'orig.tar.gz' so I checked the wiki and saw they say to use apt-get souece
[07:33] <dholbach> if you run    bzr bd -- -S -us -uc    it should get you the orig.tar.gz
[07:33] <dholbach> but apt-get source cheese should work too
[07:44] <somethinginteres> dholbach: thanks. I assume that the version I am wanting is the mavrick one b/c that is 'active development' but when I ran dch -i it had 'lucid' written for my changes and mavrick for everyone elses but I did bzr brach the active development tree (hope this makes sense)
[07:45] <dholbach> somethinginteres: are you still running lucid?
[07:45] <somethinginteres> dholbach, yeah I am atm
[07:45] <dholbach> yeah, that explains it
[07:45] <dholbach> just branching off   lp:ubuntu/<package>  should give you the latest
[07:47] <somethinginteres> yeah I did umm lp:ubuntu/cheese and edited the required files but if I submit my fixes is that going to get to mavrick as well or will it only fix for lucid I just want to make sure I am fixing the right then :)
[07:48] <somethinginteres> * thing
[07:49] <dholbach> somethinginteres: once you're done and documented your changes, run debcommit, then bzr push lp:~<your ID>/ubuntu/maverick/<package>/<some branch name>
[07:49] <dholbach> then bzr lp-open and click on "propose for merging"
[07:50] <somethinginteres> dholbach, I would do that but last time I pushed to a branch and did a merge proposal I was asked to instead send it to debian
[07:50] <dholbach> ok
[07:52] <dholbach> maybe this helps: https://wiki.ubuntu.com/ReviewersTeam/WorkingWithPatches
[07:52] <dholbach> (if you need to decide when to upstream something)
[07:53] <somethinginteres> dholbach, it's going to be upstream then b/c the bug is the software centre description
[07:54] <dholbach> aha, so in that case it'd go to debian, right
[07:56] <somethinginteres> Mmm.  I just wanted to confirm I was not fixing an outdated package using apt-get source or or bzr bd or whatever, but if that is OK and will give me the correct stuff then I'm good to go
[07:57] <dholbach> yep
[07:58] <somethinginteres> could you just explain the bzr bd -- -S -us -uc command for me?
[07:58] <somethinginteres> I've not used that before :) *n00b*
[07:58] <dholbach> "bzr bd -- -S -us -uc" creates a source package (.orig.tar.gz, .dsc, .diff.gz) from the branch
[07:58] <dholbach> it passes -S -us -uc to debuild
[07:59] <dholbach> it's basically because we're living in two worlds right now: branches, building from branches, etc. on the one side and source packages, patches, etc. on the other side
[07:59] <dholbach> that's why we have to deal with stuff like that right now
[08:00] <somethinginteres> ah right.. so I run that command to pull down the source from the branch.. make my changes and submit
[08:01] <dholbach> it will use the latest code in your local branch, then get the tarbal from some location, then generate the .diff.gz (with your changes) and then the .dsc file
[08:03] <somethinginteres> oh ok so I still run bzr branch blahblah first make changes then run that command - right, i'm with you
[08:03] <dholbach> let me know how it goes :)
[08:03] <somethinginteres> will do - thanks, good class yesterday btw :)
[08:04] <dholbach> thanks a bunch :)
[08:09] <bilalakhtar> dholbach: I have a help request. Could you please examine why https://edge.launchpad.net/ubuntu/+source/krename/4.0.4-2ubuntu1/+build/1864396 is repeatedly failing?
[08:10] <bilalakhtar> It is working for other architectures, including both amd64 and i386
[08:11] <dholbach> did you ask the kubuntu folks if they have an idea? or maybe ask in #ubuntu-mobile too, if it's just arm failing
[08:12] <bilalakhtar> dholbach: ok, will ask kubuntu-devel fist
[08:12] <dholbach> good luck
[08:12] <bilalakhtar>  /join #kubuntu-devel
[08:12] <bilalakhtar> sorry ^^ typo
[08:12] <bilalakhtar> .join #kubuntu-devel
[08:13] <bilalakhtar> ARGH!
[08:44] <Rhonda> Hmm. There's something fishy with planet.ubuntu. It plants the ubuntu logo into my feed reader and I have no clue where it takes the icon from. It definitely isn't favicon nor is it referenced in the rss file.
[08:56] <Rhonda> … and the feedback link at the end of the planet page yields an 404 not found error
[09:11] <somethinginteres> blast! http://paste.ubuntu.com/462883/
[09:13] <Rhonda> somethinginteres: Missing build-depends on cdbs?
[09:14] <somethinginteres> Rhonda: probably.. how do I get that?
[09:14] <Rhonda> Take a look at debian/control.
[09:15] <Rhonda> The gimp package in the pool though has that Build-Depends.
[09:15] <Rhonda> http://packages.ubuntu.com/lucid/cdbs
[09:15] <Rhonda> bleah, wrong link :)
[09:15] <Rhonda> http://packages.ubuntu.com/source/lucid/gimp of course#
[09:16] <Rhonda> highvoltage: Why used you the link for my blog entry from planet.debian instead of from planet.ubuntu? They differ, and the one on planet.ubuntu is the more "correct" one that I prefer. :)
[09:17] <somethinginteres> Rhonda, installing cdbs now :)
[09:17] <Rhonda> somethinginteres: Actually I thought debuild does complain about not installed Build-Depends …
[09:19] <Rhonda> highvoltage: Also, at least for me it wasn't related to Zack's talk. It is spinning around in my head at least since I wrote this: http://rhonda.deb.at/blog/debian/2009/10/16 - note the date. ;)
[09:23] <somethinginteres> 'dpkg-source: error: syntax error in gimp-2.6.8/debian/control at line 45: line with unknown format (not field-colon-value)' that's the line with the description for GiMP that I just changed
[09:23] <Rhonda> How did you change it?
[09:25] <somethinginteres> just replaced  the old description with the one suggested at https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/599785 using gedit
[09:25] <sebner> Rhonda: ohh, I'm pretty late. congrats for being MOTU now
[09:25] <Rhonda> somethinginteres: Did you try to forward that to Ari from Debian for fixing it in there?
[09:26] <somethinginteres> Rhonda, no I haven't.
[09:26] <Rhonda> somethinginteres: But I think you might have b0rked the spacing. Please notice that the Description: line shouldn't have any space infront of it, the long description after there though (the rest of the description) has to be indented by one space.
[09:27] <Rhonda> somethinginteres: It might make sense to coordinate that update with the Debian packager to not create a workload for future updates in case the description gets changed in Debian resulting in merge conflicts and the likes.
[09:28] <somethinginteres> Ok then how would I best notify him of the proposed change? Link him to the LP report or..?
[09:36] <Rhonda> somethinginteres: There is some wiki page on how to forward patches. First, generate one that works and doesn't give you that error ;)  Then let someone dig out the BTS howto for you.
[09:36] <Rhonda> somethinginteres: And make sure to join Laney's and my talk this evening on exactly this topic. :P
[09:37] <somethinginteres> Rhonda, I plan to, thanks :)
[09:38] <Rhonda> somethinginteres: https://wiki.ubuntu.com/Debian/Bugs is a good entry point
[09:39] <Rhonda> And https://wiki.ubuntu.com/Debian/Usertagging
[10:17] <ripps> Any MOTU's here willing to checkout my wacom-source package on REVU. It creates a wacom-dkms package that builds a new wacom kernel module, something desperately needed for anybody using any of the new Wacom Bamboo models, as they don't work on Ubuntu Lucid/Maverick with it.
[10:18] <ripps> http://revu.ubuntuwire.com/p/wacom-source
[11:56] <highvoltage> Rhonda: still around?
[11:57] <Rhonda> Sure. :)
[12:01] <highvoltage> Rhonda: your link from planet ubuntu and planet debian look the same to me
[12:01] <Rhonda> Uh?
[12:02] <Rhonda> highvoltage: http://rhonda.deb.at/blog/2010/07/12#motu.en is from planet ubuntu
[12:03] <Rhonda> http://alfie.ist.org/blog/2010/07/12#motu.en is from planet debian
[12:03] <highvoltage> ah, when I copied and pasted they looked the same (updated now)
[12:48] <ripps> Any MOTU's here willing to checkout my wacom-source package on REVU. It creates a wacom-dkms package that builds a new wacom kernel module, something desperately needed for anybody using any of the new Wacom Bamboo models, as they don't work on Ubuntu Lucid/Maverick with it.
[12:48] <ripps> http://revu.ubuntuwire.com/p/wacom-source
[13:00] <Rhonda> ripps: For a start, the patches don't have the meta header information (author, description, ...).
[13:01] <ripps> I can fix that, but I was under the impression that was mostly optional.
[13:01] <Rhonda> Second, the package doesn't have any long description, at all.
[13:02] <Rhonda> It is optional in the way that you would need a very good reason to leave it out. ;)
[13:02] <Rhonda> You wrote "is licensed under the GPL, see `/usr/share/common-licenses/GPL'."
[13:03] <Rhonda> Please be more specific than that, include GPL version you want to have it covered under, potential including the "or later" part.
[13:03] <Rhonda> Also you don't mention /usr/share/common-licenses/GPL-2 for the upstream copyright.
[13:04] <Rhonda> The debian/install file looks weird.  A * wildcard and an additional file?
[13:04] <Rhonda> Ah, because that's debian/*, scratch that last remark. :)
[13:04] <Rhonda> Hmm, I probably should put that into the comment box instead of here. %-)
[13:09] <Rhonda> And I think REVU has issues with source format 3.0, is that possible?
[13:09] <Rhonda> "Warning! This package could not be extracted; there's no browsable directory for it on REVU."
[13:18] <geser> Rhonda: yes, REVU doesn't support v3 src packages
[13:19] <Rhonda> sebner: Thanks btw. :)
[13:19] <sebner> Rhonda: haha, better late than never :P
[13:22] <ripps> Rhonda: okay, I'm uploading an updated package now.
[13:37] <ripps> Rhonda: hmm.. patch headers weren't exactly dep-3 compliant. updloading a version with better fields
[13:47] <ripps> Rhonda: see anything else wrong with the package?
[13:48] <Rhonda> ripps: I'm not familiar with dkms, and neither with cdbs. People discourage usage of cdbs magic these days.
[13:49] <ripps> Rhonda: yeah, but I couldn't get dkms to work with dh7
[13:52] <shadeslayer> oh.. you already got hold of Rhonda :P
[13:56] <Rhonda> shadeslayer: I'm out of the boat now. I just didn't want to get ripps depressed because he asked three times within 24 hours without any response.
[13:56] <shadeslayer> Rhonda: hehe :D
[13:57] <ripps> Things on REVU have a habit of getting ignored. I'm trying to be a little more forceful with this because alot of users need this fix.
[13:58] <Rhonda> Out of curiosity, why isn't this in Debian at all?
[14:00] <ripps> I don't know, I haven't found a bug report with a similar problem in Debian. If there was, I would just try to get this into Debian.
[14:00] <ripps> Maybe nobody in Debian uses Wacom Bamboo Pen/Touches
[14:03] <Rhonda> It doesn't work with xserver-xorg-input-wacom?
[14:04] <Rhonda> Ah, wait, that's only the input driver - the kernel is the issue here, right?
[14:04] <ripps> ype
[14:04] <ripps> yep
[14:04] <geser> Rhonda: IIRC, yes. A friend has this device and he got problems to run it with Debian.
[14:05] <ripps> geser: he should have filed a bug report
[14:06] <ripps> the current method recommended is to compile a new module manually: http://www.ubuntugeek.com/wacom-bamboo-ctl-460-in-ubuntu-10-04-lucid-lynx.html
[14:07] <ripps> this is messy and it has to be redone every time the kernel is updated. So I created a wacom-dkms package in a ppa. I've been told it works, and I'm currently try to spread the word. But some people just don't like using ppa's
[14:13] <ripps> are there any motu's who are familiar with cdbs/dkms? I know alot of people need a real fix for this, not just a PPA or guide on how to compile kernel modules
[15:19] <geser> micahg: another candidate for the mozilla package set or removal from the archive: instantbird (Instant messaging client based on XULrunner and libpurple)
[15:20] <micahg> geser: thanks, I need to chat with chrisccoulson about it
[15:27] <chrisccoulson> geser - thanks. i will review that later and see if it's something that we want to keep (but i suspect it probably isn't)
[16:37] <dholbach> https://wiki.ubuntu.com/UbuntuDeveloperWeek Day 2 starts in 24 minutes in #ubuntu-classroom
[17:09] <DktrKranz> LucidFox: hi, do you need sponsoring for valknut_0.4.9-1 in Debian?
[17:10] <LucidFox> DktrKranz> Indeed!
[17:11] <DktrKranz> LucidFox: if you can give it a quick look (e.g. bump Standards-Version, and thelike) I could give it a go
[17:11] <LucidFox> Okay, moment!
[17:14] <Rhonda> \o LucidFox
[17:14] <ripps> Hi, can someone please sponsor my wacom-source package in REVU? It creates a wacom-dkms package that builds an updated wacom module. This is essential because Wacom Bamboo Pen & Touch tablets have been broken since Lucid because the Kernel's default wacom module doesn't support them.
[17:15] <ripps> http://revu.ubuntuwire.com/p/wacom-source
[17:15]  * Rhonda smirks at ripps
[17:15] <Rhonda> The times between your requests start to get shorter. I wonder when you'll travel back in time. ;)
[17:17] <ripps> Rhonda: hey, I waited almost 4 hours. I think I might just keep doing this every 4-6 hours until I get a sponsor, or someone explains to me why it won't be sponsored :P
[17:18] <ripps> I've been poking at this about since mid-June, I'm just not taking silence as an answer anymore (that and I'm feeling kinda proactive today)
[17:20] <Rhonda> Maybe you could try #debian-mentors on OFTC network too. It really looks like something that would be well suited within Debian, too.
[17:22] <joaopinto> ripps, unfortunately REVU does not get much attention
[17:23] <ripps> joaopinto: I'm aware, that's why I'm being aggressive and bugging everybody here ;)
[17:23] <joaopinto> I decided to try Debian's ITP's, I hope it works better :P
[17:24] <ripps> joaopinto: I've had success with getting packages into Ubuntu through Debian, but there isn't a bug related to my problem in Debian (although I've been told problem exists there too) and Debian Mentors want a Debian bug to be closed before they accept a package.
[17:25] <joaopinto> do you need to go through Debian Mentor's ?
[17:25] <joaopinto> can't you simple use the Intent to Package Process ?
[17:26] <ripps> joaopinto: unless you get debian developer to sponsor your package, how else are you supposed to get it in?
[17:26] <ripps> Debian Mentors makes it easy to get a sponsor
[17:27] <joaopinto> ripps, no idea, I am just following the process as documented on the web, some will have to sponsor it,
[17:27] <joaopinto> otherwise the process should not exist
[17:27] <Laney> ripps: err, you can just file the ITP yourself
[17:27] <Laney> reportbug -B debian wnpp
[17:27] <joaopinto> that's what I did :)
[17:30] <Rhonda> ripps: Then open a bugreport yourself? :)
[17:30] <ripps> I'm doing that now.
[17:34] <joaopinto> ITPs also have a huge backlog, so I am keeping limited expectations
[17:38] <Rhonda> joaopinto: Erm. ITPs means that the people who filed them are working on them. Backlog would mean that some person might actually not be really working on them and one could take them over.
[17:38] <joaopinto> Rhonda, so I am missing something, I have filled an ITP, what are the next steps ?
[17:39] <joaopinto> erm, wait, it's on Debian mentor's FAQ :P
[17:40] <Rhonda> Package it and get it uploaded. :)
[17:41] <Rhonda> ITP stands for "Intend To Package" - and if one doesn't have that intent (any more) the bugreport should rather either be closed if noone is interested, or renamed into a RFP (Request For Packaging)
[17:42] <joaopinto> ok, I am reading the get it uploaded part :P
[17:44] <ripps> I hate reportbug, I never know if it sent my ITP or not
[17:44] <joaopinto> ripps, didn't you specify your email ? You will get a message
[17:45] <ripps> joaopinto: yeah, still no email
[17:45] <LucidFox> DktrKranz> Updated package, now going to pbuilder and check it for lintian warnings
[17:46] <ripps> how do I know if sendmail worked or not?
[17:47] <ripps> wait since I didn't recieve a copy, that probably means it didn't....
[17:47] <joaopinto> ripps, assuming you are using a local sendmail, check your logs ?
[17:47] <joaopinto> Rhonda, are you familiar with the "Free Art License"  ?
[17:48] <ripps> where are the sendmail logs?
[17:48] <joaopinto> http://wiki.debian.org/DFSGLicenses#TheArtisticLicense states that the original version is free, the documentation describes version 1.2
[17:49] <joaopinto> ripps, /var/log/mail.log
[17:49] <ripps> yeah... it seems I'm getting connection timed out
[17:49] <ripps> Jul 13 11:45:13 ripps-desktop postfix/smtp[14004]: A3FD8229A2: to=<ripps818@gmail.com>, relay=none, delay=551, delays=445/0.26/106/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.77.27]:25: Connection timed out)
[17:50] <ripps> so, I guess my postfix is broken
[17:57] <Laney> ripps: set smtphost in ~/.reportbugrc
[17:57] <ripps> Laney: set it to what?
[18:01] <Rhonda> Hmm, if people ask me something and don't wait for an answer for a few minutes it gets a bit … depressing. :/
[18:02] <c_korn> Rhonda: joao had to leave.
[18:05] <ripps> Argh.... I hate this postfix senmail reportbug crap.
[18:07] <ripps> someone please explain how to setup postfix
[18:07] <ripps> I went through dpkg-reconfigure, still not working
[18:20] <Laney> ripps: You should be more patient. Use your ISP's server.
[18:20] <Laney> or reportbug.debian.org
[18:21] <Rhonda> What is reportbug.debian.org meant to be? :)
[18:21] <ripps> Laney: well, I'm just wondering why postfix doesn't work. It seems postfix keeps trying every couple minutes, and it fails to send to both debian.org and gmail
[18:21]  * Laney shrugs
[18:21] <Laney> I use ssmtp as a simple mta
[18:28] <ripps> Laney: woo, I got it working
[18:29] <ripps> I had to set my relayhost = mail.charter.net
[18:31] <ripps> I wish the confiure dialog had warned me that ISP's block port 25
[19:05] <ripps> Yeah, okay. So a Debian Dev just snuffed my ITP.
[19:06] <ripps> snubbed
[19:06] <ripps> basically, he says I'm working around both the Kernel Development process and the problem should be fixed directly in the mainline kernel, not working around it with a dkms package.
[19:07] <ripps> I would love to have the kernel fixed directly, but I have no idea how to write a patch like this for the kernel
[19:08] <micahg> ripps: have you tried asking the kernel team for guidance?
[19:09] <ripps> micahg: I've asked about it in the #ubuntu-kernel before, but I was never responded to.
[19:11] <micahg> ripps: what about the kernel team ML?
[19:11] <ripps> micahg: haven't tried that yet...
[19:57] <LucidFox> DktrKranz> Okay, valknut updated, verified to build in sid without lintian warnings, and uploaded to mentors
[20:01] <omid> trying to make package for pecl-cairo for php, but get this error: http://pastebin.ubuntu.com/463116/
[20:06] <micahg> omid: it's using a static path to install instead of under the build dir
[20:07] <omid> micahg, how can I solve it?
[20:08] <micahg> omid: idk
[20:17] <omid> micahg, thanks :)
[20:25] <shadeslayer> simar: poke
[20:26] <shadeslayer> simar: ok,first up is getting the info you need to start working,checkout the topic of this channel
[20:26] <shadeslayer> loads of stuff needs fixing
[20:27] <shadeslayer> unfortunately im about to crash and burn on the keyboard :S
[20:29] <simar_mohaar> shadeslayer, Hi i'm simar now simar_mohaar temp
[20:29] <shadeslayer> :)
[20:29] <shadeslayer> simar_mohaar: ok,btw im from india as well ;)
[20:30] <shadeslayer> simar_mohaar: just check out the links in the topic
[20:30] <shadeslayer> the last one is pretty good for starting
[20:30] <shadeslayer> fixing ftbfs errors
[20:30] <simar_mohaar> shadeslayer, Good to know that ..
[20:31] <simar_mohaar> shadeslayer, I'm sorry which topics .. I dinn't get :(
[20:31] <shadeslayer> :)
[20:31] <shadeslayer> simar_mohaar: type : /topic
[20:31] <shadeslayer> and hit enter
[20:31] <simar_mohaar> shadeslayer, ya I can see now
[20:31] <shadeslayer> good :D
[20:31] <shadeslayer> simar_mohaar: see the last one
[20:32] <shadeslayer> simar_mohaar: for eg. right now im fixing kdiff3,have a look at the build log
[20:32] <shadeslayer> simar_mohaar: https://edge.launchpad.net/ubuntu/+source/kdiff3/0.9.95-6/+build/1811961
[20:32] <shadeslayer> click on buildlog
[20:32] <simar_mohaar> shadeslayer, ok
[20:33] <shadeslayer> simar_mohaar: itll load loads of text and fancy stuff
[20:33] <shadeslayer> simar_mohaar: just go along the build log and look at what happens
[20:33] <simar_mohaar> shadeslayer, ya that is what danial explained yesterday. :)
[20:33] <shadeslayer> :)
[20:34] <shadeslayer> thats why im telling you to have a look at this :P
[20:34] <shadeslayer> since you did this yesterday :D
[20:34] <simar_mohaar> shadeslayer, One thing before this from where to get more such bug to fix ...
[20:34] <shadeslayer> simar_mohaar: again,/topic
[20:34] <shadeslayer> there are loads of ftbfs errors waiting to be loved
[20:34] <simar_mohaar> shadeslayer, Tday in morning i tried to fix these but dinn;t find any :(
[20:35] <simar_mohaar> shadeslayer, ok, Now i'm getting the stuff
[20:35] <shadeslayer> see when you open the last link,it loads up a list of packages
[20:36] <shadeslayer> it has 3 links,PTS == package tracking system ( debian ) , LP == Launchpad BTS == debian bug tracking system
[20:36] <shadeslayer> for every package
[20:36] <shadeslayer> simar_mohaar: you will want to look at the LP links first and then at lp build log
[20:36] <simar_mohaar> shadeslayer, As you find good :)
[20:37] <shadeslayer> simar_mohaar: well.. ive gtg.. need some sleep,will be back tommorow to help,ive given you enough info to get started i think
[20:37] <shadeslayer> but just poke around the channel and someone will help
[20:38] <shadeslayer> simar_mohaar: pick a package and start hacking
[20:38] <shadeslayer> no matter how long it takes,keep at it :P
[20:38] <simar_mohaar> shadeslayer, how to poke and really thanks for your help
[20:38] <shadeslayer> simar_mohaar: well.. just ask people around for help
[20:38] <shadeslayer> like suppose you have xyz error
[20:38] <simar_mohaar> shadeslayer, thanks again ...
[20:39] <shadeslayer> post that error here and then someone who knows will help
[20:39] <shadeslayer> simar_mohaar: np
[20:39] <simar_mohaar> shadeslayer, thankyou we will catch tommorrow ..
[20:39] <shadeslayer> sure
[20:40] <shadeslayer> im online a bit more.. 10-15 mins,then gone for sleep :)
[20:40] <simar_mohaar> shadeslayer, ok
[20:41] <simar_mohaar> shadeslayer, I think i will look at kdiff as you said earlier .
[20:41] <shadeslayer> simar_mohaar: its not that easy :P
[20:41]  * shadeslayer is still struggling....
[20:41] <shadeslayer> but sure go aheahd
[20:42] <simar_mohaar> shadeslayer, Please tell me some eary first.
[20:42] <shadeslayer> hmm
[20:42] <simar_mohaar> shadeslayer, One more thing I'm running Lucid and not Maveric does this make sense ??
[20:43] <simar_mohaar> shadeslayer, Or do I need Virtual machine ?
[20:43] <shadeslayer> simar_mohaar: yeah,you just need a pbuilder
[20:43] <shadeslayer> !pbuilder | simar_mohaar
[20:43] <simar_mohaar> pbuilder with -dist or just pbuilder -create
[20:44] <simar_mohaar> !pbuilder | simar_mohaar
[20:45] <shadeslayer> simar_mohaar: https://edge.launchpad.net/ubuntu/+source/mgltools-bhtree
[20:45] <shadeslayer> that looks good
[20:45] <shadeslayer> simar_mohaar: http://people.ubuntuwire.org/~lucas/ubuntu-nbs/64/gst-plugins-bad-multiverse0.10_0.10.18-0ubuntu1_lubuntu64.buildlog
[20:46] <shadeslayer> see one of the install files in debian/ needs fixing
[20:46] <shadeslayer> dh_install: cp -a ./debian/tmp/usr/lib/gstreamer-0.10/libgstxvid.so debian/gstreamer0.10-plugins-bad-multiverse//usr/lib/gstreamer-0.10/ returned exit code 1 << means it could not find the file it needs to copy
[20:47] <simar_mohaar> shadeslayer, ok that fine .. I got it. :)
[20:47] <simar_mohaar> shadeslayer, Probably i will fix it by tomm. :)
[20:47] <shadeslayer> :)
[20:47] <simar_mohaar> shadeslayer, By the way what these package are. These are for Lucid or Maveric ??
[20:48] <shadeslayer> simar_mohaar: these are package for maverick that failed to rebuild
[20:48] <shadeslayer> due to some changes in another package maybe
[20:49] <simar_mohaar> shadeslayer, But i have created the chroot enviroment using pbuilder -create  . I think this will create for Lucid base tarball
[20:49] <shadeslayer> simar_mohaar: that depends on your pbuilderrc
[20:49] <simar_mohaar> shadeslayer, let me check
[20:51] <simar_mohaar> shadeslayer, How to open this file. I mean where it is located?
[20:51] <dupondje> simar_mohaar: /var/cache/pbuilder :)
[20:52] <shadeslayer> simar_mohaar: open : .pbuilderrc : in your ~
[20:52] <shadeslayer> dupondje: pbuilder rc :D
[20:52] <dupondje> I recommend using pbuilder-dist
[20:52] <dupondje> this is a wrapper to make build environments for lucid/maverick etc
[20:52] <dupondje> quite easly :)
[20:52] <simar_mohaar> shadeslayer, I have this in it COMPONENTS="main universe multiverse restricted"
[20:53] <simar_mohaar> shadeslayer, Do i need to build another chroot
[20:53] <shadeslayer> simar_mohaar: set DISTRIBUTION=maverick
[20:53] <shadeslayer> simar_mohaar: then just do sudo pbuilder update
[20:53] <shadeslayer> dupondje: around to help?
[20:54] <dupondje> yea :)
[20:54] <simar_mohaar> ok thanks. Now i think I can work right away ..
[20:54] <shadeslayer> dupondje: need to sleep :D
[20:54] <dupondje> héhé :)
[20:54] <simar_mohaar> shadeslayer, thankyou verry much for your great help
[20:54] <shadeslayer> simar_mohaar: dupondje will be able to help with queries :D
[20:54] <shadeslayer> simar_mohaar: np
[20:54] <shadeslayer> ciao
[20:54] <dupondje> enjoy :)
[20:54] <simar_mohaar> shadeslayer, dupondje Thats great
[20:55] <shadeslayer> dupondje: hehe :D
[20:55] <simar_mohaar> shadeslayer, But I think I will need some work on my part on one package to fix..
[20:56] <shadeslayer> dupondje: the error is a simple cp -a error,from dh.. he probably will be able to fix it himself,tho might need info about what .install files actually do :D
[20:56] <shadeslayer> ok then.. bye all :D
[20:57] <simar_mohaar> ok bye
[21:05] <omid> trying to make package for pecl-cairo for php, but get this error: http://pastebin.ubuntu.com/463116/
[21:06] <dupondje> did you try looking at another php 'addon' package ? :) should be quite the same way
[21:10] <omid> dupondje, mmmm, nice idea :> thanks
[21:39] <omid> dupondje, how can I find debian/rules of a package
[21:40] <dupondje> apt-get source 'package'"
[21:40] <EzraR> any motu want to review a package on REVU? The package is for Mangler, a ventrillo client for linux. Its already got one advocation and all issues should be fixed!
[21:41] <EzraR> http://revu.ubuntuwire.com/p/mangler
[21:50] <omid> dupondje, thanks :)