[00:13] <hallyn> i'm not thinking right about something.  i have some source in a bzr tree.  i want to build a package from it.  bzr bd insists i need a .orig.tgz, but it's all in (and only in) the bzr tree!  should i just build a bogus .orig.tgz and .changes and debuild -S by hand with that?
[00:14] <hallyn> clearly i'm not thinking right about something
[01:37] <jonrafkind> i screwed up my source package but when I rebuild the package with debuild -S (which builds the same filename as before) I get a rejection saying the file already exists
[01:38] <jonrafkind> so is the solution to make a new filename (bump the version)? which means I have to bump the version in all the control/changelog/whatever files?
[01:38] <jonrafkind> sorry i meant after i rebuild the package with debuild -S and upload it with dput
[01:48] <ebroder> That's right. You can only upload a particular version of a particular package to a particular repository once
[02:10] <ebroder> Did something replace gdebi as the default .deb file type handler in maverick?
[02:10] <kklimonda> ebroder: software-center
[02:10] <ebroder> Huh. Thanks
[02:13] <sladen> ebroder: xdg-open somefile.deb
[03:34] <jonrafkind> how do I get dh-make not to run 'make test' ?
[03:35] <jonrafkind> or maybe its just 'dh' that i want
[03:38] <ion> jonrafkind: See dh(1), look for “Commands not to run” and “override_dh_auto_test”.
[03:39] <jonrafkind> neither of those are in dh or debhelper
[03:39] <jonrafkind> man pages
[03:40] <ion> debhelper: /usr/share/man/man1/dh.1.gz
[03:40] <jonrafkind> can you send me that file or something? i guess i have an older version than you
[03:41] <jonrafkind> actually ill try to find it online i guess
[05:42] <jonrafkind> can someone show me an example of overriding dhauto test ? I tried adding rules to my makefile 'override_dh_auto_test: echo nothing' but it doesnt take
[05:42] <jonrafkind> i also tried override-dh-auto-test
[05:46] <james_w> jonrafkind: "override_dh_auto_test:\n\techo foo" is correct
[05:46] <jonrafkind> does it have to be before the %: dh $@ rule?
[05:46] <james_w> nope
[05:46] <jonrafkind> hm.. i wonder why its not working
[05:47] <james_w> jonrafkind: did you literally write "override_dh_auto_test: echo nothing"?
[05:47] <jonrafkind> well i used the newline and tab stuff
[05:47] <james_w> ok
[05:47] <jonrafkind> i know makefile syntax
[05:48] <james_w> http://bazaar.launchpad.net/~linaro-maintainers/linaro-image-tools/linaro-image-tools/annotate/head:/debian/rules
[05:48] <james_w> that's one I wrote just the other day that works
[05:49] <jonrafkind> ok
[06:31] <jonrafkind> ok it didnt work becuase somehow pbuilder installed an old version of dh that didn't recognize the override stuff
[06:31] <jonrafkind> which is strange considering my local dh does recognize override, so i wonder what pbuild is installing
[09:37] <pk4r> Hello, is this the right place to ask a few packaging related questions ? I'm currently trying to package a few PHP web applications, while following the official Ubuntu Packaging Guide I feel there're more things to know when it comes to web apps (supporting different servers, post-install configuration etc.).. I downloaded source of phpmyadmin to explore a little bit.. just starting with it. Can anybody give some pointers on that ?
[09:38] <micahg> pk4r: if it's for a PPA, #ubuntu-packaging is the place, if it's for the archive, #ubuntu-motu would be the place
[11:36] <hyperair> hmm this is interesting. openoffice's orig.tar.gz was 300+M, but libreoffice's is only 13M
[11:36] <hyperair> i wonder what's been left out of libreoffice's
[11:40] <slomo> hyperair: maybe they don't include copies of every single dependency, including python and other large things ;)
[11:40] <hyperair> slomo: oh lol
[11:41] <hyperair> slomo: i remember openoffice taking over 2 days to build on a pentium 4 system. i wonder if libreoffice would do the same
[11:41] <hyperair> it's kinda hard to imagine 13M of source code taking that long to build.
[11:41] <hyperair> i mean hey the kernel was 700M or so...
[12:27] <Riddell> hyperair: the source is actually the go-oo build source, which is just patches for applying to the openoffice.org source
[12:28] <hyperair> Riddell: and so.. there's 300M of patches?
[12:29] <Riddell> there's 13M of patches
[12:45] <alex88> hi..i've 2 questions, why after installing the nvidia drivers plymouth gives me low-res splash screen? also, is possible to unlock keyring on login? If i install libpam-keyring and add to /etc/pam.d/gmd i can't login..
[13:01] <Laney> ssh
[14:42] <steve|m> hi, can anyone confirm that if pressing a multimedia hotkey on the keyboard the left mousebutton doesn't work anymore in the current session in maverick?
[14:51] <steve|m> I tried it on 2 different machines, xev even doesn't show the left mouse button click anymore (multimedia keys being Play/Pause, calculator, email and the like)
[19:48] <zyga> hi
[19:53] <steve|m> can anyone confirm this one? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/654201
[22:33] <maxb> james_w: Hi. That bug you just edited - is there another one to track the rest of the NoSuchTag UDD failures?
[22:55] <jonrafkind> im making a source package for my ppa, what is my make install target supposed to do? i tried doing 'mkdir /usr/bin/games; cp my-game /usr/bin/games' but I get a build error that says the mkdir failed because of permission errors
[22:56] <jonrafkind> does the launchpad builder not run with root permissions?
[22:56] <ebroder> jonrafkind: http://www.gnu.org/prep/standards/html_node/DESTDIR.html
[22:56] <jonrafkind> ah ok
[22:56] <lifeless> jonrafkind: #ubuntu-packaging is probably a better channel for this question; packages install into a staging area not into /usr
[22:56] <jonrafkind> so maybe $(DESTDIR)/bin/games
[22:57] <jonrafkind> omg, how many different channels are there? so far ive found 3
[22:57] <ebroder> Lots. https://wiki.ubuntu.com/IRC/ChannelList
[22:57] <ebroder> And I don't think that list is exhaustive
[22:57] <jonrafkind> ubuntu loves beauracracy eh?
[22:57] <sladen> jonrafkind: you don't install it directly, you install your stuff into some directory where told (DESTDIR in this case), and then the packaging build system will bundle that up
[22:58] <lifeless> no, ubuntu is dealing with thousands of people doing stuff at the same time.
[22:58] <sladen> jonrafkind: it's more that Ubuntu is quite big.  If would get very noisy if everyone was in the same place
[23:26] <jonrafkind> $DESTDIR is not set in the debian/rules file
[23:28] <zyga> jonrafkind, is your software written in C?
[23:28] <jonrafkind> hm, dh_auto_install sets DESTDIR, but I have my own install target that acts differently
[23:28] <jonrafkind> c++
[23:28] <zyga> jonrafkind, if so you'd save everyone lots of hassle by using autotools
[23:28] <jonrafkind> i use scons
[23:28] <zyga> jonrafkind, that will work too
[23:29] <zyga> jonrafkind, oh
[23:29] <zyga> jonrafkind, does scons suport DESTDIR?
[23:29] <jonrafkind> the point is i have my own makefile that when you do 'make install' it runs  another script that asks you some questions about where to install
[23:29] <jonrafkind> i could have a separate install target for this dh stuff that used DESTDIR I guess
[23:29] <zyga> jonrafkind, in packaging that is always a bad idea
[23:30] <jonrafkind> well.. thats debateable
[23:30] <jonrafkind> is it possible to get dh_auto_install to use a different target?
[23:30] <zyga> jonrafkind, you should install to $(DESTDIR)$(something)
[23:31] <zyga> jonrafkind, you miss the point - the installer is just building the image of the stuff that gets installed by the end user from a package, things have well defined locations, if you want to configure something do that _before_ building you package (configure step in autotools)
[23:31] <zyga> jonrafkind, I'm not sure I don't do a lot of packaging
[23:31] <jonrafkind> i understand how it all works and I know thats what most people do
[23:31] <jonrafkind> but i have decided to do it a different way
[23:32] <zyga> jonrafkind, it seems that you built an user-friently installer, is that correct?
[23:32] <jonrafkind> yes
[23:32] <zyga> jonrafkind, that should be a separate script IMHO, you should use it to trigger the normal build script/makefile/whatever with arguments
[23:32] <jonrafkind> it is a separate script, but so far i have 'make install' just execute that script
[23:33] <zyga> jonrafkind, well changing it to be exactly opposite is the quickest way to solve your problem
[23:33] <zyga> jonrafkind, you can still keep the custom installer script
[23:33] <jonrafkind> only to satisfy ubuntu's process
[23:34] <jonrafkind> other systems (arch, gentoo) don't have this issue
[23:34] <zyga> jonrafkind, honestly if your software is open source it's not related to ubuntu, nobody expects a talking installer
[23:34] <jonrafkind> well they are gonna get one!
[23:34] <zyga> jonrafkind, arch has binary packages correct?
[23:34] <jonrafkind> yea
[23:35] <zyga> jonrafkind, I don't know too much about it but your problem is trying to use interactive steps in an environment that requires none (automated builds)
[23:35] <cjwatson> could you please take this elsewhere?  I think there was already conversation above indicating that it's more relevant to #ubuntu-packaging than here - we try to reserve this channel for development of Ubuntu itself, so that our developers can focus on that
[23:35] <zyga> I understand your desire to use user friendly installer but IMHO you used the wrong place to put your interactivity bits
[23:35] <jonrafkind> well that assumes the way dh works cannot be changed
[23:35] <jonrafkind> i asked in #ubuntu-packacing and no one responded, and b) there is no one else talking
[23:36] <zyga> jonrafkind, cjwatson is right, this is not the right place
[23:36] <cjwatson> b) irrelevant, developers read scrollback
[23:36] <cjwatson> and the fact that another channel is quiet doesn't mean this is the right place for it
[23:36] <jonrafkind> zyga, do you wish to join #ubuntu-packaging?
[23:37] <zyga> why not
[23:37] <cjwatson> thanks