[01:00] <dtchen> anyone with i386 -- bare metal, not vm -- lying about?
[02:06]  * jdong scratches head at bug 475891
[02:08] <dtchen> heh, I remember eagle.
[02:13] <jdong> dtchen: heh the proposed fix is one of the more amusing ones I'v eseen
[02:13] <jdong> especially when it seems like neither the SRU submitter nor the Debian uploader seem to give a second thought to it
[03:12] <JonyBlaze> maybe it uses relative paths?
[03:17] <JonyBlaze> still though...heh
[04:18] <jgoppert1> how best to make a package that is just a super package that makes other package ?
[04:18] <jgoppert1> install
[04:20] <sbalneav> jgoppert1: Take a look at one of the existing metapackages
[04:20] <sbalneav> something like ubuntu-desktop.
[04:21] <jgoppert1> thanks i'll check it out
[04:21] <sbalneav> apt-get source ubuntu-desktop.
[04:29] <jgoppert1> exec germinate-update-metapackage --bzr ??
[04:29] <jgoppert1> i think this is probably not needed for me, but wondered if anyone knows that this command does
[04:33] <jgoppert1> has anyone used dh --with germinate, i think it must be used to pipe files in somehow Depends: ${misc:Depends}, ${germinate:Depends}
[04:42] <jgoppert1> found the equivs package, looks very helpful, thanks guys
[04:45] <JonyBlaze> is there a way I can delete a package I uploaded to REVU?
[04:50] <nhandler_> JonyBlaze: What is the package?
[04:50] <nhandler_> JonyBlaze: And why do you want to delete it?
[04:51] <JonyBlaze> nhandler_: pep8, after I made it I relized there is a Debian package with the same name (unrelated)
[04:51] <JonyBlaze> I need to rename it
[04:52] <JonyBlaze> I will rename it to pep8simulator
[04:53] <JonyBlaze> http://revu.ubuntuwire.com/p/pep8
[04:54] <JonyBlaze> http://packages.debian.org/sid/pep8
[04:54] <JonyBlaze> thats not good :(
[04:55] <nhandler_> JonyBlaze: Done
[04:55] <JonyBlaze> thank you!
[04:56] <nhandler_> JonyBlaze: You are welcome
[05:56] <ScottK> jgoppert1: If you think equivs is a solution to your problem you are almost certainly not considering the solution correctly.  In almost all cases, including the one you're considering, it's a horrible hack and not the write way to go.
[05:58] <jgoppert1> Scottk: what do you recommend? I can do it manually. I have built other packages
[05:58] <ScottK> It depends on how often it will change.
[05:59] <ScottK> For most in archive metapackages we use seeds and germinate, but if it'll rarely change, manually is fine.
[05:59] <jgoppert1> its a set of packages that i want to install on my computer network, maybe every month or so
[06:00] <jgoppert1> i've been looking at ubuntu-meta, but have yet to figure out how germinate:Depends is supposed to pull in what file
[06:00] <ScottK> But if the set isn't going to change, then just do it manually and make the packages you want a depends of the metapackage.
[06:00] <jgoppert1> the set will change every month
[06:05] <austin_laptop> so at wineconf, Scott Richie mentioned that there is a list of ~1000 packages that don't compile on Karmic, anyone know where that is? google doesn't show much
[06:07] <siretart> austin_laptop: see the topic, last link
[06:07] <austin_laptop> ah, crap, I'm blind
[06:07] <austin_laptop> thanks
[06:30] <jmarsden> Package version numbering confusion: bible-kjv is one of those "doesn't build on Karmic" packages.  I just fixed it.  It was version 4.23.  No -1, no -1ubuntu1, etc.  Just 4.23.  What should I number the fixed package?
[06:31] <ScottK> jmarsden: If it's a native package in Debian, leave it that way.
[06:32] <jmarsden> So ... does that mean I can bump it to 4.24 myself?
[06:34] <siretart> no, that would clash if debian publishes 4.24. this would then confuse everyone
[06:35] <AnAnt> should one sign the new CoC ?
[06:35] <siretart> ScottK: TBH, converting it to non-native does not sound like the worst idea to me.
[06:36] <jmarsden> I know a friendly DD I can probably get to upload it to Debian unstable for me... should I bump to 4.24 and do things that way??
[06:37] <siretart> jmarsden: the cleanest way: get 4.24 sponsored to debian and then have it synced to ubuntu. in that order
[06:37] <jmarsden> OK, makes sense.  Will do.  Thanks.
[07:56] <dholbach> good morning
[08:29] <iulian> Morning dholbach.
[08:30] <dholbach> hi iulian
[09:07] <wrapster> I recently added a few changes to bintuils pkg that i was working on... I fixed/uploaded the latest one .. but on some machine via the APT if i try to install them I get this error... http://pastie.org/689890
[09:33] <LucidFox> Why does mc have such weird defaults for file associations?
[09:34] <LucidFox> It tries to run gqview for image files, for one
[09:42] <siretart`> LucidFox: I see that you work a lot on multimedia packages in
[09:42] <siretart`> ubuntu. have you considered joining pkg-multimedia and maintain the
[09:42] <siretart`> ubuntu packages there?
[09:54] <LucidFox> siretart`> In Debian?
[09:55] <siretart`> well, sort-of yes.
[09:57] <slytherin> NCommander: ping
[09:59] <directhex> poke pokey poke poke. is TheMuso about?
[10:07] <LucidFox> siretart`, won't all the packages depending on libmp4v2 in Ubuntu also be able to use it in Debian?
[10:08] <siretart`> LucidFox: probably yes
[10:22] <\sh> moins
[10:24] <siretart`> hi \sh!
[11:02] <\sh> bah...office power outage and the whole infrastructure inhouse doesn't work anymore...dear god of sysadmins, please give me pros to work with
[11:11] <mok0> \sh: no UPS'es?
[11:27] <\sh> mok0, not in this office...and it's internal it which is responsible for this mess
[11:38] <dpm> hey dholbach, I've got a question on SRUs on the sponsorship queue. I'm looking at http://people.canonical.com/~dholbach/sponsoring/ I filed an SRU at https://bugs.edge.launchpad.net/ubuntu-translations/+bug/460984 and it doesn't appear on the list. I'm not sure I did the nomination for karmic correctly. What do you think it could be?
[11:39] <dholbach> it doesn't have the sponsoring team on it? :)
[11:39] <dholbach> ubuntu-main-sponsors in this case
[11:49] <dpm> dholbach, argh! I had not noticed I had only subscribed ubuntu-sru. Thanks! :)
[11:49] <dpm> sorted
[12:19] <\sh> ttx, pingeling ;) bug #475457 :)
[12:25] <ttx> \sh: yo
[12:26] <\sh> ttx, I wanted to put this topic as start of a discussion about this...I wonder if the patch I did is sane, or if it's better, to move $JSVC_CLASSPATH from /etc/default/tomcat6 after the default startup classes
[12:27] <ttx> \sh: the way you did it allows to override the default classes, which sounds cool...
[12:28] <ttx> only unknown is whther starting a classpath with ":" is allowed/harmful or not
[12:33] <\sh> ttx, imho it is, but we can go with a better solution with some shell magic..e.g. setting JSVC_CLASSPATH in default to empty... and in /etc/init.d/tomcat6 if [ -z "$JSVC_CLASSPATH" ]; then JSVC_CLASSPATH="<the standard stuff>" else JSVC_CLASSPATH="$JSVC_CLASSPATH:<the standard stuff>" fi
[12:33] <ttx> \sh: sure.
[12:34] <\sh> ttx, or just set the default settings in /etc/default/tomcat6 and use it as well in the init script...so we are clean...all defaultsettings are set where it really belongs :)
[12:35] <ttx> \sh: yes, that's even better... then you can add your stuff before and/or after the regular stuff.
[12:35] <\sh> ttx, yepp...
[12:51] <sebner> hiuhu \sh, everything fine? :D
[12:52] <ThreeOfEight> Hallo, can anyone help me build a package, step by step?
[12:53] <\sh> sebner, if you ask in such a tone, no ;)
[12:53] <sebner> ThreeOfEight: that always differ from source to source. have you read the packaging guide?
[12:53] <ThreeOfEight> Yes I have.
[12:54] <ThreeOfEight> In two languages
[12:54] <sebner> \sh: "such tone" ?
[12:54] <sebner> ThreeOfEight: ok, where do you have problems?
[12:54] <ThreeOfEight> Well first of all, I'm not entirely sure how to start
[12:55] <ThreeOfEight> The programme I'm trying to build a package of is a small game a friend of mine wrote, I've got the source and a binary
[12:55] <ThreeOfEight> So what do I do? Put both in one package? Or build two separate ones?
[12:55] <sebner> ThreeOfEight: https://wiki.ubuntu.com/MOTU/GettingStarted
[12:57] <ThreeOfEight> oh, okay, I haven't read that one.
[12:57] <directhex> ThreeOfEight, you don't package binaries. you create source packages, which define how binaries should be built and packaged by the build servers
[12:59] <ThreeOfEight> ah okay, that makes sense
[13:00] <ThreeOfEight> however, when I tried to build my source package, I had a weird error
[13:00] <ThreeOfEight> It said that "changes could not be applied because the binary file was changed"
[13:00] <ThreeOfEight> but I'll try again from scratch
[13:01] <directhex> ThreeOfEight, if your "clean" rule in debian/rules doesn't revert everything back to before-you-tried-compiling status, then you get that error
[13:01] <ThreeOfEight> Oh yes, that was weird, too
[13:01] <ThreeOfEight> it first said that there was no rule to make clean
[13:01] <ThreeOfEight> but there was a clean: in the rules file
[13:08] <geser> clean from debian/rules often calls clean from the upstream makefile, perhaps it's that what's missing
[13:08] <ThreeOfEight> There is no upstream makefile
[13:08] <ThreeOfEight> because there's really nothing to clean
[13:08] <ThreeOfEight> Where am I, that is my script, supposed to put the compiled binary?
[13:12] <joaopinto> ThreeOfEight, aren't you building from source ? there should be a resulting binary to clean
[13:12] <ThreeOfEight> Well, what do I do with that binary?
[13:12] <ThreeOfEight> Where do I put it?
[13:12] <ThreeOfEight> The root directory of the package?
[13:13] <directhex> ThreeOfEight, the "binary" rule in debian/rules should take the binary produced in the "build" rule, and place it inside an appropriate pretend path (usually debian/tmp/usr/bin/fooapp or something like that), and send the right commands to turn that path into a package
[13:13] <joaopinto> ThreeOfEight, to start, was the binary built from the source as part of the package build process ?
[13:13] <joaopinto> directhex, I believe he is trying to install a precompiled binary
[13:13] <ThreeOfEight> it was.
[13:13] <ThreeOfEight> no, I'm not
[13:13] <ThreeOfEight> I am compiling, and that works
[13:13] <joaopinto> ThreeOfEight, so you already fixed the binary on changes error, right ?
[13:14] <directhex> let me find a simple example of a makefile-free package
[13:14] <ThreeOfEight> yes
[13:14] <joaopinto> ok
[13:14] <ThreeOfEight> I just don't know where to put the compiled binary now
[13:14] <joaopinto> ThreeOfEight, are you using cdbs or debhelper ?
[13:14] <ThreeOfEight> er
[13:14] <joaopinto> with cdbs it's simpler
[13:14] <ThreeOfEight> right now I just call dpkg-buildpackage
[13:14] <joaopinto> ok, and how is your debian/rules ?
[13:14] <ThreeOfEight> Well it compiles it
[13:15] <joaopinto> a long list of dh_* calls ?
[13:15] <ThreeOfEight> It cleans it up
[13:15] <ThreeOfEight> Yes
[13:15] <directhex> joaopinto, cdbs is never simpler than dh7 unless you are doing *just* the right voodoo
[13:15] <joaopinto> ok, so it's using debhelper
[13:15] <ThreeOfEight> I just modified the original one created by dh_make
[13:15] <ThreeOfEight> ah, yes
[13:15] <ThreeOfEight> right, I am. sorry.
[13:15] <directhex> joaopinto, dh7, that is. dh5 is complex
[13:15] <joaopinto> directhex, right, but most people still use dh5
[13:15] <ThreeOfEight> and I removed all the Makefile calls
[13:15] <directhex> well, they're sillypants! dh5 is hard!
[13:15] <ThreeOfEight> so what I need to know now is where to put the binary. It's supposed to go into /usr/share/games/ttmine
[13:16] <joaopinto> I personally found cdbs easier to understand :P
[13:16] <directhex> binaries don't go in /usr/share. /usr/share is for cross-platform code
[13:16] <directhex> or non-code, more commonly
[13:16] <ThreeOfEight> Really? But all the other games install in there.
[13:16] <directhex> in part
[13:16] <directhex> things like art assets go in /usr/share
[13:16] <directhex> as art is cross-platform
[13:17] <ThreeOfEight> heh... true...
[13:17] <ThreeOfEight> okay
[13:17] <ThreeOfEight> so /usr/bin/?
[13:17] <directhex> but libraries go in /usr/lib, and executables in /usr/bin
[13:17] <ThreeOfEight> alright
[13:17] <joaopinto> games binaries go into /usr/games
[13:17] <directhex> oh, yes
[13:17] <directhex> silly distinction IMHO
[13:17] <ThreeOfEight> I am a bit of a newbie in Linux, especially to package building
[13:17] <ThreeOfEight> so where do I put the binary in the package
[13:18] <ThreeOfEight> ttmine-0.51/games?
[13:18] <ThreeOfEight> or ttmine-0.51/debian/games?
[13:18] <directhex> ThreeOfEight, typically into debian/tmp/usr/games/
[13:18] <ThreeOfEight> Why tmp?
[13:20] <directhex> think of debian/tmp as a "staging area" where you construct your ideal installation, with everything in its nice little folders as expected, before you issue the appropriate command to turn debian/tmp/* into * inside a package
[13:20] <ThreeOfEight> ah okay
[13:20] <ThreeOfEight> so in the final package, I will just move all the contents of tmp up directly into debian?
[13:21] <directhex> well, the dh_builddeb command is what does that, whether you call it manually or via a layer like cdbs or dh7
[13:22] <directhex> dh_builddeb reads a list of files or folders in debian/install, removes debian/tmp from the start of them, and shoves them in a .deb file
[13:22] <ThreeOfEight> what is debian/install then?
[13:22] <directhex> just a list of files & folders to put in the package
[13:23] <ThreeOfEight> so I have to create that, too?
[13:23] <directhex> yes
[13:24] <ThreeOfEight> so okay
[13:24] <ThreeOfEight> I have rules in build so that all the stuff created goes into debian/tmp/and so on
[13:24] <ThreeOfEight> Where and what do I have to put stuff into debian/install?
[13:24] <directhex> debian/install is just a text file
[13:25] <directhex> it should contain lines like "debian/tmp/usr/bin"
[13:26] <ThreeOfEight> okay, thanks, I thought it was a director
[13:26] <ThreeOfEight> +y
[13:27] <directhex> it's just a list of what you want to go into a package. sometimes build processes make lots of extra crap you want to skip - or you have multiple install files to send different files into different packages in the event that you want multiple packages from a single sourcwe
[13:27] <ThreeOfEight> Are the contents of the tmp directory (and the directory structure itself) supposed to be created during build or can I create that before, too?
[13:27] <directhex> they should be created during the build
[13:27] <ThreeOfEight> alright
[13:28] <directhex> makes life easier - your clean rule can just go "rm -r debian/tmp"
[13:29] <ThreeOfEight> unrelated question, is there an easy way to construct an entire path?
[13:29] <ThreeOfEight> like, one command instead of mkdir debian/tmp; mkdir debian/tmp/usr and so on
[13:29] <directhex> try "-p"
[13:30] <directhex> as in "mkdir -p debian/tmp/usr/lib/foogame/" will create every piece of that chain
[13:30] <ThreeOfEight> Aaah
[13:30] <ThreeOfEight> I just read the man file, but it seems like I failed to see that option
[13:30] <ThreeOfEight> thanks
[13:32] <joaopinto> directhex, doesn't dh_clean rm debian/tmp already ?
[13:32] <ThreeOfEight> I think so
[13:32] <directhex> joaopinto, maybe. even better
[13:32] <ThreeOfEight> That's why I thought it's supposed to be created during build
[13:32] <ThreeOfEight> I built it and tmp was gone
[13:32] <joaopinto> ThreeOfEight, you can also use debian/dirs
[13:32]  * directhex runs deprecated dh_prep calls on joaopinto 
[13:32] <ThreeOfEight> For what?
[13:32] <joaopinto> which takes care of the dirs creation
[13:32] <ThreeOfEight> ah okay
[13:33] <joaopinto> assumming your rules call dh_installdirs somehow
[13:33] <ThreeOfEight> yes
[13:33] <ThreeOfEight> so I just but, er
[13:34] <ThreeOfEight>  /usr/games into dirs?
[13:56] <ThreeOfEight> I don't get it... I did move my binary to debian/tmp/usr/games, but it doesn't get included into the package
[13:57] <joaopinto> ThreeOfEight, do you have debian/install with the file you need ?
[13:57] <Laney> you have to copy from there to the package build directories
[13:57] <Laney> debian/tmp is just a staging area
[13:57] <joaopinto> and your rules call  dh_install  ?
[13:57] <ThreeOfEight> oh
[13:57] <ThreeOfEight> right right...
[13:58] <ThreeOfEight> so what exactly do I put into debian/install
[13:58] <joaopinto> ThreeOfEight, debian/tmp/usr/games
[13:58] <Laney> debian/tmp/usr/games
[13:58] <ThreeOfEight> okay
[13:58] <joaopinto> dh_install will strip the debian/tmp...
[13:58] <Laney> "the stuff you want in your package"
[13:58] <joaopinto> for the target name
[13:58] <ThreeOfEight> well then I could just as well write debian/tmp, aye
[13:59] <joaopinto> on you case yes, since you want it all :p
[14:00] <ThreeOfEight> Okay, thanks everyone, I think it works
[14:01] <joaopinto> :)
[14:19] <qense> The Guake package is using "gconf-schemas --register guake.schemas > /dev/null" to install the file /data/guake/guake.schemas in its postinst script. Now there is bug #366621, with some people reporting that the schemas are not properly installed. Could this be fixed by switching to "gconftool-2 --makefile-install-rule {path}", and which of the two ways is encouraged?
[15:06] <cemc> is there a way to tell pbuilder to use something other than tar+gzip for the base.tgz ?
[15:09] <hyperair> cemc: try reimplementing the function create_basetgz() in your .pbuilderrc
[15:09] <hyperair> it may or may not work
[15:09] <hyperair> the original is in /usr/lib/pbuilder/pbuilder-modules
[15:09] <hyperair> hmm no it won't work
[15:09] <hyperair> well you could dpkg-divert it away and edit it directly =p
[15:11] <cemc> I just thought why not try to use pigz for example
[15:12] <hyperair> is it better?
[15:12] <hyperair> hmm parallel eh
[15:12] <hyperair> interesting
[15:13] <cemc> well honestly I didn' try it,
[15:13] <cemc> but I tried pbzip2 on a quad-core,
[15:13] <cemc> and it is ~4x faster
[15:13] <hyperair> in all honesty, gzip is pretty damn fast, so the bottleneck is probably already your disk i/o
[15:13] <hyperair> bz is something else entirely
[15:13] <cemc> with 4gb ram it's likely cached
[15:13] <hyperair> bzip2 takes damn long.
[15:15] <cemc> and with tmpfs as buildplace I think it would be worth a try :)
[15:16] <bddebian> Heya gang
[15:16] <\sh> anyone needs a hand regarding merging?
[15:16] <hyperair> cemc: i was talking more of the writing.
[15:17] <hyperair> cemc: tar -czf reads the entire chroot, tarballs it, gzips it, and writes it to disk
[15:17] <hyperair> the bottleneck is probably writing
[15:17] <hyperair> since the files are probably cached, as you said
[15:17] <hyperair> cemc: if you've got enough disk space, i'd suggest cowbuilder instead.
[15:18] <bddebian> Hey if you folks are merging any packages that are orphaned in Debian, let me know and I'll try to upload changes to Debian so you can sync. :)
[15:19] <cemc> hyperair: tar -czf is rarely used, only when building the base, right? if one does a lot of package building, it gets tar -xzf 'd more, without changing. that's what I was thinking about. but I can try cowbuilder too
[15:20] <cemc> of course -x'ing is not that cpu intensive as -c'ing ;)
[15:20] <hyperair> cemc: but even -xzf writes a lot of data. in fact, it writes more than it reads
[15:20] <hyperair> -xzf writes more than it reads, and -czf reads more than it writes.
[15:20] <hyperair> but both involve quite a lot of writing
[15:22] <cemc> that's true. but I have a tmpfs /cache where all the -x'ing and compiling/building is going on, so there's no real writing when -x'ing
[15:22] <cemc> how's cowbuilder different anyway?
[15:25] <geser> cemc: a pbuilder on a tmpfs is pretty fast
[15:26] <cemc> geser: I know ;)
[15:26] <\sh> sbuild with local archive on a dl385 with 10k hds is fast too ,-)
[15:27] <hyperair> but it's more of a pain to setup
[15:27] <\sh> hyperair, hmm..no...mk-sbuild-lv is doing that for you, but right, you need to use debmirror to mirror the archives ;)
[15:27] <hyperair> see? what a pain >_>
[15:27] <hyperair> and there's no --autocleanaptcache
[15:28] <hyperair> besides, i don't like the idea of a fix-sized volume
[15:28] <geser> I use apt-cacher-ng for my pbuilder to cache the needed debs
[15:28] <hyperair> but why?
[15:29] <cemc> hyperair: so what would I need to hack exactly to use something other than tar+gzip?
[15:29] <cemc> just for the heck of it :)
[15:29] <\sh> hyperair, http://paste.ubuntu.com/314164/ <- it's enough for me ;)
[15:30] <hyperair> cemc: change tar -czf and -xzf to tar -c | pigz -c > file and cat file | tar -x | pigz -dc respectively
[15:30] <hyperair> cemc: dig around in /usr/lib/pbuilder
[15:30] <hyperair> \sh: that is HUGE
[15:31] <\sh> hyperair, no :)
[15:31] <hyperair> well for the time being, as long as i'm on this campus, i live on the same LAN as a full ubuntu mirror so i don't really care about caching really =\
[15:32] <hyperair> \sh: 450G is not big to you?!
[15:32] <\sh> hyperair, there is still place on the iscsi msa ;)
[15:32] <\sh> hyperair, nope
[15:32]  * hyperair whacks \sh 
[15:32] <hyperair> hmph
[15:32] <hyperair> i've only got 320G
[15:33] <hyperair> and i get touchy when my pbuilder's aptcache exceeds 1G
[15:33] <\sh> hyperair, hd space is one thing I have enough of
[15:33] <hyperair> blargh!
[15:34] <hyperair> i used to live on a 160G hard disk
[15:34] <hyperair> then it died prematurely
[15:34] <\sh> next week I'll reactivate some of my old 7TB machines
[15:34]  * hyperair wants.
[15:34] <\sh> let's see if they are stable with a new raid controller
[15:35] <\sh> and a new backplane
[15:58] <ThreeOfEight> Bloody hell... okay, for some reason, my files still don't get moved into the package, even though I created a debian/install file which lists the directory
[16:02] <ThreeOfEight> sorry, did anyone reply? I was gone for some time
[16:02] <joaopinto> TheMuso, is dh_install invoked when you run debuild ?
[16:02] <joaopinto> ops, was ThreeOfEight
[16:03] <ThreeOfEight> I'm calling dpkg-buildpackage
[16:03] <ThreeOfEight> but... wait, I'll look
[16:05] <ThreeOfEight> it calls dh_installdirs, installchangelogs, installdocs, installman and installdeb
[16:05] <gnomefreak> anyone know if pulseaudio-module-udev was replaced by another package?
[16:06] <gnomefreak> sorry in lucid
[16:09] <ThreeOfEight> When am I supposed to call dh_install?
[16:14] <shankao> hi, I'm trying to get a new package uploaded to REVU, but although I get dput success, my revu page shows no uploaded packages by me... I have my keys correctly configured and used to sing the package that also contain the original sources
[16:14] <shankao> is there anything missing?
[16:19] <gnomefreak> shankao: IIRC it will show up on next refresh on revus end
[16:21] <ThreeOfEight> Where and how am I supposed to call dh_install if I want it to put everything in debian/tmp into the right place?
[16:22] <shankao> gnomefreak: ok, thanks... is that something automatic (like periodic refresh each hour) or manual?
[16:23] <gnomefreak> shankao: yes its automatic but its been a while sinc ei used revu
[16:25] <directhex> ThreeOfEight, how much of your "binary" rule is abnormal? is it just assorted dh_* commands?
[16:25] <ThreeOfEight> What do you mean abnormal?
[16:25] <directhex> ThreeOfEight, things that aren't just dh_* commands
[16:25] <ThreeOfEight> binary: binary-indep binary-arch
[16:26] <ThreeOfEight> binary-indep and binary-arch both call install
[16:26] <ThreeOfEight> and binary-arch also has lots of dh_'s
[16:26] <ThreeOfEight> but that's it
[16:26] <ThreeOfEight> anyway, I got it working now, somehow
[16:26] <directhex> okay. delete binary, binary-indep and binary-arch. then just write
[16:26] <directhex> binary:
[16:27] <directhex>         dh $@
[16:27] <ThreeOfEight> By removing dh_prep and manually including dh_install in install:
[16:27] <ThreeOfEight> erm
[16:27] <ThreeOfEight> okay I'll try
[16:27] <directhex> (make sure debian/compat contains the number 7)
[16:27] <ThreeOfEight> it does
[16:27] <directhex> then the "dh" command works
[16:27] <ThreeOfEight> what about that .PHONY part down there
[16:28] <directhex> shouldn't be needed in simple cases, really
[16:28] <ThreeOfEight> and what am I supposed to put in install and build?
[16:29] <directhex> given you don't have a makefile, i'd leave them be for now
[16:29] <ThreeOfEight> Right now, I have build calls build-stamp (for some reason)
[16:29] <ThreeOfEight> okay
[16:33] <cemc> hyperair: ok, I'll try that, thx
[16:33] <hyperair> cemc: np
[16:33] <ThreeOfEight> okay, now dh_install (automatically called by dh $@) doesn't find the directory I specified in debian/install anymore
[16:34] <ThreeOfEight> ...because dh_prep deletes it before dh_install is called
[16:34] <ThreeOfEight> odd
[16:45] <ThreeOfEight> Never mind, I worked around it, just left out dh_prep
[17:09] <Vorador> Hi. Could someone help with PPA builds? The problem is that the build-bot installs the wrong version of software (I have the needed version in my ppa already built, but it installs ubuntu version instead) and package building fails because of that. Build log -> http://launchpadlibrarian.net/35424976/buildlog_ubuntu-karmic-lpia.audacious-plugins_1.5.1-2ubuntu3~ppa1_FAILEDTOBUILD.txt.gz Package list -> https://launchpad.net/~sandshrew/+
[17:09] <Vorador> archive/ppa/+packages
[17:14] <Adri2000> RainCT: do you know someone called chancellor? (he unassigned you from bug #161762)
[17:14] <jgoppert> anyone know why my pbuilder would pick up some packages on my mirror but say that others are virtual packages and fail out ??
[17:16] <jgoppert> I did the obvious stuff like apt-get update. The packages install fine through apt, have my ppa set as the other mirror in my pbuilderrc
[17:20] <jgoppert> lol pbuilder update, stupid me
[17:24] <pkern> jdong: Well, just changing the version number and the suite target on LP: #365770 can hardly require resubscription of motu-sru, no?  I don't see any "ACK otherwise" there.
[17:29] <Vorador> So, nobody knows how to fix the issue with dependences?
[17:33] <ScottK> Vorador: Without looking, I'd guess you uploaded something with a lower version number than what's in the archive.
[17:33] <ScottK> Vorador: We work on developing Ubuntu here, so PPA questions aren't a priority for a lot of people.
[17:34] <Vorador> ScottK, yes I uploaded lower version.  Anyway, where I could ask PPA questions? Is there anything better than #ubuntu?
[17:35] <Vorador> [lower than the one in ubuntu default repos]
[17:35] <ScottK> Vorador: #launchpad maybe.  They seem to think we should anwswer the world's packaging questions for PPAs, so not sure.
[17:36] <Vorador> Ok, i'll try...
[17:36] <RainCT> Adri2000: uh? No, I don't think so
[17:37] <Adri2000> RainCT: that's what I thought. well, dunno what he is doing with the bug...
[17:44] <jdong> pkern: one can certainly argue a re-ack is superfluous
[17:45] <jdong> and I'd agree with that ;-)
[17:45] <jdong> it was more of "please resubscribe -sru if my attention is needed again" to reduce the clutter of subscribed bugs
[17:46] <RainCT> Adri2000: well, anyway I haven't started doing any of the Ajax yet (waiting for Scott to merge the design stuff)
[17:46] <pkern> jdong: So I fix that and upload?
[17:48] <jdong> pkern: yes please; I just commented on the ticket to the same effect
[17:55] <ScottK> jdong: You and probably TheMuso need to decide what to do about the currently pending lmms SRU upload.  It got shoved in the queue at the last second when upstream said "Oh, you want these patches too", but doesn't have a proper bug/test cases/etc.
[18:04] <Adri2000> RainCT: ok
[18:24] <jdong> ScottK: I'll take a look at that tonight
[18:24] <jdong> got a midterm in an hour
[18:24] <jdong> [which I'm gonna fail]
[18:24] <ScottK> Then you may as well keep working on Ubuntu.  ;-)
[18:24] <ScottK> jdong: OK.  Thanks.
[18:26] <jdong> LOL
[18:26] <jdong> I feel the same way at times
[18:26] <jdong> stop putting evil thoughts in my head
[18:27] <jdong> *starts filling out drop-subject form in preparation for the midterm*
[20:05] <DktrKranz> james_w: have you access to sync-blacklist?
[20:06] <james_w> yes
[20:13] <DktrKranz> james_w: mind add entries for gdebi (which already slipped in, luckily with no harm) and ubuntu-dev-tools (actually in Debian NEW)
[20:14] <james_w> nope
[20:14] <james_w> can you version ubuntu-dev-tools such that it won't happen?
[20:14] <james_w> just makes more sense that way
[20:15] <DktrKranz> are there special versions which are excluded from autosync?
[20:16] <DktrKranz> (for native packages)
[20:16] <james_w> done
[20:16] <james_w> don't think so
[20:17] <DktrKranz> I could eventually use ~debian1
[20:18] <Laney> DktrKranz: so what's the plan there?
[20:18] <Laney> do we upload to debian now?
[20:19] <Laney> what about getting other scripts into eg devscripts?
[20:48] <ScottK> Many of the scripts in u-d-t aren't really Ubuntu specific.
[20:53] <DktrKranz> Laney: some of them could be eventually proposed for merging into devscripts, some are really Ubuntu-specific, some have already some counterpart in devscripts (or similar packages)
[20:54] <DktrKranz> nhandler's summary is a good starting point
[20:56] <DktrKranz> james_w: FYI, I updated launchpadlib and dependant packages to latest version, most of them (if not all) could be synced now
[20:56] <james_w> DktrKranz: great, thanks
[20:57] <DktrKranz> I have only discovered a drawback in restfulclient unicode implementation which breaks u-d-t (buildd, at least), patch to fix it is http://people.debian.org/~dktrkranz/u-d-t_unicode.patch
[20:57] <DktrKranz> s/patch/workaround/
[21:03]  * RoAkSoAx is happy... lucid pbuilder creation succeeded... 
[21:12] <jgoppert_> can anyone tell me why launchpad fails to import my git repository from sourceforge?
[21:13] <cody-somerville> ask in #launchpad
[21:13] <jgoppert_> thanks
[22:07] <ari-tczew> any sponsors are now working on lucid?
[22:25] <geser> if I find time then yes
[22:30] <chrisccoulson> i'm still working on karmic SRU's :(
[22:31] <RaXOR> hi 2 all, may be it's not right to start my speech like that, but i want to know how can usual person join soft developers team for ubuntu in gnome or kde ??
[22:32] <RaXOR> or if you can give me any information about i searching... please
[22:33] <RaXOR> i'm a programmer and very interested in ubuntu project
[22:33] <ScottK> RaXOR: For KDE, see #kubuntu-devel and ask.
[22:33] <RaXOR> thx
[22:33] <RaXOR> and for gnome ?
[22:34] <RaXOR> i have asked for kde cose of using qt libraries
[22:35] <RaXOR> thx #ubuntu-devel is a nice room... i hope =) buy
[22:36] <geser> for gnome: #ubuntu-desktop
[22:36] <RaXOR> thx 2 u =)
[22:36] <geser> there are the persons working on the gnome packages
[22:50] <jgoppert_> i've got a .so that depends on another .so, works fine, make dist check works, but when running debuild when trying to build some shared libraries it fails, can you guys help?
[22:52] <jgoppert_> i think i spotted it, missing \ in my automake file :-)
[22:53] <TheMuso> directhex: You wre after me last night?
[22:54] <directhex> TheMuso, yeah, prematurely it seems
[22:55] <directhex> TheMuso, banshee with a11y is un banshee-daily ppa... but it's disabled in build due to needing an exact version of gtk# which isn't in the archive
[22:59] <TheMuso> directhex: ah ok
[23:00] <jgoppert_> dh_shlibdeps
[23:00] <jgoppert_> dpkg-shlibdeps: error: no dependency information found for /usr/lib/libcxcore.so.4 (used by debian/uvsim1/usr/lib/libuvsimSensing.so.0.0.0).
[23:00] <jgoppert_> have you guys seeen this sort of thing?
[23:19] <jgoppert_> looks like i left out .shlibs.local
[23:33] <Laney> DktrKranz: I mean, do we upload to debian and sync now
[23:33] <Laney> or are you going to sync back from debian or or or?
[23:33] <Laney> from ubuntu to debian even
[23:40] <jgoppert_> how do you get the shlib file to install should it be lib lib1.shlib?
[23:40] <jcastro> ScottK, ok talked to elmo and he agrees that keeping old gobby is the sanest thing. I've updated the wiki page and I've asked jono to mention it at the opening plenary.
[23:42] <ScottK> jcastro: Excellent.
[23:42] <ScottK> At least it's decided in advance
[23:42] <DktrKranz> Laney: I asked to sync-blacklist u-d-t for now, I don't plan to have many changes in Debian that I won't push back to trunk, but it could happen (as happened in gdebi, for instance)
[23:42] <jgoppert_> got it, uncomment dh_makeshlibs and my life is easy.. whew
[23:43] <DktrKranz> Laney: I think it's better upload in Ubuntu as upstream first, and then in Debian if needed
[23:43] <Laney> hmm
[23:45] <Laney> yeah I think it makes more sense to treat this as a special case reversal of the normal package flow
[23:45] <Laney> so you as Debian maintainer can take care of syncing it back to unstable
[23:46] <DktrKranz> the main reason I listed as maintainer is to avoid bouncing
[23:46] <DktrKranz> *myself
[23:48] <Laney> well someone has to take care of it