[02:01] <Bachstelze> rawr
[02:01] <Bachstelze> nvidia kernel module won't load on boot :/
[02:16] <Bachstelze> jdong: ping
[02:52] <Bachstelze> ew, wrong channel actually :|
[04:57] <micahg> RoAkSoAx: ping
[05:49] <RoAkSoAx> micahg: pong
[05:51] <micahg> RoAkSoAx: was the testdrive fix for vbox 3.2 just a packaging change or were there internal changes as well?
[05:52] <RoAkSoAx> micahg: there were internal changes only actually
[05:53] <micahg> RoAkSoAx: oh, because in lucid, you can't install testdrive + vbox 3.2 because of conflicts
[05:53] <RoAkSoAx> micahg: that's weird. I'm using testdrive and vbox3.2 and didn't get the conflicts
[05:54] <micahg> RoAkSoAx: Lucid or Maverick?
[05:54] <micahg> RoAkSoAx: http://pastebin.com/bbjuWCUp
[05:54] <RoAkSoAx> micahg: lucid! I now know what you mean though :). I', using vbox-ose you are prolly using vbox itself?
[05:54] <micahg> RoAkSoAx: ah, yes
[05:55] <micahg> RoAkSoAx: I was wondering if I added | virtualbox-3.2 if it would work in Lucid
[05:55] <RoAkSoAx> micahg: just give it a try :)
[05:56] <RoAkSoAx> micahg: i'm pretty sure that's why
[05:56] <micahg> RoAkSoAx: k, if it works, can I SRU it?
[05:57] <RoAkSoAx> micahg: sure thing, though we could do a backport that includes the new features of testdrive
[05:57] <micahg> RoAkSoAx: k, I guess that would work too
[05:59] <RoAkSoAx> micahg: indeed. I'll push that to the trunk tomorrow since I'm about to go to bed and please, if you have the time test the packaging fix to see if you still have the issue please :)
[06:00] <RoAkSoAx> micahg: and if you'd like, submit a patch and I'll merge it
[06:00] <RoAkSoAx> to the trunk
[06:00] <micahg> RoAkSoAx: I'm test building now, I'll let you know, can I just update the bug?
[06:00] <RoAkSoAx> micahg: sure
[06:00] <micahg> RoAkSoAx: k, thanks for your time, I have to go to sleep soon as well :)
[06:01] <RoAkSoAx> micahg: oki, have a good one. Nighty :)
[06:02] <micahg> night RoAkSoAx
[06:05] <micahg> RoAkSoAx: oh, one more thing, I made my original bug a dupe of yours, should the packaging changes be a different bug?
[07:56] <dholbach> good morning
[07:57] <ajmitch> morning dholbach
[07:58] <dholbach> hey ajmitch
[10:00] <asac> who is maintaining http://qa.ubuntuwire.com/ftbfs/ ?
[10:12] <geser> asac: wgrant and me
[10:13] <geser> asac: it's about the broken links, right?
[10:13] <asac> geser: no ... its about zyga who works on dashboards for QA for us in linaro ... i will send him here ;)
[10:14] <asac> be nice to thim ;)
[10:14] <geser> asac: aren't we always nice?
[10:15] <asac> yes ;)
[10:19]  * ajmitch hasn't seen any flames in here for days
[12:13] <filip> hi, I have a problem with python distutils: root@tefnet:~# grep egg /usr/lib/python2.6/distutils/command/bdist.py
[12:13] <filip> and I have no idea how I could solve this...
[12:16] <\sh> hmm...where does mk-sbuild now holds the build-chroots when creating one with --type=file?
[13:22] <spiv> w/in 28
[14:46] <mok0> remind me how to get rmadison to look in Debian's archive
[14:46] <jpds> -u deb
[14:47] <mok0> jpds: thanks!
[15:03] <Njh> does anyone know how to run a script after a deb package was installed?
[15:08] <dyfet> Njh: you can have a "postinst" script as part of a package, and it is of course ran during dpkg after the package has been installed.  The $1 argument passed to the script tells you whether it is a new install, an upgrade, etc.  Is this what you mean and are asking?
[15:10] <Njh> dyfet: kind of, im confused on how to run a script post installation, what i have is a metapackage pointing to the most updated version of my program, and when i install the metapackage, i want to be able to create a symlink between the metapackage name and the most updated version
[15:11] <dyfet> Njh: Well, if you have created a debian package, "foo", you can have a "foo.postinst" shell script in your package's debian directory, and it will be ran after install of foo.  It is a shell script, so ultimately it can do anything, including setting symlinks as you suggest.  You expect to have multiple versions of this package simultaneously installed?
[15:13] <Njh> dyfet: yah, i need to be able to have multiple versions, but i want the meta pointing to the most updated version, is the file called "foo.postinst" or "postinst.ex" ... i have tried creating posinst.ex and just echo hello, but i cant seem to get that to work
[15:16] <dyfet> it would be pkgname.postinst.  It should have execute permission, and start with #!/bin/sh of course...you will also need to add a special tag, #DEBHELPER#, into the script, as this will insert additional required code into your script.  You can usually do it before the final exit.  It should exit 0 on success, so that dpkg knows whatever the postinst script did was successfull
[15:16] <Njh> do i need any other bits of code besides the #!/ and DEBHELPER ?
[15:17] <dyfet> You may want to do a case block on "$1", so you know whether the package is being installed or upgraded, though maybe knowing that is not essential in your use case
[15:19] <Njh> Right, i just want it to echo hello for now, and if i can get that then ill be good to go,  but the code should look like  #!/bin/sh  set -e  #DEBHELPER#  echo hello exit 0
[15:19] <Njh> ?
[15:20] <dyfet> That could work, or having the echo before #DEBHELPER#.  I think that usually should be last...
[15:20] <dyfet> (well last before the exit 0 :)
[15:20] <Njh> lol, ok, im going to try after debhelper right now and see if that works
[15:22] <dyfet> I think the idea is that if the user added code to the postinst script fails, it should exit with a non-zero status before #DEBHELPER# stuff is called, since if the package is not going to install successfully the default part of the script should be bypassed
[15:22] <dyfet> At least that would make sense to me :)
[15:23] <Njh> ah ok, cause ya after the debhelper didnt work
[15:25] <Njh> that didnt work either :/
[15:26] <dyfet> Does lintian say anything about your package?
[15:27] <Njh> what do you mean? ... it creates fine
[15:27] <dyfet> what's the name of the binary package(s) produced in the control file?
[15:28] <Njh> there is no binary produced in the meta, right?
[15:30] <dyfet> It still has a Package: entry in control
[15:30] <Njh> yah i have a package name in the control file
[15:33] <Njh> is that what you are asking?
[15:33] <dyfet> I think since there is one package in your control you can also use debian/postinst
[15:34] <dyfet> Your package is basically a meta with a control, a simple rules file, and just a postinst script you want to run?
[15:35] <Njh> yah thats exactly what it is
[15:36] <dyfet> Hmm...I could create a test case for this to try quickly here then :)
[15:36] <Njh> sounds good to me!
[15:45] <dyfet> Njh: since I normally do not build pure metas I had to try this...but this is what I got for my postinst....Unpacking testit (from testit.deb) ...
[15:45] <dyfet> Setting up testit (0.1) ...
[15:45] <dyfet> **** TESTIT!! **********
[15:45] <Njh> .......... y cant mine lol
[15:45] <dyfet> In testit, I have just a DEBIAN/control, and DEBIAN/postinst
[15:46] <Njh> whats in both files
[15:46] <Njh> ill try to just run that
[15:47] <dyfet> http://pastebin.com/dYqZE7Qt
[15:47] <dyfet> and the control is in http://pastebin.com/vYWqAAU9
[15:48] <Njh> ok thanks, give me a second
[15:48] <Njh> what did u use to make the deb
[15:48] <dyfet> dpkg-deb -b testit testit.deb
[15:49] <Njh> ok thats what i use too
[15:50] <dyfet> But I wanted to see why this did not work for you...It was dirty, no changelog, etc :)
[15:50] <Njh> haha, im going to try it now
[15:52] <Njh> if i just have postinst, i get bad permissions 644
[15:52] <dyfet> Yes, it has to have execute permission
[15:52] <dyfet> (chmod +x)
[15:52] <Njh> ok
[15:52] <Njh> do i need to specify what fuke
[15:52] <Njh> ive enver used chmod
[15:53] <dyfet> Njh: well, in my case, I just used "chmod +x testit/DEBIAN/postinst"
[15:53] <Njh> ok, thanks, hold on
[15:54] <dyfet> Njh: this is of course not really a proper way to do a meta, but if it's something you just need to do for your own use, and to answer your question why your postinst did not run, I think it is sufficient
[15:55] <Njh> ok
[15:55] <Njh> i know why it wasnt working
[15:55] <Njh> it was never an executable
[15:55] <Njh> the chmod is what did it
[15:56] <dyfet> ah...yes :) that is needed
[15:56] <Njh> thank you so much!
[16:06] <Njh> dyfet: is there any specifc way to run terminal commands in the postins
[16:07] <dyfet> Njh: what do you mean by terminal commands?  Do you mean like menus?  You can use something like dialog of course to create a user selection
[16:08] <Njh> dyfet: like if i just want to run ls -la  from the postinst
[16:09] <Njh> or cp,mv, etc ...
[16:09] <dyfet> Njh: You could do things like that, too
[16:09] <Njh> dyfet: right, how would i do that
[16:11] <dyfet> Njh: pretty much the same as with any other shell script.  Just add the commands you need to do.  If you use some command that is not part of a minimal install, you can add a Depends: entry to your meta to make sure it is installed first
[16:12] <Njh> dyfet: yah, im kinda new at all of this haha, how would i do that .
[16:13] <dyfet> I would suggest starting with a basic reference on shell scripting, etc.  I do not know of a good one offhand, but I am sure if you ask others will have something to recommend.
[17:28]  * ari-tczew has got 1st place in maverick bug fixing \o/
[17:29] <nigelb> ari-tczew: congrats :)
[17:29] <ari-tczew> hehe :P
[17:34] <micahg> ari-tczew: where is that?
[17:35] <ari-tczew> http://qa.ubuntu.com/reports/bug-fixing/maverick-fixes-report.html
[17:37] <micahg> ari-tczew: thanks
[17:37] <ari-tczew> you're welcome
[17:48] <dupondje> jean-louis@dupond.be has 2 fixes => i'm even in the list
[17:48] <dupondje> sick :D
[17:49] <dupondje> oh, and with my old email adress also 2 fixes
[17:49] <dupondje> great :p
[18:06] <l3on> Hi all.. does someone of you know the meaning of "kj-triage" tag in LP?
[18:38] <dupondje> i'm checking http://launchpadlibrarian.net/48423954/buildlog_ubuntu-maverick-i386.synce-kpm_0.15-1_FAILEDTOBUILD.txt.gz atm
[18:38] <dupondje> its creating: creating /build/buildd/synce-kpm-0.15/debian/synce-kpm/usr/local/lib/python2.6/dist-packages/synceKPM
[18:38] <dupondje> while it should be creating /build/buildd/synce-kpm-0.15/debian/synce-kpm/usr/lib/python2.6/site-packages/synceKPM
[18:38] <dupondje> any idea what causes this ?
[18:38] <ari-tczew> check debian/rules
[18:40] <dupondje> python setup.py install \ --root=$(CURDIR)/debian/synce-kpm \ --single-version-externally-managed \
[18:57] <blue_anna> does nvidia provide no binaries drivers for powerpc architecture? -- I was going to search for Scott and ask if he'd compile nvidia-glx-185 for us but I just read that it is binary
[18:57] <blue_anna> and the nvidia website is crashing to much to browse it :P
[19:03] <carstenh> blue_anna: as far as i know, they do not
[19:18] <geser> dupondje: using dist-packages for python 2.6 is correct, but I also see that it installs to /usr/local which is bad
[19:19] <geser> dupondje: please coordinate a fix with the Debian Python team in #debian-python@OFTC. They can tell you how to fix it best.
[19:35] <micahg> RoAkSoAx: it gives me an error w/just the packaging change :)  Are you changes in individual commits in bzr?
[19:55] <shadeslayer> i call upon the power of the MOTU :P
[19:58] <shadeslayer> looks like the MOTU have a day off :P
[19:59] <micahg> !ask | shadeslayer
[20:00] <shadeslayer> are there any packaging jobs that i can look at to contribute to MOTU and eventually become one myself?
[20:00] <shadeslayer> ( i need specific stuff that i can work upon,not just a wiki page describing what i can do )
[20:01] <micahg> shadeslayer: merges?
[20:01] <shadeslayer> micahg: hmm.. ive heard of those,is there a list of outstanding merges?
[20:01]  * shadeslayer wonders if any are left
[20:03] <micahg> shadeslayer: https://merges.ubuntu.com/
[20:03] <shadeslayer> what do you mean by outstanding merges? Merges to be done i.e. worked upon or merges that have been worked upon and are pending  approval
[20:04] <geser> shadeslayer: https://merges.ubuntu.com/universe.html and my merges are free to take
[20:04] <shadeslayer> geser: :P
[20:04] <shadeslayer> which ones have to be done? the red ones?
[20:04] <micahg> shadeslayer: there you go :)
[20:04] <geser> shadeslayer: all
[20:05] <shadeslayer> so what do the colors represent?
[20:06] <shadeslayer> geser: where do i upload a package once i work  upon it?
[20:06] <geser> the Priority of a package, you can safely ignore it
[20:06] <shadeslayer> eh?
[20:06] <shadeslayer> oh the color
[20:07] <geser> shadeslayer: file a bug, attach the debdiff, and subscribe the ubuntu-sponsors team
[20:07] <shadeslayer> okies..
[20:07]  * shadeslayer goes to read  more about debdiff and merging before starting
[20:07] <shadeslayer> all of geser's packages are mine :P
[20:07]  * micahg already has a list of merges to do :)
[20:08]  * micahg is just waiting for upload rights and time to do them :)
[20:08]  * shadeslayer counts 16 packages in all 
[20:08] <shadeslayer> micahg: same here.. will do merges from 11th onwards
[21:06] <shadeslayer_> micahg: btw how much time does it take to become a MOTU?
[21:06] <shadeslayer_> like whats the period of time that i have to lear before i can apply for MOTU
[21:06] <shadeslayer_> *learn
[21:06] <micahg> shadeslayer_: depends, I'm not there yet :)  usually when others say you're ready
[21:07] <shadeslayer_> micahg: hmm awesome :D
[21:52] <micahg1> SpamapS: were there any issues with xulrunner and mongodb?
[22:52] <dupondje> you need to create a bug to fix a FTBFS right ?
[22:55] <geser> only if you need sponsoring
[23:04] <dupondje> https://bugs.launchpad.net/ubuntu/+source/synce-kpm/+bug/589908
[23:04] <dupondje> there it is :D
[23:08] <BlackZ> dupondje: last time remember to update the maintainer to "Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>" or run update-maintainer instead
[23:09] <BlackZ> BTW it isn't an error, but that address would be preferred
[23:09] <dupondje> argh, I didn't know it for sure, so I checked the wiki ... :p
[23:09] <BlackZ> also, I think there's no need to generate a new debdiff, for this time let what you have set
[23:09] <BlackZ> but please, the next time remember to do that
[23:10] <dupondje> i'll do for sure
[23:11]  * dupondje bookmarks https://wiki.ubuntu.com/DebianMaintainerField
[23:13] <BlackZ> dupondje: if you're bored to update it manually, remember there's update-maintainer
[23:13] <micahg> BlackZ: I would think update-maintainer is preferred in case the policy changes again
[23:14] <BlackZ> micahg: but the ubuntu-devel-discuss address would be preferred, am I wrong?
[23:14] <dupondje> yea indeed, just didn't know that command yet :)
[23:15] <micahg> BlackZ: I thought that's what it sets everything to
[23:15] <BlackZ> micahg: in some packages there's still the MOTU address as maintainer
[23:16] <BlackZ> s/as maintainer/set as maintainer
[23:16] <dupondje> did a bugreport in debian also btw, to get issue fixed on this package
[23:16] <micahg> BlackZ: ah, yeah, well, idk then :)
[23:17] <ScottK> Using MOTU as maintainer is obsolete.
[23:17] <BlackZ> micahg: I think it should get updated
[23:17] <BlackZ> ScottK: ^
[23:17] <ScottK> They should all be Ubuntu Developers now.
[23:17] <ScottK> It's not worth an upload just for that, but when you are changing a package for other reasons, fixing that too is good.
[23:18] <micahg> ScottK: should update-maintainer be patched for htat?
[23:18] <BlackZ> micahg: it's
[23:18] <dupondje> '/usr/bin/install' -o root -g root -m 644 debian/build-qmail.1 debian/tmp-src/usr/share/man/man1
[23:18] <dupondje> /usr/bin/install: cannot change ownership of `debian/tmp-src/usr/share/man/man1/build-qmail.1': Operation not permitted
[23:18] <ScottK> micahg: No, you should just fix it.
[23:18] <dupondje> huh ? isn't it building as root ?
[23:18] <micahg> ScottK: k
[23:18] <BlackZ> ah, you mean update-maintainer, yeah sorry
[23:18] <ScottK> It will already DTRT if it's not an ubuntu.com address as maintainer.
[23:19] <BlackZ> misunderstood :P
[23:53] <dupondje> BlackZ: http://launchpadlibrarian.net/49689035/fix3.debdiff => bit improved :)
[23:58] <dutchie> if I build using pdebuild, is there a way to get stuff like config.log out for debugging?