[00:29] <c_korn> hm, I cannot install libgoogle-perftools-dev. it says it depends on version 0.98 but version 0.85 is going to be installed
[00:35] <mmmiiikkkeee> Hi, I am writing my first OS app; I want to learn how to package it for Ubuntu.  I was reading the Ubuntu policy manual and it says: "Every package must have a Debian maintainer"  I am not a Debian developer; does that mean I can't package my app for Ubuntu?
[00:42] <directhex> mmmiiikkkeee, no. it's probably an error in the copypasta from debian policy
[00:42] <ScottK> Actually it's not.
[00:43] <ScottK> Every package must have a maintainer, just in Ubuntu it's almost always a team.
[00:43] <directhex> it's preferred if the team is dynamic & sexy, though
[00:44] <prower> Is there any reason why libstdc++-5 is no longer included in the repositories for karmic? The lack of the libraries has broken a lot of the closed-source software that I used to use without issue in Jaunty
[00:44] <TheMuso> prower: Because the version of gcc that libstdc++5 was part of, was removed from karmic.
[00:45] <prower> TheMuso, I see...so there's no way to run any of these commercial packages in karmic any more, then
[00:46] <mmmiiikkkeee> ScottK: so for my package I would just put myself as the maintainer? since I wrote the app?
[00:46] <prower> A little advice for MOTU, it'd be nice if you provided some warning -before- breaking a ton of software on your own users... :P
[00:46] <ScottK> mmmiiikkkeee: No, you make Ubuntu Developers the maintainer
[00:46] <TheMuso> prower: Its generally because Debian also removes software, so we follow their lead.
[00:47] <prower> TheMuso: Even if it's to the detriment of your end users?
[00:47] <ScottK> prower: It's a pretty ancient GCC version.  Indefinitely maintaining ancient stuff is really not feasible.
[00:47] <prower> ScottK: Well obviously, yes :> It's not really feasible to run a lot of the stuff that I've bought now either
[00:47] <prower> Hence the problem
[00:48] <ScottK> prower: It's very within the power of these closed source vendors to user more recent GCC.  You're pointing your anger in the wrong direction.
[00:48] <ScottK> prower: It's also equally possible to stay with an older Ubuntu version too.  Hardy is supported on the desktop for another 18 months.
[00:48] <prower> ScottK: You're right...I should approach the manufacturer of every individual piece of software that I own and ask them to recompile their binaries, that's much more convenient? Thanks for the "help" :P
[00:49] <ScottK> If he comes back, someone might mention this is one reason not to use closed source stuff.
[00:49] <directhex> shall i summon the whaaambulance?
[00:49] <ajmitch> directhex: it's obviously mono's fault
[00:49] <directhex> ajmitch, bloody patents :(
[00:50] <TheMuso> ScottK: Whats also interesting, is that c++ stuff seems to be affected more so than c, since it needs extra libs. I could be wrong however.
[00:50] <ScottK> Yes, it does.  Not sure why.
[00:50] <ajmitch> symbol mangling changes
[00:51] <mmmiiikkkeee> ScottK: Ok, thanks; I just put "Ubuntu Developers" in the field or I need to specify a specific person? sorry for the confusion(I am new to all of this...)
[00:51] <directhex> yeah. c++ has always been fragile with its symbols
[00:51] <directhex> consider how many times there have been "c102" or "c2" appends onto package names, to cope with broken APIs from C++ tomfoolery
[00:52] <directhex> t'is simply fragile
[00:52] <ajmitch> at least we don't generally have to worry about libc5 :)
[00:52] <TheMuso> ajmitch: heh
[00:53] <TheMuso> directhex: If I was a proprietary software vendor looking to write for Linux, unless my project really needed to use c++, then using c would be much more appealing.
[00:53] <TheMuso> Due to c++ fragility.
[00:53] <ajmitch> it would be nice to be able to have libstdc++5 still lying around without needing the full gcc-3.3 source in the repository
[00:53] <directhex> TheMuso, i think it happens a fair bit with games
[00:54] <ajmitch> windows is so much better at binary compatibility than linux :)
[00:54] <TheMuso> directhex: I'll bet.
[01:01] <TheMuso> ajmitch: One thing that probably needs to be improved in Linux. Sure its better to use open source, but the fact is that there are some things that will remain proprietary and be made available for Linux.
[01:03] <ajmitch> TheMuso: I don't know how easy it'd be to have libstdc++5 kept around & still buildable from source, without carrying all of gcc-3.3 indefinitely
[01:36] <TheMuso> ajmitch: I am not referring to libstdc++5 specifically.
[01:36] <TheMuso> ajmitch: I do agree though.
[01:36] <ajmitch> no, it's just one of the common cases
[01:36] <ajmitch> we don't want to go out of our way to make it hard for people who still need to use proprietary software
[01:37] <TheMuso> yep
[01:37] <fcuk112> what is the difference between "closes" and "LP" when updating the changelog?
[01:37] <ajmitch> "Closes: #123456" is what debian will pick up
[01:38] <ajmitch> LP: #123435 is the equivalent for closing a bug in launchpad
[01:39] <fcuk112> i see, can you do (LP: #12345, #12344) to close 2 bugs simultaneously?
[01:39] <jdong> you need LP: #12345, LP: 12344
[01:39] <fcuk112> ok cool thanks.
[01:51] <jdong> what's our opinion on APSL?
[01:51] <jdong> the same as the DFSG's?
[01:51] <jdong> http://lists.debian.org/debian-legal/2001/09/msg00103.html
[01:51] <ajmitch> that is from 8 years ago, too
[01:52] <jdong> ajmitch: yeah; I was wondering what's the feasiability of Apple's diskdev-cmds in Universe
[01:52] <jdong> (giving us an effective fsck_hfs for iPod and such owners)
[01:52] <ajmitch> what version of the APSL?
[01:53] <ajmitch> since even the FSF considers 2.0 a free software licence
[01:54] <jdong> version 2.0
[01:57] <ajmitch> 2.0 seems to have different wording around the problematic section there
[01:58] <jdong> *nods*
[01:58] <ajmitch> ask the ubuntu ftpmasters :)
[01:59] <ajmitch> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302462 seems to indicate that debian consider the APSL 2.0 to not be considered a free licence under the DFSG
[02:12] <ScottK> jdong: Link to the license?
[02:12] <jdong> http://www.opensource.apple.com/source/diskdev_cmds/diskdev_cmds-491/APPLE_LICENSE
[02:27] <ScottK> jdong: I think it's OK for multiverse for sure.
[02:28] <ScottK> It may be OK for Universe/Main, but I'd have to think about it.
[02:28] <ScottK> The notion that a requirement to provide source makes a license non-free is at the very least odd.
[03:00] <nhandler> It appears that merges.ubuntu.com is now up
[03:01] <nhandler> Maybe I spoke too soon. It looks like only the /main.html listing is currently up.
[03:11] <wgrant> nhandler: See Keybuk's recent statements in #-devel
[03:11] <wgrant> nhandler: universe is some days away.
[03:13] <nhandler> Thanks wgrant. I think I'll just sift through my old emails to try and get some of my merges taken care of
[04:09] <ScottK> See u-d-a for merging via bzr
[05:10] <wrapster> even though i've changed the version of a pkg and uploaded it a repo when i run upgrade i see that there is 0 pkg installed and 0 removed..
[05:11] <wrapster> why and how is that possible?
[05:22] <wgrant> wrapster: "a repo" being a PPA?
[06:01] <wrapster> wgrant: when i do an upgrade libnspr4 is said that its kept back.. But i want to update that particular pkg itself... any idea why it may say so?
[06:01] <wrapster> wgrant: and to your earlier question was... That i had goofed up a few things.. my mistake resolved taht one.
[06:01] <wrapster> that*
[06:23] <_ruben> wrapster: most common reason for packages to be kept back during upgrade is that the package in question depends on a new (not yet installed) package
[06:47] <Edwin_ach> Hi everybody out, it is a nice work what are you doing for Ubuntu distro...
[06:52] <Edwin_ach> I was reading short interviews to MOTU members and their words make me feel confidence to want to get involved helping out with this project, for the moment I will have to read the wiki and then dive into! :D
[06:53] <ScottK> Edwin_ach: Welcome.
[06:54] <Edwin_ach> thanks ScottK! :)
[06:54] <jmarsden> Edwin_ach: https://wiki.ubuntu.com/MOTU/GettingStarted is a good starting page for wiki reading about what MOTUs do and how you can do it too.
[06:55] <Edwin_ach> ScottK, I am feel happy to know anyone can help and become an active contributor to enhance Ubuntu distro!
[06:56] <Edwin_ach> thank you ScottK, I will read the GettingStarted guide
[07:03] <\sh> moins
[07:04] <ScottK> Good morning \sh.
[07:04] <micahg> hi \sh
[07:04] <demongt> how do i get youtube video's to work?
[07:04] <micahg> \sh: I copied zend fw in the ppa from hardy to karmic
[07:04] <micahg> demongt: check in #ubuntu for support
[07:04] <\sh> micahg, hey...I just pushed a new dojo upstream to my PPA...if you want to have a look at it :)
[07:04] <micahg> or #ubuntu-mozillateam
[07:05] <micahg> \sh: did you have to push the stuff in the ppa or were you able to copy it
[07:06] <\sh> micahg, I uploaded the versions for zf into the zf ppa...
[07:06] <micahg> ok
[07:06] <\sh> micahg, ScottK will approve official backports for the next releases...
[07:06] <micahg> oh, that's great
[07:06] <micahg> although, I don't know if we should
[07:07] <micahg> well, to karmic would be fine
[07:07] <\sh> micahg, zf is harmless...a good package for backporting
[07:07] <micahg> \sh: not for people using it in production :)
[07:07] <\sh> micahg, tbh..people using ubuntu in production don't use backports (at least me ;))
[07:08] <\sh> but zf needs to be always the latest..regarding our zf devs
[07:08] <micahg> I guess it's ok, as backports by default has a priority of 1
[07:08] <\sh> micahg, btw..if you have time and pleasure, debian is still waiting for our packages of zf on mentors...if you want, please jump on that wagon and push it into debian :)
[07:09] <micahg> \sh: time is something I'm short on this month
[07:10] <micahg> \sh: btw, there's a proposal in debian for dojo to be called libjs-dojo
[07:10] <micahg> maybe your idea is better though
[07:10] <\sh> micahg, yes...we need to change the package names...as said, my dojo package was just the first shot to try it out..it needs more love to make it rocking
[07:11] <micahg> ok
[07:11] <micahg> well, if you want to make a blueprint of what's required, I can probably get to it at some point before Lucid
[07:11] <\sh> micahg, the package split in dojo-core, dojo-dijit and dojo-dojox makes sense, because it's just like jquery and jquery-ui ... three different functionalities
[07:12] <\sh> micahg, whats really missing is the java js foo which needs separate packaging, because there is also a separate source...it needs to be removed from the dojo-src tarball when preparing the orig.tar.gz
[07:13] <\sh> (which I don't do right now)
[07:13] <Edwin_ach> ScottK, I was reading in the GettingStarted guide that MOTU are the people dealing with packaging... (it's sound great) but actually I have not enough experience in programming.... :S
[07:13] <\sh> but the real crazyness of dojo are the licenses...we need to be careful about that
[07:13] <ScottK> Edwin_ach: very little actual programming experience is needed.
[07:14] <Edwin_ach> ScottK, I learned programming in C++some years ago, but by the slack of practice I am not feel confident to help in that area...
[07:15] <ScottK> Edwin_ach: If you can do some basic shell scripting then you know enough.
[07:15] <ScottK> If you know more, there's more you can do, but I'm not much of a programmer either
[07:16] <micahg> \sh: is that it, just gather the licenses and clean the orig.tar.gz?
[07:16] <Edwin_ach> ScottK, maybe very basic shell scripting, I'm still in the learning process :p
[07:16] <ScottK> That's fine.
[07:17] <ScottK> That's about where I was when I started
[07:17] <Edwin_ach> if you are not programming ScottK, what do you do? (sorry for that question :$)
[07:18] <ScottK> Packaging is mostly about integrating upstream software into the Debian style package system that we use.
[07:18] <\sh> micahg, it's one of the things still to do ... as said, there is this "shrinksafe" tool, which needs to be packaged as standalone
[07:18] <ScottK> Most of that is shell and make and most of the make stuff is reasonably stylized and reusable.
[07:19] <ScottK> So programming doesn't really enter into it.
[07:19] <ScottK> Those here that are good programmers also get into fixing bugs found in the packages too, but there is plenty of pure packaging work it's not essential
[07:24] <Edwin_ach> ScottK, it sounds good... then, it is a nice chance to focus my efforts on learning shell scripting instead of specific language programming!!!
[07:25] <Edwin_ach> although I remember programming is too fun! :D
[07:25] <jmarsden> Edwin_ach: There are descriptions and examples of the packaging process in the Packaging Guide which will help you get a feel for the kind of work that is involved: https://wiki.ubuntu.com/PackagingGuide/Complete
[07:29] <Edwin_ach> thank you jmarsden, I will read that guide too (I have plenty of material to read to begin getting involved! :) )
[07:29] <jmarsden> Yes, there's no shortage of reading material :)
[07:32] <Edwin_ach> yes, there are a lot of links in the GettingStarted and PackagingGuide/Complete that will be useful :)
[07:33] <Edwin_ach> thank you jmarsden & ScottK for the links
[07:34] <Edwin_ach> I will have beginning to read (and sleep a little too, since in Central America is 1:35am XD )
[07:36] <Edwin_ach> thanks in advance guys for your useful help!!!
[07:41] <slytherin> If DVD is not auto mounting, which package is at fault in karmic?
[07:50] <stochastic> is there any way to tell why a package is in multiverse?
[07:50] <stochastic> * rather than universe
[07:50] <Elbrus> stochastic: usually the license
[07:50] <Elbrus> or that of it rdepends
[07:51]  * Elbrus thinks
[07:51] <stochastic> hmm, must be its rdepends
[07:54] <slytherin> stochastic: not rdepends, but build or runtime depends
[07:54] <slytherin> stochastic: which package is it by the way?
[07:54] <stochastic> Elbrus, http://packages.ubuntu.com/karmic/xjadeo
[07:55] <stochastic> sorry, slytherin, http://packages.ubuntu.com/karmic/xjadeo
[07:55] <stochastic> is it because of the "or" in the control file?
[07:56] <siretart`> morning
[07:58] <slytherin> stochastic: in this case probably because it recommends mencoder and transcode. Both of them are in multiverse.
[08:01] <stochastic> slytherin, so a recommends can be enough to put something into multiverse?  interesting.
[08:02] <slytherin> stochastic: AFAIK, yes
[08:02] <slytherin> stochastic: since recommends are installed by default
[08:03] <stochastic> oh yeah, I forgot about that
[08:03] <jmarsden> It might be worth turning them into Suggests: and moving it to universe, if that is the only reason for it being in multiverse?
[08:03] <stochastic> jmarsden, good idea.
[08:05] <stochastic> Is there a method to determine why a package is installed on a system?
[08:06] <Elbrus> you mean, as in if it was manually installed or due to a dependency?
[08:07] <Elbrus> the answer to that is yes, but I don't now how exactly
[08:07] <Elbrus> look for dkpg I think
[08:07] <jmarsden> stochastic: aptitude why
[08:08] <stochastic> jmarsden I'd like to find out which program installed ttf-mscorefonts-installer
[08:08] <jmarsden> stochastic: What does aptitude why ttf-mscorefonts-installer   say ?
[08:09] <jmarsden> My guess would be gnumeric
[08:10] <stochastic> jmarsden, ubuntu-restricted-extras
[08:11] <stochastic> thanks, that's the info I needed.
[08:11] <jmarsden> No problem.
[08:25] <siretart`> slytherin: IMO we should promote mencoder and transcode to universe,
[08:25] <siretart`> though. at least in mplayer, there is no 'non-free' piece in it.
[08:26] <siretart`> haven't checked transcode, but I don't expect anything evil there as well
[08:26] <slytherin> siretart`: I think it is more about the patented codecs that mencoder or trancode allows you to use. But I am no expert in that regard.
[08:28] <\sh> so..done with my merges
[08:28] <siretart`> slytherin: you might note that we already promoted x264 and
[08:28] <siretart`> vlc. patents are no longer reason for multiverse. only licensing matters
[08:28] <\sh> transcode uses patented codecs? I thought it's using whats ffmpeg and mencode delivers
[08:29] <siretart`> IIRC transcode implements many encoders itself
[08:29] <siretart`> err, s/encoders/muxers/
[08:30] <\sh> which is a different story ;)
[08:30] <siretart`> not really
[08:30] <siretart`> avi is patented as well AFAIUI
[08:34] <\sh> siretart, you mean avi container
[08:41] <twisted_> someone say something entertaining
[08:44] <dholbach> good morning
[08:44] <twisted_> morning
[08:45] <slytherin> twisted_: Your name looks twisted. :-P
[08:46] <twisted_> got the nickname in the army,   melted the barrel of my rifle on accident, it  was twisted and bent
[08:46] <echol> good afternoon
[08:47] <echol> How to join MOTU?
[08:48] <tsimpson> echol: see https://wiki.ubuntu.com/MOTU/GettingStarted
[08:48]  * Laney stretches
[08:49] <Laney> morning folks
[08:50] <echol> I am here PM
[08:50] <echol> China
[08:50]  * slytherin is glad MoM is back.
[08:50] <echol> 2009年 11月 06日 星期五 16:50:43 CST
[09:35] <\sh> hmm...something broke the planet...noupdates (even jono has written two new articles)
[09:48] <av`> ScottK, nicotine was uploaded to lucid already, you should be able to process the SRU now :)
[09:49] <av`> slytherin, use the brand new bzr merge thing instead of mom now!
[09:50] <slytherin> av`: I am not comfortable with DVCS. I still love svn.
[09:50] <av`> oh ok then :) thought you didnt know about that
[09:51] <slytherin> av`: I didn't and the reason is that I don't use bzr. :-)
[09:51] <av`> fine, then :)
[09:57] <siretart`> \sh: yes.
[10:25] <hyperqbe> Newbie Q: Is there a reason why the output of debdiff would not include my changes to debian/changelog?
[10:26] <Laney> you didn't do them
[10:26] <Laney> you didn't build the source package
[10:26] <Laney> you are debdiffing against the wrong thing
[10:26] <hyperqbe> good answers... i double checked the first two
[10:26] <hyperqbe> let me triple check.
[10:27] <slytherin> dtchen: is there any known issue about cracking sound with pulseaudio on powerpc ?
[10:30] <hyperqbe> Laney, thanks... I was indeed debdiffing the wrong thing.  When I added the changelog entry, it had a new name for the .dsc file
[10:34] <slytherin> NCommander: ping
[10:34] <NCommander> slytherin, png
[10:35]  * Laney is going to upload ubuntu-dev-tools
[10:35] <slytherin> NCommander: Do you by any chance remember the kernel panic issue (discussed long time back) with b43/rfkill combination on powerpc?
[10:36] <NCommander> slytherin, no
[10:36] <slytherin> NCommander: Ok. The issue is more severe now. :-( bug 476154
[10:37] <NCommander> ugh
[10:37] <NCommander> slytherin, I still can't reproduce. ENOB43
[10:44] <Laney> geser: any reason not to upload udt?
[10:45] <slytherin> NCommander: I am glad that you can't reproduce it. Believe me, it is very irritating.
[10:46] <NCommander> slytherin, no, if I could< I would do something about it >.<;
[10:47] <slytherin> I am wondering how much of this is caused by rfkill rewrite in .31 kernel
[10:48] <slytherin> I will also try changing firmware to http://www.ing.unibs.it/openfwwf/
[10:50] <slytherin> looks like I will need to version of firmware. http://wireless.kernel.org/en/users/Drivers/b43#firmware
[10:52] <hyperqbe> I was investigating a bug and found that there was a Debian bug for the same thing.  Should I do anything other than put a comment pointing to the debian bug?
[10:54] <Laney> geser: uploaded now ;)
[11:25] <gomersion> 5
[12:35] <wrapster> if i say apt-cache show <pkg A> then it will look at the source.lst and pull in the info from there right?
[12:35] <wrapster> its a very intriguing scenario here.. thats y asking you people...
[12:40] <joaopinto> wrapster, no, apt-cache will look at yout current apt cache, which is not related to the curent source.lst state
[12:41] <joaopinto> source.list is used during the cache update process, using apt-get update
[12:41] <wrapster> oh...
[12:42] <wrapster> joaopinto: where would the current apt-cache be located..
[12:42] <wrapster> var/cache/apt/archives ?
[12:54] <slytherin> wrapster: /var/lib/apt/lists/
[12:57] <wrapster> slytherin: if you dont mind.. could you pls explain to me, who/ how its written... coz i see differnt entries of it on 2 separate machine that im working on.. and its causing major issues...
[13:01] <joaopinto> wrapster, what problem are you experiencing ?
[13:02] <joaopinto> if you want to learn about apt tou could check the source :)
[13:02] <wrapster> joaopinto: http://pastie.org/686341
[13:03] <wrapster> before the .... is from one machine and after the .... is from another machine..
[13:03] <wrapster> there is huge diff... and how is it?
[13:03] <joaopinto> wrapster, apt-cache policy package
[13:04] <joaopinto> the different is that you have different versions available for the same package on one of the machines
[13:04] <joaopinto> difference
[13:08] <wrapster> joaopinto: yeah i know that.. I had to make a few mods so bumped the version no...
[13:08] <wrapster> but now eventhough the pkg is installed ... i cant see its effect..
[13:08] <wrapster> one moment pls ill do a pastie ...
[13:08] <joaopinto> wrapster, so what is your doubt about the differences ?
[13:08] <joaopinto> on the first machine, you have nexenta1 installed, and nexenta2 available
[13:09] <joaopinto> on the other machine, you have only nexenta3 available
[13:10] <wrapster> joaopinto: http://pastie.org/686374
[13:11] <joaopinto> wrapster, why was the package expected to be listed if is not installed ?
[13:11] <wrapster> and apart from bumping the version there were no changes made to that pkg as a whole at all..
[13:11] <wrapster> it is installed.. you do see libnspr4-dev right...
[13:11] <wrapster> in the latest pastie
[13:12] <joaopinto> wrapster, dpkg -L libnspr4 | grep  nspr.h
[13:12] <joaopinto> ops,.. -dev
[13:13] <wrapster> ok.
[13:14] <wrapster> ah.. I can see it present in one pkg while not in the other...
[13:14] <wrapster> how is that possible?
[13:14] <wrapster> playing around with the source?
[13:15] <wrapster> but surprisingly.. I was the one who built /installed these pkgs.. on both machines.... it really worked
[13:16] <joaopinto> wrapster, you are doing some trivial mistake with your package management, nothing we can help you with, just get out of the computer, get some fresh air, it will look fine when you come back :)
[13:16] <wrapster> hee hee...
[13:17] <wrapster> ok thanks for the advice.. at least happy to know its a trival issue... :)
[13:17] <wrapster> hope trivial wont torment me :p
[13:19] <slytherin> wrapster: dpkg -S needs full path of the file
[13:22] <jpds> Of you could just use apt-file.
[13:51] <joaopinto> slytherin, dpkg -S does work with a filename
[14:08] <geser> Laney: thanks for doing the upload
[14:08] <Laney> np
[14:08] <Laney> how do we do the SRU?
[14:08] <Laney> just the whole thing?
[14:09] <geser> I just wanted to pick the changes to change the default (less testing for possible regressions)
[14:09] <Elbrus> hyperair: you were fast with bug 476333 thanks
[14:09] <Laney> makes sense
[14:11] <ttx> I'm trying to run "bzr mark-uploaded" after uploading a merge and before doing the "bzr push", but I get "bzr: ERROR: Unknown target distribution: lucid"
[14:11] <ttx> anyone else tried to do merges following DistributedDevelopment ?
[14:12] <hyperair> Elbrus: np
[14:12] <hyperair> Elbrus: actually i should change it back to inprogress. i found more xterm references.
[14:23] <ScottK> av`: pitti took care of it.  In future, please make sure to close the bug on the changelog so the status is clear.
[14:23] <av`> ScottK, yes, forget to add that on the lucid task :)
[14:25] <falktx> aynone can tell me what is the fastest way to create man pages?
[14:25] <falktx> are there tools for that?
[14:25] <falktx> or just need to write the full thing manually?
[14:32] <randomaction> falktx: help2man
[14:33] <falktx> will try that
[14:35] <randomaction> but writing by hand is not too hard imo
[14:37] <falktx> i hope it doesn't
[14:37] <falktx> the only thing i've left to do in my package is the manpages
[14:38] <falktx> I don't really need to create a man page for *all* binaries in my package, do I?
[14:38] <falktx> (for revu)
[14:39] <joaopinto> afaik manpages are not required but recommended
[14:45] <mdomsch> does anyone here know what software ubuntu uses for their ipv6 torrent tracker?
[14:46] <mdomsch> perhaps opentracker built for ipv6?
[14:46] <slytherin> falktx: manpages are recommended not a requirement
[14:51] <falktx> ok
[14:52] <falktx> i'll write the most important ones
[15:08] <falktx> can i use something like man --page=/path
[15:08] <falktx> ?
[15:10] <pochu> you can do man ./foo.1
[15:10] <falktx> lol
[15:10] <falktx> that simple...
[15:12] <randomaction> What do different colours mean in MoM?
[15:13] <JonyBlaze> i have a program that I would like to package but it doesnt install itself to /usr/bin what would be the best way to fix that?
[15:13] <echol> night
[15:14] <slytherin> JonyBlaze: Where does it install?
[15:14] <JonyBlaze> it just leaves it in the source dir
[15:14] <echol> shell?
[15:15] <slytherin> JonyBlaze: what program is it?
[15:15] <JonyBlaze> where it gets built
[15:15] <slytherin> JonyBlaze: and what build system does it use?
[15:15] <JonyBlaze> QT
[15:15] <JonyBlaze> http://code.google.com/p/pep8-1/
[15:15] <gomersion> Hi all. I have recently posted a bug report here on launchpad. I have subsequently seen that the packe I referred to "is not linked to an upstream package". Does anyone know how, or what the criteria are for a package to be linked to upstream? The bug ref is: https://bugs.launchpad.net/ubuntu/+source/smbldap-tools/+bug/476361
[15:16] <slytherin> JonyBlaze: QT is a toolkit. I am asking about build system like make, cmake, ant etc.
[15:17] <JonyBlaze> slytherin: well it uses qmake
[15:17] <JonyBlaze> slytherin: to make a makefile, then you use make to build it
[15:17] <wrapster> even though i have libc.so.1 present in /usr/lib...
[15:18] <slytherin> JonyBlaze: then doesn't it have a install target, something like qmake install
[15:18] <wrapster> Why is it that i get an error like this "dh_shlibdeps -l/usr/lib:/lib;;;;;;;;dpkg-shlibdeps: failure: couldn't find library libc.so.1 needed by debian/libnspr4-0d/usr/lib/libplds4.so.0d (its RPATH is '/usr/lib').
[15:18] <wrapster> "
[15:18] <JonyBlaze> slytherin: it doesnt, i cant change that but would the created package know how to uninstall it?
[15:20] <slytherin> JonyBlaze: then in that case you can simply what files to put where in debian/install file.
[15:23] <JonyBlaze> slytherin: ok, I also want to have it make a menu entry and an icon so that is where I would put those as well I take it
[15:25] <slytherin> JonyBlaze: right, provided you have them already.
[15:25] <JonyBlaze> slytherin: right
[15:25] <JonyBlaze> slytherin: thank you for the help
[15:29] <slytherin> welcome
[16:07] <JonyBlaze> what debian/install file :)
[16:07] <JonyBlaze> ive been had
[16:07] <JonyBlaze> lol
[17:43] <pmcenery> lbrinkma: I see you updated 476361
[17:43] <fabrice_sp> bug #476361
[17:44] <pmcenery> Have you somehow linked it to upstream now?
[17:44] <pmcenery> Sorry... do you have to put a # in front of the bug number to get it to automatically come up
[17:44] <fabrice_sp> you have to put bug :-)
[17:45] <pmcenery> thanks. will do so in future
[17:45] <falktx> ayone available for a final revu?
[17:45] <falktx> http://revu.ubuntuwire.com/p/qtsixa
[17:47] <RainCT> wow, nano now has syntax highlight for source.list \o/
[17:47] <lbrinkma> pmcenery, i had found the upstream bug tracker, but i don't linked it, because the package is alredy building
[18:03] <bdrung> bigon: did you upload gajim to karmic-proposed?
[18:04] <pmcenery> lbrinkma: How if you dont mind... do you (a) get some package to build like you did there, and (b) how do you "link" a package to upstream so its automatically pulled in?
[18:08] <lbrinkma> pmcenery: i don't know what you?
[18:10] <pmcenery> lbrinkma: I am just interested in the process of how that package build was not "activated" if you like, seeing as it has not been building up to now.
[18:11] <pmcenery> lbrinkma: but now it has been set to build. Was that something you had to initiate?
[18:12] <lbrinkma> pmcenery: now i understand
[18:13] <lbrinkma> pmcenery: does this answer your question: https://help.launchpad.net/Packaging/BuildScores
[18:22] <pmcenery> lbrinkma: Partly. Did you upload a new package, presumably from the latest debian source package?
[18:38] <bigon> bdrung_: not yet (for gajum upload)
[19:03] <bdrung_> bigon: when will you do it? or should i do it?
[19:34] <JonyBlaze> anyone know of a very simple qt program in the repos that i can look at as an example to try a figure out how to package an app?
[19:55] <RoAk> heya guys anyoine has a link that shows how to use pbuilder-dist?
[20:02] <c_korn> can I add an argument to cmake using dh7 without needing to override dh_auto_configure ?
[20:07] <RoAk> RainCT, what did I do wrong: http://pastebin.ubuntu.com/311792/
[20:08] <RainCT> RoAk: try with just "pbuilder-dist karmic create"
[20:10] <RoAk> RainCT, and how would I be able to add the repos for universe/multiverse?
[20:10] <RainCT> RoAk: should be in there by default
[20:10] <RoAk> RainCT, ok awesome. Thansk a lot :)
[20:11] <sebner> Roak: else just edit pbuilder.rc and add COMPOMENTS="main restricted multiverse universe"
[20:12] <RoAk> sebner, ok will do if it's not default :) thanks for the tip
[20:21] <Laney> .pbuilderrc isn't it?
[20:22] <c_korn> does aclocal generate wrong code ? http://pastebin.com/d1f02d21c
[20:24] <RainCT> right
[20:25]  * Laney nibbles
[20:28] <sebner> and COMPONENTS rather than COMPOMENTS *gg*
[20:28] <sebner> c_korn: did you patch configure or the makefiles?
[20:29] <c_korn> sebner: I just created them using the autogen.sh http://pastebin.com/d662a3e3a
[20:30] <sebner> c_korn: post the configure line which fails (and some lines above and below)
[20:30] <c_korn> line 8: http://pastebin.com/d2b3ff4c6
[20:31] <sebner> c_korn: failure found: fiif should rather be fi and if. don't you think so?
[20:32] <c_korn> of course. but why does aclocal do that ? a bug ? this is the configure.ac http://pastebin.com/d556b3aaa
[20:33] <directhex> poor MTecknology
[20:36] <sebner> c_korn: wondering too, I'm not really an autofoo expert myself :\
[20:37] <c_korn> I found this Debian bug where the error also occured but I don't see how it has been fixed. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543082
[20:39] <sebner> c_korn: if there is no patch or anything visible in rules it might have been fixed upstream (svn)
[20:55] <Hrun> hi, i downloaded a source package, but the owner is root... how can i build it as myself?
[21:00] <fabrice_sp__> Hrun, did you used apt-get source to retrieve the source?
[21:01] <jdong> Hrun: more importantly, did you use sudo apt-get source instead of using apt-get source?
[21:02] <ScottK> Hrun: Don't download it as root (apt-get source, not sudo apt-get source)
[21:02] <jdong> *grins* 3 variants of the same answer
[21:02] <fabrice_sp__> lol
[21:03] <Hrun> i did a sudo apt indeed, i think i copy/paste it from the wiki. i'll get it as myself instead. how do i remove the source? just rm, because i could not find a apt-get remove source command.
[21:03] <jdong> just rm -rf the directory that it unpacked
[21:04] <ScottK> Hrun: What wiki
[21:04] <jdong> and the associated files.
[21:04] <ScottK> (with sudo)
[21:04] <jdong> and yeah, the wiki should be corrected if it says to sudo apt-get source
[21:04] <ScottK> Be very careful with sudo rm -rf
[21:04] <Hrun> :)
[21:06]  * jdong gets ready to migrate his build-ish server to btrfs
[21:06] <jdong> XFS you served me well for the past 4 years, but your rm -rf performance sucks.
[21:15] <lfaraone> Can I put in a sync request for a stable release? (ie sync a patch applied in debian to karmic, when no other changes have been made to the package)
[21:16] <ScottK> lfaraone: No.
[21:16] <ScottK> You need to get it into Lucid first (sync that) and then do an SRU
[21:16] <lfaraone> ScottK: ah, okay.
[21:16] <lfaraone> Hm. Maybe the requestsync tool should warn somebody about that before they submit a report...
[21:16]  * lfaraone goes off to implement a feature.
[21:23] <RoAk> has anyone created a lucid pbuilder without any problem yet?
[21:26] <mok0> RoAk:  I've made an sbuilder without problems
[21:30] <RoAk> mok0, any ideas of how I would troubleshoot and error in the creation that tells me to run 'apt-get -f install' ?
[22:30] <maxb> What determines whether a package has package branches yet?
[22:30] <maxb> e.g. python-defaults doesn't
[22:48] <serialorder_> do people have a quick way to grab a package source from the debian repositories ?
[22:49] <sebner> serialorder_: pull-debian-source foobar
[22:49] <serialorder_> apt-get source is nice and easy for ubuntu package source, is there something similar that works for debian?
[22:50] <serialorder_> awesome! thanks
[23:18] <MTecknology> directhex: hm?
[23:19] <directhex> MTecknology, i sense frustration in your "please stop replying :(" responses to the eleventeen million duplicates of the nspluginwrapper/GDK_NATIVE_WINDOWS bug
[23:22] <MTecknology> directhex: no frustration when I sent it; just tacked a message on the duplicated - they should have had a message added when they were filed anyway
[23:23] <jdong> I think setting GDK_NATIVE_WINDOWS=1 fixes it. I'll open up a new bug!
[23:23] <jdong> (hahaha *DUCKS*)
[23:25] <Amaranth> jdong: I kill you
[23:25] <MTecknology> jdong: it's not me you need to fear ;) ^^
[23:25] <Amaranth> Everyone keeps blaming compiz :(
[23:25] <jdong> obviously not!
[23:25] <Amaranth> Maybe I should explain passive X grabs to them
[23:25] <jdong> Amaranth: oh I've been meaning to ask you.. Compiz is making pbuilder slow.
[23:25] <Amaranth> s/X/X input/
[23:25] <jdong> hahaha now you' re goona kill me for real
[23:26] <Amaranth> jdong: Wha?
[23:26]  * Amaranth gets the bat
[23:26] <JonyBlaze> if I send a package to my ppa and it fails to build then i delete it and fix the problem why does it say its already accepted and I have to change the version
[23:26] <JonyBlaze> before i can upload it
[23:26] <Amaranth> JonyBlaze: It keeps a record of everything uploaded, deleted or not
[23:27] <Amaranth> I wonder if that's per-PPA or global...
[23:27] <jdong> per-ppa
[23:27] <JonyBlaze> Amaranth: but it failed to build
[23:27] <Amaranth> JonyBlaze: But you uploaded it
[23:27] <jdong> sources exist even if the binaries don't build
[23:27] <Amaranth> JonyBlaze: Once you upload something you can't use that version again no matter what
[23:28] <jdong> and not just can't... really you shouldn't even if you can.
[23:29] <JonyBlaze> Amaranth: ok thanks, it failed because I capitalized the o in Optional >.<
[23:29] <Amaranth> ouch, I hate it when I make silly mistakes like that
[23:29] <Amaranth> Then everyone knows because you've got a ~ppa6 version on the end
[23:29] <JonyBlaze> (in the control file)
[23:29] <JonyBlaze> lol
[23:29] <jdong> lol
[23:29] <jdong> I've gotten higher before ;-)
[23:29] <Amaranth> (I used to actually end up with that many mistakes when doing manual compiz backports)
[23:29] <jdong> but fortunately, in private repos
[23:30] <Amaranth> But I made the same mistakes every single update which was the most frustrating
[23:30] <MTecknology> Amaranth: compiz iz make aptitude sloe
[23:30]  * Amaranth uses the bat
[23:30] <MTecknology> lol
[23:30]  * Amaranth pokes at launchpad
[23:30] <jdong> compiz is making my videos blue!
[23:30] <Amaranth> Come on, update the bug title, you know you want to
[23:30] <jdong> (haha I think that's actually a real bug)
[23:30] <Amaranth> jdong: That has happened :/
[23:30] <jdong> (though it's not compizs fault)
[23:31] <Amaranth> Nope, silly bug in the Xv support in the driver
[23:31] <jdong> indeed
[23:31] <Amaranth> overlay Xv still does weird things to compiz
[23:31] <jdong> but haha boy does that sound like a plausible bug!
[23:31] <jdong> it's almost like telling keybuk that your bootup is hanging :)
[23:32] <MTecknology> Can we make a tutorial process that people need to follow before contributing to any part of Launchpad? Example: create account; go through a tutorial before handling bugs; test; they can deal with bugs..... same thing w/ translations and everything else. Nothing hard, just a 10min process or something
[23:46]  * jdong has some trouble following but 223825
[23:49] <ScottK> MTecknology: #launchpad-dev
[23:49] <MTecknology> ScottK: I was only joking
[23:58]  * jdong goes through the hundred odd motu-sru bug tickets