[00:02] <dholbach> haha, nice REVU bug: http://revu.ubuntuwire.com/p/zope.index will get the "index" removed from the URL
[00:24] <StevenK> geser: Killed.
[00:25] <ari-tczew> can we sync nonfree -> multiverse ?
[00:29] <geser> StevenK: thanks
[00:32] <persia> ari-tczew: Sometimes, and usually.
[00:33] <persia> More specifically, check the license against ubuntu-policy
[00:38] <Dabian> This is a user question, I guess, but maybe it will end up in a bug report.
[00:38] <Dabian> I am sitting in my arm chair, ready to watch a DVD.  Turns out its encrypted.
[00:38] <Dabian> I installed libdvdread4, and sudo'ed the script ...
[00:38] <Dabian> But it still doesn't work.
[00:39] <Dabian> What is wrong?
[00:40] <Dabian> (I tried playing the dvd with xine, vlc and mythtv)
[00:40] <Dabian> (VLC might have the configuration messed up though)
[00:41] <persia> Dabian: You may find that you can get an answer in #ubuntu
[00:41] <Dabian> What say you?  No idea, or its broken?
[00:41] <Dabian> persia: I thought that would be the right place to ask.  Not sure why I asked here, sorry.
[00:42] <persia> Dabian: No worries.  It's just the sort of question that almost never gets answered here.
[00:43] <Dabian> persia: Thanks for pointer.
[00:45] <Dabian> Seems #Ubuntu is clueless too.
[00:46] <Dabian> The more skilled you get, the less help are you likely to get, I guess.
[00:47] <persia> Indeed.
[00:48] <Dabian> :)
[00:48] <Dabian> OK . now I am getting some response...
[00:56] <Dabian> OK .. turns out that its a limitation
[00:56] <Dabian> Ubuntu doesn't work for certain DVD's.  You have to use windows or something else.
[00:57] <Dabian> As I don't have or intend to aquire windows, I will have to watch the DVD at my parents place or similar, I guess. :|
[00:57] <Dabian> (Not that they run windows on a dvd-capable machine, but they have a television and a dvd-player)
[00:58] <Dabian> I guess thats it for GNU/Linux as "media-player".
[00:58] <sladen> Dabian: urm, I doubt it's as simple as that
[00:59] <Dabian> sladen: Well, nobody knows how to make it work.
[00:59] <Dabian> apparently.
[00:59] <sladen> Dabian: the unencryption is just a matter of software;  and hasn't changed for about 10 years
[00:59] <Dabian> sladen: I was told that some DVD's just doesn't work with ubuntu.
[00:59] <sladen> Dabian: what error message are you seeing.  Have you googled it?
[00:59] <sladen> Dabian: sounds like FUD
[01:00] <marnold> Dabian, you using libdvdcss2
[01:00] <Dabian> Not sure how I get an error message.
[01:00] <Dabian> marnold: I am using libdvdread4, and I ran the script.
[01:00] <Dabian> I guess I can fire up xine in the gnome-termial.
[01:01] <Dabian> libdvdread: Error cracking CSS key for /VIDEO_TS/VTS_02_1.VOB (0x001ff86b)!!
[01:01] <sladen> Dabian: run   vlc dvd://   or   mplayer dvd://    or   totem dvd://   or   xine dvd://   from a terminal and look at what it prints when you press play, and it doesn't
[01:01] <Dabian> Will try google that.
[01:01] <marnold> perhaps we should take this in to #ubuntu... Hold on  why are you runnin xine in gnome
[01:02] <Dabian> Why not?
[01:02] <Dabian> I guess #ubuntu would be the apropiate forum.
[01:03] <Dabian> I got some page from google that talks about "regionset"
[01:03] <persia> This really isn't the right forum :)
[01:03] <Dabian> persia: Right.
[01:04] <sladen> Dabian: from Googling on your behalf, it sounds like you probably have a region-locked DVD drive of some sort, and a DVD that doesn't match that region
[01:04] <Dabian> right ..
[01:04] <Dabian> Not something I know a lot about .. but I guess most dvd's over here are region locked.
[01:05] <Dabian> Maybe this dvd is a different region.
[01:05] <Dabian> I dunno.
[01:05] <Laney> please, if you wish to provide support, take it to some more appropriate forum
[01:05] <Dabian> I am in #ubuntu also, sorry Laney
[01:06] <marnold> oh now i remember why i'm here
[01:06] <Dabian> :)
[01:07] <sladen> Dabian: given that the DVD hardware (its firmware) is below the level of the software, then there's little the software can do about it (the DVD drive is not passing it the data).  You need to get a normal DVD drive that doesn't have unnecessary restrictions (this will apply equally in MS Windows as it does in Debian, Ubuntu, or other $distro of choice)
[01:08] <Dabian> sladen: Thanks.
[01:09] <marnold> we may have an outstanding security issue in ircd-hybrid http://www.debian.org/security/2010/dsa-1980 appears not to be fixed in lucid
[01:10] <Dabian> EF-net irc?
[01:10] <marnold> as last uploader of that package
[01:10] <marnold> i wondering what i should do
[01:11] <marnold> s/I/I'm
[01:11] <sladen> marnold: pull the packages from Debian when they're available
[01:11] <marnold> Dabian, most have switched to ratbox
[01:11] <Dabian> I guess you should contact the security team right away.
[01:12] <sladen> marnold: poke pitti or someone for help
[01:12] <marnold> sladen, this one doesn't get much active maintenance
[01:12] <persia> #ubuntu-hardened tends to be a good place to ask about security stuff.  Asking in the next 10 minutes or so is likely to be best.
[01:12] <mdeslaur> marnold: what's the issue?
[01:13] <marnold> and I'm also wondering about the wisdom of including hybrid in lucid
[01:14] <marnold> its hasn't seen much upstream development
[01:14] <sladen> marnold: have a look at popcon
[01:26] <lfaraone> jdong: I fixed bug 479131 in a 0.2 upload, but because the error occurs on package removal or reinstallation (when the service is stopped), people who have already installed the package will continue to have problems. How should I go about fixing this? (or should I just tell people to "LANG=C apt-get upgrade" first?)
[01:27] <jdong> lfaraone: ... is there no way to correct the problem without forcing people to use an oddball apt-get incantation?
[01:28] <lfaraone> jdong: well, it's a issue in the init script that has to do with internationalization.
[01:28] <Dabian> sladen: I fixed my problem with regionset!  THANK YOU! :))))
[01:28] <jdong> lfaraone: can you not call the init script from post(inst,rm) with LANG=C in that case?
[01:28] <lfaraone> jdong: the issue is not with the 0.2 version, but the broken original version in the archives.
[01:29] <jdong> lfaraone: understood, but IMO part of the responsibility of the SRU is to address that
[01:29] <jdong> or at leaset make it behave in a way that doesn't involve nasty postinst errors
[01:30] <lfaraone> jdong: okay. the package uses CDBS, so I'm not sure how I'd override what it does in the postinst/postrm.
[01:31] <jdong> sorry, I'm not currently at a machine where I can get you more specific advice
[01:32] <jdong> but with SRU hat on, from a policy standpoint I'd like for the package to cleanly upgrade affected users through the update manager / apt-get upgrade as expected
[01:32] <jdong> hopefully a volunteer idling in this channel can provide more specific assistance :)
[01:40] <ScottK> It's doable.  Let me look something up.
[01:42] <ScottK> lfaraone: See --error-handler= in man dh_installinit
[03:41] <diwic> I'm trying to debug a program crash but all I get in gdb is "Thread exited" and a SIGKILL. How can I trace down where the bug occurs?
[03:41] <diwic> If I run the program under strace, the program does not crash.
[03:49] <ScottK> Ah. A Heisnburg.  Those are tough.
[03:52] <nigel_nb> ScottK, how do I look through the source for how a particular package is being installed/uninstalled?
[03:54] <diwic> ScottK: any hints?
[03:55] <ScottK> diwic: No.  Not really, just trying to share the pain.
[03:57] <diwic> perhaps if I can put a breakpoint on thread exit, is this possible?
[03:57] <ScottK> I'm very unlikely to have any additional useful information for you.  Sorry.
[03:57] <ScottK> Off the top of my head, I'd think you'd have to know what thread.
[03:58] <kamalmostafa> diwic: I would think that the "Thread exited" is the symptom, not the cause...  The SIGKILL bears investigation though.  That's an unusual signal for a program to get unless something is explicitly sending it (that's "kill -9").  Is it possible that the program is sending *itself* the SIGKILL "intentionally"?  Does the string "SIGKILL" appear anywhere in the source?
[04:00] <kamalmostafa> diwic: ... or for that matter, does the program call kill() or raise() internally anyplace?
[04:01] <kamalmostafa> If the program were to call raise(9) for example, you'd get this effect I think.
[04:01] <diwic> SIGKILL is not present
[04:01] <diwic> raise is but not with sigkill as argument
[04:02] <kamalmostafa> diwic: what argument does it call raise() with?
[04:02] <diwic> kill is present in quite a few places
[04:02] <diwic> SIGTERM, SIGTRAP, SIGQUIT, SIGUSR1
[04:03] <crimsun> (inside gdb) info threads
[04:03] <crimsun> () thread foo
[04:03] <crimsun> () break linenum thread foo
[04:03] <crimsun> etc.
[04:04] <crimsun> busy ATM but will look in a bit
[04:04] <diwic> crimsun, so do that on all calls to kill() and raise()?
[04:04] <crimsun> (I presume this is 517902?)
[04:04] <diwic> crimsun, yes
[04:05] <diwic> bug #517902
[04:05] <kamalmostafa> diwic: You could just set a breakpoint on "kill" and another on "raise" I think -- you shouldn't need to set individual breakpoints on each call to them.
[04:06] <diwic> crimsun, I suspect that the new alsa-lib wakeup thing might be involved
[04:10] <diwic> hmm
[04:10] <diwic> got one kill breakpoint but that wasn't it, when I continued, the program didn't crash.
[04:11] <kamalmostafa> Question about version numbers:  Package 'gwp' currently shows version number (0.4.0-1.2build1) -- I want to make change to fix the FTBFS in ubuntu.  What should the next version number be?  Should it be "...build2" or "...ubuntu1" next?
[04:11] <diwic> kamalmostafa, best thing I guess would be to upstream the FTBFS
[04:12] <Takyoji> So I take it that the Basic PackagingGuide on the Ubuntu wiki is just a little dated; or?
[04:12] <diwic> kamalmostafa, if that is not possible I'd suggest ubuntu1
[04:12] <Takyoji> Because the rules file displayed is quite different from the one generated
[04:13] <Takyoji> and it refers to debhelper 5 or 6; when I think the recent release is supposedly 7
[04:13] <ScottK> kamalmostafa: ubuntu1
[04:14] <diwic> kamalmostafa, nope, now it quitted without any kill breakpoints
[04:14] <Takyoji> otherwise I'm referring to https://wiki.ubuntu.com/PackagingGuide/Basic
[04:15] <kamalmostafa> diwic: your SIGKILL problem sounds like it could be a timing related thing (since you also said that running under strace also hides the problem).   If I were in your shoes, I'd examine each kill() call in the source visually -- figure out which one might possibly send a kill(9), if any.   But this is getting pretty involved -- perhaps a different channel would be a better place to ask about this?  (which one I don't know).
[04:16] <kamalmostafa> ScottK: thank you.  Is the use of "build1" a normal thing to do (for "no change" rebuilds)?  I'd not seen that before.
[04:16] <diwic> kamalmostafa, IRL calling, got to go, thanks anyway
[04:16] <ScottK> kamalmostafa: Yes.  A build1 build will got overwritten by autosync.
[04:17] <kamalmostafa> diwic: good luck!
[04:17] <kamalmostafa> Scottk: Ah, okay, that makes perfect sense.  thanks.
[05:04] <nigel_nb> hggdh, will you be awake for some more time?
[05:23] <hggdh> nigel_nb: not for long, no
[05:23] <hggdh> why?
[05:23] <nigel_nb> hggdh, I wanted to make sense of debian/rules
[05:24] <hggdh> oh
[05:24] <nigel_nb> (which is why I'm pining here)
[05:24] <hggdh> nigel_nb: unfortunately this is pretty much it for me this night, sorry. But we can do it later
[05:24] <jmarsden> nigel_nb: Why would someone else's wakefulness (or otherwise) affect *your* ability to make sense of a debian/rules file?
[05:24] <hggdh> meanwhile, this is indeed the best place
[05:25] <hggdh> heh. Good question, methinks
[05:25] <nigel_nb> jmarsden, well my mentor's awakefullness would
[05:25] <nigel_nb> hggdh, later then...
[05:25] <jmarsden> nigel_nb: There are plenty of useful people here when you need help :)  Ask the channel when you get stuck and see who helps.
[05:25] <nigel_nb> ah well, here goes then
[05:26] <nigel_nb> I'm looking at the rules files and I wanted to know if all the files being created are being cleaned
[05:26] <nigel_nb> package is firestarter
[05:27] <jmarsden> nigel_nb: Well, you could test that by copying your pristine just-unpacked source tree, then running the build, then clean, then compare the cleaned copy with the copied one using diff, and see if any files got left around.  Would that help?
[05:28] <nigel_nb> jmarsden, that definitely would.  Let me try :) thanks
[05:28] <jmarsden> You're welcome.
[06:27] <rhpot1991> if anyone is available for a revu: http://revu.ubuntuwire.com/p/hdhomerun-config-gui
[07:53] <randomaction> suji11: you still have lintian errors/warnings
[07:55] <suji11> randomaction: ya, i'm checking that how to rectify the errors. But it is little bit tough for me, because this is my first package.
[07:55] <randomaction> you can ask here if you don't know how to fix some items
[07:58] <suji11>  randomaction: ya, my first problem is how to add the copyright information in files to my copyright file. Actually i'm having 3 directories, src(Contains c programs and header files), share(contain the bitmap image of IOK), po(contain the translation files).
[08:00] <suji11> randomaction: In po directory there are around 30 files, each file has different copyright holders. should i add all those peoples name in copyright file, if yes how to?
[08:08] <randomaction> hmm, afaik that's not usually done
[08:18] <randomaction> suji11: but yes, in your case in some of the files copyright is claimed
[08:18] <randomaction> by Red Hat, Fedora etc.
[08:19] <randomaction> for this situation I would recommend using DEP5 format: http://dep.debian.net/deps/dep5/
[08:20] <randomaction> where the file says "Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER", you can assume that the copyright holder is the same as the rest of the package
[08:34] <suji11> randomaction: ok, i will do that, how to create the man page for my package/
[08:39] <suji11> randomaction: http://pastebin.com/m67980505 this is the copyright information of two files, how to i add this in my copyright file?
[08:40] <randomaction> for as.po: nothing to add
[08:40] <randomaction> for ca.po: Copyright (C) 2009 Free Software Foundation
[08:43] <suji11> randomaction: that is enough ah? shouldn't add the name Xavier Conde Rueda <xavi.conde@gmail.com>, 2009. ?
[08:44] <randomaction> as far as I can tell from the contents of the file, he doesn't claim copyright
[08:46] <suji11> randomaction: ok, i sent a mail to you about the copyright information,let me know what are the things should i add in my copyright file from that.
[08:48] <randomaction> suji11: now format everything according to http://dep.debian.net/deps/dep5/
[08:49] <randomaction> and instead of sending me mails, just pastebin the text somewhere
[08:50] <suji11> randomaction: ok
[08:50] <suji11> randomaction: i will do the copyright file and will copy that in pastebin and send to you.
[08:53] <suji11>  randomaction: http://pastebin.com/m2ac2e7d0 for this what should i add in copyright?
[08:54] <randomaction> use your judgement
[08:58] <suji11> randomaction: Copyright: 2009 iok , is this right?
[09:19] <suji11> randomaction: http://pastebin.com/m54ee125b this is the copyright file i created now, is this ok?
[09:22] <randomaction> generally OK. Use "License: GPL-2+". "Copyright:" and "License:" mustn't be preceded by spaces. Stanzas must be separated by blank lines. Last stanza must mention "/usr/share/common-licenses/GPL-2" and in examples in DEP5.
[09:23] <randomaction> s/and in/as in/
[09:32] <suji11> randomaction: http://pastebin.com/m46fcd05a i changed the things, now ok?
[09:33] <randomaction> looks ok to me
[09:34] <suji11> randomaction: i will update this to revu.ubuntuwire.com now.
[09:37] <suji11> randomaction: Thank you :)
[09:48] <suji11> bye
[12:12] <siretart> sebner: master thesis, not a phd
[12:13] <sebner> siretart: oh, I'm sorry. nearly the same though :P
[13:23] <riot_le> hello
[13:24] <riot_le> anyone here who can help me with an pbuilder/debootstrap error?
[13:28] <c_korn> riot_le: just ask.
[13:29] <riot_le> i want to create the pbuilder environment on a new client and get an debootstrap-error by doing pbuilder --create: " Failure trying to run: chroot /var/cache/pbuilder/build/10088/. mount -t proc proc /proc"
[13:30] <riot_le> i've searched google and the Ubuntu Wiki but didn't find an answer to this issue
[13:31] <riot_le>  i try it with sudo and as root-User but the Issue is the same
[13:54] <alkisg> I need my app to be ran with gksu, and I'm getting this lindian warning: http://lintian.debian.org/tags/su-wrapper-not-su-to-root.html
[13:54] <alkisg> However, su-to-root isn't install by default on Lucid. Should I depend on that? Should I just keep using gksu? (nope, no thoughts currently about switching to PK :))
[14:10] <kemmotar> hi there! how i can contribute if i'm not programmer?
[14:10] <nigel_nb> kemmotar, yes.  Please see http://www.ubuntu.com/community
[14:12] <kemmotar> nigel_nb: all from here need programmer skill...
[14:13] <nigel_nb> kemmotar, artwork doesnt
[14:13] <nigel_nb> kemmotar, bug squad doesn't, and neither does docs
[14:15] <kemmotar> nigel_nb: "bug squad doesn't" ??? i think it based on programming...
[14:20] <rmunn> kemmotar, Fixing bugs does need programming skill. Reading bug reports and triaging them (can I reproduce it on my computer, or would I need more information to reproduce the bug?) doesn't necessarily take programming skill, just patience.
[14:20] <kemmotar> in last full circle motu said that to be motu no programmer skill are required...what he meant?
[14:21] <rmunn> kemmotar, And answering the "is this a duplicate of another bug?" question also doesn't take programming skill, just knowledge of how to do a search. :-)
[14:22] <nigel_nb> kemmotar, you *dont* need to code in MOTU
[14:22] <nigel_nb> kemmotar, you need to package, which is a bit differnt
[14:22] <rmunn> If non-programmers spend their time sorting through bug reports and filtering out the duplicates and the ones that can't be reproduced, that frees up programmer time to spend actually *fixing* bugs.
[14:22] <nigel_nb> you need enough skills to understand what a patch does and some other stuff though
[14:24] <rmunn> Basic requirements for packaging are not being intimidated by the command line. If that describes you, read https://wiki.ubuntu.com/MeetingLogs/devweek1001/GetStarted and https://wiki.ubuntu.com/MeetingLogs/devweek1001/FixSmallBugs and try the exercises there. If you can do those, you have the skills to help out with packaging.
[14:25] <kemmotar> rmunn: so "bug squad" is something different to "bug fixing"?
[14:25] <nigel_nb> kemmotar, Bug Squad does not fix bugs
[14:26] <rmunn> kemmotar, "Bug Squad" is the team of people that work on bugs. There are many steps to working on bugs, and fixing it is only the last step.
[14:26] <rmunn> See https://wiki.ubuntu.com/BugSquad for what the Ubuntu Bug Squad does in detail.
[14:26] <nigel_nb> kemmotar, we make sure the dev can start fixing rather than spending time deciding which is important
[14:26] <rmunn> From that page: "They assign bugs to packages, ensure that bug reports are complete, find duplicate bug reports, recreate bugs, and forward bugs to their upstream authors." None of that takes any programming skill.
[14:30] <kemmotar> and what are easier - Bug Squad or packaging ?
[14:32] <rmunn> kemmotar, You can see the complexity of packaging by looking at those two devweek1001 links I posted a few minutes ago. Bug Squad consists mostly of reading bug reports and deciding if they're duplicates, if they need more information, and so on.
[14:33] <rmunn> In my opinion, Bug Squad is probably easier for a beginner to get started in. But I don't know how much knowledge you have, so it's possible that packaging might be easier for you. You'll know for sure if you read those meeting logs and try the exercises. :-)
[14:42] <BlackZ> I get this error when I run: "sudo pbuilder build *.dsc": http://paste.ubuntu.com/370289/ how can I solve? it's a python package, this is the "rules" file: http://paste.ubuntu.com/370290/
[14:42] <ahe> would someone take a look at my package http://revu.ubuntuwire.com/p/rubyripper please?
[14:43] <kemmotar> rmunn, nigel_nb: thanks guys!!!
[14:44] <geser> BlackZ: do you have python in Build-Depends for your python package?
[14:45] <rmunn> BlackZ, paste your debian/control file, I think it might be missing a dependency
[14:45] <rmunn> BlackZ, The "ImportError: No module named distutils.core" message suggests that python-dev is missing from the dependency list
[14:47] <BlackZ> this is the control file: http://paste.ubuntu.com/370293/
[14:50] <rmunn> Why do you have a "python-dev (>= 3)" requirement? That won't ever get installed: starting with Python 3.0, the python-dev package is called python3-dev. Change that to "python-dev (>= 2)" and I think your problem should get fixed.
[14:51] <randomaction> BlackZ: rerun debuild, pbuilder didn't even try to install python
[14:54] <abogani> Hi All, What mean when in changelog "1:" precedece version number?
[14:54] <BlackZ> randomaction, http://paste.ubuntu.com/370297/
[14:56] <rmunn> abogani, That's called an "epoch", it makes that version number sort "after" anything without a "1:" in front. It's used for when a package's version numbering changes in a way that wouldn't normally sort correctly (like going from "20090425" to "1.0" for example).
[14:57] <rmunn> BlackZ, Line 54 of that paste: "pbuilder-satisfydepends-dummy: Depends: python-dev (>= 3) but it is not installable" -- change that version number to 2 instead of 3 and things will work.
[14:57] <abogani> rmunn: Thanks a lot! :-)
[14:57] <BlackZ> rmunn, ok, I'm trying to do so
[14:57] <rmunn> There is no python-dev >= 3, python-dev versions only go up to 2.NN.
[14:58] <rmunn> Change the python-dev version in the Build-Depends: line of your debian/control file, then it should work.
[15:01] <BlackZ> http://paste.ubuntu.com/370302/
[15:09] <rmunn> Okay, we've gotten past the distutils.core problem, now we've got a different problem: "dh: Command not found".
[15:10] <rmunn> Got it. It's not "dh clean", it should be "dh_clean". The line in your debian/rules that says "dh $@" is wrong.
[15:11] <rmunn> I don't know debhelper very well yet (I've only created one package so far and I used CDBS for it), so someone correct me if I'm mistaken -- but I think changing that line to "dh_$@" will work.
[15:12] <rmunn> ... no wait, the documentation talks about doing "dh $@". Now I'm confused.
[15:12] <geser> debhelper 7
[15:12] <rmunn> Do you have debhelper listed as a build dependency?
[15:13] <rmunn> Someone else better take this, I'm past where my knowledge runs out.
[15:13] <rmunn> Except that I don't see pbuilder installing debhelper anywhere, so I think you just have to add debhelper to your Build-Depends: line.
[15:14] <randomaction> I agree
[15:15] <BlackZ> hmm, now I get that when I run: "debuild -S": http://paste.ubuntu.com/370309/ but I have added debhelper 7 in the dependences
[15:16] <randomaction> read the error message, you should start line 6 in debian/rules with a tab
[15:16] <rmunn> debian/rules is a Makefile, and Makefiles are picky about whitespace. You *must* use a Tab character, not spaces, for indentation in Makefiles. Annoying, but there you go. Make sure you used a tab on line 6.
[15:17] <randomaction> actually, always read error messages
[15:17] <BlackZ> hmm, I've started it with a tab
[15:18] <rmunn> randomaction is right -- 90% of my problem-solving technique is "read the error message, paste it into Google if I don't understand it, read the first four or five Google results." Works nearly every time. :-)
[15:18] <randomaction> some editors replace tabs with spaces, check yours
[15:19] <hakaishi> Hello everyone! Anyone up to advocate/review qt-shutdown-p? - It is a program to shutdown the system (using the session manager or HAL or 'sudo shutdown -P now') and display the remaining time. http://revu.ubuntuwire.com/p/qt-shutdown-p
[15:25] <BlackZ> randomaction, I get the spaces with nano, pico and gedit - what do you use?
[15:26] <randomaction> gedit has a setting to replace/not replace tab with spaces
[15:26] <randomaction> changeable in the right-hand side of the status bar
[15:27] <randomaction> anyway, try to replace these spaces with a tab and then save file
[15:28] <rmunn> Make sure you get the whole file... if it changed one tab it probably changed all of them, so you'll have to change them *all* back.
[15:29] <BlackZ> ok thanks all, I'll be back in few moments ;)
[15:59] <ejat> hi .. who can help me with this http://bit.ly/alDSYa
[16:07] <hakaishi> ejat: the problem is libtool, but I can't tell you anything else because I don't know your source code. Maybe it is just that you need a (>=2.2.6) in the debian/control file
[16:10] <ejat> hakaishi: ok .. ill give a try .. thanks ..
[16:13] <segler> hi, please help me with: http://revu.ubuntuwire.com/p/rhythmbox-radio-browser
[16:31] <ejat> help me with this plz ... http://paste.ubuntu.com/370346/
[16:32] <rmunn> I don't understand libtool, so I can't tell you how to do it, but lines 11 and 12 look like the thing to do: "You should recreate aclocal.m4 with macros from libtool 2.2.6a-4 and run autoconf again."
[16:34] <ejat> yeah line 11 n 12 .. but i dont know to do that :(
[16:38] <kklimonda> ejat, you can try running autoreconf in the source directory
[16:38] <kklimonda> or aclocal alone
[16:39] <jdong> superm1: discovery of the day: Pairing the apple wireless keyboards tends to work 100% of the time *if* the profile is REMOVED from OS X first
[16:39] <jdong> superm1: I'm not sure if OS X puts something persistent in the bluetooth controller (likely) or keyboard (possible also).... but that glitches out the pairing process
[16:39] <jdong> no idea how to perform the "factory reset" equivalent if OS X is no longer around.
[16:42] <ejat> kklimonda: http://paste.ubuntu.com/370351/
[16:43] <kklimonda> ejat, install libtool
[16:43] <ejat> ok ..
[16:58] <ejat> kklimonda: then after that i need to re-tarball back all the codes right?
[16:59] <kklimonda> ejat, if it worked you would have to create a diff between clean source and the one after autoreconf was launched and patch it at the build time.
[17:42] <superm1> jdong, well i never had OS X w/ mine and still always have a hard time pairing :)
[17:43] <jdong> superm1: hmm interesting :)
[17:43] <jdong> superm1: yeah when OS X still knew about the keyboard it was impossible to pair
[17:43] <jdong> the keyboard would get ADHD and start trying to connect to the last bt it remembered which in turn rejects it, ...
[17:45] <superm1> jdong, i am suspecting the only way we're gonna get down to the bottom of this is to find someone who is knowledgable enough to sniff all the USB packets through a VM or something w/ OSX pairing
[17:45] <jdong> yeah
[17:47] <segler> hi, please help me with: http://revu.ubuntuwire.com/p/rhythmbox-radio-browser
[18:24] <jgoppert> is there any way to get debian lenny packages into the launchpad ppa?
[18:25] <ScottK> jgoppert: PPA questions are better asked on #launchpad
[18:27] <jgoppert> ok thanks
[18:28] <segler> hi, please help me with: http://revu.ubuntuwire.com/p/rhythmbox-radio-browser
[18:31] <jdong> superm1: btw, what's the status with fglrx and lucid?
[18:31] <jdong> superm1: my attempt to install ot right now led to all sorts of pretty glitching and a corrupted root :)
[18:31] <superm1> jdong, amd hasn't published a build that works with the new X server
[18:31] <jdong> superm1: *nods* gotcha
[18:31] <superm1> most of the packaging should be ready though for the new style
[18:32] <superm1> )eg alternatives)
[18:32] <jdong> cool
[18:43] <quadrispro> hello folks
[18:53] <iulian> Hey quadrispro.
[18:54] <quadrispro> heya iulian
[18:59] <rmunn> Any MOTUs interested in reviewing or advocating for http://revu.ubuntuwire.com/p/python-nltk today? NLTK is a set of Python libraries for computational linguistics, and is apparently rather famous in that field (even has an O'Reilly book about it: http://oreilly.com/catalog/9780596516499). I'd like to see it get into Lucid, so I'd like to get some reviews and/or advocates before Feature Freeze on Feb. 18th.
[19:02] <ScottK> rmunn: Did you see about getting into Debian?  It's particularly easy to get Python stuff in.  Visit #debian-python on OFTC.
[19:03] <rmunn> I figured the Debian process would take longer than the Ubuntu process, so I did the Ubuntu package first. I do plan on getting it into Debian as well, though.
[19:03] <ScottK> For Python stuff, Debian is often faster.
[19:04] <rmunn> And if it gets accepted into sid before the Debian freeze this coming Thursday, it'd be automatic in Lucid. Right.
[19:08] <ScottK> It's need to get into Testing before the Freeze, so no, but it's easy to ask for a sync once it's in Unstable
[19:08] <rmunn> ScottK: Understood, thanks
[19:15] <cyberix> I'm trying to do "requestsync --lp -s -d unstable miredo", but this does not work because the package in debian is fresh
[19:15] <cyberix> how long does it take for this to start working after the package is out?
[19:17] <geser> I don't know how long it takes to get the changelog updated
[19:19] <crimsun> hmm. I hadn't even noticed that --skip-minimize is now the default in piuparts(1).
[20:03] <rmunn> ScottK: Thanks for the suggestion: it seems there's a Debian python-nltk package sitting abandoned... someone on #debian-python suggested I ping the maintainer and take over if he doesn't answer within, say, a week. But that'll be after the Debian import freeze for Lucid, so if I'm going to get this into Lucid I'll still need someone to review http://revu.ubuntuwire.com/p/python-nltk
[20:10] <rhpot1991> got a question about the copyright file, since I'm updating an already existing package I just add my information and leave the previous authors info in tact correct?
[20:10] <rhpot1991> http://pastebin.com/f3e30bccc
[23:22] <qense> I've added hooks to configure.ac, but they aren't picked up by Soyuz and debuild. How do I get those to regenerate configure and the Makefiles.in files?
[23:24] <chrisccoulson> qense - is your question there regarding transmission?
[23:24] <qense> yes
[23:25] <qense> I built it only to find it without the right flag enabled.
[23:25] <chrisccoulson> qense - you can just run autoreconf in the build system
[23:25] <chrisccoulson> but we already have a patch in transmission which contains a refresh of the build system
[23:25] <chrisccoulson> so you can just update that patch
[23:25] <qense> chrisccoulson: update that patch to do what?
[23:27] <chrisccoulson> qense - you can make the changes to 99_autoreconf.patch
[23:28] <chrisccoulson> if you just extract that patch for editting
[23:28] <chrisccoulson> and then run "autoreconf" in the build system
[23:28] <chrisccoulson> and make sure you delete autom4te.cache and config.h.in~ afterwards too
[23:29] <chrisccoulson> that will update configure and Makefile.in with the changes you made
[23:29] <qense> chrisccoulson: What changes should I made to the patch?
[23:29] <qense> and with extracting you mean applying?
[23:29] <qense> with cbds?
[23:29] <chrisccoulson> qense - just run "autoreconf" with the patch extracted for editing
[23:29] <qense> ah
[23:29] <chrisccoulson> qense - transmission uses quilt
[23:29] <qense> ok
[23:30] <chrisccoulson> qense - you can automate it with this script: http://people.ubuntu.com/~chrisccoulson/scripts/quilt-autotools.sh
[23:31] <chrisccoulson> by running "quilt-autotools.sh -p 99_autoreconf.patch -a dont_build_libevent.patch"
[23:31] <chrisccoulson> that will do it automatically, make sure any new files are included in the patch, and clean up afterwards too
[23:31] <qense> chrisccoulson: thanks!